[SOLVED] System asking to remove pkgs that I installed

Ztcoracat · 06-30-2014, 04:01 PM

Hi:

I installed flashplayer-plugin, Libre Office, and Openjdk because I needed them.

After updating the system I ran 'slackpkg clean-system'
Upon doing so Slackware offered to remove them-

Code:

flashplayer-plugin-11.2202.359-x86_64-1alien
libreoffice-4.2.4-x86_64-1alien
openjdk-7u55_b14-x86_64-1alien

If I remove the packages then I will only have to install them again-
Right?

If so... why is Slackware offering to remove what I need?
-:--(trying to understand how this distribution thinks)--:-

Is this because the package extension is not .txz?

Also I noticed when I wanted to 'upgrade all' pkg's the old mosilla-firefox-24 is still in the list. FF 30 is the current version.

Using the "removepkg" tool should solve that issue--

Didier Spaier · 06-30-2014, 04:15 PM

This is just because these packages are not shipped with Slackware and slackpkg only deal with official Slackware packages.

To avoid that inconvenience, blacklist them.

To know more:

Code:

man slackpkg
man slackpkg.conf

Quote:

Also I noticed when I wanted to 'upgrade all' pkg's the old mosilla-firefox-24 is still in the list. FF 30 is the current version.

'upgrade all' only upgrade if:

You did a "slackpkg update" before and
There was an update showing in the ChangeLog for your Slackware version,

But the last update of Firefox for Slackware 14.1 is

Code:

Sat Jun 7 02:47:42 UTC 2014
patches/packages/mozilla-firefox-24.6.0esr-i486-1_slack14.1.txz: Upgraded.

PS Slackware's policy is to upgrade software shipped in stable releases mostly as security fixes, and sometimes to correct major failures, almost never to get other kinds of enhancements as shows for instance the Stable ChangeLog for x86 (32-bit).

WhiteWolf1776 · 06-30-2014, 04:15 PM

As these are not part of the core Slackware, slackpkg does not know that you want them there and are managing them with a different system.

To prevent this, you need to blacklist the packages using the /etc/slackpkg/blacklist file.

Once added, the clean system command will no longer try to remove them for you.

Ztcoracat · 06-30-2014, 04:57 PM

I found how to blacklist in the 'man slackpkg' manpage-

Code:

blacklist
            With this action, you can "blacklist" certain packages.
            Blacklisted  packages  will not be installed, upgraded, or removed
            by slackpkg.  If you want to remove some package  from  the  black
            list, please edit /etc/slackpkg/blacklist.

I haven't blacklisted any pkg's before. Before I edit the /etc/slackpkg/blacklist file I'll look in our Form here to see where members have shown how they have blacklisted pkg's and or maybe drivers too.

If I had to guess I'm thinking I could just simply type something like this?
# blacklist mozilla-firefox-24.6.0esr-x86_64-1_ (or whatever the pkg that is the inconvenience)

Didier Spaier · 06-30-2014, 05:02 PM

Just have a look at /etc/slackpkg/blacklist, it's well commented.

Ztcoracat · 06-30-2014, 05:10 PM

Quote:

Originally Posted by Didier Spaier

Just have a look at /etc/slackpkg/blacklist, it's well commented.

Looking at it now.

Code:

bash-4.2$ ls /etc/slackpkg/blacklist
/etc/slackpkg/blacklist
bash-4.2$ cat /etc/slackpkg/blacklist
# This is a blacklist file. Any packages listed here won't be
# upgraded, removed, or installed by slackpkg.
#
# The correct syntax is:
#
# To blacklist the package xorg-server-1.6.3-x86_64-1 the line will be:
# xorg-server
#
# DON'T put any space(s) before or after the package name or regexp.
# If you do this, the blacklist will NOT work.

#
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below 
#
#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source

#
# aaa_elflibs can't be updated.
#
aaa_elflibs

# You can blacklist using regular expressions.
#
# Don't use *full* regex here, because all of the following 
# will be checked for the regex: series, name, version, arch, 
# build and fullname.
#
# This one will blacklist all SBo packages:
#[0-9]+_SBo
bash-4.2$

If I remember correctly when bash see's the pound (#) sign it's ignored.
I should be abe to edit (add the word blacklist and the pkg name) at the end of this file; right?

TobiSGD · 06-30-2014, 05:13 PM

The clean-system command is only ever needed for version updates (for example from Slackware 14.0 to 14.1), in a stable release packages will never be removed from the tree. So instead of blacklisting you could just stop to use clean-system (for that matter, install-new is also not needed).

BCarey · 06-30-2014, 05:14 PM

You don't have to add the word blacklist, and you should not include any version information. So the line would be simply, eg.

Code:

mozilla-firefox

Brian

TobiSGD · 06-30-2014, 05:16 PM

Quote:

Originally Posted by Ztcoracat

If I remember correctly when bash see's the pound (#) sign it's ignored.

Correct.

Quote:

I should be abe to edit (add the word blacklist and the pkg name) at the end of this file; right?

You don't add the word blacklist, just the package name, preferably without version numbers, so for Firefox (for example if you use ruario's latest-firefox script to use non-ESR Firefox versions) you put just

Code:

mozilla-firefox

in that file.

Ztcoracat · 06-30-2014, 05:17 PM

Quote:

Originally Posted by TobiSGD

The clean-system command is only ever needed for version updates (for example from Slackware 14.0 to 14.1), in a stable release packages will never be removed from the tree. So instead of blacklisting you could just stop to use clean-system (for that matter, install-new is also not needed).

Thanks; TobiSGD-

It is good however to learn how to blacklist. Might come in handy in the future.

Ztcoracat · 06-30-2014, 05:22 PM

Quote:

You don't add the word blacklist, just the package name, preferably without version numbers, so for Firefox (for example if you use ruario's latest-firefox script to use non-ESR Firefox versions) you put just

Got it-:-

I see now where that file says "DON"T put any spaces before the pkg name or regexp.
If you do the blacklist will not work."

Ztcoracat · 06-30-2014, 05:33 PM

@Didier Spaier; WhiteWolf 1776 & BCarey thanks for your support:-

Ztcoracat · 06-30-2014, 05:40 PM

Just edited the /etc/slackpkg/blacklist file with "mozilla-firefox" successfully.

All is good now--

brianL · 07-01-2014, 03:55 AM

In /etc/slackpkg/blacklist:
To blacklist Alien Bob's packages, put:

Code:

[0-9]+alien

And if you're using ruario's latest-firefox script, put:

Code:

[0-9]+ro

Ztcoracat · 07-01-2014, 02:39 PM

Quote:

Originally Posted by brianL

In /etc/slackpkg/blacklist:
To blacklist Alien Bob's packages, put:

Code:

[0-9]+alien

And if you're using ruario's latest-firefox script, put:

Code:

[0-9]+ro

Thanks!

I am using Ruario's latest script:-

I only have to do that once in that file for ruario's script right?