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#25866 - A pkg, foo-bar, that provides foo will fail to install if a pkg depends on a specific version of foo
Attached to Project:
Arch Linux
Opened by Andrew Gunnerson (chenxiaolong) - Friday, 02 September 2011, 21:47 GMT
Last edited by Allan McRae (Allan) - Friday, 02 September 2011, 22:22 GMT
Opened by Andrew Gunnerson (chenxiaolong) - Friday, 02 September 2011, 21:47 GMT
Last edited by Allan McRae (Allan) - Friday, 02 September 2011, 22:22 GMT
|
DetailsDescription:
If a package depends on a specific version of package foo, the package, foo-bar, providing foo, will fail to install. For example: PKGBUILD of foo-bar: ===================== pkgname=foo-bar pkgver=1.0 ... provides=('foo') conflicts=('foo') ... ===================== myapp's PKGBUILD: ===================== ... depends=('foo>=1.0') ... ===================== foo-bar will fail to install with the following error: :: foo-bar and foo are in conflict. Remove foo? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: myapp: requires foo>=1.0 Additional info: * package version(s) - pacman 3.5.4-4 |
This task depends upon
Comment by Pierre Schmitz (Pierre) -
Friday, 02 September 2011, 22:08 GMT
What is the bug here? This is intended behavior. Use provides with a specific version. Or even better: reconsider if you really need a versioned depends; in most cases it's wrong.
Comment by Allan McRae (Allan) -
Friday, 02 September 2011, 22:22 GMT
provides=('foo=1.0')... done