From: chris <chris@bumblehead.com>
To: zimon.toutoune@gmail.com
Cc: guix-devel@gnu.org, chris@bumblehead.com
Subject: Re: Reducing "You found a bug" reports
Date: Tue, 23 Jul 2024 13:45:10 -0700 [thread overview]
Message-ID: <ZqAWVriKcpq_k3yY@lenovo-21bx> (raw)
Politely, my relatively-new-user observations about `guix pull` and home/system reconfigure commands,
1. The commands, in my experience, always fail with network troubles, and the commands must be re-issued multiple times for
things to complete. Other internet-requesting utilities such as wget, curl, yt-dlp, pacman, apk and mpv do not have these
issues,
2. The commands, based on shell output, appear to download the same versions of the same packages multiple times,
3. The commands, based on shell output, appear to request the same substitute services over and again multiple times in a row
and they appear to do so at multiple different times within the same process. Perhaps the output messages lack details to inform the user, but to the user these appear as un-necessary repetition,
4. The commands usually print correct localised output in the shell process, but less frequently, question marks are printed
instead of text, such as like this '????'
For a new user, the guix experience would be more convincing if the above issues were not present.
next reply other threads:[~2024-07-26 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 20:45 chris [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-09 3:04 Reducing "You found a bug" reports Ian Eure
2024-06-17 12:59 ` Ludovic Courtès
2024-06-17 16:09 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-17 20:40 ` Ricardo Wurmus
2024-07-22 20:48 ` Attila Lendvai
2024-07-17 18:24 ` Simon Tournier
2024-07-21 13:16 ` Ludovic Courtès
2024-07-22 11:30 ` Simon Tournier
2024-07-22 17:43 ` Suhail Singh
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=ZqAWVriKcpq_k3yY@lenovo-21bx \
--to=chris@bumblehead.com \
--cc=877cddhdeo.fsf@gmail.com \
--cc=guix-devel@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).