View previous topic :: View next topic |
Author |
Message |
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Tue Dec 01, 2015 9:51 am Post subject: emerge --sync complaining about /usr/portage/.git existing |
|
|
My cursory search has been fruitless, so here's the issue. When I type emerge --sync, I get the following:
Code: | >>> Syncing repository 'gentoo' into '/usr/portage'...
!!! /usr/portage appears to be under revision control (contains .git).
!!! Aborting rsync sync (override with "sync-rsync-vcs-ignore = true" in repos.conf). |
Has Gentoo gone to git like funtoo? If not, then why was a /usr/portage/.git directory delivered with last night's update? If there is a choice, I'd much prefer git. Just let me know how to set it up. Thanks.
Cheers,
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
DawgG l33t
Joined: 17 Sep 2003 Posts: 866
|
Posted: Tue Dec 01, 2015 10:19 am Post subject: |
|
|
i experienced the same thing yesterday - and just deleted /usr/portage/.git (hasn't reappeared since).
my guess is that someone with write-perms just accidentally put the dir there. i also guess that switching portage to git would deserve some kind of announcement :wink: _________________ DUMM KLICKT GUT. |
|
Back to top |
|
|
franzf Advocate
Joined: 29 Mar 2005 Posts: 4565
|
|
Back to top |
|
|
dilfridge Developer
Joined: 18 Sep 2010 Posts: 120 Location: Regensburg, Germany
|
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Wed Dec 02, 2015 7:31 am Post subject: |
|
|
Awesome. That was quick.
Cheers,
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
Atom2 Apprentice
Joined: 01 Aug 2011 Posts: 185
|
Posted: Fri Dec 04, 2015 1:32 am Post subject: |
|
|
dilfridge,
dilfridge wrote: | The bug is now fixed, but you still need to manually remove the .git directory once. | The bug as such may be fixed, but in my view the handling of the sync problem from emerge was not in line with standard unix practices: If, for whatever reason, a command fails (and in my view this clearly was a failure), the command should return with a non-zero exit code. Despite that the return code was zero and therefore the problem went unnoticed for a number of days in my automated script.
I don't know whether that's a big deal to change, but exiting with a proper return code would have been nice and should probably be amended in order to avoid this in the future.
Thanks Atom2 |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Sat Dec 05, 2015 2:48 am Post subject: |
|
|
Thanks for the info, I had that problem last night.
Time to sync my box |
|
Back to top |
|
|
|