[7005] in Release_7.7_team
Re: Maverick support
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Wed Oct 13 01:13:35 2010
Date: Wed, 13 Oct 2010 01:13:28 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: release-team@mit.edu, debathena@mit.edu
In-Reply-To: <509E58F2-96E9-4ADF-B1C3-2EB4E4698F90@mit.edu>
Message-ID: <alpine.DEB.1.10.1010130110120.26010@dr-wily.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
I can't reproduce this using a machine installed from the RC CD and
updating it to the final release through Update Manager before running the
installer, nor did I run into this with any of the tests I was doing over
the weekend.
What other modifications to the installer did you make? (I had to add
maverick to a conditional, and enable -proposed support unconditionally.)
How did you install this machine?
If by any change the machine is still on that prompt, can you get me a
dump of the relevant processes and their environment variables (via, e.g.,
xargs -0n1 < /proc/$pid/environ)?
--
Geoffrey Thomas
geofft@mit.edu
On Tue, 12 Oct 2010, Jonathan Reed wrote:
> Doing a test install on Maverick today (using the installer from
> r24891), I selected "workstation", but was prompted (by debconf) for the
> default Kerberos realm. I'm not sure why I saw this prompt, but I don't
> think I should have.
>
> -Jon
>
> On Oct 11, 2010, at 11:19 PM, Geoffrey Thomas wrote:
>
>> 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
>
>
