Release progress, week 10

Release progress, week 10

[Ludovic Courtès]

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

Hello Guix!

Here’s what may be the last update for the 1.4.0 release.

The second release candidate was released earlier a few days ago:

  https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00145.html

Thanks to everyone who tested and reported back!

There are currently two installer bugs that I think now have a valid fix:

  https://issues.guix.gnu.org/60010
  https://issues.guix.gnu.org/59784

I’m waiting for confirmation from Florian; kudos to Florian for
tirelessly testing the installer over the past few weeks!

Apart from that, there have been only 3 cosmetic commits since RC2.

If everything goes well, I plan to publish the release on Monday, 19th.
Time to get to your instrument for a release song or whatever other
performance you feel like making!  :-)

Ludo’.

Week 9: https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00119.html
Week 8: https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00034.html
Week 7: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00274.html
Week 6: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00161.html
Week 5: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00026.html
Week 4: https://lists.gnu.org/archive/html/guix-devel/2022-11/msg00026.html
Week 3: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00293.html
Week 2: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00210.html
Week 1: https://lists.gnu.org/archive/html/guix-devel/2022-10/msg00137.html

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

cirrus (was Re: Release progress, week 10)

[pelzflorian (Florian Pelz)]

Ludovic Courtès <ludo@gnu.org> writes:
> There are currently two installer bugs that I think now have a valid fix:
>
>   https://issues.guix.gnu.org/60010
>   https://issues.guix.gnu.org/59784

Sadly those are still not completely fixed…

That hold-up aside, maybe could you also tentatively add the cirrus
initrd module to the 1.4.0 installation image?  I suppose it won’t break
anything, but it might help with bugs like
<https://issues.guix.gnu.org/60002>.

Regards,
Florian

Re: cirrus (was Re: Release progress, week 10)

[pelzflorian (Florian Pelz)]

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

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> That hold-up aside, maybe could you also tentatively add the cirrus
> initrd module to the 1.4.0 installation image?  I suppose it won’t break
> anything, but it might help with bugs like
> <https://issues.guix.gnu.org/60002>.

I tested the following chance:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: cirrus.patch --]
[-- Type: text/x-patch, Size: 539 bytes --]

diff --git a/gnu/system/install.scm b/gnu/system/install.scm
index 3dd9e0e87b..dfa6db9408 100644
--- a/gnu/system/install.scm
+++ b/gnu/system/install.scm
@@ -507,6 +507,10 @@ (define installation-os
     ;; Thus, blacklist it.
     (kernel-arguments '("quiet" "modprobe.blacklist=radeon,amdgpu"))
 
+    (initrd-modules (append
+                    (list "cirrus")
+                    %base-initrd-modules))
+
     (file-systems
      ;; Note: the disk image build code overrides this root file system with
      ;; the appropriate one.

[-- Attachment #3: Type: text/plain, Size: 475 bytes --]


This makes the installer work on QEMU with '-vga cirrus'.

It also still works under default QEMU (cirrus isn’t default anymore
since QEMU 2.2 according to the docs).

The installer also still works on my:

* Beebox with Intel

* PC with Nvidia

and thanks to the resolution of the
  https://issues.guix.gnu.org/60010
  it also works on my

* PC with AMD

* laptop with AMD

None is modern hardware, but still, please add cirrus.

Regards,
Florian

Re: cirrus (was Re: Release progress, week 10)

[Ludovic Courtès]

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>> There are currently two installer bugs that I think now have a valid fix:
>>
>>   https://issues.guix.gnu.org/60010
>>   https://issues.guix.gnu.org/59784
>
> Sadly those are still not completely fixed…

Both should be fixed now!

> That hold-up aside, maybe could you also tentatively add the cirrus
> initrd module to the 1.4.0 installation image?  I suppose it won’t break
> anything, but it might help with bugs like
> <https://issues.guix.gnu.org/60002>.

This wasn’t under my radar and I think it’s too late for such a change
now.

But look, we can do 1.4.1 next month if we want it.  There’s a position
for a release management team (2–3 people) coming up BTW, so you can all
prepare your applications.  :-)

Ludo’.

Re: cirrus (was Re: Release progress, week 10)

[pelzflorian (Florian Pelz)]

Ludovic Courtès <ludo@gnu.org> writes:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>> That hold-up aside, maybe could you also tentatively add the cirrus
>> initrd module to the 1.4.0 installation image?  I suppose it won’t break
>> anything, but it might help with bugs like
>> <https://issues.guix.gnu.org/60002>.
>
> This wasn’t under my radar and I think it’s too late for such a change
> now.

OK.


> But look, we can do 1.4.1 next month if we want it.  There’s a position
> for a release management team (2–3 people) coming up BTW, so you can all
> prepare your applications.  :-)

I cannot guarantee being available or a good enough decision maker, but
I’m most grateful to you and all maintainers.

Regards,
Florian

Re: Release progress, week 10

[zimoun]

Hi Ludo,

On Thu, 15 Dec 2022 at 17:38, Ludovic Courtès <ludo@gnu.org> wrote:

> If everything goes well, I plan to publish the release on Monday, 19th.
> Time to get to your instrument for a release song or whatever other
> performance you feel like making!  :-)

It reminds me the announce on hpc.guix.info.  Well, I am not have the
time before Monday to collect the changes.  I can draft on Monday.

The draft of the announce for the Guix website LGTM.  I will try to
write a paragraph about «Supporting long-term reproducibility» (SWH
fallback for channels and Disarchive) on Monday morning.  If you want to
proceed before, go ahead. :-)

I still think that it would be worth to mention the removal of many
Python 2 packages and that the project stops to maintain Python 2
packages.  I know it appears in NEWS but it costs nothing to restate
because many people are not reading all the details of all. :-)


Cheers,
simon

Re: Release progress, week 10

[Ludovic Courtès]

Hi!

zimoun <zimon.toutoune@gmail.com> skribis:

> On Thu, 15 Dec 2022 at 17:38, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> If everything goes well, I plan to publish the release on Monday, 19th.
>> Time to get to your instrument for a release song or whatever other
>> performance you feel like making!  :-)
>
> It reminds me the announce on hpc.guix.info.  Well, I am not have the
> time before Monday to collect the changes.  I can draft on Monday.

Would be great!

> The draft of the announce for the Guix website LGTM.  I will try to
> write a paragraph about «Supporting long-term reproducibility» (SWH
> fallback for channels and Disarchive) on Monday morning.  If you want to
> proceed before, go ahead. :-)

I wrote a couple of paragraphs about this and other things yesterday
(tried to keep it relatively short).  Let me know if you think
anything’s missing.

> I still think that it would be worth to mention the removal of many
> Python 2 packages and that the project stops to maintain Python 2
> packages.  I know it appears in NEWS but it costs nothing to restate
> because many people are not reading all the details of all. :-)

Oh right, I’ll add a few lines.

Thanks!

Ludo’.

Re: Release progress, week 10

[zimoun]

Hi,

On Sun, 18 Dec 2022 at 16:13, Ludovic Courtès <ludo@gnu.org> wrote:

> I wrote a couple of paragraphs about this and other things yesterday
> (tried to keep it relatively short).  Let me know if you think
> anything’s missing.

All appears to me good.  You do not mention that the coverage for
git-fetch is about ~98% and that Disarchive is very important because
the main source of origins is url-fetch, hence the total of 75%.

I would add at the end of the first paragraph something like:

--8<---------------cut here---------------start------------->8---
[...]
Software Heritage as a fallback, with version 1.4.0 **the source code of
Guix channels is automatically fetched from Software Heritage** if its
original URL has become unreachable.  As of the “[Preservation of Guix
Report](https://ngyro.com/pog-reports/latest/)” published in January
2022, more than 98% of the packages directly referring to Git
repositories are now fully archived in Software Heritage.
--8<---------------cut here---------------end--------------->8---


>> I still think that it would be worth to mention the removal of many
>> Python 2 packages and that the project stops to maintain Python 2
>> packages.  I know it appears in NEWS but it costs nothing to restate
>> because many people are not reading all the details of all. :-)
>
> Oh right, I’ll add a few lines.

LGTM.


Cheers,
simon

PS: A side note and it is too late. :-)  This:

  - [“Using TeX and
    LaTeX”](https://guix.gnu.org/manual/en/html_node/Using-TeX-and-LaTeX.html)

appears to me a Cookbook section and not a Manual section.  Well, let
discuss that on January. :-)

Re: Release progress, week 10

[Ludovic Courtès]

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Sun, 18 Dec 2022 at 16:13, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I wrote a couple of paragraphs about this and other things yesterday
>> (tried to keep it relatively short).  Let me know if you think
>> anything’s missing.
>
> All appears to me good.  You do not mention that the coverage for
> git-fetch is about ~98% and that Disarchive is very important because
> the main source of origins is url-fetch, hence the total of 75%.
>
> I would add at the end of the first paragraph something like:
>
> [...]
> Software Heritage as a fallback, with version 1.4.0 **the source code of
> Guix channels is automatically fetched from Software Heritage** if its
> original URL has become unreachable.  As of the “[Preservation of Guix
> Report](https://ngyro.com/pog-reports/latest/)” published in January
> 2022, more than 98% of the packages directly referring to Git
> repositories are now fully archived in Software Heritage.

Sorry this came in too late, but we can have it in the announcement for
hpc.guix.info (tomorrow I guess?).

Thanks,
Ludo’.