all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Dan Partelly <dan_partelly@rdsor.ro>
Cc: guix-devel@gnu.org
Subject: Re: Suboptimal experience
Date: Sun, 17 Jun 2018 17:40:44 +0200	[thread overview]
Message-ID: <20180617173942.4e97e315@lepiller.eu> (raw)
In-Reply-To: <5F881124-7897-40FD-B554-B845CB1200C5@rdsor.ro>

Le Sun, 17 Jun 2018 13:09:54 +0300,
Dan Partelly <dan_partelly@rdsor.ro> a écrit :

> Hello,
> 
> 
> First thanks for the development effort you guys do. Now the issues:
> 
> 1. I managed to install 0.14 to a Virtual box VM. I used bare-bones
> configuration. 2. I tried to get familiar with guix / guixSD a bit, I
> never used it before 3. Within minutes I managed to break the system
> completely , due to my misguided idea to execute a guix pull to
> upgrade the packages to the latest available. This command is a
> liability, while it should 100% safe given how  central is to the OS.
> 4. This resulted into an unusable system , the command “system” for
> guix did not functioned at all after whatever git pull did .  Guix
> reported: 5. attempting to fix the issue by pulling from git branch
> 0.14 where not successful.

Hi Dan,

congrats on installing GuixSD :)

I think you fell in a bug introduced by a recent change in how guix and
guix pull work. You probably need to run guix pull once more to end up
in a usable state. Sorry for the inconvenience :/

You won't need to run guix pull twice after that, there's only one time
where it's needed to transition to the new architecture.

> 
> 
> Now some  points:

For your other points... I can't really elaborate on them. Some of your
points go against our core values (software freedom) so we won't
implement them, but we're free software. We make it easy for you to
adapt guix packages to build your own, or even fork the project
entirely and create another distribution with different goals.

The rest of your points I think are already solved by the new guix pull
that caused the bug you experienced.

I hope I could help you. Don't hesitate to ask more questions or come
back if running guix pull once more didn't work :)

> 
> 
> With thanks

  reply	other threads:[~2018-06-17 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17 10:09 Suboptimal experience Dan Partelly
2018-06-17 15:40 ` Julien Lepiller [this message]
2018-06-17 19:55   ` Dan Partelly
2018-06-17 20:09     ` Julien Lepiller
2018-06-17 20:13       ` Dan Partelly
2018-06-17 20:16         ` Julien Lepiller
2018-06-17 17:31 ` Mark H Weaver
2018-06-17 19:51   ` Dan Partelly
2018-06-18 11:11     ` swedebugia
2018-06-18 15:01       ` Dan Partelly
2018-06-18 15:52         ` Julien Lepiller
2018-06-18 18:08           ` Dan Partelly
2018-06-18 18:29             ` Nils Gillmann

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180617173942.4e97e315@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=dan_partelly@rdsor.ro \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.