Processed: tagging 803618

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 803618 + patch
Bug #803618 [mysql-workbench] mysql-workbench, FTBFS on architectures where 
char is unsigned.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#803618: tagged as pending

[Dmitry Smirnov]

tag 803618 pending
--

We believe that the bug #803618 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:


http://anonscm.debian.org/cgit/collab-maint/mysql-workbench.git/diff/?id=1b7b209

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 1b7b209 (HEAD, master)
Author: Dmitry Smirnov 
Date:   Sun Nov 1 03:12:38 2015

patch: to fix FTBFS + changelog summary (Closes: #803618)

 Thanks, Peter Michael Green 

Processed: Bug#803618 tagged as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 803618 pending
Bug #803618 [mysql-workbench] mysql-workbench, FTBFS on architectures where 
char is unsigned.
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#803618: marked as done (mysql-workbench, FTBFS on architectures where char is unsigned.)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2015 04:21:45 +
with message-id 
and subject line Bug#803618: fixed in mysql-workbench 6.3.4+dfsg-3
has caused the Debian Bug report #803618,
regarding mysql-workbench, FTBFS on architectures where char is unsigned.
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.)


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

Package: mysql-workbench
Version:  6.3.4+dfsg-2
Severity: serious

When building mysql-workbench on arm*, ppc* and s390x there are errors like.

/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:
 In function 'int mysql_parser::hexlo(int)':
/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:3890:3:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
   };
   ^
/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:3890:3:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]


then the error repeats a load of times (with the same sourcecode 
position given each time).


The signdness of plain char is implementation dependent. On linux 
systems it depends on the CPU architecture.


Investigating the sourcecode shows an array of char with many values 
initialised to -1. To fix this I changed data type to signed char


I have successfully built the package with this change in a raspbian 
stretch-staging environment and uploaded to raspbian. I have not tested 
it beyond that. A debdiff can be found at  
http://debdiffs.raspbian.org/main/m/mysql-workbench/mysql-workbench_6.3.4+dfsg-2+rpi1.debdiff  
No intent to NMU in Debian.
--- End Message ---
--- Begin Message ---
Source: mysql-workbench
Source-Version: 6.3.4+dfsg-3

We believe that the bug you reported is fixed in the latest version of
mysql-workbench, 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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated mysql-workbench 
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: Sun, 01 Nov 2015 14:10:13 +1100
Source: mysql-workbench
Binary: mysql-workbench mysql-workbench-data
Architecture: source all amd64
Version: 6.3.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 mysql-workbench - MySQL Workbench - a visual database modeling, administration 
and
 mysql-workbench-data - MySQL Workbench -- architecture independent data
Closes: 803618
Changes:
 mysql-workbench (6.3.4+dfsg-3) unstable; urgency=medium
 .
   [ Peter Michael Green  ]
   * Fix build failure on architectures where plain char is unsigned
 (Closes: #803618).
Checksums-Sha1:
 40da77f53122bd89fb079eba73becfd1538ba7e8 2587 mysql-workbench_6.3.4+dfsg-3.dsc
 af5bb408f4acacc862682e4dd12f383a8fa3511a 39080 
mysql-workbench_6.3.4+dfsg-3.debian.tar.xz
 e59b152ea53d3f4ab155028dbfe26d0ebf50df64 1607944 
mysql-workbench-data_6.3.4+dfsg-3_all.deb
 f2b2763ff9e5775fbf697ebb249ca19bcf5b200b 8671344 
mysql-workbench_6.3.4+dfsg-3_amd64.deb
Checksums-Sha256:
 a3f1d42940924ffce318087257ae245f54005bb4736a0abcd63f7cd07fbbf313 2587 
mysql-workbench_6.3.4+dfsg-3.dsc
 7c8d7b386ce845bfcdcf417d4e6ade7af79709df0062abcb217cef24a07b2937 39080 
mysql-workbench_6.3.4+dfsg-3.debian.tar.xz
 9dae0e0cd743453b4afaeaf2d8406dd4c1429225694e2f3c89b7df3daf34459c 1607944 
mysql-workbench-data_6.3.4+dfsg-3_all.deb
 794cad6c853050e3627c644489cc62322a2ae27dc9aa582628b3f0fef39a4409 8671344 
mysql-workbench_6.3.4+dfsg-3_amd64.deb
Files:
 10399ed3fc0696966732a4e9f05cf04d 2587 database optional 
mysql-workbench_6.3.4+dfsg-3.dsc
 b8c631a2d60cccac8d3c2d5c7d1d4bfd 39080 database optional 
mysql-workbench_6.3.4+dfsg-3.debian.tar.xz
 4e500729e3ff51c25b79805f8c0587f5 1607944 database optional 
mysql-workbench-data_6.3.4+dfsg-3_all.deb
 c77f14b62e57f013a03665b08541e9b5 8671344 database optional 

Bug#803618: mysql-workbench, FTBFS on architectures where char is unsigned.

[Dmitry Smirnov]

On Saturday 31 October 2015 23:22:13 peter green wrote:
> To fix this I changed data type to signed char
> 
> I have successfully built the package with this change in a raspbian
> stretch-staging environment and uploaded to raspbian. I have not tested
> it beyond that. A debdiff can be found

Many thanks for this patch, Peter. Much appreciated.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Odious ideas are not entitled to hide from criticism behind the human
shield of their believers' feelings.
-- Richard Stallman


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

Bug#802248: awesome: FTBFS: ldoc: Error: no suitable Lua interpreter found

[Uli Schlachter]

reassign 802248 lua-ldoc 1.4.3-4
retitle 802248 lua-ldoc does not work with lua5.1
tag 802248 patch
thanks

Hi,

lua-ldoc clearly uses lua-any, but claims to only work with lua5.2:

$ grep Lua-Versions /usr/bin/ldoc
-- Lua-Versions: 5.2

After uninstalling lua5.2 I thus get:

$ ldoc
Error: no suitable Lua interpreter found
Error: supported versions are: 5.2

A sudoedit later I get:

$ grep Lua-Versions /usr/bin/ldoc
-- Lua-Versions: 5.1 5.2
$ ldoc
ldoc: missing required parameter: file
[...]

So I'll (try to...) reassign this bug to lua-ldoc. Also, it should be obvious
how to fix this. :-)

Cheers,
Uli
-- 
"In the beginning the Universe was created. This has made a lot of
 people very angry and has been widely regarded as a bad move."

Bug#803555: pygame: FTBFS in experimental

[Andreas Beckmann]

Source: pygame
Version: 1.9.2~pre~r3348-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

pygame/exerimental FTBFS in a current sid+experimental environment:

[...]
 debian/rules build
dh build --with python2,python3
   dh_testdir
   dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
Using UNIX configuration...


Hunting dependencies...
SDL : found 1.2.15
FONT: found
IMAGE   : found
MIXER   : found
SMPEG   : found 0.4.5
PNG : found
JPEG: found
SCRAP   : found
PORTMIDI: found
PORTTIME: found
AVFORMAT: not found
SWSCALE : not found
FREETYPE: found 2.6.0


Warning, some of the pygame dependencies were not found. Pygame can still
compile and install, but games that depend on those missing dependencies
will not run. Would you like to continue the configuration? [Y/n]:Traceback 
(most recent call last):
  File "config.py", line 169, in 
if __name__ == '__main__': main()
  File "config.py", line 157, in main
deps = CFG.main()
  File "/tmp/buildd/pygame-1.9.2~pre~r3348/config_unix.py", line 232, in main
will not run. Would you like to continue the configuration?"""):
  File "/tmp/buildd/pygame-1.9.2~pre~r3348/config_unix.py", line 30, in confirm
reply = raw_input('\n' + message + ' [Y/n]:')
EOFError: EOF when reading a line
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking returned exit code 1
debian/rules:19: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas

Bug#802085: marked as done (lmfit-py: FTBFS: ImportError: No module named '__init__')

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 09:52:32 +
with message-id 
and subject line Bug#802085: fixed in lmfit-py 0.9.2+dfsg-1
has caused the Debian Bug report #802085,
regarding lmfit-py: FTBFS: ImportError: No module named '__init__'
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.)


-- 
802085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lmfit-py
Version: 0.8.0+dfsg.1-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

running build_ext
ordereddict (unittest.loader._FailedTest) ... ERROR
ipy_fitter (unittest.loader._FailedTest) ... ERROR
umath (unittest.loader._FailedTest) ... ERROR
ipy_fitter (unittest.loader._FailedTest) ... ERROR
umath (unittest.loader._FailedTest) ... ERROR

==
ERROR: ordereddict (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: ordereddict
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/lmfit-py-0.8.0+dfsg.1/lmfit/ordereddict.py", line 23, in 
from UserDict import DictMixin
ImportError: No module named 'UserDict'


==
ERROR: ipy_fitter (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: ipy_fitter
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/lmfit-py-0.8.0+dfsg.1/lmfit/ui/ipy_fitter.py", line 11, in 
import IPython
ImportError: No module named 'IPython'


...

FAILED (errors=5)

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/lmfit-py.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: lmfit-py
Source-Version: 0.9.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
lmfit-py, 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 802...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated lmfit-py 
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, 31 Oct 2015 08:20:22 +0100
Source: lmfit-py
Binary: python-lmfit python3-lmfit python-lmfit-doc
Architecture: source all
Version: 0.9.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 python-lmfit - Least-Squares Minimization with Constraints (Python 2)
 python-lmfit-doc - Least-Squares Minimization with Constraints (Documentation)
 python3-lmfit - Least-Squares Minimization with Constraints (Python 3)
Closes: 802085
Changes:
 lmfit-py (0.9.2+dfsg-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.9.2+dfsg (Closes: #802085)
   * Use the pypi redirector
Checksums-Sha1:
 22284c4d566496514362f91b911c5bce2422f50e 2480 lmfit-py_0.9.2+dfsg-1.dsc
 73fcd322865fdaa97836068fb0c7f4e4fe6b2f6c 869179 lmfit-py_0.9.2+dfsg.orig.tar.gz
 9a4906f6fa9a0bb0b31d4380d6eaaaf221d92460 4756 
lmfit-py_0.9.2+dfsg-1.debian.tar.xz
 13791ff109fd64dae1fda898490cad79b0217a70 510362 
python-lmfit-doc_0.9.2+dfsg-1_all.deb
 20d2ace2402de0527afbb0e1b59d775dab6ffeab 75596 
python-lmfit_0.9.2+dfsg-1_all.deb
 4ebdf69c4a1f6a4c5c8129dd4176c77ab8b14c4d 75708 
python3-lmfit_0.9.2+dfsg-1_all.deb
Checksums-Sha256:
 6f68986b68a543b14e137a6fcd8793c161ba2dac7dfde2daf7d2999cca5c74d4 2480 
lmfit-py_0.9.2+dfsg-1.dsc
 

Processed: Re: awesome: FTBFS: ldoc: Error: no suitable Lua interpreter found

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 802248 lua-ldoc 1.4.3-4
Bug #802248 [src:awesome] awesome: FTBFS: ldoc: Error: no suitable Lua 
interpreter found
Bug reassigned from package 'src:awesome' to 'lua-ldoc'.
No longer marked as found in versions awesome/3.5.6-1.
Ignoring request to alter fixed versions of bug #802248 to the same values 
previously set
Bug #802248 [lua-ldoc] awesome: FTBFS: ldoc: Error: no suitable Lua interpreter 
found
Marked as found in versions lua-ldoc/1.4.3-4.
> retitle 802248 lua-ldoc does not work with lua5.1
Bug #802248 [lua-ldoc] awesome: FTBFS: ldoc: Error: no suitable Lua interpreter 
found
Changed Bug title to 'lua-ldoc does not work with lua5.1' from 'awesome: FTBFS: 
ldoc: Error: no suitable Lua interpreter found'
> tag 802248 patch
Bug #802248 [lua-ldoc] lua-ldoc does not work with lua5.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#803557: [fglrx-driver] fglrx installation should blacklist amdgpu kernel module

[José Antonio Insua]

Package: fglrx-driver
Version: 1:15.9-2
Severity: critical

--- Please enter the report below this line. ---

Hello, 

after the latest kernel update in sid, the free "amdgpu" driver is available 
as a module and it gets automatically loaded at boot, conflicting with fglrx.

This module should probably be blacklisted like the "radeon" module by 
default.

I was hit by this issue and everything was solved by adding a file with 
"blacklist amdgpu" under /etc/modprobe.d/

Regards

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.de.debian.org 
  500 unstabledownload.jitsi.org 
  500 unstabledeb-multimedia.org 
  500 testing ftp.de.debian.org 
  500 stable  dl.google.com 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
libfglrx  (= 1:14.6~betav1.0-1) | 
xorg-video-abi-15   | 
 OR xorg-video-abi-14   | 
 OR xorg-video-abi-13   | 
 OR xorg-video-abi-12   | 
 OR xorg-video-abi-11   | 
 OR xorg-video-abi-10   | 
 OR xorg-video-abi-8| 
 OR xorg-video-abi-6.0  | 
xserver-xorg-core   | 
glx-alternative-fglrx   (>= 0.4.1~) | 
libc6(>= 2.3.4) | 
libgl1-mesa-glx | 
 OR libgl1  | 
libx11-6| 
libxext6| 
libxrandr2  | 
libxrender1 | 
debconf   (>= 0.5)  | 
 OR debconf-2.0 | 
libfglrx  (= 1:14.6~betav1.0-1) | 
xorg-video-abi-15   | 
 OR xorg-video-abi-14   | 
 OR xorg-video-abi-13   | 
 OR xorg-video-abi-12   | 
 OR xorg-video-abi-11   | 
 OR xorg-video-abi-10   | 
 OR xorg-video-abi-8| 
 OR xorg-video-abi-6.0  | 
xserver-xorg-core   | 
glx-alternative-fglrx   (>= 0.4.1~) | 
libc6(>= 2.3.4) | 
libgl1-mesa-glx | 
 OR libgl1  | 
libx11-6| 
libxext6| 
libxrandr2  | 
libxrender1 | 
debconf   (>= 0.5)  | 
 OR debconf-2.0 | 


Package Status (Version) | Installed
-+-===
xserver-xorg | 1:7.7+12
xserver-xorg-core| 2:1.17.3-2
linux-headers| 
libdrm-radeon1   | 
xserver-xorg-video-ati   | 
xserver-xorg-video-radeon| 
ia32-libs| 


Recommends  (Version) | Installed
=-+-
===
fglrx-modules-dkms (= 1:14.6~betav1.0-1)  | 1:15.9-2
 OR fglrx-kernel-14.6-betav1.0| 
libgl1-fglrx-glx(= 1:14.6~betav1.0-1) | 
libgl1-fglrx-glx-i386 | 
fglrx-atieventsd  | 
fglrx-modules-dkms (= 1:14.6~betav1.0-1)  | 1:15.9-2
 OR fglrx-kernel-14.6-betav1.0| 
libgl1-fglrx-glx(= 1:14.6~betav1.0-1) | 
libgl1-fglrx-glx-i386 | 
fglrx-atieventsd  | 


Suggests(Version) | Installed
=-+-===
fglrx-control | 1:15.9-2
xvba-va-driver| 
amd-opencl-icd| 1:15.9-2
fglrx-control | 1:15.9-2
xvba-va-driver| 
amd-opencl-icd| 1:15.9-2




-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
  /tmp/reportbug-ng-fglrx-driver-T0tbkC.txt
to the mail. I'd do it myself if the output wasn't too long to handle.

  Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--

Bug#803558: clang-tidy: fails to upgrade from 'testing' - trying to overwrite /usr/bin/clang-tidy

[Andreas Beckmann]

Package: clang-tidy
Version: 1:3.6-31
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package clang-tidy-3.6.
  Preparing to unpack .../clang-tidy-3.6_1%3a3.6.2-3_amd64.deb ...
  Unpacking clang-tidy-3.6 (1:3.6.2-3) ...
  Selecting previously unselected package clang-tidy.
  Preparing to unpack .../clang-tidy_1%3a3.6-31_amd64.deb ...
  Unpacking clang-tidy (1:3.6-31) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clang-tidy_1%3a3.6-31_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/clang-tidy', which is also in package clang 
1:3.5-26
  Errors were encountered while processing:
   /var/cache/apt/archives/clang-tidy_1%3a3.6-31_amd64.deb


cheers,

Andreas


clang=1%3.5-26_clang-tidy=1%3.6-31.log.gz
Description: application/gzip

Bug#803550: rsem: uninstallable on architectures without bowtie

[Andreas Beckmann]

Package: rsem
Version: 1.2.22+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid on most architectures:

rsem/i386 unsatisfiable Depends: bowtie | bowtie2
rsem/armel unsatisfiable Depends: bowtie | bowtie2
rsem/armhf unsatisfiable Depends: bowtie | bowtie2
rsem/mips unsatisfiable Depends: bowtie | bowtie2
rsem/mipsel unsatisfiable Depends: bowtie | bowtie2
rsem/powerpc unsatisfiable Depends: bowtie | bowtie2
rsem/s390x unsatisfiable Depends: bowtie | bowtie2

since bowtie/bowtie2 is only available on a restricted set of
architectures. This will prevent its migration to testing.


Cheers,

Andreas

Bug#803552: libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha causes gnudatalanguage to FTBFS on arm64

[Axel Beckert]

Package: libeigen3-dev
Version: 3.3~alpha1-2
Severity: grave
Control: affects -1 src:gnudatalanguage
Justification: Makes package unusable on one release architecture

Hi,

with the most recent upload of gnudatalanguage (which just changed
documentation stuff), it deterministically FTBFS on arm64 -- and only
there (not counting non-release architectures which have different
issues):

https://buildd.debian.org/status/package.php?p=gnudatalanguage
https://buildd.debian.org/status/fetch.php?pkg=gnudatalanguage=arm64=0.9.5-3=1445723100

Example log excerpt:

In function 'float64x2_t vdupq_lane_f64(float64x1_t, int)',
inlined from 'Packet Eigen::internal::pmul(const Packet&, const Packet&) 
[with Packet = Eigen::internal::Packet1cd]' at 
/usr/include/eigen3/Eigen/src/Core/arch/NEON/Complex.h:329:22,
inlined from 'Packet Eigen::internal::pmadd(const Packet&, const Packet&, 
const Packet&) [with Packet = Eigen::internal::Packet1cd]' at 
/usr/include/eigen3/Eigen/src/Core/GenericPacketMath.h:450:14,
inlined from 'static void Eigen::internal::etor_product_packet_impl<0, -1, 
Lhs, Rhs, Packet, LoadMode>::run(Eigen::Index, Eigen::Index, const Lhs&, const 
Rhs&, Eigen::Index, Packet&) [with Lhs = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> > >; Rhs = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> > >; Packet = Eigen::internal::Packet1cd; int 
LoadMode = 0; Eigen::Index = long int]' at 
/usr/include/eigen3/Eigen/src/Core/ProductEvaluators.h:601:7,
inlined from 'const PacketType 
Eigen::internal::product_evaluator, ProductTag, 
Eigen::DenseShape, Eigen::DenseShape, typename Lhs::Scalar, typename 
Rhs::Scalar>::packet(Eigen::Index, Eigen::Index) const [with int LoadMode = 0; 
PacketType = Eigen::internal::Packet1cd; Lhs = 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>; Rhs = Eigen::Map, 16, 
Eigen::Stride<0, 0> >; int ProductTag = 8; typename Rhs::Scalar = 
std::complex; typename Lhs::Scalar = std::complex; Eigen::Index 
= long int]' at /usr/include/eigen3/Eigen/src/Core/ProductEvaluators.h:493:5,
inlined from 'void 
Eigen::internal::generic_dense_assignment_kernel::assignPacket(Eigen::Index, Eigen::Index) 
[with int StoreMode = 16; int LoadMode = 0; PacketType = 
Eigen::internal::Packet1cd; DstEvaluatorTypeT = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> > >; SrcEvaluatorTypeT = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> >, 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>, 1> >; Functor = Eigen::internal::assign_op; int 
Version = 0; Eigen::Index = long int]' at 
/usr/include/eigen3/Eigen/src/Core/AssignEvaluator.h:598:5,
inlined from 'void 
Eigen::internal::generic_dense_assignment_kernel::assignPacketByOuterInner(Eigen::Index, 
Eigen::Index) [with int StoreMode = 16; int LoadMode = 0; PacketType = 
Eigen::internal::Packet1cd; DstEvaluatorTypeT = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> > >; SrcEvaluatorTypeT = 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> >, 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>, 1> >; Functor = Eigen::internal::assign_op; int 
Version = 0; Eigen::Index = long int]' at 
/usr/include/eigen3/Eigen/src/Core/AssignEvaluator.h:612:5,
inlined from 'static void Eigen::internal::dense_assignment_loop::run(Kernel&) [with Kernel = 
Eigen::internal::generic_dense_assignment_kernel, 16, Eigen::Stride<0, 0> > >, 
Eigen::internal::evaluator, 16, Eigen::Stride<0, 0> >, 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>, 1> >, Eigen::internal::assign_op, 0>]' at 
/usr/include/eigen3/Eigen/src/Core/AssignEvaluator.h:516:9,
inlined from 'void Eigen::internal::call_dense_assignment_loop(const 
DstXprType&, const SrcXprType&, const Functor&) [with DstXprType = 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>; SrcXprType = Eigen::Product, 16, Eigen::Stride<0, 0> >, 
Eigen::Map, 16, Eigen::Stride<0, 0> 
>, 1>; Functor = Eigen::internal::assign_op]' at 
/usr/include/eigen3/Eigen/src/Core/AssignEvaluator.h:659:3:
/usr/lib/gcc/aarch64-linux-gnu/5/include/arm_neon.h:14027:10: error: lane 1 out 
of range 0 - 0
   return 

Processed: libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha causes gnudatalanguage to FTBFS on arm64

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gnudatalanguage
Bug #803552 [libeigen3-dev] libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha 
causes gnudatalanguage to FTBFS on arm64
Added indication that 803552 affects src:gnudatalanguage

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

Bug#803559: golang-go: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/go/pkg/tool/linux_amd64/cover

[Andreas Beckmann]

Package: golang-go
Version: 2:1.5.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package golang-go.
  Preparing to unpack .../golang-go_2%3a1.5.1-3_amd64.deb ...
  Unpacking golang-go (2:1.5.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-go_2%3a1.5.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/go/pkg/tool/linux_amd64/cover', which is also 
in package golang-go.tools 0.0~hg20140703-4
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/golang-go_2%3a1.5.1-3_amd64.deb


cheers,

Andreas


golang-go.tools=0.0~hg20140703-4_golang-go=2%1.5.1-3.log.gz
Description: application/gzip

Bug#803565: ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc

[Andreas Beckmann]

Package: ure
Version: 5.0.3~rc1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libreoffice-common/jessie
  # (1)
  apt-get install ure/stretch
  apt-get remove ure/stretch
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/lib/libreoffice/program/unorc

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The ure package has the following relationships with libreoffice-common:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libreoffice-common (<< 1:4.4.0)

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

1m16.5s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/libreoffice-common.list expected(root, root, - 100644, 
236321, None) != found(root, root, - 100644, 236286, None)
1m16.5s ERROR: FAIL: After purging files have disappeared:
  /usr/lib/libreoffice/program/unorc owned by: ure

1m16.5s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libreoffice-common.list not owned


cheers,

Andreas


libreoffice-common=1%4.3.3-2+deb8u1_ure=5.0.3~rc1-2.log.gz
Description: application/gzip

Bug#789403: marked as done (FTBFS with OCaml 4.02.2: Some fatal warnings were triggered)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 10:23:07 +
with message-id 
and subject line Bug#789403: fixed in llvm-toolchain-3.4 1:3.4.2-16
has caused the Debian Bug report #789403,
regarding FTBFS with OCaml 4.02.2: Some fatal warnings were triggered
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.)


-- 
789403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-3.4
Version: 3.4.2-14
Severity: important
Tags: patch

Dear Maintainer,

Your package FTBFS with OCaml 4.02.2:
> [...]
> Command Output (stderr):
> --
> File 
> "/tmp/pbuilder/llvm-toolchain-3.4-3.4.2/build-llvm/test/Bindings/Ocaml/Output/bitwriter.ml.tmp.builddir/bitwriter.ml",
>  line 20, characters 12-25:
> Warning 3: deprecated: String.create
> Use Bytes.create instead.
> File 
> "/tmp/pbuilder/llvm-toolchain-3.4-3.4.2/build-llvm/test/Bindings/Ocaml/Output/bitwriter.ml.tmp.builddir/bitwriter.ml",
>  line 1:
> Error: Some fatal warnings were triggered (1 occurrences)
> [...]

I suggest to not use the -warn-error option. With the attached patch,
the package builds. It should as well build with the version of OCaml
currently in unstable, so I suggest you to upload it as soon as
possible, and not wait for the transition to start.

Cheers,

-- 
Stéphane

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru llvm-toolchain-3.4-3.4.2/debian/changelog llvm-toolchain-3.4-3.4.2/debian/changelog
--- llvm-toolchain-3.4-3.4.2/debian/changelog	2015-05-07 09:22:00.0 +0200
+++ llvm-toolchain-3.4-3.4.2/debian/changelog	2015-06-20 08:07:10.0 +0200
@@ -1,3 +1,10 @@
+llvm-toolchain-3.4 (1:3.4.2-14.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix compilation with OCaml 4.02
+
+ -- Stéphane Glondu   Sat, 20 Jun 2015 06:07:10 +
+
 llvm-toolchain-3.4 (1:3.4.2-14) unstable; urgency=medium
 
   * d/patches/isl-0.13-compat.diff, ensure compatibility with libisl13
diff -Nru llvm-toolchain-3.4-3.4.2/debian/patches/-fix-ftbfs-ocaml-4.02 llvm-toolchain-3.4-3.4.2/debian/patches/-fix-ftbfs-ocaml-4.02
--- llvm-toolchain-3.4-3.4.2/debian/patches/-fix-ftbfs-ocaml-4.02	1970-01-01 01:00:00.0 +0100
+++ llvm-toolchain-3.4-3.4.2/debian/patches/-fix-ftbfs-ocaml-4.02	2015-06-20 08:15:12.0 +0200
@@ -0,0 +1,147 @@
+Description: Fix FTBFS with OCaml 4.02
+ New warnings were introduced in OCaml 4.02; do not use -warn-error.
+Author: Stéphane Glondu 
+
+--- llvm-toolchain-3.4-3.4.2.orig/test/Bindings/Ocaml/analysis.ml
 llvm-toolchain-3.4-3.4.2/test/Bindings/Ocaml/analysis.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A llvm.cmxa llvm_analysis.cmxa %t.builddir/analysis.ml -o %t
++ * RUN: %ocamlopt  llvm.cmxa llvm_analysis.cmxa %t.builddir/analysis.ml -o %t
+  * RUN: %t
+  * XFAIL: vg_leak
+  *)
+--- llvm-toolchain-3.4-3.4.2.orig/test/Bindings/Ocaml/bitreader.ml
 llvm-toolchain-3.4-3.4.2/test/Bindings/Ocaml/bitreader.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A llvm.cmxa llvm_bitreader.cmxa llvm_bitwriter.cmxa %t.builddir/bitreader.ml -o %t
++ * RUN: %ocamlopt  llvm.cmxa llvm_bitreader.cmxa llvm_bitwriter.cmxa %t.builddir/bitreader.ml -o %t
+  * RUN: %t %t.bc
+  * RUN: llvm-dis < %t.bc
+  * XFAIL: vg_leak
+--- llvm-toolchain-3.4-3.4.2.orig/test/Bindings/Ocaml/bitwriter.ml
 llvm-toolchain-3.4-3.4.2/test/Bindings/Ocaml/bitwriter.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: %ocamlopt -warn-error A unix.cmxa llvm.cmxa llvm_bitwriter.cmxa %t.builddir/bitwriter.ml -o %t
++ * RUN: %ocamlopt  unix.cmxa llvm.cmxa llvm_bitwriter.cmxa %t.builddir/bitwriter.ml -o %t
+  * RUN: %t %t.bc
+  * RUN: llvm-dis < %t.bc
+  * XFAIL: vg_leak
+--- llvm-toolchain-3.4-3.4.2.orig/test/Bindings/Ocaml/executionengine.ml
 llvm-toolchain-3.4-3.4.2/test/Bindings/Ocaml/executionengine.ml
+@@ -1,7 +1,7 @@
+ (* RUN: rm -rf %t.builddir
+  * RUN: mkdir -p %t.builddir
+  * RUN: cp %s %t.builddir
+- * RUN: 

Bug#803563: libncurses5-dev, libncursesw5-dev: removal of libncurses5-dev makes files disappear from ncurses-bin

[Andreas Beckmann]

Package: libncurses5-dev,libncursesw5-dev
Version: 6.0+20151024-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install ncurses-bin/stretch
  # (1)
  apt-get install libncurses5-dev/sid
  apt-get remove libncurses5-dev/sid
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/bin/ncurses5-config
  /usr/share/man/man1/ncurses5-config.1.gz

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The libncurses5-dev package has the following relationships with ncurses-bin:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  ncurses-bin (<< 6.0+20151017)

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

0m50.7s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/ncurses-bin.list expected(root, root, - 100644, 994, None) 
!= found(root, root, - 100644, 928, None)
0m50.7s ERROR: FAIL: After purging files have disappeared:
  /usr/bin/ncurses5-config   owned by: libncurses5-dev:amd64
  /usr/share/man/man1/ncurses5-config.1.gz   owned by: libncurses5-dev:amd64

0m50.7s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/ncurses-bin.listnot owned


A similar problem exists in the libncursesw5-dev package.


cheers,

Andreas


ncurses-bin=5.9+20140913-1+b1_libncurses5-dev=6.0+20151024-1.log.gz
Description: application/gzip

Bug#799340: marked as done (libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 07:19:15 +
with message-id 
and subject line Bug#799340: fixed in libgetdata 0.9.0-1
has caused the Debian Bug report #799340,
regarding libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man3/gd_frameoffset.3.gz
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.)


-- 
799340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgetdata-doc
Version: 0.8.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgetdata-doc.
  Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ...
  Unpacking libgetdata-doc (0.8.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/gd_frameoffset.3.gz', which is also 
in package libgetdata-dev 0.7.3-6+b2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb

and

  Selecting previously unselected package libgetdata-doc.
  Preparing to unpack .../libgetdata-doc_0.8.9-2_all.deb ...
  Unpacking libgetdata-doc (0.8.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/dirfile.5.gz', which is also in 
package libgetdata-tools 0.7.3-6+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libgetdata-doc_0.8.9-2_all.deb
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libgetdata-dev=0.7.3-6+b2_libgetdata-doc=0.8.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libgetdata
Source-Version: 0.9.0-1

We believe that the bug you reported is fixed in the latest version of
libgetdata, 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 799...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libgetdata 
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, 29 Oct 2015 05:22:16 +
Source: libgetdata
Binary: libgetdata-doc libgetdata-dev libgetdata5 libgetdata++3 libfgetdata2 
libf95getdata2 libgetdata-tools python-pygetdata libgetdata-perl
Architecture: source amd64 all
Version: 0.9.0-1
Distribution: sid
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 libf95getdata2 - library to read/write dirfile data - Fortran 95 bindings
 libfgetdata2 - library to read/write dirfile data - Fortran 77 bindings
 libgetdata++3 - library to read/write dirfile data - C++ bindings
 libgetdata-dev - library to read/write dirfile data - devel files (C, C++, 
F77, F9
 libgetdata-doc - library to read/write dirfile data - API and standards 
documents
 libgetdata-perl - library to read/write dirfile data - perl bindings
 libgetdata-tools - library to read/write dirfile data - extra tools
 libgetdata5 - library to read/write dirfile data
 python-pygetdata - library to read/write dirfile data - python bindings
Closes: 799340
Changes:
 libgetdata (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Breaks/Replace fix. Closes: #799340.
Checksums-Sha1:
 f92130b0b37a96cb981229251c310e007a5a1481 2661 libgetdata_0.9.0-1.dsc
 60c98546bfcaec8a9387a37126b1148e8386ef88 1654458 libgetdata_0.9.0.orig.tar.gz
 7b546d8fffdd892c661aad4098e46292167770c1  

Bug#803306: marked as done ("[...] contains files not owned by package libreoffice(-dev), cannot switch to symlink" on upgrades with libreoffice-dev(-doc) installed)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 17:39:42 +
with message-id 
and subject line Bug#803306: fixed in libreoffice 1:5.0.3~rc2-1
has caused the Debian Bug report #803306,
regarding "[...] contains files not owned by package libreoffice(-dev), cannot 
switch to symlink" on upgrades with libreoffice-dev(-doc) 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.)


-- 
803306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice,libreoffice-dev-doc
Version: 1:5.0.3~rc1-2
Severity: serious

Hi again,

On Wed, Oct 28, 2015 at 04:28:20PM +0100, Rene Engelhard wrote:
> # time apt-get dist-upgrade
> [...]
> Preparing to unpack .../libreoffice-dev_1%3a5.0.3~rc1-2_armhf.deb ...
>  apparent dpkg -L of each file found is slw...>
> 
> 
> Yeah, this defnitely is unfortunate and unexpected, but it's not a hang, dpkg
> does its job.
> 
> > Versions of packages libreoffice-dev suggests:
> > ii  libmythes-dev2:1.2.4-1
> > ii  libreoffice-dev-doc  1:5.0.2-1
> 
> OK, now we at least now you *do* have a big tree under 
> /usr/share/doc/libreoffice-dev/docs.
> As I thought.

OK, and after that wait finishes I get:

Preparing to unpack .../libreoffice-dev_1%3a5.0.3~rc1-2_armhf.deb ...
dpkg-maintscript-helper: error: directory '/usr/share/doc/libreoffice-dev' 
contains files not owned by package libreoffice-dev, cannot switch to symlink
dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-dev_1%3a5.0.3~rc1-2_armhf.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
[...]
Errors were encountered while processing:
 /var/cache/apt/archives/libreoffice-dev_1%3a5.0.3~rc1-2_armhf.deb
 /var/cache/apt/archives/libreoffice_1%3a5.0.3~rc1-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

real32m0.179s
user14m19.360s
sys 11m3.510s

(same error for libreoffice)

so there's actual breakage there, too. :( Filing a new bug for this...

(apt-get -f install complains again about libreoffice and runs into the
find "hang" again.)

I tested dist-upgrades; but apparently not with -dev or -dev-doc installed... :/

Sounds like we need a Breaks: or Conflicts: or somesuch to get a clean
upgrade...

Regards,
 
Rene
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:5.0.3~rc2-1

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 31 Oct 2015 14:15:25 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc 
libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core 
libreoffice-base libreoffice-style-oxygen libreoffice-style-breeze 
libreoffice-style-tango libreoffice-style-hicontrast libreoffice-style-sifr 
libreoffice-style-galaxy libreoffice-gtk libreoffice-gnome python3-uno 
libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-pdfimport libreoffice-avmedia-backend-gstreamer 
libreoffice-avmedia-backend-vlc libreoffice-sdbc-firebird 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-ar libreoffice-l10n-as libreoffice-l10n-ast 
libreoffice-l10n-be libreoffice-l10n-bg libreoffice-l10n-bn libreoffice-l10n-br 
libreoffice-l10n-bs libreoffice-l10n-ca libreoffice-l10n-cs libreoffice-l10n-cy
 libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-dz 
libreoffice-l10n-el libreoffice-l10n-en-gb libreoffice-l10n-en-za 
libreoffice-l10n-eo libreoffice-l10n-es libreoffice-l10n-et libreoffice-l10n-eu 
libreoffice-l10n-fa libreoffice-l10n-fi libreoffice-l10n-fr libreoffice-l10n-ga 
libreoffice-l10n-gd 

Bug#803565: marked as done (ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 17:39:42 +
with message-id 
and subject line Bug#803565: fixed in libreoffice 1:5.0.3~rc2-1
has caused the Debian Bug report #803565,
regarding ure: removal of ure makes files disappear from libreoffice-common: 
/usr/lib/libreoffice/program/unorc
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.)


-- 
803565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ure
Version: 5.0.3~rc1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libreoffice-common/jessie
  # (1)
  apt-get install ure/stretch
  apt-get remove ure/stretch
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/lib/libreoffice/program/unorc

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
https://www.debian.org/doc/debian-policy/footnotes.html#f53

The ure package has the following relationships with libreoffice-common:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libreoffice-common (<< 1:4.4.0)

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

1m16.5s DEBUG: Modified(user, group, mode, size, target): 
/var/lib/dpkg/info/libreoffice-common.list expected(root, root, - 100644, 
236321, None) != found(root, root, - 100644, 236286, None)
1m16.5s ERROR: FAIL: After purging files have disappeared:
  /usr/lib/libreoffice/program/unorc owned by: ure

1m16.5s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libreoffice-common.list not owned


cheers,

Andreas


libreoffice-common=1%4.3.3-2+deb8u1_ure=5.0.3~rc1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:5.0.3~rc2-1

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 31 Oct 2015 14:15:25 +0100
Source: libreoffice
Binary: libreoffice libreoffice-l10n-za libreoffice-l10n-in libreoffice-core 
libreoffice-common libreoffice-java-common libreoffice-writer libreoffice-calc 
libreoffice-impress libreoffice-draw libreoffice-math libreoffice-base-core 
libreoffice-base libreoffice-style-oxygen libreoffice-style-breeze 
libreoffice-style-tango libreoffice-style-hicontrast libreoffice-style-sifr 
libreoffice-style-galaxy libreoffice-gtk libreoffice-gnome python3-uno 
libreoffice-officebean libreoffice-script-provider-python 
libreoffice-script-provider-bsh libreoffice-script-provider-js 
libreoffice-pdfimport libreoffice-avmedia-backend-gstreamer 
libreoffice-avmedia-backend-vlc libreoffice-sdbc-firebird 
libreoffice-sdbc-hsqldb libreoffice-base-drivers libreoffice-l10n-af 
libreoffice-l10n-ar libreoffice-l10n-as libreoffice-l10n-ast 
libreoffice-l10n-be libreoffice-l10n-bg libreoffice-l10n-bn libreoffice-l10n-br 
libreoffice-l10n-bs libreoffice-l10n-ca libreoffice-l10n-cs libreoffice-l10n-cy
 libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-dz 
libreoffice-l10n-el libreoffice-l10n-en-gb libreoffice-l10n-en-za 
libreoffice-l10n-eo libreoffice-l10n-es libreoffice-l10n-et libreoffice-l10n-eu 
libreoffice-l10n-fa libreoffice-l10n-fi libreoffice-l10n-fr libreoffice-l10n-ga 
libreoffice-l10n-gd libreoffice-l10n-gl libreoffice-l10n-gu libreoffice-l10n-he 
libreoffice-l10n-hi libreoffice-l10n-hr libreoffice-l10n-hu libreoffice-l10n-id 
libreoffice-l10n-is libreoffice-l10n-it 

Bug#802803: bluedevil: after qt 5.5.1 upgrade, bluedevill does no more work

[Adam Majer]

> I has a working bletooth setup with kde 5.4.2. Audio speaker
> connexion was always working. Since upgrade to qt 5.5.1, I first
> have a message saying to device are not discoverable by default, but
> even after fixing this, it seems connected for 3s and than
> disconnect and fails.  Not found any workaround yet.

Did you upgrade any other parts of the system at the same time? Like
bluez or linux?

- Adam

-- 
Adam Majer
ad...@zombino.com

Processed: Re: Bug#803222: RuntimeError: Incorrect MySQL client library version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 803222 grave
Bug #803222 [ruby-mysql] RuntimeError: Incorrect MySQL client library version! 
This gem was compiled for 5.5.43 but the client library is 5.6.25.
Severity set to 'grave' from 'important'
> tag 803222 + patch
Bug #803222 [ruby-mysql] RuntimeError: Incorrect MySQL client library version! 
This gem was compiled for 5.5.43 but the client library is 5.6.25.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#803597: flashplugin-nonfree: Downloaded and installed flashplugin is not picked up by browsers

[Johan Ouwerkerk]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When installing flashplugin-nonfree neither Iceweasel nor Chromium will list 
the plugin as part of the installed browser plugins, and neither browser will 
be able to play any flash content on sites that make use of it. For Iceweasel 
this can be worked around by creating a 'symlink' to help the browser out, for 
chromium I have not yet found the right/magic symlink path (or it may not be as 
simple).

The flashplugin-nonfree package provides an 'alternative' for:

/usr/lib/mozilla/plugins/flash-mozilla.so

Which points into the /etc/alternatives tree and ultimately the chain leads to 
/usr/lib/flashplugin-nonfree/libflashplayer.so

Unfortunately, while this setup enables the use of 'alternative' 
implementations of libflashplayer.so, it also means that by 
default the user must manually create symlinks in the /usr/lib hierarchy. So, 
by default the flash player plugin does not 
actually 'work' out of the 'box' when flashplugin-nonfree is installed -- 
making this package unusable by default. 

This is because browsers do not look for a 'flash-mozilla' but for a 
'libflashplayer' library.

One can fix this manually for Iceweasel/Firefox by creating a symlink at 
/usr/lib/firefox-addons/plugins/libflashplayer.so 
pointing to /usr/lib/mozilla/plugins/flash-mozilla.so

Presumably there ought to be a similar workaround for Chromium but so far I 
have been unable to find one that works.

Please consider redesigning the set of symlinks installed to make sure that the 
libflashplayer.so is found by browsers looking for it (as libflashplayer.so), 
or at least clarify that the user must manually create necessary symlinks in 
/usr/lib themselves during installation.


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

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

Bug#802803: bluedevil: after qt 5.5.1 upgrade, bluedevill does no more work (connexion alway fails)

[Diederik de Haas]

On Friday 23 October 2015 19:22:49 Eric Valette wrote:
> I has a working bletooth setup with kde 5.4.2. Audio speaker connexion was
> always working. Since upgrade to qt 5.5.1, I first have a message
> saying to device are not discoverable by default, but even after
> fixing this, it seems connected for 3s and than disconnect and fails.
> Not found any workaround yet.

Bluetooth is working here reasonably well. When I plug in my bluetooth adapter 
in my PC is gets recognized and I was able to pair it with both my phone and 
my headset. I've been able to send a file from my phone to my PC using 
bluetooth.
Besides connecting my headset to my PC I haven't been able to do anything 
useful with it, but I haven't been able to do that ever. Don't even know if 
and how it's supposed to work (and I don't care as I only use it with my 
phone).

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

Bug#803567: r-bioc-cummerbund: FTBFS: objects 'FilterRules', 'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges'

[Andreas Tille]

See #803479

On Sat, Oct 31, 2015 at 01:09:09PM +, Chris Lamb wrote:
> Source: r-bioc-cummerbund
> Version: 2.10.0-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,
> 
> r-bioc-cummerbund fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   * installing *source* package 'cummeRbund' ...
>   ** R
>   ** data
>   ** inst
>   ** preparing package for lazy loading
>   Warning: replacing previous import by 'IRanges::FilterRules' when
>   loading 'VariantAnnotation'
>   Warning: replacing previous import by 'IRanges::FilterMatrix' when
>   loading 'VariantAnnotation'
>   Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix',
>   'subsetByFilter' are not exported by 'namespace:IRanges'
>   Error : package 'Gviz' could not be loaded
>   ERROR: lazy loading failed for package 'cummeRbund'
>   * removing
>   
> '/home/lamby/temp/cdt.20151031125953.K7Z1F3IZ2W/r-bioc-cummerbund-2.10.0/debian/r-bioc-cummerbund/usr/lib/R/site-library/cummeRbund'
>   /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
>   failed
>   make: *** [R_any_arch] Error 1
> 
>   [..]
> 
> The full build log is attached.
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-


> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Bug#803552: libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha causes gnudatalanguage to FTBFS on arm64

[Anton Gladky]

Hi Axel,

thanks for bugreport, I will try to contact upstream
regarding this issue, usually they are very responsive. So
I hope we will solve this issue as far as possible.

There were reasons, why I uploaded alpha version into sid.
First of all this version was precisely tested for all packages
(yes, arm64 was not used for that). But the main reason is
the following: starting from 3.3 old eigen2-support will be
dropped. So affected packages were NMU-ed, dropping
eigen2-interface and migrating to eigen3. To escape the new
package uploads into the sid, which could potentially use
eigen2, this alpha version was uploaded.

Regarding bug`s severity, I think it should be important. This
affects only one package on one architecture, even if it is
a release architecture. I can just propose now to remove
gnudatalanguage on arm64 till the issue is not resolved.

Best regards

Anton


2015-10-31 12:20 GMT+01:00 Axel Beckert :
> So far I would have set the severity only to "important" as only
> gnudatalanguage seems affected. But since upstream knows about issues
> with arm64 (see below) and they sound as broken as gnudatalanguage
> currently is on arm64, IMHO "grave" is justified.

Bug#785849: marked as done (libnice: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 13:04:47 +
with message-id 
and subject line Bug#785849: fixed in libnice 0.1.7-2
has caused the Debian Bug report #785849,
regarding libnice: Please update to GStreamer 1.x
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.)


-- 
785849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnice
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package libnice currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Source: libnice
Source-Version: 0.1.7-2

We believe that the bug you reported is fixed in the latest version of
libnice, 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 785...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated libnice 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, 31 Oct 2015 13:50:29 +0100
Source: libnice
Binary: libnice10 libnice-dev gstreamer1.0-nice libnice-doc libnice-dbg
Architecture: source
Version: 0.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gstreamer1.0-nice - ICE library (GStreamer plugin)
 libnice-dbg - ICE library (debugging symbols)
 libnice-dev - ICE library (development files)
 libnice-doc - ICE library (documentation)
 libnice10  - ICE library (shared library)
Closes: 785849
Changes:
 libnice (0.1.7-2) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * Remove myself from Uploaders
 .
   [ Emilio Pozuelo Monfort ]
   * Drop gstreamer0.10-nice package. It has no reverse dependencies
 anymore and GStreamer 0.10 is going away. Closes: #785849.
Checksums-Sha1:
 ec06cf7dbd47d51d1a19723f5a9caa87242d6615 2391 libnice_0.1.7-2.dsc
 f3e06d67d2ea5e45c62b991de5ddebc8bb7d7643 14588 libnice_0.1.7-2.debian.tar.xz
Checksums-Sha256:
 5f4ff6a36dd39702800754859b01362bf1037d7588e89094fa7bc9a68fe158ff 2391 
libnice_0.1.7-2.dsc
 12ffb670576d88d201c40cfcf575b18e6db32fab6b1a066e7d1f428f24174396 14588 
libnice_0.1.7-2.debian.tar.xz
Files:
 64a76bc34add5ade5fc55bc3a618436f 2391 libs optional libnice_0.1.7-2.dsc
 fd4e2b66f8aff6449b002e7a1d398cf8 14588 libs optional 
libnice_0.1.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWNLsTAAoJEJ1GxIjkNoMCdtIQALpxm9OVMuddFWsnpNaoqXij
P3Kl6tcJMl0hd3eOG/P246vrVk1u+5ZLS6Vh8z5+xDMafzd8qUx7ydyez/enIr8U
DeEVdIzH0/dn+1AW1EAkgknd3PhvcIceUg5KVsMeNjhele4wJWu7QLnJutfODpWC
clkyIkp14uHiWsiMVgHDTWS8T4u0xvJxbRUqEN2NjGhlkxR9nLn0NMLjOlP4LqrR
G14i98ov9sg5+M8EEKhs1P/APnEbrsHnUpXXBDLxNsb+HaHOCYczI7bImOy7r3yC
zT9MPUk/fkrUf30Dq+/z/DwWHtZLtiXJgEQ6FBiiwLk7vNgEzdQij11TOi57Lxrr
54fEKNAjX3DvXuMuE07Jsg6H/tQnDAU9uDzCCo8OH8/vomoYq+JYYpS4EsOycOjn
tQeDPkeyOKzExBE+08eWD4TOk0MhozF2B0KUadTbVe5bU/o3i9Yv2Ouu3pFqClGH
lEKH/lZV/CgY/MMOcRY30cAhH7QUz6UU83LbVIJ7da2Q7PgMPkK/dpvXz3HOHXqB
/DOmshQXzbbQRdo/R8tODTX9KDm3h2+mO8RcZZMql2OD+DXdB6ixzI9I8jDrdu1n
Q06Vo9cNYMIuoEtSI5ZBQr7UTVCYghQbiMGCIITUgIVId7jcr51G1F6lsly/8KeN
JqWqelgGD5lAZr1eNZhf
=YBTg
-END PGP SIGNATURE End Message ---

Bug#803565: ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc

[Rene Engelhard]

Hi,

On Sat, Oct 31, 2015 at 02:02:13PM +0100, Andreas Beckmann wrote:
> This is caused by using Replaces without corresponding Breaks.
> 
> The installation sequence to reproduce this problem is
> 
>   apt-get install libreoffice-common/jessie
>   # (1)
>   apt-get install ure/stretch
>   apt-get remove ure/stretch

Which is not really helpful given it will basically remove LO, too. But only
the arch-dep parts, so yes, the "properly but not properly installed"
libreoffice-common stays.

I was starting to say "downgrades are not supported" but..

That probably explains #801152
I tried a upgrade/downgrade in #801152 but probably because I did it
"the right way" the issue didn't appear.

> This is a serious bug violating policy 7.6, see
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> and also see the footnote that describes this incorrect behavior
> https://www.debian.org/doc/debian-policy/footnotes.html#f53

... this makes sense, yeah.

Regards,

Rene

P.S: Perfect timing, I almost wanted to upload 1:5.0.3~rc2-1 now :)

Processed: block 792779 with 790978

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 792779 with 790978
Bug #792779 [release.debian.org] nmu: android-platform-frameworks-base_21-2
792779 was not blocked by any bugs.
792779 was not blocking any bugs.
Added blocking bug(s) of 792779: 790978
> thanks
Stopping processing here.

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

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

[Moritz Muehlenhoff]

On Thu, May 21, 2015 at 02:31:29PM +0300, Sebastian Dröge wrote:
> Hi Olly,
> 
> On Do, 2015-05-21 at 01:24 +0100, Olly Betts wrote:
> 
> > But there's an upstream ticket about switching to gstreamer 1.0 with a
> > recently added patch.  I'd appreciate a quick review from someone who
> > has more idea about gstreamer's API than I do if you have a few minutes
> > (it's not a huge patch):
> > 
> > http://trac.wxwidgets.org/attachment/ticket/14976/gst1.0.patch
> > 
> > I can tell the configure part needs improving, at least to make it
> > upstream-able, which makes me wonder about its general quality.
> 
> wxGStreamerMediaBackend::QueryVideoSizeFromPad() probably leaks the caps
> now, you need to unref() them after usage.
> 
> !gst_structure_has_name (gst_message_get_structure(message), 
> "prepare-window-handle"))
> should be using
> gst_is_video_overlay_prepare_window_handle_message()
> 
> Otherwise seems ok if that is really enough to make things work. Not
> sure if more changes are needed elsewhere.

Hi Olly,
what's the status? wxwidgets is now one of the two remaining packages blocking
the removal of gstreamer 0.10 from stretch.

Cheers,
Moritz

Processed: ifrit: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798170 798963 798169 798172 798171 798165 798174 801820 
798168 798166 798167
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 803593

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

Bug#803593: ifrit: depends on vtk 5

[Andreas Beckmann]

Source: ifrit
Version: 3.4.2-2
Severity: serious
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,

Andreas

Processed: found 789927 in uim-anthy/1:1.8.6-14exp1, severity of 803229 is serious ..., tagging 797829 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 789927 uim-anthy/1:1.8.6-14exp1
Bug #789927 [libanthyinput0] libanthyinput0: fails to upgrade from 'sid' - 
trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
The source uim-anthy and version 1:1.8.6-14exp1 do not appear to match any 
binary packages
Marked as found in versions uim-anthy/1:1.8.6-14exp1.
> severity 803229 serious
Bug #803229 [audiotools] audiotools: uninstallable, name conflict with cdtool 
package
Severity set to 'serious' from 'important'
> reassign 777596 src:fcitx-qt5 0.1.2-4
Bug #777596 [libfcitx-qt5-0] libfcitx-qt5-0: fails to upgrade from 'sid' - 
trying to overwrite /usr/lib/x86_64-linux-gnu/libfcitx-qt5.so.0.1
Warning: Unknown package 'libfcitx-qt5-0'
Bug reassigned from package 'libfcitx-qt5-0' to 'src:fcitx-qt5'.
No longer marked as found in versions fcitx-qt5/0.1.2-4.
Ignoring request to alter fixed versions of bug #777596 to the same values 
previously set
Bug #777596 [src:fcitx-qt5] libfcitx-qt5-0: fails to upgrade from 'sid' - 
trying to overwrite /usr/lib/x86_64-linux-gnu/libfcitx-qt5.so.0.1
Marked as found in versions fcitx-qt5/0.1.2-4.
> tags 797829 - sid stretch
Bug #797829 [src:python-igraph] python-igraph ftbfs in unstable with igraph 0.7
Removed tag(s) sid and stretch.
> tags 759858 - jessie sid stretch
Bug #759858 [src:python-igraph] python-igraph: FTBFS: src/graphobject.c:3734:9: 
error: too few arguments to function 'igraph_closeness'
Removed tag(s) stretch, sid, and jessie.
> merge 759858 797829
Bug #759858 [src:python-igraph] python-igraph: FTBFS: src/graphobject.c:3734:9: 
error: too few arguments to function 'igraph_closeness'
Bug #759858 [src:python-igraph] python-igraph: FTBFS: src/graphobject.c:3734:9: 
error: too few arguments to function 'igraph_closeness'
Added tag(s) patch.
Bug #797829 [src:python-igraph] python-igraph ftbfs in unstable with igraph 0.7
Merged 759858 797829
> tags 749531 + sid - pending
Bug #749531 [fslview] Switch to vtk6
Added tag(s) sid.
Bug #749531 [fslview] Switch to vtk6
Removed tag(s) pending.
> severity 749531 serious
Bug #749531 [fslview] Switch to vtk6
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Processed: found 798164 in 5.10.1+dfsg-2, notfound 798164 in 5.8.0-17.5, notfound 798164 in 5.8.0-13

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 798164 5.10.1+dfsg-2
Bug #798164 [src:vtk] vtk: do not ship in stretch
Marked as found in versions vtk/5.10.1+dfsg-2.
> notfound 798164 5.8.0-17.5
Bug #798164 [src:vtk] vtk: do not ship in stretch
No longer marked as found in versions vtk/5.8.0-17.5.
> notfound 798164 5.8.0-13
Bug #798164 [src:vtk] vtk: do not ship in stretch
No longer marked as found in versions vtk/5.8.0-13.
> thanks
Stopping processing here.

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

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

[Dominique Dumont]

On Friday 30 October 2015 10:58:55 Steve Langasek wrote:
> But I'm also marking this as affects: devscripts, because I find it
> surprising that the new licensecheck output includes a line for sample.png,
> when the file was explicitly reported as unparseable.  It doesn't seem
> desirable to me that licensecheck would list files in its output that are
> definitely not going to have embedded license/copyright information and
> whose copyright information must be listed elsewhere.
> 
> Perhaps we want to make sure the new behavior for licensecheck is settled
> before patching license-reconcile.

For what it's worth this change of behavior was requested in #794282 [1]. 
Jonas explicitly requested licensecheck to parse binary files.

This broke 'cme update dpkg-copyright', which led to #797562 [2] . To 
alleviate the issue, I added a -t option to licensecheck to skip binary files.

After re-reading the whole saga, I think this situation can be improved. I'll 
discuss with Jonas to nail down the requirements for a better solution.

All the best

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794282
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797562
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#802803: bluedevil: after qt 5.5.1 upgrade, bluedevill does no more work (connexion alway fails)

[Eric Valette]

On 31/10/2015 18:40, Diederik de Haas wrote:


Besides connecting my headset to my PC I haven't been able to do anything
useful with it, but I haven't been able to do that ever. Don't even know if
and how it's supposed to work (and I don't care as I only use it with my
phone).


I do listen music using wireless headset (phone/tablet but also PC...). 
It worked like a charm and did break after upgrade.


I upgraded my kernel to latest long term stable release (4.1.12). No 
change (connect when I click on it and immediately disconnect). Removed 
the headset from the known device list (never needed to do this before) 
and tried discovery again. It worked.


So, if I have not to do this every time in boot this would be almost fine.

-- eric

Processed: Re: Bug#803552: libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha causes gnudatalanguage to FTBFS on arm64

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 803552 http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1103
Bug #803552 [libeigen3-dev] libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha 
causes gnudatalanguage to FTBFS on arm64
Set Bug forwarded-to-address to 
'http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1103'.
> thanks
Stopping processing here.

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

Processed: severity of 802611 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 802611 important
Bug #802611 [subversion] subversion: Core dump of "svn diff -c 102".
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

[Jonas Smedegaard]

Quoting Dominique Dumont (2015-10-31 20:41:18)
> On Friday 30 October 2015 10:58:55 Steve Langasek wrote:
>> But I'm also marking this as affects: devscripts, because I find it 
>> surprising that the new licensecheck output includes a line for 
>> sample.png, when the file was explicitly reported as unparseable.  It 
>> doesn't seem desirable to me that licensecheck would list files in 
>> its output that are definitely not going to have embedded 
>> license/copyright information and whose copyright information must be 
>> listed elsewhere.
>>
>> Perhaps we want to make sure the new behavior for licensecheck is 
>> settled before patching license-reconcile.
>
> For what it's worth this change of behavior was requested in #794282 
> [1]. Jonas explicitly requested licensecheck to parse binary files.

You make it sound like I requested licensecheck to change behaviour, 
which was not the case.

I explicitly requested licensecheck to not change behaviour.

It may seem silly for licensecheck to scan binary files like a PNG, but 
consider hte less obvious example of Postscript code containing 
plaintext including copyright and licensing info, with embedded binary 
chunks.  Or consider non-Unicde plaintext files where the part flagging 
it as "it's binary, move along" is the very copyright character!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#785924: wxwidgets3.0: Please update to GStreamer 1.x

[Olly Betts]

On Sat, Oct 31, 2015 at 02:16:28PM +0100, Moritz Muehlenhoff wrote:
> On Thu, May 21, 2015 at 02:31:29PM +0300, Sebastian Dröge wrote:
> > Hi Olly,
> > 
> > On Do, 2015-05-21 at 01:24 +0100, Olly Betts wrote:
> > 
> > > But there's an upstream ticket about switching to gstreamer 1.0 with a
> > > recently added patch.  I'd appreciate a quick review from someone who
> > > has more idea about gstreamer's API than I do if you have a few minutes
> > > (it's not a huge patch):
> > > 
> > > http://trac.wxwidgets.org/attachment/ticket/14976/gst1.0.patch
> > > 
> > > I can tell the configure part needs improving, at least to make it
> > > upstream-able, which makes me wonder about its general quality.
> > 
> > wxGStreamerMediaBackend::QueryVideoSizeFromPad() probably leaks the caps
> > now, you need to unref() them after usage.
> > 
> > !gst_structure_has_name (gst_message_get_structure(message), 
> > "prepare-window-handle"))
> > should be using
> > gst_is_video_overlay_prepare_window_handle_message()
> > 
> > Otherwise seems ok if that is really enough to make things work. Not
> > sure if more changes are needed elsewhere.
> 
> what's the status? wxwidgets is now one of the two remaining packages
> blocking the removal of gstreamer 0.10 from stretch.

Status is stalled, essentially.

I gather from what slomo said that the current patch isn't suitable
for applying.  But I don't know anything about the old or new gstreamer
APIs, and don't have the spare time to learn them, so the chances of me
successfully fixing up the patch in response to slomo's feedback are
pretty much non-existent.

There's been no response from upstream or the original patch author to
slomo's feedback on the patch so far.  I prodded them last week about
this, which hasn't had a response yet either.

My impression (from responses and lack of responses to previous bug
reports about the wxmedia stuff) is that it's not a feature which the
active upstream developers care much about, so I suspect any fixes will
need to come from outside.

Despite quite a lot of noise about enabling it, it only actually seems
to be used by whyteboard currently (at least if I can work "dak rm"),
and support for playing video there hardly seems an essential feature.
So a rather brutal way out might be to disable support again, and if
that upsets anyone, then ... well, improved patches welcome.

Cheers,
Olly

Bug#802874: marked as done (mariadb-10.0: Various security fixes from 10.0.22 release)

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 21:17:59 +
with message-id 
and subject line Bug#802874: fixed in mariadb-10.0 10.0.22-0+deb8u1
has caused the Debian Bug report #802874,
regarding mariadb-10.0: Various security fixes from 10.0.22 release
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.)


-- 
802874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.0
Version: 10.0.16-1
Severity: grave
Tags: security upstream

Hi

Various CVEs were fixed in the 10.0.21 and 10.0.22 release:

https://mariadb.com/kb/en/mariadb/mariadb-10021-release-notes/
https://mariadb.com/kb/en/mariadb/mariadb-10022-release-notes/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mariadb-10.0
Source-Version: 10.0.22-0+deb8u1

We believe that the bug you reported is fixed in the latest version of
mariadb-10.0, 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 802...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated mariadb-10.0 
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: Fri, 30 Oct 2015 00:07:24 +0200
Source: mariadb-10.0
Binary: libmariadbd-dev mariadb-common mariadb-client-core-10.0 
mariadb-client-10.0 mariadb-server-core-10.0 mariadb-test-10.0 
mariadb-server-10.0 mariadb-server mariadb-client mariadb-test 
mariadb-connect-engine-10.0 mariadb-oqgraph-engine-10.0
Architecture: all source
Version: 10.0.22-0+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 779992 802874
Description: 
 libmariadbd-dev - MariaDB embedded database development files
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.0 - MariaDB database client binaries
 mariadb-client-core-10.0 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-connect-engine-10.0 - Connect storage engine for MariaDB
 mariadb-oqgraph-engine-10.0 - OQGraph storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.0 - MariaDB database server binaries
 mariadb-server-core-10.0 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite (metapackage for the 
lates
 mariadb-test-10.0 - MariaDB database regression test suite
Changes:
 mariadb-10.0 (10.0.22-0+deb8u1) jessie-security; urgency=high
 .
   [ Otto Kekäläinen ]
   * New upstream release 10.0.22. Includes fixes for the following
 security vulnerabilities (Closes: #802874):
 - CVE-2015-4802
 - CVE-2015-4807
 - CVE-2015-4815
 - CVE-2015-4826
 - CVE-2015-4830
 - CVE-2015-4836
 - CVE-2015-4858
 - CVE-2015-4861
 - CVE-2015-4870
 - CVE-2015-4913
 - CVE-2015-4792
   * New release includes updated man pages (Closes: #779992)
   * Add CVE IDs to previous changelog entries
 .
   [ Arnaud Fontaine ]
   * New upstream release 10.0.21.
 + Refreshed debian/patches/*.
 + Upstream changed mysqld_safe_syslog.cnf to fix logging error
 + Includes fixes the following security vulnerabilities:
   - CVE-2015-4816
   - CVE-2015-4819
   - CVE-2015-4879
   - CVE-2015-4895
Checksums-Sha1: 
 69c95029cff8288c68c8df884560bfa06b93fa92 3148 mariadb-10.0_10.0.22-0+deb8u1.dsc
 53b305fa9b6d620734a48a94b60253ad34e319c9 56252325 
mariadb-10.0_10.0.22.orig.tar.gz
 7525107fcde363bd103d909f970588b5984d92dd 187784 
mariadb-10.0_10.0.22-0+deb8u1.debian.tar.xz
 15f7f8d1fff349b43daf428f4c113d45904145be 16480 
mariadb-common_10.0.22-0+deb8u1_all.deb
 44e27e16878a8713a3136982e8f41263e93f27df 16178 
mariadb-server_10.0.22-0+deb8u1_all.deb
 53d021e62a3436ca0a0ce8fdcefad36ecd6a85b2 16042 
mariadb-client_10.0.22-0+deb8u1_all.deb
 3c19957dbab1ed94daa21517207623977f8526ee 15982 
mariadb-test_10.0.22-0+deb8u1_all.deb
Checksums-Sha256: 
 

Bug#802803: Full upgrade today : same problem.

[Eric Valette]

FYI.

--eric

Processed: Re: Bug#802391: gimagereader: Segfaults when opening an image file

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 802391 pending
Bug #802391 [gimagereader] gimagereader: Segfaults when opening an image file
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802391: gimagereader: Segfaults when opening an image file

[Philip Rinn]

tags 802391 pending
thanks

Hi Peter,

thanks for the report. Well, that's annoying as it's the second time in a row 
that
this happens with gimagereader. I just packaged an upstream snapshot now to fix
this. You find the updated packaging here:

http://anonscm.debian.org/cgit/collab-maint/gimagereader.git/

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

I'm waiting for my sponsor now to upload the package.

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

[Nicholas Bamber]

I have had another think and I would like to make the folloiwng points.

1.) license-reconcile is an experimental package and not at all critical 
to Debian. Unlike decscripts so something is a really wrong if a bug in 
license-reconcile affects devscripts.
2.) I think what Steve meant to do was clone #801609, retitle and 
reassign the clone to devscripts. That's reasonable as there may well be 
more work to do.
3.) As it is supposed to work, license-reconcile is not wholly dependent 
on licensecheck. That said I think one filter is probably obsolete now 
that licensecheck has been improved.
4.) The core thing I wish to avoid is licnese-reconcile development and 
licensecheck development being tied together in anyway. That of course 
means licensecheck will continue to cause problems for license-reconcile 
but as long as those problems are not gratuitous I see no issue.



On 31/10/15 19:41, Dominique Dumont wrote:

On Friday 30 October 2015 10:58:55 Steve Langasek wrote:

But I'm also marking this as affects: devscripts, because I find it
surprising that the new licensecheck output includes a line for sample.png,
when the file was explicitly reported as unparseable.  It doesn't seem
desirable to me that licensecheck would list files in its output that are
definitely not going to have embedded license/copyright information and
whose copyright information must be listed elsewhere.

Perhaps we want to make sure the new behavior for licensecheck is settled
before patching license-reconcile.


For what it's worth this change of behavior was requested in #794282 [1].
Jonas explicitly requested licensecheck to parse binary files.

This broke 'cme update dpkg-copyright', which led to #797562 [2] . To
alleviate the issue, I added a -t option to licensecheck to skip binary files.

After re-reading the whole saga, I think this situation can be improved. I'll
discuss with Jonas to nail down the requirements for a better solution.

All the best

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794282
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797562

Bug#803552: libeigen3-dev: Upgrade from 3.2.x to 3.3~alpha causes gnudatalanguage to FTBFS on arm64

[Axel Beckert]

Hi Anton,

Anton Gladky wrote:
> thanks for bugreport, I will try to contact upstream
> regarding this issue, usually they are very responsive. So
> I hope we will solve this issue as far as possible.

Thanks, much appreciated.

> There were reasons, why I uploaded alpha version into sid.
> First of all this version was precisely tested for all packages
> (yes, arm64 was not used for that). But the main reason is
> the following: starting from 3.3 old eigen2-support will be
> dropped. So affected packages were NMU-ed, dropping
> eigen2-interface and migrating to eigen3. To escape the new
> package uploads into the sid, which could potentially use
> eigen2, this alpha version was uploaded.

I see, thanks for the explanation. (I actually didn't mind uploading
alpha versions to Sid, especially if they're well tested. I just
mentioned it because for me it raised the probability that the issue
is not in gnudatalanguage. :-)

> Regarding bug`s severity, I think it should be important. This
> affects only one package on one architecture, even if it is
> a release architecture.

Feel free to downgrade the severity. As mentioned I veered between
those two severities.

> I can just propose now to remove gnudatalanguage on arm64 till the
> issue is not resolved.

That's my plan B, yes. ;-)

But I'll first wait a little bit more before I'll do this.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 800727 python3-astropy: Incompatible with Python 3.5
Bug #800727 {Done: Ole Streicher } [python3-astropy] 
python3-astropy: Incompatible to Python-3.5
Changed Bug title to 'python3-astropy: Incompatible with Python 3.5' from 
'python3-astropy: Incompatible to Python-3.5'
> thanks
Stopping processing here.

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

Bug#802803: bluedevil: after qt 5.5.1 upgrade, bluedevill does no more work (connexion alway fails)

[Eric Valette]

On 31/10/2015 20:53, Eric Valette wrote:

On 31/10/2015 18:40, Diederik de Haas wrote:


Besides connecting my headset to my PC I haven't been able to do anything
useful with it, but I haven't been able to do that ever. Don't even
know if
and how it's supposed to work (and I don't care as I only use it with my
phone).


I do listen music using wireless headset (phone/tablet but also PC...).
It worked like a charm and did break after upgrade.

I upgraded my kernel to latest long term stable release (4.1.12). No
change (connect when I click on it and immediately disconnect). Removed
the headset from the known device list (never needed to do this before)
and tried discovery again. It worked.

So, if I have not to do this every time in boot this would be almost fine.



Now it connects correctly each time. Dunno what has changed (because of 
course I did the remove device before when desesperately tried to make 
it work again).


-- eric

Bug#803568: stellarium: FTBFS: StelSkyCultureMgr.hpp:47:1: error: expected class-name before '{' token

[Chris Lamb]

Source: stellarium
Version: 0.13.3-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,

stellarium fails to build from source in unstable/amd64:

  [..]

  In file included from
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.cpp:20:0:
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:47:1:
  error: expected class-name before '{' token
   {
   ^
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:48:2:
  error: 'Q_OBJECT' does not name a type
Q_OBJECT
^
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:62:8:
  error: expected ':' before 'slots'
   public slots:
  ^
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:62:8:
  error: 'slots' does not name a type
  [ 85%] Building CXX object
  src/CMakeFiles/stellarium.dir/core/StelTexture.cpp.o
  cd
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/obj-x86_64-linux-gnu/src
  && /usr/bin/c++   -DENABLE_NLS -DENABLE_SCRIPT_CONSOLE
  -DINSTALL_DATADIR=\"/usr/share/stellarium\"
  -DINSTALL_LOCALEDIR=\"/usr/share/locale\" -DPACKAGE_VERSION=\"0.13.3\"
  -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB
  -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SCRIPT_LIB
  -DQT_WIDGETS_LIB -DUSE_STATIC_PLUGIN_ANGLEMEASURE
  -DUSE_STATIC_PLUGIN_ARCHAEOLINES -DUSE_STATIC_PLUGIN_COMPASSMARKS
  -DUSE_STATIC_PLUGIN_EQUATIONOFTIME -DUSE_STATIC_PLUGIN_EXOPLANETS
  -DUSE_STATIC_PLUGIN_FOV -DUSE_STATIC_PLUGIN_METEORSHOWERS
  -DUSE_STATIC_PLUGIN_NAVSTARS -DUSE_STATIC_PLUGIN_NOVAE
  -DUSE_STATIC_PLUGIN_OBSERVABILITY -DUSE_STATIC_PLUGIN_OCULARS
  -DUSE_STATIC_PLUGIN_POINTERCOORDINATES -DUSE_STATIC_PLUGIN_PULSARS
  -DUSE_STATIC_PLUGIN_QUASARS -DUSE_STATIC_PLUGIN_SATELLITES
  -DUSE_STATIC_PLUGIN_SCENERY3D -DUSE_STATIC_PLUGIN_SOLARSYSTEMEDITOR
  -DUSE_STATIC_PLUGIN_SUPERNOVAE -DUSE_STATIC_PLUGIN_TELESCOPECONTROL
  -DUSE_STATIC_PLUGIN_TEXTUSERINTERFACE
  -DUSE_STATIC_PLUGIN_TIMEZONECONFIGURATION -g -O2
  -fstack-protector-strong -Wformat -Werror=format-security
  -D_FORTIFY_SOURCE=2  -Wall -Wextra -Wno-unused-parameter
  -Wno-unused-result
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/obj-x86_64-linux-gnu/src
  -I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src
  -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtScript -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
  /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64
  -I/usr/include/x86_64-linux-gnu/qt5/QtTest
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/obj-x86_64-linux-gnu
  -I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/modules
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/planetsephems
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/external
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/external/qtcompress
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/external/glues_stel/source
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/external/glues_stel/source/libtess
  -I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/gui
  
-I/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/scripting
  -isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtDeclarative -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
  /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
  /usr/include/libdrm-fPIC -o
  CMakeFiles/stellarium.dir/core/StelTexture.cpp.o -c
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelTexture.cpp
  [ 85%] Building CXX object
  src/CMakeFiles/stellarium.dir/core/StelToneReproducer.cpp.o
  cd
  
/home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/obj-x86_64-linux-gnu/src
  && /usr/bin/c++   -DENABLE_NLS -DENABLE_SCRIPT_CONSOLE
  -DINSTALL_DATADIR=\"/usr/share/stellarium\"
  -DINSTALL_LOCALEDIR=\"/usr/share/locale\" -DPACKAGE_VERSION=\"0.13.3\"
  -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DECLARATIVE_LIB -DQT_GUI_LIB
  -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SCRIPT_LIB
  -DQT_WIDGETS_LIB -DUSE_STATIC_PLUGIN_ANGLEMEASURE
  -DUSE_STATIC_PLUGIN_ARCHAEOLINES -DUSE_STATIC_PLUGIN_COMPASSMARKS
  -DUSE_STATIC_PLUGIN_EQUATIONOFTIME -DUSE_STATIC_PLUGIN_EXOPLANETS
  

Bug#803567: r-bioc-cummerbund: FTBFS: objects 'FilterRules', 'seqsplit', 'FilterMatrix', 'subsetByFilter' are not exported by 'namespace:IRanges'

[Chris Lamb]

Source: r-bioc-cummerbund
Version: 2.10.0-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,

r-bioc-cummerbund fails to build from source in unstable/amd64:

  [..]

  * installing *source* package 'cummeRbund' ...
  ** R
  ** data
  ** inst
  ** preparing package for lazy loading
  Warning: replacing previous import by 'IRanges::FilterRules' when
  loading 'VariantAnnotation'
  Warning: replacing previous import by 'IRanges::FilterMatrix' when
  loading 'VariantAnnotation'
  Error : objects 'FilterRules', 'seqsplit', 'FilterMatrix',
  'subsetByFilter' are not exported by 'namespace:IRanges'
  Error : package 'Gviz' could not be loaded
  ERROR: lazy loading failed for package 'cummeRbund'
  * removing
  
'/home/lamby/temp/cdt.20151031125953.K7Z1F3IZ2W/r-bioc-cummerbund-2.10.0/debian/r-bioc-cummerbund/usr/lib/R/site-library/cummeRbund'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch'
  failed
  make: *** [R_any_arch] Error 1

  [..]

The full build log is attached.


Regards,

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


r-bioc-cummerbund.2.10.0-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#802111: [Pkg-javascript-devel] smash: FTBFS: TypeError: sandbox must be an object

[Thomas Goirand]

On 10/29/2015 04:34 PM, Jérémy Lal wrote:
> 
> 
> 2015-10-29 16:24 GMT+01:00 Thomas Goirand  >:
> 
> Hi,
> 
> I'm worried that this bug is left undressed. It affects *a lot* of
> packages, including:
> - nodejs
> - openstack-dashboard
> 
> And also, upstream seems to not care about it, as per the github issue
> set in the forwarded-to-url.
> 
> Laszlo, will you work on this?
> 
> 
> Hi,
> how does it affect "nodejs" ?
> 
> Jérémy

Well, not nodejs itself directly. Though a lot of javascript libraries
are build-depending on node-smash, like for example libjs-angularjs.
This breaks the dependency chain of many things, not only nodejs packages:

- libjs-angular-gettext
- libjs-angularjs-smart-table
- libjs-lrdragndrop
- libjs-magic-search
- libjs-twitter-bootstrap-wizard
- rickshaw: buggy deps smash, flagged for removal in 29.9 days

Then lots of things are in AUTORM status because of this:
- python-mpld3
- some owncloud stuff
- things related to d3
- prometheus
- ...

and affecting OpenStack dashboard and friends:
- horizon
- murano-dashboard
- python-xstatic-angular-cookies
- python-xstatic-angular-gettext
- python-xstatic-angular-lrdragndrop
- python-xstatic-angular-mock
- python-xstatic-angular
- python-xstatic-d3
- python-xstatic-magic-search
- python-xstatic-rickshaw
- python-xstatic-smart-table
- tuskar-ui

I didn't have my facts completely strait, though the point is:
node-smash removal from testing would impact lots of packages, so it'd
be nice to have a way to solve the issue ASAP. And I'm worried that
upstream wrote in the Github issue that nothing will be done. :(

Thomas Goirand (zigo)

Bug#803595: vtk-dicom: depends on vtk 5

[Andreas Beckmann]

Source: vtk-dicom
Version: 0.5.5-2
Severity: serious
Tags: sid
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,

Andreas

Processed: vtk-dicom: depends on vtk 5

[Debian Bug Tracking System]

Processing control commands:

> block 798164 with -1
Bug #798164 [src:vtk] vtk: do not ship in stretch
798164 was blocked by: 798174 803593 798169 798167 798172 798165 798166 801820 
798168 798170 798171 798963
798164 was not blocking any bugs.
Added blocking bug(s) of 798164: 803595

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

Processed: Re: Bug#803563: libncurses5-dev, libncursesw5-dev: removal of libncurses5-dev makes files disappear from ncurses-bin

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #803563 [libncurses5-dev,libncursesw5-dev] libncurses5-dev, 
libncursesw5-dev: removal of libncurses5-dev makes files disappear from 
ncurses-bin
Severity set to 'normal' from 'serious'

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

Processed: wpa: diff for NMU version 2.3-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 787371 + patch
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Added tag(s) patch.
> tags 787371 + pending
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Added tag(s) pending.
> tags 787372 + patch
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Added tag(s) patch.
> tags 787372 + pending
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Added tag(s) pending.
> tags 787373 + patch
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Added tag(s) patch.
> tags 787373 + pending
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Added tag(s) pending.
> tags 795740 + pending
Bug #795740 [src:wpa] wpa: Incomplete WPS and P2P NFC NDEF record payload 
length validation
Added tag(s) pending.

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

Processed: wpa: diff for NMU version 2.3-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 787371 + patch
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787371 + pending
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787372 + patch
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787372 + pending
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787373 + patch
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 787373 + pending
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 795740 + pending
Bug #795740 [src:wpa] wpa: Incomplete WPS and P2P NFC NDEF record payload 
length validation
Ignoring request to alter tags of bug #795740 to the same tags previously set

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

Bug#787371: wpa: diff for NMU version 2.3-2.2

[Salvatore Bonaccorso]

Control: tags 787371 + patch
Control: tags 787371 + pending
Control: tags 787372 + patch
Control: tags 787372 + pending
Control: tags 787373 + patch
Control: tags 787373 + pending
Control: tags 795740 + pending

Dear maintainer,

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

Regards,
Salvatore
diff -Nru wpa-2.3/debian/changelog wpa-2.3/debian/changelog
--- wpa-2.3/debian/changelog	2015-08-30 15:30:35.0 +0200
+++ wpa-2.3/debian/changelog	2015-10-31 14:18:37.0 +0100
@@ -1,3 +1,22 @@
+wpa (2.3-2.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add patch to address CVE-2015-4141.
+CVE-2015-4141: WPS UPnP vulnerability with HTTP chunked transfer
+encoding. (Closes: #787372)
+  * Add patch to address CVE-2015-4142.
+CVE-2015-4142: Integer underflow in AP mode WMM Action frame processing.
+(Closes: #787373)
+  * Add patches to address CVE-2015-414{3,4,5,6}
+CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 CVE-2015-4146: EAP-pwd missing
+payload length validation. (Closes: #787371)
+  * Add patch to address 2015-5 vulnerability.
+NFC: Fix payload length validation in NDEF record parser (Closes: #795740)
+  * Thanks to Julian Wollrath  for the initial debdiff
+provided in #787371.
+
+ -- Salvatore Bonaccorso   Sat, 31 Oct 2015 14:13:50 +0100
+
 wpa (2.3-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru wpa-2.3/debian/patches/2015-2/0001-WPS-Fix-HTTP-chunked-transfer-encoding-parser.patch wpa-2.3/debian/patches/2015-2/0001-WPS-Fix-HTTP-chunked-transfer-encoding-parser.patch
--- wpa-2.3/debian/patches/2015-2/0001-WPS-Fix-HTTP-chunked-transfer-encoding-parser.patch	1970-01-01 01:00:00.0 +0100
+++ wpa-2.3/debian/patches/2015-2/0001-WPS-Fix-HTTP-chunked-transfer-encoding-parser.patch	2015-10-31 14:18:37.0 +0100
@@ -0,0 +1,49 @@
+From 5acd23f4581da58683f3cf5e36cb71bbe4070bd7 Mon Sep 17 00:00:00 2001
+From: Jouni Malinen 
+Date: Tue, 28 Apr 2015 17:08:33 +0300
+Subject: [PATCH] WPS: Fix HTTP chunked transfer encoding parser
+
+strtoul() return value may end up overflowing the int h->chunk_size and
+resulting in a negative value to be stored as the chunk_size. This could
+result in the following memcpy operation using a very large length
+argument which would result in a buffer overflow and segmentation fault.
+
+This could have been used to cause a denial service by any device that
+has been authorized for network access (either wireless or wired). This
+would affect both the WPS UPnP functionality in a WPS AP (hostapd with
+upnp_iface parameter set in the configuration) and WPS ER
+(wpa_supplicant with WPS_ER_START control interface command used).
+
+Validate the parsed chunk length value to avoid this. In addition to
+rejecting negative values, we can also reject chunk size that would be
+larger than the maximum configured body length.
+
+Thanks to Kostya Kortchinsky of Google security team for discovering and
+reporting this issue.
+
+Signed-off-by: Jouni Malinen 
+---
+ src/wps/httpread.c | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/src/wps/httpread.c b/src/wps/httpread.c
+index 2f08f37..d2855e3 100644
+--- a/src/wps/httpread.c
 b/src/wps/httpread.c
+@@ -533,6 +533,13 @@ static void httpread_read_handler(int sd, void *eloop_ctx, void *sock_ctx)
+ 	if (!isxdigit(*cbp))
+ 		goto bad;
+ 	h->chunk_size = strtoul(cbp, NULL, 16);
++	if (h->chunk_size < 0 ||
++	h->chunk_size > h->max_bytes) {
++		wpa_printf(MSG_DEBUG,
++			   "httpread: Invalid chunk size %d",
++			   h->chunk_size);
++		goto bad;
++	}
+ 	/* throw away chunk header
+ 	 * so we have only real data
+ 	 */
+-- 
+1.9.1
+
diff -Nru wpa-2.3/debian/patches/2015-3/0001-AP-WMM-Fix-integer-underflow-in-WMM-Action-frame-par.patch wpa-2.3/debian/patches/2015-3/0001-AP-WMM-Fix-integer-underflow-in-WMM-Action-frame-par.patch
--- wpa-2.3/debian/patches/2015-3/0001-AP-WMM-Fix-integer-underflow-in-WMM-Action-frame-par.patch	1970-01-01 01:00:00.0 +0100
+++ wpa-2.3/debian/patches/2015-3/0001-AP-WMM-Fix-integer-underflow-in-WMM-Action-frame-par.patch	2015-10-31 14:18:37.0 +0100
@@ -0,0 +1,41 @@
+From ef566a4d4f74022e1fdb0a2addfe81e6de9f4aae Mon Sep 17 00:00:00 2001
+From: Jouni Malinen 
+Date: Wed, 29 Apr 2015 02:21:53 +0300
+Subject: [PATCH] AP WMM: Fix integer underflow in WMM Action frame parser
+
+The length of the WMM Action frame was not properly validated and the
+length of the information elements (int left) could end up being
+negative. This would result in reading significantly past the stack
+buffer while parsing the IEs in ieee802_11_parse_elems() and while doing
+so, resulting in segmentation fault.
+
+This can result in an invalid frame being used for a denial of service
+attack (hostapd process killed) against an AP 

Processed: wpa: diff for NMU version 2.3-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 787371 + patch
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787371 + pending
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787372 + patch
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787372 + pending
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787373 + patch
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 787373 + pending
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 795740 + pending
Bug #795740 [src:wpa] wpa: Incomplete WPS and P2P NFC NDEF record payload 
length validation
Ignoring request to alter tags of bug #795740 to the same tags previously set

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

Processed: wpa: diff for NMU version 2.3-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags 787371 + patch
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787371 + pending
Bug #787371 [src:wpa] wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 
CVE-2015-4146: EAP-pwd missing payload length validation
Ignoring request to alter tags of bug #787371 to the same tags previously set
> tags 787372 + patch
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787372 + pending
Bug #787372 [src:wpa] wpa: CVE-2015-4141: WPS UPnP vulnerability with HTTP 
chunked transfer encoding
Ignoring request to alter tags of bug #787372 to the same tags previously set
> tags 787373 + patch
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 787373 + pending
Bug #787373 [src:wpa] wpa: CVE-2015-4142: Integer underflow in AP mode WMM 
Action frame processing
Ignoring request to alter tags of bug #787373 to the same tags previously set
> tags 795740 + pending
Bug #795740 [src:wpa] wpa: Incomplete WPS and P2P NFC NDEF record payload 
length validation
Ignoring request to alter tags of bug #795740 to the same tags previously set

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

Bug#803566: kmidimon: FTBFS: add_custom_target cannot create target "uninstall"

[Chris Lamb]

Source: kmidimon
Version: 0.7.5-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,

kmidimon fails to build from source in unstable/amd64:

  [..]

  -- checking for module 'drumstick-alsa>=0.5'
  --   found drumstick-alsa, version 0.5.0
  -- kmidimon 0.7.5 install prefix: /usr
  CMake Warning (dev) at /usr/lib/automoc4/Automoc4Config.cmake:179
  (get_directory_property):
Policy CMP0059 is not set: Do no treat DEFINITIONS as a built-in
directory
property.  Run "cmake --help-policy CMP0059" for policy details. 
Use the
cmake_policy command to set the policy and suppress this warning.
  Call Stack (most recent call first):
/usr/lib/automoc4/Automoc4Config.cmake:243 (_add_automoc4_target)
/usr/share/kde4/apps/cmake/modules/KDE4Macros.cmake:1026
(_automoc4_kde4_pre_target_handling)
src/CMakeLists.txt:68 (KDE4_ADD_EXECUTABLE)
  This warning is for project developers.  Use -Wno-dev to suppress it.
  
  CMake Error at CMakeLists.txt:135 (ADD_CUSTOM_TARGET):
add_custom_target cannot create target "uninstall" because another
target
with the same name already exists.  The existing target is a custom
target
created in source directory
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5". 
See
documentation for policy CMP0002 for more details.
  
  
  -- Configuring incomplete, errors occurred!
  See also
  
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
  See also
  
"/home/lamby/temp/cdt.20151031125942.DIQJT2tM3F/kmidimon-0.7.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
  /usr/share/cdbs/1/class/cmake.mk:55: recipe for target
  'obj-x86_64-linux-gnu/CMakeCache.txt' failed
  make: *** [obj-x86_64-linux-gnu/CMakeCache.txt] Error 1

  [..]

The full build log is attached.


Regards,

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


kmidimon.0.7.5-1.unstable.amd64.log.txt.gz
Description: application/gzip

Bug#803568: [Debian-astro-maintainers] Bug#803568: stellarium: FTBFS: StelSkyCultureMgr.hpp:47:1: error: expected class-name before '{' token

[Alexander Wolf]

Hi!

2015-10-31 19:09 GMT+06:00 Chris Lamb :

> Source: stellarium
> Version: 0.13.3-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,
>
> stellarium fails to build from source in unstable/amd64:
>
>   [..]
>
>   In file included from
>
> /home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.cpp:20:0:
>
> /home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:47:1:
>   error: expected class-name before '{' token
>{
>^
>
> /home/lamby/temp/cdt.20151031125946.xqReuhpbMC/stellarium-0.13.3/src/core/StelSkyCultureMgr.hpp:48:2:
>   error: 'Q_OBJECT' does not name a type
> Q_OBJECT
> ^
>

It's already fixed in upstream (version 0.14.0 + we have patch for version
0.13.3 -
http://bazaar.launchpad.net/~stellarium/stellarium/0.13/revision/6940)

-- 
With best regards, Alexander

Processed: found 803565 in 1:5.0.0~alpha1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 803565 1:5.0.0~alpha1-1
Bug #803565 [ure] ure: removal of ure makes files disappear from 
libreoffice-common: /usr/lib/libreoffice/program/unorc
There is no source info for the package 'ure' at version '1:5.0.0~alpha1-1' 
with architecture ''
Unable to make a source version for version '1:5.0.0~alpha1-1'
Marked as found in versions 1:5.0.0~alpha1-1.
> thanks
Stopping processing here.

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

Bug#803565: ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc

[Rene Engelhard]

On Sat, Oct 31, 2015 at 02:18:56PM +0100, Rene Engelhard wrote:
> That probably explains #801152
> I tried a upgrade/downgrade in #801152 but probably because I did it
> "the right way" the issue didn't appear.

#801552 that is

Regards,

Rene

Bug#803565: ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc

[Rene Engelhard]

Hi again,

On Sat, Oct 31, 2015 at 02:18:56PM +0100, Rene Engelhard wrote:
> Which is not really helpful given it will basically remove LO, too. But only
> the arch-dep parts, so yes, the "properly but not properly installed"
> libreoffice-common stays.

Ah, no, it doesn't:

# apt-get remove ure
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  fonttools-eexecop
Use 'apt-get autoremove' to remove it.
The following packages will be REMOVED:
  libreoffice libreoffice-avmedia-backend-gstreamer libreoffice-base
  libreoffice-base-core libreoffice-base-drivers libreoffice-calc
  libreoffice-common libreoffice-core libreoffice-dev libreoffice-draw
[...]

So I still don't know how one can get into a situation where this matters
(as in #801552).

> P.S: Perfect timing, I almost wanted to upload 1:5.0.3~rc2-1 now :)

Added the Breaks: anyway...

Regards,

Rene

Bug#803565: ure: removal of ure makes files disappear from libreoffice-common: /usr/lib/libreoffice/program/unorc

[Andreas Beckmann]

On 2015-10-31 14:56, Rene Engelhard wrote:
> Hi again,
> 
> On Sat, Oct 31, 2015 at 02:18:56PM +0100, Rene Engelhard wrote:
>> Which is not really helpful given it will basically remove LO, too. But only
>> the arch-dep parts, so yes, the "properly but not properly installed"
>> libreoffice-common stays.
> 
> Ah, no, it doesn't:
> 
> # apt-get remove ure

Maybe just dpkg -r ure to keep the dependencies installed ... the
reproduction command may have been too simple, the log has the full
etails. (I have a script doing these tests ... and there was a valid
installation possible (all relationships satisfied, no --force used)
first mixing old libreoffice-common and new ure and thereafter removing
ure resulting in this disapperance)

> So I still don't know how one can get into a situation where this matters
> (as in #801552).

Maybe downgrading libreoffice-common before downgrading ure.


Andras

Bug#803306: Bug#803272: libreoffice-dev: apt-get dist-upgrade -u -f *HANGS* on libreoffice-dev 3a5.0.3~rc1-2

[Rene Engelhard]

Hi,

On Wed, Oct 28, 2015 at 05:03:12PM +0100, Rene Engelhard wrote:
> > I'll try to unhose my system and upgrade it overnight (old machine, but 
> > that's what my employer wishes me to use...).
> 
> Remove -dev-doc for now, maybe? (And -dev.).
> And reinstall them afterwards?

No, doesn't work. Even dist-upgrading to the fixed version with conflicts
doesn't work since apt wants -f install anymore. Even after removing -dev
and -dev-doc it fails on all(?) of the other preinsts.

Clean upgrades work but once you are stuck here you probably need a hammer
to get out of it.

Like manually dpkg -r/-P ing the packages.
(I did # dpkg -P `dpkg -l | grep libreoffice  | grep ^i | awk '{ print $2 }' | 
xargs` python3-uno)

No idea how to get out of this by package actions, sorry. Then again, this
is testing/unstable/experimental... (Shouldn't happen, but..)

The fix for "clean" upgrades works for me and will be uploaded RSN.

Sorry for the breakage.

Regards,
 
Rene

Processed: Re: pocl: With 0.11 some test are failing

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 799322 patch
Bug #799322 [src:pocl] pocl: FTBFS: (gcc5 related?) symbols mismatches + test 
failures
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#799322: pocl: With 0.11 some test are failing

[James Price]

tag 799322 patch
thanks

On Wed, 14 Oct 2015 18:33:01 +0200 Gert Wollny  wrote:
> Hi, I had a look into the package, but I for me with 0.11 an llvm-3.6
> two tests are failing - this has also already been reported upstream:
> 
> https://github.com/pocl/pocl/issues/181
> 

I’ve attached a patch that fixes these test failures. With this patch, and 
removing the libpocl1.symbols file as mentioned earlier, I can now build the 
0.11 package successfully. I’ve forwarded the patch upstream.

There is now a 0.12 release as well, so I’m not sure whether you intend to 
finish the 0.11 package first or just skip straight to 0.12. The 0.12 release 
seems to build cleanly for me and passes all the tests (with the same patch 
applied).

James




fix-image-args.patch
Description: Binary data

Bug#803563: libncurses5-dev, libncursesw5-dev: removal of libncurses5-dev makes files disappear from ncurses-bin

[Sven Joachim]

Control: severity -1 normal

On 2015-10-31 13:53 +0100, Andreas Beckmann wrote:

> Package: libncurses5-dev,libncursesw5-dev
> Version: 6.0+20151024-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts replaces-without-breaks
>
> Hi,
>
> during a test with piuparts and DOSE tools I noticed your package causes
> removal of files that also belong to another package.
> This is caused by using Replaces without corresponding Breaks.

I have avoided using Breaks here since it has the potential of
complicating upgrades, but I can add a versioned dependency on
ncurses-bin to the -dev packages if it makes piuparts happy.

> The installation sequence to reproduce this problem is
>
>   apt-get install ncurses-bin/stretch
>   # (1)
>   apt-get install libncurses5-dev/sid
>   apt-get remove libncurses5-dev/sid
>   # (2)
>
> The list of installed files at points (1) and (2) should be identical,
> but the following files have disappeared:
>
>   /usr/bin/ncurses5-config
>   /usr/share/man/man1/ncurses5-config.1.gz
>
> This is a serious bug violating policy 7.6, see
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
> and also see the footnote that describes this incorrect behavior
> https://www.debian.org/doc/debian-policy/footnotes.html#f53

The disappearing files are not required for ncurses-bin to work
correctly (hint: ncurses-bin does not depend on libncurses5-dev), hence
I disagree with the severity.

Cheers,
   Sven

Bug#802803: bluedevil: after qt 5.5.1 upgrade, bluedevill does no more work (connexion alway fails)

[Diederik de Haas]

On Saturday 31 October 2015 22:28:30 Eric Valette wrote:
> Now it connects correctly each time. Dunno what has changed (because of 
> course I did the remove device before when desesperately tried to make 
> it work again).

Feel free to close the bug in that case ;-)


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

Bug#802060: marked as done (aiopg: FTBFS: ImportError: No module named 'psycopg2')

[Debian Bug Tracking System]

Your message dated Sat, 31 Oct 2015 22:48:40 +
with message-id 
and subject line Bug#802060: fixed in aiopg 0.7.0-3
has caused the Debian Bug report #802060,
regarding aiopg: FTBFS: ImportError: No module named 'psycopg2'
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.)


-- 
802060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aiopg
Version: 0.7.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

writing manifest file 'aiopg.egg-info/SOURCES.txt'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:170: cd /aiopg-0.7.0/.pybuild/pythonX.Y_3.5/build; python3.5 -m 
unittest discover -v 
aiopg (unittest.loader._FailedTest) ... ERROR

==
ERROR: aiopg (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: aiopg
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/aiopg-0.7.0/.pybuild/pythonX.Y_3.5/build/aiopg/__init__.py", line 5, 
in 
from .connection import connect, Connection, TIMEOUT as DEFAULT_TIMEOUT
  File "/aiopg-0.7.0/.pybuild/pythonX.Y_3.5/build/aiopg/connection.py", line 5, 
in 
import psycopg2
ImportError: No module named 'psycopg2'


--
Ran 1 test in 0.000s

FAILED (errors=1)

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/aiopg.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: aiopg
Source-Version: 0.7.0-3

We believe that the bug you reported is fixed in the latest version of
aiopg, 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 802...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated aiopg 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, 31 Oct 2015 23:28:24 +0100
Source: aiopg
Binary: python3-aiopg
Architecture: source all
Version: 0.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 python3-aiopg - PostgreSQL integration with asyncio
Closes: 802060
Changes:
 aiopg (0.7.0-3) unstable; urgency=medium
 .
   * Fix a typo in Build-Depends (and depend on Python 3.X version of psycopg2
 package, closes: 802060)
   * Add python3-sqlalchemy to Build-Depends (needed by python3.5's new
 "feature")
Checksums-Sha1:
 b06123ec07f27d5ad8322e57e970d18b6395d8df 2001 aiopg_0.7.0-3.dsc
 3a209f4db0ba7506ad928fe8a5bdf1a8aacf0b5f 2192 aiopg_0.7.0-3.debian.tar.xz
 ff1b7df164ccaf92b4f498aa40fbbd5444dcec99 21318 python3-aiopg_0.7.0-3_all.deb
Checksums-Sha256:
 15d89f139678f9e00499cb1ee478f76f22e6af29281cc75b712caa4358bdaa7f 2001 
aiopg_0.7.0-3.dsc
 c9200211596fef5ff6aae5e98cc76c73af1aab037bbcdebbb26bab1418e49085 2192 
aiopg_0.7.0-3.debian.tar.xz
 e73b4ec9a52981a24ed6d0f780efbdb73d13a60b08a87dda5f42d7e96a8dabbc 21318 
python3-aiopg_0.7.0-3_all.deb
Files:
 20d39889a3de61ec9b6f534d9ec31345 2001 python optional aiopg_0.7.0-3.dsc
 a4adf1060f76c78a865e4decdfa9dafd 2192 python optional 
aiopg_0.7.0-3.debian.tar.xz
 cec4c7c4af06a0546c6d856cdf1b6b68 21318 python optional 
python3-aiopg_0.7.0-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWNUMeAAoJEK728aKnRXZFykoP/08q4VOpeZkttdUhrRDtH9Ll
tg85uUlpZaWZGpivU8+6HarAHgXpTiVwLVXdVbRUrz6hQ9nD7NVkDX60Dg/W29cu
2oO3FRSaebMJWHsUMPcKF0Rl0n5zbC443y29B9WAzZMjNhn1wPTVYTlSGuU9yDWp

Bug#803595: waiting for gdcm clearing new

[Gert Wollny]

Hello, 

I'll look into this as soon as gdcm-2.6 has cleared NEW because 
vtk-dicom depends on gdcm which also needed the transition to vtk6. 

Best,
Gert

Bug#802281: icedove: Stuck at "Welcome to Icedove"

[Guido Günther]

On Mon, Oct 19, 2015 at 02:09:23PM +1300, Eliot Blennerhassett wrote:
> I can also confirm that 64 bit thunderbird 38.3.0 does *not* have this
> problem.

This ic caused by Debian using a newer jquery. If you use the jquery
from upstram thunderbird (which is 1.6) it works again.

Cheers,
 -- Guido

Processed: Bug#802060 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 802060 pending
Bug #802060 [src:aiopg] aiopg: FTBFS: ImportError: No module named 'psycopg2'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802060: marked as pending

[Piotr Ożarowski]

tag 802060 pending
thanks

Hello,

Bug #802060 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://git.debian.org/?p=python-modules/packages/aiopg.git;a=commitdiff;h=fab2d6f

---
commit fab2d6fb11f0ccf2c41688797449f1ef67746ffd
Author: Piotr Ożarowski 
Date:   Sat Oct 31 23:42:05 2015 +0100

Fix a typo in Build-Depends (and depend on Python 3.X version of psycopg2 
package, closes: 802060)

diff --git a/debian/changelog b/debian/changelog
index 6816a9f..0093a24 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+aiopg (0.7.0-3) unstable; urgency=medium
+
+  * Fix a typo in Build-Depends (and depend on Python 3.X version of psycopg2
+package, closes: 802060)
+  * Add python3-sqlalchemy to Build-Depends (needed by python3.5's new
+"feature")
+
+ -- Piotr Ożarowski   Sat, 31 Oct 2015 23:28:24 +0100
+
 aiopg (0.7.0-1) unstable; urgency=low
 
   * Initial release (closes: 795413)

Bug#803597:

[Tautvydas Žukauskas]

found 803597 flashplugin-nonfree/1:3.6.1tags 803597 +unreproducible
+moreinfothanks

Bug#803618: mysql-workbench, FTBFS on architectures where char is unsigned.

[peter green]

Package: mysql-workbench
Version:  6.3.4+dfsg-2
Severity: serious

When building mysql-workbench on arm*, ppc* and s390x there are errors like.

/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:
 In function 'int mysql_parser::hexlo(int)':
/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:3890:3:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
   };
   ^
/«BUILDDIR»/mysql-workbench-6.3.4+dfsg/library/sql.parser/source/ctype-utf8.cpp:3890:3:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]


then the error repeats a load of times (with the same sourcecode 
position given each time).


The signdness of plain char is implementation dependent. On linux 
systems it depends on the CPU architecture.


Investigating the sourcecode shows an array of char with many values 
initialised to -1. To fix this I changed data type to signed char


I have successfully built the package with this change in a raspbian 
stretch-staging environment and uploaded to raspbian. I have not tested 
it beyond that. A debdiff can be found at  
http://debdiffs.raspbian.org/main/m/mysql-workbench/mysql-workbench_6.3.4+dfsg-2+rpi1.debdiff  
No intent to NMU in Debian.

Processed: tagging 803618

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 803618 + help upstream
Bug #803618 [mysql-workbench] mysql-workbench, FTBFS on architectures where 
char is unsigned.
Added tag(s) help and upstream.
> thanks
Stopping processing here.

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

Processed: bug 803618 is forwarded to https://bugs.mysql.com/bug.php?id=78950

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 803618 https://bugs.mysql.com/bug.php?id=78950
Bug #803618 [mysql-workbench] mysql-workbench, FTBFS on architectures where 
char is unsigned.
Set Bug forwarded-to-address to 'https://bugs.mysql.com/bug.php?id=78950'.
> thanks
Stopping processing here.

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

Processed: tagging 803618

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 803618 - help
Bug #803618 [mysql-workbench] mysql-workbench, FTBFS on architectures where 
char is unsigned.
Removed tag(s) help.
> thanks
Stopping processing here.

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

Bug#802866: marked as done (fcitx-frontend-qt5 version 1.0.0-1 can't be installed)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2015 10:45:16 +0800
with message-id