all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: myglc2 <myglc2@gmail.com>
Cc: 29072@debbugs.gnu.org
Subject: bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found
Date: Wed, 1 Nov 2017 22:44:40 -0400	[thread overview]
Message-ID: <20171102024440.GA17609@jasmine.lan> (raw)
In-Reply-To: <86shdxv1w0.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

On Wed, Nov 01, 2017 at 10:40:47PM -0400, myglc2 wrote:
> On 11/01/2017 at 11:27 Leo Famulari writes:
> 
> > On Wed, Nov 01, 2017 at 10:40:28AM -0400, myglc2 wrote:
> >> Binary file ./gnu/packages/qemu.go matches		 
> >
> > Try deleting this compiled qemu.go and then try again.
> 
> Thank you Leo.
> 
> I deleted ./gnu/packages/qemu.go and re-ran make.
> 
> Make failed to regenerate ./gnu/packages/qemu.go
> 
> So now I am really confused.

The 'gnu/packages/qemu.scm' file was removed from Guix in July 2017,
with commit 59132b800093e486e4d81aed6b837e9ac76aa86c. The QEMU packages
were moved into 'gnu/packages/virtualization.scm'.

I'm not an Autotools expert, but in cases like this I usually try `make
clean && ./configure --localstatedir=/var && make`. Did you try
something like that yet?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-11-02  2:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 20:34 bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found myglc2
2017-10-31  0:31 ` Leo Famulari
2017-11-01 14:40   ` myglc2
2017-11-01 15:27     ` Leo Famulari
2017-11-02  2:40       ` myglc2
2017-11-02  2:44         ` Leo Famulari [this message]
2017-11-04 23:50           ` myglc2
2017-11-05 17:46             ` Efraim Flashner
2017-11-06  1:15               ` myglc2
2017-11-06 20:12 ` bug#29072: The usability of Guix configurations myglc2

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=20171102024440.GA17609@jasmine.lan \
    --to=leo@famulari.name \
    --cc=29072@debbugs.gnu.org \
    --cc=myglc2@gmail.com \
    /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.