Processed: retitle 754713 to elmerfem: FTBFS: The MPI version needs parpack. Disabling MPI.

[Debian Bug Tracking System]

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

> retitle 754713 elmerfem: FTBFS: The MPI version needs parpack. Disabling MPI.
Bug #754713 [src:elmerfem] elmerfem: FTBFS on powrpc, ppc64el, s390x, hppa: The 
MPI version needs parpack. Disabling MPI.
Changed Bug title to 'elmerfem: FTBFS: The MPI version needs parpack. Disabling 
MPI.' from 'elmerfem: FTBFS on powrpc, ppc64el, s390x, hppa: The MPI version 
needs parpack. Disabling MPI.'.
> thanks
Stopping processing here.

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

Processed: Re: elmer: fails to remove: rmdir: failed to remove '/usr/share/ElmerGUI/edf': Directory not empty

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -pending -fixed
Bug #720146 [elmer] elmer: fails to remove: rmdir: failed to remove 
'/usr/share/ElmerGUI/edf': Directory not empty
Removed tag(s) pending.
Bug #720146 [elmer] elmer: fails to remove: rmdir: failed to remove 
'/usr/share/ElmerGUI/edf': Directory not empty
Removed tag(s) fixed.

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

Bug#720146: elmer: fails to remove: rmdir: failed to remove '/usr/share/ElmerGUI/edf': Directory not empty

[Tobias Frost]

Source: elmerfem
Followup-For: Bug #720146
Control: tags -1 -pending -fixed

Removing tags fixed and pending, as a fix has never entered the archives and 
the defintion of "soon"
is not meaning "more than two years".

-- tobi

fixed / pending as defined here:
[1] https://www.debian.org/Bugs/Developer#tags


> Date: Wed, 12 Feb 2014 01:53:58 +0400
> From: Boris Pek 
> Subject: Re: elmer: fails to remove: rmdir: failed to remove 
> '/usr/share/ElmerGUI/edf': Directory not empty
>
> control: tags -1 + fixed pending

> during a test with piuparts I noticed your package fails to remove.


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

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

Bug#803555: marked as done (pygame: FTBFS in experimental)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 05:23:46 +
with message-id 
and subject line Bug#803555: fixed in pygame 1.9.2~pre~r3449-1
has caused the Debian Bug report #803555,
regarding pygame: FTBFS in experimental
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.)


-- 
803555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: pygame
Source-Version: 1.9.2~pre~r3449-1

We believe that the bug you reported is fixed in the latest version of
pygame, 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.
Vincent Cheng  (supplier of updated pygame 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: Tue, 03 May 2016 21:39:41 -0700
Source: pygame
Binary: python-pygame python3-pygame
Architecture: source
Version: 1.9.2~pre~r3449-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Vincent Cheng 
Description:
 python-pygame - SDL bindings for games development in Python (Python 2)
 python3-pygame - SDL bindings for games development in Python (Python 3)
Closes: 750315 803555 812717
Changes:
 pygame (1.9.2~pre~r3449-1) experimental; urgency=medium
 .
   [ Vincent Cheng ]
   * Stop symlinking fonts into deprecated /usr/share/pyshared/ directory;
 fixes FTBFS. (Closes: #750315)
   * Drop doc-base file.
   * Update Standards version to 3.9.8.
 .
   [ Stefano Rivera ]
   * New upstream snapshot.
 - Fixes FTBFS with clang. (Closes: #812717)
   * Support Python 3 in setup_ignore_portmidi_on_non_linux.diff
   * Drop ffmpeg, and smpeg dependencies, upstream has dropped movie support.
 (Closes: #803555)
   * Run tests against built pygame, don't 

Bug#805852: marked as done (depends on libjpeg8)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 04:52:35 +
with message-id 
and subject line Bug#814873: fixed in ipe 7.1.10-2
has caused the Debian Bug report #814873,
regarding depends on libjpeg8
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.)


-- 
814873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libipe7.1.10
Version: 7.1.10-1
Severity: wishlist

Dear Maintainer(s),

the library depends on libjpeg8 now and not on libjpeg62-turbo as the
version before. What is the reason for that? A comment in the changelog
would be nice.

Regards,
jvp.

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

Kernel: Linux 4.3.0
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libipe7.1.10 depends on:
ii  libc6   2.19-20
ii  libcairo2   1.14.4-1
ii  libfreetype62.6.1-0.1
ii  libgcc1 1:5.2.1-23
ii  libjpeg88d1-2
ii  liblua5.2-0 5.2.4-1
ii  libpng12-0  1.2.54-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.2.1-23
ii  zlib1g  1:1.2.8.dfsg-2+b1

libipe7.1.10 recommends no packages.

libipe7.1.10 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ipe
Source-Version: 7.1.10-2

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

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

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated ipe 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: Tue, 03 May 2016 23:04:20 -0500
Source: ipe
Binary: ipe libipe7.1.10 libipe-dev
Architecture: source amd64
Version: 7.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Description:
 ipe- drawing editor for creating figures in PDF or PS formats
 libipe-dev - Ipe library used by ipelets (developer files)
 libipe7.1.10 - Ipe library used by ipelets
Closes: 805852 814873
Changes:
 ipe (7.1.10-2) unstable; urgency=medium
 .
   * patches/fix-moc.patch: Remove.  Use QT_SELECT to tell qtchooser which
 version of Qt we want.
 .
   * control: Revert back to libjpeg-dev.  Appreciate the gentle prodding
 by all.  Closes: #805852, #814873.
Checksums-Sha1:
 fd6b082c6dc6a9bbf590f52a45a5e968bb568d7b 2151 ipe_7.1.10-2.dsc
 373cb13fa74fe4714c292d7c2fa6b304e3ad0aac 9276 ipe_7.1.10-2.debian.tar.xz
 ea305f3bb3661660e0fd5dfe0412261f8a516120 1659130 ipe-dbgsym_7.1.10-2_amd64.deb
 b3dc4ddc1eac470043af661de96bc1a2dbabe1a4 913682 ipe_7.1.10-2_amd64.deb
 87428b173eefe2d4021902f33fe980e9273cd451 34172 libipe-dev_7.1.10-2_amd64.deb
 5de3959098d5bd14fd0e029993455bee7e82eba3 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 028df1c1c6db193732a324c3aa16279385d9d18b 314116 libipe7.1.10_7.1.10-2_amd64.deb
Checksums-Sha256:
 26cb4d6fa6f48e721223d0d9b443bbaaf461c06584a78e61256fdfc0f166437c 2151 
ipe_7.1.10-2.dsc
 b8115f7e575b43439f7029d0b2221a4c4b7359ec84033ec4c5c0e22fda0d3fee 9276 
ipe_7.1.10-2.debian.tar.xz
 2d8fd8122b4556aae26e4aa0641bc02d5ffd2fa2582a58a336051f8dca6d0f2e 1659130 
ipe-dbgsym_7.1.10-2_amd64.deb
 59a32f9fa09b3bd1feebb6061b74347ed9744bdae1ff66fae2f0745889f7495e 913682 
ipe_7.1.10-2_amd64.deb
 83346f858bff6cbe099a54706422385c04dca943d2d3b34901b533c36a837549 34172 
libipe-dev_7.1.10-2_amd64.deb
 e5a0ceddb28ae68712006edf2d7056fca17427132410fe5ae5e23bdef5919cfd 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 bdb956b96a15e1b5011031f2f6374e4af22c6f7d8cec4797e6c6bfea0dd18003 314116 
libipe7.1.10_7.1.10-2_amd64.deb
Files:
 8e953f8cc7dda371b8a8519928f1770a 2151 graphics optional ipe_7.1.10-2.dsc
 f9910a062824b11c305025df1e7aeb84 9276 graphics optional 

Bug#805852: marked as done (depends on libjpeg8)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 04:52:35 +
with message-id 
and subject line Bug#805852: fixed in ipe 7.1.10-2
has caused the Debian Bug report #805852,
regarding depends on libjpeg8
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.)


-- 
805852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libipe7.1.10
Version: 7.1.10-1
Severity: wishlist

Dear Maintainer(s),

the library depends on libjpeg8 now and not on libjpeg62-turbo as the
version before. What is the reason for that? A comment in the changelog
would be nice.

Regards,
jvp.

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

Kernel: Linux 4.3.0
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libipe7.1.10 depends on:
ii  libc6   2.19-20
ii  libcairo2   1.14.4-1
ii  libfreetype62.6.1-0.1
ii  libgcc1 1:5.2.1-23
ii  libjpeg88d1-2
ii  liblua5.2-0 5.2.4-1
ii  libpng12-0  1.2.54-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.2.1-23
ii  zlib1g  1:1.2.8.dfsg-2+b1

libipe7.1.10 recommends no packages.

libipe7.1.10 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ipe
Source-Version: 7.1.10-2

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated ipe 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: Tue, 03 May 2016 23:04:20 -0500
Source: ipe
Binary: ipe libipe7.1.10 libipe-dev
Architecture: source amd64
Version: 7.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Description:
 ipe- drawing editor for creating figures in PDF or PS formats
 libipe-dev - Ipe library used by ipelets (developer files)
 libipe7.1.10 - Ipe library used by ipelets
Closes: 805852 814873
Changes:
 ipe (7.1.10-2) unstable; urgency=medium
 .
   * patches/fix-moc.patch: Remove.  Use QT_SELECT to tell qtchooser which
 version of Qt we want.
 .
   * control: Revert back to libjpeg-dev.  Appreciate the gentle prodding
 by all.  Closes: #805852, #814873.
Checksums-Sha1:
 fd6b082c6dc6a9bbf590f52a45a5e968bb568d7b 2151 ipe_7.1.10-2.dsc
 373cb13fa74fe4714c292d7c2fa6b304e3ad0aac 9276 ipe_7.1.10-2.debian.tar.xz
 ea305f3bb3661660e0fd5dfe0412261f8a516120 1659130 ipe-dbgsym_7.1.10-2_amd64.deb
 b3dc4ddc1eac470043af661de96bc1a2dbabe1a4 913682 ipe_7.1.10-2_amd64.deb
 87428b173eefe2d4021902f33fe980e9273cd451 34172 libipe-dev_7.1.10-2_amd64.deb
 5de3959098d5bd14fd0e029993455bee7e82eba3 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 028df1c1c6db193732a324c3aa16279385d9d18b 314116 libipe7.1.10_7.1.10-2_amd64.deb
Checksums-Sha256:
 26cb4d6fa6f48e721223d0d9b443bbaaf461c06584a78e61256fdfc0f166437c 2151 
ipe_7.1.10-2.dsc
 b8115f7e575b43439f7029d0b2221a4c4b7359ec84033ec4c5c0e22fda0d3fee 9276 
ipe_7.1.10-2.debian.tar.xz
 2d8fd8122b4556aae26e4aa0641bc02d5ffd2fa2582a58a336051f8dca6d0f2e 1659130 
ipe-dbgsym_7.1.10-2_amd64.deb
 59a32f9fa09b3bd1feebb6061b74347ed9744bdae1ff66fae2f0745889f7495e 913682 
ipe_7.1.10-2_amd64.deb
 83346f858bff6cbe099a54706422385c04dca943d2d3b34901b533c36a837549 34172 
libipe-dev_7.1.10-2_amd64.deb
 e5a0ceddb28ae68712006edf2d7056fca17427132410fe5ae5e23bdef5919cfd 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 bdb956b96a15e1b5011031f2f6374e4af22c6f7d8cec4797e6c6bfea0dd18003 314116 
libipe7.1.10_7.1.10-2_amd64.deb
Files:
 8e953f8cc7dda371b8a8519928f1770a 2151 graphics optional ipe_7.1.10-2.dsc
 f9910a062824b11c305025df1e7aeb84 9276 graphics optional 

Bug#814873: marked as done (src:ipe: build-depends on libjpeg8-dev)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 04:52:35 +
with message-id 
and subject line Bug#805852: fixed in ipe 7.1.10-2
has caused the Debian Bug report #805852,
regarding src:ipe: build-depends on libjpeg8-dev
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.)


-- 
805852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipe
Version: 7.1.10-1
Severity: normal

Hi!
ipe holds the dubious honor of being the only package build-depending on
libjpeg8-dev.  This goes against the jpeg8->jpeg62-turbo transition.
I see this has been introduced in SVN commit 47177, without any explanation.
I tried changing this b-dependency to libjpeg-dev -- ipe builds successfully
so it doesn't use any APIs introduced by jpeg8.

Is there a reason to use jpeg8?  The security team opposed having two jpeg
libraries in jessie, I guess the same applies to stretch.
--- End Message ---
--- Begin Message ---
Source: ipe
Source-Version: 7.1.10-2

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated ipe 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: Tue, 03 May 2016 23:04:20 -0500
Source: ipe
Binary: ipe libipe7.1.10 libipe-dev
Architecture: source amd64
Version: 7.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Description:
 ipe- drawing editor for creating figures in PDF or PS formats
 libipe-dev - Ipe library used by ipelets (developer files)
 libipe7.1.10 - Ipe library used by ipelets
Closes: 805852 814873
Changes:
 ipe (7.1.10-2) unstable; urgency=medium
 .
   * patches/fix-moc.patch: Remove.  Use QT_SELECT to tell qtchooser which
 version of Qt we want.
 .
   * control: Revert back to libjpeg-dev.  Appreciate the gentle prodding
 by all.  Closes: #805852, #814873.
Checksums-Sha1:
 fd6b082c6dc6a9bbf590f52a45a5e968bb568d7b 2151 ipe_7.1.10-2.dsc
 373cb13fa74fe4714c292d7c2fa6b304e3ad0aac 9276 ipe_7.1.10-2.debian.tar.xz
 ea305f3bb3661660e0fd5dfe0412261f8a516120 1659130 ipe-dbgsym_7.1.10-2_amd64.deb
 b3dc4ddc1eac470043af661de96bc1a2dbabe1a4 913682 ipe_7.1.10-2_amd64.deb
 87428b173eefe2d4021902f33fe980e9273cd451 34172 libipe-dev_7.1.10-2_amd64.deb
 5de3959098d5bd14fd0e029993455bee7e82eba3 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 028df1c1c6db193732a324c3aa16279385d9d18b 314116 libipe7.1.10_7.1.10-2_amd64.deb
Checksums-Sha256:
 26cb4d6fa6f48e721223d0d9b443bbaaf461c06584a78e61256fdfc0f166437c 2151 
ipe_7.1.10-2.dsc
 b8115f7e575b43439f7029d0b2221a4c4b7359ec84033ec4c5c0e22fda0d3fee 9276 
ipe_7.1.10-2.debian.tar.xz
 2d8fd8122b4556aae26e4aa0641bc02d5ffd2fa2582a58a336051f8dca6d0f2e 1659130 
ipe-dbgsym_7.1.10-2_amd64.deb
 59a32f9fa09b3bd1feebb6061b74347ed9744bdae1ff66fae2f0745889f7495e 913682 
ipe_7.1.10-2_amd64.deb
 83346f858bff6cbe099a54706422385c04dca943d2d3b34901b533c36a837549 34172 
libipe-dev_7.1.10-2_amd64.deb
 e5a0ceddb28ae68712006edf2d7056fca17427132410fe5ae5e23bdef5919cfd 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 bdb956b96a15e1b5011031f2f6374e4af22c6f7d8cec4797e6c6bfea0dd18003 314116 
libipe7.1.10_7.1.10-2_amd64.deb
Files:
 8e953f8cc7dda371b8a8519928f1770a 2151 graphics optional ipe_7.1.10-2.dsc
 f9910a062824b11c305025df1e7aeb84 9276 graphics optional 
ipe_7.1.10-2.debian.tar.xz
 d4a0a1fad360042ceddc543704e14bef 1659130 debug extra 
ipe-dbgsym_7.1.10-2_amd64.deb
 ca70bcffc78f08b3535e5c1061114b48 913682 graphics optional 
ipe_7.1.10-2_amd64.deb
 632f5aaa2a192bbe840c6be49f0fe5ff 34172 libdevel optional 
libipe-dev_7.1.10-2_amd64.deb
 2d064f20154ef35896d667db271be0d3 3287762 debug extra 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 c0c70618b14069e610bf919d7ef54424 314116 libs optional 
libipe7.1.10_7.1.10-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#814873: marked as done (src:ipe: build-depends on libjpeg8-dev)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 04:52:35 +
with message-id 
and subject line Bug#814873: fixed in ipe 7.1.10-2
has caused the Debian Bug report #814873,
regarding src:ipe: build-depends on libjpeg8-dev
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.)


-- 
814873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipe
Version: 7.1.10-1
Severity: normal

Hi!
ipe holds the dubious honor of being the only package build-depending on
libjpeg8-dev.  This goes against the jpeg8->jpeg62-turbo transition.
I see this has been introduced in SVN commit 47177, without any explanation.
I tried changing this b-dependency to libjpeg-dev -- ipe builds successfully
so it doesn't use any APIs introduced by jpeg8.

Is there a reason to use jpeg8?  The security team opposed having two jpeg
libraries in jessie, I guess the same applies to stretch.
--- End Message ---
--- Begin Message ---
Source: ipe
Source-Version: 7.1.10-2

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

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

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated ipe 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: Tue, 03 May 2016 23:04:20 -0500
Source: ipe
Binary: ipe libipe7.1.10 libipe-dev
Architecture: source amd64
Version: 7.1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Steve M. Robbins 
Description:
 ipe- drawing editor for creating figures in PDF or PS formats
 libipe-dev - Ipe library used by ipelets (developer files)
 libipe7.1.10 - Ipe library used by ipelets
Closes: 805852 814873
Changes:
 ipe (7.1.10-2) unstable; urgency=medium
 .
   * patches/fix-moc.patch: Remove.  Use QT_SELECT to tell qtchooser which
 version of Qt we want.
 .
   * control: Revert back to libjpeg-dev.  Appreciate the gentle prodding
 by all.  Closes: #805852, #814873.
Checksums-Sha1:
 fd6b082c6dc6a9bbf590f52a45a5e968bb568d7b 2151 ipe_7.1.10-2.dsc
 373cb13fa74fe4714c292d7c2fa6b304e3ad0aac 9276 ipe_7.1.10-2.debian.tar.xz
 ea305f3bb3661660e0fd5dfe0412261f8a516120 1659130 ipe-dbgsym_7.1.10-2_amd64.deb
 b3dc4ddc1eac470043af661de96bc1a2dbabe1a4 913682 ipe_7.1.10-2_amd64.deb
 87428b173eefe2d4021902f33fe980e9273cd451 34172 libipe-dev_7.1.10-2_amd64.deb
 5de3959098d5bd14fd0e029993455bee7e82eba3 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 028df1c1c6db193732a324c3aa16279385d9d18b 314116 libipe7.1.10_7.1.10-2_amd64.deb
Checksums-Sha256:
 26cb4d6fa6f48e721223d0d9b443bbaaf461c06584a78e61256fdfc0f166437c 2151 
ipe_7.1.10-2.dsc
 b8115f7e575b43439f7029d0b2221a4c4b7359ec84033ec4c5c0e22fda0d3fee 9276 
ipe_7.1.10-2.debian.tar.xz
 2d8fd8122b4556aae26e4aa0641bc02d5ffd2fa2582a58a336051f8dca6d0f2e 1659130 
ipe-dbgsym_7.1.10-2_amd64.deb
 59a32f9fa09b3bd1feebb6061b74347ed9744bdae1ff66fae2f0745889f7495e 913682 
ipe_7.1.10-2_amd64.deb
 83346f858bff6cbe099a54706422385c04dca943d2d3b34901b533c36a837549 34172 
libipe-dev_7.1.10-2_amd64.deb
 e5a0ceddb28ae68712006edf2d7056fca17427132410fe5ae5e23bdef5919cfd 3287762 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 bdb956b96a15e1b5011031f2f6374e4af22c6f7d8cec4797e6c6bfea0dd18003 314116 
libipe7.1.10_7.1.10-2_amd64.deb
Files:
 8e953f8cc7dda371b8a8519928f1770a 2151 graphics optional ipe_7.1.10-2.dsc
 f9910a062824b11c305025df1e7aeb84 9276 graphics optional 
ipe_7.1.10-2.debian.tar.xz
 d4a0a1fad360042ceddc543704e14bef 1659130 debug extra 
ipe-dbgsym_7.1.10-2_amd64.deb
 ca70bcffc78f08b3535e5c1061114b48 913682 graphics optional 
ipe_7.1.10-2_amd64.deb
 632f5aaa2a192bbe840c6be49f0fe5ff 34172 libdevel optional 
libipe-dev_7.1.10-2_amd64.deb
 2d064f20154ef35896d667db271be0d3 3287762 debug extra 
libipe7.1.10-dbgsym_7.1.10-2_amd64.deb
 c0c70618b14069e610bf919d7ef54424 314116 libs optional 
libipe7.1.10_7.1.10-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#822976: gtk3-engines-unico: Package broken by GTK 3.16

[James Lu]

Hi George,

As far as I'm concerned, Unico itself isn't even a theme - it's an
engine that theme authors can borrow from. I don't think it has any
reverse dependencies in Debian, but various themes in Ubuntu (where the
package originates) have it listed as a dependency or used to.

Perhaps I should inquire with upstream on what exactly still uses Unico
in the coming days.



gl@millennium:~$ reverse-depends gtk3-engines-unico -r xenial
Reverse-Depends
===
* lubuntu-artwork-11-10
* lubuntu-artwork-12-04
* lubuntu-artwork-12-10
* lubuntu-artwork-13-04
* lubuntu-artwork-13-10
* lubuntu-artwork-14-04
* lubuntu-artwork-14-10
* lubuntu-artwork-15-04
* lubuntu-artwork-15-10
* lubuntu-artwork-16-04
* mythbuntu-default-settings

Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, powerpc, ppc64el, s390x

gl@millennium:~$ reverse-depends gtk3-engines-unico -r sid
No reverse dependencies found

Best,
James

On 03/05/2016 8:19 AM, George B. wrote:
> Hi James,
> 
> On 30/04/16 06:13, James Lu wrote:
>> Since newer GTK versions have already made it into the archive, does
>> that mean that this package no longer serves any purpose?
> 
> It would appear so - oxygen-gtk3 package was removed for the same
> reason.[1]
> 
>> From what I
>> can tell, GTK3 engines for Breeze and Xfce still exist elsewhere in the
>> archive: https://packages.debian.org/search?keywords=gtk3-engines-
> 
> Breeze was actually ported to CSS - I have already filed a bug with a
> request to rename the package to avoid confusion.[2]
> 
> The Xfce package contains a mix of partially converted and broken
> themes. [3]
> 
>> If this inevitably ends with Unico being removed, I guess I'm okay with
>> that too. What might be the best course of action here?
> 
> I guess the best solution would be to port the theme to CSS, but it is
> not the easiest. ;)
> 
> 
> Best regards,
> 
> George
> 
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797796
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822975
> [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762936
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#818060: marked as done (FTBFS: pep8 module is now in python-pep8 package)

[Debian Bug Tracking System]

Your message dated Wed, 04 May 2016 01:34:29 +
with message-id 
and subject line Bug#818060: fixed in shortuuid 0.4.3-1.1
has caused the Debian Bug report #818060,
regarding FTBFS: pep8 module is now in python-pep8 package
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.)


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

Building the package fails in the test suite because the pep8 module is now in 
the python-pep8 package. 

The Build-Depends for this package need to be updated.

Here is the failing part of the build:

debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
set -e ; \
python2.7 build2.7/lib.*-2.7/shortuuid/tests.py
Traceback (most recent call last):
  File "build2.7/lib.linux-x86_64-2.7/shortuuid/tests.py", line 5, in 
import pep8
ImportError: No module named pep8
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
Edward.
--- End Message ---
--- Begin Message ---
Source: shortuuid
Source-Version: 0.4.3-1.1

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

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

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

Debian distribution maintenance software
pp.
Brian May  (supplier of updated shortuuid 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: Mon, 02 May 2016 11:12:25 +1000
Source: shortuuid
Binary: python-shortuuid python3-shortuuid
Architecture: source all
Version: 0.4.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda 
Changed-By: Brian May 
Description:
 python-shortuuid - generates concise, unambiguous, URL-safe UUIDs
 python3-shortuuid - generates concise, unambiguous, URL-safe UUIDs for Python3
Closes: 818060
Changes:
 shortuuid (0.4.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS. Add python-pep8 to build-depends. Closes: #818060.
Checksums-Sha1:
 63b53849d858e7a1391b399c825bcc69083d50ac 1936 shortuuid_0.4.3-1.1.dsc
 cd02ec7e61ae72d6898ff5e481531fcd5617572f 6096 shortuuid_0.4.3.orig.tar.gz
 297dbf833316f4146afb27ce471e51532e67c28a 3756 shortuuid_0.4.3-1.1.debian.tar.xz
 a1d2d90f6fa31a8c83b4d99d9e17061c1f40f4f3 8068 
python-shortuuid_0.4.3-1.1_all.deb
 a9e731c687afea59e526dba06d986a49de6ad912 6804 
python3-shortuuid_0.4.3-1.1_all.deb
Checksums-Sha256:
 3317a3447043e53d4c48910e5a6464f8d2063026a42dc00dd123ea380bef3598 1936 
shortuuid_0.4.3-1.1.dsc
 4606dbb19124d98109c00e2cafae2df8117aec02115623e18fb2abe3f766d293 6096 
shortuuid_0.4.3.orig.tar.gz
 a177d1861a038ef1138dd34e8ce1aadb1b74d146ad4f59e85455b6866a00ce7b 3756 
shortuuid_0.4.3-1.1.debian.tar.xz
 7ace35eafad2fc861132d74e2081891249f4464503a73faa43e6bc29de12f90e 8068 
python-shortuuid_0.4.3-1.1_all.deb
 28dd342c0147490e710a492847dd3df2bc0a34a1d4574d1f108605a77f9b2026 6804 
python3-shortuuid_0.4.3-1.1_all.deb
Files:
 1de03cd378e5fcd4311cb55545d7716c 1936 python optional shortuuid_0.4.3-1.1.dsc
 4f70db8174c0b7b8cad36de48b529947 6096 python optional 
shortuuid_0.4.3.orig.tar.gz
 c0a709b8bbc6c1f3184cdf2f35d3d55e 3756 python optional 
shortuuid_0.4.3-1.1.debian.tar.xz
 9cb6f39c7280e96807966479bdd36b67 8068 python optional 
python-shortuuid_0.4.3-1.1_all.deb
 6ed392a3b278ac1a58c2af821988dad9 6804 python optional 
python3-shortuuid_0.4.3-1.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXJqu3AAoJEBeEV3+BH26s8xIQAMnN8KLijo8oVgkh4YPyJVe1
f+eYTseiyOxTM2l4yVbOpXJPb8+GJie0A8wDNaoSiBiYu8P6W8Ck7NV1mYuCgbqH
vkQEEyzZK9zgTkT4I0LnAsGkd0bAsx2MxavwRbWaIzVi3/u8zFjY22rax9PJA6PP
JxaYKavMxhX2l3UcuyX48RHkSiGI1pVZ89nKH6oo0b2dadWnHZOfukhEcUeJSPGW
CDFLCuKtJfU1penbSO0crhxT71YuygJJe4Fn5JMx30F2noGBxr/e0B8wpXGEBaeV

Processed: Bug#820693: gdebi: Add flakes8 Build-Depends to fix FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #820693 [gdebi] gdebi: Add flakes8 Build-Depends to fix FTBFS
Severity set to 'serious' from 'normal'
> tags -1 sid stretch
Bug #820693 [gdebi] gdebi: Add flakes8 Build-Depends to fix FTBFS
Added tag(s) sid and stretch.

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

Bug#823369: adacontrol: FTBFS: t_representation_clauses vs. big-endian systems

[Aaron M. Ucko]

Source: adacontrol
Version: 1.17r3.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of adacontrol for big-endian architectures such as mips or
powerpc are now failing:

  t_representation_clauses.adb:89:12: attempt to specify non-contiguous field 
not permitted
  t_representation_clauses.adb:89:12: caused by non-standard Bit_Order specified
  t_representation_clauses.adb:89:12: consider possibility of using Ada 2005 
mode here
  Controlling T_REPRESENTATION_CLAUSES specification ... not found!
  Controlling T_REPRESENTATION_CLAUSES body ... not found!
  [...]
  => t_representation_clauses.txtFAILED
<=
  [...]
  --   Passed= 78, Failed= 1   
--

Could you please take a look?

Thanks!

Processed: Re: [Debichem-devel] Bug#822501: bagel: FTBFS: error: 'inner_product' is not a member of 'std'

[Debian Bug Tracking System]

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

> tags 822501 +pending
Bug #822501 [bagel] bagel: FTBFS: error: 'inner_product' is not a member of 
'std'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822501: [Debichem-devel] Bug#822501: bagel: FTBFS: error: 'inner_product' is not a member of 'std'

[Michael Banck]

tags 822501 +pending
thanks

On Sun, Apr 24, 2016 at 06:16:10PM -0700, Martin Michlmayr wrote:
> This package fails to build in unstable:
> 
> > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
> > libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -g -O2 
> > -DNDEBUG -std=c++11 -c distzmatrix.cc -o distzmatrix.o
> > In file included from algo.cc:27:0:
> > ../../../src/util/math/algo.h: In function 'decltype (((* p) * (* q))) 
> > bagel::blas::{anonymous}::dot_product(T, size_t, U)':
> > ../../../src/util/math/algo.h:151:12: error: 'inner_product' is not a 
> > member of 'std'
> >  return std::inner_product(p, p+n, q, static_cast(0.0), 
> > std::plus(), [](decltype(*p) i, decltype(*q) j) { return 
> > detail::conj(i)*j; });
> > ^

Thanks, I've cherry-picked a fix from upstream to subversion which fixes
this.  Will upload when I've verified the rest of the package still
builds as well.


Michael

Bug#822435: marked as done (python-extractor,python-sfepy: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 22:29:27 +
with message-id 
and subject line Bug#822435: fixed in sfepy 2016.1-2
has caused the Debian Bug report #822435,
regarding python-extractor,python-sfepy: error when trying to install together
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.)


-- 
822435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-extractor,python-sfepy
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1:0.6-4
Control: found -1 2016.1-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python-sfepy.
  Preparing to unpack .../python-sfepy_2016.1-1_amd64.deb ...
  Unpacking python-sfepy (2016.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-sfepy_2016.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/extractor.py', which 
is also in package python-extractor 1:0.6-4

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

   usr/lib/python2.7/dist-packages/extractor.py

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python-extractor=1%0.6-4_python-sfepy=2016.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sfepy
Source-Version: 2016.1-2

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated sfepy 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: SHA1

Format: 1.8
Date: Tue, 03 May 2016 21:59:05 +0200
Source: sfepy
Binary: python-sfepy python-sfepy-doc
Architecture: source
Version: 2016.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 python-sfepy - Simple Finite Elements in Python
 python-sfepy-doc - Simple Finite Elements in Python. Docs
Closes: 822435
Changes:
 sfepy (2016.1-2) unstable; urgency=medium
 .
   * [2649ad0] Rename extractor to extractor_sfepy. (Closes: #822435)
   * [3667f7f] Add autopkgtest.
   * [96d5449] Ignore quilt dir
Checksums-Sha1:
 62c4f59844689085b8b6d655ea79a857316ec644 2364 sfepy_2016.1-2.dsc
 5630a17c753bbc895b238dc571812bb5117856c0 14112 sfepy_2016.1-2.debian.tar.xz
Checksums-Sha256:
 a71957b2675d48505f6823b09f7d30b072f56680112ea13d727a9696a7582ca2 2364 
sfepy_2016.1-2.dsc
 1f7f4e45740da1eeba830d4dda47dfec94f60de634c61e87dbf6dbf7475d04e0 14112 
sfepy_2016.1-2.debian.tar.xz
Files:
 1f0d4122c8598a5a2b80427131700806 2364 python optional sfepy_2016.1-2.dsc
 8f338cd93d77d0741261eb9021a5c50d 14112 python optional 
sfepy_2016.1-2.debian.tar.xz

-BEGIN PGP 

Bug#822408: marked as done (yosys: FTBFS: error: expected unqualified-id before '(' token)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 22:31:38 +
with message-id 
and subject line Bug#822408: fixed in yosys 0.6-5
has caused the Debian Bug report #822408,
regarding yosys: FTBFS: error: expected unqualified-id before '(' token
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.)


-- 
822408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yosys
Version: 0.6-4
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> [ 23%] Building passes/tests/test_abcloop.o
> [ 23%] Building passes/sat/sat.o
> [ 24%] Building passes/sat/freduce.o
> In file included from frontends/ast/ast.cc:39:0:
> frontends/ast/ast.cc: In member function 'Yosys::RTLIL::Const 
> Yosys::AST::AstNode::realAsConst(int)':
> frontends/ast/ast.cc:863:12: error: expected unqualified-id before '(' token
>   if (!std::isfinite(v)) {
> ^
> [ 24%] Building passes/sat/eval.o

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: yosys
Source-Version: 0.6-5

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

Debian distribution maintenance software
pp.
Ruben Undheim  (supplier of updated yosys 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: Tue, 03 May 2016 21:56:53 +0200
Source: yosys
Binary: yosys yosys-dev yosys-doc
Architecture: source
Version: 0.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ruben Undheim 
Description:
 yosys  - Framework for Verilog RTL synthesis
 yosys-dev  - Framework for Verilog RTL synthesis (development files)
 yosys-doc  - Documentation for Yosys
Closes: 822408
Changes:
 yosys (0.6-5) unstable; urgency=medium
 .
   [ Sebastian Kuzminsky ]
   * debian/patches/fixup-initalization.patch:
 - Add a bugfix patch from upstream's development branch.
 .
   [ Ruben Undheim ]
   * debian/patches/fix_ftbfs_cannot_find_infinite.patch:
 - Fixes FTBFS due to std::isfinite not found. (Closes: #822408)
   * Move PDFs in yosys-doc to /usr/share/doc/yosys in order to adhere to
 Debian Policy 12.3.
   * Refreshed patches
Checksums-Sha1:
 229a8702775a5af5919f493888fddc4bc1e1f378 2436 yosys_0.6-5.dsc
 f27363f01c84bc0c2b4de9081301f1dcc048a006 12984 yosys_0.6-5.debian.tar.xz
Checksums-Sha256:
 37aef38ba341a852eba84906ce940a27c560a2ce1e53db3b2423f3e5120721b1 2436 
yosys_0.6-5.dsc
 fcfecd4a42e054c51d816edd214e7b4cc757c9485da9470213190e7fdf6755e5 12984 
yosys_0.6-5.debian.tar.xz
Files:
 2804290d329fb40fc5f13d772f3a0bdd 2436 electronics optional yosys_0.6-5.dsc
 c40cfc6dc1e90d48bd649d52bc3dac71 12984 electronics optional 
yosys_0.6-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXKQKjAAoJEPxqH2TRCNERqgMP+waIl0cNnOPRTo6BP1mylUbO
kd/ORUuxt72mdSHxBdynIkRZzpwQJ5fIu0+IQ9//8mokaAZeaoB5fjgZi1rPTPD8
2Z8/fzgYOQyzIco9D6tAwWGhduextXUoSqjkx0363GQ0BLOBVx7gILt0Xe8AO3mP
DE/9Y3gcNfifrC/bkgzUsFhNZGc/jlPcxgYc2pWMCJhq3ZEoMQq4ohuwZSPEpWtc
+7SsPK+tLhRmitEHY9vpbLN37vzbb94PUxhlinXAUkURq5gFY7aIDAX+9ishJ0Nt
ikeSqFlVrcTk4rV6xMffOVNf+KCkzG3L8+1wwmL6uF69xfOyddyBUyuNBV2kSZvd
Zi4KUA34r1bYrxvunyrFkz5rGy/eIV9TmwYp+0sXi8eIQ6LZQOTVa5sKsYPMXMqZ
uapJt5pIpRi3PO0OSw3MQlzmvkkPxsZG6qDp5M/4ors7qgIl43hRypzLTBbKOaOl
1/WI0NNNJEZQ/InoZARrygt6pABh4ix7Vs+sGdAAfrPMuOu+C2XUWTsFVxyt3Jdu
Dqb+usfQDG272/00Br2N203joksiUha6aIAJ18R1sbz1TodObG1N0mWzJdLFrstf
zRVqCOJghYZXsvSML8rX0fdeiNutK72UWjOgshCw2ByucBB3ozwdiJqyjCn8XbQF
wHQjfpcFc8NfCzlQC7GQ
=7Orc
-END PGP SIGNATURE End Message ---

Bug#823310: marked as done (libnanomsg-raw-perl: FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 22:23:44 +
with message-id 
and subject line Bug#823310: fixed in libnanomsg-raw-perl 0.06-2
has caused the Debian Bug report #823310,
regarding libnanomsg-raw-perl: FTBFS: test failures
to be marked as done.

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

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


-- 
823310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnanomsg-raw-perl
Version: 0.06-1
Severity: serious

On a rebuild against libnanomsg4, your package failed to build
everywhere:

https://buildd.debian.org/status/package.php?p=libnanomsg-raw-perl

Emilio
--- End Message ---
--- Begin Message ---
Source: libnanomsg-raw-perl
Source-Version: 0.06-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libnanomsg-raw-perl 
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: Tue, 03 May 2016 22:23:53 +0200
Source: libnanomsg-raw-perl
Binary: libnanomsg-raw-perl
Architecture: source
Version: 0.06-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 823310
Description: 
 libnanomsg-raw-perl - low-level interface to nanomsg for Perl
Changes:
 libnanomsg-raw-perl (0.06-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Add patch from upstream Git repo to fix tests with newer libnanomsg.
 (Closes: #823310)
   * Set bindnow linker flag in debian/rules.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1: 
 e641fca18712e38aa6dcedc3a144b57c11f5d87b 2294 libnanomsg-raw-perl_0.06-2.dsc
 3592e866a71f8388caf71183194adc3cd7f6b6b8 3620 
libnanomsg-raw-perl_0.06-2.debian.tar.xz
Checksums-Sha256: 
 36bf6fb906b06eb76ca52deefdb0bf4c48454fb6c0e6d5f8c9f4c3cd3833039b 2294 
libnanomsg-raw-perl_0.06-2.dsc
 697cc783200ea13b6f23ef7e782928d2ba4699764fc20d18f95c92592173b3d7 3620 
libnanomsg-raw-perl_0.06-2.debian.tar.xz
Files: 
 f4659ea9544ad2ada503e4dfea174018 2294 perl optional 
libnanomsg-raw-perl_0.06-2.dsc
 0e840295d3da011ddf0b62a3ee7aac9a 3620 perl optional 
libnanomsg-raw-perl_0.06-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXKQnCXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGb4UQALDMJoAY6aQY53KKwSIKG4db
ZF+HeQm3FhkD5AYoqjtZQBv/RnBk+2eow7sTOAq5I0MMRBNvwUJAUwIBzzfma/X1
AljAfAaKmAHx+MTortCrRE0hLmOkMzPUTBB+UFAjuzYytTeqFCO7/Ofym4di6mnD
XFQCeR1YV8sIy8K1CGhaLKQ1We8bUO5Zs72p9kQABqPctfbbT10cMtmKuB/uWjp7
20SkHgxcyGKSg9+yM4flrffni2mvVdp4/jpFCQRBP425WFFPCG5SGN6hS31lSyuK
6R7Zg2hOq1p77Yujs/Mk2KbNyCErHmu9qb3HvZaEOo3dBxeqgR3VKQDgiSpWnc86
JP4yxB0wPp6N8XLUuQUQzm6T9Wj/tX49i14B9uLxk9mt+jfsnaPZzeOF7mTFsSQR
xFRZu5r4PEmy3csy/X6uV+SrGr+SulIzcoqiAaY1shT65kbMnXKOtlHmcWK+nC8r
qY2g9Go1gBzpJOugpSWnIFS+pLhRZ30sBf1Gmj25iFAS5zyYhZa1W2As5kBzcGgc
adv4ja8mnyeyOlrhCLKUsdirg9D2Kk8UlDfRn2z9YV1MyTfRxjRHgDR/gd1aS/Xs
oMflznMU0JhYUbLH4XOuhE5ed3hAWGvc8jG+5IpAPyF1F+63paAMW7ax9jzlnzPN
8dT/Do1RdOT7ScGfjEKN
=ypRO
-END PGP SIGNATURE End Message ---

Bug#823345: marked as done (golang-logrus: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 22:22:03 +
with message-id 
and subject line Bug#823345: fixed in golang-logrus 0.10.0-2
has caused the Debian Bug report #823345,
regarding golang-logrus: maintainer address bounces
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.)


-- 
823345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-logrus
Version: 0.10.0-1
Severity: serious

The maintainer address for golang-logrus bounces, see below.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   j...@docker.com
> SMTP error from remote mail server after RCPT TO::
> host aspmx.l.google.com [2a00:1450:400c:c09::1a]:
> 550-5.1.1 The email account that you tried to reach does not exist. 
> Please try
> 550-5.1.1 double-checking the recipient's email address for typos or
> 550-5.1.1 unnecessary spaces. Learn more at
> 550 5.1.1  https://support.google.com/mail/answer/6596 gg1si106659wjd.214 
> - gsmtp
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Jessie Frazelle , =?utf-8?q?Mart=C3=ADn_Ferrari?= 
> 
[...]
> Subject: golang-logrus_0.10.0-1_amd64.changes ACCEPTED into unstable
[...]
> Date: Tue, 03 May 2016 18:22:07 +
--- End Message ---
--- Begin Message ---
Source: golang-logrus
Source-Version: 0.10.0-2

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-logrus 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: Tue, 03 May 2016 21:30:40 +
Source: golang-logrus
Binary: golang-github-sirupsen-logrus-dev golang-logrus-dev
Architecture: source all
Version: 0.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 golang-github-sirupsen-logrus-dev - Logrus: a logging library for Go
 golang-logrus-dev - Transitional package for golang-github-sirupsen-logrus-dev
Closes: 823345
Changes:
 golang-logrus (0.10.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Make pkg-go the maintainer. Closes: #823345.
Checksums-Sha1:
 9401a61f560bd8fcd0dbec3e18d3ae6c90db3ac0 2172 golang-logrus_0.10.0-2.dsc
 d3c695db10cea4d7b0b40b0431d041f280933878 3752 
golang-logrus_0.10.0-2.debian.tar.xz
 c1ea8694a7b5f7269e87a2724f0909926c1ee961 24550 
golang-github-sirupsen-logrus-dev_0.10.0-2_all.deb
 f14b9897772284879823ff085749f28c714deea7 3522 
golang-logrus-dev_0.10.0-2_all.deb
Checksums-Sha256:
 fc305f7398813a063aa7a944062a70532ea7cf91380413b1444f343a00e24850 2172 
golang-logrus_0.10.0-2.dsc
 0b34004504162dbe0e4eff5fc7675ac0c386434703b35369f7992b3318a4f023 3752 
golang-logrus_0.10.0-2.debian.tar.xz
 b99561d419d45548d35dae7e65cc9be32763496391d1c9ba8c4b295e9b54857f 24550 
golang-github-sirupsen-logrus-dev_0.10.0-2_all.deb
 0bffbc54915d2db3696deb5380bee5fd2368fd36b36c5a8b4b60aa58b79de4ae 3522 
golang-logrus-dev_0.10.0-2_all.deb
Files:
 ff32028553738d9c99760a37b71e0897 2172 devel extra golang-logrus_0.10.0-2.dsc
 ae3c5401c2f3c41e136cc877fe23d161 3752 devel extra 
golang-logrus_0.10.0-2.debian.tar.xz
 d8f90f9dfe369b0ecb2d883238e9fc8c 24550 devel extra 
golang-github-sirupsen-logrus-dev_0.10.0-2_all.deb
 ea4277abc11145d67d5e034f383f 3522 oldlibs extra 
golang-logrus-dev_0.10.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXKRisAAoJEF3Y4L+Ro9PalA4QAMS6cQMBwr7/y4sfkQbjd+vP
0vBy+UAfcln5UEc6of2ZYLlbcanvXno1JXqAmRS8SSnVeIM6wh3JZ/M7Ee0amNKr
OQLSs7oEs+2zpZF80zZRy+kExS5bp7FVaJzutLMq43LppSEtUbN0416scy+O/uZL

Bug#823166:

[Ondrej Novy]

I can't reproduce it locally.

Can you attach output of this script from your env please?

#!/usr/bin/python

import getpass
import pwd
import os
import grp

user = getpass.getuser()
ugroup = pwd.getpwnam(user).pw_gid
os_groups = os.getgroups()
groups = [g.gr_gid for g in grp.getgrall() if user in g.gr_mem]

print "getpass.getuser: %s" % user
print "pwd.getpwname(user).pw_gid: %d" % ugroup
print "os.getgroups(): %s" % os_groups
print "grp.getgrall() filtered: %s" % groups

##

My result:
onovy@sid:~$ ./test.py
getpass.getuser: onovy
pwd.getpwname(user).pw_gid: 1000
os.getgroups(): [27, 117, 1000]
grp.getgrall() filtered: [27, 117]

Which passes tests.

Thanks.

-- 
Best regards
 Bc. Ondrej Novy

Email: n...@ondrej.org
GPG: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Processed: Pending fixes for bugs in the golang-logrus package

[Debian Bug Tracking System]

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

> tag 823345 + pending
Bug #823345 [src:golang-logrus] golang-logrus: maintainer address bounces
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823345: Pending fixes for bugs in the golang-logrus package

[pkg-go-maintainers]

tag 823345 + pending
thanks

Some bugs in the golang-logrus package are closed in revision
db6b4102842840cea96a453a9c68085744d7d63f in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-logrus.git/commit/?id=db6b410

Commit message:

Make pkg-go the maintainer. Closes: #823345.

Processed: Pending fixes for bugs in the libnanomsg-raw-perl package

[Debian Bug Tracking System]

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

> tag 823310 + pending
Bug #823310 [libnanomsg-raw-perl] libnanomsg-raw-perl: FTBFS: test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823310: Pending fixes for bugs in the libnanomsg-raw-perl package

[pkg-perl-maintainers]

tag 823310 + pending
thanks

Some bugs in the libnanomsg-raw-perl package are closed in revision
953c2163bfaefed07c71e1308d9319848cd6780f in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnanomsg-raw-perl.git/commit/?id=953c216

Commit message:

Add patch from upstream Git repo to fix tests

with newer libnanomsg.

Closes: #823310

Bug#823345: golang-logrus: maintainer address bounces

[Ansgar Burchardt]

Source: golang-logrus
Version: 0.10.0-1
Severity: serious

The maintainer address for golang-logrus bounces, see below.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   j...@docker.com
> SMTP error from remote mail server after RCPT TO::
> host aspmx.l.google.com [2a00:1450:400c:c09::1a]:
> 550-5.1.1 The email account that you tried to reach does not exist. 
> Please try
> 550-5.1.1 double-checking the recipient's email address for typos or
> 550-5.1.1 unnecessary spaces. Learn more at
> 550 5.1.1  https://support.google.com/mail/answer/6596 gg1si106659wjd.214 
> - gsmtp
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Jessie Frazelle , =?utf-8?q?Mart=C3=ADn_Ferrari?= 
> 
[...]
> Subject: golang-logrus_0.10.0-1_amd64.changes ACCEPTED into unstable
[...]
> Date: Tue, 03 May 2016 18:22:07 +

Bug#766397: emacs/gnus: Uses s_client to for SSL.

[Deago Thouxan]

Date: Sun, 21 Feb 2016 13:47:45  1100
>From: Lars Ingebrigtsen 
>-
>Body:

Bug#822157: marked as pending

[Vincent Bernat]

tag 822157 pending
thanks

Hello,

Bug #822157 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/python-future.git;a=commitdiff;h=b984583

---
commit b9845834eb3980dedeaf00ff71d9362b74a3074a
Author: Vincent Bernat 
Date:   Tue May 3 21:28:02 2016 +0200

Remove configparser module and depends on python-configparser

diff --git a/debian/changelog b/debian/changelog
index 0f121f8..002fbff 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,6 +6,8 @@ python-future (0.15.2-2) UNRELEASED; urgency=medium
   [ Vincent Bernat ]
   * d/control: Bump Standards-Version.
   * d/rules: Switch to pybuild.
+  * Remove configparser module and depends on python-configparser
+instead. Closes: #822157.
 
  -- Vincent Bernat   Tue, 03 May 2016 21:06:42 +0200
 

Bug#823313: marked as done (r-base-dev: causes r-cran-tgp to FTBFS: error: template with C linkage)

[Debian Bug Tracking System]

Your message dated Tue, 3 May 2016 21:42:47 +0200
with message-id <5728ff37.2010...@debian.org>
and subject line Re: r-cran-tgp: FTBFS: cmath:171:3: error: template with C 
linkage
has caused the Debian Bug report #823313,
regarding r-base-dev: causes r-cran-tgp to FTBFS: error: template with C linkage
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.)


-- 
823313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-base-dev
Version: 3.2.5.20160429-1
Severity: serious
Control: block 820866 with -1

Hi,

current r-base-dev in sid causes r-cran-tgp to FTBFS (#820866),
downgrading to 3.2.5-1 makes it build again.

from the log of an amd64 build:

g++ -I/usr/share/R/include -DNDEBUG -DRPRINT -DNDEBUG  -fpic  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -g  -c base.cc -o base.o
In file included from /usr/share/R/include/R.h:40:0,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/cstdlib: In function 'long long int std::abs(long long int)':
/usr/include/c++/5/cstdlib:174:20: error: conflicting declaration of C function 
'long long int std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
/usr/include/c++/5/cstdlib: In function '__int128 std::abs(__int128)':
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function 
'__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:174:3: note: previous declaration 'long long int 
std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
   ^
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function 
'__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
In file included from /usr/include/c++/5/cmath:42:0,
 from /usr/share/R/include/R.h:43,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/bits/cpp_type_traits.h: At global scope:
/usr/include/c++/5/bits/cpp_type_traits.h:72:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:85:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:89:3: error: template specialization 
with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:95:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:103:3: error: template with C linkage
   template
   ^


Andreas
--- End Message ---
--- Begin Message ---
> On 3 May 2016 at 15:29, Pablo Oliveira wrote:
> | The new upstream version of tgp (2.4-14) fixes the issue on unstable.

Thanks for checking this.

As expected, 2.4-9-1 also fails with 3.3.0-1 (which just arrived on my
mirror).

Since that has been identified as a bug in tgp that got exposed by the
new r-base, I'm closing the r-base bug.


Andreas--- End Message ---

Processed: Bug#822157 marked as pending

[Debian Bug Tracking System]

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

> tag 822157 pending
Bug #822157 [src:python-future] python-future hides and breaks 
python-configparser
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823287: selinux-basics: System cannot boot with SELinux enabled after upgrade

[Jonathan Yu]

On Tue, May 3, 2016 at 10:10 AM, Laurent Bigonville 
wrote:
>
>
> Do you have a policy installed on your machine?
>

I do not - I was unable to install the latest selinux-policy-default
package from unstable due to dependency problems that I was unable to
resolve.

The following packages have unmet dependencies:
 selinux-policy-default : Depends: policycoreutils (>= 2.2.1) but it is not
going to be installed
 udev : Depends: libblkid1 (>= 2.19.1) but it is not going to be installed
Depends: adduser but it is not going to be installed
Depends: util-linux (>= 2.27.1)
Depends: procps


> The policy package currently in unstable is not compatible with the new
> userspace and needs to be adjusted, see bug #805492.
>

Ah, it does look like the same problem. However, I expected some sort of
safeguard that would prevent me from breaking my system -- i.e. a check in
selinux-activate that ensured that a policy was available, if that is
required to boot. Making my system unbootable is not desired behaviour.


> I've unfortunately not a lot of time for this. That means that if you want
> to use SELinux in debian, you'll have to compile/build your own policy.
>

I can understand that. I have some experience with Debian packaging, but
little with SELinux or advanced things like maintainer scripts, however I'd
be happy to spend a few weekends hacking on this if you can give me some
direction. I'll read through #805492 this weekend and come back to you with
questions.

Thanks again for all your contributions to Debian :)

Processed: Re: Bug#817094: mercurial-keyring: fails to import Gnome module

[Debian Bug Tracking System]

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

> reassign 817094 python-keyring
Bug #817094 [mercurial-keyring] mercurial-keyring: fails to import Gnome module
Bug reassigned from package 'mercurial-keyring' to 'python-keyring'.
No longer marked as found in versions mercurial-keyring/0.6.7-1.
Ignoring request to alter fixed versions of bug #817094 to the same values 
previously set
> forcemerge 820905 817094
Bug #820905 {Done: Dmitry Shachnev } [python-keyring] 
python-keyring: ImportError: No module named Gnome
Bug #817094 [python-keyring] mercurial-keyring: fails to import Gnome module
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as found in versions python-keyring/8.5.1-1.
Added tag(s) moreinfo.
Merged 817094 820905
>
End of message, stopping processing here.

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

Processed: block 819259 with 759645

[Debian Bug Tracking System]

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

> block 819259 with 759645
Bug #819259 [src:tomcat7] Don't include in stretch
819259 was blocked by: 823332
819259 was not blocking any bugs.
Added blocking bug(s) of 819259: 759645
> thanks
Stopping processing here.

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

Processed: forcibly merging 819146 821702, severity of 819146 is serious

[Debian Bug Tracking System]

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

> forcemerge 819146 821702
Bug #819146 [src:php-mongo] PHP 7 transition and moving to pkg-php-pecl team
Bug #821550 [src:php-mongo] php5-mongo: PHP 7.0 Transition
Bug #821702 [src:php-mongo] src:php-mongo: PHP 7.0 Transition
Marked as found in versions php-mongo/1.6.10-1.
Bug #821550 [src:php-mongo] php5-mongo: PHP 7.0 Transition
Merged 819146 821550 821702
> severity 819146 serious
Bug #819146 [src:php-mongo] PHP 7 transition and moving to pkg-php-pecl team
Bug #821550 [src:php-mongo] php5-mongo: PHP 7.0 Transition
Bug #821702 [src:php-mongo] src:php-mongo: PHP 7.0 Transition
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#823288 in package dpkg marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 823288 pending
Bug #823288 [dpkg] dpkg misplaces tpl-config.tlib during unpack
Added tag(s) pending.

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

Bug#823288: in package dpkg marked as pending

[Guillem Jover]

Control: tag 823288 pending

Hi!

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

https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=c931762

---
commit c931762286a22626b4f9958d457248a027bfc0f7
Author: Guillem Jover 
Date:   Tue May 3 18:11:06 2016 +0200

dpkg: Fix file queue tail assignment in file queue pop

When we are popping a file from the files queue, we might end up messing
it up. To check for the side-effects on the file-system one should look
for files with .dpkg-new extension for packages that have been fully
configured and where those files are not listed as owned by them. These
packages will need to be reinstalled.

Closes: #823288

diff --git a/debian/changelog b/debian/changelog
index b8acd2b..e070e58 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,9 @@
 dpkg (1.18.6) UNRELEASED; urgency=medium
 
+  * Fix file queue tail assignment on file queue pop during unpack. This
+could mess up the file queue in some circumstances and leave behind
+files in the filesystem as «pathname».dpkg-new after configuration
+and without traces of the files in the dpkg database. Closes: #823288
   * Packaging:
 - Bump Standards-Version to 3.9.8 (no changes needed).
 

Bug#823287: selinux-basics: System cannot boot with SELinux enabled after upgrade

[Laurent Bigonville]

On Mon, 02 May 2016 20:51:55 -0700 Jonathan Yu  wrote:
>
> Dear Maintainer,

Hello,

>
> Thank you for your work bringing SELinux to Debian!
>
> I regret that my knowledge of both SELinux and systemd is limited, so 
I do not

> know what diagnostics to collect or how to collect it. That said, I can
> reproduce this problem at will, and I'm happy to collect whatever 
diagnostics

> you need.
>
> * What led up to the situation?
>
> I upgraded my system doing full-upgrade. My system is mainly 
'testing' with

> some packages coming from 'unstable' (I tried updating to the newer
> selinux-utils in unstable, but to no avail).
>
> Unfortunately there are not much diagnostics provided during boot, and I
> could not find any trace of the failed boots in journalctl or in files
> in /var/log, presumably because the problems occurred at such an early
> stage of boot. I checked /var/log/syslog, but did not find much 
informative.

>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> * What was the outcome of this action?
>
> Removing the "selinux=1 security=selinux" flags from grub allowed me 
to boot.

> I then used "selinux-activate disabled" to disable SELinux while we sort
> these issues out.
>
> I also tried running "selinux-activate disabled" and re-activating it 
again,
> as it seems to do something with restorecond on first boot after 
activation.

> Unfortunately this did not change anything :(
>
> * What outcome did you expect instead?
>
> I expected that my system could continue booting. I've never had 
significant
> issues with Debian upgrades (thanks to careful maintainers like you 
:) and

> guess that there must be something strange about the way my system is
> configured.
>
> [...]
> May  2 20:31:38 theory dbus-daemon[1183]: Failed to start message 
bus: Failed to open "/etc/selinux/default/contexts/dbus_contexts": No 
such file or directory

> [...]
> pn  selinux-policy-default

Do you have a policy installed on your machine?

The policy package currently in unstable is not compatible with the new 
userspace and needs to be adjusted, see bug #805492.


I've unfortunately not a lot of time for this. That means that if you 
want to use SELinux in debian, you'll have to compile/build your own policy.

Processed: block 819259 with 823332

[Debian Bug Tracking System]

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

> block 819259 with 823332
Bug #819259 [src:tomcat7] Don't include in stretch
819259 was not blocked by any bugs.
819259 was not blocking any bugs.
Added blocking bug(s) of 819259: 823332
> thanks
Stopping processing here.

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

Bug#823330: Upstream known bug with a fix

[Eric Valette]

see 

Bug#822976: gtk3-engines-unico: Package broken by GTK 3.16

[George B.]

Hi James,

On 30/04/16 06:13, James Lu wrote:

Since newer GTK versions have already made it into the archive, does
that mean that this package no longer serves any purpose?


It would appear so - oxygen-gtk3 package was removed for the same reason.[1]


From what I
can tell, GTK3 engines for Breeze and Xfce still exist elsewhere in the
archive: https://packages.debian.org/search?keywords=gtk3-engines-


Breeze was actually ported to CSS - I have already filed a bug with a request 
to rename the package to avoid confusion.[2]

The Xfce package contains a mix of partially converted and broken themes. [3]


If this inevitably ends with Unico being removed, I guess I'm okay with
that too. What might be the best course of action here?


I guess the best solution would be to port the theme to CSS, but it is not the 
easiest. ;)


Best regards,

George


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797796
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822975
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762936

Bug#787500: libcoro-perl: FTBFS with perl 5.22

[gregor herrmann]

On Mon, 21 Sep 2015 19:44:46 +0100, Dominic Hargreaves wrote:

> In due time, if it's clear that it's not going to change, the package
> can be removed from unstable.

Interesting summary about the Coro situation as of May 2016 / Perl
5.21.7 - 5.24.0-RC3:
http://blogs.perl.org/users/aristotle/2016/05/coro-vs-5022.html


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Letitbleed


signature.asc
Description: Digital Signature

Bug#823288: gnutls28: FTBFS: gcc: error: srptool-args.c: No such file or director

[Helmut Grohne]

Control: retitle -1 dpkg misplaces tpl-config.tlib during unpack
Control: reassign -1 dpkg
Control: found -1 1.18.5
Control: affects -1 + autogen src:gnutls28
Control: severity -1 grave

On Tue, May 03, 2016 at 06:17:38AM +0200, Helmut Grohne wrote:
> I have little clue what is going on here, but what I can tell already is
> that this issue is not caused by the 3.4.11-4 upload. My first
> failing[1] build was on 2nd of May at 21:00 UTC. My last successful[2]
> build was on the same day at 16:00 UTC (both using the ftp.de.debian.org
> mirror). Now all of my gnutls28 builds fail with that error. They differ
> by one or two mirror pushes, so not many things can have caused that
> regression.  The only potentially relevant piece I could find thus far
> is the tar NMU.

Simple. /usr/lib/x86_64-linux-gnu/autogen/tpl-config.tlib isn't there.
It's part of autogen, but dpkg 1.18.5 fails place it correctly.

Unpacking autogen with dpkg 1.18.4 places it at the correct location.
Unpacking autogen with dpkg 1.18.5 places it at
/usr/lib/x86_64-linux-gnu/autogen/tpl-config.tlib.dpkg-new.

It is yet unclear under what conditions this happens. Still we can
conclude that dpkg 1.18.5 can result in broken installations, thus
marking grave.

Helmut

Processed: Re: gnutls28: FTBFS: gcc: error: srptool-args.c: No such file or director

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 dpkg misplaces tpl-config.tlib during unpack
Bug #823288 [src:gnutls28] gnutls28: FTBFS: gcc: error: srptool-args.c: No such 
file or director
Changed Bug title to 'dpkg misplaces tpl-config.tlib during unpack' from 
'gnutls28: FTBFS: gcc: error: srptool-args.c: No such file or director'.
> reassign -1 dpkg
Bug #823288 [src:gnutls28] dpkg misplaces tpl-config.tlib during unpack
Bug reassigned from package 'src:gnutls28' to 'dpkg'.
No longer marked as found in versions gnutls28/3.4.11-4.
Ignoring request to alter fixed versions of bug #823288 to the same values 
previously set
> found -1 1.18.5
Bug #823288 [dpkg] dpkg misplaces tpl-config.tlib during unpack
Marked as found in versions dpkg/1.18.5.
> affects -1 + autogen src:gnutls28
Bug #823288 [dpkg] dpkg misplaces tpl-config.tlib during unpack
Added indication that 823288 affects autogen and src:gnutls28
> severity -1 grave
Bug #823288 [dpkg] dpkg misplaces tpl-config.tlib during unpack
Severity set to 'grave' from 'serious'

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

Bug#823330: tsocks: The actual configure command disable host name resolution in tsocks.conf when it was supposed to enable it

[Eric Valette]

Package: tsocks
Version: 1.8beta5-9.4
Severity: grave
Justification: renders package unusable

The configure script is bugged and the way debian/rules triggers the bug.

make clean
rm -f *.so *.so.* *.o *~ libtsocks.so.1.8  saveme inspectsocks validateconf
./configure

grep HOSTNAME config.h  
#define HOSTNAMES 1

So by default HOSTNAME resolution is enabled as mentionned via configure *
help command:

./configure --help
...
--disable-hostnames  disable hostname lookups for socks servers

./configure --disable-hostnames
...
grep HOSTNAME config.h
#define HOSTNAMES 0

So far so good.

But when issuing

./configure --enable-hostnames
grep HOSTNAME config.h

#define HOSTNAMES 0


And debain/rules uses --enable-hostnames...




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

Kernel: Linux 4.4.8 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages tsocks depends on:
ii  libc6  2.23-0experimental2

tsocks recommends no packages.

tsocks suggests no packages.

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

-- no debconf information

Bug#819606: Doxygen help needed (Was: FTBFS: error while building documentation)

[Jakub Wilk]

* Andreas Tille , 2016-05-03, 12:54:

Runaway argument?
{\texorpdfstring {operator\%=(const t value)}{operator\begin {DoxyPar\ETC.


The generated LaTeX code looks like this:

\subsubsection[{\texorpdfstring{operator\%=(const t value)}{operator%=(const t 
value)}}]{\setlength{\rightskip}{0pt plus 5cm}{\bf C\+Img}$<$T$>$\& operator\%= 
(
\begin{DoxyParamCaption}

Note that the second "%" is not escaped. "%" is a comment character, so 
the rest of the line ignored. Ooops. This smells like a Doxygen bug!  
Googling for "doxygen unescaped percent latex" led me to these:


https://bugzilla.gnome.org/show_bug.cgi?id=762982
https://github.com/doxygen/doxygen/commit/d4ab02c2da7df472bebbf2724419ba00f2de229c

--
Jakub Wilk

Processed: Re: php-pear: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on + XML Extension not found

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822771 [php-pear] php-pear: Invalid argument supplied for foreach() in 
/usr/share/php/PEAR/Command.php on + XML Extension not found
Severity set to 'important' from 'grave'

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

Bug#822771: php-pear: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on + XML Extension not found

[Mathieu Parent]

Control: severity -1 important

Downgrading severity as I can't reproduce.

Regards

Bug#823325: mariadb-10.0: Various security fixes from 10.0.25 release

[Salvatore Bonaccorso]

Source: mariadb-10.0
Version: 10.0.10-1
Severity: grave
Tags: security upstream fixed-upstream

Hi Otto

I know you are ware, but opening a bug to keep track of it as well in
the BTS. Various CVEs are fixed with 10.0.25 release.

Could you please prepare updates for unstable and then jessie-security
as well.

More informations at
https://security-tracker.debian.org/tracker/source-package/mariadb-10.0
and
https://mariadb.com/kb/en/mariadb/mariadb-10025-release-notes/
https://mariadb.com/kb/en/mariadb/mariadb-10024-release-notes/

Regards,
Salvatore

Bug#823281: [Debian GNUstep maintainers] Bug#823281: gnustep-make: build-indep depends on binary-arch

[Santiago Vila]

On Tue, May 03, 2016 at 03:46:13PM +0200, Eric Heintzmann wrote:
> Thanks for this bug report and thanks for finding a solution.
> 
> Anyway I plan to repackage the Core GNUstep packages (including
> gnustep-make),
> and rewriting debian/rules using dh_overrides_* targets.
> (If there are no objections from other Debian GNUstep Maintainers)
> It should solve these bugs.

You are welcome.

I tried to find a solution, yes, but the current debian/rules was too
much convoluted and I never understood how it really worked.

Rewriting it in "dh" seems a very good idea. Wish you luck.

Thanks.

Bug#820866: r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage

[Dirk Eddelbuettel]

On 3 May 2016 at 15:29, Pablo Oliveira wrote:
| On Mon, 2 May 2016 16:52:31 +0200 Pablo Oliveira  wrote:
| > Dear both,
| > 
| > On Wed, 20 Apr 2016 03:44:41 +0200 Andreas Beckmann  wrote:
| > > Hi Chris,
| > > [...]
| > > 
| > > I cannot reproduce this in my sid pbuilder setup. Could you check again?
| > > (I think gcc got updated since you filed this bug.)
| > 
| > I am able to reproduce the problem using cowbuilder unstable/amd64.
| > 
| > I will try to see if the new upstream version (2.4-14) fixes the problem
| > and update the package.
| 
| The new upstream version of tgp (2.4-14) fixes the issue on unstable.

Awesome. Contacting you (and maybe Robert + Matt upstream; I happen to know
them) was next on my list.

| (I have not tested with the previous 3.2.5-1 r-base-dev, nor with 3.3.0,
| so I have no comments regarding #823313)

I am pretty sure it will pass as I did point already to the squeaky-clean
page with all the tests done at CRAN.
 
| I have updated the tgp package at
| 
|   
| 
| The new upstream version adds a new dependency (r-cran-maptree) which I
| have packaged here (ITP #823320):
| 
|  
| 
| Could somebody please upload these packages ?

I am not that involved with debian-science but I can help you if nobody on
their side steps forward.  Can you ask within debian-science.

I suggest we remove the FTBFS blocker from r-base-core too.

Dirk
 
| Thanks,
| 
| Pablo
| 

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#820866: r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage

[Pablo Oliveira]

On Mon, 2 May 2016 16:52:31 +0200 Pablo Oliveira  wrote:
> Dear both,
> 
> On Wed, 20 Apr 2016 03:44:41 +0200 Andreas Beckmann  wrote:
> > Hi Chris,
> > [...]
> > 
> > I cannot reproduce this in my sid pbuilder setup. Could you check again?
> > (I think gcc got updated since you filed this bug.)
> 
> I am able to reproduce the problem using cowbuilder unstable/amd64.
> 
> I will try to see if the new upstream version (2.4-14) fixes the problem
> and update the package.

The new upstream version of tgp (2.4-14) fixes the issue on unstable.
(I have not tested with the previous 3.2.5-1 r-base-dev, nor with 3.3.0,
so I have no comments regarding #823313)

I have updated the tgp package at

  

The new upstream version adds a new dependency (r-cran-maptree) which I
have packaged here (ITP #823320):

 

Could somebody please upload these packages ?

Thanks,

Pablo

Bug#823281: [Debian GNUstep maintainers] Bug#823281: gnustep-make: build-indep depends on binary-arch

[Eric Heintzmann]

Thanks for this bug report and thanks for finding a solution.

Anyway I plan to repackage the Core GNUstep packages (including 
gnustep-make),

and rewriting debian/rules using dh_overrides_* targets.
(If there are no objections from other Debian GNUstep Maintainers)
It should solve these bugs.

Thanks
Eric

Le 03/05/2016 02:07, Santiago Vila a écrit :

Package: src:gnustep-make
Version: 2.6.6-3
Severity: serious

Dear maintainer:

While investigating Bug #806197 I found the following policy
violations in debian/rules:


* The build target should depend on build-arch and build-indep.

Currently, it is like this:

# NOTE: The Build-Indep-Depends are only available, when building the
# build-indep packages.
build: build-arch # build-indep

Quoting policy speaking about build-arch and build-indep:

   The build target should either depend on those targets or take the
   same actions as invoking those targets would perform.

If I only install build-depends and not build-indep-depends, it follows
that I can only use the build-arch target, but that's *my* problem.

The build target should still build everything, for the case that I
install all the build-dependencies and want to build everything.


* The "build-indep" target depends indirectly on "binary-arch" (!).
This is what I see:

build-indep: debian/build-indep-stamp
clean_files += debian/build-indep-stamp
debian/build-indep-stamp: binary-arch


Well, binary-arch is where architecture-dependent .deb packages are
created (i.e. Arch: any). Quoting policy:

   The build-arch and build-indep targets must not do anything that
   might require root privilege.

Because actually creating .deb packages requires to be root (or fakeroot),
it follows that build-indep must *not* depend on any of the binary
targets.


This is probably the reason why "dpkg-buildpackage -A" fails (Bug #806197),
but I can't verify this easily because I don't have a fixed debian/rules.

Thanks.

___
Debian GNUstep maintainers mailing list
pkg-gnustep-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gnustep-maintainers

Bug#823316: stk: contains non-free Steinberg ASIO library

[Felipe Sateler]

Control: found -1 4.5.0-1

On 3 May 2016 at 09:58, James Cowgill  wrote:
> On Tue, 2016-05-03 at 09:54 -0300, Felipe Sateler wrote:
>> Control: fixed -1 4.5.0-1
>>
>> On 3 May 2016 at 08:27, James Cowgill  wrote:
>> >
>> > Source: stk
>> > Version: 4.4.3-2
>> > Severity: serious
>> >
>> > Hi,
>> >
>> > stk contains a bundled copy of the Steinberg ASIO library headers
>> > in
>> > src/include. These files are under very strict licensing terms
>> Indeed. Fortunately, the latest release has already fixed this issue.
>
> Err, no it hasn't:
> https://sources.debian.net/src/stk/4.5.0-3/src/include/asio.h/

Meh, I only looked at ./include, not ./src/include. Sorry about that.

Patches still welcome though ;)

-- 

Saludos,
Felipe Sateler

Processed: Re: Bug#823316: stk: contains non-free Steinberg ASIO library

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.5.0-1
Bug #823316 [src:stk] stk: contains non-free Steinberg ASIO library
Marked as found in versions stk/4.5.0-1; no longer marked as fixed in versions 
stk/4.5.0-1.

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

Bug#823316: stk: contains non-free Steinberg ASIO library

[James Cowgill]

On Tue, 2016-05-03 at 09:54 -0300, Felipe Sateler wrote:
> Control: fixed -1 4.5.0-1
> 
> On 3 May 2016 at 08:27, James Cowgill  wrote:
> > 
> > Source: stk
> > Version: 4.4.3-2
> > Severity: serious
> > 
> > Hi,
> > 
> > stk contains a bundled copy of the Steinberg ASIO library headers
> > in
> > src/include. These files are under very strict licensing terms
> Indeed. Fortunately, the latest release has already fixed this issue.

Err, no it hasn't:
https://sources.debian.net/src/stk/4.5.0-3/src/include/asio.h/

James

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

Processed: Re: Bug#823316: stk: contains non-free Steinberg ASIO library

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 4.5.0-1
Bug #823316 [src:stk] stk: contains non-free Steinberg ASIO library
Marked as fixed in versions stk/4.5.0-1.

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

Bug#823316: stk: contains non-free Steinberg ASIO library

[Felipe Sateler]

Control: fixed -1 4.5.0-1

On 3 May 2016 at 08:27, James Cowgill  wrote:
> Source: stk
> Version: 4.4.3-2
> Severity: serious
>
> Hi,
>
> stk contains a bundled copy of the Steinberg ASIO library headers in
> src/include. These files are under very strict licensing terms

Indeed. Fortunately, the latest release has already fixed this issue.

I suppose all we need is to repack source to remove the file for
stable. We are not using the ASIO driver anyway.

Patches (and uploads) welcome. Otherwise it'll take me a few days to do this.

-- 

Saludos,
Felipe Sateler

Bug#823313: r-base-dev: causes r-cran-tgp to FTBFS: error: template with C linkage

[Dirk Eddelbuettel]

On 3 May 2016 at 13:07, Andreas Beckmann wrote:
| Package: r-base-dev
| Version: 3.2.5.20160429-1
| Severity: serious
| Control: block 820866 with -1
| 
| Hi,
| 
| current r-base-dev in sid causes r-cran-tgp to FTBFS (#820866),
| downgrading to 3.2.5-1 makes it build again.
| 
| from the log of an amd64 build:
| 
| g++ -I/usr/share/R/include -DNDEBUG -DRPRINT -DNDEBUG  -fpic  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -g  -c base.cc -o base.o
| In file included from /usr/share/R/include/R.h:40:0,
|  from rhelp.h:20,
|  from base.h:30,
|  from base.cc:25:
| /usr/include/c++/5/cstdlib: In function 'long long int std::abs(long long 
int)':
| /usr/include/c++/5/cstdlib:174:20: error: conflicting declaration of C 
function 'long long int std::abs(long long int)'
|abs(long long __x) { return __builtin_llabs (__x); }
| ^
| /usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
|abs(long __i) { return __builtin_labs(__i); }
|^
| /usr/include/c++/5/cstdlib: In function '__int128 std::abs(__int128)':
| /usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C 
function '__int128 std::abs(__int128)'
|abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
|  ^
| /usr/include/c++/5/cstdlib:174:3: note: previous declaration 'long long int 
std::abs(long long int)'
|abs(long long __x) { return __builtin_llabs (__x); }
|^
| /usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C 
function '__int128 std::abs(__int128)'
|abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
|  ^
| /usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
|abs(long __i) { return __builtin_labs(__i); }
|^
| In file included from /usr/include/c++/5/cmath:42:0,
|  from /usr/share/R/include/R.h:43,
|  from rhelp.h:20,
|  from base.h:30,
|  from base.cc:25:
| /usr/include/c++/5/bits/cpp_type_traits.h: At global scope:
| /usr/include/c++/5/bits/cpp_type_traits.h:72:3: error: template with C linkage
|template
|^
| /usr/include/c++/5/bits/cpp_type_traits.h:85:3: error: template with C linkage
|template
|^
| /usr/include/c++/5/bits/cpp_type_traits.h:89:3: error: template 
specialization with C linkage
|template<>
|^
| /usr/include/c++/5/bits/cpp_type_traits.h:95:3: error: template with C linkage
|template
|^
| /usr/include/c++/5/bits/cpp_type_traits.h:103:3: error: template with C 
linkage
|template
|^
| 

Based on a few R packages of mine, I also suspect that this can be fixed
somewhat 'simply' by declaring the C++11 compilation standard. I'll try to
test that hypothesis later today.

Dirk
 
| Andreas

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: severity of 822322 is normal

[Debian Bug Tracking System]

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

> severity 822322 normal
Bug #822322 [src:openmeeg] openmeeg: please drop B-D alternative on vtk5
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#820866: R and r-cran-tgp

[Dirk Eddelbuettel]

Darn. R 3.3.0 was just released, I just uploaded Debian binaries and it is
likely that it is very close to the last 3.2.5.20160429 'rc' upload I made.

Did you by any chance check with the maintainers of r-cran-tgp upstream?
See  of r-cran-tgp upstream? The CRAN page at

 https://cloud.r-project.org/web/packages/tgp/index.html
 
points to Professors Gramacy and Taddy here in Chicago (and I happen to know
both of them)?  Under standard R usage this is more likely to be an issue
with the package.  Also see the CRAN tests results

 https://cloud.r-project.org/web/checks/check_results_tgp.html

which comprises testing on Debian 'testing' so I am a bit surprised here.

Will follow-up --- but if you could confirm/check that R 3.3.0 also fails it
would help.

Thanks, Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#823318: giada: contains non-free Steinberg ASIO library

[James Cowgill]

Source: giada
Version: 0.11.2~dfsg-1
Severity: serious

Hi,

giada contains a bundled copy of the Steinberg ASIO library headers in
src/deps/rtaudio-mod/include. These files are under very strict
licensing terms which can be found here (you have to download the SDK
and open the PDF):
http://www.steinberg.net/en/company/developers.html

The term "Licensed Software Developer Kit" appears to cover all the
code:

1.1
The object of this agreement consists of the Steinberg ASIO (Audio
Stream I/O) Software Development Kit version 2.3, respectively any
preview version of this Kit, comprising of documentation, example code,
and several ASIO examples. These are described hereinafter as the
"Licensed Software Developer Kit".

The license goes on to include other terms which seem to prohibit
modification or redistribution in most cases:

2.3
The Licensee has no permission to sell, license, give-away and/or
distribute the Licensed Software Developer Kit or parts of it for the
use as software developer kit in any way, for example, integrated in
any framework application, on any medium, including the Internet, to
any other person, including sub-licensors of the Licensee or companies
where the Licensee has any involvement. This includes re-working this
specification, or reverse-engineering any products based upon this
specification.

2.4
In case the Licensed Software Developer Kit is modified, it shall not
be published, sold or distributed without agreement of Steinberg.
Furthermore, the naming of the Licensed Software Developer Kit shall
not include “ASIO 2.3 SDK” or any combination containing the VST brand
without permission of Steinberg.

Thanks,
James

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

Bug#823316: stk: contains non-free Steinberg ASIO library

[James Cowgill]

Source: stk
Version: 4.4.3-2
Severity: serious

Hi,

stk contains a bundled copy of the Steinberg ASIO library headers in
src/include. These files are under very strict licensing terms which
can be found here (you have to download the SDK and open the PDF):
http://www.steinberg.net/en/company/developers.html

The term "Licensed Software Developer Kit" appears to cover all the
code:

1.1
The object of this agreement consists of the Steinberg ASIO (Audio
Stream I/O) Software Development Kit version 2.3, respectively any
preview version of this Kit, comprising of documentation, example code,
and several ASIO examples. These are described hereinafter as the
"Licensed Software Developer Kit".

The license goes on to include other terms which seem to prohibit
modification or redistribution in most cases:

2.3
The Licensee has no permission to sell, license, give-away and/or
distribute the Licensed Software Developer Kit or parts of it for the
use as software developer kit in any way, for example, integrated in
any framework application, on any medium, including the Internet, to
any other person, including sub-licensors of the Licensee or companies
where the Licensee has any involvement. This includes re-working this
specification, or reverse-engineering any products based upon this
specification.

2.4
In case the Licensed Software Developer Kit is modified, it shall not
be published, sold or distributed without agreement of Steinberg.
Furthermore, the naming of the Licensed Software Developer Kit shall
not include “ASIO 2.3 SDK” or any combination containing the VST brand
without permission of Steinberg.

Thanks,
James

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

Processed: Re: r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = sid stretch
Bug #820866 [src:r-cran-tgp] r-cran-tgp: FTBFS: cmath:171:3: error: template 
with C linkage
Added tag(s) sid and stretch; removed tag(s) moreinfo and unreproducible.

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

Bug#820866: r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage

[Andreas Beckmann]

Control: tags -1 = sid stretch

On 2016-05-02 16:52, Pablo Oliveira wrote:
> Dear both,
> 
> On Wed, 20 Apr 2016 03:44:41 +0200 Andreas Beckmann  wrote:
>> Hi Chris,
>> [...]
>>
>> I cannot reproduce this in my sid pbuilder setup. Could you check again?
>> (I think gcc got updated since you filed this bug.)
> 
> I am able to reproduce the problem using cowbuilder unstable/amd64.
> 
> I will try to see if the new upstream version (2.4-14) fixes the problem
> and update the package.

Now I can reproduce it as well. Probably my mirror was a little bit
behind at the time I initially tried it. The problem is
introduced with r-base-dev/r-base-core 3.2.5.20160429-1, building in sid
with the version from testing (3.2.5-1) works fine.

I just filed a bug against r-base-dev.

Andreas

Bug#823313: r-base-dev: causes r-cran-tgp to FTBFS: error: template with C linkage

[Andreas Beckmann]

Package: r-base-dev
Version: 3.2.5.20160429-1
Severity: serious
Control: block 820866 with -1

Hi,

current r-base-dev in sid causes r-cran-tgp to FTBFS (#820866),
downgrading to 3.2.5-1 makes it build again.

from the log of an amd64 build:

g++ -I/usr/share/R/include -DNDEBUG -DRPRINT -DNDEBUG  -fpic  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -g  -c base.cc -o base.o
In file included from /usr/share/R/include/R.h:40:0,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/cstdlib: In function 'long long int std::abs(long long int)':
/usr/include/c++/5/cstdlib:174:20: error: conflicting declaration of C function 
'long long int std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
/usr/include/c++/5/cstdlib: In function '__int128 std::abs(__int128)':
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function 
'__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:174:3: note: previous declaration 'long long int 
std::abs(long long int)'
   abs(long long __x) { return __builtin_llabs (__x); }
   ^
/usr/include/c++/5/cstdlib:179:33: error: conflicting declaration of C function 
'__int128 std::abs(__int128)'
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
 ^
/usr/include/c++/5/cstdlib:166:3: note: previous declaration 'long int 
std::abs(long int)'
   abs(long __i) { return __builtin_labs(__i); }
   ^
In file included from /usr/include/c++/5/cmath:42:0,
 from /usr/share/R/include/R.h:43,
 from rhelp.h:20,
 from base.h:30,
 from base.cc:25:
/usr/include/c++/5/bits/cpp_type_traits.h: At global scope:
/usr/include/c++/5/bits/cpp_type_traits.h:72:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:85:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:89:3: error: template specialization 
with C linkage
   template<>
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:95:3: error: template with C linkage
   template
   ^
/usr/include/c++/5/bits/cpp_type_traits.h:103:3: error: template with C linkage
   template
   ^


Andreas

Processed: r-base-dev: causes r-cran-tgp to FTBFS: error: template with C linkage

[Debian Bug Tracking System]

Processing control commands:

> block 820866 with -1
Bug #820866 [src:r-cran-tgp] r-cran-tgp: FTBFS: cmath:171:3: error: template 
with C linkage
820866 was not blocked by any bugs.
820866 was not blocking any bugs.
Added blocking bug(s) of 820866: 823313

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

Bug#819606: Doxygen help needed (Was: FTBFS: error while building documentation)

[Andreas Tille]

Hi,

as you can read below upstream can not reproduce this problem.  I
checked the last upstream version and the problem persists - probably
due to different doxygen versions?  I've moved the packaging of cimg
to Git

  https://anonscm.debian.org/git/debian-science/packages/cimg.git

and injected the latest upstream version there.  Any help from an
doxygen expert would be welcome.

Kind regards

  Andreas.

On Fri, Apr 29, 2016 at 08:49:07AM +0200, David Tschumperlé wrote:
> Hello Andreas,
> 
> I've just tested here with the latest version available (1.7.1), and
> everything works as expected, without error.
> Maybe there was an error in 1.6.5, but so far it seems to have been fixed.
> 
> Regards,
> 
> David.
> 
> 2016-04-28 16:45 GMT+02:00 Andreas Tille :
> 
> > Hi David,
> >
> > there is an error when trying to build the cimg documentation that did
> > not happened before (= at the time when I have created the package).
> >
> > The log which you can find in the Debian bug tracking system[1] in full
> > length says:
> >
> > ...
> > Runaway argument?
> > {\texorpdfstring {operator\%=(const t value)}{operator\begin {DoxyPar\ETC.
> > ! Paragraph ended before \@sect was complete.
> > 
> >\par
> > l.4286
> >
> > ?
> > ! Emergency stop.
> > 
> >\par
> > l.4286
> >
> > !  ==> Fatal error occurred, no output PDF file produced!
> > Transcript written on refman.log.
> > Makefile:6: recipe for target 'refman.pdf' failed
> >
> >
> > Have you ever heard of similar issues?  Is there perhaps an explanation
> > or a known patch?
> >
> > Kind regards
> >
> >Andreas.
> >
> >
> > [1]
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;filename=cimg_1.6.5%2Bdfsg-1_amd64.build;msg=5;bug=819606
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Bug#823186: chromium: crashes on many websites

[Boris Pek]

control: reopen 823186 =
control: notfixed 823186 50.0.2661.75-2
control: severity 823186 important


Hi,

>>  Chromium become completely unusable at many websites since version
>>  50.0.2661.75-1. See screenshot and stack trace examples in attachments.
>>  And this is not duplicate of bug #821154, because watching videos at
>>  youtube.com have been fixed in 50.0.2661.75-2 and still works, but other
>>  websites -- do not.
>>
>>  After updating from chromium 49.0.2623.108-1 some packages are no longer
>>  required:
>> libavcodec-ffmpeg56 (7:2.8.6-1+b2)
>> libavformat-ffmpeg56 (7:2.8.6-1+b2)
>> libavutil-ffmpeg54 (7:2.8.6-1+b2)
>> libswresample-ffmpeg1 (7:2.8.6-1+b2)
>>
>>  Probably chromium was built incorrectly it lacks some mandatory features.
>
> This issue was fixed in 50.0.2661.75-2.

Please read bug reports carefully before closing them.

In 50.0.2661.75-2 you have fixed only HTML5 videos on websites like youtube.com.

But problem from this bug report is not fixed nor in 50.0.2661.75-2, nor in
50.0.2661.94-1. It 100% reproducible. For example, open URL [1] and chromium tab
will crash immediately. Another crash you may see if you click on any play
button at [2]. And there are more affected websites. In my case the most
annoying problem is that I can't access to my email correspondence via Web UI,
as you may see at screenshot in attachments.

I have tested chromium with and without extensions.

[1] https://www.chess.com/echess/game?id=131722832
[2] https://music.yandex.ru/artist/233138


Next:

$ apt-cache show chromium
Package: chromium
...
Version: 50.0.2661.94-1
...
Architecture: i386
...
Depends: libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4),
 libavcodec57 (>= 7:3.0) | libavcodec-extra57 (>= 7:3.0),
 libavformat57 (>= 7:3.0), libavutil55 (>= 7:3.0), libc6 (>= 2.15),
 libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14),
 libexpat1 (>= 2.0.1), libfontconfig1 (>= 2.11), libfreetype6 (>= 2.4.2),
 libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.41.1),
 libgnome-keyring0 (>= 3.2.2-2~), libgtk2.0-0 (>= 2.24.0),
 libjpeg62-turbo (>= 1.3.1), libnspr4 (>= 2:4.9-2~) | libnspr4-0d (>= 1.8.0.10),
 libnss3 (>= 2:3.13.4-2~) | libnss3-1d (>= 3.12.4), libpango-1.0-0 (>= 1.14.0),
 libpangocairo-1.0-0 (>= 1.14.0), libpci3 (>= 1:3.3.1-1),
 libspeechd2 (>= 0.7.1), libstdc++6 (>= 5.2), libx11-6 (>= 2:1.4.99.1),
 libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1),
 libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxml2 (>= 2.7.4),
 libxrandr2 (>= 2:1.2.99.2), libxrender1, libxslt1.1 (>= 1.1.25), libxss1,
 libxtst6, x11-utils, xdg-utils
...

I don't see anything related to libswresample. It may be related to the problem
or not related. Just a note which may be useful.


My system is up to date Debian Sid with i686-pae kernel.

Please ask if you need more info or any tests, but do not just close bug report.

Best regards,
Boris

Processed: Re: Bug#823186: chromium: crashes on many websites

[Debian Bug Tracking System]

Processing control commands:

> reopen 823186 =
Bug #823186 {Done: Sebastian Ramacher } [chromium] 
chromium: crashes on many websites
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 50.0.2661.75-2.
> notfixed 823186 50.0.2661.75-2
Bug #823186 [chromium] chromium: crashes on many websites
Ignoring request to alter fixed versions of bug #823186 to the same values 
previously set
> severity 823186 important
Bug #823186 [chromium] chromium: crashes on many websites
Severity set to 'important' from 'grave'

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

Bug#823310: libnanomsg-raw-perl: FTBFS: test failures

[Emilio Pozuelo Monfort]

Package: libnanomsg-raw-perl
Version: 0.06-1
Severity: serious

On a rebuild against libnanomsg4, your package failed to build
everywhere:

https://buildd.debian.org/status/package.php?p=libnanomsg-raw-perl

Emilio

Bug#805852: ipe: diff for NMU version 7.1.10-1.2

[Manuel A. Fernandez Montecelo]

Hi Laurent,

2016-05-02 16:22 Laurent Bigonville:

Control: tags 805852 + pending

Dear maintainer,

I've prepared an NMU for ipe (versioned as 7.1.10-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.


Thanks a lot for this.  I just noticed that it affects one of my
packages so I was about to NMU it myself, and came here only to see that
you saved me from it.

So just wanted to say that -- Thanks!

--
Manuel A. Fernandez Montecelo 

Bug#823309: missing dependency on python-networkx

[Robert Bihlmeyer]

Package: androguard
Version: 2.0-1
Severity: serious

  $ apkviewer foo.apk
  Traceback (most recent call last):
File "/usr/bin/apkviewer", line 25, in 
  from androguard.core.data import data
File "/usr/lib/python2.7/dist-packages/androguard/core/data/data.py", line 
18, in 
  from networkx import DiGraph
  ImportError: No module named networkx

Installing python-networkx fixes it.

-- System Information:

Versions of packages androguard depends on:
ii  ipython   2.3.0-2
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18+deb8u4
ii  libgcc1   1:4.9.2-10
ii  liblzma5  5.1.1alpha+20120614-2+b3
ii  libmuparser2  2.2.3-4
ii  libsnappy11.1.2-3
ii  libstdc++64.9.2-10
ii  zlib1g1:1.2.8.dfsg-2+b1

androguard recommends no packages.

Versions of packages androguard suggests:
pn  python-pyside.qtcore  
pn  python-pyside.qtgui   

Processed: reopening 822322

[Debian Bug Tracking System]

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

> reopen 822322
Bug #822322 {Done: Yaroslav Halchenko } [src:openmeeg] 
openmeeg: please drop B-D alternative on vtk5
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmeeg/2.3.0~20160502-1.
> thanks
Stopping processing here.

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

Bug#822322: openmeeg: please switch to vtk6

[Tobias Frost]

Package: src:openmeeg
Followup-For: Bug #822322
Control: retitle -1 openmeeg: please drop B-D alternative on vtk5

Hi Yaroslav,

Thanks for the upload of openmeeg to experimental, and hoping the best that it
"feels well" there as you wrote in #809671 ;-)

However let me reopen this bug and downgrade its severity because of this
changelog entry:

 bdepend on vtk6 (allowing vtk5 as alternative) (Closes: #822322)

vtk5 will be removed very soon and vtk6 is even available in jessie,
so this alternative can really go away. It is also bpo safe.

So please just depend on vtk6 and drop the vtk5 entierly.

Many thanks,

-- 
tobi

PS: Can you push your changes to the repository? Thanks!

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Processed: Re: openmeeg: please switch to vtk6

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 openmeeg: please drop B-D alternative on vtk5
Bug #822322 {Done: Yaroslav Halchenko } [src:openmeeg] 
openmeeg: please switch to vtk6
Changed Bug title to 'openmeeg: please drop B-D alternative on vtk5' from 
'openmeeg: please switch to vtk6'.

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

Bug#823297: libbotan: security update breaks monotone

[Tim Weippert]

Package: libbotan-1.10-0
Version: 1.10.8-2+deb8u1
Severity: grave
File: libbotan
Justification: renders package unusable

Dear Maintainer,

it seems that the recent security update breaks monotone:

mtn: Symbol `_ZTVN5Botan17DataSource_MemoryE' has different size in shared 
object, consider re-linking
mtn: updating along branch 'net.dn42.registry'
mtn: fatal signal: Segmentation fault
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to 

do not send a core dump, but if you have one, 
please preserve it in case we ask you for information from it.
Segmentation fault

Maybe the bug should also be sent to monotone for rebuilding?

cheers, 
tim

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages libbotan-1.10-0 depends on:
ii  libbz2-1.0   1.0.6-7+b3
ii  libc62.19-18+deb8u4
ii  libgcc1  1:4.9.2-10
ii  libgmp10 2:6.0.0+dfsg-6
ii  libssl1.0.0  1.0.1k-3+deb8u4
ii  libstdc++6   4.9.2-10
ii  zlib1g   1:1.2.8.dfsg-2+b1

libbotan-1.10-0 recommends no packages.

libbotan-1.10-0 suggests no packages.

-- no debconf information

Bug#821443: marked as done (qmmp: FTBFS on armel and armhf)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 07:04:31 +
with message-id 
and subject line Bug#821443: fixed in qmmp 1.0.5-1.1
has caused the Debian Bug report #821443,
regarding qmmp: FTBFS on armel and armhf
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.)


-- 
821443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmmp
Version: 1.0.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid stretch

qmmp FTBFS on armel and armhf:
| make[1]: Leaving directory '/«PKGBUILDDIR»/obj-arm-linux-gnueabi'
|debian/rules override_dh_install
| make[1]: Entering directory '/«PKGBUILDDIR»'
| dh_install -pqmmp-plugin-projectm
| dh_install: qmmp-plugin-projectm missing files: 
usr/lib/qmmp/qmmp/Visual/libprojectm.so
| dh_install: missing files, aborting
| debian/rules:35: recipe for target 'override_dh_install' failed
| make[1]: *** [override_dh_install] Error 2

See
https://buildd.debian.org/status/fetch.php?pkg=qmmp=armel=1.0.5-1=1453581975
for a full build log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qmmp
Source-Version: 1.0.5-1.1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated qmmp 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: Tue, 03 May 2016 08:41:32 +0200
Source: qmmp
Binary: qmmp qmmp-plugin-projectm
Architecture: source
Version: 1.0.5-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matteo Cypriani 
Changed-By: Sebastian Ramacher 
Description:
 qmmp   - feature-rich audio player with support of many formats
 qmmp-plugin-projectm - qmmp audio player -- projectM visualization plugin
Closes: 821443
Changes:
 qmmp (1.0.5-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/{control,rules}: Do not build qmmp-plugin-projectm on armel and
 armhf. (Closes: #821443)
Checksums-Sha1:
 c6ba3c1487f1cfed0f0285c04e32e3e09de6af64 2637 qmmp_1.0.5-1.1.dsc
 71be4590916f3bd283af7a4339577b67f57bfd94 14652 qmmp_1.0.5-1.1.debian.tar.xz
Checksums-Sha256:
 995cfdb98976ff791cb8a0b17f0aa36a1ac09f4388488213c485e23c3f4dbd86 2637 
qmmp_1.0.5-1.1.dsc
 a4dc110cf88b558cd77abb818ceffe3f1bea706f3d66640882aecca255f8 14652 
qmmp_1.0.5-1.1.debian.tar.xz
Files:
 88a5954ecae37f6e159b76b45989d431 2637 sound optional qmmp_1.0.5-1.1.dsc
 8f64e1024e1703ff5e6887418f2a82b7 14652 sound optional 
qmmp_1.0.5-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXKEqyAAoJEGny/FFupxmT1ZoQALL9uhKn5v7o27yfABdiWja2
P2Hf6Gyi+LL9dHRDvo6JQu0FsnQ2AOIqjUATD/acRcQSo3fKocLOrpfLT6y7llPO
OSZCgvm0bI+gvI5IU6uiNvQKCb5Jjn0MjK0mD5s3jRSD+dZGU2iuj9ntT5QcPg0s
eJHXNkRd27q6u1aM6+n2+TN5eOFVdcdJGjJC3u2orkPGhCmJiWF+IoaEWf0SlXK8
fkoqhjveD1wLzFOpR0KunecMMYTZQrjzBclYatd1VZvKNj9FGsjxlw4Lpj5+a/zG
/vecB9Lc7J+2pr2SJusxYsvzjlPF9Jp1cnOCYLxWU7f+WNPMNyx6rc/uRruaayZr
APMhZzJRaUdpeI5J5sHep8nS7dEEM2G791w0h6ltETQ2761PJ2tc1Sx2NvFQR8dK
DKC+LoqNriiUIfMlar4jRGG/B/OfcStdn1Wz95ioOit/FK1oQ1cO6nsKfYxKiEhi
Oj8B7s8xlA6MEoU+i9FzmvOiQPcv1CdqhcQBfUi+ckKD6EQlBh1ghVdzUDdnGEoN
2opxMLs+x9AUlYaXQomeKJ4lIjdz0+SfOzjes29KkhKIsqCwgaOgl5E+Wimz2VjZ
WGTJsehnSzQ5/HdA+25SCBk9PhL1vHsUsDvk4caizik4YciNN5oRuBcV9EcD3Emf
ZBSg8fKl7Hdebyh9buXU
=xb21
-END PGP SIGNATURE End Message ---

Bug#808696: marked as done (zzuf: FTBFS: check-utils fails at fread(1,100) fseek(50,SEEK_SET) fread(1,33000))

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 07:04:46 +
with message-id 
and subject line Bug#808696: fixed in zzuf 0.15-1
has caused the Debian Bug report #808696,
regarding zzuf: FTBFS: check-utils fails at fread(1,100) fseek(50,SEEK_SET) 
fread(1,33000)
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.)


-- 
808696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zzuf
Version: 0.14-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:

make[4]: Entering directory '/zzuf-0.14/test'
PASS: check-zzuf-A-autoinc
PASS: check-zzuf-f-fuzzing
PASS: check-zzuf-m-md5
PASS: check-zzuf-M-max-memory
PASS: check-zzuf-r-ratio
PASS: check-source
PASS: check-win32
PASS: check-overflow
PASS: check-div0
FAIL: check-utils
PASS: check-mmap

Testsuite summary for zzuf 0.14

# TOTAL: 11
# PASS:  10
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log

Makefile:723: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/zzuf-0.14/test'



zzuf-0.14/test% egrep '^\*|FAILED' check-utils.log
*** running zzuf utils test suite with seed 71703058 ***
*** file ./file-00, ratio 0.0 ***
*** should be bb7df04e1b0a2570657527a7e108ae23 ***
*** file ./file-ff, ratio 0.0 ***
*** file ./file-text, ratio 0.0 ***
*** file ./file-random, ratio 0.0 ***
*** file ./file-00, ratio 0.001 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 202ac6c66ac6e7c369ca58cce2462129 FAILED
*** file ./file-ff, ratio 0.001 ***
 fread(1,100) fseek(50,SEEK_SET) fread( fd5943554c2ba1f4dedf20fccf0ae4f0 FAILED
*** file ./file-text, ratio 0.001 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 9f9cd97f263a03c51d4590b93350d5cc FAILED
*** file ./file-random, ratio 0.001 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 501242a3ca8970e96ab22394ae9d9cc3 FAILED
*** file ./file-00, ratio 1.0 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 6de5641171d7036b59ae4b328df5d77c FAILED
*** file ./file-ff, ratio 1.0 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 527f799e4e976a40293b1f757e29a325 FAILED
*** file ./file-text, ratio 1.0 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 48b3257f130b2db2016bf9569c964e60 FAILED
*** file ./file-random, ratio 1.0 ***
 fread(1,100) fseek(50,SEEK_SET) fread( 6ac46d8b0e20f804904df1fb8bd3ceec FAILED
*** 8 tests failed out of 565 ***



This fails if re-run interactively, as a different user, without any security, 
etc.

Maybe it's angry about btrfs *and* tmpfs?  Seems unlikely.


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

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

Debian distribution maintenance software
pp.
Sam Hocevar  (supplier of updated zzuf 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: Tue, 03 May 2016 08:32:17 +0200
Source: zzuf
Binary: zzuf
Architecture: source amd64
Version: 0.15-1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar 
Changed-By: Sam Hocevar 
Description:
 zzuf   - transparent application fuzzer
Closes: 808696
Changes:
 zzuf (0.15-1) unstable; urgency=medium
 .
   * New upstream release.
   * This version fixes the testsuite for recent glibcs (Closes: #808696).
Checksums-Sha1:
 6de503690a620a569c6c4a586e30e2bc26e3c7df 1617 zzuf_0.15-1.dsc
 

Bug#790297: marked as done (zzuf: FTBFS with glibc 2.21 and gcc-5)

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 07:04:46 +
with message-id 
and subject line Bug#808696: fixed in zzuf 0.15-1
has caused the Debian Bug report #808696,
regarding zzuf: FTBFS with glibc 2.21 and gcc-5
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.)


-- 
808696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zzuf
Version: 0.13.svn20100215-4.1
Severity: normal

>From my pbuilder build log, using a setup preferring glibc and gcc-defaults
from experimental:

...
 fakeroot debian/rules binary
/usr/bin/make check
make[1]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215'
Making check in src
make[2]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215/src'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215/src'
Making check in test
make[2]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
/usr/bin/make  check-TESTS
make[3]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
make[4]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
PASS: check-zzuf-A-autoinc
PASS: check-zzuf-f-fuzzing
PASS: check-zzuf-m-md5
PASS: check-zzuf-M-max-memory
PASS: check-zzuf-r-ratio
PASS: check-source
PASS: check-win32
PASS: check-overflow
PASS: check-div0
FAIL: check-utils
make[5]: Entering directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215/test'

Testsuite summary for zzuf 0.13

# TOTAL: 10
# PASS:  9
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log

Makefile:690: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
Makefile:796: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
Makefile:932: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215/test'
Makefile:402: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/tmp/buildd/zzuf-0.13.svn20100215'
debian/rules:44: recipe for target 'check-stamp' failed
make: *** [check-stamp] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: zzuf
Source-Version: 0.15-1

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

Debian distribution maintenance software
pp.
Sam Hocevar  (supplier of updated zzuf 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: Tue, 03 May 2016 08:32:17 +0200
Source: zzuf
Binary: zzuf
Architecture: source amd64
Version: 0.15-1
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar 
Changed-By: Sam Hocevar 
Description:
 zzuf   - transparent application fuzzer
Closes: 808696
Changes:
 zzuf (0.15-1) unstable; urgency=medium
 .
   * New upstream release.
   * This version fixes the testsuite for recent glibcs (Closes: #808696).
Checksums-Sha1:
 6de503690a620a569c6c4a586e30e2bc26e3c7df 1617 zzuf_0.15-1.dsc
 21541d54cec64750c2dd3366a73832e6f5250833 493559 zzuf_0.15.orig.tar.gz
 6a73e62f452b078461ac7d1a0a9fd521cd73bb5e 2972 zzuf_0.15-1.debian.tar.xz
 959033322b1300fa97a9244136542526e0151b49 119990 zzuf-dbgsym_0.15-1_amd64.deb
 ee895daf0cd563db16ea80e0d3b25274bd04beb0 61324 zzuf_0.15-1_amd64.deb
Checksums-Sha256:
 98b0f16e2071828acd4f78bc78a62284b1a817d137c47be526e63c99ad493150 1617 

Bug#821443: qmmp: diff for NMU version 1.0.5-1.1

[Sebastian Ramacher]

Control: tags 821443 + patch

Dear maintainer,

I've prepared an NMU for qmmp (versioned as 1.0.5-1.1). The diff
is attached to this message.

Regards.

-- 
Sebastian Ramacher
diff -Nru qmmp-1.0.5/debian/changelog qmmp-1.0.5/debian/changelog
--- qmmp-1.0.5/debian/changelog	2016-01-23 13:55:41.0 +0100
+++ qmmp-1.0.5/debian/changelog	2016-05-03 08:41:33.0 +0200
@@ -1,3 +1,11 @@
+qmmp (1.0.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/{control,rules}: Do not build qmmp-plugin-projectm on armel and
+armhf. (Closes: #821443)
+
+ -- Sebastian Ramacher   Tue, 03 May 2016 08:41:32 +0200
+
 qmmp (1.0.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru qmmp-1.0.5/debian/control qmmp-1.0.5/debian/control
--- qmmp-1.0.5/debian/control	2016-01-23 13:55:41.0 +0100
+++ qmmp-1.0.5/debian/control	2016-05-02 21:27:05.0 +0200
@@ -10,7 +10,7 @@
   libsndfile1-dev, libwavpack-dev, libpulse-dev, libavcodec-dev,
   libavformat-dev, libcdio-dev, libcdio-paranoia-dev, libcddb2-dev,
   libfaad-dev, libgme-dev, libopus-dev (>= 1.0.2), libopusfile-dev,
-  libwildmidi-dev, libsidplayfp-dev (>= 1.0.3), libbs2b-dev, libprojectm-dev,
+  libwildmidi-dev, libsidplayfp-dev (>= 1.0.3), libbs2b-dev, libprojectm-dev [!armel !armhf],
   libenca-dev
 Standards-Version: 3.9.6
 Homepage: http://qmmp.ylsoftware.com/
@@ -85,7 +85,7 @@
   - global hotkeys
 
 Package: qmmp-plugin-projectm
-Architecture: any
+Architecture: any-amd64 any-arm64 any-i386 any-mips any-mipsel any-powerpc any-ppc64el any-s390x any-alpha any-hppa any-m68k any-mips64el any-powerpcspe any-sh4 any-sparc64 any-x32
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: qmmp audio player -- projectM visualization plugin
  Qmmp is feature-rich audio player with support of many formats.
diff -Nru qmmp-1.0.5/debian/rules qmmp-1.0.5/debian/rules
--- qmmp-1.0.5/debian/rules	2016-01-23 13:55:41.0 +0100
+++ qmmp-1.0.5/debian/rules	2016-05-03 08:40:44.0 +0200
@@ -32,7 +32,9 @@
 	dh_auto_build -- VERBOSE=1
 
 override_dh_install:
+ifneq (,$(filter-out armel armhf,$(DEB_HOST_ARCH)))
 	dh_install -pqmmp-plugin-projectm
+endif
 	dh_install -Xprojectm
 
 # Avoid a call to ldconfig in postinst & postrm (ldconfig is not needed since we


signature.asc
Description: PGP signature

Processed: qmmp: diff for NMU version 1.0.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 821443 + patch
Bug #821443 [src:qmmp] qmmp: FTBFS on armel and armhf
Added tag(s) patch.

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

Bug#823294: cpants-lint: fails to install

[Paul Wise]

Package: cpants-lint
Version: 0.05-4
Severity: serious
File: cpants-lint

cpants-lint fails to install, requisite Conflicts/Replaces are missing:

# apt install cpants-lint
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-image-amd64
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libapp-cpants-lint-perl libarchive-any-lite-perl libarray-diff-perl 
libcpan-distnameinfo-perl libfile-find-object-perl libio-capture-perl 
libmodule-cpants-analyse-perl
  libmodule-extractuse-perl libpod-strip-perl libset-scalar-perl
The following NEW packages will be installed:
  cpants-lint libapp-cpants-lint-perl libarchive-any-lite-perl 
libarray-diff-perl libcpan-distnameinfo-perl libfile-find-object-perl 
libio-capture-perl libmodule-cpants-analyse-perl
  libmodule-extractuse-perl libpod-strip-perl libset-scalar-perl
0 upgraded, 11 newly installed, 0 to remove and 9 not upgraded.
Need to get 264 kB of archives.
After this operation, 1,379 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mirror.linux.org.au/debian testing/main amd64 
libarchive-any-lite-perl all 0.10-2 [8,280 B]
Get:2 http://mirror.linux.org.au/debian testing/main amd64 libarray-diff-perl 
all 0.07-2 [7,438 B]
Get:3 http://mirror.linux.org.au/debian testing/main amd64 
libcpan-distnameinfo-perl all 0.12-1 [9,472 B]
Get:4 http://mirror.linux.org.au/debian testing/main amd64 
libfile-find-object-perl all 0.2.13-1 [28.4 kB]
Get:5 http://mirror.linux.org.au/debian testing/main amd64 libio-capture-perl 
all 0.05-3 [32.9 kB]
Get:6 http://mirror.linux.org.au/debian testing/main amd64 libpod-strip-perl 
all 1.02-2 [6,678 B]
Get:7 http://mirror.linux.org.au/debian testing/main amd64 
libmodule-extractuse-perl all 0.341-1 [33.8 kB]
Get:8 http://mirror.linux.org.au/debian testing/main amd64 libset-scalar-perl 
all 1.29-1 [35.3 kB]
Get:9 http://mirror.linux.org.au/debian testing/main amd64 
libmodule-cpants-analyse-perl all 0.96-1 [72.3 kB]
Get:10 http://mirror.linux.org.au/debian testing/main amd64 
libapp-cpants-lint-perl all 0.05-3 [17.8 kB]
Get:11 http://mirror.linux.org.au/debian unstable/main amd64 cpants-lint all 
0.05-4 [11.1 kB]
Fetched 264 kB in 5s (48.4 kB/s)
Selecting previously unselected package libarchive-any-lite-perl.
(Reading database ... 372849 files and directories currently installed.)
Preparing to unpack .../libarchive-any-lite-perl_0.10-2_all.deb ...
Unpacking libarchive-any-lite-perl (0.10-2) ...
Selecting previously unselected package libarray-diff-perl.
Preparing to unpack .../libarray-diff-perl_0.07-2_all.deb ...
Unpacking libarray-diff-perl (0.07-2) ...
Selecting previously unselected package libcpan-distnameinfo-perl.
Preparing to unpack .../libcpan-distnameinfo-perl_0.12-1_all.deb ...
Unpacking libcpan-distnameinfo-perl (0.12-1) ...
Selecting previously unselected package libfile-find-object-perl.
Preparing to unpack .../libfile-find-object-perl_0.2.13-1_all.deb ...
Unpacking libfile-find-object-perl (0.2.13-1) ...
Selecting previously unselected package libio-capture-perl.
Preparing to unpack .../libio-capture-perl_0.05-3_all.deb ...
Unpacking libio-capture-perl (0.05-3) ...
Selecting previously unselected package libpod-strip-perl.
Preparing to unpack .../libpod-strip-perl_1.02-2_all.deb ...
Unpacking libpod-strip-perl (1.02-2) ...
Selecting previously unselected package libmodule-extractuse-perl.
Preparing to unpack .../libmodule-extractuse-perl_0.341-1_all.deb ...
Unpacking libmodule-extractuse-perl (0.341-1) ...
Selecting previously unselected package libset-scalar-perl.
Preparing to unpack .../libset-scalar-perl_1.29-1_all.deb ...
Unpacking libset-scalar-perl (1.29-1) ...
Selecting previously unselected package libmodule-cpants-analyse-perl.
Preparing to unpack .../libmodule-cpants-analyse-perl_0.96-1_all.deb ...
Unpacking libmodule-cpants-analyse-perl (0.96-1) ...
Selecting previously unselected package libapp-cpants-lint-perl.
Preparing to unpack .../libapp-cpants-lint-perl_0.05-3_all.deb ...
Unpacking libapp-cpants-lint-perl (0.05-3) ...
Selecting previously unselected package cpants-lint.
Preparing to unpack .../cpants-lint_0.05-4_all.deb ...
Unpacking cpants-lint (0.05-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/cpants-lint_0.05-4_all.deb (--unpack):
 trying to overwrite '/usr/bin/cpants_lint', which is also in package 
libapp-cpants-lint-perl 0.05-3
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/cpants-lint_0.05-4_all.deb

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 

Bug#822784: marked as done (mypaint: Does not start "TypeError: GLib.filename_to_utf8() takes exactly 2 arguments (4 given)")

[Debian Bug Tracking System]

Your message dated Tue, 03 May 2016 06:19:17 +
with message-id 
and subject line Bug#822784: fixed in mypaint 1.2.0-2
has caused the Debian Bug report #822784,
regarding mypaint: Does not start "TypeError: GLib.filename_to_utf8() takes 
exactly 2 arguments (4 given)"
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.)


-- 
822784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mypaint
Version: 1.2.0-1.1+b2
Severity: important

Dear Maintainer,

mypaint does not start, output is:

INFO: mypaint: Installation layout: conventional POSIX-like structure with 
prefix u'/usr'
INFO: lib.i18n: POSIX: LANG='sv_SE.utf8'
INFO: lib.i18n: POSIX: LANGUAGE=None
Traceback (most recent call last):
  File "/usr/bin/mypaint", line 462, in 
main.main(datapath, iconspath, old_confpath, version=version)
  File "/usr/share/mypaint/gui/main.py", line 92, in main
lib.glib.init_user_dir_caches()
  File "/usr/share/mypaint/lib/glib.py", line 109, in init_user_dir_caches
logger.debug("Init g_get_user_config_dir(): %r", get_user_config_dir())
  File "/usr/share/mypaint/lib/glib.py", line 71, in get_user_config_dir
return filename_to_unicode(d_fs)
  File "/usr/share/mypaint/lib/glib.py", line 57, in filename_to_unicode
ustring = GLib.filename_to_utf8(opsysstring, -1, 0, 0)
TypeError: GLib.filename_to_utf8() takes exactly 2 arguments (4 given)

Since it mentions locale and utf8 for some reason, I also confirmed it
behaves the same with LANG=C.

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

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

Versions of packages mypaint depends on:
ii  gir1.2-gtk-3.0   3.18.9-1
ii  libatk1.0-0  2.20.0-1
ii  libc62.22-7
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libgcc1  1:5.3.1-14
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgomp1 5.3.1-14
ii  libgtk-3-0   3.18.9-1
ii  libjson-c3   0.12-3
ii  liblcms2-2   2.7-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpng16-16  1.6.21-2
ii  libpython2.7 2.7.11-8
ii  libstdc++6   5.3.1-14
ii  mypaint-data 1.2.0-1.1
ii  python   2.7.11-1
ii  python-gi-cairo  3.20.0-2
ii  python-numpy 1:1.11.0-1
pn  python2.7:any
pn  python:any   

Versions of packages mypaint recommends:
ii  shared-mime-info  1.5-2

Versions of packages mypaint suggests:
pn  mypaint-data-extras  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mypaint
Source-Version: 1.2.0-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated mypaint 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: Mon,  2 May 2016 23:05:49 PDT
Source: mypaint
Binary: mypaint mypaint-data mypaint-data-extras
Architecture: source all
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Vincent Cheng 
Description: 
 mypaint - paint program for use with graphics tablets
 mypaint-data - runtime data files for MyPaint
 mypaint-data-extras - high resolution backgrounds for mypaint
Closes: 822784
Changes:
 mypaint (1.2.0-2) unstable; urgency=medium
 .
   * Acknowledge NMU. Thanks Tobias!
   * Add debian/patches/fix-glib-2.48-startup-crash.patch to fix startup crash.
 (Closes: #822784)
   * Add myself to Uploaders.
   * Update Standards version to 3.9.8.

Bug#823290: gitlab: several security issues fixed by latest version (including CVE-2016-4340)

[Paul Wise]

Package: gitlab
Severity: serious

GitLab recently fixed several serious security issues:

https://about.gitlab.com/2016/05/02/cve-2016-4340-patches/

CVE-2016-4340: Privilege escalation via "impersonate" feature
Privilege escalation via notes API
Privilege escalation via project webhook API
XSS vulnerability via branch and tag names
XSS vulnerability via custom issue tracker URL
XSS vulnerability via window.opener
XSS vulnerability via label drop-down
Information disclosure via milestone API
Information disclosure via snippet API
Information disclosure via project labels
Information disclosure via new merge request page

Please update the Debian gitlab package to the latest upstream.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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