Bug#895848: RFS: inotify-tools/3.14-5

control: tag -1 +moreinfo control: owner -1 ! On Mon, Apr 16, 2018 at 10:25:01PM +0300, Dmitry Bogatov wrote: > > I am looking for a sponsor for my package "inotify-tools" FTBFS: dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below

Bug#895870: RFS: deepin-music/3.1.8.1+ds-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "deepin-music" * Package name: deepin-music Version : 3.1.8.1+ds-1 Upstream Author : Deepin Technology Co., Ltd. * URL :

Bug#895848: RFS: inotify-tools/3.14-5

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "inotify-tools" * Package name : inotify-tools Version : 3.14-5 Upstream Author : Radu Voicilas * Url :

Bug#895812: Fwd: RFS: json-editor.js/0.7.28+ds-1 [ITP]

Ho Joel, thanks for your contribution ! Looking at your work there are a couple of things that can be improved: 1. I see that you set the Maintainer = Debian Javascript Maintainers. In that team normally we use git repos to keep track of the packaging; more precisely we use the

Bug#895847: RFS: pqiv/2.10.3-0.1 [NMU] -- Powerful image viewer with minimal UI

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my new revision of the pqiv package. I am the upstream author. * Package name: pqiv Version : 2.10.3-0.1 Upstream Author : Phillip Berndt * URL :

Bug#889515: marked as done (RFS: persepolis/3.0.1-1 [ITP])

Your message dated Mon, 16 Apr 2018 16:20:29 + with message-id and subject line closing RFS: persepolis/3.0.1-1 [ITP] has caused the Debian Bug report #889515, regarding RFS: persepolis/3.0.1-1 [ITP] to be marked as done. This means that you claim that

Re: Question concerning BTS, my own patch and upstream bugfix

On Mon, 16 Apr 2018 15:02:43 +0500 Andrey Rahmatullin wrote: >On Mon, Apr 16, 2018 at 11:38:25AM +0200, Oliver Meißner wrote: >> How should I deal with this patch? >> >> * Leave it inside my current package (ver 3.5-2), close the bug via >> (Closes: #893812) in

Bug#895814: RFS: swagger-ui/2.2.10+ds-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "swagger-ui" * Package name: swagger-ui Version : 2.2.10+ds-1 Upstream Author : Tony Tam * URL : http://swagger.io * License :

Bug#895812: RFS: json-editor.js/0.7.28+ds-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "json-editor.js" * Package name: json-editor.js Version : 0.7.28+ds-1 Upstream Author : Jeremy Dorn (http://jeremydorn.com) * URL

Re: Question concerning BTS, my own patch and upstream bugfix

On Mon, Apr 16, 2018 at 11:38:25AM +0200, Oliver Meißner wrote: > How should I deal with this patch? > > * Leave it inside my current package (ver 3.5-2), close the bug via > (Closes: #893812) in d/changelog and remove the patch with the next > upstream release > or > * Remove the patch from

Question concerning BTS, my own patch and upstream bugfix

Hi, just a short Question how to handle following situation properly I'm about to adopt the storebackup package and fixed bug #893812 by including a patch into the package. While waiting for a sponsor I got the information from the upstream author, that he'd fixed that bug in his next release,

Bug#895803: RFS: linuxbrew-wrapper/20180209-1 [RC]

Package: sponsorship-requests Severity: important Notes: I have DM permission to this package. However to fix an RC bug this package needs to go through NEW, moving from the main section to the contrib section. See the RC bug for detail. Dear mentors, I am looking for a sponsor for my