mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] image_tgz: Make label optional
Date: Wed, 21 May 2014 17:03:27 +0200	[thread overview]
Message-ID: <843b581c30123e166a3aadbd0bbfcb6e@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20140423065229.GB3804@pengutronix.de>

Hei hei, 

Am 2014-04-23 08:52, schrieb Michael Olbrich:
> On Tue, Apr 22, 2014 at 12:21:59PM -0400, jon@ringle.org wrote:
>> From: Jon Ringle <jringle@gridpoint.com>
>>
>> Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> 
> Thanks, applied with a followup patch. It still looks good here. Can you
> check that I didn't break anything for you?

Breaks here. Introduced after nigration to ptxdist 2014.05.0 is

PTXCONF_IMAGE_TGZ_LABEL="${PTXCONF_PROJECT_VENDOR}-${PTXCONF_PROJECT}${PTXCONF_PROJECT_VERSION}"

${PTXCONF_PROJECT_VENDOR} contains spaces here.

Although in rules/post/image_tgz.make line 16 there are single quotes
around the argument to label, the output of `ptxdist images` is
something like:


Creating root.tgz from working dir with label "foo bar
baz-myproject-2014.03.1"... tar: bar: Cannot stat: No such file or
directory
tar: baz-myproject-2014.03.1: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors


I'm not sure how to fix this, no time anymore today, so I let you know
this way.

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

  parent reply	other threads:[~2014-05-21 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 16:21 jon
2014-04-23  6:52 ` Michael Olbrich
2014-04-23 12:00   ` Jon Ringle
2014-05-21 15:03   ` Alexander Dahl [this message]
2014-05-26  7:13     ` Alexander Dahl
2014-06-02  9:17       ` Michael Olbrich
  -- strict thread matches above, loose matches on Subject: below --
2014-04-17 15:11 jon
2014-04-22 15:58 ` Jon Ringle
2014-04-22 16:08 ` 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=843b581c30123e166a3aadbd0bbfcb6e@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