(Sorry for replying again, but since my message wasn't reaching to
gnu-devel for others to see, I'm trying this again, this time, hopefully it
should reach others)
Hello Steve,
Yes, you're right about that - I am on the master branch. Should I switch
to a different commit? Maybe the ones listed in
On 2024-04-10 17:17:27 +0200, Ludovic Courtès wrote:
> Yes, we could change the default to #f: it’s equivalent to
> ‘%default-channels’ but wouldn’t cause the undesirable side effect you
> experienced.
>
> Do you want to prepare a patch (or two)? :-)
Well it took me approximately forever to get to
Hi Andreas,
On Wed, May 08 2024, Andreas Enge wrote:
> I am a little bit confused by the suggestion; you mean removing all
> .la files from all packages?
I don't mean to answer for Josselin but at least in Debian, which seems
to be acceptable as a reference from time to time, there has been a
lo
Simon Tournier writes:
> Here or there, we have bugs as:
>
> https://issues.guix.gnu.org/70659
> https://issues.guix.gnu.org/70726
>
> And our answer looks like:
>
> > Additionally, I strongly advise upgrading guix-daemon, as noted in
> the
> > bug report above.
>
> Well,
Hello,
Am Mon, May 06, 2024 at 10:47:13AM +0200 schrieb Josselin Poiret:
> Maxim Cournoyer writes:
> > I don't mind too much; when we re-enable the change we should add a
> > phase to the gnu-build-system automatically deleting/moving the libtool
> > archives. so that we're covered.
>
> I agree,
Hi Ludo,
Ludovic Courtès writes:
> I’m in favor of whatever allows us to move forward more quickly, so
> temporarily stashing away the pkgconf changes sounds good to me.
>
> In that case, when time permits, could you push a ‘core-updates-new’ (?)
> branch, (partially) rebased and without the pkg
