[pkg-go] Bug#915907: rclone: autopkgtest regression: missing versioned dependency?

Dr. Tobias Quathamer toddy at debian.org
Sun Dec 16 13:15:23 GMT 2018

Am 09.12.2018 um 20:26 schrieb Paul Gevers:
> On Fri, 7 Dec 2018 21:16:40 +0100 Paul Gevers <elbrus at debian.org> wrote:
>> With a recent upload of rclone the autopkgtest of rclone fails in
>> testing when that autopkgtest is run with the binary packages of rclone
>> from unstable.
> I wonder if this isn't just pointing at a missing versioned depends on
> golang-github-okzk-sdnotify as updating that package in testing also
> makes the (older) version of rclone in testing fail, while rclone passes
> in unstable.

Hi Paul,

I've now uploaded a new version of rclone which passes (as expected)
with the current golang-github-okzk-sdnotify package from sid.

However, the debci test now fails in testing, because the
golang-github-okzk-sdnotify package has already migrated to testing,
while rclone did not. Therefore, the older version of rclone in testing
now fails to build with the newer okzk-package.

The testing migration time (of okzk) has now been increased by 34 days
due to the failing test. However, in my opinion, the test result is
bogus, because the rclone package in sid builds fine with okzk in sid.
So both packages could migrate together without the increased delay. Or
am I missing something here?

Could you do anything about the increased testing migration? Or can I do
something about that?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20181216/af5cad79/attachment.sig>

More information about the Pkg-go-maintainers mailing list