Bug#930595: RFS: uacme/1.0.15-2 [ITP]

2019-06-17 Thread Nicola Di Lieto
On Tue, Jun 18, 2019 at 10:39:06AM +0800, Paul Wise wrote: You might want to sign these tarballs: https://wiki.debian.org/Creating%20signed%20GitHub%20releases You may also want to sign all git tags and commits: https://mikegerwitz.com/papers/git-horror-story All my git tags and releases ar

Bug#930595: RFS: uacme/1.0.15-2 [ITP]

2019-06-17 Thread Paul Wise
On Mon, 2019-06-17 at 20:10 +0200, Nicola Di Lieto wrote: > I generate the original tarball by tagging master with 'vX.Y.Z', then > './configure' and 'make dist' (note master does NOT include a /debian > directory). You might want to sign these tarballs: https://wiki.debian.org/Creating%20sign

Bug#930664: ITP: libcamera/0~190601-1

2019-06-17 Thread eamanu15 .
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libcamera" * Package name: libcamera Version : 0~190601-1 Upstream Author : Libcamera * URL : http://libcamera.org/ * License : LGPL-2.1+ Section :

Bug#930595: RFS: uacme/1.0.15-2 [ITP]

2019-06-17 Thread Nicola Di Lieto
On Mon, Jun 17, 2019 at 05:59:17PM +0800, Paul Wise wrote: One should always build everything from source as often as possible. Also remove build products from upstream VCSen and tarballs (except autotools cruft). I generate the original tarball by tagging master with 'vX.Y.Z', then './configu

Bug#930633: i3-gaps RFS/ITP

2019-06-17 Thread Dominik George
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi antisocrates, > Ingo will outline what needs to be done to get i3-gaps into a mergable > state, so that we can eventually bring these features to all i3 users. > > For the time being, our recommendation is to NOT add i3-gaps to Debian or > any o

Bug#930633: i3-gaps RFS/ITP

2019-06-17 Thread Michael Stapelberg
Hey, thanks everyone for reaching out. The interest in making i3-gaps available to more people has prompted some discussion between Ingo (the maintainer of the i3-gaps fork, and an i3 core maintainer) and me. The key concern about the i3-gaps fork is code quality: the implementation cannot easil

Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

2019-06-17 Thread Dominik George
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Thanks for your contribution! I looked into your package and have the > following remarks: Oh, plus, also please fix the issues listed on your package's mentors page as well, obiously ☺. - -nik -BEGIN PGP SIGNATURE- iQJlBAEBCgBPFiEEPJ1Up

Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

2019-06-17 Thread Dominik George
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, On Mon, Jun 17, 2019 at 04:10:03AM +0300, antisocrates wrote: > I am looking for a sponsor for my package "i3-gaps" Thanks for your contribution! I looked into your package and have the following remarks: * Did you talk to the i3-wm maintaine

Bug#930595: RFS: uacme/1.0.15-2 [ITP]

2019-06-17 Thread Paul Wise
On Sun, Jun 16, 2019 at 8:27 PM Nicola Di Lieto wrote: > The reason I patched it out is because I thought it's better not to > build-depend on asciidoc (as I do not regenerate the docs unless I make > a new revision). But of course I am happy to remove the patch and > build-depend on asciidoc. On