You are not logged in.

#1 2009-12-05 23:18:16

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

[SOLVED] Custom kernels compile with dirty aka when git repos go wild

I thought this was merely an issue with the 2.6.32 testing PKGBUILD, so I disregarded it for the time being. However, it seems that any kernel I now build via the ABS results in having "ga58433b-dirty" appended to the name, e.g. 2.6.31-zero-ga58433b-dirty (zero is my suffix). Compiling an absolutely vanilla kernel results in the same behavior: 2.6.31-ARCH-ga58433b-dirty

Where do I need to look to figure out what's causing this?

add: Arf... so this seems to be related to a process done by scripts/setlocalversion involving a git/svn/hg repo. However, I don't have any repos anywhere near where the build is happening. It would be hard for me to believe, but is this something that's happening upstream?

ARRRGGHHH... The repo in my ~/ apparently got out of control and even while being in an untracked subdirectory, git thought I was still in the repo. Now to figure out how to clean up that disaster...

Last edited by falconindy (2009-12-06 00:12:57)

Offline

Board footer

Powered by FluxBB