Package: devscripts
Version: 2.16.2
Severity: normal
When "pristine-tar" and "upstream" branches are present, "origtargz" leaves
upstream files in "master" after tarball generation.
This is a quite annoying behaviour for repositories where "master" tracks
only Debian packaging without upstream
Control: tags -1 moreinfo
Re: Dmitry Smirnov 2016-04-09 <4233478.bJBLRpzaE8@deblab>
> When "pristine-tar" and "upstream" branches are present, "origtargz" leaves
> upstream files in "master" after tarball generation.
>
> This is a quite annoying behaviour for repositories where "master" tracks
On Saturday, 9 April 2016 11:19:02 AM AEST Christoph Berg wrote:
> did you meant to report this for mk-origtargz instead?
>
> Though both origtargz and mk-origtargz don't do anything directly with
> git and branches, so I'm wondering where you got that connection from?
From "origtargz" functional
Re: Dmitry Smirnov 2016-04-09 <2265949.YxrWVc7PcZ@deblab>
> > Though both origtargz and mk-origtargz don't do anything directly with
> > git and branches, so I'm wondering where you got that connection from?
>
> From "origtargz" functionality of course. One can checkout package repository
> with
Re: Dmitry Smirnov 2016-04-09 <2265949.YxrWVc7PcZ@deblab>
> From "origtargz" functionality of course. One can checkout package repository
> with upstream and pristine-tar branches and generate orig tarball using
> "origtargz" even if package is not uploaded yet in which case tarball is
> generat
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
Re: Dmitry Smirnov 2016-04-09 <1740755.tD23JeLo3f@deblab>
> 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.
Sorry, this is just plain wrong. origtargz d
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
Re: Dmitry Smirnov 2016-04-09 <1639699.INnWnnHQ89@deblab>
> 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 sayin
On Saturday, 9 April 2016 1:06:03 PM AEST Christoph Berg wrote:
> Right, but this is exactly what's documented, and what origtargz is
> supposed to be doing - give you a full working tree to work on.
Fair enough. :)
I just want to note that phrase "optionally unpacks it into the current
director
Processing control commands:
> tags -1 moreinfo
Bug #820494 [devscripts] origtargz: leaves "upstream" files in "master" after
invocation
Added tag(s) moreinfo.
--
820494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
11 matches
Mail list logo
