Dear logol and swi-prolog maintainers, On 01-03-2022 10:21, Debian Bug Tracking System wrote:
Changes:
logol (1.7.9+dfsg-2) unstable; urgency=medium
.
* Source only upload, rebuilding against swi-prolog/8.4.2+dfsg-2 after
swi-prolog ABI break (Closes: #1006384).
This "fix" suggest there may be more breakage, normally the Release Team would schedule binNMU's. Can you please elaborate how ABI is normally maintained within swi-prolog, such that the rebuilds can be detected and requested? I fail to see how in the case of logol and swi-prolog the right versions are chosen. In other words, I think the "fixed" logol can migrate to testing even if swi-prolog does not and will be broken in testing until swi-prolog can migrate. Normally *versioned* dependencies should prevent this.
I checked, there are more reverse build dependencies of swi-prolog, I'm afraid there's more breakage that hasn't been detected yet. (eye seems to go in lockstep, so that package currently seems OK).
Paul
OpenPGP_signature
Description: OpenPGP digital signature
