Hacker News new | ask | show | jobs
by dane-pgp 1714 days ago
I guess the release date was as recent as 2021-07-23, and it's conceivable that such a rebuilding project being run only with spare CPU cycles might take months (or might only have started recently).

As an interesting data point, I see that the number of pending packages is now 21.2%. Let's hope that most of these remaining packages (and those being retried) turn out to be reproducible.
1 comments
Foxboron 1714 days ago
Such rebuilds systems are complicated and might not work 100% when you first start out. There can be multiple complete rebuilds done while removing edge-case bugs that either fails the building or introduces variance into the builds.
link
dane-pgp 1713 days ago
That's some helpful context, thank you.

As a further analysis, I note that, excluding the current "pending" builds, the "reproducible" segment accounts for 93% of all packages so far.

I don't know if it's reasonable to assume that the "pending" packages are a representative sample in terms of their reproducibility, or how likely the "retry" packages are to succeed, but I'm hopeful that in a few days the "reproducible" stat will pass 90% for real.

link
dane-pgp 1710 days ago
As predicted, the "reproducible" segment on that pie chart[0] is now at 90.1% with a few percent of packages still pending or being retried.

[0] https://debian.notset.fr/rebuild/results/bullseye_full.amd64...

link