[GRASS-dev] g.extension: still fetching from SVN?

neteler · June 27, 2019, 3:10pm

Hi devs,

I have the strong impression that g.extension is still fetching from SVN.
If true I consider this an important showstopper...

Is anyone able to verify this and, if needed, update it to point to
GitHub (which is supported already)?

thanks,
Markus

neteler · June 30, 2019, 9:14pm

On Thu, Jun 27, 2019 at 5:10 PM Markus Neteler <neteler@osgeo.org> wrote:

Hi devs,

I have the strong impression that g.extension is still fetching from SVN.
If true I consider this an important showstopper...

Is anyone able to verify this and, if needed, update it to point to
GitHub (which is supported already)?

We have tested it in our office, it still points to SVN.

Anika was so kind to implement a solution/workaround:

https://github.com/OSGeo/grass/pull/39

Please test!

thanks,
Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog

martinl · July 1, 2019, 1:37pm

Hi,

ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

We have tested it in our office, it still points to SVN.

yes, its still pointing to SVN. I will try to take a look on this
issue after solving wingrass builds. Volunteers welcome in in case. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

neteler · July 1, 2019, 3:47pm

On Mon, Jul 1, 2019 at 3:37 PM Martin Landa <landa.martin@gmail.com> wrote:

Hi,

ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
> We have tested it in our office, it still points to SVN.

yes, its still pointing to SVN. I will try to take a look on this
issue after solving wingrass builds. Volunteers welcome in in case. Ma

After Anika's pull request it points to Github!
Please just test it...

Note: the only way we found is to use "svn export" in order to fetch a
subdir from https://github.com/OSGeo/grass-addons/
A dirty hack but apparently no other way when one does not want to
clone the entire repo for a single addon.

Markus

hellik · July 1, 2019, 8:23pm

>I will try to take a look on this

issue after solving wingrass builds.

Volunteers welcome in in case.

Anything to help/test regarding winGRASS builds? After upgrading to the
latest msys2/mingw stuff, compiling works locally here.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

neteler · July 15, 2019, 8:53pm

Hi

Markus Neteler <neteler@osgeo.org> schrieb am Mo., 1. Juli 2019, 17:47:

On Mon, Jul 1, 2019 at 3:37 PM Martin Landa <landa.martin@gmail.com> wrote:

Hi,

ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

We have tested it in our office, it still points to SVN.

yes, its still pointing to SVN. I will try to take a look on this
issue after solving wingrass builds. Volunteers welcome in in case. Ma

After Anika’s pull request it points to Github!
Please just test it…

Note: the only way we found is to use “svn export” in order to fetch a
subdir from https://github.com/OSGeo/grass-addons/
A dirty hack but apparently no other way when one does not want to
clone the entire repo for a single addon.

In absence of feedback I have recently merged it.

Still the backports are needed.
I’m traveling with phone only, anyone to do that?

Thanks,
Markus

hellik · July 16, 2019, 6:49am

Markus Neteler wrote

Hi

Markus Neteler <

neteler@

> schrieb am Mo., 1. Juli 2019, 17:47:

On Mon, Jul 1, 2019 at 3:37 PM Martin Landa <

landa.martin@

>

wrote:
>
> Hi,
>
> ne 30. 6. 2019 v 23:15 odesílatel Markus Neteler <

neteler@

>

napsal:
> > We have tested it in our office, it still points to SVN.
>
> yes, its still pointing to SVN. I will try to take a look on this
> issue after solving wingrass builds. Volunteers welcome in in case. Ma

After Anika's pull request it points to Github!
Please just test it...

Note: the only way we found is to use "svn export" in order to fetch a
subdir from https://github.com/OSGeo/grass-addons/
A dirty hack but apparently no other way when one does not want to
clone the entire repo for a single addon.

In absence of feedback I have recently merged it.

Still the backports are needed.
I'm traveling with phone only, anyone to do that?

see also:

[GRASS-web] How to install GRASS Add-Ons after migration from SVN to Github?
[https://lists.osgeo.org/pipermail/grass-web/2019-July/004919.html\]

[GRASS-user] Extensions
[https://lists.osgeo.org/pipermail/grass-user/2019-July/080446.html\]

for adapting winGRASS addon system for git.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

hellik · July 16, 2019, 6:52am

Helmut Kudrnovsky wrote

see also:

[GRASS-web] How to install GRASS Add-Ons after migration from SVN to
Github?
[https://lists.osgeo.org/pipermail/grass-web/2019-July/004919.html\]

[GRASS-user] Extensions
[https://lists.osgeo.org/pipermail/grass-user/2019-July/080446.html\]

for adapting winGRASS addon system for git.

there will be a 7.6.2 release needed to work with addons in git.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

neteler · July 16, 2019, 7:04am

Hi

Helmut Kudrnovsky <hellik@web.de> schrieb am Di., 16. Juli 2019, 08:52:

Helmut Kudrnovsky wrote

see also:

[GRASS-web] How to install GRASS Add-Ons after migration from SVN to
Github?
[https://lists.osgeo.org/pipermail/grass-web/2019-July/004919.html]

[GRASS-user] Extensions
[https://lists.osgeo.org/pipermail/grass-user/2019-July/080446.html]

for adapting winGRASS addon system for git.

there will be a 7.6.2 release needed to work with addons in git.

Exactly. But first the g.extension change needs to be backported which has not been done yet AFAIK.
On phone I cannot do that

Markus

martinl · July 16, 2019, 7:38am

Hi,

út 16. 7. 2019 v 9:04 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

Exactly. But first the g.extension change needs to be backported which has not been done yet AFAIK.
On phone I cannot do that

I can take a look. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

martinl · July 16, 2019, 8:41am

Hi,

út 16. 7. 2019 v 9:38 odesílatel Martin Landa <landa.martin@gmail.com> napsal:

> Exactly. But first the g.extension change needs to be backported which has not been done yet AFAIK.
> On phone I cannot do that

I can take a look. Ma

done. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Andy_Wickert · August 1, 2019, 4:43pm

Hi all,

I have just updated to GRASS 7.6.1 on the Ubuntu grass-devel ppa. It now find the set of relatively new add-ons that I have built (r.flowfill; r.richdem.*) with the “-l” flag, but when I try to install them, I receive, for example, “ERROR: Extension <r.flowfill> not found”. Is this simply that I must compile the most recent version from source, or is there some other problem?

Thanks!

Andy

On Tue, Jul 16, 2019 at 3:41 AM Martin Landa <landa.martin@gmail.com> wrote:

Hi,

út 16. 7. 2019 v 9:38 odesílatel Martin Landa <landa.martin@gmail.com> napsal:

Exactly. But first the g.extension change needs to be backported which has not been done yet AFAIK.
On phone I cannot do that

I can take a look. Ma

done. Ma

–
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

neteler · August 1, 2019, 5:25pm

Hi Andy,

On Thu, Aug 1, 2019 at 6:43 PM Andy Wickert <andrewwickert@gmail.com> wrote:

Hi all,

I have just updated to GRASS 7.6.1 on the Ubuntu grass-devel ppa. It now find the set of relatively new add-ons that I have built (r.flowfill; r.richdem.*) with the "-l" flag, but when I try to install them, I receive, for example, "ERROR: Extension <r.flowfill> not found". Is this simply that I must compile the most recent version from source, or is there some other problem?

I have merged it only now (before it was an open pull request).

Now the binaries need to be rebuild - or you compile yourself - or you
simply update the g.extension.py which does not need to be compiled
but just put into the right place.

Best
Markus

martinl · August 5, 2019, 8:12pm

Hi,

čt 1. 8. 2019 v 19:26 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

Now the binaries need to be rebuild - or you compile yourself - or you

it will require a new release 7.6.2. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

neteler · August 5, 2019, 8:22pm

On Mon, Aug 5, 2019 at 10:12 PM Martin Landa <landa.martin@gmail.com> wrote:

čt 1. 8. 2019 v 19:26 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
> Now the binaries need to be rebuild - or you compile yourself - or you

it will require a new release 7.6.2. Ma

Yes, perfect timing:

https://trac.osgeo.org/grass/milestone/7.6.2
-> 5th Aug 2019 was planned

Markus

martinl · August 5, 2019, 8:26pm

Hi,

po 5. 8. 2019 v 22:22 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

https://trac.osgeo.org/grass/milestone/7.6.2
-> 5th Aug 2019 was planned

yes, there is one blocker issue which should be solved before any
release. How to deal with svn keyword propagation in the code ($DATE$,
$REVISION$, ...). There is no straightforward replacement for git to
my knowledge. Any suggestion very welcome!

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

neteler · August 5, 2019, 8:38pm

On Mon, Aug 5, 2019 at 10:26 PM Martin Landa <landa.martin@gmail.com> wrote:

Hi,

po 5. 8. 2019 v 22:22 odesílatel Markus Neteler <neteler@osgeo.org> napsal:
> https://trac.osgeo.org/grass/milestone/7.6.2
> -> 5th Aug 2019 was planned

yes, there is one blocker issue which should be solved before any
release. How to deal with svn keyword propagation in the code ($DATE$,
$REVISION$, ...). There is no straightforward replacement for git to
my knowledge. Any suggestion very welcome!

The closest suggestion (for $Date$) I found was this
https://stackoverflow.com/questions/62264/dealing-with-svn-keyword-expansion-with-git-svn#72874

but overall it is everywhere discouraged as svn != git.

The only tag I really like is the date, at the bottom of the manual
pages. Would be great to keep the last-edited timestamps.

Markus

Ken_Mankoff · August 5, 2019, 8:41pm

On 2019-08-05 at 16:26 -04, Martin Landa <landa.martin@gmail.com> wrote...

Hi,

po 5. 8. 2019 v 22:22 odesílatel Markus Neteler <neteler@osgeo.org> napsal:

https://trac.osgeo.org/grass/milestone/7.6.2
-> 5th Aug 2019 was planned

yes, there is one blocker issue which should be solved before any
release. How to deal with svn keyword propagation in the code ($DATE$,
$REVISION$, ...). There is no straightforward replacement for git to
my knowledge. Any suggestion very welcome!

It seems like this is not officially supported, can be done easily with some scripts [1], but is not recommended [2].

Why is it needed?

I regularly use the gitinfo LaTeX package that provides a git commit hook. This hook simply puts latest hash (and some other commit data such as author, branch, date, etc.) into a file, that the LaTeX package then uses to make nice headers or footers with the commit info.

Could a commit hook make a file that is then somehow included in the footer of each HTML file?

-k.

[1] https://stackoverflow.com/questions/11534655/git-keyword-substitution-like-those-in-subversion
[2] https://git.wiki.kernel.org/index.php/GitFaq#Does_Git_have_keyword_expansion.3F