On Saturday, 9 April 2016 12:14:00 PM AEST Christoph Berg wrote: > Sorry, this is just plain wrong. origtargz does not look into git > branches. If any of the backends used do that, which backend is used?
What's the point of saying that origtargz doesn't do what it does?
Fine, problem happens in backend but I'm not invoking backend directly...
> > Contents of orig.tar left behind.
>
> Where? How do they look like? Paste an example please.
git clone git://anonscm.debian.org/pkg-go/packages/cadvisor.git
cd cadvisor
origtargz
~~~~
/tmp/pristine-tar.39h8pOeFMT/cadvisor_0.22.2+dfsg.orig.tar.xz.tmp (1/1)
100 % 447.2 KiB / 1980.0 KiB = 0.226
pristine-tar: successfully generated ../cadvisor_0.22.2+dfsg.orig.tar.xz
Unpacking ../cadvisor_0.22.2+dfsg.orig.tar.xz
100 % 447.2 KiB / 1,980.0 KiB = 0.226
~~~~
At this point unpacked tarball contents left in "master";
"git status" show untracked files.
Problem is not happening if I run "origtargz --unpack=no" so I'm suggesting
to alter defaults to avoid unpacking when origtargz invoked from git
repository... I hope that make sense. Thanks.
--
All the best,
Dmitry Smirnov.
---
A creative man is motivated by the desire to achieve, not by the desire
to beat others.
-- Ayn Rand
signature.asc
Description: This is a digitally signed message part.
