Re: [RFC] Kernel version numbering scheme change

On Thu, Oct 16, 2008 at 07:46:02PM +0300, Adrian Bunk wrote:
On Thu, Oct 16, 2008 at 08:17:48AM -0700, Greg KH wrote:
On Thu, Oct 16, 2008 at 03:49:43PM +0300, Adrian Bunk wrote:
...
If a distribution will try to autobuild an urgent OpenSSL security
update for their stable release in a chroot on a machine running
kernel 2009.2.3 they will surely love you for being responsible
for this...

Distros properly patch things and backport "urgent OpenSSL security
updates" to older versions of packages, so they would not run into this
problem.

You didn't get my point.

Let me make an example:

The current Debian release will be supported until one year after the
next release gets released.

Someone from the Debian security team send a fixed package to the
buildds.

The buildds build packages in chroots.

A buildd may run any Debian release.

And it's perfectly normal that a buildd runs a more recent release of
Debian than the one a package gets built for in a chroot.

So you are saying the Debian build system would build a package for an
older release, on a system that is newer, and that build would be
determining things based on the system it is built on, not what it is
being built for?

If so, then something is very broken already in the Debian build system
and I think you have much bigger problems to worry about right now.

For all other "sane" build systems that I know of, you build against the
libraries/kernel/gcc/glibc/etc that you are wanting to support it for,
not against some random-whatever-happened-to-be-installed-on-the-box.

No matter what you claim, you suggest to break currently working setups.

No, you have described a broken setup.

Now for new releases, yes, something might have to be changed, but that
is when a sane distro would move to the newly named kernel, not
affecting any old releases at all.

Hope this helps,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [RFC] Kernel version numbering scheme change
    ... The current Debian release will be supported until one year after the ... The buildds build packages in chroots. ... Debian than the one a package gets built for in a chroot. ...
    (Linux-Kernel)
  • Re: debian-user-digest Digest V2008 #1217
    ... basically what version of debian will suit my setup, foxconn motherboard, ... Any idea why chroot temporarily "can [David Barrett < ... USB Wi-Fi dongles are often ... ItaliaDream ...
    (Debian-User)
  • Re: the best Linux for me
    ... I've ben using debian on my desktop for about 8 years, ... What's Debian's package / distro system called? ... cl-clx-sbcl - An X11 Common Lisp client library for SBCL ... You can also see how out of date my unstable install ...
    (comp.lang.lisp)
  • Re: what version?
    ... > handling of RedHat package management had been jumbled by an architect who ... Debian, Gentoo, etc. ... As I mentioned earlier, Debian-compatible installation media (including ... the stable-branch archive, because he felt it was in particularly good ...
    (comp.os.linux.setup)
  • Re: CLARITY re: challenge: end of life for 6.2 is prematurewithbuggy 6.3
    ... If the new php package works fine on your build box, ... For most of the ports this works, ... Even debian has no plus point there (at least in our environment at ... I've had a disk down of course it was in gmirror and the situation ...
    (freebsd-stable)