From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge --sync
Date: Sat, 15 Jul 2017 14:11:03 +0100 [thread overview]
Message-ID: <2507921.1XAsqjbQZa@peak> (raw)
In-Reply-To: <0LfC4q-1dyl601xWK-00oncI@mail.gmx.com>
On Saturday 15 Jul 2017 12:14:52 Daniel Wagener wrote:
> On Sat, 15 Jul 2017 11:00:01 +0100
>
> Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> > Hello list,
> >
> > Today I get this:
> >
> > # emerge --sync
> >
> > >>> Syncing repository 'gentoo' into '/usr/portage'...
> >
> > /usr/bin/git pull
> > remote: Counting objects: 25, done.
> > remote: Compressing objects: 100% (9/9), done.
> > remote: Total 25 (delta 15), reused 25 (delta 15), pack-reused 0
> > Unpacking objects: 100% (25/25), done.
> > From https://github.com/gentoo-mirror/gentoo
> >
> > c80ef88a736..b9cb9e0b42e stable -> origin/stable
> >
> > Updating c5ec29f674c..b9cb9e0b42e
> > error: Your local changes to the following files would be overwritten
> >
> > by merge:
> > metadata/layout.conf
> >
> > Please commit your changes or stash them before you merge.
> > Aborting
> > !!! git pull error in /usr/portage
> >
> > I can't imagine I'd ever make any changes to that file, especially
> > not using git, but I tried reverting to backups of /var
> > and /usr/portage from a week ago, but I still get the same error.
> > Using backups from two weeks ago also made no difference.
> >
> > I sync and update every day, with never a problem like this before.
> >
> > Can anyone see what else I should try? Should I just delete the
> > offending file? (I'll get some coffee meanwhile...)
>
> Why not just go there and do a "git diff"?
> It will show you what changed – maybe that gives an Idea what happened
It showed me that I'd changed "masters =" to "masters = gentoo" in
layout.conf, which I knew because I'd been told to at some time. But I did
that ages ago, long before my last sync yesterday, so what else has changed?
I didn't emerge anything yesterday, as confirmed by "grep completed
/var/log/emerge.log" (so it wasn't a failed emerge, Alexander).
> "git reset --hard" to reset the repository should solve that problem.
It has - thanks Daniel. I haven't tried to understand the ins and outs of
git, I just use it blindly for --sync.
--
Regards
Peter
next prev parent reply other threads:[~2017-07-15 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 10:00 [gentoo-user] Can't emerge --sync Peter Humphrey
2017-07-15 10:05 ` Adam Carter
2017-07-15 10:14 ` Daniel Wagener
2017-07-15 13:11 ` Peter Humphrey [this message]
2017-07-15 14:07 ` Marc Joliet
2017-07-15 15:47 ` Peter Humphrey
2017-12-15 11:44 ` Marc Joliet
2017-07-15 10:22 ` Alexander Kapshuk
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 13:30 [gentoo-user] can't " Matias Grana
2006-05-15 14:19 ` Pablo Antonio
2006-05-15 14:37 ` Neil Bothwick
2006-05-15 16:02 ` Matias Grana
2006-05-15 22:45 ` Pablo Antonio
2006-05-17 23:08 ` louis brazeau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2507921.1XAsqjbQZa@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox