On Fri, 17 Feb 2012, Michal Suchanek wrote:
> > You should have made a backup of all the important files in
> > /var/lib/dpkg/ (at least status, possibly the content of the updates
> > directory too, if not empty) when you were encountering the problem.
>
> Now this is somewhat redudndant chasing a bug fixed in newer dpkg
> already.
Right... why did you decide to report it then? Do you really believe that
it's worth being fixed in oneiric? It's not a widely encountered bug since
you're the firt one to report it. :-)
Please, despite this, can you attach the /var/lib/dpkg/status that
triggers this bug ? I don't have any oneiric chroot to reproduce it
quickly...
On Fri, 17 Feb 2012, Michal Suchanek wrote:
> > You should have made a backup of all the important files in
> > /var/lib/dpkg/ (at least status, possibly the content of the updates
> > directory too, if not empty) when you were encountering the problem.
>
> Now this is somewhat redudndant chasing a bug fixed in newer dpkg
> already.
Right... why did you decide to report it then? Do you really believe that
it's worth being fixed in oneiric? It's not a widely encountered bug since
you're the firt one to report it. :-)
Please, despite this, can you attach the /var/lib/ dpkg/status that
triggers this bug ? I don't have any oneiric chroot to reproduce it
quickly...
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help debian- handbook. info/liberation /
liberate it: http://