On Fri, Aug 28, 2020 at 07:06:10AM -0700, Matthew Fernandez wrote: > Thanks for reporting this, Adrian. I noticed this some time after upload and > fixed it upstream: > https://github.com/Smattr/rumur/commit/68683c4742b380421936a703c4b9262dac1e68dc > > <https://github.com/Smattr/rumur/commit/68683c4742b380421936a703c4b9262dac1e68dc> > > I hadn’t uploaded a fixed version to Debian because Rumur’s release cadence > is so frequent I expected to release a new upstream version before the fix > could get into Debian unstable. I hope this is an acceptable strategy.
No problem with that, just close this bug in the upload. > By the way, is there any way to run the buildd tests prior to upload? I don’t > have, e.g. armhf, hardware and bringing up a usable armhf qemu environment > seems non-trivial. The buildd tests only seem to run after an upload is > accepted, so I end up only being able to run this cross-platform testing once > per release and only after the fact. For armhf specifically the answer would be to get a Raspberry Pi. There are porterboxes that can also be made available to non-DDs, but in many cases it is easiest to just upload and see how it goes. cu Adrian
