Eugenio Cano-Manuel Mendoza eugeniocanom at
Fri May 24 16:10:45 UTC 2013

Hello everyone,

I just pushed scout. The changes:
    -Added watch file
    -Fixed copyright format issue
    -Removed trailing whitespace from debian/control
    -Created a new description, not very happy with it so please let me
know how to improve it
    -Closed ITP bug.

What's the policy for packages whose upstream doesn't provide a change log?
Do we build one? If so, do we use git log?

Another question. When (in the lifespan of my packages) am I supposed to
use dput-ng? Am I even allowed to do this? Shouldn't I wait for review from


On Thu, May 23, 2013 at 5:40 PM, Wolodja Wentland <debian at>wrote:

> Hi Eugenio,
> On Thu, May 23, 2013 at 16:16 +0100, Wolodja Wentland wrote:
> > I: libscout-clojure: description-synopsis-might-not-be-phrased-properly
> I forgot that I wanted to comment on this. One thing you have to keep in
> mind
> is that the package description is meant for people running Debian and
> *not*
> necessarily for Clojure developers. A person reading the short description
> should not have to be aware that clojure even exists, but should be able to
> know what the package is actually for.
> This is one of the many reasons why copying the upstream description is
> typically not a very good idea. I would expect something like:
> Description: Text scanning library for Clojure
>   Scout is a library for Clojure ....
> or something Along those lines ... The "Scout is a library for scanning
> through strings in a functional way" doesn't contain much information and
> is
> simply not a good description of the library.
> --
> Wolodja <debian at>
> 4096R/CAF14EFC
> 081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC
> _______________________________________________
> Pkg-clojure-maintainers mailing list
> Pkg-clojure-maintainers at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Pkg-clojure-maintainers mailing list