Ed_P wrote: ↑20 Dec 2021, 15:33
Ref your USM update problem, you need to run the usmupdate2021 script.
Sadly, that creates other errors while claiming the usm update was successful.
I executed your script as root and this is the result (only the last part printed here, the successful updates do not bother)
Code: Select all
Starting slackonly database update
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz DONE
gzip: /var/usm/slackonly/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 248
Could not decompress: CHECKSUMS.md5.gz
==============================================================================
ls /var/usm/slacky/
CHECKSUMS.md5 LIBS.TXT OPTIFEST PACKAGES.TXT
ls /var/lock/usm*
ls: cannot access '/var/lock/usm*': No such file or directory
USM Update done.
__________________________
Thanks for the find, the download is slow and… delicate:
Code: Select all
geany-plugins-1.30- 62%[++++++++++=> ] 763.20K 21.3KB/s in 16s
2021-12-20 21:01:33 (6.16 KB/s) - Connection closed at byte 781515. Retrying
Good there is a md5sums text in there as well (called CHECKSUMS.md5 ).
I definitely check the md5sum when geany-1.30.1-i686-s750.txz is finally downloaded. Which can take its time considering the
gigantic download speed of --.-KB/s: </irony>
Code: Select all
64%[===========> ] 1.93M --.-KB/s eta 50s
but all is well that ends well:
Code: Select all
guest@porteus:/mybin/linux/porteus/4.0_i486$ grep geany-1.30.1-i686-s750.txz CHECKSUMS.md5
85c4859b9d4a6d94768db320289d307a ./geany-1.30.1-i686-s750.txz
guest@porteus:/mybin/linux/porteus/4.0_i486$ md5sum geany-1.30.1-i686-s750.txz
85c4859b9d4a6d94768db320289d307a geany-1.30.1-i686-s750.txz
Added in 4 minutes 27 seconds:
Update
I presume that
defaulttexteditor is a Puppy thingy?
root@porteus:/mybin/linux/porteus/4.0_i486# txz2xzm geany-1.30.1-i686-s750.txz
Verifying package geany-1.30.1-i686-s750.txz.
Installing package geany-1.30.1-i686-s750.txz:
PACKAGE DESCRIPTION:
# Light weight powerful gtk text editor and IDE
#
Executing install script for geany-1.30.1-i686-s750.txz.
/bin/bash: line 3: usr/local/bin/defaulttexteditor: No such file or directory
chmod: cannot access 'usr/local/bin/defaulttexteditor': No such file or directory
Setting geany as defaulttexteditor
Package geany-1.30.1-i686-s750.txz installed.
Creating /mybin/linux/porteus/4.0_i486/geany-1.30.1-i686-s750.xzm
(highlighting by me)
Seems that part was just ignored:
Code: Select all
root@porteus:/mybin/linux/porteus/4.0_i486# lsxzm geany-1.30.1-i686-s750.xzm |grep default
root@porteus:/mybin/linux/porteus/4.0_i486#
Added in 8 minutes :
I think I need to tweak the .desktop file.
It sets up geany in the main-menu sub-menu of "Other" instead of "Programming" like the x86-64 geany does…
I prefer
programming as sub-menu and category for geany, thank you very much. </picky>
A geany filed in just "other" …
- just no.
Added in 2 minutes 58 seconds:
And I hope the work I put in creating a dark geany by changing its default settings to look better with the dark XFCE theme also works for that i586 geany without any further tweaking. (Lazy Rava is lazy)
But I have to visit my main machine for getting the geany default settings (I have one for /home/guest and one for /root - even when technically they are the same, I just do not want a file with guest.users ownership in /root . Also no unwritable-for-guest file in /home/guest owned by root either.
)