Re: Help in packaging rubber

2012-05-04 Thread Andreas Noteng
On 04. mai 2012 12:01, Hilmar Preuße wrote:
 Correct. It applies to a preview for a new upload, which is on my PC.
 I just wanted to document, which changes I've applied for the
 dh_pysupport - dh_python2 migration.
It's kind of hard to say without seeing the whole package, but if you
get it into SVN it'll be easy to see.

 I just sent the join request on alioth (https://a.d.org/projects/python-apps/)
 Should I make the package team managed, i.e.
 python-apps-t...@lists.alioth.debian.org as maintainer?
python-apps-t...@lists.alioth.debian.org should be in either maintainer
or uploaders.

-- 
Andreas Noteng



signature.asc
Description: OpenPGP digital signature


Re: Help in packaging rubber

2012-05-04 Thread Hilmar Preusse
On 04.05.12 Andreas Noteng (andr...@noteng.no) wrote:
 On 04. mai 2012 12:01, Hilmar Preuße wrote:

Hi,

  Correct. It applies to a preview for a new upload, which is on my PC.
  I just wanted to document, which changes I've applied for the
  dh_pysupport - dh_python2 migration.
 
 It's kind of hard to say without seeing the whole package, but if
 you get it into SVN it'll be easy to see.
 
The version the patch applies to is here:
http://wagner.debian.org/~hilmar-guest/rubber/

I don't have write access to your SVN yet (AFAICT).

  I just sent the join request on alioth 
  (https://a.d.org/projects/python-apps/)

  Should I make the package team managed, i.e. 
  python-apps-t...@lists.alioth.debian.org as maintainer?
 
 python-apps-t...@lists.alioth.debian.org should be in either maintainer
 or uploaders.
 
I'll fix that ASAP.

H.
-- 
http://www.hilmar-preusse.de.vu/#206401 http://counter.li.org


signature.asc
Description: Digital signature


Re: Help in packaging rubber

2012-05-03 Thread olivier.sal...@codeless.fr
 I am not a python expert so consider the following as the result of
previous experiences only.

Le 5/2/12 11:39 PM, Hilmar Preusse a écrit :
 Dear python maintainers,

 I intend/plan to adopt the rubber package[1]. I prepared a package
 for testing, it is available from here[2].

 When building the package two warnings occur:

 - dh_pysupport: This program is deprecated, you should use dh_python2 
 instead. Migration guide: http://deb.li/dhs2p
I think you have to set ---with=python2 in your rules file after the dh $@
 - dpkg-deb: warning: 'debian/rubber/DEBIAN/control' contains user-defined 
 field 'Python-Version'
t from old memories I think it is fine.

 Yes, I've read http://deb.li/dhs2p, but I'm failing to understand
 what I have to do in the Before you begin section. Unfortunately I
 don't speak python myself, this might be the reason.
In the Before you begin, they ask you to check there is no existing
package using same namespace (like Java package).
If your package uses namespace rubber.Rubber for example, there should
be no other rubber in Debian packages to avoid conflicts.

Olivier
 Please be so kind to teach me, what needs to be changed. Please keep
 me in Cc, I'm not subscribed.

 Regards,
   Hilmar

 [1] http://bugs.debian.org/670755
 [2] http://wagner.debian.org/~hilmar-guest/

 -- 
 gpg key id: 4096R/326D8438  (keyring.debian.org)
 Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438


Re: Help in packaging rubber

2012-05-03 Thread Andreas Noteng
On 02. mai 2012 23:39, Hilmar Preusse wrote:
 Dear python maintainers,
 
 I intend/plan to adopt the rubber package[1]. I prepared a package
 for testing, it is available from here[2].
 
 When building the package two warnings occur:
 
 - dh_pysupport: This program is deprecated, you should use dh_python2 
 instead. Migration guide: http://deb.li/dhs2p

Make sure you removed python-support from the dependencies, also make
sure your rules file calls dh --with python2 (often this is enough:
%:
dh $@ --with python2
). Depending on the complexity of your package, you might need to remove
any references to python-support in your debian/rules

 - dpkg-deb: warning: 'debian/rubber/DEBIAN/control' contains user-defined 
 field 'Python-Version'

It should be X-Python-Version
 
 Yes, I've read http://deb.li/dhs2p, but I'm failing to understand
 what I have to do in the Before you begin section. Unfortunately I
 don't speak python myself, this might be the reason.
 
 Please be so kind to teach me, what needs to be changed. Please keep
 me in Cc, I'm not subscribed.
 
Python sponsors tend to be picky; I'd recommend running lintian -Iv
--pedantic on the resulting .changes file after building. It'd likely
save you a couple of mails back and fourth with the sponsor.

Regards
-- 
Andreas Noteng



signature.asc
Description: OpenPGP digital signature


Re: Help in packaging rubber

2012-05-03 Thread Jakub Wilk

* Olivier Sallou olivier.sal...@codeless.fr, 2012-05-03, 08:06:
Yes, I've read http://deb.li/dhs2p, but I'm failing to understand what 
I have to do in the Before you begin section. Unfortunately I don't 
speak python myself, this might be the reason.
In the Before you begin, they ask you to check there is no existing 
package using same namespace (like Java package).


No, it has nothing to do with other programming languages.

--
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/20120503191616.ga4...@jwilk.net



Re: Help in packaging rubber

2012-05-03 Thread Hilmar Preusse
On 03.05.12 Andreas Noteng (andr...@noteng.no) wrote:
 On 02. mai 2012 23:39, Hilmar Preusse wrote:

Hi,

  Dear python maintainers,
  
  I intend/plan to adopt the rubber package[1]. I prepared a package
  for testing, it is available from here[2].
  
  When building the package two warnings occur:
  
  - dh_pysupport: This program is deprecated, you should use dh_python2 
  instead. Migration guide: http://deb.li/dhs2p
 
 Make sure you removed python-support from the dependencies, also make
 sure your rules file calls dh --with python2 (often this is enough:
   %:
   dh $@ --with python2
 ). Depending on the complexity of your package, you might need to remove
 any references to python-support in your debian/rules
 
Attached is the patch documenting the changes I've applied. Is this
OK?

When building the package I get two warnings:

- W: dh_python2:90: Python 2.7 should install files in 
/usr/lib/python2.7/dist-packages/. Did you forget --install-layout=deb?
- dpkg-gencontrol: warning: package rubber: unused substitution variable 
${python:Versions}

Can I ignore the first one for now? I don't understand the second
one, there is no substitution variable like this in debian/control.

Finally I'm not sure if the Before you begin section on
http://wiki.debian.org/Python/TransitionToDHPython2 is relevant for
me. Please advise!

  - dpkg-deb: warning: 'debian/rubber/DEBIAN/control' contains user-defined 
  field 'Python-Version'
 
 It should be X-Python-Version
 
Until now there exista a file called debian/pyversions . It just
contained a - . I guess this specification is not necessary at all.

 Python sponsors tend to be picky; I'd recommend running lintian -Iv
 --pedantic on the resulting .changes file after building. It'd likely
 save you a couple of mails back and fourth with the sponsor.
 
This gave me a few more things to fix, I killed a few of them, but
not all.

Thanks,
  Hilmar
-- 
http://www.hilmar-preusse.de.vu/#206401 http://counter.li.org
diff -urN rubber-1.1+20100306_20120503/debian/control 
rubber-1.1+20100306/debian/control
--- rubber-1.1+20100306_20120503/debian/control 2012-05-03 11:13:43.0 
+0200
+++ rubber-1.1+20100306/debian/control  2012-05-03 22:41:13.0 +0200
@@ -4,8 +4,7 @@
 Maintainer: Hilmar Preuße hill...@web.de
 Uploaders: Baruch Even bar...@debian.org
 Build-Depends: debhelper (= 7)
-Build-Depends-Indep: python, texinfo, python-support (=0.5.3)
-XB-Python-Version: all
+Build-Depends-Indep: python (= 2.6.6-3~), texinfo
 Standards-Version: 3.9.3
 Homepage: https://launchpad.net/rubber
 
@@ -13,7 +12,6 @@
 Architecture: all
 Depends: ${python:Depends}, ${misc:Depends}, texlive-latex-base
 Suggests: imagemagick, transfig, sam2p
-XB-Python-Version: ${python:Versions}
 Description: automated system for building LaTeX documents
  This is a building system for LaTeX documents. It is based on a routine that
  runs just as many compilations as necessary. The module system provides a
diff -urN rubber-1.1+20100306_20120503/debian/pyversions 
rubber-1.1+20100306/debian/pyversions
--- rubber-1.1+20100306_20120503/debian/pyversions  2012-04-23 
22:31:59.0 +0200
+++ rubber-1.1+20100306/debian/pyversions   1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
--
diff -urN rubber-1.1+20100306_20120503/debian/rules 
rubber-1.1+20100306/debian/rules
--- rubber-1.1+20100306_20120503/debian/rules   2012-05-03 11:18:52.0 
+0200
+++ rubber-1.1+20100306/debian/rules2012-05-03 11:36:35.0 +0200
@@ -37,7 +37,8 @@
 binary-indep: build install
dh_testdir
dh_testroot
-   dh_pysupport
+   #dh_pysupport
+   dh_python2
dh_installdocs
dh_installman
dh_installinfo doc/rubber.info


signature.asc
Description: Digital signature


Re: Fwd: Re: Help in packaging rubber

2012-05-03 Thread Hilmar Preusse
On 03.05.12 olivier.sal...@codeless.fr (olivier.sal...@codeless.fr) wrote:

Hi,

  Yes, I've read http://deb.li/dhs2p, but I'm failing to understand
  what I have to do in the Before you begin section. Unfortunately I
  don't speak python myself, this might be the reason.
 
 In the Before you begin, they ask you to check there is no existing
 package using same namespace (like Java package).  If your package
 uses namespace rubber.Rubber for example, there should be no other
 rubber in Debian packages to avoid conflicts.
 
How can I find out if it does?

Thanks,
  Hilmar
-- 
http://www.hilmar-preusse.de.vu/#206401 http://counter.li.org


signature.asc
Description: Digital signature


Re: Help in packaging rubber

2012-05-03 Thread Andreas Noteng
On 03. mai 2012 22:54, Hilmar Preusse wrote:
 Attached is the patch documenting the changes I've applied. Is this
 OK?
The patch does not seem to apply to the revision currently in Debian. If
you plan to maintain this package I'd strongly recommend joining the
PAPT [1], and using the PAPT svn repository and svn buildpackage. This
would ease the process of helping you, and later for the sponsors to
review your package. I'd also recommend subscribing to this list..

[1]: http://wiki.debian.org/Teams/PythonAppsPackagingTeam

Regards
-- 
Andreas Noteng



signature.asc
Description: OpenPGP digital signature