Hi, I'm a bit desperate to find out how the Debian project maintains its patches w.r.t. upstream repositories. Thus, while I can explore the _current_ patches of a package by looking at the "*.debian.tar.gz"-archive after obtaining its sources through "apt-get source <package-name>", I'd be rather interested in both history and future of these patches along the lifetime of a Debian releases' maintainance period.
At the first glance, things look quite straight forward: Starting with, say, the "glibc"-package, an "apt-get source glibc" tells me that I may get the git repo of the related Debian patches by cloning https://anonscm.debian.org/git/pkg-glibc/glibc.git. But as it turns out, this (and some other Debian) hosts went offline as they are being replaced by https://salsa.debian.org. So I finally get what I am looking for by cloning https://salsa.debian.org/glibc-team/glibc.git. Great. Getting rather encouraged by that, I tried to find the repo for the "binutils" patches. Again, "apt-get source binutils" tells me that I should get it from http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian. And again, http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian is gone. But this time, I couldn't find a substitute on https://salsa.debian.org. Further looking around, it seems that there are still quite a few (if not most!) packages still missing on https://salsa.debian.org, although this transition was, as I recall, supposed to be completed by the end of Mai 2018. So finally, here is my question: When may I expect that VCS-repositories for all Debian packages may be available through https://salsa.debian.org (including updates of the packages to point to the new repository location on https://salsa.debian.org as printed by "apt-get source") and what could I do in the meantime w.r.t. packages like binutils, which are obviously gone from their old place, while they are still not available on https://salsa.debian.org? Many thanks for any insight on that topic, Chris
