LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   slackware current and slackpkg selects kdei packages series in error (http://www.linuxquestions.org/questions/slackware-14/slackware-current-and-slackpkg-selects-kdei-packages-series-in-error-4175422509/)

kingbeowulf 08-16-2012 05:56 PM

slackware current and slackpkg selects kdei packages series in error
 
This has been an issue with current beta, RC1 and now RC2 on both x86 archs. when using slackpkg to update, even though series kdei was NOT elected during the initial installation, executing

slackpkg install-new
slackpkg upgrade-all

all the calligra-l10n-* languages are selected. Nothing else from series kdei and nothing from emacs, which I also did not install.

I can blacklist this; however, isn't this supposed to be automagical? Why just calligra and not any other packages/series I skipped? This also occurs in the qemu VMs when I do a full install omitting just /kdei

Wrong tagfiles?

Thanks.

mlangdn 08-16-2012 06:11 PM

In x86_64, I was getting the calligra-|10n also, but not the kdei. This time, I got neither.

kingbeowulf 08-16-2012 08:12 PM

Nope, did it again: this time slackware64-14-RC2 updated from beta pre-RC1. No matter what (short of blacklisting), slackpkg thinks the kdei/calligra-l10n-* files need to be added when given "slackpkg install-new" - Note that there are a bunch of otehr files kdei/ that slackpkg properly ignores.

hitest 08-16-2012 08:19 PM

Quote:

Originally Posted by kingbeowulf (Post 4756190)
Nope, did it again: this time slackware64-14-RC2 updated from beta pre-RC1. No matter what (short of blacklisting), slackpkg thinks the kdei/calligra-l10n-* files need to be added when given "slackpkg install-new"

Yes. I see the same behaviour when I issue slackpkg install-new.

kingbeowulf 08-16-2012 08:35 PM

Thanks. I was hoping the heat wasn't making me loopy!

Alien Bob 08-17-2012 03:34 AM

You may not realize how slackpkg determines if a package is new to Slackware.

The "slackpkg install-new" command acts on the word "Added" in the Slackware ChangeLog.txt. So, if you upgrade to a certain Slackware release, slackpkg will scan that release's ChangeLog.txt and add all packages to the pick-list for which it finds "Added."
That is why you get things like gptfdisk, but also all the calligra-l10n packages when you run "slackpkg install-new" for slackware-current.

Eric

wildwizard 08-17-2012 04:14 AM

I came up with these lines in /etc/slackpkg/blacklist

Code:

calligra-l10n-[^e][^n]_[^G][^B]
calligra-l10n-[a-z]*

This gives me the en_GB but none of the others.

If you want to block all of them then just use

Code:

calligra-l10n

chrisretusn 08-17-2012 06:59 AM

You can also block all of kdei with

kdei

guanx 08-17-2012 07:18 AM

Quote:

Originally Posted by chrisretusn (Post 4756608)
You can also block all of kdei with

kdei

But this is not the solution. Years ago I've complained about the same thing here (on LQ) and it was announced to be fixed a while later.

Note that "announced". Actually nothing happened to the maketag files under kdei.
It should be quite easy to change the "on"s to "off"s.

Alien Bob 08-17-2012 08:36 AM

Quote:

Originally Posted by guanx (Post 4756620)
But this is not the solution. Years ago I've complained about the same thing here (on LQ) and it was announced to be fixed a while later.

Note that "announced". Actually nothing happened to the maketag files under kdei.
It should be quite easy to change the "on"s to "off"s.

Slackpkg does not look at tagfiles at all. And inide the Slackware installer, you can simply de-select the KDEI series.

Eric

guanx 08-17-2012 07:08 PM

Quote:

Originally Posted by Alien Bob (Post 4756693)
Slackpkg does not look at tagfiles at all. And inide the Slackware installer, you can simply de-select the KDEI series.

Eric

Hi Eric, Thanks for the reply.

Do you have an idea why these few kdei packages should default to "on" while all others default to "off"? I Always remove them during menuconfig and got no system break down in any way.

This is a cross-major-release bug.

chrisretusn 08-17-2012 10:38 PM

Quote:

Originally Posted by guanx (Post 4756620)
But this is not the solution.

Why isn't it? Adding kdei to blacklist prevents all of the kdei series packages from being acted on. This takes care of the caligra-l10n packages.

you could also use:
Code:

./slackware/kdei
./slackware64/kdei
-or-
./slackware[0-9]+/kdei

It's already been explained (here) why the Caligra language packages (calligra-l10n) are included when running "slackpkg install-new"

An except from the Sat Apr 14 22:06:26 UTC 2012 entry in ChangeLog.txt in -current.
Code:

kdei/calligra-l10n-ca-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-ca@valencia-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-cs-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-da-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-de-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-el-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-en_GB-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-es-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-et-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-fi-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-fr-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-hu-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-it-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-kk-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-nb-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-nds-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-nl-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-pl-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-pt-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-pt_BR-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-ru-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-sk-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-sv-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-uk-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-zh_CN-2.4.0-noarch-1.txz:  Added.
kdei/calligra-l10n-zh_TW-2.4.0-noarch-1.txz:  Added.

I see slackpkg as a more or less default "on" with Slackware (official) packages when it comes to updating. If I want to turn something off, that is what blacklist is for. When I saw that calligra was added, I turned to blacklist. Originally I used "calligra-l10n", then decided since I don't use kdei at all, I when with "./slackwar64[0-9]+/kdei"

If I needed a particular language file I would have done this differently in my blacklist
Code:

calligra-l10n-zh_TW
calligra-l10n-zh_CN
calligra-l10n-uk
calligra-l10n-sv
calligra-l10n-sk
#calligra-l10n-ru
calligra-l10n-pt_BR
calligra-l10n-pt
calligra-l10n-pl
calligra-l10n-nl
calligra-l10n-nds
calligra-l10n-nb
calligra-l10n-kk
calligra-l10n-it
calligra-l10n-hu
calligra-l10n-fr
calligra-l10n-fi
calligra-l10n-et
calligra-l10n-es
calligra-l10n-en_GB
calligra-l10n-el
calligra-l10n-de
calligra-l10n-da
calligra-l10n-cs
calligra-l10n-ca@valencia
calligra-l10n-ca

When Slackware 14.0 is released, I would no longer need those entries.

Using slakcpkg search is a good way to test blacklist entries. Also looking at /var/lib/slackpkg/pkglist can give you ideas on what you can use in search and in blacklist.

kingbeowulf 08-18-2012 01:28 AM

Quote:

Originally Posted by Alien Bob (Post 4756465)
You may not realize how slackpkg determines if a package is new to Slackware.

The "slackpkg install-new" command acts on the word "Added" in the Slackware ChangeLog.txt. So, if you upgrade to a certain Slackware release, slackpkg will scan that release's ChangeLog.txt and add all packages to the pick-list for which it finds "Added."
That is why you get things like gptfdisk, but also all the calligra-l10n packages when you run "slackpkg install-new" for slackware-current.

Eric

Hmmm...that makes sense from one point, but not in another, as just searching for "added" is a bit of a short cut. Why, once 'install-new' is run and new packages added, why do just 'calligra-l10n' packages come back again after each update? Heck, the where added April 14, 2012. I kipped other packages and series while I'm playing around in a VM. Should not slackpkg skip a package series if it was not installed originally? Should not slackpkg skip scanning for the added packages if the user unchecks the box?

Well, my opinion. Guess I could patch it if it bothers my enough....

wildwizard 08-18-2012 02:48 AM

kingbeowolf

I had thought about what you just posted and for most people it would work but not all.

If for instance you want to upgrade only part of the system first and then the rest later on the second run you might end up missing something.

What it probably needs is a bit more intelligence in it to detect which packages out of the entire system are missing and provide them via another option like "slackpkg install-missing"

TobiSGD 08-18-2012 04:55 AM

Quote:

Originally Posted by wildwizard (Post 4757351)
What it probably needs is a bit more intelligence in it to detect which packages out of the entire system are missing and provide them via another option like "slackpkg install-missing"

Isn't that the same as
Code:

slackpkg install slackware
?


All times are GMT -5. The time now is 06:20 PM.