Whom should I send a patch to?

Assume that, I improved some .vim scripts in the package vim-runtime, then I run apt-cache show vim-runtime, to find a email addr like this : ``` Maintainer: Debian Vim Maintainers pkg-vim-maintain...@lists.alioth.debian.org ``` Then, I have some choices: 1. Join a team related to vim, then

odd Vcs-Git pointer in control file, package fortune-zh

Hi, I'm a very newbie trying to adopt a package, according to the Debian new maintainer's guide. My target package is now fortune-zh, as it seems to be very simple to work with (to fix chinese character typo that I noticed). In the 1.10 version (jessie, unstable) of fortune-zh, I found this line

Re: odd Vcs-Git pointer in control file, package fortune-zh

Thank you for advise, Russ Allbery and Paul Wise. I'll try it later :) -- Regards, C.D.Luminate -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

RFS: fortune-zh_1.11, section games

Dear mentors, (Please CC me when reply, thanks!) Package: fortune-zh (native) License: GPL Description: Chinese Data files for fortune This package contains the Chinese data files for fortune in UTF-8 encoding. . Those data files included: * tang300

Re: RFS: fortune-zh_1.11, section games

Oops, I should file a RFS bug against it, instead of posting here. I'm sorry and please ignore the former message, I'm filing the RFS bug now. Thanks. ;) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#779072: RFS: fortune-zh/1.13 [ITA #629014] -- Chinese Data files for fortune

Package: sponsorship-requests Severity: wishlist Dear memtors, I am looking for a sponsor for my package fortune-zh: * Package name: fortune-zh Version : 1.13 Upstream Author : Yu Guanghui y...@debian.org * URL :

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-mentors@lists.debian.org, a...@debian.org Dear mentors, I am looking for a sponsor for package cv: * Package name: cv Version : 0.6-1 Upstream Author : Xfennec * URL :

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)

Hi guys, On Mon, 2015-05-18 at 14:24 +0200, Christoph Egger wrote: I'll give it a look shortly Thank you ;) probably not that one, right? OMG, I missed that line ... Additionally I noticed there's already a package shipping /usr/bin/cv: radiance: /usr/bin/cv maybe you can use a

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)

On Mon, 2015-05-18 at 17:18 +0200, Xfennec wrote: Well, the best tip I can give is the following GitHut issue: https://github.com/Xfennec/cv/issues/8 The summary of this is that I'm pleased with the current name, and think the name conflict is quite unlikely, and is easy to deal with simple

Bug#779072: RFS: fortune-zh/1.11 [ITA] -- Chinese Data files for fortune

retitle 779072 RFS: fortune-zh/1.11 [ITA] -- Chinese Data files for fortune thanks To access further information about this package, please visit the following URL: http://mentors.debian.net/package/fortune-zh Alternatively, one can download the package with dget using this command:

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)

To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cv Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cv/cv_0.6-1.dsc More information

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)

I have rebuild the package cv_0.6-1, with a working watch file, and modified Makefile, and some other small changes. lintian clean. Then the last thing remains to be done upon this package is the change of name ? To access further

Avoiding linking with /home/packaging/X/libxx.so

Hi mentors, I've been struggling with this shared library linking issue for a while. I scanned maint-guide, dev-ref (detail not enough), debmake-doc (osamu's new version of maint-guide), and a library packaging guide [1] that debmake-doc recommended. Then I still have no idea how to handle the

Re: Avoiding linking with /home/packaging/X/libxx.so

Hi mentors, That's not the unusual way to link to a shared library. You should use something like: $(CC) -g -o hello hello.o -L../lib/ -lsharedlib (Although it would probably only work if the library had a SONAME.) I did an experiment. Had the rpath issue fixed, the build result

Re: Avoiding linking with /home/packaging/X/libxx.so

= /home/lumin/hdd/caffe/.build_release/tools/./../lib/libcaffe.so (0x7fb4c816) To my surprise after I installed this executable to /usr/bin: $ ldd caffe.bin | grep libcaffe libcaffe.so = /usr/bin/./../lib/libcaffe.so (0x7fa36300f000) Now I

Bug#785426: RFS: cv/0.6-1 [ITP] -- cv - Coreutils (progress) Viewer)

On Wed, 2015-05-27 at 09:27 +0200, Xfennec wrote: Is such a name is available within Debian ? The good news is, the name progress as an executable is available in Debian. $ apt-file search progress | grep /bin debconf: /usr/bin/debconf-apt-progress

Bug#790957: RFS: fortune-zh/2.0 -- Chinese Data files for fortune

Package: sponsorship-requests Severity: normal X-Debbugs-CC: a...@debian.org lintian: clean Dear mentors, I am looking for a sponsor for my package fortune-zh * Package name: fortune-zh Version : 2.0 Upstream Author : Debian Chinese Team * URL :

Re: why dpkg-buildpackage doesn't care my build targets in debian/rule

I got it. Thank you, Santiago, Jakub, Johannes, Mattia and Wookey ! :) -- Regards, C.D.Luminate -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

why dpkg-buildpackage doesn't care my build targets in debian/rule

Hi mentors, I'm trying to package caffe as said [1] at debian-science@ . However I encountered a problem when writing debian/rules. I'd like to take over the whole build process, so I wrote: 32 override_dh_auto_build: build_cpuonly 33 34 build_cpuonly: config_cpuonly

Re: why dpkg-buildpackage doesn't care my build targets in debian/rule

Hi, I modified the debian/rules[1] according to Santiago and Jakub (thank you both!), and tested again. The result was the same. dh build works while dpkg-buildpackage doesn't. [1] --- the whole debian/rules 1 #!/usr/bin/make -f 2 # See debhelper(7)

Re: why dpkg-buildpackage doesn't care my build targets in debian/rule

Hi mentors, I solved this problem, after line-by-line reviewing the screen output of those commands. It turns out that, the clean target of Makefile needs the Makefile.config too. this rules file makes dpkg-buildpackage continue building. (I deleted some comments )

Re: Introduce wrapper package of linuxbrew into Debian

way I fixed them in my workplace). I'm glad to hear that. If other DDs gives an ack I'll be happy to finish my review :) OK and thank you :-) -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3

Re: Introduce wrapper package of linuxbrew into Debian

) [...] Thank you Gianfranco Costamagna for reviewing this package! :-) -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A signature.asc Description: This is a digitally signed message part

Bug#794187: closed by Gianfranco Costamagna costamagnagianfra...@yahoo.it (uploaded on new queue)

Oops That package is good except for one thing: the issue comes from patch: add-license-info.patch The patch is patching author's source files with author's original copyright declaration in the global LICENSE file and the one in head of progress.c . The patch was sent to author days ago

Re: Introduce wrapper package of linuxbrew into Debian

the GPL-3+ Debian license (not mandatory, but it might be good to clarify I have changed Debian license to GPL-2. FYI: the packaging repo is located at http://anonscm.debian.org/cgit/users/cdluminate-guest/linuxbrew-wrapper.git/ -- .''`. Lumin

Re: Introduce wrapper package of linuxbrew into Debian

installs openssl with linuxbrew: $ brew list openssl /home/lumin/.linuxbrew/Cellar/openssl/1.0.2d_1/bin/c_rehash /home/lumin/.linuxbrew/Cellar/openssl/1.0.2d_1/bin/openssl /home/lumin/.linuxbrew/Cellar/openssl/1.0.2d_1/include/openssl/ (75 files) /home/lumin/.linuxbrew/Cellar/openssl/1.0.2d_1/lib

Bug#794187: RFS: progress/0.7.1~git20150730+9c31d02b65-1 [ITP] (it is formerly known as 'cv')

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package progress * Package name: progress Version : 0.7.1~git20150730+9c31d02b65-1 Upstream Author : Xfennec xfen...@cqfd-corp.org * URL :

Bug#794187: RFS: progress/0.8-1 [ITP] (it is formerly known as 'cv'))

Control: retitle 794187 RFS: progress/0.8-1 [ITP] (it is formerly known as 'cv')) Dear mentors, I'v fixed lintian warning after the last time upload to mentors. Now package progress_0.8-1 is lintian clean. I am looking for a sponsor for my package progress * Package name: progress

Introduce wrapper package of linuxbrew into Debian

/495 [2] http://mentors.debian.net/package/linuxbrew-wrapper -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A signature.asc Description: This is a digitally signed message part

delete unsafe symlink with dquilt

Hi mentors, I'm preparing the linuxbrew package for Debian [1], and found it hard to remove 2 troublesome symlinks from upstream source. Lintian complains that E: linuxbrew source: source-contains-unsafe-symlink Library/ENV/pkgconfig/fuse/fuse.pc They are:

Re: Introduce wrapper package of linuxbrew into Debian

installed by linuxbrew. + See example file /usr/share/doc/linuxbrew/examples/profile == This script will install: /home/lumin/.linuxbrew/bin/brew /home/lumin/.linuxbrew/Library/... /home/lumin/.linuxbrew/share/man/man1/brew.1 Press RETURN to continue or any other key to abort 2) man brew doesn't

Bug#804343: RFS: libsvm/3.20-1 [NMU] -- library implementing support vector machines

Hi, That's OK. Please ping me if there's anything I can help. Thanks. On Mon, 2015-11-09 at 18:59 -0600, Chen-Tse Tsai wrote: > Hi, > > > Sorry for the late reply as I missed your message earlier. I'll update > the package as soon as possible. Thanks for the help! > > > Regards, > Chen-Tse

Bug#804343: RFS: libsvm/3.20-1 [NMU] -- library implementing support vector machines

9) * Add watch file. * d/rules: Bump version as new version is imported. * Update "d/*.install". Regards, lumin

Bug#804343: RFS: libsvm/3.20-1 [NMU] -- library implementing support vector machines

Hi, On Sat, 2015-11-07 at 17:21 +, Gianfranco Costamagna wrote: > version for an NMU should be 3.20-0.1 I've fixed this locally. > this is really out of an NMU scope, do you have any evidence about the > maintainer > being MIA/not interested anymore, or acking you to upload a new release?

Trouble with Alioth user repo: can't be cloned

Hi mentors, I encountered this trouble when making user's personal repo on alioth.d.o according to the link below. [https://wiki.debian.org/Alioth/Git] I've set up 2 repos: http://anonscm.debian.org/cgit/users/cdluminate-guest/caffe.git

Re: Trouble with Alioth user repo: can't be cloned

Hi Alexander Wirt, Thank you very much, and now it works! On Thu, 2015-07-09 at 08:58 +0200, Alexander Wirt wrote: I'm confused. And you are right to be confused. It was a bug on our (alioth) side. I fixed it and cloning is now possible. Alex -- To UNSUBSCRIBE, email to

Re: Introduce wrapper package of linuxbrew into Debian

things in d/rules next time upload. thanks again for packaging it and for following my boring nitpicks :) Also thanks again for pointing them out :-) -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264

Re: Introduce wrapper package of linuxbrew into Debian

-wrapper_20150804-1.dsc Changes since last upload: * dch -r unstable * bump debian copyright to bsd-2-clause * update manpage Thanks. -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A

[caffe] one step closer to the final caffe package

very slow ...) Thank you. -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A

Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

Hi Gianfranco Costamagna, On Thu, 2015-09-03 at 13:41 +, Gianfranco Costamagna wrote: > Can you please start by fixing the lintian warnings on mentors page? Now caffe is lintian clean. and I've stripped some lines in dch. Please have a look at it. :-) Thanks.

Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

On Thu, 2015-09-03 at 15:13 +, Gianfranco Costamagna wrote: > > Hi, > > control: > > libboost-all-dev (>= 1.55) | libboost1.55-all-dev (>= 1.55), > what is the rationale for that? I guess libboost-all-dev is already enough... I've removed libboost1.55-all-dev (>= 1.55) locally. >

Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

On Fri, 2015-09-04 at 17:14 +, Gianfranco Costamagna wrote: > Hi again, > > The package doesn't build in a clean environment. > > http://debomatic-amd64.debian.net/distribution#experimental/caffe/0.~rc2+git20150902+e8e660d3-1/buildlog Well, I am surprised source Caffe suffers FTBFS on

Re: Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

Hi Gianfranco Costamagna, On Fri, 2015-09-04 at 17:04 +, Gianfranco Costamagna wrote: > if they aren't called by standard dh calls it is fine to keep them there. > > maybe just move to the bottom, (I think they are already there) I will keep those custom target in the bottom of d/rules.

how to prevent dpkg-shlibdeps from Depending on CONFLICTING packages?

pu and caffe-cuda suites are conflicting with each other, which means the dependency entry generated by `dpkg-shlibdeps` is wrong. I looked up dpkg-shlibdeps(1), but found no option like 'exclude' 'prevent' etc... How should I prevent that wrong and needless dependencies ? Sed'ing caffe-cpu.su

[Caffe] uploaded to mentors but NOT RFS

1st python3 package), so I'm not sure how far it is to be accepted into Archive. Just a ping, thank you all. :-) -- .''`. Lumin : :' : `. `' `-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A signature.asc

Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-mentors@lists.debian.org, 788...@bugs.debian.org Dear mentors, I am looking for a sponsor for my package "caffe" * Package name: caffe Version :

Re: how to prevent dpkg-shlibdeps from Depending on CONFLICTING packages?

=python-caffe-cuda \ 121 -- \ 122 -xlibcaffe-cpu0 123 endif Thank you all. On Thu, 2015-09-03 at 07:10 +, lumin wrote: > Hi mentors, > > I'm packaging caffe, which is nearly done. > > http://mentors.debian.net/package/caffe > > http://mentors.debian.net/

Re: Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

Hi, I've uploaded updated Caffe to mentors. http://mentors.debian.net/package/caffe On Thu, 2015-09-03 at 15:13 +, Gianfranco Costamagna wrote: > libboost-all-dev (>= 1.55) | libboost1.55-all-dev (>= 1.55), > what is the rationale for that? I guess libboost-all-dev is already enough...

Re: Fwd: Re: [Caffe] uploaded to mentors but NOT RFS

On Wed, 2015-09-09 at 09:03 +, lumin wrote: > > note that nvidia-cuda-toolkit is from non-free. And packages from main > can't build-depend on non-free components :-/ It means that it might > be necessary either to > > 1. move caffe into contrib (again, away from

Re: Fwd: Re: [Caffe] uploaded to mentors but NOT RFS

Hi, On Wed, 2015-09-09 at 09:02 +, lumin wrote: > snapshot versions use following strategy to come up with upstream version -- > should end with what 'git describe' ends with for the treeish: e.g. > > $> git describe --tags e8e66 > rc2-513-ge8e660d > > a

[Caffe / ITP / FTBFS] undefined reference to `XXX` issue

r a day when caffe-cuda can pass the build. Any comment is appreciated. Thank you all. :-) [1] http://caffe.berkeleyvision.org/ [2] http://anonscm.debian.org/cgit/debian-science/packages/caffe.git/ [3] https://github.com/CDLuminate/asdf/blob/master/caffe_0.~rc2%2B20150925-g674b349-1_amd64.build --

Bug#799557: RFS: progress/0.9-1 -- Coreutils Progress Viewer

Package: sponsorship-requests Severity: normal X-Debbugs-CC: costamagnagianfra...@yahoo.it Dear mentors, I am looking for a sponsor for my package "progress" * Package name: progress Version : 0.9-1 Upstream Author : Xfennec * URL :

Bug#799565: RFS: linuxbrew/20150804-2 -- missing package manager for linux

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "linuxbrew-wrapper" * Package name: linuxbrew-wrapper Version : 20150804-2 Upstream Author : Linuxbrew contributors * URL :

Bug#799565: Acknowledgement (RFS: linuxbrew/20150804-2 -- missing package manager for linux)

Control: retitle 799565 RFS: linuxbrew-wrapper/20150804-2 -- missing package manager for linux signature.asc Description: This is a digitally signed message part

Re: Bug#799390: linuxbrew-wrapper: over-restrictive architecture setting?

Hi Aaron M. Ucko, On Fri, 2015-09-18 at 13:11 -0400, Aaron M. Ucko wrote: > linuxbrew-wrapper's control file declares amd64 to be the only > supported architure. Is that restriction really necessary? From what > I gather, Linuxbrew is perfectly capable of building software from > source, so it

Bug#799557: RFS: progress/0.9-1 -- Coreutils Progress Viewer

On Mon, 2015-09-21 at 07:33 +, Gianfranco Costamagna wrote: > can you please add them both? Fixed, please take a look at dch. :-) And updated version was uploaded to mentors. To access further information about this package, please visit the following URL:

Bug#804343: RFS: libsvm/3.20-1 [NMU] -- library implementing support vector machines

Hi, Actually I don't know how it is going. However IMHO you we can close this RFS, and wait for the maintainer to update this package someday... Thanks. On Wed, 2015-11-25 at 15:44 +, Gianfranco Costamagna wrote: > Hi Lumin and Chen-Tse, > > thanks for the answer, let me know if

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

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org, a...@debian.org Dear mentors, This package is the very core part of "Torch", a state-of-the-art machine learning framework. Note, this package requires luajit from experimental, and the

Bug#826705: RFS: lua-torch-paths/0~20160203-g68d579a-1 [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org, a...@debian.org Dear mentors, This package is a part of "Torch", a state-of-the-art machine learning framework. Home: http://torch.ch I am looking for a sponsor for my package

Bug#826704: RFS: lua-torch-cwrap/0~20160222-gdbd0a62-1 [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org, a...@debian.org Dear mentors, This package is a part of "Torch", a state-of-the-art machine learning framework. I am looking for a sponsor for my package "lua-torch-cwrap" * Package name

Bug#826076: Acknowledgement (RFS: lua-cwrap/0~20160222-gdbd0a62-1 -- CWrap package for Torch Framework [ITP])

Mentors package is updated.

Bug#826081: RFS: linuxbrew-wrapper/20160506-1

Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "linuxbrew-wrapper" * Package name: linuxbrew-wrapper Version : 20160506-1 Upstream Author : Shaun Jackman. * URL

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

On Thu, 2016-05-26 at 14:32 +0100, Ghislain Vaillant wrote: > I don't agree. Regarding the testsuite, I believe most features should > be tested at package build time, including the Python stuff. We want to > fail early if something goes wrong. To me, the autopkgtest testsuite > serves a

Bug#826076: RFS: lua-cwrap/0~20160222-gdbd0a62-1 -- CWrap package for Torch Framework [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "lua-cwrap" * Package name: lua-cwrap Version : 0~20160222-gdbd0a62-1 Upstream Author : Torch Developers * URL

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

On Tue, 2016-05-31 at 16:17 +, Gianfranco Costamagna wrote: > Hi, > > python-skimage should be RC free now (if no other RC bugs are opened of > course :) ) > > let me know when you have updates, > > G. Thank you for working on it ! :-)

Bug#827895: RFS: lua-torch-nn/0~20160604-gd23a8f5+dfsg-1 [ITP]

se. Closes: #826794 -- Best, Lumin

Bug#827590: RFS: lua-torch-trepl/0~20160613-g06128f9-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lua-torch-trepl" * Package name: lua-torch-trepl Version : 0~20160613-g06128f9-1 Upstream Author : Torch Developers * URL : github.com/torch/trepl *

Bug#827582: RFS: lua-torch-xlua/0~20160617-g0dd5f4c-1 [ITP]

* Initial release. Closes: #826791 -- Best, Lumin

Bug#827521: RFS: lua-torch-sys/0~20160415-g8d2b8fa-1 [ITP]

rch-sys (0~20160415-g8d2b8fa-1) experimental; urgency=low * Initial release. Closes: #826792 -- Best, Lumin

Bug#814388: RFS: progress/0.13-1

ss (0.13-1) unstable; urgency=medium * Import upstream version 0.13. * Fix typo in section progress (0.12.1+git20160202-g2ec12d42-1), "pkg-control" -> "pkg-config" Regards, lumin

Bug#813495: RFS: progress/0.12.1+git20160202-g2ec12d42-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "progress" * Package name: progress Version : 0.12.1+git20160202-g2ec12d42-1 Upstream Author : xfennec * URL : https://github.com/Xfennec/progress * License

Bug#816356: RFS: progress/0.13-2

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "progress" * Package name: progress Version : 0.13-2 Upstream Author : xfennec * URL : https://github.com/Xfennec/progress * License : gpl-3

Bug#819536: RFS: linuxbrew-wrapper/20150804-3

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "linuxbrew-wrapper" * Package name: linuxbrew-wrapper Version : 20150804-3 Upstream Author : homebrew * URL : http://brew.sh/linuxbrew/ * License :

[Mentors] upload via http fails with HTTP 403

the mentors site. ``` D: File to upload: /home/lumin/hdd/schroot/sid/tmp/python-caffe-cuda_1.0.0~rc3-1_amd64.deb D: Checksum for /home/lumin/hdd/schroot/sid/tmp/python-caffe-cuda_1.0.0~rc3-1_amd64.deb is fine D: Checking: distribution experimental matches .* D: File to upload: /home/lumin/hdd/schroot/sid

Re: [Mentors] upload via http fails with HTTP 403

On Fri, 2016-04-29 at 16:15 +0200, Christian Seiler wrote: > > Did you upload the package with the same version number before and > then deleted the package in the web interface? No deletion. > My experience with > mentors is that the HTTP interface really doesn't like that, IIRC I > got HTTP

Re: [Mentors] upload via http fails with HTTP 403

On Fri, 2016-04-29 at 14:43 +, Gianfranco Costamagna wrote: > This is what I had on my dput.cf > (note: I used mentors a few months ago, last time) > > [mentors] > method = ftp > fqdn= mentors.debian.net > incoming= . > login

Re: [Mentors] upload via http fails with HTTP 403

On Fri, 2016-04-29 at 13:53 +, Gianfranco Costamagna wrote: > Hi, > 1) upload *source only* stuff > 2) no dcut is supported > > to fix, just upload -f also the changes file, at this point it will be > processed, the files removed from the queue > and you will be able to repush the package. >

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

On Thu, 2016-05-19 at 06:32 +, Gianfranco Costamagna wrote: > Hi Lumin, > >Why should runtime deps be added into build-dep, which are useless > >unless I provide python-caffe-* testsuite. > > > not sure then, it should be fine that way! An update to

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Control: block -1 by 795841 Control: block 788539 by 795841 On Wed, 2016-05-18 at 21:12 +, Gianfranco Costamagna wrote: > Hi Lumin, > > >Thank you James, I've solved this problem. > I don't want to do the final checks until Ghislain gives me his personal ack, > but > I

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Control: block -1 by 799262 one more functional blocker, python3-opencv opencv is (I guess) frequently used by caffe users, Debian should have python3-opencv if we provide python3-caffe. when is the EOL of python2.x? I forgot it. If it is not 2017, can we first upload python2-caffe-* ? I'll

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Thank you for this careful and thorough review! On Tue, 2016-05-17 at 14:50 +0100, Ghislain Vaillant wrote: > Dear all, > > On 16/05/16 15:50, Gianfranco Costamagna wrote: > > Hi Lumin > > > > > >> Done. Updated package has been uploaded to mentors: > >

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

On Tue, 2016-05-17 at 16:55 +0100, Ghislain Vaillant wrote: > On 17/05/16 15:42, lumin wrote: > > Thank you for this careful and thorough review! http://anonscm.debian.org/cgit/debian-science/packages/caffe.git/ Let me summarize the changes this time * remove python script for autogen,

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

debomatic result * build pass, * autopkgtest OK, according to log no error occurs * lintian remains 1 warning about that weird YAML issue * piuparts fails because of DoM problem updated package was uploaded to mentors https://mentors.debian.net/package/caffe

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

> Title: 'Caffe: Convolutional Architecture for Fast Feature Embedding' Thank you James, I've solved this problem. Mentors, please check the latest caffe package on mentors: https://mentors.debian.net/package/caffe debomatic result should be the same as that obtained 1 hour ago. I think

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

On Sat, 2016-05-07 at 10:05 +0100, Ghislain Vaillant wrote: > > s/DEB_CPPFLAGS_MAINT_APPEND/DEB_CXXFLAGS_MAINT_APPEND in your d/rules. > Done. Updated package has been uploaded to mentors: https://mentors.debian.net/package/caffe

Bug#824104: RFS: gneural-network/0.9.1-1 [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: Jean Michel Sellier , a...@debian.org Dear mentors, I am looking for a sponsor for my package "gneural-network" * Package name: gneural-network Version : 0.9.1-1 Upstream Author :

Bug#824104: RFS: gneural-network/0.9.1-1 [ITP]

On Thu, 2016-05-12 at 11:17 +0100, Ghislain Vaillant wrote: > On 12/05/16 10:41, lumin wrote: > > Package: sponsorship-requests > > [...] > > Thanks, > > mentors: "Watch file is not present" > > Why? http://cvs.savannah.gnu.org/viewvc/gneuralnetwor

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Hi mentors, I found the way to fix lintianI: no-fortify-functions, and I'll add multi-arch support as suggested by Aron, so please wait for my next upload.

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Hi mentors, I've fixed the issues you pointed out. New packages are rebuilt locally, and uploaded to mentors. https://mentors.debian.net/package/caffe Debomatic-amd64 is still building this updated package: http://debomatic-amd64.debian.net/distribution#experimental/caffe/1.0.0~rc3-1/buildlog

Bug#823289: RFS: progress/0.13-3

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "progress" * Package name: progress Version : 0.13-3 Upstream Author : xfennec * URL : github.com/xfennec/progress * License : gpl Section

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: a...@debian.org, deb...@danielstender.com, deb...@onerussian.com, debian-de...@lists.debian.org, debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "caffe" * Package name: caffe

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Hi, I've split the caffe-cpu package and the caffe-cuda package, and I'd like to first handle the cpu version, leaving the CUDA version pending at debian/science/caffe-contrib. The updated cpu version has been uploaded to mentors: https://mentors.debian.net/package/caffe This update involves

Bug#832703: RFS: caffe-contrib/1.0.0~rc3-2

c:caffe (1.0.0~rc3-4). + Import README.Debian from src:caffe. * Update symbols control file. -- Best, Lumin

weird dependency-installbility problem of buildd

tic-amd64.debian.net/distribution#experimental/caffe-contrib/1.0.0~rc3-2/buildlog ​ ​[4] https://buildd.debian.org/status/package.php?p=caffe-contrib=experimental ​ ​[5] https://buildd.debian.org/status/package.php?p=nvidia-cuda-toolkit=sid ​ -- Best, Lumin

Bug#832647: RFS: caffe/1.0.0~rc3-4

- update-MNIST-example-to-use-new-DB-classes * Update symbols control file, diverge symbols control file for ppc64el. * Synchronize packaging with src:caffe-contrib (= 1.0.0~rc3-2). -- Best, Lumin

Bug#834332: RFS: lua-torch-optim/0~20160808-g6c59c35-1 [ITP]

perimental; urgency=low * Initial release. Closes: #827435 -- Best, Lumin

Bug#827582: RFS: lua-torch-xlua/0~20160617-g0dd5f4c-1 [ITP]

bomatic is still failing ... -- Best, Lumin

Bug#834325: RFS: lua-torch-graph/0~20160415-g34d7128-1 [ITP]

nges since the last upload: lua-torch-graph (0~20160415-g34d7128-1) experimental; urgency=low * Initial release. Closes: #827432 -- Best, Lumin

Bug#827582: missing ITP

Control: block 826793 by 827582 Hi, the missing ITP is found. On 12 August 2016 at 11:30, Bart Martens <ba...@debian.org> wrote: > Hi Lumin, > > Where is the ITP? There should be one, see the instructions at "new packages": > https://www.debian.org/doc/manuals/de

Bug#827895: missing ITP

Control: block 826794 by 827895 Hi, now the missing ITP is found. On 12 August 2016 at 11:23, Bart Martens <ba...@debian.org> wrote: > Hi Lumin, > > Where is the ITP? There should be one, see the instructions at "new packages": > https://www.debian.org/doc/manuals/de

  1   2   3   >