repo v2.6 prerelease

[Mike Frysinger]

I've created a new release, but not yet pushed it live.  Instead, people have to opt-in to it.  For example:

  repo init --repo-branch master

  repo selfupdate

  repo version

So please bang on things and let us know how it goes.  Even "it works" is useful feedback as it means I'm not the only one running it :).
If things look good the rest of this week, I'll publish it next week.

Here's the short log since the last release.

2fe84e17b923 (George Engelbrecht) project.py: Remove extraneous ','
1122353683fa (Mike Frysinger) Revert "commit-msg: Insert Change-Id at start of trailers"
b6871899be40 (George Engelbrecht) project: have clone.bundle failures print better diagnostics
8e0fe1920eee (Anders Björklund) Use hash for ControlPath instead of full variables
d086467012e1 (Karsten Pfeiffer-Raddatz) forall.py: Close file after removing the stream
2735bfc5ff65 (Marcos Marado) tests: fix SetupGnuPG test
653f8b711be3 (David Pursehouse) commit-msg: Insert Change-Id at start of trailers
9bc283e49bcb (George Engelbrecht) sync: add retry to fetch operations
b4a6f6d7981f (Mike Frysinger) version: include tag commit date for easy reference
-mike

[Mike Frysinger]

gLinux already has python3 installed and repo supports it fine.  i use it constantly.  so something else is wrong on your system.

make sure `repo version` reports recent versions and make sure you have `python3 --version` reporting 3.6+.

-mike

On Thu, Apr 16, 2020 at 2:40 AM Al Sutton <alsu...@google.com> wrote:

Running through this on a gLinux desktop I got the following warning;

remote: Counting objects: 1, done    
remote: Finding sources: 100% (9/9)          
remote: Total 9 (delta 3), reused 9 (delta 3)        
info: A new version of repo is available

info: Restarting repo with latest version
repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.

The default python on gLinux is 2.7.17;

alsutton@ws:Android $ which python
/usr/bin/python
alsutton@ws:Android $ python --version
Python 2.7.17

Can something be done to ensure compatibility with our standard corporate configuration before this is rolled out? Asking all engineers using it to update to a non-standard configuration seems like a lot of work to push on folk. It might be worth talking to CorpEng about a python version bump to ensure compatibility.

--
You received this message because you are subscribed to the Google Groups "Repo tool (git-repo) announcements" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-repo-annou...@google.com.
To view this discussion on the web visit https://groups.google.com/a/google.com/d/msgid/git-repo-announce/CAAbOScndYwfxaMW5D1NsUh%2BZxnS%3DEG49iokN7epVQLP1S-cNCQ%40mail.gmail.com.

--

Al Sutton Software Engineer, Android alsu...@google.com

[Mike Frysinger]

i posted a fix for the selfupdate path triggering that warning:

https://gerrit-review.googlesource.com/c/git-repo/+/263272

-mike

[Mike Frysinger]

[ +repo-discuss ]

if your existing workspace is repo-2.5, then you should be able to switch to master & upgrade to repo-2.6.  i just checked here and it worked.

$ repo version

repo version v2.5

repo launcher version 2.5

...

$ repo selfupdate

repo version v2.5 is current

$ repo init --repo-rev=master

$ repo selfupdate

$ repo version

repo version v2.6

repo launcher version 2.5

...

-mike

On Thu, Apr 16, 2020 at 12:17 PM Lee Shombert <shom...@google.com> wrote:

Hi Mike - can I update an existing workspace, or does this only work on new workspaces? I tried this on two existing 

workspaces and now 'repo sync' fails.  (Not to worry - I am just rebuilding the workspaces with v2.6, to see what happens).

Lee

[Mike Frysinger]

I've pushed v2.6 to the stable branch for release now.

NB: Repo will automatically check for & upgrade itself.  There is no need for users to handle this themselves.  This happens once every 24hrs.  If you want to force it locally, run `repo selfupdate`.

-mike

[唐木村]

@Dear Mike Frysinger

https://gerrit.googlesource.com/git-repo/+/refs/heads/master/docs/python-support.md

Python 3.6 (released Dec 2016) is required by default starting with repo-2.x.

whether could repo-2 backport python3.5 support ???

because our large android team developer use ubuntu 16.04 LTS that is default python 3.5

in fact, upgrade linux system python version is realy difficult

when we use repo and get warn like below

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.

what any Python 3.6 feature repo2 using or use in plan ???

$ repo init -u https://android.googlesource.com/platform/manifest

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.

Downloading Repo source from https://gerrit.googlesource.com/git-repo

remote: Finding sources: 100% (9/9)

remote: Total 9 (delta 1), reused 9 (delta 1)
Unpacking objects: 100% (9/9), done.

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.

Downloading manifest from https://android.googlesource.com/platform/manifest
Receiving objects: 100% (76756/76756), 52.73 MiB | 34.72 MiB/s, done.
Resolving deltas: 100% (22642/22642), done.
remote: Counting objects: 9, done        
remote: Finding sources: 100% (414/414)          
remote: Total 414 (delta 134), reused 393 (delta 134)        
Receiving objects: 100% (414/414), 1.90 MiB | 0 bytes/s, done.
Resolving deltas: 100% (134/134), completed with 27 local objects.

在 2020年4月29日星期三 UTC+8上午12:15:10，Mike Frysinger写道：

[David Ostrovsky]

Am Samstag, 2. Mai 2020 11:45:59 UTC+2 schrieb 唐木村:

@Dear Mike Frysinger

https://gerrit.googlesource.com/git-repo/+/refs/heads/master/docs/python-support.md

Python 3.6 (released Dec 2016) is required by default starting with repo-2.x.

whether could repo-2 backport python3.5 support ???

because our large android team developer use ubuntu 16.04 LTS that is default python 3.5

in fact, upgrade linux system python version is realy difficult

Ubuntu 16.04 is two LTS releases behind: 18.04 LTS and 20.04 LTS.

Why would you expect from the community driven project to support outdated releases of third party dependencies? It's not just Ubuntu LTS, of course, the same applies to Java releases, Elasticsearch, Git core version. etc. 

[David Pursehouse]

It's quite common for corporate environments to be stuck with older dependencies.  At $former-employer we were at least 2 LTS releases behind the latest.  I don't think it's unreasonable for projects like git-repo to consider such cases.

 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/926e1cab-f5cb-4d65-84fc-aadc2fd3a8cf%40googlegroups.com.

[Martin Fick]

Perhaps David doesn't know what the 'L' in 'LTS' means? It stands for 'Long ', and for Ubuntu that specifically means '5 years', and not 'until the next nightly snapshot release'.

[唐木村]

ok, thanks to reply, and thanks community contiune to improve git-repo

maybe keep to use repo v1 for ubuntu 16.04 LTS version that is better choice

在 2020年5月2日星期六 UTC+8下午6:33:55，David Pursehouse写道：

On Sat, May 2, 2020 at 7:10 PM David Ostrovsky <david.o...@gmail.com> wrote:

Am Samstag, 2. Mai 2020 11:45:59 UTC+2 schrieb 唐木村:

@Dear Mike Frysinger

https://gerrit.googlesource.com/git-repo/+/refs/heads/master/docs/python-support.md

Python 3.6 (released Dec 2016) is required by default starting with repo-2.x.

whether could repo-2 backport python3.5 support ???

because our large android team developer use ubuntu 16.04 LTS that is default python 3.5

in fact, upgrade linux system python version is realy difficult

Ubuntu 16.04 is two LTS releases behind: 18.04 LTS and 20.04 LTS.

Why would you expect from the community driven project to support outdated releases of third party dependencies? It's not just Ubuntu LTS, of course, the same applies to Java releases, Elasticsearch, Git core version. etc. 

It's quite common for corporate environments to be stuck with older dependencies.  At $former-employer we were at least 2 LTS releases behind the latest.  I don't think it's unreasonable for projects like git-repo to consider such cases.

 

--
--
To unsubscribe, email repo-d...@googlegroups.com

More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to repo-d...@googlegroups.com.

[6020peaks /\/\/\]

Hi,

I am having exactly the same issue and cannot find out the reason why repo keeps using my python 2.7.17 instead of the newer 3.6.9. `python --version` reports 2.7.17 and `python3 --version` reports 3.6.9. `repo --version` reports v2.5, but below I see it reports repo launcher version 1.23. Do I have to manually map python3 to python, so that repo works with the latest version?

Thanks for your help!

To unsubscribe from this group and stop receiving emails from it, send an email to git-repo...@google.com.

To view this discussion on the web visit https://groups.google.com/a/google.com/d/msgid/git-repo-announce/CAAbOScndYwfxaMW5D1NsUh%2BZxnS%3DEG49iokN7epVQLP1S-cNCQ%40mail.gmail.com.