On Fri, 31 May 2019 16:25:17 +0500 Pirate Praveen <prav...@onenetbeyond.org> wrote: > > > On Fri, May 31, 2019 at 3:12 PM, Mattia Rizzolo <mat...@debian.org> > wrote: > > user devscri...@packages.debian.org > > usertags 929786 origtargz > > tags 929786 moreinfo > > quit > > > > On Thu, May 30, 2019 at 08:26:27PM +0500, Pirate Praveen wrote: > >> pravi@nishumbha:~/forge/debian/git/js-team/node-vinyl-fs$ origtargz > >> pristine-tar: successfully generated > >> ../node-vinyl-fs_3.0.3.orig.tar.gz > >> > >> But it failed to download multiple tarballs from archive. You can > >> use > >> https://salsa.debian.org/js-team/node-vinyl-fs to reproduce this > >> issue. > > > > Honestly, I don't think there is any sane way for `origtargz` to > > fiugre > > that it needs to download/produce/build more than one orig tarball, > > from > > inside the unpacked source. > > > > That's an information that is available *only* from the .dsc, which is > > not something `origtargz` has access to. Anything else would truly be > > guesswork. > > > > > > Suggestions? > > > If #577113 gets implemented, that will give a uniform way to get list > of components. But even now this information is available in > debian/gbp.conf for packages that use git-buildpackage. I think > origtargz should look in gbp.conf for components if the file is present. > > When pristine-tar branch is missing it does apt source, I think the > same could be tried here also.
pristine-tar list will show all the tarballs when it is a git clone and has pristine-tar branch.
signature.asc
Description: OpenPGP digital signature
