You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using librarian-puppet 5.0.0 from the debian package in debian sid.
I'm seeing a conflict reported by librarian-puppet that I think should not be a conflict at all (librarian-puppet should be able to resolve this by itself).
The following example will possibly not stand the test of time (maybe it will, since the second module uses a git commit hash directly?). The following Puppet file is a minimal reproducer for the issue:
forge "https://forgeapi.puppetlabs.com"
mod 'puppet/kmod'
mod 'smash/ganeti',
:git => 'https://gitlab.com/shared-puppet-modules-group/puppet-ganeti.git',
:commit => '393056a9e57f47be60ad15e1acfa46b963cb92a5'
when I launch librarian-puppet install --verbose with this file, I get told that there is a version conflict between puppet/kmod, which has no version restriction, and smash/ganeti which has an upper bound on the kmod module version.
What seems to be happening is that librarian-puppet first processes the line mod 'puppet/kmod' and chooses the current latest version, 4.0.1, then it processes the line mod 'smash/ganeti' and since it has already chosen the earliest version for kmod, it's unable to fulfill the requirements for ganeti. But in this situation, since there is no version restriction on kmod, librarian-puppet should be able "backtrack" and to decide to bump kmod's version down to the last version before 4.0.0 as long as that change respects all other known constraints for the version of kmod.
Here's the full output from librarian-puppet with the Puppetfile above:
Note: In the example Puppetfile, if I move the line mod 'puppet/kmod' to the bottom of the file, librarian-puppet is then able to figure out the dependencies correctly. This shows that librarian-puppet is just tripping over its own wires.
I'm using librarian-puppet 5.0.0 from the debian package in debian sid.
I'm seeing a conflict reported by librarian-puppet that I think should not be a conflict at all (librarian-puppet should be able to resolve this by itself).
The following example will possibly not stand the test of time (maybe it will, since the second module uses a git commit hash directly?). The following Puppet file is a minimal reproducer for the issue:
when I launch
librarian-puppet install --verbose
with this file, I get told that there is a version conflict betweenpuppet/kmod
, which has no version restriction, andsmash/ganeti
which has an upper bound on the kmod module version.What seems to be happening is that librarian-puppet first processes the line
mod 'puppet/kmod'
and chooses the current latest version, 4.0.1, then it processes the linemod 'smash/ganeti'
and since it has already chosen the earliest version for kmod, it's unable to fulfill the requirements for ganeti. But in this situation, since there is no version restriction on kmod, librarian-puppet should be able "backtrack" and to decide to bump kmod's version down to the last version before4.0.0
as long as that change respects all other known constraints for the version of kmod.Here's the full output from librarian-puppet with the Puppetfile above:
The text was updated successfully, but these errors were encountered: