Re: Not selecting outdated <package-implementions>

On 4 June 2015 at 18:21, Bastian Eicher <[email protected]> wrote:
> Hmm, I just noticed strange behavior for Mono even when it is up-to-date:
>
> $ 0install run http://0install.net/tools/0install.xml -V
> 0install (zero-install) 2.8
> (...)
>
> $ 0install run -c http://0install.de/feeds/cli/mono.xml
> The following components need to be installed using native packages. These
> come from your distribution, and should therefore be trustworthy, but they
> also run with extra privileges. In particular, installing them may run extra
> services on your computer or affect other users. You may be asked to enter a
> password to confirm. The packages are:
>
> - mono-complete;3.2.8+dfsg-4ubuntu1.1;amd64;Ubuntu
> [Y/N] y
> 9: Package mono-complete is already installed
>
> $ dpkg -s mono-complete
> Package: mono-complete
> Status: install ok unpacked
> Priority: optional
> Section: cli-mono
> Installed-Size: 70
> Maintainer: Ubuntu Developers <[email protected]>
> Architecture: amd64
> Source: mono
> Version: 3.2.8+dfsg-4ubuntu1.1
> Config-Version: 3.2.8+dfsg-4ubuntu1
> (...)

1. What's in ~/.cache/0install.net/injector/dpkg-status.cache ? This
should list the version it thinks is already installed.

2. What do you see running with "-vv"? It should log its
communications with PackageKit.

3. Are you using the real PackageKit or Ubuntu's aptdaemon alternative?


-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

------------------------------------------------------------------------------