public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: "Moessbauer, Felix (T CED OES-DE)" <felix.moessbauer@siemens.com>,
	 "Gylstorff,
	Quirin (T CED OES-DE)" <quirin.gylstorff@siemens.com>,
	"ubely@ilbers.de" <ubely@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	 "Kowalsky, Clara (T CED OES-DE)" <clara.kowalsky@siemens.com>
Subject: Re: [PATCH v2] debianize: use debhelper-compat to generate compat file
Date: Thu, 18 Apr 2024 14:15:25 +0200	[thread overview]
Message-ID: <034645c737629413fdfdcb7ce513cedf86df21fc.camel@siemens.com> (raw)
In-Reply-To: <eb08b896ff1f3fbcb3fed837018efb5b73e6c361.camel@siemens.com>

On Wed, 2024-04-17 at 21:16 +0000, Moessbauer, Felix (T CED OES-DE)
wrote:
> On Wed, 2024-04-17 at 11:00 +0200, Florian Bezdeka wrote:
> > Hi all,
> > 
> > [CC: Clara]
> > 
> > On Thu, 2024-02-01 at 11:12 +0100, 'Quirin Gylstorff' via isar-users
> > wrote:
> > > From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> > > 
> > > debhelper supports the versions debhelper-compat (= 9) till
> > > debhelper-compat (= 13).
> > > 
> > > This patch also adds the variable `DEBIAN_COMPAT` to set the compat
> > > to the desired version.
> > 
> > This introduces a regression. We are no longer able to build the rpi-
> > firmware with that patch applied.
> > 
> > Seems there are more side effects switching from debhelper to
> > debhelper-compat.
> 
> Hi Florian,
> 
> these side-effects are expected and also required for many users. All
> packages build for post buster should use debhelper-compat 13 as stated
> in the policies. Not being compatible is considered a bug.
> 
> > 
> > In our case something with the dh_dwz step goes wrong. TheELF file
> > generated during build is no longer "recognized", or as a file with
> > wrong input format. Clara can provide more information / logs if
> > necessary.
> 
> If dh_dwz is the issue, just overwrite that in the rules file.

The patch does two things at once:

- Switch from debhelper to debhelper-compat
- Lifting the compatibility level from 10 to 13 (for bookworm)

The later is causing trouble here. It seems to enable dh_dwz which
turns out to be broken for arm64. Some Debian bugs indicate it's
unfixable for bookworm...

For now no further action required. We can handle it here.

Just another "updating ISAR broke my layers" cycle. We're used to that
(sadly).

Florian

> 
> > 
> > I have no solution/fix right now. As this is clearly a regression we
> > should consider reverting.
> 
> Please do not revert, but fix the package. Many users already rely on
> the debhelper-compat 13 features (like tmpfiles.d support).
> 
> Felix
> 
> > 
> > Best regards,
> > Florian
> > 


  reply	other threads:[~2024-04-18 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 10:12 Quirin Gylstorff
2024-02-15  8:37 ` MOESSBAUER, Felix
2024-02-16  6:12 ` Uladzimir Bely
2024-02-20 19:07 ` Jan Kiszka
2024-04-17  9:00 ` Florian Bezdeka
2024-04-17 21:16   ` MOESSBAUER, Felix
2024-04-18 12:15     ` Florian Bezdeka [this message]
2024-04-19  9:48       ` Gylstorff Quirin

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=034645c737629413fdfdcb7ce513cedf86df21fc.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=quirin.gylstorff@siemens.com \
    --cc=ubely@ilbers.de \
    /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