[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Please allow util-vserver 0.30.212-1 into etch



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Micah Anderson <micah@riseup.net> writes:
>> Due to changes in the vserver patch necessary for 2.6.19+, changes in
>> the user-space util-vserver package were required. The changes
>> between 0.30.211-6 and 0.30.212-1 are important.

Marc 'HE' Brockschmidt wrote:
> 161 files changed, 5326 insertions(+), 10685 deletions(-)

If I remove all the useless stuff (.svn stuff that crept in, upstream
Changelog which for some reason had a number of changes, autotools
noise, debian patches that have been incorporated into upstream, NOOP
RCS header date changes, fedora yum repo gpg key change (unrelated to
debian) gentoo initscript changes (unrelated to debian), redhat initpost
changes (unrelated to debian), documentation changes
(doc/configuration.html, configuration-xhtml.xsl, configuration.xml),
redhat spec file changes (unrelated to debian) and the THANKS change,
leaves:

58 files changed, 189 insertions(+), 446 deletions(-)

Removing the 20+ trivial fixes of:

- -       WRITE_MSG(2, " --help\" for more information.\n");
+       WRITE_MSG(2, " --help' for more information.\n");

Leaves 40 changes, 169 insertions(+), 426 deletions, not that much when
you consider a new kernel API is supported.

>This is simply not reviewable and we don't have kernels >= 2.6.19 in
>etch, so I'm really not convinced that letting this trought at this
>point of the freeze is a good idea.

The reason for requesting this is to make etch+.5 transition smoother,
and as I understand it, a newer kernel is expected to be introduced in
etch+.5, and anything newer than 2.6.18 will break all vserver support.
Additionally, any user who installs a backported kernel, or a
hand-rolled one, will be unable to use vservers with 0.30.211-6.

Micah
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF6yf+9n4qXRzy1ioRAo3nAKCIIwP0Rnb2Ds+m5UA3isgjCMxuAQCeOkpI
J5Z3C1tHQ3nelrXPv44cFNE=
=nJyM
-----END PGP SIGNATURE-----



Reply to: