If a dependency or a 'Required By' package is in [testing] or [community-testing] it's marked as such e.g. 'foo (testing)'.
pygtk 2.24.0-3 is in [extra] and should depend on packages in [extra]. One if its dependencies, pygobject2-devel, is both in [extra] and in [testing] http://www.archlinux.org/packages/?sort … =&limit=50
pygtk should depend on the one in extra and pacman pulls it all right, but according to the web interface http://www.archlinux.org/packages/extra/i686/pygtk/ it depends on the one in testing. When you click (or mouse over) on 'pygobject (python2-gobject2)' you go to http://www.archlinux.org/packages/testi … -gobject2/ even though it's not marked as a [testing] package.
Why is it so? Is it a bug?
Probably a bug - bug report?
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
It may be a glitch related to package foo providing bar, like systemd providing libsystemd.
Another example of a package in [extra] depending on a package in [testing] instead of the one in non-testing repo: http://www.archlinux.org/packages/extra … tsservice/
accountsservice 0.6.25-1 depends on systemd 194-4 instead of systemd 194-3.
Bug reported: https://bugs.archlinux.org/task/32018