On Tue, 2016-12-27 at 22:47 +0100, Adam Borowski wrote:
> I don't see why you would do that...?
It's my bad -- I misunderstood your comments.
> What I meant is that you install a lot of cruft that doesn't appear to be
> user docs at all
I agree with that. I reverted the package split and moved t
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 lin
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: https://lists.debian.org/1423134462.2546.1
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 (
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 listmas...@lists.debia
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
* URL :
http://anonscm.debian.org/cgit/chinese/fortune-zh.git
* License
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 : https://github.com/Xfe
Hi mentors,
Initially I intend to package cv ITP : [1]
* Description : cv - Coreutils (progress) Viewer
Then I checked the packages.d.o avoiding package name conflict [2],
there is indeed no package named "cv" for any suites.
However immediate after I filed the RFS againt my ITP
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 abou
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
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
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:
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
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
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) (
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 )
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
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
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
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
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
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
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.
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
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:
~/hdd/debia
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
* URL : https://github.com/Xfennec/progress
* Licens
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
.com/Homebrew/linuxbrew/issues/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
, GPL-3+ means you can't
> redistribute
> as BSD-2-clause without an explicit written permission, even if I didn't
> check right now
> the above, and IANAL)
[...]
Thank you Gianfranco Costamagna for reviewing this package!
:-)
--
.''`.
x" will put the x installed files?
Well, here is an example which 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/
gt;
> The problem here is that using non-standard locations is source of troubles,
> but I see you/brew fixed them
> in the proper way (at least the same 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
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
t; debian/copyright, please rethink 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/
--
.''`.
ors.debian.net/debian/pool/main/l/linuxbrew-wrapper/linuxbrew-wrapper_20150804-1.dsc
Changes since last upload:
* dch -r unstable
* bump debian copyright to bsd-2-clause
* update manpage
Thanks.
--
.''`. Lumin
: :' :
MANPATH,INFOPATH environment to utilize software
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 co
updated.
Since that install script in relatively stable
(not yet changed since Apr 24)
I don't mind to manually update check and update it.
However I think automate the process will be better
for adopters. I'm about to add related things
(build it on my laptop is very slow ...)
Thank you.
--
.''`. Lumin
: :' :
`. `'
`-638B C75E C1E5 C589 067E 35DE 6264 5EB3 5F68 6A8A
es my 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
er caffe-cpu 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 depen
ckage=python-caffe-cuda \
121 -- \
122 -xlibcaffe-cpu0
123 endif
Thank you all.
On Thu, 2015-09-03 at 07:10 +0000, lumin wrote:
> Hi mentors,
>
> I'm packaging caffe, which is nearly done.
>
> http://mentors.debian.net/package/caffe
>
> http://mentors.d
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 : 0.~rc2+git20150902+e8e660d3
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.
http://mentors.debian.net/deb
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.
> Multi-Arc
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...
Reduc
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.
Yes,
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 x8
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
>
>
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 fro
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 : https://github.com/Xfennec/pr
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
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 : https://github.com/Homebrew/linuxb
Control: retitle 799565 RFS: linuxbrew-wrapper/20150804-2 -- missing package
manager for linux
signature.asc
Description: This is a digitally signed message part
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:
http://mentors.debian.net/pa
mment caffe-cuda out,
letting caffe-cpu work first, and wait for 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/CDLuminat
e.
* d/rules: Bump version as new version is imported.
* Update "d/*.install".
Regards,
lumin
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?
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
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 kn
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
On Sat, 2017-01-07 at 07:52 +, Gianfranco Costamagna wrote:
>
> Lumin, can you please check caffe*?
I think caffe-* are safe. Since searching h5py in the upstream
code with ack yields the following result (the result is
stripped by me):
```
$ ack -i h5py
examples/brewing-logreg.ip
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: la...@debian.org
X-Debbugs-CC: 073p...@gmail.com
Dear mentors,
I am looking for a sponsor for my package "fortune-zh"
* Package name: fortune-zh
Version : 2.1
Upstream Author : myself
* URL : [fill i
On Mon, 2017-01-09 at 17:38 +, Chris Lamb wrote:
> lumin wrote:
>
> > Trying to upload package to ftp-master (ftp.upload.debian.org)
> Checking signature on .changes
> > Uploading to ftp-master (via ftp to ftp.upload.debian.org):
> Uploading fortune-zh_2.1_all.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "farmhash"
* Package name: farmhash
Version : 0~20161014-g92e897b-2
Upstream Author : google
* URL : https://github.com/google/farmhash
* License :
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "lua-torch-cutorch"
* Package name: lua-torch-cutorch
Version : 0~20170202-g64536bc-1
Upstream Author : torch developers
* URL : https://github.com/torch/c
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "fortune-zh"
* Package name: fortune-zh
Version : 2.2
Upstream Author : myself
* URL : https://anonscm.debian.org/cgit/chinese/fortune-zh.git
* License
> Unpacking fortune-zh (2.2) over (2.1) ...
> Errors were encountered while processing:
> /tmp/fortunes-zh_2.2_all.deb
>
>
> G.
--
Best,
Lumin
Hi, uploaded new source package to mentors.
With changes:
fortunes-zh: Breaks: fortune-zh (<= 2.1)
this works for me since several upgrade/downgrade tests are successful.
Does it work for you?
On 10 April 2017 at 07:35, Lumin wrote:
> Oops, the file '/usr/games/fortune-zh
d from "fortune-zh" to
>>"fortunes-zh".
>>Should I add conflict: fortune-zh (<= 2.1) for binary package
>>fortunes-zh to fix this?
>
> https://wiki.debian.org/PackageTransitionG.
--
Best,
Lumin
Control: tag -1 -moreinfo
> I cannot sponsor the upload, just a few comments after reviewing your package.
>
> I see some activities on your PR on github:
> - https://github.com/google/gemmlowp/pull/63
> So you're going to update the CMakeLists.txt based on upstream's feedback?
I can help upstre
The latest package is uploaded to mentors:
https://mentors.debian.net/debian/pool/main/g/gemmlowp/gemmlowp_0~20170407-g719389f-1.dsc
debomatic test passed:
http://debomatic-amd64.debian.net/distribution#experimental/gemmlowp/0~20170407-g719389f-1/buildlog
On 14 April 2017 at 04:43, Lumin wrote
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "highwayhash"
* Package name: highwayhash
Version : 0~20170419-g1f4a24f-1
Upstream Author : google
* URL : https://github.com/google/highwayhash
* License
test binaries (except for the
"benchmark").
Is it acceptable now?
:-)
On 20 April 2017 at 16:08, Adam Borowski wrote:
> On Thu, Apr 20, 2017 at 10:35:41AM +, Lumin wrote:
>> I am looking for a sponsor for my package "highwayhash"
>>
>> * Packa
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
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
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:
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
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
t symbol files
>
> one single file should be enough for every arch.
>
> G.
--
Best,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
-- 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
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
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
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
101 - 200 of 279 matches
Mail list logo
