New release while waiting for sponsoring
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 debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54f4ac64.2050...@gmail.com
Re: New release while waiting for sponsoring
On 2 March 2015 at 19:31, Christoph Mathys 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 it? > I would suggest to start working in packaging the new upstream release. If at the time you finish the new upstream package: * no sponsor happened, you could close #779049 (giving some reasons) and open a new one. * sponsor happened, well, just open a new RFS for the new package. -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caoksjbildjcv-q18gafwg44z0x2k6xacsytbclnmtnqkhjf...@mail.gmail.com
Bug#779049: marked as done (RFS: mercurial-keyring/0.6.6-1)
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 you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 779049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mercurial-keyring" * Package name: mercurial-keyring Version : 0.6.6-1 Upstream Author : Marcin Kasperski * URL : http://pypi.python.org/pypi/mercurial_keyring * License : BSD-3-clause Section : python It builds those binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_0.6.6-1.dsc More information about mercurial-keyring can be obtained from http://pypi.python.org/pypi/mercurial_keyring Changes since the last upload: * New upstream release. * Update packaging to use dh-python and pybuild. * Policy bumped to 3.9.6 without changes. * Update watch file to accomodate changes on pypi. Regards, Christoph Mathys --- End Message --- --- Begin Message --- Since upstream released a new version and I'm going to upload it to mentors soon this RFS no longer applies.--- End Message ---
Trouble with git import-orig --pristine-tar
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] gbp:info: Importing '/home/andreas/debian-maintain/alioth/debian-med_git/fastaq_3.2.0.orig.tar.gz' to branch 'upstream'... gbp:info: Source package is fastaq gbp:info: Upstream version is 3.2.0 pristine-tar: committed fastaq_3.2.0.orig.tar.gz.delta to branch pristine-tar gbp:info: Merging to 'master' gbp:error: Merge failed, please resolve. After this the repository is messed up with a lot of changed, deleted and new files, most of the files in debian/* vanished. I havn't experienced anything similar before. Any clue? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150302185726.gc9...@an3as.eu
Bug#779589: RFS: mercurial-keyring/0.6.7-1
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 action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Dear mentors, I am looking for a sponsor for my package "mercurial-keyring" * Package name: mercurial-keyring Version : 0.6.7-1 Upstream Author : Marcin Kasperski * URL : http://pypi.python.org/pypi/mercurial_keyring * License : BSD-3-clause Section : python It builds those binary packages: mercurial-keyring - Mercurial Keyring Extension To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mercurial-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mercurial-keyring/mercurial-keyring_0.6.7-1.dsc More information about mercurial-keyring can be obtained from http://pypi.python.org/pypi/mercurial_keyring Changes since the last upload: * New upstream release. * Update packaging to use dh-python and pybuild. * Policy bumped to 3.9.6 without changes. * Update watch file to accomodate changes on pypi. Regards, Christoph Mathys -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-46-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150302191322.13252.87931.reportbug@obsidian
Re: Trouble with git import-orig --pristine-tar
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 ../fastaq_3.2.0.orig.tar.gz > What is the upstream version? [3.2.0] > gbp:info: Importing > '/home/andreas/debian-maintain/alioth/debian-med_git/fastaq_3.2.0.orig.tar.gz' > to branch 'upstream'... > gbp:info: Source package is fastaq > gbp:info: Upstream version is 3.2.0 > pristine-tar: committed fastaq_3.2.0.orig.tar.gz.delta to branch pristine-tar > gbp:info: Merging to 'master' > gbp:error: Merge failed, please resolve. > > > After this the repository is messed up with a lot of changed, deleted > and new files, most of the files in debian/* vanished. > > I havn't experienced anything similar before. Your master branch contains changes in upstream files (commit 35b6b76c8a48c9e8702763abee5fef92c9dbc718), those changes conflict with the changes in the new upstream version. $ git diff --stat a12e4b2e47b945db9e3dbfefc078de8837d32129 master debian/changelog | 6 debian/control| 5 --- debian/copyright | 2 +- debian/patches/delay-import-statements-for-manpage-creation.patch | 307 +++ debian/usage_to_man | 47 +++-- fastaq/tasks.py | 31 - fastaq/tests/data/sequences_test_fastaq_to_quasr_primers.expected | 2 -- fastaq/tests/data/sequences_test_fastaq_to_quasr_primers.fa | 4 --- fastaq/tests/data/tasks_test_sequence_trim_1.fa | 24 + fastaq/tests/data/tasks_test_sequence_trim_1.trimmed.fa | 14 +--- fastaq/tests/data/tasks_test_sequence_trim_2.fa | 24 + fastaq/tests/data/tasks_test_sequence_trim_2.trimmed.fa | 14 +--- fastaq/tests/data/tasks_test_sequences_to_trim.fa | 8 ++--- fastaq/tests/tasks_test.py| 11 +- scripts/fastaq_sequence_trim | 4 ++- scripts/fastaq_to_quasr_primers_file | 12 --- setup.py | 2 +- 17 files changed, 300 insertions(+), 217 deletions(-) -- WBR, wRAR signature.asc Description: Digital signature
Re: Trouble with git import-orig --pristine-tar
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 ../-1.0.tar.gz or: git-import-orig --upstream-version=1.0 --filter="debian/*" ../-1.0.tar.gz --- Have a nice day. Joachim (Germany) signature.asc Description: PGP signature
Re: Trouble with git import-orig --pristine-tar
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), those changes conflict with the > changes in the new upstream version. > > $ git diff --stat a12e4b2e47b945db9e3dbfefc078de8837d32129 master > debian/changelog | 6 > debian/control| 5 --- > ... > setup.py | 2 +- > 17 files changed, 300 insertions(+), 217 deletions(-) That's really weird. Thanks for opening my eyes Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150302211827.gb13...@an3as.eu
RE:Trouble with git import-orig --pristine-tar
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 UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53b1ff1...@sun-dag3.synchrotron-soleil.fr
Re: Python logo license
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 its legitimate use, if you ask. If it makes a difference in this case, please do ask the PSF. Cheers, -Barry pgpb_Pt8Hidti.pgp Description: OpenPGP digital signature
Re: Trouble with git import-orig --pristine-tar
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 --upstream-version was not passed. -- WBR, wRAR -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150303070257.ga9...@belkar.wrar.name
