From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: filename restrictions for packaged staging
Date: Sun, 04 Sep 2011 15:01:06 +0200 [thread overview]
Message-ID: <4E637692.2080402@vollmann.ch> (raw)
Some of my recipes fail with
ERROR: Function 'staging_packager' failed (see /dev/null for further
information)
Unfortunately /dev/null didn't give much information ;-(
But eventually (with -vvvvv -D -D -D -D) I got a real error message:
*** Error: Package name contains illegal characters, (other than
[a-z0-9.+-])
While the '' between 'name' and 'contains' isn't of much help
either (it's a bug in stage-manager-ipkg-build, I'll file a patch
for that later), it turned out that my machine name contained
upper case letters, which stage-manager-ipkg-build doesn't like.
Now without packaged staging everything runs fine, i.e. packages
in deploy are created with those upper case letters in it.
So is there a reason why packaged staging is more picky about
filenames than normal opkg packaging?
Detlef
reply other threads:[~2011-09-04 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E637692.2080402@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.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