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

Bug#1026794: marked as done (nmu: logol_1.7.9+dfsg-6)

Your message dated Thu, 22 Dec 2022 19:32:49 +0500
with message-id <87mt7fwlta.fsf@localhost>
and subject line Re: Bug#1026794: nmu: logol_1.7.9+dfsg-6
has caused the Debian Bug report #1026794,
regarding nmu: logol_1.7.9+dfsg-6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1026794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026794
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: logol@packages.debian.org
Control: affects -1 + src:logol

nmu logol_1.7.9+dfsg-6 . ANY . unstable . -m "Rebuild against swi-prolog 9.0.3+dfsg-1"

Hi,

Please, binNMU logol 1.7.9+dfsg-6 (currently in unstable) against
swi-prolog 9.0.3+dfsg-1 (currently in unstable) to fix autopkgtests
failures and make transition to testing possible.

Thanks!

Cheers!
Lev

--- End Message ---
--- Begin Message --- 
Hi Paul,

Чт 22 дек 2022 @ 10:38 Paul Gevers <elbrus@debian.org>:

> Control: tag -1 moreinfo
>
> On 21-12-2022 09:49, Lev Lamberov wrote:
>> Please, binNMU logol 1.7.9+dfsg-6 (currently in unstable) against
>> swi-prolog 9.0.3+dfsg-1 (currently in unstable) to fix autopkgtests
>> failures and make transition to testing possible.
>
> The version of logol in unstable passes its autopkgtest in unstable (on 
> all architectures I tried it on). Are you sure the rebuild is needed?
>
> I think your problem is that there's no versioned relation (Depends or 
> Breaks) pulling the logol from unstable for the triggered test by 
> swi-prolog. Essentially this problem is the same as the one I recently 
> discussed with you, so another reason to solve it.

Ahhh... now I see that logol is OK. Probably, Debian Package Tracker
reported logol's failures because of some delay.

Actually, I wondered why logol may fail, since there are no any
significant changes in swi-prolog 9.0.3 except fix for #1026057.

Then, I'm closing this bug report. Sorry for the noise.

logol is already depends and build-depends on a specific ABI version.
Now is it swi-prolog-abi-binary-68. I wrote to logol maintainers that it
is not an elegant decision, and that they should take eye maintainers
route and depend on something like swi-prolog-abi-${prolog:ABI} (see,
#1006384).

Cheers!
Lev

--- End Message ---
Reply to: