On 12/08/10 05:05, IOhannes m zmoelnig wrote:
> On 2010-08-11 16:04, Felipe Sateler wrote:
>> I have just added you to the team on alioth. Welcome! 
> cool thank you.
>> First import the packages in the team's git repository (and be sure to
>> enable the commit notifications to the pkg-multimedia-commits list).
>> Also, read our wiki page for some details regarding how we usually
>> handle packaging (wiki.debian.org/DebianMultimedia).
> ok.
> so i have started from scratch (turned out to be easier; not much of a
> git-wizz yet...), and created a "pd-zexy" package for the new upstream
> version 2.2.3.
> the package builds fine in a pbuilder environment, and is basically
> lintian clean (there are some I and P warnings: no upstream changelog
> (true), no watch file  (as upstream i know that it is hard to create a
> watch file given how zexy is released) and spelling mistakes (cannot
> change that as it would break zexy's API)
> i have uploaded i386 packages to mentors.d.o:
> http://mentors.debian.net/debian/pool/main/p/pd-zexy/
> i have created a git repository "pd-zexy":
>  git+ssh://git.debian.org/git/pkg-multimedia/pd-zexy.git
> with the /git/pkg-multimedia/setup-repository script, so all hooks
> should be working (at least my commits show up in pkg-multimedia-commits)
> i have populated the repository with my .dsc file, which was probably a
> bad idea, since this has automatically set the "debian/2.2.3-1" tag.
> since i already pushed, i guess this cannot be helped any more.
>> I could "sponsor" your packages after you have imported them into the
>> git repository (I don't have time right now, ping again when you have
>> done this).
> ping.

Why do you install zexy into a non standard pd path?

Also, the copyright file could use some updating (what are your
contributions, etc). There are some files with copyrights other than

debian/dirs seems to be redundant.

Aand... short-form dh7 seems to not work correctly. since there is a
build directory, debian/rules build says that 'build' is up to date. And
phony targets do not seem to work with dh7.
This means that the package ends up being built under root (in the
binary stage), which is frowned upon by policy.

Felipe Sateler

pkg-multimedia-maintainers mailing list

Reply via email to