FS#5073 - totem-plugin upgrade forces removal of totem-xine

Attached to Project: Pacman
Opened by pete (drg006) - Wednesday, 19 July 2006, 13:17 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 28 September 2007, 03:55 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am using totem-xine, but whenever I upgrade totem-plugin, I am forced to remove totem-xine, and upgrade totem. Once totem-plugin and totem have been upgraded and totem-xine is removed, I can replace totem with totem-xine without problems. I am not familiar with the advanced features of pacman, but I am guessing this issue is caused by the way the dependencies are defined in the package(s).
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 28 September 2007, 03:55 GMT
Reason for closing:  Not a bug
Additional comments about closing:  No longer an issue.
Comment by Jan de Groot (JGC) - Wednesday, 19 July 2006, 17:24 GMT
Assigning to judd: totem-plugin depends on a specific version of totem, which can be totem-xine or totem itself. Upgrading totem and totem-xine by hand using pacman -U works fine, but it seems pacman really wants the specific "totem" package when upgrading with -Su. When looking for a dependency candidate, it should put upgrading the current virtual dependency to a newer version before installing another package that is named like the virtual dependency.
Comment by Aaron Griffin (phrakture) - Friday, 29 December 2006, 18:10 GMT
Sorry 'bout that - switched the category, then noticed Jan's comment... it _is_ pacman related.

Loading...