On Wed, 2011-08-31 at 20:14 +0100, Iulian Udrea wrote: > Dan Doel has just uploaded vector-algorithms 0.5.3 with the following > dependencies: primitive (>= 0.3 & < 0.5), vector (>= 0.6 & < 0.10). I'm > updating the remaining packages now. What is the best practice for upgrading packages that are dependencies of other packages? In this case, if we upload vector, then we have to upload the newest version of primitive (0.4.0.1) and then either upgrade (if there are new upstream releases) the rest of the packages that have as dependencies primitive or vector or binNMU them. Should we wait for a transition to happen and then upgrade them or go with scheduling binNMUs (for packages that don't have newer upstream releases) so that we won't end up with broken packages in the archive. I'd appreciate it if someone could enlighten me a tad about this. Cheers, -- Iulian Udrea iulian@linux.com
Attachment:
signature.asc
Description: This is a digitally signed message part