Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#7045 - gnome-icon-theme has its own gnome group

Attached to Project: Pacman
Opened by Spencer French (ingvildr) - Tuesday, 01 May 2007, 16:53 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 11 December 2007, 17:54 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When i try to run a pacman -S gnome with pacman 3.0.3 i get this output

[root@amnesia spencer]# pacman -S gnome
:: group gnome:
gnome-icon-theme
:: Install whole content? [Y/n] n
:: Install gnome-icon-theme from group gnome? [Y/n] n
:: group gnome:
control-center epiphany gnome-applets gnome-backgrounds gnome-desktop
gnome-media gnome-mime-data gnome-mount gnome-panel gnome-session
gnome-themes gnome2-user-docs metacity nautilus yelp
:: Install whole content? [Y/n]

As shown it seems gnome-icon-theme is in a duplicate gnome group, or maybe pacman is behaving strange i dont know.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 11 December 2007, 17:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with the core/extra splitup
Comment by Jan de Groot (JGC) - Tuesday, 01 May 2007, 17:00 GMT
The gnome group is split into two repositories: current and extra. Each repo has its own gnome group according to pacman logic. I can't move gnome-icon-theme to extra, neither can I move the rest of gnome to current, so packaging-wise this is not fixable without changing pacman.
Comment by Aaron Griffin (phrakture) - Tuesday, 01 May 2007, 23:35 GMT
Yeah, pacman splits the groups over repos. I think this may have been by design a while back. Here are the options available:

1) allow a group to span multiple repos
2) remove gnome-icon-theme from the gnome group
3) combine current and extra into one repo (he he, see the arch-repos stuff and Paul's repoman)

Just out of curiosity, JGC, why can't gnome-icon-theme move to current?
Comment by Jan de Groot (JGC) - Wednesday, 02 May 2007, 05:42 GMT
gnome-icon-theme is in current because the icons are required by libgnomeprintui, which is a dependency for abiword. I suspect abiword to be working with GtkPrint instead of gnomeprint in the near future, but we haven't seen any stable releases for a long while. When all this happens, I expect to move gnomeprint to extra, taking the rest of it with it, but as long as current packages use gnomeprint, I can't.
Comment by Allan McRae (Allan) - Sunday, 09 December 2007, 11:31 GMT
This is fixed with the repo shuffle. So this can be closed unless #1 of phrakture's suggestions is going to be implemented.

Loading...