[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug closed because program has new major version ??



Debian Bug Tracking System writes ("Bug#16484 acknowledged by developer          (Package 'gmp' removed from Debian)"):
...
> It has been closed by one of the developers, namely
> Martin Michlmayr <tbm@cyrius.com>.
...
> You have filed a bug report against the package 'gmp'.  This package
> is now no longer part of Debian unstable, so I'm closing your bug.

This is an absurd reason for closing my bug report.  gmp has been
replaced by a variety of new packages, including relevantly
libgmp3-dev.  What on earth makes you think my bug report does not
still apply ?

Bugs should not be closed merely because the package involved has been
renamed, causing them to be recorded against a nonexistent package.
Instead, they should be reassigned to the package's new name.

The fact that the package renaming corresponded to a new upstream
version doesn't change this.  New upstream versions aren't a reason to
close a bug report either; if the new version had the bug fixed then
that would be a good reason to close the bug, but you don't show any
signs of having looked at the libgmp3-dev package to see whether it
was fixed.

Disclaimer: I haven't checked the package either, but given the
attitude of the upstream maintainer, which you can see expressed in
the bug report logs for #16484, it seems unlikely that the problem is
now solved.

I shall reopen #16484 and reassign it to libgmp3-dev.
Martin Michlmayr, would you like to explain your behaviour ?

Thanks,
Ian.



Reply to: