[Top][All Lists]

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

Re: [PATCH hurd 0/6] Add file record locking support

From: Svante Signell
Subject: Re: [PATCH hurd 0/6] Add file record locking support
Date: Fri, 09 Jan 2015 10:54:32 +0100

On Fri, 2015-01-09 at 10:22 +0100, Justus Winter wrote:
> Quoting Svante Signell (2015-01-09 09:06:34)
> > Cloning hurd git from debian
> > git clone git://git.debian.org/git/pkg-hurd/hurd.git
> > shows that no patches are committed to the git tree
> That is unfortunately correct.  The Debian Hurd package is patched
> beyond recognition, to the point that if you build a stock Hurd
> component and install it on your Debian system, the system likely
> breaks.  Help reduce the pain by upstreaming the debian/patches.

Just an observation: Who is in charge of deciding on which patches are
applied upstream? It is very annoying that even Hurd has a lot of Debian
patches not upstreamed. Couldn't at least these (maybe not all) patches
be on an upstream branch and not in a Debian repo?

And I'm not talking about glibc here, there the situation is even worse,
e.g. Debian Hurd patches are not even admitted to be used to make a new
release of Debian glibc until the Debian maintainer decides :( Now
during the freeze nothing happens with glibc, and e.g. the symbol file
update lingers in -ports. Can glibc (upstream and/or Debian) be split in
parts, like common, linux related, hurd related, kfreebsd related, etc,
and making point releases of these separate parts?

Is moving to devuan or joining guix/dmd/Guixotic a better alternative?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]