Bug#849754: RFS: guerillabackup/0.0.0-1

Hello Andreas, I did not hear from you after the last mails, see messages from 04 May 2017 21:59, 23 Jun 2017 05:59. Are you still interested in doing the (quite tricky) review? I have now also tested the build procedures and the software on Debian Stretch, see today's upload of package to

Bug#864241: RFS: pnmixer/0.7.2-1 -- Simple mixer application for system tray

Hi all, sorry for late reply ! > > > > Done, the watch file seem to work according to `uscan`, but > > mentors.debian.net says there's a problem. I'm not sure what's wrong. > > > > Take a look on [1] as an example, your `watch` file is broken > > presumably since you're calling `uupdate`

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

Il giorno 31/ago/2017 00:25, "Adam Borowski" ha scritto: > > On Wed, Aug 30, 2017 at 10:58:05PM +0200, Adam Borowski wrote: > > On Wed, Aug 30, 2017 at 10:37:43PM +0200, Giulio Paci wrote: > > > Are you able to try it on the kfreebsd-i386 building machine? > > > > You do know

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

On Wed, Aug 30, 2017 at 10:58:05PM +0200, Adam Borowski wrote: > On Wed, Aug 30, 2017 at 10:37:43PM +0200, Giulio Paci wrote: > > Are you able to try it on the kfreebsd-i386 building machine? > > You do know you have a kfreebsd-i386 capable machine right on your desk, > right? All you need is

Bug#873630: marked as done (RFS: python-qtpy/1.3.1-1)

Your message dated Wed, 30 Aug 2017 22:20:06 + with message-id and subject line closing RFS: python-qtpy/1.3.1-1 has caused the Debian Bug report #873630, regarding RFS: python-qtpy/1.3.1-1 to be marked as done. This means that you claim that the problem

Bug#873631: marked as done (RFS: pytest-qt/2.1.2-3 [RC])

Your message dated Wed, 30 Aug 2017 22:20:06 + with message-id and subject line closing RFS: pytest-qt/2.1.2-3 [RC] has caused the Debian Bug report #873631, regarding RFS: pytest-qt/2.1.2-3 [RC] to be marked as done. This means that you claim that the

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

On Wed, Aug 30, 2017 at 10:37:43PM +0200, Giulio Paci wrote: > On 29/08/2017 18:43, Giulio Paci wrote: > > As far as I know it is just a matter of available memory. In the past > > we estimated how much memory is needed to compile the package and > > limited the number of compilation processes

Bug#872559: RFS: opengrm-ngram/1.3.2-1 -- opengrm n-gram library

I noticed that the building failed on several architectures. I have the impression that some of them failed due to memory exhaustion and some other were aborted. I monitored RAM on amd64 and found out that most files require about 650MB of RAM in order to be compiled, but a couple of them

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

On 29/08/2017 18:43, Giulio Paci wrote: > On Tue, Aug 29, 2017 at 12:31, "Adam Borowski" > wrote: >> >> On Mon, Aug 28, 2017 at 12:49:22PM +0200, Giulio Paci wrote: >> > Hi Adam, >> > I just saw that building on freebsd-i386 failed due to

Bug#872569: RFS: kadu/4.3-0.1 [RC]

On 29.08.2017 at 21:22 +0200, Andrey Rahmatullin wrote: On Tue, Aug 29, 2017 at 08:22:28PM +0200, Mateusz Łukasik wrote: If parallel is more than 1 (-j1) when is this FTFBS. I will try fix that. Actually you shouldn't fix that if the package works with -J but fails with -j. Please send the

Bug#873113: marked as done (RFS: xssproxy/1.0.0-1 [ITP])

Your message dated Wed, 30 Aug 2017 21:20:22 +0500 with message-id <20170830162022.tg62t4ieitqxh...@belkar.wrar.name> and subject line Re: Bug#873113: RFS: xssproxy/1.0.0-1 [ITP] has caused the Debian Bug report #873113, regarding RFS: xssproxy/1.0.0-1 [ITP] to be marked as done. This means that

Bug#873744: RFS: liboauth/1.0.3-1 [QA-upload]

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "liboauth" * Package name: liboauth Version : 1.0.3-1 Upstream Author : Robin Gareus * URL : http://liboauth.sourceforge.net/ * License