Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • from http://en.wikipedia.org/wiki/Debian [wikipedia.org]

    Software packages in development are either uploaded to the project distribution named unstable (also known as sid), or to the experimental repository. Software packages uploaded to unstable are normally versions stable enough to be released by the original upstream developer, but with the added Debian-specific packaging and other modifications introduced by Debian developers. These additions may be new and untested. Software not ready yet for the unstable distribution is typically placed in the experimental repository.[34]

    After a version of a software package has remained in unstable for a certain length of time (depending on the urgency of the software's changes), that package is automatically migrated to the testing distribution. The package's migration to testing occurs only if no serious (release-critical) bugs in the package are reported and if other software needed for package functionality qualifies for inclusion in testing.[34]

    • Thanks, but that doesn't answer the "why" for this case. I roughly understand the procedure, but I had no idea what the details for Python are, and why it's still in experimental, not even in unstable. I think that Bob's link did reveal the causes, for 2.6. 3.1 remains a mystery.

      • I guess for experimental repository, you will have to ask the package maintainer(s) directly.