From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: git-diff-files and fakeroot
Date: Tue, 17 Jan 2006 00:27:59 -0500 [thread overview]
Message-ID: <20060117052758.GA22839@mythryan2.michonline.com> (raw)
In-Reply-To: <7vzmlvk2bs.fsf@assigned-by-dhcp.cox.net>
On Mon, Jan 16, 2006 at 06:36:39PM -0800, Junio C Hamano wrote:
> Ryan Anderson <ryan@michonline.com> writes:
>
> > I've been trying to track down a strange issue with building kernels
> > (and scripts/setlocalversion) and finally realized the problem was the
> > when run under fakeroot, git-diff-files thinks everything is changed
> > (deleted, I believe)
>
> BTW, Ryan, I suspect this is where you try to append "-dirty" to
> the version number. But I wonder why you are doing the build
> under fakeroot to begin with? Wasn't the SOP "build as
> yourself, install as root"?
That's exactly what started this search, because I was running
"make deb-pkg". (Effectively.) dpkg-buildpackage wants to think it is
running as root, either via sudo or via fakeroot. I had my build
environment switched over entirely to fakeroot, as it just seems to be a
better practice, but I've temporarily switched back to sudo.
However, your explanation has pointed out to me how I can solve this -
run "fakeroot -u" instead of "fakeroot", and I think it will be fixed.
lkml cc:ed to hopefully stick this in an archive where someone else will
find it.
--
Ryan Anderson
sometimes Pug Majere
next parent reply other threads:[~2006-01-17 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43CC5231.3090005@michonline.com>
[not found] ` <7vzmlvk2bs.fsf@assigned-by-dhcp.cox.net>
2006-01-17 5:27 ` Ryan Anderson [this message]
2006-01-17 5:59 ` Kyle Moffett
2006-01-17 6:08 ` Ryan Anderson
2006-01-17 18:10 ` Sam Ravnborg
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=20060117052758.GA22839@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®