Control: severity -1 important
Control: tags -1 moreinfo unreproducible
[ Lowering severity, because as it stands this report does not seem
reproducible, and it does not seem to affect anyone else? ]
On Wed, 2015-12-16 at 07:16:33 +0000, Simon McVittie wrote:
> On 16/12/15 01:15, Wayne Rowcliffe wrote:
> > I was able to get things working correctly by moving libevdocument3-4 up
> > in the `/var/lib/dpkg/status` file so that it was next to `evince`. I
> > have no idea why that changed anything, but afterward it found the
> > package fine.
Can you reproduce this? But removing and reinstalling evince and the
other related libraries? (But please see below first.)
Are you using some non-standard filesysem/kernel or anything that
might not be common, on that system? Have you noticed other weird
things going on that could be attributed to hardware failure?
> I am not a dpkg maintainer, but I expect that they will ask you for the
> following information:
>
> * version of dpkg and the packages it depends on
> ("reportbug --template dpkg")
> * entries in /var/log/dpkg.log* since just before the upgrade that
> failed to complete
> * entries in /var/log/apt/history.log* and /var/log/apt/term.log*
> since just before that upgrade
That would be helpful indeed. In addition if you can reproduce (or
even better can find a recipe to do so), that would be helpful. And
running «dpkg -C» on broken state, and sending the status file too
would be ideal. If you have concerns about privacy due to leaking
installed package state please send the information to me directly.
If you cannot reproduce you might still have the status file with the
broken state under /var/backup, which I'd appreciate if you could send.
> so you can probably speed up diagnosis by providing that information
> before you are asked for it.
Yes. :)
Thanks,
Guillem
