slackpkg 2.84.0_beta1

rworkman · 12-02-2018, 09:46 PM

Back when I decided to "maintain" slackpkg, I tried to make it clear that the goal was a *true* "maintenance mode," i.e. new features are generally not desirable. However, enhancement and fixing of existing functionality *is* desirable. With that said, I'd like to get some testing of a 2.84.0_beta1 release. From the ChangeLog:

Code:

Sun Dec  2 06:46:33 UTC 2018
---------------
        - 2.84.0_beta1
        - Allow blacklisting of individual packages without collateral
          damage (e.g. glibc ---> glibc-*). This changes the prior behavior
          of the blacklist function; previously, adding "glibc" to the
          blacklist would cause glibc, glibc-profile, glibc-zoneinfo, et al
          to be ignored by slackpkg. The new behavior is that *only* the
          glibc package is ignored. If you want to blacklist all packages
          whose names begin with glibc, you would need to add "glibc.*" to
          the blacklist now.  Also note that any special characters, e.g. "+",
          will need to be escaped in the blacklist file. (David Woodfall)
        - Add support for listing .new files without PAGER (David Woodfall)
        - Remove switch.ch mirrors
        - Add config option to allow *not* saving .orig configs (Darren Austin)
        - Mention possible stale mirror if CHECKSUMS.md5 gpg verify fails
        - Clarify that a press of "Enter" is needed to confirm kernel change
          (Mario Preksavec)
        - doinst.sh Don't remove ChangeLog.txt upon upgrade/reinstall.
          (Patrick Volkerding)
        - mirrors-x86*.sample: Remove bjtu.edu.cn mirror
        - Fix for /var/log/packages/ possibly being a symlink to elsewhere
        - Use CHECKSUMS.md5.asc to determine ChangeLog newness
          (Patrick Volkerding)

I'm pretty sure this is going to change the blacklist behavior slightly by fixing what was (in my opinion) a bug, and I know that there are probably people who depended on that bug being present [1], but I'm hoping to see how prevalent that is and how much of a dealbreaker it actually is from users.

If/when new betas are released, they'll be on the slackpkg homepage [2] and in the beta download area [3]. Here's a direct link to the 2.84.0_beta1 release: https://slackpkg.org/beta/slackpkg-2...arch-1_rlw.txz

[1] https://xkcd.com/1172/
[2] https://slackpkg.org/
[3] https://slackpkg.org/beta/

rworkman · 12-02-2018, 09:49 PM

Be sure to move/merge config files in /etc/slackpkg/ *and* you'll want to (temporarily) add slackpkg to the blacklist so that you don't immediately go back to the stock version the first time you use it :-)

Paulo2 · 12-03-2018, 04:07 PM

I installed this new version in a Slackware-current pure alsa install.
It seems that it is running ok. There is a new update in -current today Dec 3,
but the mirror I use didn't sync yet, a few more hours and I can run the new
slackpkg with updates to process.

One thing that I noted, slackpkg+ is installed as well but it seems that
the new slackpkg version doesn't work well with slackpkg+.

I blacklisted slackpkg and sbopkg and, with slackpkg+ installed, they
still appear in the 'upgrade-all' (slackpkg) and 'clean-system' (sbopkg).

Then I uninstalled slackpkg+ and this time blacklist is honored (and the
pulseaudio packages appear as upgrades to the pure alsa ones).

dive · 12-04-2018, 02:14 PM

It looks like slackpkg+ does it's own parsing of the
blacklist file.

With slackpkg+ installed, blacklisting [0-9]+_SBo still
lists all the SBo packages for removal with clean-system.
As soon as I removed slackpkg+ they weren't listed.

rworkman · 12-04-2018, 07:28 PM

I haven't looked (and probably won't look) at slackpkg+, but it seems like the best solution would be for it to use the stock slackpkg functions except when it can't. Either way, I'm not going to intentionally break slackpkg+ or any other third-party addon for slackpkg, but I'm also not going change an implementation of something in slackpkg for the sake of slackpkg+.

rworkman · 12-04-2018, 09:32 PM

Okay, I looked. At a glance, it appears that they use their own blacklist function to work around one of the very things this beta fixes :-)

zerouno · 12-11-2018, 07:08 AM

Hello.
Just now I saw this post.

I have not saw the slackpkg 2.84 code, but from the changelog I think I need a lot of change to slackpkg+

Have you an estimated time to release a slackpkg 2.84 stable release?

ponce · 12-11-2018, 07:14 AM

if can be useful to anyone

https://github.com/rworkman/slackpkg

rworkman · 12-11-2018, 04:49 PM

Quote:

Originally Posted by zerouno

Hello.
Just now I saw this post.

I have not saw the slackpkg 2.84 code, but from the changelog I think I need a lot of change to slackpkg+

Have you an estimated time to release a slackpkg 2.84 stable release?

I don't really have an ETA on release. I'd like for this version to be in Slackware 15.0 at least, but aside from that, I'm not really in a rush.

rworkman · 12-31-2018, 01:50 AM

Just released 2.84_beta3 with some fixes for blacklisting entire package sets; thanks again to David Woodfall (dive)!

Get it here: https://slackpkg.org/beta/slackpkg-2...arch-1_rlw.txz

Be sure to take note of the new sample blacklist file, and if you're updating from 2.83.x, the new slackpkg.conf as well.

Drakeo · 12-31-2018, 08:48 AM

Quote:

Originally Posted by rworkman

Just released 2.84_beta3 with some fixes for blacklisting entire package sets; thanks again to David Woodfall (dive)!

Get it here: https://slackpkg.org/beta/slackpkg-2...arch-1_rlw.txz

Be sure to take note of the new sample blacklist file, and if you're updating from 2.83.x, the new slackpkg.conf as well.

can you point me to your change log or do you keep it on the github or bitbucket

Drakeo · 12-31-2018, 08:50 AM

found changelog
made this tool help me see the direction and show your hard work thank you.
https://github.com/Drakeo/slackpkg-beta
shows your history from 2007 on.

zerouno · 01-03-2019, 05:42 AM

slackpkg+-1.7.0-noarch-10mt.txz and slackpkg+-1.7.0d1-noarch-6mt.txz now allow to use new blacklist system, but only for install/upgrade/remove options (not search) and not for greylist.

Paulo2 · 01-03-2019, 09:20 AM

Quote:

Originally Posted by zerouno

slackpkg+-1.7.0-noarch-10mt.txz and slackpkg+-1.7.0d1-noarch-6mt.txz now allow to use new blacklist system, but only for install/upgrade/remove options (not search) and not for greylist.

Which one can be tested with the slackpkg beta?
I have installed slackpkg+-1.7.0-noarch-9mt then should I download the 10mt?
I'm testing this on a separated partition so there is no danger on breaking things.

EDIT- The package slackpkg+-1.7.0-noarch-10mt.txz is the stable release,
and slackpkg+-1.7.0d1-noarch-6mt.txz is from development branch.

I installed slackpkg+-1.7.0-noarch-10mt.txz and is working ok
with slackpkg-2.84.0_beta3-noarch-1_rlw.txz.

blacklist now works, adding 'slackpkg' to it and running 'slackpkg upgrade-all'
doesn't show the Slackware package to upgrade.

greylist now works too, adding 'sbopkg' to it and running 'slackpkg clean-system'
shows the package unselected. (sbopkg isn't in the blacklist)

FTIO · 01-03-2019, 08:36 PM

This is the program that comes with Slackware that does things like...

Code:

pkgtool

or

Code:

installpkg

etc, correct?