Jan de Groot wrote:
Well, usually, when a basic package like a codec where >15 packages depend on has a sobump, these packages go to testing first to give developers chance to rebuild. If they go to current directly instead, the packages that depend on it should be rebuilt during the same run of db-extra/db-arch. Wasn't this one of the reasons we have testing?
How do you know that >15 packages depend on this? It seems to be it would be really good to have something on the website where we can query all packages that depend on another package, recursively. Otherwise I don't see how we can expect people to divine this information. I've been told various things about different [testing]. In this case, it seemed like the upgrade and the email would allow those needing to rebuild time to do it without significant trouble. Anyhow, as I've said, I'm happy to conform to any identifiable documented guidelines we agree upon, or to consider suggestions to do things differently. - P