[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#797109: marked as done (libstdc++6: please consider bumping shlibs to version >= 5)



Your message dated Sat, 13 Feb 2016 10:55:11 +0100
with message-id <56BEFD7F.3070109@debian.org>
and subject line Re: Bug#797109: libstdc++6: please consider bumping shlibs to version >= 5
has caused the Debian Bug report #797109,
regarding libstdc++6: please consider bumping shlibs to version >= 5
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 owner@bugs.debian.org
immediately.)


-- 
797109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 5.2.1-15
Severity: normal

The libstdc++ transition would be easier to track if its shlibs forced
a dependency on libstdc++ (>= 5) even for packages not using any of
the new symbols.

In practice I suspect most C++ packages depend on a package that has needed
a transition anyway, and some packages (such as KDE) are apparently
migrating, but actually broken in testing.

Regards,
    S

--- End Message ---
--- Begin Message ---
tags 797109 + wontfix
thanks

On 27.08.2015 22:24, Simon McVittie wrote:
Package: libstdc++6
Version: 5.2.1-15
Severity: normal

The libstdc++ transition would be easier to track if its shlibs forced
a dependency on libstdc++ (>= 5) even for packages not using any of
the new symbols.

In practice I suspect most C++ packages depend on a package that has needed
a transition anyway, and some packages (such as KDE) are apparently
migrating, but actually broken in testing.

done with the transition. closing as won't fix.

--- End Message ---

Reply to: