Re: dovecot-antispam rebuild (or is there a way to automatically rebuild a package)
On 1/27/21 12:58 AM, Sebastian Ramacher wrote: > > For step 2 someone needs to request a binNMU > > reportbug release.debian.org -> binNMU > > See also https://wiki.debian.org/binNMU > > Best > Thank you (for the info, and processing the binNMU)! Antonio OpenPGP_0xB01C53D5DED4A4EE.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Re: dovecot-antispam rebuild (or is there a way to automatically rebuild a package)
On 2021-01-26 21:50:54, Antonio Russo wrote: > 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. > > It seems to me that what should ideally happen is: > > 1. New version of dovecot gets uploaded > 2. dovecot-antispam gets rebuilt (automatically?) > 3. enough time passes > 4. dovecot and dovecot-antispam migrate to testing together > > Is this correct? If so, what mechanism triggers the rebuild of > dovecot-antispam, > and why hasn't it already happened? If not, what action should be taken? For step 2 someone needs to request a binNMU reportbug release.debian.org -> binNMU See also https://wiki.debian.org/binNMU Best > > More importantly, where is this all documented? > > Thanks, > Antonio > > > [1] https://tracker.debian.org/pkg/dovecot > [2] https://tracker.debian.org/pkg/dovecot-antispam pub RSA 4096/DED4A4EE 2016-03-29 Antonio Enrico Russo > sub RSA 4096/8C0F 2016-03-29 > sub RSA 4096/38D2EE86 2016-03-29 > -- Sebastian Ramacher
dovecot-antispam rebuild (or is there a way to automatically rebuild a package)
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. It seems to me that what should ideally happen is: 1. New version of dovecot gets uploaded 2. dovecot-antispam gets rebuilt (automatically?) 3. enough time passes 4. dovecot and dovecot-antispam migrate to testing together Is this correct? If so, what mechanism triggers the rebuild of dovecot-antispam, and why hasn't it already happened? If not, what action should be taken? More importantly, where is this all documented? Thanks, Antonio [1] https://tracker.debian.org/pkg/dovecot [2] https://tracker.debian.org/pkg/dovecot-antispam OpenPGP_0xB01C53D5DED4A4EE.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
