Something must have changed in the subversion repository and I want to
confirm that this is a deliberate change.
At least once a week when I'm working with grass I start by checking for
upgrades using 'svn up'. The past month or two the server's response is that
I'm already at the current revision, just now that's at revision 72862. I'm
having trouble understanding how upgrades are being pushed to me without my
knowledge or active requests.
Please explain this to me.
Thanks,
Rich
Rich,
On Wed, Jun 20, 2018 at 11:41 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
Something must have changed in the subversion repository and I want to
confirm that this is a deliberate change.
... nothing was changed. The server operates as before.
At least once a week when I'm working with grass I start by checking for
upgrades using 'svn up'. The past month or two the server's response is that
I'm already at the current revision, just now that's at revision 72862. I'm
having trouble understanding how upgrades are being pushed to me without my
knowledge or active requests.
As of now, i.e. date -u
Thu Jun 21 20:49:37 UTC 2018
... the SVN trunk revision is 72867.
HTH
Markus
On Thu, 21 Jun 2018, Markus Neteler wrote:
As of now, i.e. date -u
Thu Jun 21 20:49:37 UTC 2018... the SVN trunk revision is 72867.
Markus,
Then I wonder what changed here:
$ date -u
Thu Jun 21 21:23:28 UTC 2018
$ svn up
Updating '.':
At revision 72869.
Any thoughts?
Best regards,
Rich
Rich Shepard wrote
On Thu, 21 Jun 2018, Markus Neteler wrote:
As of now, i.e. date -u
Thu Jun 21 20:49:37 UTC 2018... the SVN trunk revision is 72867.
Markus,
Then I wonder what changed here:
$ date -u
Thu Jun 21 21:23:28 UTC 2018$ svn up
Updating '.':
At revision 72869.Any thoughts?
Best regards,
Rich
_______________________________________________
grass-user mailing list
grass-user@.osgeo
as already mentioned in another mail, the easiest thing to stay updated
about svn activities is to look at:
https://lists.osgeo.org/pipermail/grass-commit/
for svn related command options, the easiest thing is to consult the svn
manual.
-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
On Thu, 21 Jun 2018, Helmut Kudrnovsky wrote:
as already mentioned in another mail, the easiest thing to stay updated
about svn activities is to look at:
https://lists.osgeo.org/pipermail/grass-commit/
Helmut,
This morning I checked out the trunk, configured and built it. This told
me the revision number is 72869. I assume that's the most current revision
as it's the at the bottom of that web page dated Thu Jun 21 13:57:47 PDT
2018.
for svn related command options, the easiest thing is to consult the svn
manual.
As a non-developer who does not commit changes I use either co or up.
Usually the latter. The other commands are not appropriate for me.
Neither of these explain why 'svn up' returns the result that I'm at the
latest revision when no new code has been downloaded.
Regards,
Rich
Rich,
On Fri, Jun 22, 2018 at 12:02 AM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
...
This morning I checked out the trunk, configured and built it. This told
me the revision number is 72869.
Please tell us where you exactly see this number.
I assume that's the most current revision
as it's the at the bottom of that web page dated Thu Jun 21 13:57:47 PDT
2018.
Which web page is that (URL?)?
Just to be sure that we speak about the same things.
thanks,
Markus
On Sat, 23 Jun 2018, Markus Neteler wrote:
This morning I checked out the trunk, configured and built it. This told
me the revision number is 72869.Please tell us where you exactly see this number.
Markus,
Yesterday morning the revision was 72869 (as above). Just now:
$ svn up
Updating '.':
At revision 72886.
I have not explicitly downloaded anything from the repository since I
checked out and built 72869, so I don't know why svn tells me my local
source is at revision 72886.
I assume that's the most current revision as it's the at the bottom of
that web page dated Thu Jun 21 13:57:47 PDT 2018.Which web page is that (URL?)?
https://lists.osgeo.org/pipermail/grass-commit/2018-June/thread.html
which shows: Last message date: Sat Jun 23 01:55:37 PDT 2018/ Archived on:
Sat Jun 23 01:55:39 PDT 2018
Just to be sure that we speak about the same things.
Does this clarify my questions?
Best regards,
Rich
Rich,
On 6/23/18, Rich Shepard <rshepard@appl-ecosys.com> wrote:
...
I have not explicitly downloaded anything from the repository since I
checked out and built 72869, so I don't know why svn tells me my local
source is at revision 72886.
Yes. The "confusion" may arise from the fact that rev numbers are
handled globally across the GRASS GIS SVN repo which also contains
grass-addons, sandbox and more.
Any change leads to an increment of the revision number. The last
changes happened in grass-addons, pushing the rev number to currently
revision 72887. However, that does not necessarily mean that trunk
received an update.
See the attached screenshot for illustration.
HTH,
Markus
On Sat, 23 Jun 2018, Rich Shepard wrote:
Yesterday morning the revision was 72869 (as above). Just now:
$ svn up
Updating '.':
At revision 72886.
Markus,
My response to your clarification was mis-handled (by me) and not sent.
Now I understand that when 'svn up' does not download any files it's because
the source here is at the latest _trunk_ revision. I should have looked more
closely at the checkin log web page.
Thanks very much,
Rich