Hi Alexandru, The two changes in your proposed upload are good to include but I think it would be better if you had at least one material change (such as a bugfix) to justify the upload.
On Tue, Jan 20, 2026 at 09:04:42AM +0200, Alexandru Mihail wrote: > mini-httpd (1.30-16) unstable; urgency=medium > . > * Modify all patches headers to specify being forwarded via email to > upstream > by me. Upstream has no official git or mailing list, so I > established > by convention Forwarded: not-needed (sent by email; upstream > has no public tracker) > Upstream is rather slow, I forwarded everything and confirmed they > were > received anyway. This is good housekeeping but I would simply commit your updated DEP-3 metadata to your packaging repo and include with your next material upload. This is verbose; changelog entries should be succinct. Something like: * Mark all patches as forwarded upstream by email I think 'not-needed' is the wrong value for this field anyway. It's a freeform field so you could put the e-mail address to which you sent them, 'email', or simply 'yes'. > * Declare compliance with Standards-Version 4.7.3. > (Removed Priority from control). The new policy simply clarifies an already-relaxed requirement, that you can commit this field because a default applies - it does not necessitate a change that you have to make, so would itself not be a reason for an upload. The package tracker makes a lot of noise about standards version but you need to apply your own judgment too and not let the tail wag the dog! Andrew
