Bug#838014: RFS: imagemagick

2016-09-16 Thread Bastien ROUCARIES 
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: Mattia Rizzolo 
X-Debbugs-CC: Salvatore Bonaccorso 


  Dear mentors,

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

 * Package name: imagemagick
   Version : 8:6.9.5.9+dfsg-1
   Section : graphics

  It builds those binary packages:

imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-common - image manipulation programs -- infrastructure
dummy package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics
routines -- Q16 versio
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick
- header files
 libmagick++-6.q16-6v6 - object-oriented C++ interface to ImageMagick
 libmagick++-6.q16-dev - object-oriented C++ interface to ImageMagick
- development files
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library -
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library --
quantum depth Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library -
extra codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library -
development files (Q16)
 libmagickcore-dev - low-level image manipulation library -- dummy package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library
 libmagickwand-6.q16-dev - image manipulation library - development files
 libmagickwand-dev - image manipulation library -- dummy package
 perlmagick - Perl interface to ImageMagick -- dummy package

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

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


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

dget -x 
https://mentors.debian.net/debian/pool/main/i/imagemagick/imagemagick_6.9.5.9+dfsg-1.dsc

  More information about hello can be obtained from https://www.example.com.



  Regards,
   bastien roucaries

Bug#838005: RFS: python-arrayfire/3.3.20160624-1

2016-09-16 Thread Ghislain Vaillant 
On Fri, 2016-09-16 at 11:07 +, Gianfranco Costamagna wrote:
> Hi,
> 
> > 
> > I am looking for a sponsor for my package "python-arrayfire"
> 
> 
> I see upstream changes wrt sphinx documentation.
> 
> Please consider trying to build the sphinx documentation in the -doc
> package for a future release (if possible and not already done, I
> didn't
> check)
> 
> thanks
> 
> G.

You are correct, I forgot to include the sphinx docs.

I will correct this in a subsequent release.

Thanks for sponsoring.

Ghis

Bug#838005: RFS: python-arrayfire/3.3.20160624-1

2016-09-16 Thread Ghislain Vaillant 

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-arrayfire"

* Package name: python-arrayfire
  Version : 3.3.20160624-1
  Upstream Author : ArrayFire
* URL : https://github.com/arrayfire/arrayfire-python
* License : BSD
  Section : python

It builds those binary packages:

  python-arrayfire - Python wrappers for the ArrayFire library (Python 2)
  python-arrayfire-doc - examples for the ArrayFire Python wrappers
  python3-arrayfire - Python wrappers for the ArrayFire library (Python 3)

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


  https://mentors.debian.net/package/python-arrayfire

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-arrayfire/python-arrayfire_3.3.20160624-1.dsc


Successful builds on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-arrayfire/3.3.20160624-1/buildlog

http://debomatic-i386.debian.net/distribution#unstable/python-arrayfire/3.3.20160624-1/buildlog

Changes since the last upload:

  * New upstream release.
  * Patch buggy standalone tests module.
  * Update test override.
  * Simplify packaging testsuite.
  * d/control: add missing Testsuite: autopkgtest.
  * d/control: mark -doc package Multi-Arch: foreign.

Regards,
Ghislain Vaillant

Bug#838004: RFS: rear/1.18-1 ITP: rear -- Bare metal disaster recovery and system migration framework

2016-09-16 Thread Frederic Bonnard 


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 Package name: rear
 Version : 1.18-1
 Upstream Author : Schlomo Schapiro, Gratien D'haese, Stefan Semmelroggen, Peer 
Heinlein, Dag Wieers, Jeroen Hoekx
 URL : https://github.com/rear/rear/
 License : GPL-3+, LGPL-2.1+, GPL-2+, CC-BY-ND-3.0
 Section : admin

It builds those binary packages:

  rear  - Bare metal disaster recovery and system migration framework
  rear-doc   - Bare metal disaster recovery and system migration framework 
(documentation)

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

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


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

  dget -x https://mentors.debian.net/debian/pool/main/r/rear/rear_1.18-1.dsc

More information about rear can be obtained from http://relax-and-recover.org/

Note:
  There is a load of Info lintians but this is due to the fact that rear embeds
  skeleton files/dirs that won't be use by the system installing rear, but
  those files will be used by the rear OS created to be booted later.


Regards,
 Frederic Bonnard

Re: How to trigger auto-building for seqan

2016-09-16 Thread Gianfranco Costamagna 
Hi,

BTW you did upload the arch:all package, no there isn't stuff
that autobuilders should do.

Last thing:gasic needs to be fixed to see the package removed
(it depends on the package you want to remove)

https://sources.debian.net/src/gasic/0.0.r18-3/debian/control/
G.

Re: How to trigger auto-building for seqan

2016-09-16 Thread Gianfranco Costamagna 
Hi,


>I did a source only upload of seqan which somehow leaded to the fact

>that autobuilders ignored it[1].  What can I do?
>
>Kind regards


https://sources.debian.net/src/seqan/1.4.2%2Bdfsg-1/debian/control/

Arch:all package.

and you removed seqan-apps, so it won't migrate unless you file a bug against 
ftpmasters.

(this answer has been provided with *great* help
from  and  on #-ftp irc channel)

G.

Re: Any reason why sphinx does not migrate to testing?

2016-09-16 Thread Gianfranco Costamagna 
Hi


>22 days old (needed 5 days)
>Valid candidate 
>
>
>So what might be the problem here?


wild guess, many packages have a dependency on the old version.

but they are arch:all, so binNMU isn't possible (or is, but nobody
wants to try them).
So, sourceful uploads are needed for reverse-dependencies
e.g. cdist
https://packages.debian.org/testing/cdist-doc

compared to
https://packages.debian.org/unstable/cdist-doc

G.

Re: Any reason why sphinx does not migrate to testing?

2016-09-16 Thread Sebastiaan Couwenberg 
On 09/16/2016 10:01 AM, Andreas Tille wrote:
> So what might be the problem here?

The strict dependencies on sphinx in cdist-doc apparently.

>From the britney output:

 Trying easy from autohinter: clustalo/1.2.3-1 sphinx/1.4.6-1
 start: 57+556: a-3:i-18:a-0:a-0:a-0:m-0:m-0:p-35:p-0:s-1:m-556
 orig: 57+556: a-3:i-18:a-0:a-0:a-0:m-0:m-0:p-35:p-0:s-1:m-556
 easy: 59+556: a-4:i-19:a-0:a-0:a-0:m-0:m-0:p-35:p-0:s-1:m-556
 * amd64: cdist-doc
 * i386: cdist-doc

 FAILED

https://release.debian.org/britney/update_output.txt

The new cdist has not aged sufficiently to migrate:

 Excuse for cdist

 * Too young, only 4 of 5 days old
 * Depends: cdist sphinx
 * Not considered

https://qa.debian.org/excuses.php?package=cdist

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

How to trigger auto-building for seqan

2016-09-16 Thread Andreas Tille 
Hi,

I did a source only upload of seqan which somehow leaded to the fact
that autobuilders ignored it[1].  What can I do?

Kind regards

   Andreas.


[1] https://buildd.debian.org/status/package.php?p=seqan

-- 
http://fam-tille.de

Any reason why sphinx does not migrate to testing?

2016-09-16 Thread Andreas Tille 
Hi,

  https://qa.debian.org/excuses.php?package=sphinx

says:


22 days old (needed 5 days)
Valid candidate 


So what might be the problem here?

Kind regards

Andreas.

-- 
http://fam-tille.de