Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

2016-08-08 Thread Gianfranco Costamagna
Hi, >Sorry for this late replay, I've been working on your advices and meanwhile >packaging a new released version (4.6.4). >You'll see in this new version I had to repack upstream sources to make the >package DFSG compliant. Oliver did it with a script (prep.sh); I've used uscan >and >excludin

Bug#833586: marked as done (RFS: groonga/6.0.7-1)

2016-08-08 Thread Debian Bug Tracking System
Your message dated Mon, 8 Aug 2016 16:37:11 + (UTC) with message-id <1476636050.19351324.1470674231954.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#833586: RFS: groonga/6.0.7-1 has caused the Debian Bug report #833586, regarding RFS: groonga/6.0.7-1 to be marked as done. This means

Bug#833766: marked as done (RFS: caffe/1.0.0~rc3+20160715-g42cd785-1)

2016-08-08 Thread Debian Bug Tracking System
Your message dated Mon, 8 Aug 2016 16:12:40 + (UTC) with message-id <1785938898.19108439.1470672760566.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#833766: RFS: caffe/1.0.0~rc3+20160715-g42cd785-1 has caused the Debian Bug report #833766, regarding RFS: caffe/1.0.0~rc3+20160715-g42c

Bug#826715: RFS: lua-torch-torch7/0~20160604-g69d7a01-1 [ITP]

2016-08-08 Thread Gianfranco Costamagna
>changed the target release to experimental, >require 'luajit >= 2.1' as B-D. fails http://debomatic-amd64.debian.net/distribution#experimental/lua-torch-torch7/0~20160803-g17ff317-1/buildlog sbuild-build-depends-lua-torch-torch7-dummy : Depends: luajit (>= 2.1.0~beta2) but it is not going to

Bug#826715: RFS: lua-torch-torch7/0~20160604-g69d7a01-1 [ITP]

2016-08-08 Thread Lumin
Hello, Updated lua-torch-torch7, with a version bump: https://mentors.debian.net/debian/pool/main/l/lua-torch-torch7/lua-torch-torch7_0~20160803-g17ff317-1.dsc On 7 August 2016 at 16:32, Lumin wrote: > > > I'll change the target release, and make the B-D luajit version > constraint strict. ch

Bug#833766: RFS: caffe/1.0.0~rc3+20160715-g42cd785-1

2016-08-08 Thread Lumin
Package: sponsorship-requests Severity: normal Debomatic-amd64: PASS http://debomatic-amd64.debian.net/distribution#experimental/caffe/1.0.0~rc3+20160715-g42cd785-1/buildlog Dear mentors, I am looking for a sponsor for my package "caffe" * Package name: caffe Version : 1.0.0

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Andrew Shadura
On 8 August 2016 at 13:28, Bartosz Fenski wrote: > C us czg, x zf Are you sure about that? -- Cheers, Andrew

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Bartosz Fenski
C us czg, x zf Sent from my Sony Xperia™ smartphone Laurent Bigonville wrote >On 08/08/16 12:09, Paul Wise wrote: >> On Mon, 2016-08-08 at 11:45 +0200, Laurent Bigonville wrote: >> >>> TBH I don't want to use alternatives if the two tools are not using the >>> same flags, for example,

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Laurent Bigonville
On 08/08/16 12:09, Paul Wise wrote: On Mon, 2016-08-08 at 11:45 +0200, Laurent Bigonville wrote: TBH I don't want to use alternatives if the two tools are not using the same flags, for example, arping has two implementation in debian using alternatives (or being installed in two different paths

Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

2016-08-08 Thread Jose G. López
On Tue, 26 Jul 2016 18:18:51 + (UTC) Gianfranco Costamagna wrote: > lets see. > 1) > > The package will be probably orphaned in 10-15 days, so you might want to set > yourself > as Maintainer and adopt it > > 2) > +* Copyright (C) 2013-2015 Fulvio Benini > > > maybe you want also to put

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Paul Wise
On Mon, 2016-08-08 at 11:45 +0200, Laurent Bigonville wrote: > TBH I don't want to use alternatives if the two tools are not using the  > same flags, for example, arping has two implementation in debian using  > alternatives (or being installed in two different paths, not sure  > anymore) but they

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Laurent Bigonville
Le 08/08/16 à 11:18, Paul Wise a écrit : On Mon, Aug 8, 2016 at 5:06 PM, Christian Seiler wrote: Maybe the best idea would then be to have iproute2 ship the ifstat utility as iproute2-ifstat (or similar), keep ifstat as the name for the ifstat package, and if a Linux admin wants to have ifstat

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Paul Wise
On Mon, Aug 8, 2016 at 5:06 PM, Christian Seiler wrote: > Maybe the best idea would then be to have iproute2 ship the > ifstat utility as iproute2-ifstat (or similar), keep ifstat > as the name for the ifstat package, and if a Linux admin > wants to have ifstat be the iproute2 thing, they can easi

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Christian Seiler
On 08/08/2016 10:36 AM, Goswin von Brederlow wrote: > Ifstat upstream is alife and responsive. The command is just complete, > no new features have been added. So I guess we should keep ifstat, if > only for kfreebsd and hurd. Maybe the best idea would then be to have iproute2 ship the ifstat util

Bug#830788: RFS: ifstat/1.1-9

2016-08-08 Thread Goswin von Brederlow
On Sat, Jul 30, 2016 at 07:12:24PM +0200, Laurent Bigonville wrote: > On Mon, 11 Jul 2016 15:44:39 +0200 Goswin von Brederlow > wrote: > > > Dear mentors, > > > > Hi, > > > I am looking for a sponsor for my package "ifstat" > > I have a question, is the ifstat package really still needed? It s