Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Thilo Cestonaro <thilo@cestona.ro>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Openembedded Core List <openembedded-core@lists.openembedded.org>
Subject: Re: opkg-build and dpkg-deb 1.17.x
Date: Tue, 25 Feb 2014 21:24:07 +0100	[thread overview]
Message-ID: <530CFBE7.5060103@cestona.ro> (raw)
In-Reply-To: <CANyK_8dB_ZV61OkmuWM5TUjBgp7gTBGPU58-iVy6TXCJmCUv=Q@mail.gmail.com>

Hey Paul,

thx for your hints. I managed to get git send-email to work and send it
with signed-off-by line.

Regarding your question; The debian-binary needs to be the first member
of the archive, then control.tar.gz and then the data.tar.gz.

Have a look at "man 5 deb" there is a detailed description how the
archive should look like.

Greetings,
Thilo

Am 25.02.2014 16:34, schrieb Paul Barker:
> On 25 February 2014 15:15, Thilo Cestonaro <thilo@cestona.ro> wrote:
>> Hey all,
>>
>> with a recent change in dpkg-deb (
>> http://anonscm.debian.org/gitweb/?p=dpkg/dpkg.git;a=commitdiff;h=547dca4c3ff23df5dfa554f1943b371cd7056ee4
>> ), the packages generated by opkg-build will not be accepted by dpkg-deb
>> anymore. The change disallows that the data.tar.gz is packed into the
>> ipk or deb before the control.tar.gz.
>>
>> Supplied patch for opkg-utils repo fixes this.
>>
>> Greetings
>> Thilo
>>
> 
> This needs to be sent to the yocto@yoctoproject.org mailing list
> rather than the openembedded-core@lists.openembedded.org mailing list.
> 
> It should also be sent using 'git send-email' if possible and the
> description of why this change is needed needs to be included in the
> commit message for the patch.
> 
> You'll also need to add a 'Signed-off-by' line to the patch.
> 
> The full contribution guidelines for opkg-utils are now in the file
> 'CONTRIBUTING' in the root of the source tree. See
> https://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/tree/CONTRIBUTING
> for an online copy.
> 
> Regarding the change itself, is the 'debian-binary' file still allowed
> to be infront of the 'control.tar.gz' file in the archive? Other than
> that question, the change looks good at first glance.
> 
> If any of that doesn't work for you, let me know and I'll try to help out.
> 
> Thanks,
> 



      reply	other threads:[~2014-02-25 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 15:15 opkg-build and dpkg-deb 1.17.x Thilo Cestonaro
2014-02-25 15:34 ` Paul Barker
2014-02-25 20:24   ` Thilo Cestonaro [this message]

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=530CFBE7.5060103@cestona.ro \
    --to=thilo@cestona.ro \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    /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