Upgrade default packages in Porteus-XFCE-v3.2.2 to latest

[privateip]

Greetings Porteus members,

I am interested to learn how is it the step to upgrade all default packages installed using default iso Porteus-XFCE-v3.2.2-x86_64.iso or 32bit iso,

Objective is to have latest Porteus-XFCE with latest or security fixed packages.

[tome]

You can try in terminal

Code: Select all

usm -u system

[Ed_P]

^ Wow!

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u system

 ##### NOTICE ###### 

Updating the base system should be done while saving changes
otherwise problems may be encountered. You will finish with
both the old and the new package versions due to the modular
concept of Porteus and the aufs file system.

 Press any key to continue.

Updates required:

ca-certificates-20160104-noarch-1 --> ca-certificates-20161130-noarch-1_slack14.2.txz
curl-7.51.0-x86_64-1_slack14.2 --> curl-7.55.0-x86_64-1_slack14.2.txz
dbus-1.10.8-x86_64-1 --> dbus-1.10.8-x86_64-2_slack14.2.txz
freetype-2.6.3-x86_64-1 --> freetype-2.6.3-x86_64-2_slack14.2.txz
glibc-2.23-x86_64-1 --> glibc-2.23-x86_64-4_slack14.2.txz
glibc-solibs-2.23-x86_64-1 --> glibc-solibs-2.23-x86_64-4_slack14.2.txz
glibc-zoneinfo-2016i-noarch-1_slack14.2 --> glibc-zoneinfo-2017b-noarch-1_slack14.2.txz
gnupg-1.4.21-x86_64-1_slack14.2 --> gnupg-1.4.22-x86_64-1_slack14.2.txz
gnutls-3.4.15-x86_64-1_slack14.2 --> gnutls-3.5.8-x86_64-1_slack14.2.txz
libgcrypt-1.7.3-x86_64-1_slack14.2 --> libgcrypt-1.7.8-x86_64-1_slack14.2.txz
libpcap-1.7.4-x86_64-1 --> libpcap-1.8.1-x86_64-1_slack14.2.txz
libpng-1.6.23-x86_64-1 --> libpng-1.6.27-x86_64-1_slack14.2.txz
libsoup-2.52.2-x86_64-2 --> libsoup-2.52.2-x86_64-3_slack14.2.txz
libtiff-4.0.6-x86_64-1 --> libtiff-4.0.7-x86_64-1_slack14.2.txz
libtirpc-1.0.1-x86_64-2 --> libtirpc-1.0.2-x86_64-1_slack14.2.txz
lynx-2.8.8rel.2-x86_64-1 --> lynx-2.8.8rel.2-x86_64-3_slack14.2.txz
openssh-7.3p1-x86_64-1_slack14.2 --> openssh-7.4p1-x86_64-1_slack14.2.txz
openssl-1.0.2j-x86_64-1_slack14.2 --> openssl-1.0.2k-x86_64-1_slack14.2.txz
openvpn-2.3.11-x86_64-1 --> openvpn-2.3.17-x86_64-1_slack14.2.txz
python-2.7.11-x86_64-2 --> python-2.7.13-x86_64-2_slack14.2.txz
rpcbind-0.2.3-x86_64-1 --> rpcbind-0.2.4-x86_64-2_slack14.2.txz
samba-4.4.5-x86_64-1_slack14.2 --> samba-4.4.15-x86_64-1_slack14.2.txz
squashfs-tools-4.3-x86_64-1 --> squashfs-tools-4.3-x86_64-2_slack14.2.txz
sudo-1.8.16-x86_64-1 --> sudo-1.8.20p2-x86_64-1_slack14.2.txz

 Press [r] to remove packages, [q] to quit, or enter to continue.

root@porteus:/home/guest#

A nice command tome.

[privateip]

Thanks for replying,

How tedious would it be to have old packages remove totally, and packing back 000, 001, 002, 003 with latest packages?

Does modular design and aufs will remove files that exists in old package after upgrade to new package?

Code: Select all

dbus-1.10.8-x86_64-1 --> dbus-1.10.8-x86_64-2_slack14.2.txz
freetype-2.6.3-x86_64-1 --> freetype-2.6.3-x86_64-2_slack14.2.txz
glibc-2.23-x86_64-1 --> glibc-2.23-x86_64-4_slack14.2.txz
glibc-solibs-2.23-x86_64-1 --> glibc-solibs-2.23-x86_64-4_slack14.2.txz
intltool-0.51.0-x86_64-2 --> intltool-0.51.0-x86_64-3_slack14.2.txz
libsoup-2.52.2-x86_64-2 --> libsoup-2.52.2-x86_64-3_slack14.2.txz
lynx-2.8.8rel.2-x86_64-1 --> lynx-2.8.8rel.2-x86_64-3_slack14.2.txz
openssl-1.0.2j-x86_64-1_slack14.2 --> openssl-1.0.2k-x86_64-1_slack14.2.txz
squashfs-tools-4.3-x86_64-1 --> squashfs-tools-4.3-x86_64-2_slack14.2.txz
xorg-server-1.18.3-x86_64-2 --> xorg-server-1.18.3-x86_64-3_slack14.2.txz

Above are part of confusing output I got after usm -u system

Wondering why exact version of above programs are considered as upgrade?

ex: there are libsoup-2.53.1, until my system upgraded to libsoup-2.52.2-x86_64-3_slack14.2.txz, USM will not shows
libsoup-2.52.2-x86_64-2 --> libsoup-2.53.1-x86_64-3_slack14.3.txz ?

Or I don't have to bother with exact version upgrade?

[ncmprhnsbl]

How tedious would it be to have old packages remove totally, and packing back 000, 001, 002, 003 with latest packages?

a bit tedious.. (and not guaranteed to work)
the thing with slackware is it's a fixed release(14.2), so apart from a few security patches, there aren't many package upgrades during its lifetime..
however, there is slackware 'current', which a sort of testing repo which will become the next stable release..
have a look at /usr/local/bin/getpkg (in a text editor), this script will download a list of slackware packages, first change (in the script) SLACKVER=14.2 to current
(this is the tedious bit:) get lists of packages from each module ie //var/log/packages and strip version info..
be aware, that some packages have been custom built (look for -jay tag on the end) and these will need to be built from source..
after this you have a folder of packages for each module, so then do:

Code: Select all

ROOT=/path/to/unpacked/module upgradepkg /path/to/packages/*.t*z

overall size will have increased due to stripped stuff(man,sources,locales etc) returning..(i'll try to find the link to the official build scripts for you)

be aware: a new porteus version is in the works, so i wouldnt rush into it

[privateip]

Hi ncmprhnsbl,

Glad to know new Porteus is on the way,

I am not sure if the following method could be considered as clean upgrade:

1. I will use curl in following example.

2. Unpack 001 002 003...

3. Determine which 00X to upgrade.

4. List of files copied during curl installation in /var/log/packages/curl-7.51.0-x86_64-1_slack14.2 ( But it doesn't lists files copied into /var/log/ )

5. Write a program to parse /var/log/packages/curl-7.51.0-x86_64-1_slack14.2

6. Check directory and files in FILE LIST, remove them

7. Download the upgraded package, in this case curl-7.55.0-x86_64-1_slack14.2.xzm

8. Unpack and write a program to parse /var/log/packages/curl-7.55.0-x86_64-1_slack14.2

9. Copy upgraded files into previous working 001 or 002 or 003

10. Repack working 00X and reboot,

[ncmprhnsbl]

4 to 9 > this is what upgradepkg does for you
heres the link for 3.2.2 build scripts: https://www.dropbox.com/s/vh60g0z8w9mqb ... ar.gz?dl=0
handy to learn about configs(see TREE) and stripping..

[privateip]

Thanks for being so helpful.