RFS: fgetty/0.7-0.1 [NMU] -- very small, efficient, console-only getty

Package: sponsorship-request Severity: normal Dear mentors, I am looking for a sponsor for my package "fgetty" * Package name: fgetty Version : 0.7-0.1 Upstream Author : Felix von Leitner * Url : https://www.fefe.de/fgetty * Licenses:

Re: [RFS] eoconv -- convert text files between various Esperanto encodings

On Tue, Mar 01, 2016 at 09:38:19AM +0300, Dmitry Bogatov wrote: > Package: sponsorship-request keep in mind that it's "reqeuests" (with a trailing 's'). your bug was also wrongly filed (but got reassigned) > I am looking for a sponsor for my package "eoconv". I already filed RFS > several weeks

Bug#813952: RFS: helm/1.9.2-1 -- Emacs incremental completion and selection narrowing framework

control: block -1 by 813953 On Mon, Feb 29, 2016 at 06:00:05PM -0700, Sean Whitton wrote: > The Emacs Addons packaging team recently started using PET [1], which > works best if packages are tagged only after they are uploaded, so I > removed the tag. ok, cool. > I didn't expect anyone outside

Bug#816356: RFS: progress/0.13-2

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "progress" * Package name: progress Version : 0.13-2 Upstream Author : xfennec * URL : https://github.com/Xfennec/progress * License : gpl-3

[RFS] eoconv -- convert text files between various Esperanto encodings

Package: sponsorship-request Severity: wishlist Dear mentors, I am looking for a sponsor for my package "eoconv". I already filed RFS several weeks ago, this is just bump (not sure, if it is good practice) * Package name: eoconv Version : 1.4-1 Upstream Author : Tristan Miller

Re: how to take advantage of uscan for git upstream source with only commits (read no tags) ?

On Tue, Mar 1, 2016 at 1:05 AM, Jerome BENOIT wrote: > I am on my way to package a software whose the upstream source is available > at github with only commits: > the upstream team uploads new material the last Friday of each month, but > without emitting any tags. > Can we use uscan (version

Bug#814456: marked as done (RFS: pam-ufpidentity/1.0-2 [ITP] -- UFP Identity PAM Module)

Your message dated Tue, 01 Mar 2016 04:23:46 + with message-id and subject line closing RFS: pam-ufpidentity/1.0-2 [ITP] -- UFP Identity PAM Module has caused the Debian Bug report #814456, regarding RFS: pam-ufpidentity/1.0-2 [ITP] -- UFP Identity PAM

Bug#816351: RFS: perspective-el/1.12+git20160216.add7942-1 -- tagged workspaces in Emacs

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an update to perspective-el. * Package name: perspective-el Version : 1.12+git20160216.add7942-1 Upstream Author : Natalie Weizenbaum * URL :

Bug#813952: RFS: helm/1.9.2-1 -- Emacs incremental completion and selection narrowing framework

Hello, Thank you for your review. On Mon, Feb 29, 2016 at 11:25:22PM +, Mattia Rizzolo wrote: > On Sat, Feb 06, 2016 at 06:11:40PM -0700, Sean Whitton wrote: > > git clone https://anonscm.debian.org/git/pkg-emacsen/pkg/helm > > git checkout debian/1.9.2-1 > > there is no such tag

Bug#813850: RFS: amanda/3.3.8-1 -- Advanced Maryland Automatic Network Disk Archiver

On 29/02/16 23:09, Mattia Rizzolo wrote: > sorry, this took awfully long. > > On Fri, Feb 05, 2016 at 11:09:20PM +, Jose M Calhariz wrote: >> Amanda have release a new upstream version. My main sponsor is too >> busy for helping me. So I am searching for someone that can help >> sponsor the

Bug#813952: RFS: helm/1.9.2-1 -- Emacs incremental completion and selection narrowing framework

control: tag -1 moreinfo control: owner -1 ! On Sat, Feb 06, 2016 at 06:11:40PM -0700, Sean Whitton wrote: > git clone https://anonscm.debian.org/git/pkg-emacsen/pkg/helm > git checkout debian/1.9.2-1 there is no such tag (luckily?) anyway, looking at HEAD: * please use

Bug#813850: RFS: amanda/3.3.8-1 -- Advanced Maryland Automatic Network Disk Archiver

sorry, this took awfully long. On Fri, Feb 05, 2016 at 11:09:20PM +, Jose M Calhariz wrote: > Amanda have release a new upstream version. My main sponsor is too > busy for helping me. So I am searching for someone that can help > sponsor the new release. Ok, I can do it. Should I use the

Bug#809308: marked as done (RFS: cl-asdf/2:3.1.6-1 [ITA] - Another System Definition Facility)

Your message dated Mon, 29 Feb 2016 22:44:21 + with message-id <20160229224421.gc24...@chase.mapreri.org> and subject line Re: Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility has caused the Debian Bug report #809308, regarding RFS: cl-asdf/2:3.1.6-1 [ITA] - Another

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

On 2016-02-29 22:31 CET, Mattia Rizzolo wrote: > On Mon, Feb 29, 2016 at 10:26:36PM +0100, Kambiz Darabi wrote: >> I uploaded a new version. > > W: cl-asdf source: timewarp-standards-version (2015-10-17 < 2016-02-01) > > Please bump also the date in the changelog (`dch -r`

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

On Mon, Feb 29, 2016 at 10:26:36PM +0100, Kambiz Darabi wrote: > I uploaded a new version. W: cl-asdf source: timewarp-standards-version (2015-10-17 < 2016-02-01) Please bump also the date in the changelog (`dch -r` does that). :) And btw, I'd argue that means you didn't run lintian before

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

> * in the meantime a new version of policy is out, 3.9.7. Check whether > your package is still compliant [0] and if so bump Standards-Version > ... > [0] https://www.debian.org/doc/debian-policy/upgrading-checklist Checked, and bumped. > * in d/changelog, there should be a blank line

Bug#813900: RFS: ripit/4.0.0~beta20140508-1

* Sven Hoexter [2016-02-29 20:30 +0100]: > On Sat, Feb 20, 2016 at 04:32:06PM +0100, Elimar Riesebieter wrote: > > Hi, > > > I wonder why no sponsor takes care of my package since 3 weeks > > now... > > We also have day jobs and I do not look at sponsoring that often

Bug#809623: RFS: telegram-purple/1.2.5

Hi, >It *is* backward-compatible, but now a freshly-introduced >turns-out-to-be-big feature is missing. let me know if you can do your upstream features in time, and I'll try to quickly make the package uploaded on unstable then :) cheers, G.

Bug#809623: RFS: telegram-purple/1.2.5

Hey there, Well, that didn't work. Also, see below. As it turns out, pushing 1.2.5 into Debian right now would be a bad idea. again, if the problem is on Windows, I don't really care. We're not entirely sure about that; and 1.3.0 isn't ready yet. Due to Telegram cranking out unexpected

Bug#812728: RFS: identity4c/1.0-1 [ITP] -- UFP Identity C library

All of your comments have been addressed except for the empty NEWS which is part of upstream. All of the previous uploads have been removed and the only one that should be evaluated is: http://mentors.debian.net/debian/pool/main/i/identity4c/identity4c_1.0-1.dsc Thank you. r

Bug#809623: RFS: telegram-purple/1.2.5

Hi, > sorry for the long wait, real life happened. Also, note the version bump > in the subject from 1.2.3 to 1.2.5. no problem :) > We now bundle the origtar, and listen for it in d/watch wonderful! > I would like to see this work helping all Debian-derivatives. > A month ago, before I went

Re: how to take advantage of uscan for git upstream source with only commits (read no tags) ?

Jerome BENOIT writes: > I am on my way to package a software whose the upstream source is > available at github with only commits: the upstream team uploads new > material the last Friday of each month, but without emitting any tags. I'm not an expert on the

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

On Mon, Feb 29, 2016 at 04:39:26PM +0100, Kambiz Darabi wrote: > Thank you for the heads up, Mattia. Since January, I am working on > several projects and unfortunately forgot to finish the packaging. no worries, let's finish this :) > > * make is called should be called by dh_auto_build in this

how to take advantage of uscan for git upstream source with only commits (read no tags) ?

Dear Mentaors: I am on my way to package a software whose the upstream source is available at github with only commits: the upstream team uploads new material the last Friday of each month, but without emitting any tags. Can we use uscan (version 4) for such a scheme ? Thanks in advance,

Bug#807432: RFS: python-jellyfish/0.5.1-1 [ITP]

About gbp.conf, we at #debian-mentors have realized that if you want to comply with DPMT's Policy, then you will need to set up the `upstream` branch by importing only the tar.gzs, without upstream's commit history on it. That makes gbp.conf superfluous and also there's no need to think about

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

Thank you for the heads up, Mattia. Since January, I am working on several projects and unfortunately forgot to finish the packaging. I have uploaded a new version which addresses these: > On Thu, Dec 31, 2015 at 12:22:43PM +0100, Kambiz Darabi wrote: >> > - $ codespell --quiet-level=3 >> >

Bug#814852: RFS: openfst/1.5.1-1 -- weighted finite-state transducers library

* Giulio Paci , 2016-02-29, 13:24: 1) I need to package latest version, as the differences are not trivial anymore; 2) I have to convince upstream stop these bad practices (however it seems very hard, as they stop for one release and then start again a immediately after);

Bug#807432: RFS: python-jellyfish/0.5.1-1 [ITP]

I can't sponsor you (I'm just a contributor) but since I packaged python-jellyfish on my own as I didn't see your ITP first, let me chime in to be of some help. # d/watch It is correct, but from the contents of the orig.tar.gz I see you have used the one from Github (that contains the docs/ etc)

Bug#809308: RFS: cl-asdf/3.1.6 [ITA] - Another System Definition Facility

Gentle ping. Are you still interested in adopting this package and getting it uploaded? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad

Bug#816192: RFS: python-proselint/0.3.5-1 [ITP] -- A prose linter

On Mon, 29 Feb 2016 01:08:02 +0100 Jakub Wilk wrote: > Typo in the manpages: > initiliaze -> initialize Fixed. > The license text in the copyright file is not correctly formated; see > bug #700970. Fixed. Many thanks for the review! :) I have uploaded the fixes to mentors

Bug#810836: marked as done (RFS: nvme-cli - User space tooling to control NVMe drives.)

Your message dated Mon, 29 Feb 2016 10:15:34 -0300 with message-id <56d44476.6080...@br.ibm.com> and subject line has caused the Debian Bug report #810836, regarding RFS: nvme-cli - User space tooling to control NVMe drives. to be marked as done. This means that you claim that the problem has

Bug#814852: RFS: openfst/1.5.1-1 -- weighted finite-state transducers library

Hi Jakub, On 29/02/2016 00:27, Jakub Wilk wrote: > * Giulio Paci , 2016-02-28, 23:19: >> I packaged >> "http://openfst.org/twiki/bin/viewfile/FST/FstDownload?filename=openfst-1.5.1.tar.gz;rev=1; >> and noticed the behaviour when upstream was at >>

Bug#816266: RFS: python-qtawesome/0.3.0-1 [ITP]

> The Spyder Development Team is not upstream of this font actually. So I > don't think creating a font package from this source package is the > right solution, is it? No you are right I looked at the elusive content /tmp$ unzip elusive-icons-2.0.0.zip Archive: elusive-icons-2.0.0.zip

Bug#816266: RFS: python-qtawesome/0.3.0-1 [ITP]

The Spyder Development Team is not upstream of this font actually. So I don't think creating a font package from this source package is the right solution, is it? What I thought of doing was to keep the embedded copy of the font for now and file a RFP for elusive-iconfont. I don't think I'll

Bug#816266: RFS: python-qtawesome/0.3.0-1 [ITP]

Hello Ghislain >* The -common package contains 2 fonts, one of which is not available > for Debian (elusive-iconfont, SIL OFL 1.1). The other one (fontawesome) > is symlinked from its corresponding package. in that case can you create a real fonts package in order to be consistant with all

Bug#816266: RFS: python-qtawesome/0.3.0-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-qtawesome" * Package name: python-qtawesome Version : 0.3.0-1 Upstream Author : The Spyder Development Team * URL :

Bug#816262: RFS: python-hdf5storage/0.1.13-1

Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "python-hdf5storage" * Package name: python-hdf5storage Version : 0.1.13-1 Upstream Author : Freja Nordsiek

Bug#816261: RFS: django-prometheus/1.0.6-1

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for "django-prometheus" * Package name: django-prometheus Version : 1.0.6-1 Upstream Author : Uriel Corfa * URL :