update mercurial to 3.7.3 on vcs-sync machines

RESOLVED FIXED

Status

Product:
Developer Services
Component:
General
RESOLVED FIXED
Reported:
2 years ago
Modified:
2 years ago

People

(Reporter: hwine, Assigned: hwine)

Tracking

Details

(Whiteboard: [vcs-sync] [vcs-sync-legacy])

(Assignee)

Description

•
2 years ago 
Need to update on both legacy and modern
(Assignee)

Comment 2

•
2 years ago 
legacy update (manual):

[vcs2vcs@ip-172-31-26-60 hg]$ type -a hg
hg is /home/vcs2vcs/bin/hg
[vcs2vcs@ip-172-31-26-60 hg]$ head -2 /home/vcs2vcs/bin/hg
#!/home/vcs2vcs/venv/hg/bin/python2.7
#
[vcs2vcs@ip-172-31-26-60 hg]$ pwd
/home/vcs2vcs/venv/hg
[vcs2vcs@ip-172-31-26-60 hg]$ . bin/activate
(hg)[vcs2vcs@ip-172-31-26-60 hg]$ pip freeze | grep mercurial
mercurial==3.7.2+19.ec62f08b4a8f
(hg)[vcs2vcs@ip-172-31-26-60 hg]$ pip install --upgrade mercurial==3.7.3
Collecting mercurial==3.7.3
  Downloading mercurial-3.7.3.tar.gz (4.6MB)
    100% |████████████████████████████████| 4.6MB 186kB/s 
Installing collected packages: mercurial
  Found existing installation: mercurial 3.7.2+19.ec62f08b4a8f
    Uninstalling mercurial-3.7.2+19.ec62f08b4a8f:
      Successfully uninstalled mercurial-3.7.2+19.ec62f08b4a8f
  Running setup.py install for mercurial ... done
Successfully installed mercurial-3.7.3
(hg)[vcs2vcs@ip-172-31-26-60 hg]$ deactivate
[vcs2vcs@ip-172-31-26-60 hg]$ hg --version
Mercurial Distributed SCM (version 3.7.3)
(see https://mercurial-scm.org for more information)

Copyright (C) 2005-2016 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[vcs2vcs@ip-172-31-26-60 hg]$
 (Assignee)

Updated

•
2 years ago
Assignee: nobody → hwine
Status: NEW → ASSIGNED
 (Assignee)

Comment 3

•
2 years ago 
comment 1 contains the configuration update for vcs-sync modern. However, that only takes effect when the venv is rebuild from scratch.

To deploy, a manual process was used on each virtual env:
  source path/to/vcs_dir/build/venv/bin/activate
  pip install --upgrade mercurial==3.7.3

After ensuring that instance was idle by acquiring the lock file. Roughly:
  cd path/to/vcs_dir
  touch hwine.lock
  while ! ln hwine.lock this_instance_name.lock ; do sleep 10; done
  # when loop exits, you have the lock
  # update per above
  rm this_instance_name.lock
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.