Hello Nicholas, > They're about the same for me. Honestly I'd prefer to do a git upload > at this time, and save the GPG key discussion for your next upload. > We can use dput and mentors then, and I think we'll both agree that > we've both worked hard enough for this first upload haha. Indeed, it was quite a lot of work, but it is for a good cause ! :) > At this point, please do a "dch -r" and ensure that the changelog entry > is refinalised; this will update the date stamp. Hint: you may have to > make do a noop edit like <space>+<backspace> to make this work properly. > Commit the new changelog entry with a message like: > And push that to the remote we're using for your MR. Then make an > annotated and optionally GPG signed tag. I like to use "gbp tag" for > this, but you can use whatever method you prefer. Please make sure > the annotated tag is on the master branch and not a detached head. > Let me know, and I'll review, and upload when everything looks good, > as it no doubt will. I've commited and pushed the changes to the remote I was using for the MR so far: commit: https://salsa.debian.org/alexandru_mihail/mini-httpd/-/commit/fc7c4f664dc1369b1bf5d46c8c9b7aa11de68407 But I think I may have not commited where I was supposed to, granted you've already closed the MR. I've already created a GPG signed tag accessible at: https://salsa.debian.org/alexandru_mihail/mini-httpd/-/tags/debian%2F1.30-4 The commit is not visible in the previous MR: https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2? Is there something I've glanced over here ? Otherwhise, the commit & tag are per your requirements. > Cheers, > Nicholas Have a great day ! Alexandru Mihail
Attachment:
signature.asc
Description: This is a digitally signed message part