[Pkg-puppet-devel] Bug#1129967: puppetserver has unmet dependencies

[Jérôme Charaoui]

Le 2026-03-12 à 05 h 02, Paul Gevers a écrit :
> Hi,
> 
> On Fri, 06 Mar 2026 21:52:48 +0200 Adrian Bunk <bunk at debian.org> wrote:
>> Package: puppetserver
>> Version: 8.7.0-6
>> Severity: serious
>>
>> The following packages have unmet dependencies:
>>  puppetserver : Depends: ruby-locale (< 2.1.4.) but 2.1.5-1 is to be 
>> installed
>>                 Depends: ruby-concurrent (< 1.3.5.) but 1.3.6-1 is to 
>> be installed
> 
> I'm seeing a reoccurring pattern:
> 
> puppetserver (8.7.0-4) unstable; urgency=medium
> 
>    * Rebuild for new version of ruby-concurrent (Closes: #1100569)
> 
> puppetserver (8.7.0-3) unstable; urgency=medium
> 
>    * Rebuild for new version of ruby-concurrent (Closes: #1092567)
> 
> puppetserver (8.4.0-7) unstable; urgency=medium
> 
>    * Rebuild for ruby-puppetserver-ca-cli update.
> 
> puppetserver (8.4.0-4) unstable; urgency=medium
> 
>    * Rebuild for ruby-gettext update (Closes: #1077156)
> 
> 
> It seems to me that these upper limit Depends are generated during 
> building. Are they really useful or just a safeguard? In the latter 
> case, I wonder if the solution isn't worse than the problem, 
> particularly if the package has significant autopkgtests. Our 
> infrastructure will spot breakage and prevent migration. It seems like 
> this upper limit now is causing artificial breakage.

These limits are needed for running puppetserver: when building the 
package, versioned symlinks for a handful of (packaged) ruby libraries 
are generated and included. These symlinks contain version numbers 
because of the way gem-ified ruby libraries are structured on the 
filesystem.

The alternative would be to embed separate copies of the libraries in 
the package, but I try to avoid that.

-- Jérôme