fatal: <project> invalid "path": .: bad component: .

[Jim Palte]

We've been using repo for a while.  This morning, it stopped working.

The message being received is:

+ repo init -u https://npi-optionality.googlesource.com/manifests -m default.xml

... A new version of repo (2.12) is available.

... You should upgrade soon:

    cp /workspace/louhi_ws/manifests/.repo/repo/repo /usr/local/bin/repo

Downloading manifest from https://npi-optionality.googlesource.com/manifests

fatal: manifest 'default.xml' not available

fatal: <project> invalid "path": .: bad component: .

A build at 9:15am (PT) this morning worked.  The build at 10:20a this morning failed.

It looks like a newer version doesn't like our manifest files.

Questions: 

How do I revert to the older version of repo so my builds are functional again.

How do I figure out what the new version doesn't like about the manifest files so

  I can fix them.

Thanks

[Jim Palte]

We moved the directory in the manifest file to get past this problem.

[Yaobin Wen]

I encountered the same issue this afternoon, too. In my case, the error was reported because we have a project definition as follows:

```xml

<project
    name="proj_name"
    groups="grp"
    path="." />

```

`repo` since v2.13 doesn't allow `path` to be `.`. I don't have the permission to view your manifest XML file but I guess you have the same `path="."` attribute.

This "issue" starts to occur since v2.13 so the last working version for me is v2.12.2 (maybe also for you). To roll back to an earlier version of repo, run `repo init --repo-rev="v2.12.2"`. I found the change was introduce in the following commit:

```

commit a29424ea6d6f5a38ef9c25141c9f095161dbd3ff

    manifest: validate project name & path and include name attributes

    

    These attribute values are used to construct local filesystem paths,

    so apply the existing filesystem checks to them.

    

    Bug: https://crbug.com/gerrit/14156

    Change-Id: Ibcceecd60fa74f0eb97cd9ed1a9792e139534ed4

```

But I didn't understand what you meant when you said "moved the directory in the manifest file". What did you mean by "move"??

[Jim Palte]

We changed our directory referenced as "." to be a subdirectory name, then modified the rest of the build procedure to accommodate that change.