From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 4/4] Add all new packages (util-macros, libpciaccess, libyajl) to make.sh
Date: Tue, 29 Mar 2016 14:20:31 +0100 [thread overview]
Message-ID: <1459257631.30749.185.camel@ipfire.org> (raw)
In-Reply-To: <1458980010.2015.2@mail01.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Okay, I will wait for the updated patchset.
Will you send a patch for dmidecode in a different commit? I didn't quite get
what the problem is with this.
Best,
-Michael
On Sat, 2016-03-26 at 09:13 +0100, Jonatan Schlag wrote:
> Hi,
> util-macros will not build not spice-protocol python-pyparsing and python-
> six.
> Sorry, I do not notice that this was the wrong thread.
>
> Regards Jonatan
>
> Am Sa, 26. Mär, 2016 um 9:11 schrieb Jonatan Schlag <jonatan.schlag(a)ipfire.org
> >:
> > 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:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458980010.2015.2@mail01.ipfire.org>
2016-03-29 13:20 ` Michael Tremer [this message]
2016-03-29 19:52 Libvirt hard dependencies [2] Jonatan Schlag
2016-03-29 19:52 ` [PATCH 4/4] Add all new packages (util-macros, libpciaccess, libyajl) to make.sh Jonatan Schlag
-- strict thread matches above, loose matches on Subject: below --
2016-03-25 17:10 Libvirt dependencies Jonatan Schlag
2016-03-25 17:11 ` [PATCH 4/4] Add all new packages (util-macros, libpciaccess, libyajl) to make.sh 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=1459257631.30749.185.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