unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: quiliro@riseup.net
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 37160@debbugs.gnu.org
Subject: bug#37160: guix lint --checkers=refresh fails
Date: Tue, 27 Aug 2019 07:59:02 -0500	[thread overview]
Message-ID: <3689b74456212dacda495f6d549eec3c.squirrel@sm.riseup.net> (raw)
In-Reply-To: <569bd2b3-5e2f-053b-88fa-9ed6112b9e58@web.de>

El Mar, 27 de Agosto de 2019, 7:51 am, Jonathan Brielmaier escribió:
> On 27.08.19 12:29, quiliro@riseup.net wrote:
>>
>>> Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:
>>>
>>>> During testing various guix commands on openSUSE Tumbleweed with the
>>>> openSUSE package, I found a strange error. This happens with guix
>>>> 1.0.1
>>>> and d78bc23411 as openSUSE packages.
>>>
>>>
>>>> Steps to reproduce:
>>>> * Install Tumbleweed
>>>> $ sudo zypper install guix
>>>> $ sudo systemctl start guix-daemon
>>
>> Why don't you 'guix pull' before the next step ?
>
> Because I use an openSUSE packages which gets regulary built from
> current master commit of guix. So I don't need guix pull :)

Oh! Thank you for the information I did not know that was available. It
sounds like a good thing.

I am not sure about this, but (just in case) would you please test guix
pull and then verify if the error comes up again? Then we could compare.

      reply	other threads:[~2019-08-27 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 14:45 bug#37160: guix lint --checkers=refresh fails Jonathan Brielmaier
2019-08-27  9:44 ` Ludovic Courtès
2019-08-27 10:27   ` Jonathan Brielmaier
2019-08-27 22:33     ` Ludovic Courtès
2019-08-28  9:36       ` Jonathan Brielmaier
2019-08-27 10:29   ` quiliro
2019-08-27 12:51     ` Jonathan Brielmaier
2019-08-27 12:59       ` quiliro [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=3689b74456212dacda495f6d549eec3c.squirrel@sm.riseup.net \
    --to=quiliro@riseup.net \
    --cc=37160@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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).