Porteus-v5.01 updates

[Ed_P]

Round three of security/bugfix updates for v5.01 are now available (as of Feb 29 2023)

I know we are not in the same time zone but 2023!! My calendar shows 2024. Is Feb 29 right?

Added in 12 minutes 22 seconds:
I just checked the ISOs, (http://mirrors.dotsrc.org/porteus/x86_64/current/) they're date is Mar 6 2024! Shouldn't the 2 Updates be Mar 6 2024 also?

[ncmprhnsbl]

My calendar shows 2024.

lol, the hazards of recycling posts :O ... now fixed.
as for the exact dating of modules, versions, and folders, as long as the internal ver date is newer than the folder date on the server, the updater will work.
the date of the ISOs just represents some lag time around building and uploading them.

[Ed_P]

I'm confused.

n Mar 7, 2024 I created a new Porteus 5.01 Cinnamon ISO. The dates on the booted iso show all the files with a Mar 5 2024 date.

Code: Select all

guest@porteus:/mnt/isoloop/porteus/base$ ls -on
total 392820
-rw-r--r-- 1 0 108732416 Mar  5 16:34 000-kernel.xzm
-rw-r--r-- 1 0 128954368 Mar  5 16:41 001-core.xzm
-rw-r--r-- 1 0 117542912 Mar  5 16:41 002-xorg.xzm
-rw-r--r-- 1 0  21655552 Mar  5 16:41 002-xtra.xzm
-rw-r--r-- 1 0  25362432 Mar  5 17:05 003-cinnamon.xzm
guest@porteus:/mnt/isoloop/porteus/base$ 

Today I ran the Porteus Update app and it downloaded a new 003-Cinnamon.xzm file. It shows a date of Dec 30, 2023! Not Mar 2024.

Code: Select all

guest@porteus:/mnt/nvme0n1p7/porteus5.0/Modules$ ls -on
total 725388
-rwxrwxrwx 1 1000  25354240 Dec 30 01:32 003-cinnamon.xzm*

The date of the 003-cinnamon.xzm in my booted system is Aug 7, 2023

Code: Select all

guest@porteus:/mnt/live/memory/images$ ls -on
total 0
drwxr-xr-x  5 0  61 Mar  5 12:26 000-kernel.xzm/
drwxr-xr-x 20 0 305 Mar  1 06:24 001-core.xzm/
drwxr-xr-x 10 0 154 Mar  1 06:29 002-xorg.xzm/
drwxr-xr-x  6 0  72 Mar  1 06:34 002-xtra.xzm/
drwxr-xr-x 10 0 129 Aug  7  2023 003-cinnamon.xzm/
drwxr-xr-x  7 0  82 Feb  4  2023 07-printing-x86_64-2023-02-04.xzm/

guest@porteus:/mnt/live/memory/images$ 

And the dates on my system stats show Sept 22, 2023:

Code: Select all

~#  uname -a
Linux porteus.example.net 6.6.20-porteus #1 SMP PREEMPT_DYNAMIC Tue Mar  5 20:06:09 MSK 2024 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20240301
002-xorg.xzm:20240301
002-xtra.xzm:20240301
003-cinnamon.xzm:20230922
initrd.xz:20230923

~#  ls -l /mnt/live/memory/images
000-kernel.xzm : Mar 5 12:26
001-core.xzm : Mar 1 06:24
002-xorg.xzm : Mar 1 06:29
002-xtra.xzm : Mar 1 06:34
003-cinnamon.xzm : Aug 7 2023
07-printing-x86_64-2023-02-04.xzm : Feb 4 2023

firefox-122.0-x86_64-en-US.xzm : Jan 27 23:51
mychanges.xzm : Mar 12 03:23
wmctrl-1.07-x86_64-2salix15.0.xzm : Feb 6 11:54

~#  cat /proc/cmdline
quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-240306.iso volume=33 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2

ISO: /ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64-240306.iso

So my Mar 07, 2024 system has a Aug 7, 2023 Cinnamon mod showing a Sept 22 2023 date, which will get updated to a Dec 29, 2023 Cinnamon mod Mar 10, 2024.

[ncmprhnsbl]

yep, i messed up,
003-cinnamon.xzm:20230922 should have either: been in a folder dated 20230922 or older
or been dated internally 20231229 or newer for the 20231229 update folder (and probably the other 003- modules)
i should have it fixed one way or another this week.
in the meantime, since the 5.01 release there's only been one 003- update so if you've done it once you can deselect it when using the updater tool.
and the ISOs are up to date so no need update at this time.

[bour59]

update-browser -f
says current = 124.0
should be 125.0.1

Now it's ok

[ncmprhnsbl]

update-browser -f
says current = 124.0
should be 125.0.1

Now it's ok

thanks for the heads up mozilla in their wisdom decided to skip 125.0 this time or perhaps they've decided on some "sanity" in their versioning regime..

yep, i messed up,
003-cinnamon.xzm:20230922 should have either: been in a folder dated 20230922 or older
or been dated internally 20231229 or newer for the 20231229 update folder (and probably the other 003- modules)
i should have it fixed one way or another this week.
in the meantime, since the 5.01 release there's only been one 003- update so if you've done it once you can deselect it when using the updater tool.
and the ISOs are up to date so no need update at this time.

correction: only the 003-DE modules on the ISOs are out of date and the updates on the server are correct ... fix coming.

[insomnia]

Tried to install VMWare tools on v5.01 but failed to find Perl to execute the installer. Why was it dropped and how to add Perl there?

[ncmprhnsbl]

Tried to install VMWare tools on v5.01 but failed to find Perl to execute the installer. Why was it dropped and how to add Perl there?

it was dropped to save a few megs of space since it wasn't needed for basic operation
i was skeptical at the time and it will most likely return to 001-core in future editions.
at present it's available in 05-devel(which you may need for VMWARE installation anyway) or directly from slackware(with getpkg or slapt-mod)