Hi.
Thanks for your help and sorry for the delay in answering.
I found the problem while gathering info for you:
# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
1 http://deb.debian.org/debian experimental/main amd64 Packages
release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian sid/contrib amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian sid/non-free amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian sid/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
libmypaint-common -> 1.3.0-2 with priority -30000
This file was in /etc/apt/preferences.d/apt-listbugs:
Explanation: Pinned by apt-listbugs at 2018-05-03 08:43:14 +0200
Explanation: #894757: libmypaint-common: file conflict with mypaint-data
Package: libmypaint-common
Pin: version *
Pin-Priority: -30000
After removing the file, I could install gimp without issues.
Best regards!
On Mon, Jun 18, 2018 at 9:41 PM James Cowgill <jcowg...@debian.org> wrote:
> Hi,
>
> Sorry I accidentally sent the last email by mistake before it was finished.
>
> On 18/06/18 14:35, José Couto wrote:
> > Sorry, I forgot to cc bugs.debian.org <http://bugs.debian.org>.
> >
> > Hi, James. Thank you for your help.
> [...]
> > I can't install libmypaint-common by hand either:
> >
> > ###
> > # apt-get -o Debug::pkgProblemResolver=yes install libmypaint-commo
> > n
> >
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Package libmypaint-common is not available, but is referred to by
> > another packag
> > e.
> > This may mean that the package is missing, has been obsoleted, or
> > is only available from another source
> >
> > E: Package 'libmypaint-common' has no installation candidate
> > ###
>
> As I said I don't know what's wrong here. That package should exist and
> does exist in the main package lists and on my machine.
>
> Maybe try running "apt update" again?
> What's in your /etc/apt/sources.list?
>
> James
>
>
