public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "amikan@ilbers.de" <amikan@ilbers.de>
Subject: Re: [PATCH] dpkg-source: Drop -I filter
Date: Thu, 26 Oct 2023 10:21:31 +0000	[thread overview]
Message-ID: <50dc03958e268d5367ccef29a41c2a1cfe891267.camel@siemens.com> (raw)
In-Reply-To: <3040766a-bb96-4aa1-ba4d-0c47b9721c79@siemens.com>

On Thu, 2023-10-12 at 14:27 +0200, 'Jan Kiszka' via isar-users wrote:
> On 12.10.23 13:19, 'Jan Kiszka' via isar-users wrote:
> > From: Jan Kiszka <jan.kiszka@siemens.com>
> > 
> > This is a regression of 38b832ad8248 which added this while
> > factoring
> > out this step. However, some packages may break over this, e.g. the
> > edk2-standalonemm-rpmb recipe in isar-cip-core.
> > 
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> >  meta/classes/dpkg-source.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/classes/dpkg-source.bbclass b/meta/classes/dpkg-
> > source.bbclass
> > index 1f4f8164..a86b4635 100644
> > --- a/meta/classes/dpkg-source.bbclass
> > +++ b/meta/classes/dpkg-source.bbclass
> > @@ -12,7 +12,7 @@ do_dpkg_source() {
> >      if [ ! -z "${SOURCE_DATE_EPOCH}" ]; then
> >          export SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH}"
> >      fi
> > -    sh -c "cd ${WORKDIR}; dpkg-source -I -b ${PPS}"
> > +    sh -c "cd ${WORKDIR}; dpkg-source -b ${PPS}"
> >  }
> >  addtask dpkg_source after do_prepare_build before do_dpkg_build
> >  
> 
> That said, we can also think about re-introducing it, but it would
> need
> some control in recipe hands. Would be work on top in any case.

There are more things that break with the original patch:

First, we do not generate a debian/source/format, which defaults to 1.0
which is an ancient version. Second, when setting this correctly to 3.0
(native), we cannot include any non soversioned binaries into the
source archive (--include-binaries does not work for native packages).
This unfortunately breaks many packages at our side containing
proprietary stuff (like GPU drivers).

Best regards,
Felix

> 
> Jan
> 
> -- 
> Siemens AG, Technology
> Linux Expert Center
> 


  reply	other threads:[~2023-10-26 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 11:19 Jan Kiszka
2023-10-12 12:27 ` Jan Kiszka
2023-10-26 10:21   ` MOESSBAUER, Felix [this message]
2023-10-26 13:55     ` Anton Mikanovich
2023-10-26 14:02     ` Jan Kiszka
2023-10-26 14:56       ` MOESSBAUER, Felix

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=50dc03958e268d5367ccef29a41c2a1cfe891267.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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