Just an update on some things relevant to this bug: * a new version of Rumur I uploaded, v2020.03.12-1, was just approved by Adam * Rumur v2020.01.27-2, my attempted final resolution to this bug, was removed from mentors due to the more recent upload
For anyone following this bug at home or trying to comprehend it in the future, we had an out-of-band email thread with Adam, Anatoly and myself, the relevant last part of which is: >> On Mar 3, 2020, at 11:08, Matthew Fernandez <matthew.fernan...@gmail.com> >> wrote: >> On Tue, 3 Mar 2020 at 07:22, Adam Borowski <kilob...@angband.pl> wrote: >> On Tue, Mar 03, 2020 at 06:59:14AM -0800, Matthew Fernandez wrote: >> > > On Mar 3, 2020, at 05:57, Debian Bug Tracking System >> > > <ow...@bugs.debian.org> wrote: >> > > #951881: RFS: rumur/2020.01.27-2 -- model checker for the Murphi language >> > > >> > > It has been closed by Adam Borowski <kilob...@angband.pl>. >> >> > Sorry, I don’t understand the rationale here. Is submitting an older -2 >> > to unstable not the way to do this? >> >> Any version numbers in a release must be monotonic. Once 2020.02.17-1 is >> in unstable, there's no way to upload 2020.01.27-2 there. >> >> ... >> >> Ah I see. Thanks for the explanation, Adam. >> >> Anatoly, does that mean we can close #951497? Adam/Anatoly, I think there’s nothing left for me to do in relation to this issue, but please let me know if I’m mistaken. I’ll leave it to you to adjust the bug status as relevant.
