I was chasing this a bit further down ... just to ensure this really is where it needs to be. It was not concurrent access, it seems to be confusion by the tools.
I've seen lines like: $ ./change-override --component main --suite plucky-proposed --source-and-binary tinysparql --dry-run ... libtinysparql-dev 3.8.2-5 in plucky ppc64el: main/libdevel/optional/100% -> main libtinysparql-dev 3.8.2-5 in plucky ppc64el: universe/libdevel/optional/100% -> main ... Same content, reported both ways. And acting on it essentially writing the same state again led to: 31 publications overridden; 64 publications remained the same. But the situation stayed the same. I hope this is resolved and I'll consider this an disturbance of the force. By tomorrow I'll recheck the state as it won't give me more debug/info now. If you spot anything odd along the way of tracking the migration of this let me know here on the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2099086 Title: [MIR] tinysparql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinysparql/+bug/2099086/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
