[8572] in athena10
Re: [Debathena] #731: update-manager should warn that third-party
daemon@ATHENA.MIT.EDU (Debathena Trac)
Fri Oct 21 11:50:27 2011
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: jdreed@MIT.EDU, andersk@MIT.EDU, geofft@MIT.EDU
Date: Fri, 21 Oct 2011 15:50:23 -0000
Reply-To:
Message-ID: <057.fc0266aa679672c432bb2de32d1e59e1@mit.edu>
In-Reply-To: <042.d43bd8aeb5d0da30216a260411195fe6@mit.edu>
Content-Transfer-Encoding: 8bit
#731: update-manager should warn that third-party sources may not support the new
distro
-------------------------+-----------------------------------
Reporter: jdreed | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: The Distant Future
Component: -- | Resolution:
Keywords: | Upstream bug:
-------------------------+-----------------------------------
Comment (by jdreed):
I did some testing with this today, and I think the right answer is to
change the meta-release file to point to a URI we control. There are
still a couple of screw cases:
- what if -standard and -login work, but -workstation doesn't? Is the
release "supported" or not?
- should this be opt-in or opt-out?
Personally, I think, if you install Debathena, you really don't want to
upgrade to something we don't support. And if you do want to upgrade to
something that will break your system, you're smart enough to override
this mechanism. However, I'd be ok with making it a question (that
defaults to "yes") in the installer (and manual install people are
presumably clueful enough to deal).
Whatever meta-release file we point people at could either be a static
file (that we only fetch from Ubuntu once the release works), or a CGI
script that checks a flag file we set (or, awesomely, debian-versions.sh).
We should maybe also consider shipping our own ReleaseNotes and
ReleaseNotesHtml listed in the meta-releasqe file.
An alternative, is simply to transform meta-release on the fly to point at
our own upgrader tarball which, prior to running the standard upgrade,
checks a Debathena URL, and if the target release isn't supported, loudly
inform the user that this is a terrible idea (but let them continue if
they insist). However, looking at the "oneiric.tar.gz" tarbomb that they
ship, I'm scared, because there are things named "demoted.cfg.hardy" and
"prerequists-sources.dapper.list", so I don't think I want to touch that
code.
--
Ticket URL: <http://athena10.mit.edu/trac/ticket/731#comment:5>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
