Hi Sluggers,
A week ago I posted a (cryptic?) email about upgrading one
single package on a Deb/Etch install. I have more info now and can
prolly ask the right question.
Here is what I need to do:
util-vserver 0.30.212 has a serious bug in which the guests can
suddenly start using all available CPU, in the vcontext binary.
util-vserver 0.30.213 (specifically the vcontext programme) fixes
the problem.
How can I install util-vserver 0.30.213 and not disturb
anything else on the system?
Background info:
util-vserver 0.30.213 is classed as unstable. I do not care about
that. I would like to force an install of the "unstable" version
to fix a bug. I was advised by the dev team for the project that
I need 0.30.213
Further question:
In the days before package mgmt, one would download the fix (for vcontext
in thiscase), cobble together related changes (because of version
compatibilities) and test the new version. If that passes muster, install
on production.
How does one manage this process using deb packages (or any package manager
for that matter)? It seems to me that one really needs a parallel test
box on which to install and test the automated upgrades. I say this since
my experience has shown time and time again that unforeseen and unintended
incompatibilities can arise when installing system componentry in an ad hoc
fashion. I presumse this is why deb package mgr maintains its dependency
graph.
More specifically, in the above case of util-vserver, how does one upgrade
just IT and nothing else?
cheers
rickw
--
_________________________________
Rick Welykochy || Praxis Services
Never keep up with the Joneses. Try to drag them down to your level. It's
cheaper.
--Quentin Crisp
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
