Hi Paul, Чт 15 дек 2022 @ 21:10 Paul Gevers <elb...@debian.org>:
> On 14-12-2022 10:15, Debian Bug Tracking System wrote: >> * rebuild against new swi-prolog (Closes: #1026056) > > I can't but feel a bit uneasy by this "solution". Apparently it's not > properly tracked by dependencies, so it doesn't show up on the Release > Teams auto transition trackers [1] (which would typically trigger the > Release Team to trigger binNMU's, but if nothing else at least would put > it on the radar). For C based libraries this "solution" typically hides > real problems. Do we believe we can improve the logol/swi-prolog > situation in a similar way, or is the effort really not worth it > (apparently autopkgtest catches the issue, but the solution isn't > visible from the failure). > [1] https://release.debian.org/transitions/ Thanks for your attention! Yes, I should have initiated transition. Guess, I will do this in the future. There are not so much packages depending on swi-prolog, just logol and eye. Only these packages require rebuilding with a major upgrade of swi-prolog. Anyway, transitions are preferable way, I agree. Cheers! Lev
