Followup-For: Bug #901936
Ok, fair enough. That is actually smart to not mirror debug symbols by default to all mirrors, and create debug package automatically out of compiled binaries in standarized way. However... But before reporting I checked: https://packages.debian.org/source/sid/chromium-browser https://packages.debian.org/source/buster/chromium-browser https://tracker.debian.org/pkg/chromium-browser https://tracker.debian.org/news/964307/accepted-chromium-browser-670339679-2-source-into-unstable/ https://buildd.debian.org/status/logs.php?pkg=chromium-browser&arch=amd64 https://packages.qa.debian.org/c/chromium-browser.html https://packages.debian.org/search?searchon=sourcenames&keywords=chromium-browser and none of them show any mention of debug symbols or links to packages for buster or unstable. https://packages.debian.org/search?suite=buster&arch=amd64&searchon=names&keywords=chromium-dbgsym is also empty. When looking at suite option, there are -backports, but no -debug or anything like that. Thechnically automatically crated debug symbol package are normal deb packages, just in different repo. Feel free to reassign to qa.debian.org , tracker.debian.org , or who ever is more relevant for this problem. Thank you! Witold
