Bug#794891: iceweasel: 39.0.3-1 suddenly depends on libstdc++6 >= 5.2 instead of >= 4.9 as before

[Nicolas KAROLAK]

On Sat, 8 Aug 2015 15:31:55 +1000 David Tulloh <david at tulloh.id.au> wrote:
> On Fri, 7 Aug 2015 21:31:04 +0200 Moritz Muehlenhoff <jmm at inutil.org> wrote:
> > On Fri, Aug 07, 2015 at 08:10:54PM +0200, Thibaut Renaux wrote:
> > > Package: iceweasel
> > > Version: 39.0-1
> > > Severity: grave
> > > Justification: renders package unusable
> > >
> > > I'm tracking stable for most of my packages but am using experimental
> for
> > > Iceweasel since it's the only way to get the latest version.
> > >
> > > I'm currently running Iceweasel 39.0-1 and wanted to upgrade to
> 39.0.3-1,
> > > mostly to get the fix for CVE-2015-4495.
> > >
> > > However, when trying to upgrade it with aptitude, I get the following:
> > >
> > > "
> > > The following packages will be upgraded:
> > >   iceweasel{b}
> > > 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > > Need to get 38.9 MB of archives. After unpacking 824 kB will be freed.
> > > The following packages have unmet dependencies:
> > >  iceweasel : Depends: libstdc++6 (>= 5.2) but 4.9.2-10 is installed.
> > > "
> > >
> > > aptitude then proposes solutions ranging from ignoring the update,
> downgrading
> > > Iceweasel, or upgrading libstdc++6 which would then break dozens of
> currently
> > > installed packages.
> > >
> > > I understand my setup is prone to this kind of issue, due to tracking
> multiple
> > > branches. However, I don't really understand why that dependency on a
> newer
> > > version of libstdc++6 suddenly appeared, especially considering this is
> a minor
> > > update.
> > >
> > > Would it be possible to revert the dependency back to libstdc++6 >= 4.9?
> >
> > No, that's an ongoing transition:
> > https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html
> 
> Would depending on libstdc++6 >= 5.1 be an acceptable middle ground?
> 
> This would allow pulling in the testing tree rather than the risking
> unstable.
> 
> 
> David

Even in testing it doesn't work, it requires 5.1.1-14 but only 5.1.1-13
is available.

-- 
Cordialement,
Nicolas KAROLAK