Hi Bart,
sorry for the latency but I had a problems.
Well, I have uploaded a new version of the package and hope that the
copyright file is complete.
On Wednesday 25 July 2012 19:48:19 you wrote:
Hi Francesco,
I had a look at your package at mentors uploaded there on 2012-07-25 08:17.
The
The problem is that I ran dput yesterday but the package dis not
appear in my packages on mentor (I didn't even receive an email).
I guess it got stuck somewhere in the incoming queue.
I read somewhere that it takes 6 hours to get unstuck, but still no
email from yesterdays' upload and I get
2012/12/3 Nick Andrik nick.and...@gmail.com:
The problem is that I ran dput yesterday but the package dis not
appear in my packages on mentor (I didn't even receive an email).
I guess it got stuck somewhere in the incoming queue.
I read somewhere that it takes 6 hours to get unstuck, but still
Dear all,
After several months of using git-buildpackage with the recommended
pristine-tar option I still keep making myself the following question.
Why does git-buildpackage need pristine-tar to generate the orig.tar.gz
file?. Can't it just pick the contents from the upstream branch
together
On Mon, 3 Dec 2012 13:27:15 +0100
Nick Andrik nick.and...@gmail.com wrote:
The problem is that I ran dput yesterday but the package dis not
appear in my packages on mentor (I didn't even receive an email).
I guess it got stuck somewhere in the incoming queue.
I read somewhere that it takes 6
Hi,
On 03.12.2012 13:44, Miguel Telleria de Esteban wrote:
and it works !!
so why does not git-buildpackage do this?
Try:
md5sum $orig_tarball_from_pristine_Tar
vs
md5sum $orig_tarball_recreated_from_the_upstream_branch
While the /contents/ of the tarball are identical, the tarball
On Mon, 3 Dec 2012 13:44:55 +0100
Miguel Telleria de Esteban mig...@mtelleria.com wrote:
Dear all,
After several months of using git-buildpackage with the recommended
pristine-tar option I still keep making myself the following question.
Why does git-buildpackage need pristine-tar to
Hi all,
Submitted a few updates to Debian Mentors for this package. Filed a new
RFS (#694968) and was correctly informed to continue using the old one.
So here goes...
Addressed the errors reported by the QA process and Bart Martens.
* Package name: podget
Version : 0.6.8-12
On 12/03/2012 10:30 PM, Antonio Ospite wrote:
in debian/gbp.conf there are just these lines:
[DEFAULT]
debian-branch = debian
upstream-branch = master
upstream-tag = v%(version)s
By just running git buildpackage the package builds fine, and
the .orig.tar.gz
On Mon, Dec 03, 2012 at 01:44:55PM +0100, Miguel Telleria de Esteban wrote:
Why does git-buildpackage need pristine-tar to generate the orig.tar.gz
file?.
It doesn't and it's even not enabled by default.
Can't it just pick the contents from the upstream branch
together with version number
On Mon, Dec 03, 2012 at 03:30:09PM +0100, Antonio Ospite wrote:
In my limited experience if the upstream project uses git already and
_tags_ stable releases it is very easy to avoid using pristine-tar
It's also very easy to avoid it in any other workflow: just don't enable
it. There is no
Thanks everybody for your answers.
After some review on my files and seeing your responses I can see that:
* The orig.tar.gz was not created because the debian/changelog version
lacked a - to differentiate upstream_version from debian
versions.
As a result gbp considered my
Il 02/12/2012 15:56, Jakub Wilk ha scritto:
* Giulio Paci giuliop...@gmail.com, 2012-12-01, 20:45:
I decided to push my git repository to collab-maint. You can find it here:
Vcs-Git: git://git.debian.org/git/collab-maint/yamcha.git
Vcs-Browser:
Miguel Telleria de Esteban mig...@mtelleria.com writes:
* In a pure git storage scenario, pristine-tar doesn't add much
benefit since we can always generate an orig.tar.gz from an upstream
tag and obtain the same result...
... or maybe subsequent git-buildpackage invocations may
On Mon, 03 Dec 2012 13:11:56 -0800 Russ Allbery wrote:
Miguel Telleria de Esteban writes:
... or maybe subsequent git-buildpackage invocations may generate
md5sum different .orig.tar.gz?? I guess not (although I will
check).
Every time you generate an *.orig.tar.gz file from
15 matches
Mail list logo
