Bug#816756: marked as done (php-pimple: Useless in Debian)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Apr 2016 12:06:14 +1000
with message-id <2188967.UG5BjOMnI2@deblab>
and subject line Re: #816756 php-pimple: Useless in Debian
has caused the Debian Bug report #816756,
regarding php-pimple: Useless in Debian
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.)


-- 
816756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-pimple
Version: 1.1.1-1
Severity: serious

[ Filled as an RC-bug by the maintainer to see the package auto-removed
  from testing, and not let it block the PHP 7.0 transition. ]

I packaged php-pimle as used by owncloud, but owncloud is going away,
see #816376. There is a priori little point to ship php-pimple in a
stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.0.2-2

We need php-pimple for php7cc that should be useful to check PHP packages for 
incompatibilities with PHP-7.

I did some maintenance on php-pimple so it is not blocking PHP-7 transition 
any more.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

-- 
Regards,
 Dmitry Smirnov.

---

We do our friends no favors by pretending not to notice flaws in their
work, especially when those who are not their friends are bound to notice
these same flaws.
-- Sam Harris


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


Bug#820568: tracker: searches fail with "no such module: fts5"

2016-04-09 Thread Sam Morris
Package: tracker
Version: 1.8.0-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Searches fail with the following error:

$ tracker search test
Could not get search results, no such module: fts5

- -- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (550, 'stable-updates'), (550, 'stable'), (530, 'testing'), (520, 
'unstable'), (510, 'experimental'), (500, 'unstable-debug'), (500, 
'testing-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tracker depends on:
ii  dbus 1.10.8-1
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libc62.22-5
ii  libexempi3   2.3.0-2
ii  libglib2.0-0 2.48.0-1
ii  libtagc0 1.9.1-2.4
ii  libtracker-control-1.0-0 1.8.0-2+b1
ii  libtracker-sparql-1.0-0  1.8.0-2+b1
ii  shared-mime-info 1.3-1

Versions of packages tracker recommends:
ii  tracker-gui   1.8.0-2+b1
ii  tracker-miner-fs  1.8.0-2+b1

tracker suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXCbEDAAoJENILQgJc2ie5NxoP+wQq+84ZY51h7Y6bjt5zyLJe
+6j4r5a9mBXCFWRkHKz8+DnaW1AQwT3c/UU08UdeXrnWpVTCDGjZ43oAmss/CStN
UfF1UbPxrdDxUOMHjQrlayg2ONbuYoNN6Gc0Ps90SifTA1hrUmEQNhtNY4kp7B3i
sTzL7HdTXGmhILpO7wDu8t2ei1hEghLvCEnxu5uFVdtDSOdG+Y0L2uzTZ8Wjeo8N
GJOtPkQR7Pq1qxq6zrIcYX6eyEWCuj7fX0pSxwYy8dasWIwvXbGJ7Qp4eomky9Nd
zrO6Q2hI+LOUvc1tDLZBPyTsmsnlXm6IH8Y5k6bnghVFc7r9HU8VLlB0aC3R9h2U
nbEavhGu7ogWNKlP4vdzOckjG3FhPNw5jdO6rJOEmCYGAPr1c8ZPC961+NhhwPUz
ArrpNfpiOBb/CwznpSN7DF1WuAyQm5ORAMxr3QLr044QiTxB4bX2nRP5b6Krilhf
UVRxEtEp4Jlif7jZfu6unSE/p0oKnuiy5FdCAeQwdbKG1KiaFHTHxiKw0Z0iKiH9
n6A6hd8Vx6Yznc6c38vK4V6fHnp92p9OfMot05toBtPh+TuoHebSBLQq6oqjtMpA
piwV6R3oDIM0AIw8sF14Zzb4iGPAbM7hZFcSi575w2rljTJi8JBinvcaJ3eq+dqP
UpMTanA4QkOcWWy0vPh0
=jaYx
-END PGP SIGNATURE-



Bug#820083: marked as done (gridengine-drmaa-dev: fails to install: update-alternatives: error: alternative path /usr/lib/gridengine-drmaa/lib/libdrmaa.so doesn't exist)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Apr 2016 01:18:59 +
with message-id 
and subject line Bug#820083: fixed in gridengine 8.1.8+dfsg-4
has caused the Debian Bug report #820083,
regarding gridengine-drmaa-dev: fails to install: update-alternatives: error: 
alternative path /usr/lib/gridengine-drmaa/lib/libdrmaa.so doesn't exist
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.)


-- 
820083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gridengine-drmaa-dev
Version: 8.1.8+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gridengine-drmaa-dev.
  (Reading database ... 
(Reading database ... 7660 files and directories currently installed.)
  Preparing to unpack .../gridengine-drmaa-dev_8.1.8+dfsg-3_amd64.deb ...
  Unpacking gridengine-drmaa-dev (8.1.8+dfsg-3) ...
  Setting up gridengine-drmaa-dev (8.1.8+dfsg-3) ...
  update-alternatives: error: alternative path 
/usr/lib/gridengine-drmaa/lib/libdrmaa.so doesn't exist
  dpkg: error processing package gridengine-drmaa-dev (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   gridengine-drmaa-dev


cheers,

Andreas


gridengine-drmaa-dev_8.1.8+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gridengine
Source-Version: 8.1.8+dfsg-4

We believe that the bug you reported is fixed in the latest version of
gridengine, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 820...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Afif Elghraoui  (supplier of updated gridengine package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 18:03:30 -0700
Source: gridengine
Binary: gridengine-common gridengine-client gridengine-qmon gridengine-master 
gridengine-exec gridengine-drmaa1.0 libdrmaa1.0-java libdrmaa1.0-java-doc 
gridengine-drmaa-dev libdrmaa1.0-ruby
Architecture: source
Version: 8.1.8+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Grid Engine Maintainers 

Changed-By: Afif Elghraoui 
Description:
 gridengine-client - Utilities for Grid Engine queue management
 gridengine-common - Distributed resource management - common files
 gridengine-drmaa-dev - Distributed resource management Application API library 
- develop
 gridengine-drmaa1.0 - Distributed resource management Application API library
 gridengine-exec - Distributed resource management - Execution Server
 gridengine-master - Distributed resource management - Master Server
 gridengine-qmon - Graphical utilities for Grid Engine queue management
 libdrmaa1.0-java - Distributed resource management Application API library - 
Java bi
 libdrmaa1.0-java-doc - Distributed resource management Application API library 
- Java bi
 libdrmaa1.0-ruby - Distributed resource management Application API library - 
Ruby bi
Closes: 694040 735017 820083
Changes:
 gridengine (8.1.8+dfsg-4) unstable; urgency=medium
 .
   * Use maintainer scripts to start/stop daemons during upgrades.
   * Use arch: any for arch-dependent packages (Closes: #694040, #735017).
   * Add a symlink to versioned libdrmaa so file (Closes: #820083).
   * Set rpath to /usr/lib/gridengine during build.
Checksums-Sha1:
 76f12c56dc7773ee34063f9e15ae937ab55c9953 2990 gridengine_8.1.8+dfsg-4.dsc
 59c5da1c7648a3e1c809696c56789da54130d56e 37472 
gridengine_8.1.8+dfsg-4.debian.tar.xz
Checksums-Sha256:
 3bb6f4f8f05de4d3840ba32eef909cfab54caa3aefff02aee949b7efe86b831a 2990 
gridengine_8.1.8+dfsg-4.dsc
 17af2b33417a4e1f304eb8e82fbc9ad08dbae39719e56f4df8defb0d3dad49c5 37472 
gridengine_8.1.8+dfsg-4.debian.tar.xz
Files:
 

Bug#820498: marked as done (tachyon: FTBFS with libpng16 on mipsel)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 Apr 2016 01:11:07 +
with message-id <20160410011107.ga4...@chase.mapreri.org>
and subject line Re: Bug#820498: tachyon: FTBFS with libpng16 on mipsel
has caused the Debian Bug report #820498,
regarding tachyon: FTBFS with libpng16 on mipsel
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.)


-- 
820498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tachyon
Severity: serious
Justification: FTBFS but did in the past

Dear maintainer,

the package FTBFS with libpng 1.6 on mipsel (release arch) and others
non-release archs (mips64el and sh4) (it built on mipsel in the past, so it is
RC)

Note that hppa also shows a very similar error, which was not binNMUed. So it
might be that the problem is not related to the library tansition.

Buildlog for mips: 

https://buildd.debian.org/status/fetch.php?pkg=tachyon=mipsel=0.99~b6%2Bdsx-4%2Bb1=1460116130

Buildd page:
https://buildd.debian.org/status/package.php?p=tachyon

snippet: 
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so" (tried in "." and "debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so
dh_install: missing files, aborting
debian/rules:59: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Sat, Apr 09, 2016 at 12:56:27PM +0200, Emilio Pozuelo Monfort wrote:
> On Sat, 09 Apr 2016 09:26:58 +0200 Tobias Frost  wrote:
> > Source: tachyon
> > Severity: serious
> > Justification: FTBFS but did in the past
> > 
> > Dear maintainer,
> > 
> > the package FTBFS with libpng 1.6 on mipsel (release arch) and others
> > non-release archs (mips64el and sh4) (it built on mipsel in the past, so it 
> > is
> > RC)
> 
> This is caused by #818909, which has just been fixed in chrpath. The necessary
> rebuilds will be scheduled soon.

It did indeed build, so closing this bug.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---


Processed: view3dscene: please stop depending on libpng12-0

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> block 650601 by -1
Bug #650601 [release.debian.org] transition: libpng 1.6
650601 was blocked by: 809885 810205 809905 742569 810166 819434 810177 809955 
810187 810197 809872 816103 809961 809889 809962 635945 641892 809906 662566 
809956 816115 809959 662550 742559 741894 650563 809895 810200 809954 662492 
636998 662473 809958 742560 809947 816116 810179 809957 662421 662278 649552 
819440 810193 809950 819428 810171 810176 809893 809867 809951 809835 809935 
662381 816114 662554 809860 810188 650484 816102 809953 810207 662314 809864 
648129 820347 809904 638812 809836 809943 809878 809896 662530 743391 809942 
809871 810209 810185 809941 809952 809949 810203 809937 809948 810172 810178 
820439 809891 809939 650575 809921 809870 641889 809863 809890 809898 649547 
809936 809869 650567 810195 809945 662523 809960 662416 809882 662407 810165 
809861 810202 809913 810186 809907 810208 810168 810170 650489 649798 809859 
741891 809884 648131 809865 810190 809897 810191 810182 809880 810180 810175 
662556 810183 662443 809879 809883 810201 662411 650571 648126 649557 635704 
809909 642265 809888 662273 809881 810167 649546 810095 636004 809862 810169 
809886 810192 662334 662476 809873 809866 662444 819438 809892 635946 809911 
809899 662522 811370 809887 662437 809894 809910 650483 810174 809908 662465 
741901 809944 810189 809940 742655 649971 809833 809946 809938 809933 809934 
809868 814879
650601 was blocking: 649556 649973 810001
Added blocking bug(s) of 650601: 820566

-- 
650601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601
820566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820566: view3dscene: please stop depending on libpng12-0

2016-04-09 Thread Mattia Rizzolo
Source: view3dscene
Version: 3.15.0-4
Severity: serious
Control: block 650601 by -1

Dear maintainer,

your package has a binary dependency on libpng12-0.
For some reason it doesn't build-depend on it, and shlibs seems to think
it is not needed, so I'm not sure at all why you would need such
dependency, but for sure now it's going to cause a problem as there is
an ongoing migration from libpng12 to libpng16.

If you really such dependency that shlibs doesn't pick up for you,
please switch the dep, or do whatever's sensible for you but please stop
depending on libpng12-0.

Thank you for maintaing this view3dscene

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://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#804582: (no subject)

2016-04-09 Thread Jeremy T. Bouse
I believe I may have it fixed... I'm doing some final testing in my
build environment but I suspect I'll have the 1.16.0 package ready to go
shortly.

On 04/08/2016 05:18 PM, Barry Warsaw wrote:
> Okay, so I think the locale changes are enough to fix the FTBFS.  I retried
> building in an Ubuntu PPA and the build succeeded.
> 
> The timeout failure must just have been a problem with my local sbuild.
> 



Processed: Re: Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 791725 by 820563
Bug #791725 [node-mapnik] node-mapnik: FTBFS against mapnik 3.0.0
791725 was not blocked by any bugs.
791725 was not blocking any bugs.
Added blocking bug(s) of 791725: 820563
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
791725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#800229: marked as done (dict-gazetteer2k: Please migrate a supported debhelper compat level)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 22:40:48 +
with message-id 
and subject line Bug#800229: fixed in dict-gazetteer2k 1.0.0-5.3
has caused the Debian Bug report #800229,
regarding dict-gazetteer2k: Please migrate a supported debhelper compat level
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.)


-- 
800229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dict-gazetteer2k
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package dict-gazetteer2k is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: dict-gazetteer2k
Source-Version: 1.0.0-5.3

We believe that the bug you reported is fixed in the latest version of
dict-gazetteer2k, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated 
dict-gazetteer2k package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Mar 2016 21:32:47 -0300
Source: dict-gazetteer2k
Binary: dict-gazetteer2k dict-gazetteer2k-places dict-gazetteer2k-counties 
dict-gazetteer2k-zips
Architecture: source
Version: 1.0.0-5.3
Distribution: unstable
Urgency: medium
Maintainer: John Goerzen 
Changed-By: Giovani Augusto Ferreira 
Description:
 dict-gazetteer2k - Placeholder package to install entire Gazetteer 2000
 dict-gazetteer2k-counties - Counties Database for the 2000 US Gazetteer
 dict-gazetteer2k-places - Places Database for the 2000 US Gazetteer
 dict-gazetteer2k-zips - ZIP and ZCTA database for the 2000 US Gazetteer
Closes: 800229
Changes:
 dict-gazetteer2k (1.0.0-5.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update DH level to 9. (Closes: #800229)
   * debian/compat: created and set to 9, instead of using DH_COMPAT.
   * debian/control:
  - Added the ${misc:Depends} variable to provide the right install
dependencies.
  - Bumped Standards-Version to 3.9.7.
  - Moved debhelper from Build-Depends-Indep to Build-Depends.
   * debian/rules: disabled the DH_COMPAT line.
Checksums-Sha1:
 750817a84d84699e7c9dd43b688f346613283664 2022 dict-gazetteer2k_1.0.0-5.3.dsc
 a3b9348c2ca9ded23d3d93af1a1d003b2688ec20 6315 
dict-gazetteer2k_1.0.0-5.3.diff.gz
Checksums-Sha256:
 a58a7d79e0ca86b6aa45d3197568406089e0a8e865bd6425656619527edb 2022 
dict-gazetteer2k_1.0.0-5.3.dsc
 3e50f8f3b37ed93253d9ff741ffb7731c9dea1414ba09bcffb160b3989430452 6315 
dict-gazetteer2k_1.0.0-5.3.diff.gz
Files:
 ee81be1e754b0d09a184e9c6bac78ba5 2022 text optional 
dict-gazetteer2k_1.0.0-5.3.dsc
 5eb06543fad660795139be64dbdb0f7e 6315 text optional 
dict-gazetteer2k_1.0.0-5.3.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1


Bug#814167: marked as done (lwjgl: (Build-)Depends on OpenJDK 7)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 22:00:04 +
with message-id 
and subject line Bug#814167: fixed in lwjgl 2.9.3+dfsg-1
has caused the Debian Bug report #814167,
regarding lwjgl: (Build-)Depends on OpenJDK 7
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.)


-- 
814167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lwjgl
Version: 2.7.1+dfsg-5
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Source: lwjgl
Source-Version: 2.9.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
lwjgl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 814...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated lwjgl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Apr 2016 22:33:53 +0200
Source: lwjgl
Binary: liblwjgl-java liblwjgl-java-jni liblwjgl-java-doc
Architecture: source
Version: 2.9.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 liblwjgl-java - Lightweight Java Game Library
 liblwjgl-java-doc - Lightweight Java Game Library (javadoc)
 liblwjgl-java-jni - Lightweight Java Game Library (jni)
Closes: 648624 814167
Changes:
 lwjgl (2.9.3+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Imported Upstream version 2.9.3+dfsg. (Closes: #648624)
   * d/control: Build-depend on default-jdk instead of openjdk-7-jdk.
 (Closes: #814167)
   * Declare compliance with Debian Policy 3.9.7.
   * Vcs-Git: Use https.
   * d/rules: Use default-java as JAVA_HOME.
   * Fix debian/watch file and track the latest 2.x releases.
   * Refresh all patches for new release.
   * debian/rules: Build with parallel and javahelper.
   * Add build-failure.patch and fix a FTBFS.
   * Add no-asm-support.patch and remove optional code for asm.jar.
   * Export DEB_BUILD_MAINT_OPTIONS = hardening=+all.
   * Update debian/copyright for new release.
Checksums-Sha1:
 e5625f4fa76f09d33f715673b599035f62566b80 2369 lwjgl_2.9.3+dfsg-1.dsc
 39d5aba15743c09f7cd5338eec447dc564343496 956825 lwjgl_2.9.3+dfsg.orig.tar.gz
 ca744844faeb8b2c1de883d1e3144b50e75d3c84 24344 lwjgl_2.9.3+dfsg-1.debian.tar.xz
Checksums-Sha256:
 aaef56d6f76d0d4f40c9739b328cfc03a2fd8ca4204eab6f798f74e18f53c54d 2369 
lwjgl_2.9.3+dfsg-1.dsc
 7f3ae71f93d382e0c37e3fb741360bd180685a4b938ccd34bb805cf6a278778e 956825 
lwjgl_2.9.3+dfsg.orig.tar.gz
 e44af74bcce3e5110a2c1728829082bf0a808175e30523bb27b88a3c80e154c8 24344 
lwjgl_2.9.3+dfsg-1.debian.tar.xz
Files:
 b1d941bfbc730d9e3d21894daa1de5fd 2369 java optional lwjgl_2.9.3+dfsg-1.dsc
 b610feabacfebea9458faa96d0a39b98 956825 java optional 
lwjgl_2.9.3+dfsg.orig.tar.gz
 ab8e777d7296df34e6edaf583f35cf67 24344 java optional 
lwjgl_2.9.3+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXCWgPXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkNLIP/Rd2aDKT4sTXN776eP4m6FSU
UniSMtRBG5jCdGTHeMXgig7PxiRxu3nMJoueAqviUa7jXhaSYi4ZysEd799j9/tR
5fbeKsPKDfvAN0/qdUDp/t6RBO1d810omPBtgRQyik0yCzwkxXF8MxrGXha/U6OQ
m9E8EjGK/OZGBq1U34zBJonKhV/EceD+WQUbT0cz4RqpscZG5TRyG1h6Qz+h8g5n
HMEVCPo0v0/LUHhLZZ9kPAEYQiHX72YVN/qRSmbU/rwG8Lh75oHPi9PHi6Qna9fI
KO3Wq9ikIpALdZuvrHI9/nu9dSBqaRJUA3tYZgwNuziTlUMh14cZl1aireCXUoaA
ubmL+f9kV9dpAijFw/1X8VaNAr6y2vcGEIXT0Yb41U9MFr/lpCfMT+DWd8aXvHXS
b1kZVLAb8KimAEte0GevxNpGzhyCUcyHFTu/6ClMdkACG73A6qC+ZGLcR8ROLJCa

Bug#820545: marked as done (ifrit: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', )

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 21:59:12 +
with message-id 
and subject line Bug#820545: fixed in ifrit 4.1.2-3
has caused the Debian Bug report #820545,
regarding ifrit: FTBFS: No rule to make target 
'/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', 
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.)


-- 
820545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifrit
Version: 4.1.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ifrit fails to build from source in unstable/amd64:

  [..]

  [100%] Building CXX object CMakeFiles/ifrit.dir/ifrit.cpp.o
  /usr/bin/c++   -DI_EXTERNAL_CONFIGURATION 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="4(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingFreeTypeOpenGL,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/usr/include/vtk-6.2 -I/usr/include/freetype2 -I/usr/include/python2.7 
-I/usr/include/jsoncpp -I/usr/include/x86_64-linux-gnu 
-I/usr/include/hdf5/openmpi 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include 
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
-I/usr/include/libxml2 -I/usr/include/tcl -I/usr/include/qt4 
-I/usr/include/qt4/QtCore 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../configure
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../core
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../help
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../docs
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/configure
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/generic
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/base
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/cl
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/os
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/qt
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../scripts/python
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o CMakeFiles/ifrit.dir/ifrit.cpp.o -c 
/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/ifrit.cpp
  make[3]: *** No rule to make target 
'/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/ifrit'.  Stop.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:107: recipe for target 'CMakeFiles/ifrit.dir/all' failed
  make[2]: *** [CMakeFiles/ifrit.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  Makefile:130: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:20: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ifrit.4.1.2-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ifrit
Source-Version: 4.1.2-3

We believe that the bug you reported is fixed in the latest version of
ifrit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one 

Processed: found 816116 in 0.8.3-5, tagging 816116, found 820498 in 0.99~b6+dsx-4

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 816116 0.8.3-5
Bug #816116 {Done: Gianfranco Costamagna } 
[libpolybori-dev] libpolybori-dev: Please change dependency from libpng12-dev 
to libpng-dev
Marked as found in versions polybori/0.8.3-5.
> tags 816116 + sid stretch
Bug #816116 {Done: Gianfranco Costamagna } 
[libpolybori-dev] libpolybori-dev: Please change dependency from libpng12-dev 
to libpng-dev
Added tag(s) stretch and sid.
> found 820498 0.99~b6+dsx-4
Bug #820498 [src:tachyon] tachyon: FTBFS with libpng16 on mipsel
Marked as found in versions tachyon/0.99~b6+dsx-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816116
820498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#818997: [pkg-gnupg-maint] Bug#818997: gpgv.exe linked dynamically against zlib1, doesn't allow proper signature verification

2016-04-09 Thread Daniel Kahn Gillmor
On Tue 2016-04-05 02:23:59 -0400, Didier 'OdyX' Raboud wrote:

>  gpgv-win32 from unstable seems to work for me now (using the 
>  debian/tests/gpgv-win32 test at least).

good!

>  The CI test still fails though, you might want to try integrating 
>  Antonio's proposal below.

it should already be integrated in the version in experimental.  Please
let me know if that doesn't work for you.  (maybe the CI isn't pulling
from experimental at all so we just don't see it?)

>  That '53' error is gpgv.exe failing to load zlib1, so it was just 
>  exposing this very bug. :) There's no need to wrap it in xvfb-run, 
>  AFAIK.

right, agreed.

   --dkg



Processed: your mail

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # experience says a version is needed for the avoid-entering-testing
> # machinery to work.
> found 819963 1.2.54-4
Bug #819963 [src:libpng] libpng: keep out of Stretch
Marked as found in versions libpng/1.2.54-4.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
819963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820545: ifrit: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so',

2016-04-09 Thread Chris Lamb
Source: ifrit
Version: 4.1.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ifrit fails to build from source in unstable/amd64:

  [..]

  [100%] Building CXX object CMakeFiles/ifrit.dir/ifrit.cpp.o
  /usr/bin/c++   -DI_EXTERNAL_CONFIGURATION 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="4(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingFreeTypeOpenGL,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/usr/include/vtk-6.2 -I/usr/include/freetype2 -I/usr/include/python2.7 
-I/usr/include/jsoncpp -I/usr/include/x86_64-linux-gnu 
-I/usr/include/hdf5/openmpi 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
-I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include 
-I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
-I/usr/include/libxml2 -I/usr/include/tcl -I/usr/include/qt4 
-I/usr/include/qt4/QtCore 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../configure
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../core
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../help
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../docs
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/configure
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/generic
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/base
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/cl
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/os
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../shells/qt
 
-I/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/../scripts/python
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o CMakeFiles/ifrit.dir/ifrit.cpp.o -c 
/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/build/ifrit.cpp
  make[3]: *** No rule to make target 
'/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/ifrit'.  Stop.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:107: recipe for target 'CMakeFiles/ifrit.dir/all' failed
  make[2]: *** [CMakeFiles/ifrit.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  Makefile:130: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160409190149.Br8zVpSuYC.ifrit/ifrit-4.1.2/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:20: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ifrit.4.1.2-2.unstable.amd64.log.txt.gz
Description: Binary data


Bug#820546: jackson-module-afterburner: FTBFS: OptimizedSettableBeanProperty.java:[171,29] cannot find symbol _nullProvider

2016-04-09 Thread Chris Lamb
Source: jackson-module-afterburner
Version: 2.4.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

jackson-module-afterburner fails to build from source in unstable/amd64:

  [..]

  [INFO] 
  [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
jackson-module-afterburner ---
  [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
  [INFO] Copying 2 resources
  [INFO] 
  [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ 
jackson-module-afterburner ---
  [INFO] Changes detected - recompiling the module!
  [WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
  [INFO] Compiling 32 source files to 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/target/classes
  [INFO] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/ser/ObjectFieldPropertyWriter.java:
 Some input files use or override a deprecated API.
  [INFO] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/ser/ObjectFieldPropertyWriter.java:
 Recompile with -Xlint:deprecation for details.
  [INFO] -
  [ERROR] COMPILATION ERROR : 
  [INFO] -
  [ERROR] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/deser/OptimizedSettableBeanProperty.java:[168,17]
 cannot find symbol
symbol:   variable _nullProvider
location: class 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty
  [ERROR] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/deser/OptimizedSettableBeanProperty.java:[171,29]
 cannot find symbol
symbol:   variable _nullProvider
location: class 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty
  [INFO] 2 errors 
  [INFO] -
  [INFO]
 
  [INFO] 

  [INFO] Skipping Jackson-module-Afterburner
  [INFO] This project has been banned from the build due to previous failures.
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 1.955 s
  [INFO] Finished at: 2016-04-09T19:09:32+01:00
  [INFO] Final Memory: 14M/234M
  [INFO] 

  [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on 
project jackson-module-afterburner: Compilation failure: Compilation failure:
  [ERROR] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/deser/OptimizedSettableBeanProperty.java:[168,17]
 cannot find symbol
  [ERROR] symbol:   variable _nullProvider
  [ERROR] location: class 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty
  [ERROR] 
/home/lamby/temp/cdt.20160409190738.kbNVFPZacq.jackson-module-afterburner/jackson-module-afterburner-2.4.3/src/main/java/com/fasterxml/jackson/module/afterburner/deser/OptimizedSettableBeanProperty.java:[171,29]
 cannot find symbol
  [ERROR] symbol:   variable _nullProvider
  [ERROR] location: class 
com.fasterxml.jackson.module.afterburner.deser.OptimizedSettableBeanProperty
  [ERROR] -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
  dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 

Bug#820530: marked as done (pdal: FTBFS because of openmpi)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 17:50:56 +
with message-id 
and subject line Bug#820530: fixed in pdal 1.1.0-5
has caused the Debian Bug report #820530,
regarding pdal: FTBFS because of openmpi
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.)


-- 
820530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdal
version: 1.1.0-4 

severity: serious

Hi, I don't know about the openmpi breakage, but it seems it hit a lot of 
packages,
and your package is currently FTBFS because of it (probably)

the build log has many
make[4]: *** No rule to make target 
'/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
'lib/libpdal_plugin_filter_voxelgrid.so'.  Stop.
make[4]: *** No rule to make target 
'/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
'lib/libpdal_plugin_filter_pclblock.so'.  Stop.


Seems that the above file is provided by libhdf5-openmpi-dev, maybe it is just 
a matter of a new dependency to add, but due to 

the libng16 transition I'm sorry but I can't investigate more.
Please don't hesitate to ask for a quick NMU if you can't investigate too, and 
I'll make sure to increase the priority of this failure.

#820113 #820098 are similar issues

I uploaded on DoM a build with the additional dependency, not sure how it will 
go.

http://debomatic-amd64.debian.net/distribution#unstable/pdal/1.1.0-4.1/buildlog

thanks,
Gianfranco
--- End Message ---
--- Begin Message ---
Source: pdal
Source-Version: 1.1.0-5

We believe that the bug you reported is fixed in the latest version of
pdal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 820...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pdal package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Apr 2016 19:04:46 +0200
Source: pdal
Binary: pdal pdal-doc libpdal-base1 libpdal-plang1 libpdal-util1 libpdal-dev 
libpdal-plugins libpdal-plugin-attribute libpdal-plugin-greyhound 
libpdal-plugin-icebridge libpdal-plugin-pgpointcloud libpdal-plugin-python 
libpdal-plugin-sqlite
Architecture: source amd64 all
Version: 1.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 libpdal-base1 - Point Data Abstraction Library - libpdal_base
 libpdal-dev - Point Data Abstraction Library - development files
 libpdal-plang1 - Point Data Abstraction Library - libpdal_plang
 libpdal-plugin-attribute - Point Data Abstraction Library - Attribute plugin
 libpdal-plugin-greyhound - Point Data Abstraction Library - Greyhound plugin
 libpdal-plugin-icebridge - Point Data Abstraction Library - Icebridge plugin
 libpdal-plugin-pgpointcloud - Point Data Abstraction Library - PostgreSQL 
PointCloud plugin
 libpdal-plugin-python - Point Data Abstraction Library - Python plugin
 libpdal-plugin-sqlite - Point Data Abstraction Library - SQLite plugin
 libpdal-plugins - Point Data Abstraction Library - plugins
 libpdal-util1 - Point Data Abstraction Library - libpdal_util
 pdal   - Point Data Abstraction Library
 pdal-doc   - Point Data Abstraction Library - documentation
Closes: 820530
Changes:
 pdal (1.1.0-5) unstable; urgency=medium
 .
   * Don't build PCL plugin, requires vtk5 (not in testing).
 (closes: #820530)
Checksums-Sha1:
 dd11a29c6f48a6c54272c567049c263423d91972 3201 pdal_1.1.0-5.dsc
 7b9882f229c3c148a454a1803e57b326e890c6fa 38328 pdal_1.1.0-5.debian.tar.xz
 0313dfa896de36764bad204d0183eeba5ce9be87 14865980 
libpdal-base1-dbgsym_1.1.0-5_amd64.deb
 08197e72c149bd7add5b2ed2d3203907343b802b 815222 libpdal-base1_1.1.0-5_amd64.deb
 267119ae5dae9ef40cc875ba1ec6546e77de0c92 221012 libpdal-dev_1.1.0-5_amd64.deb
 e23d5df567b842f3465598ece412fe6ac2b6030b 546782 
libpdal-plang1-dbgsym_1.1.0-5_amd64.deb
 77458e14d82e8a6e580389ada71a451e525403ff 198842 
libpdal-plang1_1.1.0-5_amd64.deb
 1a6249ba84f867061b5e1b75d4b97c035b0135de 300940 

Bug#656096: marked as done (dante-client: socksify preloads libdl.so.2 from an incorrect path)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 17:49:16 +
with message-id 
and subject line Bug#656096: fixed in dante 1.4.1+dfsg-1
has caused the Debian Bug report #656096,
regarding dante-client: socksify preloads libdl.so.2 from an incorrect path
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.)


-- 
656096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dante-client
Version: 1.1.19.dfsg-3+b3
Severity: normal


socksify preloads /lib/libdl.so.2, which is no longer in that path, and it
causes the dynamic linker to print a lot of error messages. It should preload
something like /lib/i386-linux-gnu/libdl.so.2 instead.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (980, 'testing'), (980, 'stable'), (500, 'unstable'), (500, 
'stable'), (200, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-rc6-lis64+ (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dante-client depends on:
ii  libdsocksd0  1.1.19.dfsg-3+b3

dante-client recommends no packages.

dante-client suggests no packages.

-- Configuration Files:
/etc/dante.conf changed [not included]

-- no debconf information

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/


--- End Message ---
--- Begin Message ---
Source: dante
Source-Version: 1.4.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
dante, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated dante package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 17:14:40 +0300
Source: dante
Binary: libsocksd0 libsocksd0-dev libdsocksd0 dante-client dante-server
Architecture: source all amd64
Version: 1.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Description:
 dante-client - SOCKS wrapper for users behind a firewall
 dante-server - SOCKS (v4 and v5) proxy daemon (danted)
 libdsocksd0 - SOCKS library preloaded in user applications
 libsocksd0 - SOCKS library for packages built using libsocksd-dev
 libsocksd0-dev - Development files for compiling programs with SOCKS support
Closes: 626316 656096 715117 716681 731178 740749 776907
Changes:
 dante (1.4.1+dfsg-1) unstable; urgency=medium
 .
   * Fix FTBFS by depending on libtool-bin instead of libtool.
 Closes: #776907
   * Remove the obsolete DM-Upload-Allowed source control field.
   * Note the migration to my GitLab repository in the Vcs-* fields.
   * Use the default dpkg-dev source package compression method.
   * Drop the versions from the autotools-dev and dpkg-dev dependencies.
   * Fix the broken .so symlink in libsocksd0-dev.  Closes: #715117
   * Bump the debhelper compatibility level to 10:
 - install into the multiarch library directory
 - get the compiler and linker flags directly from debhelper
 - override the "experimental debhelper version" Lintian warning
 - drop the autotools-dev dependency and invocation, debhelper uses
   autoreconf automatically in level 10; do not override the Lintian
   "outdated autotools file" warnings, since it's wrong - see #820441
   * New upstream version:
 - Closes: #740749 (new upstream version)
 - Closes: #731178 (tries to dlopen a linker script)
 - rework some of the patches to modify the *.am files instead of
   the *.in ones; Closes: #716681
 - add a lot more filenames to debian/clean
 - put the preloaded libdsocksd back into its own package, complete
   with a SONAME, in preparation for socksify being able to select
   the one with the correct ABI/architecture; drop the 15-lib-dante-client
   patch that is no longer applicable
 - update the libsocksd0 symbols file - all the internal symbols were
   dropped from the public interface; this should 

Bug#731178: marked as done (dante-server: requires libc6-dev to be installed)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 17:49:16 +
with message-id 
and subject line Bug#731178: fixed in dante 1.4.1+dfsg-1
has caused the Debian Bug report #731178,
regarding dante-server: requires libc6-dev to be installed
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.)


-- 
731178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dante-server
Version: 1.1.19.dfsg-3+b4
Severity: important

Dec  2 21:47:29 (1386020849) danted[96427]: symbolfunction(): compiletime 
configuration error?  Failed to open "libc.so": 
/usr/lib/x86_64-linux-gnu/libc.so: invalid ELF header


this symlink is only present when libc6-dev is installed

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dante-server depends on:
ii  libc6 2.17-97
ii  libpam0g  1.1.3-10
ii  libwrap0  7.6.q-24

dante-server recommends no packages.

dante-server suggests no packages.

-- Configuration Files:
/etc/danted.conf changed:
logoutput: stderr
internal: eth0 port = 1080
external: 198.20.106.155
method: pam
user.privileged: proxy
user.notprivileged: nobody
user.libwrap: nobody
client pass {
from: 0.0.0.0/0 port 1-65535 to: 0.0.0.0/0
method: pam
}


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dante
Source-Version: 1.4.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
dante, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 731...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated dante package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 17:14:40 +0300
Source: dante
Binary: libsocksd0 libsocksd0-dev libdsocksd0 dante-client dante-server
Architecture: source all amd64
Version: 1.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Description:
 dante-client - SOCKS wrapper for users behind a firewall
 dante-server - SOCKS (v4 and v5) proxy daemon (danted)
 libdsocksd0 - SOCKS library preloaded in user applications
 libsocksd0 - SOCKS library for packages built using libsocksd-dev
 libsocksd0-dev - Development files for compiling programs with SOCKS support
Closes: 626316 656096 715117 716681 731178 740749 776907
Changes:
 dante (1.4.1+dfsg-1) unstable; urgency=medium
 .
   * Fix FTBFS by depending on libtool-bin instead of libtool.
 Closes: #776907
   * Remove the obsolete DM-Upload-Allowed source control field.
   * Note the migration to my GitLab repository in the Vcs-* fields.
   * Use the default dpkg-dev source package compression method.
   * Drop the versions from the autotools-dev and dpkg-dev dependencies.
   * Fix the broken .so symlink in libsocksd0-dev.  Closes: #715117
   * Bump the debhelper compatibility level to 10:
 - install into the multiarch library directory
 - get the compiler and linker flags directly from debhelper
 - override the "experimental debhelper version" Lintian warning
 - drop the autotools-dev dependency and invocation, debhelper uses
   autoreconf automatically in level 10; do not override the Lintian
   "outdated autotools file" warnings, since it's wrong - see #820441
   * New upstream version:
 - Closes: #740749 (new upstream version)
 - Closes: #731178 (tries to dlopen a linker script)
 - rework some of the patches to modify the *.am files instead of
   the *.in ones; Closes: #716681
 - add a lot more filenames to debian/clean
 - put the preloaded libdsocksd back into its own package, complete
   with a SONAME, in preparation for socksify being able to select
   the one with the correct ABI/architecture; drop the 15-lib-dante-client
   patch 

Bug#776907: marked as done (dante: FTBFS due to libtool movement)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 17:49:16 +
with message-id 
and subject line Bug#776907: fixed in dante 1.4.1+dfsg-1
has caused the Debian Bug report #776907,
regarding dante: FTBFS due to libtool movement
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.)


-- 
776907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dante
Version: 1.2.2+dfsg-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 dante-client

Hi,

dante/experimental needs a libtool dependency update, things have moved
between packages some time ago already.

   dh_auto_build
make[1]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg'
Making all in include
make[2]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/include'
make  all-am
make[3]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/include'
make[3]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/include'
make[2]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/include'
Making all in libscompat
make[2]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/libscompat'
/usr/bin/libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. 
-I../include -I../include -I.  -D_FORTIFY_SOURCE=2 -DDEBUG=0 -DSOCKS_CLIENT=0 
-DSOCKS_SERVER=0 -DSOCKSLIBRARY_DYNAMIC=0 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security  -fPIE  -fstack-protector-strong  
-D_FORTIFY_SOURCE=2  -Wformat -Wformat-security -Werror=format-security
-pipe  -c -o issetugid.lo issetugid.c
/bin/bash: /usr/bin/libtool: No such file or directory
Makefile:312: recipe for target 'issetugid.lo' failed
make[2]: *** [issetugid.lo] Error 127
make[2]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/libscompat'
Makefile:271: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg'
dh_auto_build: make -j1 returned exit code 2
debian/rules:67: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package


Andreas
--- End Message ---
--- Begin Message ---
Source: dante
Source-Version: 1.4.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
dante, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 776...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated dante package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 17:14:40 +0300
Source: dante
Binary: libsocksd0 libsocksd0-dev libdsocksd0 dante-client dante-server
Architecture: source all amd64
Version: 1.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Description:
 dante-client - SOCKS wrapper for users behind a firewall
 dante-server - SOCKS (v4 and v5) proxy daemon (danted)
 libdsocksd0 - SOCKS library preloaded in user applications
 libsocksd0 - SOCKS library for packages built using libsocksd-dev
 libsocksd0-dev - Development files for compiling programs with SOCKS support
Closes: 626316 656096 715117 716681 731178 740749 776907
Changes:
 dante (1.4.1+dfsg-1) unstable; urgency=medium
 .
   * Fix FTBFS by depending on libtool-bin instead of libtool.
 Closes: #776907
   * Remove the obsolete DM-Upload-Allowed source control field.
   * Note the migration to my GitLab repository in the Vcs-* fields.
   * Use the default dpkg-dev source package compression method.
   * Drop the versions from the autotools-dev and dpkg-dev dependencies.
   * Fix the broken .so symlink in libsocksd0-dev.  Closes: #715117
   * Bump the debhelper compatibility level to 10:
 - install into the multiarch library directory
 - get the compiler and linker flags directly from debhelper
 - override the "experimental debhelper version" Lintian warning
 - drop the autotools-dev dependency and 

Bug#742566: marked as done (linuxtv-dvb-apps: FTBFS with libpng 1.6)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 17:29:22 +
with message-id 
and subject line Bug#742566: fixed in linuxtv-dvb-apps 1.1.1+rev1500-1.1
has caused the Debian Bug report #742566,
regarding linuxtv-dvb-apps: FTBFS with libpng 1.6
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.)


-- 
742566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source:   linuxtv-dvb-apps
Version:  1.1.1+rev1500-1
User: lib...@packages.debian.org
Usertags: libpng15-transition

Hi,

libpng maintainers have a plan transition of libpng16[0].

libpng16 is already installed in experimental, and we are re-building
the package depending on libpng16.
As a result, we checked that your package was FTBFS.
Would you check also in your environment?
And if you could confirm problem, could you fix this?

-

cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include
-D_FORTIFY_SOURCE=2  -c -o exp-txt.o exp-txt.c
cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include
-D_FORTIFY_SOURCE=2  -c -o exp-html.o exp-html.c
cc -O -g -w -DVERSION=\"1.7.0\" -DWITH_PNG -DUSE_LIBZVBI -I/include
-D_FORTIFY_SOURCE=2  -c -o exp-gfx.o exp-gfx.c
exp-gfx.c: In function 'png_open':
exp-gfx.c:172:22: error: 'Z_DEFAULT_COMPRESSION' undeclared (first use
in this function)
 D->compression = Z_DEFAULT_COMPRESSION;
  ^
exp-gfx.c:172:22: note: each undeclared identifier is reported only
once for each function it appears in
make[3]: *** [exp-gfx.o] Error 1
make[3]: Leaving directory
`/tmp/buildd/linuxtv-dvb-apps-1.1.1+rev1500/util/alevt'

-

Best regards,
  Nobuhiro

[0]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650601

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
--- End Message ---
--- Begin Message ---
Source: linuxtv-dvb-apps
Source-Version: 1.1.1+rev1500-1.1

We believe that the bug you reported is fixed in the latest version of
linuxtv-dvb-apps, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 742...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
linuxtv-dvb-apps package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Apr 2016 18:12:02 +0200
Source: linuxtv-dvb-apps
Binary: dvb-apps
Architecture: source
Version: 1.1.1+rev1500-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Gianfranco Costamagna 
Description:
 dvb-apps   - Digital Video Broadcasting (DVB) applications
Closes: 742566
Changes:
 linuxtv-dvb-apps (1.1.1+rev1500-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/patches/fix-build-libpng16.patch: fix build with
 libpng16 (Closes: #742566)
Checksums-Sha1:
 0f6aa48ed6513375510be34bf58d4770594b3819 2176 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.dsc
 66c37f5be6a2b513c92c5c06f72e872585525bc1 18152 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.debian.tar.xz
Checksums-Sha256:
 ef96c89b5dbf414cd3189a2b0cc88e37f55f44a999751250f83f6f1bf42e9834 2176 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.dsc
 93f62a98fa8cf46c367ae5cf62235e2a5f17246c8059c1029ba63fd180c0b279 18152 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.debian.tar.xz
Files:
 b2ca92408d7610adccdfcc9f9254965b 2176 video extra 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.dsc
 b210196df8331e28ba2429153c5f290d 18152 video extra 
linuxtv-dvb-apps_1.1.1+rev1500-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXBodUAAoJEPNPCXROn13ZXN8QAL296Rt1spJQgouVd0JL0ESm
d1P85fUuB1u5NY21GUtDlF7xZP1yt0WiUPdecVTvCw44HbjloMtZs/Sh0awMElV6
jFWbzkmEnHCKY7qOwb7vQ/tZiv4chdnV5jzwLVv7SOnqh4223nfBtoKvqAs2Pw2H
QaEHNrFkXvPzeH5THfC/XmRpFvjxJdDnqLLwQmTY3UGOl3NDQquEKBKkp8lBFOLQ
6IwcmzYJ8/t1SOBAHnGXZqFNCm84lzUSiLWmjjZv8xNpCEs8W7+mRqctAgfVdCA3
cTTVSwx2ysuNNd3nPwVCZSwu89uHWPCcvzWOqC7aaQ3gATT2S0bMR5niGCw5jHpv
4Mqlaj8Y6OrztoUcdRoeXLWXoT/zshAC83z1nMevlA1ccFId6GPK67YdoA0NiMzT
hf2CgjYrhnc2rT1B6s/FJJsP2lrd2mTab7hw6kxQhJwFHyEcqr76y4uQcrUzaF14

Bug#820530: pdal: FTBFS because of openmpi

2016-04-09 Thread Sebastiaan Couwenberg
Control: tags -1 pending

On 04/09/2016 05:58 PM, Sebastiaan Couwenberg wrote:
> On 04/09/2016 05:50 PM, Mattia Rizzolo wrote:
>> On Sat, Apr 09, 2016 at 03:10:23PM +, Gianfranco Costamagna wrote:
>>> the build log has many
>>> make[4]: *** No rule to make target 
>>> '/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
>>> 'lib/libpdal_plugin_filter_voxelgrid.so'.  Stop.
>>> make[4]: *** No rule to make target 
>>> '/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
>>> 'lib/libpdal_plugin_filter_pclblock.so'.  Stop.
>>>
>>>
>>> Seems that the above file is provided by libhdf5-openmpi-dev, maybe it
>>> is just a matter of a new dependency to add, but due to the libpng16
>>> transition I'm sorry but I can't investigate more.
>>>
>>> #820113 #820098 are similar issues
>>
>> actually, I think this is not something that should be fixed in the
>> package, but it's a problem of libvtk6-dev missing a dependency.  See
>> #820113 (marked as blocking of this bug).
>>
>> For now I'd do nothing but wait on vtk6 maintainers to react to that
>> bug.
> 
> Because vtk & vtk6 are such problematic packages, I dropped the PCL
> support in PDAL 1.2.0 to not have VTK in the dependency chain.
> 
> Unfortunately pdal (1.2.0-1~exp1) is still in NEW. If that takes too
> long I'll drop it from the 1.1.0 package in unstable too.

I decided not to wait for that after all, pdal (1.1.0-5) is on its way
to unstable.

Kind Regards,

Bas

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



signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#820530: pdal: FTBFS because of openmpi

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 pending
Bug #820530 [src:pdal] pdal: FTBFS because of openmpi
Added tag(s) pending.

-- 
820530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#814879: marked as done (timidity: FTBFS with libpng16 / does not specify libpng-dev B-D)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 16:44:54 +
with message-id 
and subject line Bug#814879: fixed in timidity 2.13.2-40.4
has caused the Debian Bug report #814879,
regarding timidity: FTBFS with libpng16 / does not specify libpng-dev B-D
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.)


-- 
814879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timidity
Severity: serious
User: lib...@packages.debian.org
Usertags: libpng16-transition
Control: block 650601 by -1 

Dear maintainer,

Currently we are preparing the transition of libpng1.2 to libpng1.6.
The transition bug is #650601.

A rebuild of all packages depending on libpng-dev and
libpng(3,12,12-0)-dev has been done. However, as timidity is not explicitly
B-D on libpng-dev (but using it) this package has slipped through the net.

The result with buildlogs can be
found here: https://libpng.sviech.de/

The package FTBFS with the new libpng API. The buildlog is here:
https://libpng.sviech.de/timidity.build

relevant snippet:

x_sherry.c: In function 'png_read_func':
x_sherry.c:785:41: error: dereferencing pointer to incomplete type 'png_struct 
{aka struct png_struct_def}'
 tf = (struct timidity_file *)png_ptr->io_ptr;
 ^
x_sherry.c: In function 'sry_load_png':
x_sherry.c:912:6: warning: implicit declaration of function 'png_set_dither' 
[-Wimplicit-function-declaration]
  png_set_dither(pngPtr, palette,
  ^

As the start of the transition is imminent, I filed this bug with a RC severity.

You can get hints about how to fix it here:
here: https://titanpad.com/libpng16-transistion (look for fixing recipes)

PLEASE also explitly B-D on libpng-dev. (please do not use versioned dev 
packages)


Thanks

-- 
tobi


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: timidity
Source-Version: 2.13.2-40.4

We believe that the bug you reported is fixed in the latest version of
timidity, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 814...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated timidity package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 07 Apr 2016 14:04:03 +
Source: timidity
Binary: timidity timidity-interfaces-extra timidity-el timidity-daemon
Architecture: source
Version: 2.13.2-40.4
Distribution: unstable
Urgency: medium
Maintainer: Geoffrey Thomas 
Changed-By: Mattia Rizzolo 
Description:
 timidity   - Software sound renderer (MIDI sequencer, MOD player)
 timidity-daemon - runs TiMidity++ as a system-wide MIDI sequencer
 timidity-el - Emacs front end to Timidity++
 timidity-interfaces-extra - TiMidity++ extra user interfaces
Closes: 814879
Changes:
 timidity (2.13.2-40.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with libpng 1.5 and newer.  Closes: #814879
   * Run wrap-and-sort.
   * Explicit Build-Depends on libpng-dev
Checksums-Sha1:
 f023874d5318f668f11fe171033f95da6ddaaa77 2340 timidity_2.13.2-40.4.dsc
 1ca87d746290515825fc278e5b9124eaf43ef3e9 97416 
timidity_2.13.2-40.4.debian.tar.xz
Checksums-Sha256:
 26b356ab699fbd9f61dc03484ed3a938ccddf2272fa157184ba529034aeda4a0 2340 
timidity_2.13.2-40.4.dsc
 d54f8990e5b5dd652ad40b6fabc763750a75be740df9a7cc6c67d4f0f168330d 97416 
timidity_2.13.2-40.4.debian.tar.xz
Files:
 5def5df99226095deff943aabcf3c07a 2340 sound optional timidity_2.13.2-40.4.dsc
 6fdb9b6607fcc694c76ac42d642028a2 97416 sound optional 
timidity_2.13.2-40.4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2


Bug#820329: marked as done (playonlinux: FTBFS in sid: dh_install: Cannot find (any matches for) "plugins/TransgamingCedega*" and "plugins/Wine*")

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 16:40:02 +
with message-id 
and subject line Bug#820329: fixed in playonlinux 4.2.10-2
has caused the Debian Bug report #820329,
regarding playonlinux: FTBFS in sid: dh_install: Cannot find (any matches for) 
"plugins/TransgamingCedega*" and "plugins/Wine*"
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.)


-- 
820329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: playonlinux
Version: 4.2.10-1
Severity: serious
Justification: fails to build from source

Hi,

playonlinux FTBFS in current sid with current debhelper:

 fakeroot debian/rules binary
dh binary --with python2
   dh_testroot
   dh_prep
   dh_auto_install
   debian/rules override_dh_install
make[1]: Entering directory '/build/playonlinux-4.2.10'
dh_install
dh_install: Cannot find (any matches for) "plugins/TransgamingCedega*" (tried 
in "." and "debian/tmp")
dh_install: Cannot find (any matches for) "plugins/Wine*" (tried in "." and 
"debian/tmp")
dh_install: missing files, aborting
debian/rules:19: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 255
make[1]: Leaving directory '/build/playonlinux-4.2.10'
debian/rules:13: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2


Andreas


playonlinux_4.2.10-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: playonlinux
Source-Version: 4.2.10-2

We believe that the bug you reported is fixed in the latest version of
playonlinux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 820...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bertrand Marc  (supplier of updated playonlinux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 15:55:40 +0200
Source: playonlinux
Binary: playonlinux
Architecture: source all
Version: 4.2.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Bertrand Marc 
Description:
 playonlinux - front-end for Wine
Closes: 820329
Changes:
 playonlinux (4.2.10-2) unstable; urgency=medium
 .
   * Remove obsolete plugins from debian/playonlinux.install (Closes: #820329).
   * Standards version 3.9.8: no changes needed.
   * Update years in debian/copyright.
Checksums-Sha1:
 d4f65e3f10560e8a5001a2dbe2f2f82da27186c9 1997 playonlinux_4.2.10-2.dsc
 68dfb7069978d063529228243a291af08126db1a 6900 
playonlinux_4.2.10-2.debian.tar.xz
 ab9fcdd8aae0f49107dddb4297b130dbcab8bdef 1056700 playonlinux_4.2.10-2_all.deb
Checksums-Sha256:
 7130536f47f859ccfdf1ba057cd1778f74f65b75388809a23560f1540e11e871 1997 
playonlinux_4.2.10-2.dsc
 10e6dd5451cb4c867a257f1c9a1bde9350eeae8aedae4c27772bd5a02489b33b 6900 
playonlinux_4.2.10-2.debian.tar.xz
 2df2376297f9d262d3acf76ce474fd3b0d8d0d898e27711ced8b7d6a322bf0cd 1056700 
playonlinux_4.2.10-2_all.deb
Files:
 a2f83686950122e0931972e808816059 1997 contrib/otherosfs optional 
playonlinux_4.2.10-2.dsc
 574c1e0ecf3c9627f8a92ddc04ea3ebe 6900 contrib/otherosfs optional 
playonlinux_4.2.10-2.debian.tar.xz
 2dc6fa36cdd48758914c920dd0e3965a 1056700 contrib/otherosfs optional 
playonlinux_4.2.10-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXCQvXAAoJEKBKs7rb4mPuoNoP/iHVIacwhbymfKMAfK5zYH++
TAe4pxLhyf+wsHCxcgRImhoEss3YnFK7rgsc9Ii105f+7kzcagScnBTW3FjdrPFJ
EvBZcWt48HsU4IOnDmebpuhIp4VijnVMgEqiwF+x75R4mXsphShBHOEBq2D1B9ky
AZ9zY2x/kQa7d9tNu+2ic1Zabte3xWj90c0B45ob5tRFycCb94lDHd+yEeRNFHgP
LN/IU2KicNfXtaXm2U0FIoZGE/jjc6UkB+IpwfhdYVi6GBHel0H4RgDOeOPweQAz
UupS72/blIrczLv4519FraCrMbTKZWbHi1UmoXgcGyCSHidzRNwfjeO5vz4oeR6z
Zq4On+nxm6FdLCFpoYuUlx5X0KuLD51C0aIF9r4PI1/mut5CJSpHXfaaDDG4LjDe
tYNl2su9QfCtv3kZ+qNcEL+Tih1La9tE1bjuz9YKv/bLFiWpHMUTYwo2yIzI8pZi
Ex6uxU7jtQpqwdJtTrv2w/3SeYxCSSPO/+IlKz9+o/+ixG2CBziuMEXcyg97ldEo
TMkpNZAEoLyI7q2bl+57B5+vnv51KmGWuUkN4ZmBMj06bF2/K6SkWtjFf+Vt3eAl

Bug#818515: marked as done (iulib: FTBFS: '/usr/share/libtool/config/ltmain.sh': No such file or directory)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 16:31:54 +
with message-id 
and subject line Bug#818515: fixed in iulib 0.3-3.3
has caused the Debian Bug report #818515,
regarding iulib: FTBFS: '/usr/share/libtool/config/ltmain.sh': No such file or 
directory
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.)


-- 
818515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iulib
Version: 0.3-3.2
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[1]: Entering directory '/<>'
> mv aclocal.m4 aclocal.m4.old
> mv configure configure.old
> mv Makefile.in Makefile.in.old
> cp /usr/share/libtool/config/ltmain.sh .
> cp: cannot stat '/usr/share/libtool/config/ltmain.sh': No such file or 
> directory
> debian/rules:14: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'
> debian/rules:11: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: iulib
Source-Version: 0.3-3.3

We believe that the bug you reported is fixed in the latest version of
iulib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated iulib 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 Apr 2016 11:02:55 +0200
Source: iulib
Binary: libiulib0 libiulib-dev
Architecture: source
Version: 0.3-3.3
Distribution: unstable
Urgency: medium
Maintainer: Jeffrey Ratcliffe 
Changed-By: Gianfranco Costamagna 
Description:
 libiulib-dev - C++ library of image understanding-related algorithms -- 
developm
 libiulib0  - C++ library of image understanding-related algorithms
Closes: 818515
Changes:
 iulib (0.3-3.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to autoreconf (Closes: #818515).
   * Bump compat level to 9 and std-version to 3.9.8.
Checksums-Sha1:
 ef305881e0b308d0df9478981dc13511e4177227 1894 iulib_0.3-3.3.dsc
 6ded9a1e92b13fd54d29484b8fd9ffe68ecbac3e 4128 iulib_0.3-3.3.debian.tar.xz
Checksums-Sha256:
 3aa6b4967d6656feb4c3289b3ac50b5bc736b559e0917ba7fc1b3ebf97be71dc 1894 
iulib_0.3-3.3.dsc
 2da1ff5c67dc138f33bae91ba42c81694fff684c4237c353f75e6aa279e188c2 4128 
iulib_0.3-3.3.debian.tar.xz
Files:
 1ff7a47c173a93a52882a05a3447a579 1894 graphics optional iulib_0.3-3.3.dsc
 c5adad115f444213bf5418977888d049 4128 graphics optional 
iulib_0.3-3.3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXB3PrAAoJEPNPCXROn13ZEycP/jP4aML+0KnqwfChR8ZpOxj8
1nJ24j/oWTuuO62MOak2aA4n4huPYEUp2TVFwO9hfIMG2mb4o1SKvgNO/JvEC8gW
LPWzvnrYR61CMTfirFsi0ir4ajxcxK6zA6fxBk9+mPAq+RMYhs5ToTyAQtSH7bwM
dXZbCpdWMC8G8PgRB6RpK8Pr4espeDm9iHgsbJ3sMhGK7wP3wLjDXWrdsZAhrhg2
jq/mfSQa07Rpfnzxj6pqciucfS4WI22Y2Tb+cxyh4QcQ4IhRi0YzFStJ2n6I8oVX
coTC0k7HdurOvMJ8kjI2FUEJlnwl7FfKfmAVOGnLI1imPL5L+lxgi3nZHxtx+M9A
gxbcvg2+y18t9PPUIU5PwgORfj7AGXCr6lvlaGj7pVLTcgRRBXxmM26C4fLUn8lC
m2eMwefaWBb00TLF8TA8eAb+Y/yk45T047fQlhS5UFPtO3FCTtlsiN44aiSE+tb0
SEtFKV1Nkoa5mdm80SxN2RAfwzBaWmgEKmc1hOrf/H5Jf1ywGxHUuimf0wAJ8ejB
ZKC2aPlF4VbmbUInJRNopt/tmXMdWA3df0UpvqwtGJr7AB7p9LP/b4/bdXcVzSQZ
sHYyqSDteJxIXjp/JvybC2FXI69JP+gpTxb2jL6EPCEAFiDb5u9b+rWbKYYkKp5S
nQCJbnnNAtmoUmR0bbiy
=KHhb
-END PGP SIGNATURE End Message ---


Bug#820530: pdal: FTBFS because of openmpi

2016-04-09 Thread Sebastiaan Couwenberg
On 04/09/2016 05:50 PM, Mattia Rizzolo wrote:
> On Sat, Apr 09, 2016 at 03:10:23PM +, Gianfranco Costamagna wrote:
>> the build log has many
>> make[4]: *** No rule to make target 
>> '/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
>> 'lib/libpdal_plugin_filter_voxelgrid.so'.  Stop.
>> make[4]: *** No rule to make target 
>> '/usr/lib/aarch64-linux-gnu/hdf5/openmpi/lib/libhdf5.so', needed by 
>> 'lib/libpdal_plugin_filter_pclblock.so'.  Stop.
>>
>>
>> Seems that the above file is provided by libhdf5-openmpi-dev, maybe it
>> is just a matter of a new dependency to add, but due to the libpng16
>> transition I'm sorry but I can't investigate more.
>>
>> #820113 #820098 are similar issues
> 
> actually, I think this is not something that should be fixed in the
> package, but it's a problem of libvtk6-dev missing a dependency.  See
> #820113 (marked as blocking of this bug).
> 
> For now I'd do nothing but wait on vtk6 maintainers to react to that
> bug.

Because vtk & vtk6 are such problematic packages, I dropped the PCL
support in PDAL 1.2.0 to not have VTK in the dependency chain.

Unfortunately pdal (1.2.0-1~exp1) is still in NEW. If that takes too
long I'll drop it from the 1.1.0 package in unstable too.

Kind Regards,

Bas

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



signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#820530: pdal: FTBFS because of openmpi

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #820530 [src:pdal] pdal: FTBFS because of openmpi
Severity set to 'serious' from 'normal'
> block -1 by 820113
Bug #820530 [src:pdal] pdal: FTBFS because of openmpi
820530 was not blocked by any bugs.
820530 was not blocking any bugs.
Added blocking bug(s) of 820530: 820113

-- 
820530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#819890: haskell-http2: FTBFS on armel buildds (was: Re: Please give back haskell-http2 on armel)

2016-04-09 Thread Clint Adams
On Mon, Apr 04, 2016 at 05:24:38AM +, Riku Voipio wrote:
> The reproducible-builds is armhf while the failing ones are armel. The 
> regression
> appears to be a code change in haskell-http2 between 1.0.4 and 1.3.1:
> 
> https://buildd.debian.org/status/logs.php?pkg=haskell-http2=armel

I think we can be pretty confident that the bug is in ghc or doctest.



Processed: Re: Bug#820113: No rule to make target '/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #820113 [libvtk6-dev] No rule to make target 
'/usr/lib/x86_64-linux-gnu/hdf5/openmpi/lib/libhdf5.so'
Severity set to 'serious' from 'normal'

-- 
820113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820531: yafc: FTBFS: m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN

2016-04-09 Thread Chris Lamb
Source: yafc
Version: 1.3.7-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

yafc fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'yafc-build-deps' in 
'../yafc-build-deps_1.3.7-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package yafc-build-deps.
  (Reading database ... 22985 files and directories currently installed.)
  Preparing to unpack yafc-build-deps_1.3.7-1_all.deb ...
  Unpacking yafc-build-deps (1.3.7-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
autoconf-archive comerr-dev krb5-multidev libbsd-dev libedit-dev libedit2
libelf1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgssrpc4
libkadm5clnt-mit9 libkadm5srv-mit9 libkdb5-8 libkrb5-dev libpcre16-3
libpcre3-dev libpcre32-3 libpcrecpp0v5 libssh-4 libssh-dev libssl-dev
libtext-unidecode-perl libtinfo-dev libxml-libxml-perl
libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl pkg-config
tex-common texinfo ucf zlib1g-dev
  Suggested packages:
doc-base krb5-doc libglib2.0-doc krb5-user libssh-doc texlive-base
texlive-latex-base texlive-generic-recommended texinfo-doc-nonfree
  Recommended packages:
libssl-doc libxml-sax-expat-perl
  The following NEW packages will be installed:
autoconf-archive comerr-dev krb5-multidev libbsd-dev libedit-dev libedit2
libelf1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgssrpc4
libkadm5clnt-mit9 libkadm5srv-mit9 libkdb5-8 libkrb5-dev libpcre16-3
libpcre3-dev libpcre32-3 libpcrecpp0v5 libssh-4 libssh-dev libssl-dev
libtext-unidecode-perl libtinfo-dev libxml-libxml-perl
libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl pkg-config
tex-common texinfo ucf zlib1g-dev
  0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 14.7 MB of archives.
  After this operation, 56.7 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 autoconf-archive all 
20150925-1 [688 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 
libtext-unidecode-perl all 1.27-1 [103 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 
libxml-namespacesupport-perl all 1.11-1 [14.8 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libxml-sax-base-perl 
all 1.07-1 [23.1 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 ucf all 3.0036 [70.2 
kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libxml-sax-perl all 
0.99+dfsg-2 [68.3 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libxml-libxml-perl 
amd64 2.0123+dfsg-1+b1 [340 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 tex-common all 6.05 
[564 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 texinfo amd64 
6.1.0.dfsg.1-5 [1263 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libbsd-dev amd64 
0.8.2-1 [177 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libedit2 amd64 
3.1-20150325-1+b1 [85.2 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160319-1 [77.6 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libedit-dev amd64 
3.1-20150325-1+b1 [101 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 libelf1 amd64 
0.165-3 [169 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 libglib2.0-data all 
2.48.0-1 [2494 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 libglib2.0-bin amd64 
2.48.0-1 [1618 kB]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libpcre16-3 amd64 
2:8.38-3.1 [252 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 libpcre32-3 amd64 
2:8.38-3.1 [244 kB]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 libpcrecpp0v5 amd64 
2:8.38-3.1 [150 kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libpcre3-dev amd64 
2:8.38-3.1 [633 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 pkg-config amd64 
0.29-3 [62.3 kB]
  Get:22 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b1 [206 kB]
  Get:23 http://httpredir.debian.org/debian sid/main amd64 libglib2.0-dev amd64 
2.48.0-1 [2956 kB]
  Get:24 http://httpredir.debian.org/debian sid/main amd64 libgssrpc4 amd64 
1.13.2+dfsg-5 [87.4 kB]
  Get:25 

Bug#820329: playonlinux: FTBFS in sid: dh_install: Cannot find (any matches for) "plugins/TransgamingCedega*" and "plugins/Wine*"

2016-04-09 Thread Bertrand Marc
Le 09/04/2016 06:50, Denis Briand a écrit :
> tags 820329 patch
> thanks
> 
> Hello,
> Upstream did removed these two plugin and add another one.
> You should try this trivial patch.
> 
> Best regards
> 
> Denis Briand  

Thank you Denis. It was indeed quite simple. It is now uploaded to unstable.

Best regards,
Bertrand



Bug#820528: libicu-4.2-java: Needs to Replace / Conflict with libicu4j-java

2016-04-09 Thread Hilko Bengen
Package: libicu-4.2-java
Version: 4.2.1.1-4
Severity: grave

libicu4j-4.2-java cannot be installed on a system where libicu4j-java is
installed:

Preparing to unpack .../libicu4j-4.2-java_4.2.1.1-4_all.deb ...
Unpacking libicu4j-4.2-java (4.2.1.1-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libicu4j-4.2-java_4.2.1.1-4_all.deb (--unpack):
 trying to overwrite 
'/usr/share/maven-repo/com/ibm/icu/icu4j/4.2.1.1/icu4j-4.2.1.1.pom', which is 
also in package libicu4j-java 4.2.1.1-3

Please add the necessary "Conflicts", "Replaces".

Cheers,
-Hilko



Bug#820464: linux-headers-4.4.0-1-grsec-amd64: missing scripts/Makefile.gcc-plugins

2016-04-09 Thread Yves-Alexis Perez
Control: retitle -1 no support for building external plugin
Control: reassign -1 src:linux-grsec
Control: severity -1 wishlist

On ven., 2016-04-08 at 19:01 +0200, Andreas Beckmann wrote:
> Package: linux-headers-4.4.0-1-grsec-amd64
> Version: 4.4.6-1+grsec201604021734+1
> Severity: serious
> Justification: fails to build from source

Hi,

that's not a correct justification neither a correct severity.
> 
> Hi,
> 
> external modules cannot be built against the 4.4.0-1-grsec-amd64 kernel
> (but this worked for 4.3.0-1-grsec-amd64):

Actually I don't think it ever worked, but if it really was working on 4.3.0-
1-grsec-amd64 I'm interested.

> 
> DKMS make.log for r8168-8.041.01 for kernel 4.4.0-1-grsec-amd64 (x86_64)
> Fri Apr  8 16:54:52 UTC 2016
> make: Entering directory '/usr/src/linux-headers-4.4.0-1-grsec-amd64'
> /usr/src/linux-headers-4.4.0-1-common-grsec/Makefile:625:
> scripts/Makefile.gcc-plugins: No such file or directory
> make[2]: *** No rule to make target 'scripts/Makefile.gcc-plugins'.  Stop.

Yes, external/DKMS plugins are not yet supported, feel free to help if you
want this to happen. I think we'd need to provide our own linux-kbuild in
order to ship some files (like Makefile.gcc-plugins).

Regards,
-- 
Yves-Alexis



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


Processed: Re: Bug#820464: linux-headers-4.4.0-1-grsec-amd64: missing scripts/Makefile.gcc-plugins

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 no support for building external plugin
Bug #820464 [linux-headers-4.4.0-1-grsec-amd64] 
linux-headers-4.4.0-1-grsec-amd64: missing scripts/Makefile.gcc-plugins
Changed Bug title to 'no support for building external plugin' from 
'linux-headers-4.4.0-1-grsec-amd64: missing scripts/Makefile.gcc-plugins'.
> reassign -1 src:linux-grsec
Bug #820464 [linux-headers-4.4.0-1-grsec-amd64] no support for building 
external plugin
Bug reassigned from package 'linux-headers-4.4.0-1-grsec-amd64' to 
'src:linux-grsec'.
No longer marked as found in versions linux-grsec/4.4.6-1+grsec201604021734+1.
Ignoring request to alter fixed versions of bug #820464 to the same values 
previously set
> severity -1 wishlist
Bug #820464 [src:linux-grsec] no support for building external plugin
Severity set to 'wishlist' from 'serious'

-- 
820464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#819174: marked as done (Fails to start with missing cache dir)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 13:24:37 +
with message-id 
and subject line Bug#819174: fixed in mopidy 2.0.0-2
has caused the Debian Bug report #819174,
regarding Fails to start with missing cache dir
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.)


-- 
819174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mopidy
Version: 2.0.0-1
Severity: serious

If /var/cache/mopidy is lost (e.g. because /var/cache is a tmpfs),
mopidy fails to start. However, the FHS specifies that files in
/var/cache must not be relied upon.

The problem here is that mopidy tries to create the directory but
fails due to permissions. Either the directory needs to be created
by systemd, or another location used as a fallback (e.g. /run).

● mopidy.service - Mopidy music server
   Loaded: loaded (/lib/systemd/system/mopidy.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Thu 2016-03-24 14:49:15 CET; 8s ago
  Process: 21065 ExecStart=/usr/bin/mopidy --config 
/usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf (code=exited
 Main PID: 21065 (code=exited, status=1/FAILURE)

Mar 24 14:49:15 albatross mopidy[21065]:   File 
"/usr/lib/python2.7/dist-packages/mopidy/__main__.py", line 147, 
Mar 24 14:49:15 albatross mopidy[21065]: 
path.get_or_create_dir(config['core']['cache_dir'])
Mar 24 14:49:15 albatross mopidy[21065]:   File 
"/usr/lib/python2.7/dist-packages/mopidy/internal/path.py", line 
Mar 24 14:49:15 albatross mopidy[21065]: os.makedirs(dir_path, 0o755)
Mar 24 14:49:15 albatross mopidy[21065]:   File "/usr/lib/python2.7/os.py", 
line 157, in makedirs
Mar 24 14:49:15 albatross mopidy[21065]: mkdir(name, mode)
Mar 24 14:49:15 albatross mopidy[21065]: OSError: [Errno 13] Permission denied: 
'/var/cache/mopidy'
Mar 24 14:49:15 albatross systemd[1]: mopidy.service: Main process exited, 
code=exited, status=1/FAILURE
Mar 24 14:49:15 albatross systemd[1]: mopidy.service: Unit entered failed state.
Mar 24 14:49:15 albatross systemd[1]: mopidy.service: Failed with result 
'exit-code'.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mopidy depends on:
ii  adduser  3.114
ii  debconf [debconf-2.0]1.5.59
ii  gir1.2-gst-plugins-base-1.0  1.6.3-1
ii  gir1.2-gstreamer-1.0 1.6.3-1
ii  gstreamer1.0-plugins-good1.6.3-1
ii  gstreamer1.0-plugins-ugly1.6.3-1
ii  init-system-helpers  1.29
ii  lsb-base 9.20160110
ii  python-gst-1.0   1.6.2-1+b1
ii  python-pkg-resources 20.3.1-1
ii  python-pykka 1.2.1-2
ii  python-requests  2.9.1-3
ii  python-tornado   4.2.1-1+b2
pn  python:any   

Versions of packages mopidy recommends:
pn  gstreamer1.0-alsa
ii  gstreamer1.0-pulseaudio  1.6.3-1
ii  gstreamer1.0-tools   1.6.3-1

Versions of packages mopidy suggests:
pn  mopidy-doc  

-- Configuration Files:
/etc/mopidy/mopidy.conf [Errno 13] Permission denied: u'/etc/mopidy/mopidy.conf'

-- debconf-show failed


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
Source: mopidy
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
mopidy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 819...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stein Magnus Jodal  (supplier of updated mopidy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN 

Bug#817307: ufraw: diff for NMU version 0.20-3.1

2016-04-09 Thread Tobias Frost
Control: tags 817307 + patch
Control: tags 817307 + pending

Dear maintainer,

I've prepared an NMU for ufraw (versioned as 0.20-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u ufraw-0.20/debian/changelog ufraw-0.20/debian/changelog
--- ufraw-0.20/debian/changelog
+++ ufraw-0.20/debian/changelog
@@ -1,3 +1,11 @@
+ufraw (0.20-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove dh_desktop call (NOOP since 2009) to fix the FTBFS seen
+during a binNNU (Closes: #817307)
+
+ -- Tobias Frost   Sat, 09 Apr 2016 14:25:38 +0200
+
 ufraw (0.20-3) unstable; urgency=low
 
   * dcraw.cc: Apply patch from
diff -u ufraw-0.20/debian/rules ufraw-0.20/debian/rules
--- ufraw-0.20/debian/rules
+++ ufraw-0.20/debian/rules
@@ -111,7 +111,6 @@
mv $(CURDIR)/debian/ufraw-batch/usr/share/man/man1/ufraw.1 
$(CURDIR)/debian/ufraw-batch/usr/share/man/man1/ufraw-batch.1
dh_link
dh_strip
-   dh_desktop -pufraw
dh_compress
dh_fixperms
dh_installdeb



Processed: ufraw: diff for NMU version 0.20-3.1

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> tags 817307 + patch
Bug #817307 [src:ufraw] ufraw: Removal of dh_desktop
Added tag(s) patch.
> tags 817307 + pending
Bug #817307 [src:ufraw] ufraw: Removal of dh_desktop
Added tag(s) pending.

-- 
817307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

2016-04-09 Thread Riku Voipio
On Sat, Apr 09, 2016 at 12:02:44PM +0200, Graham Inggs wrote:
> On 9 April 2016 at 00:53, peter green  wrote:
> > It would be useful if someone can reproduce the issue and get a dissasembly
> > of the failure location.
> 
> I hope this is useful.  I'll leave my screen session on abel.d.o. open
> in case I need to fetch more information.
> 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
> WARNING: unable to determine host cpu name.
> exports.jl
> essentials.jl
> docs/bootstrap.jl
> base.jl
> reflection.jl
> build_h.jl
> version_git.jl
 
> Program received signal SIGILL, Illegal instruction.
> 0x940c5060 in julia_call_891 ()
> (gdb) disassemble $pc
> Dump of assembler code for function julia_call_891:
>0x940c5054 <+0>: push{r4, r5, r6, lr}
>0x940c5058 <+4>: vpush   {d8}
>0x940c505c <+8>: mov r0, #40 ; 0x28
> => 0x940c5060 <+12>:vorrd8, d0, d0

And yes, vorr is an NEON instruction.

>0x940c5064 <+16>:mov r4, r3
>0x940c5068 <+20>:mov r5, r2
>0x940c506c <+24>:mov r6, r1
>0x940c5070 <+28>:bl  0x940c50c4
>0x940c5074 <+32>:movwr1, #16432  ; 0x4030
>0x940c5078 <+36>:movtr1, #37900  ; 0x940c
>0x940c507c <+40>:ldr r1, [r1]
>0x940c5080 <+44>:stmda   r0, {r1, r6}
>0x940c5084 <+48>:ldr r1, [sp, #24]
>0x940c5088 <+52>:str r5, [r0, #4]
>0x940c508c <+56>:str r4, [r0, #8]
>0x940c5090 <+60>:str r1, [r0, #12]
>0x940c5094 <+64>:ldr r1, [sp, #28]
>0x940c5098 <+68>:str r1, [r0, #16]
>0x940c509c <+72>:ldrbr1, [sp, #32]
>0x940c50a0 <+76>:and r1, r1, #1
>0x940c50a4 <+80>:strbr1, [r0, #20]
>0x940c50a8 <+84>:ldr r1, [sp, #36]   ; 0x24
>0x940c50ac <+88>:str r1, [r0, #24]
>0x940c50b0 <+92>:vstrd8, [r0, #32]
>0x940c50b4 <+96>:vpop{d8}
>0x940c50b8 <+100>:   pop {r4, r5, r6, pc}
> End of assembler dump.

 



Processed: tagging 818072

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 818072 + stretch sid
Bug #818072 [src:warzone2100] warzone2100: FTBFS in stretch (new flex)
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

2016-04-09 Thread Aurelien Jarno
control: retitle -1 openmpi: please remove mips chrpath workaround
control: severity -1 minor

On 2016-04-09 09:38, Gilles Filippini wrote:
> Control: reopen -1
> 
> On Fri, 8 Apr 2016 13:34:04 +0200 Emilio Pozuelo Monfort
>  wrote:
> > On Fri, 8 Apr 2016 12:16:47 +0200 Alastair McKinstry
> >  wrote:
> > > 
> > > >> OpenMPI maintainers (and anyone else affected):
> > > >> One possible workaround is to use chrpath -r ""  on mips*
> > > >> architectures until this is fixed since that command does not cause any
> > > >> tags to be moved. It has a tiny performance penalty but should
> > > >> otherwise work properly.
> > > > Thanks for the workaround.
> > > >
> > > > Aurelien
> > > >
> > > Thanks.
> > > I've tested this fix within openmpi on mips (works) and have uploaded a
> > > new version with
> > > the workaround.
> > 
> > Thanks! Unfortunately you forgot to apply this same workaround to mipsel and
> > mips64el. Could you apply it in those architectures as well?
> 
> Reopening, until the problem is fixed for mipsel and mip64el.

The chrpath issue has been fixed, I have scheduled binNMUs to get a
fixed openmpi on mipsel and mips64el

I am keeping this bug open with severity minor to not forget to remove
the workaround that has been added (thanks for that). There is no
urgency for it, it can wait other changes.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature


Processed: Re: Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 openmpi: please remove mips chrpath workaround
Bug #818909 [libopenmpi-dev] libopenmpi-dev: [mips*] mpicc.openmpi unusable
Changed Bug title to 'openmpi: please remove mips chrpath workaround' from 
'libopenmpi-dev: [mips*] mpicc.openmpi unusable'.
> severity -1 minor
Bug #818909 [libopenmpi-dev] openmpi: please remove mips chrpath workaround
Severity set to 'minor' from 'grave'

-- 
818909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820498: tachyon: FTBFS with libpng16 on mipsel

2016-04-09 Thread Emilio Pozuelo Monfort
On Sat, 09 Apr 2016 09:26:58 +0200 Tobias Frost  wrote:
> Source: tachyon
> Severity: serious
> Justification: FTBFS but did in the past
> 
> Dear maintainer,
> 
> the package FTBFS with libpng 1.6 on mipsel (release arch) and others
> non-release archs (mips64el and sh4) (it built on mipsel in the past, so it is
> RC)
> 
> Note that hppa also shows a very similar error, which was not binNMUed. So it
> might be that the problem is not related to the library tansition.
> 
> Buildlog for mips: 
> 
> https://buildd.debian.org/status/fetch.php?pkg=tachyon=mipsel=0.99~b6%2Bdsx-4%2Bb1=1460116130
> 
> Buildd page:
> https://buildd.debian.org/status/package.php?p=tachyon
> 
> snippet: 
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0 missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0 missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0 missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0-dev missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0-dev missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so
> dh_install: Cannot find (any matches for) 
> "usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so" (tried in "." and 
> "debian/tmp")
> dh_install: libtachyon-openmpi-0-dev missing files: 
> usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so
> dh_install: missing files, aborting
> debian/rules:59: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 2

This is caused by #818909, which has just been fixed in chrpath. The necessary
rebuilds will be scheduled soon.

Cheers,
Emilio



Bug#814316: New Flash player is available -- fixes a security issue

2016-04-09 Thread Thomas Renard
... again:


sudo update-flashplugin-nonfree --status   1
Flash Player version installed on this system  : 11.2.202.577
Flash Player version available on upstream site: 11.2.202.616
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50

fixes ancountable CVEs, Zeordays...

https://helpx.adobe.com/security/products/flash-player/apsb16-10.html



Bug#704206: marked as done (teem: FTBFS[any-i386]: testsuite failures)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:04:00 +
with message-id 
and subject line Bug#704206: fixed in teem 1.11.0~svn6057-1.1
has caused the Debian Bug report #704206,
regarding teem: FTBFS[any-i386]: testsuite failures
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.)


-- 
704206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:teem
Version: 1.11.0~svn5906-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!

Your package failed to build on the buildds:

77% tests passed, 8 tests failed out of 35

Total Test time (real) =  24.32 sec

The following tests FAILED:
  9 - trand (Failed)
 20 - probeScl (Failed)
 26 - kernall (Failed)
 30 - probeSS_cos02 (Failed)
 31 - probeSS_cos04 (Failed)
 32 - probeSS_cos10 (Failed)
 34 - probeSS_ctmr04 (Failed)
 35 - probeSS_ctmr10 (Failed)
Errors while running CTest
make: *** [build/libteem2] Error 8

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=teem=i386=1.11.0%7Esvn5906-1=1357758591

Regards

Christoph
--- End Message ---
--- Begin Message ---
Source: teem
Source-Version: 1.11.0~svn6057-1.1

We believe that the bug you reported is fixed in the latest version of
teem, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 704...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated teem package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 10:34:39 +0200
Source: teem
Binary: libteem-dev teem-apps libteem2 libteem2-dbg
Architecture: source
Version: 1.11.0~svn6057-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Frost 
Description:
 libteem-dev - Tools to process and visualize scientific data and images - devel
 libteem2   - Tools to process and visualize scientific data and images - runti
 libteem2-dbg - debugging symbols for libteem2
 teem-apps  - Tools to process and visualize scientific data and images - comma
Closes: 704206 820503
Changes:
 teem (1.11.0~svn6057-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use -ffloat-store (i386) and -ffp-contract=off on certain archs to fix
 testsuite failures due to rounding issues. Thanks to Adam Conrad and Erwan
 Prioul for the patch (Closes: #704206)
   * Make build verbose (Closes: #820503)
Checksums-Sha1:
 09c7a8f1bdf651a78db0c7a58593ef7c0ea915e1 2192 teem_1.11.0~svn6057-1.1.dsc
 8cafe05dbf07b767affc167b085b52818019b347 22268 
teem_1.11.0~svn6057-1.1.debian.tar.xz
Checksums-Sha256:
 fd0b063a2b654baa04d0a222eb650253d95524ecbeabe71f877a5664b9230457 2192 
teem_1.11.0~svn6057-1.1.dsc
 b2b015275abfb212f4c72936392d808067913a804e5538606d518da4f6d35267 22268 
teem_1.11.0~svn6057-1.1.debian.tar.xz
Files:
 ea71c7991983ccb57da1f9d0c78da76a 2192 libs optional teem_1.11.0~svn6057-1.1.dsc
 590efa6d3a68b582bd86f212278731ed 22268 libs optional 
teem_1.11.0~svn6057-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXCL9LAAoJEJFk+h0XvV028P0P/0kgTow6GAqE3QPVby56FZiy
6DUc8/qprzZtWooAPsbk9pXJidR0nRSOr6d142huTLzCskb1t5ppODJPX2gvAamK
Ntmd7y3JmYG27ZR++DSO5BFF6NzUkGsmDG35RGA5OXARp3YtpmVCMH/OmRVrUBA6
VmS38Qei1bf8HvVpdaNdNQY+W6b3TJazSvOy2wGHhPnhKR7ldtArwOE0nQU65eCk
gwJPdGmwlV4/cY/R4Oc+AXqnZwF9q1qQiaZbf0DkGXt+RF22zx87RKdpOaSulSIe
M0cMpeONXBda6kezK0D5yDLAIAa2CHrBgHIYvGEhaKbpPrOo7TeJ0kboqzd34oh6
g2RlPx1uYu/wadW3MNgYbVQPI7r6enJrIA4QWI9nlWLo61txfihHAhrsJbSpRn89
zNBgskoDtpc31UQCk9ZaGEn7LZoVMrGvc0fSRJTwogm95OJlEsiNLnkitoe/Es/L
VJx2pjcZYvU0sHPI+xrJKK7OKorBuFLo3H/QR1o5ige5xqUofO3a9Wg49/ceOsrz
an3YjwssNfTi8XiVJZ0hphCM5i5if5rOaLeythI7n3TooQCK8Khy6BOJxNUx+FYG
r5egIJ1y0CP5YO44pg7NFY3QU8N1aQ6kUO0Y4CBpJWPWt9CywnZgWwpre3mUBDK3
m7BYecIgtspIzH8vvECb
=WmON
-END PGP SIGNATURE End Message ---


Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

2016-04-09 Thread Graham Inggs
On 9 April 2016 at 00:53, peter green  wrote:
> It would be useful if someone can reproduce the issue and get a dissasembly
> of the failure location.

I hope this is useful.  I'll leave my screen session on abel.d.o. open
in case I need to fetch more information.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
WARNING: unable to determine host cpu name.
exports.jl
essentials.jl
docs/bootstrap.jl
base.jl
reflection.jl
build_h.jl
version_git.jl

Program received signal SIGILL, Illegal instruction.
0x940c5060 in julia_call_891 ()
(gdb) disassemble $pc
Dump of assembler code for function julia_call_891:
   0x940c5054 <+0>: push{r4, r5, r6, lr}
   0x940c5058 <+4>: vpush   {d8}
   0x940c505c <+8>: mov r0, #40 ; 0x28
=> 0x940c5060 <+12>:vorrd8, d0, d0
   0x940c5064 <+16>:mov r4, r3
   0x940c5068 <+20>:mov r5, r2
   0x940c506c <+24>:mov r6, r1
   0x940c5070 <+28>:bl  0x940c50c4
   0x940c5074 <+32>:movwr1, #16432  ; 0x4030
   0x940c5078 <+36>:movtr1, #37900  ; 0x940c
   0x940c507c <+40>:ldr r1, [r1]
   0x940c5080 <+44>:stmda   r0, {r1, r6}
   0x940c5084 <+48>:ldr r1, [sp, #24]
   0x940c5088 <+52>:str r5, [r0, #4]
   0x940c508c <+56>:str r4, [r0, #8]
   0x940c5090 <+60>:str r1, [r0, #12]
   0x940c5094 <+64>:ldr r1, [sp, #28]
   0x940c5098 <+68>:str r1, [r0, #16]
   0x940c509c <+72>:ldrbr1, [sp, #32]
   0x940c50a0 <+76>:and r1, r1, #1
   0x940c50a4 <+80>:strbr1, [r0, #20]
   0x940c50a8 <+84>:ldr r1, [sp, #36]   ; 0x24
   0x940c50ac <+88>:str r1, [r0, #24]
   0x940c50b0 <+92>:vstrd8, [r0, #32]
   0x940c50b4 <+96>:vpop{d8}
   0x940c50b8 <+100>:   pop {r4, r5, r6, pc}
End of assembler dump.



Bug#813429: marked as done (python-numpy: breaks the CI tests of some installed packages)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813932: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813932,
regarding python-numpy: breaks the CI tests of some installed packages
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.)


-- 
813932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-numpy
Version: 1:1.11.0~b2-1
Severity: serious
Forwarded: Yes

The numpy beta release breaks the CI tests of some astrophysics
packages, namely python-astropy, sunpy, and wcsaxes. Upstream bug
reports are here:

https://github.com/numpy/numpy/issues/7161
https://github.com/numpy/numpy/issues/7162
https://github.com/numpy/numpy/issues/7164

Although it is not everywhere clear whether this is a problem of numpy
or the astrophysics packages, I'd ask not to enter testing unless the
problems are resolved by numpy or clarified that the dependent packages
shall fix it.

Would it generally be possible to put beta releases to experimental
instead of unstable?

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 

Bug#813932: marked as done (sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816574: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816574,
regarding sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis 
(`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
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.)


-- 
816574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunpy
Version: 0.6.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sunpy fails to build from source in unstable/amd64:

  [..]

  --
  new_delt : float
  New delta between consecutive values.
  """
  if self.t_delt == new_delt:
  return self
  factor = self.t_delt / float(new_delt)
  
  # The last data-point does not change!
  new_size = floor((self.shape[1] - 1) * factor + 1) # pylint: 
disable=E1101
  data = ndimage.zoom(self.data, (1, new_size / self.shape[1])) # 
pylint: disable=E1101
  
  params = self._get_params()
  params.update({
  'time_axis': np.linspace(
  self.time_axis[0],
  >   self.time_axis[(new_size - 1) * new_delt / self.t_delt],
  new_size
  ),
  't_delt': new_delt,
  })
  E   IndexError: only integers, slices (`:`), ellipsis (`...`), 
numpy.newaxis (`None`) and integer or boolean arrays are valid indices
  
  sunpy/spectra/spectrogram.py:960: IndexError
  __ test_combine_freqs 
__
  
  def test_combine_freqs():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  >   comb = LinearTimeSpectrogram.combine_frequencies([spec, spec2])
  
  sunpy/spectra/tests/test_spectrogram.py:575: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  sunpy/spectra/spectrogram.py:1162: in combine_frequencies
  specs = cls.intersect_time(specs)
  sunpy/spectra/spectrogram.py:1144: in intersect_time
  cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs]
  sunpy/spectra/spectrogram.py:601: in __getitem__
  return self._slice(key[0], key[1])
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = 
  y_range = slice(None, None, None), x_range = slice(0.0, None, None)
  
  def _slice(self, y_range, x_range):
  """Return new spectrogram reduced to the values passed
  as slices. Implementation detail."""
  >   data = self.data[y_range, x_range]
  E   IndexError: invalid slice
  
  sunpy/spectra/spectrogram.py:339: IndexError
  _ test_intersect_time 
__
  
  def test_intersect_time():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  901,
  0.25
  )
  
  one, other = LinearTimeSpectrogram.intersect_time(
  >   [spec, spec2]
  )
  
  sunpy/spectra/tests/test_spectrogram.py:632: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#816574: marked as done (FTBFS: object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813932: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813932,
regarding FTBFS: object cannot be interpreted as an index
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.)


-- 
813932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sunpy
Version: 0.6.1-2
Severity: serious

sunpy fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> # level operations
> return img.reshape(img.shape[0] / dimensions[0],
>dimensions[0],
>img.shape[1] / dimensions[1],
> >  dimensions[1])
> E   TypeError: 'numpy.float64' object cannot be interpreted as an index

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 df6376fe6b1016cadb5287e04c0723b6b164010621497edbda8941a7a0320ba8 1769292 
python3-numpy_1.11.0-1_amd64.deb
Files:
 bda73188757b92bad2234ab4dfa92724 2661 python optional python-numpy_1.11.0-1.dsc
 

Bug#816369: marked as done (TypeError: 'float' object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816369: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816369,
regarding TypeError: 'float' object cannot be interpreted as an index
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.)


-- 
816369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

healpy fails to build from source in unstable/amd64:

  [..]

  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values of
  existing keywords and appending new keywords otherwise; similar to
  `dict.update`.
  
  `update` accepts either a dict-like object or an iterable.  In the
  former case the keys must be header keywords and the values may be
  either scalar values or (value, comment) tuples.  In the case of 
an
  iterable the items must be (keyword, value) tuples or (keyword, 
value,
  comment) tuples.
  
  Arbitrary arguments are also accepted, in which case the update() 
is
  called again with the kwargs dict as its only argument.  That is,
  
  ::
  
  >>> header.update(NAXIS1=100, NAXIS2=100)
  
  is equivalent to::
  
  >>> header.update({'NAXIS1': 100, 'NAXIS2': 100})
  """
  
  if args:
  other = args[0]
  else:
  other = None
  
  def update_from_dict(k, v):
  if not isinstance(v, tuple):
  card = Card(k, v)
  elif 0 < len(v) <= 2:
  card = Card(*((k,) + v))
  else:
  raise ValueError(
  'Header update value for key %r is invalid; the value '
  'must be either a scalar, a 1-tuple containing the '
  'scalar value, or a 2-tuple containing the value and a '
  'comment string.' % k)
  self._update(card)
  
  if other is None:
  pass
  elif hasattr(other, 'iteritems'):
  for k, v in other.iteritems():
  update_from_dict(k, v)
  elif hasattr(other, 'keys'):
  for k in other.keys():
  update_from_dict(k, other[k])
  else:
  for idx, card in enumerate(other):
  if isinstance(card, Card):
  self._update(card)
  elif isinstance(card, tuple) and (1 < len(card) <= 3):
  self._update(Card(*card))
  else:
  raise ValueError(
  'Header update sequence item #%d is invalid; the '
  'item must either be a 2-tuple containing a keyword '
  'and value, or a 3-tuple containing a keyword, '
  >   'value, and comment string.' % idx)
  E   ValueError: Header update sequence item #0 is invalid; 
the item must either be a 2-tuple containing a keyword and value, or a 3-tuple 
containing a keyword, value, and comment string.
  
  /usr/lib/python2.7/dist-packages/pyfits/header.py:1017: ValueError
   TestReadWriteCl.test_write_read_cl_II 
_
  
  self = 
  
  def test_write_read_cl_II(self):
  cl = np.arange(1025, dtype=np.double)
  >   write_cl("test_cl.fits", cl)
  
  healpy/test/test_fitsfunc.py:84: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  healpy/fitsfunc.py:86: in write_cl
  tbhdu.header.update('CREATOR','healpy')
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = XTENSION= 'BINTABLE'   / binary table extension
   ...FORM1  = 'D   '   
 
  args = ('CREATOR', 'healpy'), kwargs = {}, other = 'CREATOR'
  update_from_dict = , idx = 0
  card = 'C'
  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values 

Bug#816574: marked as done (FTBFS: object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816369: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816369,
regarding FTBFS: object cannot be interpreted as an index
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.)


-- 
816369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sunpy
Version: 0.6.1-2
Severity: serious

sunpy fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> # level operations
> return img.reshape(img.shape[0] / dimensions[0],
>dimensions[0],
>img.shape[1] / dimensions[1],
> >  dimensions[1])
> E   TypeError: 'numpy.float64' object cannot be interpreted as an index

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 df6376fe6b1016cadb5287e04c0723b6b164010621497edbda8941a7a0320ba8 1769292 
python3-numpy_1.11.0-1_amd64.deb
Files:
 bda73188757b92bad2234ab4dfa92724 2661 python optional python-numpy_1.11.0-1.dsc
 

Bug#813932: marked as done (sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813932: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813932,
regarding sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis 
(`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
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.)


-- 
813932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunpy
Version: 0.6.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sunpy fails to build from source in unstable/amd64:

  [..]

  --
  new_delt : float
  New delta between consecutive values.
  """
  if self.t_delt == new_delt:
  return self
  factor = self.t_delt / float(new_delt)
  
  # The last data-point does not change!
  new_size = floor((self.shape[1] - 1) * factor + 1) # pylint: 
disable=E1101
  data = ndimage.zoom(self.data, (1, new_size / self.shape[1])) # 
pylint: disable=E1101
  
  params = self._get_params()
  params.update({
  'time_axis': np.linspace(
  self.time_axis[0],
  >   self.time_axis[(new_size - 1) * new_delt / self.t_delt],
  new_size
  ),
  't_delt': new_delt,
  })
  E   IndexError: only integers, slices (`:`), ellipsis (`...`), 
numpy.newaxis (`None`) and integer or boolean arrays are valid indices
  
  sunpy/spectra/spectrogram.py:960: IndexError
  __ test_combine_freqs 
__
  
  def test_combine_freqs():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  >   comb = LinearTimeSpectrogram.combine_frequencies([spec, spec2])
  
  sunpy/spectra/tests/test_spectrogram.py:575: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  sunpy/spectra/spectrogram.py:1162: in combine_frequencies
  specs = cls.intersect_time(specs)
  sunpy/spectra/spectrogram.py:1144: in intersect_time
  cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs]
  sunpy/spectra/spectrogram.py:601: in __getitem__
  return self._slice(key[0], key[1])
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = 
  y_range = slice(None, None, None), x_range = slice(0.0, None, None)
  
  def _slice(self, y_range, x_range):
  """Return new spectrogram reduced to the values passed
  as slices. Implementation detail."""
  >   data = self.data[y_range, x_range]
  E   IndexError: invalid slice
  
  sunpy/spectra/spectrogram.py:339: IndexError
  _ test_intersect_time 
__
  
  def test_intersect_time():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  901,
  0.25
  )
  
  one, other = LinearTimeSpectrogram.intersect_time(
  >   [spec, spec2]
  )
  
  sunpy/spectra/tests/test_spectrogram.py:632: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#813932: marked as done (sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816369: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816369,
regarding sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis 
(`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
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.)


-- 
816369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunpy
Version: 0.6.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sunpy fails to build from source in unstable/amd64:

  [..]

  --
  new_delt : float
  New delta between consecutive values.
  """
  if self.t_delt == new_delt:
  return self
  factor = self.t_delt / float(new_delt)
  
  # The last data-point does not change!
  new_size = floor((self.shape[1] - 1) * factor + 1) # pylint: 
disable=E1101
  data = ndimage.zoom(self.data, (1, new_size / self.shape[1])) # 
pylint: disable=E1101
  
  params = self._get_params()
  params.update({
  'time_axis': np.linspace(
  self.time_axis[0],
  >   self.time_axis[(new_size - 1) * new_delt / self.t_delt],
  new_size
  ),
  't_delt': new_delt,
  })
  E   IndexError: only integers, slices (`:`), ellipsis (`...`), 
numpy.newaxis (`None`) and integer or boolean arrays are valid indices
  
  sunpy/spectra/spectrogram.py:960: IndexError
  __ test_combine_freqs 
__
  
  def test_combine_freqs():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  >   comb = LinearTimeSpectrogram.combine_frequencies([spec, spec2])
  
  sunpy/spectra/tests/test_spectrogram.py:575: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  sunpy/spectra/spectrogram.py:1162: in combine_frequencies
  specs = cls.intersect_time(specs)
  sunpy/spectra/spectrogram.py:1144: in intersect_time
  cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs]
  sunpy/spectra/spectrogram.py:601: in __getitem__
  return self._slice(key[0], key[1])
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = 
  y_range = slice(None, None, None), x_range = slice(0.0, None, None)
  
  def _slice(self, y_range, x_range):
  """Return new spectrogram reduced to the values passed
  as slices. Implementation detail."""
  >   data = self.data[y_range, x_range]
  E   IndexError: invalid slice
  
  sunpy/spectra/spectrogram.py:339: IndexError
  _ test_intersect_time 
__
  
  def test_intersect_time():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  901,
  0.25
  )
  
  one, other = LinearTimeSpectrogram.intersect_time(
  >   [spec, spec2]
  )
  
  sunpy/spectra/tests/test_spectrogram.py:632: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#816369: marked as done (TypeError: 'float' object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813932: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813932,
regarding TypeError: 'float' object cannot be interpreted as an index
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.)


-- 
813932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

healpy fails to build from source in unstable/amd64:

  [..]

  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values of
  existing keywords and appending new keywords otherwise; similar to
  `dict.update`.
  
  `update` accepts either a dict-like object or an iterable.  In the
  former case the keys must be header keywords and the values may be
  either scalar values or (value, comment) tuples.  In the case of 
an
  iterable the items must be (keyword, value) tuples or (keyword, 
value,
  comment) tuples.
  
  Arbitrary arguments are also accepted, in which case the update() 
is
  called again with the kwargs dict as its only argument.  That is,
  
  ::
  
  >>> header.update(NAXIS1=100, NAXIS2=100)
  
  is equivalent to::
  
  >>> header.update({'NAXIS1': 100, 'NAXIS2': 100})
  """
  
  if args:
  other = args[0]
  else:
  other = None
  
  def update_from_dict(k, v):
  if not isinstance(v, tuple):
  card = Card(k, v)
  elif 0 < len(v) <= 2:
  card = Card(*((k,) + v))
  else:
  raise ValueError(
  'Header update value for key %r is invalid; the value '
  'must be either a scalar, a 1-tuple containing the '
  'scalar value, or a 2-tuple containing the value and a '
  'comment string.' % k)
  self._update(card)
  
  if other is None:
  pass
  elif hasattr(other, 'iteritems'):
  for k, v in other.iteritems():
  update_from_dict(k, v)
  elif hasattr(other, 'keys'):
  for k in other.keys():
  update_from_dict(k, other[k])
  else:
  for idx, card in enumerate(other):
  if isinstance(card, Card):
  self._update(card)
  elif isinstance(card, tuple) and (1 < len(card) <= 3):
  self._update(Card(*card))
  else:
  raise ValueError(
  'Header update sequence item #%d is invalid; the '
  'item must either be a 2-tuple containing a keyword '
  'and value, or a 3-tuple containing a keyword, '
  >   'value, and comment string.' % idx)
  E   ValueError: Header update sequence item #0 is invalid; 
the item must either be a 2-tuple containing a keyword and value, or a 3-tuple 
containing a keyword, value, and comment string.
  
  /usr/lib/python2.7/dist-packages/pyfits/header.py:1017: ValueError
   TestReadWriteCl.test_write_read_cl_II 
_
  
  self = 
  
  def test_write_read_cl_II(self):
  cl = np.arange(1025, dtype=np.double)
  >   write_cl("test_cl.fits", cl)
  
  healpy/test/test_fitsfunc.py:84: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  healpy/fitsfunc.py:86: in write_cl
  tbhdu.header.update('CREATOR','healpy')
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = XTENSION= 'BINTABLE'   / binary table extension
   ...FORM1  = 'D   '   
 
  args = ('CREATOR', 'healpy'), kwargs = {}, other = 'CREATOR'
  update_from_dict = , idx = 0
  card = 'C'
  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values 

Bug#813429: marked as done (python-numpy: breaks the CI tests of some installed packages)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816369: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816369,
regarding python-numpy: breaks the CI tests of some installed packages
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.)


-- 
816369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-numpy
Version: 1:1.11.0~b2-1
Severity: serious
Forwarded: Yes

The numpy beta release breaks the CI tests of some astrophysics
packages, namely python-astropy, sunpy, and wcsaxes. Upstream bug
reports are here:

https://github.com/numpy/numpy/issues/7161
https://github.com/numpy/numpy/issues/7162
https://github.com/numpy/numpy/issues/7164

Although it is not everywhere clear whether this is a problem of numpy
or the astrophysics packages, I'd ask not to enter testing unless the
problems are resolved by numpy or clarified that the dependent packages
shall fix it.

Would it generally be possible to put beta releases to experimental
instead of unstable?

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 

Bug#816369: marked as done (TypeError: 'float' object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813429: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813429,
regarding TypeError: 'float' object cannot be interpreted as an index
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.)


-- 
813429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

healpy fails to build from source in unstable/amd64:

  [..]

  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values of
  existing keywords and appending new keywords otherwise; similar to
  `dict.update`.
  
  `update` accepts either a dict-like object or an iterable.  In the
  former case the keys must be header keywords and the values may be
  either scalar values or (value, comment) tuples.  In the case of 
an
  iterable the items must be (keyword, value) tuples or (keyword, 
value,
  comment) tuples.
  
  Arbitrary arguments are also accepted, in which case the update() 
is
  called again with the kwargs dict as its only argument.  That is,
  
  ::
  
  >>> header.update(NAXIS1=100, NAXIS2=100)
  
  is equivalent to::
  
  >>> header.update({'NAXIS1': 100, 'NAXIS2': 100})
  """
  
  if args:
  other = args[0]
  else:
  other = None
  
  def update_from_dict(k, v):
  if not isinstance(v, tuple):
  card = Card(k, v)
  elif 0 < len(v) <= 2:
  card = Card(*((k,) + v))
  else:
  raise ValueError(
  'Header update value for key %r is invalid; the value '
  'must be either a scalar, a 1-tuple containing the '
  'scalar value, or a 2-tuple containing the value and a '
  'comment string.' % k)
  self._update(card)
  
  if other is None:
  pass
  elif hasattr(other, 'iteritems'):
  for k, v in other.iteritems():
  update_from_dict(k, v)
  elif hasattr(other, 'keys'):
  for k in other.keys():
  update_from_dict(k, other[k])
  else:
  for idx, card in enumerate(other):
  if isinstance(card, Card):
  self._update(card)
  elif isinstance(card, tuple) and (1 < len(card) <= 3):
  self._update(Card(*card))
  else:
  raise ValueError(
  'Header update sequence item #%d is invalid; the '
  'item must either be a 2-tuple containing a keyword '
  'and value, or a 3-tuple containing a keyword, '
  >   'value, and comment string.' % idx)
  E   ValueError: Header update sequence item #0 is invalid; 
the item must either be a 2-tuple containing a keyword and value, or a 3-tuple 
containing a keyword, value, and comment string.
  
  /usr/lib/python2.7/dist-packages/pyfits/header.py:1017: ValueError
   TestReadWriteCl.test_write_read_cl_II 
_
  
  self = 
  
  def test_write_read_cl_II(self):
  cl = np.arange(1025, dtype=np.double)
  >   write_cl("test_cl.fits", cl)
  
  healpy/test/test_fitsfunc.py:84: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  healpy/fitsfunc.py:86: in write_cl
  tbhdu.header.update('CREATOR','healpy')
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = XTENSION= 'BINTABLE'   / binary table extension
   ...FORM1  = 'D   '   
 
  args = ('CREATOR', 'healpy'), kwargs = {}, other = 'CREATOR'
  update_from_dict = , idx = 0
  card = 'C'
  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values 

Bug#816369: marked as done (TypeError: 'float' object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816574: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816574,
regarding TypeError: 'float' object cannot be interpreted as an index
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.)


-- 
816574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

healpy fails to build from source in unstable/amd64:

  [..]

  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values of
  existing keywords and appending new keywords otherwise; similar to
  `dict.update`.
  
  `update` accepts either a dict-like object or an iterable.  In the
  former case the keys must be header keywords and the values may be
  either scalar values or (value, comment) tuples.  In the case of 
an
  iterable the items must be (keyword, value) tuples or (keyword, 
value,
  comment) tuples.
  
  Arbitrary arguments are also accepted, in which case the update() 
is
  called again with the kwargs dict as its only argument.  That is,
  
  ::
  
  >>> header.update(NAXIS1=100, NAXIS2=100)
  
  is equivalent to::
  
  >>> header.update({'NAXIS1': 100, 'NAXIS2': 100})
  """
  
  if args:
  other = args[0]
  else:
  other = None
  
  def update_from_dict(k, v):
  if not isinstance(v, tuple):
  card = Card(k, v)
  elif 0 < len(v) <= 2:
  card = Card(*((k,) + v))
  else:
  raise ValueError(
  'Header update value for key %r is invalid; the value '
  'must be either a scalar, a 1-tuple containing the '
  'scalar value, or a 2-tuple containing the value and a '
  'comment string.' % k)
  self._update(card)
  
  if other is None:
  pass
  elif hasattr(other, 'iteritems'):
  for k, v in other.iteritems():
  update_from_dict(k, v)
  elif hasattr(other, 'keys'):
  for k in other.keys():
  update_from_dict(k, other[k])
  else:
  for idx, card in enumerate(other):
  if isinstance(card, Card):
  self._update(card)
  elif isinstance(card, tuple) and (1 < len(card) <= 3):
  self._update(Card(*card))
  else:
  raise ValueError(
  'Header update sequence item #%d is invalid; the '
  'item must either be a 2-tuple containing a keyword '
  'and value, or a 3-tuple containing a keyword, '
  >   'value, and comment string.' % idx)
  E   ValueError: Header update sequence item #0 is invalid; 
the item must either be a 2-tuple containing a keyword and value, or a 3-tuple 
containing a keyword, value, and comment string.
  
  /usr/lib/python2.7/dist-packages/pyfits/header.py:1017: ValueError
   TestReadWriteCl.test_write_read_cl_II 
_
  
  self = 
  
  def test_write_read_cl_II(self):
  cl = np.arange(1025, dtype=np.double)
  >   write_cl("test_cl.fits", cl)
  
  healpy/test/test_fitsfunc.py:84: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  healpy/fitsfunc.py:86: in write_cl
  tbhdu.header.update('CREATOR','healpy')
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = XTENSION= 'BINTABLE'   / binary table extension
   ...FORM1  = 'D   '   
 
  args = ('CREATOR', 'healpy'), kwargs = {}, other = 'CREATOR'
  update_from_dict = , idx = 0
  card = 'C'
  
  def update(self, *args, **kwargs):
  """
  Update the Header with new keyword values, updating the values 

Bug#816574: marked as done (FTBFS: object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816574: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816574,
regarding FTBFS: object cannot be interpreted as an index
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.)


-- 
816574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sunpy
Version: 0.6.1-2
Severity: serious

sunpy fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> # level operations
> return img.reshape(img.shape[0] / dimensions[0],
>dimensions[0],
>img.shape[1] / dimensions[1],
> >  dimensions[1])
> E   TypeError: 'numpy.float64' object cannot be interpreted as an index

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 df6376fe6b1016cadb5287e04c0723b6b164010621497edbda8941a7a0320ba8 1769292 
python3-numpy_1.11.0-1_amd64.deb
Files:
 bda73188757b92bad2234ab4dfa92724 2661 python optional python-numpy_1.11.0-1.dsc
 

Bug#816574: marked as done (FTBFS: object cannot be interpreted as an index)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813429: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813429,
regarding FTBFS: object cannot be interpreted as an index
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.)


-- 
813429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sunpy
Version: 0.6.1-2
Severity: serious

sunpy fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> # level operations
> return img.reshape(img.shape[0] / dimensions[0],
>dimensions[0],
>img.shape[1] / dimensions[1],
> >  dimensions[1])
> E   TypeError: 'numpy.float64' object cannot be interpreted as an index

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 df6376fe6b1016cadb5287e04c0723b6b164010621497edbda8941a7a0320ba8 1769292 
python3-numpy_1.11.0-1_amd64.deb
Files:
 bda73188757b92bad2234ab4dfa92724 2661 python optional python-numpy_1.11.0-1.dsc
 

Bug#813429: marked as done (python-numpy: breaks the CI tests of some installed packages)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#816574: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #816574,
regarding python-numpy: breaks the CI tests of some installed packages
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.)


-- 
816574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-numpy
Version: 1:1.11.0~b2-1
Severity: serious
Forwarded: Yes

The numpy beta release breaks the CI tests of some astrophysics
packages, namely python-astropy, sunpy, and wcsaxes. Upstream bug
reports are here:

https://github.com/numpy/numpy/issues/7161
https://github.com/numpy/numpy/issues/7162
https://github.com/numpy/numpy/issues/7164

Although it is not everywhere clear whether this is a problem of numpy
or the astrophysics packages, I'd ask not to enter testing unless the
problems are resolved by numpy or clarified that the dependent packages
shall fix it.

Would it generally be possible to put beta releases to experimental
instead of unstable?

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 

Bug#813932: marked as done (sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis (`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813429: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813429,
regarding sunpy: FTBFS: IndexError: only integers, slices (`:`), ellipsis 
(`...`), numpy.newaxis (`None`) and integer or boolean arrays are valid indices
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.)


-- 
813429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sunpy
Version: 0.6.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

sunpy fails to build from source in unstable/amd64:

  [..]

  --
  new_delt : float
  New delta between consecutive values.
  """
  if self.t_delt == new_delt:
  return self
  factor = self.t_delt / float(new_delt)
  
  # The last data-point does not change!
  new_size = floor((self.shape[1] - 1) * factor + 1) # pylint: 
disable=E1101
  data = ndimage.zoom(self.data, (1, new_size / self.shape[1])) # 
pylint: disable=E1101
  
  params = self._get_params()
  params.update({
  'time_axis': np.linspace(
  self.time_axis[0],
  >   self.time_axis[(new_size - 1) * new_delt / self.t_delt],
  new_size
  ),
  't_delt': new_delt,
  })
  E   IndexError: only integers, slices (`:`), ellipsis (`...`), 
numpy.newaxis (`None`) and integer or boolean arrays are valid indices
  
  sunpy/spectra/spectrogram.py:960: IndexError
  __ test_combine_freqs 
__
  
  def test_combine_freqs():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, image.shape[1] - 1, image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  >   comb = LinearTimeSpectrogram.combine_frequencies([spec, spec2])
  
  sunpy/spectra/tests/test_spectrogram.py:575: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  sunpy/spectra/spectrogram.py:1162: in combine_frequencies
  specs = cls.intersect_time(specs)
  sunpy/spectra/spectrogram.py:1144: in intersect_time
  cut = [sp[:, (start - sp.t_init) / delt:] for sp in specs]
  sunpy/spectra/spectrogram.py:601: in __getitem__
  return self._slice(key[0], key[1])
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  self = 
  y_range = slice(None, None, None), x_range = slice(0.0, None, None)
  
  def _slice(self, y_range, x_range):
  """Return new spectrogram reduced to the values passed
  as slices. Implementation detail."""
  >   data = self.data[y_range, x_range]
  E   IndexError: invalid slice
  
  sunpy/spectra/spectrogram.py:339: IndexError
  _ test_intersect_time 
__
  
  def test_intersect_time():
  image = np.random.rand(5, 3600)
  spec = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([8, 6, 4, 2, 0]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  900,
  0.25
  )
  image = np.random.rand(5, 3600)
  spec2 = LinearTimeSpectrogram(image,
  np.linspace(0, 0.25 * (image.shape[1] - 1), image.shape[1]),
  np.array([9, 7, 5, 3, 1]),
  datetime(2010, 1, 1, 0, 15),
  datetime(2010, 1, 1, 0, 30),
  901,
  0.25
  )
  
  one, other = LinearTimeSpectrogram.intersect_time(
  >   [spec, spec2]
  )
  
  sunpy/spectra/tests/test_spectrogram.py:632: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Bug#813429: marked as done (python-numpy: breaks the CI tests of some installed packages)

2016-04-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Apr 2016 10:00:55 +
with message-id 
and subject line Bug#813429: fixed in python-numpy 1:1.11.0-1
has caused the Debian Bug report #813429,
regarding python-numpy: breaks the CI tests of some installed packages
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.)


-- 
813429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-numpy
Version: 1:1.11.0~b2-1
Severity: serious
Forwarded: Yes

The numpy beta release breaks the CI tests of some astrophysics
packages, namely python-astropy, sunpy, and wcsaxes. Upstream bug
reports are here:

https://github.com/numpy/numpy/issues/7161
https://github.com/numpy/numpy/issues/7162
https://github.com/numpy/numpy/issues/7164

Although it is not everywhere clear whether this is a problem of numpy
or the astrophysics packages, I'd ask not to enter testing unless the
problems are resolved by numpy or clarified that the dependent packages
shall fix it.

Would it generally be possible to put beta releases to experimental
instead of unstable?

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: python-numpy
Source-Version: 1:1.11.0-1

We believe that the bug you reported is fixed in the latest version of
python-numpy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-numpy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 Apr 2016 09:47:40 +0100
Source: python-numpy
Binary: python-numpy python-numpy-dbg python3-numpy python3-numpy-dbg 
python-numpy-doc
Architecture: source amd64 all
Version: 1:1.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Description:
 python-numpy - Numerical Python adds a fast array facility to the Python 
languag
 python-numpy-dbg - Fast array facility to the Python language (debug extension)
 python-numpy-doc - NumPy documentation
 python3-numpy - Fast array facility to the Python 3 language
 python3-numpy-dbg - Fast array facility to the Python 3 language (debug 
extension)
Closes: 813429 813932 816369 816574
Changes:
 python-numpy (1:1.11.0-1) unstable; urgency=medium
 .
   [ Sandro Tosi ]
   * New upstream release: Closes: #816369, #813429, #813932, #816574
   * debian/control
 - bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
Checksums-Sha1:
 761309df812f89a57af98b06124256f6381548a6 2661 python-numpy_1.11.0-1.dsc
 3e43596cba1d5df4002dd0c87d4041f31ea6e1b5 4169494 
python-numpy_1.11.0.orig.tar.gz
 76e3eb031cc337b52f1944536993c985b40b0f1e 141028 
python-numpy_1.11.0-1.debian.tar.xz
 75f8d925cd2547997617653c1ac6596ba79c8f61 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 65dbc3c2f3ffeedc8fe629664125c585e4a16896 3573596 
python-numpy-doc_1.11.0-1_all.deb
 2b29971160f9b3d75d504359ead256c6b1cb94f7 1769802 
python-numpy_1.11.0-1_amd64.deb
 6d717f6930e5357e81115c916109e2e403ea7bd5 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 fa4f501571a0c0d6ddf75d6797ee3482c30c12e1 1769292 
python3-numpy_1.11.0-1_amd64.deb
Checksums-Sha256:
 783c07956322fa7e69123faccf074f2e52ca16fca91c9552b3b295737494 2661 
python-numpy_1.11.0-1.dsc
 a1d1268d200816bfb9727a7a27b78d8e37ecec2e4d5ebd33eb64e2789e0db43e 4169494 
python-numpy_1.11.0.orig.tar.gz
 ce6c761d2d555d8c0c522ce2734ae5fb406294a01bb46d685c980df94b9ca23c 141028 
python-numpy_1.11.0-1.debian.tar.xz
 c8a022b74c5591db466137a1e2c740fa99fd8cb1453a7d895ce4364161ec299d 3554480 
python-numpy-dbg_1.11.0-1_amd64.deb
 522a4b35163ef06cb13911769d39e4281ce5dcfac7c96164ee33974e248e11ce 3573596 
python-numpy-doc_1.11.0-1_all.deb
 dc2c027bd75b9994385445efe8422bf493144eb7f9c78730545f2aedd3e07d2a 1769802 
python-numpy_1.11.0-1_amd64.deb
 a3bbdb59c95a0414e386528a24fc24eb7d54a0031fe7dabc236af6d28c420e9a 7056320 
python3-numpy-dbg_1.11.0-1_amd64.deb
 

Processed: tagging 820342

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # Version-tracking already sufficient for fixed suites
> tags 820342 - jessie
Bug #820342 [gpa] gpa send public key to server despite the refusal of the user
Removed tag(s) jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#704206: teem: diff for NMU version 1.11.0~svn6057-1.1

2016-04-09 Thread Gianfranco Costamagna
Hi Tobias,


dcut ftp-master reschedule -d 0 -f teem_1.11.0~svn6057-1.1_source.changes


thanks for the NMU!

g.

On Sat, 09 Apr 2016 10:36:05 +0200 Tobias Frost  wrote:
> Control: tags 704206 + pending
> Control: tags 820503 + patch
> Control: tags 820503 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for teem (versioned as 1.11.0~svn6057-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> diff -Nru teem-1.11.0~svn6057/debian/changelog 
> teem-1.11.0~svn6057/debian/changelog
> --- teem-1.11.0~svn6057/debian/changelog  2013-08-17 05:16:21.0 
> +0200
> +++ teem-1.11.0~svn6057/debian/changelog  2016-04-09 10:34:39.0 
> +0200
> @@ -1,3 +1,13 @@
> +teem (1.11.0~svn6057-1.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Use -ffloat-store (i386) and -ffp-contract=off on certain archs to fix
> +testsuite failures due to rounding issues. Thanks to Adam Conrad and 
> Erwan
> +Prioul for the patch (Closes: #704206)
> +  * Make build verbose (Closes: #820503)
> +
> + -- Tobias Frost   Sat, 09 Apr 2016 10:34:39 +0200
> +
>  teem (1.11.0~svn6057-1) unstable; urgency=low
>  
>* new upstream snapshot
> diff -Nru teem-1.11.0~svn6057/debian/rules teem-1.11.0~svn6057/debian/rules
> --- teem-1.11.0~svn6057/debian/rules  2013-01-11 18:23:26.0 +0100
> +++ teem-1.11.0~svn6057/debian/rules  2016-04-09 10:27:04.0 +0200
> @@ -16,7 +16,7 @@
>  DEB_CMAKE_EXTRA_FLAGS = \
>  -DCMAKE_INSTALL_PREFIX:PATH=/usr \
>  -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \
> --DCMAKE_VERBOSE_MAKEFILE=$(DH_VERBOSE) \
> +-DCMAKE_VERBOSE_MAKEFILE=ON \
>  -DCMAKE_SKIP_RPATH:BOOL=ON \
>  -DBUILD_EXPERIMENTAL_APPS:BOOL=OFF \
>  -DBUILD_EXPERIMENTAL_LIBS:BOOL=OFF \
> @@ -24,6 +24,13 @@
>  -DTeem_USE_LIB_INSTALL_SUBDIR:BOOL=ON \
>  -DBUILD_SHARED_LIBS:BOOL=ON \
>  
> +ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
> +  CFLAGS += -ffloat-store
> +endif
> +ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 s390x))
> +  CFLAGS += -ffp-contract=off
> +endif
> +
>  
>  build/libteem${ABI_VERSION}::
>   cd $(DEB_BUILDDIR) && LD_LIBRARY_PATH=`pwd`/bin:$$LD_LIBRARY_PATH ctest 
> -VV -D ExperimentalTest
> 
> 



signature.asc
Description: OpenPGP digital signature


Processed: fixed 820342 in 0.9.9-1

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 820342 0.9.9-1
Bug #820342 [gpa] gpa send public key to server despite the refusal of the user
Marked as fixed in versions gpa/0.9.9-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 820342

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 820342 + upstream fixed-upstream
Bug #820342 [gpa] gpa send public key to server despite the refusal of the user
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tag bug jessie

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 820342 jessie
Bug #820342 [gpa] gpa send public key to server despite the refusal of the user
Added tag(s) jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820026: icedove crashes (segfaults) when installed along with xul-ext-foxyproxy-standard

2016-04-09 Thread Cyril Chaboisseau
Hi,

Sorry Carsten for rushing things out and not giving the proper feedback
(backtrace et al), but I really thought that before looking more
precisely into the bug, we would first have to avoid that other users
from being hit with this crash (conflicts?)

anyway, here is the bt:

#0  0x7fcfe8777c09 in raise () from /lib/x86_64-linux-gnu/libpthread.so.0
[Current thread is 1 (Thread 0x7fcfe8b75740 (LWP 25445))]
(gdb) bt
#0  0x7fcfe8777c09 in raise () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7fcfe3f4c08d in nsProfileLock::FatalSignalHandler (signo=11, 
info=0x7ffd8e51d330, context=0x7ffd8e51d200) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/profile/dirserviceprovider/nsProfileLock.cpp:180
#2  
#3  nsPACMan::IsPACURI (this=0xe5e5e5e5e5e5e5e5, uri=0x7fcfb6007208) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/netwerk/base/nsPACMan.h:145
#4  0x7fcfe2b15485 in nsProtocolProxyService::Resolve_Internal 
(this=0x7fcfcddbf800, channel=, info=..., flags=0, 
usePACThread=0x7ffd8e51dbef, result=0x7ffd8e51dbf8)
at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/netwerk/base/nsProtocolProxyService.cpp:1698
#5  0x7fcfe2b1598b in nsProtocolProxyService::DeprecatedBlockingResolve 
(this=0x7fcfcddbf800, aChannel=aChannel@entry=0x7fcfb6021c40, 
aFlags=aFlags@entry=0, retval=retval@entry=0x7ffd8e51dda8)
at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/netwerk/base/nsProtocolProxyService.cpp:1162
#6  0x7fcfe28f92b9 in MsgExamineForProxy (channel=0x7fcfb6021c40, 
proxyInfo=0x7ffd8e51dda8) at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/base/util/nsMsgUtils.cpp:2122
#7  0x7fcfe29b4d23 in nsImapProtocol::SetupWithUrl 
(this=this@entry=0x7fcfb6c5f800, aURL=aURL@entry=0x7fcfb6007208, 
aConsumer=aConsumer@entry=0x0) at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapProtocol.cpp:839
#8  0x7fcfe29b510e in nsImapProtocol::LoadImapUrl (this=0x7fcfb6c5f800, 
aURL=0x7fcfb6007208, aConsumer=0x0) at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapProtocol.cpp:2138
#9  0x7fcfe297ae01 in nsImapIncomingServer::GetImapConnectionAndLoadUrl 
(this=0x7fcfb5f423e0, aImapUrl=0x7fcfb6007200, aConsumer=0x0) at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapIncomingServer.cpp:444
#10 0x7fcfe29c0174 in nsImapService::GetImapConnectionAndLoadUrl 
(this=, aImapUrl=0x7fcfb6007200, aConsumer=0x0, aURL=) at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapService.cpp:2224
#11 0x7fcfe29c3278 in nsImapService::VerifyLogon (this=0x7fcfb6ca4d30, 
aFolder=0x7fcfb6087c38, aUrlListener=0x7fcfb60be980, aMsgWindow=0x7fcfbb625aa0, 
aURL=0x7ffd8e51e3b0)
at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapService.cpp:1530
#12 0x7fcfe297beb9 in nsImapIncomingServer::VerifyLogon 
(this=0x7fcfb5f423e0, aUrlListener=0x7fcfb60be980, aMsgWindow=0x7fcfbb625aa0, 
aURL=0x7ffd8e51e3b0)
at 
/build/icedove-m4au6s/icedove-38.7.0/mailnews/imap/src/nsImapIncomingServer.cpp:991
#13 0x7fcfe2ab8423 in NS_InvokeByIndex (that=, 
methodIndex=, paramCount=, params=)
at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/xpcom/reflect/xptcall/md/unix/xptcinvoke_x86_64_unix.cpp:176
#14 0x7fcfe2e1bd2f in CallMethodHelper::Invoke (this=0x7ffd8e51e338) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:2110
#15 CallMethodHelper::Call (this=0x7ffd8e51e338) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1447
#16 XPCWrappedNative::CallMethod (ccx=..., 
mode=mode@entry=XPCWrappedNative::CALL_METHOD) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/xpconnect/src/XPCWrappedNative.cpp:1414
#17 0x7fcfe2e2260f in XPC_WN_CallMethod (cx=0x7fcfbbd0ec40, argc=2, 
vp=0x7fcfd548d428) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1144
#18 0x7fcfe42a8560 in js::CallJSNative (args=..., native=, 
cx=0x7fcfbbd0ec40) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/jscntxtinlines.h:226
#19 js::Invoke (cx=0x7fcfbbd0ec40, args=..., construct=) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/vm/Interpreter.cpp:498
#20 0x7fcfe429d27d in Interpret (cx=0x7fcfbbd0ec40, state=...) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/vm/Interpreter.cpp:2602
#21 0x7fcfe42a8221 in js::RunScript (cx=cx@entry=0x7fcfbbd0ec40, state=...) 
at /build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/vm/Interpreter.cpp:448
#22 0x7fcfe42a84ac in js::Invoke (cx=cx@entry=0x7fcfbbd0ec40, args=..., 
construct=construct@entry=js::NO_CONSTRUCT) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/vm/Interpreter.cpp:517
#23 0x7fcfe42a8fbf in js::Invoke (cx=cx@entry=0x7fcfbbd0ec40, thisv=..., 
fval=..., argc=1, argv=, rval=...) at 
/build/icedove-m4au6s/icedove-38.7.0/mozilla/js/src/vm/Interpreter.cpp:554
#24 0x7fcfe45735aa in JS::Call (cx=cx@entry=0x7fcfbbd0ec40, thisv=..., 
thisv@entry=..., fval=..., fval@entry=..., 

Processed: teem: diff for NMU version 1.11.0~svn6057-1.1

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> tags 704206 + pending
Bug #704206 [src:teem] teem: FTBFS[any-i386]: testsuite failures
Ignoring request to alter tags of bug #704206 to the same tags previously set
> tags 820503 + patch
Bug #820503 [teem] teem: Please enable verbose building
Ignoring request to alter tags of bug #820503 to the same tags previously set
> tags 820503 + pending
Bug #820503 [teem] teem: Please enable verbose building
Ignoring request to alter tags of bug #820503 to the same tags previously set

-- 
704206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704206
820503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#704206: teem: diff for NMU version 1.11.0~svn6057-1.1

2016-04-09 Thread Tobias Frost
Control: tags 704206 + pending
Control: tags 820503 + patch
Control: tags 820503 + pending

Dear maintainer,

I've prepared an NMU for teem (versioned as 1.11.0~svn6057-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru teem-1.11.0~svn6057/debian/changelog 
teem-1.11.0~svn6057/debian/changelog
--- teem-1.11.0~svn6057/debian/changelog2013-08-17 05:16:21.0 
+0200
+++ teem-1.11.0~svn6057/debian/changelog2016-04-09 10:34:39.0 
+0200
@@ -1,3 +1,13 @@
+teem (1.11.0~svn6057-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use -ffloat-store (i386) and -ffp-contract=off on certain archs to fix
+testsuite failures due to rounding issues. Thanks to Adam Conrad and Erwan
+Prioul for the patch (Closes: #704206)
+  * Make build verbose (Closes: #820503)
+
+ -- Tobias Frost   Sat, 09 Apr 2016 10:34:39 +0200
+
 teem (1.11.0~svn6057-1) unstable; urgency=low
 
   * new upstream snapshot
diff -Nru teem-1.11.0~svn6057/debian/rules teem-1.11.0~svn6057/debian/rules
--- teem-1.11.0~svn6057/debian/rules2013-01-11 18:23:26.0 +0100
+++ teem-1.11.0~svn6057/debian/rules2016-04-09 10:27:04.0 +0200
@@ -16,7 +16,7 @@
 DEB_CMAKE_EXTRA_FLAGS = \
 -DCMAKE_INSTALL_PREFIX:PATH=/usr \
 -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \
--DCMAKE_VERBOSE_MAKEFILE=$(DH_VERBOSE) \
+-DCMAKE_VERBOSE_MAKEFILE=ON \
 -DCMAKE_SKIP_RPATH:BOOL=ON \
 -DBUILD_EXPERIMENTAL_APPS:BOOL=OFF \
 -DBUILD_EXPERIMENTAL_LIBS:BOOL=OFF \
@@ -24,6 +24,13 @@
 -DTeem_USE_LIB_INSTALL_SUBDIR:BOOL=ON \
 -DBUILD_SHARED_LIBS:BOOL=ON \
 
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386))
+  CFLAGS += -ffloat-store
+endif
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 s390x))
+  CFLAGS += -ffp-contract=off
+endif
+
 
 build/libteem${ABI_VERSION}::
cd $(DEB_BUILDDIR) && LD_LIBRARY_PATH=`pwd`/bin:$$LD_LIBRARY_PATH ctest 
-VV -D ExperimentalTest



Processed: teem: diff for NMU version 1.11.0~svn6057-1.1

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> tags 704206 + pending
Bug #704206 [src:teem] teem: FTBFS[any-i386]: testsuite failures
Added tag(s) pending.
> tags 820503 + patch
Bug #820503 [teem] teem: Please enable verbose building
Added tag(s) patch.
> tags 820503 + pending
Bug #820503 [teem] teem: Please enable verbose building
Added tag(s) pending.

-- 
704206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704206
820503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820504: gst-plugins-base0.10: FTBFS: mv: cannot stat 'html/index.sgml': No such file or directory

2016-04-09 Thread Chris Lamb
Source: gst-plugins-base0.10
Version: 0.10.36-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gst-plugins-base0.10 fails to build from source in unstable/amd64:

  [..]

  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/tests/icles'
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/tests/icles'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/tests'
  make[4]: Nothing to be done for 'all-am'.
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/tests'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/tests'
  Making all in docs
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs'
  Making all in design
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs/design'
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs/design'
  make[5]: Nothing to be done for 'all-am'.
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs/design'
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs/design'
  Making all in libs
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160409084245.0X9m8qsw0l.gst-plugins-base0.10/gst-plugins-base0.10-0.10.36/docs/libs'
DOC   Scanning header files
DOC   Introspecting gobjects
DOC   Building XML
  ../../gst-libs/gst/rtp/gstbasertpdepayload.h:106: warning: unknown annotation 
"deprecated" in documentation for GstBaseRTPDepayloadClass.
  :0: warning: Field descriptions for struct GstRTSPExtensionInterface are 
missing in source code comment block.
  ../../gst-libs/gst/video/video.c:2357: warning: Parameter description for 
gst_video_event_new_downstream_force_key_unit::stream_time is not used from 
source code comment block.
  ../../gst-libs/gst/video/video.c:2357: warning: Parameter description for 
gst_video_event_new_downstream_force_key_unit::running_time is not used from 
source code comment block.
  ../../gst-libs/gst/video/video.c:2357: warning: Parameter description for 
gst_video_event_new_downstream_force_key_unit::streamtime is missing in source 
code comment block.
  ../../gst-libs/gst/video/video.c:2357: warning: Parameter description for 
gst_video_event_new_downstream_force_key_unit::runningtime is missing in source 
code comment block.
  ../../gst-libs/gst/video/video.c:2456: warning: Parameter description for 
gst_video_event_parse_downstream_force_key_unit::stream_time is not used from 
source code comment block.
  ../../gst-libs/gst/video/video.c:2456: warning: Parameter description for 
gst_video_event_parse_downstream_force_key_unit::running_time is not used from 
source code comment block.
  ../../gst-libs/gst/video/video.c:2456: warning: Parameter description for 
gst_video_event_parse_downstream_force_key_unit::streamtime is missing in 
source code comment block.
  ../../gst-libs/gst/video/video.c:2456: warning: Parameter description for 
gst_video_event_parse_downstream_force_key_unit::runningtime is missing in 
source code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:737: warning: Parameter 
description for gst_video_overlay_rectangle_new_argb::x is not used from source 
code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:737: warning: Parameter 
description for gst_video_overlay_rectangle_new_argb::y is not used from source 
code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:737: warning: Parameter 
description for gst_video_overlay_rectangle_new_argb::render_x is missing in 
source code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:737: warning: Parameter 
description for gst_video_overlay_rectangle_new_argb::render_y is missing in 
source code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:952: warning: Parameter 
description for gst_video_overlay_rectangle_get_pixels_unscaled_argb::width is 
not used from source code comment block.
  ../../gst-libs/gst/video/video-overlay-composition.c:952: warning: Parameter 
description for gst_video_overlay_rectangle_get_pixels_unscaled_argb::height is 
missing in source code comment block.
  ./gst-plugins-base-libs-unused.txt:1: warning: 54 unused 

Processed: retitle 816756 to php-pimple: Useless in Debian

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 816756 php-pimple: Useless in Debian
Bug #816756 [php-pimple] Useless in Debian
Changed Bug title to 'php-pimple: Useless in Debian' from 'Useless in Debian'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: block 820420 with 816756

2016-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 820420 with 816756
Bug #820420 [wnpp] ITP: php7cc -- command line tool to detect PHP 7 
incompatible code
820420 was not blocked by any bugs.
820420 was not blocking any bugs.
Added blocking bug(s) of 820420: 816756
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
820420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

2016-04-09 Thread Gilles Filippini
Control: reopen -1

On Fri, 8 Apr 2016 13:34:04 +0200 Emilio Pozuelo Monfort
 wrote:
> On Fri, 8 Apr 2016 12:16:47 +0200 Alastair McKinstry
>  wrote:
> > 
> > >> OpenMPI maintainers (and anyone else affected):
> > >> One possible workaround is to use chrpath -r ""  on mips*
> > >> architectures until this is fixed since that command does not cause any
> > >> tags to be moved. It has a tiny performance penalty but should
> > >> otherwise work properly.
> > > Thanks for the workaround.
> > >
> > > Aurelien
> > >
> > Thanks.
> > I've tested this fix within openmpi on mips (works) and have uploaded a
> > new version with
> > the workaround.
> 
> Thanks! Unfortunately you forgot to apply this same workaround to mipsel and
> mips64el. Could you apply it in those architectures as well?

Reopening, until the problem is fixed for mipsel and mip64el.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#818909: Segfaults caused by new DT_MIPS_RLD_MAP_REL tag and RPATH removers

2016-04-09 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #818909 {Done: Alastair McKinstry } [libopenmpi-dev] 
libopenmpi-dev: [mips*] mpicc.openmpi unusable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmpi/1.10.2-12.

-- 
818909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#820498: tachyon: FTBFS with libpng16 on mipsel

2016-04-09 Thread Tobias Frost
Source: tachyon
Severity: serious
Justification: FTBFS but did in the past

Dear maintainer,

the package FTBFS with libpng 1.6 on mipsel (release arch) and others
non-release archs (mips64el and sh4) (it built on mipsel in the past, so it is
RC)

Note that hppa also shows a very similar error, which was not binNMUed. So it
might be that the problem is not related to the library tansition.

Buildlog for mips: 

https://buildd.debian.org/status/fetch.php?pkg=tachyon=mipsel=0.99~b6%2Bdsx-4%2Bb1=1460116130

Buildd page:
https://buildd.debian.org/status/package.php?p=tachyon

snippet: 
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so.0.0.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0 missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so.0.0.0
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-openmp.so
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so" (tried in "." and 
"debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi-thr.so
dh_install: Cannot find (any matches for) 
"usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so" (tried in "." and "debian/tmp")
dh_install: libtachyon-openmpi-0-dev missing files: 
usr/lib/mipsel-linux-gnu/libtachyon-openmpi.so
dh_install: missing files, aborting
debian/rules:59: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#820220: [Pkg-julia-devel] Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: Bug#820220: julia: FTBFS on armel/armhf

2016-04-09 Thread Viral Shah
LLVM 3.7.1 should have decent performance as we upstreamed various performance 
patches from the Julia project. However, we still have patches on top of llvm 
3.7.1 for getting acceptable performance. However, this is all on the julia 
master, and not julia 0.4.

-viral



> On 08-Apr-2016, at 9:31 PM, Peter Colberg  wrote:
> 
> On Fri, Apr 08, 2016 at 09:55:02PM +0200, Graham Inggs wrote:
>> On 8 April 2016 at 21:16, Emilio Pozuelo Monfort  wrote:
>>> Why did you switch to 3.8? The default in unstable is 3.6 and in 
>>> experimental is
>>> 3.7.
>> 
>> I understood there were severe performance regressions with Julia on
>> LLVM > 3.3 that were only fixed in 3.8.
> 
> The reason for switching to LLVM 3.8 was the abysmal performance
> of LLVM 3.7 on i386, and complete failure of LLVM 3.6 or earlier.
> 
> https://github.com/JuliaLang/julia/issues/14191
> 
> Peter
> 
> ___
> Pkg-julia-devel mailing list
> pkg-julia-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-julia-devel