El 26/12/22 a las 17:30, Raphael Hertzog escribió:
Hello,
On Fri, 23 Dec 2022, Santiago Vila wrote:
For example, this one:
I have just imported version 2.10-2. Now dpkg-buildpackage
does not work because it expects some timestamps to be the ones in the
orig.tar.gz where upstream maintainer already ran autoconf and friends.
I know that autoreconf may help here, but I would prefer not to be forced
to use it. What are my options?
Is there some git-buildpackage specific solution for this?
Yes, I think so. Use --git-export-dir=../build-area/ (many persons
have it in their ~/.gbp.conf).
$ cat ~/.gbp.conf
[DEFAULT]
pristine-tar = True
cleaner = /bin/true
[buildpackage]
sign-tags = True
export-dir = ../build-area/
ignore-branch = True
ignore-new = True
[import-orig]
filter-pristine-tar = True
[pq]
patch-numbers = False
[dch]
multimaint-merge = True
ignore-branch = True
Ok. For "hello" I will follow the trend and add whatever build-dependencies are
required for
it to work in all cases, but I'm still interested in these kind of tricks just
in case I need
them for other packages.
So, suppose that someone has a package requiring the above for "gbp
buildpackage" to work.
Does the package have a disclaimer somewhere saying "plain dpkg-buildpackage is
not supported
here" or something alike?
Thanks a lot.
