Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16517 - [many kde packages] not belonging to any group

Attached to Project: Arch Linux
Opened by Corrado Primier (bardo) - Thursday, 08 October 2009, 09:20 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 22 October 2009, 15:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

There are many kde packages that get installed as dependencies of the three main groups (kde, kde-extragear, kde-l10n) but don't belong to any. This brings problems when using, for example IgnoreGroup in pacman.conf (or the corresponding --ignoregroup switch), leading to a partially updated and potentially broken kde system.

List follows, all of these packages belong to no group except for kdebindings-python, which belongs to the kdebindings 'subgroup':

kdebase-lib
kdebase-runtime
kdebindings-python
kdebindings-smoke
kdeedu-data
kdeedu-libkdeedu
kdegames-libkdegames
kdegames-libkmahjongg
kdegraphics-libs
kdelibs
kdelibs-experimental
kdepim-libkdepim
kdepim-runtime
kdepimlibs
kdeplasma-addons-libs
oxygen-icons
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Thursday, 22 October 2009, 15:39 GMT
Reason for closing:  Won't implement
Comment by Roman Kyrylych (Romashka) - Thursday, 08 October 2009, 09:25 GMT
Having dependencies like these in groups is problematic too, because they will have "explicitly installed" status
and thus if a package will not be required in the future - it will not be removed during -Syu nor it will show up with -Qtd.
Comment by Jan de Groot (JGC) - Thursday, 08 October 2009, 10:58 GMT
I don't see any functional reason for putting these packages into groups, which has the side effects explained by Roman.
Dependencies should be applied strict enough to force updates for these packages, but IMHO, not upgrading the total system installation, but only a part of it is responsibility for the user. We only support complete pacman -Syu upgrades.
Comment by Pierre Schmitz (Pierre) - Thursday, 08 October 2009, 11:06 GMT
It does not make sense to put libs in a group. Packages in a group should be a selection of applications that are actually usable to the user.

PS: Using IgnorePkg and IgnoreGroup is not really supported and the user has to deal with all its consequences.

Loading...