Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]
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 >excluding files in debian/copyright (hope it's correct). thanks :) >P.D: On mentors, the watch file seems that doesn't work but on my devel >machine is working properly ?? not a problem. (mentors uscan seems to be outdated) new review: 1) please convert the versioning into 1:4.6.2-1 and remove the NMU syntax. and add a "Set myself as Maintainer" 2) missing newline between last entry and your signature to make it DFSG compliant. -- Jose G. López Mon, 08 Aug 2016 11:23:07 +0200 3) copyrights missing grep -i copyright . -R |grep -v Fulv |grep -v Shane |grep -vi pascal after that we should be *really* good, and I'll put the package in deferred, to make it reach unstable in 15 days or so (mia team should orphan the package in the meanwhile). In case it gets orphaned close the bug with "set myself as Maintainer (Closes: #) thanks! G.
Bug#833586: marked as done (RFS: groonga/6.0.7-1)
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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 833586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "groonga" * Package name: groonga Version : 6.0.7-1 Upstream Author : Groonga Project * URL : http://groonga.org/ * License : LGPL-2.1 Section : database It builds those binary packages: groonga- Fulltext search engine (metapackage for library use) groonga-bin - Commands for Groonga groonga-doc - Documentation of Groonga groonga-examples - Examples of Groonga groonga-httpd - Groonga HTTP server groonga-munin-plugins - munin-node plugins for Groonga groonga-plugin-suggest - Suggest plugin for Groonga groonga-server-common - Fulltext search engine (metapackage for server use) groonga-server-gqtp - Fulltext search engine (metapackage for GQTP server use) groonga-token-filter-stem - Stemming token filter for Groonga groonga-tokenizer-mecab - MeCab tokenizer for Groonga libgroonga-dev - Development files to use Groonga as a library libgroonga0 - Library files for Groonga To access further information about this package, please visit the following URL: https://mentors.debian.net/package/groonga Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/groonga/groonga_6.0.7-1.dsc More information about groonga can be obtained from http://groonga.org. Changes since the last upload: * New upstream release. * debian/patches/fix-nginx-build-error-with-openssl-1.1.patch - Update OpenSSL patch for bundled nginx 1.11.3 Regards, pgpVHo65AtI6g.pgp Description: PGP signature --- End Message --- --- Begin Message --- Hi, >I am looking for a sponsor for my package "groonga" its in, G.--- End Message ---
Bug#833766: marked as done (RFS: caffe/1.0.0~rc3+20160715-g42cd785-1)
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-g42cd785-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 833766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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~rc3+20160715-g42cd785-1 Upstream Author : BVLC * URL : caffe.berkeleyvision.org * License : BSD-2-Clause Section : science It builds those binary packages: caffe-cpu - Fast, open framework for Deep Learning (Meta) caffe-doc - Doxygen Document of Caffe caffe-tools-cpu - Tools for fast, open framework for Deep Learning (CPU_ONLY) libcaffe-cpu-dev - development files for Caffe (CPU_ONLY) libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY) python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/caffe Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3+20160715-g42cd785-1.dsc Changes since the last upload: caffe (1.0.0~rc3+20160715-g42cd785-1) experimental; urgency=medium * Import upstream snapshot (42cd785e4b5ed824a9b2a02a19aa534042b64325). * Suggest OpenBLAS/Atlas library for metapackage caffe-cpu. * Update manpage d/man/caffe.1 . * Comment out "-pedantic" from rules to reduce the size of build log. * Drop cherry-picked patches, already included in this new snapshot: - dont-set-map-size-1TB-in-db-lmdb - print-to-stderr-for-example-LMDB-code - update-MNIST-example-to-use-new-DB-classes * Remove patch fix-spelling-error, which was merged by upstream. * Refresh patch cmake-fix-python-module-installdir. * Refresh symbols comtrol file. * Override dh_fixperms to remove executable bit from several python scripts. * Add git and libboost-dev to B-D. * Add patch: cmake-avoid-argument-missing . -- Best, Lumin --- End Message --- --- Begin Message --- Hi, > * Add git and libboost-dev to B-D. next time please specify *why* you need to add them. sponsored, G.--- End Message ---
Bug#826715: RFS: lua-torch-torch7/0~20160604-g69d7a01-1 [ITP]
>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 be installed Depends: lua-torch-paths which is a virtual package and is not provided by any available package >Forwarded. add cmake versioning for libluaT.so Fowrad: not yet BTW "Fowrad" please update and fix the typo and ping back when you have something ready. G.
Bug#826715: RFS: lua-torch-torch7/0~20160604-g69d7a01-1 [ITP]
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.
changed the target release to experimental,
require 'luajit >= 2.1' as B-D.
> > also, not neeed to specify this
> > Depends: ${misc:Depends}, ${shlibs:Depends}, luajit | lua5.1,
Fixed.
>
> > do you really want to maintain that downstream? please forward it.
>
Forwarded.
>
>
> > why luaT and TH are not packaged separately? at a first look (not
careful at all)
> > they look external dependencies
--
Best,
Lumin
Bug#833766: RFS: caffe/1.0.0~rc3+20160715-g42cd785-1
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~rc3+20160715-g42cd785-1 Upstream Author : BVLC * URL : caffe.berkeleyvision.org * License : BSD-2-Clause Section : science It builds those binary packages: caffe-cpu - Fast, open framework for Deep Learning (Meta) caffe-doc - Doxygen Document of Caffe caffe-tools-cpu - Tools for fast, open framework for Deep Learning (CPU_ONLY) libcaffe-cpu-dev - development files for Caffe (CPU_ONLY) libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY) python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/caffe Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3+20160715-g42cd785-1.dsc Changes since the last upload: caffe (1.0.0~rc3+20160715-g42cd785-1) experimental; urgency=medium * Import upstream snapshot (42cd785e4b5ed824a9b2a02a19aa534042b64325). * Suggest OpenBLAS/Atlas library for metapackage caffe-cpu. * Update manpage d/man/caffe.1 . * Comment out "-pedantic" from rules to reduce the size of build log. * Drop cherry-picked patches, already included in this new snapshot: - dont-set-map-size-1TB-in-db-lmdb - print-to-stderr-for-example-LMDB-code - update-MNIST-example-to-use-new-DB-classes * Remove patch fix-spelling-error, which was merged by upstream. * Refresh patch cmake-fix-python-module-installdir. * Refresh symbols comtrol file. * Override dh_fixperms to remove executable bit from several python scripts. * Add git and libboost-dev to B-D. * Add patch: cmake-avoid-argument-missing . -- Best, Lumin
Bug#830788: RFS: ifstat/1.1-9
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
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, arping has two implementation in debian using >>> alternatives (or being installed in two different paths, not sure >>> anymore) but they are not providing the same flags/options, >>> network-manager is using this tool but only works with one of the implementation. >> Why isn't there a Breaks from the right arping to network-manager? >> >>> FTR, other distributions (RHEL/Fedora at least) are using the iproute >>> implementation. >> Probably that is the best way to go then. >> >Mhh, on Fedora the two implementations are available actually (but not >on RHEL) and the iproute one is being installed by default. >
Bug#830788: RFS: ifstat/1.1-9
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, not sure anymore) but they are not providing the same flags/options, network-manager is using this tool but only works with one of the implementation. Why isn't there a Breaks from the right arping to network-manager? FTR, other distributions (RHEL/Fedora at least) are using the iproute implementation. Probably that is the best way to go then. Mhh, on Fedora the two implementations are available actually (but not on RHEL) and the iproute one is being installed by default.
Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]
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 copyright file in machine readable format > https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ > Done. > 3) > X: scid source: maybe-not-arch-all-binnmuable scid -> scid-data > > 4) the breaks+replaces can be dropped, since that version is already > available in oldstable > > Breaks: scid (<=1:4.3.0.cvs20110714-2) > Replaces: scid (<=1:4.3.0.cvs20110714-2) > Recommends: scid (>=1:4.3.0.cvs20111216-1) > Dropped. > last thing: > > 4) this hack seems useless now > sed s/x86_64-linux-gnu/$(DEB_HOST_MULTIARCH)/ configure > configure.sed > chmod 755 configure.sed > ./configure.sed BINDIR="$(CURDIR)/debian/tmp/scid/usr/games" \ Deleted too. > > please fix the above and I'll give another review/upload. > > thanks, > > G. Hi Gianfranco, 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 excluding files in debian/copyright (hope it's correct). It's uploaded to mentors[0]. Thanks and regards, P.D: On mentors, the watch file seems that doesn't work but on my devel machine is working properly ?? [0]https://mentors.debian.net/package/scid pgpgdVz1PK0qZ.pgp Description: PGP signature
Bug#830788: RFS: ifstat/1.1-9
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 are not providing the same flags/options, > network-manager is using this tool but only works with one of the > > implementation. Why isn't there a Breaks from the right arping to network-manager? > FTR, other distributions (RHEL/Fedora at least) are using the iproute > implementation. Probably that is the best way to go then. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#830788: RFS: ifstat/1.1-9
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 be the iproute2 thing, they can easily set an alias in their shell. (Maybe add instructions to a README.Debian file.) Sounds like a case for alternatives, are the two implementations command-line compatible? 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 are not providing the same flags/options, network-manager is using this tool but only works with one of the implementation. FTR, other distributions (RHEL/Fedora at least) are using the iproute implementation.
Bug#830788: RFS: ifstat/1.1-9
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 easily > set an alias in their shell. (Maybe add instructions to a > README.Debian file.) Sounds like a case for alternatives, are the two implementations command-line compatible? -- bye, pabs https://wiki.debian.org/PaulWise
Bug#830788: RFS: ifstat/1.1-9
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 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 easily set an alias in their shell. (Maybe add instructions to a README.Debian file.) Regards, Christian
Bug#830788: RFS: ifstat/1.1-9
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 seems to be > dead upstream (last release is from 2004). > > The iproute2 package (which is still maintained upstream) also has a ifstat > binary, I've added that binary by mistake in the last upload I've made. > > So I see two solutions here, either I'm removing that binary from the > iproute2 package (and we are back to the situation before my boggus upload) > or we are removing the ifstat package from debian. Note iproute2 is linux > only though. > > Any thoughts about this? > > Regards, > > Laurent Bigonville How do they compare in functionality? 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. MfG Goswin
