On 3/20/23 17:13, Renato Gallo wrote:
Package: puppet
Version: 7.23.0
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainers,
At work I must install foreman and puppet using the official upstream repos for
a testing environment which are
cat puppet7.list
# Puppet 7 bullseye Repository
deb http://apt.puppetlabs.com bullseye puppet7
cat foreman.list
deb http://deb.theforeman.org/ bullseye nightly
deb http://deb.theforeman.org/ plugins nightly
problem being that the puppet debian version is not 7.23.0 the upstream dep
package has been named puppet7-release (not just puppet) and after having
installed a module via apt I find myself in a broken condition where apt
absolutely wants to install the old version of puppet (even when I try to
uninstall it) which breaks the foreman nightly installation. Can you please I
pray you upgrade the debian repo so that it follows the upstream one ?
else can you tell me how can I set up my preferences so that only the upstream
repo is considered ?
I have tried setting priority 1001 but it doesn't seem to work for all the
packages
Thanks in advance
Hi Renato,
Thanks for your bug report. However...
What you're reporting here, is an issue due to using upstream
repository. In no way, this is a valid bug report for Debian (ie: the
Debian repository and packages are working perfectly well).
Therefore, I'm closing your bug. If you need help on how to setup and
use upstream repositories, I strongly suggest you that you ask for such
help upstream, or in another location than the bug tracker.
If you think there's ways to improve the Debian packaging so that it
plays in a nicer way with upstream repositories, this IMO is a case for
a wishlist bug, absolutely not severity: grave.
Cheers,
Thomas Goirand (zigo)
