slackpkg 2.84.0_beta1 - Testing Wanted

Exaga · 03-01-2020, 08:43 AM

Quote:

Originally Posted by chrisretusn

Odd, I'm using "slackpkg - version 2.84.0_beta6" when we go to beta8?

'slackpkg -onoff=off upgrade-all' works here. Tested with slackpkg+ and without slackpkg+

Perhaps it be a Slackware ARM issue.

Whether the '-onoff' parameter works or not is irrelevant because it's working and perfectly, if you interprited my post correctly.

There is no Slackware ARM issue. It's an omission on the man page. The '-onoff' parameter used to feature on the 'man slackpkg' page but now it doesn't. So, how do users know about this function when it's not documented? This is the point I wish to be realised.

Chuck56 · 03-01-2020, 08:46 AM

Quote:

Originally Posted by Exaga

Whether the '-onoff' parameter works or not is irrelevant because it's working and perfectly, if you interprited my post correctly.

There is no Slackware ARM issue. It's an omission on the man page. The '-onoff' parameter used to feature on the 'man slackpkg' page but now it doesn't. So, how do users know about this function when it's not documented? This is the point I wish to be realised.

Try: man slackpkg.conf

You'll find ONOFF and other config options there.

Exaga · 03-01-2020, 09:08 AM

Quote:

Originally Posted by Chuck56

Try: man slackpkg.conf

You'll find ONOFF and other config options there.

Chucky dear, I'm NOT looking for a solution.

Hahahahahahaha

My post was directed to Robby who asked users to verify the software. It's up to him whether to update the man pages, or not. I'm just reporting what I've found.

Chuck56 · 03-01-2020, 10:10 AM

Quote:

Originally Posted by Exaga

Chucky dear, I'm NOT looking for a solution.

Hahahahahahaha

My post was directed to Robby who asked users to verify the software. It's up to him whether to update the man pages, or not. I'm just reporting what I've found.

I'm not your dear. No need for anybody to update the man pages as I pointed out.

Code:

NAME
       slackpkg - Automated tool for managing Slackware Linux packages
...

SEE ALSO
       slackpkg.conf(5), installpkg(8), upgradepkg(8), explodepkg(8), makepkg(8), pkgtool(8).

Note the reference to slackpkg.conf(5).

Peace out!

magicm · 03-01-2020, 10:29 AM

Steadfast 14.2 user here - watching and waiting for -current to transition to -stable .....

re: -onoff and man pages
slackpkg version 2.82.1 had the same setup:
man slackpkg did _not_ mention onoff
man slackpkg.conf did mention onoff

Don't see a reason to change that (although not terribly against it, either; just seems superfluous)

rworkman · 03-01-2020, 10:45 AM

Quote:

Originally Posted by allend

I note that 2.84.0-beta8 does not include this suggestion.

I don't think I like that change - this PAM addition is enough of a corner case, *and* as others have mentioned, the operation is adequately handled otherwise.

This is admittedly not entirely rational, but /testing is primarily a -current thing, and I'd like to think that -current users are able to adjust to the "once in a blue moon" occasion like this :-)

rworkman · 03-01-2020, 10:47 AM

Quote:

Originally Posted by Exaga

Testing "slackpkg - version 2.84.0_beta8" and it seems to be working great, thus far. Thanks for the new software and the opportunity to test it.

Only thing I've noticed is literary. In the man page, it appears that the 'onoff' function is no longer featured, yet still works like a boss:

Code:

~# slackpkg -onoff=off upgrade-all
~# slackpkg -onoff=off install-new

I use the '-onoff=off' parameter a lot. It's very useful for my 'slackpkg' requirements.

[EDIT] ^^^ This is on Slackware ARM -current btw.

Since this is documented in slackpkg.conf(5) and is likely where you saw it previously, I think we'll leave it alone as "good enough" for now.
After I broke things at beta7, I'm going to be very resistant to further changes :-)

rworkman · 03-01-2020, 10:48 AM

Quote:

Originally Posted by magicm

Steadfast 14.2 user here - watching and waiting for -current to transition to -stable .....

re: -onoff and man pages
slackpkg version 2.82.1 had the same setup:
man slackpkg did _not_ mention onoff
man slackpkg.conf did mention onoff

Don't see a reason to change that (although not terribly against it, either; just seems superfluous)

I'm just glad to see you're still on Slackware - I thought you'd moved on to other pastures :-)

zerouno · 03-01-2020, 02:06 PM

Quote:

After I broke things at beta7, I'm going to be very resistant to further changes :-)

it's a beta, may be happens

Quote:

It's reverted. I don't like the inconsistency with ROOT definitions but I'm not going to break our upstream either :-)
Unless something major comes along and/or some very trivial things occur, consider 2.84.0_beta8 to be what will hopefully become 2.84.0

well, but now persist the blacklist inconsistence mentioned at #34 that need to be fixed

Code:

# ROOT=/var/cache/lxc/slackware/rootfs-current-x86_64/ CONF=/var/cache/lxc/slackware/slackpkg-conf slackpkg search aaa_base

grep: /var/cache/lxc/slackware/rootfs-current-x86_64///var/cache/lxc/slackware/slackpkg-conf/blacklist: No such file or directory
Looking for aaa_base in package list. Please wait... DONE

Code:

core-functions.sh:595:  grep -vE "(^#|^[[:blank:]]*$)" ${ROOT}/${CONF}/blacklist | \
core-functions.sh:647:                                  grep -qx "${i}" ${CONF}/blacklist || LIST="$LIST $i"
core-functions.sh:1235:                 grep -qx "${i}" ${CONF}/blacklist && continue
core-functions.sh:1283: echo $SHOWLIST | tr ' ' "\n" >> ${ROOT}/${CONF}/blacklist
core-functions.sh:1286:If you want to remove those packages, edit ${CONF}/blacklist.\n"

slackpkg:469:                   grep -e "^\([a-z]\)" $CONF/blacklist | $MORECMD

all ${ROOT}/${CONF} so should be ${CONF}

Quote:

IMHO is not essential to enforce $CONF under $ROOT as it can specified manually at the same location (CONF=/chroot/etc/slackpkg) as needed with losing no functionality.

Yes.
Sometime may be useful (at install time in this cases) that $CONF is out of $ROOT.
After the install may be useful to use $ROOT/etc/slackpkg , so in lxc container cache:
ROOT=/var/cache/lxc/slackware/rootfs-current-x86_64/ CONF=/var/cache/lxc/slackware/slackpkg-conf slackpkg
this may be used in other use cases (a chroot installation or a second partition mounted or other, where I want to install a package).
ROOT=/chroot CONF=/chroot/etc/slackpkg slackpkg ....
but I admit that the double $ROOT specify is not intuitive.

a solution may be that
ROOT=/chroot slackpkg ...
may use /chroot/etc/slackpkg as configuration, /chroot/var/lib/slackpkg for workdir, etc, and
ROOT=/chroot CONF=/myconf slackpkg ...
may use /chroot/var/lib/slackpkg for workdir and /myconf as configuration
also in an installed lxc container (that no longer uses /var/cache/lxc/slackware/slackpkg-conf)
ROOT=/var/lib/lxc/test7/rootfs slackpkg ...

/usr/sbin/slackpkg:55

Code:

if [ -z "$CONF" ];then
  CONF=/etc/slackpkg
  if [ ! -z "$ROOT" ];then
    CONF=$ROOT/$CONF
  fi
fi
#CONF=${CONF:-/etc/slackpkg}

ponce · 03-01-2020, 02:13 PM

Quote:

Originally Posted by zerouno

well, but now persist the blacklist inconsistence mentioned at #34 that need to be fixed

Code:

# ROOT=/var/cache/lxc/slackware/rootfs-current-x86_64/ CONF=/var/cache/lxc/slackware/slackpkg-conf slackpkg search aaa_base

grep: /var/cache/lxc/slackware/rootfs-current-x86_64///var/cache/lxc/slackware/slackpkg-conf/blacklist: No such file or directory
Looking for aaa_base in package list. Please wait... DONE

I think this happens because of this commit

https://github.com/rworkman/slackpkg...419c2de6d04954

Quote:

Originally Posted by zerouno

Sometime may be useful (at install time in this cases) that $CONF is out of $ROOT.
After the install may be useful to use $ROOT/etc/slackpkg , so in lxc container cache:
ROOT=/var/cache/lxc/slackware/rootfs-current-x86_64/ CONF=/var/cache/lxc/slackware/slackpkg-conf slackpkg
this may be used in other use cases (a chroot installation or a second partition mounted or other, where I want to install a package).
ROOT=/chroot CONF=/chroot/etc/slackpkg slackpkg ....
but I admit that the double $ROOT specify is not intuitive.
a solution may be that
ROOT=/chroot slackpkg ...
may use /chroot/etc/slackpkg as configuration, /chroot/var/lib/slackpkg for workdir, etc, and
ROOT=/chroot CONF=/myconf slackpkg ...
may use /chroot/var/lib/slackpkg for workdir and /myconf as configuration
also in an installed lxc container (that no longer uses /var/cache/lxc/slackware/slackpkg-conf)
ROOT=/var/lib/lxc/test7/rootfs slackpkg ...

/usr/sbin/slackpkg:55

Code:

if [ -z "$CONF" ];then
  CONF=/etc/slackpkg
  if [ ! -z "$ROOT" ];then
    CONF=$ROOT/$CONF
  fi
fi
#CONF=${CONF:-/etc/slackpkg}

I'm sorry but I don't understand what you mean by that: if you have chroots or containers the normal use case is to execute slackpkg from the inside; if you need to do it from the outside you do it via the chroot command or lxc-attach, for example.

zerouno · 03-01-2020, 02:55 PM

$ROOT may be used not only for lxc.

Consider this use case:
1) slackware installed on usbdisk (or pendrive) configured in dhcp at myhome network
2) something broke the disk so it not boot and you need to reinstall some package to fix
3) since it not boot I mount the usbdisk on my pc where I work
4) this network need a proxy

to reinstall the package I need (at least)

Code:

# mount -o bind /proc /mnt/usb/proc
# mount -o bind /dev /mnt/usb/dev
# chroot /mnt/usb
# echo '192.168.1.1' > /etc/resolv.conf
# export http_proxy=myproxy:8080
# slackpkg reinstall package
# exit
# umount /mnt/usb/dev
# umount /mnt/usb/proc

(well, I may need more things)
or simply

Code:

# ROOT=/mnt/usb slackpkg reinstall package

I think may be other cases where ROOT= may be better or fastest than chroot.

Exaga · 03-01-2020, 05:46 PM

Quote:

Originally Posted by magicm

re: -onoff and man pages
slackpkg version 2.82.1 had the same setup:
man slackpkg did _not_ mention onoff
man slackpkg.conf did mention onoff

Don't see a reason to change that (although not terribly against it, either; just seems superfluous)

Yeah, you're right. It's quite a few years since I read the slackpkg man pages and my memory isn't what it used to be. Apologies.

Quote:

Originally Posted by rworkman

Since this is documented in slackpkg.conf(5) and is likely where you saw it previously, I think we'll leave it alone as "good enough" for now.
After I broke things at beta7, I'm going to be very resistant to further changes :-)

Yeah, you're right. It's quite a few years since I read the slackpkg man pages and my memory isn't what it used to be. Apologies.

chrisretusn · 03-01-2020, 09:21 PM

Quote:

Originally Posted by Exaga

Whether the '-onoff' parameter works or not is irrelevant because it's working and perfectly, if you interprited my post correctly.

There is no Slackware ARM issue. It's an omission on the man page. The '-onoff' parameter used to feature on the 'man slackpkg' page but now it doesn't. So, how do users know about this function when it's not documented? This is the point I wish to be realised.

Yes I did misread your post. Thanks for the clarification.

The users will discover this feature the same way I did, you did, and many others did. Reading the slackpkg.conf man page. I don't recall seeing the '-onoff' parameter featured on the slackpkg man page.

allend · 03-02-2020, 06:31 AM

Quote:

I don't think I like that change - this PAM addition is enough of a corner case, *and* as others have mentioned, the operation is adequately handled otherwise.

This is admittedly not entirely rational, but /testing is primarily a -current thing, and I'd like to think that -current users are able to adjust to the "once in a blue moon" occasion like this :-)

OK - But I will retain my patch locally as "blue moons" do re-occur and I see no reason for the usual 'slackpkg update; slackpkg install-new; slackpkg upgrade-all' dance not to work correctly.

xpetrl · 06-12-2020, 11:51 AM

You can add a Swiss mirror to mirrors-x86*.sample, it replace the outdated mirror.switch.ch which is listed in mirrors of the slackpkg stable.
mirror.init7.net is listed as alternate mirror on mirror.switch.ch website, https://mirror.switch.ch/

Quote:

diff a/mirrors-x86.sample b/mirrors-x86.sample
163a164,165
> # SWITZERLAND (CH)
> # https://mirror.init7.net/slackware/slackware-14.2/
327a330,331
> # SWITZERLAND (CH)
> # https://mirror.init7.net/slackware/slackware-current/
diff a/mirrors-x86_64.sample b/mirrors-x86_64.sample
161a162,163
> # SWITZERLAND (CH)
> # https://mirror.init7.net/slackware/slackware64-14.2/
323a326,327
> # SWITZERLAND (CH)
> # https://mirror.init7.net/slackware/slackware64-current/