Nevow (was Re: Pycha packaging)

2008-01-08 Thread Vincent Bernat
OoO En ce début de soirée du vendredi 04 janvier 2008, vers 21:07, Piotr
Ożarowski [EMAIL PROTECTED] disait:

 May I also add nevow to the list of team-maintained packages?
 http://packages.qa.debian.org/n/nevow.html

 it's a Python module, you're a team member - I don't see a reason why you
 shouldn't add it :)

I have updated Nevow package to  a new upstream version. The package has
never been reread. Could someone check if all seems correct?

Vcs-Svn: svn://svn.debian.org/python-modules/packages/nevow/trunk
Vcs-Browser: 
http://svn.debian.org/wsvn/python-modules/packages/nevow/trunk/?op=log

Thanks.
-- 
Test programs at their boundary values.
- The Elements of Programming Style (Kernighan  Plauger)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-05 Thread Vincent Bernat
OoO Vers la fin de l'après-midi du vendredi 04 janvier 2008, vers 16:10,
Bernd Zeimetz [EMAIL PROTECTED] disait:

 The file exists in the upstream tarball, so I cannot remove it. 

 sure, you can. Just delete it in the clean target.

You  are right, it  worked without  any problem.  I feared  that diff.gz
would have contained a diff with the missing file.
-- 
Avoid unnecessary branches.
- The Elements of Programming Style (Kernighan  Plauger)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-04 Thread Bernd Zeimetz
Vincent Bernat wrote:
 OoO En cette  nuit nuageuse du vendredi 04 janvier  2008, vers 00:56, je
 disais:
 
 * add python-setuptools (= 0.6b3-1) to Build-Depends
 
 lintian  asked  me  to  add  it to  Build-Depends-Indep  unless  it  was
 necessary  for clean.  Since python  setup.py clean  is called  on clean
 target, I have added a lintian override.

wrong way to go - Please report this as bug against lintian.

 
 I have removed  it. I will upload  this to SVN shortly and  will ask you
 for  upload  when  the  description  review  by  debian-l10n-english  is
 complete.
 
 I  have uploaded to  SVN using  svn-inject -o.  Because of  the modified
 SOURCES.txt, I have now a not-so-clean SVN tree. Should I leave as is or
 should I remove SOURCES.txt from trunk and branches?


please remove it and add a patch using quilt or dpatch.


Cheers,

Bernd

-- 
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-04 Thread Piotr Ożarowski
[Bernd Zeimetz, 04.01.2008]
 Vincent Bernat wrote:
  I  have uploaded to  SVN using  svn-inject -o.  Because of  the modified
  SOURCES.txt, I have now a not-so-clean SVN tree. Should I leave as is or
  should I remove SOURCES.txt from trunk and branches?
 
 please remove it and add a patch using quilt or dpatch.

or just remove this file in clean rule, it will be regenerated with
every ./setup.py call...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-04 Thread Vincent Bernat

On Fri, 4 Jan 2008 09:29:11 +0100, Piotr Ożarowski [EMAIL PROTECTED]
wrote:

  I  have uploaded to  SVN using  svn-inject -o.  Because of  the
modified
  SOURCES.txt, I have now a not-so-clean SVN tree. Should I leave as is
or
  should I remove SOURCES.txt from trunk and branches?

 please remove it and add a patch using quilt or dpatch.
 
 or just remove this file in clean rule, it will be regenerated with
 every ./setup.py call...

The file exists in the upstream tarball, so I cannot remove it. One line is
missing, so it is modified and the clean target does not revert the
modification. Even if I think this is a bit overkill, I will add a patch to
handle this.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-04 Thread Bernd Zeimetz
Vincent Bernat wrote:
 On Fri, 4 Jan 2008 09:29:11 +0100, Piotr Ożarowski [EMAIL PROTECTED]
 wrote:
 
 I  have uploaded to  SVN using  svn-inject -o.  Because of  the
 modified
 SOURCES.txt, I have now a not-so-clean SVN tree. Should I leave as is
 or
 should I remove SOURCES.txt from trunk and branches?
 please remove it and add a patch using quilt or dpatch.
 or just remove this file in clean rule, it will be regenerated with
 every ./setup.py call...
 
 The file exists in the upstream tarball, so I cannot remove it. 

sure, you can. Just delete it in the clean target.


-- 
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-04 Thread Josselin Mouette
Le vendredi 04 janvier 2008 à 00:11 +0100, Piotr Ożarowski a écrit :
 * Provides: ${python:Provides} is not really needed (sorry Joss)

You don’t need to be sorry, I’m the first one to say we should remove
them in many cases ;) They introduce the need for Python-Depends, which
is frankly not the most sexy thing in python-related packages.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée


Re: Pycha packaging

2008-01-04 Thread Piotr Ożarowski
[Vincent Bernat, 04.01.2008]
 I have removed  it. I will upload  this to SVN shortly and  will ask you
 for  upload  when  the  description  review  by  debian-l10n-english  is
 complete.

ping me via private mail or on IRC (#debian-python, OFTC network,
nickname: POX)

  you're added, welcome in the team :-)
[...]
 May I also add nevow to the list of team-maintained packages?
  http://packages.qa.debian.org/n/nevow.html

it's a Python module, you're a team member - I don't see a reason why you
shouldn't add it :)

-- 
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpuCU2KvpD9T.pgp
Description: PGP signature


Re: Pycha packaging

2008-01-03 Thread Piotr Ożarowski
Hi Vincent,

 I have  packaged Pycha,  a simple chart-drawing  library using  Cairo as
 backend.
[...]
 Any feedback on the packaging is welcome.

* Priority: extra - why not optional?
* Build depend on python-support (= 0.6.4) or you will have some
  problems with Eggs
* add python-setuptools (= 0.6b3-1) to Build-Depends
* add to source stanza (in debian/control):

  Vcs-Svn: svn://svn.debian.org/python-modules/packages/pycha/trunk
  Vcs-Browser: 
http://svn.debian.org/wsvn/python-modules/packages/pycha/trunk/?op=log

* Provides: ${python:Provides} is not really needed (sorry Joss)
  you can add ${misc:Depends} to Depends
* remove CHANGES.txt from debian/docs, add in debian/rules

  DEB_INSTALL_CHANGELOGS_ALL = CHANGES.txt

* I want to make few uploads by myself before adding
  XS-DM-Upload-Allowed: yes, so please remove it for now (feel free to
  leave it if upload will be done by any other DD that already knows
  you)

 I would like  to maintain it into the debian  modules packaging team. My
 alioth login bernat-guest.

you're added, welcome in the team :-)

-- 
http://people.debian.org/~piotr/sponsor.txt


pgpYOAWlFqp9U.pgp
Description: PGP signature


Re: Pycha packaging

2008-01-03 Thread Vincent Bernat
OoO  En cette nuit  nuageuse du  vendredi 04  janvier 2008,  vers 00:11,
Piotr Ożarowski [EMAIL PROTECTED] disait:

 I have  packaged Pycha,  a simple chart-drawing  library using  Cairo as
 backend.
 [...]
 Any feedback on the packaging is welcome.

 * Priority: extra - why not optional?

Well, I am never sure of when  to use extra and when to use optional.

 * Build depend on python-support (= 0.6.4) or you will have some
   problems with Eggs
 * add python-setuptools (= 0.6b3-1) to Build-Depends
 * add to source stanza (in debian/control):

   Vcs-Svn: svn://svn.debian.org/python-modules/packages/pycha/trunk
   Vcs-Browser: 
 http://svn.debian.org/wsvn/python-modules/packages/pycha/trunk/?op=log

 * Provides: ${python:Provides} is not really needed (sorry Joss)
   you can add ${misc:Depends} to Depends
 * remove CHANGES.txt from debian/docs, add in debian/rules

   DEB_INSTALL_CHANGELOGS_ALL = CHANGES.txt

Done all this.

 * I want to make few uploads by myself before adding
   XS-DM-Upload-Allowed: yes, so please remove it for now (feel free to
   leave it if upload will be done by any other DD that already knows
   you)

I have removed  it. I will upload  this to SVN shortly and  will ask you
for  upload  when  the  description  review  by  debian-l10n-english  is
complete.

 I would like  to maintain it into the debian  modules packaging team. My
 alioth login bernat-guest.

 you're added, welcome in the team :-)

Thanks !

May I also add nevow to the list of team-maintained packages?
 http://packages.qa.debian.org/n/nevow.html

No upload is planned for the moment. I will just fix similar issues that
you spotted in Pycha.
-- 
printk(KERN_WARNING Multi-volume CD somehow got mounted.\n);
2.2.16 /usr/src/linux/fs/isofs/inode.c


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Pycha packaging

2008-01-03 Thread Vincent Bernat
OoO En cette  nuit nuageuse du vendredi 04 janvier  2008, vers 00:56, je
disais:

 * add python-setuptools (= 0.6b3-1) to Build-Depends

lintian  asked  me  to  add  it to  Build-Depends-Indep  unless  it  was
necessary  for clean.  Since python  setup.py clean  is called  on clean
target, I have added a lintian override.

 I have removed  it. I will upload  this to SVN shortly and  will ask you
 for  upload  when  the  description  review  by  debian-l10n-english  is
 complete.

I  have uploaded to  SVN using  svn-inject -o.  Because of  the modified
SOURCES.txt, I have now a not-so-clean SVN tree. Should I leave as is or
should I remove SOURCES.txt from trunk and branches?

Thanks.
-- 
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE SEIZURES
I WILL NOT FAKE SEIZURES
-+- Bart Simpson on chalkboard in episode 8F23


pgpsqbEEY5jOS.pgp
Description: PGP signature