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

2015-05-18 Thread lumin
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

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

2015-05-18 Thread lumin
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 > s

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

2015-05-19 Thread lumin
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)

2015-05-19 Thread lumin
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 infor

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

2015-05-21 Thread lumin
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

2015-05-21 Thread lumin
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

2015-05-21 Thread lumin
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: why dpkg-buildpackage doesn't care my build targets in debian/rule

2015-05-23 Thread lumin
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: https://lists.debian.org/1432439429.714

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

2015-05-27 Thread lumin
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

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

2015-06-12 Thread lumin
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 pro

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

2015-06-12 Thread lumin
ed that: $ ldd caffe | grep libcaffe libcaffe.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/b

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

2015-06-13 Thread lumin
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 r

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

2015-07-03 Thread lumin
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 : http://anonsc

Trouble with Alioth user repo: can't be cloned

2015-07-08 Thread lumin
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 http://anonscm.debian.org/cgit/users/cdluminate-guest/test.

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

2015-07-09 Thread lumin
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 t

Bug#860804: RFS: highwayhash/0~20170419-g1f4a24f-1 [ITP] -- tensorflow dependency library

2017-04-24 Thread Lumin
Hi Adam, > It does look uploadable, yeah, even though there's a bunch of issues. It's > up to you whether you want to get it good first or to upload present state > then improve it incrementally. Please say what you prefer. I updated the package again with the following changes: * changed Mul

Bug#861289: RFS: highwayhash/0~20170419-g1f4a24f-2

2017-04-26 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20170419-g1f4a24f-2 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upst

Bug#861291: RFS: luajit/2.1.0~beta2+dfsg-3.1 -- [NMU,RC/experimental]

2017-04-26 Thread Lumin
Package: sponsorship-requests Severity: important X-Debbugs-CC: 818...@bugs.debian.org, woo...@wookware.org, da...@dannf.org, gareuselesi...@debian.org NOTE: not approved by maintainer (Enrico Tassi) yet. Dear mentors, I am looking for a sponsor for my package "luajit" * Package name:

Bug#861291: Fwd: RFS: luajit/2.1.0~beta2+dfsg-3.1 -- [NMU,RC/experimental]

2017-04-26 Thread Lumin
you. :-) -- Forwarded message -- From: Lumin Date: 27 April 2017 at 03:17 Subject: RFS: luajit/2.1.0~beta2+dfsg-3.1 -- [NMU,RC/experimental] To: submit Package: sponsorship-requests Severity: important X-Debbugs-CC: 818...@bugs.debian.org, woo...@wookware.org, da...@dannf.org

Bug#861291: Fwd: RFS: luajit/2.1.0~beta2+dfsg-3.1 -- [NMU,RC/experimental]

2017-05-04 Thread Lumin
s to a single patch should be more suitable even for a 0 day > NMU, > while changing std-version and that above stuff will probably mean: > 1) 15 days delay for the upload > 2) a maintainer ack. > > Your call :) > > cheers and thanks for the RFS! > > G. -- Best

Bug#861289: RFS: highwayhash/0~20170419-g1f4a24f-2

2017-05-04 Thread Lumin
t symbol files > > one single file should be enough for every arch. > > G. -- Best, Lumin

Bug#833193: RFS: chapel/1.15-1 [ITP]

2017-05-04 Thread Lumin
m rules, including the CHPL_LLVM flag which seems to be a key of one of your TODO. This chapel 1.15 package was succesfully built on my laptop and a simple helloworld example is working. -- Best, Lumin

Bug#833193: RFS: chapel/1.15-1 [ITP]

2017-05-10 Thread Lumin
Hi Ben, > We do install the Chapel modules and runtime to versioned directories > like this: > > /usr/share/chapel/1.15/modules etc > > The documentation is installed to > > /usr/share/doc/chapel/1.15/rst etc > > Is it obviously better in your opinion to use > > /usr/share/chapel-1.1

Bug#833193: RFS: chapel/1.15-1 [ITP]

2017-05-14 Thread lumin
On Fri, 2017-05-12 at 20:41 +, Ben Albrecht wrote: > > We understand that Debian plans to upgrade to Python 3. We're not > intending to install user-visible Python scripts or modules. The > Python code that we use is used internally by our compiler and build > scripts. In this case, is it nece

Bug#863229: RFS: lua-torch-cutorch/0~20170511-g92e9c08-1

2017-05-24 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "lua-torch-cutorch" * Package name: lua-torch-cutorch Version : 0~20170511-g92e9c08-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in

Bug#864271: RFS: protobuf/3.3.1-0.1 [NMU]

2017-06-05 Thread Lumin
Package: sponsorship-requests Severity: normal Tags: morinfo X-Debbugs-CC: pkg-protobuf-de...@lists.alioth.debian.org Clarification-moreinfo: this tag is for protbuf maintainers to approve this NMU. Dear mentors, I am looking for a sponsor for my package "protobuf" * Package name: pr

Bug#864271: [Pkg-protobuf-devel] Bug#864271: RFS: protobuf/3.3.1-0.1 [NMU]

2017-06-06 Thread Lumin
Hi GCS, Thank you for the quick reply. On 6 June 2017 at 10:06, László Böszörményi (GCS) wrote: >> Clarification-moreinfo: >> this tag is for protbuf maintainers to approve this NMU. > You misspelled the package name and the tag as well, among other things. Sorry for the typo, I fixed that t

Bug#849273: RFS: gemmlowp/0~20170407-g719389f-1 [ITP]

2017-06-17 Thread Lumin
Hi, On 16 June 2017 at 04:33, Ying-Chun Liu (PaulLiu) wrote: > I've reviewed your package. The package looks quite good to me. > The only thing missing is the README.source > https://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource Updated the package and uploaded to mentors. http

Bug#869664: RFS: ptpython/0.39~20170703-1 [ITP]

2017-07-25 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "ptpython" * Package name: ptpython Version : 0.39~20170703-1 Upstream Author : jonathanslenders * URL : https://github.com/jonathanslenders/ptpython * Li

Bug#869664: RFS: ptpython/0.39~20170703-1 [ITP]

2017-07-25 Thread Lumin
ted ... ] -> Iter 1 | loss 2.196 | Bch Train Accu 0.28 -> Iter 2 | loss 1.967 | Bch Train Accu 0.47 -> Iter 3 | loss 1.853 | Bch Train Accu 0.53 On 25 July 2017 at 13:23, Andrey Rahmatullin wrote: > Why is this aimed at experimental? > > -- > WBR, wRAR -- Best, Lumin

Bug#870125:

2017-07-29 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lua-moses" * Package name: lua-moses Version : 1.6.1+git20170613-1 Upstream Author : Yonaba * URL :http://yonaba.github.io/Moses/ * License : MIT

Bug#870127: RFS: lua-moses/1.6.1+git20170613-1 -- [ITP] Utility library for functional programming in Lua

2017-07-29 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lua-moses" * Package name: lua-moses Version : 1.6.1+git20170613-1 Upstream Author : Yonaba * URL :http://yonaba.github.io/Moses/ * License : MIT

Bug#887683: RFS: highwayhash/0~20180103-geeea446-1 [RC/experimental]

2018-01-18 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180103-geeea446-1 Upstream Author : * URL : * License : Section : science It b

Bug#887699: RFS: lua-moses/1.6.1+git20170613-1 [ITP]

2018-01-18 Thread Lumin
Package: sponsorship-requests Severity: wishlist Note: The first time upload was rejected by ftpmaster due to license issues. I have fixed them in this version. This ITP package will fix an RC bug of another package lua-torch-nn, because lua-moses was added as a new dependency by upstream. Dear

Bug#887728: RFS: nvidia-cudnn/7.0.5~cuda9.0-1 [ITP / ppc64el help needed]

2018-01-19 Thread Lumin
eader File To access further information about this package, please visit the following URL: https://salsa.debian.org/lumin-guest/nvidia-cudnn ##NOTE## I didn't upload the package to debomatic-amd64, nor the mentors because the source package is too large to me (~660MB). My local a

Bug#889800: RFS: highwayhash/0~20180103-geeea446-2

2018-02-06 Thread Lumin
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180103-geeea446-2 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of u

Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP]

2018-02-15 Thread Lumin
control: owner -1 ! control: tag -1 +moreinfo Hi Félix, Some comments on your package: changelog --- * One line is enough for the initial upload, e.g. "Initial release. (Closes: #753350)" compat & control - * I'd recommend to use debhelper compat level

Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]

2018-02-15 Thread Lumin
six.py. What's the relationship between it and python3-six? My preliminary guess is that upstream just copied that file to their project. 2. This package failed to build when python2 version of sphinx exists: make[2]: Entering directory '/home/lumin/packages/sponsor/python-jsonrpc-1

Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP]

2018-02-15 Thread Lumin
control: owner -1 ! control: tags -1 +moreinfo Hi Yangfl, * URL : http://www.iolang.com Are you sure this URL is correct? Thank you for your work. Here are some comments on your package. * -dfsg: would you please explain what is removed from original source in README.source? * please fix

Bug#886827: Fwd: Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP]

2018-02-15 Thread Lumin
-- Forwarded message -- From: Lumin Date: 15 February 2018 at 14:51 Subject: Re: Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP] To: Félix Sipma Hi, On 15 February 2018 at 09:41, Félix Sipma wrote: > Changelog: is there a problem with being more verbose? I like writing ab

Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]

2018-02-15 Thread Lumin
Hi, On 15 February 2018 at 13:52, Ghislain Vaillant wrote: >> 1. please fix the following copyright issue: > I will update d/copyright accordingly. >> 2. This package failed to build when python2 version of sphinx exists: > > I don't care to be honest. > > It builds fine on a clean chroot with

Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP]

2018-02-15 Thread Lumin
On 15 February 2018 at 15:33, Félix Sipma wrote: > I don't get the harm in having a little more verbose initial changelog, we're > talking about 10 lines there, not a whole book... Anyway, I've just kept the > attribution and a line mentioning the lack of python3 support. > >> OK. You can overri

Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP]

2018-02-21 Thread Lumin
On Fri, 16 Feb 2018 at 01:22 Félix Sipma wrote: > > > This part seems unrelated to auto update functionality. Would you > > mind splitting it to another patch? > > It is a part of the patch: youtube-dl-gui tries to download youtube-dl in > 'youtubedl_path', and then launches "youtubedl_path/youtu

Bug#891922: RFS: you-get/0.4.1040-1 [ITP]

2018-03-02 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "you-get" * Package name: you-get Version : 0.4.1040-1 Upstream Author : Mort Yao * URL : https://github.com/soimort/you-get * License : MIT Se

Bug#891922: RFS: you-get/0.4.1040-1 [ITP]

2018-03-14 Thread Lumin
On Sat, 3 Mar 2018 at 01:46 Alex Mestiashvili wrote: > > > > It would be interesting to see how this program is different from > already existing tools like youtube-dl and cclive. > > Thank you! I have noticed the existence of youtube-dl. However, the user may switch to you-get when youtube-dl

Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP]

2018-03-21 Thread Lumin
Control: owner -1 w...@debian.org Hi, I'm releasing the ownership of this bug since I'm not able to deal with it due to work in real life. Sorry for the inconvenience. On 22 February 2018 at 16:05, Yangfl wrote: > Control: tags -1 - moreinfo > > On Thu, 15 Feb 2018 0

Bug#886827: RFS: youtube-dl-gui/0.4-1 [ITP]

2018-03-25 Thread Lumin
mple way to use python3 version of youtube-dl from python2 version of gui. I'm not sure whether it's possible since I didn't look into the code. Regards, Lumin. On 22 February 2018 at 09:51, Félix Sipma wrote: > On 2018-02-22 03:27+, Lumin wrote: >> I built the package lo

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-25 Thread Lumin
Control: owner -1 ! Control: tag -1 +moreinfo Hi François, Several questions about your package: 1. Why is the package on mentors newer than that on github repo? Could you please keep the packaging repo up-to-date? https://github.com/moleculext/taptempo 2. Where is your public key? no such

Bug#894024: RFS: highwayhash/0~20180209-g14dedec-1

2018-03-25 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180209-g14dedec-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upst

Bug#894071: RFS: gemmlowp/0~20180308-gf59a96b-1 [ITP]

2018-03-25 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "gemmlowp" * Package name: gemmlowp Version : 0~20180308-gf59a96b-1 Upstream Author : google * URL : https://github.com/google/gemmlowp * License

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-03-27 Thread Lumin
Hi François, On 26 March 2018 at 19:56, François Mazen wrote: > I've manually changed the timestamp of the changelog file from the > original repo, and I haven't check that the date was wrong. I can > update the changelog file. I've seen new commits in the repo. Let's assume it's the latest vers

Bug#894197: RFS: highwayhash/0~20180209-g14dedec-2

2018-03-27 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180209-g14dedec-2 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upst

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-04-02 Thread Lumin
Hi François, On 31 March 2018 at 21:59, François Mazen wrote: > > This program is useful to quickly find the tempo of a song. > The idea is to type "taptempo" in a terminal, then hit enter key at > each beat while hearing a song, and display the tempo. > > The targeted people are mainly musicians

Bug#894671: RFS: nltk/3.2.5-2 [ITA] : natural language processing lib, popcon: ~300

2018-04-02 Thread Lumin
Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "nltk" * Package name: nltk Version : 3.2.5-2 Upstream Author : [fill in name and email of upstream] * URL : [f

Bug#894863: RFS: highwayhash/0~20180209-g14dedec-3

2018-04-04 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180209-g14dedec-3 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upst

Bug#893377: RFS: taptempo/1.2.1-1 [ITP]

2018-04-09 Thread Lumin
ept for waiting for the sponsorship. Let's hope Gianfranco will find a time doing the sponsorship. Regards, On 9 April 2018 at 17:43, François Mazen wrote: > Hi Lumin, > > I just want to know if I must do something to go on with the > integration of TapTempo into Debian. > Shou

Bug#895729: RFS: mkl-dnn/0.13~20180406-ga5f6077-1 [ITP] -- math kernel lib for deep neural network

2018-04-15 Thread Lumin
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: mkl-dnn Version : 0.13~20180406-ga5f6077-1 Upstream Author : Intel * URL : https:

Bug#895803: RFS: linuxbrew-wrapper/20180209-1 [RC]

2018-04-16 Thread Lumin
Package: sponsorship-requests Severity: important Notes: I have DM permission to this package. However to fix an RC bug this package needs to go through NEW, moving from the main section to the contrib section. See the RC bug for detail. Dear mentors, I am looking for a sponsor for my packag

Bug#896186: RFS: netctl/1.16-1 [ITP]

2018-04-21 Thread Lumin
Hi Yangfl, Some feedbacks after checking you package: 1. Vcs-* fields are missing, which makes it hard to track the changes. I'd recommend you to put the packaging work on salsa or somewhere alike. 2. lintian overrides: why do you override them? Please add the explanation as comments

Bug#883840: RFS: spglib/1.10.3-1 [ITP]

2018-04-23 Thread Lumin
control: owner -1 ! control: tag -1 +moreinfo Hi Andrius, Thank you for the package. Here are some nitpicking about your package: 1. There seems to be ruby binding available, why isn't it packaged? 2. control: Your -dev package should also depend on the lib package. Depends: ${misc:Depends}

Bug#883840: RFS: spglib/1.10.3-1 [ITP]

2018-04-23 Thread Lumin
On 23 April 2018 at 14:11, Andrius Merkys wrote: >> 6. tests: your autopkgtest testsuite failed: > > I will look into this. It is possible that I invoke the Python tests > incorrectly. Oh, I forgot to tell you that the failure is due to output to stderr. By redirecting the stderr to e.g. stdout,

Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP]

2018-04-24 Thread Lumin
control: owner -1 ! control: tag -1 +moreinfo Hi Yangfl, As discussed previously, the python script for automatically generating the files should be added in the package. -- Best,

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-04-26 Thread Lumin
control: tag -1 +moreinfo control: owner -1 ! Hi Dmitry, Thank you for this package. Here are some problems found in your package: 1. This package misses dependency libconfig-dev 2. Please fix the lintian warnings. e.g. W: odp-doc: privacy-breach-generic 3. debhelper compat level and the

Bug#897238: RFS: intel-mkl/2018.2.199-1 -- Intel Math Kernel Library (Intel MKL)

2018-04-30 Thread Lumin
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "intel-mkl" * Package name: intel-mkl Version : 2018.2.199-1 Upstream Author : Intel * URL : https://software.i

Bug#897238: Re: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-01 Thread Lumin
Hi Sébastien, > - if MKL was not already selected and the user says no, the setting > will be > left untouched (either in automatic or manual mode, depending on the > user > customization) > > - if MKL was already selected and the user says no (e.g. after a > reconfigure), > then MKL will be unse

Bug#897238: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-02 Thread Lumin
ng on system. Apart from all things discussed above, there is upstream confirmation to the ambiguous license declaration in several headers. See [1] The blockers are cleared. I think I'll update the package as proposed, and the copyright information as said in [1] before this weekend. [1] https://github.com/intel/mkl-dnn/issues/206#issuecomment-385772103 Regards, Lumin signature.asc Description: PGP signature

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-05-03 Thread Lumin
at 22:21 Dmitry Eremin-Solenikov wrote: > Package: sponsorship-requests > Followup-For: Bug #896970 > > Hi Lumin, > > I've updated ODP package on mentors.d.n, according to most of your > comments. Could you please review it? > > -- > With best wishes > Dmitry &g

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-05-05 Thread Lumin
On Sat, Apr 28, 2018 at 01:58:26PM +0300, Dmitry Eremin-Solenikov wrote: > > 5. Could you explain why these lines exist? Package libodp-linux-dev > > seems not exist. > > Packages libodp-linux-dev and libodp-linux119 are virtual package, > provided by different implementations of ODP API. We are p

Bug#897238: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-06 Thread Lumin
On Wed, May 02, 2018 at 10:03:38AM -0500, Dirk Eddelbuettel wrote: > > On 2 May 2018 at 14:41, Lumin wrote: > | Seems that things are getting more complicated. Recall that here we'are > | going to prevent users from GPL violation in situations such as this > | one: > |

Bug#897238: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-06 Thread Lumin
Just forgot to CC the RFS bug. - Forwarded message from Lumin - Date: Sun, 6 May 2018 08:29:29 + From: Lumin To: sebast...@debian.org Cc: debian-scie...@lists.debian.org Subject: Re: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS User-Agent: Mutt/1.9.5 (2018-04

Bug#897238: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-11 Thread Lumin
Hi Sébastien, > Using a Pre-Depends here is IMO wrong. Quoting Policy §7.2: Thanks. I didn't notice that when considering ways to avoid corner cases. > I also think that removing the Provides is not a good idea. The alternative is > provided by the package, and that should be made clear in the d

Bug#897238: RFS: intel-mkl/2018.2.199-1 -- ready for review

2018-05-12 Thread Lumin
P.S. Don't perform source-only upload since this is non-free blob. A source+amd64+i386 upload is needed. Thanks in advance. :-) Best, lumin signature.asc Description: PGP signature

Bug#898484: [cdlumin...@gmail.com: RFS: nltk/3.3.0]

2018-05-12 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nltk": * Package name: nltk Version : 3.3.0 Upstream Author : NLTK project * URL : https://www.nltk.org/ * License : Apache-2.0 Section : science

Bug#898975: RFS: lua-moses/1.6.1+git20170613-2

2018-05-17 Thread Lumin
Package: sponsorship-requests Severity: normal X-Debbugs-CC: ti...@debian.org Dear mentors, I am looking for a sponsor for my package "lua-moses": * Package name: lua-moses Version : 1.6.1+git20170613-2 Upstream Author : * URL : * License : MIT Section

Bug#897238: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

2018-05-19 Thread Lumin
On Fri, May 18, 2018 at 11:49:05PM +0800, Drew Parsons wrote: > > I wonder if the simplest solution is to just have > intel-mkl Depends: libblas. i.e. use policy to simply prevent a sole > mkl installation. > > That way, the mkl alternative will always have a free BLAS to press > it's preferen

Bug#896186: RFS: netctl/1.16-1 [ITP]

2018-05-20 Thread Lumin
control: tag -1 +moreinfo On Fri, May 04, 2018 at 10:37:27AM +0800, Yangfl wrote: > control: tag -1 - moreinfo > > Reuploaded. Please fix your packaging repo first: https://salsa.debian.org/chinese-team/netctl/network/master The stuff in the master branch is identical to the upstream branch.

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-05-24 Thread Lumin
On Wed, May 23, 2018 at 07:50:57PM +0300, Dmitry Eremin-Solenikov wrote: > Hello, > > I have updated odp & odp-dpdk packages on mentors.d.n. Please file another RFS bug for the odp-dpdk package since it is a different source. > 2018-05-06 3:56 GMT+03:00 Dmitry Eremin-Solenikov : > > I will make

Bug#896186: RFS: netctl/1.16-1 [ITP]

2018-05-26 Thread Lumin
Hi Yangfl, On Tue, May 22, 2018 at 08:43:07PM +0800, Yangfl wrote: > 2018-05-20 19:50 GMT+08:00 Lumin : > > control: tag -1 +moreinfo > > > > On Fri, May 04, 2018 at 10:37:27AM +0800, Yangfl wrote: > >> control: tag -1 - moreinfo > >> > >> Reupload

Bug#900175: RFS: nltk/3.3.0-1

2018-05-26 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nltk" * Package name: nltk Version : 3.3.0-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License

Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP]

2018-05-30 Thread Lumin
control: tags -1 +morefino On Fri, Feb 23, 2018 at 12:05:41AM +0800, Yangfl wrote: > > d/copyright should have provided a list of removed files (see Files-Excluded). > > By the way, I have made a PR to upstream to remove ConvertUTF and it > has accepted. The next release will not affected by this

Bug#896186: Info received (Bug#896186: RFS: netctl/1.16-1 [ITP])

2018-06-01 Thread Lumin
control: noowner -1 I quit reviewing this RFS, because frequent and incooperative force-{push,squash}'es drive me crazy, which makes it hard to track the changes. Any mentors interested in this package can take it over. I guess the package was nearly in shape, and the remaining reviewing work sh

Bug#888859: Info received (Bug#888859: RFS: iolang/2017.09.06+dfsg-1 [ITP])

2018-06-01 Thread Lumin
control: noowner -1 I'm recently too busy to review and test such a complex package, hence dropping it. Currently the package can be successfully built.

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-06-01 Thread Lumin
On Wed, May 30, 2018 at 01:40:48PM +0300, Dmitry Eremin-Solenikov wrote: > > 1. README.Debian > >"Library packages should contain libodp-linux.so.FOO" > >It should be "libodp-linux.so.SOVER", which is more precise. > > Hmm. I have checked buster package lists. Only blas/lapack packages > u

Bug#896970: Info received (Bug#896970: RFS: odp/1.19.0.0-1 [ITP])

2018-06-01 Thread Lumin
Forgot to check the copyright ... The copyright looks incomplete. A simple search on the source tree would reveal many non-Linaro copyright holders: grep -ri copyright | grep -vi linaro | grep -i copyright The package will be rejected by ftp-master if we don't fix the copyright.

Bug#896970: RFS: odp/1.19.0.0-1 [ITP]

2018-06-01 Thread Lumin
On Sat, Jun 02, 2018 at 03:24:07AM +, Lumin wrote: > Please fix the aforementioned problems. Hopefully we'll have the last > round of check next time. Thank you for working on this. > > [1] > http://debomatic-amd64.debian.net/distribution#unstable/odp/1.19.0.1-1/buildlog

Bug#900407: RFS: odp-dpdk/1.19.0.0-1 [ITP]

2018-06-01 Thread Lumin
control: tag -1 +moreinfo control: owner -1 ! Hi Dmitry, Thank you for the package. It looks good except for several flaws: 1. error in postrm script, which causes error on removal update-alternatives: error: alternative name (/usr/lib/x86_64-linux-gnu/libodp-linux.so.119) must not contain '

Bug#900407: Info received (RFS: odp-dpdk/1.19.0.0-1 [ITP])

2018-06-01 Thread Lumin
Use this command to generate a some copyright template: licensecheck --deb-machine -r .

Bug#900617: RFS: ujson/1.35-3 [ITA]

2018-06-01 Thread Lumin
Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-pyt...@lists.debian.org, mo...@debian.org Dear mentors, I am looking for a sponsor for my package "ujson" * Package name: ujson Version : 1.35-3 Upstream Author : [fill in name and email of upstream] * UR

Mysterious autopkgtest tests of ujson package

2018-06-02 Thread Lumin
Hello mentors, I'm adopting the ujson package[1][2]. Currently there is no autopkgtest control file under the debian directory[3], but ci.d.o, to my surprise, is running autopkgtest[4] on this package. As far as I know, tests are defined in debian/tests/control when the tester is autopkgtest. No

Bug#900626: RFS: gemmlowp/0.0~git20180416.38ebac7-1

2018-06-02 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "gemmlowp" * Package name: gemmlowp Version : 0.0~git20180416.38ebac7-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstre

Re: Re: Mysterious autopkgtest tests of ujson package

2018-06-02 Thread Lumin
> > autodep8: /usr/share/autodep8/support/python > > BTW: codesearch.debian.net is a good place to find out this sort of thing. > Ah, here it is. Thanks!

Bug#900617: RFS: ujson/1.35-3 [ITA]

2018-06-02 Thread Lumin
On Sat, Jun 02, 2018 at 12:02:17PM -0400, Sandro Tosi wrote: > > + Move Sandro Tosi to Uploaders. > > please remove me from uploaders too, thanks! Re-uploaded the package. https://mentors.debian.net/debian/pool/main/u/ujson/ujson_1.35-3.dsc changes: ujson (1.35-3) unstable; urgency=mediu

Bug#900944: RFS: python-cymem/1.31.2-1 [ITP]

2018-06-06 Thread Lumin
Package: sponsorship-requests Severity: wishlist Control: block 900941 by -1 Dear mentors, I am looking for a sponsor for my package "python-cymem" * Package name: python-cymem Version : 1.31.2-1 Upstream Author : [fill in name and email of upstream] * URL : [

Bug#900948: RFS: python-preshed/1.0.0-1 [ITP, one of spaCy deps]

2018-06-06 Thread Lumin
Package: sponsorship-requests Severity: wishlist Control: block 900945 by -1 Control: block -1 by 900944 Dear mentors, I am looking for a sponsor for my package "python-preshed" * Package name: python-preshed Version : 1.0.0-1 Upstream Author : [fill in name and email of u

Bug#900978: RFS: python-murmurhash/0.28.0-1 [ITP, spaCy deps]

2018-06-07 Thread Lumin
Package: sponsorship-requests Severity: wishlist Control: blocks 900977 by -1 Dear mentors, I am looking for a sponsor for my package "python-murmurhash" * Package name: python-murmurhash Version : 0.28.0-1 Upstream Author : [fill in name and email of upstream] * URL

Bug#901204: RFS: python-plac/0.9.6-1 [ITP, spaCy deps]

2018-06-10 Thread Lumin
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-plac" plac is one of spaCy dependencies: [✓] cython>=0.24,<0.28.0 [✓] pathlib [✓] numpy>=1.7 [*] cymem>=1.30,<1.32 # ITP/RFS [*] preshed>=1.0.0,<2.

Bug#901235: RFS: python-thinc/6.11.2-1 [ITP, spaCy deps]

2018-06-10 Thread Lumin
Package: sponsorship-requests Severity: wishlist Control: block 901231 by -1 Dear mentors, I am looking for a sponsor for my package "python-thinc" * Package name: python-thinc Version : 6.11.2-1 Upstream Author : github.com/explosion * URL : https://github.co

Bug#901304: RFS: python-cytoolz/0.9.0.1-1 [ITP, spaCy deps]

2018-06-11 Thread Lumin
Package: sponsorship-requests Severity: wishlist Control: block 882725 by -1 Dear mentors, I am looking for a sponsor for my package "python-cytoolz" * Package name: python-cytoolz Version : 0.9.0.1-1 Upstream Author : Erik Welch * URL : https://github.com/pyt

Bug#902577: RFS: highwayhash/0~20180209-g14dedec-4

2018-06-27 Thread Lumin
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "highwayhash" * Package name: highwayhash Version : 0~20180209-g14dedec-4 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upst

Bug#901958: RFS: lsmount/0.2.2-1 [ITP] -- output /proc/mounts formatted

2018-06-29 Thread Lumin
Hi Andreas Schwarz, > I am looking for a sponsor for my package "lsmount" Thank you for this package. I'm not sponsoring it but here are some comments: 1. debian/copyright: OK 2. debian/rules: MINOR The debhelper compat level is set to 11. That means --parallel is default. So you don't h

<    1   2   3   >