Sylpheed.sfs and QuiteRSS.sfs created and tested in Fossapup64

[geo_c]

I made working 64bit sfs versions of Sylpheed 3.7.0 and QuiteRSS 0.19.3

Tested and used extensively, working flawlessly in Fossapup64. Simply mount the sfs and entries are added to the Internet category of the puppy menu. Sylpheed is a lightweight, versatile email client, and QuiteRss is a news aggregator.

Sylpheed can be found here:
https://mega.nz/file/XShxAIzA#E4Hp41DPJ ... 9pMh3B0AQ0

QuiteRSS can be found here:
https://mega.nz/file/nPp0xD4Y#IM-4mdBe6 ... XWEuPJBPSo

md5 hash and other sfs files found here:
https://mega.nz/folder/reoShDjA#ONbUYMfog9J7AWe9RVe2Uw

Thanks to all who helped me with scripts, especially @mikeslr

Let me know if you try it, how it works in different puppy versions.

[April]

Being a sylpheed user of some standing ii thought to get these downloads and try them in xenialpup64 7.5

My first attempt from Mega opened fine then poked up this screen below.
I wonder if you knew they did that behind your back .
I certainly did not expect it and I have been with them since they started almost.

Managed to get round it by logging in myself but a new user won't I guess.
Its attached to the IP so if you use a vpn close the browser and come back in with a new vpn.

Ergone(1).jpg (118.69 KiB) Viewed 713 times

[April]

So being an rss news reader fan I thought to get your quiterss sfs.
As above got it down and wanted to try it in Xenialpup64-7.5 and assumed it would probably run ok here.

I copied the file to "home" with my other sfs's removed the ending (opdownload) and then opened "open sfs on the fly" and gave it a try.

I got this message at which point it stumped me .
Any suggestion as to what might be wrong?
I'm just checking the md5 sums now so should have done that first.

With an md5 check I downloaded it again because I got the first download with "opdownload" attached to the name?
Downloaded it again and got it right this time but then it went dead and starting it manually gave the console code below.

Ergone(2).jpg (8.3 KiB) Viewed 712 times

root# quiterss
quiterss: error while loading shared libraries: libQt5WebKitWidgets.so.5: cannot open shared object file: No such file or directory
root#

So I guess it won't run in Xenialpup64.

[April]

Interestingly the sylpheed version 3.7 came down and needed no name change and it appeared to load and run fine but I noticed it was version 3.5 running when I started it from the sfs option window .so it did not load the 3.7 version it seems. Renaming the usr/bin/sylpheed executeable to something else did not help . It would not run 3.7 from the sfs?

Using the built in update button told me there was a later version available and I wondered what might happen there if I tried to update it . Probably try to put the whole lot in with the sfs.

So I think this should run in xenialpup64 but I don't think you have it quite right.

[geo_c]

Interestingly the sylpheed version 3.7 came down and needed no name change and it appeared to load and run fine but I noticed it was version 3.5 running when I started it from the sfs option window .so it did not load the 3.7 version it seems. Renaming the usr/bin/sylpheed executeable to something else did not help . It would not run 3.7 from the sfs?

Using the built in update button told me there was a later version available and I wondered what might happen there if I tried to update it . Probably try to put the whole lot in with the sfs.

So I think this should run in xenialpup64 but I don't think you have it quite right.

Well that's strange, because I'm running from this same sfs and the About screen says it's Version 3.7.0 (Build 1185)

I only built the sfs once, so I'm scratching my head.

Thanks for the heads up. I'll look into it further. And I'll re-upload the file and from the exact copy I'm using.

[geo_c]

So being an rss news reader fan I thought to get your quiterss sfs.
As above got it down and wanted to try it in Xenialpup64-7.5 and assumed it would probably run ok here.

I copied the file to "home" with my other sfs's removed the ending (opdownload) and then opened "open sfs on the fly" and gave it a try.

I got this message at which point it stumped me .
Any suggestion as to what might be wrong?
I'm just checking the md5 sums now so should have done that first.

With an md5 check I downloaded it again because I got the first download with "opdownload" attached to the name?
Downloaded it again and got it right this time but then it went dead and starting it manually gave the console code below.

Ergone(2).jpg

root# quiterss
quiterss: error while loading shared libraries: libQt5WebKitWidgets.so.5: cannot open shared object file: No such file or directory
root#

So I guess it won't run in Xenialpup64.

My first impression is that Xenial isn't based on Ubuntu/Fossa based packages. And these packages were downloaded from the Fossapup Puppy Package Manager.

edit: So it seems likely that these sfs packages won't run on anything not Debian/Ubuntu based. I see (as noted below in the next post) that Xenial is Ubuntu/Debian based, but still not Fossa, so there may be libraries missing.

Thanks for the feedback! I'll look at these later today.

[geo_c]

Being a sylpheed user of some standing ii thought to get these downloads and try them in xenialpup64 7.5

Here's a link to the exact Sylpheed sfs that reports as 3.7.0 in my system.

https://mega.nz/file/XShxAIzA#E4Hp41DPJ ... 9pMh3B0AQ0

and the checksum: https://mega.nz/file/iS4QzYbS#TJIktS8Wn ... W2yn8tKD9w

If you have time and don't mind trying again this copy of Sylpheed should be 3.7.0, I made an sfs package one time before this one, but the previous attempt was rolled together with another application and it was over a 1GB, so I'm almost certain that's not the one you downloaded. At any rate this should be right unless something else is going on. Is there any chance that Sylpheed was already installed on your system? Older versions of puppy often came with Sylpheed as the default email client.

In regards to QuiteRss, I checked out the Xenial distribution thread, and although it is an Ubuntu based pup, it may not have the proper libraries for Fossa applications.

[April]

OOps . Should have made it clearer. I'm a Sylpheed user and yes 3.5 is installed on my system.
In a console "sylpheed" brings up the usr/bin/sylpheed program so thets where the 3.5 is probably coming from .

However when running the 3.7 sfs it should load your binary I would have thought but it does not?

[williams2]

3.5 is installed on my system ... when running the 3.7 sfs it should load your binary I would have thought

When sfs files are loaded, the file system in the sfs file is added to the bottom of the aufs file system layers.

The upper layers have precedence over the lower layers.

If you have a file with the same path and name in the upper read/write layer, it will be used and files with the same path and name in lower layers will be ignored.

If there is a file /usr/bin/sylpheed in the save file and if there is a file /usr/bin/sylpheed in a loaded sfs file, then the /usr/bin/sylpheed file in the save file layer will be used and the /usr/bin/sylpheed file in the loaded sfs layer will be ignored. Files in upper layers take precedence over files in lower layers, and the file systems in loaded sfs files are always the lowest layers.

if you install an sfs file, the file system in the sfs file will be copied to the top rw layer (usually the save file/folder) and will take precedence over the other layers.

this will list the 10 upper aufs layers: cat /sys/fs/aufs/*/br[0-9]

[April]

Yes I'm fully aware of that so I renamed usr/bin/sylpheed to " sylpheedtest" and loaded the sfs afresh but it would not run .

Thats why I wondered if something in the sfs is maybe not quite right .

I tried your command but I don't understand the results . Can you explain them to me please?
(honestly I don't understand the command either.)

puppysys(1).jpg (78.15 KiB) Viewed 621 times

[geo_c]

Thats why I wondered if something in the sfs is maybe not quite right .

The sfs was created with a package downloaded from the Fossapup64 package manager, so my feeling is it will only run on Fossapup64, because there are probably missing elements in other puppies or mismatched versions of components.