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. |
In x86_64, I was getting the calligra-|10n also, but not the kdei. This time, I got neither.
|
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.
|
Quote:
|
Thanks. I was hoping the heat wasn't making me loopy!
|
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 |
I came up with these lines in /etc/slackpkg/blacklist
Code:
calligra-l10n-[^e][^n]_[^G][^B] If you want to block all of them then just use Code:
calligra-l10n |
You can also block all of kdei with
kdei |
Quote:
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. |
Quote:
Eric |
Quote:
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. |
Quote:
you could also use: Code:
./slackware/kdei 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. If I needed a particular language file I would have done this differently in my blacklist Code:
calligra-l10n-zh_TW 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. |
Quote:
Well, my opinion. Guess I could patch it if it bothers my enough.... |
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" |
Quote:
Code:
slackpkg install slackware |
All times are GMT -5. The time now is 03:59 AM. |