Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Thu, Oct 27, 2016 at 10:36:59AM -0700, Lars Tangvald wrote:
> Hi Salvatore,
> - car...@debian.org wrote:
> 
> > What is the status for src:mysql-5.5 for a possible jessie-security
> > upload? (Btw, if-and-only-if the package is still needed due to
> > rebuild, then let's please fix the changelog entry as well.)
> > 
> > Regards,
> > Salvatore
> 
> I thought I sent over the debdiffs a week ago, but must have messed
> that up, since I would have cc'ed it to the security team and list
> (but the reply I sent to Balint to answer the exact same question
> for wheezy, about an hour ago hasn't shown up in the bug yet
> either).

Okay :-/. Apparently at least that I did not recieved on my end.

> I think it should be good to go with the debdiff I've attached
> (source is also at
> https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/log/), but I
> can rebuild with a changelog edit if you'd prefer.

It looks good to me, so please go ahead with an upload (built with
-sa, to include the orig.tar.gz).

Regards,
Salvatore

Bug#828285: dogecoin: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Fri, Oct 28, 2016 at 12:53:51PM +0800, Keng-Yu Lin wrote:
> Built on my local machine with the latest sid, the failure is not
> reproducible any more.

Please note that it's still in experimental.


Kurt

Bug#842324: console-setup: During apt-get dist-upgrade stage, console-setup did not finish cleanly under ja_JP.UTF-8 locale.

[ishikawa]

Package: console-setup
Version: 1.152
Severity: critical
Tags: d-i l10n
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?

 I ran "apt-get dist-upgrade" to upgrade to testing repository.
 I ran "apt-get dist-upgrade" after "su" ing to the superuser.
 I am afraid that somehow LANG=ja_JP.UTF-8 setting seeped into the
 environment.
 In that environment, during the execution of
 console-setup, "iconv" failed due to illegal or invalid character
 code or something like that. I am afraid that I failed to log the
 operation successfully and so can't recall the exact message, but
 the failure is due to "iconv", this is for sure.
 I have experienced various "iconv" issues before, and
 thus I changed LANG to LANG=C after seeing the failure and
 ran "apt-get install console-setup" again, and this time
 it succeeded and so the "apt-get dist-upgrade" as a whole 
succeeded!


 On a different PC, I set LANG=C before running apt-get 
dist-upgrade, and found that it ran successfully the first time.



* What exactly did you do (or not do) that was effective (or
 ineffective)?
 Simply ran "apt-get dist-upgrade", and found console-setup failed
 due to the failure of "iconv" that was invoked during its 
execution.

 But setting LANG=C before running apt-get was the cure to solve
 the problem.

   * What was the outcome of this action?

 Failure to run console-setup successfully.

   * What outcome did you expect instead?
 console-setup to run to completion successfully.

*** End of the template - remove these template lines ***


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

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

Versions of packages console-setup depends on:
ii  console-setup-linux 1.152
ii  debconf 1.5.59
ii  keyboard-configuration  1.152
ii  xkb-data2.18-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.24-5
ii  lsb-base  9.20161016

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.59
ii  liblocale-gettext-perl  1.07-3+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.45
ii  initscripts 2.88dsf-59.8
ii  kbd 2.0.3-2
ii  keyboard-configuration  1.152

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2
ii  systemd   231-9

-- debconf information:
* keyboard-configuration/model: A4Tech KB-21
  console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/variant: Japanese
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/compose: No compose key
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_layout: true
  console-setup/codesetcode: Lat15
  console-setup/framebuffer_only:
  keyboard-configuration/unsupported_options: true
  console-setup/use_system_font:
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and 
Turkic languages

* keyboard-configuration/xkb-keymap: jp
  console-setup/fontsize: 8x16
* keyboard-configuration/layout:
  console-setup/guess_font:
  console-setup/fontface47: Fixed
* console-setup/charmap47: UTF-8
* keyboard-configuration/variantcode:
* keyboard-configuration/optionscode:
  console-setup/fontsize-fb47: 8x16
  keyboard-configuration/unsupported_layout: true
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/other:
* keyboard-configuration/layoutcode: jp
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/modelcode: a4techKB21
  console-setup/fontsize-text47: 8x16

Bug#840691: ghostscript and evince/libspectre problem

[Salvatore Bonaccorso]

On Thu, Oct 27, 2016 at 08:54:39PM -0400, Roberto C. Sánchez wrote:
> On Thu, Oct 27, 2016 at 11:43:01PM +0200, Francesco Poli wrote:
> > On Thu, 27 Oct 2016 18:17:20 +0200 Salvatore Bonaccorso wrote:
> > 
> > [...]
> > > On Thu, Oct 27, 2016 at 09:50:02AM -0400, Roberto C. Sánchez wrote:
> > > > Is your plan to release this as a -2 regression update to the previous
> > > > DSA?  I assume that is what you plan to do, but I wanted to confirm to
> > > > be certain.
> > > 
> > > Yes exactly, that's the plan. I would still like to hear Francesco's
> > > feedback before proceeding with a regression update.
> > 
> > I would love to help, but, as I said, I am unfortunately swamped:
> > I cannot promise any fast feedback for the time being.
> > Maybe I'll find some time for a test during the week-end, but this is
> > not a promise!   :-(
> > 
> 
> I have built wheezy packages with the patch and tested.  The PS file I
> used (from the MIT site in the original report) now renders correctly
> in evince and zathura without fault.

The 'ftp://publications.ai.mit.edu/ai-publications/500-999/AIM-864.ps'
PS actually crashes for me evince as well with 9.06~dfsg-2+deb8u1
(additionally, ans seemingly unrelated to the invalidaccess part), but
was able to verify the fix with other cases so far.

Regards,
Salvatore

Bug#828285: marked as done (dogecoin: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2016 12:53:51 +0800
with message-id 

and subject line Re: Bug#828285: dogecoin: FTBFS with openssl 1.1.0
has caused the Debian Bug report #828285,
regarding dogecoin: 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.)


-- 
828285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dogecoin
Version: 1.10.0-2
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/dogecoin_1.10.0-2_amd64-20160529-1415

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 ---
Built on my local machine with the latest sid, the failure is not
reproducible any more.
Closing the bug.

2016-06-26 18:21 GMT+08:00 Kurt Roeckx :
> Source: dogecoin
> Version: 1.10.0-2
> 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/dogecoin_1.10.0-2_amd64-20160529-1415
>
> 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 ---

Bug#840691: ghostscript and evince/libspectre problem

[Salvatore Bonaccorso]

Hi Francesco,

On Thu, Oct 27, 2016 at 11:43:01PM +0200, Francesco Poli wrote:
> On Thu, 27 Oct 2016 18:17:20 +0200 Salvatore Bonaccorso wrote:
> 
> [...]
> > On Thu, Oct 27, 2016 at 09:50:02AM -0400, Roberto C. Sánchez wrote:
> > > Is your plan to release this as a -2 regression update to the previous
> > > DSA?  I assume that is what you plan to do, but I wanted to confirm to
> > > be certain.
> > 
> > Yes exactly, that's the plan. I would still like to hear Francesco's
> > feedback before proceeding with a regression update.
> 
> I would love to help, but, as I said, I am unfortunately swamped:
> I cannot promise any fast feedback for the time being.
> Maybe I'll find some time for a test during the week-end, but this is
> not a promise!   :-(

Don't worry. I just wanted to be extra-sure. But I'm now confident
that should be the needed change. After some testing on my workplace
machine as well I will do the regression update (today or tomorrow
latest, unless some other problem arise).

Regards,
Salvatore

Processed: bug 823330 is forwarded to https://sourceforge.net/p/tsocks/bugs/27/

[Debian Bug Tracking System]

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

> forwarded 823330 https://sourceforge.net/p/tsocks/bugs/27/
Bug #823330 [tsocks] tsocks: The actual configure command disable host name 
resolution in tsocks.conf when it was supposed to enable it
Set Bug forwarded-to-address to 'https://sourceforge.net/p/tsocks/bugs/27/'.
> thanks
Stopping processing here.

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

Bug#842319: gnome-sushi: Missing dependency gir1.2-evince-3.0

[Kan-Ru Chen]

Package: gnome-sushi
Version: 3.21.91-1
Severity: grave
Justification: renders package unusable

Without gir1.2-evince-3.0 sushi always fail to start

% sushi

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/viewers/audio.js:31


** (sushi-start:10503): WARNING **: Unable to parse viewer audio.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring EvinceDocument, 
version none: Typelib file for namespace 'EvinceDocument' (any version) not 
found
@/usr/share/sushi/js/viewers/evince.js:26


** (sushi-start:10503): WARNING **: Unable to parse viewer evince.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/ui/fallbackRenderer.js:29
@/usr/share/sushi/js/ui/mimeHandler.js:26
@/usr/share/sushi/js/viewers/font.js:26


** (sushi-start:10503): WARNING **: Unable to parse viewer font.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/ui/fallbackRenderer.js:29
@/usr/share/sushi/js/ui/mimeHandler.js:26
@/usr/share/sushi/js/viewers/gst.js:37


** (sushi-start:10503): WARNING **: Unable to parse viewer gst.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/viewers/html.js:30


** (sushi-start:10503): WARNING **: Unable to parse viewer html.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/ui/fallbackRenderer.js:29
@/usr/share/sushi/js/ui/mimeHandler.js:26
@/usr/share/sushi/js/viewers/image.js:35


** (sushi-start:10503): WARNING **: Unable to parse viewer image.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/viewers/text.js:33


** (sushi-start:10503): WARNING **: Unable to parse viewer text.js: 
JS_EvaluateScript() failed

(sushi-start:10503): Gjs-WARNING **: JS ERROR: Error: Requiring Sushi, version 
none: Typelib file for namespace 'EvinceDocument', version '3.0' not found
@/usr/share/sushi/js/ui/mainWindow.js:37
@/usr/share/sushi/js/ui/application.js:32
@/usr/share/sushi/js/ui/main.js:29
@main.c:1


** (sushi-start:10503): ERROR **: Failed to load main javascript: 
JS_EvaluateScript() failed
zsh: trace trap  sushi

Fixed after install gir1.2-evince-3.0 manually

-- 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.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 gnome-sushi depends on:
ii  gir1.2-clutter-gst-3.03.0.20-1
ii  gir1.2-gtkclutter-1.0 1.8.2-1
ii  gir1.2-webkit2-4.02.14.1-1
ii  gstreamer1.0-plugins-good 1.8.3-1+b1
ii  libc6 2.24-5
ii  libcairo2 1.14.6-1+b1
ii  libclutter-1.0-0  1.26.0+dfsg-1
ii  libclutter-gst-3.0-0  3.0.20-1
ii  libclutter-gtk-1.0-0  1.8.2-1
ii  libevdocument3-4  3.22.1-2
ii  libevview3-3  3.22.1-2
ii  libfreetype6  2.6.3-3+b1
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libgirepository-1.0-1 1.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0]  1.46.0-1+b1
ii  libglib2.0-0  2.50.1-1
ii  libgstreamer-plugins-base1.0-01.8.3-1
ii  libgstreamer1.0-0 1.8.3-1
ii  libgtk-3-03.22.2-1
ii  libgtksourceview-3.0-13.22.0-1
ii  libharfbuzz0b 1.2.7-1+b1
ii  libmusicbrainz5-2 5.1.0+git20150707-6
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libx11-6  2:1.6.3-1
ii  nautilus  3.22.1-2

gnome-sushi recommends no packages.

Versions of packages gnome-sushi suggests:
ii  gstreamer1.0-libav  1.8.3-1

-- no debconf information

Bug#841665: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Bug#841665: fixed in boinc 7.6.33+dfsg-2)

[Mike Brennan]

Thank you Gainfranco, molte grazie.

On 23/10/16 22:00, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the boinc-client package:
>
> #841665: boinc-client: The boinc-client init script has a badly constructed 
> parameter for xhost
>
> It has been closed by Gianfranco Costamagna .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Gianfranco Costamagna 
>  by
> replying to this email.
>
>

Processed: tsocks: diff for NMU version 1.8beta5-9.5

[Debian Bug Tracking System]

Processing control commands:

> tags 815611 + patch
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Added tag(s) patch.
> tags 815611 + pending
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Added tag(s) pending.
> tags 823330 + patch
Bug #823330 [tsocks] tsocks: The actual configure command disable host name 
resolution in tsocks.conf when it was supposed to enable it
Added tag(s) patch.
> tags 823330 + pending
Bug #823330 [tsocks] tsocks: The actual configure command disable host name 
resolution in tsocks.conf when it was supposed to enable it
Added tag(s) pending.

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

Processed: tsocks: diff for NMU version 1.8beta5-9.5

[Debian Bug Tracking System]

Processing control commands:

> tags 815611 + patch
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815611 to the same tags previously set
> tags 815611 + pending
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815611 to the same tags previously set
> tags 823330 + patch
Bug #823330 [tsocks] tsocks: The actual configure command disable host name 
resolution in tsocks.conf when it was supposed to enable it
Ignoring request to alter tags of bug #823330 to the same tags previously set
> tags 823330 + pending
Bug #823330 [tsocks] tsocks: The actual configure command disable host name 
resolution in tsocks.conf when it was supposed to enable it
Ignoring request to alter tags of bug #823330 to the same tags previously set

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

Bug#815611: tsocks: diff for NMU version 1.8beta5-9.5

[gustavo panizzo (gfa)]

Control: tags 815611 + patch
Control: tags 815611 + pending
Control: tags 823330 + patch
Control: tags 823330 + pending

Dear maintainer,

I've prepared an NMU for tsocks (versioned as 1.8beta5-9.5)
I'll look for an sponsor and upload it

Regards.

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa
diff -Nru tsocks-1.8beta5/debian/changelog tsocks-1.8beta5/debian/changelog
--- tsocks-1.8beta5/debian/changelog	2016-03-01 01:40:38.0 +0800
+++ tsocks-1.8beta5/debian/changelog	2016-10-28 10:33:56.0 +0800
@@ -1,3 +1,13 @@
+tsocks (1.8beta5-9.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Removal of deprecated dh_undocumented debhelper command (Closes: #815611).
+  * Enable host name resolution on /etc/tsocks.conf at configure time,
+it was intended to be enabled in previous releases, but a bug in the
+configure script disabled it (Closes: #823330).
+
+ -- gustavo panizzo   Fri, 28 Oct 2016 10:33:56 +0800
+
 tsocks (1.8beta5-9.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru tsocks-1.8beta5/debian/patches/00list tsocks-1.8beta5/debian/patches/00list
--- tsocks-1.8beta5/debian/patches/00list	2011-10-02 14:37:03.0 +0800
+++ tsocks-1.8beta5/debian/patches/00list	2016-10-28 10:33:56.0 +0800
@@ -4,3 +4,4 @@
 04_getpeername
 05_config_in_home
 06_fallback
+07_tsocks-1.8_beta5-hostname-config-fix.patch
diff -Nru tsocks-1.8beta5/debian/patches/07_tsocks-1.8_beta5-hostname-config-fix.patch tsocks-1.8beta5/debian/patches/07_tsocks-1.8_beta5-hostname-config-fix.patch
--- tsocks-1.8beta5/debian/patches/07_tsocks-1.8_beta5-hostname-config-fix.patch	1970-01-01 08:00:00.0 +0800
+++ tsocks-1.8beta5/debian/patches/07_tsocks-1.8_beta5-hostname-config-fix.patch	2016-10-28 10:33:56.0 +0800
@@ -0,0 +1,25 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 07_tsocks-1.8_beta5-hostname-config-fix.patch by https://sourceforge.net/u/phobosk/profile/
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Enable host name resolution on /etc/tsocks.conf at configure time,
+## DP: this was intended to be enabled in previous releases, but a bug in the configure script
+## DP: made it impossible
+## DP: Poor's man DEP3 headers
+## DP: Origin: https://sourceforge.net/p/tsocks/bugs/27/
+## DP: Last-Update: 2016-10-28
+
+@DPATCH@
+--- tsocks-1.8.orig/configure.in
 tsocks-1.8/configure.in
+@@ -171,8 +171,8 @@
+   AC_DEFINE(ALLOW_MSG_OUTPUT)
+ fi
+ 
+-if test "x${enable_hostnames}" = "x"; then
+-  AC_DEFINE(HOSTNAMES)
++if test "${enable_hostnames}" = "yes"; then
++  AC_DEFINE(HOSTNAMES,1)
+ fi
+ 
+ if test "${enable_socksdns}" = "yes" -a \
diff -Nru tsocks-1.8beta5/debian/rules tsocks-1.8beta5/debian/rules
--- tsocks-1.8beta5/debian/rules	2016-02-29 22:08:47.0 +0800
+++ tsocks-1.8beta5/debian/rules	2016-10-28 10:33:56.0 +0800
@@ -69,7 +69,7 @@
 	dh_testdir
 
 #	dpkg-gencontrol -isp
-	dh_undocumented
+#	dh_undocumented
 	dh_installdocs
 
 	#dh_installdebconf


signature.asc
Description: PGP signature

Processed: Re: Bug#839379: yelp: FTBFS: segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:webkit2gtk 2.14.1-1
Bug #839379 [src:yelp] yelp: FTBFS: segmentation fault
Bug reassigned from package 'src:yelp' to 'src:webkit2gtk'.
No longer marked as found in versions yelp/3.22.0-1.
Ignoring request to alter fixed versions of bug #839379 to the same values 
previously set
Bug #839379 [src:webkit2gtk] yelp: FTBFS: segmentation fault
Marked as found in versions webkit2gtk/2.14.1-1.
> affects -1 src:yelp
Bug #839379 [src:webkit2gtk] yelp: FTBFS: segmentation fault
Added indication that 839379 affects src:yelp

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

Bug#839379: yelp: FTBFS: segmentation fault

[Michael Biebl]

Control: reassign -1 src:webkit2gtk 2.14.1-1
Control: affects -1 src:yelp

Am 28.10.2016 um 01:52 schrieb Michael Biebl:
> Am 01.10.2016 um 10:42 schrieb Lucas Nussbaum:
>>> (process:32124): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 
>>> 'GDK_IS_SCREEN (screen)' failed
>>>
>>> ** (process:32124): WARNING **: Unable to connect to dbus: Cannot spawn a 
>>> message bus without a machine-id: Unable to load /var/lib/dbus/machine-id 
>>> or /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such 
>>> file or directory
>>> Segmentation fault
> 
> Looks like a duplicate of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803104
> 
> Maybe webkit2gtk has regressed in that regard.


I built yelp inside a chroot (without X) and ran
docs/libyelp/libyelp-scan directly. The resulting backtrace from the
crash is attached. This looks to me like it's webkit2 related, so I'm
reassigning the bug. The dbus warning is a red herring fwiw.
The binary crashes even when installing dbus and running with
dbus-run-session.

Berto, would be great if you can have a look.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Starting program: /yelp-3.22.0/docs/libyelp/.libs/lt-libyelp-scan 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe0e20700 (LWP 23308)]

Thread 1 "lt-libyelp-scan" received signal SIGSEGV, Segmentation fault.
XQueryExtension (dpy=dpy@entry=0x0, name=name@entry=0x7fffe946b721 
 "Composite", 
major_opcode=major_opcode@entry=0x7fffda94, 
first_event=first_event@entry=0x7fffda98, 
first_error=first_error@entry=0x7fffda9c) at ../../src/QuExt.c:43
43  ../../src/QuExt.c: No such file or directory.
#0  0x7fffe96a60ad in XQueryExtension (dpy=dpy@entry=0x0, 
name=name@entry=0x7fffe946b721  "Composite", 
major_opcode=major_opcode@entry=0x7fffda94, 
first_event=first_event@entry=0x7fffda98, 
first_error=first_error@entry=0x7fffda9c) at ../../src/QuExt.c:43
rep = 
  {type = 0 '\000', pad1 = 0 '\000', sequenceNumber = 0, length = 0, 
present = 152 '\230', major_opcode = 218 '\332', first_event = 255 '\377', 
first_error = 255 '\377', pad3 = 32767, pad4 = 4294957716, pad5 = 32767, pad6 = 
3913725729, pad7 = 32767}
req = 
#1  0x7fffe9699e92 in XInitExtension (dpy=dpy@entry=0x0, 
name=name@entry=0x7fffe946b721  "Composite") at 
../../src/InitExt.c:47
codes = {extension = 48, major_opcode = 0, first_event = -375723504, 
first_error = 32767}
ext = 
#2  0x7fffe946afe0 in XCompositeFindDisplay (extinfo=0x7fffe966c090 
, ext_name=, dpy=0x0) at 
../../src/Xcomposite.c:111
info = 0x557c0a60
dpy = 0x0
info = 0x557c0a60
#3  0x7fffe946afe0 in XCompositeFindDisplay (dpy=0x0) at 
../../src/Xcomposite.c:208
dpy = 0x0
info = 0x557c0a60
#4  0x7fffe946b141 in XCompositeQueryExtension (dpy=, 
event_base_return=event_base_return@entry=0x7fffdb48, 
error_base_return=error_base_return@entry=0x7fffdb4c) at 
../../src/Xcomposite.c:219
info = 
#5  0x73e5dca3 in WebCore::PlatformDisplayX11::supportsXComposite() 
const (this=this@entry=0x7fffe05fd040)
at ./Source/WebCore/platform/graphics/x11/PlatformDisplayX11.cpp:80
eventBase = -202133058
errorBase = 32767
#6  0x730210bd in WebKit::WebPreferences::platformInitializeStore() 
(this=0x7fffe05f5000)
at ./Source/WebKit2/UIProcess/gtk/WebPreferencesGtk.cpp:63
damageBase = {m_isEngaged = false, m_value = {__data = "\377\177\000", 
__align = {}}}
#7  0x72e23b02 in WebKit::WebPreferences::create(WTF::String const&, 
WTF::String const&, WTF::String const&) (identifier=..., keyPrefix=..., 
globalDebugKeyPrefix=...) at ./Source/WebKit2/UIProcess/WebPreferences.cpp:43
#8  0x72fddc33 in webkit_settings_init(WebKitSettings*) 
(this=0x557aa590)
at ./Source/WebKit2/UIProcess/API/gtk/WebKitSettings.cpp:51
priv = 0x557aa590
#9  0x72fddc33 in webkit_settings_init(WebKitSettings*) 
(self=)
at ./Source/WebKit2/UIProcess/API/gtk/WebKitSettings.cpp:94
priv = 0x557aa590
#10 0x777b134b in g_type_create_instance (type=) at 
././gobject/gtype.c:1866
instance = 0x557aa5f0 [WebKitSettings]
class = 0x557bfbe0
allocated = 
private_size = 
ivar_size = 
i = 
#11 0x777931fb in g_object_new_internal 
(class=class@entry=0x557bfbe0, params=params@entry=0x7fffdee0, 
n_params=n_params@entry=1) at ././gobject/gobject.c:1783
nqueue = 0x0
object = 
__func__ = "g_object_new_internal"
#12 0x7779510e in g_object_new_valist (object_type=, 
first_property_name=first_property_name@entry=0x7725dab1 "default-charset", 
var_args=var_args@entry=0x7fffe030) at 

Bug#837629: OpenRD* with debian's u-boot 2016.09

[Rick Thomas]

On Oct 5, 2016, at 1:26 PM, Vagrant Cascadian  wrote:

> On 2016-10-03, Rick Thomas wrote:
>> On Oct 1, 2016, at 3:39 PM, Vagrant Cascadian  wrote:
>>> On 2016-09-17, Rick Thomas wrote:
 On Sep 16, 2016, at 3:19 PM, Vagrant Cascadian  wrote:
> https://bugs.debian.org/837629
> ...
>>> deb http://cascadia.debian.net/~vagrant/debian UNRELEASED main
>>> 
>>> The repository should be signed by my key, available in the
>>> debian-keyring package in the archive
>>> (F0ADA5240891831165DF98EA7CFCD8CD257721E9).
>>> 
>>> There were two critical fixes in 2016.09.01, *maybe* they fix the issue?
> 
> And now uploaded 2016.11~rc1 to my "UNRELEASED" repository, please test
> that...
> 
> 
>>> If not, I'll likely be removing OpenRD* from the packages on future
>>> uploads.
> ...
>> Sadly, it doesn’t look like it fixed the problem.  Still nothing after
>> installing the new u-boot.kwb and typing “reset”.
>> 
>> let me know if there’s anything more I can do to help…
> 
> If it's not fixed in 2016.11~rc1, the only thing left to try is git
> bisecting the issue...
> 
> 
> live well,
>  vagrant

Hi,

It’s been an “interesting” month (in the sense of the ancient curse: “May you 
live in interesting times!”)

Unfortunately testing u-boot on OpenRD fell by the wayside.
I gather that the current u-boot in experimental has OpenRD support removed?

But… as of now, all the “interesting” bits are temporarily under control.
Would you like me to test something?

Rick

Bug#840691: ghostscript and evince/libspectre problem

[Roberto C . Sánchez]

On Thu, Oct 27, 2016 at 11:43:01PM +0200, Francesco Poli wrote:
> On Thu, 27 Oct 2016 18:17:20 +0200 Salvatore Bonaccorso wrote:
> 
> [...]
> > On Thu, Oct 27, 2016 at 09:50:02AM -0400, Roberto C. Sánchez wrote:
> > > Is your plan to release this as a -2 regression update to the previous
> > > DSA?  I assume that is what you plan to do, but I wanted to confirm to
> > > be certain.
> > 
> > Yes exactly, that's the plan. I would still like to hear Francesco's
> > feedback before proceeding with a regression update.
> 
> I would love to help, but, as I said, I am unfortunately swamped:
> I cannot promise any fast feedback for the time being.
> Maybe I'll find some time for a test during the week-end, but this is
> not a promise!   :-(
> 

I have built wheezy packages with the patch and tested.  The PS file I
used (from the MIT site in the original report) now renders correctly
in evince and zathura without fault.

This certainly seems to address the regression.  I am ready to make an
upload to wheezy whenever the upload to jessie is ready.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Bug#842017: marked as done (haskell-hsopenssl-x509-system: FTBFS: '/usr/bin/haddock' exited with an error: Haddock failed (no modules?), refusing to create empty documentation package.)

[Debian Bug Tracking System]

Your message dated Fri, 28 Oct 2016 00:25:17 +
with message-id <20161028002517.ga6...@scru.org>
and subject line mathjax
has caused the Debian Bug report #842017,
regarding haskell-hsopenssl-x509-system: FTBFS: '/usr/bin/haddock' exited with 
an error: Haddock failed (no modules?), refusing to create empty documentation 
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.)


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

Dear Maintainer,

haskell-hsopenssl-x509-system fails to build from source in unstable/amd64:

  […]

  (Reading database ... 23467 files and directories currently installed.)
  Preparing to unpack 
haskell-hsopenssl-x509-system-build-deps_0.1.0.3-0_all.deb ...
  Unpacking haskell-hsopenssl-x509-system-build-deps (0.1.0.3-0) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs dctrl-tools dh-buildinfo ghc ghc-doc ghc-prof haskell-devscripts
haskell-devscripts-minimal hscolour html-xml-utils libbsd-dev libffi-dev
libghc-hsopenssl-dev libghc-hsopenssl-doc libghc-hsopenssl-prof
libghc-network-dev libghc-network-prof libghc-old-locale-dev
libghc-old-locale-prof libgmp-dev libgmpxx4ldbl libidn2-0 libncurses5-dev
libssl-dev libtinfo-dev zlib1g-dev
  Suggested packages:
debtags haskell-doc llvm-3.5 libghc-network-doc libghc-old-locale-doc
gmp-doc libgmp10-doc libmpfr-dev ncurses-doc
  Recommended packages:
libghc-network-doc libssl-doc
  The following NEW packages will be installed:
cdbs dctrl-tools dh-buildinfo ghc ghc-doc ghc-prof haskell-devscripts
haskell-devscripts-minimal hscolour html-xml-utils libbsd-dev libffi-dev
libghc-hsopenssl-dev libghc-hsopenssl-doc libghc-hsopenssl-prof
libghc-network-dev libghc-network-prof libghc-old-locale-dev
libghc-old-locale-prof libgmp-dev libgmpxx4ldbl libidn2-0 libncurses5-dev
libssl-dev libtinfo-dev zlib1g-dev
  0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 83.9 MB of archives.
  After this operation, 1065 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dctrl-tools amd64 
2.24-2 [101 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 dh-buildinfo all 
0.11+nmu1 [18.1 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libgmpxx4ldbl amd64 
2:6.1.1+dfsg-1 [22.3 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libgmp-dev amd64 
2:6.1.1+dfsg-1 [629 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libffi-dev amd64 
3.2.1-6 [161 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libbsd-dev amd64 
0.8.3-1 [178 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160917-1 [77.3 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libncurses5-dev amd64 
6.0+20160917-1 [173 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 ghc amd64 7.10.3-10 
[37.5 MB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.148 
[82.3 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 libidn2-0 amd64 
0.10-3 [68.9 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 html-xml-utils amd64 
7.1-1 [299 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 
haskell-devscripts-minimal all 0.12 [38.3 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 hscolour amd64 
1.24.1-1 [309 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 haskell-devscripts 
all 0.12 [15.4 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 ghc-prof amd64 
7.10.3-10 [32.1 MB]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libghc-network-dev 
amd64 2.6.3.1-1 [283 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 
libghc-old-locale-dev amd64 1.0.0.7-3 [32.7 kB]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
1:1.2.8.dfsg-2+b1 [206 kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libssl-dev amd64 
1.0.2j-1 [1541 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 libghc-hsopenssl-dev 
amd64 0.11.1.1-2+b1 [367 

Bug#839379: yelp: FTBFS: segmentation fault

[Michael Biebl]

Am 01.10.2016 um 10:42 schrieb Lucas Nussbaum:
>> (process:32124): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 
>> 'GDK_IS_SCREEN (screen)' failed
>>
>> ** (process:32124): WARNING **: Unable to connect to dbus: Cannot spawn a 
>> message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or 
>> /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such 
>> file or directory
>> Segmentation fault

Looks like a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803104

Maybe webkit2gtk has regressed in that regard.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#828610: marked as done (xrdp: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 23:34:28 +
with message-id <e1bzubo-00036p...@franck.debian.org>
and subject line Bug#828610: fixed in xrdp 0.9.0~20161027+gitc524b06-1
has caused the Debian Bug report #828610,
regarding xrdp: 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.)


-- 
828610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrdp
Version: 0.6.1-2
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/xrdp_0.6.1-2_amd64-20160529-1558

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: xrdp
Source-Version: 0.9.0~20161027+gitc524b06-1

We believe that the bug you reported is fixed in the latest version of
xrdp, 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 Glaser <t...@mirbsd.de> (supplier of updated xrdp 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: SHA384

Format: 1.8
Date: Thu, 27 Oct 2016 22:53:12 +0200
Source: xrdp
Binary: xrdp xorgxrdp
Architecture: source
Version: 0.9.0~20161027+gitc524b06-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Glaser <t...@mirbsd.de>
Changed-By: Thorsten Glaser <t...@mirbsd.de>
Description:
 xorgxrdp   - Remote Desktop Protocol (RDP) modules for X.org
 xrdp   - Remote Desktop Protocol (RDP) server
Closes: 828610 828868 836583
Changes:
 xrdp (0.9.0~20161027+gitc524b06-1) unstable; urgency=medium
 .
   * New upstream version 0.9.0~20161027+gitc524b06.
   * Remove unnecessary dh-systemd dependency.
   * Depend on lsb-base.
   * Suggest guacamole.
   * Fix build with OpenSSL 1.1.0. (Closes: #828610)
   * Be more aggressive when creating /var/run directories.
  + Fixes upgrade path from 0.6.1. (Closes: #828868)
   * Move old, duplicate pam config to new name.
  + Fixes upgrade path from 0.6.1. (Closes: #836583)
   * Fix VCS URLs.
Checksums-Sha1:
 3aa73f6937c9ac411717979db5b7861bbe85f744 2439 
xrdp_0.9.0~20161027+gitc524b06-1.dsc
 b35d6e356d317e452150d48e220bb815c7c1e767 1550280 
xrdp_0.9.0~20161027+gitc524b06.orig.tar.xz
 49993304d7f852d6478366533a4a0ee72e7fe456 30272 
xrdp_0.9.0~20161027+gitc524b06-1.debian.tar.xz
Checksums-Sha256:
 705138403f0ec504a8440bd30bbffe7c1ac0dc2646006c0843f31ee5f8fae568 2439 
xrdp_0.9.0~20161027+gitc524b06-1.dsc
 15f212e40d926f36a54d1034162f9965fc1537fc075e30ce875f914fc1f8a3d0 1550280 
xrdp_0.9.0~20161027+gitc524b06.orig.tar.xz
 e889230f07e0b50248218a13c4c4929b8eb114010baaea83d66a02be56090648 30272 
xrdp_0.9.0~20161027+gitc524b06-1.debian.tar.xz
Files:
 fcc1bb247ba765c02b67d02836356df4 2439 net optional 
xrdp_0.9.0~20161027+gitc524b06-1.dsc
 7c5d22d65e73ceae2969d2591ab00985 1550280 net optional 
xrdp_0.9.0~20161027+gitc524b06.orig.tar.xz
 d45d60b862610e8262e2430795898d89 30272 net optional 
xrdp_0.9.0~20161027+gitc524b06-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８　☕☂☄

iQIcBAEBCQAGBQJYEnzPAAoJEHa1NLLpkAfgzM8QAKxkM8pI1zu9Vw4tHxt94v2i
Co++g/BGEEIPNFgIx1UAYU0fEJ4GjtPI8hp2WO0LTMQYFirwNrdjfIugaUztLgng
trU/CeCVU82tJAdQfExzLycQ7D6/hUG9M/qkTGltVvPR0KGL3596fsYr4CMb9SWp
GhEVH8AoAfX9l39fdihq9t0HQqPzGHJMcmPzoofmNsqeP4OxMDuOMsZ/bQyNd/ya
LtN/Gv0yuYT5MTLrNcT9bh2ZPch2iaZQhJ8KfmnBaGg4OBLhy2EOVNCzNoQt6FT0
n707nYGZFEPkU/WYSPhMDG53ceiRiaoMzOMkihC0RPq4mEIcAkwAdzYGpsTybbSj
Biw+xsazn563bYH84oMlr9W7P41T2WIefXHGJRLH

Bug#842311: node-grunt-cli: uninstallable due to wrong dependency

[Alessandro Ghedini]

Package: node-grunt-cli
Version: 1.2.0-1
Severity: grave
Justification: renders package unusable

Hello,

when trying to install the package I get:

  The following packages have unmet dependencies:
   node-grunt-cli : Depends: node-findup-sync (>= 0.3.0) but 0.1.3-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

Cheers

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

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


signature.asc
Description: PGP signature

Processed: severity of 837786 is important ...

[Debian Bug Tracking System]

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

> severity 837786 important
Bug #837786 [mutter] mutter: Issues repainting the display on mouse movement
Severity set to 'important' from 'grave'
> retitle 837786 mutter: repaint issues/flickering when using 
> CLUTTER_PAINT=disable-clipped-redraws:disable-culling
Bug #837786 [mutter] mutter: Issues repainting the display on mouse movement
Changed Bug title to 'mutter: repaint issues/flickering when using 
CLUTTER_PAINT=disable-clipped-redraws:disable-culling' from 'mutter: Issues 
repainting the display on mouse movement'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#828245: Acknowledgement (balsa: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #828245 [src:balsa] balsa: FTBFS with openssl 1.1.0
Severity set to 'wishlist' from 'serious'
> retitle -1 balsa: Stop using deprecated openssl functions
Bug #828245 [src:balsa] balsa: FTBFS with openssl 1.1.0
Changed Bug title to 'balsa: Stop using deprecated openssl functions' from 
'balsa: FTBFS with openssl 1.1.0'.

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

Bug#828245: Acknowledgement (balsa: FTBFS with openssl 1.1.0)

[Michael Biebl]

Control: severity -1 wishlist
Control: retitle -1 balsa: Stop using deprecated openssl functions

On Sun, 3 Jul 2016 20:27:27 +0200 Kurt Roeckx  wrote:
> unblock 827061 by 828245
> thanks
> 
> After upstream changes it no longer FTBFS:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-07-02/successful/balsa_2.4.12-3_amd64-20160702-2206
> 
> It just has some warnings about deprecated functions you might
> want to address, or you could just close it.

Adjusting severity and title accordingly



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: reassign 836426 to libspice-client-gtk-3.0-5, severity of 836426 is important, fixed 836426 in 0.33-1

[Debian Bug Tracking System]

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

> reassign 836426 libspice-client-gtk-3.0-5 0.32-1
Bug #836426 [gnome-boxes] GTK+ 3.21 causes application redraw issues and 
warnings ("is drawn without a current allocation")
Bug reassigned from package 'gnome-boxes' to 'libspice-client-gtk-3.0-5'.
Ignoring request to alter found versions of bug #836426 to the same values 
previously set
Ignoring request to alter fixed versions of bug #836426 to the same values 
previously set
Bug #836426 [libspice-client-gtk-3.0-5] GTK+ 3.21 causes application redraw 
issues and warnings ("is drawn without a current allocation")
Marked as found in versions spice-gtk/0.32-1.
> severity 836426 important
Bug #836426 [libspice-client-gtk-3.0-5] GTK+ 3.21 causes application redraw 
issues and warnings ("is drawn without a current allocation")
Severity set to 'important' from 'serious'
> fixed 836426 0.33-1
Bug #836426 [libspice-client-gtk-3.0-5] GTK+ 3.21 causes application redraw 
issues and warnings ("is drawn without a current allocation")
Marked as fixed in versions spice-gtk/0.33-1.
> thanks
Stopping processing here.

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

Bug#837786: Severity of this bug

[Keshav Kini]

Hello,

This bug was originally marked with severity Grave, with justification
"causes non-serious data loss".  I don't see anyone in the thread
reporting data loss, including the OP.  Can this bug be bumped down to
Important, especially since it only affects a subset of users (those who
had the /etc/environment workaround set up on their systems)?  The
current severity of Grave makes this a release-critical bug which
prevents upgrade to Gnome 3.22.

-Keshav

Bug#839104: marked as done (libsfml-window2.4: unusable applications after XCB conversion)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 22:30:01 +
with message-id 
and subject line Bug#839104: fixed in libsfml 2.4.1~git15.b61c2f8+dfsg-1
has caused the Debian Bug report #839104,
regarding libsfml-window2.4: unusable applications after XCB conversion
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.)


-- 
839104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: extremetuxracer
Version: 0.7.3-2+b1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   launch extremetuxracer
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 none window is displayed, the screen is flashing
   * What was the outcome of this action?
   impossible to switch to other applications and to close
   extremetuxracer
   * What outcome did you expect instead?
   displaying the extremetuxracer window


-- 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.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages extremetuxracer depends on:
ii  extremetuxracer-data  0.7.3-2
ii  libc6 2.23-5
ii  libgcc1   1:6.1.1-11
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libsfml-audio2.4  2.4.0+dfsg-2
ii  libsfml-graphics2.4   2.4.0+dfsg-2
ii  libsfml-system2.4 2.4.0+dfsg-2
ii  libsfml-window2.4 2.4.0+dfsg-2
ii  libstdc++66.1.1-11

extremetuxracer recommends no packages.

extremetuxracer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libsfml
Source-Version: 2.4.1~git15.b61c2f8+dfsg-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libsfml 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, 27 Oct 2016 21:34:07 +0100
Source: libsfml
Binary: libsfml-dev libsfml-audio2.4 libsfml-graphics2.4 libsfml-network2.4 
libsfml-system2.4 libsfml-window2.4 libsfml-doc
Architecture: source
Version: 2.4.1~git15.b61c2f8+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: James Cowgill 
Description:
 libsfml-audio2.4 - Simple and Fast Multimedia Library - Audio part
 libsfml-dev - Simple and Fast Multimedia Library - Development Files
 libsfml-doc - Simple and Fast Multimedia Library - Documentation
 libsfml-graphics2.4 - Simple and Fast Multimedia Library - Graphics part
 libsfml-network2.4 - Simple and Fast Multimedia Library - Network part
 libsfml-system2.4 - Simple and Fast Multimedia Library - System part
 libsfml-window2.4 - Simple and Fast Multimedia Library - Window part
Closes: 839104
Changes:
 libsfml (2.4.1~git15.b61c2f8+dfsg-1) experimental; urgency=medium
 .
   * New upstream pre-release.
 - Reverts window implementation to X11 from XCB. (Closes: #839104)
 .
   * debian/control:
 - Update dependencies.
 - Ensure graphics 2.4 is not used with window 2.4.1.
   * debian/patches:
 - Refresh patches.
 - Drop 07_config-kfreebsd.patch - applied upstream.
 - Add 07_abi.patch to maintain SFML 2.4 ABI.
   * debian/rules:
 - Bump libsfml-window2.4 shlibs dependency.
   * debian/tests:
 - Fix autopkgtests on Ubuntu by depending on make in the cmake test.
Checksums-Sha1:
 b0a8e285ae261cfcd8667033b6d51b34518a414b 2715 
libsfml_2.4.1~git15.b61c2f8+dfsg-1.dsc
 66d28f7c04b48c339483a360bcbc9e856ae36cab 680460 
libsfml_2.4.1~git15.b61c2f8+dfsg.orig.tar.xz
 b1538a951e1894012aad1d2ab6c69e7b0546dfbc 18360 

Bug#828389: marked as done (libcrypt-smime-perl: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 22:28:45 +
with message-id 
and subject line Bug#828389: fixed in libcrypt-smime-perl 0.18-1
has caused the Debian Bug report #828389,
regarding libcrypt-smime-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.)


-- 
828389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-smime-perl
Version: 0.16-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-smime-perl_0.16-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-smime-perl
Source-Version: 0.18-1

We believe that the bug you reported is fixed in the latest version of
libcrypt-smime-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-smime-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, 27 Oct 2016 22:55:24 +0200
Source: libcrypt-smime-perl
Binary: libcrypt-smime-perl
Architecture: source
Version: 0.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 828389
Description: 
 libcrypt-smime-perl - S/MIME message signing, verification, encryption and 
decryption m
Changes:
 libcrypt-smime-perl (0.18-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 Fixes "FTBFS with openssl 1.1.0". (Closes: #828389)
   * Enable autopkgtest use.t test by adding
 debian/tests/pkg-perl/use-name.
Checksums-Sha1: 
 b836d3f4603231abdaffda3c54334ca0b64bae1b 2408 libcrypt-smime-perl_0.18-1.dsc
 c149ffefeb847316643401ad2aea10b9da339372 25632 
libcrypt-smime-perl_0.18.orig.tar.gz
 8d10c5c6fe8fc648259ac1851546ba08a1352523 2976 
libcrypt-smime-perl_0.18-1.debian.tar.xz
Checksums-Sha256: 
 a0c00e848c2d4996c57bc681933ffe8c562aebcd9baaf66b71edca0ad4528461 2408 
libcrypt-smime-perl_0.18-1.dsc
 472a81a78c28a8fb78a14691c1281838a71f7a87409a83eec4887af4e3d39dc5 25632 
libcrypt-smime-perl_0.18.orig.tar.gz
 2eb83d212228145f25baeba26e506052a47d3424d81388bd4c0f99faa6984629 2976 
libcrypt-smime-perl_0.18-1.debian.tar.xz
Files: 
 81fd9b6749facdbee5b2a2dfe9896dd1 2408 perl optional 
libcrypt-smime-perl_0.18-1.dsc
 dc37ffb82628e3f6b7c939a1fc17fa1d 25632 perl optional 
libcrypt-smime-perl_0.18.orig.tar.gz
 c0381f4f43a694f71a808b312d4cb2bc 2976 perl optional 
libcrypt-smime-perl_0.18-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYEmoRXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGVCwQALwJR1WXezgrum6Wf0ZBhFLs
gaYFEI9WTWfxvQbxESAtV4mq28oBXJbnh985lyMOc0XhKrJB/5xalAEne0TH+vgY
YIAQzqUgc53hyCkxhVFZMx8NkR60HpztRZc6Fsi0CfA+D5SujnkRDO4uOP12t5BX
9i96INemtFobH5cXF8nO92MdMX4yTJgRpti27l/2POv/VrnLZ4Tu7eZHsooDTsuC
++cnlPdN9Z15vCTKRKYzrkOebMzaSDBwfv5VUI/12ar5+nn+09NG3tKOQK0BtTFB
WBcjFxlWcZPQts/hGdPp6QEZOn+pMpek9sTrndt7hJImgQorDADzowvZduDk1QIN
JX0/2+ME7o65OXU5BAFVK9qjdQFoldQItw0SQQ1YMo75aDYBJe/0sMjwpCKnsWpd
IDp1Ovk4zyxeg4SUSwbWB8yCiLlY/CiwW9Di+fy5eSC3O/VpVbeuAGrJwlfqxcHl
8JaVJuyuzadDd1okt1QWoleSlOoUKEF8Ulp1ojxpaKp/MVQKTjDgpdAQwCZKwLAQ
ofWGtYT0EwAi4CDkBn1j8WctW/+SuYnKytY7gE2A3oNcuOtH4UMgDVdQY45qwZI/

Bug#828442: marked as done (mosquitto: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 22:30:38 +
with message-id 
and subject line Bug#828442: fixed in mosquitto 1.4.10-1
has caused the Debian Bug report #828442,
regarding mosquitto: 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.)


-- 
828442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mosquitto
Version: 1.4.8-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/mosquitto_1.4.8-1_amd64-20160529-1452

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: mosquitto
Source-Version: 1.4.10-1

We believe that the bug you reported is fixed in the latest version of
mosquitto, 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.
Roger A. Light  (supplier of updated mosquitto 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, 27 Oct 2016 14:01:40 +0100
Source: mosquitto
Binary: mosquitto mosquitto-dev libmosquitto1 libmosquitto-dev libmosquittopp1 
libmosquittopp-dev mosquitto-clients mosquitto-dbg libmosquitto1-dbg 
libmosquittopp1-dbg
Architecture: source
Version: 1.4.10-1
Distribution: unstable
Urgency: low
Maintainer: Roger A. Light 
Changed-By: Roger A. Light 
Description:
 libmosquitto-dev - MQTT version 3.1/3.1.1 client library, development files
 libmosquitto1 - MQTT version 3.1/3.1.1 client library
 libmosquitto1-dbg - debugging symbols for libmosquitto binaries
 libmosquittopp-dev - MQTT version 3.1 client C++ library, development files
 libmosquittopp1 - MQTT version 3.1/3.1.1 client C++ library
 libmosquittopp1-dbg - debugging symbols for libmosquittopp binaries
 mosquitto  - MQTT version 3.1/3.1.1 compatible message broker
 mosquitto-clients - Mosquitto command line MQTT clients
 mosquitto-dbg - debugging symbols for mosquitto binaries
 mosquitto-dev - Development files for Mosquitto
Closes: 824571 828442
Changes:
 mosquitto (1.4.10-1) unstable; urgency=low
 .
   * New upstream release.
   * Add support for openssl 1.1.0 (closes: #828442)
   * Fix FTBFS on Hurd (closes: #824571)
Checksums-Sha1:
 50e846dd58de204bf7f006e457f5dd3258430461 2533 mosquitto_1.4.10-1.dsc
 f09641cd34eddb6747bc3e7ffee64d2a7cfd6183 359569 mosquitto_1.4.10.orig.tar.gz
 1ff921e2058eccf175925949cf4efdb5cc9c4002 25184 mosquitto_1.4.10-1.debian.tar.xz
Checksums-Sha256:
 ec7522652e3aa91d4220a0690499a8e4f9969a836c75063e16d67d208a617af9 2533 
mosquitto_1.4.10-1.dsc
 437648d68a4a781dd8d913814cd5451f59ab4a5fcf84cccaf7c36e6a07459770 359569 
mosquitto_1.4.10.orig.tar.gz
 13e94c2848a334a95bb7587ca9299925c53716382102e0f7ae6d18cd6f2d9407 25184 
mosquitto_1.4.10-1.debian.tar.xz
Files:
 992012bc950104358343bbb4d63a64ea 2533 net optional mosquitto_1.4.10-1.dsc
 61839b47b58c5799aab76584f13ed66f 359569 net optional 
mosquitto_1.4.10.orig.tar.gz
 e4d48cffa8f692a06e38a0a70e43e8ff 25184 net optional 
mosquitto_1.4.10-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIbBAEBCAAGBQJYEmBvAAoJEPNPCXROn13ZwsQP92C01TRVy7IfMKkngEwS3HXl
3+GEO2PbZkHEbQGOk4iT96AbN/soisotJp5NtVabX43dF1h+GXEE+Srlj8Gli1U3
onVnpmp62MnzzQBLQ2PYoUL9q8xbzG4aU5K8l5L7f2sPKR93ctz+SLjsnH2WxP63
Ev9ZjykJw0CPLivgqK/29MJQOyxv8La8Ca7jBv8GR8lcTSW8fNQqArPYNwjVY5JX
kGZ69yNJIHsEU3zMxH1v8vE/RtxMbBLyije+GSdTl3zmHiH4IDPthb8buC7zS7aZ

Bug#842064: marked as done (libbabeltrace-ctf-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/babeltrace/ctf-writer/clock.h)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 22:21:00 +
with message-id 
and subject line Bug#842064: fixed in babeltrace 1.5.0~rc1-3
has caused the Debian Bug report #842064,
regarding libbabeltrace-ctf-dev: fails to upgrade from 'testing' - trying to 
overwrite /usr/include/babeltrace/ctf-writer/clock.h
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.)


-- 
842064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbabeltrace-ctf-dev
Version: 1.5.0~rc1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libbabeltrace-ctf-dev.
  Preparing to unpack .../2-libbabeltrace-ctf-dev_1.5.0~rc1-2_amd64.deb ...
  Unpacking libbabeltrace-ctf-dev (1.5.0~rc1-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-50DroU/2-libbabeltrace-ctf-dev_1.5.0~rc1-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/babeltrace/ctf-writer/clock.h', which is 
also in package libbabeltrace-dev 1.4.0-3
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-50DroU/2-libbabeltrace-ctf-dev_1.5.0~rc1-2_amd64.deb


cheers,

Andreas


libbabeltrace-dev=1.4.0-3_libbabeltrace-ctf-dev=1.5.0~rc1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: babeltrace
Source-Version: 1.5.0~rc1-3

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

Debian distribution maintenance software
pp.
Michael Jeanson  (supplier of updated babeltrace 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, 27 Oct 2016 17:21:08 -0400
Source: babeltrace
Binary: babeltrace libbabeltrace1 libbabeltrace-dev libbabeltrace-ctf1 
libbabeltrace-ctf-dev python3-babeltrace
Architecture: source
Version: 1.5.0~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Jon Bernard 
Changed-By: Michael Jeanson 
Description:
 babeltrace - Trace conversion program
 libbabeltrace-ctf-dev - Common Trace Format (CTF) development files
 libbabeltrace-ctf1 - Common Trace Format (CTF) library
 libbabeltrace-dev - Babeltrace development files
 libbabeltrace1 - Babeltrace conversion libraries
 python3-babeltrace - Babeltrace Python 3 bindings
Closes: 842064
Changes:
 babeltrace (1.5.0~rc1-3) unstable; urgency=medium
 .
   * [14b570a] Fix move of includes (Closes: #842064)
Checksums-Sha1:
 a0466eeb15d146a2f8ab6c25b242fdcfe8718cec 2467 babeltrace_1.5.0~rc1-3.dsc
 722e026a2f7a3575b40c2cf9463a628325aecf60 10660 
babeltrace_1.5.0~rc1-3.debian.tar.xz
Checksums-Sha256:
 f5faf227f88d110ed8a655a032b31f5e127da6e2c2ce2e7240a810f41bce99be 2467 
babeltrace_1.5.0~rc1-3.dsc
 14c93d9aa29ebd56d4a388e60797ebd9df6ee05feef3127e0076983501de0709 10660 
babeltrace_1.5.0~rc1-3.debian.tar.xz
Files:
 77d8851fc100f23f89f70a5f98bacafd 2467 libs extra babeltrace_1.5.0~rc1-3.dsc
 dfb60307a93963d6f2ddd5e22fb300e9 10660 libs extra 
babeltrace_1.5.0~rc1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Comment: GPGTools - https://gpgtools.org

iQIxBAEBCgAbBQJYEnAKFBxtamVhbnNvbkB1YnVudHUuY29tAAoJEIZWH0UhgPz+
hCEP/2GKOwTFBVAbMepTaap3YfCOPGtD9M8f7LJow/Gh3i3scZFIu1TXivFGTIiy
fjMXfh/vG2e+HgtB+QVfBsfDmL3wwGuofWVxCVNPuUSqeuA2A+jizVEP6+uX0ZE2
i4Fkikygq53vdNUxoFf1o/kMPUegBIz67NDcfFGVkXborIvHdDyg82vvtX8MEvOk
aIajdUktSDF0Lesqh89f5nOcV1YLqfRik4sMhPyIcC+HmM2i/twXcUawEkgh51LD
rxxJHuXRo7piWk/ABAayadhar9RicymIkheiyBQ9uzAbLFWTSIZLEnyHFD1XJ44e
WOcLy3kWrp0WsecTdmH8BkRLnGiAOuyElsPrugAUkhco0EITLBl+DXGyFpdpMonz
izofRHqFxwxYs8hQ3RxkrzqVJtL15zyeG6yBjP31DOdRAFYgR1JB47TMJxbF8Nlp

Bug#840691: ghostscript and evince/libspectre problem

[Francesco Poli]

On Thu, 27 Oct 2016 18:17:20 +0200 Salvatore Bonaccorso wrote:

[...]
> On Thu, Oct 27, 2016 at 09:50:02AM -0400, Roberto C. Sánchez wrote:
> > Is your plan to release this as a -2 regression update to the previous
> > DSA?  I assume that is what you plan to do, but I wanted to confirm to
> > be certain.
> 
> Yes exactly, that's the plan. I would still like to hear Francesco's
> feedback before proceeding with a regression update.

I would love to help, but, as I said, I am unfortunately swamped:
I cannot promise any fast feedback for the time being.
Maybe I'll find some time for a test during the week-end, but this is
not a promise!   :-(


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfMds4ewy9k.pgp
Description: PGP signature

Processed: Re: Bug#841708: debci: FTBFS with bash as /bin/sh

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841708 [src:debci] debci: FTBFS with bash as /bin/sh
Severity set to 'important' from 'serious'

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

Bug#841708: debci: FTBFS with bash as /bin/sh

[Antonio Terceiro]

Control: severity -1 important

Hi,

On Sat, Oct 22, 2016 at 03:15:40PM +0100, Chris Lamb wrote:
> Source: debci
> Version: 1.4
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> debci fails to build from source in unstable/amd64 when 
> /bin/sh is set to bash:

thanks for your bug report. I am sympathetic to users with bash as
/bin/sh, but dash has been the default for several releases now, and
even though I want to support having bash as /bin/sh, I do not think
that this qualifies as a serious bug as a system with bash as /bin/sh is
not exactly standard.

Any user with a standard Debian system can build the package just fine.


signature.asc
Description: PGP signature

Bug#839104: libsfml-window2.4: unusable applications after XCB conversion (was: extremetuxracer takes the focus but no windows is displayed...)

[James Cowgill]

Control: tags -1 pending

[+CC everyone affected by the bug]

Hi all,

On 27/10/16 11:28, James Cowgill wrote:
> On 27/10/16 05:56, Marko Lindqvist wrote:
>> Even my own build I last used a couple of months ago has broken this
>> way. I suspect it was broken either SFML (etr no longer uses SDL) or
>> gdm updates.
> 
> This reminded me of this bug in SFML which fixes a lot of glitches:
> https://github.com/SFML/SFML/pull/1138
> 
> Sure enough, applying that fixes extremetuxracer. SFML is planning a
> new release very soon (in fact I'm probably responsible for relaying it
> a few days). Hopefully this will be fixed fairly soon.

I have uploaded the 2.4.x git branch from upstream SFML to experimental
which should fix this issue. Can someone test it please? You may have to
wait a few hours from now before it appears on the mirrors.

I'll upload it to unstable when there's an actual release, which
shouldn't be too long now (ha).

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Bug#839104: libsfml-window2.4: unusable applications after XCB conversion (was: extremetuxracer takes the focus but no windows is displayed...)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #839104 [libsfml-window2.4] libsfml-window2.4: unusable applications after 
XCB conversion
Added tag(s) pending.

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

Processed: will be handled upstream

[Debian Bug Tracking System]

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

> forwarded 828308 https://sourceforge.net/p/gdcm/bugs/397/
Bug #828308 [src:gdcm] missing include for 'X509_STORE_CTX cert_ctx'
Set Bug forwarded-to-address to 'https://sourceforge.net/p/gdcm/bugs/397/'.
>
End of message, stopping processing here.

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

Bug#842303: [web2py] License problem and source missing

[Bastien ROUCARIÈS]

Package: web2py
Version: 2.12.3-1
Severity: serious
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org

Hi,

your package includes some files that seem to lack sources
in preferred forms of modification (analytic seems to be google analytic 
under non free license):
applications/admin/static/codemirror/addon/hint/html-hint.js line length is 
577 characters (>512)
applications/admin/static/codemirror/emmet.min.js
applications/admin/static/js/analytics.min.js
applications/admin/static/js/bootstrap.min.js
applications/admin/static/js/calendar.js line length is 32013 characters 
(>512)
applications/admin/static/js/dd_belatedpng.js line length is 6549 
characters (>512)
applications/admin/static/js/hogan-2.0.0.js line length is 5779 characters 
(>512)
applications/admin/static/js/jquery.flot.js line length is 2952 characters 
(>512)
applications/admin/static/js/jquery.flot.resize.js line length is 863 
characters (>512)
applications/admin/static/js/jquery.js line length is 32038 characters 
(>512)
applications/admin/static/js/modernizr.custom.js line length is 14752 
characters (>512)
applications/admin/static/js/share.js line length is 529 characters (>512)
applications/admin/static/js/typeahead.min.js
applications/admin/static/plugin_jqmobile/dd_belatedpng.js line length is 
6549 characters (>512)
applications/admin/static/plugin_jqmobile/jquery.mobile-1.2.0.min.js
applications/admin/static/plugin_jqmobile/jquery.mobile-1.3.1.min.js
applications/examples/static/js/analytics.min.js
applications/examples/static/js/bootstrap.min.js
applications/examples/static/js/calendar.js line length is 32013 characters 
(>512)
applications/examples/static/js/dd_belatedpng.js line length is 6549 
characters (>512)
applications/examples/static/js/jquery.js line length is 32038 characters 
(>512)
applications/examples/static/js/modernizr.custom.js line length is 14752 
characters (>512)
applications/examples/static/js/share.js line length is 529 characters 
(>512)
applications/welcome/static/js/analytics.min.js
applications/welcome/static/js/bootstrap.min.js
applications/welcome/static/js/calendar.js line length is 32013 characters 
(>512)
applications/welcome/static/js/jquery.js line length is 32038 characters 
(>512)
applications/welcome/static/js/modernizr-2.8.3.min.js
applications/welcome/static/js/respond-1.4.2.min.js
applications/welcome/static/js/share.js line length is 529 characters (>512)


According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1.  add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both way satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   full filling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.

[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract


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

Bug#828252: qtcreator is marked for autoremoval from testing

[Adam Majer]

On 27/10/16 09:59 AM, Ondřej Surý wrote:

I can probably generate two sets of packages with versioned symbols
if I have some help with that.

Cheers,



Yes, but this will not help and I'm not sure it is required since 
OpenSSL is versioned already.


The problem is that Qt5 is using dlopen for OpenSSL. Versioned symbols 
are not used with dlopen as is so we are SOL. Either Qt5 needs to be 
linked directly against OpenSSL, or Qt5 needs to use symbols from old 
OpenSSL library.


And now I'm looking at Qt source, and it looks like for Qt5 it is 
possible to specify SHLIB version number for OpenSSL. see


   qtbase/src/network/ssl/qsslsocket_openssl_symbols.cpp line 653

which means it *may be* possible to have multiple OpenSSL versions 
installed and have Qt use only the old version. But this needs to be 
tested with some test application to make sure correct functions are 
actually called.


SHLIB_VERSION_NUMBER = 1.0.2

during compilation of Qt maybe all that is required to keep Qt crypto 
support working in a mixed environment.


- Adam

Processed: bug 828610 is forwarded to https://github.com/neutrinolabs/xrdp/pull/459

[Debian Bug Tracking System]

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

> forwarded 828610 https://github.com/neutrinolabs/xrdp/pull/459
Bug #828610 [src:xrdp] xrdp: FTBFS with openssl 1.1.0
Set Bug forwarded-to-address to 'https://github.com/neutrinolabs/xrdp/pull/459'.
> thanks
Stopping processing here.

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

Processed: libcrypt-smime-perl: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #828389 [src:libcrypt-smime-perl] libcrypt-smime-perl: FTBFS with openssl 
1.1.0
Added tag(s) fixed-upstream and patch.
> forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=118344
Bug #828389 [src:libcrypt-smime-perl] libcrypt-smime-perl: FTBFS with openssl 
1.1.0
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=118344'.

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

Bug#828389: libcrypt-smime-perl: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch fixed-upstream
control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=118344

Crypt-SMIME-0.18 has the fix

Sebastian

Processed: tagging 828610

[Debian Bug Tracking System]

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

> tags 828610 + pending
Bug #828610 [src:xrdp] xrdp: FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#828466: Info received (opendkim: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

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

> tags 828466 patch
Bug #828466 [src:opendkim] opendkim: FTBFS with openssl 1.1.0
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#828466: opendkim: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

Control: tags - patch

builds. Further testing is welcome.

Sebastian
>From f6afa6be81eae0b149ad18a0642c67e75b148c69 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Thu, 27 Oct 2016 19:43:15 +
Subject: [PATCH] opendkim: port to openssl 1.1.0

In configure.ac AC_SEARCH_LIBS([SSL_library_init]) does not work as
expected because openssl 1.1.0 does not provide this function anymore.
Instead it is a macro pointing to another function so we need the
header file for this to work. Therefore it is replaced with
AC_LINK_IFELSE() where it is possible to add a header file.

OPENSSL_thread_stop() shouldn't be required. As of openssl 1.1.0 thread
managements is different and those function shouldn't be required
because openssl takes care of it. As per "NOTES" is is said, that it
might be requiired for staticaly linked code.

Signed-off-by: Sebastian Andrzej Siewior 
---
 configure.ac   | 40 +---
 opendkim/opendkim-crypto.c |  8 
 2 files changed, 29 insertions(+), 19 deletions(-)

diff --git a/configure.ac b/configure.ac
index 0370d43..0eec798 100644
--- a/configure.ac
+++ b/configure.ac
@@ -860,26 +860,28 @@ then
 	AC_SEARCH_LIBS([ERR_peek_error], [crypto], ,
 	   AC_MSG_ERROR([libcrypto not found]))
 
-	AC_SEARCH_LIBS([SSL_library_init], [ssl], ,
-		[
-			if test x"$enable_shared" = x"yes"
-			then
-AC_MSG_ERROR([Cannot build shared opendkim
-  against static openssl libraries.
-  Configure with --disable-shared
-  to get this working or obtain a
-  shared libssl library for
-  opendkim to use.])
-			fi
 
-			# avoid caching issue - last result of SSL_library_init
-			# shouldn't be cached for this next check
-			unset ac_cv_search_SSL_library_init
-			LIBCRYPTO_LIBS="$LIBCRYPTO_LIBS -ldl"
-			AC_SEARCH_LIBS([SSL_library_init], [ssl], ,
-			   AC_MSG_ERROR([libssl not found]), [-ldl])
-		]
-	)
+	AC_LINK_IFELSE(
+		   [AC_LANG_PROGRAM([[#include ]],
+	[[SSL_library_init();]])],
+	[od_have_ossl="yes";],
+	[od_have_ossl="no";])
+	if test x"$od_have_ossl" = x"no"
+	then
+		if test x"$enable_shared" = x"yes"
+		then
+			AC_MSG_ERROR([Cannot build shared opendkim
+			  against static openssl libraries.
+			  Configure with --disable-shared
+			  to get this working or obtain a
+			  shared libssl library for
+			  opendkim to use.])
+		fi
+
+		LIBCRYPTO_LIBS="$LIBCRYPTO_LIBS -ldl"
+		AC_SEARCH_LIBS([SSL_library_init], [ssl], ,
+		   AC_MSG_ERROR([libssl not found]), [-ldl])
+	fi
 
 	AC_CHECK_DECL([SHA256_DIGEST_LENGTH],
   AC_DEFINE([HAVE_SHA256], 1,
diff --git a/opendkim/opendkim-crypto.c b/opendkim/opendkim-crypto.c
index d78426d..ba82789 100644
--- a/opendkim/opendkim-crypto.c
+++ b/opendkim/opendkim-crypto.c
@@ -222,7 +222,11 @@ dkimf_crypto_free_id(void *ptr)
 	{
 		assert(pthread_setspecific(id_key, ptr) == 0);
 
+#if OPENSSL_VERSION_NUMBER >= 0x1010
+		OPENSSL_thread_stop();
+#else
 		ERR_remove_state(0);
+#endif
 
 		free(ptr);
 
@@ -392,11 +396,15 @@ dkimf_crypto_free(void)
 {
 	if (crypto_init_done)
 	{
+#if OPENSSL_VERSION_NUMBER >= 0x1010
+		OPENSSL_thread_stop();
+#else
 		CRYPTO_cleanup_all_ex_data();
 		CONF_modules_free();
 		EVP_cleanup();
 		ERR_free_strings();
 		ERR_remove_state(0);
+#endif
 
 		if (nmutexes > 0)
 		{
-- 
2.10.1

Bug#842295: nginx: CVE-2016-1247

[Salvatore Bonaccorso]

Source: nginx
Version: 1.6.2-5
Severity: grave
Tags: security
Justification: user security hole
Control: fixed -1 1.6.2-5+deb8u3

Hi,

the following vulnerability was published for nginx. This bug is to
track the CVE-2016-1247 as well in the Debian BTS.

CVE-2016-1247[0]:
www-data to root privilege escalation via log file handling

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1247

Regards,
Salvatore

Processed: nginx: CVE-2016-1247

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.6.2-5+deb8u3
Bug #842295 [src:nginx] nginx: CVE-2016-1247
Marked as fixed in versions nginx/1.6.2-5+deb8u3.

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

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Hilmar Preusse]

On 27.10.16 Mattia Rizzolo (mat...@debian.org) wrote:
> On Thu, Oct 27, 2016 at 02:07:17PM +0200, Hilmar Preuße wrote:

Hi,

> > Sorry to bother you again. The generated configure script seems to be broken
> > or incomplete:
> 
> arggg :(
> 
#842293, I've set you as submitter.

> IMHO, this should be handled upstream.
> I've now looked for the first time at the upstream git repo, and I see
> the "configure" file being there: it shouldn't.  All the artifacts of
> autotool are not supposed to be stored within a VCS, only generated at
> release time.  Though that one seems to be kept up to date with
> configure.in; clearly they are not doing the same with the rest of
> autotools-generated artifacts.
> 
> Considering that there are so many issues and maybe you want to upload
> soon rather than later, for me feel free to skip this point about
> autoreconf, but please try to get this fixed.
> 
Yes, I'll/we'll do so.

> btw, I peaked at the debian's git repository, and I saw that you used
> the git:// protocol in Vcs-Git; given that it's possible please avoid
> doing so, also see
> https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html
> 
Fixed i git. Sorry for misunderstanding.

Hilmar
-- 
sigmentation fault


signature.asc
Description: PGP signature

Processed: tagging 842276

[Debian Bug Tracking System]

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

> tags 842276 + confirmed pending
Bug #842276 [src:nginx] nginx-common.config dpkg --compare-versions will 
mishandle return codes should the check fail
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#841342: marked as done (zshdb: FTBFS under some locales (eg. fr_CH.UTF-8))

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 18:29:12 +
with message-id 
and subject line Bug#841342: fixed in zshdb 0.92-2
has caused the Debian Bug report #841342,
regarding zshdb: FTBFS under some locales (eg. fr_CH.UTF-8)
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.)


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


Dear Maintainer,

zshdb fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8").

The code already tries to work around this:

  54 # set the constants readonly
  55 shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  56 echo "${shunit_constants_}" |grep '^Binary file' >/dev/null && \
  57 shunit_constants_=`set |grep -a '^__SHUNIT_' |cut -d= -f1`

… but this doesn't work if the "Binary file" message is in, say, French :)

Changing this:

  - shunit_constants_=`set |grep '^__SHUNIT_' |cut -d= -f1`
  + shunit_constants_=`set |LC_ALL=C grep '^__SHUNIT_' |cut -d= -f1`

… makes this appear to work, but then you get other errors:

--- /tmp/setshow-filtered.check 2016-10-19 18:22:06.324491603 +0200
+++ zshdb-0.92/test/data/setshow.right  2016-07-06 18:47:42.0 +0200
@@ -1,4 +1,3 @@
-** pas un tty is not reputed to be a tty.
 (dbg-test2.sh:6):
 fn1 () { echo "fn1 here" x=5 fn3 }

etc. etc.

One solution (attached) is to simply set LC_ALL=C when running the
tests, but that suggests it would still fail at runtime and we are
just masking that issue? I would speak to upstream.

The full build log is attached.


Regards,

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


zshdb.0.92-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 5639f0e..a3b5d33 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,5 +11,5 @@ override_dh_auto_test:
# The tests make use of things like the history file, they need a dummy
# home directory.
mkdir test_homedir
-   HOME=$(shell pwd)/test_homedir dh_auto_test
+   LC_ALL=C HOME=$(shell pwd)/test_homedir dh_auto_test
rm -rf test_homedir
--- End Message ---
--- Begin Message ---
Source: zshdb
Source-Version: 0.92-2

We believe that the bug you reported is fixed in the latest version of
zshdb, 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.
Iain R. Learmonth  (supplier of updated zshdb 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, 27 Oct 2016 03:36:49 +0100
Source: zshdb
Binary: zshdb
Architecture: source all
Version: 0.92-2
Distribution: unstable
Urgency: medium
Maintainer: Iain R. Learmonth 
Changed-By: Iain R. Learmonth 
Description:
 zshdb  - debugger for Z-Shell scripts
Closes: 841342
Changes:
 zshdb (0.92-2) unstable; urgency=medium
 .
   * Force locale to C for the test suite. (Closes: #841342)
Checksums-Sha1:
 8e7ce70709f9f9c5113c70f8cefd6cb3b3836ccb 1486 zshdb_0.92-2.dsc
 0d8402752e923778c0568a98f4292accb41548a9 3672 zshdb_0.92-2.debian.tar.xz
 164081258a6b7e40786da16231cf9da6040775a8 103910 zshdb_0.92-2_all.deb
Checksums-Sha256:
 a0df7b95396eb6b4243f1b73eff14898ddb767ff31bbd360c810d6a8a7391e86 1486 
zshdb_0.92-2.dsc
 243ae19e77f60173b64c5e3e01455314445b6b23f15790bfca09612a989bf38d 3672 
zshdb_0.92-2.debian.tar.xz
 1cebc8d14a2a5a0c0370ae8a6fbb8bdac3ec0e9896545d6a985d5ead1d51de85 103910 
zshdb_0.92-2_all.deb
Files:
 76f36135bd58b4966b300714b4468a32 1486 devel extra zshdb_0.92-2.dsc
 89e646b43bda6edf3b42a9bbcb06fe82 3672 devel extra zshdb_0.92-2.debian.tar.xz
 a50d06758c3f49ab2e12b9d087e44ad6 103910 devel extra zshdb_0.92-2_all.deb

-BEGIN PGP SIGNATURE-

Processed: Merge #840786 & #841584

[Debian Bug Tracking System]

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

> severity 840786 serious
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Severity set to 'serious' from 'important'
> tags 840786 sid stretch
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Added tag(s) sid and stretch.
> tags 841584 patch
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Added tag(s) patch.
> merge 840786 841584
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Merged 840786 841584
> thanks
Stopping processing here.

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

Bug#842184: policykit-1: synaptic-pkexec no more work

[Brian Vaughan]

I can confirm that:

A) Executing
'/usr/lib/x86_64-linux-gnu/polkit-gnome-authentication-agent-1' on the
command line enabled the expected dialog for launching Synaptic from XFCE;

B) The issue has been resolved with policykit-1-gnome 0.105-5.

Thank you.

On Oct 27, 2016 2:00 AM, "Simon McVittie"  wrote:

> Control: reassign 842184 policykit-1-gnome 0.105-4
> Control: severity 842184 serious
>
> On Thu, 27 Oct 2016 at 07:27:05 +, Grand T wrote:
> > The error is in  policykit-1-gnome 0.105-4
> >
> >  /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop refer to
> >
> > Exec=/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
> >
> > but it don't exist so it is not started !
> >
> > The exec is now at/usr/lib/x86_64-linux-gnu/polkit-gnome-authentication-
> agent-1
> >
> > I modified
> >
> > /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop to set up
> > Exec=/usr/lib/x86_64-linux-gnu/polkit-gnome-authentication-agent-1
>
> Good catch! It looks as though this was caused by modernizing the
> packaging of policykit-1-gnome from debhelper 8 to 10, which changed its
> ${libexecdir}, without also updating
> debian/polkit-gnome-authentication-agent-1.desktop to use the new
> value of ${libexecdir}.
>
> So this is not actually a policykit-1 bug, but rather policykit-1-gnome,
> which is a separate source package. Contrary to its name, pk-1-gnome
> is not actually used in "full" GNOME any more (because GNOME Shell has
> its own built-in polkit agent), but it does get used in XFCE, Unity and
> GNOME Flashback.
>
> Brian (and anyone else who is seeing #841878), are you using
> policykit-1-gnome as your implementation of a polkit agent? If you
> run /usr/lib/x86_64-linux-gnu/polkit-gnome-authentication-agent-1
> "by hand" from a terminal, does authentication work normally for you?
>
> (If you have edited /etc/xdg/autostart/polkit-
> gnome-authentication-agent-1.desktop
> as a workaround, you will probably need to edit it again, or go back to
> the version provided by the package maintainer, after this bug is fixed -
> we will probably choose a different location for the authentication agent,
> or go back to its old location, because the architecture-dependent path is
> awkward to use in the packaging.)
>
> Thanks,
> S
>

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:sqlobject
> # 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 #841596 (http://bugs.debian.org/841596)
> # Bug title: sqlobject: FTBFS: tests failed
> #  * https://github.com/sqlobject/sqlobject/issues/128
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 841596 + fixed-upstream
Bug #841596 [src:sqlobject] sqlobject: FTBFS: tests failed
Added tag(s) fixed-upstream.
> usertags 841596 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:jasper
> # 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 #841110 (http://bugs.debian.org/841110)
> # Bug title: jasper: CVE-2016-8693
> #  * https://github.com/mdadams/jasper/issues/32
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 841110 + fixed-upstream
Bug #841110 [src:jasper] jasper: CVE-2016-8693
Added tag(s) fixed-upstream.
> usertags 841110 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#842171: marked as done (musl: CVE-2016-8859: Regex integer overflow in buffer size computations)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 17:41:47 +
with message-id 
and subject line Bug#842171: fixed in musl 1.1.15-2
has caused the Debian Bug report #842171,
regarding musl: CVE-2016-8859: Regex integer overflow in buffer size 
computations
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.)


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

Hi,

the following vulnerability was published for musl.

CVE-2016-8859[0]:
Regex integer overflow in buffer size computations

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8859
[1] http://www.openwall.com/lists/oss-security/2016/10/19/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: musl
Source-Version: 1.1.15-2

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated musl 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, 27 Oct 2016 18:53:49 +0200
Source: musl
Binary: musl musl-dev musl-tools
Architecture: source
Version: 1.1.15-2
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Description:
 musl   - standard C library
 musl-dev   - standard C library development files
 musl-tools - standard C library tools
Closes: 842171
Changes:
 musl (1.1.15-2) unstable; urgency=high
 .
   * Cherry-pick upstream fix for regex integer overflow in buffer size
 computations; CVE-2016-8859 (Closes: #842171)
Checksums-Sha1:
 6c3c41416769520898c001be212397ad5072f270 2787 musl_1.1.15-2.dsc
 027c3ae2182fa53c2b554ca98a28dc5cfca4b2c3 911600 musl_1.1.15.orig.tar.gz
 e2fb3d9270da73ebb45c67a5d1ae4117b5fd4170 490 musl_1.1.15.orig.tar.gz.asc
 bde3025de47947e6e312243262e79338f4350c48 10876 musl_1.1.15-2.debian.tar.xz
Checksums-Sha256:
 e0f867988755a1d19255d675db3c8931347f5d296a812b9c7e0c23ebf11cbe9a 2787 
musl_1.1.15-2.dsc
 97e447c7ee2a7f613186ec54a93054fe15469fe34d7d323080f7ef38f5ecb0fa 911600 
musl_1.1.15.orig.tar.gz
 9c9f0ce169a96f9214adc3c8f4261b10d6742ff5061fd6589bbe5789c1d3d6aa 490 
musl_1.1.15.orig.tar.gz.asc
 31ae73e4ab8563e0322f641e468dc4f6ba6ab8caba1e58b267a80b073a3139ca 10876 
musl_1.1.15-2.debian.tar.xz
Files:
 fc23202ad63a62375fd1c3a10af8a7ec 2787 libs extra musl_1.1.15-2.dsc
 9590a9d47ee64f220b3c12f7afb864ca 911600 libs extra musl_1.1.15.orig.tar.gz
 605ab8dd3de1d080dd6b0c1c6c192361 490 libs extra musl_1.1.15.orig.tar.gz.asc
 2bf6319342188abfc189f2321355b6b0 10876 libs extra musl_1.1.15-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYEjSpAAoJEMzwSSjbDuqnb34QAK7VhUyTYZrzcsnUZmpMj35i
YZiFKe16kcPsbeUyEpuIZMXSEMS0SwKtG87xJAk5fBepJyx5Lmg626OmdPxR+o7R
BYeGT8nJQNAOnZCyMucBjYn1RUGwwVeHvuPBUKfmYAsjRrfbeoir1UEr2g+WheOq
zz7ysYNeUQn5QtS7eMLOTBbUDYPcmvdZmA5nW+szJ8GE44yjGJwoUY9cFdLDgu3W
yxoQNhmqBEmgI7p/+cRomRSfbuJHrUZw+u0BT9IITIHwglfvsaKqeN0ir0nIgYiQ
ZYpbO7qt4YgBuUlePRCfDQfN95KeY3TMQk2nQqMe7roM2AMHNJvzmyKSNarnvxvN
LYa3IDauIfO75wV7z4+EM4+TfZf7CL3E9FKTxxNzyTFqSz5Dy9VYL2DWssEApvS2
HZZ/qjnjTWDKt1a+0DYNHX3/YxtVXzR8j4bElUfyP6HfP+xGupmy7FEB6UnDeYet
2KiiNoPCM4mqLX9y8Qd10IixiabwGCrxJMPUtOCLuQw8wEccL0sdiozyVtXMtsdv
zp1OvJBnV3bWpO4T89vg6S88lGf/qCRuXVp7GhcIm3LEhl23GPjNv92csJHvAsaO
F+ZhLwz1T/LmrVteRVisYTR0ZlfN4KSeH/WOnnszewjl+7IE8vvsPl6bbkTjl7OA
HDY2pQwByc5edZ+9zKPe
=lYQz
-END PGP SIGNATURE End Message ---

Bug#837574: marked as done (qemu: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 17:42:05 +
with message-id 
and subject line Bug#837574: fixed in qemu 1:2.7+dfsg-3
has caused the Debian Bug report #837574,
regarding qemu: 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.)


-- 
837574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 2.6+dfsg-3
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):
...
cc -I/<>/qemu-2.6+dfsg/tcg
-I/<>/qemu-2.6+dfsg/tcg/i386
-I/<>/qemu-2.6+dfsg/linux-headers
-I/<>/qemu-2.6+dfsg/qemu-build/linux-headers -I.
-I/<>/qemu-2.6+dfsg -I/<>/qemu-2.6+dfsg/include
-I/<>/qemu-2.6+dfsg/block -Iblock -I/usr/include/pixman-1
-DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes
-Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes
-fno-strict-aliasing -fno-common  -g -O2
-fdebug-prefix-map=/<>/qemu-2.6+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2
-DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
-DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body
-Wnested-externs -Wformat-security -Wformat-y2k -Winit-self
-Wignored-qualifiers -Wold-style-declaration -Wold-style-definition
-Wtype-limits -fstack-protector-strong  -I/usr/include/p11-kit-1
-I/usr/include/libpng16 -I/usr/include/spice-server
-I/usr/include/spice-1 -I/usr/include/cacard -I/usr/include/libusb-1.0
-I/<>/qemu-2.6+dfsg/tests -MMD -MP -MT block/iscsi.o -MF
block/iscsi.d -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-pthread -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g  -fPIC -DBUILD_DSO  -c
-o block/iscsi.o /<>/qemu-2.6+dfsg/block/iscsi.c
cc -nostdlib -Wl,-r  -o block/iscsi.mo block/iscsi.o
/usr/bin/ld: -r and -pie may not be used together
collect2: error: ld returned 1 exit status
/<>/qemu-2.6+dfsg/rules.mak:99: recipe for target
'block/iscsi.mo' failed
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/qemu_2.6+dfsg-3_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.7+dfsg-3

We believe that the bug you reported is fixed in the latest version of
qemu, 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.
Michael Tokarev  (supplier of updated qemu 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, 27 Oct 2016 19:38:01 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.7+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system 

Bug#828427: marked as done (lua-sec: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 17:03:30 +
with message-id 
and subject line Bug#828427: fixed in lua-sec 0.6-1
has caused the Debian Bug report #828427,
regarding lua-sec: 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.)


-- 
828427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-sec
Version: 0.5.1-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/lua-sec_0.5.1-1_amd64-20160529-1447

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: lua-sec
Source-Version: 0.6-1

We believe that the bug you reported is fixed in the latest version of
lua-sec, 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.
Ondřej Surý  (supplier of updated lua-sec 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, 27 Oct 2016 17:16:10 +0200
Source: lua-sec
Binary: lua-sec lua-sec-dev
Architecture: source
Version: 0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Enrico Tassi 
Changed-By: Ondřej Surý 
Description:
 lua-sec- SSL socket library for the Lua language
 lua-sec-dev - SSL socket library library devel files for the Lua language
Closes: 828427
Changes:
 lua-sec (0.6-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.6
   * Add OpenSSL 1.1.0 patch from upstream (Closes: #828427)
Checksums-Sha1:
 fdbf3edeb1c513cf01f2231a49c01eccc75d55a8 2048 lua-sec_0.6-1.dsc
 3204c0ac99f7be1952ad8f1157e83cc513491cb4 51071 lua-sec_0.6.orig.tar.gz
 01fddeca7b470565125f597d6da46ebff8d87ff4 4972 lua-sec_0.6-1.debian.tar.xz
Checksums-Sha256:
 7d6df8dcea463bce4f1505a9b9ae2cc6028e6b81ca9d8058a9e19251b2c7a30f 2048 
lua-sec_0.6-1.dsc
 cef3a35c18beb8a54d9c8ce6260a4cabbd9a386de8711320d084daffad0aed5d 51071 
lua-sec_0.6.orig.tar.gz
 57a2cb2228cb838c43214eb36e2006cc335e728332f88b0a806f17abe1ac58a6 4972 
lua-sec_0.6-1.debian.tar.xz
Files:
 c629036a31a38b5a29eb7780f24498bf 2048 interpreters optional lua-sec_0.6-1.dsc
 14e1aef6d2aae96bbf98afc6b6634af2 51071 interpreters optional 
lua-sec_0.6.orig.tar.gz
 f3e43d530e843dcb0dd61fa7343efdd6 4972 interpreters optional 
lua-sec_0.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYEhwiXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHkDoQAKPNN5suMR5mweyIPYzdeIA9
c/dy4oB4ZBfp4n+OlBRAk3ASgbBVXzlIe913MuRrpXGA3bPeNSm1x+59whLtVbCX
PO0PlnTEDW4q0jdszpWW3h2kcjUmDmBGKotUEWtVo4Q9ArKjuFPdVSiNQAwTOgJM
I96vLgPUt/GiFsFugAnog1eM6/8uNl95wksVxpM1ItjnFB276YYEV6iMCe71J2A7
tzlHEoHi6g8DThz+ROaYB2e9IJYxSQBrLe1RFGG/zkj7PJicZnrNH2UaR1kabwt7
+968S0ILoP1hQnEifa6ZQ9Ykq/MA3SLylB6k13hhYpQmUxThGVKUynXW3N8gldTR
HygQSyYnbHgfdwzkKho27pb+N+RU9N9aDdvKRMt8F6GuO98vKUS8hWNNG2/06B3j
KMf/TpustNaKabPrcvstNbxB/n0Djy+GGA3kp3q2kv7urz9YGB1iROplTW6IGayO
rg4R/h2ymrKWGTAO1gVyWYc5GzLggQHnphxUzW1Oyxk7D/wBr0x2GVJVBqOXP5Kt
p9NsBlvVse3sKZbJaeyD67XOmkvVIIdLyUl7B/f1f1aORxW529ee9pSGtoRXLWN/
kM35gkPVyVp5/aLyUu6AJLs8vzV6WBHyZlVj3eeyRC0ASHW7inqxp0n6lTeRqEyq
cUexmyh8iuprTHsdpNWz
=23YC
-END PGP SIGNATURE End Message ---

Bug#828361: marked as done (kamailio: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 16:58:01 +
with message-id 
and subject line Bug#828361: fixed in kamailio 4.4.3-2
has caused the Debian Bug report #828361,
regarding kamailio: 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.)


-- 
828361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kamailio
Version: 4.4.1-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/kamailio_4.4.1-1_amd64-20160530-2110

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: kamailio
Source-Version: 4.4.3-2

We believe that the bug you reported is fixed in the latest version of
kamailio, 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.
Victor Seva  (supplier of updated kamailio 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, 27 Oct 2016 17:51:44 +0200
Source: kamailio
Binary: kamailio kamailio-dbg kamailio-geoip-modules kamailio-sqlite-modules 
kamailio-json-modules kamailio-memcached-modules kamailio-lua-modules 
kamailio-mono-modules kamailio-python-modules kamailio-redis-modules 
kamailio-mysql-modules kamailio-postgres-modules kamailio-cpl-modules 
kamailio-radius-modules kamailio-unixodbc-modules kamailio-presence-modules 
kamailio-perl-modules kamailio-snmpstats-modules kamailio-purple-modules 
kamailio-xmpp-modules kamailio-xml-modules kamailio-carrierroute-modules 
kamailio-berkeley-modules kamailio-berkeley-bin kamailio-ldap-modules 
kamailio-ims-modules kamailio-utils-modules kamailio-sctp-modules 
kamailio-java-modules kamailio-tls-modules kamailio-outbound-modules 
kamailio-websocket-modules kamailio-dnssec-modules kamailio-autheph-modules 
kamailio-kazoo-modules kamailio-cnxcc-modules kamailio-erlang-modules 
kamailio-extra-modules
Architecture: source amd64
Version: 4.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Victor Seva 
Description:
 kamailio   - very fast and configurable SIP proxy
 kamailio-autheph-modules - authentication using ephemeral credentials module 
for Kamailio
 kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program
 kamailio-berkeley-modules - Berkeley database module for Kamailio
 kamailio-carrierroute-modules - carrierroute module for Kamailio
 kamailio-cnxcc-modules - cnxcc modules for Kamailio
 kamailio-cpl-modules - CPL module (CPL interpreter engine) for Kamailio
 kamailio-dbg - very fast and configurable SIP proxy [debug symbols]
 kamailio-dnssec-modules - contains the dnssec module
 kamailio-erlang-modules - erlang modules for Kamailio
 kamailio-extra-modules - extra modules for Kamailio
 kamailio-geoip-modules - contains the geoip module
 kamailio-ims-modules - IMS module for Kamailio
 kamailio-java-modules - contains the app_java module
 kamailio-json-modules - Json parser and jsonrpc modules for Kamailio
 kamailio-kazoo-modules - kazoo modules for Kamailio
 kamailio-ldap-modules - LDAP modules for Kamailio
 kamailio-lua-modules - contains the app_lua module
 kamailio-memcached-modules - interface to memcached server
 kamailio-mono-modules - contains the app_mono module
 kamailio-mysql-modules - MySQL database connectivity module for Kamailio
 kamailio-outbound-modules - Outbound module 

Processed: affects 842276

[Debian Bug Tracking System]

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

> affects 842276 + release.debian.org,security.debian.org
Bug #842276 [src:nginx] nginx-common.config dpkg --compare-versions will 
mishandle return codes should the check fail
Added indication that 842276 affects release.debian.org and security.debian.org
> thanks
Stopping processing here.

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

Bug#841577: marked as done (ginkgocadx: FTBFS: build-dependency not installable: libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 16:56:05 +
with message-id 
and subject line Bug#841577: fixed in ginkgocadx 3.8.3-2
has caused the Debian Bug report #841577,
regarding ginkgocadx: FTBFS: build-dependency not installable: 
libmysqlclient-dev
to be marked as done.

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

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


-- 
841577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ginkgocadx
Version: 3.8.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), chrpath, cmake, libcairo2-dev, 
> libcurl4-gnutls-dev, libdcmtk-dev, libfftw3-dev, libfreetype6-dev, 
> libgtk2.0-dev, libinsighttoolkit4-dev, libjsoncpp-dev, libmysqlclient-dev, 
> libsqlite3-dev, libssl-dev, libvtk6-dev, libwrap0, libwrap0-dev, 
> libwxgtk3.0-dev, libxml2-dev, libgdcm-tools
> Filtered Build-Depends: debhelper (>= 9), chrpath, cmake, libcairo2-dev, 
> libcurl4-gnutls-dev, libdcmtk-dev, libfftw3-dev, libfreetype6-dev, 
> libgtk2.0-dev, libinsighttoolkit4-dev, libjsoncpp-dev, libmysqlclient-dev, 
> libsqlite3-dev, libssl-dev, libvtk6-dev, libwrap0, libwrap0-dev, 
> libwxgtk3.0-dev, libxml2-dev, libgdcm-tools
> dpkg-deb: building package 'sbuild-build-depends-ginkgocadx-dummy' in 
> '/<>/resolver-9J6FbL/apt_archive/sbuild-build-depends-ginkgocadx-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-ginkgocadx-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-9J6FbL/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-9J6FbL/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-9J6FbL/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-9J6FbL/apt_archive ./ Sources [469 B]
> Get:5 copy:/<>/resolver-9J6FbL/apt_archive ./ Packages [556 B]
> Fetched 1982 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install ginkgocadx build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ginkgocadx-dummy : Depends: libmysqlclient-dev but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

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/21/ginkgocadx_3.8.3-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 ---
Source: ginkgocadx
Source-Version: 3.8.3-2

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

A summary of the changes 

Bug#841050: [debian-mysql] Bug#841050: Security fixes from the October 2016 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Oct 19, 2016 at 10:38:22AM +0200, Lars Tangvald wrote:
> Hi,
> 
> On 10/19/2016 10:18 AM, Moritz Muehlenhoff wrote:
> > Hi,
> > 
> > On Wed, Oct 19, 2016 at 09:10:59AM +0200, Lars Tangvald wrote:
> > > So for Linux we consider this fixed in 5.5.52, but the complete fix
> > > was in 5.5.53.
> > Is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837984
> > addressed in 5.5.53?
> No, this hasn't been changed.
> If you take a look at
> https://github.com/mysql/mysql-server/blob/5.5/scripts/mysqld_safe.sh (just
> search for 'i386') you'll see it restricts it to intel architectures.
> This is a whitelist of where the --malloc-lib option is allowed to be set,
> and is restricted to the intel archs because we considered it of little use
> on other architectures.
> If needs to be available on other architectures we could make a patch in the
> packaging to add them.
> 
> > > Should I remove the CVE from the Debian changelog entry?
> > That's not needed, we can add a comment to the Security Tracker.
> Ok, thanks :)

What is the status for src:mysql-5.5 for a possible jessie-security
upload? (Btw, if-and-only-if the package is still needed due to
rebuild, then let's please fix the changelog entry as well.)

Regards,
Salvatore

Bug#839498: marked as done (bup: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 16:51:42 +
with message-id 
and subject line Bug#839498: fixed in bup 0.28.1-1.1
has caused the Debian Bug report #839498,
regarding bup: FTBFS: Tests failures
to be marked as done.

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

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


-- 
839498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bup
Version: 0.27.1-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):
> prw--- 1001/1001 0 1969-07-20 20:18 fifo
> -rw--- 1001/1001 1024 1969-07-20 20:18 file
> srwx-- 1001/1001 0 1969-07-20 20:18 socket
> lrwxrwxrwx 1001/1001 4 2016-10-01 11:45 symlink -> file -rwx-- 1001/1001 
> 0 1969-07-20 15:18 executable
> prw--- 1001/1001 0 1969-07-20 15:18 fifo
> -rw--- 1001/1001 1024 1969-07-20 15:18 file
> srwx-- 1001/1001 0 1969-07-20 15:18 socket
> lrwxrwxrwx 1001/1001 4 2016-10-01 11:45 symlink -> file
> Makefile:126: recipe for target 'tmp-target-run-test-ls.sh' failed
> make[2]: *** [tmp-target-run-test-ls.sh] Error 1
> make[2]: Leaving directory '/<>'
> ! Program returned non-zero exit code (2)   FAILED
> WvTest: 2641 tests, 1 failure, total time 21.148s.
> 
> WvTest result code: 2
> Makefile:134: recipe for target 'test' failed

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/bup_0.27.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 ---
Source: bup
Source-Version: 0.28.1-1.1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated bup 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, 27 Oct 2016 15:22:29 +0100
Source: bup
Binary: bup bup-doc
Architecture: source
Version: 0.28.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Robert Edmonds 
Changed-By: James Cowgill 
Description:
 bup- highly efficient file backup system based on git
 bup-doc- highly efficient file backup system based on git (documentation)
Closes: 839498
Changes:
 bup (0.28.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-Depend on tzdata to fix FTBFS. (Closes: #839498)
Checksums-Sha1:
 88571dca063e248fbe0ab698ffcbbf7a9ce5cf29 2008 bup_0.28.1-1.1.dsc
 3c0d7f71587baf2f1969013e416f119fc5758af3 6000 bup_0.28.1-1.1.debian.tar.xz
Checksums-Sha256:
 aa02f971d4381cfbf80674c2c4fd7a1bd32b7ace0485f24c0cae51e066e4b1cc 2008 
bup_0.28.1-1.1.dsc
 84208771173064a2d9d47872caff7813b8e79334205eff2bdaae4a92151d4d83 6000 
bup_0.28.1-1.1.debian.tar.xz
Files:
 668e60bfd97370e12027b68c654e10e7 2008 admin extra bup_0.28.1-1.1.dsc
 96fb5c555c240acb4a20fb156755e6b0 6000 admin extra bup_0.28.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYEg3GAAoJEMfxZ23qLQHvTHMP/3n9W7X3kI+RaP333U6f0zWi

Processed: tagging 842171

[Debian Bug Tracking System]

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

> tags 842171 + pending
Bug #842171 [src:musl] musl: CVE-2016-8859: Regex integer overflow in buffer 
size computations
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828293: encfs: FTBFS with openssl 1.1.0

[Agustin Martin]

On Sun, Jun 26, 2016 at 12:21:34PM +0200, Kurt Roeckx wrote:
> Source: encfs
> Version: 1.8.1-3
> 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/encfs_1.8.1-3_amd64-20160529-1416
> 
> 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.

For the records, Debian package (1.8.1) is behind upstream (1.9.1),

  https://github.com/vgough/encfs/releases

This problem about building with OpenSSL 1.1.0 seems to have been
addressed upstream 11 days ago,

  https://github.com/vgough/encfs/pull/230

although apparently based on encfs 1.9.1, which has also been migrated
to cmake.

I have tried a build with new encfs 1.9.1, the two patches about openssl
1.1.0 applied, old patches disabled, cmake added to build-deps and
attached simplified debian/rules. At least it builds here with openssl
1.1.0, but it should really be looked carefully by maintainer, in case
something is wrong.

Hope this helps,

-- 
Agustin
#!/usr/bin/make -f

DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/buildflags.mk
include /usr/share/dpkg/architecture.mk

%:
dh $@

ifneq ($(DOENCFSTESTS),FORCE)
# needs configured fuse -> ignore
override_dh_auto_test:
true
endif

Processed: Restore bug info

[Debian Bug Tracking System]

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

> forwarded 746005 https://code.google.com/p/lilypond/issues/detail?id=1055
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Set Bug forwarded-to-address to 
'https://code.google.com/p/lilypond/issues/detail?id=1055'.
> thanks
Stopping processing here.

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

Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

On jueves, 27 de octubre de 2016 4:59:39 P. M. ART Ondřej Surý wrote:
> I can probably generate two sets of packages with versioned symbols
> if I have some help with that.

That would be *very* kind of you! But before going ahead we might better 
contact the release team and see what they prefer here.


-- 
La ciencia sin la religión es renga, la religión sin la ciencia es ciega.
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: Restore bug info

[Debian Bug Tracking System]

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

> severity 746005 serious
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#840691: ghostscript and evince/libspectre problem

[Salvatore Bonaccorso]

Hi Roberto,

On Thu, Oct 27, 2016 at 09:50:02AM -0400, Roberto C. Sánchez wrote:
> Is your plan to release this as a -2 regression update to the previous
> DSA?  I assume that is what you plan to do, but I wanted to confirm to
> be certain.

Yes exactly, that's the plan. I would still like to hear Francesco's
feedback before proceeding with a regression update.

Regards,
Salvatore


signature.asc
Description: PGP signature

Processed (with 1 error): Fix block/unblock mess ...

[Debian Bug Tracking System]

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

> unblock 760986 by 746005
Failed to set blocking bugs of 760986: Not altering archived bugs; see 
unarchive.

> block 830347 by 746005 841736
Bug #830347 [src:denemo] denemo: FTBFS: build-dependency not installable: 
lilypond
830347 was not blocked by any bugs.
830347 was not blocking any bugs.
Added blocking bug(s) of 830347: 841736 and 746005
> thanks
Stopping processing here.

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

Processed: Re: Bug#828361: kamailio: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

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

> forwarded 828361 https://github.com/kamailio/kamailio/issues/834
Bug #828361 [src:kamailio] kamailio: FTBFS with openssl 1.1.0
Changed Bug forwarded-to-address to 
'https://github.com/kamailio/kamailio/issues/834' from 
'https://github.com/kamailio/kamailio/issues/685'.
> tags 828361 + pending
Bug #828361 [src:kamailio] kamailio: FTBFS with openssl 1.1.0
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
828361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828361
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:

> block 828306 by 828239
Bug #828306 [src:galera-3] galera-3: FTBFS with openssl 1.1.0
828306 was not blocked by any bugs.
828306 was blocking: 827061
Added blocking bug(s) of 828306: 828239
>
End of message, stopping processing here.

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

Processed (with 3 errors): Restore bug info

[Debian Bug Tracking System]

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

> # Restore bug info, accidentally deleted with a forcemerge
> unblock 830347 by 746005
Bug #830347 [src:denemo] denemo: FTBFS: build-dependency not installable: 
lilypond
830347 was blocked by: 841736 746005
830347 was not blocking any bugs.
Removed blocking bug(s) of 830347: 746005
> forcemerge 746005 841736
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Bug #841736 [lilypond] lilypond in Testing?
830347 was blocked by: 841736
830347 was not blocking any bugs.
Removed blocking bug(s) of 830347: 841736
Failed to forcibly merge 746005: Not altering archived bugs; see unarchive.

> severity 746005 serious
Failed to set severity of Bug 746005 to serious: failed to get lock on 
/org/bugs.debian.org/spool/lock/746005 -- Unable to lock 
/org/bugs.debian.org/spool/lock/746005 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> forwarded 746005 https://code.google.com/p/lilypond/issues/detail?id=1055
Failed to set the forwarded-to-address of 746005: failed to get lock on 
/org/bugs.debian.org/spool/lock/746005 -- Unable to lock 
/org/bugs.debian.org/spool/lock/746005 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#842276: nginx-common.config dpkg --compare-versions will mishandle return codes should the check fail

[Thomas Ward]

Source: nginx
Severity: serious
Version: 1.6.2-5+deb8u3

This was originally identified as a result of my own failure downstream
in Ubuntu when applying the patches from Debian for CVE-2016-1247.

One of the things added was nginx-common.config.  In this, the following
set of code exists:

log_symlinks_check() {
# Skip new installations
[ -z "$1" ] && return

# Skip unaffected installations
dpkg --compare-versions "$1" lt-nl "1.6.2-5+deb8u3" || return

# Check for unsecure symlinks
linked_logfiles="` find "$logdir" -type l -user www-data -name
'*.log' `"

# Skip if nothing is found
[ -z "$linked_logfiles" ] && return

db_subst nginx/log-symlinks logfiles $linked_logfiles
db_input high nginx/log-symlinks || true
db_go || true
}


This line will break all future version upgrades:

dpkg --compare-versions "$1" lt-nl "1.6.2-5+deb8u3" || return



What happens here is, say that the package is updated, and we have
+deb8u4 then.  Let's examine the error code we get from this:

teward@debian:~$ dpkg --compare-versions 1.6.2-5+deb8u4 lt-nl
1.6.2-5+deb8u3; echo $?
1


This error code is caught by `dpkg` and will ultimately die off with a
failure code, like this (NOTE: +deb8u4 was a 'fake' package created by
me from the nginx source code that has no changes between +deb8u3, it
was just used to test the version bump issue):

teward@debian:~$ sudo dpkg -i ./nginx-common_1.6.2-5+deb8u4_all.deb
(Reading database ... 29849 files and directories currently installed.)
Preparing to unpack .../nginx-common_1.6.2-5+deb8u4_all.deb ...
Unpacking nginx-common (1.6.2-5+deb8u4) over (1.6.2-5+deb8u3) ...
Setting up nginx-common (1.6.2-5+deb8u4) ...
dpkg: error processing package nginx-common (--install):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u5) ...
Processing triggers for man-db (2.7.0.2-5) ...
Errors were encountered while processing:
 nginx-common


This prevents clean package updates.

The fix implemented downstream, considered a Security Regression update
in Ubuntu, was to change the line referenced above to the following:

dpkg --compare-versions "$1" lt-nl "1.6.2-5+deb8u3" || return 0


This will force an "OK" status code when the version check fails, and
permit updating.


Please update this ASAP, *long before* we have to deal with this as a
core problem in the package.



--
Thomas

Processed (with 3 errors): Restore bug info

[Debian Bug Tracking System]

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

> # Restore bug info, accidentally deleted with a forcemerge
> forcemerge 746005 841736
Bug #746005 [lilypond] lilypond: please migrate to guile-2.0
Bug #841736 [lilypond] lilypond in Testing?
830347 was blocked by: 746005
830347 was not blocking any bugs.
Added blocking bug(s) of 830347: 841736
Failed to forcibly merge 746005: Not altering archived bugs; see unarchive.

> severity 746005 serious
Failed to set severity of Bug 746005 to serious: failed to get lock on 
/org/bugs.debian.org/spool/lock/746005 -- Unable to lock 
/org/bugs.debian.org/spool/lock/746005 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> forwarded 746005 https://code.google.com/p/lilypond/issues/detail?id=1055
Failed to set the forwarded-to-address of 746005: failed to get lock on 
/org/bugs.debian.org/spool/lock/746005 -- Unable to lock 
/org/bugs.debian.org/spool/lock/746005 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/746005 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

On jueves, 27 de octubre de 2016 4:48:33 P. M. ART Ondřej Surý wrote:
> So is there an option to not switch to openssl 1.1.0 for stretch?

I was recently told something along that, but the problem is not easy 
actually. Some people might need botan switched, some not.

And we are to expect crashes if apps mix them :-/

-- 
10: El procesador de textos es:
* Un programa que le da vida a una computadora haciendo que
intente dominar el mundo (ver pregunta 1)
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#828252: qtcreator is marked for autoremoval from testing

[Ondřej Surý]

I can probably generate two sets of packages with versioned symbols
if I have some help with that.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Oct 27, 2016, at 16:55, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On jueves, 27 de octubre de 2016 4:48:33 P. M. ART Ondřej Surý wrote:
> > So is there an option to not switch to openssl 1.1.0 for stretch?
> 
> I was recently told something along that, but the problem is not easy 
> actually. Some people might need botan switched, some not.
> 
> And we are to expect crashes if apps mix them :-/
> 
> -- 
> 10: El procesador de textos es:
> * Un programa que le da vida a una computadora haciendo que
> intente dominar el mundo (ver pregunta 1)
> Damian Nadales
> http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html
> 
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#828252: qtcreator is marked for autoremoval from testing

[Ondřej Surý]

So is there an option to not switch to openssl 1.1.0 for stretch?

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Oct 27, 2016, at 16:33, Lisandro Damián Nicanor Pérez Meyer
wrote:
> For what is wort Qt5 won't be switching to libssl 1.1, so if botan gets 
> updated we will have to remove qtcreator from testing.
> 
> On jueves, 27 de octubre de 2016 4:40:03 A. M. ART Debian testing
> autoremoval 
> watch wrote:
> > qtcreator 4.1.0-2 is marked for autoremoval from testing on 2016-11-25
> > 
> > It (build-)depends on packages with these RC bugs:
> > 828252: botan1.10: FTBFS with openssl 1.1.0
> 
> 
> -- 
> ~/ sweet ~/
> 
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#828505: pjproject: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Thu, Oct 27, 2016 at 09:18:31AM +0200, Bernhard Schmidt wrote:
> 
> I changed that to check for OPENSSL_init_ssl instead of
> SSL_library_init, which makes configure enable SSL and ultimately leads
> to the following build error

Those are all very easy to fix. Maybe other files also have such
problems.


Kurt

Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

For what is wort Qt5 won't be switching to libssl 1.1, so if botan gets 
updated we will have to remove qtcreator from testing.

On jueves, 27 de octubre de 2016 4:40:03 A. M. ART Debian testing autoremoval 
watch wrote:
> qtcreator 4.1.0-2 is marked for autoremoval from testing on 2016-11-25
> 
> It (build-)depends on packages with these RC bugs:
> 828252: botan1.10: FTBFS with openssl 1.1.0


-- 
~/ sweet ~/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#828306: [debian-mysql] Bug#828306: Bug#828306: galera-3: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Thu, Oct 27, 2016 at 08:58:17AM +0300, Otto Kekäläinen wrote:
> You increased the seriousness of this issue, with the result of
> upcoming autoremoval of galera-3 from Debian testing despite OpenSSL
> 1.1 not being available in testing yet, and not even in unstable yet.
> Galera-3 currently builds fine in testing and unstable.

But it will be uploaded soon, and then you'll have to fix it
anyway.

> Also the build problem with OpenSSL is not per se in Galera, but in
> libasio-dev. So if you want to have the status serious against
> something, make it against asio
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828239) and push
> the asio maintainer to release a new version of it, and then all other
> packages that depend on it will automatically be fixed.

So mark your bug as being blocked by the asio one.


Kurt

Bug#840691: ghostscript and evince/libspectre problem

[Roberto C . Sánchez]

On Thu, Oct 27, 2016 at 01:12:10PM +0200, Salvatore Bonaccorso wrote:
> 
> Packages with that patch added are now as well on
> 
> https://people.debian.org/~carnil/tmp/ghostscript/
> 
> Please test those if possible for you.
> 

Salvatore,

Is your plan to release this as a -2 regression update to the previous
DSA?  I assume that is what you plan to do, but I wanted to confirm to
be certain.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Processed: Bug#839498: bup: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #839498 [src:bup] bup: FTBFS: Tests failures
Added tag(s) pending.

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

Bug#839498: bup: FTBFS: Tests failures

[James Cowgill]

Control: tags -1 pending

Hi,

I've uploaded the attached NMU to fix this bug.

This will also trigger a rebuild on mipsel which (I hope) will fix the
FTBFS there as well.

Thanks,
James
diff -Nru bup-0.28.1/debian/changelog bup-0.28.1/debian/changelog
--- bup-0.28.1/debian/changelog 2016-10-02 22:22:52.0 +0100
+++ bup-0.28.1/debian/changelog 2016-10-27 15:22:29.0 +0100
@@ -1,3 +1,10 @@
+bup (0.28.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-Depend on tzdata to fix FTBFS. (Closes: #839498)
+
+ -- James Cowgill   Thu, 27 Oct 2016 15:22:29 +0100
+
 bup (0.28.1-1) unstable; urgency=medium
 
   * New upstream version 0.28.1
diff -Nru bup-0.28.1/debian/control bup-0.28.1/debian/control
--- bup-0.28.1/debian/control   2016-10-02 22:22:52.0 +0100
+++ bup-0.28.1/debian/control   2016-10-27 15:11:21.0 +0100
@@ -12,6 +12,7 @@
  python-pylibacl,
  python-pyxattr [linux-any],
  rsync,
+ tzdata,
 Build-Depends-Indep: pandoc (>= 1.11.1-4~), pandoc-data (>= 1.11.1-4~)
 Standards-Version: 3.9.6
 Homepage: https://github.com/bup/bup


signature.asc
Description: OpenPGP digital signature

Bug#828529: r-cran-openssl: FTBFS with openssl 1.1.0

[Andreas Tille]

Hi Jeroen,

thanks for your quick and helpful response.

On Thu, Oct 27, 2016 at 02:58:08PM +0200, Jeroen Ooms wrote:
> I had a first attempt at fixing everything for libssl 1.1.0:
> https://github.com/jeroenooms/openssl/commit/3066903e4e1d475616c1c784053e30bf290decd3
> 
> Things look good, but I need to test on more systems to make sure the
> package also still builds agains OpenSSL 1.0.0 and 1.0.1. Some of our
> users are on academic supercomputers which, for better or worse, run
> old versions of CentOS 5 or 6, that need to keep working as well.
> 
> If all goes well I hope to do an upstream release later this week.

It would be great if you could ping me once you have prepared a new
release.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#840691: ghostscript and evince/libspectre problem

[Roberto C . Sánchez]

On Thu, Oct 27, 2016 at 03:31:15PM +0200, Edgar Fuß wrote:
> > If it works, I will apply the same patch to the wheezy package and upload 
> > it.
> I didn’t look at the jessie package but it is wheezy with debian-security 
> where I figured out that changing that ,,put’’ to ,,.forceput’’ made evince 
> display PostScript again.

Thanks for the info.  That gives me more confidence that this is
appropriate for wheezy.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Bug#836070: marked as done (r-cran-sem: FTBFS: ERROR: dependencies 'MASS', 'boot' are not available for package 'sem')

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 13:35:51 +
with message-id 
and subject line Bug#836070: fixed in r-cran-sem 3.1.7-4
has caused the Debian Bug report #836070,
regarding r-cran-sem: FTBFS: ERROR: dependencies 'MASS', 'boot' are not 
available for package 'sem'
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.)


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

Dear Maintainer,

r-cran-sem fails to build from source in unstable/amd64:

  [..]

  Selecting previously unselected package libpango-1.0-0:amd64.
  Preparing to unpack .../34-libpango-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpango-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libgraphite2-3:amd64.
  Preparing to unpack .../35-libgraphite2-3_1.3.8-1_amd64.deb ...
  Unpacking libgraphite2-3:amd64 (1.3.8-1) ...
  Selecting previously unselected package libharfbuzz0b:amd64.
  Preparing to unpack .../36-libharfbuzz0b_1.2.7-1+b1_amd64.deb ...
  Unpacking libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Selecting previously unselected package libpangoft2-1.0-0:amd64.
  Preparing to unpack .../37-libpangoft2-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangoft2-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libpangocairo-1.0-0:amd64.
  Preparing to unpack .../38-libpangocairo-1.0-0_1.40.1-1_amd64.deb ...
  Unpacking libpangocairo-1.0-0:amd64 (1.40.1-1) ...
  Selecting previously unselected package libsm6:amd64.
  Preparing to unpack .../39-libsm6_2%3a1.2.2-1+b1_amd64.deb ...
  Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
  Selecting previously unselected package libtcl8.6:amd64.
  Preparing to unpack .../40-libtcl8.6_8.6.6+dfsg-1_amd64.deb ...
  Unpacking libtcl8.6:amd64 (8.6.6+dfsg-1) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../41-libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparing to unpack .../42-libtiff5_4.0.6-2_amd64.deb ...
  Unpacking libtiff5:amd64 (4.0.6-2) ...
  Selecting previously unselected package libxft2:amd64.
  Preparing to unpack .../43-libxft2_2.3.2-1_amd64.deb ...
  Unpacking libxft2:amd64 (2.3.2-1) ...
  Selecting previously unselected package libxss1:amd64.
  Preparing to unpack .../44-libxss1_1%3a1.2.2-1_amd64.deb ...
  Unpacking libxss1:amd64 (1:1.2.2-1) ...
  Selecting previously unselected package libtk8.6:amd64.
  Preparing to unpack .../45-libtk8.6_8.6.6-1_amd64.deb ...
  Unpacking libtk8.6:amd64 (8.6.6-1) ...
  Selecting previously unselected package libxt6:amd64.
  Preparing to unpack .../46-libxt6_1%3a1.1.5-1_amd64.deb ...
  Unpacking libxt6:amd64 (1:1.1.5-1) ...
  Selecting previously unselected package openssl.
  Preparing to unpack .../47-openssl_1.0.2h-1_amd64.deb ...
  Unpacking openssl (1.0.2h-1) ...
  Selecting previously unselected package ca-certificates.
  Preparing to unpack .../48-ca-certificates_20160104_all.deb ...
  Unpacking ca-certificates (20160104) ...
  Selecting previously unselected package r-base-core.
  Preparing to unpack .../49-r-base-core_3.3.1-1+b1_amd64.deb ...
  Unpacking r-base-core (3.3.1-1+b1) ...
  Selecting previously unselected package libgfortran-6-dev:amd64.
  Preparing to unpack .../50-libgfortran-6-dev_6.2.0-1_amd64.deb ...
  Unpacking libgfortran-6-dev:amd64 (6.2.0-1) ...
  Selecting previously unselected package gfortran-6.
  Preparing to unpack .../51-gfortran-6_6.2.0-1_amd64.deb ...
  Unpacking gfortran-6 (6.2.0-1) ...
  Selecting previously unselected package gfortran.
  Preparing to unpack .../52-gfortran_4%3a6.1.1-1_amd64.deb ...
  Unpacking gfortran (4:6.1.1-1) ...
  Selecting previously unselected package libblas-dev.
  Preparing to unpack .../53-libblas-dev_3.6.1-2_amd64.deb ...
  Unpacking libblas-dev (3.6.1-2) ...
  Selecting previously unselected package liblapack-dev.
  Preparing to unpack .../54-liblapack-dev_3.6.1-2_amd64.deb ...
  Unpacking liblapack-dev (3.6.1-2) ...
  Selecting previously unselected package libtinfo-dev:amd64.
  Preparing to unpack .../55-libtinfo-dev_6.0+20160625-1_amd64.deb ...
  Unpacking libtinfo-dev:amd64 (6.0+20160625-1) ...
  Selecting previously unselected package libncurses5-dev:amd64.
  Preparing to unpack 

Bug#840691: ghostscript and evince/libspectre problem

[Edgar Fuß]

> If it works, I will apply the same patch to the wheezy package and upload it.
I didn’t look at the jessie package but it is wheezy with debian-security where 
I figured out that changing that ,,put’’ to ,,.forceput’’ made evince display 
PostScript again.

Bug#831142: marked as done (gcc-arm-none-eabi: FTBFS with GCC 6: cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' attribute)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 13:05:03 +
with message-id 
and subject line Bug#831142: fixed in gcc-arm-none-eabi 15:5.4.1+svn241155-1
has caused the Debian Bug report #831142,
regarding gcc-arm-none-eabi: FTBFS with GCC 6: cfns.gperf:101:1: error: 'const 
char* libc_name_p(const char*, unsigned int)' redeclared inline with 
'gnu_inline' attribute
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.)


-- 
831142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-arm-none-eabi
Version: 15:4.9.3+svn231177-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -c  -DIN_GCC_FRONTEND -g -O2 -fstack-protector-strong 
> -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti 
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -I. -Icp 
> -I../../src/gcc -I../../src/gcc/cp -I../../src/gcc/../include 
> -I../../src/gcc/../libcpp/include  -I../../src/gcc/../libdecnumber 
> -I../../src/gcc/../libdecnumber/dpd -I../libdecnumber 
> -I../../src/gcc/../libbacktrace   -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> cp/except.o -MT cp/except.o -MMD -MP -MF cp/.deps/except.TPo 
> ../../src/gcc/cp/except.c
> In file included from ./tm.h:17:0,
>  from ../../src/gcc/cp/except.c:27:
> ../../src/gcc/config/elfos.h:102:21: warning: invalid suffix on literal; 
> C++11 requires a space between literal and string macro [-Wliteral-suffix]
> fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",\
>  ^
> ../../src/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; 
> C++11 requires a space between literal and string macro [-Wliteral-suffix]
>fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",  \
> ^
> In file included from ../../src/gcc/cp/except.c:1013:0:
> cfns.gperf: In function 'const char* libc_name_p(const char*, unsigned int)':
> cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' 
> redeclared inline with 'gnu_inline' attribute
> cfns.gperf:26:14: note: 'const char* libc_name_p(const char*, unsigned int)' 
> previously declared here
> cfns.gperf: At global scope:
> cfns.gperf:26:14: warning: inline function 'const char* libc_name_p(const 
> char*, unsigned int)' used but never defined
> make[4]: *** [cp/except.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/gcc-arm-none-eabi_4.9.3+svn231177-1_unstable_gcc6.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 ---
Source: gcc-arm-none-eabi
Source-Version: 15:5.4.1+svn241155-1

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

Debian distribution maintenance software
pp.
Agustin Henze  (supplier of updated gcc-arm-none-eabi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Oct 2016 08:12:07 -0300
Source: gcc-arm-none-eabi
Binary: gcc-arm-none-eabi gcc-arm-none-eabi-source
Architecture: source amd64 all
Version: 

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Mattia Rizzolo]

On Thu, Oct 27, 2016 at 02:07:17PM +0200, Hilmar Preuße wrote:
> Sorry to bother you again. The generated configure script seems to be broken
> or incomplete:

arggg :(

> Should we open a new bug for all this?

IMHO yes.

> 
> > I suggest you bring that upstream, not being able to run
> > autoreconf -f -i
> > on a autotools project is IMHO a bug that ought to be fixed.
> > 
> Well, yes. Something to do in the future, not sure when.

IMHO, this should be handled upstream.
I've now looked for the first time at the upstream git repo, and I see
the "configure" file being there: it shouldn't.  All the artifacts of
autotool are not supposed to be stored within a VCS, only generated at
release time.  Though that one seems to be kept up to date with
configure.in; clearly they are not doing the same with the rest of
autotools-generated artifacts.

Considering that there are so many issues and maybe you want to upload
soon rather than later, for me feel free to skip this point about
autoreconf, but please try to get this fixed.


btw, I peaked at the debian's git repository, and I saw that you used
the git:// protocol in Vcs-Git; given that it's possible please avoid
doing so, also see
https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#840528:

[A. Jesse Jiryu Davis]

Thanks Andreas, you're right. We'll submit 1.4.2 with the fix promptly.

On Wed, Oct 26, 2016 at 6:34 PM, Andreas Beckmann  wrote:

> Control: reopen -1
>
> On Wed, 12 Oct 2016 22:00:26 -0400 "A. Jesse Jiryu Davis" <
> je...@mongodb.com> wrote:
> > Version: 1.4.1-1
>
> Nope.
>
> > Fixed in the upstream repository and uploaded as a new package version to
> > Debian. See the forwarded-to bug in MongoDB's Jira for details.
>
> That new version is not yet in Debian. Jira says fixed in 1.4.2.
>
> Also:
>
> $ echo '#include ' | gcc -x c -I /usr/include/libmongoc-1.0 -c -
> In file included from :1:0:
> /usr/include/libmongoc-1.0/mongoc.h:22:18: fatal error: bson.h: No such
> file or directory
>  #include 
>   ^
> compilation terminated.
>
>
> Andreas
>

Bug#840468: marked as done (mame: FTBFS[arm64]: immediate value out of range 0 to 63)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 12:22:22 +
with message-id 
and subject line Bug#840468: fixed in mame 0.179-1
has caused the Debian Bug report #840468,
regarding mame: FTBFS[arm64]: immediate value out of range 0 to 63
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.)


-- 
840468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mame
Version: 0.178-1
Severity: serious
Justification: FTBFS, but built successfully in the past

Hi,

On linux-arm64, mame since 0.176-3 FTBFS, because:

https://buildd.debian.org/status/fetch.php?pkg=mame=arm64=0.178-1=1475578747
| Compiling src/emu/emumem.cpp...
| g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE -fstack-protector-strong 
-Wformat -Werror=format-security -g0 -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP -MP -DNDEBUG 
-DCRLF=2 -DLSB_FIRST -DXMD_H -DFLAC__NO_DLL -DMAME_NOASM -DLUA_COMPAT_ALL 
-DLUA_COMPAT_5_1 -DLUA_COMPAT_5_2 -DPTR64=1 -DNO_AFFINITY_NP 
-I../../../../../src/osd -I../../../../../src/emu -I../../../../../src/lib 
-I../../../../../src/lib/util -I../../../../../3rdparty 
-I../../../../generated/emu -I../../../../generated/emu/layout 
-I../../../../../scripts/src   -pipe -Wno-deprecated-declarations -O3 
-fno-strict-aliasing -mabi=lp64 -Wno-unknown-pragmas -Wall -Wcast-align -Wundef 
-Wformat-security -Wwrite-strings -Wno-sign-compare -Wno-conversion 
-Wno-unused-result -Wno-array-bounds -Wno-cast-align -x c++ -std=c++14 
-Woverloaded-virtual -Wsuggest-override -flifetime-dse=1 -include obj
 /Release/emu.h -o "obj/Release/src/emu/emumem.o" -c 
"../../../../../src/emu/emumem.cpp"
| {standard input}:28638: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,64,16'
| {standard input}:28643: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,80,16'
| {standard input}:28648: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,96,16'
| {standard input}:28653: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,112,16'
| {standard input}:28658: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,128,16'
| {standard input}:28663: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,144,16'
| {standard input}:28668: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,160,16'
| {standard input}:28673: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,176,16'
| {standard input}:28678: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,192,16'
| {standard input}:28683: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,208,16'
| {standard input}:28688: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,224,16'
| {standard input}:31708: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,64,32'
| {standard input}:31713: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,96,32'
| {standard input}:31718: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,128,32'
| {standard input}:31723: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,160,32'
| {standard input}:31728: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,192,32'
| {standard input}:32454: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,64,16'
| {standard input}:32459: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,80,16'
| {standard input}:32464: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,96,16'
| {standard input}:32469: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,112,16'
| {standard input}:32474: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,128,16'
| {standard input}:32479: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,144,16'
| {standard input}:32484: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,160,16'
| {standard input}:32489: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,176,16'
| {standard input}:32494: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx x0,x2,192,16'
| {standard input}:32499: Error: immediate value out of range 0 to 63 at 
operand 3 -- `ubfx 

Bug#841589: marked as done (webissues: FTBFS: install: cannot create regular file '/usr/bin/webissues': Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 12:24:08 +
with message-id 
and subject line Bug#841589: fixed in webissues 1.1.4-4
has caused the Debian Bug report #841589,
regarding webissues: FTBFS: install: cannot create regular file 
'/usr/bin/webissues': Permission denied
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.)


-- 
841589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webissues
Version: 1.1.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[2]: Entering directory '/<>/src'
> install -m 755 -p ../debug/webissues /usr/bin/webissues
> install: cannot create regular file '/usr/bin/webissues': Permission denied
> Makefile:3487: recipe for target 'install_target' failed
> make[2]: [install_target] Error 1 (ignored)
> mkdir: cannot create directory '/usr/share/applications': Permission denied
> Makefile:3496: recipe for target 'install_desktop' failed
> make[2]: *** [install_desktop] 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/21/webissues_1.1.4-3_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 ---
Source: webissues
Source-Version: 1.1.4-4

We believe that the bug you reported is fixed in the latest version of
webissues, 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.
Patrick Matthäi  (supplier of updated webissues 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, 27 Oct 2016 13:26:24 +0200
Source: webissues
Binary: webissues webissues-dbg
Architecture: source amd64
Version: 1.1.4-4
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 webissues  - network system supporting team collaboration
 webissues-dbg - network system supporting team collaboration (dbg symbols)
Closes: 841589
Changes:
 webissues (1.1.4-4) unstable; urgency=high
 .
   * Set destdir manualy to prevent a FTBFS.
 Closes: #841589
   * Remove unused lintian overrides.
Checksums-Sha1:
 afea9966600ba92169f272a7618bfb012cb5cd6d 1820 webissues_1.1.4-4.dsc
 12e7b9d0486e85c0cac3626b5c6382e5c97b3182 24240 webissues_1.1.4-4.debian.tar.xz
 fb1e0c2433b7280bcab74715f5b3195801fe9633 18488106 
webissues-dbg_1.1.4-4_amd64.deb
 a4ef72b20baeb9f47b3b89e384ad724d78e4492a 2687306 webissues_1.1.4-4_amd64.deb
Checksums-Sha256:
 e918e56413670c837acb70a19a98dc595302c24c0bec9da2a33647e2cb24455c 1820 
webissues_1.1.4-4.dsc
 d9c99dbec80ff505d443368fa582aa967eb7c51a208debeb3dff518168b0e3c5 24240 
webissues_1.1.4-4.debian.tar.xz
 d0cffd5857afe5b198a1aabcdb5f365be55b9378ba0fdfef66d24d13bf7641ab 18488106 
webissues-dbg_1.1.4-4_amd64.deb
 23529bebfebb0c52c7490cda03a6f44e1c4e17b9fb5f126a4a00905a532540ef 2687306 
webissues_1.1.4-4_amd64.deb
Files:
 0b671a5689b92b5cfcb31e4ed10938ff 1820 x11 optional webissues_1.1.4-4.dsc
 4f3a2410442905c686648994727e1c58 24240 x11 optional 

Bug#841565: marked as done (fraqtive: FTBFS: install: cannot create regular file '/usr/bin/fraqtive': Permission denied)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 12:19:27 +
with message-id 
and subject line Bug#841565: fixed in fraqtive 0.4.8-4
has caused the Debian Bug report #841565,
regarding fraqtive: FTBFS: install: cannot create regular file 
'/usr/bin/fraqtive': Permission denied
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.)


-- 
841565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fraqtive
Version: 0.4.8-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[2]: Entering directory '/<>/src'
> install -m 755 -p "../debug/fraqtive" "/usr/bin/fraqtive"
> install: cannot create regular file '/usr/bin/fraqtive': Permission denied
> Makefile:1252: recipe for target 'install_target' failed
> make[2]: [install_target] Error 1 (ignored)
> mkdir: cannot create directory '/usr/share/applications/': Permission denied
> Makefile:1261: recipe for target 'install_desktop' failed
> make[2]: *** [install_desktop] 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/21/fraqtive_0.4.8-3_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 ---
Source: fraqtive
Source-Version: 0.4.8-4

We believe that the bug you reported is fixed in the latest version of
fraqtive, 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.
Patrick Matthäi  (supplier of updated fraqtive 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, 27 Oct 2016 13:25:38 +0200
Source: fraqtive
Binary: fraqtive fraqtive-dbg
Architecture: source amd64
Version: 0.4.8-4
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 fraqtive   - draws Mandelbrot and Julia fractals
 fraqtive-dbg - draws Mandelbrot and Julia fractals (debugging symbols)
Closes: 841565
Changes:
 fraqtive (0.4.8-4) unstable; urgency=high
 .
   * Override dh_auto_install.
 Closes: #841565
   * Remove unused overrrides.
Checksums-Sha1:
 9572e8b1d4aa5e348608feb65cb149ce46c6ef26 1965 fraqtive_0.4.8-4.dsc
 524dda61c99fd73eb3be68346ca5a63dfa3aacb0 5604 fraqtive_0.4.8-4.debian.tar.xz
 6cf3b3897f1cbccea60da338b7c55937fe743c5e 4905210 fraqtive-dbg_0.4.8-4_amd64.deb
 d642ada067b15da30613a7f3819ffcbde44ac480 235960 fraqtive_0.4.8-4_amd64.deb
Checksums-Sha256:
 3faaf0ae70506baed955d71e7ffd1b0be9a6e1684adc6f06a553497a3773e353 1965 
fraqtive_0.4.8-4.dsc
 316e072f890b07c4b9074e5ec109559a2808405310b5d213a0f703b58a118fe8 5604 
fraqtive_0.4.8-4.debian.tar.xz
 ac18ba7be2db92465a2dbc292f8a942295a443651eccc633e240cf0e41c06dca 4905210 
fraqtive-dbg_0.4.8-4_amd64.deb
 4e09931051a5acf8f7b03ca2ef16177201486e86db97bfb5da8cd62941a9e8b5 235960 
fraqtive_0.4.8-4_amd64.deb
Files:
 17c7765ac0714894b8cbd720b5cfcc3c 1965 kde optional fraqtive_0.4.8-4.dsc
 27402accd9c06b3a30dd9d94b3a88803 5604 kde optional 
fraqtive_0.4.8-4.debian.tar.xz
 fbf76d088ca2ae549aa5c1d56d6c5284 4905210 debug 

Processed: tagging 840691

[Debian Bug Tracking System]

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

> tags 840691 + confirmed pending
Bug #840691 [libgs9] libgs9: security update DSA-3691-1 breaks zathura, evince, 
... in jessie
Bug #842154 [libgs9] evince: Crashed while opening PS document
Added tag(s) pending and confirmed.
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#836759: proftpd-dfsg: please drop the build dependency on hardening-wrapper

[Hilmar Preuße]

Am 27.10.2016 um 01:58 schrieb Mattia Rizzolo:

On Wed, Oct 26, 2016 at 10:56:12PM +0200, Hilmar Preuße wrote:


Hi,


Tried to implement this according to [1]. I gave me an FTBFS (log attached).


That's configure.in being buggy.  I quickly asked to a friend of mine
(jrtc27) whom speaks autotools (I don't really), and in about 5 minutes
he came up with https://paste.debian.net/890189/
Apparently this is a requirement since 2001:
http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=e3e7e0a0afcbb870bec9a34d22fe0750393c40a1;hp=aa8dfa178d82db0fae8f5b0692f74e33763a263d
Unless I'm missing something, this also means upstream did not run
autoheader in the last 15+ years?!

Sorry to bother you again. The generated configure script seems to be 
broken or incomplete:


checking for struct statfs.f_type... yes
./configure: line 22589: PR_CHECK_STRUCT_ADDRINFO: command not found
./configure: line 22590: PR_CHECK_STRUCT_SS: command not found
./configure: line 22591: PR_CHECK_SS_FAMILY: command not found
./configure: line 22592: PR_CHECK_SS_LEN: command not found
checking sys/acl.h usability... yes
checking sys/acl.h presence... yes



checking whether linking with OpenSSL has complete ECC support... yes
checking for Postgres's PQescapeStringConn... yes
./configure: line 24427: syntax error near unexpected token `Wfloat-equal'
./configure: line 24427: `PR_CHECK_CC_OPT(Wfloat-equal)'
debian/rules:77: recipe for target 'configure-stamp' failed
make: *** [configure-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1376:

The code in question is

  if test x"$GCC" = xyes; then

PR_CHECK_CC_OPT(Wfloat-equal)
PR_CHECK_CC_OPT(Wformat)
PR_CHECK_CC_OPT(Wformat-security)
PR_CHECK_CC_OPT(Wimplicit-function-declaration)
PR_CHECK_CC_OPT(Wmaybe-uninitialized)
PR_CHECK_CC_OPT(Wpointer-to-int-cast)
PR_CHECK_CC_OPT(Wstack-protector)
PR_CHECK_CC_OPT(Wunreachable-code)
PR_CHECK_CC_OPT(fstack-protector-all)
  fi

PR_CHECK_CC_OPT is defined in m4/proftpd.m4. Not sure if it is read, b/c 
the functions above PR_CHECK_STRUCT_ADDRINFO... are defined there too.


Should we open a new bug for all this?


I suggest you bring that upstream, not being able to run
autoreconf -f -i
on a autotools project is IMHO a bug that ought to be fixed.


Well, yes. Something to do in the future, not sure when.

Hilmar
--
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#837668: marked as done (axiom: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 07:43:38 -0400
with message-id <87d1im9fv9@valiant.maguirefamily.org>
and subject line pie bindnow
has caused the Debian Bug report #837668,
regarding axiom: 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.)


-- 
837668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: axiom
Version: 20140801-11
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):
...
Compiling /<>/books/tangle1.lisp.
; (DEFUN ALLCHUNKS ...) is being compiled.
;; Warning: The variable VALUE is not used.
End of Pass 1.  End of Pass 2.  OPTIMIZE levels: Safety=0 (No runtime
error checking), Space=0, Speed=3
Finished compiling /<>/books/tangle1.lisp.
Loading /<>/books/tangle1.o
Unrelocated non-local symbol: _GLOBAL_OFFSET_TABLE_

Error: ERROR "The assertion !emsg(\"Unrelocated non-local symbol:
%s\\n\",st1+sym->st_name) on line 236 of sfaslelf.c in function
relocate_symbols failed: Success"
Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by LOAD.
ERROR "The assertion !emsg(\"Unrelocated non-local symbol:
%s\\n\",st1+sym->st_name) on line 236 of sfaslelf.c in function
relocate_symbols failed: Success"

Broken at LOAD.  Type :H for Help.
1  Return to top level. >>Makefile:18: recipe for target
'/<>/obj/linux/bin/lisp' failed
make[3]: *** [/<>/obj/linux/bin/lisp] Error 255
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/axiom_20140801-11_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Greetings, and thanks for your report!  These are fixed with
gcl-2.6.12-43.

Take care,
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah--- End Message ---

Bug#837667: marked as done (acl2: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Thu, 27 Oct 2016 07:43:38 -0400
with message-id <87d1im9fv9@valiant.maguirefamily.org>
and subject line pie bindnow
has caused the Debian Bug report #837667,
regarding acl2: 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.)


-- 
837667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acl2
Version: 7.2dfsg-2
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):
...
Compiling acl2-fns.lisp.
End of Pass 1.
;; Note: Tail-recursive call of GET-TYPE-FROM-DCLS was replaced by
iteration.
;; Note: Tail-recursive call of COLLECT-TYPES was replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of OUTPUT-TYPE-FOR-DECLARE-FORM-REC was
replaced by iteration.
;; Note: Tail-recursive call of REV1@ was replaced by iteration.
;; Note: Tail-recursive call of ACL2-READ-CHARACTER-STRING was replaced
by iteration.
;; Note: Tail-recursive call of FANCY-STRING-READER-MACRO-AUX was
replaced by iteration.
End of Pass 2.  OPTIMIZE levels: Safety=0 (No runtime error checking),
Space=0, Speed=3
Finished compiling /<>/acl2-fns.lisp.
Loading acl2-fns.o
Unrelocated non-local symbol: _GLOBAL_OFFSET_TABLE_

Error: Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by LOAD.
Condition in LOAD [or a callee]: INTERNAL-SIMPLE-ERROR: The assertion
!emsg("Unrelocated non-local symbol: %s\n",st1+sym->st_name) on line 236
of sfaslelf.c in function relocate_symbols failed: Success

Broken at LOAD.  Type :H for Help.
1  Return to top level. ACL2>>
Error: Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by LOAD.
Condition in LOAD [or a callee]: INTERNAL-SIMPLE-UNDEFINED-FUNCTION:
Cell error on MAKE-TAGS: Undefined function:
Broken at LOAD.
1 (abort) Return to debug level 1. 2  Return to top level. ACL2>>>
Error: Fast links are on: do (si::use-fast-links nil) for debugging
Signalled by LOAD.
Condition in LOAD [or a callee]: INTERNAL-SIMPLE-UNDEFINED-FUNCTION:
Cell error on EXIT-LISP: Undefined function:
Broken at LOAD.
1 (abort) Return to debug level 2. 2  Return to debug level 1.
  3  Return to top level. ACL2GNUmakefile:417: recipe for target
'TAGS' failed
make[2]: *** [TAGS] Error 255
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/acl2_7.2dfsg-2_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Greetings, and thanks for your report!  These are fixed with
gcl-2.6.12-43.

Take care,
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah--- End Message ---

Processed: maxima-emacs

[Debian Bug Tracking System]

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

> severity 842164 important
Bug #842164 [maxima-emacs] maxima-emacs does not work
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: Re: Bug#837289: kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: Invalid bfd target

[Debian Bug Tracking System]

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

> severity 837289 important
Bug #837289 [src:kfreebsd-10] kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: 
Invalid bfd target
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#842248: urlgrabber: FTBFS (build hangs)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 urlgrabber: FTBFS randomly (build hangs)
Bug #842248 [src:urlgrabber] urlgrabber: FTBFS (build hangs)
Changed Bug title to 'urlgrabber: FTBFS randomly (build hangs)' from 
'urlgrabber: FTBFS (build hangs)'.

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

Bug#842248: urlgrabber: FTBFS (build hangs)

[Santiago Vila]

Control: retitle -1 urlgrabber: FTBFS randomly (build hangs)

I built it two more times and then it succeeded.
I'm modifying the title to reflect this.

Bug#837289: kfreebsd-10: FTBFS: objcopy:linux32_vdso.so: Invalid bfd target

[Steven Chamberlain]

severity 837289 important
thanks

Hi,

Lucas Nussbaum wrote:
> Severity: serious
> Justification: FTBFS on amd64

This package's Architecture: fields do not include [linux-]amd64, so I
think this is not release-critical.  It is desirable though that we can
fix it to become possible (again) to build it on linux.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature