Processed: notfound 844638 in 0.9.11-1

[Debian Bug Tracking System]

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

> notfound 844638 0.9.11-1
Bug #844638 [prosody] Does not work with lua-sec 0.6
Ignoring request to alter found versions of bug #844638 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: found 844638 in 0.9.10-1

[Debian Bug Tracking System]

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

> found 844638 0.9.10-1
Bug #844638 [prosody] Does not work with lua-sec 0.6
Ignoring request to alter found versions of bug #844638 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: bug 844660 is forwarded to https://github.com/mbunkus/mkvtoolnix/issues/1812

[Debian Bug Tracking System]

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

> forwarded 844660 https://github.com/mbunkus/mkvtoolnix/issues/1812
Bug #844660 [src:mkvtoolnix] mkvtoolnix FTBFS with QT 5.7
Set Bug forwarded-to-address to 
'https://github.com/mbunkus/mkvtoolnix/issues/1812'.
> thanks
Stopping processing here.

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

Bug#844638: Does not work with lua-sec 0.6

[Michael Meskes]

As was just pointed out to me, prosody 0.9.11 works well with lua-sec 0.6. It
would have been nice to have this properly documented and the dependency 
enforced.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Processed: notfound 844638 in 0.9.11-1

[Debian Bug Tracking System]

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

> notfound 844638 0.9.11-1
Bug #844638 [prosody] Does not work with lua-sec 0.6
Ignoring request to alter found versions of bug #844638 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#837009: marked as done (cheetah: FTBFS: debian/rules:20: *** no python implementation resolved from flavor "python$buildver". Stop.)

[Debian Bug Tracking System]

Your message dated Fri, 18 Nov 2016 06:48:45 +
with message-id 
and subject line Bug#837009: fixed in cheetah 2.4.4-4
has caused the Debian Bug report #837009,
regarding cheetah: FTBFS: debian/rules:20: *** no python implementation 
resolved from flavor "python$buildver".  Stop.
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.)


-- 
837009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cheetah
Version: 2.4.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> set -e; cd . && python2 setup.py build 
> --build-base="/<>/./build";
> running build
> running build_py
> running build_ext
> running build_scripts
> touch debian/python-module-stampdir/python-cheetah
> Adding cdbs dependencies to debian/python-cheetah.substvars
> dh_installdirs -ppython-cheetah \
>   
> set -e; cd . && python2 setup.py install 
> --root="/<>/debian/python-cheetah/" --install-layout=deb 
> --no-compile -O0 --single-version-externally-managed;
> running install
> running build
> running build_py
> running build_ext
> running build_scripts
> running install_lib
> creating /<>/debian/python-cheetah/usr
> creating /<>/debian/python-cheetah/usr/lib
> creating /<>/debian/python-cheetah/usr/lib/python2.7
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/SiteHierarchy.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/RecursiveNull.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/CGITemplate.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/__init__.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/MondoReport.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Template.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/FileUtils.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SettingsManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DummyTransaction.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportHooks.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DirectiveAnalyzer.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SourceReader.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Version.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/NameMapper.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Parser.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/CacheStore.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ErrorCatchers.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/WebInputMixin.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-pack

Bug#844683: libreoffice-common 5.3 preinst fails when removing missing directories

[Rene Engelhard]

tag 844683 + pending
thanks

On Fri, Nov 18, 2016 at 11:52:54AM +0800, Drew Parsons wrote:
> libreoffice-common fails during preinst attempting to remove
> directories which are not there:

That is not true.

This is rm_conffile, so "if this obsolete conffile exists, remove it".

> Preparing to unpack .../libreoffice-common_1%3a5.3.0~alpha1-1_all.deb ...
> dpkg-maintscript-helper: error: conffile 
> '"/etc/bash_completion.d/libreoffice.sh"' is not an absolute path

The problem here is the "'s. Seems dpkg accepted it until shortly and chaned
behaviour to stop doing so. Or debhelper, where 5.3 changed to compat 10.
That would explain why 5.2 didn't break.

https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/commit/?h=debian-experimental-5.3&id=e1f72e38cc5820826d146d972098452a5e567f89

is the fix.

> dpkg: error processing archive 
> /var/cache/apt/archives/libreoffice-common_1%3a5.3.0~alpha1-1_all.deb 
> (--unpack):
>  subprocess new pre-installation script returned error exit status 1
> rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or 
> directory
> rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or 
> directory
> rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
> directory
> rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
> rmdir: failed to remove '/var/lib/libreoffice': No suchi file or directory

These are https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754333 and minor.

> The chain of dependencies then prevents the other libreoffice 5.3
> packages from completing their configuration.

I know, I actually saw this, but I didn't care, this is experimental and beta1
is supposed be there next week.
That alpha1 has been in NEW for 3 weeks, enough
that I stopped caring about it already.

Regards,

Rene

Processed: Re: Bug#844683: libreoffice-common 5.3 preinst fails when removing missing directories

[Debian Bug Tracking System]

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

> tag 844683 + pending
Bug #844683 [libreoffice-common] libreoffice-common 5.3 preinst fails when 
removing missing directories
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837009: marked as pending

[Arnaud Fontaine]

tag 837009 pending
thanks

Hello,

Bug #837009 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/cheetah.git;a=commitdiff;h=61d2b11

---
commit 61d2b111ff82a00def81297b7c1f3cf537fbc6bd
Author: Arnaud Fontaine 
Date:   Fri Nov 18 12:48:20 2016 +0900

Fix FTBFS due to change in CDBS 0.4.144 (cdbs_python_binary). Closes: 
#837009.

diff --git a/debian/changelog b/debian/changelog
index 50d4bce..e7df4c0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,11 @@
 cheetah (2.4.4-4) UNRELEASED; urgency=low
 
   [ Arnaud Fontaine ]
-  * debian/rules: add --install-layout=deb to python install command to
-install files in the proper directory, as per dh_python2 warning.
+  * d/rules:
++ Add --install-layout=deb to python install command to
+  install files in the proper directory, as per dh_python2 warning.
++ Fix FTBFS due to change in CDBS 0.4.144 (cdbs_python_binary).
+  Closes: #837009.
   * d/control:
 + Add dh-python to Build-Depends (dh_python2 warning).
 + Bump debhelper compat level to 10 (5 is deprecated).

Processed: Bug#837009 marked as pending

[Debian Bug Tracking System]

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

> tag 837009 pending
Bug #837009 [src:cheetah] cheetah: FTBFS: debian/rules:20: *** no python 
implementation resolved from flavor "python$buildver".  Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#783797: Courier was unable to deliver the parcel, ID4629485

[FedEx SmartPost]

Hello,
Courier was unable to deliver the parcel to you. Shipment Label is attached to 
email.
Nannie Peoples - Area Manager FedEx , CA
Kind regards


FedEx.doc
Description: MS-Word document

Processed: retitle 844546 to teeworlds: CVE-2016-9400: possible remote code execution on the client

[Debian Bug Tracking System]

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

> retitle 844546 teeworlds: CVE-2016-9400: possible remote code execution on 
> the client
Bug #844546 {Done: Felix Geyer } [teeworlds] teeworlds: 
possible remote code execution on the client
Changed Bug title to 'teeworlds: CVE-2016-9400: possible remote code execution 
on the client' from 'teeworlds: possible remote code execution on the client'.
> thanks
Stopping processing here.

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

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Stefan Fritsch]

On Friday, 18 November 2016 01:09:53 CET Adrian Bunk wrote:
> On Thu, Nov 17, 2016 at 11:18:57PM +0100, Stefan Fritsch wrote:
> > On Thursday, 17 November 2016 21:39:19 CET Kurt Roeckx wrote:
> > > > That header was created for mod_ssl_ct which provides support for
> > > > certificate  transparency. It's quite new and likely that nothing else
> > > > uses the header. It would probably be acceptable to remove the
> > > > dependency
> > > > in apache2-dev on libssl-dev and add a caveat to the README.Debian. I
> > > > could also not install the header, or put it into a separate new
> > > > package
> > > > that depends on libssl-dev.
> > > 
> > > So can you confirm that the only reason for the libssl-dev
> > > depedency is that file?
> > 
> > Yes.
> 
> What does create the dependency in
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828330#16
> ?

By including its own copy of ssl_private.h from the apache source (not 
installed in apache2-dev). Urgh.

/*
 * After 2.0.49, Apache mod_ssl has most of the mod_ssl structures defined
 * in ssl_private.h, which is not installed along with httpd-devel (eg in
 * the FC2 RPM.) This include file provides SIMPLIFIED structures for use
 * by mod_gridsite: for example, pointers to unused structures are replaced
 * by  void *  and some of the structures are truncated when only the early
 * members are used.
 *
 * CLEARLY, THIS WILL BREAK IF THERE ARE MAJOR CHANGES TO ssl_private.h!!!
 */

That's very ugly. So, not installing mod_ssl_openssl.h or a caveat in 
README.Debian would not help.

But putting it into a separate apache2-mod_ssl-dev package with the proper 
mod_ssl dependency would still work. gridsite would then need to build-dep on 
that package and (AFAICS) php does not do the same ugly tricks and would be 
unaffected by the dependency on libssl1.0-dev.

Bug#834080: elasticsearch: FTBFS: Could not resolve dependencies for project org.elasticsearch:elasticsearch:jar:1.7.5

[tony mancill]

On Thu, Nov 17, 2016 at 09:11:14AM +0100, Michael Prokop wrote:
> * Hans Joachim Desserud [Tue Oct 04, 2016 at 09:40:16PM +0200]:
> 
> > After adding a build dependency on libantlr3-runtime-java,
> > elasticsearch built successfully. (See the attached patch)
> 
> Any news about this from the maintainers? Is there any specific
> reason why this wasn't uploaded yet? (Asking because the
> elasticsearch package isn't part of testing/stretch yet and am
> wondering whether we might see stretch being released with the
> elasticsearch package included.)

Thank you for the patch!  I'll try take a look at elasticsearch this
weekend or next week.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#844683: libreoffice-common 5.3 preinst fails when removing missing directories

[Drew Parsons]

Package: libreoffice-common
Version: 1:5.3.0~alpha1-1
Severity: serious
Justification: Policy 6.2

The new libreoffice 5.3 in experimental fails to install.

libreoffice-common fails during preinst attempting to remove
directories which are not there:

Preparing to unpack .../libreoffice-common_1%3a5.3.0~alpha1-1_all.deb ...
dpkg-maintscript-helper: error: conffile 
'"/etc/bash_completion.d/libreoffice.sh"' is not an absolute path
dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_1%3a5.3.0~alpha1-1_all.deb 
(--unpack):
 subprocess new pre-installation script returned error exit status 1
rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or 
directory
rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
directory
rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
dpkg-maintscript-helper: error: conffile 
'"/etc/bash_completion.d/libreoffice.sh"' is not an absolute path
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libreoffice-common_1%3a5.3.0~alpha1-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


The chain of dependencies then prevents the other libreoffice 5.3
packages from completing their configuration.


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

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

Versions of packages libreoffice-common depends on:
ii  dpkg  1.18.15
iu  libreoffice-style-galaxy [libreoffice-style-default]  1:5.3.0~alpha1-1
iu  libreoffice-style-tango [libreoffice-style]   1:5.3.0~alpha1-1
ii  ure   5.3.0~alpha1-1

Versions of packages libreoffice-common recommends:
ii  fonts-liberation1:1.07.4-2
ii  libexttextcat-data  3.4.4-2
iu  python3-uno 1:5.3.0~alpha1-1

Versions of packages libreoffice-common suggests:
pn  libreoffice-style-breeze  
pn  libreoffice-style-hicontrast  
pn  libreoffice-style-oxygen  
pn  libreoffice-style-sifr
iu  libreoffice-style-tango   1:5.3.0~alpha1-1

Versions of packages python3-uno depends on:
ii  libc6 2.24-5
ii  libgcc1   1:6.2.0-13
ii  libpython3.5  3.5.2-7
iu  libreoffice-core  1:5.3.0~alpha1-1
ii  libstdc++66.2.0-13
ii  python3   3.5.1-4
ii  python3.5 3.5.2-7
pn  python3:any   
ii  uno-libs3 5.3.0~alpha1-1
ii  ure   5.3.0~alpha1-1

-- no debconf information

Processed: severity of 844486 is minor

[Debian Bug Tracking System]

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

> severity 844486 minor
Bug #844486 [src:wxwidgets3.0] wxwidgets3.0 should drop the ABI mismatch message
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Bug#840186: nwchem builds on amd64 with -march=native

[Apra, Edoardo]

The attached patch disables the gfortran flag -march=native.
Same patch can be found at the URL
http://www.nwchem-sw.org/images/Disable_march_native.patch.gz
--- nwchem-6.6/src/config/makefile.h	2016-11-17 22:29:09.794581240 +
+++ nwchem-6.6/src/config/makefile.h.orig	2016-11-17 22:26:29.497599135 +
@@ -1956,7 +1956,7 @@
   FOPTIONS +=  -ff2c -fno-second-underscore
 endif
 ifeq ($(GNU_GE_4_6),true) 
-  FOPTIONS +=  -mtune=native
+  FOPTIONS += -march=native -mtune=native
   FOPTIONS += -finline-functions
 else
 ifeq ($(_GOT3DNOW),Y) 

Bug#811576: patch is available upstream

[Hon Ching(Vicky) Lo]

Please rebase to tpm-tools 1.3.9 to pick up the patch.  

Thanks,
Vicky

Bug#828579: The patch is upstream

[Hon Ching(Vicky) Lo]

On Thu, 2016-11-17 at 14:18 -0500, Hon Ching(Vicky) Lo wrote:
> The patch that supports OpenSSL 1.1 (backward-compatible) is upstream:
> https://sourceforge.net/p/trousers/trousers/ci/05411ea68746acbaf4e69295be50b9a47cddb2fd/
> 
> 
> Vicky

The patch above is based off the latest code in Trousers-0.3.14.  Please
rebase to Trousers-0.3.14 to pick up the patch instead.  Thanks!

Vicky

Bug#828577: The patch is upstream

[Hon Ching(Vicky) Lo]

On Thu, 2016-11-17 at 16:29 -0500, Hon Ching(Vicky) Lo wrote:
> Hi
> 
> The patch is upstream:
> https://sourceforge.net/p/trousers/tpm-tools/ci/6fb8a3c5ad3bc6e62f6895a4fcf3540faa29b4f2/
> 
> 
> Thanks,
> Vicky

The patch above is based off the latest code in tpm-tools 1.3.9.  Please
rebase to tpm-tools 1.3.9 to pick up the patch instead.  Thanks!

Vicky

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Adrian Bunk]

On Thu, Nov 17, 2016 at 11:18:57PM +0100, Stefan Fritsch wrote:
> On Thursday, 17 November 2016 21:39:19 CET Kurt Roeckx wrote:
> > > That header was created for mod_ssl_ct which provides support for
> > > certificate  transparency. It's quite new and likely that nothing else
> > > uses the header. It would probably be acceptable to remove the dependency
> > > in apache2-dev on libssl-dev and add a caveat to the README.Debian. I
> > > could also not install the header, or put it into a separate new package
> > > that depends on libssl-dev.
> 
> > So can you confirm that the only reason for the libssl-dev
> > depedency is that file? 
> 
> Yes.

What does create the dependency in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828330#16
?

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844490: marked as done (FTBFS with boost1.62)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 22:22:18 +
with message-id 
and subject line Bug#844490: fixed in gyoto 1.1.1-3
has caused the Debian Bug report #844490,
regarding FTBFS with boost1.62
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.)


-- 
844490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gyoto
Version: 1.1.1-2+b1
Severity: serious
Justification: fails to build from source (but built successfully in the
past)

Dear BTS,

gyoto FTBFS with boost1.62 on several release architectures:
https://buildd.debian.org/status/package.php?p=gyoto

It looks like it was known before the upload of boost1.62 to unstable:
http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

The failure occurs in the test suite. Some debugging shows that the
culprit lies in lib/Screen.C, line 567. More precisely, the function
acos() overloaded for type boost::multiprecision::cpp_dec_float_100
sometimes never returns. It appears to be somewhat reproducible (I think
the test suite of gyoto fails always at the same point in its execution
on a given architecture, when it fails), but I was not able to isolate a
specific value of the argument that would hang acos().

The test suite can succeed if I decrease somewhat the number of digits,
e.g. using only 50 or even 90 decimal digits instead of 100. The build
failure occurs earlier if I use even more digits, so it looks like a
memory leak of some sort.

Several approaches could hide the problem under the carpet:
 - skipping the test suite on the affected architectures ;
 - decreasing the number of digits.

I'm very reluctant to do any of this because there, even if the test
suite goes through, there is no guarantee that the bug will not bite
users in the middle of a weeks-long simulation.

Besides, decreasing the number of digits means gyoto will loose in accuracy.

Looks like this needs to be fixed in boost.

Kind regards, Thibaut.
--- End Message ---
--- Begin Message ---
Source: gyoto
Source-Version: 1.1.1-3

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

Debian distribution maintenance software
pp.
Thibaut Paumard  (supplier of updated gyoto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 17 Nov 2016 22:29:08 +0100
Source: gyoto
Binary: gyoto gyoto-bin libgyoto5 gyoto-dbg libgyoto5-dev yorick-gyoto 
python-gyoto python3-gyoto gyoto-doc
Architecture: source amd64 all
Version: 1.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Thibaut Paumard 
Description:
 gyoto  - General relativistic geodesic integration and ray-tracing
 gyoto-bin  - General relativistic ray-tracing command-line interface
 gyoto-dbg  - debugging symbols for the Gyoto framework
 gyoto-doc  - documentation for the Gyoto library
 libgyoto5  - Gyoto framework main library an standard plug-in
 libgyoto5-dev - development files for libgyoto
 python-gyoto - General relativistic geodesic integration for the Python 2 
langua
 python3-gyoto - General relativistic geodesic integration for the Python 3 
langua
 yorick-gyoto - General relativistic geodesic integration for the Yorick 
language
Closes: 844490
Changes:
 gyoto (1.1.1-3) unstable; urgency=medium
 .
   * Bug fix: "FTBFS with boost1.62" (Closes: #844490).
Checksums-Sha1:
 1dd143d4b240ef1a3adc27f4ad158b96bd511fd5 2944 gyoto_1.1.1-3.dsc
 d83ead00e29561c2660cd48988bb66e85fd79261 10256 gyoto_1.1.1-3.debian.tar.xz
 a82b66c69bb184f10f288179bad9e5dfcac5e756 127568 gyoto-bin_1.1.1-3_amd64.deb
 36c98277dafe7bf5eee484d758b0ffd68fe3a5b7 12598178 gyoto-dbg_1.1.1-3_amd64.deb
 bbe845f16880402275f6a4cfba96f814a5925dbb 1264326 gyoto-doc_1.1.1-3_all.deb
 6a3136d9afbf80f940cca5e67dde33bab50ccaea 67772 gyoto_1.1.1-3_all.deb
 9a8cc6960b00dbe7e2f8f076938fa1b458fe410c 12274 gyoto_1.1.1-3_amd64.buildinfo
 67131df7c0358ddcf382a77f032c69114197d428 1068528 
libgyoto5-dev_1.1.1-3_amd64.deb
 ba822a4b3141995b83ca17e059bcf8d2f824e994 496512 libgyoto5_1.

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Stefan Fritsch]

On Thursday, 17 November 2016 21:39:19 CET Kurt Roeckx wrote:
> > That header was created for mod_ssl_ct which provides support for
> > certificate  transparency. It's quite new and likely that nothing else
> > uses the header. It would probably be acceptable to remove the dependency
> > in apache2-dev on libssl-dev and add a caveat to the README.Debian. I
> > could also not install the header, or put it into a separate new package
> > that depends on libssl-dev.

> So can you confirm that the only reason for the libssl-dev
> depedency is that file? 

Yes.

Processed: Re: Bug#844646: Could not install debian with debian-testing-i386-netinst.iso 2016-11-17

[Debian Bug Tracking System]

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

> forcemerge 844646 844644
Bug #844646 [debian-installer] Could not install debian with 
debian-testing-i386-netinst.iso 2016-11-17
Bug #844644 [debian-installer] debian-installer: debootstrap fails with error 
127: line 617: : Permission denied
Severity set to 'critical' from 'normal'
Marked as found in versions debian-installer/20161031.
Merged 844644 844646
> thanks
Stopping processing here.

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

Bug#828328: marked as done (gnupg-pkcs11-scd: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 22:03:57 +
with message-id 
and subject line Bug#828328: fixed in gnupg-pkcs11-scd 0.7.3-2
has caused the Debian Bug report #828328,
regarding gnupg-pkcs11-scd: FTBFS with openssl 1.1.0
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.)


-- 
828328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg-pkcs11-scd
Version: 0.7.3-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/gnupg-pkcs11-scd_0.7.3-1_amd64-20160529-1423

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: gnupg-pkcs11-scd
Source-Version: 0.7.3-2

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated gnupg-pkcs11-scd 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Nov 2016 18:07:31 +0100
Source: gnupg-pkcs11-scd
Binary: gnupg-pkcs11-scd gnupg-pkcs11-scd-dbg
Architecture: source amd64
Version: 0.7.3-2
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 gnupg-pkcs11-scd - GnuPG smart-card daemon with PKCS#11 support
 gnupg-pkcs11-scd-dbg - GnuPG smart-card daemon with PKCS#11 support (debug)
Closes: 761831 828328
Changes:
 gnupg-pkcs11-scd (0.7.3-2) unstable; urgency=medium
 .
   * New maintainer (Closes: #761831)
   * add openssl-1.1.0.patch (Closes: #828328)
   * debian/control: set dh version to >= 9
   * debian/control: bump standard to 3.9.8 (no changes)
Checksums-Sha1:
 45e116c171c963d40121261db14004893c6baf6a 2279 gnupg-pkcs11-scd_0.7.3-2.dsc
 2d7e35254df96b295eb2d970021c18f3470ea78a 150358 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 d55b13891a3d6729238fa370e0fc2bbdb3180f30 3824 
gnupg-pkcs11-scd_0.7.3-2.debian.tar.xz
 f48bb81f1197077f76fe812f20efde1228d07efe 56152 
gnupg-pkcs11-scd-dbg_0.7.3-2_amd64.deb
 d7de015782f90c889d8c73628245bc42c024ccc4 5096 
gnupg-pkcs11-scd_0.7.3-2_amd64.buildinfo
 10c409362f9289e492b582811eb0f863a6d20cea 26112 
gnupg-pkcs11-scd_0.7.3-2_amd64.deb
Checksums-Sha256:
 97d199367c064a5ede4263e87455e4267e00d017f94e30b92a4ea09bbc0feb2c 2279 
gnupg-pkcs11-scd_0.7.3-2.dsc
 04bd11d07b89b0cae40df14e698d35eb5c7067b6c62823dc75fc2ca3b196e338 150358 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 c8b15faccb2d69b59b051d4eefaa004fc731646573e25873357bebf39e423aad 3824 
gnupg-pkcs11-scd_0.7.3-2.debian.tar.xz
 bed6fe389a6409f32c6964b04f3bd56214d4d31b25f5c3362951b7389a168b91 56152 
gnupg-pkcs11-scd-dbg_0.7.3-2_amd64.deb
 40eab5b240ea2d6ed88cfbeef9012e4188a02f5bfce1b987b1c656675731a805 5096 
gnupg-pkcs11-scd_0.7.3-2_amd64.buildinfo
 3d6ae768856dc31229057c44db61f14bc32ede29949165b3721531288efa91a5 26112 
gnupg-pkcs11-scd_0.7.3-2_amd64.deb
Files:
 899d36e04797bfa1e9b5e5fe0fb0744c 2279 utils optional 
gnupg-pkcs11-scd_0.7.3-2.dsc
 a91680d73f814bd3a16fa4a72e0ee998 150358 utils optional 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 b073ffc4bbf5aa0aec355d536465932a 3824 utils optional 
gnupg-pkcs11-scd_0.7.3-2.debian.tar.xz
 16cdb7709e03f5f594a8525f0a909c8a 56152 debug extra 
gnupg-pkcs11-scd-dbg_0.7.3-2_amd64.deb
 0ff12106cbb27e8aa5759d52d5ee3a6d 5096 utils optional 
gnupg-pkcs11-scd_0.7.3-2_amd64.buildinfo
 dc82d81ed4826c476a2d13e59d4ace0c 26112 utils optional 
gnupg-pkcs11-scd_0.7.3-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u

Processed (with 1 error): Re: Bug#844646: Could not install debian with debian-testing-i386-netinst.iso 2016-11-17

[Debian Bug Tracking System]

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

> merge 844644 844646
Bug #844644 [debian-installer] debian-installer: debootstrap fails with error 
127: line 617: : Permission denied
Unable to merge bugs because:
severity of #844646 is 'critical' not 'normal'
Failed to merge 844644: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#844664: salt-formula-kubernetes: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: OPENSSL_no_config

[Chris Lamb]

Source: salt-formula-kubernetes
Version: 2016.8.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

salt-formula-kubernetes fails to build from source in unstable/amd64:

  […]

 dh_auto_test
make -j1 test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161117225224.ZcUOpQDBud.db.salt-formula-kubernetes/salt-formula-kubernetes-2016.8.3'
  [ ! -d tests ] || (cd tests; ./run_tests.sh)
  /usr/bin/salt-call
  Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in 
  salt_call()
File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 346, in 
salt_call
  import salt.cli.call
File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 6, in 

  from salt.utils import parsers
File "/usr/lib/python2.7/dist-packages/salt/utils/parsers.py", line 28, in 

  import salt.config as config
File "/usr/lib/python2.7/dist-packages/salt/config/__init__.py", line 41, 
in 
  import salt.utils.sdb
File "/usr/lib/python2.7/dist-packages/salt/utils/sdb.py", line 9, in 

  import salt.loader
File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 30, in 
  import salt.utils.event
File "/usr/lib/python2.7/dist-packages/salt/utils/event.py", line 72, in 

  import salt.payload
File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 

  import salt.crypt
File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
  import salt.utils.rsax931
File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 

  libcrypto = _init_libcrypto()
File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
_init_libcrypto
  libcrypto.OPENSSL_no_config()
File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
  func = self.__getitem__(name)
File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
  func = self._FuncPtr((name_or_ordinal, self))
  AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
OPENSSL_no_config
  [ERROR] Execution of kubernetes.master_cluster failed
  [ERROR] Execution failed
  Makefile:22: recipe for target 'test' failed
  make[1]: *** [test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161117225224.ZcUOpQDBud.db.salt-formula-kubernetes/salt-formula-kubernetes-2016.8.3'
  dh_auto_test: make -j1 test returned exit code 2
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


salt-formula-kubernetes.2016.8.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844663: salt-formula-swift: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: OPENSSL_no_config

[Chris Lamb]

Source: salt-formula-swift
Version: 2016.8.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

salt-formula-swift fails to build from source in unstable/amd64, probably
due to OpenSSL 1.10.1:

  […]

 dh_auto_test
make -j1 test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161117225259.5K4PtsdlgI.db.salt-formula-swift/salt-formula-swift-2016.8.3'
  [ ! -d tests ] || (cd tests; ./run_tests.sh)
  /usr/bin/salt-call
  Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in 
  salt_call()
File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 346, in 
salt_call
  import salt.cli.call
File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 6, in 

  from salt.utils import parsers
File "/usr/lib/python2.7/dist-packages/salt/utils/parsers.py", line 28, in 

  import salt.config as config
File "/usr/lib/python2.7/dist-packages/salt/config/__init__.py", line 41, 
in 
  import salt.utils.sdb
File "/usr/lib/python2.7/dist-packages/salt/utils/sdb.py", line 9, in 

  import salt.loader
File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 30, in 
  import salt.utils.event
File "/usr/lib/python2.7/dist-packages/salt/utils/event.py", line 72, in 

  import salt.payload
File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 17, in 

  import salt.crypt
File "/usr/lib/python2.7/dist-packages/salt/crypt.py", line 42, in 
  import salt.utils.rsax931
File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 69, in 

  libcrypto = _init_libcrypto()
File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
_init_libcrypto
  libcrypto.OPENSSL_no_config()
File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
  func = self.__getitem__(name)
File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
  func = self._FuncPtr((name_or_ordinal, self))
  AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
OPENSSL_no_config
  [ERROR] Execution of swift.proxy_cluster failed
  [ERROR] Execution failed
  Makefile:22: recipe for target 'test' failed
  make[1]: *** [test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161117225259.5K4PtsdlgI.db.salt-formula-swift/salt-formula-swift-2016.8.3'
  dh_auto_test: make -j1 test returned exit code 2
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


salt-formula-swift.2016.8.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844661: golang-github-googleapis-gax-go: FTBFS: dial.go:7:2: cannot find package "golang.org/x/oauth2/google"

[Chris Lamb]

Source: golang-github-googleapis-gax-go
Version: 0.0~git20160714.0.8b0741b-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

golang-github-googleapis-gax-go fails to build from source in unstable/amd64:

  […]

go install -v -p 1 github.com/googleapis/gax-go
  src/github.com/googleapis/gax-go/dial.go:7:2: cannot find package 
"golang.org/x/oauth2/google" in any of:
/usr/lib/go-1.7/src/golang.org/x/oauth2/google (from $GOROOT)

/home/lamby/temp/cdt.20161117225201.u3dpYXGu8a.db.golang-github-googleapis-gax-go/golang-github-googleapis-gax-go-0.0~git20160714.0.8b0741b/obj-x86_64-linux-gnu/src/golang.org/x/oauth2/google
 (from $GOPATH)
  dh_auto_build: go install -v -p 1 github.com/googleapis/gax-go returned exit 
code 1
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 1

  […]

The full build log is attached.


Regards,

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


golang-github-googleapis-gax-go.0.0~git20160714.0.8b0741b-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#828577: The patch is upstream

[Hon Ching(Vicky) Lo]

Hi

The patch is upstream:
https://sourceforge.net/p/trousers/tpm-tools/ci/6fb8a3c5ad3bc6e62f6895a4fcf3540faa29b4f2/


Thanks,
Vicky

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

[Luca Boccassi]

On Wed, 16 Nov 2016 08:55:47 +0100 picca  wrote:
> Source: zeromq3
> Severity: important
> 
> Dear Maintainer,
> 
> It seems that zeromq 4.2.0 brakes the tango package.
> this is why I fill an important bug in orer to block migration testing.
> 
> You can have a look here
> 
> http://lists.zeromq.org/pipermail/zeromq-dev/2016-November/031093.html
> 
> thanks
> 
> Fred

Hi Fred,

This is very unfortunate, but as explained on the mailing list, this
behaviour was an unintentional internal side effect. I didn't quite
realise it was there, and so most other devs.

In general we do our best to keep track of our public API/ABI, and
lately a large effort has gone into making the management of these
better. Recently for example an ABI-breaking bugfix was fixed up to be
ABI-compatible. But when it comes to internal, undocumented
implementation details I hope you realise it's much, much harder.

I understand this is not much consolation when it means some work for
application/clients maintainers/developers, and I am sorry for the
trouble it could cause, but I do think the right thing in this specific
case is to avoid relying on what essentially is undefined behaviour, if
possible.

How much work would it be to change tango to avoid relying on aligned
internal recv buffers?

The only alternative would be for the maintainer to revert all or part
of this pull request and any subsequent fixes:

https://github.com/zeromq/libzmq/pull/1466

But I would recommend against it.

Of course a pull request that would restore the aligned side effect
while maintaining the new decoder implementation with one less memcopy
would be very welcome!

Kind regards,
Luca Boccassi


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

Bug#844660: mkvtoolnix FTBFS with QT 5.7

[Adrian Bunk]

Source: mkvtoolnix
Version: 9.5.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=mkvtoolnix&suite=sid

...
 CXX src/info/qt_ui.cpp
In file included from src/common/common_pch.h:4:0:
src/info/ui/mainwindow.h: In member function 'void 
Ui_main_window::retranslateUi(QMainWindow*)':
src/common/common.h:81:45: error: 'pgettext' was not declared in this scope
 #  define PY(context, s) pgettext(context, s)
 ^
src/common/qt.h:28:32: note: in expansion of macro 'PY'
 #define QPTR(s, context) to_qs(PY(context, s))
^~
src/info/ui/mainwindow.h:106:37: note: in expansion of macro 'QPTR'
 main_window->setWindowTitle(QPTR("mkvInfo", Q_NULLPTR));
 ^
compilation terminated due to -Wfatal-errors.
debian/rules:16: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:13: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#837566: marked as done (mjpegtools: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 21:09:32 +
with message-id 
and subject line Bug#837566: fixed in mjpegtools 1:2.1.0+debian-5
has caused the Debian Bug report #837566,
regarding mjpegtools: FTBFS with bindnow and PIE enabled
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.)


-- 
837566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mjpegtools
Version: 2.1.0+debian-4
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I../utils -Wdate-time
-D_FORTIFY_SOURCE=2 -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -c -o yuvscaler-yuvscaler_resample.o `test -f
'yuvscaler_resample.c' || echo './'`yuvscaler_resample.c
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I../utils -Wdate-time
-D_FORTIFY_SOURCE=2 -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -c -o yuvscaler-yuvscaler_bicubic.o `test -f
'yuvscaler_bicubic.c' || echo './'`yuvscaler_bicubic.c
/bin/bash ../libtool  --tag=CC   --mode=link gcc -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused  -Wl,-z,relro -Wl,-z,now -o yuvscaler yuvscaler-yuvscaler.o
yuvscaler-yuvscaler_resample.o yuvscaler-yuvscaler_bicubic.o
../utils/libmjpegutils.la  -lm  -lm libtool: link: gcc -fno-PIC -g -O2
-fdebug-prefix-map=/<>/mjpegtools-2.1.0+debian=.
-fstack-protector-strong -Wformat -Werror=format-security -pthread -Wall
-Wunused -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/yuvscaler
yuvscaler-yuvscaler.o yuvscaler-yuvscaler_resample.o
yuvscaler-yuvscaler_bicubic.o  ../utils/.libs/libmjpegutils.so -lm -pthread
/usr/bin/ld: yuvscaler-yuvscaler.o: relocation R_X86_64_32 against
`.rodata.str1.8' can not be used when making a shared object; recompile
with -fPIC
/usr/bin/ld: yuvscaler-yuvscaler_resample.o: relocation R_X86_64_32
against `.rodata.str1.8' can not be used when making a shared object;
recompile with -fPIC
/usr/bin/ld: yuvscaler-yuvscaler_bicubic.o: relocation R_X86_64_32
against `.rodata.str1.8' can not be used when making a shared object;
recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:441: recipe for target 'yuvscaler' failed
make[3]: *** [yuvscaler] Error 1
make[3]: Leaving directory '/<>/mjpegtools-2.1.0+debian/yuvscaler'
Makefile:572: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/mjpegtools_2.1.0+debian-4_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: mjpegtools
Source-Version: 1:2.1.0+debian-5

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated mjpegtools 
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: Wed, 16 Nov 2016 21:50:46 +0100
Source: mjpegtools
Binary: mjpegtools mjpegtools-gtk libmjpegtools-dev liblavfile-2.1-0 
liblavjpeg-2.1-0 liblavplay-2.1-0 libmjpegutils-2.1-0 libmpeg2encpp-2.1-0 
libmplex2-2.1-0
Architecture: source
Version: 1:2.1.0+debian-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 liblavfile-2.1-0

Bug#844546: marked as done (teeworlds: possible remote code execution on the client)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 21:10:46 +
with message-id 
and subject line Bug#844546: fixed in teeworlds 0.6.4+dfsg-1
has caused the Debian Bug report #844546,
regarding teeworlds: possible remote code execution on the client
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.)


-- 
844546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: teeworlds
Version: 0.6.1+dfsg-1
Severity: grave
Tags: security
Justification: user security hole

teeworlds upstream has released version 0.6.4.

https://www.teeworlds.com/?page=news&id=12086 says

> the security vulnerability is worse, attacker controlled memory-writes and
> possibly arbitrary code execution on the client, abusable by any server the
> client joins

The upstream fix:
https://github.com/teeworlds/teeworlds/commit/ff254722a2683867fcb3e67569ffd36226c4bc62

There doesn't seem to be a CVE assigned to this vulnerability.

Felix
--- End Message ---
--- Begin Message ---
Source: teeworlds
Source-Version: 0.6.4+dfsg-1

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated teeworlds package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Nov 2016 20:57:15 +0100
Source: teeworlds
Binary: teeworlds teeworlds-server teeworlds-data
Architecture: source
Version: 0.6.4+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Debian Games Team 
Changed-By: Felix Geyer 
Description:
 teeworlds  - online multi-player platform 2D shooter
 teeworlds-data - data for Teeworlds; an online multi-player platform 2D shooter
 teeworlds-server - server for Teeworlds; an online multi-player platform 2D 
shooter
Closes: 844546
Changes:
 teeworlds (0.6.4+dfsg-1) unstable; urgency=high
 .
   * New upstream release.
 - Fixes possible remote code execution on the client. (Closes: #844546)
   * Refresh new-wavpack.patch
   * Drop patches that have been fixed upstream:
 - fix-gcc6-rename-round.patch
 - fix-gcc6-var-types.patch
 - reset-nethash.patch
Checksums-Sha1:
 d3643df6cedba2b5e02c94b59a8d2c3c5f808950 2249 teeworlds_0.6.4+dfsg-1.dsc
 485599e6943352cae713782c2c9dfe48d04f1654 7046740 
teeworlds_0.6.4+dfsg.orig.tar.gz
 09148a5c0d0c906ed4baabf2e32d0e0c4b655857 8196 
teeworlds_0.6.4+dfsg-1.debian.tar.xz
Checksums-Sha256:
 dcdc77474a44eae1b67268495697d67eaf24f87e575f9fd48a8dc2360d644907 2249 
teeworlds_0.6.4+dfsg-1.dsc
 62286ee7c786dc565f42864ca23dd02a6b4ba7b52ed54014145ec9724a2df045 7046740 
teeworlds_0.6.4+dfsg.orig.tar.gz
 e16674531f71e67f00810f1f2c60fecac67f1e30b27b7729cd5a30fbc904145a 8196 
teeworlds_0.6.4+dfsg-1.debian.tar.xz
Files:
 c176510c4ca619ed9bedb45488ffaf7e 2249 games optional teeworlds_0.6.4+dfsg-1.dsc
 d24bd8b9b68a403adcdd6b2cfb485c13 7046740 games optional 
teeworlds_0.6.4+dfsg.orig.tar.gz
 984b4fcb8f6de3daa849f6d246c5 8196 games optional 
teeworlds_0.6.4+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYLgv0AAoJEP4ixv2DE11FVHIQAJvbgTB7VE5cYkk6TU8dlJBM
/xmpZA78pxWRkNthBbDnu1MEFZau1SyhjCxdvzCZxlwMXhLXoQ00ywkrsdM4AeIl
QkVBxzrD6dYFe7LgoogMbWfFipsrkq+FvrubcR3gBdvMB3dk+3unvh5M0+J6cPIh
uKIw8MaHcRSYoIxQ6Aa3DHIAm9utYK4xZ5vgFhA7qbDOfYXKTkE7WLqUESOoVGb0
1K9j5FnC6GvONIDQtssjyVJnKswNkKfJnQ9acjIb3wN4L6tI2yxbC92mxUNgIWsk
xzQns/xaqq/3rQToGd8xT3x3qq92MMij9C42GGF8cvHjOsiQ3nK30ermbSG/nacR
VCw2S5LszI6HE3cLfjjbHpAxWIkHSKUVVtLiVw/xtq2S4zl1d1yu28S1UQCixuNc
e5Q6OKmWsGgyLGKB55z+msF1r99//Lyvxplxs2cMDYXT9Co5AnCLVutmAArvwehR
VMlfVn2f+J+y6GYuEzqfEcB+cEqYxJZrPzkV1M2I45GrfHC4Y5xTRaSQDo9IHAyv
aDCxWyWU3wTijGwl55HGn5txpTmMwDCn3/ul/t4nOv0XzvgmntrfNctmqy+p5Ruq
9Da8cPC8FypPjdUasm8nGNWz+Tx4BXcemSrU6HknboFo1KgVhyCdkDuvq32smEjZ
+5uMFPMv57zj3Hxnhzv8
=Zo1U
-END PGP SIGNATURE End Message ---

Bug#828357: isync: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch fixed-upstream

On 2016-07-24 12:01:29 [+0200], Oswald Buddenhagen wrote:
> fixed in git on isync_1_2_branch.

Upstream fixed it

https://sourceforge.net/p/isync/isync/ci/41308e481466b91813f6765a0c92ad83fd9d1ab2/
In their 1.2 release branch which is available in experimental.
Alessandro: do you plan to upload the fixed 2.1 branch any time soon or
do you need something fixed for the 1.2 branch?

Sebastian
>From 41308e481466b91813f6765a0c92ad83fd9d1ab2 Mon Sep 17 00:00:00 2001
From: Oswald Buddenhagen 
Date: Sun, 24 Jul 2016 11:58:57 +0200
Subject: [PATCH] fix build with openssl 1.1

they finally made their structs opaque, and provided proper getters.
---
 src/socket.c | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/src/socket.c b/src/socket.c
index 94d0e7fba95f..3736fd5210b7 100644
--- a/src/socket.c
+++ b/src/socket.c
@@ -40,6 +40,10 @@
 # include 
 # include 
 # include 
+# if OPENSSL_VERSION_NUMBER < 0x1010L
+#  define X509_OBJECT_get0_X509(o) ((o)->data.x509)
+#  define X509_STORE_get0_objects(o) ((o)->objs)
+# endif
 #endif
 
 enum {
@@ -171,7 +175,7 @@ verify_cert_host( const server_conf_t *conf, conn_t *sock )
 
 	trusted = (STACK_OF(X509_OBJECT) *)sock->conf->trusted_certs;
 	for (i = 0; i < sk_X509_OBJECT_num( trusted ); i++) {
-		if (!X509_cmp( cert, sk_X509_OBJECT_value( trusted, i )->data.x509 ))
+		if (!X509_cmp( cert, X509_OBJECT_get0_X509( sk_X509_OBJECT_value( trusted, i ) ) ))
 			return 0;
 	}
 
@@ -222,7 +226,7 @@ init_ssl_ctx( const server_conf_t *conf )
 		   conf->cert_file, ERR_error_string( ERR_get_error(), 0 ) );
 		return 0;
 	}
-	mconf->trusted_certs = (_STACK *)sk_X509_OBJECT_dup( SSL_CTX_get_cert_store( mconf->SSLContext )->objs );
+	mconf->trusted_certs = (_STACK *)sk_X509_OBJECT_dup( X509_STORE_get0_objects( SSL_CTX_get_cert_store( mconf->SSLContext ) ) );
 	if (mconf->system_certs && !SSL_CTX_set_default_verify_paths( mconf->SSLContext ))
 		warn( "Warning: Unable to load default certificate files: %s\n",
 		  ERR_error_string( ERR_get_error(), 0 ) );
-- 
2.10.2

Processed: Re: Bug#828357: isync: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #828357 [src:isync] isync: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.

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

Bug#844617: g++-mingw-w64: C++ linking fails with cannot find -latomic.

[Steven Gawroriski]

On Thu, 17 Nov 2016 21:04:49 +0100
Stephen Kitt  wrote:

> Hi Steven,
> 
> On Thu, 17 Nov 2016 11:20:59 -0500, Steven Gawroriski
>  wrote:
> > During the linking stage of even the most simplest source code
> > (just a main function), the C++ linking fails because it cannot
> > find `-latomic`. This effectively makes the C++ compiler useless
> > because it cannot link any binaries.  
> 
> Could you try on another architecture? I can link C++ programs on all
> the architectures I have easy access to (amd64, i386, armhf, arm64)
> and the resulting programs run correctly on Windows.
> 
> Thanks,
> 
> Stephen

Hello,

I do not have another architecture running sid. However, it appears
that the compiler is configured with `--disable-libatomic`, if this
makes a difference.

Using built-in specs.
COLLECT_GCC=i686-w64-mingw32-g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-w64-mingw32/6.1-win32/lto-wrapper
Target: i686-w64-mingw32
Configured with: ../../src/configure --build=powerpc-linux-gnu
--prefix=/usr --includedir='/usr/include' --mandir='/usr/share/man'
--infodir='/usr/share/info' --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir='/usr/lib/powerpc-linux-gnu'
--libexecdir='/usr/lib/powerpc-linux-gnu' --disable-maintainer-mode
--disable-dependency-tracking --prefix=/usr --enable-shared
--enable-static --disable-multilib --with-system-zlib
--libexecdir=/usr/lib --without-included-gettext --libdir=/usr/lib
--enable-libstdcxx-time=yes --with-tune=generic
--enable-version-specific-runtime-libs --enable-fully-dynamic-string
--enable-libgomp --enable-languages=c,c++,fortran,objc,obj-c++
--enable-lto --with-plugin-ld --enable-threads=win32
--program-suffix=-win32 --program-prefix=i686-w64-mingw32-
--target=i686-w64-mingw32 --with-as=/usr/bin/i686-w64-mingw32-as
--with-ld=/usr/bin/i686-w64-mingw32-ld --disable-libatomic
Thread model: win32
gcc version 6.1.1 20160815 (GCC)

Thanks.


pgpurJxzhIlEA.pgp
Description: OpenPGP digital signature

Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-11-16 12:14:43 [+0100], Filip Pytloun wrote:
> To reproduce the issue simply install salt-master and run salt-call:
> 
> apt-get install salt-master
> salt-call
> 
> Following exception will occur:
> 
> Traceback (most recent call last):
>   File "/usr/bin/salt-call", line 11, in 
> salt_call()
…
>   File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", line 63, in 
> _init_libcrypto
> libcrypto.OPENSSL_no_config()
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in __getattr__
> func = self.__getitem__(name)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: /lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
> OPENSSL_no_config

the problem is that salt/rsax931.py loads the library manually and
expects certain symbols which are no longer available in OpenSSL 1.1.0.
And it loads the first libcrypto it finds plus has no dependency on
openssl.

Sebastian
>From 67676f782796071a793ec1908de50c7b86e9fbee Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Thu, 17 Nov 2016 20:43:04 +
Subject: [PATCH] load libcrypto.1.0.2 and not libcrypto.1.1.0

Signed-off-by: Sebastian Andrzej Siewior 
---
 debian/control| 1 +
 salt/utils/rsax931.py | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 5947de1336fb..b60ca31b52b2 100644
--- a/debian/control
+++ b/debian/control
@@ -31,6 +31,7 @@ Depends: python-apt,
  python-requests (>= 1.0.0),
  python-tornado (>= 4.2),
  python-yaml,
+ libssl1.0.2,
  ${misc:Depends},
  ${python:Depends}
 Recommends: lsb-release, python-croniter
diff --git a/salt/utils/rsax931.py b/salt/utils/rsax931.py
index 9eb1f4a1faf0..2d73cc2428ed 100644
--- a/salt/utils/rsax931.py
+++ b/salt/utils/rsax931.py
@@ -28,7 +28,8 @@ from ctypes.util import find_library
 os.path.dirname(sys.executable),
 'libcrypto.so*'))[0])
 else:
-lib = find_library('crypto')
+# We need to load the lib from 1.0.2 and not what might come first
+lib = "libcrypto.so.1.0.2"
 if not lib and salt.utils.is_smartos():
 # smartos does not have libraries in std location
 lib = glob.glob(os.path.join(
-- 
2.10.2

Processed: Re: Bug#844503: Acknowledgement (salt-call fails with libcrypto.so.1.1: undefined symbol: OPENSSL_no_config)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #844503 [salt] salt-call fails with libcrypto.so.1.1: undefined symbol: 
OPENSSL_no_config
Added tag(s) patch.

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

Processed: bug 842753 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=118824

[Debian Bug Tracking System]

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

> forwarded 842753 https://rt.cpan.org/Ticket/Display.html?id=118824
Bug #842753 [libnet-sip-perl] FTBFS: test failures
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=118824'.
> thanks
Stopping processing here.

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

Bug#844160: Bug#828236: [Pkg-openssl-devel] Bug#844160: openssl 1.1 and apache2

[Kurt Roeckx]

On Wed, Nov 16, 2016 at 11:05:13PM +0100, Stefan Fritsch wrote:
> Hi,
> 
> [I have trimmed the cc list a bit]
> 
> On Wednesday, 16 November 2016 20:36:49 CET Kurt Roeckx wrote:
> > On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> > > Stefan Fritsch  writes:
> > > > I must admit that I did not think of php when doing that change, sorry.
> > > > 
> > > > On the other hand, shibboleth-sp2 also build-depends on apache2-dev and
> > > > there have been some indications that shibboleth won't be switching to
> > > > openssl 1.1 for stretch. See
> > > > https://lists.debian.org/debian-release/2016/11/msg00024.html> 
> > > It turns out that Shibboleth will be okay if Apache goes to 1.1.  The
> > > Shibboleth code that goes into Apache is isolated from the OpenSSL use
> > > inside Shibboleth, so we can keep building Shibboleth against 1.0 and
> > > Apache can go to 1.1 and all the pieces are happy.  (The OpenSSL work is
> > > done in a separate daemon, shibd, that the Apache module talks to.)
> > 
> > So I looked at apache2-dev to see why it depends on libssl-dev.
> > The only thing I can find is that mod_ssl_openssl.h provides some
> > hooks, and you actually get SSL_CTX * and SSL * in there. But
> > nothing in Debian seems to include that file.
> 
> That header was created for mod_ssl_ct which provides support for certificate 
> transparency. It's quite new and likely that nothing else uses the header. It 
> would probably be acceptable to remove the dependency in apache2-dev on 
> libssl-dev and add a caveat to the README.Debian. I could also not install 
> the 
> header, or put it into a separate new package that depends on libssl-dev. 

So can you confirm that the only reason for the libssl-dev
depedency is that file? 


Kurt

Processed: Lowering severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841250 {Done: Mathieu Parent } [src:php-facedetect] 
php-facedetect: FTBFS: error with opencv 3.1
Severity set to 'important' from 'serious'

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

Bug#841250: Lowering severity

[Mathieu Parent]

Control: severity -1 important

Lowering severity as opencv 3.1 is still in experimental and
transition freeze has already happened.

Regards

-- 
Mathieu

Processed: bug 844538 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=118823

[Debian Bug Tracking System]

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

> forwarded 844538 https://rt.cpan.org/Ticket/Display.html?id=118823
Bug #844538 [src:libdbd-mysql-perl] libdbd-mysql-perl: FTBFS on some 
architectures
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Ticket/Display.html?id=118823'.
> thanks
Stopping processing here.

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

Processed: Correct syntax for the block

[Debian Bug Tracking System]

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

> block 844654 by 841704
Bug #844654 [src:berkshelf] berkshelf FTBFS in stretch due to missing 
berkshelf-api
844654 was not blocked by any bugs.
844654 was not blocking any bugs.
Added blocking bug(s) of 844654: 841704
> thanks
Stopping processing here.

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

Bug#844617: g++-mingw-w64: C++ linking fails with cannot find -latomic.

[Stephen Kitt]

Hi Steven,

On Thu, 17 Nov 2016 11:20:59 -0500, Steven Gawroriski
 wrote:
> During the linking stage of even the most simplest source code (just a
> main function), the C++ linking fails because it cannot find `-latomic`.
> This effectively makes the C++ compiler useless because it cannot link
> any binaries.

Could you try on another architecture? I can link C++ programs on all the
architectures I have easy access to (amd64, i386, armhf, arm64) and the
resulting programs run correctly on Windows.

Thanks,

Stephen


pgpi7ACZGlU3f.pgp
Description: OpenPGP digital signature

Bug#844654: berkshelf FTBFS in stretch due to missing berkshelf-api

[Adrian Bunk]

Source: berkshelf
Version: 4.3.5-1
Severity: serious
Tags: stretch
Control: block -1 by #841704

berkshelf build-depends on berkshelf-api, which is not in testing
due to #841704

Processed: Part of the OpenSSL transition

[Debian Bug Tracking System]

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

> block 827061 by 844503
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828479 828610 829452 828294 828546 828543 828421 828458 
828082 828370 828573 828364 828422 828393 828601 828286 828369 828510 828423 
828564 822380 828303 828465 828318 835585 828332 828381 828372 828620 828307 
828319 828432 828434 828367 828315 828284 828334 828444 828584 828530 828366 
828536 828529 828478 828272 828271 828454 828325 828314 828228 828400 828387 
828608 828489 828304 828523 828587 828514 828237 828576 828555 828231 828330 
828538 827076 828469 835797 828585 828392 828310 828331 828266 828428 828476 
828599 844254 844311 828363 828265 828324 828506 828267 828496 828415 828356 
828605 828411 828519 835793 828548 828520 828395 828417 828554 828260 828384 
828572 828470 828442 828361 828139 828567 828355 828532 828440 828255 828326 
828466 828365 828396 828547 828461 828574 828274 828280 828406 828341 828451 
828241 828435 828407 828614 828497 828390 828359 828540 828416 828426 828439 
828448 828328 828379 828512 828347 828246 828528 828582 828277 828486 828563 
828597 828460 828268 828617 828545 828446 828450 828386 828380 828577 828351 
828468 828521 828578 835789 828269 828251 828397 828373 828245 828405 828526 
844347 828611 837960 828566 844301 828604 828480 828424 828598 828462 828553 
828340 828342 828591 828232 835549 828425 828580 828494 828275 828583 828235 
828441 828350 828398 828606 828413 828492 828518 828313 828501 828485 828262 
828376 828522 828593 828083 828335 828561 828445 835786 835790 828513 844345 
828317 828560 828394 828282 828571 828503 828516 828535 828233 828404 844534 
828259 828455 828579 828603 844271 828306 828410 828487 828240 808669 828401 
835811 828505 828258 828336 828308 828298 828539 828568 828551 828290 828230 
828437 828254 828581 828276 828375 828443 828544 828295 835799 828452 828368 
843988 828602 828333 828348 828320 828500 828281 828418 828575 835794 835800 
828385 814600 828490 828388 828542 828249 828565 828296 828472 828471 828481 
828288 828419 828412 841635 828616 828338 828234 828344 828239 828263 828343 
828243 828248 828507 828484 828558 828508 809271 828420 828493 828250 828436 
828323 828511 828609 828309 828499 828453 828552 828362 828556 828592 828559 
828285 828339 828289 828524 828447 828619 828586 828509 828615 828287 828618 
828502 828488 828305 828256 828142 828389 828596 828349 843532 828312 828383 
828316 835798 828495 828474 828229 835796 828352 828541 828607 828391 828431 
828588 828433 828283 828589 828430 828562 828464 828273 836419 828353 828504 
828427 828311 828482 828297 828374 828414 828291 828491 828399 828257 828242 
828515 828438 828329 828594 828534 828302 828570 828357 828301 828459 828293 
828449 828371 828557 828346 828327 828525 828238 828612 828477 828244 828337 
828457 828402 828127 828409 828261 828360 828378 828483 828467 829465 828278 
828590 828377 828517 828463 828569 828600 828403 835804 828527 828473 828321 
828252 828382 828292 828549 828264 828595 828537 828358 828498 828253 828613 
828550 828531 828270 828429 835785 828533 828345 828279 828322 828354 828300 
827068 828456
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 844503
> thanks
Stopping processing here.

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

Bug#844653: stylish FTBFS in testing: firefox-dev won't be in stretch

[Adrian Bunk]

Source: stylish
Version: 2.0.3-1
Severity: serious

firefox-dev is not in stretch, and it is not planned that it
ever will be (see #817954).

firefox-esr-dev might be the alternative, but the Mozilla maintainers
(Cc'ed on this bug) should be able to give a more definite answer
on that.

Bug#844648: libtesseract-data: overwrites files in libtesseract3, needs Breaks/Replaces

[Dmitry Shachnev]

Package: libtesseract-data
Version: 3.04.01-4.1
Severity: serious

The recently introduced libtesseract-data package fails to install, as it
overwrites files from previous version of libtesseract3 package:

dpkg: error processing .../06-libtesseract-data_3.04.01-4.1_all.deb (--unpack):
 trying to overwrite '/usr/share/tesseract-ocr/tessdata/configs/ambigs.train',
 which is also in package libtesseract3 3.04.01-4+b1

Looks like it needs Breaks/Replaces on libtesseract3 (<< 3.04.01-4.1~).

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#844647: validator.js FTBFS: build dependency node-contextify was removed

[Adrian Bunk]

Source: validator.js
Version: 4.7.1+dfsg1-1
Severity: serious

validator.js build-depends on node-contextify, which was removed in
https://bugs.debian.org/842022

Bug#841247: [Calendarserver-maintainers] Bug#841247: calypso: UnicodeDecodeError when importing an .ics

[Guido Günther]

On Thu, Nov 17, 2016 at 01:20:59PM +0100, Mathias Behrle wrote:
> * Guido Günther: " Re: [Calendarserver-maintainers] Bug#841247: calypso:
>   UnicodeDecodeError when importing an .ics" (Wed, 2 Nov 2016 21:30:21 +0100):
> 
> Hi Guido,
> 
> > Hi Mathias,
> > 
> > On Wed, Nov 02, 2016 at 01:14:02PM +0100, Mathias Behrle wrote:
> > > control: affects -1 + tryton-modules-calendar
> > > tryton-modules-calendar-classification tryton-modules-calendar-scheduling
> > > tryton-modules-calendar-todo tryton-modules-party-vcarddav tryton-meta 
> > > > From: Guido Günther 
> > > > To: Jens Reyer , 841...@bugs.debian.org
> > > > Subject: Re: Bug#841247: calypso: UnicodeDecodeError when importing
> > > > an .ics Date: Sun, 23 Oct 2016 12:28:37 +0200  
> > >  
> > > 
> > > Hi Guido,
> > >   
> > > > The unicode handling for python 2.7 got broken in upstream commit
> > > > 
> > > > 
> > > > https://github.com/eventable/vobject/commit/b3f9bbcf4cf222f0dda3ac29f96364c5d7ab5f16
> > > > 
> > > > Let's see if upstream cares at all. If not we should rather drop the
> > > > python2.7 version for stretch.  
> > > 
> > > There are currently 6 Tryton modules affected as rdepends of 
> > > python-vobject.
> > > There are still some bits in the Tryton framework lacking Python3 support,
> > > so it is currently not possible to switch the whole Tryton stuff to 
> > > Python3
> > > (and I suppose this won't be the case for stretch). Dropping the Python2
> > > version of python-vobject would seriously hurt those Tryton modules. So
> > > please let's find a way to keep the Python2 version in the archive (for
> > > stretch).  
> > 
> > It breaks calyso as well which I'd rather see in the archive than
> > removed.
> > 
> > The bug is fixable. Someone needs to sit down and cook a patch. I have
> > it on the TODO list but work is piling up at the moment - but I hope to
> > get it done til the end of the year.
> 
> While I am currently not able to assist in making a patch I had a quite
> intensive test with a complete Tryton calendar setup using vobject 0.9.3 under
> Python2. It is working like a charm. So it seems the Tryton modules are
> not *directly* affected by this bug.
> 
> I would want to elaborate the different measures to take now (time is running
> away and the autoremoval is scheduled in 27 days).
> 
> For me the severity of this bug is definitely important, not grave. I think we
> should downgrade the severity immediately. Would you agree with this?
> 
> As another measure to avoid the autoremoval of basically unaffected
> Tryton modules it could be argued, that calypso is not ready for current 
> vobject
> and reassign the bug to calypso.

This is not related to calypso. The ABI has changed significantly.

We're miles away from an autoremoval so keep calm ;)

> 
> > Somebody uploading 0.8.x for python2 would be another option.
> 
> Would that be accepted?
> 
> Cheers,
> Mathias
> 
> -- 
> 
> Mathias Behrle
> PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
> AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6
> 

Bug#835237: marked as done (apscheduler: FTBFS with pytest 3.0.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 19:18:32 +
with message-id 
and subject line Bug#835237: fixed in apscheduler 3.3.0-1
has caused the Debian Bug report #835237,
regarding apscheduler: FTBFS with pytest 3.0.0
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.)


-- 
835237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apscheduler
Version: 3.0.5-1
Severity: important
Tags: sid stretch
Usertags: pytest3.0.0

During a test rebuild of apscheduler against pytest 3.0.0 from experimental,
apscheduler failed to build:
| === FAILURES 
===
|  TestConvertToDatetime.test_date[None] 
_
| tests/test_util.py:109: in test_date
| assert isinstance(returned, datetime)
| E   assert False
| E+  where False = isinstance(None, datetime)
|  TestConvertToDatetime.test_date[date] 
_
| tests/test_util.py:112: in test_date
| assert returned == expected
| E   assert datetime.datetime(2009, 8, 1, 0, 0, tzinfo=) == datetime.datetime(2009, 7, 6, 0, 0, 
tzinfo=)
| __ TestConvertToDatetime.test_date[datetime] 
___
| tests/test_util.py:112: in test_date
| assert returned == expected
| E   assert datetime.datetime(2009, 8, 1, 5, 6, 12, tzinfo=) == datetime.datetime(2009, 7, 6, 0, 0, 
tzinfo=)
|  TestConvertToDatetime.test_date[date as text] 
_
| tests/test_util.py:112: in test_date
| assert returned == expected
| E   assert datetime.datetime(2009, 8, 1, 0, 0, tzinfo=) == datetime.datetime(2009, 7, 6, 0, 0, 
tzinfo=)
| __ TestConvertToDatetime.test_date[datetime as text] 
___
| tests/test_util.py:112: in test_date
| assert returned == expected
| E   assert datetime.datetime(2009, 8, 1, 5, 16, 12, tzinfo=) == None
| ___ TestConvertToDatetime.test_date[existing tzinfo] 
___
| tests/test_util.py:112: in test_date
| assert returned == expected
| E   assert datetime.datetime(2009, 8, 1, 0, 0, tzinfo=pytz.FixedOffset(-60)) 
== None
|  pytest-warning summary 

| WC1 None [pytest] section in setup.cfg files is deprecated, use [tool:pytest] 
instead.
| = 6 failed, 305 passed, 90 skipped, 1 pytest-warnings in 3.07 seconds 
==
| E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
python2.7 setup.py test
| dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 
--system=custom --test-args={interpreter} setup.py test returned exit code 13

See https://people.debian.org/~sramacher/logs/pytest3.0.0/apscheduler_amd64.log
for a full log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: apscheduler
Source-Version: 3.3.0-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated apscheduler 
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, 15 Nov 2016 17:22:02 +
Source: apscheduler
Binary: python-apscheduler python3-apscheduler
Architecture: source all
Version: 3.3.0-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-apscheduler - In-process task scheduler with Cron-like capabilities
 python3-apscheduler - In-process task scheduler with Cron-like capabilities
Closes: 835237
Changes:
 apscheduler (3.3.0-1) unstable; urgency=low
 .
   * New upstream release.
   * Add python{,3}-setuptools-scm to build depends.
   * Add Python{,3} build depends to all jobstores for self-tests
 (closes: #835237).
   * Add patch to skip RethinkDB jobstore tests.
   * Break build depends to several lines.
   * Remove the Python 2 AsyncIOExecutor as asyncio is not supported on it.
   * Update

Processed: Part of the OpenSSL transition

[Debian Bug Tracking System]

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

> block 827061 by 844534
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828556 828330 828462 828414 828283 828584 837960 828610 
828339 828521 828599 828446 828453 828594 828565 828281 828497 828407 828343 
828239 828317 828600 828369 828514 828559 828582 835811 828244 828352 828492 
828325 828349 828437 828467 828421 828430 841635 828249 828379 828376 828614 
828424 828303 828271 829465 828503 828507 828473 828290 828476 828585 828452 
828384 828373 828619 828538 828481 828575 828338 828500 828457 828545 828347 
828401 828527 828558 828399 828289 835585 828295 828544 828409 828425 844254 
828332 828478 828380 828618 828572 835799 828082 828431 828501 828494 828496 
828448 828411 828439 828267 828608 828419 828232 828142 828264 828273 828309 
828406 835797 828280 828579 828571 828461 828377 828488 828413 828276 828447 
828592 828304 828344 828288 828518 828353 828386 828292 828603 828504 828533 
828390 828308 828331 828490 828391 828256 835800 828248 828482 828534 828604 
828537 828393 828506 828417 828438 828305 828562 828381 827076 828389 828429 
828367 835789 828540 828553 828329 828426 828327 828427 828480 828450 828315 
835786 828531 828262 828319 828596 828423 828597 828459 828508 828442 828605 
828483 828300 828241 828307 828543 828270 828612 828472 828528 828306 828400 
828230 828512 828602 828529 835798 828253 828291 828398 808669 828578 828258 
828318 828402 828269 828484 835785 828552 828228 828371 828573 828471 828583 
828609 828395 828449 828311 828577 828498 828416 828328 828510 828591 828511 
828342 828383 828443 828323 828581 828351 828396 828322 828321 828127 828451 
828607 828260 828587 828233 828284 828355 828434 828617 828509 828441 828268 
828491 828301 828243 828590 828454 828359 828485 828320 828561 828350 828460 
835804 828334 828567 828456 828557 828516 836419 828314 828252 828479 828235 
828278 828324 828523 828237 828487 828436 828257 828444 828282 828616 828378 
828392 835549 828410 828240 828515 828245 828606 828542 835790 828316 828365 
828266 828397 828375 828387 828560 828463 828404 828279 828382 828519 828366 
829452 828586 835796 828536 828370 828563 828360 828418 828341 828394 828595 
828440 828250 828296 828620 828615 828551 828405 828525 828259 828539 828569 
828548 828522 828598 828364 828601 828361 828285 828346 828265 828486 828354 
828570 828336 844271 828412 828298 828469 828466 828546 828566 828348 828297 
828368 828139 828238 828564 828261 828554 828275 828445 828313 828310 844301 
828403 828505 843532 828337 828435 828568 828358 828524 828229 828356 828251 
828293 828489 828493 828550 828470 828231 828302 828432 828433 828465 828242 
828372 844347 828357 828588 828613 828272 828589 835793 828502 828340 827068 
828294 828611 844311 828477 828362 828286 828385 828532 828312 828428 828580 
828326 828234 828458 828455 828374 828274 828345 828574 835794 814600 828246 
828549 828263 828468 828535 844345 828499 828526 828287 828513 828593 828254 
809271 828517 828520 828530 828576 828333 828415 828541 828474 828388 828363 
828495 828335 822380 828083 828555 828420 828277 843988 828255 828547 828422 
828464
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 844534
> thanks
Stopping processing here.

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

Bug#828579: The patch is upstream

[Hon Ching(Vicky) Lo]

The patch that supports OpenSSL 1.1 (backward-compatible) is upstream:
https://sourceforge.net/p/trousers/trousers/ci/05411ea68746acbaf4e69295be50b9a47cddb2fd/


Vicky

Bug#841639: marked as done (obmenu does not start)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 20:57:02 +0200
with message-id <20161117185702.bzuarzg7kcbk6...@bunk.spdns.de>
and subject line Re: Bug#841639: obmenu does not start [RESOLVED]
has caused the Debian Bug report #841639,
regarding obmenu does not start
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.)


-- 
841639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: obmenu
Version: 1.0-2+nmu2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

running obmenu returns the following:

Traceback (most recent call last):
  File "/usr/bin/obmenu", line 617, in 
app.init()
  File "/usr/bin/obmenu", line 521, in init
self.menu.loadMenu(self.menu_path)
  File "/usr/lib/python2.7/dist-packages/obxml.py", line 153, in loadMenu
self.dom = xml.dom.minidom.parseString(fil.read())
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 4, column
75



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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
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 obmenu depends on:
ii  python 2.7.11-2
ii  python-glade2  2.24.0-5.1
pn  python:any 

Versions of packages obmenu recommends:
ii  openbox  3.6.1-3

obmenu suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Oct 21, 2016 at 04:58:44PM +, byanbyanroryan wrote:
> Sorry, apparently it was my menu.xml file.  I changed tabs to spaces and 
> deleted an ampersand inside an id value, and it works now.

Thanks for the update.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#822013: marked as done (pebl: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 18:48:56 +
with message-id 
and subject line Bug#822013: fixed in pebl 1.0.2-4
has caused the Debian Bug report #822013,
regarding pebl: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pebl
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package pebl builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that pebl builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to pebl at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, pebl will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: pebl
Source-Version: 1.0.2-4

We believe that the bug you reported is fixed in the latest version of
pebl, 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.
Miriam Ruiz  (supplier of updated pebl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Nov 2016 18:58:44 +0100
Source: pebl
Binary: python-pebl python-pebl-dbg python-pebl-doc
Architecture: source amd64 all
Version: 1.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Miriam Ruiz 
Description:
 python-pebl - Python Environment for Bayesian Learning
 python-pebl-dbg - Python Environment for Bayesian Learning - debug
 python-pebl-doc - Python Environment for Bayesian Learning - documentation
Closes: 645255 822013
Changes:
 pebl (1.0.2-4) unstable; urgency=medium
 .
   * Upgraded Standards-Version from 3.9.1 to 3.9.8 and compat-version to 9
   * Added build-{arch,indep} targets. Closes: #822013. Thanks to Santiago Vila
   * Added dependency: python-pkg-resources. Closes: #645255
   * Added missing dh_numpy call in debian/rules
   * Changed Homepage from https://code.google.com/p/pebl-project/
 to https://github.com/abhik/pebl
Checksums-Sha1:
 2c7953055ffd3648a800cba6cea150df9339f5e9 2233 pebl_1.0.2-4.dsc
 51eebd0eadbeef68bad2a6245c4e3bd867bfe214 4620 pebl_1.0.2-4.debian.tar.bz2
 e2e5faeb5ea79f266455423350650d5750bdd8bf 8177 pebl_1.0.2-4_amd64.buildinfo
 01c879d985a75c93f5c6cea7c058f7646399fbf1 32142 
python-pebl-dbg_1.0.2-4_amd64.deb
 7c80d640bd1c369492f7a11bec3edbaa9968957e 1665568 
python-pebl-doc_1.0.2-4_all.deb
 c111fd3374f746f6bb1f435e97742bbeaf63e26e 63236 python-pebl_1.0.2-4_amd64.deb
Checksums-Sha256:
 95d58acdd1a9b1fe6779460af1f60452f445c3e1b5ea4100cd57e79b77a06dac 2233 
pebl_1.0.2-4.dsc
 6dbbf73fa551a4382f5772144e7b43bad1d6c6caf3430e669b3746e9b03d4c71 4620 
pebl_1.0.2-4.debian.tar.bz2
 db07b41ff631256cb99c71b2ebcc8d4fc5915f32832e6b96d3faeaec283c2cd8 8177 
pebl_1.0.2-4_amd64.buildinfo
 0b010b37dc82f0cd863ced4a8cd5ee077b3ca3a3b443c9e9714c58844af045be 32142 
python-pebl-dbg_1.0.2-4_amd64.deb
 ef20a30effeb67fb7ce525f8a68882a4159930d7ecdad26e3cb58f50e7e6cc0b 1665568 
python-pebl-doc_1.0.2-4_all.deb
 746c278a9cd425f1ac173d15f3c34ca2c9527436040bcf1c995c741f506f75fc 63236 
python-pebl_1.0.2-4_amd64.deb
Files:
 e30da7d4d519a38b54386955b5872856 2233 python optional pebl_1.0.2-4.dsc
 8b8fc1dcd7a0c0ceaab59a1a299cfec6 4620 python optional 
pebl_1.0.2-4.debian.tar.bz2
 bc2087e97f43d052d04a17315f9b4983 8177 python optional 
pebl_1.0.2-4_amd64.buildinfo
 4c0c2020252b71657a54631e17e1fcfc 32142 debug extra 
python-pebl-dbg_1.0.2-4_amd64.deb
 421d86543e02f24e83ee9090eede2f6c 1665568 doc optional 
python-pebl-doc_1.0.2-4_all.deb
 02e63cdc3de98ad2dbadf94ff9fde0af 63236 python optional 
python-pebl_1.0.2-

Bug#834066: marked as done (python-pyhsm: ships /usr/lib/python2.7/dist-packages/test/__init__.py)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 20:32:57 +0200
with message-id <20161117183257.nggsrp7nsoze6...@bunk.spdns.de>
and subject line The upstream fix is in 1.2.0
has caused the Debian Bug report #834066,
regarding python-pyhsm: ships /usr/lib/python2.7/dist-packages/test/__init__.py
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.)


-- 
834066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pyhsm
Version: 1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 python-toposort 1.1-1
Control: retitle -2 python-toposort: ships 
/usr/lib/python2.7/dist-packages/test/__init__.py

Hi,

/usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic
name that shouldn't be used by any python module, since it can easily
lead to file conflicts between packages (that is how I noticed it).


Andreas
--- End Message ---
--- Begin Message ---
Version: 1.2.0-1

The upstream fix is included in the 1.2.0 release.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Processed: Bug#834919 closed by Miriam Ruiz

[Debian Bug Tracking System]

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

> retitle 834919 python-pattern: FTBFS randomly (failing tests)
Bug #834919 {Done: Miriam Ruiz } [src:python-pattern] 
python-pattern: FTBFS too much often (failing tests)
Changed Bug title to 'python-pattern: FTBFS randomly (failing tests)' from 
'python-pattern: FTBFS too much often (failing tests)'.
> thanks
Stopping processing here.

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

Bug#834919: closed by Miriam Ruiz

[Santiago Vila]

retitle 834919 python-pattern: FTBFS randomly (failing tests)
thanks

Hi. I'm retitling this bug because I never liked the "FTBFS too much often"
wording. Either it always fails, or it fails randomly. This one
was of the second type.

An alternate approach to the current fix would be to run the tests
followed by "|| true", that way we would still have the output of the
tests in the build log, but without failing tests making the whole
build to fail.

Thanks.

Bug#844638: Does not work with lua-sec 0.6

[Michael Meskes]

Package: prosody
Version: 0.9.10-1
Severity: grave

Prosody needs lua 5.1 it seems, but the latest version of lua-sec does
not seem to offer this anymore. Therefore prosody is not able to
initialize TLS anymore:

... tls error   Unable to initialize TLS: LuaSec (required for encryption) was 
not found

This results in a server that is no longer accessible in a standard
encrypted way and thus either makes the service unusable or unsafe.

Re-installing lua-sec 0.5 from stable fixes the issue.

Michael

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

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

Versions of packages prosody depends on:
ii  adduser 3.115
ii  libc6   2.24-5
ii  libidn111.33-1
ii  libssl1.0.2 1.0.2j-1
ii  lua-expat [lua5.1-expat]1.3.0-3
ii  lua-filesystem [lua5.1-filesystem]  1.6.3-1
ii  lua-sec [lua5.1-sec]0.5-1
ii  lua-socket [lua5.1-socket]  3.0~rc1+git+321c0c9-1
ii  lua5.1  5.1.5-8.1+b2
ii  ssl-cert1.0.38

Versions of packages prosody recommends:
ii  lua-event [lua5.1-event]  0.4.3-2

Bug#834919: marked as done (python-pattern: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 18:05:40 +
with message-id 
and subject line Bug#834919: fixed in python-pattern 2.6+git20150109-2
has caused the Debian Bug report #834919,
regarding python-pattern: FTBFS too much often (failing tests)
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.)


-- 
834919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pattern
Version: 2.6+git20150109-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
#dh build-indep --with python2,python3
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/pattern

[... snipped ...]

pattern.vector.entropy()
pattern.vector.Model.feature_selection()
pattern.vector.Model.filter()
pattern.vector.Model.frequent()
pattern.vector.Model.idf()
patten.vector.Model.information_gain()
patten.vector.Model.gain_ratio()
pattern.vector.Model.reduce()
pattern.vector.Model
pattern.vector.Model.append()
pattern.vector.Model.export()
pattern.vector.Model.save()
pattern.vector.Model.load()
pattern.vector.Model.neighbors()
pattern.vector.Model.search()
pattern.vector.Document.tfidf()
pattern.vector.LSA
pattern.vector.LSA.concepts
pattern.vector.LSA.transform()
pattern.vector.Model.reduce()
pattern.vector.centroid()
pattern.vector.distance()
pattern.vector.DistanceMap
pattern.vector.features()
pattern.vector.Cluster()
pattern.vector.hierarchical()
pattern.vector.kmeans(seed=KMPP)
pattern.vector.kmeans(seed=RANDOM)
pattern.vector.mean()
pattern.vector.Classifier._vector()
pattern.vector.IGTree.train()
pattern.vector.IGTree.classify()
pattern.vector.IGTree.save()
pattern.vector.KNN.train()
pattern.vector.KNN.classify()
pattern.vector.KNN.save()
pattern.vector.svm.LIBSVM
pattern.vector.svm.LIBLINEAR
pattern.vector.NB.train()
pattern.vector.NB.classify()
pattern.vector.NB.save()
pattern.vector.SLP.train()
pattern.vector.SLP.classify()
pattern.vector.SLP.save()
pattern.vector.SVM.train()
pattern.vector.SVM.classify()
pattern.vector.SVM.save()
debian/rules:85: recipe for target 'run-tests' failed
make[1]: *** [run-tests] Error 1
make[1]: Leaving directory '/<>/python-pattern-2.6+git20150109'
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense, and the fact that I was
doing "dpkg-buildpackage -A" does not mean anything special.

I attach two different failed build logs, but you may find more here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pattern.html

Thanks.

python-pattern_2.6+git20150109-1_amd64-20160820T133441Z.gz
Description: application/gzip


python-pattern_2.6+git20150109-1_amd64-20160818T213731Z.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pattern
Source-Version: 2.6+git20150109-2

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

Debian distribution maintenance software
pp.
Miriam Ruiz  (supplier of updated python-pattern package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Nov 2016 18:30:43 +0100
Source: python-pattern
Binary: python-pattern
Architecture: source all
Version: 2.6+git20150109-2
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Miriam Ruiz 
Description:
 python-pattern - web mining modul

Bug#844632: marked as done (Drupal: SA-CORE-2016-005)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 12:03:22 -0600
with message-id <20161117180322.gi55...@gwolf.org>
and subject line Re: Bug#844632: Drupal: SA-CORE-2016-005
has caused the Debian Bug report #844632,
regarding Drupal: SA-CORE-2016-005
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.)


-- 
844632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drupal7
Version: 7.32-1+deb8u7
Severity: grave
Tags: security

Hi!

The Drupal Security Team publicly announced a fix for an external URL
injection flaw in Drupal7:
https://www.drupal.org/SA-CORE-2016-005

-- Adi


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 7.32-1+deb8u8
Version: 7.52-1
Version: 7.52-1~bpo8+1

Adi Kriegisch dijo [Thu, Nov 17, 2016 at 06:27:28PM +0100]:
> Package: drupal7
> Version: 7.32-1+deb8u7
> Severity: grave
> Tags: security
> 
> Hi!
> 
> The Drupal Security Team publicly announced a fix for an external URL
> injection flaw in Drupal7:
> https://www.drupal.org/SA-CORE-2016-005

Thanks for the heads-up - I have just uploaded the package to
unstable, am waiting for the security team for the Jessie upload, and
am about to do the Jessie-Backports upload :-)

I am hand-closing your bug, as I didn't get to note it in the
changelogs. I'm not sure if the multiple version tags will be properly
noted by the BTS, but we will soon find out :)


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

Bug#844632: Drupal: SA-CORE-2016-005

[Adi Kriegisch]

Package: drupal7
Version: 7.32-1+deb8u7
Severity: grave
Tags: security

Hi!

The Drupal Security Team publicly announced a fix for an external URL
injection flaw in Drupal7:
https://www.drupal.org/SA-CORE-2016-005

-- Adi


signature.asc
Description: Digital signature

Processed: [bts-link] source package src:libcrypt-openssl-dsa-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:libcrypt-openssl-dsa-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #828384 (http://bugs.debian.org/828384)
> # Bug title: libcrypt-openssl-dsa-perl: FTBFS with openssl 1.1.0
> #  * http://rt.cpan.org/Public/Bug/Display.html?id=118346
> #  * remote status changed: open -> resolved
> #  * closed upstream
> tags 828384 + fixed-upstream
Bug #828384 {Done: gregor herrmann } 
[src:libcrypt-openssl-dsa-perl] libcrypt-openssl-dsa-perl: FTBFS with openssl 
1.1.0
Added tag(s) fixed-upstream.
> usertags 828384 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 828384 + status-resolved
There were no usertags set.
Usertags are now: status-resolved.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package uqm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package uqm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #843979 (http://bugs.debian.org/843979)
> # Bug title: uqm: FTBFS with gcc-6 on i386: scalemmx.h:638: Error: register 
> value used as expression
> #  * http://gcc.gnu.org/PR78311
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 843979 + fixed-upstream
Bug #843979 [uqm] uqm: FTBFS with gcc-6 on i386: scalemmx.h:638: Error: 
register value used as expression
Added tag(s) fixed-upstream.
> usertags 843979 + status-RESOLVED resolution-INVALID
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INVALID.
> thanks
Stopping processing here.

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

Bug#828384: marked as done (libcrypt-openssl-dsa-perl: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 17:34:24 +
with message-id 
and subject line Bug#828384: fixed in libcrypt-openssl-dsa-perl 0.18-1
has caused the Debian Bug report #828384,
regarding libcrypt-openssl-dsa-perl: FTBFS with openssl 1.1.0
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.)


-- 
828384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-openssl-dsa-perl
Version: 0.15-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libcrypt-openssl-dsa-perl_0.15-1_amd64-20160529-1439

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libcrypt-openssl-dsa-perl
Source-Version: 0.18-1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcrypt-openssl-dsa-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: Thu, 17 Nov 2016 18:07:21 +0100
Source: libcrypt-openssl-dsa-perl
Binary: libcrypt-openssl-dsa-perl
Architecture: source
Version: 0.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 828384
Description: 
 libcrypt-openssl-dsa-perl - module which implements the DSA signature 
verification system
Changes:
 libcrypt-openssl-dsa-perl (0.18-1) unstable; urgency=medium
 .
   * Team upload.
   * Import upstream version 0.18.
 Fixes "FTBFS with openssl 1.1.0" (closes: #828384).
Checksums-Sha1: 
 60a478022eb3e56bda81a765a238ae9b12a3b05c 2341 
libcrypt-openssl-dsa-perl_0.18-1.dsc
 c0e3e571919c086c09967b8e94d6eb89288de717 9178 
libcrypt-openssl-dsa-perl_0.18.orig.tar.gz
 dd31c94c9fe5aba28404c8f9ceb63305c3e81e97 3536 
libcrypt-openssl-dsa-perl_0.18-1.debian.tar.xz
Checksums-Sha256: 
 fe913bfca379cdd16fe9b39816d011305c74dde35bf6ce03c314b01cb6639a65 2341 
libcrypt-openssl-dsa-perl_0.18-1.dsc
 ab4ae301b4835676aa6d2d7d36f882472a21795b68f42441a6ad6f2bbe228080 9178 
libcrypt-openssl-dsa-perl_0.18.orig.tar.gz
 2087ddf249bc3d3242ddd14ef84393ff99ed34f758dee051d60bf2e4bcf2ddde 3536 
libcrypt-openssl-dsa-perl_0.18-1.debian.tar.xz
Files: 
 99d5bca301e6041965a83039c812777e 2341 perl optional 
libcrypt-openssl-dsa-perl_0.18-1.dsc
 eeea3cd7d7651bee856697e1c038257c 9178 perl optional 
libcrypt-openssl-dsa-perl_0.18.orig.tar.gz
 a97500283fd955ed87ae5344c50584ec 3536 perl optional 
libcrypt-openssl-dsa-perl_0.18-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlgt5B1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qga7HA//bdaBxg9znpPC8HPzd7WyC/CwgPyhUAv1iMSNoofnt/joJVXix+URwRG6
mq8d3kXijVEwEcg7YDEGhwrGX5ND7hoHf6t5Z8tqDanlkP8wAUJiVWfYGFFLz/1A
t0r1X7oNxVJxM5D0wSEtb2cNghRPVtpsD5/ACZHHa9ywK/Lcq3VfdhNyjZ42oHi/
QkXsGVgYDwaWhgFf02/qxelfopizmcN6WdKOWSo1qI/idgKZyDAehUXmnoC37qFN
l1gj03vPT3Y/N1XmLIGvlIaKiMexb5eB+EkfPUMgXob//3oSyB/2oDDgAziM99Ub
DvmhpDqHkqUIVSLi7rxBeJUiTRwkHhDB8Ff7fEtC5AFIvlICxMFc6zpVsJ0oF2uW
kS2CXRtXs4TpENGrCax7mW9TXNLszpqQkJJLhr/w46R0fHnIS8PQNzU9fpwr5P/1
hFATLfjFlV02Bc+tfnAhihUlqPHNeWYH6zlER6A7hD8IS6m6bpLUrtYnyf2CJZoP
V7xcsl+indsBsXS+hF3i7x8tIckEhJzYAbCsaGQbZSvN0IpGUT8C68n2vBXUfzK4
UImV89W3mrkyPYJxJCN9lEjQmw6uFX2OkoT8pMjpFFfnxe8i8jAX/w8AM5l9Jroy
ztDzCCm24gO7diRU2zDK9blpDC1/LHo5MOYzN/DZSc/hMxTdKOU=
=QZ+

Processed: [bts-link] source package cython

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package cython
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #833288 (http://bugs.debian.org/833288)
> # Bug title: would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: 
> Cannot assign type 'float' to 'int'
> #  * https://github.com/cython/cython/issues/551
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 833288 + fixed-upstream
Bug #833288 [cython] would FTBFS now with cython 0.24.1 
MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
Bug #835674 [cython] macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not 
use this file, it is the result of a failed Cython compilation.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 833288 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 833288 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #835674 (http://bugs.debian.org/835674)
> # Bug title: macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not use 
> this file, it is the result of a failed Cython compilation.
> #  * https://github.com/cython/cython/issues/551
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 835674 + fixed-upstream
Bug #835674 [cython] macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not 
use this file, it is the result of a failed Cython compilation.
Bug #833288 [cython] would FTBFS now with cython 0.24.1 
MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
Ignoring request to alter tags of bug #835674 to the same tags previously set
Ignoring request to alter tags of bug #833288 to the same tags previously set
> usertags 835674 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 835674 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:tiff

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:tiff
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #844013 (http://bugs.debian.org/844013)
> # Bug title: tiff: CVE-2016-9273
> #  * http://bugzilla.maptools.org/show_bug.cgi?id=2587
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 844013 + fixed-upstream
Bug #844013 [src:tiff] tiff: CVE-2016-9273
Added tag(s) fixed-upstream.
> usertags 844013 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #844057 (http://bugs.debian.org/844057)
> # Bug title: tiff: Heap buffer overflow via writeBufferToSeparateStrips 
> tiffcrop.c:1170
> #  * http://bugzilla.maptools.org/show_bug.cgi?id=2592
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 844057 + fixed-upstream
Bug #844057 [src:tiff] tiff: Heap buffer overflow via 
writeBufferToSeparateStrips tiffcrop.c:1170
Added tag(s) fixed-upstream.
> usertags 844057 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #844226 (http://bugs.debian.org/844226)
> # Bug title: tiff: CVE-2016-9297: potential read outside buffer in 
> _TIFFPrintField()
> #  * http://bugzilla.maptools.org/show_bug.cgi?id=2590
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 844226 + fixed-upstream
Bug #844226 [src:tiff] tiff: CVE-2016-9297: potential read outside buffer in 
_TIFFPrintField()
Added tag(s) fixed-upstream.
> usertags 844226 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package pnp4nagios

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package pnp4nagios
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #821642 (http://bugs.debian.org/821642)
> # Bug title: pnp4nagios-web: PHP 7.0 Transition
> #  * https://github.com/lingej/pnp4nagios/issues/125
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 821642 + fixed-upstream
Bug #821642 [pnp4nagios-web] pnp4nagios-web: PHP 7.0 Transition
Added tag(s) fixed-upstream.
> usertags 821642 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#841844: marked as done (libtesseract3: shared data files shipped in shared library package)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 10:00:18 +
with message-id 
and subject line Bug#841844: fixed in tesseract 3.04.01-4.1
has caused the Debian Bug report #841844,
regarding libtesseract3: shared data files shipped in shared library 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.)


-- 
841844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtesseract3
Version: 3.04.01-4.1
Severity: serious
Justification: Debian Policy section 8.2

libtesseract3 includes data files in /usr/share/tesseract-ocr/tessdata.
That filename is not versioned. After a soname bump, the new library
package will thus conflict with libtesseract3. Such behaviour is
forbidden by Debian Policy section 8.2:

| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package. 

The usual solution is to add a libtesseract-data package containing
them.

Helmut
--- End Message ---
--- Begin Message ---
Source: tesseract
Source-Version: 3.04.01-4.1

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated tesseract package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2016 09:56:23 +
Source: tesseract
Binary: tesseract-ocr-dev libtesseract-dev libtesseract-data libtesseract3 
tesseract-ocr tesseract-ocr-all
Architecture: source all amd64
Version: 3.04.01-4.1
Distribution: unstable
Urgency: medium
Maintainer: Jeffrey Ratcliffe 
Changed-By: Jonathan Wiltshire 
Description:
 libtesseract-data - Development files for the tesseract command line OCR tool
 libtesseract-dev - Development files for the tesseract command line OCR tool
 libtesseract3 - Tesseract OCR library
 tesseract-ocr - Tesseract command line OCR tool
 tesseract-ocr-all - Tesseract OCR with all language packages
 tesseract-ocr-dev - transitional dummy package
Closes: 841844
Changes:
 tesseract (3.04.01-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move architecture-independent files into a new
 binary package (Closes: #841844)
Checksums-Sha1:
 525ba6d7a8c7de76f050a3a502a0d0fa031f18f1 2187 tesseract_3.04.01-4.1.dsc
 efc69bbc3385203bce029f5d3e0c1b5b019dafa0 8075 tesseract_3.04.01-4.1.diff.gz
 d4c61c14cb8fc1301139de4e6fd503cc6d5986fc 12094 
libtesseract-data_3.04.01-4.1_all.deb
 f63a7d91a47a3bb3bc9bf6927f86153270eea5e4 1346028 
libtesseract-dev_3.04.01-4.1_amd64.deb
 eac47af0d4a151dfa732d811b29395d73ed8 11134440 
libtesseract3-dbgsym_3.04.01-4.1_amd64.deb
 7016e95c7c0a26e4573b2b789c4893a78738e3ed 1123356 
libtesseract3_3.04.01-4.1_amd64.deb
 d2c696a538301aafe597852f7ba98e0f0666949a 9770 
tesseract-ocr-all_3.04.01-4.1_all.deb
 d79666dedf51a08ca60647d575a02811d75ef1b8 1918866 
tesseract-ocr-dbgsym_3.04.01-4.1_amd64.deb
 a37804a02e5c57749fdd3d0278b0442ccfce08b9 11244 
tesseract-ocr-dev_3.04.01-4.1_all.deb
 1c226069dc44426d48061bb7b62183a64778ff83 141720 
tesseract-ocr_3.04.01-4.1_amd64.deb
 27229cc7cc0e75d111b1b3a5b481d8bd1f065db3 9417 
tesseract_3.04.01-4.1_2016T102625z-0f9eb4de.buildinfo
Checksums-Sha256:
 3b6e3beda2dae27d62b7553a4dc0667e4d999864b3daddca01956f5b0b132964 2187 
tesseract_3.04.01-4.1.dsc
 8d46aa5250d4d214a4430633a3742f5cbeee6e9d3624bdddc2bf80a382ef6681 8075 
tesseract_3.04.01-4.1.diff.gz
 fc1f9523ef72db49f6e2b854c9f6973044d8b041dba5faff2192e6be259eb1ac 12094 
libtesseract-data_3.04.01-4.1_all.deb
 bfb0b6fa2569eb91966ab72a2f87dab4698fc374678c4014825f3be615ca27f4 1346028 
libtesseract-dev_3.04.01-4.1_amd64.deb
 12a74d34d060e2813b16cf951cb762a1afa96aa105ff0f07c652755224e1e883 11134440 
libtesseract3-dbgsym_3.04.01-4.1_amd64.deb
 d70c8ce2b194c72c252527ca8698b864181132cd179e990e8cc80cef759380a7 1123356 
libtesseract3_3.04.01-4.1_amd64.deb
 97ba2e92afc63ad52bdf9131abc7d8df51d8d2120a5b5fcbd9d00e6e435052ef 9770 
tesseract-ocr-all_3.04.01-4.1_all.deb
 b04733ade80c94439fb43781900ed7918aee9f

Bug#828326: marked as done (glusterfs: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 15:05:40 +
with message-id 
and subject line Bug#828326: fixed in glusterfs 3.8.5-2
has caused the Debian Bug report #828326,
regarding glusterfs: FTBFS with openssl 1.1.0
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.)


-- 
828326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glusterfs
Version: 3.7.11-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/glusterfs_3.7.11-1_amd64-20160529-1422

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: glusterfs
Source-Version: 3.8.5-2

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated glusterfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 17 Nov 2016 15:19:56 +0100
Source: glusterfs
Binary: glusterfs-client glusterfs-server glusterfs-common glusterfs-dbg
Architecture: source amd64
Version: 3.8.5-2
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 glusterfs-client - clustered file-system (client package)
 glusterfs-common - GlusterFS common libraries and translator modules
 glusterfs-dbg - GlusterFS debugging symbols
 glusterfs-server - clustered file-system (server package)
Closes: 828326
Changes:
 glusterfs (3.8.5-2) unstable; urgency=high
 .
   * Build depend on libssl1.0-dev | libssl-dev.
 Closes: #828326
Checksums-Sha1:
 03069b2418da0704b38ce72f5bba13afcb51a7dd 2261 glusterfs_3.8.5-2.dsc
 d78ae0ca31ab7d9010189aca4b55e1fb528bd413 15588 glusterfs_3.8.5-2.debian.tar.xz
 669686b48e6139dc7357ba27b622a1425e9b5550 3692298 
glusterfs-client_3.8.5-2_amd64.deb
 330ce04b8b23aa836b7e52404d9f84d1911df64c 6609294 
glusterfs-common_3.8.5-2_amd64.deb
 96b87746f9d472b86b5c6cd1d90735d0a56c33e3 17901708 
glusterfs-dbg_3.8.5-2_amd64.deb
 b6b40d490ebc6e0c1cc90c970b89c56333cec51f 3847776 
glusterfs-server_3.8.5-2_amd64.deb
 f58a30d6e383efd140a8a11a89f71aa113b545bc 8143 glusterfs_3.8.5-2_amd64.buildinfo
Checksums-Sha256:
 b4323f354a6b3143e32406980b272c379e1e52cf8ad2d8077585c87414c565b8 2261 
glusterfs_3.8.5-2.dsc
 cdc75b473f79eeb8a8023e0cd5946933761f459316b2a2d7a44b94779a1aa99a 15588 
glusterfs_3.8.5-2.debian.tar.xz
 8c958391565d9ca6b88bfd5d64706f961e47448534488bfac388cb6eb8ac4ed7 3692298 
glusterfs-client_3.8.5-2_amd64.deb
 a9d4648cb79d878cf4e70955424d6eae352f09281d9ae8c4980adba7d702d089 6609294 
glusterfs-common_3.8.5-2_amd64.deb
 519f0ed6ad179d6075be289ccdd3156e05aa7223e93dd16472293d2d27ba238a 17901708 
glusterfs-dbg_3.8.5-2_amd64.deb
 122c7a302e6331e52f2a70823301aab85d158d668e090a1ce64a03e5c6859b3a 3847776 
glusterfs-server_3.8.5-2_amd64.deb
 ab2585ee26f5157ad3bbb08963c36c913aaee0e806808221e90ca8c6991527e8 8143 
glusterfs_3.8.5-2_amd64.buildinfo
Files:
 b11dcf948672855e96d6f57eb7be0c53 2261 admin optional glusterfs_3.8.5-2.dsc
 592de6b6d8ed5f0159caa2e701395924 15588 admin optional 
glusterfs_3.8.5-2.debian.tar.xz
 86d5e0c257674572c193a806bfd22f14 3692298 admin optional 
glusterfs-client_3.8.5-2_amd64.deb
 bd02e481d8fa8079ff7afbbe23189cab 6609294 admin optional 
glusterfs-common_3.8.5-2_amd64.deb
 69d62da361899d7db02ae6b2ef114b66 17901708 debug extra 
glusterfs-dbg_3.8.5-2_amd64.deb
 998299e32ed699af8861955efbcf21fd 3847776 admin optional 
glusterfs-server_3.8.5-2_amd

Processed: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #835416 [src:imagevis3d] imagevis3d: FTBFS: singleton.hpp:131: undefined 
reference to `boost::serialization::singleton_module::is_locked()'
Added tag(s) patch.

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

Bug#835416: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

[Graham Inggs]

Control: tags -1 patch

Hi Maintainer

The attached patch links libboost_serialization, as suggested by Tom
Fogal, and fixes the FTBFS with Boost 1.61.

I also found the build dependency on libboost-all-dev can be replaced
by libboost-serialization-dev, as follows:

--- a/debian/control
+++ b/debian/contro
@@ -9,7 +9,7 @@
debhelper (>= 9),
flex,
g++ (>= 4:4.6),
-   libboost-all-dev,
+   libboost-serialization-dev,
libbz2-dev,
libglew-dev,
libjpeg-dev,

Regards
Graham


boost_serialization.patch
Description: application/empty

Processed (with 1 error): merging 788062 648208 806273

[Debian Bug Tracking System]

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

> merge 788062 648208 806273
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Unable to merge bugs because:
severity of #648208 is 'important' not 'critical'
Failed to merge 788062: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#811634: meshlab: FTBFS with GCC 6: cannot convert x to y

[Graham Inggs]

In addition to Gert Wollny's patch, the attached patch fixes narrowing
conversions with GCC 6 on architectures where char is unsigned by
default.

Copying to debian-science-maintainers list in case someone is
interested in rescuing this package.


narrowing-conversion.patch
Description: application/empty

Bug#844617: g++-mingw-w64: C++ linking fails with cannot find -latomic.

[Steven Gawroriski]

Package: g++-mingw-w64
Version: 6.1.1-12+19.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

During the linking stage of even the most simplest source code (just a
main function), the C++ linking fails because it cannot find `-latomic`.
This effectively makes the C++ compiler useless because it cannot link
any binaries.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 4.4.27.161027.1
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 g++-mingw-w64 depends on:
ii  g++-mingw-w64-i6866.1.1-12+19.1
ii  g++-mingw-w64-x86-64  6.1.1-12+19.1

g++-mingw-w64 recommends no packages.

g++-mingw-w64 suggests no packages.

-- no debconf information

Processed: Re: apticron: apt-get stops when an update for a held back package is found

[Debian Bug Tracking System]

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

> severity 840064 normal
Bug #840064 [apticron] apticron: apt-get stops when an update for a held back 
package is found
Severity set to 'normal' from 'grave'
> tag 840064 moreinfo
Bug #840064 [apticron] apticron: apt-get stops when an update for a held back 
package is found
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#840064: apticron: apt-get stops when an update for a held back package is found

[Francesco Namuri]

severity 840064 normal
tag 840064 moreinfo
thanks

Hello Michael,
thanks for your bug report. I'm downgrading it to normal severity
waiting for more information. IMHO this is not a bug but I'd like
to see the error you're getting. Can you please attach it to
this report?

Trying to automatically update a package that has the "held"
flag it's a dangerous/unwanted behavior, IMHO the warning/error
should be raised and the executions must stop.

The solution proposed "allow-change-held-packages" it's also
very dangerous, as you can see in the man page:

"
--allow-change-held-packages
   Force yes; this is a dangerous option that will
   cause apt to continue without prompting if it is
   changing held packages. It should not be used
   except in very special situations. Using it can
   potentially destroy your system! Configuration
   Item: APT::Get::allow-change-held-packages.
   Introduced in APT 1.1.
"

Ciao,
Francesco

Bug#843025: fixed in metview 4.7.2-2

[Alastair McKinstry]

Ugh.

Its just broken now because ksh was a dependency of magics++, which is a
dependency of metview, and so it was being pulled in.

ksh suffers from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810158 "Grave;  wontfix".

I've removed the dependency in magics++ by rewriting the scripts; trivial.

I think I need to add an explicit dep on "pdksh | ksh" and see if pdksh
can do the job instead.

regards

Alastair




On 17/11/2016 14:49, Gianfranco Costamagna wrote:
> control: unarchive -1
> control: reopen -1
> control: severity -1 serious
> control: found -1 4.7.2-2
>
> Hi,
>> We believe that the bug you reported is fixed in the latest version of
>> metview, which is due to be installed in the Debian FTP archive.
> the build is now broken in a clean sbuild sid environment, because the 
> package FTBFS due to missing ksh
>
> btw the failure is probably related to your cmake-fixes.patch
>
> @@ -148,7 +148,7 @@ set(extra_install_files macro_built_in_f
>
>  ADD_CUSTOM_COMMAND(
>  OUTPUT  
> ${CMAKE_BINARY_DIR}/share/metview/etc/macro_built_in_functions.txt
> -COMMAND ${FULL_STARTUP_SCRIPT_PATH} -b 
> ${CMAKE_CURRENT_SOURCE_DIR}/../../../scripts/generate_list_of_macro_functions.mv
>  ${CMAKE_BINARY_DIR}/share/metview/etc/macro_built_in_functions.txt
> +COMMAND ksh ${FULL_STARTUP_SCRIPT_PATH} -b 
> ${CMAKE_CURRENT_SOURCE_DIR}/../../../scripts/generate_list_of_macro_functions.mv
>  ${CMAKE_BINARY_DIR}/share/metview/etc/macro_built_in_functions.txt
>  DEPENDS ${FULL_STARTUP_SCRIPT_PATH} ${metview_core_targets}
>  )
>
>
> maybe you need to revert that?
>
> G.
>
> see the build log [1]
> [...]
> ../../lib/libMvMars.a(files.c.o): In function `marstmp':
> ./debian/build/src/libMars/./src/libMarsClient/files.c:21: warning: the use 
> of `tempnam' is dangerous, better use `mkstemp'
> make[3]: Leaving directory '/<>/debian/build'
> [ 80%] Built target Reprojection
> make -f share/metview/etc/CMakeFiles/macro_built_in_functions.dir/build.make 
> share/metview/etc/CMakeFiles/macro_built_in_functions.dir/depend
> make[3]: Entering directory '/<>/debian/build'
> cd /<>/debian/build && /usr/bin/cmake -E cmake_depends "Unix 
> Makefiles" /<> /<>/share/metview/etc 
> /<>/debian/build /<>/debian/build/share/metview/etc 
> /<>/debian/build/share/metview/etc/CMakeFiles/macro_built_in_functions.dir/DependInfo.cmake
>  --color=
> Scanning dependencies of target macro_built_in_functions
> make[3]: Leaving directory '/<>/debian/build'
> make -f share/metview/etc/CMakeFiles/macro_built_in_functions.dir/build.make 
> share/metview/etc/CMakeFiles/macro_built_in_functions.dir/build
> make[3]: Entering directory '/<>/debian/build'
> [ 80%] Generating macro_built_in_functions.txt
> cd /<>/debian/build/share/metview/etc && ksh 
> /<>/debian/build/bin/metview -b 
> /<>/share/metview/etc/../../../scripts/generate_list_of_macro_functions.mv
>  /<>/debian/build/share/metview/etc/macro_built_in_functions.txt
> /bin/sh: 1: ksh: not found
> share/metview/etc/CMakeFiles/macro_built_in_functions.dir/build.make:67: 
> recipe for target 'share/metview/etc/macro_built_in_functions.txt' failed
> make[3]: *** [share/metview/etc/macro_built_in_functions.txt] Error 127
> make[3]: Leaving directory '/<>/debian/build'
> CMakeFiles/Makefile2:5526: recipe for target 
> 'share/metview/etc/CMakeFiles/macro_built_in_functions.dir/all' failed
> make[2]: *** [share/metview/etc/CMakeFiles/macro_built_in_functions.dir/all] 
> Error 2
> make[2]: *** Waiting for unfinished jobs
> [...]
>
> [1] 
> http://debomatic-amd64.debian.net/distribution#unstable/metview/4.7.2-2/buildlog
>

-- 
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

Bug#817092: marked as done (libjs-handlebars: source package contains files whose source is not in Debian)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 21:05:33 +0530
with message-id 
and subject line Re: libjs-handlebars: Minified source is non-free
has caused the Debian Bug report #817092,
regarding libjs-handlebars: source package contains files whose source is not 
in Debian
to be marked as done.

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

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


-- 
817092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-handlebars
Version: 1.3.0-1
Severity: serious
Justification: DSFG §2

Hello,

I noticed that, aside from the version in experimental, libjs-handlebars is
combined into a single file and already pre-"built". That means that Debian is
not distributing the actual source, which fails DFSG §2

  -- Luke Faraone
--- End Message ---
--- Begin Message ---
On Tue, 08 Mar 2016 05:40:34 + Luke Faraone  wrote:
> I noticed that, aside from the version in experimental, libjs-handlebars is
> combined into a single file and already pre-"built". That means that Debian is
> not distributing the actual source, which fails DFSG §2

The version in experimental is now reuploaded to unstable as prometheus
dropped dependency on libjs-handlebars and switched to libjs-moustache.
ruby-handlebars-assets is in non-free and now can move to contrib as
node-handlebars provides source but build tools are currently missing.
diaspora is already in contrib.

This means libjs-handlebars cannot be used in browser environment until
we browserify it in debian (which is in progress, jison and grunt is
packaged, we still need to package babel-runtime, babel-handlers, and
grunt-babel to move forward).



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#830986: marked as done (libjs-handlebars: missing source)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 21:04:59 +0530
with message-id 
and subject line Re: libjs-handlebars: missing source
has caused the Debian Bug report #830986,
regarding libjs-handlebars: missing source
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.)


-- 
830986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjs-handlebars
Version: 1.3.0-1
Severity: serious
Control: clone -1 -2
Control: reassign -2 ruby-handlebars-assets
Control: found -2 2:0.23.0-2
Control: block -2 by -1

Hi,

I briefly looked into the package due to the discussion on -devel@ and
the ctte bug.  The source for the javascript code seems to be missing:
it contains generated lexer/parser code, see the upstream source at

  https://github.com/wycats/handlebars.js/blob/v1.3.0/src/handlebars.l

(Just search for "yytext" in handlebars-v1.3.0.js
or vendor/assets/javascripts/handlebars.js for ruby-handlebar-assets.)

That seems to be a bit more than just concatenating files.

Ansgar
--- End Message ---
--- Begin Message ---
On Wed, 13 Jul 2016 15:44:34 +0100 Ansgar Burchardt 
wrote:
> I briefly looked into the package due to the discussion on -devel@ and
> the ctte bug. Â The source for the javascript code seems to be missing:
> it contains generated lexer/parser code, see the upstream source at
> 
> Â Â https://github.com/wycats/handlebars.js/blob/v1.3.0/src/handlebars.l

node-handlebars package now includes these files

> (Just search for "yytext" in handlebars-v1.3.0.js
> or vendor/assets/javascripts/handlebars.js for ruby-handlebar-assets.)
> 
> That seems to be a bit more than just concatenating files.

and the tool needed to convert these to javascript, jison is now in
main. Though to make it usable in browser still needs more work.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#844605: X11 segfault with AMD GPU since 4.8.x / Firmware issue

[Patrick Matthäi]

Package: linux
Version: 4.8.7-1
Severity: serious

Hello,

with linux 4.8.x (tested 4.8.5 and 4.8.7-1) X segfaults with this device:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) (prog-if 00
[VGA controller])
Subsystem: Hightech Information System Ltd. Tobago PRO [Radeon
R7 360 / R9 360 OEM]
Flags: fast devsel, IRQ 16
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=8M]
I/O ports at 3000 [size=256]
Memory at d200 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1
Len=010 
Capabilities: [150] Advanced Error Reporting
Capabilities: [200] #15
Capabilities: [270] #19
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] #13
Capabilities: [2d0] #1b
Kernel modules: radeon

dmesg reports a firmware missmatch:

[3.260395] [drm] register mmio size: 262144
[3.260422] [drm] doorbell mmio base: 0xD000
[3.260422] [drm] doorbell mmio size: 8388608
[3.260471] ATOM BIOS: C91306
[3.260595] radeon :01:00.0: VRAM: 2048M 0x -
0x7FFF (2048M used)
[3.260596] radeon :01:00.0: GTT: 2048M 0x8000 -
0x
[3.260597] [drm] Detected VRAM RAM=2048M, BAR=256M
[3.260597] [drm] RAM width 128bits DDR
[3.260623] [TTM] Zone  kernel: Available graphics memory: 8164316 kiB
[3.260623] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[3.260624] [TTM] Initializing pool allocator
[3.260628] [TTM] Initializing DMA pool allocator
[3.260638] [drm] radeon: 2048M of VRAM memory ready
[3.260639] [drm] radeon: 2048M of GTT memory ready.
[3.260646] [drm] Loading bonaire Microcode
[3.261103] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_pfp.bin
[3.261270] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_me.bin
[3.261546] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_ce.bin
[3.261725] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_mec.bin
[3.261858] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_rlc.bin
[3.262251] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_sdma.bin
[3.262442] radeon :01:00.0: firmware: direct-loading firmware
radeon/bonaire_mc.bin
[3.262451] radeon :01:00.0: firmware: failed to load
radeon/bonaire_k_smc.bin (-2)
[3.262454] radeon :01:00.0: Direct firmware load for
radeon/bonaire_k_smc.bin failed with error -2
[3.262845] radeon :01:00.0: firmware: direct-loading firmware
radeon/BONAIRE_smc.bin
[3.262846] ci_fw: mixing new and old firmware!
[3.262882] [drm:cik_init [radeon]] *ERROR* Failed to load firmware!
[3.262885] radeon :01:00.0: Fatal error during GPU init
[3.262887] [drm] radeon: finishing device.
[3.270266] [TTM] Finalizing pool allocator
[3.270269] [TTM] Finalizing DMA pool allocator
[3.270282] [TTM] Zone  kernel: Used memory at exit: 0 kiB
[3.270283] [TTM] Zone   dma32: Used memory at exit: 0 kiB
[3.270284] [drm] radeon: ttm finalized
[3.270451] radeon: probe of :01:00.0 failed with error -22
[3.273478] EFI Variables Facility v0.08 2004-May-17
[3.299516] pstore: using zlib compression
[3.299528] pstore: Registered efi as persistent store backend
[3.320176] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

With linux 4.7.8-1 everything works like a charm.


Xorg.log:
[ 4.981] (EE) Backtrace:
[ 4.981] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a)
[0x5636cf57a01a]
[ 4.981] (EE) 1: /usr/lib/xorg/Xorg (0x5636cf3c+0x1be389)
[0x5636cf57e389]
[ 4.981] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(0x7f9efd115000+0x33040) [0x7f9efd148040]
[ 4.981] (EE) 3: /usr/lib/xorg/Xorg (RRSetChanged+0x92) [0x5636cf4d7302]
[ 4.981] (EE) 4: /usr/lib/xorg/Xorg (RRScreenSetSizeRange+0x54)
[0x5636cf4dbab4]
[ 4.981] (EE) 5: /usr/lib/xorg/Xorg
(xf86RandR12CreateScreenResources+0x2bd) [0x5636cf49564d]
[ 4.981] (EE) 6: /usr/lib/xorg/Xorg (0x5636cf3c+0xc85e0)
[0x5636cf4885e0]
[ 4.981] (EE) 7: /usr/lib/xorg/Xorg (0x5636cf3c+0x57ed1)
[0x5636cf417ed1]
[ 4.981] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf1) [0x7f9efd1352b1]
[ 4.981] (EE) 9: /usr/lib/xorg/Xorg (_start+0x2a) [0x5636cf401fea]
[ 4.981] (EE)
[ 4.981] (EE) Segmentation fault at address 0xa0

-- 
/*
Mit freundlichem Gruß / 

Bug#844421: marked as pending

[Ondřej Nový]

tag 844421 pending
thanks

Hello,

Bug #844421 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/pycodestyle.git;a=commitdiff;h=4a83f33

---
commit 4a83f33aa66411aff0fecde9549ccec2211b3049
Author: Ondřej Nový 
Date:   Thu Nov 17 14:07:31 2016 +0100

New upstream release (Closes: #844421)

diff --git a/debian/changelog b/debian/changelog
index 0fc4670..72bda00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pycodestyle (2.2.0-1) UNRELEASED; urgency=medium
+
+  * New upstream release (Closes: #844421)
+
+ -- Ondřej Nový   Thu, 17 Nov 2016 14:03:46 +0100
+
 pycodestyle (2.1.0-1) unstable; urgency=medium
 
   * New upstream release

Processed: Bug#844421 marked as pending

[Debian Bug Tracking System]

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

> tag 844421 pending
Bug #844421 {Done: Ondřej Nový } [pycodestyle] rpmlint: FTBFS 
(failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 839424 mono/4.6.1.3+dfsg-2
Bug #839424 [src:mono-debugger-libs] mono-debugger-libs: FTBFS: 
System.IO.FileNotFoundException: Could not find file "/etc/localtime"
Marked as fixed in versions mono/4.6.1.3+dfsg-2.
>
End of message, stopping processing here.

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

Processed (with 1 error): Re: Bug#843025: fixed in metview 4.7.2-2

[Debian Bug Tracking System]

Processing control commands:

> unarchive -1
> reopen -1
Bug #843025 {Done: Alastair McKinstry } [metview] 
metview: doesn't need to depend on zsh or ksh-variant shells
'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 metview/4.7.2-2.
> severity -1 serious
Bug #843025 [metview] metview: doesn't need to depend on zsh or ksh-variant 
shells
Severity set to 'serious' from 'normal'
> found -1 4.7.2-2
Bug #843025 [metview] metview: doesn't need to depend on zsh or ksh-variant 
shells
Marked as found in versions metview/4.7.2-2.

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

Processed: Re: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:wxwidgets3.0
Bug #844486 [gnuplot-qt] gnuplot-qt: Mismatch between the program and library 
build versions with GNUTERM=wxt
Bug reassigned from package 'gnuplot-qt' to 'src:wxwidgets3.0'.
No longer marked as found in versions gnuplot/5.0.5+dfsg1-4.
Ignoring request to alter fixed versions of bug #844486 to the same values 
previously set
> retitle -1 wxwidgets3.0 should drop the ABI mismatch message
Bug #844486 [src:wxwidgets3.0] gnuplot-qt: Mismatch between the program and 
library build versions with GNUTERM=wxt
Changed Bug title to 'wxwidgets3.0 should drop the ABI mismatch message' from 
'gnuplot-qt: Mismatch between the program and library build versions with 
GNUTERM=wxt'.
> affects -1 gnuplot-qt
Bug #844486 [src:wxwidgets3.0] wxwidgets3.0 should drop the ABI mismatch message
Added indication that 844486 affects gnuplot-qt

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

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Adrian Bunk]

Control: reassign -1 src:wxwidgets3.0
Control: retitle -1 wxwidgets3.0 should drop the ABI mismatch message
Control: affects -1 gnuplot-qt

On Thu, Nov 17, 2016 at 09:41:07AM +0100, Vincent Lefevre wrote:
> On 2016-11-17 14:36:08 +1300, Olly Betts wrote:
> > In upstream wxWidgets, if the compile-time ABI and run-time ABI don't
> > match, then you get an error and the app won't run, which is just not
> > helpful.  In Debian we reduce that error to a warning - in practice I've
> > never seen an actual problem due to this, but leaving the warning there
> > means that this at least gets flagged as a potential issue.
> 
> A warning can be very annoying (e.g. because it mixes with other output
> to the terminal) and possibly break scripts that don't expect output to
> stderr. If this is not expected to work, then an error like upstreams's
> behavior is the right thing to do (there is a real issue, and the user
> must make sure that it gets fixed). Otherwise a warning isn't needed,
> except in some debug mode for developers or andvanced users (but such
> a mode would not be the default).

Yes, this is what should be done.

When the C++ ABI changes in an incompatible way (like it did a year ago),
there will anyway be a complete ABI transition in Debian - any
potential issue would not be specific to wxWidgets.

Matthias Klose confirmed that ABI version 10 is supposed to be backwards 
compatible with ABI version 9.

I'm closing the binNMU request and move the other bug
to src:wxwidgets3.0

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#839424: marked as done (mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not find file "/etc/localtime")

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 10:28:13 +
with message-id 
and subject line 
has caused the Debian Bug report #839424,
regarding mono-debugger-libs: FTBFS: System.IO.FileNotFoundException: Could not 
find file "/etc/localtime"
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.)


-- 
839424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono-debugger-libs
Version: 0+20131201.3459502-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory 
> '/<>/mono-debugger-libs-0+20131201.3459502'
> xbuild debugger-libs.sln
> XBuild Engine Version 12.0
> Mono, Version 4.2.1.0
> Copyright (C) 2005-2013 Various Mono authors
> 
> Unhandled Exception:
> System.IO.FileNotFoundException: Could not find file "/etc/localtime"
> File name: '/etc/localtime'
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, 
> FileOptions options) <0x7fa466d5d2c0 + 0x005ed> in :0 
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share) <0x7fa466d5cf30 + 0x0004b> in  unknown>:0 
>   at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor 
> (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
>   at System.IO.File.OpenRead (System.String path) <0x7fa466d5aa50 + 0x00034> 
> in :0 
>   at System.TimeZoneInfo.FindSystemTimeZoneByFileName (System.String id, 
> System.String filepath) <0x7fa466cbbfe0 + 0x00032> in :0 
>   at System.TimeZoneInfo.CreateLocal () <0x7fa466cba850 + 0x00176> in 
> :0 
>   at System.TimeZoneInfo.get_Local () <0x7fa466cba7c0 + 0x00025> in  unknown>:0 
>   at System.TimeZoneInfo.GetDateTimeNowUtcOffsetFromUtc (DateTime time, 
> System.Boolean& isAmbiguousLocalDst) <0x7fa466cbbce0 + 0x00017> in  unknown>:0 
>   at System.DateTime.get_Now () <0x7fa466b64260 + 0x00046> in  unknown>:0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine, System.String toolsVersion) 
> <0x40a987e0 + 0x00220> in :0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine) <0x40a98790 + 0x0001b> in 
> :0 
>   at Microsoft.Build.BuildEngine.Engine.CreateNewProject () <0x40a98740 + 
> 0x00037> in :0 
>   at Mono.XBuild.CommandLine.MainClass.Execute () <0x40a905d0 + 0x00be3> in 
> :0 
>   at Mono.XBuild.CommandLine.MainClass.Main (System.String[] args) 
> <0x40a8dd70 + 0x0008b> in :0 
> debian/rules:4: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/01/mono-debugger-libs_0+20131201.3459502-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
fixed 839424 mono/4.6.1.3+dfsg-2--- End Message ---

Bug#841247: [Calendarserver-maintainers] Bug#841247: calypso: UnicodeDecodeError when importing an .ics

[Mathias Behrle]

* Guido Günther: " Re: [Calendarserver-maintainers] Bug#841247: calypso:
  UnicodeDecodeError when importing an .ics" (Wed, 2 Nov 2016 21:30:21 +0100):

Hi Guido,

> Hi Mathias,
> 
> On Wed, Nov 02, 2016 at 01:14:02PM +0100, Mathias Behrle wrote:
> > control: affects -1 + tryton-modules-calendar
> > tryton-modules-calendar-classification tryton-modules-calendar-scheduling
> > tryton-modules-calendar-todo tryton-modules-party-vcarddav tryton-meta 
> > > From: Guido Günther 
> > > To: Jens Reyer , 841...@bugs.debian.org
> > > Subject: Re: Bug#841247: calypso: UnicodeDecodeError when importing
> > > an .ics Date: Sun, 23 Oct 2016 12:28:37 +0200  
> >  
> > 
> > Hi Guido,
> >   
> > > The unicode handling for python 2.7 got broken in upstream commit
> > > 
> > > 
> > > https://github.com/eventable/vobject/commit/b3f9bbcf4cf222f0dda3ac29f96364c5d7ab5f16
> > > 
> > > Let's see if upstream cares at all. If not we should rather drop the
> > > python2.7 version for stretch.  
> > 
> > There are currently 6 Tryton modules affected as rdepends of python-vobject.
> > There are still some bits in the Tryton framework lacking Python3 support,
> > so it is currently not possible to switch the whole Tryton stuff to Python3
> > (and I suppose this won't be the case for stretch). Dropping the Python2
> > version of python-vobject would seriously hurt those Tryton modules. So
> > please let's find a way to keep the Python2 version in the archive (for
> > stretch).  
> 
> It breaks calyso as well which I'd rather see in the archive than
> removed.
> 
> The bug is fixable. Someone needs to sit down and cook a patch. I have
> it on the TODO list but work is piling up at the moment - but I hope to
> get it done til the end of the year.

While I am currently not able to assist in making a patch I had a quite
intensive test with a complete Tryton calendar setup using vobject 0.9.3 under
Python2. It is working like a charm. So it seems the Tryton modules are
not *directly* affected by this bug.

I would want to elaborate the different measures to take now (time is running
away and the autoremoval is scheduled in 27 days).

For me the severity of this bug is definitely important, not grave. I think we
should downgrade the severity immediately. Would you agree with this?

As another measure to avoid the autoremoval of basically unaffected
Tryton modules it could be argued, that calypso is not ready for current vobject
and reassign the bug to calypso.

> Somebody uploading 0.8.x for python2 would be another option.

Would that be accepted?

Cheers,
Mathias

-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

Bug#844421: marked as done (rpmlint: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 13:34:13 +
with message-id 
and subject line Bug#844421: fixed in pycodestyle 2.2.0-1
has caused the Debian Bug report #844421,
regarding rpmlint: FTBFS (failing tests)
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.)


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

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f __version__.py
rm -f __isocodes__.py
ISO_3166_1_URL="file:///usr/share/iso-codes/json/iso_3166-1.json" \
ISO_639_3_URL="file:///usr/share/iso-codes/json/iso_639-3.json" \
dh_auto_build
make -j1

[... snipped ...]

test/test_scl.py::TestSCLBinary::test_scl_name_screwed_up PASSED
test/test_scl.py::TestSCLBinary::test_scl_forbidden_folders PASSED
test/test_scl.py::TestSCLBinary::test_scl_macros_outside_of_build PASSED

== 30 passed in 7.59 seconds ===
flake8 tests
./Config.py:84:1: E305 expected 2 blank lines after class or function 
definition, found 1
./Config.py:98:1: E305 expected 2 blank lines after class or function 
definition, found 1
./Config.py:112:1: E305 expected 2 blank lines after class or function 
definition, found 1
./Config.py:133:1: E305 expected 2 blank lines after class or function 
definition, found 1
./Config.py:143:1: E305 expected 2 blank lines after class or function 
definition, found 1
./PostCheck.py:194:1: E305 expected 2 blank lines after class or function 
definition, found 1
./FilesCheck.py:314:1: E305 expected 2 blank lines after class or function 
definition, found 1
./FilesCheck.py:1003:1: E305 expected 2 blank lines after class or function 
definition, found 1
./ConfigCheck.py:33:1: E305 expected 2 blank lines after class or function 
definition, found 1
./BinariesCheck.py:282:1: E305 expected 2 blank lines after class or function 
definition, found 1
./BinariesCheck.py:554:1: E305 expected 2 blank lines after class or function 
definition, found 1
./SignatureCheck.py:41:1: E305 expected 2 blank lines after class or function 
definition, found 1
./Pkg.py:69:1: E305 expected 2 blank lines after class or function definition, 
found 1
./Pkg.py:144:1: E305 expected 2 blank lines after class or function definition, 
found 1
./Pkg.py:198:1: E305 expected 2 blank lines after class or function definition, 
found 1
./RpmFileCheck.py:37:1: E305 expected 2 blank lines after class or function 
definition, found 1
./PamCheck.py:31:1: E305 expected 2 blank lines after class or function 
definition, found 1
./AbstractCheck.py:108:1: E305 expected 2 blank lines after class or function 
definition, found 1
./SpecCheck.py:40:1: E305 expected 2 blank lines after class or function 
definition, found 1
./SpecCheck.py:610:1: E305 expected 2 blank lines after class or function 
definition, found 1
./ZipCheck.py:26:1: E305 expected 2 blank lines after class or function 
definition, found 1
./NamingPolicyCheck.py:72:1: E305 expected 2 blank lines after class or 
function definition, found 1
./LSBCheck.py:43:1: E305 expected 2 blank lines after class or function 
definition, found 1
./I18NCheck.py:161:1: E305 expected 2 blank lines after class or function 
definition, found 1
./FHSCheck.py:53:1: E305 expected 2 blank lines after class or function 
definition, found 1
./MenuXDGCheck.py:66:1: E305 expected 2 blank lines after class or function 
definition, found 1
./SourceCheck.py:46:1: E305 expected 2 blank lines after class or function 
definition, found 1
./test/test.SpecCheck.py:34:1: E305 expected 2 blank lines after class or 
function definition, found 1
./test/test.SpecCheck2.py:20:1: E305 expected 2 blank lines after class or 
function definition, found 1
./test/test.Pkg.py:33:1: E305 expected 2 blank lines after class or function 
definition, found 1
./test/test.SpecCheck3.py:20:1: E305 expected 2 blank lines after class or 
function definition, found 1
./test/test.PamCheck.py:25:1: E305 expected 2 blank lines after class or 
function definition, found 1
Makefile:60: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving d

Bug#839318: marked as done (citus: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

[Debian Bug Tracking System]

Your message dated Thu, 17 Nov 2016 11:59:18 +0100
with message-id <20161117105918.w3f4sy3wofrjl...@msg.df7cb.de>
and subject line Re: Bug#839318: citus: FTBFS: Error: debian/control needs 
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #839318,
regarding citus: FTBFS: Error: debian/control needs updating from 
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)


-- 
839318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: citus
Version: 5.1.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> pg_buildext checkcontrol
> --- debian/control2016-07-07 18:43:03.0 +
> +++ debian/control.dtqrPH 2016-10-01 00:47:49.42400 +
> @@ -8,9 +8,9 @@
>  Homepage: https://github.com/citusdata/citus
>  XS-Testsuite: autopkgtest
>  
> -Package: postgresql-9.5-citus
> +Package: postgresql-9.6-citus
>  Architecture: any
> -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.5
> +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.6
>  Description: sharding and distributed joins for PostgreSQL
>   Citus is a distributed database implemented as a PostgreSQL extension. It
>   provides functions to easily split a PostgreSQL table into shards to be
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
> 'debian/control' failed
> make: *** [debian/control] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/citus_5.1.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 6.0.0.PGDG-1

Fixed earlier this week.

Christoph--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 844503 grave
Bug #844503 [salt] salt-call fails with libcrypto.so.1.1: undefined symbol: 
OPENSSL_no_config
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

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

Bug#844595: fbpanel: FTBFS: error: --ldflagsx=-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now -lglib-2.0 -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmod

[Chris Lamb]

Source: fbpanel
Version: 6.1-6
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

fbpanel fails to build from source in unstable/amd64:

  […]

  Preparing to unpack .../101-libcairo2-dev_1.14.6-1.1_amd64.deb ...
  Unpacking libcairo2-dev (1.14.6-1.1) ...
  Selecting previously unselected package libharfbuzz-icu0:amd64.
  Preparing to unpack .../102-libharfbuzz-icu0_1.2.7-1+b1_amd64.deb ...
  Unpacking libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Selecting previously unselected package libharfbuzz-gobject0:amd64.
  Preparing to unpack .../103-libharfbuzz-gobject0_1.2.7-1+b1_amd64.deb ...
  Unpacking libharfbuzz-gobject0:amd64 (1.2.7-1+b1) ...
  Selecting previously unselected package libgraphite2-dev.
  Preparing to unpack .../104-libgraphite2-dev_1.3.9-1_amd64.deb ...
  Unpacking libgraphite2-dev (1.3.9-1) ...
  Selecting previously unselected package icu-devtools.
  Preparing to unpack .../105-icu-devtools_57.1-4_amd64.deb ...
  Unpacking icu-devtools (57.1-4) ...
  Selecting previously unselected package libicu-dev.
  Preparing to unpack .../106-libicu-dev_57.1-4_amd64.deb ...
  Unpacking libicu-dev (57.1-4) ...
  Selecting previously unselected package libharfbuzz-dev:amd64.
  Preparing to unpack .../107-libharfbuzz-dev_1.2.7-1+b1_amd64.deb ...
  Unpacking libharfbuzz-dev:amd64 (1.2.7-1+b1) ...
  Selecting previously unselected package libxft-dev.
  Preparing to unpack .../108-libxft-dev_2.3.2-1_amd64.deb ...
  Unpacking libxft-dev (2.3.2-1) ...
  Selecting previously unselected package libpango1.0-dev.
  Preparing to unpack .../109-libpango1.0-dev_1.40.3-3_amd64.deb ...
  Unpacking libpango1.0-dev (1.40.3-3) ...
  Selecting previously unselected package libatk1.0-dev:amd64.
  Preparing to unpack .../110-libatk1.0-dev_2.22.0-1_amd64.deb ...
  Unpacking libatk1.0-dev:amd64 (2.22.0-1) ...
  Selecting previously unselected package x11proto-xinerama-dev.
  Preparing to unpack .../111-x11proto-xinerama-dev_1.2.1-2_all.deb ...
  Unpacking x11proto-xinerama-dev (1.2.1-2) ...
  Selecting previously unselected package libxinerama-dev:amd64.
  Preparing to unpack .../112-libxinerama-dev_2%3a1.1.3-1+b1_amd64.deb ...
  Unpacking libxinerama-dev:amd64 (2:1.1.3-1+b1) ...
  Selecting previously unselected package x11proto-fixes-dev.
  Preparing to unpack .../113-x11proto-fixes-dev_1%3a5.0-2_all.deb ...
  Unpacking x11proto-fixes-dev (1:5.0-2) ...
  Selecting previously unselected package libxfixes-dev:amd64.
  Preparing to unpack .../114-libxfixes-dev_1%3a5.0.2-1_amd64.deb ...
  Unpacking libxfixes-dev:amd64 (1:5.0.2-1) ...
  Selecting previously unselected package libxi-dev:amd64.
  Preparing to unpack .../115-libxi-dev_2%3a1.7.6-1.1_amd64.deb ...
  Unpacking libxi-dev:amd64 (2:1.7.6-1.1) ...
  Selecting previously unselected package x11proto-randr-dev.
  Preparing to unpack .../116-x11proto-randr-dev_1.5.0-1_all.deb ...
  Unpacking x11proto-randr-dev (1.5.0-1) ...
  Selecting previously unselected package libxrandr-dev:amd64.
  Preparing to unpack .../117-libxrandr-dev_2%3a1.5.0-1_amd64.deb ...
  Unpacking libxrandr-dev:amd64 (2:1.5.0-1) ...
  Selecting previously unselected package libxcursor-dev:amd64.
  Preparing to unpack .../118-libxcursor-dev_1%3a1.1.14-1+b1_amd64.deb ...
  Unpacking libxcursor-dev:amd64 (1:1.1.14-1+b1) ...
  Selecting previously unselected package x11proto-composite-dev.
  Preparing to unpack .../119-x11proto-composite-dev_1%3a0.4.2-2_all.deb ...
  Unpacking x11proto-composite-dev (1:0.4.2-2) ...
  Selecting previously unselected package libxcomposite-dev.
  Preparing to unpack .../120-libxcomposite-dev_1%3a0.4.4-1_amd64.deb ...
  Unpacking libxcomposite-dev (1:0.4.4-1) ...
  Selecting previously unselected package x11proto-damage-dev.
  Preparing to unpack .../121-x11proto-damage-dev_1%3a1.2.1-2_all.deb ...
  Unpacking x11proto-damage-dev (1:1.2.1-2) ...
  Selecting previously unselected package libxdamage-dev:amd64.
  Preparing to unpack .../122-libxdamage-dev_1%3a1.1.4-2+b1_amd64.deb ...
  Unpacking libxdamage-dev:amd64 (1:1.1.4-2+b1) ...
  Selecting previously unselected package libxml2-utils.
  Preparing to unpack .../123-libxml2-utils_2.9.4+dfsg1-2.1_amd64.deb ...
  Unpacking libxml2-utils (2.9.4+dfsg1-2.1) ...
  Selecting previously unselected package libgtk2.0-dev.
  Preparing to unpack .../124-libgtk2.0-dev_2.24.31-1_amd64.deb ...
  Unpacking libgtk2.0-dev (2.24.31-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../125-libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package libxt-dev:amd64.
  Preparing to unpack .../126-libxt-dev_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt-dev:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package libxmu6:amd64.
  Preparing to unpack .../127-libxmu6_2%3a1.1.2-2_amd64.deb ...
  Unpacking libxmu6:amd64

Processed: affects 844593 + erlang

[Debian Bug Tracking System]

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

> affects 844593 + erlang
Bug #844593 [erlang-wx] erlang-wx: WX broken due to "-fno-pie -no-pie" 
CFLAGS/LDFLAGS
Added indication that 844593 affects erlang
> thanks
Stopping processing here.

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

Bug#844593: [Pkg-erlang-devel] Bug#844593: erlang-wx: WX broken due to "-fno-pie -no-pie" CFLAGS/LDFLAGS

[Sergei Golovan]

Hi Johannes,

On Thu, Nov 17, 2016 at 12:30 PM, Johannes Weißl  wrote:
> Package: erlang-wx
> Version: 1:19.1.6+dfsg-1
> Severity: grave
> Tags: upstream patch
> Justification: renders package unusable
>
> The solution of bug #842998 breaks WX:
>
> 1> observer:start().
> {error,{{load_driver,"No driver found"},
> [{wxe_server,start,1,[{file,"wxe_server.erl"},{line,65}]},
>  {wx,new,1,[{file,"wx.erl"},{line,115}]},
>  {observer_wx,init,1,[{file,"observer_wx.erl"},{line,104}]},
>  {wx_object,init_it,6,[{file,"wx_object.erl"},{line,355}]},
>  {proc_lib,init_p_do_apply,3,
>[{file,"proc_lib.erl"},{line,247}]}]}}
>
> =ERROR REPORT 17-Nov-2016::10:12:15 ===
> ERROR: Could not find 'wxe_driver.so' in: 
> /usr/lib/erlang/lib/wx-1.7.1/priv

Sorry, I've missed this.

>
> What works is to remove "-fno-pie -no-pie" from CFLAGS and LDFLAGS in
> debian/rules and to apply the following two upstream patches:
>
> - 
> https://github.com/erlang/otp/commit/5aa13e16ae81050509fceaf603650fc8594af7ec.patch
> - 
> https://github.com/erlang/otp/commit/edfa3b87542687baa2530a41241eb83d9afda1fb.patch
>
> (both are necessary).

Thank you for the patches. I'll upload the updated package soon.

Cheers!
-- 
Sergei Golovan

Bug#844593: erlang-wx: WX broken due to "-fno-pie -no-pie" CFLAGS/LDFLAGS

[Johannes Weißl]

Package: erlang-wx
Version: 1:19.1.6+dfsg-1
Severity: grave
Tags: upstream patch
Justification: renders package unusable

The solution of bug #842998 breaks WX:

1> observer:start().
{error,{{load_driver,"No driver found"},
[{wxe_server,start,1,[{file,"wxe_server.erl"},{line,65}]},
 {wx,new,1,[{file,"wx.erl"},{line,115}]},
 {observer_wx,init,1,[{file,"observer_wx.erl"},{line,104}]},
 {wx_object,init_it,6,[{file,"wx_object.erl"},{line,355}]},
 {proc_lib,init_p_do_apply,3,
   [{file,"proc_lib.erl"},{line,247}]}]}}

=ERROR REPORT 17-Nov-2016::10:12:15 ===
ERROR: Could not find 'wxe_driver.so' in: /usr/lib/erlang/lib/wx-1.7.1/priv

What works is to remove "-fno-pie -no-pie" from CFLAGS and LDFLAGS in
debian/rules and to apply the following two upstream patches:

- 
https://github.com/erlang/otp/commit/5aa13e16ae81050509fceaf603650fc8594af7ec.patch
- 
https://github.com/erlang/otp/commit/edfa3b87542687baa2530a41241eb83d9afda1fb.patch

(both are necessary).



-- 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.8.0-1-amd64 (SMP w/4 CPU cores)
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 erlang-wx depends on:
ii  erlang-base-hipe  1:19.1.6+dfsg-1

erlang-wx recommends no packages.

Versions of packages erlang-wx suggests:
ii  erlang   1:19.1.6+dfsg-1
ii  erlang-doc   1:19.1.6+dfsg-1
ii  erlang-manpages  1:19.1.6+dfsg-1

-- no debconf information

Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Vincent Lefevre]

On 2016-11-17 14:36:08 +1300, Olly Betts wrote:
> In upstream wxWidgets, if the compile-time ABI and run-time ABI don't
> match, then you get an error and the app won't run, which is just not
> helpful.  In Debian we reduce that error to a warning - in practice I've
> never seen an actual problem due to this, but leaving the warning there
> means that this at least gets flagged as a potential issue.

A warning can be very annoying (e.g. because it mixes with other output
to the terminal) and possibly break scripts that don't expect output to
stderr. If this is not expected to work, then an error like upstreams's
behavior is the right thing to do (there is a real issue, and the user
must make sure that it gets fixed). Otherwise a warning isn't needed,
except in some debug mode for developers or andvanced users (but such
a mode would not be the default).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#844584: dhclient should perform additional validity checks

[Anton Ivanov]

Package: isc-dhcp-client
Version: 4.3.1-6+deb8u2
Severity: serious
File: /sbin/dhclient
Tags: security

https://samy.pl/poisontap/

This is a variation on an ancient "gem" by a DSL Modem vendor
where the router pretends to be the entire internet by spoofing
arp so that it captures all traffic.

The best way to deal with this is to set an upper limit on the
size of acceptable netmask in /etc/default/isc-dhcp-client and
verify it in a hook (which can be debian specific).

This way dhcp reply of 0.0.0.0/0 or anything larger than a class 
A will raise a security alert instead of blindly exposing the
machine to a spoofing attack.


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

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

Versions of packages isc-dhcp-client depends on:
ii  debianutils   4.4+b1
ii  iproute2  3.16.0-2
ii  isc-dhcp-common   4.3.1-6+deb8u2
ii  libc6 2.19-18+deb8u6
ii  libdns-export100  1:9.9.5.dfsg-9+deb8u7
ii  libirs-export91   1:9.9.5.dfsg-9+deb8u7
ii  libisc-export95   1:9.9.5.dfsg-9+deb8u7

isc-dhcp-client recommends no packages.

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd  
pn  resolvconf 

-- no debconf information