On Tue, 12 May 2020 07:33:45 +0900 Mike Hommey wrote:

> On Tue, May 12, 2020 at 12:17:36AM +0200, Francesco Poli wrote:
> > On Tue, 12 May 2020 06:55:00 +0900 Mike Hommey wrote:
> > 
> > > On Mon, May 11, 2020 at 11:34:39PM +0200, Francesco Poli wrote:
> > [...]
> > > > Yes, I downgraded firefox-esr and the bug vanished.
> > > > This confirms that the issue is indeed caused by the new version of
> > > > firefox-esr.
> > > 
> > > Or not. This could also be caused by some upgraded build dependency.
> > 
> > Well, that's another possibility, I agree...
> > 
> > > Do you have the resources to attempt rebuilding 68.7 against current
> > > unstable?
> > 
> > I can try inside a pbuilder-managed sid chroot.
> > 
> > I issued the following command:
> > 
> >  $ dget 
> > https://snapshot.debian.org/archive/debian/20200408T025735Z/pool/main/f/firefox-esr/firefox-esr_68.7.0esr-1.dsc
> > 
> > and obtained the unpacked source package.
> > 
> > Can you confirm that this the source I should attempt to build?
> 
> Sounds good.

Mmmmh...

debian/control includes

  Build-Depends: [...]
                 libvpx-dev (>= 1.5.0),
                 [...]
  Build-Conflicts: [...]
                   libvpx-dev (>= 1.8.0),
                   [...]

but current sid has:

  $ rmadison libvpx-dev | grep unstable
  libvpx-dev | 1.8.2-1         | unstable     | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x

How should I handle this conflict?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgpwqa0TLIloS.pgp
Description: PGP signature

Reply via email to