If you are looking for a specific 32-bit package and you can't find it in any of the 32-bit repos, please post a request for it here.
-
Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Post#1
by Rava » 23 Nov 2020, 00:42
Why for Porteus 3.1 you might ask. Because that version works flawlessly on the outdated Samsung Q40 - unlike Porteus 4.0…
Creating it myself failed.
usm approach:
Code: Select all
root@porteus:/Porteus_modules/system/florence# usm -u all Starting alien database update
Downloading: vercheck.txt DONE
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz DONE
gzip: /var/usm/alien/CHECKSUMS.md5.gz: unexpected end of file
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
usm update_database 270
Could not decompress: CHECKSUMS.md5.gz
==============================================================================
I tried manually
Always checking via
ldd /usr/bin/florence|grep not
first results
Code: Select all
libpng16.so.16 => not found
libxcb-sync.so.1 => not found
libxshmfence.so.1 => not found
libxcb-dri3.so.0 => not found
libxcb-present.so.0 => not found
Manually resolving the above gave 2nd results
Code: Select all
libgtk-3.so.0 => not found
libgdk-3.so.0 => not found
libgbm.so.1 => not found
Manually resolving the above gave 3rd results
Code: Select all
libxkbcommon.so.0 => not found
libwayland-cursor.so.0 => not found
libwayland-egl.so.1 => not found
libwayland-client.so.0 => not found
libepoxy.so.0 => not found
libxkbcommon.so.0 => not found
libwayland-cursor.so.0 => not found
libwayland-egl.so.1 => not found
libwayland-client.so.0 => not found
libepoxy.so.0 => not found
libwayland-client.so.0 => not found
libwayland-server.so.0 => not found
And there I gave up…
looks too much like a never ending story trying to manually resolve the dependencies.
Cheers!
Yours Rava
Rava
-
ncmprhnsbl
- DEV Team
- Posts: 3937
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
-
Contact:
Post#2
by ncmprhnsbl » 23 Nov 2020, 04:38
Rava wrote: ↑23 Nov 2020, 00:42
I tried manually
more information please
like for instance, if it's a package, from where does it come? note 3.1 series uses slackware 14.1 packages and using newer packages would lead to the above issues..
afaiui, slackonly didn't start packaging sbo till 14.2 ..
so the best option would be to compile it yourself.. using the sbo slackbuild, if you so desire.. that way it should use the libs you have..
looks like you'll need(at least) to get libcxb (for 14.1)
https://mirrors.slackware.com/slackware ... i486-1.txz
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
ncmprhnsbl
-
Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Post#3
by Rava » 23 Nov 2020, 11:20
ncmprhnsbl wrote: ↑23 Nov 2020, 04:38
more information please
I thought I explained above: I manually downloaded all named dependencies, and made a dependencies module and then a 2nd dependencies module out of these, which lead to the 3rd and largest so far missing dependencies listing.
I am sure I also need the missing stuff from my above quoted listing 3 - unless your linked file holds all these.
And the usm issue - I first updated usm to the newest version but sadly that did not help much.
Cheers!
Yours Rava
Rava
-
ncmprhnsbl
- DEV Team
- Posts: 3937
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
-
Contact:
Post#4
by ncmprhnsbl » 23 Nov 2020, 12:16
Rava wrote: ↑23 Nov 2020, 11:20
I thought I explained above: I manually downloaded all named dependencies,
yes, but where from? for what version of slackware were these package built?
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
ncmprhnsbl
-
Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Post#5
by Rava » 23 Nov 2020, 12:33
ncmprhnsbl wrote: ↑23 Nov 2020, 12:16
yes, but where from? for what version of slackware were these package built?
since usm did not work I used pkgs.org and checked if dependencies work with slackware 14.1.
I think I do give Porteus 4.0 another go, maybe it works after all.
Cheers!
Yours Rava
Rava
-
Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Post#6
by Rava » 24 Nov 2020, 23:12
ncmprhnsbl wrote: ↑23 Nov 2020, 12:16
yes, but where from? for what version of slackware were these package built?
Please lookie here, it documents a similar
pulled through till success approach by yours truly:
TestDisk & PhotoRec 7.1 (Post by Rava #79940) - I managed to get missing dependencies for Slackers x86_64 testdisk-7.1-x86_64-1cf.txz by rpm2xzm dependencies - when I recall correctly all of these have been for openSUSE Tumbleweed. But its the result that counts
Rava wrote: ↑24 Nov 2020, 23:05
Could that really be the end of the dependency hell line, did I reach the light at the end of the TestDisk & PhotoRec 7.1 tunnel? Seems like it
Code: Select all
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
TestDisk is free data recovery software designed to help recover lost
partitions and/or make non-booting disks bootable again when these symptoms
are caused by faulty software, certain types of viruses or human error.
It can also be used to repair some filesystem errors.
Information gathered during TestDisk use can be recorded for later
review. If you choose to create the text file, testdisk.log , it
will contain TestDisk options, technical information and various
outputs; including any folder/file names TestDisk was used to find and
list onscreen.
Use arrow keys to select, then press Enter key:
>[ Create ] Create a new log file
[ Append ] Append information to log file
[ No Log ] Don't record anything
Code: Select all
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Cannot open testdisk.log: Permission denied
Please enter the full log filename or press Enter
to abort log file creation.
<B
Cheers!
Yours Rava
Rava