Re: Re: [RFC] How to review RFS package

2017-02-08 Thread James Clarke
> On 8 Feb 2017, at 14:49, Gianfranco Costamagna > wrote: >>> apt build-dep (dsc-file) to build-dependencies> > >> I remember "apt build-dep " is only for package already > >> exists in archive. > > > > when the argument is a dsc file, apt parses the dependency

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

2016-05-18 Thread James Clarke
> On 18 May 2016, at 14:15, James Clarke <jrt...@jrtc27.com> wrote: > >> On 18 May 2016, at 13:44, lumin <cdlumin...@gmail.com> wrote: >> * add debian/upstream/metadata , but lintian says >> >>> W: caffe source: upstream-metadata-yaml-invalid >>

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

2016-05-18 Thread James Clarke
> On 18 May 2016, at 13:44, lumin wrote: > * add debian/upstream/metadata , but lintian says > >> W: caffe source: upstream-metadata-yaml-invalid > > Is there anything wrong with this file? I have no idea > > ``` > Homepage: http://caffe.berkeleyvision.org/ > Name: Caffe

Bug#787861: review: polyml

2015-10-17 Thread James Clarke
Hi Gianfranco, > I sponsored the package Thank you again for all your help. > (BTW I was intending to subscribe to debian-science, but also debian-devel is > nice to be subscribed) I have subscribed to debian-science as well. > However, I would appreciate a fix for the following missing

Bug#787861: review: polyml

2015-10-17 Thread James Clarke
Hi Gianfranco, >> I have uploaded 5.5.2-2 to mentors (and updated my git repository) enabling >> all hardening flags. I also realised that the new polyc shell script >> requires gcc and >libffi-dev to produce standalone executables, so I have >> added those as dependencies for polyml. > >

Bug#787861: review: polyml

2015-10-15 Thread James Clarke
Hi Gianfranco, > On 15 Oct 2015, at 10:56, Gianfranco Costamagna > wrote: > > Hi James > > >> I have uploaded 5.5.2-1~rc2 to mentors. > > > > please call it 5.5.2-1 and nothing more :) > you can push the same version many times on mentors with no problems.

Bug#787861: review: polyml

2015-10-15 Thread James Clarke
bian-science/packages/polyml.git to http://anonscm.debian.org/cgit/users/jrtc27-guest/polyml.git/ and pushed all my changes there. Thanks, James Clarke signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#787861: review: polyml

2015-10-14 Thread James Clarke
Hi Gianfranco, I have uploaded 5.5.2-1~rc2 to mentors. 1) Do I need to send a separate email to this then? I also filed #801793 for a transition, but that has already been closed as unnecessary since there are no rdeps. 2) Added 6) The compiler is indeed forcing your code to be linked against

Bug#787861: review: polyml

2015-10-13 Thread James Clarke
; 9) licensecheck * -r shows many licenses not LGPL-2.1+ > 10) debian/menu please remove (menu is deprecated since a month or two) > 11) > usr/share/man/man1/poly.1* > usr/share/man/man1/polyc.1* > usr/share/man/man1/polyimport.1* > > > > they belong to dh_installmanpage

Bug#787861: review: polyml

2015-10-07 Thread James Clarke
Hi, I believe I have addressed the changes you mentioned in http://mentors.debian.net/debian/pool/main/p/polyml/polyml_5.5.2-0.2.dsc, and would be grateful if you could please review it. Thanks, James > On 6 Oct 2015, at 10:54, James Clarke <jrt...@jrtc27.com> wrote: > >

Bug#787861: review: polyml

2015-10-06 Thread James Clarke
Firstly sorry for not replying, I hadn’t subscribed to the bug so I was never emailed a copy of your message. I figured it wasn’t really common to have NMUs like this, but given the fact that the package is not orphaned but its maintainers have not replied to bug reports, I thought this was

Bug#787861: RFS: polyml/5.5.2-0.1 [NMU]

2015-06-05 Thread James Clarke
, so I have packaged it myself to hopefully move things along. Regards, James Clarke -- 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/c847a3f3-7ad6-492e-9def-6411c2edb