On Tue, Dec 17, 2013 at 10:29:35AM -0800, Russ Allbery wrote:
Adrian Bunk b...@stusta.de writes:
this hits exactly the core of the problem:
The minimum supported Linux kernel version in glibc is currently 2.6.16,
released in 2006. And I'd trust glibc upstreamt that this requirement
Adrian Bunk b...@stusta.de writes:
The holding back upstream packages would only be true for Linux-only
software that additionally chooses to drop the non-kdbus codepaths.
As I already explained, software like glib2.0 and libdbus that supports
non-Linux kernels will anyway have to continue
On Tue, Dec 17, 2013 at 09:38:56PM +0200, Adrian Bunk wrote:
On Tue, Dec 17, 2013 at 10:29:35AM -0800, Russ Allbery wrote:
Adrian Bunk b...@stusta.de writes:
this hits exactly the core of the problem:
The minimum supported Linux kernel version in glibc is currently 2.6.16,
Kurt Roeckx k...@roeckx.be writes:
We release about every 2 years, but the kernel we have in wheezy was
already about 16 months old when wheezy was released. Jessie will
freeze in november 2014, so that the kernel will then be about 3 years
old. I'm going to assume that the release team is
Adrian Bunk b...@stusta.de writes:
this hits exactly the core of the problem:
The minimum supported Linux kernel version in glibc is currently 2.6.16,
released in 2006. And I'd trust glibc upstreamt that this requirement
won't suddenly be bumped to a quite recent version.
Is there any
Hi Russ,
Le mardi 17 décembre 2013 à 12:26 -0800, Russ Allbery a écrit :
Is there actually any implementation other than glib2.0 and libdbus that
would be affected by a switch to kdbus?
This is an interesting question. Josselin, is GNOME (for example) likely
to acquire a hard dependency
On Mon, 16 Dec 2013, Don Armstrong wrote:
From everyone who has responded, it looks like the 19th is the best day.
date -d 'Thu Dec 19 18:00:00 UTC 2013'
As no one has responded to tell me otherwise, I'm rescheduling our next
meeting to:
date -d 'Thu Dec 19 18:00:00 UTC 2013'
I'll update
Adrian == Adrian Bunk b...@stusta.de writes:
Adrian Yes, it is speculation that other new features (or even
Adrian bugfixes) might appear in the kernel and might become
Adrian mandatory in systemd between jessie and jessie+1.
Adrian But that is a risk, and it is a risk that is
On Tue, Dec 17, 2013 at 02:54:50PM -0800, Don Armstrong wrote:
On Mon, 16 Dec 2013, Don Armstrong wrote:
From everyone who has responded, it looks like the 19th is the best day.
date -d 'Thu Dec 19 18:00:00 UTC 2013'
As no one has responded to tell me otherwise, I'm rescheduling our next
Sam Hartman hartm...@debian.org writes:
I'm confused, when I hear you say that this risk is unique to the
systemd option and not shared by other options. I would understand that
statement if we thought we could avoid systemd entirely. It sounds like
we may be able to avoid systemd as pid 1
10 matches
Mail list logo
