[ replying to the lists only, please do not cc me in this thread ]

On Wed, Jul 15, 2026 at 03:21:58PM +0300, Adrian Bunk wrote:

> The MariaDB exclusion in the latest point release that prevented  
> a broken MariaDB from entering stable was only found throough a
> FTBFS in an rdep reported by Santiago for unstable.
> 
> I just discovered that DSA 6336-1 included in the latest point release 
> causes FTBFS of at least 6 packages in stable (there might also be some 
> runtime breakage in the affected packages), and this could have been 
> fixed before the point release had it been discovered in time.

Additionally, the revert of geoip-database to an older version is
probably the reason why the tests of lua-geoip now fail, the new
python triggered a weird bug in sphinx which made between 7 and 10
packages to FTBFS, and several other packages which used to build ok
in trixie do not build ok anymore.

I share your concern. We have been unable to ship a stable release
without FTBFS bugs in a very long time, and I believe people in
general is not aware of that.

> @Santiago:
> How long would a rebuild of all packages in trixie (perhaps with
> exclusions for a few large packages) take?
> [...]

An archive rebuild takes between 24h and 48h, so your estimate is
correct.

Unfortunately, there are FTBFS bugs in trixie which I reported shortly
after 13.0 (or even *before*) which are still unfixed as of today, so
I do not perceive true willingness from the project as a whole to ship
point releases without FTBFS bugs (and of course I can't blame anybody
for that because we are all volunteers).

Sorry, but I can't do archive rebuilds all the time. I have enough
work doing them after each point release with the hope that maybe the
bugs found could be fixed for the next point release, but we are not
even able to fix those, so I don't think any amount of archive
rebuilds will fix the underlying problem.

Maybe what we need is a cultural change of some kind.

(In either case, raising awareness of the problem is indeed a very
good first step).

Thanks.

Reply via email to