On Sep 26, 2006, at 11:08 AM, John H. Robinson, IV wrote:
I have taken a copy of the currently installed mailman and placed
it into
~root. I want to upgrade our mailman to the most recently released
version that Debian provides, test it, then go yell at people if it
fals
my checks.
Am I reading the system wrong? It appears that mailman-2.1.5-8sarge2
is what is already installed, and that's the version that you placed
in ~root. Also, p.d.o seems to think that 2.1.5-8sarge3 is the
current version, which is the version I thought we weren't getting
due to the hold.
And neither 8sarge2 nor 8sarge3 address the security vulnerability
that Neil originally posted about.
If mailman breaks, in theory I could re-install the version that is
currently installed and everything will Just Work. This is the same
theory that states that everything will Just Work right after the
upgrade, so no downgrade will be required. Comforting theory, no?
I like it. :) If it does not Just Work I will be happy to help
investigate the problem.
I also want to request that anyone that does package management to use
the aptitude interface. It actually works just like apt-get does
(aptitude install <blah>; aptitude remove <blah>) and it willkeep
track
of cruft, and remove things that are not required anymore.
Is it possible to remove the apt-get toolset so as to force us to use
aptitude? My fingers need some help sometimes, and I have no
objection to aptitude.
Any objections to the mailman upgrade?
If my paragraph above about the version does not apply, then go ahead
and apply whatever is current. This will be a good test run for the
*next* upgrade we'll have to do when the actual fix for Neil's
vulnerability finally comes through (what's up Debian Security team???).
--
Joshua Penix http://www.binarytribe.com
Binary Tribe Linux Integration Services & Network Consulting
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
