Phil Hagelberg, On Tuesday, August 6, 2024 9:51:20 AM MST Phil Hagelberg wrote: > I'm a little confused why the lintian results you've provided are so > different from what mentors.debian.net has shown. Is the mentors upload > process using an outdated version of lintian?
Yes, unfortunately mentors runs an older version of lintian (I believe it runs lintian from stable). For the most accurate information, you want to run lintian from unstable. https://tracker.debian.org/pkg/lintian If you setup sbuild using the following instructions and include the lintian option, it will run lintian from unstable whenever you build you package locally: https://wiki.kathenas.org/pmwiki.php/Kathenas/Article00000002 > > E: fennel source: source-ships-excluded-file style.md [debian/copyright:5] > > > > mk-origtargz(1) is typically responsible for removing such files. > > Support in git-buildpackage is being tracked in Bug#812721. > > Yeah, it sounds like gbp doesn't do this yet unfortunately. > > I will see if I can get gbp to pull from a branch where this deletion > has already been committed manually in git instead of relying on it to > filter out the pristine-tarball. It should handle it (it does for the electrum package). Are you running `gbp import-orig --uscan`? > > W: fennel: groff-message troff:<standard input>:1003: warning: cannot > > select font 'C' > > Looks like this is a bug in pandoc; I've added a workaround upstream: > > https://git.sr.ht/~technomancy/fennel/commit/ f83dd129a3100d53f5e3545ca45da14ba > 340a6d7 > > I will ignore this in the debian packaging for now since it's just a > warning and it will be fixed in the next release, if that's OK. The FTP masters might or might not let this through (they often don’t like lintian errors or warnings, but they let some lintian info tags slide, and pedantic and experimental tags are generally left up to your discretion). The easiest way to handle it is to add a patch to debian/patches that cherry-picks your upstream commit, and then remove the patch with the next release. > > 5. Build Twice [sudo pbuilder build --twice <package>.dsc]: Issue > > This appears to be an issue where `dh_auto_clean` fails to recognize the > fact that my Makefile has a "clean" target that it needs to run. I can > work around this by adding this to debian/rules: > > execute_after_dh_clean: ; $(MAKE) clean > > But if there's a better solution I'm all ears. =) The man file for dh_clean says: 'It does not run "make clean" to clean up after the build process. Use dh_auto_clean(1) to do things like that.’ https://manpages.debian.org/jessie/debhelper/dh_clean.1.en.html -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
