Re: -dbg packages
[Vincent Bernat, 2011-08-10]
> I remember a discussion about dh_python2 supporting -dbg packages
> here. Therefore, I was thinking that it could handle some steps, like
> dependencies (in ${python:Depends}) and install (keep only debug files).
dh_python2 cleans -dbg packages (unless invoked with --no-dbg-cleaning)
and adds dependencies to ${python:Depends}, yes
--
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
--
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/20110810083941.gl16...@piotro.eu
Re: -dbg packages
* Piotr Ożarowski , 2011-08-10, 10:39:
I remember a discussion about dh_python2 supporting -dbg packages
here. Therefore, I was thinking that it could handle some steps, like
dependencies (in ${python:Depends}) and install (keep only debug
files).
dh_python2 cleans -dbg packages
What do you mean by "clean"?
(unless invoked with --no-dbg-cleaning)
Uh? My dh_python2 doesn't have such option.
and adds dependencies to ${python:Depends}, yes
What exactly it puts into python:Depends? I know it puts -dbg
interpreter there, but what about stuff from requires.txt?
Also, it means that you should use "Recommends: ${python:Depends}" for
your -dbg package. Yay.
--
Jakub Wilk
--
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/20110810093641.ga1...@jwilk.net
Re: -dbg packages
[Jakub Wilk, 2011-08-10]
> * Piotr Ożarowski , 2011-08-10, 10:39:
> >>I remember a discussion about dh_python2 supporting -dbg packages
> >>here. Therefore, I was thinking that it could handle some steps,
> >>like dependencies (in ${python:Depends}) and install (keep only
> >>debug files).
> >
> >dh_python2 cleans -dbg packages
>
> What do you mean by "clean"?
removes everything except .so and .h files from public directories
> >(unless invoked with --no-dbg-cleaning)
>
> Uh? My dh_python2 doesn't have such option.
ah, right, not released yet, will be uploaded soon
> >and adds dependencies to ${python:Depends}, yes
>
> What exactly it puts into python:Depends? I know it puts -dbg
> interpreter there, but what about stuff from requires.txt?
requires.txt is removed (as all other files in .egg-info) so there's
nothing to add
> Also, it means that you should use "Recommends: ${python:Depends}"
> for your -dbg package. Yay.
why?
--
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
--
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/20110810095524.gm16...@piotro.eu
Re: need someone to review and upload my package python-pycaptcha
* Olivier Sallou , 2011-08-10, 08:39: I need a DD to upload (and review) (Hopefully in the reverse order! :P) I'm not interested in uploading it, but here's my (cursory) review: - Binary package name is wrong; see Python Policy 2.2. Also, I'd use the name upstream uses (pycaptcha) for source package name. - python-all is needed in the clean target, so in must be in Build-Depends, not Build-Depends-Indep.[0] - Did you intend to use dh_python2? (You currently use python-support without build depending on it...) - You don't need get-orig-source target if only calls uscan. - Use "debhelper (>= 8)" rather than "debhelper (>= 8.0.0)" to ease backporting. - Remove "DEB_PYTHON_INSTALL_ARGS_ALL += ..." from your debian/rules, it does nothing. I tested with lintian and pbuilder. Oh, did you? :) My lintian complains heavily: P: python-pycaptcha: no-upstream-changelog I: python-pycaptcha: extended-description-is-probably-too-short I: python-pycaptcha: capitalization-error-in-description python Python W: python-pycaptcha: image-file-in-usr-lib usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/1.jpeg W: python-pycaptcha: image-file-in-usr-lib usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/10.jpeg W: python-pycaptcha: image-file-in-usr-lib usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/11.jpeg [snip - 27 more image-file-in-usr-lib...] W: python-pycaptcha: extra-license-file usr/share/doc/python-pycaptcha/COPYING [0] Separating B-D and B-D-I is often tricky, and if a package builds only arch:all binaries there's only very little benefit from the separation. So my general advice is: use only B-D (unless you know what you are doing). -- Jakub Wilk -- 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/20110810103315.ga5...@jwilk.net
Re: need someone to review and upload my package python-pycaptcha
HI, thanks for comments I will have a look. regarding lintian, which command did you run? I only have: debiansid:~/DEBIAN-PYTHON/pycaptcha$ lintian python-pycaptcha_0.4-1_all.deb W: python-pycaptcha: extra-license-file usr/share/doc/python-pycaptcha/COPYING Thanks Olivier Le 8/10/11 12:33 PM, Jakub Wilk a écrit : > * Olivier Sallou , 2011-08-10, 08:39: >> I need a DD to upload (and review) > > (Hopefully in the reverse order! :P) > > I'm not interested in uploading it, but here's my (cursory) review: > > - Binary package name is wrong; see Python Policy 2.2. Also, I'd use > the name upstream uses (pycaptcha) for source package name. > - python-all is needed in the clean target, so in must be in > Build-Depends, not > Build-Depends-Indep.[0] > - Did you intend to use dh_python2? (You currently use python-support > without build depending on it...) > - You don't need get-orig-source target if only calls uscan. > - Use "debhelper (>= 8)" rather than "debhelper (>= 8.0.0)" to ease > backporting. > - Remove "DEB_PYTHON_INSTALL_ARGS_ALL += ..." from your debian/rules, > it does > nothing. > >> I tested with lintian and pbuilder. > > Oh, did you? :) My lintian complains heavily: > > P: python-pycaptcha: no-upstream-changelog > I: python-pycaptcha: extended-description-is-probably-too-short > I: python-pycaptcha: capitalization-error-in-description python Python > W: python-pycaptcha: image-file-in-usr-lib > usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/1.jpeg > W: python-pycaptcha: image-file-in-usr-lib > usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/10.jpeg > W: python-pycaptcha: image-file-in-usr-lib > usr/lib/python2.6/dist-packages/Captcha/data/pictures/abstract/11.jpeg > [snip - 27 more image-file-in-usr-lib...] > W: python-pycaptcha: extra-license-file > usr/share/doc/python-pycaptcha/COPYING > > > [0] Separating B-D and B-D-I is often tricky, and if a package builds > only arch:all binaries there's only very little benefit from the > separation. So my general advice is: use only B-D (unless you know > what you are doing). > -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- 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/4e426044.6050...@irisa.fr
Re: need someone to review and upload my package python-pycaptcha
[Olivier Sallou, 2011-08-10] > regarding lintian, which command did you run? > > I only have: > debiansid:~/DEBIAN-PYTHON/pycaptcha$ lintian python-pycaptcha_0.4-1_all.deb if you want lintian to check binary *and* source package, invoke it with .changes file, not with the .deb. Jakub used --pedantic and --display-info options, but it's not a must to fix those (at least I don't require it, although I check them). There's also --info which you should use if you don't understand the error message PS please try to avoid top posting and remove unneeded quotes, TIA -- 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 -- 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/20110810105512.gn16...@piotro.eu
Re: need someone to review and upload my package python-pycaptcha
Hi, I have fixed several things on package: - Now source package is pycaptcha as upstream (though in svn still named python-pycaptcha, could rename it in svn later on) - binary is renamed python-captcha as per module name -I use python2 instead of python-support. Applied other comments. Only remaining lintian warn is: W: python-captcha: old-versioned-python-dependency depends: python (<< 2.8) though i use python-all so maybe it is related Thanks Olivier -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- 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/4e4268d3.4060...@irisa.fr
Re: need someone to review and upload my package python-pycaptcha
[Olivier Sallou, 2011-08-10] > Only remaining lintian warn is: > W: python-captcha: old-versioned-python-dependency depends: python (<< 2.8) > > though i use python-all so maybe it is related you should develop on Sid -- 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 -- 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/20110810112156.go16...@piotro.eu
Re: -dbg packages
* Piotr Ożarowski , 2011-08-10, 11:55:
I remember a discussion about dh_python2 supporting -dbg packages
here. Therefore, I was thinking that it could handle some steps,
like dependencies (in ${python:Depends}) and install (keep only
debug files).
dh_python2 cleans -dbg packages
What do you mean by "clean"?
removes everything except .so and .h files from public directories
Added to my "Why You Should Stay Away From Dh_Python2" list, thanks.
and adds dependencies to ${python:Depends}, yes
What exactly it puts into python:Depends? I know it puts -dbg
interpreter there, but what about stuff from requires.txt?
requires.txt is removed (as all other files in .egg-info) so there's
nothing to add
I hope you are all aware, that if python-dbg tries to import foo, and
foo_d.so is not found, it'll try to load foo.so instead (and then it'll
fail with a very obscure error message). So it's quite important to keep
your bar-dbg's Depends/Recommends line correct. And you have to do it
manually (which is not bad per se), even when bar's Depends line is
automatically generated from requires.txt.
Also, it means that you should use "Recommends: ${python:Depends}" for
your -dbg package. Yay.
why?
Because otherwise you'll end up with "Depends: python-dbg" which is too
strict. See http://wiki.debian.org/Python/DbgBuilds for rationale.
--
Jakub Wilk
--
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/20110810112827.ga1...@jwilk.net
Re: need someone to review and upload my package python-pycaptcha
I am on sid and changes file specify unstable distrib Whatever, package should be ok now (at least from lintian point of view). If you have other comments, please let me know Thanks Olivier Le 8/10/11 1:21 PM, Piotr Ożarowski a écrit : > [Olivier Sallou, 2011-08-10] >> Only remaining lintian warn is: >> W: python-captcha: old-versioned-python-dependency depends: python (<< 2.8) >> >> though i use python-all so maybe it is related > you should develop on Sid -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- 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/4e426d10.4060...@irisa.fr
Re: -dbg packages
[Jakub Wilk, 2011-08-10]
> Added to my "Why You Should Stay Away From Dh_Python2" list, thanks.
can I see that list? (dh_python2 has been already improved a lot thanks
to your bug reports)
> >>>and adds dependencies to ${python:Depends}, yes
> >>What exactly it puts into python:Depends? I know it puts -dbg
> >>interpreter there, but what about stuff from requires.txt?
> >requires.txt is removed (as all other files in .egg-info) so there's
> >nothing to add
>
> I hope you are all aware, that if python-dbg tries to import foo, and
> foo_d.so is not found, it'll try to load foo.so instead (and then
> it'll fail with a very obscure error message). So it's quite
yeah, we should file a bug upstream to fix this error message
(the first thing I say when someone points me to it is: "did you install
-dbg package for this extension?")
> important to keep your bar-dbg's Depends/Recommends line correct. And
> you have to do it manually (which is not bad per se), even when bar's
> Depends line is automatically generated from requires.txt.
the problem is I have no idea if Baz should be translated to
python-baz-dbg or skipped (as python-bar already depends on python-baz)
i.e. if Baz is a pure Python module or an extension, so I cannot use
requires.txt data anyway (crazy idea: Provide: python-foo-dbg packages
in packages with pure Python foo modules and no extensions)
> >>Also, it means that you should use "Recommends:
> >>${python:Depends}" for your -dbg package. Yay.
> >
> >why?
>
> Because otherwise you'll end up with "Depends: python-dbg" which is
> too strict. See http://wiki.debian.org/Python/DbgBuilds for
> rationale.
it actually generates python2.X-dbg | python2.Y-dbg (and python-dbg (>=
2.X), python-dbg (<< 2.Y+1) which you requested due to transitions issues)
--
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
--
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/20110810114418.gq16...@piotro.eu
Re: Python 3 BoF at DebConf11
On Mon, 2011-08-08 at 23:50 +0200, Piotr Ożarowski wrote: > We discussed /usr/bin/python2 symlink issue shortly and we all agreed > that we don't want Debian to use it (should helpers change shebangs back > to /usr/bin/python? Should lintian warn about it?) although we might > want to ship it with Wheezy to follow other distributions³. > > /usr/bin/python will point to Python 2 in Debian for a while (Wheezy and > Wheezy+1 for sure). /usr/bin/python3 might point to python3.3 instead of > 3.2, though. Python 3.3 should be released short after Wheezy freeze, > but we'll have RC releases in unstable before the freeze and it could be > possible to replace 3.2 with 3.3 in supported Python 3 versions (but > that's something we'll consider later, after checking how much work is > needed for the transition). Why not make Python 2 point to /usr/bin/python2? Also, which distros have already done this change? OT: Is Arch Linux still insisting on Python 3 pointing to /usr/bin/python by default? -- 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/1312979410.11506.5.camel@tshepang.tauspace.local
/usr/bin/python2 again
[Tshepang Lekhonkhobe, 2011-08-10] > Why not make Python 2 point to /usr/bin/python2? because instead of: | oh, look, /usr/bin/python is a symlink, lets use different 2.X version, | I don't care about 2.Y anymore and I want 2.Z by default. What? foo | application doesn't work anymore? Damn Debian developers, and they call | their system stable! we'll get: | oh, look, there's /usr/bin/python2 and /usr/bin/python3 binaries | so it should be safe to change /usr/bin/python symlink, lets | do that, ... Damn Debian developers! a *LOT* more often (changes between 2.X versions are not that big compared to 2.X-3.X ones > Also, which distros have already done this change? all that do not support more than one Python version at the same time probably (and all that do not care about beeing nice to other distributions, like Arch) -- 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 -- 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/20110810130359.gr16...@piotro.eu
Re: Some thoughts about py{support,central} -> dh_python2 conversion
On 07/08/11 21:29, Jakub Wilk wrote: > Dear all, > > If you can't resist the urge to convert your packages from > python-support to dh_python2, then please at least: > > 1) Test your packages. Don't assume that the helper you use does the > right thing. Sometimes it does, sometimes it doesn't. > > 2) Do not skip the "Before you begin"[0] step. This is very important: > if two packages share a namespace, either both or none of them must use > python-support. Also, it's not enough just to convert them all to > dh_python2: you must make sure (using Breaks or Depends relationships) > that you cannot co-install an older python-support-based versions > together with dh_python2-based ones. > > I set up a page to track this kinds of issues in unstable[2] and > testing[3]. Please note that I analyse only package contents, not > relationships. The tracker is updated daily. (Any volunteers to file bugs?) After breaking the hgext namespace with mercurial-1.9.1-1, I've filed bugs against hgsubversion[0], hgview[1] and qct[2]. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637399 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637400 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637401 Thanks for the heads up, Javi (vicho) signature.asc Description: OpenPGP digital signature
