FS#49871 - "provides" without specifying version does not pass ranged dependency checks
Attached to Project:
Pacman
Opened by Baptiste (zorun) - Tuesday, 28 June 2016, 08:25 GMT
Last edited by Allan McRae (Allan) - Tuesday, 28 June 2016, 08:46 GMT
Opened by Baptiste (zorun) - Tuesday, 28 June 2016, 08:25 GMT
Last edited by Allan McRae (Allan) - Tuesday, 28 June 2016, 08:46 GMT
|
Details
When a package "provides" another without explicitly
specifying a version, it seems to fail any ranged dependency
check.
Here is an example: - alsa-lib is at version 1.1.1 - alsa-utils depends on alsa-lib>1.0.24 - alsa-lib-noassertion 1.1.1 [1] provides alsa-lib - installing alsa-lib-noassertion instead of alsa-lib breaks the dependency from alsa-utils to alsa-lib>1.0.24 The expected behaviour would be to use the version number of alsa-lib-noassertion, 1.1.1, when resolving a dependency such as alsa-lib>1.0.24. To reproduce: $ wget https://aur.archlinux.org/cgit/aur.git/snapshot/alsa-lib-noassertion.tar.gz $ tar xvf alsa-lib-noassertion.tar.gz $ cd alsa-lib-noassertion $ makepkg --syncdeps $ sudo pacman -U --nodeps alsa-lib-noassertion-1.1.1-1-x86_64.pkg.tar.xz $ sudo pacman -Dk error: missing 'alsa-lib>1.0.24' dependency for 'alsa-utils' [1] https://aur.archlinux.org/packages/alsa-lib-noassertion |
This task depends upon
Is it always necessary to specify the version in a "provides" field, e.g. provides=("alsa-lib=1.1.1")?