fix for previous patch:
diff --git a/gbp/deb/git.py b/gbp/deb/git.py
index fa45807a..aa4562b4 100644
--- a/gbp/deb/git.py
+++ b/gbp/deb/git.py
@@ -324,7 +324,7 @@ class DebianGitRepository(PkgGitRepository):
self.pristine_tar.checkout(source.name,
source.upstream_version, comp.type, o
What's wrong with a failed git checkout?
---
gbp/deb/git.py | 15 ---
gbp/scripts/buildpackage.py | 2 ++
gbp/scripts/export_orig.py | 6 +-
3 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/gbp/deb/git.py b/gbp/deb/git.py
index 3584f6ff..fa45807a 10
Hi,
On Thu, Nov 21, 2019 at 05:19:04PM +0100, Christian Göttsche wrote:
> Control: severity -1 important
> Control: tags -1 patch
>
> Hi,
>
> what about the following patch:
The existence of the signature in the pristine-tar branch needs to be
checked beforehand instead of trying, failing and th
Control: severity -1 important
Control: tags -1 patch
Hi,
what about the following patch:
--- /usr/lib/python3/dist-packages/gbp/deb/git.py 2019-10-31
16:07:04.0 +0100
+++ /root/git.py2019-11-21 17:07:41.485223303 +0100
@@ -320,7 +320,15 @@
output = source.upstream
Hi all,
Anything one could do to get this implemented?
Thanks for your work,
cheers,
Georg
signature.asc
Description: Digital signature
Hi,
I have a few question a bit related to the test failure in the github
PR#35 [1].
As of now, `/usr/bin/pristine-tar` will fail if we tell it to commit /
checkout a non existing signature.
So when calling `pristine-tar`, we need to check if the signature exists
or not.
For the commit operation
Hi,
I got signature file integration working with the orig tarball with the
attached patch.
This implementation is somewhat simple and does not check if
pristine-tar has the signature feature (and thus require pristine-tar 1.41)
I think the check for the presence of a signature file in the
prist
Hi,
On Fri, Oct 20, 2017 at 02:35:28PM +0100, Chris Lamb wrote:
> Hi Guido,
>
> > No problem; I personally hadn't seen the blocking pristine-tar issue
> > had been uploaded until now so I thought it might have passed you by
> > too. :)
>
> Gentle ping on this? Seems like the only piece of the puz
Hi Guido,
> No problem; I personally hadn't seen the blocking pristine-tar issue
> had been uploaded until now so I thought it might have passed you by
> too. :)
Gentle ping on this? Seems like the only piece of the puzzle missing!
Regards,
--
,''`.
: :' : Chris Lamb
`. `
Hi Guido,
> Yept, and I was working on a patch even before that ;) But now that
> Debconf is over things are progressing much more slowly due to RL.
No problem; I personally hadn't seen the blocking pristine-tar issue
had been uploaded until now so I thought it might have passed you by
too. :)
Hi,
On Sat, Sep 02, 2017 at 07:43:31AM +0100, Chris Lamb wrote:
> Chris Lamb wrote:
>
> > > We should checkout the upstream signatures from the pristine-tar branch
> > > as well.
> >
> > This blocks on support in pristine-tar (now pending release).
>
> … which is now in unstable as pristine-tar 1
Chris Lamb wrote:
> > We should checkout the upstream signatures from the pristine-tar branch
> > as well.
>
> This blocks on support in pristine-tar (now pending release).
… which is now in unstable as pristine-tar 1.41 :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'`
block 872864 by 871809
thanks
> We should checkout the upstream signatures from the pristine-tar branch
> as well.
This blocks on support in pristine-tar (now pending release).
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Package: git-buildpackage
Version: 0.9.0~exp4~2.gbpa7b96a
Severity: wishlist
We should checkout the upstream signatures from the pristine-tar branch
as well.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'te
14 matches
Mail list logo
