5 ms·

A curious fact is that Debian name their releases after Toy Story characters. Debian experimental is permanently named "sid" (the kid that breaks toys) and "st

A curious fact is that Debian name their releases after Toy Story characters. Debian experimental is permanently named "sid" (the kid that breaks toys) and "stretch" (Debian 9) is a rubber octopus from Toy Story 3. https://www.debian.org/doc/manuals/project-history/ch-releases.en.html https://www.debian.org/doc/manuals/project-history/ch-releas... https://wiki.debian.org/DebianUnstable#Which_Toy_Story_character_is_Sid.3F https://wiki.debian.org/DebianUnstable#Which_Toy_Story_chara... Other curious fact about Debian, is that there are 2 logos: the open use one, and the restricted use one. The restricted use one is a less known and includes a bottle.

jlgaddis 9y ago
sid == unstable
- evook 9y ago
  sid (still in Development)
  - jlgaddis 9y ago
    I began using Debian c. 1998 and I've never heard that.
  - scbrg 9y ago
    While true, I guess the point was that it's misleading to refer to sid as Debian's "experimental" release, since Debian actually has a "release" referred to as experimental and it is not sid. https://wiki.debian.org/DebianExperimental https://wiki.debian.org/DebianExperimental
    - evook 9y ago
      But sid isn't referred to as an experimental release. The experimental release is more or less an voluntary option for the devs to use or not. > Some packages/developers don't use experimental, they just put the new versions in unstable
  - samueloph 9y ago
    "It is sometimes wrongly backronymed as "Still In Development"" https://wiki.debian.org/DebianUnstable#Which_Toy_Story_character_is_Sid.3F https://wiki.debian.org/DebianUnstable#Which_Toy_Story_chara...
  - middleclick 9y ago
    sid is said to be unstable but I have experienced the opposite of that. In fact, testing is way more unstable than sid.
    - samueloph 9y ago
      That is not true at all, and i can prove to you by showing just one bugreport: An update to network-manager broke dns for everyone, the broken package stayed about 5 hours on unstable repository, if i recall correctly. This broken package never got even close to being on testing. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784587 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784587
      - lorenzhs 9y ago
        On the other hand, if a serious issue is detected after a specific version has already migrated to testing, the package will never (automatically) migrate to testing as long as new blocking issues keep being found. This can make testing rather unpleasant. Of course, the same two-week wait time also applies to any regular bugfix, unless it's manually migrated to testing. Thus, one bug that affected unstable but not testing is not proof at all. Personally, I'm happier with unstable than testing on my laptop and work desktop.
        samueloph 9y ago
        > On the other hand, if a serious issue is detected after a specific version has already migrated to testing, the package will never (automatically) migrate to testing as long as new blocking issues keep being found. This can make testing rather unpleasant. That is a valid example on what can make testing unpleasant, but still holds my point as this is a lot more uncommon than sid breakages, and also the package is removed from testing automatically a few days after any RC bug is filled, which prevent new testing installations of this broken package. > Of course, the same two-week wait time also applies to any regular bugfix, unless it's manually migrated to testing. Thus, one bug that affected unstable but not testing is not proof at all. Personally, I'm happier with unstable than testing on my laptop and work desktop. The default wait time is 5 days (medium urgency), high urgency fixes (which fixes RC bugs on testing) waits 2 days before being migrated to testing. But you don't need to believe me, see for yourself: Release critical bugs affecting sid (excluding packages that are already removed from testing, so we don't see any obsolete package that is to be removed from unstable too)[1]: 539 Release critical bugs affecting testing[2]: 453 [1]https://udd.debian.org/bugs/?release=sid&notbuster=ign&merged=ign&done=ign&fnewerval=7&flastmodval=7&rc=1&ctags=1&cdeferred=1&sortby=id&sorto=asc&format=html#results https://udd.debian.org/bugs/?release=sid&notbuster=ign&merge... [2]https://udd.debian.org/bugs/?release=buster&notbuster=ign&merged=ign&done=ign&fnewerval=7&flastmodval=7&rc=1&ctags=1&cdeferred=1&sortby=id&sorto=asc&format=html#results https://udd.debian.org/bugs/?release=buster&notbuster=ign&me...
- squarefoot 9y ago
  For years I thought that the unstable release was named like that as a reference to Sid Vicious.
samueloph 9y ago
I always like to point out the other two logos[1][2] that prefaced the buzz lightyears chin logo[3]. [1]http://ianmurdock.debian.net/index.html%3Fp=1880.html http://ianmurdock.debian.net/index.html%3Fp=1880.html [2]see "old logo" at https://www.debian.org/vote/1999 https://www.debian.org/vote/1999 [3]https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL._SL1500_.jpg/vote_0004 https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL...
- smcl 9y ago
  I get an error for image 3 - what is the logo?
  - samueloph 9y ago
    Sorry, its not really the logo, i was kidding with the fact that the current logo looks like buzzlightyear's chin.
    - smcl 9y ago
      Ahhhhhh I never noticed the swirl on Buzz' chin before!
  - antsar 9y ago
    Fixed URL: https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL._SL1500_.jpg https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL...
- partycoder 9y ago
  I am glad they did not select the chicken logo.
lamby 9y ago
Little known: the "experimental" distribution is called "rc-buggy", a pun on "release critical".
lamby 9y ago
> The restricted use one is a less known and includes a bottle. It indeed is very very rarely used whatsoever these days. Even the "official" CD media (which used to be the only place where it was really seen in the past 10 years) don't really exist anymore.

jlgaddis 9y ago

sid == unstable

evook 9y ago
sid (still in Development)
- jlgaddis 9y ago
  I began using Debian c. 1998 and I've never heard that.
- scbrg 9y ago
  While true, I guess the point was that it's misleading to refer to sid as Debian's "experimental" release, since Debian actually has a "release" referred to as experimental and it is not sid. https://wiki.debian.org/DebianExperimental https://wiki.debian.org/DebianExperimental
  - evook 9y ago
    But sid isn't referred to as an experimental release. The experimental release is more or less an voluntary option for the devs to use or not. > Some packages/developers don't use experimental, they just put the new versions in unstable
- samueloph 9y ago
  "It is sometimes wrongly backronymed as "Still In Development"" https://wiki.debian.org/DebianUnstable#Which_Toy_Story_character_is_Sid.3F https://wiki.debian.org/DebianUnstable#Which_Toy_Story_chara...
- middleclick 9y ago
  sid is said to be unstable but I have experienced the opposite of that. In fact, testing is way more unstable than sid.
  - samueloph 9y ago
    That is not true at all, and i can prove to you by showing just one bugreport: An update to network-manager broke dns for everyone, the broken package stayed about 5 hours on unstable repository, if i recall correctly. This broken package never got even close to being on testing. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784587 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784587
    - lorenzhs 9y ago
      On the other hand, if a serious issue is detected after a specific version has already migrated to testing, the package will never (automatically) migrate to testing as long as new blocking issues keep being found. This can make testing rather unpleasant. Of course, the same two-week wait time also applies to any regular bugfix, unless it's manually migrated to testing. Thus, one bug that affected unstable but not testing is not proof at all. Personally, I'm happier with unstable than testing on my laptop and work desktop.
      - samueloph 9y ago
        > On the other hand, if a serious issue is detected after a specific version has already migrated to testing, the package will never (automatically) migrate to testing as long as new blocking issues keep being found. This can make testing rather unpleasant. That is a valid example on what can make testing unpleasant, but still holds my point as this is a lot more uncommon than sid breakages, and also the package is removed from testing automatically a few days after any RC bug is filled, which prevent new testing installations of this broken package. > Of course, the same two-week wait time also applies to any regular bugfix, unless it's manually migrated to testing. Thus, one bug that affected unstable but not testing is not proof at all. Personally, I'm happier with unstable than testing on my laptop and work desktop. The default wait time is 5 days (medium urgency), high urgency fixes (which fixes RC bugs on testing) waits 2 days before being migrated to testing. But you don't need to believe me, see for yourself: Release critical bugs affecting sid (excluding packages that are already removed from testing, so we don't see any obsolete package that is to be removed from unstable too)[1]: 539 Release critical bugs affecting testing[2]: 453 [1]https://udd.debian.org/bugs/?release=sid&notbuster=ign&merged=ign&done=ign&fnewerval=7&flastmodval=7&rc=1&ctags=1&cdeferred=1&sortby=id&sorto=asc&format=html#results https://udd.debian.org/bugs/?release=sid&notbuster=ign&merge... [2]https://udd.debian.org/bugs/?release=buster&notbuster=ign&merged=ign&done=ign&fnewerval=7&flastmodval=7&rc=1&ctags=1&cdeferred=1&sortby=id&sorto=asc&format=html#results https://udd.debian.org/bugs/?release=buster&notbuster=ign&me...
squarefoot 9y ago
For years I thought that the unstable release was named like that as a reference to Sid Vicious.

samueloph 9y ago

I always like to point out the other two logos[1][2] that prefaced the buzz lightyears chin logo[3]. [1]http://ianmurdock.debian.net/index.html%3Fp=1880.html http://ianmurdock.debian.net/index.html%3Fp=1880.html [2]see "old logo" at https://www.debian.org/vote/1999 https://www.debian.org/vote/1999 [3]https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL._SL1500_.jpg/vote_0004 https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL...

smcl 9y ago
I get an error for image 3 - what is the logo?
- samueloph 9y ago
  Sorry, its not really the logo, i was kidding with the fact that the current logo looks like buzzlightyear's chin.
  - smcl 9y ago
    Ahhhhhh I never noticed the swirl on Buzz' chin before!
- antsar 9y ago
  Fixed URL: https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL._SL1500_.jpg https://images-na.ssl-images-amazon.com/images/I/81x4CGvFvNL...
partycoder 9y ago
I am glad they did not select the chicken logo.

lamby 9y ago

Little known: the "experimental" distribution is called "rc-buggy", a pun on "release critical".

lamby 9y ago

> The restricted use one is a less known and includes a bottle. It indeed is very very rarely used whatsoever these days. Even the "official" CD media (which used to be the only place where it was really seen in the past 10 years) don't really exist anymore.