Apache 1.3.x, because apache2 isn't close to being production-ready
XFree86 4.1.x
Kernel 2.4.x has been here since the dawn of time
I think you're bark^Wlooking up the wrong tree (har har har). Try seeing what woody actually has, some day.
2.2.2 *is* in testing. The issue is not this, the issue is that we don't want x.x.0 in a stable series, and KDE bloates the archive. Like, heaps.
Like, 2.5 gig on its own.
Having KDE3 would up this figure significantly. Think about it.
Our sponsors are already generous enough; maybe it's just because I live in Australia, this fantastic backwater of the Internet, but I shudder to think of transferring all that crap for people who pay for their bandwidth.
KDE3 is not yet tested enough for a Debian stable release, trust me. Neither are the debs, packaging issues can play a significant part in some problems. I'm personally waiting for 3.0.1 or 3.0.2 before I start deploying it throughout work, although I tracked KDE3 CVS for some time at home (I can deal with segfaults, and it makes it easier to package if you only have to make slight changes every time, instead of being hit with one big lot in the tarballs).
apache2 is NOT NOT NOT ready for prime time. I would not deploy this in a Debian stable release; luckily, neither would Thom. When I maintained it, I always said it would wait until after woody, and luckily it will. The GA was only announced today, and so Thom would have to upload it as NEW, which means it wouldn't make it into woody, even if it could. Even offering it side-by-side with Apache 1.3.x in a stable series is irresponsible.
As for XFree86 4.2, Branden's been too busy with fixing up 4.1.x to do 4.2.x well. XFree86 is one of those dead core packages that need to just WORK every single time, and cannot screw up. There was never enough time to give it the thrashing it needs; I think that having XF4.1.x in a stable series is a pretty sweet effort; Branden deserves a pat on the back. He has a reputation for quality, well-tested packages, and I somehow doubt he'd shatter that this close to a release. Plus, we'd all rip his arms off and beat him to death with the limp end if he did.
Thom has the debs available, along with vhost-base, at pandora.d.o, and they're stable, and good, and stuff, but they will NOT go into woody.
Re:One thing that's starting to annoy me about deb
on
KDE 3.0 is Out
·
· Score: 3, Informative
We have had experimental debs for some time, but have not wanted to release them to the public as they weren't ready for general consumption. The only release that was vaguely public was the whole RC4 fiasco, and its being made public was not my doing.
KDE3 won't enter sid for a while yet; not until woody is released. Don't hold your breath. The reason we do this is because KDE2.2.2 currently takes up about 2.5gig of archive space, and forking with KDE3 would not only cause havoc with the woody release, but it would also make it impossible for us to issue any 2.2.2 fixes, and bloat the archive massively. I'm not going to be a party to this.
Re:One thing that's starting to annoy me about deb
on
KDE 3.0 is Out
·
· Score: 4, Informative
KDE 3.0.0 final tarballs were released to a group of packagers 9 days ago. That's how everyone has final packages, and that's why I have some packages that end in _3.0.0-1_i386.deb.
As for the accusations of being i386-only, that's completely false.
That's one of the main reason to choose Debian. If something doesn't build correctly on all arches (autobuilders), then it'll get a serious-severity bug against it, and that version won't make it to testing.
Our current Debian Project Leader (Ben Collins) is the lead SPARC porter, while Bdale Garbee, who came 4th IIRC is the main IA64 porter, and Branden Robinson is active in PowerPC stuff. Porters are given a high status in Debian as it's absolutely essential.
Do your homework sometime. One of the main reasons to choose Debian is the diversity of architecture support.
Hi,
I'm DanielS, who originally submitted the story. You can find me on irc.openprojects.net as DanielS, if you want to talk to me.
Around an hour ago, OpenProjects started experiencing severe difficulties caused by a minor bug. All of our servers disconnected, and were all independent. Because of this, one of our operators took the decision to revert back to the old codebase.
Please be assured that we are working on it, and hope to redeliver you to the dancer codebase very soon. It's been very upsetting for us to see the revert happen.
As anything breaks, I will post news about it in #conversion, irc.openprojects.net. This channel is moderated, and is for operators to post news only./msg me if you feel you have something newsworthy.
Thankyou for your patience and your support of OpenProjects Net. We hope to see you there soon.
Slashdot Mirror
As soon as calc and I finish sorting out things like how the KDM session-setting stuff works, you can leave my bloody cow alone. :)
Mozilla 0.9.9 (is 1.0.0 even released?)
GNOME 1.4, and also GLib/GTK 2.0
KDE 2.2.2, with KDE3 debs to separately available
Apache 1.3.x, because apache2 isn't close to being production-ready
XFree86 4.1.x
Kernel 2.4.x has been here since the dawn of time
I think you're bark^Wlooking up the wrong tree (har har har). Try seeing what woody actually has, some day.
What, you mean apart from the fact some architectures need 2.2.x, and some need 2.4.x?
2.2.2 *is* in testing. The issue is not this, the issue is that we don't want x.x.0 in a stable series, and KDE bloates the archive. Like, heaps.
Like, 2.5 gig on its own.
Having KDE3 would up this figure significantly. Think about it.
Our sponsors are already generous enough; maybe it's just because I live in Australia, this fantastic backwater of the Internet, but I shudder to think of transferring all that crap for people who pay for their bandwidth.
alien does this.
Why the *hell* is this not good?
KDE3 is not yet tested enough for a Debian stable release, trust me. Neither are the debs, packaging issues can play a significant part in some problems. I'm personally waiting for 3.0.1 or 3.0.2 before I start deploying it throughout work, although I tracked KDE3 CVS for some time at home (I can deal with segfaults, and it makes it easier to package if you only have to make slight changes every time, instead of being hit with one big lot in the tarballs).
apache2 is NOT NOT NOT ready for prime time. I would not deploy this in a Debian stable release; luckily, neither would Thom. When I maintained it, I always said it would wait until after woody, and luckily it will. The GA was only announced today, and so Thom would have to upload it as NEW, which means it wouldn't make it into woody, even if it could. Even offering it side-by-side with Apache 1.3.x in a stable series is irresponsible.
As for XFree86 4.2, Branden's been too busy with fixing up 4.1.x to do 4.2.x well. XFree86 is one of those dead core packages that need to just WORK every single time, and cannot screw up. There was never enough time to give it the thrashing it needs; I think that having XF4.1.x in a stable series is a pretty sweet effort; Branden deserves a pat on the back. He has a reputation for quality, well-tested packages, and I somehow doubt he'd shatter that this close to a release. Plus, we'd all rip his arms off and beat him to death with the limp end if he did.
Thanks for listing the good points of Woody.
No, you're wrong. aptitude, deity-gtk and more exist, and are very, very sweet. Deity could do well to segfault less, tho.
Thom has the debs available, along with vhost-base, at pandora.d.o, and they're stable, and good, and stuff, but they will NOT go into woody.
We have had experimental debs for some time, but have not wanted to release them to the public as they weren't ready for general consumption. The only release that was vaguely public was the whole RC4 fiasco, and its being made public was not my doing.
* cough*
KDE3 won't enter sid for a while yet; not until woody is released. Don't hold your breath. The reason we do this is because KDE2.2.2 currently takes up about 2.5gig of archive space, and forking with KDE3 would not only cause havoc with the woody release, but it would also make it impossible for us to issue any 2.2.2 fixes, and bloat the archive massively. I'm not going to be a party to this.
*cough*youwillhaveanaptsourcefrommeinabout12hours
KDE 3.0.0 final tarballs were released to a group of packagers 9 days ago. That's how everyone has final packages, and that's why I have some packages that end in _3.0.0-1_i386.deb.
As for the accusations of being i386-only, that's completely false.
That's one of the main reason to choose Debian. If something doesn't build correctly on all arches (autobuilders), then it'll get a serious-severity bug against it, and that version won't make it to testing.
Our current Debian Project Leader (Ben Collins) is the lead SPARC porter, while Bdale Garbee, who came 4th IIRC is the main IA64 porter, and Branden Robinson is active in PowerPC stuff. Porters are given a high status in Debian as it's absolutely essential.
Do your homework sometime. One of the main reasons to choose Debian is the diversity of architecture support.
Are you using anti-aliasing? If you are, then here is my answer. If not, I'd be looking at xfs and friends.
Bugs. Yes, filing bugs is good.
-DanielS
Hi, I'm DanielS, who originally submitted the story. You can find me on irc.openprojects.net as DanielS, if you want to talk to me. Around an hour ago, OpenProjects started experiencing severe difficulties caused by a minor bug. All of our servers disconnected, and were all independent. Because of this, one of our operators took the decision to revert back to the old codebase. Please be assured that we are working on it, and hope to redeliver you to the dancer codebase very soon. It's been very upsetting for us to see the revert happen. As anything breaks, I will post news about it in #conversion, irc.openprojects.net. This channel is moderated, and is for operators to post news only. /msg me if you feel you have something newsworthy.
Thankyou for your patience and your support of OpenProjects Net. We hope to see you there soon.