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

This is a bad status. It should be "install ok installed". Looks like
it didn't finish installing for some reason. A reinstall might sort it
out. Anyway, running mono-complete worked for me on Ubuntu 15.04 (via
Docker):

# cat /etc/issue
Ubuntu 15.04 \n \l

# 0install  --version
0install (zero-install) 2.8
Copyright (C) 2013 Thomas Leonard
This program comes with ABSOLUTELY NO WARRANTY,
to the extent permitted by law.
You may redistribute copies of this program
under the terms of the GNU Lesser General Public License.
For more information about these matters, see the file named COPYING.

# 0install run -c  http://0install.de/feeds/cli/mono.xml
Usage is: mono [options] program [program-options]


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

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