[2275] in athena10
Re: [Debathena] #194: Determine whether the "universe" repository
daemon@ATHENA.MIT.EDU (Debathena Trac)
Tue Apr 14 18:56:08 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: tabbott@mit.edu, broder@mit.edu
Date: Tue, 14 Apr 2009 22:55:46 -0000
Reply-To:
Message-ID: <053.290826dd83b9f39570e04540310f13e9@mit.edu>
In-Reply-To: <044.febcedfe1e8305839fec9ecda1fb36b2@mit.edu>
Content-Transfer-Encoding: 8bit
#194: Determine whether the "universe" repository is supported on LTS releases--------------------+-------------------------------------------------------
Reporter: tabbott | Owner:
Type: task | Status: new
Priority: major | Component: --
Keywords: |
--------------------+-------------------------------------------------------
Comment(by broder):
If you want to figure out what "supported on desktops" and "supported on
servers" means in the context of an LTS release, you can try to
dereference packages according to http://people.ubuntu.com/~ubuntu-archive
/germinate-output/ubuntu.hardy/structure and the other files in that
directory.
But...packages in universe and multiverse were never Supported By
Canonical to begin with - they are entirely community supported. That goes
for LTS releases, too - at any point while a release is still supported
(both the first 18 months and the rest of the LTS period), it's at the
"community's" (i.e. motu-sru's) discretion to decide what updates go
through.
For security updates, it seems that it's always the responsibility of the
community to generate patches, but the Ubuntu security team handles the
security release process. There, too, they seem to be fairly generous
about taking updates from the community, regardless of how supported the
release is.
See, for instance, LP 356861, where Kees seems to have effectively
approved the security update for Dapper
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/194#comment:1>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project