public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] dpkg-source: Drop -I filter
Date: Thu, 26 Oct 2023 16:55:51 +0300	[thread overview]
Message-ID: <c6641e94-20d6-4f23-a506-b62fd4a1d25d@ilbers.de> (raw)
In-Reply-To: <50dc03958e268d5367ccef29a41c2a1cfe891267.camel@siemens.com>

Hello Felix,

Can you provide some example recipe that was building ok before 38b832ad and
was broken by it?
We've never generate debian/source/format before, and it looks like more
debianization issue then source package building problem.


26/10/2023 13:21, MOESSBAUER, Felix wrote:
> 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



  reply	other threads:[~2023-10-26 13:55 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
2023-10-26 13:55     ` Anton Mikanovich [this message]
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=c6641e94-20d6-4f23-a506-b62fd4a1d25d@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --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