Bug#739121: Creepy taking over in Debian GIS team maintenance

[Andreas Tille]

Hi Daniel,

On Tue, Feb 18, 2014 at 11:03:53AM -0500, Daniel Echeverry wrote:
> >    git://anonscm.debian.org/pkg-grass/creepy.git
> >
> > You get commit permission if you apply for pkg-grass team on alioth.
> >
> 
> I sent my  request to join the team :) once  to be accepted, I will make
> the commits

Somebody else just adde you to the project. :-)
 
> > 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
> > /var/lib/creepy.
> >
> 
> Yes you are right, however, the path where plugins, and other projects are
> written, must be in the same part where creepy be installed, for this
> reason, do not think just patch the code to write in /var/lib solve the
> problem.
> 
> In fact I have discussed this issue with upstream, which says:
> 
> *"Regarding 2, its obvious that the user who runs the program has no
> permissions to write under /usr/share/creepy , should it be this way ?
> Isn't that chowned to the user account in Debian ? If not, then we need to
> find a different approach because the program needs to save projects and
> plugin configurations, if it does not have the permission to write to that
> directory , how could it be done ? "*
> 
> Coul you give me  a hand? :)

I admit I did never dealt with things like this.  I's suggest you finish
the commits and than ask on debian-mentors at lists.debian.org.  This list
is invented for questions like this.  I'm reading it and will comment as
well if I have any clue.

Thanks for your work on this

     Andreas.

-- 
http://fam-tille.de