On Sun, 15 Nov 2015 16:51:22 +0100 Andreas Beckmann wrote:
> Do you have a backup of the dpkg status file from before
> that upgrade? IIRC this should be sufficient to replay the upgrade path.
> (/var/lib/dpkg/status)
Sorry I forgot to reply. I don't have a backup of that file.
On 2015-11-15 15:18, Diederik de Haas wrote:
> update-glx is indeed the only one in the whole list with ":armhf" appended to
> its package name. Before reassigning it to apt/aptitude I'd prefer to have
> found another package which exhibits the reported behavior.
> Do you have any suggestions
On Sunday 15 November 2015 11:27:09 Andreas Beckmann wrote:
> > I haven't rebooted yet so I don't know if it will cause problems, but it
> > does seem odd that on my amd64 a package from armhf is installed as
> > dependency instead of the one from my 'native' architecture.
>
> That's weird, but
Control: tag -1 unreproducible
On 2015-11-15 05:45, Diederik de Haas wrote:
> Package: glx-alternative-nvidia
> Version: 0.7.1
> Severity: normal
>
> I haven't rebooted yet so I don't know if it will cause problems, but it
> does seem odd that on my amd64 a package from armhf is installed as
>
Package: glx-alternative-nvidia
Version: 0.7.1
Severity: normal
I haven't rebooted yet so I don't know if it will cause problems, but it
does seem odd that on my amd64 a package from armhf is installed as
dependency instead of the one from my 'native' architecture.
Probably a shortcoming of
5 matches
Mail list logo