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
Hi Daniel (2010.11.05_19:45:42_+0200)
I'm kindly asking for overchecking/uploading of the following packages:
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
On Nov 05, 2010, at 09:46 PM, Stefano Rivera wrote:
#!/usr/bin/make -f
%:
dh $@
[...]
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.
Which should be as easy as adding --with python2 to
* Stefano Rivera stef...@rivera.za.net, 2010-11-05, 21:46:
debian/rules: Not a fan of dh $...@?
FWIW, I have nothing against dh $@, but I'm opposed to abuse of %-rules.
#!/usr/bin/make -f
%:
dh $@
override_dh_auto_install:
dh_auto_install --
Moving this non-Python part of the discussion to ‘debian-mentors’.
Stefano Rivera stef...@rivera.za.net writes:
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.
Is this common practise
Hi Ben (2010.11.05_23:18:41_+0200)
Is this common practise among sponsors?
It is for debian-python. I don't have any experience with other
SVN-using teams.
If the above convention (the sponsor will change ‘UNRELEASED’ to the
appropriate suite name before re-building) is common, is it
6 matches
Mail list logo
