Re: should bugs really be closed?
"Nikita V. Youshchenko" <firstname.lastname@example.org> writes:
> As gcc changelog.Debian states, bugs filed against earlier versions of gcc
> (e.g. gcc-3.2 or gcc-2.95) are closed when they are fixed in later version
> (e.g. gcc 3.3).
> Is that really correct?
> gcc-3.2 package is still in Debian and still contains those bugs. So IMHO
> bugs should be still opened against it, unless a fix is backported.
There is absolutely no way to fix any bug in any package in the
version for which the bug has been reported. You always have to
provide an update of the software to fix bugs - you cannot magically
change the files that users have on their disks.
gcc 3.3 is an update for gcc 3.2, so it fixes bugs reported in gcc.