‘core-updates’ merged!

‘core-updates’ merged!

[Ludovic Courtès]

Hi!

At last ‘core-updates’ is merged!

This brings:

  • Security fixes in icu4c (CVE-2014-6585 and CVE-2015-1270.)

  • libc 2.22–make sure to read
    <https://lists.gnu.org/archive/html/guix-devel/2015-09/msg00717.html>
    before you upgrade!

  • New ‘install-file’ procedure in (guix build utils); consider using
    it where appropriate.

  • Patched tarballs are produced in a deterministic fashion (file
    ordering and time stamps.)

  • The closure size of openssl, curl, libtiff, libx11, libxt has been
    reduced.

  • ‘glib-or-gtk-build-system’ no longer generates icon-theme.cache
    since this is handled during profile generation.  This avoids
    collisions.

  • ‘glibc’ no longer provides bin/bash.

  • Many upgrades.

Ludo’.

‘core-updates’ merged!

[Ludovic Courtès]

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

Hello Guix!

With the last blocker out of the way, I’ve merged the branch!

The (not so new) news:

  • Updates: glibc 2.25, coreutils 8.26, grep 3.0, guile 2.0.14,
    sed 4.4, tzdata 2017a, etc.

  • Packages are built with GCC 5 (was 4.9).

  • Aarch64 is supported!

  • Reproducibility fixes: new ‘reset-gzip-timestamps’ build phase, use
    of Guile 2.0.14 which produces .go files deterministically,
    ‘perl-build-system’ no longer produces ‘perllocal.pod’ files (which
    were not reproducible).

  • No more broken store references in grafted stuff!
    <https://bugs.gnu.org/24703>

  • Only one entry in ‘GIT_EXEC_PATH’ & co.!
    <https://bugs.gnu.org/25422>

  • GNU/Hurd and powerpc-linux-gnu cross-compilation fixes.

… and probably lots of other things long forgotten.

Thanks to everyone who took the time to address the issues in this
branch!

Enjoy!

Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

‘core-updates’ merged!

[Ludovic Courtès]

Hello Guix!

Ludovic Courtès <ludo@gnu.org> skribis:

>> I think <https://issues.guix.gnu.org/issue/37501> should block the
>> merge.  Otherwise many headless systems will occasionally fail to boot.
>>
>> (attended systems too, but at least then you have a good meat-based
>> entropy source at hand)
>
> I think we made good progress there; there are still unknowns, but at
> least we have a workaround (Torvalds’ patch.)
>
> Anything else that should be blocking the merge?

Apparently not, so I went ahead and merged!

Please email bug-guix@gnu.org if you notice anything wrong.

For the record, there are many novelties: glibc 2.29, the default
compiler is now GCC 7 (was 5.5), there’s the new “reduced binary seed
bootstrap”, and tons of other updates and improvements.

Thanks to everyone who’s been working on this!

Ludo’.

Merging ‘core-updates’ real soon

[nathan via Development of GNU Guix and the GNU System distribution.]

Do we have time to merge the vulkan loading fix into core-updates because there isn't a mesa-updates branch for it to go with right now? [bug#71109]

Re: Merging ‘core-updates’ real soon

[John Kehayias]

Hi,

I did see that patch but didn't have a chance to do anything with it. I just started (locally) on updating mesa to the latest version, so I was going to rebase on core-updates (or master if core-updates is merged) and get that ready to go.

So I would say it is up to whoever is leading on core-updates, based on the current substitute coverage. I would guess if it is ready to be merged, a rebuild of ~5k packages due to vulkan would set things back a while. And I can have a mesa-updates branch with that patch building everything soon after.

Apologies for the delay! I was away for a bit but getting back to it now. I better make a formal mesa/graphics team and get some others too.

John

On Thu, Aug 22, 2024 at 07:12 PM, nathan via \"Development of GNU Guix and the GNU System distribution.\" wrote:

> Do we have time to merge the vulkan loading fix into core-updates
> because there isn't a mesa-updates branch for it to go with right now?
> [bug#71109]

Re: Merging ‘core-updates’ real soon

[Ludovic Courtès]

Hi,

John Kehayias <john.kehayias@protonmail.com> skribis:

> I did see that patch but didn't have a chance to do anything with it. I just started (locally) on updating mesa to the latest version, so I was going to rebase on core-updates (or master if core-updates is merged) and get that ready to go.
>
> So I would say it is up to whoever is leading on core-updates, based on the current substitute coverage. I would guess if it is ready to be merged, a rebuild of ~5k packages due to vulkan would set things back a while. And I can have a mesa-updates branch with that patch building everything soon after.

A dedicated branch right after ‘core-updates’ is merged sounds like the
way forward to me.

Thanks,
Ludo’.

Re: Merging ‘core-updates’ real soon

[Ludovic Courtès]

Hello Guix!

I rebased ‘core-updates’ on ‘master’ hours ago; so far, so good, though
there are a few new build failures:

  https://ci.guix.gnu.org/eval/1586727?status=newly-failed

Nothing too bad, except for icedove:

  https://ci.guix.gnu.org/build/5510567/details

and perf:

  https://ci.guix.gnu.org/build/5509604/details

Prior to that, I applied the ffmpeg i686 fix and libcamera aarch64 fix
that others provided:

  https://ci.guix.gnu.org/eval/1586636?status=succeeded

If there are no objections, I’d like us to go ahead and rebase/merge
‘core-updates’ tomorrow, Friday 30th, after adding an entry in
‘etc/news.scm’ (I can do that but I won’t mind if somebody else does; we
can coordinate on IRC and/or here.)

Thoughts?

Ludo’.

Re: Merging ‘core-updates’ real soon

[Ludovic Courtès]

Ludovic Courtès <ludo@gnu.org> skribis:

> If there are no objections, I’d like us to go ahead and rebase/merge
> ‘core-updates’ tomorrow, Friday 30th, after adding an entry in
> ‘etc/news.scm’ (I can do that but I won’t mind if somebody else does; we
> can coordinate on IRC and/or here.)

Here’s a proposed news entry:

 (entry (commit "XXX")
        (title
         (en "Core packages updated"))
        (body
         (en "Core packages have been updated, in particular those that
are used to build every other package in the distribution.  Noteworthy
upgrades include:

@itemize
@item @code{glibc} 2.39 (was 2.35);
@item @code{gcc} 11.4.0 as the default compiler (was 11.3.0);
@item @code{binutils} 2.41 (was 2.38);
@item @code{make} 4.4.1 (was 4.3);
@item TeX@tie{}Live 2024.2 (was 20230313);
@end itemize

Additional improvements were made to the build system and related
packages and tools:

@itemize
@item
the @code{glibc} package now includes the @code{C.UTF-8} locale,
suitable for use when a UTF-8-capable is necessary regardless of any
language or regional convention;
@item
origins that include patches are now repacked with zstd instead of xz,
which uses less CPU power and memory, both when compressing and when
decompressing;
@item
@code{copy-recursively} has a new @code{#:select?} parameter.
@end itemize

If you encounter any problem, please check
@url{https://issues.guix.gnu.org} for existing reports and resolutions;
email @email{bug-guix@@gnu.org} to report new bugs.")))

Did I forget anything important here?

If not, translations welcome!

Ludo’.

Re: Merging ‘core-updates’ real soon

[Kaelyn]

On Thursday, August 29th, 2024 at 12:53 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> 
> 
> Ludovic Courtès ludo@gnu.org skribis:
> 
> > If there are no objections, I’d like us to go ahead and rebase/merge
> > ‘core-updates’ tomorrow, Friday 30th, after adding an entry in
> > ‘etc/news.scm’ (I can do that but I won’t mind if somebody else does; we
> > can coordinate on IRC and/or here.)
> 
> 
> Here’s a proposed news entry:
> 
> (entry (commit "XXX")
> (title
> (en "Core packages updated"))
> (body
> (en "Core packages have been updated, in particular those that
> are used to build every other package in the distribution. Noteworthy
> upgrades include:
> 
> @itemize
> @item @code{glibc} 2.39 (was 2.35);
> @item @code{gcc} 11.4.0 as the default compiler (was 11.3.0);
> @item @code{binutils} 2.41 (was 2.38);
> @item @code{make} 4.4.1 (was 4.3);
> @item TeX@tie{}Live 2024.2 (was 20230313);
> @end itemize
> 
> Additional improvements were made to the build system and related
> packages and tools:
> 
> @itemize
> @item
> the @code{glibc} package now includes the @code{C.UTF-8} locale,
> suitable for use when a UTF-8-capable is necessary regardless of any

Overall the news entry looks good to me. However, you have a missing word on the above line--it reads "when a UTF-8-capable is necessary", and I believe it should read "when a UTF-8-capable locale is necessary".

Cheers,
Kaelyn

> language or regional convention;
> @item
> origins that include patches are now repacked with zstd instead of xz,
> which uses less CPU power and memory, both when compressing and when
> decompressing;
> @item
> @code{copy-recursively} has a new @code{#:select?} parameter.
> @end itemize
> 
> If you encounter any problem, please check
> @url{https://issues.guix.gnu.org} for existing reports and resolutions;
> email @email{bug-guix@@gnu.org} to report new bugs.")))
> 
> Did I forget anything important here?
> 
> If not, translations welcome!
> 
> Ludo’.

Re: Merging ‘core-updates’ real soon

[Nicolas Goaziou via Development of GNU Guix and the GNU System distribution.]

Hello,

Ludovic Courtès <ludo@gnu.org> writes:

> @item TeX@tie{}Live 2024.2 (was 20230313);
> @end itemize

You may want to mention that the versioning scheme for TeX Live has
changed and, unless I'm mistaken, users will need to force upgrade for
these packages. Indeed, I doubt "guix pull && guix upgrade" will update
willingly, e.g., `texlive-context' from version "66594" (old scheme) to
"2024.2" (new scheme). I didn't check, tho.

Also, the news entry might mention that compiling documents with modular
TeX Live is no longer slower than expected.

Regards,
-- 
Nicolas Goaziou

Re: Merging ‘core-updates’ real soon

[Ludovic Courtès]

Hello!

Here’s the updated news entry based on everyone’s feedback:

 (entry (commit "XXX")
        (title
         (en "Core packages updated"))
        (body
         (en "Core packages have been updated, in particular those that
are used to build every other package in the distribution.  Noteworthy
upgrades include:

@itemize
@item @code{glibc} 2.39 (was 2.35);
@item @code{gcc} 11.4.0 as the default compiler (was 11.3.0);
@item @code{binutils} 2.41 (was 2.38);
@item @code{make} 4.4.1 (was 4.3);
@item TeX@tie{}Live 2024.2 (was 20230313; note that due to the new
versioning scheme, @command{guix upgrade} will consider the new packages
as ``older'' than the previous ones so you may need to use
@command{guix install} to upgrade them).
@end itemize

Additional improvements were made to the build system and related
packages and tools:

@itemize
@item
the @code{glibc} package now includes the @code{C.UTF-8} locale,
suitable for use when a UTF-8 locale is necessary regardless of
any language or regional convention;
@item
origins that include patches are now repacked with zstd instead of xz,
which uses less CPU power and memory, both when compressing and when
decompressing;
@item
performance issues with the modular TeX@tie{}Live package set have
been fixed.
@end itemize

If you encounter any problem, please check
@url{https://issues.guix.gnu.org} for existing reports and resolutions;
email @email{bug-guix@@gnu.org} to report new bugs.")))

I can do the French translation but feel free to send other
translations.

Thanks,
Ludo’.

‘core-updates’ merged! 🎉

[Ludovic Courtès]

Hello Guix!

I rebased and applied ‘core-updates’ on top of ‘master’ minutes ago with
commit b8327cb31199fb9f4ebed6c53a59601d41def5a1! 🎉

Consider contributing translations of the news entry added in that
commit.

Let’s congratulate everyone involved in this branch for more than a year (⁈)
for the long, tedious, and hard work!

As always, please report any issue you encounter, and let’s tackle them
together!

Ludo’.

Re: ‘core-updates’ merged! 🎉

[Tomas Volf]

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

Hi!

> Hello Guix!
>
> I rebased and applied ‘core-updates’ on top of ‘master’ minutes ago with
> commit b8327cb31199fb9f4ebed6c53a59601d41def5a1! 🎉
>
> Consider contributing translations of the news entry added in that
> commit.
>
> Let’s congratulate everyone involved in this branch for more than a year (⁈)
> for the long, tedious, and hard work!

I just want to express my thanks to everyone involved.  It is great it
was finally merged and it took lot of work.  So, thanks everyone! :)

>
> As always, please report any issue you encounter, and let’s tackle them
> together!

I am writing this message from a system & home reconfigured after the
merge, so for me (on my fairly boring x86-64 system) everything works
well.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]