[debian-mysql] Fwd: [helmut at subdivi.de: Re: possible DPKG problem in crossqa]

[Otto Kekäläinen]

Moi!

Viesti alla Helmutilta joka ei näemmä voi vastata sulle suoraan.

Suosittelen jatkamaan keskustelua CC:
pkg-mysql-maint at lists.alioth.debian.org
jotta useampi voi osallistua siihen ja muut näkee mitä keskustelette.


---------- Forwarded message ---------
From: Helmut Grohne <helmut at subdivi.de>
Date: Mon, 4 Dec 2023 at 11:22
Subject: [helmut at subdivi.de: Re: possible DPKG problem in crossqa]
To: <otto at debian.org>


Hi Otto,

Tuukka Pasanen asked me about mariadb, but their email address bounces.
Do you happen to know them? If yes, could you forward my reply via other
means?

Thanks in advance

Helmut

----- Forwarded message from Helmut Grohne <helmut at subdivi.de> -----

Date: Mon, 4 Dec 2023 09:53:52 +0100
From: Helmut Grohne <helmut at subdivi.de>
To: Tuukka Pasanen <pasanen.tuukka at gmail.com>
Subject: Re: possible DPKG problem in crossqa

Hi Tuukka,

On Mon, Dec 04, 2023 at 09:45:03AM +0200, Tuukka Pasanen wrote:
> Sorry to bother you with this..

That's fine. I think though that your problem is less with the crossqa
service (where you picked the right address) and rather a general cross
build problem. In the latter case, please mail
debian-cross at lists.debian.org in future even if you end up getting a
reply from me. Thanks in advance.

> I've be maybe parking wrong tree and have no idea but I've just like to
ask
> that builds with cross-arm with MariaDB (
http://crossqa.debian.net/build/mariadb_1:10.11.4-1_arm64_20230926220242.log
)
> are currently not working because of dpkg adding
> '-mbranch-protection=standard' to building options. It works on native ARM
> building but not seems to work on cross building which makes whole
> http://crossqa.debian.net/src/mariadb look bad

You are looking at a build from two months ago that suffered from
PAC/BTI flags. It has since been fixed via
https://bugs.debian.org/1051222 in version 1:10.11.5-1.

I'm not sure why you think this looks bad. The page shows the build
history. An old failure is not bad. To the contrary, what we see here is
a failure that was fixed quickly. I note that you cannot read that page
as a "status". Very often, the information needs to be interpreted to be
useful. Frequently, a cross build failure in one package is caused by a
problem in a different package. The page is not meant for package
maintainers but for cross build porters that have an archive-wide view.

> What I'm asking you (I knowing that you might not be the person whom can
do
> anything about this) but could give me a hint which mailing list I should
> ask from this or can I somehow overcome this (I'm not just understanding
how
> things work?) by myself.

The mariadb problem has all been handled already. If you want to support
cross building in Debian, that's very welcome. I recommend the following
communication channels:
 * debian-mentors at lists.debian.org for basic packaging questions as well
   as simple cross build question.
 * irc.oftc.net #debian-mentors is the same thing with chat.
 * debian-cross at lists.debian.org for cross build sepcific questions. You
   are also encouraged to post your ideas about cross build failures and
   proposed patches there to get peer review.
 * irc.oftc.net #debian-bootstrap for more interactive support regarding
   cross building.

> I've noted that by doing manual build anf removing that parameter adding
> from Perl DPKG makes everything work again.

I still wonder why you build an old version. Please note that I only
support cross building in unstable, because that already stretches my
capacity. For all other releases, you probably are on your own.

Helmut

----- End forwarded message -----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20231205/8a3d7ad9/attachment.htm>