From: Trevor Woerner <twoerner@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: yocto@yoctoproject.org
Subject: Re: ipk zImage in master-next
Date: Mon, 10 Aug 2015 09:49:47 -0400 [thread overview]
Message-ID: <55C8ABFB.3050802@gmail.com> (raw)
In-Reply-To: <20150809100724.GA24792@bang.betafive.co.uk>
On 08/09/15 06:07, Paul Barker wrote:
> On Fri, Aug 07, 2015 at 09:19:45AM -0400, Trevor Woerner wrote:
>> When packaging a zImage kernel for IPK in master-next the following
>> error shows up:
>>
>> | kernel-image-zImage-4.1.2-fslc+g95d9e15
>> | *** Error: Package name contains illegal characters, (other than
>> [a-z0-9.+-])
>>
>> It looks like the newer kernel.bbclass is much more sophisticated about
>> generating package names than before.
>>
>> Has anyone else seen this? Is there a simple way of saying "the type is
>> zimage where packaging for ipk is concerned but zImage otherwise"?
>>
>> Best regards,
>> Trevor
>
> I believe this check is present in opkg-build just to ensure compatibility with
> the Debian Policy Manual. I don't remember this being an actual restriction of
> opkg.
>
> You could try patching the opkg-build script (in opkg-utils) to remove this
> check and see if opkg is happy to install the resulting package.
Yes, this works. Removing the check from opkg-build causes my build to
succeed, and the resulting image boots with this kernel (meaning opkg is
happy to install the package into the image).
Normally this is the part where I'd ask if you want me to send a patch,
but if that check is there for a reason, simply removing it isn't a
proper solution.
Thoughts?
Best regards,
Trevor
next prev parent reply other threads:[~2015-08-10 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 13:19 ipk zImage in master-next Trevor Woerner
2015-08-09 10:07 ` Paul Barker
2015-08-10 13:49 ` Trevor Woerner [this message]
2015-08-12 16:05 ` Alejandro del Castillo
2015-08-14 18:46 ` Paul Barker
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=55C8ABFB.3050802@gmail.com \
--to=twoerner@gmail.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.