Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-15 Thread Mo Zhou
control: close -1 On Sat, Sep 15, 2018 at 03:53:02PM +0200, François Mazen wrote: > Hi Lumin, > > the file msys/mingw-bundledlls.py was committed by mistake. It is only > needed to generate the Windows package. > I've removed it in the upstream code and I generated a new release > (1.4.3). I've

Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-15 Thread Paul Wise
On Sat, Sep 15, 2018 at 9:53 PM, François Mazen wrote: > the file msys/mingw-bundledlls.py was committed by mistake. It is only > needed to generate the Windows package. > I've removed it in the upstream code and I generated a new release > (1.4.3). I've also updated the copyright file for the

Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-15 Thread François Mazen
Hi Lumin, the file msys/mingw-bundledlls.py was committed by mistake. It is only needed to generate the Windows package. I've removed it in the upstream code and I generated a new release (1.4.3). I've also updated the copyright file for the new 1.4.3-1 package. The new package is tagged

Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-13 Thread Mo Zhou
On Thu, Sep 13, 2018 at 10:57:42PM +0200, François Mazen wrote: > Hi Lumin, > > congratulation for your promotion as Debian Developer! > > I downgraded the standard version of my package from 4.2.1 to 4.1.4 and > I uploaded it to mentors but Lintian has been updated in the meantime. > So I've

Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-13 Thread François Mazen
Hi Lumin, congratulation for your promotion as Debian Developer! I downgraded the standard version of my package from 4.2.1 to 4.1.4 and I uploaded it to mentors but Lintian has been updated in the meantime. So I've kept the 4.2.1 version and you can upload:

Bug#893377: Re: Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-09-13 Thread Mo Zhou
control: owner -1 ! Hi François, I can sponsor this package for you now. Would you mind updating the package and bump the standard version? Or should I upload it as is?

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-07-05 Thread François Mazen
Hi, I've uploaded a new release for my package taptempo (1.4.1-1), and I'm looking for a sponsor: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "taptempo" * Package name: taptempo Version : 1.4.1-1 Upstream

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-04-09 Thread Lumin
Hi François, I'm trying to apply for DD so I'm helping newcomers to review their packages. As agreed by Gianfranco, once we've finished polising the packaging, he will check and sponsor the package. Now your package is in good shape, and there is nothing left to be dealt with except for waiting

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-04-03 Thread François Mazen
Hi Lumin, upload to mentors done, please check: https://mentors.debian.net/package/taptempo Regards, François Le mardi 03 avril 2018 à 06:17 +, Lumin a écrit : > Hi François, > > On 31 March 2018 at 21:59, François Mazen wrote: > > > > This program is useful to

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-04-03 Thread Lumin
Hi François, On 31 March 2018 at 21:59, François Mazen wrote: > > This program is useful to quickly find the tempo of a song. > The idea is to type "taptempo" in a terminal, then hit enter key at > each beat while hearing a song, and display the tempo. > > The targeted people

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-31 Thread François Mazen
Hi, I've chosen to create a separate repo for packaging: https://git.tuxfamily.org/taptempo/taptempo_deb_packaging.git and I will soon remove the debian folder in the upstream repository. > 0. This program seems to be a terminal bpm meter. I'm not quite good > at music stuff, so I'd like to

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-27 Thread Lumin
Hi François, On 26 March 2018 at 19:56, François Mazen wrote: > I've manually changed the timestamp of the changelog file from the > original repo, and I haven't check that the date was wrong. I can > update the changelog file. I've seen new commits in the repo. Let's assume

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-26 Thread François Mazen
Hi Lumin, thanks a lot for your help. I'll try to fix everything. > 1. Why is the package on mentors newer than that on github repo? > Could you please keep the packaging repo up-to-date? I've manually changed the timestamp of the changelog file from the original repo, and I haven't check

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-25 Thread Lumin
Control: owner -1 ! Control: tag -1 +moreinfo Hi François, Several questions about your package: 1. Why is the package on mentors newer than that on github repo? Could you please keep the packaging repo up-to-date? https://github.com/moleculext/taptempo 2. Where is your public key? no

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-18 Thread François Mazen
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "taptempo" * Package name: taptempo Version : 1.2.1-1 Upstream Author : Francois Mazen * URL : https://github.com/moleculext/taptempo