Hi Daniel,

On Tue, Feb 18, 2014 at 10:14:36AM -0500, Daniel Echeverry wrote:
> Hi Andreas
> 2014-02-16 15:48 GMT-05:00 Andreas Tille <andr...@an3as.eu>:
> > Hi,
> >
> > I have injected the latest version of creepy into
> >
> >    git://anonscm.debian.org/pkg-grass/creepy.git

Hmmm, seems I missed to check mentors.d.n first ...

> > which would fix #739121 since the latest upstream version does not
> > depend from python-osmgpsmap any more.
> >
> > I would imagine to maintain the package in Debian GIS team since it is
> > in the wider sense related to geographic information.  I think we could
> > create a task "tools" or "misc" where this package could fit in.  So if
> > everybody agrees upon this (on one hand the former maintainer Daniel and
> > on the other hand the GIS team that this package might fit) I would
> > upload the package as is (after about waiting one week).
> >
> Cool, I'd like some help to the new upstream release. Currently it has a
> lot a problems, for example, it tries to write en /usr/share/creepy , the
> new version write a log file and I don't know how to hand that.
> Right now I've patched the source code to deny writing in /usr/share/creepy
> the problem now is that when creepy tries to write plugins or project,
> because it tries to write on /usr/share/creepy
> I uploaded the creepy 1.1 with these changes to mentors[1] Could you check
> it out? and tell me if I can help you with something

I wonder whether we should merge our efforts first.  Could you agree upon
the reporistory at


You get commit permission if you apply for pkg-grass team on alioth.

To my experience it becomes way more simple to work together on a
package when using a VCS rather than sending patches via mail.  It
also enables asking for help at debian-mentors list.

For your problem above:  I think you need to find the code piece that
tries to write to /usr/share/creepy and redirect the write attempts to

Kind regards


> [1]: http://mentors.debian.net/debian/pool/main/c/creepy/creepy_1.1-1.dsc


Pkg-grass-devel mailing list

Reply via email to