> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report). 0.4.9 is according to the debian report more than a year old and it seems the devs are unwilling to fix in it that version, especially since they cannot reproduce it in the more recent 0.4.10 and 0.4.11
Elevating importance. I believe it would be nice if this was fixed before the hardy release. Not sure if anybody is willing to upload a newer aptitude this close to the release, I guess not. But this will certainly be a highly visible and highly annoying bug.
> I run the osupgrade alias at least once a day to make sure my hardy
> installation is up to date.
hardy is still on 0.4.9 (the same as for the upstream bug report). 0.4.9 is according to the debian report more than a year old and it seems the devs are unwilling to fix in it that version, especially since they cannot reproduce it in the more recent 0.4.10 and 0.4.11
Elevating importance. I believe it would be nice if this was fixed before the hardy release. Not sure if anybody is willing to upload a newer aptitude this close to the release, I guess not. But this will certainly be a highly visible and highly annoying bug.