Hi Dhavan, Dhavan <dha...@protonmail.com> writes:
> On Monday, 10 July 2023 at 03:19, Nicholas D Steeves <s...@debian.org> wrote: > >> You've got this! :) You're already using a gbp (git-buildpackage) style >> git repository so this is very easy. Just use the Files-Excluded >> feature of debian/control, and run "gbp import-orig --uscan". > > I have finally pushed the update! Hopefully the package is built properly. Yay! Hopefully you tested that the package builds ;) Yes, I confirm that it appears to build fine on my system, but did you run lintian? I didn't investigate more deeply due to errors. > I have verified that docs are indeed excluded. Thank you for double checking. > I can update `Uploader` section as well to reflect my new working email, but > haven't pushed the change yet. Is it recommended that I do this(it probably > is)? As discussed previously a package whose human maintainer can't be reached at the email address specified in Uploader (or Maintainer for non-team packages) effectively doesn't have a human maintainer, so yeah, this will need to be updated, but... If you're working towards DM or DD privileges, and you only want to use one GPG key for future non-sponsored uploads (ie: if you want upload privileges) then you might want to reconsider the use of Proton Mail. I've been notified of the issue a couple of times, so started a discussion here to see what other people think: RFC: advise against using Proton Mail for Debian work? https://lists.debian.org/debian-devel/2023/11/threads.html To be clear, yes, it's OK to use this email provider in Uploader for sponsored uploads, and it works fine on the mailing lists :) You can wait until later for the rest, if you want, or you can start What I mean is that it can't be used for DM or DD uploads nor for voting. Meanwhile, I now see that you have a third address: https://salsa.debian.org/codingquark/elpa-lin/-/blame/debian/debian/control#L5 > Any specific things I should consider? Running lintian... E: modus-themes source: license-problem-gfdl-invariants invariant part is: with no invariant sections, with the front-cover texts being â??a gnu manual,â?? and with the back-cover texts as in (a) below [doc/modus-themes.info] E: modus-themes source: license-problem-gfdl-invariants invariant part is: with no invariant sections, with the front-cover texts being â??a gnu manual,â?? and with the back-cover texts as in (a) below [doc/modus-themes.org] E: modus-themes source: source-ships-excluded-file doc/doclicense.texi [debian/copyright:5] E: modus-themes source: source-ships-excluded-file doc/modus-themes.info [debian/copyright:5] E: modus-themes source: source-ships-excluded-file doc/modus-themes.org [debian/copyright:5] To be fair, it looks like your updated work wasn't pushed to salsa. Do you know about "gbp push" which pushes upstream branch+tag and pristine-tar? I: modus-themes source: out-of-date-standards-version 4.5.0 (released 2020-01-20) (current is 4.6.2) I: modus-themes source: repackaged-source-not-advertised [debian/copyright] You can use "lintian-explain-tags repackaged-source-not-advertised" or run lintian with "-i" or "--info" to learn about any of these. https://wiki.debian.org/DebianMentorsFaq#What_does_.2BIBw-dfsg.2BIB0_or_.2BIBw-ds.2BIB0_in_the_version_string_mean.3F Also, don't forgot to fix up the watch file to handle the repacked suffix. The solution for this is in the Debian wiki. > Thanks for the hints, those helped me be super quick about the things. You're welcome. I didn't provide a complete solution the mentorship process is supposed to cultivate problem solving, rather than checklist-following (ie: robot work). Some work should to automated though. For example, you should learn how to make lintian run automatically when you build a package. Best, Nicholas
