[debian-mysql] Bug#1139668: galera-4: FTBFS: /<<PKGBUILDDIR>>/galerautils/src/gu_asio_io_service_impl.hpp:19:10: fatal error: asio/io_service.hpp: No such file or directory

[Santiago Vila]

Hello Otto.

I see some misunderstandings here.

First and foremost, I'm not a DPL delegate for doing archive rebuilds,
I'm just doing them because I can. If I were a delegate for doing
archive rebuilds, I would have resigned a lot of time ago.

On Thu, Jun 11, 2026 at 10:27:11AM +0800, Otto Kekäläinen wrote:

> When you do these rebuilds, could you somehow automate to file the bugs on
> the packages that caused them, insted of just packages that suffers from
> them?

You seem to imply that a build-dependency which causes other packages
to FTBFS is usually the one having the bug.

That's not true in general. Usually, packages have to be adapted to
work with newer libraries all the time.

But even if the proportion was 50%/50%, there is no algorithm to determine
if the blame is in a buggy build-dependency, or it's a case where individual
packages have to be adapted, other than researching the subject, which
takes time and effort and it has never been my job.

Instead of all that, you should consider a FTBFS bug merely as a
statement of a fact: that some package failed during a rebuild.

The root cause is for the maintainers to determine, not for the
person filing the bug.

As I said above, doing archive rebuilds is not even my job.

> Maybe insted of doing full rebuilds, just rebuild a list of reverse
> dependencies each time a library updates or something?

Making sure that a library update does not break a lot of packages is
the job of library maintainers.

I try to do my part for the library packages I maintain (for example,
packages which FTBFS with gettext 0.26 were reported a lot of time
before it was finally uploaded for unstable) but I can't care about
each library in Debian, that's simply not my job.

> Or at least file with 'severity: normal'? Now anyone who uploads a new
> library without proper testing will with your help cause dependencies to be
> automatically removed from Debian, putting all the onus on downstreams of
> the problem instead of making new updates have better transition planning.

I think you are looking at the problem in a completely wrong way, in
particular when using the words "with your help".

As it's often said: "Don't kill the messenger".

Thanks.