Re: KDEE3 question
On Thu, Dec 05, 2002 at 05:17:19PM +1100, Daniel Stone wrote:
> First thing: KDE 3.1 will not be released this week. Expect a public
> announcement on this soon, but until then, I can say no more. Sorry, but
> it's out of my control.
I know what you're talking about as I just talked to Ralf.
> Secondly, ftpmasters have to add overrides for new packages, in case you
> didn't realize. That takes time: their time adding them, and our time
> waiting. We're trying to minimize the problems by ramming KDE3.1 in with
> gcc 3.2 and killing two birds with one stone. Not doing so just adds a
I see the logic behind this, don't get me wrong. The problem just is
that the gcc movement is slowing down the KDE packages for quite some
time. After all we could have had 3.0.3 or 3.0.4 in Debian for months
> stupid amount of work to both us (the Debian KDE maintainers - Chris,
> Ben Burton, Daniel Schepler, David Pashley, Ralf Nolden, and myself),
> and the ftpmasters.
I can understand that you want to minimize your workload, but then the
packages are there. Ralf spend quite some time on the packages and I'm
sure the others did as well. The only difference right now is that the
packages are stored elsewhere and yes, the ftpmasters don't have to add
them so far.
> Until then, you'll just have to wait. More work also still has to be
> done on 2.2->3.1 upgrades before it goes into sid, but that's a
> completely moot point, because it probably won't go in for over a month,
> even if gcc 3.2 on SPARC is finally fixed.
But then this work has to be spend anyway. Why not starting the testing
cycle now with 3.0.5 so 3.1 goes in cleanly?
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!