unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia@riseup.net>
Cc: 32183-done@debbugs.gnu.org
Subject: bug#32183: New ‘guix pull’ /root/.config/current/bin/guix: Permission denied
Date: Sat, 03 Nov 2018 15:13:30 +0100	[thread overview]
Message-ID: <87efc2p7ud.fsf@gnu.org> (raw)
In-Reply-To: <3a0b6575-0def-bd64-b725-01190797f794@riseup.net> (swedebugia's message of "Fri, 2 Nov 2018 15:38:09 +0100")

Hello,

swedebugia <swedebugia@riseup.net> skribis:

> This whole update to guix pull was somewhat a breaking change, but
> unfortunately it was very hard to imagine the repercussions (horrible
> bugs) down the line...
>
> Could it have been completely avoided by introducing it as such and
> forced people to reinstall/upgrade by reinstall (overwriting all files
> and invalidating the store etc.)?

Fundamentally, it’s just about moving files from ~/.config/guix to
/var/guix/profiles/per-user/$USER, which I thought was fairly harmless.

Also, the bug was around for a few days.  Those who were away during
those days didn’t notice.

That said, I agree this was poorly handled.  One way to improve it would
be to have several people run the code on their machine before it goes
to master (it’s the kind of code for which we can hardly write unit
tests, and it’s single-use code.)

Thanks,
Ludo’.

  reply	other threads:[~2018-11-03 14:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180717085541.g6nuycopf5kxoin7@thebird.nl>
     [not found] ` <20180717191554.GA23234@jasmine.lan>
2018-07-17 22:28   ` bug#32183: New ‘guix pull’ /root/.config/current/bin/guix: Permission denied Ludovic Courtès
2018-07-23 22:28 ` Pjotr Prins
2018-07-26 13:50   ` Ludovic Courtès
2018-09-02 13:55     ` Ludovic Courtès
2018-09-02 14:28       ` Pjotr Prins
2018-09-02 20:04         ` Ludovic Courtès
2018-09-06 21:10           ` Pjotr Prins
2018-09-09  7:20             ` Pjotr Prins
2018-09-09 14:02               ` Pjotr Prins
2018-09-09 14:44             ` Ludovic Courtès
2018-09-11  9:34               ` Konrad Hinsen
2018-09-11 10:12                 ` Ludovic Courtès
2018-09-11 13:23                   ` Pjotr Prins
2018-09-11 13:58                     ` Pjotr Prins
2018-09-11 14:27                       ` Ludovic Courtès
2018-10-11 16:32                       ` Ludovic Courtès
2018-10-12  6:59                         ` Konrad Hinsen
2018-10-12 12:57                           ` Ludovic Courtès
2018-10-15 11:59                             ` Konrad Hinsen
2018-10-15 19:33                               ` Ludovic Courtès
2018-10-16 10:41                                 ` Konrad Hinsen
2018-10-17  8:44                                   ` Ludovic Courtès
2018-10-17  9:17                                     ` Konrad Hinsen
2018-10-17 23:06                                       ` Ludovic Courtès
2018-11-02 14:38                                       ` swedebugia
2018-11-03 14:13                                         ` Ludovic Courtès [this message]
2018-10-14 18:12                         ` Pjotr Prins
2018-09-11 14:26                     ` Ludovic Courtès
2018-09-05 15:27 ` bug#32183: Me too! Konrad Hinsen

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=87efc2p7ud.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32183-done@debbugs.gnu.org \
    --cc=swedebugia@riseup.net \
    /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).