Jump to content
funtoo forums
  • 0
Sign in to follow this  
aitikin

ego sync failing SOLVED

Question

Tried to sync this afternoon to get caught up and was greeted with this:

ego sync
Syncing meta-repo
fatal: Couldn't find remote ref refs/heads/1.2
error: pathspec '1.2' did not match any file(s) known to git.
error: pathspec 'python-kit' did not match any file(s) known to git.
error: pathspec '=' did not match any file(s) known to git.
error: pathspec '3.6-prime-release' did not match any file(s) known to git.
HEAD is now at 1261139 kit updates
Skipping repository kits/python-modules-kit/
fatal: Couldn't find remote ref refs/heads/1.2
ERROR: There was an error syncing meta-repo.

tried doing

mv /var/git/meta-repo /var/git/meta-repo.bkup
ego sync
Syncing meta-repo
fatal: Too many arguments.

usage: git clone [<options>] [--] <repo> [<dir>]

  [truncated for readability]

ERROR: Could not clone meta-repo at '/var/git/meta-repo'.

Other ideas/suggestions?

Edited by aitikin
Solved

Share this post


Link to post
Share on other sites

10 answers to this question

Recommended Posts

  • 0

For the sake of testing, I wiped my ego.conf and was greeted with the same errors.  Then put just one kit into it (using "ego config set kits core-kit 1.2-prime") for the sake of testing and was greeted with the same issues.

Share this post


Link to post
Share on other sites
  • 0

Double checked with updatedb and locate ego.conf:

locate ego.conf
/etc/ego.conf
/usr/share/doc/ego-2.6.0/ego.conf.5.rst.bz2
/usr/share/man/man5/ego.conf.5.bz2
/var/git/meta-repo/kits/core-kit/app-admin/ego/files/ego.conf

those all appear to me to be the standard documentation.  That last one has this:

cat /var/git/meta-repo/kits/core-kit/app-admin/ego/files/ego.conf
# This is the ego.conf file

[kits]

# You can set your default kits here. Unset kits will use the Funtoo default prime/master
# branch by default.

# python-kit = 3.6-prime

so it seems that even if it were somehow being misread as the ego.conf file, everything but [kits] is commented out.

Share this post


Link to post
Share on other sites
  • 0

Good to exclude the "easy" part ;)

And with you moving meta-repo out of the way, that part should be save as well.

1 hour ago, aitikin said:

/usr/share/doc/ego-2.6.0/ego.conf.5.rst.bz2

What version of ego do you have installed? Current version is ego-2.6.0-r2

Share this post


Link to post
Share on other sites
  • 0
9 hours ago, Oleg Vinichenko said:

try with:

mv /var/git/meta-repo /var/git/meta-repo.old

ego sync

Looks like that resolved it.  Ego syncing correctly right now.  jhan, I'm on 2.6.0 as that's what was available in my sync, once this updates, I'll get current.

Thanks!

Share this post


Link to post
Share on other sites
  • 0

The question now is, why this solved the problem because in the first post you said:

On 10/6/2018 at 1:50 AM, aitikin said:

tried doing


mv /var/git/meta-repo /var/git/meta-repo.bkup
ego sync
Syncing meta-repo
fatal: Too many arguments.

usage: git clone [<options>] [--] <repo> [<dir>]

  [truncated for readability]

ERROR: Could not clone meta-repo at '/var/git/meta-repo'.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×