[SOLVED] How to remove new installed packages by groups ?

gildbg · 12-15-2020, 05:34 AM

Hello ppl,

I have a question: How to remove my KDE. Well, let me explain first. I have a server without X and KDE on current. When I do slackpkg install-new the process install all new KDE5 packages. Then I do slackpkg upgrade-all ... and few other packages was updated. Now I want to remove the X and KDE group of packages. Well, on install process asking which group of packages to install: like A, X, KDE, KDEI.

Thanks for advice.

slac · 12-15-2020, 06:24 AM

I would say that it is very important to mention which Slackware version you are using. I will assume that you are using Slackware 14.2 since you said that you want to remove the set of packages of kde and kdei, because in Slackware Current (15) kdei no longer exists, only kde.

You can use slackpkg to remove any set of packages, you only need to write the letter(s) that identify such set of packages, in your case it will be:

Code:

slackpkg remove kde
slackpkg remove kdei

Now, in order not install kde/kdei again when using slackpkg (install-new/upgrade-all), you must blacklist those set of packages, you can do so by editing /etc/slackpkg/blacklist, just add these lines there and save:

Code:

kde
kdei

Remember to blacklist only after you have uninstalled those packages since once you blacklist them they will no longer appear in any slackpkg command (until you remove them from the blacklist, of course).

gildbg · 12-16-2020, 09:41 AM

Thank you for answer.

gildbg · 02-14-2021, 02:00 AM

Hello again,

this was work in old slackpkg but on slackpkg-15.0-noarch-2 I have trouble. I do:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg remove kde
slackpkg update (forced to yes)
slackpkg install-new

and new KDE5 packages are again ready to be installed. How to resolve this issue without to added one by one in blacklist.

sasongko · 02-14-2021, 03:45 AM

Quote:

Originally Posted by gildbg

Hello again,

this was work in old slackpkg but on slackpkg-15.0-noarch-2 I have trouble. I do:

what's the trouble?
since slackpkg-15.0-noarch-1, to blacklist entire package sets a trailing slash is needed, i.e. kde/

gildbg · 02-14-2021, 04:08 AM

The trouble is, when you uninstall the package or group they should not be offered for installation as new package again.

deNiro · 02-14-2021, 04:13 AM

Quote:

Originally Posted by gildbg

Hello again,

this was work in old slackpkg but on slackpkg-15.0-noarch-2 I have trouble. I do:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg remove kde
slackpkg update (forced to yes)
slackpkg install-new

and new KDE5 packages are again ready to be installed. How to resolve this issue without to added one by one in blacklist.

Like Sasongko said, with the new slackpkg, blacklisting has changed.

The old way was that you had to use the command "slackpkg blacklist kde", which created a complete list of that group in blacklist.conf. And, on current, you also had to repeat that before a "slackpkg install-new", to avoid installing new packages from that group. But this is no longer needed.

In your blacklist.conf you now just put "kde/", and that package group will always be ignored, even when install new packages.

gildbg · 02-14-2021, 04:27 AM

Yep,

I read the documentation, but in version 14 when I uninstall a package, this package was never offer to be installed again as new and I did not put the package in blacklist.

Anyway, thanks.

Alien Bob · 02-14-2021, 04:32 AM

Quote:

Originally Posted by gildbg

The trouble is, when you uninstall the package or group they should not be offered for installation as new package again.

You'll have to re-read "man slackpkg" then

chrisretusn · 02-14-2021, 08:08 AM

In addition to what Alien Bob said, you should read the comments in the new blacklist file.

gildbg · 02-15-2021, 03:51 AM

pkg_info -s slackpkg
slackpkg-2.83.0-noarch-5

removepkg epic5
slackpkg update
slackpkg install-new
cat /etc/slackpkg/blacklist | grep epic

Epic 5 is missing and is not showed anymore, but I cant say the same for kde5 so ?

Well, I think this is a problem of slackpkg did not track probably the package status that is uninstalled because package epic5 is on default installation tree and slackpkg did not track his changes i.e. install new. When I uninstall the package I and probably most ppl expect they to stay uninstalled forever, not to be suggest on next slackpkg install-new as for example epic5.

I read the man page, did you read it because this effect is not described there ?

Petri Kaukasoina · 02-15-2021, 05:13 AM

"slackpkg install-new" installs new packages "Added" according to ChangeLog.txt. epic5 is old: it was added already Mon May 17 23:19:08 UTC 2010, so it was not "Added" in the current ChangeLog.txt. The current Changelog.txt begins at Thu Jun 30 20:26:57 UTC 2016, when Slackware 14.2 was released, so everything added after the original 14.2 release is "new".

So, "slackpkg install-new" does not mean "install packages that are new to me personally."

chrisretusn · 02-15-2021, 05:25 AM

Quote:

Originally Posted by gildbg

pkg_info -s slackpkg
slackpkg-2.83.0-noarch-5

Last I checked pkg_info was a freebsd program.

How about running 'slackpkg help | grep "- version"' and list the result so we know what version of slackpkg you are running.

Quote:

removepkg epic5
slackpkg update
slackpkg install-new
cat /etc/slackpkg/blacklist | grep epic

Epic 5 is missing and is not showed anymore, but I cant say the same for kde5 so ?

Not sure what you are getting at here.
What is the purpose of removing epic5?

What were you expecting from 'slackpkg install-new'?

I fail to understand the relevance of 'cat /etc/slackpkg/blacklist | grep epic'. Were you expecting it do appear in blacklist???

Quote:

Well, I think this is a problem of slackpkg did not track probably the package status that is uninstalled because package epic5 is on default installation tree and slackpkg did not track his changes i.e. install new. When I uninstall the package I and probably most ppl expect they to stay uninstalled forever, not to be suggest on next slackpkg install-new as for example epic5.
I read the man page, did you read it because this effect is not described there ?

You say you read the man page. Clearly you missed this then.

Code:

       install-new
            This  action  installs  any new packages that are added to the official Slackware package set.  Run
            this if you are upgrading your system to another Slackware version or if you are using -current.
            If you want to install all uninstalled Slackware packages onto your system, use the following  com‐
            mand instead of the install-new action:

                 # slackpkg install slackware.

The package epic5 is not an "Added." package to the -current or 14.2 ChangeLog.txt. 'slackpkg install-new' will not install that package. The only way to get epic5 installed again is to run 'slackpkg install epic5' or use installpkg on the package tarball.

dr.s · 02-15-2021, 08:23 AM

Quote:

Originally Posted by chrisretusn

...
Not sure what you are getting at here.
What is the purpose of removing epic5?

What were you expecting from 'slackpkg install-new'?

I fail to understand the relevance of 'cat /etc/slackpkg/blacklist | grep epic'. Were you expecting it do appear in blacklist???

The package epic5 is not an "Added." package to the -current or 14.2 ChangeLog.txt. 'slackpkg install-new' will not install that package. The only way to get epic5 installed again is to run 'slackpkg install epic5' or use installpkg on the package tarball.

Looks like OP tried removing an "old" package (<= 14.2) vs. one that's been added to -current (14.2+)

-after removing an old package, slackpkg install-new will not re-install it
-with new packages, ie. "added" to -current, slackpkg install-new will re-install them, unless they're blacklisted.

chrisretusn · 02-15-2021, 09:23 AM

Quote:

Originally Posted by dr.s

Looks like OP tried removing an "old" package (<= 14.2) vs. one that's been added to -current (14.2+)

-after removing an old package, slackpkg install-new will not re-install it
-with new packages, ie. "added" to -current, slackpkg install-new will re-install them, unless they're blacklisted.

As I stated above epic5 is not a new package, goes back to at least 14.1

Yes he was probably thinking install-new would add it.