Re: RFS: trend
On Wed, 12 Aug 2009 22:58:59 +0800
Paul Wise <email@example.com> wrote:
> On Wed, Aug 12, 2009 at 8:37 PM, Yuri D'Elia<firstname.lastname@example.org>
> > I am looking for a sponsor for my package "trend".
> Which of the things I wrote in private mail did you take action on and
> which actions did you take for each of them?
First, I made sure that the package built from source in a chroot
(this is the first time I ever used pbuilder/cowbuilder/etc).
qemubuilder looked promising for testing all the archs at once, but
failed to work for me (bug #441043).
The package built fine inside cowbuilder/pbuilder from a fresh sid in
both i386/amd64 variants. The package built and executed fine inside a
native ppc debian host that I have here (again using pbuilder). I tried
crosscompiling with gcc also for arm looking for compilation issues, but
I didn't try all the other variants inside the qemu images you
The source does not contain any libraries. No compilation warnings are
produced. I tested the executable against valgrind (with both
memcheck and helgrind; since I "am" upstream, this was a rather easy
For instance, lintian only reported warnings in the man page which I
didn't notice before, so I fixed them directly in the original source
package with a new release instead of bloating the package with
There are no security threats that the package can expose directly. This
is a simple, non-setuid program. There are no configuration files with
permission issues. No files are ever created directly. No network
connections are established.
I did read already most of documentation links you sent me. After
reading again the debian policy I've switched the priority or the
original package from optional to extra. I also switched the versioning
scheme of the upstream source to mayor.minor (I previously just had a
I'm using the package myself on all my machines.
The only unclear task was about uploading the package to
mentors.debian.org. Why building a binary package is required if only
the source is used?
I didn't assign any package tags in debian/control.