Package: git-buildpackage Version: 0.8.12.2 Severity: wishlist So I had a chance to try out the multiple upstream tarball support and I have to admit I am very happy to finally have some support to the everyday's tool that gbp is :) Thank you for it!
I have a wishlist though. Here I added a new "contrib" module injected with a separate upstream tarball: https://anonscm.debian.org/git/debian-science/packages/opencv.git/commit/?id=2e8087f9d5730b8decf024d51ba8d15df0a2860a Incidentally, while bumping the upstream version (+dfsg → +dfsg1) I also repacked the main tarball by removing another file, and apparently several other things changed too. I think I'd find a lot more clear if the import was done with separate commit, i.e.: 1. import main tarball 2. commit "New upstream version 3.1.0+dfsg1" 3. import secondary tarball 4. commit "Import upstream tarball 'contrib' version 3.1.0+dfsg1" 5. iterate from point 3 if more multiple tarballs Or something like that. The upstream/* tag should be on the last import, and then merged into the debian branch. Thoughts? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature