Re: RFS: bastet (updated package)
On (13/09/06 22:14), Nacho Barrientos Arias wrote:
> Date: Wed, 13 Sep 2006 20:59:14 +0100
> James Westby <jw+debian@jameswestby.net> wrote:
> > * http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html*/-bpp-upstream-info
> > suggests that the Homepage: field be indented by two spaces not one.
>
> 404, but i will consider it.
>
Sorry, vim seems to have a macro that interfers with this URL, I must
remember that.
http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-upstream-info
> > * The description states that the game is GPL'd, the debian/copyright
> > states that it is public domain or MIT. Most of the code has no
> > license headers or copyright. At worst it has been relicensed
> > against the authors wishes and is undistributable. At best the
> > debian/copyright and/or desciption should be updated. In the middle
> > is a clarification from upstream, and the addition of the usual
> > Copyright statements and license headers.
>
> Description's lines were inherited from last maintainer (i didn't
> changed it).
>
I realise that, but unfortuanately it doesn't protect you from the
issues I mentioned.
Thanks for trying to sort it out.
> > * Does the Debian games team that you say you are adopting the package
> > for not contain some DDs who will sponsor the packages of the group?
>
> Probably, but obviously there are more potential sponsors here.
Yes, that is true. I thought the point of team maintainence was to do
things as a team, and try and concentrate the skills/interests where
they are required.
If you find a sponsor here then it is great, but I assume that any DD
who is a member of the games team has an interest in games, and
experience with the packaging of them, two things that I assume that an
sponsor will consider when looking at whether to upload a package.
James
--
James Westby -- GPG Key ID: B577FE13 -- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!>|&7U.L#9E)Tu)T0>AM - secp256r1/nistp256
Reply to: