On Tue, 2022-08-23 at 16:59 -0500, Steven Robbins wrote: > The binary upload cannot transition to testing -- a buildd binary build is > required. So far as I know -- assuming [1] is still up-to-date, this means a > nuisance upload just bumping the debian revision from -1 to -2. Is this still > the recommended practice? The release team automatically do binNMUs for packages that need a rebuild to transition to testing and are able to be binNMUed, so for many packages you don't need to worry about this. If for some reason they don't do this or for arch:all packages, you need to reupload. Usually I use this as an opportunity for some extra package polish. The patch for dropping NEW binaries has been in dak for two years but its configuration options were never enabled by ftp-master so far. Dinstall::ThrowAwayNewBinarySuites Dinstall::ThrowAwayNewBinaryComponents > I've also been wondering about the "Give Back" action button on the buildd log The give-back action is only for failed builds, not successful ones. For successful builds you need a binNMU or new source version. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part