Requests for current-next (15.0-->15.1)

lancsuk · 01-26-2022, 03:29 AM

Quote:

Originally Posted by drumz

Perhaps I don't understand your request, but doesn't this do exactly what you ask?

https://mirrors.slackware.com/slackw...rent/source/k/

Thank you for pointing that out.

I have created 5.17.0-rc1 and 5.16.2 and it works for me.

Btw, only for completeness I meant an utility similar to make-kpkg for Debian.

John Lumby · 01-26-2022, 08:42 AM

Please include option (or even, gasp, default) for slackpkg to log all changes which it makes to, by default, /var/log/slackpkg.log.

Surely if archlinux pacman can do it, so can slackpkg.

(I now expect someone to tell me it's already there, although some time ago I asked and was told it isn't)

Cheers, John Lumby

fourtysixandtwo · 01-26-2022, 12:58 PM

Quote:

Originally Posted by John Lumby

Please include option (or even, gasp, default) for slackpkg to log all changes which it makes to, by default, /var/log/slackpkg.log.

Surely if archlinux pacman can do it, so can slackpkg.

(I now expect someone to tell me it's already there, although some time ago I asked and was told it isn't)

Cheers, John Lumby

Expectation met!

/var/lib/slackpkg/install.log

fourtysixandtwo · 01-26-2022, 12:58 PM

Quote:

Originally Posted by John Lumby

Please include option (or even, gasp, default) for slackpkg to log all changes which it makes to, by default, /var/log/slackpkg.log.

Surely if archlinux pacman can do it, so can slackpkg.

(I now expect someone to tell me it's already there, although some time ago I asked and was told it isn't)

Cheers, John Lumby

Expectation met!

/var/lib/slackpkg/install.log

Pithium · 01-26-2022, 01:15 PM

15.1 should be a re-release of 15.0 with everything exactly the same. Because operating systems are not something that need to constantly change and grow

John Lumby · 01-26-2022, 08:27 PM

Quote:

Originally Posted by fourtysixandtwo

Expectation met!

/var/lib/slackpkg/install.log

Appetite whetted maybe but expectation still expectant - read https://www.linuxquestions.org/quest...og-4175687965/

I would like it to be in 15.x by default without need for any extras.

Cheers, John Lumby

allend · 01-26-2022, 10:29 PM

Quote:

Please include option (or even, gasp, default) for slackpkg to log all changes which it makes

As slackpkg uses the standard Slackware package tools, then by default all logging goes to /var/log/packages (now symlinked to /var/lib/pkgtools/packages) and directories under /var/log/pkgtools (removed_packages and removed_scripts). These are easily reviewed with 'ls -lt /var/log/packages/ | less' and 'ls -lt /var/log/pkgtools/removed_packages | less'

John Lumby · 01-27-2022, 11:06 AM

Quote:

Originally Posted by allend

... easily reviewed with 'ls -lt /var/log/packages/ | less' and 'ls -lt /var/log/pkgtools/removed_packages | less'

I agree those commands are better than nothing, but they are no more than lists of packages - no dates, no indication of what happened to them, no mention of what versions are affected, no indication of the command being run.

Here are some selected snippets from my pacman.log, illustrating all the various kinds of information recorded there (not all from the same run) :

Quote:

[2021-09-15T13:15:47-0400] [ALPM] installed lib32-opus (1.3.1-1)
[ ... ]
[2022-01-13T22:37:08-0500] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[ ... ]
[2022-01-13T22:37:09-0500] [ALPM] upgraded python2-six (1.16.0-1 -> 1.16.0-5)
[ ... ]
[2022-01-13T22:37:10-0500] [ALPM] upgraded qt5-base (5.15.2+kde+r224-1 -> 5.15.2+kde+r289-1)
[ ... ]
[2022-01-13T22:37:16-0500] [ALPM] transaction completed
[2022-01-13T22:37:17-0500] [ALPM] running '20-systemd-sysusers.hook'...
[2022-01-13T22:37:17-0500] [ALPM] running '30-systemd-binfmt.hook'...
[2022-01-13T22:37:17-0500] [ALPM-SCRIPTLET] Skipped: Current root is not booted.
[2022-01-13T22:37:17-0500] [ALPM] running '30-systemd-catalog.hook'...

That kind of detailed information is (ideally) what I would like to see in /var/log/slackpkg.log; personally I find it invaluable, especially when, occasionally, things break, (for the same reasons as when upgrading a slackware -current).

Cheers, John Lumby

fourtysixandtwo · 01-27-2022, 02:26 PM

Quote:

Originally Posted by John Lumby

I agree those commands are better than nothing, but they are no more than lists of packages - no dates, no indication of what happened to them, no mention of what versions are affected, no indication of the command being run.

Here are some selected snippets from my pacman.log, illustrating all the various kinds of information recorded there (not all from the same run) :

That kind of detailed information is (ideally) what I would like to see in /var/log/slackpkg.log; personally I find it invaluable, especially when, occasionally, things break, (for the same reasons as when upgrading a slackware -current).

Cheers, John Lumby

I forgot that log was a feature of slackpkg+ as I always install it. However it's not something I normally look at as there is more detailed information under /var/log/pkgtools/ and /var/lib/pkgtools. Slackpkg is mostly a convenient wrapper around the pkgtools so imho it would be somewhat redundant to do what the pkgtools already provide. (the pkgtools do date stamp everything)

In my experience I've also found most slackpkg specific errors/issues to be immediately obvious as I run and watch the output manually. If I didn't, I would do as the last poster in that link you provided did.

edit: Your first statement in the above post is incorrect as what is logged by pkgtools does specify everything you mentioned.

for example:

Code:

# ls -tral /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-*
-rw-r--r-- 1 root root 1735 Mar 11  2021 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-19-upgraded-2021-04-13,07:57:53
-rw-r--r-- 1 root root 1706 Apr 13  2021 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-21-upgraded-2021-04-21,13:30:13
-rw-r--r-- 1 root root 1687 Apr 21  2021 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-23-upgraded-2021-04-29,13:51:52
-rw-r--r-- 1 root root 1687 Apr 29  2021 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-24-upgraded-2021-07-17,00:46:06
-rw-r--r-- 1 root root 1687 Jul 17  2021 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-25-upgraded-2021-10-12,15:07:44
-rw-r--r-- 1 root root 1687 Oct 12 15:07 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-26-upgraded-2022-01-25,12:27:41
-rw-r--r-- 1 root root 1687 Jan 25 12:27 /var/log/pkgtools/removed_packages/mkinitrd-1.4.11-x86_64-27-upgraded-2022-01-26,23:43:53

# ls -tral /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-*
-rwxr-xr-x 1 root root 109 Mar 11  2021 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-19-upgraded-2021-04-13,07:57:53*
-rwxr-xr-x 1 root root 109 Apr 13  2021 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-21-upgraded-2021-04-21,13:30:13*
-rwxr-xr-x 1 root root 109 Apr 21  2021 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-23-upgraded-2021-04-29,13:51:52*
-rwxr-xr-x 1 root root 109 Apr 29  2021 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-24-upgraded-2021-07-17,00:46:06*
-rwxr-xr-x 1 root root 109 Jul 17  2021 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-25-upgraded-2021-10-12,15:07:44*
-rwxr-xr-x 1 root root 109 Oct 12 15:07 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-26-upgraded-2022-01-25,12:27:41*
-rwxr-xr-x 1 root root 109 Jan 25 12:27 /var/log/pkgtools/removed_scripts/mkinitrd-1.4.11-x86_64-27-upgraded-2022-01-26,23:43:53*

And the current version that is installed:

Code:

# ls -tral /var/lib/pkgtools/packages/mkini*
-rw-r--r-- 1 root root 1687 Jan 26 23:43 /var/lib/pkgtools/packages/mkinitrd-1.4.11-x86_64-28

ls -tral /var/lib/pkgtools/scripts/mki*
-rwxr-xr-x 1 root root 109 Jan 26 23:43 /var/lib/pkgtools/scripts/mkinitrd-1.4.11-x86_64-28*

mralk3 · 01-27-2022, 05:34 PM

Additionally if you use the 'cat' command on one of the files in /var/lib/pkgtools, they double as individual log files for each version of each package. Including description, what scripts are executed (doinst.sh and douninst.sh), and a list of files installed. pkgtools logs what packages are installed, uninstalled, upgraded, reinstalled, and removed. The stuff in /var/log/packages is a symlink to /var/lib/pkgtools.

So you see, all the information is already there, tucked away, neatly and out of the user's way. The information is actually more accessible than other distributions because all you need is the ability to read text. There are no fancy commands with unnecessary flags. No need to duplicate what is already implemented. K.I.S.S.

You are asking for slackpkg to duplicate system log files and it's not really needed.

allend · 01-27-2022, 10:50 PM

Quote:

I agree those commands are better than nothing, but they are no more than lists of packages - no dates, no indication of what happened to them, no mention of what versions are affected, no indication of the command being run.

Processing of the lists is up the user. Perhaps this is more what you want.

Code:

#!/bin/bash

# Script to match installed packages with last removed package

pkgname="$1"

pushd /var/log/removed_packages/ > /dev/null
a=( $(ls -t $pkgname*) )
popd > /dev/null
pushd /var/log/packages/ > /dev/null
c=( $(ls $pkgname*) )
popd > /dev/null

for p in "${c[@]}"; do
  s="${p%-*-*-*}-[0-9]"
  match=1
  for r in "${a[@]}"; do
    [[ $r =~ $s ]] && match=0 && echo "$r --> $p" && break
  done
  [[ $match == 1 ]] && echo "No removed package matches $p"
done

Called with "kernel" as a parameter I get:

Quote:

kernel-firmware-20220111_13dca28-noarch-1-upgraded-2022-01-23,23:02:36 --> kernel-firmware-20220119_0c6a7b3-noarch-1
kernel-generic-5.15.14-x86_64-1-upgraded-2022-01-23,23:53:02 --> kernel-generic-5.15.16-x86_64-1
kernel-headers-5.15.14-x86-1-upgraded-2022-01-23,23:04:21 --> kernel-headers-5.15.16-x86-1
kernel-huge-5.15.14-x86_64-1-upgraded-2022-01-23,23:04:26 --> kernel-huge-5.15.16-x86_64-1
kernel-modules-5.15.14-x86_64-1-upgraded-2022-01-23,23:04:32 --> kernel-modules-5.15.16-x86_64-1
kernel-source-5.15.14-noarch-1-upgraded-2022-01-23,23:05:35 --> kernel-source-5.15.16-noarch-1

John Lumby · 01-28-2022, 10:04 AM

Thanks to all who pointed out that what I am looking for is

Quote:

all the information is already there, tucked away, neatly and out of the user's way.

. And for the bits of shellscript for presenting it. The only aspect of this that I think is still not covered is a sequence of events in chronological order - i.e. a (single) log. And I guess, since there are timestamps, a different script could order all the changes into a single log.

I will try using all these ways of gathering the information and see how I fare. I expect it will work just fine for me. But some newcomer to Slackware used to being able to see a true (single) installer log and not knowing all these tricks might still be lost.

Cheers, John Lumby

Petri Kaukasoina · 01-28-2022, 10:30 AM

Quote:

Originally Posted by John Lumby

The only aspect of this that I think is still not covered is a sequence of events in chronological order - i.e. a (single) log.

Try this command:

Code:

(cd /var/log && ls -gortc {,removed_}packages/*)

fourtysixandtwo · 01-28-2022, 04:47 PM

Quote:

Originally Posted by John Lumby

Thanks to all who pointed out that what I am looking for is . And for the bits of shellscript for presenting it. The only aspect of this that I think is still not covered is a sequence of events in chronological order - i.e. a (single) log. And I guess, since there are timestamps, a different script could order all the changes into a single log.

I will try using all these ways of gathering the information and see how I fare. I expect it will work just fine for me. But some newcomer to Slackware used to being able to see a true (single) installer log and not knowing all these tricks might still be lost.

Cheers, John Lumby

You should try installing the slackpkg+ plugin which in addition to the log file you're looking for also adds the ability to add other repos.
https://slakfinder.org/slackpkg+.html

For example here's a snippet from /var/lib/slackpkg/install.log :

Code:

2022/01/27 19:49:23 upgraded:    kopeninghours-21.12.1-x86_64-2.txz  [slackware64]  (was kopeninghours-21.12.1-x86_64-1)
2022/01/27 19:49:39 upgraded:    krita-5.0.2-x86_64-2.txz  [slackware64]  (was krita-5.0.2-x86_64-1)
2022/01/27 19:49:41 upgraded:    libgpg-error-1.44-x86_64-1.txz  [slackware64]  (was libgpg-error-1.43-x86_64-1)
2022/01/27 19:49:43 upgraded:    lzlib-1.13-x86_64-1.txz  [slackware64]  (was lzlib-1.12-x86_64-3)
2022/01/27 19:49:56 upgraded:    mesa-21.3.5-x86_64-1.txz  [slackware64]  (was mesa-21.3.4-x86_64-1)
2022/01/27 19:50:20 upgraded:    mozilla-firefox-91.5.1esr-x86_64-1.txz  [slackware64]  (was mozilla-firefox-91.5.0esr-x86_64-1)
2022/01/27 19:50:22 upgraded:    netpbm-10.97.03-x86_64-1.txz  [slackware64]  (was netpbm-10.97.02-x86_64-1)
2022/01/27 19:50:29 upgraded:    openexr-2.5.7-x86_64-5.txz  [slackware64]  (was openexr-2.5.7-x86_64-4)
2022/01/27 19:50:31 upgraded:    pamixer-1.5-x86_64-2.txz  [slackware64]  (was pamixer-1.5-x86_64-1)
2022/01/27 19:50:33 upgraded:    pipewire-0.3.44-x86_64-1.txz  [slackware64]  (was pipewire-0.3.43-x86_64-1)
2022/01/27 19:50:35 upgraded:    sysvinit-scripts-15.0-noarch-8.txz  [slackware64]  (was sysvinit-scripts-15.0-noarch-7)
2022/01/28 13:31:38 installed:   boost-compat-1.78-x86_64-1alien.txz  [alienbob]

zeebra · 01-29-2022, 04:09 AM

Well well lads, here we go, and here I open my silly mouth too.

So, what do you guys feel about VLC? For me it is the most overall solid media player, and I use it as a fallback player myself. I've heard it is a real PITA to compile, so it would be a nice favour of BDFL to do it for me (us).

Maybe something for 15.1 testing?

Windu · 01-29-2022, 04:57 AM

Quote:

Originally Posted by zeebra

Well well lads, here we go, and here I open my silly mouth too.

So, what do you guys feel about VLC? For me it is the most overall solid media player, and I use it as a fallback player myself. I've heard it is a real PITA to compile, so it would be a nice favour of BDFL to do it for me (us).

Maybe something for 15.1 testing?

You find something that is a PITA to compile and then you ask our BDFL to do that for you? Is your goal to further increase the time between releases even more?
You can get a VLC package from Alien BOB's repository. With all the libraries it needs already built into the package. Let him do the work rather than Patrick.