[Dev] problem of wrong prinstine tar file

Lehtonen, Markus markus.lehtonen at intel.com
Fri Oct 18 09:01:38 GMT 2013


Yes, that is obviously caused by a "broken" pristine-tar branch, generated by a buggy version of pristine-tar.

There must be dozens (or even hundreds) of packages with broken pristine-tar branches, because of this. We should go through all the packages and repair the broken branches in co-operation with the package maintainers. In order to fix the pristine-tar branch without modifying/cluttering the upstream branch and upstream tags, one should use the pristine-tar tool directly. Just re-commit the broken tarballs to pristine-tar branch, e.g.:
1. Get the release tarball from upstream, e.g.
  $ http://curl.haxx.se/download/curl-7.32.0.tar.bz2
2. Re-commit it to pristine-tar, e.g.:
  $ pristine-tar commit curl-7.32.0.tar.bz2 upstream/7.32.0

Another thing: I'd actually like to change gbs to NOT ignore pristine-tar errors. Currently gbs falls back to generating the tarball from the upstream tag, if pristine-tar fails. Thus, we cannot be sure what sources we're actually using when building the package. My proposal is to change gbs build (or export) to fail if pristine-tar branch is present and pristine-tar checkout fails.


On 10/18/13 9:35 AM, "Zhang, Qiang Z" <qiang.z.zhang at intel.com<mailto:qiang.z.zhang at intel.com>> wrote:

This is caused by corrupt tarball in pristine-tar branch, and gbs will use upstream branch to generate tar ball.
It will not affect the final build results.

To fix pristine-tar branch, please use new version of pristine-tar, which will be released next week together with gbs, to commit new tar ball to pristine-tar branch.

Markus, please correct me if I am wrong, as I can’t reproduce this issue with gbs import and export.


From: Dong, Junfeng
Sent: Friday, October 18, 2013 1:47 PM
To: Zhang, Qiang Z
Cc: dev at lists.tizen.org<mailto:dev at lists.tizen.org>
Subject: problem of wrong prinstine tar file

Hi Qiang,
Do you have any idea about the following error, which is reported when I build gdb locally. Is it the bug of gbs or gdb?

~/next/source/gdb> gbs build -A armv7l -B ~/GBS-ROOT-bad -D ../public.conf
info: generate repositories ...
info: start building packages from: /home/candy/next/source/gdb (git)
info: prepare sources...
info: start export source from: /home/candy/next/source/gdb/ ...
info: Generating patches from git (upstream/7.5.1..HEAD)
xdelta: expected from file (/tmp/pristine-tar.oaklrlIv0r/recreatetarball) of length 169574400 bytes
xdelta: expected from file (/tmp/pristine-tar.oaklrlIv0r/recreatetarball) of length 169574400 bytes
pristine-tar: Failed to reproduce original tarball. Please file a bug report.
pristine-tar: failed to generate tarball
error: Couldn't checkout "gdb-7.5.1.tar.bz2": /usr/bin/pristine-tar returned 2
info: gdb-7.5.1.tar.bz2 does not exist, creating from 'upstream/7.5.1'
info: package files have been exported to:


Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

More information about the Dev mailing list