From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libtar: add as new package
Date: Wed, 26 Feb 2014 09:41:53 +0100 [thread overview]
Message-ID: <7ea0a51eded8d805debb90beb601796e@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <1393160492-30990-1-git-send-email-post@lespocky.de>
Hei hei,
I had some problems with the get stage and git urls we already discussed
in IRC last week. This still occurs with the current ptxdist 2014.02.0
release, so I describe what I found.
Am 2014-02-23 14:01, schrieb Alexander Dahl:
> Git only I used the ptxdist mechanism for creating a tarball from a git
> clone in get stage.
In this context I noticed a behavior of ptxdist I consider a bug. Let me
describe:
We use collections here. If I mark the libtar package <*> in the config
everything builds fine. If I mark it <m> in the config and [*] in the
collection there's no problem, too. However if I mark this package <m>
in the config but leave it [ ] in the connection a manual call to the
get stage fails:
% ptxdist get libtar
----------------------------
target: libtar-1.2.20.tar.gz
----------------------------
error: empty parameter to 'ptxd_make_get'
make: ***
[/home/adahl/mnt/bagend-isys/Downloads/ptxdist_src_archive/libtar-1.2.20.tar.gz]
Error 1
I didn't notice this behavior with ordinary packages getting their
tarball by HTTP, but this one is different, because it uses git and
builds the tarball from the local mirror.
Maybe anyone has time to look into this. ;-)
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-02-26 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 13:01 Alexander Dahl
2014-02-26 8:41 ` Alexander Dahl [this message]
2014-03-06 17:47 ` Michael Olbrich
2014-03-06 18:14 ` Michael Olbrich
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=7ea0a51eded8d805debb90beb601796e@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox