When to expect certain packages in testing

Message

detly · #1 Post by **detly** » 2007-05-21 09:14

I'm not even sure what my question is, exactly, so I'll start with an example: pidgin. Say I want to know when it's going to be in testing — where would I look? Is there a site somewhere that reports on the status or progress of individual packages (it's not just pidgin in which I'm interested)?

I found a few pages around the Debian site that detail how the unstable and testing distributions work, but not much on individual packages.

It's just curiosity, really.

Lavene · #2 Post by **Lavene** » 2007-05-21 09:22

Basically a package move to testing when it's ready to move to testing. The required time for a package to stay in unstable is 10 days but if during that time some serious bugs are discovered, which is the whole idea about unstable, it will stay put until it's fixed... there are really no way of telling.

Tina

chrismortimore · #3 Post by **chrismortimore** » 2007-05-21 09:26

Your best bet is here: http://packages.qa.debian.org/p/pidgin.html
It tells you how many bugs are going for it, when it was last updated, why it isn't in testing and dependencies that are stopping it from entering testing.

detly · #4 Post by **detly** » 2007-05-21 09:36

The http://packages.qa.debian.org/ is exactly what I was looking for. I had no idea it existed :) Brilliant! Cheers.

chrismortimore · #5 Post by **chrismortimore** » 2007-05-21 09:39

You're welcome.

kink · #6 Post by **kink** » 2007-05-21 09:51

Just for the record, this is linked from each package page on packages.debian.org under "Developer information for <package>" so you can easily click through.

plugwash · #7 Post by **plugwash** » 2007-05-21 11:37

currently nothing written in a language that produces binaries linked against glibc can migrate until glibc does.

i've been keeping an eye on the situation currently we are waiting to get a sucessfull build of the gcc-4.1 package on arm. Once thats done building of the new version of glibc on arm can begin. Once thats built and required waiting times have been satisfied hopefully glibc and all the stuff backed up behind it can migrate.

detly · #8 Post by **detly** » 2007-05-21 14:47

Yeah, I realise now that it was something of a complicated example. But it often happens that I'm debating whether to wait for a package to trickle through to testing or to just go with the unstable version if it's going to be a while.

bysturyu · #9 Post by **bysturyu** » 2007-05-29 17:48

[spam removed]

AgenT · #10 Post by **AgenT** » 2007-05-29 18:12

bysturyu wrote:This is really a great system. I think That debian will really grow over the years.

What is a great system? How Stable, Testing, Unstable and Experimental work (and work together)? If so, then it's been like that for a *very* long time. Debian was started in 1993 after all, although the different branches started to crop up at later times.

A good quick overview of how Debian works:
http://en.wikipedia.org/wiki/Debian

chrismortimore · #11 Post by **chrismortimore** » 2007-05-29 21:39

If I remember correctly, Testing is quite new though. Wasn't Woody the first to be built using Testing?

Vergil · #12 Post by **Vergil** » 2007-05-30 00:38

AgenT wrote:
bysturyu wrote:This is really a great system. I think That debian will really grow over the years.
What is a great system? How Stable, Testing, Unstable and Experimental work (and work together)? If so, then it's been like that for a *very* long time. Debian was started in 1993 after all, although the different branches started to crop up at later times.

A good quick overview of how Debian works:
http://en.wikipedia.org/wiki/Debian

That person is spamming. Look at the link in the sig and post count

AgenT · #13 Post by **AgenT** » 2007-05-30 01:10

Vergil wrote:That person is spamming. Look at the link in the sig and post count

Thank you for the heads up. Did not notice the signature link as I never read them.