From: Miguel <rosen644835@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <m.othacehe@gmail.com>,
julien lepiller <roptat@lepiller.eu>
Subject: Re: Update on 1.0.1
Date: Thu, 16 May 2019 14:41:02 +0200 [thread overview]
Message-ID: <20190516144102.1d200186@gmail.com> (raw)
In-Reply-To: <20190516121302.atv7hestqgfv5qqg@pelzflorian.localdomain>
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
next prev parent reply other threads:[~2019-05-16 12:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 15:57 Update on 1.0.1 Ludovic Courtès
2019-05-09 16:35 ` znavko
2019-05-09 17:00 ` Giovanni Biscuolo
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 10:07 ` Giovanni Biscuolo
2019-05-09 17:45 ` Amin Bandali
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 13:16 ` Ludovic Courtès
2019-05-15 13:43 ` Mathieu Othacehe
2019-05-16 11:38 ` Ludovic Courtès
2019-05-16 12:13 ` pelzflorian (Florian Pelz)
2019-05-16 12:41 ` Miguel [this message]
2019-05-16 12:53 ` pelzflorian (Florian Pelz)
2019-05-16 13:02 ` Miguel
2019-05-16 22:41 ` pelzflorian (Florian Pelz)
2019-05-17 9:19 ` Ludovic Courtès
2019-05-17 9:55 ` pelzflorian (Florian Pelz)
2019-05-17 9:16 ` Ludovic Courtès
2019-05-17 13:02 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190516144102.1d200186@gmail.com \
--to=rosen644835@gmail.com \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@gmail.com \
--cc=pelzflorian@pelzflorian.de \
--cc=roptat@lepiller.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).