Re: c++ allocator transition status

2005-12-11 Thread Jan De Luyck
On Sunday 11 December 2005 23:08, Curt Howland wrote: > Checking just now, and digikam, kigikamimage, ksocrat, kimdaba, > showimg, celestia, kipi-plugins, superkaramba and tellico are all > listed for removal based on dependency of kdelibs4c2. > > I guess I'll wait a few more days. Well, you can a

Re: c++ allocator transition status

2005-12-11 Thread Curt Howland
On Sunday 11 December 2005 16:41, Georg Prager was heard to say: > Don't forget kimdaba! Checking just now, and digikam, kigikamimage, ksocrat, kimdaba, showimg, celestia, kipi-plugins, superkaramba and tellico are all listed for removal based on dependency of kdelibs4c2. I guess I'll wait a fe

Re: c++ allocator transition status

2005-12-11 Thread Adeodato Simó
* Georg Prager [Sun, 11 Dec 2005 22:41:27 +0100]: > On Thursday 08 December 2005 13:35, EmIscA wrote: > > This list is only to give a little overview of the transition status. > Don't forget kimdaba! You'll find it in today's mirror pulse. In fact, as of today's mirror pulse, only the follow

Re: c++ allocator transition status

2005-12-11 Thread Georg Prager
On Thursday 08 December 2005 13:35, EmIscA wrote: > This list is only to give a little overview of the transition status. > Don't forget kimdaba! pgpvgrwkazpl6.pgp Description: PGP signature

Re: c++ allocator transition status

2005-12-08 Thread Adeodato Simó
(Now, let's do some productive stuff with this thread.) * EmIscA [Thu, 08 Dec 2005 13:35:24 +0100]: Hi, > Today I tried to simulate a dist-upgrade (on sid) with synaptic. These > are the packages (depending on my package selection) that seem to > require the transition: Thanks for this info

Re: c++ allocator transition status

2005-12-08 Thread Matej Cepl
Hendrik Sattler wrote: > Neither is the case with kaffeine in mind. It's not a lib, dependencies > are not too tight, and it's already recompiled for c2a in Sid and could be > pushed to testing with the rest of whatever when that's due. > And I seriously hope they do not remove packages because of

Re: c++ allocator transition status

2005-12-08 Thread Christopher Martin
On Thursday 08 December 2005 11:24, Hendrik Sattler wrote: > Am Donnerstag, 8. Dezember 2005 13:35 schrieb EmIscA: > > Today I tried to simulate a dist-upgrade (on sid) with synaptic. These > > are the packages (depending on my package selection) that seem to > > require the transition: > > > > - d

Re: c++ allocator transition status

2005-12-08 Thread Adeodato Simó
* Hendrik Sattler [Thu, 08 Dec 2005 18:22:16 +0100]: > Neither is the case with kaffeine in mind. It's not a lib, dependencies are > not too tight, and it's already recompiled for c2a in Sid and could be pushed > to testing with the rest of whatever when that's due. So? It will get pushed whe

Re: c++ allocator transition status

2005-12-08 Thread Hendrik Sattler
Am Donnerstag, 8. Dezember 2005 17:54 schrieb Adeodato Simó: > The testing distribution is not an easy thing to manage, I can tell > you that. Competent people are in charge of it, so you shouldn't have > _any_ doubts that if a package gets removed from there, it is > certainly not to annoy

Re: c++ allocator transition status

2005-12-08 Thread Adeodato Simó
* Hendrik Sattler [Thu, 08 Dec 2005 17:24:41 +0100]: > I find it worse that ftp-master messes around in testing like hell :-( Just fyi, the testing distribution is competece of the release team, not of ftp-masters. > Anybody knows what's going on, here? ftp-master gone nuts? Do. Not. Insu

Re: c++ allocator transition status

2005-12-08 Thread Hendrik Sattler
Am Donnerstag, 8. Dezember 2005 13:35 schrieb EmIscA: > Today I tried to simulate a dist-upgrade (on sid) with synaptic. These > are the packages (depending on my package selection) that seem to > require the transition: > > - digikam > - kipi-plugins (related to digikam) > - inkscape (conflicts wi

c++ allocator transition status

2005-12-08 Thread EmIscA
Today I tried to simulate a dist-upgrade (on sid) with synaptic. These are the packages (depending on my package selection) that seem to require the transition: - digikam - kipi-plugins (related to digikam) - inkscape (conflicts with aptitude, I think for some dependences) - kile-i18n (kile is