[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: bzr-cvsps-import



OoO Vers  la fin de l'après-midi  du dimanche 03 août  2008, vers 16:24,
Jelmer Vernooij <jelmer@samba.org> disait :

>> > I am looking for a sponsor for my package "bzr-cvsps-import".
>> You can try to seek sponsorship inside Debian Bazaar Maintainers team.
> I'm a member of that team but unfortunately all of the active members
> are DMs these days, hence my asking here.

> Vorlon sponsored bzr-cvsps-import(thanks!), but I'm still looking for
> sponsors for bzr-stats and bzr-avahi.

Hi Jelmer!

For bzr-avahi, there is  a lot of things in diff.gz. I  think there is a
packaging problem  here, like using an unsynced  orig.tar.gz. You should
only have modifications concerning debian/ directory in diff.gz.

I don't  quite understand  your answer to  James Henstridge  about 0.2.0
version. Where did you put your fixed version?

In debian/compat, you should put 5.

In debian/control,  you should also  add a Vcs-Browser field.  I suppose
that there  is some  web interface  to browse the  source for  Bazaar as
well.

I think that  most things in Build-Depends are not  needed for the clean
rule, so  you can move them  in Build-Depends-Indep (and  just keep cdbs
and debhelper).

To avoid a lintian warning,  you should provide a debian/watch file with
just a comment about, for example, the URL to upstream repository.

For bzr-stats, there is no statement  about the license and I think that
the  GPL mention  in setup.py  is a  bit weak.  You should  arrange with
upstream  to  ask  him  to  add  a proper  copyright  statement  in  the
distributed files.

Apart from  the diff.gz which is  OK, the same remarks  as for bzr-avahi
apply.

Well,  this may  be a  bit late  since some  packages have  already been
sponsored,  but since  all those  plugins  are rather  small, you  could
bundle them in  a single package (like gnus-bonus-el  for example). This
will be a  bit harder to follow upstream since there  is no mechanism to
track  several upstreams  but  this will  ease  your work  in finding  a
sponsor, I think  and will allow you to ship more  plugins once you will
get an  upload with DM  field enabled. I  am not sure this  is something
encouraged or  something to  avoid. Maybe some  people will  give better
advices here about this.
-- 
panic("Attempted to kill the idle task!");
	2.2.16 /usr/src/linux/kernel/exit.c

Attachment: pgplONCHdHwfC.pgp
Description: PGP signature


Reply to: