[Barry Warsaw, 2011-09-08] > >* build directory is not removed in clean target (and thus package > > cannot be build twice in a row) this one is fixed, but now I get changes in SOURCES.txt which includes... .txt files in debian/python-flufl.lock/usr/lib/python2.7 (due to "global-include *.txt" in MANIFEST.in) > This is because dh_auto_clean does not remove the build/sphinx directories. > Adding an override_dh_auto_clean target which `rm -rf build/sphinx` does the > trick. However, I wonder if this is something that `--with sphinxdoc` should > help with? If so, I'm willing to at least file a bug. If that's the standard build directory for Sphinx, then sure, --with sphinxdoc could remove it; ping Jakub about it > >E: python-flufl.lock: helper-templates-in-copyright > > Okay, I removed the "(s)" but this one seems bogus for several reasons. > First, the lintian warning really doesn't tell you what's wrong with your > debian/copyright file, so you're left to guessin' 'n googlin'. Second, > debbug #631674. wasn't 631674 fixed a month ago? BTW, you did invoke lintian with -i option (or `lintian-info --tags helper-templates-in-copyright`), right? It's a little bit more verbose. [...] > >W: python-flufl.lock: duplicate-changelog-files > >usr/share/doc/python-flufl.lock/changelog.gz > >usr/share/doc/python-flufl.lock/html/_sources/NEWS.txt.gz > > I'm not getting this one now. Maybe it's due to the other changes I'm about > to commit. Please let me know if you still get this. yep, NEWS.txt.gz is now a symlink to changelog.gz thanks to dh_installchangelogs' "-k flufl/lock/NEWS.txt" option in your debian/rules new problems (or the ones I missed last time): * documentation files (*.txt *and* conf.py file) are now in dist-packages * both flufl.lock-2.1.1.egg-info and flufl.lock.egg-info files are installed - get rid of one of them * flufl.lock-2.1.1-nspkg.pth is not really needed (I think I will add an option to dh_python2 to remove .pth files, I cannot do that by default, though) * what's the purpose of empty flufl.lock.docs module (and using.txt in the directory with __init__.py)? [...] > >PS feel free to reply in private > > Thanks. I hope you don't mind me replying publicly not at all. It's just that people ask more questions in private and I prefer questions rather than "hiding" problems (if you will not ask, I might miss it). Please don't CC me if you reply to a mailing list that I'm subscribed, though. TIA [...] > Anyway, thanks for the great feedback, and apologies for taking so long to > respond. it's not a record at all, I'm still waiting for a response to my "libc/ctypes problem" reply to one of sponsorees from... 9th May 2009 - my Debian/RFS contains lots of threads waiting for sponsorees (and in few seconds: none waiting for me, yey! :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Attachment:
signature.asc
Description: Digital signature