Update on 1.0.1

Update on 1.0.1

[Ludovic Courtès]

Hello Guix!

It’s been one week since 1.0!  We’ve been partying, but not as long as
we’d like due to a couple of embarrassing bugs, in particular
<https://issues.guix.info/issue/35541>.

I’d like to release within a week because people installing Guix System
from 1.0.0 have just too many issues.

Here are the remaining blockers as far as I’m concerned:

  • Release the Shepherd 0.6.1 in a day or two, which will fix
    <https://issues.guix.info/issue/35550>.

  • Integration the Russian translation of the manual.

  • Maybe do another round via the TP since there are a few new strings
    in the installer.  Julien?

  • Fix <https://issues.guix.info/issue/35554>.

Any other really important bit people would like to address?

Thanks,
Ludo’.

Re: Update on 1.0.1

[znavko]

Sorry for this, but "Graphical Installation" people can understand as graphical mode, but actually it is console mode with menus. It is kind of non-sense.

May 9, 2019 3:58 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:

> Hello Guix!
> 
> It’s been one week since 1.0! We’ve been partying, but not as long as
> we’d like due to a couple of embarrassing bugs, in particular
> <https://issues.guix.info/issue/35541>.
> 
> I’d like to release within a week because people installing Guix System
> from 1.0.0 have just too many issues.
> 
> Here are the remaining blockers as far as I’m concerned:
> 
> • Release the Shepherd 0.6.1 in a day or two, which will fix
> <https://issues.guix.info/issue/35550>.
> 
> • Integration the Russian translation of the manual.
> 
> • Maybe do another round via the TP since there are a few new strings
> in the installer. Julien?
> 
> • Fix <https://issues.guix.info/issue/35554>.
> 
> Any other really important bit people would like to address?
> 
> Thanks,
> Ludo’.

Re: Update on 1.0.1

[Giovanni Biscuolo]

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

[...]

> Any other really important bit people would like to address?

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35655
(Installer: mount error using btrfs on already formatted partition)

there are some others I'm testing (e.g. no terminal emulation program
when installing i3 only) and hope to report soon


Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

Re: Update on 1.0.1

[Ludovic Courtès]

Giovanni Biscuolo <g@xelera.eu> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>> Any other really important bit people would like to address?
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35655
> (Installer: mount error using btrfs on already formatted partition)

Looks like this one should be fixed!  If you want, you’re welcome to
build the image and give it a try:

  https://www.gnu.org/software/guix/manual/en/html_node/Building-the-Installation-Image.html

Thanks,
Ludo’.

Re: Update on 1.0.1

[Giovanni Biscuolo]

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

Hi Ludovic,

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

> Giovanni Biscuolo <g@xelera.eu> skribis:

[...]

>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35655
>> (Installer: mount error using btrfs on already formatted partition)
>
> Looks like this one should be fixed!  If you want, you’re welcome to
> build the image and give it a try:
>
>   https://www.gnu.org/software/guix/manual/en/html_node/Building-the-Installation-Image.html

yes! I'm building an updated image and report on this particular bug
testing in the above bug report, OK?

Thanks! Gio'

P.S.: to be able to easily rebuild a (possibly customized) install image
is awesome: thanks Guix!

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

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

Re: Update on 1.0.1

[Amin Bandali]

Hi Ludo’,

> Any other really important bit people would like to address?

Not critical, but it would be nice to update guix-install.sh to mention
“ci.guix.gnu.org” instead of “ci.guix.info” for clarity, similar to this
previous commit of yours [0] from a while back.

[0]: https://git.savannah.gnu.org/cgit/guix.git/commit/etc/guix-install.sh?id=4a0b87f0ec5b6c2dcf82b372dd20ca7ea6acdd9c

Re: Update on 1.0.1

[Ludovic Courtès]

Hi Amin,

Amin Bandali <bandali@gnu.org> skribis:

> Not critical, but it would be nice to update guix-install.sh to mention
> “ci.guix.gnu.org” instead of “ci.guix.info” for clarity, similar to this
> previous commit of yours [0] from a while back.

Ricardo fixed it recently, thanks!

Ludo’.

Re: Update on 1.0.1

[Ludovic Courtès]

Hello Guix!

AFAICS the main installation-related issues have now been fixed.  Please
build an ISO image of the installer and give it a try in a VM or on the
bare metal!

  https://www.gnu.org/software/guix/manual/en/html_node/Building-the-Installation-Image.html

To try install from the ISO image in a VM, you can do:

  qemu-img create -f qcow2 /tmp/t.img 3G
  OPTS="-m 512 -net user -hda /tmp/t.img -bios $(guix build ovmf)/share/firmware/ovmf_x64.bin"
  qemu-system-x86_64 -enable-kvm -net user -net nic,model=virtio  \
     $OPTS -cdrom /gnu/store/…-image.iso -boot d

(‘-bios’ is for an UEFI install; you can omit it.)

There are 2 remaining issues in the installer that would be nice to fix:

  1. Bug with the WiFi selection dialog boxes:
     <https://issues.guix.gnu.org/issue/35620>.  Ideas, Mathieu?

  2. Keymap file issue when restarting(?) the installer:
     <https://issues.guix.gnu.org/issue/35690>,
     <https://issues.guix.gnu.org/issue/35543>.

#1 may have a simple fix.  #2 less so.  WDYT, Mathieu?

Either way, we should release in the coming days, so if we cannot
address them real soon, I’d argue that we should go ahead, so that
people get all the other installer fixes we’ve worked on.

Thoughts?

Bonus question for Julien: should we do another round of translations
for the bits that have changed here and there in the manual?

Thanks,
Ludo’.

Re: Update on 1.0.1

[Mathieu Othacehe]

Hey Ludo,

> #1 may have a simple fix.  #2 less so.  WDYT, Mathieu?

#1 may have a simple fix but it would require to have the output of
"connmanctl services" (as you requested) to better understand why the
name is #f. Plus I cannot find a way to create a network with an empty
SSID.

So we could change the regex as you suggested but without any guarantee.

#2 is much more annoying and hard to fix. As discussed previously, we
shall force a reboot on installer failure, but we have to do it in a
way that allows the user to report the backtrace.

So I think we should proceed and fix those issues later. Sorry I don't
have anything better to propose :(

Thanks,

Mathieu
 

Re: Update on 1.0.1

[Ludovic Courtès]

Hi Mathieu,

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

>> #1 may have a simple fix.  #2 less so.  WDYT, Mathieu?
>
> #1 may have a simple fix but it would require to have the output of
> "connmanctl services" (as you requested) to better understand why the
> name is #f. Plus I cannot find a way to create a network with an empty
> SSID.
>
> So we could change the regex as you suggested but without any guarantee.

Yeah.

> #2 is much more annoying and hard to fix. As discussed previously, we
> shall force a reboot on installer failure, but we have to do it in a
> way that allows the user to report the backtrace.

True.

> So I think we should proceed and fix those issues later. Sorry I don't
> have anything better to propose :(

Sounds like a good plan to me!  (And no need to be sorry! :-))

I’ll create a ‘version-1.0.1’ branch with the aim of releasing the whole
thing maybe tomorrow or at least by Tuesday.

Thanks for your feedback,
Ludo’.

Re: Update on 1.0.1

[pelzflorian (Florian Pelz)]

On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
> I’ll create a ‘version-1.0.1’ branch with the aim of releasing the whole
> thing maybe tomorrow or at least by Tuesday.
> 

If this does not go through the TP, can we send a download link for a
newer PO file adapted to current doc/guix.texi?

Also it would be good if you could make sure
http://guix.info/manual/en/html_node/Binary-Installation.html#Binary-Installation
will mention Guix version 1.0.1 instead of telling users to download
version UNKNOWN, but maybe this only happened because of the 1.0.0 %base-packages
warning added to the manual.

Regards,
Florian

Re: Update on 1.0.1

[Miguel]

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>:
> On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
> > I’ll create a ‘version-1.0.1’ branch with the aim of releasing the
> > whole thing maybe tomorrow or at least by Tuesday.
> >   
> 
> If this does not go through the TP, can we send a download link for a
> newer PO file adapted to current doc/guix.texi?

I agree that it should go through TP[1], nonetheless there is a way to
generate the pot file to merge it and get an updated po file.  From a
fresh checkout of the git tree you only have to follow these steps:

$ guix environment guix
[env]$ ./bootstrap
[env]$ ./configure
[env]$ make doc-pot-update
[env]$ msgmerge /path/to/old/de.po po/doc/guix-manual.pot > /new/de.po

And that /new/de.po file will contain the updated messages for the last
version of the manual.

> Also it would be good if you could make sure
> http://guix.info/manual/en/html_node/Binary-Installation.html#Binary-Installation
> will mention Guix version 1.0.1 instead of telling users to download
> version UNKNOWN, but maybe this only happened because of the 1.0.0
> %base-packages warning added to the manual.

This link, the official one I guess,
https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#Binary-Installation
contains the correct version.  Is the manual published in guix.info
generated automatically?  Maybe it is something related with the build
process...

Happy hacking!
Miguel

[1] Probably GNU's ftp could be used for that too, as a -pre release.
AFAIK, older pre-releases can be removed if the folder grows up too
quickly:
https://www.gnu.org/prep/maintain/html_node/FTP-Upload-Standalone-Directives.html

Re: Update on 1.0.1

[pelzflorian (Florian Pelz)]

On Thu, May 16, 2019 at 02:41:02PM +0200, Miguel wrote:
> Hi,
> 
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>:
> > On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
> > > I’ll create a ‘version-1.0.1’ branch with the aim of releasing the
> > > whole thing maybe tomorrow or at least by Tuesday.
> > >   
> > 
> > If this does not go through the TP, can we send a download link for a
> > newer PO file adapted to current doc/guix.texi?
> 
> I agree that it should go through TP[1], nonetheless there is a way to
> generate the pot file to merge it and get an updated po file.  From a
> fresh checkout of the git tree you only have to follow these steps:
> 
> $ guix environment guix
> [env]$ ./bootstrap
> [env]$ ./configure
> [env]$ make doc-pot-update
> [env]$ msgmerge /path/to/old/de.po po/doc/guix-manual.pot > /new/de.po
> 

Thank you for explaining.

I prefer doing `msgmerge --previous --nowrap /path/to/old/de.po
po/doc/guix-manual.pot > /new/de.po` to get the old fuzzy messages and
all messages on a single line.

Regards,
Florian

Re: Update on 1.0.1

[Miguel]

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>:
> Thank you for explaining.

You're welcome. :)

> I prefer doing `msgmerge --previous --nowrap /path/to/old/de.po
> po/doc/guix-manual.pot > /new/de.po` to get the old fuzzy messages and
> all messages on a single line.

I disagree with TP's --nowrap policy for my local copies.  I have them
in a git repository, and it is easier to check the history when the
lines fit in a 80-column page.  The --previous option is quite
important though, I should have included that one.

Best regards,
Miguel

Re: Update on 1.0.1

[pelzflorian (Florian Pelz)]

On Thu, May 16, 2019 at 02:13:02PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
> > I’ll create a ‘version-1.0.1’ branch with the aim of releasing the whole
> > thing maybe tomorrow or at least by Tuesday.
> > 
> 
> If this does not go through the TP, can we send a download link for a
> newer PO file adapted to current doc/guix.texi?
> 

Please include this updated German PO file:
https://pelzflorian.de/guix-manual.de.po

It would be nice if a 1.0.1 POT file were published on the TP even if
it is not in time, so that the TP can again harbor the most current
translations.

Regards,
Florian

Re: Update on 1.0.1

[Ludovic Courtès]

Hi Florian,

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

> Please include this updated German PO file:
> https://pelzflorian.de/guix-manual.de.po

Applied, thank you!

> It would be nice if a 1.0.1 POT file were published on the TP even if
> it is not in time, so that the TP can again harbor the most current
> translations.

Julien, WDYT?  I’d really like to go ahead with the release though.

Note that, at worst, we can update the on-line copy of the manual later
if new translations arrive.

Perhaps in the future we should use a different workflow if the TP
doesn’t work well for us.  Thoughts?

Thanks,
Ludo’.

Re: Update on 1.0.1

[pelzflorian (Florian Pelz)]

On Fri, May 17, 2019 at 11:19:30AM +0200, Ludovic Courtès wrote:
> Hi Florian,
> 
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> 
> > Please include this updated German PO file:
> > https://pelzflorian.de/guix-manual.de.po
> 
> Applied, thank you!
>

:)


> Perhaps in the future we should use a different workflow if the TP
> doesn’t work well for us.  Thoughts?
> 

In GNOME string freezes are introduced to give translators enough
time.  I guess this is not necessary for Guix; by now the only
unstable part of the manual that is noticeable is the list of
languages in which the manual is available, because the Russian
translation appeared just before release.

Regards,
Florian

Re: Update on 1.0.1

[Ludovic Courtès]

Hi Florian,

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

> On Thu, May 16, 2019 at 01:38:39PM +0200, Ludovic Courtès wrote:
>> I’ll create a ‘version-1.0.1’ branch with the aim of releasing the whole
>> thing maybe tomorrow or at least by Tuesday.
>> 
>
> If this does not go through the TP, can we send a download link for a
> newer PO file adapted to current doc/guix.texi?

You can send it right now if you want.  But I think the PO files are
rather up-to-date, no?

> Also it would be good if you could make sure
> http://guix.info/manual/en/html_node/Binary-Installation.html#Binary-Installation
> will mention Guix version 1.0.1 instead of telling users to download
> version UNKNOWN, but maybe this only happened because of the 1.0.0 %base-packages
> warning added to the manual.

guix.info is maintained separately, I guess something went wrong.

I worked on a Guix program to automate the generation of on-line copies
of the manual, so we should be able to avoid such issues in the future.

Thanks,
Ludo’.

Re: Update on 1.0.1

[Ricardo Wurmus]

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

>> Also it would be good if you could make sure
>> http://guix.info/manual/en/html_node/Binary-Installation.html#Binary-Installation
>> will mention Guix version 1.0.1 instead of telling users to download
>> version UNKNOWN, but maybe this only happened because of the 1.0.0 %base-packages
>> warning added to the manual.
>
> guix.info is maintained separately, I guess something went wrong.

Sorry.  I’ll update this after the release of 1.0.1.  Or point it to
gnu.org/s/guix until I get around to fully automating this.

-- 
Ricardo