unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Adam Kandur <rndd@tuta.io>, help-guix <help-guix@gnu.org>
Subject: Re: problem with common lisp
Date: Thu, 22 Oct 2020 00:51:17 +0200	[thread overview]
Message-ID: <CAJ3okZ2COk+afAepsThPb862Bu+6=SeBNvrDyLUXBGG=4gsa+A@mail.gmail.com> (raw)
In-Reply-To: <MKC8lw5--3-2@tuta.io>

Please keep help-guix CC. :-)

On Wed, 21 Oct 2020 at 23:53, Adam Kandur <rndd@tuta.io> wrote:

> hi, i mean that my packages for common lisp are same as one week ago when everything worked. also i had same issues with packages from guix channel.
> don't know about guix-deploy

I understand.

First, since the package you are building is yours, more information
is required to be able to find what is wrong.  Idem about your
channel.


The questions in my previous email are:

 1. could you provide the last version of Guix where it "worked"?
 2. could you provide the current version of Guix where it is "broken"?

The #1 means that you have to:

  a) "guix pull -l | grep guix".  This will display all the previous
versions of Guix you had (hoping that you have not deleted by running
"guix gc" with some well-chosen options).
From these versions (hashes), you can run:

   guix time-machine --commit=<hash> -- build -L paht/to/your/local/pkg sbcl-foo

and see which worked and which not.  The easiest is to go
anti-chronological (start by your current Guix version and go
backward).

  b) "guix describe" and probably attach the recipe of your broken
package.  For example it seems that one of your package is named
"sbcl-deploy" since you have one item in the store named
"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497"
and this package is not in "master", AFAICT.


All the best,
simon


  parent reply	other threads:[~2020-10-21 22:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 20:31 problem with common lisp Adam Kandur via
2020-10-21 21:44 ` zimoun
     [not found]   ` <MKC8lw5--3-2@tuta.io>
2020-10-21 22:51     ` zimoun [this message]
2020-10-24 15:59       ` Adam Kandur via
2020-10-24 16:35         ` Guillaume Le Vaillant
2020-10-24 16:43           ` Adam Kandur via
2020-10-24 17:02             ` Guillaume Le Vaillant
2020-10-22  8:27 ` Guillaume Le Vaillant
     [not found]   ` <MKFC0qb----2@tuta.io>
2020-10-22 12:28     ` Guillaume Le Vaillant

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='CAJ3okZ2COk+afAepsThPb862Bu+6=SeBNvrDyLUXBGG=4gsa+A@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rndd@tuta.io \
    /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).