Re: Trouble with git import-orig --pristine-tar

2015-03-02 Thread Andreas Tille
Hi, On Tue, Mar 03, 2015 at 12:17:50AM +0500, Andrey Rahmatullin wrote: On Mon, Mar 02, 2015 at 07:57:26PM +0100, Andreas Tille wrote: I havn't experienced anything similar before. Your master branch contains changes in upstream files (commit 35b6b76c8a48c9e8702763abee5fef92c9dbc718),

Re: Python logo license

2015-03-02 Thread Barry Warsaw
On Feb 28, 2015, at 04:37 PM, Daniel Stender wrote: 1) what would be the proper license for that file in deb/copyright? IANAL but the PSF's policy on use of its trademarks is clearly stated here: https://www.python.org/psf/trademarks/ They are also fairly permissive in granting approval for

RE:Trouble with git import-orig --pristine-tar

2015-03-02 Thread PICCA Frederic-Emmanuel
Hell andreas, I have this kind of problem with git import-orig when I forgot to synchronize the upstream branch with the origin/upstream branch this way the merge is done between master and your local upstream branch which is not the origin upstream branch. cheers Frederic -- To

Re: Trouble with git import-orig --pristine-tar

2015-03-02 Thread Joachim Wiedorn
Hello Andreas, Andreas Tille wrote on 2015-03-02 19:57: git import-orig --pristine-tar ../fastaq_3.2.0.orig.tar.gz I know that you need the upstream version: git-import-orig --upstream-version=1.0 ../paketname-1.0.tar.gz or: git-import-orig --upstream-version=1.0 --filter=debian/*

Re: Trouble with git import-orig --pristine-tar

2015-03-02 Thread Andrey Rahmatullin
On Mon, Mar 02, 2015 at 09:45:25PM +0100, Joachim Wiedorn wrote: git import-orig --pristine-tar ../fastaq_3.2.0.orig.tar.gz I know that you need the upstream version: What is the upstream version? [3.2.0 in the part of quote you deleted is the question asked by git-import-orig if

Re: New release while waiting for sponsoring

2015-03-02 Thread Arturo Borrero Gonzalez
On 2 March 2015 at 19:31, Christoph Mathys erase...@gmail.com wrote: Hi folks, While waiting for my package mercurial-keyring to be sponsored, upstream has released a new version of the software. So what do I do with the old sponsorship request bug? (#779049) Can I just update it? Or close

New release while waiting for sponsoring

2015-03-02 Thread Christoph Mathys
Hi folks, While waiting for my package mercurial-keyring to be sponsored, upstream has released a new version of the software. So what do I do with the old sponsorship request bug? (#779049) Can I just update it? Or close it? Thanks! Christoph -- To UNSUBSCRIBE, email to

Bug#779049: marked as done (RFS: mercurial-keyring/0.6.6-1)

2015-03-02 Thread Debian Bug Tracking System
Your message dated Mon, 02 Mar 2015 19:54:21 +0100 with message-id 54f4b1dd.7050...@gmail.com and subject line Re: Bug#779049: Acknowledgement (RFS: mercurial-keyring/0.6.6-1) has caused the Debian Bug report #779049, regarding RFS: mercurial-keyring/0.6.6-1 to be marked as done. This means that

Trouble with git import-orig --pristine-tar

2015-03-02 Thread Andreas Tille
Hi, is somebody able to reproduce the following: gbp-clone ssh://git.debian.org/git/debian-med/fastaq.git cd fastaq uscan --verbose ... fetches ../fastaq_3.2.0.orig.tar.gz git import-orig --pristine-tar ../fastaq_3.2.0.orig.tar.gz What is the upstream version? [3.2.0]

Bug#779589: RFS: mercurial-keyring/0.6.7-1

2015-03-02 Thread Christoph Mathys
Package: sponsorship-requests Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this

Re: Trouble with git import-orig --pristine-tar

2015-03-02 Thread Andrey Rahmatullin
On Mon, Mar 02, 2015 at 07:57:26PM +0100, Andreas Tille wrote: is somebody able to reproduce the following: gbp-clone ssh://git.debian.org/git/debian-med/fastaq.git cd fastaq uscan --verbose ... fetches ../fastaq_3.2.0.orig.tar.gz git import-orig --pristine-tar