Didjvu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, I am working on packaging Jakub Wilks's Didjvu. That is a smart little DjVu encoder employing the Gamera framework (python-gamera) for automatic foreground mask generation which drastically improves the workflow towards document scanning / creating of ebooks (cf. bug #601781). I am beginning maintainer / Debian Python packager so I would be thankful for any pointers. I've read towards RFA Python modules that they have to stay under the DPMT umbrella for at least 12 months. What does that mean? Greetings, Daniel Stender https://alioth.debian.org/users/danstender-guest/ http://www.danielstender.com/granthinam/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzK/CoACgkQU8fCMhZUvZysTQCfXciLV0BJqYRZjleCijr6uHM+ LqcAoMGBWTI6EsvXVjCeqK9XTX4B9Spl =nADH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ccafc2a.7020...@danielstender.com
RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Hi people, I'm kindly asking for overchecking/uploading of the following packages: /python-apps/packages/didjvu/tags/0.2.1-1/ initial release of 0.2.1 /python-apps/packages/djvusmooth/tags/0.2.8-2/ /python-apps/packages/ocrodjvu/tags/0.4.6-3 closes important bug #600539 in testing /python-apps/packages/pybtex/tags/0.14.1-1 new upstream release All packages are lintian clean. Thank you very much in advance, Daniel Stender -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd442c6.50...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Thanks Stefano for checking the packets and for the precious pointers (for most
of the issues it's
hard to find comprehensive documentation).
On 05.11.2010 20:46, Stefano Rivera wrote:
As a not-yet-DD I can't upload, but here's a review.
First, we don't tag releases until they are uploaded. You can leave the
changelog entry as UNRELEASED, and the sponsor will fix that and tag on
upload.
I was following maint-guide 4.3 with that: distribution should be either
unstable (or even
experimental) [16] - but I was wondering about this anyway. Thanks for the
pointer! I've fixed that
for all packages.
/python-apps/packages/didjvu/tags/0.2.1-1/ initial release of 0.2.1
Depends: ${misc:Depends}, ${python:Depends}, python-imaging, libdjvulibre21
(= 3.5.21), python-argparse
I'd suggest wrapping that (after every comma is quite neat).
argparse is part of the standard library in Python 2.7. A dependency on
python (= 2.7) | python-argparse is probably preferable.
Allright.
The description could probably be broken into a couple of shorter
paragraphs.
Mhmm, too long? o.k.
debian/copyright mentions jwilk, but not you. You should state the
licencing of your packaging.
Didn't get it. It says: This work was packaged for Debian by Daniel Stender
and also states the
license of both the upstream and the packet. I was following again maint-guide
(5.2) with details.
Also, you BD on debhelper = 7, but use an override, which requires
debhelper = 7.0.50~.
Fixed.
debian/rules: Not a fan of dh $...@?
I'm guessing you misunderstood my message on this topic, as you are
totally avoiding the setup.py and using dh_install + dh_link to install
files.
I think the following debian/rules will do what you want (and you won't
need debian/install or debian/links any more):
#!/usr/bin/make -f
%:
dh $@
override_dh_auto_install:
dh_auto_install -- --install-lib /usr/share/didjvu
Yes, great! I've got problems with dh $@ that without the lib path the
modules were considered to
be public, now it works. But without my links the executeable resides in
/usr/share/bin, isn't that
substandard?
For new packages, you should probably consider using dh_python2 instead
of python-support. The eventual plan is to migrate all Python packages
to it.
Yes definitely. I've followed Piotr's presentation at debconf 2010 on this. I
would like to to put
that on the agenda for further work on that.
/python-apps/packages/djvusmooth/tags/0.2.8-2/
Predates you, but djvusmooth is a graphical editor for DjVu
files, which allows to: isn't correct English grammar. ...which allows
one to would be better.
Fixed.
You probably want to add yourself to debian/copyright (even if you
haven't made any significant modifications yet). This applies to all the
packages.
Ah yes sure ... just overseen it. Fixed everywhere.
/python-apps/packages/ocrodjvu/tags/0.4.6-3 closes important bug
#600539 in testing
My previous argparse comment still applies, but this is aimed at squeeze
which doesn't have python2.7, so you don't need to do this yet (but
consider it for the trunk, please).
Allright.
/python-apps/packages/pybtex/tags/0.14.1-1 new upstream release
I see some trailing whitespace in debian/changelog.
Mixed tabs and spaces in debian/postinst (naughty jwilk)
All fixed and refreshed (so, everything else seem to be alright I'll guess).
Please, one more towards the procedure of updated already tagged stuff: svn
commit or again
debcommit? Then svn copy /trunk /tags/0.2.1-1?
Greetings,
Daniel Stender
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd52422.2000...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
All refreshed. How do I update tags? Svn copy (/trunk /tags/foo) says permission denied. Thanks for all pointers, Daniel Stender On 06.11.2010 11:15, Stefano Rivera wrote: Hi Daniel (2010.11.06_11:47:14_+0200) argparse is part of the standard library in Python 2.7. A dependency on python (= 2.7) | python-argparse is probably preferable. Allright. I suppose that's not necessary, Jakub had a good point that python will probably provide python-argparse when 2.7 is the default version. That appears to be how previous transitions (without renames) into the stdlib were handled. Didn't get it. It says: This work was packaged for Debian by Daniel Stender and also states the license of both the upstream and the packet. I was following again maint-guide (5.2) with details. I'm saying you should add something like: | The Debian packaging is (C) 2010, Daniel Stender | dan...@danielstender.com and is licensed under the GPL v2, see above or use DEP-5, with a Files: debian/* section. Your Licence block looks like it was copied from another debian/copyright file that used DEP5. http://dep.debian.net/deps/dep5/ Yes, great! I've got problems with dh $@ that without the lib path the modules were considered to be public, now it works. Well, it installs, as Jakub also pointed out, you'll need a patch or your own wrapper to get Python to find the private module. But without my links the executeable resides in /usr/share/bin, isn't that substandard? Hmm, I don't see that, but you haven't committed your changes to the repo yet, so I can't look at the code you are working with. Please, one more towards the procedure of updated already tagged stuff: svn commit or again debcommit? Then svn copy /trunk /tags/0.2.1-1? I debcommit when I've made changes to debian/changelog (i.e. when I first make a change). If I have to go back and fix something which hasn't been published yet, then there won't be a changelog entry, so I have to provide my own commit message with svn commit. SR -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd54a6f.6060...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Another problem:
To give XS-Python-Version: = 2.6 together with ${misc:Depends},
${python:Depends}, python (=
2.7) | python-argparse in debian/control results in an INFO file in the
deb-packet which contains:
Depends: python (= 2.6), python (= 2.7) | python-argparse
On 06.11.2010 14:16, Stefano Rivera wrote:
Hi debian-python (2010.11.06_12:15:18_+0200)
Well, it installs, as Jakub also pointed out, you'll need a patch or
your own wrapper to get Python to find the private module.
Or the obvious solution, your previous one (and the one used by
the other packages in this set), to use a symlink to the wrapper, which
you put in /usr/share/didjvu.
didjvu is missing a dependency on python-gamera.
Files: debian/*
-Copyright: 2009, 2010 Jakub Wilk jw...@debian.org
+Copyright: 2010 Daniel Stender dan...@danielstender.com
I don't think you should forget Jakub, just add yourself.
Otherwise no issues I can see.
SR
--
http://www.danielstender.com/granthinam/
GPG key ID: 1654BD9C
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd58899.3020...@danielstender.com
Re: Debhelper: LDFLAGS
... ups, misleaded. Please excuse. On 19.12.2010 21:04, Daniel Stender wrote: If we are still talking about the gummi package, I just put export LDFLAGS=-Wl,--as-needed at top of debian/rules and the dpkg-shlibdeps warnings went away. ... does it? What I am missing here? Dan -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e6627.6020...@danielstender.com
Re: Debhelper: LDFLAGS
If we are still talking about the gummi package, I just put export LDFLAGS=-Wl,--as-needed at top of debian/rules and the dpkg-shlibdeps warnings went away. ... does it? What I am missing here? Dan -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e6555.5030...@danielstender.com
RFS: didjvu, djvusmooth, pybtex
Hi guys, I would like to refresh the RFS for the following packets: didjvu 0.2.1-1 - initial release djvusmooth 0.2.8-2 - maintainer switch, standards bumped to 3.9.1 pybtex 0.14.1-1 - new upstream release Everything is at: http://svn.debian.org/wsvn/python-apps/packages/ I would say that everything is ready for upload. Towards e-documenting relating Python stuff I am also working on python-djvulibre but that needs some more days. Thanks in advance for any care for consideration, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2c1d86.3040...@danielstender.com
Re: RFS: didjvu
All right, all fixed. Thanks for checking!
Daniel
On 06.02.2011 14:35, Stefano Rivera wrote:
Hi Daniel (2011.02.06_12:26:28_+0200)
I've converted didjvu to dh_python2 now, could anybody please check it
over again? Any hints welcome!
Looks fine. A couple of minor things:
Might as well use X-Python-Version instead of XS, as it's available in
python 2.6.6-3.
I like using Breaks: ${python:Breaks}. It separates the Python version
dependencies out of Depends.
The --with should come after $@:
dh $@ --with python2
The DEP5 copyright file doesn't include a revision in the Format.
SR
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d4ecfd2.9090...@danielstender.com
RFS: pybtex
Hi guys, I would like to refresh my request for sponsorship towards Pybtex 0.15-1 after RFA. Please check it as usual at Alioth: http://svn.debian.org/wsvn/python-apps/packages/pybtex Any review welcome. Sponsors in favour of Python_dh2 as always welcome ;-) (get you chat ready then for a session). Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d7f89d7.90...@danielstender.com
Re: RFS: pybtex
Hi people, I would like to refresh my RFS for Pybtex. Isn't there anybody with a little time ...? Greetings, Daniel Stender On 15.03.2011 16:46, Daniel Stender wrote: Hi guys, I would like to refresh my request for sponsorship towards Pybtex 0.15-1 after RFA. Please check it as usual at Alioth: http://svn.debian.org/wsvn/python-apps/packages/pybtex Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac4d97.50...@danielstender.com
RFS: python-djvu ocrodjvu
Hi guys, Jakub would like to get rid of the maintenance of these packets, has anybody a couple of minutes and would be so nice to review my latest packings of python-djvulibre (0.3.3-1) and ocrodjvu (0.7.1-1) ... both packets are building fine. Python3-ing the Djvu bindings needs some more time to get deeper into things, I would like to go for that towards 0.3.3-2. Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de291d7.2010...@danielstender.com
Re: pybuild and proxies -- could we make prohibition optional?
On 22.07.2015 15:45, Yaroslav Halchenko wrote: On Wed, 22 Jul 2015, Piotr Ożarowski wrote: [Yaroslav Halchenko, 2015-07-21] As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings ah, sorry, I only quickly scanned you email. I already followed Dimitri's suggestion to add no_proxy=localhost and will add your PYBUILD_FAKE_PROXY later today awesome! feel free to tune the name to whatever you feel more appropriate. Just an additional piece of support to allow simply disabling automatic assignment of fake proxies and that no_proxy doesn't work for some libs/packages: Daniel Stender tried export no_proxy=localhost on pytest-tornado without success. ... pytest-localserver currently (in the multiple package dep solving approach for vcr.py), dh-python 2.20150719. DS -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55afa0ec.5070...@danielstender.com
Re: Git migration schedule pushback permissions/DEP-3 workflow
On 08.10.2015 17:06, Stefano Rivera wrote: > Hi Barry (2015.10.02_16:24:28_+0200) >> 8-Oct - Assuming no objections or showstoppers, turn off write access to all >> of DPMT svn. > > Done. And kicking off the migration now... > > SR Thanks for the work, things likes automatically updated Vcs fields are much appreciated. Git-dpm patching appears to be great with features like auto-dropping of patches applied by upstream, that's much better than Quilt. Exploring ... I've got a push back error here: $ git push Counting objects: 22, done. Delta compression using up to 4 threads. Compressing objects: 100% (21/21), done. Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done. Total 22 (delta 12), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc-py.git ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc-py.git' Question: When new patch has been installed after it misses a DEP-3 compliant header. I've now edited debian/patches/0001-foo.patch for that and made another commit on master. Is there a better/another workflow for this? Thanks DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: Git migration schedule
Hi, these old SVN repos could be spared and removed: On 03.10.2015 20:52, Stefano Rivera wrote: > The errors: > > Cannot "git-dpm init" package: gamera is already in: git://anonscm.debian.org/python-modules/packages/gamera.git > Cannot "git-dpm init" package: nltk old/obsolete packaging, the initial Debian package was uploaded for Debian Science > Cannot "git-dpm init" package: svg.path got into: http://anonscm.debian.org/cgit/python-modules/packages/python-svg.path.git before the initial upload and > Cannot "git-dpm init" package: pyuca ... is currently in NEW. I'll convert that manually. Cheers, DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: git repo lint tool
On 13.10.2015 16:30, Stefano Rivera wrote: > Daniel Stender <deb...@danielstender.com> >deap >gamera >greekocr4gamera >ocr4gamera >pep8-naming >pylint-celery >pylint-common >pytest-catchlog >pytest-localserver >pytest-tornado >python-djvulibre >python-requirements-detector >python-setoptconf >python-subprocess32 >python-xmp-toolkit >vcr.py All of these packages were in /git/python-modules/packages/ already before the migration, a couple have been migrated manually from SVN to Git some months before, for the other part (new packages) the packaging have been started already on/in Git. I've now restored the repos like suggested in the GitPackaging wiki page (Post-migration clean up), and there are all going to be configured for git-dpm patching in the course of the next days. In all packages, Vcs points to Vcs-Git: git://anonscm.debian.org/python-modules/packages/.git Vcs-Browser: http://anonscm.debian.org/cgit/python-modules/packages/.git Best, DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: git repo lint tool
On 13.10.2015 17:57, Stefano Rivera wrote: > Hi Daniel (2015.10.13_17:47:01_+0200) >> In all packages, Vcs points to >> Vcs-Git: git://anonscm.debian.org/python-modules/packages/.git >> Vcs-Browser: >> http://anonscm.debian.org/cgit/python-modules/packages/.git > > The linter script wants https for Vcs-Browser. > > SR Ah, o.k.! :-) I'll fix this, too. Thanks, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: pep8 python module is now in python-pep8 - triggers FTBFS
On 10.03.2016 12:10, Edward Betts wrote: > I checked a few of these, in detail: > > - fix for fuzzywuzzy uploaded > - bug filed for blockdiag > - fix for django-sekizai pushed to git, e-mailed uploaders Prospector: fixed. DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: static analysis and other tools for checking Python code
On 03.03.2016 01:38, Paul Wise wrote: > On Thu, Mar 3, 2016 at 7:52 AM, Jeremy Stanley wrote: >> ... > > All of flake8, hacking, bandit, pep257, clonedigger and more are on > the TODO list: > > https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/tree/data/python > > FYI pep257 is definitely packaged: > > https://packages.debian.org/search?keywords=pep257 > >> I can probably think up more that I've used, but the above rise to >> the top of my list. > > More suggestions would be useful but most useful would be actual > tests. They are very simple to add if you know how to run the tools. BTW there's also Prospector which provides a uniform interface to many individual linters: https://packages.qa.debian.org/p/prospector.html Cheers, DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: pypi2deb 1.20160809 and --profile dpmt
On 09.08.2016 21:27, Piotr Ożarowski wrote: > Hi, > > FYI: I just uploaded pypi2deb 1.20160809 which initializes all the git-dpm > stuff if you invoke py2dsp with --profile dpmt option > > example: > > $ py2dsp --profile dpmt django > [...] > I: to create repository on git.debian.org: > ssh git.debian.org -c 'cd /git/python-modules && ./setup-repository > django "django packaging"' > I: to push (after reviewing all files) changes to DPMT's repo: > git push --set-upstream origin --all > [...] > $ cd result/django-1.10/ > $ git branch -a > * master >pristine-tar >upstream > $ git remote -v > origin ssh://git.debian.org/git/python-modules/packages/django.git (fetch) > origin ssh://git.debian.org/git/python-modules/packages/django.git (push) On this occasion ... let it be me to start the discussion: let's get into Git also for Python Apps soon. DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: PAPT git migration
On 31.05.2017 20:58, Stefano Rivera wrote: > It's been a while, but I found some time and energy at PyCon, to work > our SVN->Git migration. > > I started with our DPMT migration script, pulled out the git-dpm bits, > and fixed the obvious issues I saw. > > Here's what the migration currently looks like [0]. > > [0]: https://anonscm.debian.org/cgit/users/stefanor/python-apps/ > > This is after several rounds of migration, and fixes to both the SVN > repo, and the migration script. Below are the notes I made during the > rounds of migration. I haven't re-reviewed every package, after fixing > it, only a couple of spot checks. The first round was ta revision 13997, > and the final one (published at [0]) was at revision 14089. > > And this is the migration script: > https://anonscm.debian.org/cgit/users/stefanor/dpmt-migration.git/ > > Does that look reasonable? Should we do this? > > SR +1 pybtex has been moved to Debian Science. BTW, the fix of #833469 from svn-buildpackage (copy .asc file together with tar) is needed to avoid problems with the error message "orig-tarball-missing-upstream-signature" from Lintian 2.5.52. DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Some pytest related packages on RFA
Hi, I have some pytest plugin packages for which I'm seeking an adopter for: 1) pytest-catchlog (https://bugs.debian.org/868844) https://packages.qa.debian.org/p/pytest-catchlog.html 2) pytest-httpbin (https://bugs.debian.org/868845) https://packages.qa.debian.org/p/pytest-httpbin.html 3) pytest-localserver (https://bugs.debian.org/868846) https://packages.qa.debian.org/p/pytest-localserver.html 4) pytest-tornado (https://bugs.debian.org/868847) https://packages.qa.debian.org/p/pytest-tornado.html 5) pytest-xdist (https://bugs.debian.org/870844) https://packages.qa.debian.org/p/pytest-xdist.html Greetings, DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Re: python logo.
On 03/06/2018 06:38 AM, Peter Green wrote: I am looking into cleaning up some software so it can be uploaded to Debian. Inside the documentation folder is a copy of the python logo. I found the python.org page for the logo more confusing than helpful. 1. Is the python logo under a license acceptable for including in a Debian package? or does it need to be stripped out? 2. If it is acceptable for inclusion how should it be documented in debian/copyright? See https://lists.debian.org/debian-legal/2015/03/msg2.html DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
