severity 714726 important merge 714726 509574 tags 714726 patch thank you This bug is almost 5 years old and has been duplicated several times: http://bugs.debian.org/509574
I'm fairly naive, but it looks to me that wheezy-backports doesn't report the suite correctly as stable-backports, and also wheezy-proposed-updates doesn't report Suite=stable-proposed-updates, as it obviously should according to the wiki: https://wiki.debian.org/StableProposedUpdates and the output I get: W: Conflicting distribution: http://http.debian.net stable-proposed-updates Release (expected stable-proposed-updates but got wheezy-proposed-updates) W: Conflicting distribution: http://http.debian.net stable-backports Release (expected stable-backports but got wheezy-backports) This is obviously broken. Symlinking repositories is more than fine (bind-mounting would be better), but Release files, if with different content, should be recreated always, obviously! Why couldn't this make it into wheezy-updates? Whoever is pinning, should be pinning Pin: release n=wheezy-backports or Pin: release a=stable-backports and not Pin: release a=wheezy-backports as I understood apt_preferences(5). Can somebody please shed some light on this? Why does suite vs. codename work for all other archive sources except stable-backports and stable-proposed-updates? What happened to codename rc-buggy? Experimental is not in line with the rest of the sources, missing it's toy like that. Can somebody please show me way to the source code where this bug manifests? ... Ok, I hacked a little what may be correct. It is the same hack by Mark Hymers, just extended for the missing archives. Is there any reason not to push this to mirrors now? :-)
dak-correct-suite.patch
Description: Binary data
