Control: severity -1 important Petter Reinholdtsen wrote: > Can you explain what rationale you have for setting the severity as > serious? To me it seem like an important bug at most.
I interpreted it as a "severe violation of Debian policy." A typo in the upstream version would be relatively minor, but the last two uploads, representing ~7 years of upstream development, were misleadingly broken. I'm no expert, so I've lowered it to important instead of release-critical. Does that seem reasonable to you? > And given where we are in the release process, it is unclear to me > what exactly you propose to do with pybluez in Stretch. Removal along > with [...] seem rather dispropotional. I agree that removal is disproportionate (and would frustrate me too), especially since this affects jessie as well. I imagine the easiest solution (that could be unblocked) would have been to bump the epoch to correct the upstream version. Regardless it's not marked as RC anymore. Dara
