Hi,

On 14/05/25 at 13:50 +0300, Adrian Bunk wrote:
> On Tue, May 06, 2025 at 08:48:29AM +0200, Lucas Nussbaum wrote:
> > On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> > > In some cases, the bug is already known, because debian/rules
> > > has --max-parallel=1. Example: The alpine package.
> > > 
> > > (I wonder how much feasible would be to skip those packages)
> > 
> > The alpine package is indeed a good example of a package that makes
> > extensive use of the sequentiality of 'make', and that is going to be
> > hard to adjust to switch to parallel building or arbitrary orders.
> > 
> > However I still think that there's value in filing bugs for such
> > packages, because --shuffle=reverse makes it much easier to debug such
> > issues: instead of trying a parallel build and getting a subtlely
> > different race conditions at each run, you get a reproducible ordering
> > that exhibits one issue that you can debug, and then move on to the next
> > issue.
> > 
> > Also it's not trivial to distinguish between packages that do not build
> > in parallel on purpose, vs those that just happen not to build in
> > parallel (yet).
> 
> What is a maintainer supposed to do when the package already does
> "dh --no-parallel" and the upstream Makefiles are basically unfixable?
> Just close the bug?

Or mark it wontfix?

> Strip "--shuffle" in debian/rules?
> 
> How many of the packages that break with "make --shuffle" are currently 
> doing parallel building?

Grepping for the 'Waiting for unfinished jobs ...' message and combining
this with bugs filed, I find 74 packages that fail with
--shuffle=reverse, and 7 that fail with --shuffle=random and not
--shuffle=reverse. (listed below)

> I am asking since these might be RC bugs for trixie.

If you are implying that I'm going to push for RC severity for those
bugs: no, I'm not planning to, unless the failures are reproducible
without --shuffle.

- Lucas



apertium-dan-nor #1105259
apertium-spa-cat #1105257
apngasm #1105275
apngopt #1105238
asciijump #1105255
blahtexml #1105265
bloboats #1105242
blockout2 #1105272
boinctui #1105294
cataclysm-dda #1105263
cbp2make #1105233
clhep #1105293
connman #1105298
consensuscore #1105296
console-common #1105247
darknet #1105249
ddd #1105232
ddir #1105261
docbook-to-man #1105271
efivar #1105354
euslisp #1105329
fact++ TODO
foo2zjs #1105322
fossil #1105310
gcl27 #1105309
genometools #1105339
gmrender-resurrect #1105332
grass #1105330
grokevt #1105325
guetzli #1105411
iraf #1105412
irrlicht #1105374
isl #1105398
iverilog #1105401
kylin-burner #1105394
ldns #1105380
le #1105371
libf2c2 #1105484
libreoffice #1105453
libsdl2 #1105444
lmod #1105445
ltrsift #1105470
mailfilter #1105490
multimon #1105488
muscle #1105460
nanovg #1105510
neomutt #1105534
octave-ltfat #1105525
openafs #1105449
peg #1105570
phalanx #1105564
pixelize #1105684
proftpd-dfsg #1105645
qemu #1105631
qtdeclarative-opensource-src-gles #1105679
qtdeclarative-opensource-src #1105556
raysession #1105586
retroarch #1105559
rootskel-gtk #1105706
simavr #1105549
simulide #1105663
snap7 #1105572
sssd #1105624
sugar-toolkit-gtk3 #1105558
swirc #1105609
texworks-manual #1105622
tk-table #1105585
tstools #1105708
uc-echo #1105670
umtp-responder #1105676
vflib3 #1105694
xelb #1105669
yaha #1105561
z80dasm #1105573

bedtools #1105730
carbon-c-relay #1105726
cssc #1105732
freeradius #1105717
mingw-w64 #1105725
open-vm-tools #1105731
uftrace #1105724

Reply via email to