unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: contact@hubert-lombard.website
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix system reconfigure doesn't work, guix system: error: python-pep8
Date: Sun, 24 Nov 2019 08:49:34 +0000	[thread overview]
Message-ID: <d742bad3b68a4dd66da4d8d04fe093b7@hubert-lombard.website> (raw)
In-Reply-To: <87blt21p3q.fsf@gmail.com>

Le 2019-11-23 17:26, Oleg Pykhalov a écrit :
> Hi,
> 
> contact@hubert-lombard.website writes:
> 
>> I have tried to launch again some guix pull, guix package -u but
>> whithout success...
> 
> Try ‘hash guix’ command after ‘guix pull’.  Also post a ‘guix describe’
> output here, please.

Hi Oleg ;-)

Thank you, it has worked ! When I launched $ guix describe the 
description was:

$ guix describe
Génération 39	23 nov. 2019 21:44:07	(actuelle)
   guix e8f8637
     URL du dépôt : https://git.savannah.gnu.org/git/guix.git
     branche: master
     commit : e8f863704549445aeace0226bd0028e15d0eec5b

Today, it's exactly the same description. I'm running Linux gnu 
5.3.12-gnu :-)

After guix pull, the guix hash command has apparently been successfully 
launched (no error message).

Then, when thinking to your suggestion to guix describe, I decided to '$ 
sudo guix system reconfigure /etc/config.scm' instead of '# guix system 
reconfigure /etc/config.scm' (... which was not working) (Even after a 
'$ guix hash') And it seems to work now...

Maybe, it was not a good practice to launch the reconfiguration always 
under the root account. It was my case and I'll consider the sudo option 
now.

Thanks again for your answer, which was concise and inspiring.

o/

Hubert

      reply	other threads:[~2019-11-24  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 10:59 guix system reconfigure doesn't work, guix system: error: python-pep8 contact
2019-11-23 17:26 ` Oleg Pykhalov
2019-11-24  8:49   ` contact [this message]

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=d742bad3b68a4dd66da4d8d04fe093b7@hubert-lombard.website \
    --to=contact@hubert-lombard.website \
    --cc=go.wigust@gmail.com \
    --cc=help-guix@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.
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).