Bug 458906

This is clearly not a spec file problem. I see that the torcs tarball was made in a weird-ish way, where it extracts as "./foo/..." instead of "foo/...", so it's probably trying to do some changes to "." which aren't permitted in your case.

Using that ugly hack just to work around this is not something I'll implement. My opinion is that you shouldn't be building in a directory similar to /tmp in which multiple users can write, or if you do, deal with the consequences (i.e. clashes with some other user's files, a tarball extracting world writeable files which can potentially be overwritten by other users of the system while you're building, etc.).

I don't even understand how when adding "-T" you still get Source0 to get unpacked. And using "-D" seems completely wrong as you can get unexpected results if you re-run the build with the previous one not having completed %clean.

Come to think of it, I think (but haven't tested) that the only reason why "-T" has worked for you was because you had a leftover build and ran the next with "-D", meaning that if you clean out your /usr/src/redhat/ directory properly, your hack won't even work anymore!

Two solutions :
 * Inform the torcs developers that their tarball is different from the "usual" ones, and ask them if they can fix that.
 * Build in a directory tree which is only accesssible by your current user and no one else.

(In reply to comment #1)
> This is clearly not a spec file problem. I see that the torcs tarball was made
> in a weird-ish way, where it extracts as "./foo/..." instead of "foo/...", so
> it's probably trying to do some changes to "." which aren't permitted in your
> case.
> 
> Using that ugly hack just to work around this is not something I'll implement.
> My opinion is that you shouldn't be building in a directory similar to /tmp in
> which multiple users can write, or if you do, deal with the consequences (i.e.
> clashes with some other user's files, a tarball extracting world writeable
> files which can potentially be overwritten by other users of the system while
> you're building, etc.).
> 
> I don't even understand how when adding "-T" you still get Source0 to get
> unpacked. And using "-D" seems completely wrong as you can get unexpected
> results if you re-run the build with the previous one not having completed
> %clean.
> 
> Come to think of it, I think (but haven't tested) that the only reason why "-T"
> has worked for you was because you had a leftover build and ran the next with
> "-D", meaning that if you clean out your /usr/src/redhat/ directory properly,
> your hack won't even work anymore!
> 
> Two solutions :
>  * Inform the torcs developers that their tarball is different from the "usual"
> ones, and ask them if they can fix that.
>  * Build in a directory tree which is only accesssible by your current user and
> no one else.

Note that the scope of the 'leftover build' is within the build,
and previous build gets erased before the tarballs are re-extracted.

My previous hack was to extract the .tgz tarballs and make .bz2 's.
(maybe there IS a problem somewhere)

The following will Always work because it uses The Force:
%setup -q -T -D -a 1 -T -D -a 2 -T -D -a 3 -T -D -a 4
Using less force probably works because SELinux isn't ENFORCING.