mock scm write_tar - file changed as we read it

Marko Myllynen myllynen at redhat.com
Mon Nov 7 07:44:55 UTC 2011


Hi,

On 2011-11-05 21:50, Alfred Landrum wrote:
> I'm using mock 1.1.16 on fedora 15, and am hitting an error with the
> 'write_tar' related scm functionality.  It looks like the creation of the
> .tar.gz of the source is confusing tar, as it's being created within the
> source dir. Example output:
> 
> DEBUG: Executing command: ['tar', 'czf',
> '/tmp/tmpmnCogc.mock-scm.less/less/less-1.tar.gz', '--exclude',
> '/tmp/tmpmnCogc.mock-scm.less/less/less-1.tar.gz',
> '--xform=s,^less,less-1,', 'less']
> DEBUG: tar: less/less-1.tar.gz: file changed as we read it
> 
> I would expect the '--exclude' to have tar not care about any timestamps
> on less-1.tar.gz, but it looks like it does.  

the tarball generating code tried to be perhaps a bit too smart with all
the fancy tar options, it was also incompatible with RHEL 5 tar. While
making it RHEL 5 compatible, the code leading to the above issue was
changed at the same time (BZ#749518).

Please try mock 1.1.17 from updates-testing, it should work.

Cheers,

-- 
Marko Myllynen


More information about the buildsys mailing list