[Pkg-puppet-devel] Bug#878193: fails to start with minimal dependencies from testing

[Adrian Bunk]

On Fri, Dec 21, 2018 at 09:07:19AM +0100, intrigeri wrote:
> Hi,
> 
> AFAICT:
> 
>  - This bug is about installing packages from testing/sid on stable,
>    i.e. partial upgrade, which is not supported.

This is kinda supported, and there are important usecases that have
a big overlap with it:
- ensuring everything continues working during an upgrade
  (might not be applicable in this specific case)
- ensuring the package does not migrate to testing too early
- ensuring the package works if backported

>  - Two different workarounds were documented (one visible here and one
>    erroneously sent to control at bugs.debian.org:
>    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878193;msg=7)
> 
> So I don't understand why this bug should be RC for Buster: it does
> not actually affect Buster and there's no supported upgrade path given
> PuppetDB was not part of any Debian stable release yet.
> 
> Adrian, what do you think? Thanks in advance!

Ignoring the severity question, versioning the dependencies
on the 5 packages mentioned in the workaround should not be
a controversial thing. It would at least ensure that noone
will create a broken backport to stretch.

But there is a real blocker hidden in the workaroud:
  # java-1.8 should be the default runtime, if it's not check update-alternatives

The date when the autopkgtest started failing also indicate that the
package might be broken with Java >= 9, and buster will use Java 11.

> Cheers,

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed