[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1107456: pre-unblock: uncertainties/3.2.3+really3.2.2-1



Package: release.debian.org
Severity: normal
X-Debbugs-Cc: sanvila@debian.org,cjwatson@debian.org,dparsons@emerall.com
User: release.debian.org@packages.debian.org
Usertags: unblock

Hello.

The upload of uncertainties 3.2.3-1 in 2025-05-05 has accidentally
broken several packages, lmfit-py and pymatgen at least.

Because the breakage only happens in unstable, the plan to keep trixie
free of breakage was to not allow uncertainties to propagate to testing.

But yesterday I realized that RC Bug #1107280 in pymatgen ("tries internet
access during build") can't be fixed as far as there is an uncertainties
version which makes the package to FTBFS, as it happens now.

(Not to mention the additional problems in form of trixie-ignore tags
that would involve such strategy).

So: Should we try the route of reverting uncertainties to version 3.2.2 ?

If yes, question for Colin: Can you care about reverting uncertainties?

[ Cc to Colin and also to Drew, who asked about this just a few days ago ].

Thanks.


Reply to: