[6996] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Maverick support

daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Mon Oct 11 23:20:04 2010

Date: Mon, 11 Oct 2010 23:19:56 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: release-team@mit.edu
cc: debathena@mit.edu
Message-ID: <alpine.DEB.1.10.1010112306050.22003@dr-wily.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

I intend to move Maverick's packages to production tomorrow morning, 
enable maverick support in the installer shell script, and send mail to 
this effect to debathena-announce and release-announce, assuming I receive 
no reports of issues between now and when I wake up. Liz, Ben, and I have 
all installed Debathena on Maverick and things seem fine.)

We've seen three issues so far:

0) Maverick doesn't come with aptitude to save space on the CD. I added an 
"apt-get install aptitude" in a conditional to the installer. apt-get's 
resolver seems capable of installing Debathena now, but I don't really 
think it's worth switching.

1) There's an upstream bug in Maverick's libc apparently tickled by the 
combination of nss_nonlocal being used and disabled by 
$NSS_NONLOCAL_IGNORE that can cause cvs's postinst to crash when creating 
/srv/cvs. The package manager reattempts the postinst and the installation 
completes fine, but /srv/cvs is not properly created. Since I'm not really 
aware of people using /srv/cvs as opposed to a real repo somewhere else, 
and also since we can't fix this on our end, I'm not considering this a 
blocker. The bug was fixed upstream shortly after the release that Ubuntu 
took for Maverick, and Anders has filed an Ubuntu bug at 
http://bugs.launchpad.net/bugs/658907
Because cvs has not been updated in Ubuntu since Jaunty, this only affects 
new installs.

2) Upstream from now uses the "alternatives" system, so our 
diversion of /usr/bin/from to install the one from mitmailutils may not 
take effect. This only affects upgrades because with new installs, we 
successfully divert the symlink to /etc/alternatives/from. On upgrades, 
that symlink beats our symlink to from.debathena. I've filed a ticket at 
http://debathena.mit.edu/trac/729 but the lack of "from" doesn't 
particularly feel like a release blocker to me.

-- 
Geoffrey Thomas
geofft@mit.edu

home help back first fref pref prev next nref lref last post