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!
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!
FS#7735 - slimserver: should not replace perl-yaml-syck
Attached to Project:
Arch Linux
Opened by Francois Charette (Firmicus) - Saturday, 04 August 2007, 09:31 GMT
Last edited by Tom Killian (tomk) - Monday, 13 August 2007, 10:29 GMT
Opened by Francois Charette (Firmicus) - Saturday, 04 August 2007, 09:31 GMT
Last edited by Tom Killian (tomk) - Monday, 13 August 2007, 10:29 GMT
|
DetailsSummary and Info:
When doing system upgrade, if one has perl-yaml-syck already installed but not slimserver, pacman asks :: Starting full system upgrade... :: Replace perl-yaml-syck with extra/slimserver? [Y/n] But this should occur only if one has both packages installed. Steps to Reproduce: |
This task depends upon
Closed by Tom Killian (tomk)
Monday, 13 August 2007, 10:29 GMT
Reason for closing: Fixed
Additional comments about closing: replaces line is incorrect, removed in slimserver v6.5.3-3
Monday, 13 August 2007, 10:29 GMT
Reason for closing: Fixed
Additional comments about closing: replaces line is incorrect, removed in slimserver v6.5.3-3
and http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/multimedia/slimserver/PKGBUILD?cvsroot=Extra&only_with_tag=CURRENT
upgpkg: slimserver v6.5.3-2
YAML::Syck 0.64 now embedded, replaces perl-yaml-syck
Now slimserver contains
provides=('perl-yaml-syck')
replaces=('perl-yaml-syck')
So pacman does everything correct.
However, you didn't actually finish your report, so if you can add the steps to reproduce, I'll double-check it.
---
I had seen the latest PKGBUILD in CVS, yet I still think that if I want to have perl-yaml-syck on my system but have no need for slimserver, then I should not be asked to replace perl-yaml-syck by slimserver, no? I understand that slimserver needs version 0.64 of YAML::Syck to run, which conflicts with the version in extra, so the line provides=('perl-yaml-syck') is ok. But is it necessary that it _replaces_ it as well? Could it rather be
conflicts=('perl-yaml-syck') instead ? Then the situation I encountered would be avoided. If this is not the case, then this should be closed and a feature request could be made for pacman to handle this in a "smarter" way in the future...
Maybe slimserver could conflicts=('perl-yaml-syck') or don't inclide YAML::Syck files and use depends=('perl-yaml-syck') instead. But that's slimserver packaging issue.