Both a .buildstamp and .buildstamp_1 ?!?

[Joel Andres Granados]

Peter Åstrand wrote:
> Installation of our nightly build of our custom distribution failed with 
> the error message:
> 
> "The OURDIST installation tree in that directory does not seem to match 
> your boot media."
> 
> After some serious debugging, I found out the problem: In minstg2.img, 
> there were *two* buildstamps:
> 
> -rw-r--r-- 1 root root 61 27 jan 12.51 squashfs-root/.buildstamp
> -rw-r--r-- 1 root root 61 28 jan 12.52 squashfs-root/.buildstamp_1
> 
> Only the second one matches the initrd buildstamp. Any idea why this 
> happens? My guess is that this is some kind of intermittent problem, but 
> those gives me a bad feeling...
> 
> Best regards, 
> ---
> Peter Åstrand		ThinLinc Chief Developer
> Cendio AB		http://www.cendio.se
> Wallenbergs gata 4
> 583 30 Linköping	Phone: +46-13-21 46 00
> 
> 
> ------------------------------------------------------------------------
> 
> --
> Fedora-buildsys-list mailing list
> Fedora-buildsys-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

This is kinda strange.  The buildstamp file gets created by mk-image (anaconda scripts)
to create the buildstamp the mk-image script erases buildstamp and then creates a new
file.  Additionally I could not find any trace of replacing the name of buildstamp with
`buildstamp_$count`.  What are you using to make your tree?  on what is your distro based
on, fedora, centos?  what versions?
I *think* what is happenning is that you are compossing on top of an already composed tree,
and your compose tool does not want to replace the existing .buildstamp file, so it makes 
another with a similar name.  I could be wrong though.
In any case you should check the compose tool and the anconda scritps from the version you
are using.

regards

-- 
Joel Andres Granados
Red Hat / Brno, Czech Republic