From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47297@debbugs.gnu.org
Subject: bug#47297: Release 1.2.1 checklist: eolie (manual example)
Date: Wed, 24 Mar 2021 15:30:41 -0400 [thread overview]
Message-ID: <YFuTYRxoka0CL2i9@jasmine.lan> (raw)
In-Reply-To: <86wntwbczr.fsf@gmail.com>
On Wed, Mar 24, 2021 at 07:52:40PM +0100, zimoun wrote:
> To me they are very important because ’eolie’ is in the manual:
>
> --8<---------------cut here---------------start------------->8---
> guix environment --preserve='^DISPLAY$' --container --network \
> --expose=/etc/machine-id \
> --expose=/etc/ssl/certs/ \
> --share=$HOME/.local/share/eolie/=$HOME/.local/share/eolie/ \
> --ad-hoc eolie nss-certs dbus -- eolie
> --8<---------------cut here---------------end--------------->8---
>
> <https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment>
>
>
> Therefore, from my point of view, we have only 2 options:
>
> 1- change the example in the manual
> 2- fix eolie.
Understood.
> Otherwise, I am not comfortable to release broken examples. Since
> releasing a rolling release is more about advertisement and attract new
> users, having broken examples is something really confusing––not to say
> unacceptable—–for these new users.
I agree.
Can you add these bugs to the checklist?
next prev parent reply other threads:[~2021-03-24 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 17:38 bug#47297: Release 1.2.1 checklist Leo Famulari
2021-03-24 3:11 ` zimoun
2021-03-24 4:06 ` Leo Famulari
2021-03-24 9:20 ` bug#47297: Release 1.2.1 checklist: eolie (manual example) zimoun
2021-03-24 18:16 ` Leo Famulari
2021-03-24 18:52 ` zimoun
2021-03-24 19:30 ` Leo Famulari [this message]
2021-03-24 19:43 ` zimoun
2021-05-17 14:42 ` bug#47297: Release 1.3.0 checklist Leo Famulari
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=YFuTYRxoka0CL2i9@jasmine.lan \
--to=leo@famulari.name \
--cc=47297@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).