Manphiz <manp...@gmail.com> writes: > Nicholas D Steeves <s...@debian.org> writes: >>> Nicholas D Steeves <nstee...@gmail.com> writes: >> > > Should have removed the redundant signatures and reuploaded to > https://keys.openpgp.org, though I don't think I had 5 signatures on the > same IDs? Anyway, PTAL.
Web interface: keys.openpgp.org Error: No key found for email address manp...@gmail.com $ gpg --search-keys manp...@gmail.com gpg: data source: https://keys.openpgp.org:443 gpg: key "manp...@gmail.com" not found on keyserver gpg: keyserver search failed: Not found Strictly speaking, you don't need to worry about your key until you start wanting to make uploads (mentors, Debian Maintainer per-package upload privileges, Debian Developer uploading), so we can defer this. >> What is your intention here? Are you rebasing our package onto this >> fork, or are you using the fork as a code dump, or something else? >> > > Well to be honest I didn't realize the github one was a fork as the > d/watch file had been pointing there. "git blame debian/watch" to see who is to blame, and fix fdde4981, which introduced this problem. This is a blocker to uploading the package. > Also from your other mail: Thank you for merging these emails. >> I found that this UTF8 issue was already fixed upstream: >> >> @@ -412,11 +433,11 @@ >> >> https://git.savannah.gnu.org/cgit/emacs/elpa.git/commit/?h=externals/muse&id=be347db7f1ad56f0384f76011bfd148ff3352610 >> >> and note that it's now an official GNU project (via copyright assignment) >> >> Copyright (C) 2004-2020 Free Software Foundation, Inc. > > So it should be clear that the Savannah one should be considered the > canonical upstream. I'll update my question on github to ask for > whether Alex want to forward the patches in his repo to Savannah as > well. Thanks. > Also as a result, I've marked the patch as "Forwarded: not-needed". Thank you. Alternatively you can either cherry pick the upstream commit (and export as quilt patch) and drop mine, or package a new upstream snapshot from the savannah source, since that's what we're tracking. >> Oh, there's one more thing that needs to be fixed before we upload: >> Bug #1048114 > > Attempted to fix it in [2] where I just regenerated the changing file in > sbuild. > > [1] https://github.com/alexott/muse/issues/16 > [2] > https://salsa.debian.org/emacsen-team/muse-el/-/commit/f5c217162d9c6f45c971cec2b8c70b2794bb77fe This doesn't look like the right approach to me, the changelog entries related to it are unclear/misleading, and a description is missing in the patch header. Have you checked Savannah for a fix? Rather than a Debian-specific approach, it's best to stay close to upstream source whenever possible. If the issue is truly Debian-specific, then why not use dh_auto_clean or dh_clean, or another cleaner method? Thank you for your attention to detail. We're just about done! Regards, Nicholas
signature.asc
Description: PGP signature
