Your message dated Mon, 20 Mar 2023 13:39:33 -0400
with message-id <3c1d8f59-d96d-6120-c967-d1757f59c...@debian.org>
and subject line Re: puppet: apt install puppet and puppet modules clash with
official upstream repo
has caused the Debian Bug report #1033243,
regarding puppet: apt install puppet and puppet modules clash with official
upstream repo
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (500, 'unstable-debug'),
(500, 'testing-security'), (500, 'testing-debug'), (499, 'experimental'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.2.7 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages puppet depends on:
pn puppet-agent <none>
puppet recommends no packages.
puppet suggests no packages.
--- End Message ---
--- Begin Message ---
tags 1033243 wontfix
thanks
Hello,
Generally, the Puppet ecosystem as packaged in the Debian archive isn't
compatible with the upstream repositories and we currently don't plan to
fix this.
Files are not installed in the same directories, versions won't be the
same and you'll experience weird breakage, like the one you seem to have.
If you absolutely need to use upstream's repositories, I would thus
recommend you don't use any of the Debian packages.
If you want to keep using the Debian packages and you need Puppet
modules that aren't packaged in the Debian, a more common workflow would
be to use the Debian packages, but download Puppet modules either
"manually" via git or from the Puppet forge.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
⠈⠳⣄
--- End Message ---
