On Sat, 2017-07-29 at 14:24 +0200, Sandro Knauß wrote: > Hey, > > > currently in stretch is 4:16.04.3-3. Thus the version which should > > preferably be used would be 4:16.04.3-3+deb9u1. > > just to understand the process better: > * Do I need to send another debdiff with the corrected versionnumber first > before uploading?
If by that you mean taking the previously incorrectly generated diff and simply changing the version number it contains, then no. > * Do I need to close this bug within the changelog entry? No. The bug will be closed by us once the package is actually in stable. Until that point, the process is incomplete, so closing the bug would be illogical. > * Are there any further issues with my debdiff? Besides not being what has been requested multiple times? The point of the process is to demonstrate that you can build - and have built - your proposed upload against the release that you're proposing to upload it to and to confirm what the debdiff of the resulting package against the target release looks like. It's entirely possible that it will be the same as the diff between the stable and testing packages that you previously provided. That's by no means certain, however, and in any case diffing things that aren't what you're proposing to upload misses the point of the review step. This isn't theoretical nitpicking. We've seen there be a distinct difference between what people propose and what they actually upload enough times in the past that there's no way we'll agree an update based on a hypothetical diff rather than an actually built and tested one. Regards, Adam
