On 08/15/2010 10:48 AM, Lionel Le Folgoc wrote:
> On Sun, Aug 15, 2010 at 05:07:40PM +0200, Martin Pitt wrote:
>> Hello,
>>
>> Benjamin Drung [2010-08-14 20:51 +0200]:
>>> I am asking this question, because libstdc++5 was removed from karmic
>>> and it was recently reintroduces in maverick.
>>
>> I
Hi Lionel (2010.08.15_17:48:56_+0200)
> AFAIK (and according to LP), it wasn't autosynced but instead
> reintroduced manually by a developer using syncpackage
I sponsored that (using syncpackage). And yes it had to go through NEW
again. Was there someone else I should have asked?
> I wasn't reall
On Sun, Aug 15, 2010 at 05:07:40PM +0200, Martin Pitt wrote:
> Hello,
>
> Benjamin Drung [2010-08-14 20:51 +0200]:
> > I am asking this question, because libstdc++5 was removed from karmic
> > and it was recently reintroduces in maverick.
>
> I wasn't really happy about libstdc++ returning to mav
Hello,
Benjamin Drung [2010-08-14 20:51 +0200]:
> I am asking this question, because libstdc++5 was removed from karmic
> and it was recently reintroduces in maverick.
I wasn't really happy about libstdc++ returning to maverick, but it
kind of "just happened" through autosyncs.
-backports sounds
Hi,
Some packages get removed from the archive. They are reintroduces to the
archive some releases later, but they are missing in the releases
between. Can we reintroduce packages through -proposed instead of only
backporting them?
I am asking this question, because libstdc++5 was removed from k
