> >I do not want to put a pressure on anyone, but if it is the only way > >to make big changes to package, let's do it. > I could understand that, but > 1) lets avoid experimental features > 2) lets try to keep changes minimal.
Okay, I can agree that compat 10 is unnecessery. But still someone someday will have to do it. > I mean, a package refactor might be acceptable if the current > packaging is broken/unmaintainable, not just for fun Sorry, can't locate any just-for-fun changes beside compat 10. > (avoding compat level 10 will remove a lot of the diff, and Is it imperative to revert it? > (BTW I would also apreciate you opening important bugs for your > changes, e.g. "please add hardening" please avoid STRIPPING of > binaries and then propose a patch for them. Okay, I will do it this next time. > STRIP is something new in this release, so you can avoid a bug) Sorry, can't understand this sentence. Do you advice aganist usage of STRIP variable? > >BTW, is it some rule of thumb, how many days of no response to > >please-package-new-upstream-version-bug should pass before considering > >NMU/MIA? > Since you opened the "please update version bug" [1] one year ago, I > propose you to bump the severity to important, and then wait some > little more time. Bumped severity. > I'll for sure put the upload in deferred/15, so the maintainers will > have time to react (adding the time you will need to prepare a good > package :) ) -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io
