I am not walking away. The failure is 2 folds. If you got hit by -6, on your machine the (broken) maintainer script gets installed, which you'll have to manually remove. That's something I do not want to handle in the package. Otherwise, the fix to not break the maintainer script is done.
On Tue, Mar 15, 2016 at 10:40 PM, Sven Hartge <s...@svenhartge.de> wrote: > On Tue, 15 Mar 2016 22:28:49 +0530 Ritesh Raj Sarraf <r...@debian.org> > wrote: > > > If you upgrade from -5 to -7, you shouldn't be hitting this problem. I > > thought about handling the breakage, but that would touch files outside > > , which I'm not keen on. > > > > And Unstable is supposed to have breakages. > > Sorry, but I find this unacceptable. Sure, Unstable can have breakages, > but is not supposed to have one. You cannot just ignore one upgrade path > because it is inconvenient for you. > > The -6 package has been release to mirrors and has been installed on > systems, so you have to provide a clean upgrade path to the next package > and not just walk away saying "upgrade from -6 to -7 are not supported" > and leave the user to manually put the package into a working state again. > > Grüße, > Sven. > > -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
