[832] in athena10
Distribution Upgrades
daemon@ATHENA.MIT.EDU (Evan Broder)
Mon Jan 12 12:08:23 2009
Message-ID: <496B78CB.4080509@mit.edu>
Date: Mon, 12 Jan 2009 12:07:23 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: debathena@mit.edu
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
In the past, doing a release upgrade has caused problems with Debathena.
The update-manager goes through all of /etc/apt/sources.list and
/etc/apt/sources.list.d and disables any repositories that it doesn't
recognize, which includes ours. The solution would be to not comment out
our repository, and substitute the new release for the old release (i.e.
s/hardy/intrepid/) in our sources.list entries as well as the entries
for the Ubuntu archives.
I asked on IRC earlier today if there was some way that we could work
around this. mvo (Michael Vogt - the guy who wrote and maintains
update-manager), suggested adding a DisableThirdPartyRepos option to
/etc/update-manager/release-upgrades, which we could easily override
with a config package. He also said that he could probably get it in
place for Jaunty.
I'm hijacking LP bug #147080 for tracking purposes, if you'd like to
follow along.
- Evan
