Ben Finney wrote:
The changelog entry for ‘debhelper’ 7.3.5 says:
* python_distutils buildsystem: Build for all supported Python
versions that are installed. Ensure that correct shebangs are
created by using `python' first during build and install.
Closes: #520834
Also
Hi, I believe that the following entries are incorrect:
/usr/share/pyshared/arista-0.9.1.egg-info:License: UNKNOWN
/usr/share/pyshared/cups-1.0.egg-info:License: UNKNOWN
/usr/share/pyshared/Django-1.1.1.egg-info:License: UNKNOWN
/usr/share/pyshared/git_build_package-0.0.0.egg-info:License:
Bernd Zeimetz be...@bzed.de writes:
Ben Finney wrote:
I can't find where ‘/usr/bin/’ is excluded from requirement to be
created; is it in a part of Policy that I've overlooked?
There is no need to use a .dirs file if setup.py creates the directory
for you.
Gotcha. Okay, removed.
The
Ben Finney ben+deb...@benfinney.id.au writes:
Once I learn how to make a ‘foo-dbg’ package, I can do that in the
next release […]
I've learned some about creating a ‘foo-dbg’ package [0]. However, I'm
ending up with a source package that installs none of the Python files
into any of the binary
W. Martin Borgert deba...@debian.org writes:
Hi, I believe that the following entries are incorrect:
/usr/share/pyshared/arista-0.9.1.egg-info:License: UNKNOWN
/usr/share/pyshared/cups-1.0.egg-info:License: UNKNOWN
[…]
/usr/share/pyshared/spambayes-1.0.4.egg-info:License: UNKNOWN
* W. Martin Borgert deba...@debian.org, 2009-10-17, 13:23:
Hi, I believe that the following entries are incorrect:
/usr/share/pyshared/arista-0.9.1.egg-info:License: UNKNOWN
[snip]
I'm too lazy right now to file bugs
It would be better to file a bug against lintian to have a check for
Jakub Wilk uba...@users.sf.net writes:
* W. Martin Borgert deba...@debian.org, 2009-10-17, 13:23:
/usr/share/pyshared/arista-0.9.1.egg-info:License: UNKNOWN
It would be better to file a bug against lintian to have a check for
such issues.
I disagree. This issue in the ‘setup.py’ settings is
On Sat, Oct 17, 2009 at 9:50 PM, Ben Finney ben+deb...@benfinney.id.au wrote:
I disagree. This issue in the ‘setup.py’ settings is upstream's
responsibility. Lintian is best reserved for reporting problems that are
the Debian package maintainer's responsibility.
Do you object to
On Sat, Oct 17, 2009 at 11:40:07PM +1100, Ben Finney wrote:
Can someone point me to an existing package that:
* uses ‘debhelper’ vversion 7 or later (i.e. uses the implied-sequence
‘dh’ command instead of explicit lists of ‘dh_foo’ commands)
* uses ‘python-support’
* creates
On 2009-10-17 23:59, Ben Finney wrote:
So currently I don't think they are bugs of any severity above ‘minor’.
I agree, that this is 'minor' or even 'wishlist'.
Presumably all these are created by upstream ‘setup.py’ settings, so it
would ultimately be for upstream to fix in each case.
The
Dear Python mentors,
I am looking for a sponsor for the python-scrapy package
* Package name: python-scrapy
Version : 0.7-1
Upstream Author : Scrapy developers [1] [2]
* URL : http://scrapy.org/
* License : BSD
Section : python
It builds these
Paul Wise p...@debian.org writes:
Do you object to spelling-error-in-binary,
duplicated-key-in-desktop-entry, embedded-zlib, duplicate-font-file or
the other lintian tests that check upstream stuff?
I think they lead to widely-used, persistent overrides, and I think such
overrides are an
On 2009-10-18 09:46, Ben Finney wrote:
I don't have a strong objection in this case, and I can see good
arguments for and against a Lintian check. I wouldn't put up a fight
either way :-)
Me neither, it's certainly one of the least pressing issues we
have with Debian Python :~)
--
To
Jonathan Wiltshire deb...@jwiltshire.org.uk writes:
On Sat, Oct 17, 2009 at 11:40:07PM +1100, Ben Finney wrote:
* uses ‘debhelper’ vversion 7 or later […]
* uses ‘python-support’
* creates multiple packages, preferably including a ‘foo-dbg’ package
IIRC, backintime does all but the -dbg
On Sun, Oct 18, 2009 at 6:46 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
Paul Wise p...@debian.org writes:
Do you object to spelling-error-in-binary,
duplicated-key-in-desktop-entry, embedded-zlib, duplicate-font-file or
the other lintian tests that check upstream stuff?
I think they
15 matches
Mail list logo
