LxPupSc: Woof-CE, Slackware-Current, LXDE build 13-Jun-2020
Fresh install of (Ally's) 01.03 shutdown cleanly half a dozen times.
Let's hope that Marv will have a similar experience.
Let's hope that Marv will have a similar experience.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Thanks Ally - sourceforge should now be online again.ally wrote:sourceforge (ISO) download broken (404) so mirrored here:
http://archive.org/download/Puppy_Linux ... 03-pae.iso
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Using the delta generated iso I've done 6 shutdowns on the core 2 duo and 6 to 8 on the Bay-Trail desktop and all have been clean. I'll be using both machines today so I'll do a couple at the end of the day but looks good from here.mavrothal wrote:Fresh install of (Ally's) 01.03 shutdown cleanly half a dozen times.
Let's hope that Marv will have a similar experience.
Edited: delta generated iso md5sum is fine.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Many thanks both.....and apologies that I've caused you both extra investigation and testing work....Marv wrote:Using the delta generated iso I've done 6 shutdowns on the core 2 duo and 6 to 8 on the Bay-Trail desktop and all have been clean. I'll be using both machines today so I'll do a couple at the end of the day but looks good from here.mavrothal wrote:Fresh install of (Ally's) 01.03 shutdown cleanly half a dozen times.
Let's hope that Marv will have a similar experience.
Edited: delta generated iso md5sum is fine.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Meh, If you weren't aproducin, we wouldn't be atestin. A couple of fixes that have gotten into woof-CE have also come out of these last couple of rounds so.... Thankspeebee wrote:Many thanks both.....and apologies that I've caused you both extra investigation and testing work....
Edit: End of day shutdowns on both core 2 duo and Bay-Trail both normal.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Apologies if this has been covered elsewhere, I didn't find it in a quick look. gpicview segfaults on jpg files for me, ok on png. Running 16.01.03 installed frugal to core 2 duo laptop.
Edit: version
Edit: version
- Attachments
-
- Screenshot.jpg
- (62.62 KiB) Downloaded 310 times
Last edited by Marv on Tue 02 Feb 2016, 21:35, edited 1 time in total.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Thanks @Marv - just checked and gpicview seems to work ok for me on jpg files.Marv wrote:Apologies if this has been covered elsewhere, I didn't find it in a quick look. gpicview segfaults on jpg files for me, ok on png. Running 16.01.03 installed frugal to core 2 duo laptop.
Edit: version
Can you pm me the problem jpg?
Maybe it needs to be rebuilt for current (still using the 14.1 pet) ....although jpeg is one of the areas of change in current as it uses libjpeg-turbo....problem not reported previously...
Please try the pet below compiled in slacko-current - thanks
Thanks for report @gcm
Cheers
peebee
- Attachments
-
- gpicview-0.2.4-i686_sc.pet
- (49.95 KiB) Downloaded 198 times
Last edited by peebee on Sat 06 Feb 2016, 11:21, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
No need, Mea Culpa. I had, in /usr/lib in my config update file from 16.01.2 to 16.01.03, a symlink from libjpeg.so.62 to libjpeg.so.62.0.0. This overwrote the symlink from libjpeg.so.62 to libjpeg.so.62.1.0 in the main SFS and caused gpicview to fail on jpegs. Pulling that symlink and libjpeg.so.62.0.0 from the savefile fixed it. I don't know when that got in as I am pretty sure I started from scratch at 16.01.2. Sorry.peebee wrote: Thanks @Marv - just checked and gpicview seems to work ok for me on jpg files.
Can you pm me the problem jpg?
Cheers
peebee
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
LxPupSc-16.02.02-pae
Updated - 13-feb-2016
LxPupSc-16.02.03-pae.iso {devx} {kernel 4.3.3-EmSeei686 sources}
iso md5 = aa84312ad7d5320aa318f353d1232e17
{SlackoC-16.02.3} is made from Slackware-current as of 11-feb-2016
BUILD_FROM_WOOF='testing;a5d36ab;2016-01-17 08:35:59 +0200'
Main changes are:
- Firefox-44.0.2
- openssl-1.0.2f
LxPupSc-16.02.03-pae.iso {devx} {kernel 4.3.3-EmSeei686 sources}
iso md5 = aa84312ad7d5320aa318f353d1232e17
{SlackoC-16.02.3} is made from Slackware-current as of 11-feb-2016
BUILD_FROM_WOOF='testing;a5d36ab;2016-01-17 08:35:59 +0200'
Main changes are:
- Firefox-44.0.2
- openssl-1.0.2f
Last edited by peebee on Wed 17 Feb 2016, 09:05, edited 9 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
LxPupSc-16.02.01-pae
Iso downloaded, md5sum checked, Grub4Dos frugal install on core 2 duo Fujitsu S6520 laptop updating savefile from 16.01.03. All connections and configurations preserved (and hopefully no user errors ) Continuing to use as daily. Posting from Firefox now using my common profile.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Firefox in 16.02.01complains in many sites about the https certificates even if other pups and browsers don't. Is it only me?
Other than that all is good.
Other than that all is good.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Just tried a bunch of https sites here in UK (maybe 10 or so) and didn't have any problems here....mavrothal wrote:Firefox in 16.02.01complains in many sites about the https certificates even if other pups and browsers don't. Is it only me?
Other than that all is good.
Can you give us the url of a problem site? Thanks.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Version 16.02.02
More slackware-current changes yesterday....
Post above has been updated to version 16.02.02
n.b. name change for sfs's - slackocurrent is now SlackoC - so savefiles etc. will need to be renamed to match.
Post above has been updated to version 16.02.02
n.b. name change for sfs's - slackocurrent is now SlackoC - so savefiles etc. will need to be renamed to match.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hi peebee,
Any chance of deltas? With frequent updates it would help with the bandwidth/quotas.
Thanks,
Any chance of deltas? With frequent updates it would help with the bandwidth/quotas.
Thanks,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Is not important by now as 02.02 and the updated FF appears OK.peebee wrote:Just tried a bunch of https sites here in UK (maybe 10 or so) and didn't have any problems here....mavrothal wrote:Firefox in 16.02.01complains in many sites about the https certificates even if other pups and browsers don't. Is it only me?
Other than that all is good.
Can you give us the url of a problem site? Thanks.
BTW on the first shutdown the superimposition of the shutdown dialogs on the session control window is not very appealing and can be confusing or mistake-prone at times (clicking below). You may want to close/minimise the session control window when shutdowncofig runs.
BTW2 when any of these is going to make it into woof-CE?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Hi @MarvMarv wrote:Hi peebee,
Any chance of deltas? With frequent updates it would help with the bandwidth/quotas.
Thanks,
I've made a deltas folder - however the 02.01 to 02.02 delta is 45.5MB....
Hi @Mavmavrothal wrote:BTW on the first shutdown the superimposition of the shutdown dialogs on the session control window is not very appealing and can be confusing or mistake-prone at times (clicking below). You may want to close/minimise the session control window when shutdowncofig runs.
BTW2 when any of these is going to make it into woof-CE?
Glad the FF problem seems to have disappeared.
Good suggestion - should be straight forward to fix.
Woof-CE support for SlackoC has some challenges which I'm not sure how to address:
- getting dependencies working in ppm (which you basically implemented) needs a 0dependencies-fix stage after 0setup and before 3builddistro-Z + there are patches needed to 3builddistro-Z
- Packages-puppy-slacko14.1-official needs edits to change 14.1 to current
- 3 repositories are used: slackware-current, slacko-14.1 and my slackware-extras - i.e. it is a mongrel current/14.1 build in reality and I know that 01micko will probably be "doing it properly" at some point
- there is an extra item to go into packages-templates - llvm-cut
Then the LXDE additions do not use Woof-CE at all at the moment....and I'm afraid that I do tend to grab components from many different sources so they'd probably have to all go into slackware-extras and I'd have to construct the database entries for each by hand and I haven't summoned up the enthusiasm to do this yet. Using woofy is so much easier and quicker....
As you can see - I have thought about it - but that's as far as its got I'm afraid
Cheers
peebee
Last edited by peebee on Tue 09 Feb 2016, 21:51, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
assuming that Slacko current is going to be a branch after the 14.2 release too, should not be difficult to add a conditions in the scripts to address this.peebee wrote:Woof-CE support for SlackoC has some challenges which I'm not sure how to address:
- getting dependencies working in ppm (which you basically implemented) needs a 0dependencies-fix stage after 0setup and before 3builddistro-Z + there are patches needed to 3builddistro-Z
If it is to go on I would think that you just need a new file instead of mode'ing 14.1peebee wrote: Packages-puppy-slacko14.1-official needs edits to change 14.1 to current
As you can see Mick is very busy these days... Besides is more fun to do it yourselfpeebee wrote:- 3 repositories are used: slackware-current, slacko-14.1 and my slackware-extras - i.e. it is a mongrel current/14.1 build in reality and I know that 01micko will probably be "doing it properly" at some point
I'm afraid there is no good excuse for that... The LXDE additions (as well as the XFCE) should be in rootfs-packages already.peebee wrote:-Then the LXDE additions do not use Woof-CE at all at the moment....
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==