Bug#858538: RFS: fadecut/0.2.0-1

control: tag -1 +moreinfo Dear Marco, On Thu, Mar 23, 2017 at 09:47:44AM +0100, Marco Balmer wrote: > Changes since the last upload: > > fadecut (0.2.0-1) unstable; urgency=low > > [...] These changes are not appropriate during the current freeze. If you want to upload this as-is, you will

Bug#858800: RFS: xtrs/4.9d-1 [ITA]

control: tag -1 +moreinfo Dear Branden, On Sun, Mar 26, 2017 at 06:45:34PM -0400, Branden Robinson wrote: > Changes since the last upload: > > * Merge new upstream release. > + "Deleted all SIGIO code. The code was a kludge to begin with and it no > longer worked with current X

Sigrok packages review/mentoring

Dear Andreas , I'm trying to summarize here the infos and thecurrent state of the adoption of the sigrok suite related packages in order to start the reviewing/mentoring process. 1. The corresponding ITA bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852830

Bug#832941: RFS: 4pane

Dear David, I can't review your latest work because the PGP signature for the tarball fails to verify: iris ~/rfs/4pane % origtargz -u W: Unable to locate package 4pane Trying uscan --download-current-version ... uscan: Newest version of 4pane on remote site is 4.0, specified

Re: Sigrok RFSs

Dear Andreas, Aaron, On 03/16/2017 08:54 PM, Aaron Brady wrote: >> OK, thx. >> @Aaron, as you were/are also working on this, do you have any objection >> if i set these RFA bugs to ITA for myself and start the >> sponsoring/reviewing process of the uploaded packages [1] with Andreas >> and

Bug#858860: RFS: arpwatch/2.1a15-3 [ITA]

Package: sponsorship-requests Severity: normal Dear mentors, thanks for the help you have provided so far. I am now officially looking for a sponsor for the arpwatch package, which I intend to adopt. I've uploaded my current packaging work to mentors:

Nova mensagem

Olá, Seu (debian-mentors@lists.debian.org) Tem duas novas mensagens criptografadas no Dropbox. Visualizar arquivo Apreciar! A equipe do Dropbox © 2017 Dropbox

Re: Problems with autoconf in pftools

On Mon, Mar 27, 2017 at 07:43:15PM +0200, Lukas Schwaighofer wrote: > > configure.ac uses the AX_PTHREAD macro, you need to build depend on > autoconf-archive (which contains /usr/share/aclocal/ax_pthread.m4). Thanks. This helped over the autoconf hurdle. However, it sounds pretty strange why

Bug#858795: RFS: python-zxcvbn/4.4.14-1 [ITA]

On 27/03/2017 08:51, Gianfranco Costamagna wrote: control: owner -1 ! control: tags -1 moreinfo I am looking for a sponsor for my package "python-zxcvbn": here we are: +python-zxcvbn (4.4.14-1) unstable; urgency=low + + * New maintainer (Closes: #855638) + ^^ remove this newline line

Re: ethercodes.dat / oui.txt (Was: Re: arpwatch & systemd)

Hi Christian, thanks for suggesting the file based triggers, hadn't thought of that. Combining that with the hook into update-ieee-data should indeed works fine and is much better than doing stuff on service startup. On Mon, 27 Mar 2017 11:06:47 +0200 Christian Seiler wrote:

Re: Problems with autoconf in pftools

Hi, On Mon, 27 Mar 2017 14:04:01 +0200 Andreas Tille wrote: > I try to package pftools[1]. Unfortunately autoreconf throws the > following error: > >dh_autoreconf -O--no-parallel > configure.ac:6: error: possibly undefined macro: AC_MSG_NOTICE > If this token and

Problems with autoconf in pftools

Hi, I try to package pftools[1]. Unfortunately autoreconf throws the following error: dh_autoreconf -O--no-parallel configure.ac:6: error: possibly undefined macro: AC_MSG_NOTICE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.

Re: ethercodes.dat / oui.txt (Was: Re: arpwatch & systemd)

On 03/27/2017 12:24 AM, Lukas Schwaighofer wrote: > 22:30:39 +0200 Christian Seiler wrote: > >> On 03/26/2017 09:19 PM, Lukas Schwaighofer wrote: >>> I'm not sure I understand what you mean… should the ethercodes.dat >>> file be removed / used from a different package? >>

Bug#858795: RFS: python-zxcvbn/4.4.14-1 [ITA]

control: owner -1 ! control: tags -1 moreinfo >I am looking for a sponsor for my package "python-zxcvbn": here we are: +python-zxcvbn (4.4.14-1) unstable; urgency=low + + * New maintainer (Closes: #855638) + ^^ remove this newline + * Fixed change upstream source to the active fork