Bug#829543: Subject: RFS: linkchecker/9.3-2 [QA]

2016-07-04 Thread David Jones
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "linkchecker"

 * Package name: linkchecker
   Version : 9.3-2
   Upstream Author : Bastian Kleineidam 
 * URL : https://wummel.github.io/linkchecker/
 * License : GPL-2+
   Section : web

It builds those binary packages:

  linkchecker - check websites and HTML documents for broken links
  linkchecker-gui - check websites and HTML documents for broken links
(GUI client)
  linkchecker-web - check websites and HTML documents for broken links
(web client)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/linkchecker


Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/linkchecker/linkchecker_9.3-2.dsc

More information about linkchecker can be obtained from
https://wummel.github.io/linkchecker/.

Changes since the last upload:

  * QA upload.
  * Set maintainer to QA Group
  * Add dh-python to build-deps
  * Put bash completions in correct location
  * Removed redundant menu file
  * Updated watch file
  * Dropped build-dep on hardening-flags
  * Dropped unneeded versions on deps
  * Bumped standards version to 3.9.8
  * Patch from upstream to fix Python version check (Closes: #826027)


Regards,
   David William Richmond Jones


Re: managing patches

2016-07-04 Thread Christian Kastner
On 2016-07-04 06:23, Herminio Hernandez Jr wrote:
> I have a question regarding managing patches. I am wondering is there
> a way to merge multiple patches into one or is there way to rollback
> from a patch?

I'm not quite sure what you mean by "rolling" back from a patch (that's
probably something for a Vcs, or quilt(1)), but regarding the merge: it
sounds as if you're looking for combinediff(1), from package patchutils.

If you're using git, you might want to look at the "git rebase -i" and
"git merge --squash" commands.

If you're using quilt, "quilt fold" might also be helpful.

Regards,
Christian




Bug#829568: RFS: git-remote-gcrypt/1.0.0-1 -- encrypted git repositories

2016-07-04 Thread Sean Whitton
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a new release of git-remote-gcrypt.

Upstream asked for a new maintainer last year (although the GitHub issue
in which he made that request now 404s), and Joey Hess doesn't want to
be considered upstream, so I'm taking on that role myself.

* Package name: git-remote-gcrypt
  Version : 1.0.0-1
  Upstream Author : engla, Joey Hess, Sean Whitton and contributors
* URL : https://git.spwhitton.name/git-remote-gcrypt
* License : GPL-2+
  Section : vcs

Changes since the last upload:

  Upstream:
  * Taking over as upstream maintainer.
  * Remove notice about repository format potentially changing.
  * Implement gcrypt.gpg-args git config setting (Closes: #771011).
  * Respect git config gpg.program if configured.
Thanks Christian Amsüss.  (Closes: #827943)
  * Don't reset the remote ID when a gcrypt remote is not available.
Thanks Sebastian Reuße.  (Closes: #827943)
  * Suppress bogus warning about keyid matching multiple fingerprints.
Based on work by Raphaël Droz.
Closes https://github.com/joeyh/git-remote-gcrypt/pull/2
  * Add "Note to users of GnuPG version 2" section to README.rst.
See https://github.com/joeyh/git-remote-gcrypt/pull/1

  Debian packaging:
  * Drop patch containing changes by Joey Hess: incorporated in release.
- Update d/copyright accordingly.
  * Patch README.rst to remove references to installation.
  * Add d/links to avoid duplicate changelogs Lintian warning.
  * Drop Lintian override of no-upstream-changelog.
  * Update URIs in old changelog entries.
  * Add a comment to d/source/lintian-overrides.
  * Bump standards version to 3.9.8 (no changes required).

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/g/git-remote-gcrypt/git-remote-gcrypt_1.0.0-1.dsc

Or build it with gbp:

gbp clone --pristine-tar https://git.spwhitton.name/git-remote-gcrypt
git checkout debian/1.0.0-1
git verify-tag debian/1.0.0-1 # if you have my key
gbp buildpackage

Thanks.

-- 
Sean Whitton



Bug#829571: RFS: gmp-ecm/7.0.3+ds-1 -- Factor integers using the Elliptic Curve Method

2016-07-04 Thread Jerome Benoit
Package: sponsorship-requests
Severity: normal

Dear Sponsors,

I am looking for sponsorship for the Debian package gmp-ecm [1], a 
mathematical
library that Factor[s] integers using the Elliptic Curve Method'. This 
package
brings the lasted patch release of [gmp-]ecm.

Thanks in advance,
Jerome

[1] https://packages.qa.debian.org/g/gmp-ecm.html

-- System Information:
Debian Release: Jessie*
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)



Bug#829286: RFS: newlisp/10.7.0-2

2016-07-04 Thread Gianfranco Costamagna
Hi,



>Still nothing.  I had read the page, but it mentions the format of the
>.commands file, and not dcut's CLI options.  I also tried specifying the
>options in a different order, but I get the same error.


dcut ftp-master reschedule -d 0  -f newlisp_10.7.0-2_source.changes

this works for dput-ng I think

BTW if you can't check-do that, you might want to add -k KEYID
or ask me to reschedule it :)

G.



Bug#829605: RFS: aspell-sk/2.02-0-0.1 [RC, NMU]

2016-07-04 Thread Pali Rohár
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "aspell-sk"

 * Package name: aspell-sk
   Version : 2.02-0-0.1
   Upstream Author : Zdenko Podobný 
 * URL : http://www.sk-spell.sk.cx/aspell-sk
 * License : GPL
   Section : text

It builds those binary packages:

  aspell-sk  - Slovak dictionary for GNU Aspell

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/aspell-sk


Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/a/aspell-sk/aspell-sk_2.02-0-0.1.dsc

Changes since the last upload:

  * Non-maintainer upload.
  * New upstream release (Closes: #603719).
  * Use compat level 9 (Closes: #817360).
  * Add Homepage and update Standards-Version.
  * Fix Coding-System in aspell-sk.info-aspell.


Regards,
 Pali Rohár


signature.asc
Description: This is a digitally signed message part.


Bug#814680: marked as done (RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover)

2016-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 Jul 2016 16:30:16 +
with message-id 
and subject line closing RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover
has caused the Debian Bug report #814680,
regarding RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
814680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "stp"

* Package name: stp
  Version : 2.1.2+dfsg-1
  Upstream Author : STP developers
* URL : https://stp.github.io/
* License : Expat and others
  Section : science

It builds those binary packages:

  python-stp - Simple theorem prover library bindgings for Python
  stp - Simple theorem prover

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/stp


Alternatively, one can download the package with dget using this
command:

  dget -x http://mentors.debian.net/debian/pool/main/s/stp/stp_2.1.2
+dfsg-1.dsc

More information about STP can be obtained from https://stp.github.io/.

Changes since the last upload:

  - new upstream release
  - added copyright for the OutputCheck archive per Thorsten Alteholz's
instructions (ftp-master)


-- 
Kind regards,
Marko Dimjašević
https://dimjasevic.net/marko




signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Package stp has been removed from mentors.--- End Message ---


Bug#822613: RFS: dynamic-graph/3.0.0-1

2016-07-04 Thread Rohan Budhiraja

Hi Gianfranco


found information on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736360  which seems to
suggest the problem was still contentious two years ago. Should I keep
overriding this warning?

I suggest to leave things as is

Ok



1) apt install check-all-the-things

codespell --quiet-level=3
^^ something that you might want to fix or report/ask upstream


Done. Except for the source from Mathjax consortium, the rest is corrected.




2) grep copyright  . -Ri

many missing people


Added as the copyright.




License: I know the license text can be just a link to common-licenses, but I 
still prefer
some brief explanation

https://codesearch.debian.net/results/License%3A%20LGPL-3/page_0

"the License, or (at your option) any later version."

3) missing a +, it seems an LGPL-3+ license


I like something like this


License: LGPL-3+
This package is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 3 of the License, or (at your option) any later version.
.
This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Lesser General Public License for more details.
.
You should have received a copy of the GNU General Public License
along with this program. If not, see.
.
On Debian systems, the complete text of the GNU Lesser General
Public License can be found in "/usr/share/common-licenses/LGPL-3".



Done.


5) trigger:
activate-noawait ldconfig


why?


lintian doesn't like ldconfig in maintenance scripts. So it gives out 
this error

https://lintian.debian.org/tags/maintscript-calls-ldconfig.html



6)

override_dh_makeshlibs:
dh_makeshlibs --exclude=lib/plugin --noscripts

override_dh_shlibdeps:
dh_shlibdeps --exclude=lib/plugin

why?
The plugin exclude was because the plugin libraries had no soversion. 
but that is now corrected.

The noscripts part was to avoid the lintian warning listed above


8)

please check dpkg-buildpackage -A
and dpkg-buildpackage -B
if they run cleanly
(in clean pbuilder/sbuild unstable environments)

They run cleanly in pdebuild


4) symbols mismatches:
http://debomatic-amd64.debian.net/distribution#unstable/dynamic-graph/3.0.0-1/buildlog

http://debomatic-i386.debian.net/distribution#unstable/dynamic-graph/3.0.0-1/buildlog

and I expect some more breakages on arm* and other Debian architectures.


dpkg-gensymbols now looks happy on my system (i386),  but I don't know 
what will happen on others. Is there any way for newbies like me to 
access these buildfarms?




it should be all for now

I am getting a new lintian error (+2 pedantic ones) about MathJax. This 
seems to be on the todo for lintian 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799861). Should I 
keep ignoring this as well?


Best regards,
Rohan



Blocked bugs

2016-07-04 Thread Herminio Hernandez Jr.
Mentors,

I placed an ITP for a package call mbpfan. I then made sure my package had 
lintian errors and updated the change log noting that packaged fixes the ITP 
bug and uploaded to the debian-mentors site. I then placed an RFS bug for the 
package. This morning I received a notice that my ITP bug is blocked by my RFS 
bug. Did I forget something? 

Thanks
Herminio

Sent from my iPhone


Bug#829286: RFS: newlisp/10.7.0-2

2016-07-04 Thread Sergio Durigan Junior
On Monday, July 04 2016, Gianfranco Costamagna wrote:

>>Still nothing.  I had read the page, but it mentions the format of the
>>.commands file, and not dcut's CLI options.  I also tried specifying the
>>options in a different order, but I get the same error.
>
>
> dcut ftp-master reschedule -d 0  -f newlisp_10.7.0-2_source.changes
>
> this works for dput-ng I think

Alright, after installing dput-ng (I had the "normal" dput package
installed) it works.  And I can confirm that the commands were accepted
and that the package apparently has moved to the 0-day queue.  Indeed,
it seems like a bug...

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Re: Blocked bugs

2016-07-04 Thread Christian Seiler
On 07/04/2016 09:13 PM, Herminio Hernandez Jr.  wrote:
> I placed an ITP for a package call mbpfan. I then made sure my
> package had lintian errors and updated the change log noting that
> packaged fixes the ITP bug and uploaded to the debian-mentors site. I
> then placed an RFS bug for the package. This morning I received a
> notice that my ITP bug is blocked by my RFS bug. Did I forget
> something?

No, that's perfectly fine. Bug A blocks bug B just means that bug
B can't be fixed without bug A being fixed first. In case of RFS
bugs, they are fixed when the upload occurs, while the bugs that
the package itself fixes are fixed once the package gets accepted
(after the upload).

So the RFS bug blocking the ITP is actually correct. In your case,
someone was so nice to add the information that the RFS bug blocks
the ITP bug for you.

Hence: everything is fine, you don't need to do anything further
until someone gets a chance to review your package.

Regards,
Christian



Re: Blocked bugs

2016-07-04 Thread Herminio Hernandez Jr.
Thanks!

Sent from my iPhone

> On Jul 4, 2016, at 12:25 PM, Christian Seiler  wrote:
> 
>> On 07/04/2016 09:13 PM, Herminio Hernandez Jr.  wrote:
>> I placed an ITP for a package call mbpfan. I then made sure my
>> package had lintian errors and updated the change log noting that
>> packaged fixes the ITP bug and uploaded to the debian-mentors site. I
>> then placed an RFS bug for the package. This morning I received a
>> notice that my ITP bug is blocked by my RFS bug. Did I forget
>> something?
> 
> No, that's perfectly fine. Bug A blocks bug B just means that bug
> B can't be fixed without bug A being fixed first. In case of RFS
> bugs, they are fixed when the upload occurs, while the bugs that
> the package itself fixes are fixed once the package gets accepted
> (after the upload).
> 
> So the RFS bug blocking the ITP is actually correct. In your case,
> someone was so nice to add the information that the RFS bug blocks
> the ITP bug for you.
> 
> Hence: everything is fine, you don't need to do anything further
> until someone gets a chance to review your package.
> 
> Regards,
> Christian



Re: Blocked bugs

2016-07-04 Thread Mattia Rizzolo
On Mon, Jul 04, 2016 at 09:25:02PM +0200, Christian Seiler wrote:
> So the RFS bug blocking the ITP is actually correct. In your case,
> someone was so nice to add the information that the RFS bug blocks
> the ITP bug for you.

FTR, that's an automated thing by bartm.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#823663: marked as done (RFS: tio/1.20-1 [ITP] -- The simple TTY terminal I/O application)

2016-07-04 Thread Debian Bug Tracking System
Your message dated Mon, 4 Jul 2016 23:32:02 +0200
with message-id <20160704213202.ga1...@jwilk.net>
and subject line Re: Bug#823663: RFS: tio/1.6-1 [ITP] -- The simple TTY 
terminal I/O application
has caused the Debian Bug report #823663,
regarding RFS: tio/1.20-1 [ITP] -- The simple TTY terminal I/O application
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
823663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "tie":

 Package name: tio
 Version : 1.6-1
 Upstream Author : Martin Lund 
 URL : http://tio.github.io/
 License : GPL-2+
 Section : comm

 It builds those binary packages:

 tio - Simple TTY terminal I/O application

 To access further information about this package, please visit the following 
URL:

 https://mentors.debian.net/package/tio

 Alternatively, one can download the package with dget using this command:

 dget -x https://mentors.debian.net/debian/pool/main/t/tio/tio_1.6-1.dsc

 More information about tio can be obtained from http://tio.github.io/.

Cheers,
sur5r
--- End Message ---
--- Begin Message ---

54f67af9cd6e uploaded.

--
Jakub Wilk--- End Message ---


Bug#829568: closing 829568

2016-07-04 Thread Sean Whitton
close 829568 
thanks
-- 
Sean Whitton



Bug#829605: RFS: aspell-sk/2.02-0-0.1 [RC, NMU]

2016-07-04 Thread Jakub Wilk

Control: owner -1 !
Control: tags -1 + moreinfo

* Pali Rohár , 2016-07-04, 18:13:

dget -x 
https://mentors.debian.net/debian/pool/main/a/aspell-sk/aspell-sk_2.02-0-0.1.dsc

Changes since the last upload:

 * Non-maintainer upload.
 * New upstream release (Closes: #603719).


debian/copyright says that the package "was downloaded from 
ftp://ftp.gnu.org/gnu/aspell/dict/sk/";, but there is no 2.02-0 at this 
location.


BTW, what's the difference between 2.01-2 and 2.02-0? There's no entry 
for the latter version in doc/CHANGELOG. :-\


Also, the copyright file says that the package is under GPL, whereas 
this new version is tri-licensed: LGPLv2.1, GPLv2, MPLv1.1.



 * Use compat level 9 (Closes: #817360).


Did you need to do any packaging changes to bump compat?


 * Add Homepage and update Standards-Version.


Why are these two in a single item? They seem unrelated to me.

Did you need to do any packaging changes to update S-V?
I wouldn't recommend updating S-V in an NMU.

Addition of debian/watch is not documented in the changelog.

You changed source format to "3.0 (quilt)", but this change is not 
documented either. Also, changing source format is not suitable for an 
NMU, unless you have a very good reason.


--
Jakub Wilk



Bug#829648: RFS: twinkle/1:1.9.0+git20160520.0.be8b8df+dfsg-1~bpo8+1 -- Voice over Internet Protocol (VoIP) SIP

2016-07-04 Thread Peter Colberg
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor to upload the package "twinkle" to
jessie-backports. I have been added to the backports ACL for
subsequent maintenance.

git clone https://anonscm.debian.org/git/pkg-voip/twinkle.git
cd twinkle && pristine-tar checkout 
../twinkle_1.9.0+git20160520.0.be8b8df+dfsg.orig.tar.xz
git checkout debian/jessie-backports

Please include all changes since the last stable version [1] in your upload:

sbuild -j4 --dist=jessie --debbuildopts=-v1:1.4.2-2 --force-orig-source

[1] https://archive.debian.net/squeeze/twinkle

For historic background, twinkle had been removed from testing before
the release of wheezy due to only building with Qt3. For a while the
console client with limited functionality was available in unstable.
A year ago twinkle was ported to Qt5 by a new upstream maintainer.

Regards,
Peter


signature.asc
Description: PGP signature


Bug#829653: RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP]

2016-07-04 Thread Lumin
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: costamagnagianfra...@yahoo.it
​, ghisv...@gmail.com​


Dear mentors,

​  This cuda version is basically synced with the CPU version in
  packaging.​


  I am looking for a sponsor for my package "caffe-contrib"

 * Package name: caffe-contrib
   Version : 1.0.0~rc3-1
   Upstream Author : Berkeley vision and learning center
 * URL : github.com/bvlc/caffe
 * License : BSD-2-Clause
   Section : science

  It builds those binary packages:

caffe-cuda - Fast, open framework for Deep Learning (Meta)
 caffe-tools-cuda - Tools for fast, open framework for Deep Learning (CUDA)
 libcaffe-cuda-dev - development files for Caffe (CUDA)
 libcaffe-cuda1 - library of Caffe, a deep leanring framework (CUDA)
 python3-caffe-cuda - Python3 interface of Caffe (CUDA)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/caffe-contrib


  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/contrib/c/caffe-contrib/caffe-contrib_1.0.0~rc3-1.dsc


  Changes since the last upload:

caffe-contrib (1.0.0~rc3-1) experimental; urgency=low

  * Initial release. (Closes: #823308)


-- 
Best,
Lumin


Bug#829653: Acknowledgement (RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP])

2016-07-04 Thread Lumin
Well it seems that the first time mentors upload is going to FTBFS[1].
Hold on and I'll make an fixed upload.

the fix is to add flag -D_FORCE_INLINES to nvcc.

​[1] dom-amd64: CUDA memcpy problem​


-- 
Best,
Lumin


Bug#829658: RFS: caffe/1.0.0~rc3-3

2016-07-04 Thread Lumin
Package: sponsorship-requests
Severity: normal
​X-Debbugs-CC: costamagnagianfra...@yahoo.it


Dear mentors,

 Debomatic-amd64 build success[1]. As for 32-bit architecture
 FTBFS issue of caffe, I'd cherry-pick upstream fix at next
 time upload, synchronizing caffe and caffe-contrib packaging.

 [1]
​​
http://debomatic-amd64.debian.net/distribution#experimental/caffe/1.0.0~rc3-3/buildlog

  I am looking for a sponsor for my package "caffe"

 * Package name: caffe
   Version : 1.0.0~rc3-3
   Upstream Author : BVLC
 * URL : github.com/bvlc/caffe
 * License : BSD-2-clause
   Section : science

  It builds those binary packages:

caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Doxygen Document of Caffe
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/caffe


  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-3.dsc


  Changes since the last upload:

caffe (1.0.0~rc3-3) experimental; urgency=medium

  * Remove octave related packages and corresponding builds, because
upstream support for octave is limited.
  * Fix typo in package descriptions, update descriptions.
  * Update rules.
  * Add symbols control file for libcaffe.so .
  * Update README.Debian .

-- 
Best,
Lumin


Bug#829653: Info received (Bug#829653: Acknowledgement (RFS: caffe-contrib/1.0.0~rc3-1 -- cuda version of caffe [ITP]))

2016-07-04 Thread Lumin
http://debomatic-amd64.debian.net/distribution#experimental/caffe-contrib/1.0.0~rc3-1/buildlog

The lastest mentors package is fixed.
Please sponsor, thanks :-)

On 5 July 2016 at 03:30, Debian Bug Tracking System 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Mentors 
>
> If you wish to submit further information on this problem, please
> send it to 829...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 829653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829653
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>



-- 
Best,
Lumin


Bug#829454: marked as done (RFS: xkcdpass/1.6.3-1)

2016-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 5 Jul 2016 06:48:16 + (UTC)
with message-id <928887238.3314965.1467701296724.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#829454: RFS: xkcdpass/1.6.3-1
has caused the Debian Bug report #829454,
regarding RFS: xkcdpass/1.6.3-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
829454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package ‘xkcdpass’, version “1.6.3-1”.

It builds those binary packages:

  xkcdpass   - secure passphrase generator inspired by XKCD 936

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/xkcdpass

-- 
 \   “I distrust those people who know so well what God wants them |
  `\to do to their fellows, because it always coincides with their |
_o__)  own desires.” —Susan Brownell Anthony, 1896 |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

uploaded, but please look at your line endings :)

Gianfranco--- End Message ---


Bug#829658: marked as done (RFS: caffe/1.0.0~rc3-3)

2016-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 5 Jul 2016 06:50:58 + (UTC)
with message-id <99503832.3287950.1467701458184.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#829658: RFS: caffe/1.0.0~rc3-3
has caused the Debian Bug report #829658,
regarding RFS: caffe/1.0.0~rc3-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
829658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
​X-Debbugs-CC: costamagnagianfra...@yahoo.it


Dear mentors,

 Debomatic-amd64 build success[1]. As for 32-bit architecture
 FTBFS issue of caffe, I'd cherry-pick upstream fix at next
 time upload, synchronizing caffe and caffe-contrib packaging.

 [1]
​​
http://debomatic-amd64.debian.net/distribution#experimental/caffe/1.0.0~rc3-3/buildlog

  I am looking for a sponsor for my package "caffe"

 * Package name: caffe
   Version : 1.0.0~rc3-3
   Upstream Author : BVLC
 * URL : github.com/bvlc/caffe
 * License : BSD-2-clause
   Section : science

  It builds those binary packages:

caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Doxygen Document of Caffe
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning
(CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/caffe


  Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/c/caffe/caffe_1.0.0~rc3-3.dsc


  Changes since the last upload:

caffe (1.0.0~rc3-3) experimental; urgency=medium

  * Remove octave related packages and corresponding builds, because
upstream support for octave is limited.
  * Fix typo in package descriptions, update descriptions.
  * Update rules.
  * Add symbols control file for libcaffe.so .
  * Update README.Debian .

-- 
Best,
Lumin
--- End Message ---
--- Begin Message ---
Hi,

>X-Debbugs-CC: costamagnagianfra...@yahoo.it


no need to cc me
>  I am looking for a sponsor for my package "caffe"


uploaded.

G.--- End Message ---