Excerpts from Thomas Kluyver's message of 2012-11-09 05:19:03 -0800:
> This is an idea I've had knocking around for a while. Packaging is complex
> - there are lots of different tools and syntaxes you have to understand to
> do a good job of it - quilt, debhelper, watch files, etc. - along with
> s
On Nov 15, 2012, at 03:49 AM, Tristan Seligmann wrote:
>On Wed, Nov 14, 2012 at 5:42 PM, Tomás Di Domenico wrote:
>> Another blurry point. I'm having a hard time understanding the
>> separation of tasks between the tarball packaging done by upstream I
>> described before, and my Debian packaging.
On Wed, Nov 14, 2012 at 5:42 PM, Tomás Di Domenico wrote:
> Another blurry point. I'm having a hard time understanding the
> separation of tasks between the tarball packaging done by upstream I
> described before, and my Debian packaging. Similar to the docs, the
> tests are run by upstream when t
On Nov 14, 2012, at 02:00 PM, Stefano Rivera wrote:
>Hi Barry (2012.11.13_01:04:59_+0200)
>> I am upgrading Ubuntu 13.04's python-virtualenv package to 1.8.2. This
>> could provide a basis for upgrading the Debian version in Wheezy+1.
>
>As usual, I'd say: You're a member of DPMT, which is the pr
On 14 November 2012 19:11, Jakub Wilk wrote:
> * Barry Warsaw , 2012-11-14, 13:17:
>
While working on the python3-sympy package, I've seen that if Python 2
is installed, various dh_* commands, like dh_auto_clean, will automatically
try to run setup.py in Python 2. In this case, setu
On Nov 14, 2012, at 11:04 AM, Jakub Wilk wrote:
I'm afraid that this creates false impression that we'd accept
anyone, without any questions asked. This is not the case. As a DPMT
admin I required that the applicant:
1) either had existing Python-related packages in the archive;
2) or sho
On Wed, Nov 14, 2012 at 11:47 AM, Paul Belanger
wrote:
> Greetings list,
>
> I wanted to start discussion around merging a package from Ubuntu,
> python-jenkins[1], into Debian. The reason for this is it is actually
> a dependency for another piece of software I am hoping to package for
> Debian,
* Barry Warsaw , 2012-11-14, 13:17:
While working on the python3-sympy package, I've seen that if Python
2 is installed, various dh_* commands, like dh_auto_clean, will
automatically try to run setup.py in Python 2. In this case, setup.py
checks the Python version and fails. This isn't a proble
Python Modules Packaging Teams Policy[0] currently reads:
"The team is open to any python-related package maintainer. To be added
on the team, please send your request on debian-python@lists.debian.org
indicate why you want to join the team: maintain your current packages
within the team, help
On Nov 14, 2012, at 02:00 PM, Stefano Rivera wrote:
>Hi Barry (2012.11.13_01:04:59_+0200)
>> I am upgrading Ubuntu 13.04's python-virtualenv package to 1.8.2. This
>> could provide a basis for upgrading the Debian version in Wheezy+1.
>
>As usual, I'd say: You're a member of DPMT, which is the pr
On Nov 14, 2012, at 02:14 PM, Jakub Wilk wrote:
>* Thomas Kluyver , 2012-11-14, 11:44:
>>While working on the python3-sympy package, I've seen that if Python 2 >is
>>installed, various dh_* commands, like dh_auto_clean, will >automatically try
>>to run setup.py in Python 2. In this case, setup.p
On Nov 14, 2012, at 11:44 AM, Thomas Kluyver wrote:
>While working on the python3-sympy package, I've seen that if Python 2 is
>installed, various dh_* commands, like dh_auto_clean, will automatically
>try to run setup.py in Python 2. In this case, setup.py checks the Python
>version and fails. Th
Greetings list,
I wanted to start discussion around merging a package from Ubuntu,
python-jenkins[1], into Debian. The reason for this is it is actually
a dependency for another piece of software I am hoping to package for
Debian, jenkins-job-builder[2]. I'd like to go through
mentors.debian.net
On 13/11/12 21:17, Jakub Wilk wrote:
> * Tomás Di Domenico , 2012-11-12, 15:34:
>> * Rebuilt the package with an upstream release tarball
>
> Much better now. :)
>
>> * Changed debian/* license to MIT, matching upstream's
>
> DEP-5-compliant short license name for the MIT license is "Expat".
>
Hi Philippe!
Please use Debian New Maintainer's Guide¹ as a starting point. For
Python-specific things, check the “Python Packaging” page² or a
similar article in the Ubuntu Packaging Guide³.
If you want a tool that will generate most of the needed files for
you, take a look at pydsc (available i
* Thomas Kluyver , 2012-11-14, 11:44:
While working on the python3-sympy package, I've seen that if Python 2
is installed, various dh_* commands, like dh_auto_clean, will
automatically try to run setup.py in Python 2. In this case, setup.py
checks the Python version and fails. This isn't a prob
On Nov 14, 2012, at 11:46 AM, Thomas Kluyver wrote:
>On 14 November 2012 11:43, Jakub Wilk wrote:
>
>> I don't think so, sorry.
>
>Could you expand on this at all? Do you think that packaging should be left
>to the experts? Or that the existing systems are easy enough for newcomers
>to learn?
I
Hi Barry (2012.11.13_01:04:59_+0200)
> I am upgrading Ubuntu 13.04's python-virtualenv package to 1.8.2. This could
> provide a basis for upgrading the Debian version in Wheezy+1.
As usual, I'd say: You're a member of DPMT, which is the primary
maintainer of this package, so please feel free to c
On 14 November 2012 11:43, Jakub Wilk wrote:
> I don't think so, sorry.
Could you expand on this at all? Do you think that packaging should be left
to the experts? Or that the existing systems are easy enough for newcomers
to learn?
Thomas
* Thomas Kluyver , 2012-11-09, 13:19:
- Do you think this is worth spending time on?
I don't think so, sorry.
--
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.d
20 matches
Mail list logo
