Steve Langasek writes:
> Hmm, I hope you mean libopenalpp-cvs1 here. There's no reason for the
Yes.
> Heh, you're certainly not the only maintainer who doesn't
> understand library versioning...
Sigh :-}
--
Loic Dachary, 12 bd Magenta, 75010 Paris. Tel: 33 8 71 18 43 38
htt
On Thu, Feb 16, 2006 at 01:41:03PM +0100, Loic Dachary wrote:
> Steve Langasek writes:
> > You can't leave the name as it is. If you can't support a stable ABI, you
> > can't have a shared library shipped in a stable release. Given that the
> > name "libopenalpp-cvs" was already used in sarge,
Steve Langasek writes:
> You can't leave the name as it is. If you can't support a stable ABI, you
> can't have a shared library shipped in a stable release. Given that the
> name "libopenalpp-cvs" was already used in sarge, you must either change the
> binary package name or drop the shared
On Thu, Feb 16, 2006 at 01:10:38PM +0100, Loic Dachary wrote:
> Matthias Klose writes:
> > reopen 339237
> > thanks
> > > Changes:
> > > openalpp-cvs (20060217-1) unstable; urgency=low
> > > .
> > >* upstream sync (closes: #339237)
> > that's pretty much not a fix. even no reply on
Matthias Klose writes:
> reopen 339237
> thanks
>
> > Changes:
> > openalpp-cvs (20060217-1) unstable; urgency=low
> > .
> >* upstream sync (closes: #339237)
>
> that's pretty much not a fix. even no reply on Steve's question in the
> bug report. please comment.
I overlo
Processing commands for [EMAIL PROTECTED]:
> reopen 339237
Bug#339237: library package needs to be renamed (libstdc++ allocator change)
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(ad
reopen 339237
thanks
> Changes:
> openalpp-cvs (20060217-1) unstable; urgency=low
> .
>* upstream sync (closes: #339237)
that's pretty much not a fix. even no reply on Steve's question in the
bug report. please comment.
thanks, Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
7 matches
Mail list logo
