Hi Chris, On Mon, Feb 25, 2019 at 07:29:56AM +0000, Chris Lamb wrote: > Hi Nicholas, > > > heaptrack (1.1.0+20180922.gitf752536-3.1) unstable; urgency=medium > > > > * Non-maintainer upload. > > * Update description to make heaptrack more discoverable to users. > > (Closes: #915241) > > > > -- Nicholas D Steeves <nsteeves@gmail.com> Sun, 24 Feb 2019 19:44:03 -0700 > > Whilst I agree about the poor visibility I don't think this > warrants a non-maintainer upload (or even a "normal"-level > severity…) especially during a freeze so I will not be sponsoring > this upload. Apologies. > Well, I packaged memleax because I couldn't find heaptrack, and when memleax was abandoned upstream I discovered heaptrack via memleax' issue tracker. There, upstream said he might not have started work on memleax if he had known about heaptrack. [1] I thought that this warranted an NMU, after waiting > 2.5 months for a reply at #915241. eg: that an NMU was for the greatest good if people have such a hard time discovering heaptrack that they start projects to reimplement its functionality unawares. So are NMUs only justified for fixing RC bugs and/or never for adding basic discoverability (apt search keyword_or_expression)? Regards, Nicholas [1] https://github.com/WuBingzheng/memleax/issues/37#issuecomment-405792279
Attachment:
signature.asc
Description: PGP signature