After some intense doubts about my sanity, I noticed that I fell into a simple trap: I had fixed a bug in the i.segment.uspo addon quite a while ago, but the same bug kept on popping up, even though I have reinstalled the addon.
Finally, I remembered that on the university's HPC it is still version 7.6.0 that is running, and that version gets its addons still from trac.
I would assume that there are still quite a lot of GRASS 7.6.0 installations out there (it was released less than a year ago). Would it somehow be envisageable to automatically update the svn addon repository on trac with the updates in github ? I have no idea what this would mean in terms of work, but if it is a simple thing to do, it might be good to have in the transition period before we can assume that no 7.6.0 installations are out there.
čt 31. 10. 2019 v 11:02 odesílatel Moritz Lennert
<mlennert@club.worldonline.be> napsal:
I would assume that there are still quite a lot of GRASS 7.6.0
installations out there (it was released less than a year ago). Would it
we definitely need to release 7.6.2 (not sure if all g.extension fixes
have been backported). Ma
I agree that a release of 7.6.2 is part of the solution, but people will not switch immediately to that new version. Some way of ensuring that any 7.6.x will get the latest and greatest in addons would be good if feasible without too much work (some automatic github -> svn updates ?).
On Thu, Oct 31, 2019 at 11:08 AM Martin Landa <landa.martin@gmail.com> wrote:
Hi,
čt 31. 10. 2019 v 11:02 odesílatel Moritz Lennert
<mlennert@club.worldonline.be> napsal:
> I would assume that there are still quite a lot of GRASS 7.6.0
> installations out there (it was released less than a year ago). Would it
What about adding an Apache redirect rule for the addon downloads?
we definitely need to release 7.6.2 (not sure if all g.extension fixes
have been backported). Ma
diff -ru grass78_git/scripts/g.extension grass76_git/scripts/g.extension
--> no differences
Careful: there is another unrelated change which would be published with 7.6.2: https://trac.osgeo.org/grass/ticket/3815#comment:14
I am not very happy about this "do not use ZSTD if available" change
which would affect 7.6 users after update.
(due to that I am enforcing
export GRASS_COMPRESSOR=ZSTD
everywhere on my systems with GRASS GIS installation).
On Thu, Oct 31, 2019 at 5:49 PM Moritz Lennert
<mlennert@club.worldonline.be> wrote:
On 31/10/19 11:58, Markus Neteler wrote:
> Hi,
>
> On Thu, Oct 31, 2019 at 11:08 AM Martin Landa <landa.martin@gmail.com> wrote:
>>
>> Hi,
>>
>> čt 31. 10. 2019 v 11:02 odesílatel Moritz Lennert
>> <mlennert@club.worldonline.be> napsal:
>>> I would assume that there are still quite a lot of GRASS 7.6.0
>>> installations out there (it was released less than a year ago). Would it
>
> What about adding an Apache redirect rule for the addon downloads?
>
>> we definitely need to release 7.6.2 (not sure if all g.extension fixes
>> have been backported). Ma
>
> diff -ru grass78_git/scripts/g.extension grass76_git/scripts/g.extension
> --> no differences
But there is a difference between the 7.6.1 tag and 76_releasebranch.