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

Bug#981179: marked as done (nmu: dovecot-antispam_2.0+20171229-1+b6)

Your message dated Wed, 27 Jan 2021 13:11:52 +0100
with message-id <20210127121152.GF11279@ramacher.at>
and subject line Re: Bug#981179: nmu: dovecot-antispam_2.0+20171229-1+b6
has caused the Debian Bug report #981179,
regarding nmu: dovecot-antispam_2.0+20171229-1+b6
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.)


-- 
981179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981179
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: aerusso@aerusso.net

Hello,

I'm watching dovecot's progress through unstable [1] and it's blocked by
dovecot-antispam [2].  If I understand correctly, it's because
dovecot-antispam depends on dovecot-abi-2.3.abiv11, which is not provided
by the new version of dovecot-core (which instead provides a new abi
virtual package dovecot-abi-2.3.abiv13).  That dependency, however, is
determined at dovecot-antispam build time, so it should naturally
resolve itself if it is rebuilt.

Per a conversation I've had on debian-devel [3], it appears I should
request a binNMU (as I believe I am, here).  Please let me know if I
am doing anything incorrectly (e.g., should I be cc-ing the dovecot*
developers involved?)

Thank you,
Antonio Russo

[1] https://tracker.debian.org/pkg/dovecot
[2] https://tracker.debian.org/pkg/dovecot-antispam
[3] https://lists.debian.org/debian-devel/2021/01/msg00395.html

nmu dovecot-antispam_2.0+20171229-1+b6 . ANY . unstable . -m "Rebuild for dovecot-abi-2.3.abiv13"

Attachment: OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On 2021-01-27 03:38:57, Antonio Russo wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> X-Debbugs-Cc: aerusso@aerusso.net
> 
> Hello,
> 
> I'm watching dovecot's progress through unstable [1] and it's blocked by
> dovecot-antispam [2].  If I understand correctly, it's because
> dovecot-antispam depends on dovecot-abi-2.3.abiv11, which is not provided
> by the new version of dovecot-core (which instead provides a new abi
> virtual package dovecot-abi-2.3.abiv13).  That dependency, however, is
> determined at dovecot-antispam build time, so it should naturally
> resolve itself if it is rebuilt.
> 
> Per a conversation I've had on debian-devel [3], it appears I should
> request a binNMU (as I believe I am, here).  Please let me know if I
> am doing anything incorrectly (e.g., should I be cc-ing the dovecot*
> developers involved?)

Scheduled.

Cheers

> 
> Thank you,
> Antonio Russo
> 
> [1] https://tracker.debian.org/pkg/dovecot
> [2] https://tracker.debian.org/pkg/dovecot-antispam
> [3] https://lists.debian.org/debian-devel/2021/01/msg00395.html
> 
> nmu dovecot-antispam_2.0+20171229-1+b6 . ANY . unstable . -m "Rebuild for dovecot-abi-2.3.abiv13"
> 

pub   RSA 4096/DED4A4EE 2016-03-29 Antonio Enrico Russo <aerusso@aerusso.net>
> sub   RSA 4096/AAAA8C0F 2016-03-29
> sub   RSA 4096/38D2EE86 2016-03-29
> 




-- 
Sebastian Ramacher

--- End Message ---
Reply to: