On Tue, Mar 24, 2026 at 11:20:06AM +0100, Andrew Lee wrote: > On Tue, Mar 17, 2026 at 1:30 AM Federico Grau <donfede@casagrau.org> wrote: > > Pardon the sloppy efforts here, I'll aim to improve. > > No worries. We all learnt that from our mistakes. Please remember to > do merge request next time then. > > I quickly check the commit history. I saw you have a commit to updated > debian/changelog earlier than commits. And debian/changelog didn't > included your later commits for refresh exist patch for 0.19.2-1 > release. Is this something you intend to not included the later > commits and hold for future 0.19.2-2 release? > Thanks for the review Andrew -- We may be getting too deep into transaction details with the Git commits. The d/changelog commit (35edc1f) I created was meant to represent the work I completed that weekend for this update to `pat' v0.19.2 . It happens I committed the d/patches a few minutes after the d/changelog commit. The d/patches I updated only include the new upstream version in man pages and upstream changelog... I have now updated d/changelog for release 0.19.2-2, mentioning the minor d/patches edits. Note: given this minor change with no questions on my part, I did not create a MR for this effort. Hopefully we can get this release of pat 0.19.2 into unstable. Looking ahead, I see pat was recently "Marked for autoremoval on 25 April due to golang-github-howeyc-gopass: #1130525". I will submit a bug/issue upstream noting this risk, but ideally pat can remain in debian while upstream adapts. Regards, donfede Fede Grau
Attachment:
signature.asc
Description: PGP signature