Hi,
is anybody else observing this:
$ LC_ALL=C apt-cache policy libgtk-3-common libgtk-3-0
libgtk-3-common:
Installed: 3.20.4-1
Candidate: 3.20.4-1
Version table:
*** 3.20.4-1 501
501
http://httpredir.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
libgtk-3-0:
Installed: 3.20.4-1
Candidate: 3.20.4-1
Version table:
3.20.5-1 50
50
http://httpredir.debian.org/debian unstable/main amd64 Packages
50
http://ftp.debian.org/debian unstable/main amd64 Packages
50
http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages
*** 3.20.4-1 501
501
http://httpredir.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
Unstable mirrors seem to miss libgtk-3-common binary package even if it
belongs to the same source as libgtk-3-0 and tracker lists all
versions[1] also of libgtk-3-common. I'm observing this effect in my
pbuilder chroots since yesterday.
Any hint?
Kind regards
Andreas.
[1]
https://tracker.debian.org/pkg/gtk+3.0--
http://fam-tille.de