GNU bug report logs - #29537
Core updates broken

Previous Next

Package: guix;

Reported by: Gábor Boskovits <boskovits <at> gmail.com>

Date: Sat, 2 Dec 2017 20:14:01 UTC

Severity: normal

Done: Marius Bakke <mbakke <at> fastmail.com>

Bug is archived. No further changes may be made.

Full log


Message #41 received at 29537 <at> debbugs.gnu.org (full text, mbox):

From: Gábor Boskovits <boskovits <at> gmail.com>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: Ricardo Wurmus <rekado <at> elephly.net>, 29537 <at> debbugs.gnu.org
Subject: Re: bug#29537: Core updates broken
Date: Sun, 3 Dec 2017 20:04:27 +0100
[Message part 1 (text/plain, inline)]
I'd go the GUIX_GLIBC_VERSION way.

That one seems the clearest, at least to me...

2017-12-03 19:43 GMT+01:00 Marius Bakke <mbakke <at> fastmail.com>:

> Ricardo Wurmus <rekado <at> elephly.net> writes:
>
> > Marius Bakke <mbakke <at> fastmail.com> writes:
> >
> >> Gábor Boskovits <boskovits <at> gmail.com> writes:
> >>
> >>> It seems, that we have a breakage in current core-updates. m4,
> gettext, and
> >>> at least a few other packages fail to build.
> >>
> >> Hello!
> >>
> >> The problem is that the glibc version string is used a couple of places
> >> to determine where locales are found.
> >>
> >> The attached patch fixes it, though I'm not sure if it's the best
> >> approach.  Thoughts?
> >
> > Thank you.
> >
> > I find it a little ugly to replace the exact version string with only
> > the major+minor version substring.  Why can’t we use the full version
> > string?
>
> I think it's because "glibc-versioned-locpath.patch" uses the libc
> VERSION constant.
>
> Perhaps we could substitute glibcs "version.h", but that might break
> other things.  Or introduce a different variable, say
> GUIX_GLIBC_VERSION, and use that.  WDYT?
>
[Message part 2 (text/html, inline)]

This bug report was last modified 7 years and 230 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.