From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number.
Date: Tue, 29 Mar 2016 14:17:15 +0100 [thread overview]
Message-ID: <1459257435.30749.184.camel@ipfire.org> (raw)
In-Reply-To: <1458979912.2015.1@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
Hey,
just move the rootfiles from the packages directory to common. That should fix
it.
The rest of this looks good.
Best,
-Michael
On Sat, 2016-03-26 at 09:11 +0100, Jonatan Schlag wrote:
> Hi,
> sadly I have to write that this series is superseded.
> The creation of the packages fails because spice-protocol python-pyparsing and
> python-six are empty.
> Tar do not like to pack empty packages.
>
> Regards Jonatan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-03-29 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458979912.2015.1@mail01.ipfire.org>
2016-03-29 13:17 ` Michael Tremer [this message]
2016-03-29 18:57 Libvirt and spice [3] Jonatan Schlag
2016-03-29 18:57 ` [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number Jonatan Schlag
-- strict thread matches above, loose matches on Subject: below --
2016-03-25 16:03 Libvirt and spice [2] Jonatan Schlag
2016-03-25 16:03 ` [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number Jonatan Schlag
[not found] <1458668167.2019.0@mail01.ipfire.org>
2016-03-22 18:54 ` Matthias Fischer
2016-03-21 18:47 Spice for Libvirt Jonatan Schlag
2016-03-21 18:47 ` [PATCH 7/7] Enable spice support in qemu, add spice as a dependency for qemu and bump qemu version number Jonatan Schlag
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=1459257435.30749.184.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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