Bug#820494: origtargz: leaves "upstream" files in "master" after invocation

[Dmitry Smirnov]

On Saturday, 9 April 2016 11:49:11 AM AEST Christoph Berg wrote:
> I think your idea from what the program is doing is just wrong.

My ideas of what origtargz is doing are not wrong. However I admit that I 
know little of origtargz internals and how precisely it works.


> There's two parts:
> 
> 1) tarball downloading - that makes sure there is a
> ../foo_1.0.orig.tar.* file for the current version of your package.

This is not the case.

 
> 2) unpacking - if the current directory contains debian/ only, or
> --unpack is passed, origtargz does the equivalent of "rm -rf
> *-except-debian", and unpacks the orig tarball to the current
> directory.

Orig tarball is generated from git repository. I don't know why are you 
talking about "unpacking". You have to have orig.tar to unpack in first 
place. I'm using "origtargz" to generate tarball.

Maybe the problem is just lack of clean-up after generation of tarball.


> Neither of these steps touch anything git-related, so I don't see how
> you got the connection to the "upstream" branch.

Sometimes "upstream" branch is the only place where "origtargz" can get 
sources for orig tarball. This is exactly the case where it leaves contents 
of tarball (or upstream branch) behind.


> What differences exactly are you seeing after unpacking?

Contents of orig.tar left behind.

-- 
Regards,
 Dmitry Smirnov.

---

Good luck happens when preparedness meets opportunity.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20160409/b963ee2f/attachment-0001.sig>