[Pkg-rust-maintainers] Bug#1008847: rust-atk-sys (autopkgtest failure with new atk)

[Peter Michael Green]

Thanks for the bug report, but i'm not convinced your patch is a good 
solution.

First off afaict your patch will break the tests with the old version of 
atk, which
may create some chicken and egg issues with getting it into testing.

There are  ways around that with extra dependenices, breaks etc
but i'm not convinced it's worth it for a constant that doesn't seem to
actually be used by any rust applications (in Debian or otherwise)
and that upstream has shown they are prepared to change without
bumping the soversion (so user code needs to cope with the case
where the value of the constant the user code was built against is
different from the one atk was built against).

Secondly I don't think adding new constants is something we should
be doing in Debian patches.

I'm more inclined towards simply ignoring this failure, the situation 
doesn't
seem any different from the case where an application is compiled against
one version of atk and run against another and as I mentioned no rust code
seems to actually use the constant in question.

I've whipped up a patch to do that, anyone else have any thoughts before
I upload?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: allow-increase-in-c-value-of-atk-state-last-defined.patch
Type: text/x-patch
Size: 1159 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20220403/2dfeccdb/attachment.bin>