Re: [GRASS-dev] [release planning] GRASS GIS 7.8.3
Hi,
so 2. 5. 2020 v 21:26 odesÃlatel Markus Neteler napsal:
> > * final check before hopefully promoting RC2 to final
> > * update: https://trac.osgeo.org/grass/wiki/Release/7.8.3-News
>
> Ok, I have copied the changes into:
> https://trac.osgeo.org/grass/wiki/Release/7.8.3-News
thanks for the great job!
> As this copy-pasting with *editing* is taking a lot of time, please:
>
> @devs: use meaningful PR/commit messages ("module: short change")!
> Otherwise all the unclear PRs have to opened and guessed what had been
> done.
I completely agree. It's embarrassing/time consuming to collect news
from unclear log messages. Please all devs (including me), take care
about log messages. You can add keyword like [news] to highlight the
change or so.
Martin
--
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
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.3
Hi, po 4. 5. 2020 v 15:59 odesÃlatel Markus Neteler napsal: > If there are no objections, I'd release G7.8.3 final in the next 24hs. +1 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
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.3
Hi, So far no real feedback but let's take it as positive :-) @wenzeslaus: it would be nice to have some of the master GitHub actions also in relbranch78, esp. compilation on Ubuntu (not the flake part etc). Possible? If there are no objections, I'd release G7.8.3 final in the next 24hs. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Busy SQLITE db
Ciao Luca, If you have stale processes e.g. on cluster nodes that have the DB opened this may occur. Also the file system can have an impact (e.g. writing to an SQLite DB on a CIFS file system from Linux is simply impossible). But that should give a different error message. So I would look for hanging processes... And you could try to copy the mapset, remove the old one and rename the copy back... Cheers Stefan -Original Message- From: grass-dev On Behalf Of Luca Delucchi Sent: mandag 4. mai 2020 10:47 To: GRASS-dev Subject: [GRASS-dev] Busy SQLITE db Hi all, I'm facing the problem with Busy SQLITE db using GRASS 7.8 in a HPC system. Reading other problems like that I saw a Metz answer [0] and another from Luis [1] but I'm not able to fix the problem. Now the mapset is unusable with vector. Do you have any idea how to solve the problem and where it come from? g.remove type=vector name=nuts2_lst_2003_daily -f Removing vector WARNING: Busy SQLITE db, already waiting for 10 seconds... WARNING: Busy SQLITE db, already waiting for 20 seconds... [0] http://osgeo-org.1560.x6.nabble.com/SQLITE-db-locking-problem-td5182180.html [1] https://gis.stackexchange.com/questions/321986/grass-what-to-do-when-the-sqlite-database-becomes-busy -- ciao Luca www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Busy SQLITE db
Hi all, I'm facing the problem with Busy SQLITE db using GRASS 7.8 in a HPC system. Reading other problems like that I saw a Metz answer [0] and another from Luis [1] but I'm not able to fix the problem. Now the mapset is unusable with vector. Do you have any idea how to solve the problem and where it come from? g.remove type=vector name=nuts2_lst_2003_daily -f Removing vector WARNING: Busy SQLITE db, already waiting for 10 seconds... WARNING: Busy SQLITE db, already waiting for 20 seconds... [0] http://osgeo-org.1560.x6.nabble.com/SQLITE-db-locking-problem-td5182180.html [1] https://gis.stackexchange.com/questions/321986/grass-what-to-do-when-the-sqlite-database-becomes-busy -- ciao Luca www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
