Bug#851828: oclgrind FTBFS on armhf: test failures

[Adrian Bunk]

Source: oclgrind
Version: 16.10-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=oclgrind=armhf=16.10-1=1484675768=0

...
  Start 75: uninitialized/uninitialized_local_array
  Start 76: uninitialized/uninitialized_local_ptr
73/86 Test #76: uninitialized/uninitialized_local_ptr 
.***Failed0.15 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

74/86 Test #74: uninitialized/uninitialized_address ...   
Passed0.36 sec
  Start 77: uninitialized/uninitialized_local_variable
  Start 78: uninitialized/uninitialized_packed_struct_memcpy
75/86 Test #75: uninitialized/uninitialized_local_array 
...***Failed0.27 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

  Start 79: uninitialized/uninitialized_padded_struct_memcpy
76/86 Test #77: uninitialized/uninitialized_local_variable    
Passed0.42 sec
77/86 Test #78: uninitialized/uninitialized_packed_struct_memcpy ..   
Passed0.41 sec
  Start 80: uninitialized/uninitialized_padded_nested_struct_memcpy
  Start 81: uninitialized/uninitialized_private_array
78/86 Test #79: uninitialized/uninitialized_padded_struct_memcpy ..   
Passed0.31 sec
79/86 Test #81: uninitialized/uninitialized_private_array 
.***Failed0.17 sec
Running test with optimisations
Test returned non-zero value (-7)
FAILED

  Start 82: wait_event/wait_event_chained
  Start 83: wait_event/wait_event_divergent
80/86 Test #80: uninitialized/uninitialized_padded_nested_struct_memcpy ...   
Passed0.28 sec
  Start 84: wait_event/wait_event_duplicates
81/86 Test #83: wait_event/wait_event_divergent ...   
Passed0.31 sec
82/86 Test #82: wait_event/wait_event_chained .   
Passed0.41 sec
  Start 85: wait_event/wait_event_invalid
  Start 86: rt_map_buffer
83/86 Test #84: wait_event/wait_event_duplicates ..   
Passed0.31 sec
84/86 Test #86: rt_map_buffer .   
Passed0.31 sec
85/86 Test #85: wait_event/wait_event_invalid .   
Passed0.31 sec
86/86 Test #32: bugs/many_alloca ..   
Passed   30.88 sec

97% tests passed, 3 tests failed out of 86

Total Test time (real) =  34.03 sec

The following tests FAILED:
 75 - uninitialized/uninitialized_local_array (Failed)
 76 - uninitialized/uninitialized_local_ptr (Failed)
 81 - uninitialized/uninitialized_private_array (Failed)
Errors while running CTest
Makefile:109: recipe for target 'test' failed
make[1]: *** [test] Error 8

Bug#849836: zekr: Missing dependency on libwebkitgtk-1.0-0

[Christoph Biedl]

Christoph Biedl wrote...

> That's indeed a no-brainer. I've prepared an NMU as below and will
> upload it to DELAYED/2 tomorrow.

Now uploaded, with a small fix:

> +  * Add install dependency on xserver-xorg-input-all. Closes: #849836

s/xserver-xorg-input-all/libwebkitgtk-1.0-0/

Christoph


signature.asc
Description: Digital signature

Processed: And re-add the fixed (sorry for the noise...)

[Debian Bug Tracking System]

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

> fixed 806917 16.04.0-1
Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package
Bug #810050 [src:ktp-call-ui] kde-telepathy-call-ui: can't install 
kde-telepathy-call-ui in sid (dependency conflicts)
Marked as fixed in versions ktp-call-ui/16.04.0-1.
Marked as fixed in versions ktp-call-ui/16.04.0-1.
> thanks
Stopping processing here.

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

Processed: And do the merge properly...

[Debian Bug Tracking System]

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

> reassign 810050 src:ktp-call-ui
Bug #810050 [kde-telepathy-call-ui] kde-telepathy-call-ui: can't install 
kde-telepathy-call-ui in sid (dependency conflicts)
Bug reassigned from package 'kde-telepathy-call-ui' to 'src:ktp-call-ui'.
No longer marked as found in versions ktp-call-ui/0.9.0-2.
Ignoring request to alter fixed versions of bug #810050 to the same values 
previously set
> forcemerge 806917 810050
Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package
Bug #810050 [src:ktp-call-ui] kde-telepathy-call-ui: can't install 
kde-telepathy-call-ui in sid (dependency conflicts)
Marked as found in versions ktp-call-ui/0.9.0-2.
Merged 806917 810050
> thanks
Stopping processing here.

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

Processed: I forgot to re-add the version

[Debian Bug Tracking System]

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

> found 806917 0.9.0-2
Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package
Marked as found in versions ktp-call-ui/0.9.0-2.
> thanks
Stopping processing here.

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

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

On Wed, Jan 18, 2017 at 02:21:04PM -0500, Lincoln Stein wrote:
> Yes, I'll remove it immediately and apply the patches to bio::graphics as
> well.

Fine.  Do you intend to do a micro release (say 2.56.1) after this change
or should I remove the file here locally for the time beeing?  Both would
be fine but I want to know in advance.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed (with 2 errors): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 806917 src:ktp-call-ui
Bug #806917 [ktp-call-ui] ktp-call-ui: build-depends on cruft package
Bug reassigned from package 'ktp-call-ui' to 'src:ktp-call-ui'.
No longer marked as found in versions 0.9.0-2.
No longer marked as fixed in versions 16.04.0-1.
> forcemerge 806917 810050
Bug #806917 [src:ktp-call-ui] ktp-call-ui: build-depends on cruft package
Unable to merge bugs because:
package of #810050 is 'kde-telepathy-call-ui' not 'src:ktp-call-ui'
Failed to forcibly merge 806917: Did not alter merged bugs.

> affects 806917 kde-telepathy-call-ui
Failed to mark 806917 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/806917 -- Unable to lock 
/org/bugs.debian.org/spool/lock/806917 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/806917 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.
-- 
806917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806917
810050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851726: liggghts: FTBFS on single-CPU machines (not enough slots available)

[Graham Inggs]

See #850229.

Processed: bug 851016 is forwarded to https://github.com/beetbox/beets/issues/2153

[Debian Bug Tracking System]

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

> forwarded 851016 https://github.com/beetbox/beets/issues/2153
Bug #851016 [src:beets] beets: FTBFS: Test failures
Set Bug forwarded-to-address to 'https://github.com/beetbox/beets/issues/2153'.
> thanks
Stopping processing here.

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

Bug#851016: beets: FTBFS: Test failures

[Carl Suster]

This looks like https://github.com/beetbox/beets/issues/2153 i.e. that the 
current version of mutagen that we have in Debian (1.36) is incompatible with 
the version of beets (1.3.19). Quoting from that issue:


 > when beets 1.3.19 was released, Mutagen 1.33 didn't exist yet.
 > When that was released, it changed the way exceptions work, which
 > broke those tests. We've since fixed compatibility with the
 > latest version, but we can't go back in time and change the
 > version specifier for 1.3.19.

So the easiest way to fix this will be to update to the latest upstream beets in 
Debian.

Bug#850230: marked as done (fabric: FTBFS (sbuild hangs))

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 03:48:52 +
with message-id 
and subject line Bug#850230: fixed in fabric 1.13.1-2
has caused the Debian Bug report #850230,
regarding fabric: FTBFS (sbuild hangs)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/fabric

[... snipped ...]

copying fabric/exceptions.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric
copying fabric/colors.py -> /<>/.pybuild/pythonX.Y_2.7/build/fabric
copying fabric/job_queue.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric
creating /<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
copying fabric/contrib/django.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
copying fabric/contrib/console.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
copying fabric/contrib/__init__.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
copying fabric/contrib/files.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
copying fabric/contrib/project.py -> 
/<>/.pybuild/pythonX.Y_2.7/build/fabric/contrib
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose tests
.Traceback
 (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 561, in process_request_thread
self.finish_request(request, client_address)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 320, in finish_request
self.RequestHandlerClass(request, client_address, self)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 631, in __init__
self.handle()
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/server.py", line 
361, in handle
if self.sudo_prompt and not self.sudo_password():
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/server.py", line 
426, in sudo_password
self.channel.send(env.sudo_prompt)
  File "/usr/lib/python2.7/dist-packages/paramiko/channel.py", line 715, in send
return self._send(s, m)
  File "/usr/lib/python2.7/dist-packages/paramiko/channel.py", line 1075, in 
_send
raise socket.error('Socket is closed')
error: Socket is closed
..Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 561, in process_request_thread
self.finish_request(request, client_address)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 320, in finish_request
self.RequestHandlerClass(request, client_address, self)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/tests/Python26SocketServer.py", 
line 631, in __init__
self.handle()
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/server.py", line 
361, in handle
if self.sudo_prompt and not self.sudo_password():
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/server.py", line 
426, in sudo_password
self.channel.send(env.sudo_prompt)
  File "/usr/lib/python2.7/dist-packages/paramiko/channel.py", line 715, in send
return self._send(s, m)
  File "/usr/lib/python2.7/dist-packages/paramiko/channel.py", line 1075, in 
_send
raise socket.error('Socket is closed')
error: Socket is closed
.
E: Build killed with signal TERM after 60 minutes of inactivity


This is just how the build ends, not necessarily the 

Bug#850230: fabric: FTBFS (sbuild hangs)

[Andrew Starr-Bochicchio]

On Thu, Jan 5, 2017 at 5:05 AM, Santiago Vila  wrote:
> The bug should be reproducible with sbuild on a single CPU virtual machine.
> It always fail for me (I tried 10 times in different autobuilders), and
> it also fails here:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fabric.html

Hi Santiago,

Thanks for the report. I had been unable to reproduce this. I tried
locally with both sbuild and pbuilder with no issues. So I spun up a
single CPU VM with an sbuild environment and was able to reproduce
this issue there. Adding another core to the VM, it built successfully
again. After some further debugging, I seem to have tracked the issue
down to a specific test:

https://github.com/fabric/fabric/blob/1.13.1/tests/test_tasks.py#L420

It's going to require some more detective work to find the root cause,
but for now I'm going to disable it as part of the package build.

Thanks,

-- Andrew Starr-Bochicchio

   Debian Developer 
   Ubuntu Developer 
   PGP/GPG Key ID: 3B56E2BBD53FDCB1

Bug#851634: marked as done (chromium: Chromium does not start after update)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 03:06:47 +
with message-id 
and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5
has caused the Debian Bug report #851634,
regarding chromium: Chromium does not start after update
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.)


-- 
851634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Starting chromium since latest upgrade ends up with the following message:
/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected 
(expecting "}")

It looks like it's related to a missing double-quote at the end of line 21 and 
it's fixed by the following patch:

21c21
<   echo "--enable-remote-extensions Allow extensions from remote sites
---
>   echo "--enable-remote-extensions Allow extensions from remote sites"


Best regards,


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.0-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 55.0.2883.75-5

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 19 Jan 2017 01:19:24 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-widevine chromium-driver 
chromedriver
Architecture: source
Version: 

Bug#851652: marked as done (chromium: syntax error reported in /usr/bin/chromium shell)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 03:06:47 +
with message-id 
and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5
has caused the Debian Bug report #851634,
regarding chromium: syntax error reported in /usr/bin/chromium shell
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.)


-- 
851634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 55.0.2883.75-4
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Upgrading chromium and running it from the command line produced the 
following output:

/usr/bin/chromium: line 122: syntax error near unexpected token `fi'
/usr/bin/chromium: line 122: `  fi'

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.10.0-rc4+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.1.3-2.0nosystemd1
ii  libdbus-1-3  1.10.14-1.0nosystemd1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:7-20161230-1
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5.0nosystemd1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.0-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 55.0.2883.75-5

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 19 Jan 2017 01:19:24 +
Source: chromium-browser
Binary: chromium 

Bug#851767: marked as done (chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 03:06:47 +
with message-id 
and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5
has caused the Debian Bug report #851634,
regarding chromium: Line 21 in the startup script /usr/bin/chromium is missing 
a terminating quote.
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.)


-- 
851634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser 
would not run.
I browsed the starting script /usr/bin/chromium and noticed that the string in 
line 21 is
missing a terminating quote. After adding that quote, the script worked OK.

Could you please add that quote?

Thank you for your service to the Debian community and users,

Grigor


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

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 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 chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 55.0.2883.75-5

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 19 Jan 2017 01:19:24 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-widevine chromium-driver 
chromedriver
Architecture: source
Version: 55.0.2883.75-5
Distribution: unstable
Urgency: medium
Maintainer: Debian 

Bug#851779: marked as done (chromium: crashes at startup)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 03:06:47 +
with message-id 
and subject line Bug#851634: fixed in chromium-browser 55.0.2883.75-5
has caused the Debian Bug report #851634,
regarding chromium: crashes at startup
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.)


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

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last recent release, chromium does not start anymore.

Wen typing the command in a shell, I get the following message:

---

chromium
/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected 
(expecting "}")---


--

but when having a look to the script, I do not understand why this 
syntax error appears.


Thanks in advance for your help !

Regards.

-- GD.


System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 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 chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 10:3.2.2-dmo3
ii  libavformat5710:3.2.2-dmo3
ii  libavutil55  10:3.2.2-dmo3
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 55.0.2883.75-5

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 19 Jan 2017 01:19:24 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-widevine chromium-driver 
chromedriver
Architecture: source
Version: 55.0.2883.75-5
Distribution: 

Bug#851820: libmojolicious-plugin-assetpack-perl: FTBFS: Failed 6/36 test programs. 20/242 subtests failed.

[Chris Lamb]

Source: libmojolicious-plugin-assetpack-perl
Version: 1.30-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

libmojolicious-plugin-assetpack-perl fails to build from source in 
unstable/amd64:

  […]

  Failed 2/10 subtests 
  t/reloader-process.t . skipped: cpanm CSS::Sass
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering template "index.html.ep" from 
DATA section
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.css". [36b3e7b800]
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00268s, 373.134/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/36b3e7b800/t-reloader.css"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00057s, 1754.386/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/mojo-assetpack-reloader-ws"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 101 Switching Protocols (0.000358s, 
2793.296/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering cached template "index.html.ep" 
from DATA section
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.css". [5958b3a722]
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.001898s, 526.870/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/5958b3a722/t-reloader.css"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.00088s, 1136.364/s)
  t/reloader.t . 
  ok 1 - GET /
  ok 2 - 200 OK
  ok 3 - element for selector "link[href="/asset/36b3e7b800/t-reloader.css"]" 
exists
  ok 4 - GET /asset/36b3e7b800/t-reloader.css
  ok 5 - exact match for content
  ok 6 - WebSocket handshake with /mojo-assetpack-reloader-ws
  ok 7 - WebSocket closed with status 1005
  ok 8 - GET /
  ok 9 - 200 OK
  ok 10 - element for selector "link[href="/asset/5958b3a722/t-reloader.css"]" 
exists
  ok 11 - GET /asset/5958b3a722/t-reloader.css
  ok 12 - exact match for content
  1..12
  ok
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:26 2017] [debug] Processed asset "app.js". [7373328564]
  [Thu Jan 19 14:02:26 2017] [debug] GET "/"
  [Thu Jan 19 14:02:26 2017] [debug] Rendering template "index.html.ep" from 
DATA section
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.002382s, 419.815/s)
  [Thu Jan 19 14:02:26 2017] [debug] GET "/asset/7373328564/r1.tag"
  [Thu Jan 19 14:02:26 2017] [debug] Routing to a callback
  [Thu Jan 19 14:02:26 2017] [debug] 200 OK (0.000522s, 1915.709/s)
  t/riotjs-not-loaded.t  
  ok 1 - GET /
  ok 2 - 200 OK
  ok 3 - element for selector "link[href="/asset/7373328564/r1.tag"]" exists
  ok 4 - GET /asset/7373328564/r1.tag
  ok 5 - 200 OK
  ok 6 - Content-Type: text/css
  ok 7 - content is similar
  1..7
  ok
  t/riotjs.t ... skipped: TEST_RIOTJS=1
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  [Thu Jan 19 14:02:27 2017] [debug] Processed asset "app.css". [681090d69b]
  t/route.t  
  ok 1 - one route
  ok 2 - two routes
  1..2
  ok
  t/sass-bin.t . skipped: TEST_SASS=1
  t/sass-dynamic-include.t . skipped: cpanm CSS::Sass
  t/sass-functions.t ... skipped: cpanm CSS::Sass
  t/sass-unable-to-download.t .. skipped: TEST_ONLINE=1
  t/sass-utf8.t  skipped: cpanm CSS::Sass
  t/sass.t . skipped: cpanm CSS::Sass
  t/typescript.t ... skipped: TEST_TYPESCRIPT=1
  t/util.t . 
  ok 1 - no_builder read-only
  ok 2 - no_builder
  ok 3 - no_builder with value
  ok 4 - with_builder read-only
  ok 5 - with_builder
  ok 6 - diag foo
  ok 7 - diag foo bar
  ok 8 - chdir
  ok 9 - back on track
  ok 10 - _install_gem
  ok 11 - _install_node
  ok 12 - _install_ruby
  1..12
  ok
  Mojo::Home::parse is DEPRECATED at t/Helper.pm line 22.
  Mojo::Home::rel_dir is DEPRECATED in favor of Mojo::Home::rel_file at 
«BUILDDIR»/blib/lib/Mojolicious/Plugin/AssetPack.pm line 28.
  Mojo::Home::parts is DEPRECATED at 

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 851634 851767 851779 851652
Bug #851634 [chromium] chromium: Chromium does not start after update
Bug #851767 [chromium] chromium: Line 21 in the startup script 
/usr/bin/chromium is missing a terminating quote.
Added tag(s) patch.
Bug #851779 [chromium] chromium: crashes at startup
Added tag(s) patch.
Bug #851652 [chromium] chromium: syntax error reported in /usr/bin/chromium 
shell
Severity set to 'grave' from 'normal'
Added tag(s) patch.
Merged 851634 851652 851767 851779
> thanks
Stopping processing here.

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

Bug#851817: Vendoring libraries

[Haruki TSURUMOTO]

Package: prometheus
Version: 1.2.3+ds2-5
Severity: serious
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org

Dear maintainers,
Prometheus depends on many libraries, including source codes located
into vendor directory.
Is this a violation for Debian Policy 4.13 ?
"4.13 Convenience copies of code"
https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

Some libraries of vendor/*  had already packaged in Debian,
 (ex: golang-github-hashicorp-go-cleanhttp-dev,
golang-github-hashicorp-consul-dev)
Can't we use these instead of vendoring method ?

Regards,

-- 
Haruki TSURUMOTO
PGP Fingerprint:3718 C84E 4EDA 1B5C 4F26 8639 9D3D EE3F 63A6 000E

Processed: severity of 810050 is serious, severity of 851513 is serious

[Debian Bug Tracking System]

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

> severity 810050 serious
Bug #810050 [kde-telepathy-call-ui] kde-telepathy-call-ui: can't install 
kde-telepathy-call-ui in sid (dependency conflicts)
Severity set to 'serious' from 'important'
> severity 851513 serious
Bug #851513 [zfs-dkms] Build fails with Linux kernel 4.9.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#851790: installation-reports: DNS not working

[Cyril Brulebois]

Cyril Brulebois  (2017-01-19):
> Summing up things from IRC:
>  - in an uptodate sid chroot (both development version and minimal one
>with daily-build script): no DNS issues with the generated mini.iso
>(amd64, tested within stable's kvm on amd64). My image was also
>tested successfully by Steve, so not a setup issue.
> 
>  - I can reproduce the issue with dailies from 2017-01-18, and from
>2017-01-19 (I picked it in advance during its build on barriere).
> 
>  - I can reproduce the issue in the above mentioned sid chroot if
>I downgrade these packages to testing's version (-9 → -8):
>  sudo apt-get install libc6:amd64=2.24-8 libc6-dev:amd64=2.24-8 
> libc-dev-bin=2.24-8
> 
>  - The older set of libc* packages is installed in barriere's current
>amd64 sid chroot, too.
> 
>  - Steve could only produce broken images when building locally, until
>he upgraded his libc* packages as well.

And since Steve was wondering how we could release something for Stretch
RC 1 with that… I've just confirmed that using -8 .deb with a -8 .udeb
(reversioned as -9+hack so that its being dropped under localudebs makes
it take precedence over sid's .udeb) leads to an image that's working
fine. And AFAICT that's the combination we had at the time.

I suspect the implementation change through the following patch in -9:
glibc-2.24/debian/patches/any/cvs-resolv-internal-qtype.diff

plus 283e7a294275a7da53258600deaaafbbec6b96c1 in debian-installer.git is
what is triggering the issue? (Explaining why host's libc .deb have an
impact on the built images.)

It's been a while since I last looked at/understood mklibs stuff though,
feel free to fix my suspicions/conclusions.


KiBi.


signature.asc
Description: Digital signature

Bug#851814: apt-build: Broken postinst by less permissive sed

[Santiago Vila]

Package: apt-build
Version: 0.12.45
Severity: serious
Tags: patch

Dear QA Group:

Installing apt-build results in this error:

Setting up apt-build (0.12.45) ...
sed: character class syntax is [[:space:]], not [:space:]
dpkg: error processing package apt-build (--configure):
 subprocess installed post-installation script returned error exit
status 4
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 apt-build

Discovered by Antonio Trujillo here:

https://lists.debian.org/msgid-search/dd7864af-d235-217c-74dc-bd1b5a086...@juntadeandalucia.es

I think the following trivial patch should fix it, but I'm not
confident enough to push it to git because version in Debian archives
does not exactly match HEAD in git.

Thanks.

--- a/debian/postinst
+++ b/debian/postinst
@@ -75,7 +75,7 @@ if [ "$1" = "configure" ] ; then
 if [ -e "$source" ] ; then
# comment in all sources lists if asked
if [ "$add_to_sourceslist" = "false" ] ; then
-sed -i -e "s|^[:space:]*$debline.*|#$debline|" "$source"
+sed -i -e "s|^[[:space:]]*$debline.*|#$debline|" "$source"
   
   # check if source entry is already enabled
   elif grep -Eq "^[[:space:]]*$debline" "$source" ; then
@@ -149,12 +149,12 @@ if [ "$1" = "configure" ] ; then
   test -z "make_options" || grep -Eq '^[[:space:]]*make_options =' $CONFFILE 
|| \
 echo "make_options =" >> $CONFFILE
   
-  sed -e "s|^[:space:]*build-dir =.*|build-dir = $build_dir|" \
-  -e "s|^[:space:]*repository-dir =.*|repository-dir = $repository_dir|" \
-  -e "s|^[:space:]*Olevel =.*|Olevel = $Olevel|" \
-  -e "s|^[:space:]*mtune =.*|mtune = $mtune|" \
-  -e "s|^[:space:]*options =.*|options = \" $options\"|" \
-  -e "s|^[:space:]*make_options =.*|make_options = \" $make_options\"|" \
+  sed -e "s|^[[:space:]]*build-dir =.*|build-dir = $build_dir|" \
+  -e "s|^[[:space:]]*repository-dir =.*|repository-dir = $repository_dir|" 
\
+  -e "s|^[[:space:]]*Olevel =.*|Olevel = $Olevel|" \
+  -e "s|^[[:space:]]*mtune =.*|mtune = $mtune|" \
+  -e "s|^[[:space:]]*options =.*|options = \" $options\"|" \
+  -e "s|^[[:space:]]*make_options =.*|make_options = \" $make_options\"|" \
   < $CONFFILE > $CONFFILE.tmp
   
   mv -f $CONFFILE.tmp $CONFFILE

Bug#851790: installation-reports: DNS not working

[Cyril Brulebois]

Cyril Brulebois  (2017-01-19):
> You can try downgrading the kernel, but I'd usually look at glibc first
> for DNS related issues.

Summing up things from IRC:
 - in an uptodate sid chroot (both development version and minimal one
   with daily-build script): no DNS issues with the generated mini.iso
   (amd64, tested within stable's kvm on amd64). My image was also
   tested successfully by Steve, so not a setup issue.

 - I can reproduce the issue with dailies from 2017-01-18, and from
   2017-01-19 (I picked it in advance during its build on barriere).

 - I can reproduce the issue in the above mentioned sid chroot if
   I downgrade these packages to testing's version (-9 → -8):
 sudo apt-get install libc6:amd64=2.24-8 libc6-dev:amd64=2.24-8 
libc-dev-bin=2.24-8

 - The older set of libc* packages is installed in barriere's current
   amd64 sid chroot, too.

 - Steve could only produce broken images when building locally, until
   he upgraded his libc* packages as well.


→ Copying glibc@packages for the time being, even I suspect this will
  likely disappear entirely once -9 propagates…


KiBi.


signature.asc
Description: Digital signature

Bug#850970: marked as done (pvpgn: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 00:19:30 +
with message-id 
and subject line Bug#850970: fixed in pvpgn 1.8.5-2.1
has caused the Debian Bug report #850970,
regarding pvpgn: switch to build depend on the metapackage 
default-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.)


-- 
850970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pvpgn
Version: 1.8.5-2
Severity: serious
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertags: default-mysql

Hi,

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL.

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html

Please update the depencies accordingly. In most cases the required
change is:

* BEFORE: Build-Depends: libmysqlclient-dev

* AFTER: Build-Depends: default-libmysqlclient-dev

Cheers,
Emilio


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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pvpgn
Source-Version: 1.8.5-2.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pvpgn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 17 Jan 2017 00:45:35 +0100
Source: pvpgn
Binary: pvpgn
Architecture: source
Version: 1.8.5-2.1
Distribution: unstable
Urgency: medium
Maintainer: Radu Spineanu 
Changed-By: Andreas Beckmann 
Description:
 pvpgn  - gaming server that emulates Battle.net(R)
Closes: 848482 850970
Changes:
 pvpgn (1.8.5-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch Build-Depends to default-libmysqlclient-dev.  (Closes: #850970)
   * Switch Suggests to default-mysql-* | virtual-mysql-*.  (Closes: #848482)
   * Use secure, canonical Vcs-* URLs.
Checksums-Sha1:
 3add2d57fc8133824d27e5d7250f54ecbd070800 1961 pvpgn_1.8.5-2.1.dsc
 c9fd4c37288996c6628cf3f3accc75580b67c772 14784 pvpgn_1.8.5-2.1.debian.tar.xz
Checksums-Sha256:
 6b54ba0c4e228b24f3998d764dab169908b48c29eda7094f7c56f62f1a1f3247 1961 
pvpgn_1.8.5-2.1.dsc
 9a97cf718219ec8b5aa2fd9fb76f74a734b1995a7bbd1e03d964b7a94cf90061 14784 
pvpgn_1.8.5-2.1.debian.tar.xz
Files:
 5924566faec5b219c66d074af9606488 1961 contrib/net optional pvpgn_1.8.5-2.1.dsc
 c6c4809a1104ee1139597ceaecff63d6 14784 contrib/net optional 
pvpgn_1.8.5-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfVyRAAoJEF+zP5NZ6e0ITtwP/136rZPaUBWlauK8LCGKJfhH
uegI9RgBYMa3JsK91jbch99vncXZ9A+2mqoXk1s0PH7qtGhLXBsssIRp9aOsK8FU
95fiivyTgbrjU4AkPdxGbsKFiJ76D3Rkqaa67afLZ20s0C4BQpOLMzpY2jCyXsnG
K+Pjm1hXSVaGGtoZ4JaFFnCGTD4kS08yRMt6gbFmrqWmTblvMit4MWrhjK1evnK+
b68MiSR//eazg/F6stVB0aBmqplsR9vzp/6C984waJVf0nJ00aqzx0x1D5yeKHw7
KNrQ2aZTtUbWDuzsphrWjF8SfsT2BwVn6DEL5y8V877HuGOvkXkgIX0b2lIphUji
vudTGsN7YmuqJk8hIh2fVZhGzVJG6pKdxtG8sqpF8Li3vrerA8qRrl7Vm3e/qMsc
zkMekTOtb0Xzk3CJ7IbfapPoKEzd+xOS7LVwVsdI4rb5QkvyynvwNkilRIHRlRY5
DaH80Rc5Sc9i5G7GAFkyIlWY7/YTwTMfz5GXTdz+/D52Zir+kgnJt/STtzaisko0
v2YpEYUlbIV4r5p1d8VwPn7wQxJRonAgpyMhitsGG2fOmVm0h7WB1eD28ee03VG5
ZEsydCZZZzlQZmyZmgQrAWfAPj/crk/wmkJo0nuS/OHhjQsv9zl9lOOM+PhgOCjC
KHlL3xFexFkft3wbXCGw
=s06H
-END PGP 

Bug#845830: marked as done (cl-sql: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Thu, 19 Jan 2017 00:03:51 +
with message-id 
and subject line Bug#845830: fixed in cl-sql 6.7.0-1.1
has caused the Debian Bug report #845830,
regarding cl-sql: switch to build depend on the metapackage 
default-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.)


-- 
845830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-sql
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: cl-sql
Source-Version: 6.7.0-1.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated cl-sql package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 17 Jan 2017 00:29:15 +0100
Source: cl-sql
Binary: cl-sql cl-sql-uffi cl-sql-mysql cl-sql-aodbc cl-sql-odbc 
cl-sql-postgresql cl-sql-postgresql-socket cl-sql-sqlite cl-sql-sqlite3 
cl-sql-oracle cl-sql-tests
Architecture: source
Version: 6.7.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kevin M. Rosenberg 
Changed-By: Andreas Beckmann 
Description:
 cl-sql - SQL Interface for Common Lisp
 cl-sql-aodbc - CLSQL database backend, AODBC
 cl-sql-mysql - CLSQL database backend, MySQL
 cl-sql-odbc - CLSQL database backend, ODBC
 cl-sql-oracle - CLSQL database backend, Oracle
 cl-sql-postgresql - CLSQL database backend, PostgreSQL via library
 cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL via sockets
 cl-sql-sqlite - CLSQL database backend, SQLite
 cl-sql-sqlite3 - CLSQL database backend, SQLite3
 cl-sql-tests - Testing suite for CLSQL
 cl-sql-uffi - Common UFFI functions for CLSQL database backends
Closes: 845830
Changes:
 cl-sql (6.7.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch (Build-)Depends to default-libmysqlclient-dev.  (Closes: #845830)
Checksums-Sha1:
 1d0bd9cbc96afe26e783bc137756b592c3050ffa 2374 cl-sql_6.7.0-1.1.dsc
 2fb4c302f8616eeb1deb6659f01b953ad513b032 11272 cl-sql_6.7.0-1.1.debian.tar.xz
Checksums-Sha256:
 400090ee275f62ac328b6d898244df9ed49210abd210de59ef87fabdc57d6e59 2374 
cl-sql_6.7.0-1.1.dsc
 ea9ccfc16251f3ed52a9416762565e4a254ca1b742d335d9fe9409105fdd08e5 11272 
cl-sql_6.7.0-1.1.debian.tar.xz
Files:
 3aeb4fef1ad5fd45c0f19fef7739c1a4 2374 lisp extra cl-sql_6.7.0-1.1.dsc
 195ee6a969ba50de42903cc96c671a49 11272 lisp extra 
cl-sql_6.7.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfVeVAAoJEF+zP5NZ6e0Ik2oP/2/CtBu1CpmRIzepk/DZANue
oMI2tYb20O91JcpICMoeTOBdg+hLNxIqn00xLTSLvN7Yzmar4a+5pENn98GShm2y
qdW7Wx8QgFE8vp5IZedt2PXUDW6HRDII8WV93LzEZKFjKiYjUUvPkY7LEiBZs1bI
euZ2obMWGRyLrg2zegFBfo1mB6asFhKe9R6/igATyEVINle3JzwYiBNS3phjwNMA
0+RsqQMtji1jjfe9Cn2juHv7/Gk/3X+uIlJ1NoUjORXL7uFCUq0qXZVHVRwey8gn
/CrsYMRUTMgKLIZkXORsnfQ4naaLhUnugUYfxZUPXS0Cc8SCPhQGdKxTLGwTsLSI
YzM7DbqzDZzAP2HJU8tmdDC8AbeQto/tlc0OuEHszDusPTdKAXitNYZAWAYOorWJ
pW0aaFPNgjcFGCB7xJGmiAvSxD0rYBTf9synKvA4/C+slbAZrMmBCuT6IAKjKxOX
3jEWQYuEZlR4kfNKgDp6aWEr9b8PYTq0/GZ2Um4kjCyHheDvc54Gmnv4r31WO1EK
fwUv7mp5xg1XadQPwnHgvxN7OWZRbCAc8CgC5rmJy3pnW0MKWl7e81T8vm/DcyEi
5Pp0H2Wjvin0aten1dlXeBSmk28oUaWWXxThlIetSsvcfAfdsA1pTGENXuWaxg60

Bug#851812: seed-webkit2 autoreconf FTBFS

[Adrian Bunk]

Source: seed-webkit2
Version: 4.0.0+20161014+6c77960+dfsg1-3
Severity: serious

https://buildd.debian.org/status/package.php?p=seed-webkit2=sid

...
set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
--copyright --deb-fmt --ignore 
'^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
/usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: /usr/bin/licensecheck: not found
0 combinations of copyright and licensing found.
diff: debian/copyright_hints: No such file or directory
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
dh_autoreconf debian/rules -- autoreconf
make[1]: Entering directory 
'/«BUILDDIR»/seed-webkit2-4.0.0+20161014+6c77960+dfsg1'
CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
enable.
./autogen.sh
You need to install gnome-common from GNOME SVN and make
sure the gnome-autogen.sh script is in your $PATH.
debian/rules:15: recipe for target 'autoreconf' failed
make[1]: *** [autoreconf] Error 1

Processed: tag 783615 pending

[Debian Bug Tracking System]

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

> tag 783615 pending
Bug #783615 {Done: Michael Shuler } [ca-certificates] 
"update-ca-certificates --fresh" doesn't correctly re-add certificates in 
/usr/local/share/ca-certificates
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

[Bálint Réczey]

Hi,

2017-01-14 23:54 GMT+01:00 Adrian Bunk :
> Control: retitle -1 ffmpeg: ChromaprintContext FTBFS
> Control: forwarded -1 https://trac.ffmpeg.org/ticket/5997
> Control: tags -1 fixed-upstream
>
> On Sat, Jan 14, 2017 at 06:47:02AM +0100, Carl Eugen Hoyos wrote:
>> The relevant lines in the build log are afaict:
>>
>> src/libavformat/chromaprint.c: In function 'write_packet':
>> src/libavformat/chromaprint.c:113:1: error: control reaches end of non-void
>> function [-Werror=return-type]
>>  }
>>  ^
>>
>> The function looks like this:
>>
>> static int write_packet(AVFormatContext *s, AVPacket *pkt)
>> {
>> ChromaprintMuxContext *cpr = s->priv_data;
>> return chromaprint_feed(cpr->ctx, pkt->data, pkt->size / 2) ? 0 :
>> AVERROR(EINVAL);
>> }
>>
>> I guess this is a compiler bug.
>
> No, you should only look at the first compile error in that file:
>
> src/libavformat/chromaprint.c:42:24: error: field 'ctx' has incomplete type
>  ChromaprintContext ctx;
> ^~~
> This is the actual error.
>
> Whatever the compiler comes up with for cpr->ctx in the place you quoted
> might be garbage, but at that point it is already game over.
>
> Upstream fix:
>   
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=581f93f37ef2e7a00662828ed0348d1edb9041fe
>
>> Carl Eugen

Is there a new FFmpeg upstream release on the horizon or I should just
update the package with a cherry-picked patch?

Cheers,
Balint

Bug#851790: installation-reports: DNS not working

[Cyril Brulebois]

Steve McIntyre  (2017-01-18):
> For the sake of completeness, I can confirm that the same problem
> shows up when running on a different network too. I also see this
> using the oldest amd64 daily I can grab (from 2017-01-17) which has
> the 4.9 kernel too.
> 
> I'll see if I can debug this, but I'm not sure where to look straight
> away.

You can try downgrading the kernel, but I'd usually look at glibc first
for DNS related issues.


KiBi.


signature.asc
Description: Digital signature

Bug#850998: marked as done (erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 23:03:47 +
with message-id 
and subject line Bug#850998: fixed in erlang-ranch 1.2.1-3
has caused the Debian Bug report #850998,
regarding erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: 
/etc/asciidoc/dblatex/asciidoc-dblatex.xsl
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.)


-- 
850998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-ranch
Version: 1.2.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 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 '/<>'
>  GENdistclean-asciidoc
> a2x -v -f pdf doc/src/guide/book.asciidoc && mv doc/src/guide/book.pdf 
> doc/guide.pdf
> a2x: ERROR: missing configuration file: 
> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
> a2x: args: ['--dblatex-opts', '-P latex.output.revhistory=0 -P 
> doc.publisher.show=0 -P index.numbered=0', '-d', 'book', '--attribute', 
> 'tabsize=4', '-v', '-f', 'pdf', 'doc/src/guide/book.asciidoc']
> a2x: resource files: []
> a2x: resource directories: ['/etc/asciidoc/images', 
> '/etc/asciidoc/stylesheets']
> a2x: executing: "/usr/bin/asciidoc" --backend docbook -a "a2x-format=pdf"  
> --doctype book --attribute "tabsize=4" --verbose  --out-file 
> "/<>/doc/src/guide/book.xml" 
> "/<>/doc/src/guide/book.asciidoc"
> 
> asciidoc: reading: /etc/asciidoc/asciidoc.conf
> asciidoc: reading: /<>/doc/src/guide/book.asciidoc
> asciidoc: reading: /etc/asciidoc/docbook45.conf
> asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf
> asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf
> asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf
> asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf
> asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf
> asciidoc: reading: /etc/asciidoc/lang-en.conf
> asciidoc: writing: /<>/doc/src/guide/book.xml
> asciidoc: include: /<>/doc/src/guide/introduction.asciidoc
> asciidoc: book.asciidoc: line 6: reading: 
> /<>/doc/src/guide/introduction.asciidoc
> asciidoc: include: /<>/doc/src/guide/listeners.asciidoc
> asciidoc: book.asciidoc: line 8: reading: 
> /<>/doc/src/guide/listeners.asciidoc
> asciidoc: include: /<>/doc/src/guide/transports.asciidoc
> asciidoc: book.asciidoc: line 10: reading: 
> /<>/doc/src/guide/transports.asciidoc
> asciidoc: include: /<>/doc/src/guide/protocols.asciidoc
> asciidoc: book.asciidoc: line 12: reading: 
> /<>/doc/src/guide/protocols.asciidoc
> asciidoc: include: /<>/doc/src/guide/embedded.asciidoc
> asciidoc: book.asciidoc: line 14: reading: 
> /<>/doc/src/guide/embedded.asciidoc
> asciidoc: include: /<>/doc/src/guide/parsers.asciidoc
> asciidoc: book.asciidoc: line 16: reading: 
> /<>/doc/src/guide/parsers.asciidoc
> asciidoc: include: /<>/doc/src/guide/ssl_auth.asciidoc
> asciidoc: book.asciidoc: line 18: reading: 
> /<>/doc/src/guide/ssl_auth.asciidoc
> asciidoc: include: /<>/doc/src/guide/internals.asciidoc
> asciidoc: book.asciidoc: line 20: reading: 
> /<>/doc/src/guide/internals.asciidoc
> 
> a2x: executing: "xmllint" --nonet --noout --valid 
> "/<>/doc/src/guide/book.xml"
> 
> 
> erlang.mk:5062: recipe for target 'asciidoc-guide' failed
> make[2]: *** [asciidoc-guide] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/erlang-ranch_1.2.1-2_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: erlang-ranch
Source-Version: 1.2.1-3

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated 

Bug#850998: [Pkg-leofs-devel] Bug#850998: erlang-ranch: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Bálint Réczey]

Hi Nobuhiro,

I have uploaded the fix but the packaging repo does not contain your
latest upload.
In case you have it offline please upload it or we can import the
history from the .dsc

Cheers,
Balint

2017-01-11 20:07 GMT+01:00 Lucas Nussbaum :
> Source: erlang-ranch
> Version: 1.2.1-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170111 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 '/<>'
>>  GENdistclean-asciidoc
>> a2x -v -f pdf doc/src/guide/book.asciidoc && mv doc/src/guide/book.pdf 
>> doc/guide.pdf
>> a2x: ERROR: missing configuration file: 
>> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
>> a2x: args: ['--dblatex-opts', '-P latex.output.revhistory=0 -P 
>> doc.publisher.show=0 -P index.numbered=0', '-d', 'book', '--attribute', 
>> 'tabsize=4', '-v', '-f', 'pdf', 'doc/src/guide/book.asciidoc']
>> a2x: resource files: []
>> a2x: resource directories: ['/etc/asciidoc/images', 
>> '/etc/asciidoc/stylesheets']
>> a2x: executing: "/usr/bin/asciidoc" --backend docbook -a "a2x-format=pdf"  
>> --doctype book --attribute "tabsize=4" --verbose  --out-file 
>> "/<>/doc/src/guide/book.xml" 
>> "/<>/doc/src/guide/book.asciidoc"
>>
>> asciidoc: reading: /etc/asciidoc/asciidoc.conf
>> asciidoc: reading: /<>/doc/src/guide/book.asciidoc
>> asciidoc: reading: /etc/asciidoc/docbook45.conf
>> asciidoc: reading: /etc/asciidoc/filters/source/source-highlight-filter.conf
>> asciidoc: reading: /etc/asciidoc/filters/graphviz/graphviz-filter.conf
>> asciidoc: reading: /etc/asciidoc/filters/music/music-filter.conf
>> asciidoc: reading: /etc/asciidoc/filters/latex/latex-filter.conf
>> asciidoc: reading: /etc/asciidoc/filters/code/code-filter.conf
>> asciidoc: reading: /etc/asciidoc/lang-en.conf
>> asciidoc: writing: /<>/doc/src/guide/book.xml
>> asciidoc: include: /<>/doc/src/guide/introduction.asciidoc
>> asciidoc: book.asciidoc: line 6: reading: 
>> /<>/doc/src/guide/introduction.asciidoc
>> asciidoc: include: /<>/doc/src/guide/listeners.asciidoc
>> asciidoc: book.asciidoc: line 8: reading: 
>> /<>/doc/src/guide/listeners.asciidoc
>> asciidoc: include: /<>/doc/src/guide/transports.asciidoc
>> asciidoc: book.asciidoc: line 10: reading: 
>> /<>/doc/src/guide/transports.asciidoc
>> asciidoc: include: /<>/doc/src/guide/protocols.asciidoc
>> asciidoc: book.asciidoc: line 12: reading: 
>> /<>/doc/src/guide/protocols.asciidoc
>> asciidoc: include: /<>/doc/src/guide/embedded.asciidoc
>> asciidoc: book.asciidoc: line 14: reading: 
>> /<>/doc/src/guide/embedded.asciidoc
>> asciidoc: include: /<>/doc/src/guide/parsers.asciidoc
>> asciidoc: book.asciidoc: line 16: reading: 
>> /<>/doc/src/guide/parsers.asciidoc
>> asciidoc: include: /<>/doc/src/guide/ssl_auth.asciidoc
>> asciidoc: book.asciidoc: line 18: reading: 
>> /<>/doc/src/guide/ssl_auth.asciidoc
>> asciidoc: include: /<>/doc/src/guide/internals.asciidoc
>> asciidoc: book.asciidoc: line 20: reading: 
>> /<>/doc/src/guide/internals.asciidoc
>>
>> a2x: executing: "xmllint" --nonet --noout --valid 
>> "/<>/doc/src/guide/book.xml"
>>
>>
>> erlang.mk:5062: recipe for target 'asciidoc-guide' failed
>> make[2]: *** [asciidoc-guide] Error 1
>
> The full build log is available from:
>http://aws-logs.debian.net/2017/01/11/erlang-ranch_1.2.1-2_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.
>
> ___
> Pkg-leofs-devel mailing list
> pkg-leofs-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-leofs-devel

Processed: Re: zekr: Missing dependency on libwebkitgtk-1.0-0

[Debian Bug Tracking System]

Processing control commands:

> tags 849836 confirmed patch pending
Bug #849836 [zekr] zekr: Missing dependency on libwebkitgtk-1.0-0
Added tag(s) confirmed, patch, and pending.

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

Bug#849836: zekr: Missing dependency on libwebkitgtk-1.0-0

[Christoph Biedl]

Control: tags 849836 confirmed patch pending

Awtul wrote...

> Installing "libwebkitgtk-1.0-0" solves the problem. I thought it may
> be a dependency missing issue.

That's indeed a no-brainer. I've prepared an NMU as below and will
upload it to DELAYED/2 tomorrow.

Regards,

Christoph

diff -Nru zekr-1.1.0+repack/debian/changelog zekr-1.1.0+repack/debian/changelog
--- zekr-1.1.0+repack/debian/changelog  2015-07-30 18:07:11.0 +0200
+++ zekr-1.1.0+repack/debian/changelog  2017-01-18 23:13:43.0 +0100
@@ -1,3 +1,10 @@
+zekr (1.1.0+repack-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add install dependency on xserver-xorg-input-all. Closes: #849836
+
+ -- Christoph Biedl   Wed, 18 Jan 2017 
23:13:43 +0100
+
 zekr (1.1.0+repack-2) unstable; urgency=medium
 
   * debian/control:
diff -Nru zekr-1.1.0+repack/debian/control zekr-1.1.0+repack/debian/control
--- zekr-1.1.0+repack/debian/control2015-07-30 18:07:11.0 +0200
+++ zekr-1.1.0+repack/debian/control2017-01-18 23:13:13.0 +0100
@@ -41,6 +41,7 @@
  libswt-cairo-gtk-3-jni,
  libswt-gnome-gtk-3-jni,
  libswt-webkit-gtk-3-jni | libswt-mozilla-gtk-3-jni,
+ libwebkitgtk-1.0-0,
  zenity,
  libjs-jquery,
  ttf-sil-scheherazade | ttf-kacst (>= 1.6.2+mry-1) | ttf-farsiweb


signature.asc
Description: Digital signature

Bug#851803: ntp: FTBFS (mv: cannot stat 'debian/tmp/usr/bin/ntpdate': No such file or directory)

[Santiago Vila]

Package: src:ntp
Version: 1:4.2.8p9+dfsg-2
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]

Installing stand-alone HTML documentation
make[4]: Leaving directory '/<>/ntp-4.2.8p9+dfsg'
make[3]: Leaving directory '/<>/ntp-4.2.8p9+dfsg'
make[2]: Leaving directory '/<>/ntp-4.2.8p9+dfsg'
make[1]: Leaving directory '/<>/ntp-4.2.8p9+dfsg'
# move the administrator programs from /usr/bin to /usr/sbin
for file in ntpdate ntp-wait ntpd ntptime ntp-keygen; do \
mv debian/tmp/usr/bin/$file debian/tmp/usr/sbin/$file || exit; \
done
mv: cannot stat 'debian/tmp/usr/bin/ntpdate': No such file or directory
debian/rules:50: recipe for target 'install' failed
make: *** [install] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The same failure happens in the reproducible builds autobuilders:

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

so I guess this should be easy to reproduce on a current stretch chroot.

Apparently ntpdate is already installed into usr/sbin and that's
why it does not exist in usr/bin anymore.

If that's the case, the trivial but untested patch below
would probably fix the problem (unless more binaries
are also in usr/sbin).

Because the same package version of ntp used to build in the past,
this is surely caused by a build-dependency that changed
behaviour.

So you might want to contact the maintainer of such build-dependency
that broke this and get a promise that the behaviour will not
change again between now and the release of stretch.

Thanks.

--- a/debian/rules
+++ b/debian/rules
@@ -55,7 +55,7 @@ install: build-stamp
$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
 
# move the administrator programs from /usr/bin to /usr/sbin
-   for file in ntpdate ntp-wait ntpd ntptime ntp-keygen; do \
+   for file in ntp-wait ntpd ntptime ntp-keygen; do \
mv debian/tmp/usr/bin/$$file debian/tmp/usr/sbin/$$file || 
exit; \
done
 

Bug#850026: marked as done (vmtk: transitive B-D on both libssl-dev and libssl1.0-dev)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 22:06:10 +
with message-id 
and subject line Bug#850026: fixed in vmtk 1.3+dfsg-2.1
has caused the Debian Bug report #850026,
regarding vmtk: transitive B-D on both libssl-dev and libssl1.0-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.)


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

Hi,

vmtk cannot be built any longer, since it transitively Build-Depends on
both libssl-dev and libssl1.0-dev which conflict with each other.


Andreas
--- End Message ---
--- Begin Message ---
Source: vmtk
Source-Version: 1.3+dfsg-2.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated vmtk 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: Wed, 18 Jan 2017 23:36:18 +0200
Source: vmtk
Binary: libvmtk1.3 python-vmtk libvmtk-dev vmtk
Architecture: source
Version: 1.3+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Adrian Bunk 
Description:
 libvmtk-dev - shared links and header files for vmtk
 libvmtk1.3 - runtime libraries for vmtk
 python-vmtk - Python interface for vmtk
 vmtk   - the Vascular Modeling Toolkit
Closes: 850026
Changes:
 vmtk (1.3+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS by using OpenSSL 1.0.2. (Closes: #850026)
Checksums-Sha1:
 b1ef52c662c1fe1107cae9cdc6742336e220e537 2417 vmtk_1.3+dfsg-2.1.dsc
 ace7d8bb899a412b2a05c86ab5185b27b02843b5 15372 vmtk_1.3+dfsg-2.1.debian.tar.xz
Checksums-Sha256:
 7f6d4239c325d613af43810ad392d2eb7639bc8df2a96a0b90ba15f3801a7dc6 2417 
vmtk_1.3+dfsg-2.1.dsc
 61065848f6b92e5650e25cf1ba728fbfad8c3bd1b7953f53096250ecdafbd782 15372 
vmtk_1.3+dfsg-2.1.debian.tar.xz
Files:
 b1fdb960923be08a4252e932f941ee47 2417 non-free/science optional 
vmtk_1.3+dfsg-2.1.dsc
 963e640d4d95442cd78282aaacfb5373 15372 non-free/science optional 
vmtk_1.3+dfsg-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh/4nwACgkQiNJCh6LY
mLH2oA//dhUT7zgRteID9dajOwt8sN3xvLcXmOsOZkm1AAZ2AjVBp1SLUe+VDrXF
LrcR1T1RlltTecsGXS9FZuDqHjeTHep/0YuiM82hPawDa40phZl7x9E9OxOCaKLg
MuaoxYeol3eu6wvlwnv9vILqdpWvQzGB5dyxNblXjm1EwNcvN86WmcQE0BhKagEP
ZSlap11eAFXbKMKqIbAWemDwTRoeEtblNMAi4q/WQ/eSYDwfk0gb0OoSfIG5lo5k
TrURwWNG2M1NVDQltwc1ECWI9mlZR+SIShvUQHip1LhGWJyHYQdMoJvw019Rh8BO
GohLrTlFoJ1aQplipfWwV8BVZwipRzWaD+3q3VOXWdGw7ZvpK8ZolGbkyLhh/+S2
dBEf7f/4wyzZl9pwtba8Smtmc+yc01YkN1a08CuWp4yV+incxqgdBQowIJ6b2ukA
vYzHVcltsIvkLx3Px7hZywoW2Y9sbTL+1v7z8m4BJlob5XqKfOzB0SMEJvGd4SqX
lbMTlMWQ0BzuQwPYrfAX0H+ueygl8yMAZBKZYIlqj7z+3FK7WvRDqpcVnizIKz2A
cjASPIVhQUvnqmyJwMfHHq6bcr92zjO41StvMIEPHNWQJsieJMFlgHcgMC8/IZkx
g/Q1F77wjYZKYR6+mY8gtJSUL/CKFnMwVJSwXv107Saxihe/2bA=
=/vbM
-END PGP SIGNATURE End Message ---

Bug#851726: marked as done (liggghts: FTBFS on single-CPU machines (not enough slots available))

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 22:04:34 +
with message-id 
and subject line Bug#851726: fixed in liggghts 3.5.0+repack1-9
has caused the Debian Bug report #851726,
regarding liggghts: FTBFS on single-CPU machines (not enough slots available)
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.)


-- 
851726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liggghts
Version: 3.5.0+repack1-8
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/liggghts-3.5.0+repack1/debian/build --parallel
   dh_testdir -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
   dh_auto_configure -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.5.0\+repack1/debian/build 
-O--parallel
cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var
-- The C compiler identification is GNU 6.2.1
-- The CXX compiler identification is GNU 6.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/mpicxx   
-Dlibliggghts_EXPORTS 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/eigen3 
-I/<>/liggghts-3.5.0+repack1 
-I/<>/liggghts-3.5.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/write_dump.cpp.o -c 
/<>/liggghts-3.5.0+repack1/src/write_dump.cpp
[ 98%] Building CXX object src/CMakeFiles/libliggghts.dir/write_restart.cpp.o
cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/mpicxx   
-Dlibliggghts_EXPORTS 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/eigen3 
-I/<>/liggghts-3.5.0+repack1 
-I/<>/liggghts-3.5.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/write_restart.cpp.o -c 
/<>/liggghts-3.5.0+repack1/src/write_restart.cpp
[ 99%] Linking CXX shared library libliggghts.so
cd /<>/liggghts-3.5.0+repack1/debian/build/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/libliggghts.dir/link.txt --verbose=1
/usr/bin/mpicxx  -fPIC -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.5.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG 
-Wl,-z,relro -Wl,--as-needed  -shared -Wl,-soname,libliggghts.so.3 -o 
libliggghts.so.3.3.1 CMakeFiles/libliggghts.dir/angle.cpp.o 
CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/atom.cpp.o CMakeFiles/libliggghts.dir/atom_map.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_atomic.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_charge.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_ellipsoid.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_line.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sph.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sph_var.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sphere.cpp.o 
CMakeFiles/libliggghts.dir/atom_vec_sphere_w.cpp.o CMakeFiles/libliggghts.dir/
 bond.cpp.o CMakeFiles/libliggghts.dir/bond_hybrid.cpp.o 
CMakeFiles/libliggghts.dir/bounding_box.cpp.o 
CMakeFiles/libliggghts.dir/cfd_datacoupling.cpp.o 
CMakeFiles/libliggghts.dir/cfd_datacoupling_file.cpp.o 

Bug#783615: "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates

[Michael Shuler]

On 01/18/2017 03:25 PM, Adrian Bunk wrote:
> after a discussion with someone who ran into this bug in stable I have 
> set the severity to serious, since this should IMHO also be fixed in 
> stable.

This does look like a good patch to backport to stable. I'll get this
commited to git and work on a stable update. Thanks, Adrian!

-- 
Kind regards,
Michael

Processed: severity of 851795 is serious

[Debian Bug Tracking System]

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

> severity 851795 serious
Bug #851795 [src:systemd] [MIPS] Forced local symbol rearranging messes up GOT
Ignoring request to change severity of Bug 851795 to the same value.
> thanks
Stopping processing here.

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

Bug#783615: "update-ca-certificates --fresh" doesn't correctly re-add certificates in /usr/local/share/ca-certificates

[Adrian Bunk]

Hi,

after a discussion with someone who ran into this bug in stable I have 
set the severity to serious, since this should IMHO also be fixed in 
stable.

It is a very nasty bug when something works on the first execution of
a command but not on subsequent executions, and the fix looks really
trivial.

cu
Adrian

-- 

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

Bug#850885: marked as done (apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 21:19:01 +
with message-id 
and subject line Bug#850885: fixed in dwww 1.13.3
has caused the Debian Bug report #850885,
regarding apache2: Using dwww, fails with internal server error when trying to 
access /usr/share/doc
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.)


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

Dear Maintainer,

Upgrading from jessie to stretch partially broke the package "dwww" when
using apache2 as web server. dwww is a CGI web application allowing
easy access to the Debian documentation. Its entry page still works on
stretch, but when trying to access any resource under /usr/share/doc
through dwww, Apache returns an "500 Internal Server Error".

To reproduce the problem one just has to go to http://localhost/dwww,
and click on the top menu link for "/usr/share/doc".

When looking at the Apache log, the following entry can be found:

[Fri Jan 06 21:34:53.830541 2017] [http:error] [pid 6785:tid
140419151554304] [client ::1:45220] AH02429: Response header name
'Last modified' contains invalid characters, aborting request,
referer: http://localhost/dwww/

When calling the dwww CGI script manually, the 'Last modified' field
is correct however, here's the HTTP header part:

Content-type: text/html
Last modified: Tue Dec 13 14:16:35 2016
Content-Disposition: inline; filename="index.html"

When using the very same dwww application with another web server (I
tried lighttpd), it works fine as before so the issue is related to
Apache.

Compared to a default apache2 configuration, I just enabled the cgid
module as well as the dwww, dhelp and dpkg-dwww configurations. No
other changes under /etc/apache2. 

Thanks

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.25-1
ii  apache2-data 2.4.25-1
ii  apache2-utils2.4.25-1
ii  dpkg 1.18.18
ii  init-system-helpers  1.46
ii  lsb-base 9.20161125
ii  mime-support 3.60
ii  perl 5.24.1~rc4-1
pn  perl:any 
ii  procps   2:3.3.12-3

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.38

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   55.0.2883.75-3
ii  konqueror [www-browser]  4:16.08.3-1
ii  w3m [www-browser]0.5.3-33

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-5
ii  libaprutil1  1.5.4-3
ii  libaprutil1-dbd-sqlite3  1.5.4-3
ii  libaprutil1-ldap 1.5.4-3
ii  libc62.24-8
ii  libldap-2.4-22.4.44+dfsg-2
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libnghttp2-141.17.0-1
ii  libpcre3 2:8.39-2
ii  libssl1.0.2  1.0.2j-4
ii  libxml2  2.9.4+dfsg1-2.1
pn  perl:any 
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   55.0.2883.75-3
ii  konqueror [www-browser]  4:16.08.3-1
ii  w3m [www-browser]0.5.3-33

Versions of packages apache2 is related to:
ii  apache2  2.4.25-1
ii  apache2-bin  2.4.25-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dwww
Source-Version: 1.13.3

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

Debian distribution 

Processed: tor: IPv6 connections through tor do not appear to work

[Debian Bug Tracking System]

Processing control commands:

> block 849845 with -1
Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore
Bug #850606 [dirmngr] dirmngr: can't resolve ipv6 addresses when use-tor is 
enabled
849845 was not blocked by any bugs.
849845 was not blocking any bugs.
Added blocking bug(s) of 849845: 851798
850606 was not blocked by any bugs.
850606 was not blocking any bugs.
Added blocking bug(s) of 850606: 851798
> affects -1 dirmgnr
Bug #851798 [tor] tor: IPv6 connections through tor do not appear to work
Added indication that 851798 affects dirmgnr

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

Processed: Unarchive and mark RC

[Debian Bug Tracking System]

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

> unarchive 783615
Bug #783615 {Done: Michael Shuler } [ca-certificates] 
"update-ca-certificates --fresh" doesn't correctly re-add certificates in 
/usr/local/share/ca-certificates
Unarchived Bug 783615
> severity 783615 serious
Bug #783615 {Done: Michael Shuler } [ca-certificates] 
"update-ca-certificates --fresh" doesn't correctly re-add certificates in 
/usr/local/share/ca-certificates
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#839443: bcron: some failing test disabled for now

[Gianfranco Costamagna]

control: severity -1 important

Hi, I'm downgrading this one, to make the current bcron have chances to 
migrated.

I think tests should be fixed, but disabling a couple of them "fixed" the 
build, and
will probably make it go in Stretch

G.



signature.asc
Description: OpenPGP digital signature

Processed: bcron: some failing test disabled for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #839443 [src:bcron] bcron: FTBFS: tests failures
Severity set to 'important' from 'serious'

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

Processed: Tag

[Debian Bug Tracking System]

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

> tags 762400 stretch sid
Bug #762400 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0 has 
a direct Build-Depends on itself
Bug #824982 {Done: Michael Biebl } [src:gtk+3.0] src:gtk+3.0: 
unsatisfiable dependency on libgtk-3-common
Bug #824999 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0: 
Architecture: all packages cannot be built
Added tag(s) stretch and sid.
Added tag(s) stretch and sid.
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#828468: marked as done (openhpi: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 20:53:05 +
with message-id 
and subject line Bug#828468: fixed in openhpi 3.6.1-2.1
has caused the Debian Bug report #828468,
regarding openhpi: 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.)


-- 
828468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openhpi
Version: 3.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/openhpi_3.6.1-2_amd64-20160529-1459

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: openhpi
Source-Version: 3.6.1-2.1

We believe that the bug you reported is fixed in the latest version of
openhpi, 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.
Adrian Bunk  (supplier of updated openhpi 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: Wed, 18 Jan 2017 21:45:48 +0200
Source: openhpi
Binary: libopenhpi3 libopenhpi-dev openhpid openhpi-clients 
openhpi-plugin-ilo2-ribcl openhpi-plugin-ipmi openhpi-plugin-ipmidirect 
openhpi-plugin-oa-soap openhpi-plugin-slave openhpi-plugin-test-agent 
openhpi-plugin-snmp-bc openhpi-plugin-sysfs openhpi-plugin-watchdog 
openhpi-plugin-simulator openhpi-plugin-dynamic-simulator openhpi 
libopenhpi3-dbgsym openhpid-dbgsym openhpi-clients-dbgsym 
openhpi-plugin-ilo2-ribcl-dbgsym openhpi-plugin-ipmi-dbgsym 
openhpi-plugin-ipmidirect-dbgsym openhpi-plugin-oa-soap-dbgsym 
openhpi-plugin-slave-dbgsym openhpi-plugin-test-agent-dbgsym 
openhpi-plugin-snmp-bc-dbgsym openhpi-plugin-sysfs-dbgsym 
openhpi-plugin-watchdog-dbgsym openhpi-plugin-simulator-dbgsym 
openhpi-plugin-dynamic-simulator-dbgsym
Architecture: source
Version: 3.6.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bryan Sutula 
Changed-By: Adrian Bunk 
Description:
 libopenhpi-dev - OpenHPI libraries (development files)
 libopenhpi3 - OpenHPI libraries (runtime and support files)
 libopenhpi3-dbgsym - Debug symbols for libopenhpi3 library
 openhpi- SAF's HPI: Abstracted interface for managing computer hardware
 openhpi-clients - OpenHPI example client programs
 openhpi-clients-dbgsym - Debug symbols for OpenHPI example client programs
 openhpi-plugin-dynamic-simulator - OpenHPI plugin module for a dynamic 
simulator
 openhpi-plugin-dynamic-simulator-dbgsym - Debug symbols for 
openhpi-plugin-dynamic-simulator plugin module
 openhpi-plugin-ilo2-ribcl - OpenHPI plugin module for HP's ProLiant rackmount 
servers
 openhpi-plugin-ilo2-ribcl-dbgsym - Debug symbols for openhpi-plugin-ilo2-ribcl 
plugin module
 openhpi-plugin-ipmi - OpenHPI plugin module for OpenIPMI
 openhpi-plugin-ipmi-dbgsym - Debug symbols for openhpi-plugin-ipmi plugin 
module
 openhpi-plugin-ipmidirect - OpenHPI plugin module for direct IPMI over LAN 
(RMCP) or SMI
 openhpi-plugin-ipmidirect-dbgsym - Debug symbols for openhpi-plugin-ipmidirect 
plugin module
 openhpi-plugin-oa-soap - OpenHPI plugin module for HP's BladeSystem c-Class
 openhpi-plugin-oa-soap-dbgsym - Debug symbols for openhpi-plugin-oa-soap 
plugin module
 openhpi-plugin-simulator - OpenHPI plugin module for a simulator that works 
without hardware
 openhpi-plugin-simulator-dbgsym - Debug symbols for openhpi-plugin-simulator 
plugin module
 openhpi-plugin-slave - OpenHPI plugin module for slave plugin
 

Bug#851792: palo ships binary in the sources

[Adrian Bunk]

Package: palo
Version: 1.95
Severity: serious

>From debian/rules:

@if [ `dpkg --print-architecture` = hppa ]; \
 then \
echo "Regenerating iplboot."; \
$(MAKE) realclean; \
$(MAKE) iplboot; \
 else \
echo "Leaving iplboot in place since we're not building on 
hppa."; \
 fi

Since hppa isn't part of jessie or stretch, there is no option to build
this package on *any* machine inside this release.

Looks like a clear GPL violation to me.

If palo should continue to be available on non-hppa machines,
a (binary-all) package that uses gcc-hppa-linux-gnu for building
might be an option.

Bug#805988: aboot : include the binaries in source to build on amd64

[Adrian Bunk]

On Wed, Jan 18, 2017 at 06:54:10PM +0100, Santiago Vila wrote:
> On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:
> 
> > I wonder if the following solution would be accepted (see the two patches 
> > attached) : let the source package ship the two binaries (bootlx and 
> > net_aboot.nh). [...]
> 
> Hmm, but this is like removing a hack and creating another one in another 
> place.
> 
> The previous package was a "fake" Arch:all package, so to speak, and now
> we would have a "fake" source package, as it would include binaries.
> 
> We don't want binaries inside source packages (and I think ftpmasters
> would surely agree on this).
> 
> If alpha is not a release architecture, would it really be a problem
> to remove this from testing before the release of stretch while we keep it in
> unstable?
> 
> We could meet the release goal of all packages being buildable
> in our Arch:all autobuilder that way without causing a major headache
> to users of alpha.
> 
> Alternatively, there is also the possibility of asking the Release
> Managers for permission to use stretch-ignore here.

"Arch:all autobuilder" is only part of the problem, since alpha won't be 
part of stretch there is no option to build this package on *any* machine
running stretch.

Looks like a clear GPL violation to me.

As Steve already suggested, using the gcc-alpha-linux-gnu package might 
be an option for building aboot.

I'll open a similar bug against palo.

> Thanks.

cu
Adrian

-- 

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

Bug#851790: installation-reports: DNS not working

[Steve McIntyre]

On Wed, Jan 18, 2017 at 06:43:33PM +, Wookey wrote:
>Package: installation-reports
>Severity: grave
>Tags: d-i
>Justification: renders package unusable
>
>Dear Maintainer,
>
>The current installer, with the new 4.9 kernel, is unable to resolve
>domains, so is quite seriously broken.

hosts, not domains, but yes...

>This was noted during install on an arm64 gigabyte MP30-AR1
>desktop/server, when choose-mirror failed, but it soon became clear
>that DNS was not working.
>
>Testing on an x86 VM with the same daily image (18th Jan 2017) found
>the same problem. Going back to the rc1 installer image (4.8 kernel)
>it works OK.
>
>Tests showed that the network came up fine and things are pingable by IP, but 
>not name:
># ping wookware.org   
>ping: bad address 'wookware.org'
># ping 93.93.131.118
>PING 93.93.131.118 (93.93.131.118): 56 data bytes
>64 bytes from 93.93.131.118: seq=0 ttl=50 time=19.892 ms
>
>similarly the failing line from the choose-mirror log works if an address is 
>inserted:
>Jan 18 17:04:11 choose-mirror[31201]: DEBUG: command: wget --no-verbose 
>http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | 
>grep -E '^(Suite|Codename|Architectures):' 
>  
>Jan 18 17:04:11 choose-mirror[31201]: WARNING **: mirror does not support the 
>specified release (stretch) 
>
># wget --no-verbose 
>http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | 
>grep -E '^(Suite|Codename|Architectures):'
>wget: unable to resolve host address 'debian-mirror.cambridge.arm.com'
>
># wget --no-verbose http://10.1.194.51/debian/dists/stretch/Release -O - | gre
>p -E '^(Suite|Codename|Architectures):'
>Suite: testing
>Codename: stretch
>Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
>2017-01-18 17:47:12 URL:http://10.1.194.51/debian/dists/stretch/Release 
>[177979/177979] -> "-" [1]
>
>resolv.conf is as expected:
>search cambridge.arm.com
>nameserver 10.1.2.24
>nameserver 10.1.2.23
>
>(adding nameserver 8.8.8.8 makes no difference)
>
>Watching packets go by when doing a VM install it is clear that the
>local DNS server returns the correct response, but this is being ignored
>or lost by the D-I initrd.

For the sake of completeness, I can confirm that the same problem
shows up when running on a different network too. I also see this
using the oldest amd64 daily I can grab (from 2017-01-17) which has
the 4.9 kernel too.

I'll see if I can debug this, but I'm not sure where to look straight
away.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Yes, I'll remove it immediately and apply the patches to bio::graphics as
well.

Lincoln

On Wed, Jan 18, 2017 at 11:58 AM, Andreas Tille  wrote:

> On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> > >
> > >https://anonscm.debian.org/cgit/debian-med/gbrowse.git/
> tree/debian/patches
> >
> > Oh, cool, adding the (build)-dep is really enough, no patching
> > required. Nice.
>
> Yes, we needed this for another package ...
>
> > For stretch, I think there's still one thing to do:
> > autopkgtest still fails with
> >
> > pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to
> overwrite '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz',
> which is also in package libbio-perl-perl 1.7.1-2
>
> Urgs - Lincoln, I guess it makes sense to remove this copy of bioperl
> even in your distribution.  What do you think?
>
> Kind regards
>
>Andreas.
>
>
> --
> http://fam-tille.de
>



-- 
*Lincoln Stein*

Scientific Director (Interim), Ontario Institute for Cancer Research
Director, Informatics and Bio-computing Program, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto


*Ontario Institute for Cancer Research*
MaRS Centre
661 University Avenue
Suite 510
Toronto, Ontario
Canada M5G 0A3

Tel: 416-673-8514
Mobile: 416-817-8240
Email: lincoln.st...@gmail.com
Toll-free: 1-866-678-6427
Twitter: @OICR_news

*Executive Assistant*
*Lisa Duncan*
Tel: 647-260-7970 <(647)%20260-7970>
Email: lisa.dun...@oicr.on.ca 
www.oicr.on.ca

This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

Processed: tagging 851039

[Debian Bug Tracking System]

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

> tags 851039 + help
Bug #851039 [src:python-apt] python-apt: FTBFS: Test failures
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#851579: marked as done (lcdproc: fails to install: post-installation script returned error exit status 10)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 19:03:59 +
with message-id 
and subject line Bug#851579: fixed in lcdproc 0.5.8~rc2-1
has caused the Debian Bug report #851579,
regarding lcdproc: fails to install: post-installation script returned error 
exit status 10
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.)


-- 
851579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcdproc
Version: 0.5.8~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package lcdproc.
  (Reading database ... 
(Reading database ... 8007 files and directories currently installed.)
  Preparing to unpack .../lcdproc_0.5.8~rc1-1_amd64.deb ...
  Unpacking lcdproc (0.5.8~rc1-1) ...
  Setting up lcdproc (0.5.8~rc1-1) ...
  dpkg: error processing package lcdproc (--configure):
   subprocess installed post-installation script returned error exit status 10
  Errors were encountered while processing:
   lcdproc


Is that a debconf question not being asked since piuparts runs the tests with
DEBIAN_FRONTEND=noninteractive ?


cheers,

Andreas


lcdproc_0.5.8~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lcdproc
Source-Version: 0.5.8~rc2-1

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

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated lcdproc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 19:29:02 +0100
Source: lcdproc
Binary: lcdproc lcdproc-extra-drivers lcdproc-dbg
Architecture: source
Version: 0.5.8~rc2-1
Distribution: experimental
Urgency: medium
Maintainer: Dominique Dumont 
Changed-By: Dominique Dumont 
Description:
 lcdproc- LCD display driver daemon and clients
 lcdproc-dbg - debugging symbols for lcdproc
 lcdproc-extra-drivers - extra drivers for the LCD display driver daemon
Closes: 851579
Changes:
 lcdproc (0.5.8~rc2-1) experimental; urgency=medium
 .
   * New upstream version 0.5.8~rc2
   * control: build-dep on cme >= 1.016-2 to deliver
 debconf files (Closes: #851579)
Checksums-Sha1:
 dd9c29450a99d616d5ca73caac7764c7f45a90ef 2644 lcdproc_0.5.8~rc2-1.dsc
 1e1efdcb8fb3b22c0b2f2ced4991f68d653d38fd 905790 lcdproc_0.5.8~rc2.orig.tar.gz
 0b77dbeced4dbff0829069847f2a591014c65fa5 14420 
lcdproc_0.5.8~rc2-1.debian.tar.xz
Checksums-Sha256:
 399e152e6e76117a87daed67bebe66890185eebc6d9cbcf18c620f185f3a78e2 2644 
lcdproc_0.5.8~rc2-1.dsc
 5748ee9198f8900c976e8291a531bb32ff7589a357c426dbc9d26e05287b1207 905790 
lcdproc_0.5.8~rc2.orig.tar.gz
 7b6cbadcb84e3e461bfe36f9a3055c244f9085241db1074b5740ccb7cea8f152 14420 
lcdproc_0.5.8~rc2-1.debian.tar.xz
Files:
 9c00c455199f33b50b4b53eb5baa6875 2644 utils extra lcdproc_0.5.8~rc2-1.dsc
 7b3fc854e003f2bf7e0f3f77224c789e 905790 utils extra 
lcdproc_0.5.8~rc2.orig.tar.gz
 ee07fdb46950d2220c2bd6a0edc934b2 14420 utils extra 
lcdproc_0.5.8~rc2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAlh/uNIACgkQwx9P2Umr
K2wVyQ//aiKF+R4kYLknV0vmgzv7hS8HqBEytLAOMyGT5fkQjknbGry8nlHMKMQ5
8Z6zGeISsRyT+XcVtZt9ZGO/5yn3OcoRFLh0e9hXhSiiUtsHP16Jp1+SH+jYy18O
JdJOHnjypKVRIo7YDrqN4sje1aKbxBigNVuwHqU2Aax64aMq87bXE+ECykRf4V/f
u3J5v8WXGlDVz7CSDaK7Z6Dpn1ga4HG0j2Dm4ehZhOggf+pkw11H2WdLXztZmQQq
gAHnyyTO0X4dirU9eXUZwludKsY51SyJld4TL4tjqjfVmEeQM0sITYpszF7lR0ip
I/gG79P9RYkm3+POeI/uh4aLynmivsebc/83txU/DXThk3Xb3nG07nbi83c8/CsZ
Mo+gkqZLAAcYTEykk2/BL+ngE7i79VDjYYLz+dVSxAhinXog+FEFRUqnPcZ5B4Bm
bDweNmtjjnbPXQQW5DuqtJyV8PbLy56l3v1MTJ8JzC3TAxIR2vVpdIcV7YLRa9PE
ZT/4Jr6FluDRMJM0vdFg8GEDuWuTfIE1SWNxeza+769bIOGAr8FaQ7kuJn5E06gU

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Lisandro Damián Nicanor Pérez Meyer]

On martes, 17 de enero de 2017 22:21:51 ART Rebecca N. Palmer wrote:
[snip] 
> This suggests the fix (warning: untested and not my area of expertise -
> and if it is using that line, why is there no -Wl,--no-whole-archive in
> the build log?):

This part I don't know.

> --- a/tools/llvm-shlib/CMakeLists.txt
> +++ b/tools/llvm-shlib/CMakeLists.txt
> @@ -42,7 +42,7 @@
>   list(REMOVE_DUPLICATES LIB_NAMES)
>   if("${CMAKE_SYSTEM_NAME}" STREQUAL "Linux" OR "${CMAKE_SYSTEM_NAME}"
> STREQUAL "GNU" OR "${CMAKE_SYSTEM_NAME}" STREQUAL "kFreeBSD") # FIXME:
> It should be "GNU ld for elf"
> # GNU ld doesn't resolve symbols in the version script.
> -  set(LIB_NAMES -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
> +  set(LIB_NAMES
> -Wl,--version-script,../../../tools/llvm-shlib/simple_version_script.map
> -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
>   elseif("${CMAKE_SYSTEM_NAME}" STREQUAL "Darwin")
> set(LIB_NAMES -Wl,-all_load ${LIB_NAMES})
>   endif()
> --- a/dev/null
> +++ b/simple_version_script.map
> @@ -0,0 +1,1 @@
> +LLVM_3.9 { global: *; };

Probably the "../../../tools" path should be replaced by $
{CMAKE_CURRENT_SOURCE_DIR}/tools

> (Should also work with the obvious change for 3.8; I haven't checked
> 3.7.  Deliberately not making 3.9 "depend" on 3.8, as the whole point is
> to make the linker treat them as separate libraries)

Right.

> Some LLVM-using libraries use -Bsymbolic to avoid similar problems (e.g.
> #768185), but I don't know whether enabling that on LLVM itself would
> help: it may well be papering over a problem that symbol versioning
> would really solve.

Right.

-- 
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#851790: installation-reports: DNS not working

[Wookey]

Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

The current installer, with the new 4.9 kernel, is unable to resolve
domains, so is quite seriously broken.

This was noted during install on an arm64 gigabyte MP30-AR1
desktop/server, when choose-mirror failed, but it soon became clear
that DNS was not working.

Testing on an x86 VM with the same daily image (18th Jan 2017) found
the same problem. Going back to the rc1 installer image (4.8 kernel)
it works OK.

Tests showed that the network came up fine and things are pingable by IP, but 
not name:
# ping wookware.org   
ping: bad address 'wookware.org'
# ping 93.93.131.118
PING 93.93.131.118 (93.93.131.118): 56 data bytes
64 bytes from 93.93.131.118: seq=0 ttl=50 time=19.892 ms

similarly the failing line from the choose-mirror log works if an address is 
inserted:
Jan 18 17:04:11 choose-mirror[31201]: DEBUG: command: wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'   

Jan 18 17:04:11 choose-mirror[31201]: WARNING **: mirror does not support the 
specified release (stretch) 

# wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'
wget: unable to resolve host address 'debian-mirror.cambridge.arm.com'

# wget --no-verbose http://10.1.194.51/debian/dists/stretch/Release -O - | gre
p -E '^(Suite|Codename|Architectures):'
Suite: testing
Codename: stretch
Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
2017-01-18 17:47:12 URL:http://10.1.194.51/debian/dists/stretch/Release 
[177979/177979] -> "-" [1]

resolv.conf is as expected:
search cambridge.arm.com
nameserver 10.1.2.24
nameserver 10.1.2.23

(adding nameserver 8.8.8.8 makes no difference)

Watching packets go by when doing a VM install it is clear that the
local DNS server returns the correct response, but this is being ignored
or lost by the D-I initrd.

attached is an strace of strace ping wookware.org > /tmp/tracelog 2>&1

That gets a response from the server OK, but then goes on to ask the
other one. a working strace then uses the provided IP address. So
there is nothing obviously going wrong there.

-- Package-specific info:

Boot method: USB
Image version: 
http://gemmei.acc.umu.se/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
Date: 

Machine: Gigabyte MP30-AR1, (and x86 VM)
Partitions: (default guided LVM, with separate /home chosen)


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[E]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Worked as expected until DNS needed

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

removed automatic info as this report written on different machine fro install.
execve("/bin/ping", ["ping", "wookware.org"], [/* 14 vars */]) = 0
brk(NULL)   = 0xc9893000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x86677000
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/aarch64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/aarch64", 0xc66b2660, 0) = 
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = 
-1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls", 0xc66b2660, 0) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/aarch64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/aarch64", 0xc66b2660, 0) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu", {st_mode=S_IFDIR|0755, 
st_size=360, ...}, 0) = 0
openat(AT_FDCWD, 

Bug#838665: /usr/lib/python3/dist-packages/speechd_config/config.py: runs argparse on Python module import

[Adrian Bunk]

On Mon, Sep 26, 2016 at 02:16:45PM +0200, Sebastian Humenda wrote:
> Hi

Hi Sebastian,

> I'll provide a patch to upstream shortly and attach it here as well, so that 
> it
> is fixed both upstream and downstream.

any news regarding that?

> Sebastian

Thanks
Adrian

-- 

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

Bug#811945: marked as done (ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal operator)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 20:14:12 +0200
with message-id <20170118181412.xh64oottft7jewcr@localhost>
and subject line Fixed in 2.10.11-3
has caused the Debian Bug report #811945,
regarding ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal 
operator
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.)


-- 
811945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ucimf-openvanilla
Version: 2.10.11-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-literal-operator

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>  -I../include   -g -O2 -c -o openvanilla_la-openvanilla.lo `test -f 
> 'openvanilla.cpp' || echo './'`openvanilla.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -c 
> openvanilla.cpp  -fPIC -DPIC -o .libs/openvanilla_la-openvanilla.o
> In file included from openvanilla.cpp:26:0:
> openvanilla.cpp: In member function 'virtual void OVImfService::notify(const 
> char*)':
> debug.h:9:93: error: unable to find string literal operator 
> 'operator""format' with 'const char [9]', 'long unsigned int' arguments
>  #define UCIMF_DEBUG(format...)  {extern int LogFd; if( LogFd >=0 ){ 
> dprintf( LogFd, "[DEBUG]:"format);} }
>   
>^
> 
> debug.h:12:28: note: in expansion of macro 'UCIMF_DEBUG'
>  #define UrDEBUG(format...) UCIMF_DEBUG(format)
> ^~~
> 
> openvanilla.cpp:147:2: note: in expansion of macro 'UrDEBUG'
>   UrDEBUG( "%s\n", msg );
>   ^~~
> 
> Makefile:333: recipe for target 'openvanilla_la-openvanilla.lo' failed
> make[3]: *** [openvanilla_la-openvanilla.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 2.10.11-3


ucimf-openvanilla (2.10.11-3) unstable; urgency=medium
...
  * Fix GCC-6 compiling error.
...
 -- ChangZhuo Chen (陳昌倬)   Wed, 18 Jan 2017 19:56:54 +0800


cu
Adrian

-- 

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

Bug#749661: marked as done (ifuse: Segfault)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 19:57:32 +0200
with message-id <20170118175732.nwmnfecckaxvyibo@localhost>
and subject line Re: Bug#749661: ifuse: Segfault
has caused the Debian Bug report #749661,
regarding ifuse: Segfault
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.)


-- 
749661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifuse
Version: 1.1.2-0.1+b2
Severity: grave

Hello,

I get a segfault when trying to mount my phone. I think this is the
backtrace:

Program terminated with signal 11, Segmentation fault.
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.


Looking for strlen.S on my machine:

$ locate strlen.S
/usr/src/linux-source-3.10/arch/alpha/lib/ev67-strlen.S
/usr/src/linux-source-3.10/arch/alpha/lib/strlen.S
/usr/src/linux-source-3.10/arch/arc/lib/strlen.S
/usr/src/linux-source-3.10/arch/ia64/lib/strlen.S
/usr/src/linux-source-3.10/arch/m32r/lib/strlen.S
/usr/src/linux-source-3.10/arch/sh/lib/strlen.S
/usr/src/linux-source-3.10/arch/sh/lib64/strlen.S
/usr/src/linux-source-3.10/arch/sparc/lib/strlen.S



Best regards,

George

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

Kernel: Linux 3.14-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

Versions of packages ifuse depends on:
ii  fuse   2.9.3-10
ii  libc6  2.18-7
ii  libfuse2   2.9.3-10
ii  libimobiledevice4  1.1.6+dfsg-1
ii  libplist2  1.11-3

ifuse recommends no packages.

ifuse suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jan 09, 2017 at 07:49:26PM +, George B. wrote:
> Hi Andreas,
> 
> I have successfully used ifuse since then so I think this bug is safe to 
> close.

Thanks for the update, I am closing it now.

> Best regards,
> 
> George

cu
Adrian

-- 

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

Bug#805988: aboot : include the binaries in source to build on amd64

[Santiago Vila]

On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:

> I wonder if the following solution would be accepted (see the two patches 
> attached) : let the source package ship the two binaries (bootlx and 
> net_aboot.nh). [...]

Hmm, but this is like removing a hack and creating another one in another place.

The previous package was a "fake" Arch:all package, so to speak, and now
we would have a "fake" source package, as it would include binaries.

We don't want binaries inside source packages (and I think ftpmasters
would surely agree on this).

If alpha is not a release architecture, would it really be a problem
to remove this from testing before the release of stretch while we keep it in
unstable?

We could meet the release goal of all packages being buildable
in our Arch:all autobuilder that way without causing a major headache
to users of alpha.

Alternatively, there is also the possibility of asking the Release
Managers for permission to use stretch-ignore here.

Thanks.

Processed: Re: Bug#789407: unable to send openpgp messages

[Debian Bug Tracking System]

Processing control commands:

> tags 789407 unreproducible
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Added tag(s) unreproducible.
> severity 789407 normal
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Severity set to 'normal' from 'grave'

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

Bug#789407: unable to send openpgp messages

[Christoph Biedl]

Control: tags 789407 unreproducible
Control: severity 789407 normal

Lowering severity as this problem was not reproducible, and the original
submitter did not provide additional information upon request.

Christoph


signature.asc
Description: Digital signature

Bug#832656: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:33:27 +
with message-id 
and subject line Bug#832656: fixed in bcron 0.10-4
has caused the Debian Bug report #832656,
regarding runit: breaks users of runit: ln: failed to create symbolic link 
'/etc/service/bcron-sched': No such file or directory
to be marked as done.

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

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


-- 
832656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package bcron-run.
  (Reading database ... 
(Reading database ... 6995 files and directories currently installed.)
  Preparing to unpack .../bcron-run_0.10-3_all.deb ...
  Unpacking bcron-run (0.10-3) ...
  Setting up bcron-run (0.10-3) ...
  Installing new version of config file /etc/crontab ...
  Adding system user `cron' (UID 151) ...
  Adding new group `cron' (GID 152) ...
  Adding new user `cron' (UID 151) with group `cron' ...
  Not creating home directory `/var/spool/cron'.
  Warning: The home dir /nonexistent you specified can't be accessed: No such 
file or directory
  Adding system user `cronlog' (UID 152) ...
  Adding new user `cronlog' (UID 152) with group `nogroup' ...
  Not creating home directory `/nonexistent'.
  ln: failed to create symbolic link '/etc/service/bcron-sched': No such file 
or directory
  dpkg: error processing package bcron-run (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bcron-run

Similar problems were seen in different *-run packages.


cheers,

Andreas


bcron-run_0.10-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bcron
Source-Version: 0.10-4

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated bcron package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 23 Aug 2016 15:42:04 +0300
Source: bcron
Binary: bcron bcron-run
Architecture: source amd64 all
Version: 0.10-4
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Dmitry Bogatov 
Description:
 bcron  - ${S:Short-Desc} (programs)
 bcron-run  - ${S:Short-Desc} (integration with runit)
Closes: 832656
Changes:
 bcron (0.10-4) unstable; urgency=medium
 .
   * Write debian/watch
   * Change source package format to quilt, remove manual patches
 application
   * Convert package to use debhelper
   * Use `dh-runit' to install runit scripts and generate log scripts
 (Closes: #832656)
   * Use `dh-buildinfo' to simplify tracking bugs, related to build-tools
   * Avoid need of hand-written maintainer scripts by
 use of `dh-runit' and `dh-sysuser'
   * Drop dietlibc-dev from Build-Depends for now. (Libraries
 depended upon are not compiled for dietlibc anymore.)
   * Remove no longer needed README files
   * Move 'debian/crontab' into 'debian/contrib' for more clean package layout
   * Enable hardening
   * Fix @dircategory in texinfo manual
   * Install `doc-base' document
   * Add Homepage field
   * Bump standards version to 3.9.8 (no changes needed)
   * Remove Section field from `bcron-run' field, since it duplicated one
 defined in first paragraph.
   * Update Vcs-Git and Vcs-Browser fields
   * Convert `debian/copyrigh' to dep5 format
   * Use S:fieldname substitution to avoid duplication in `debian/control'.
 + Add versioned dependency on (dpkg-dev >= 1.18.11)
   * Disable unreliable tests (see: #835274)
Checksums-Sha1:
 51d01b1be3ab30affd67f954e68e4a6de5febc67 2029 

Bug#805988: aboot : include the binaries in source to build on amd64

[jhcha54008]

Hi,

I wonder if the following solution would be accepted (see the two patches 
attached) : let the source package ship the two binaries (bootlx and 
net_aboot.nh). One can build aboot-base on amd64 then.
The two binaries are generated from source if the source package is
built on alpha.
(The inspiration came from Helge Deller's palo package on hppa)

I tested so far that dpkg-buildpackage -B builds aboot (on alpha)
and aboot-cross (on amd64),
and that dpkg-builpackage -A builds aboot-base (on both).

A bootable CD including a just compiled bootlx indeed booted an XP1000 
alpha workstation.

I hope it will help !

Regards,
JH Chatenet
Description: Build-depends on opensp instead of sp (deprecated, removed)
 This is the concatenation of two patches from the thread of bug
 #832491 (see the discussion therein). Should close #832491
Forwarded: no
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491#5
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491#23
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491
Author: Neil Roeth 
Author: jhcha54008 

diff -Naur aboot-1.0~pre20040408/debian/control aboot-1.0~pre20040408/debian/control
--- aboot-1.0~pre20040408/debian/control	
+++ aboot-1.0~pre20040408/debian/control	
@@ -1,5 +1,5 @@
 Source: aboot
-Build-Depends: debhelper (>= 9), sp, sgmlspl, docbook-utils
+Build-Depends: debhelper (>= 9), opensp, sgmlspl, docbook-utils
 Build-Depends-Indep: sgmltools-lite
 Section: admin
 Priority: standard
diff -Naur aboot-1.0~pre20040408/doc/man/Makefile aboot-1.0~pre20040408/doc/man/Makefile
--- aboot-1.0~pre20040408/doc/man/Makefile	
+++ aboot-1.0~pre20040408/doc/man/Makefile	
@@ -32,20 +32,20 @@
 	rm -f aboot.8 aboot.conf.5 abootconf.8 isomarkboot.1 sdisklabel.8 netabootwrap.1 manpage.log manpage.links manpage.refs
 
 aboot.8: aboot.sgml
-	nsgmls aboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls aboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 aboot.conf.5: aboot.conf.sgml
-	nsgmls aboot.conf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls aboot.conf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 abootconf.8: abootconf.sgml
-	nsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 isomarkboot.1: isomarkboot.sgml
-	nsgmls isomarkboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls isomarkboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 netabootwrap.1: netabootwrap.sgml
-	nsgmls netabootwrap.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls netabootwrap.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 sdisklabel.8: sdisklabel.sgml
-	nsgmls sdisklabel.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls sdisklabel.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
diff -Naur aboot-1.0~pre20040408/doc/man/README aboot-1.0~pre20040408/doc/man/README
--- aboot-1.0~pre20040408/doc/man/README	2003-05-30 16:57:34.0 +
+++ aboot-1.0~pre20040408/doc/man/README	
@@ -26,7 +26,7 @@
 please contact me.
 
 Technical note:
-To create the nroff version from the SGML sources, nsgml was used like
-nsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+To create the nroff version from the SGML sources, onsgmls was used like
+onsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 Hannover, Germany, January 17th 2003
diff -Naur aboot-1.0~pre20040408/doc/man/de/Makefile aboot-1.0~pre20040408/doc/man/de/Makefile
--- aboot-1.0~pre20040408/doc/man/de/Makefile	
+++ aboot-1.0~pre20040408/doc/man/de/Makefile	
@@ -1,35 +1,35 @@
 all:  srmbootraw.de.8 aboot.de.8 aboot.conf.de.5 abootconf.de.8 isomarkboot.de.1 sdisklabel.de.8 srmbootfat.de.1 e2writeboot.de.8 swriteboot.de.8 netabootwrap.de.1
 
 aboot.de.8: aboot.sgml
-	nsgmls aboot.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls aboot.sgml | sgmlspl docbook2man-de-spec.pl
 	mv aboot.8 aboot.de.8
 
 aboot.conf.de.5: aboot.conf.sgml
-	nsgmls aboot.conf.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls aboot.conf.sgml | sgmlspl docbook2man-de-spec.pl
 	mv aboot.conf.5 aboot.conf.de.5
 
 abootconf.de.8: abootconf.sgml
-	nsgmls abootconf.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls abootconf.sgml | sgmlspl docbook2man-de-spec.pl
 	mv abootconf.8 abootconf.de.8
 
 netabootwrap.de.1: netabootwrap.sgml
-	nsgmls netabootwrap.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls netabootwrap.sgml | sgmlspl docbook2man-de-spec.pl
 	mv netabootwrap.1 netabootwrap.de.1
 
 isomarkboot.de.1: isomarkboot.sgml
-	nsgmls isomarkboot.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls isomarkboot.sgml | sgmlspl docbook2man-de-spec.pl
 	mv isomarkboot.1 isomarkboot.de.1
 
 sdisklabel.de.8: sdisklabel.sgml
-	nsgmls sdisklabel.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls sdisklabel.sgml | sgmlspl docbook2man-de-spec.pl
 	mv sdisklabel.8 sdisklabel.de.8
 
 srmbootfat.de.1: srmbootfat.sgml
-	nsgmls 

Bug#733433: marked as done (tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id 
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: FTBFS: dpkg-source: error: can't build with source format 
'3.0 (native)': native package version may not have a revision
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.)


-- 
223915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tk-brief
Version: 5.9-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> # Add here commands to clean up after the build process.
> dh_clean
>  dpkg-source -b tk-brief-5.9
> dpkg-source: error: can't build with source format '3.0 (native)': native 
> package version may not have a revision
> dpkg-buildpackage: error: dpkg-source -b tk-brief-5.9 gave error exit status 
> 255
> 
> Build finished at 20131227-0323

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/tk-brief_5.9-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: tk-brief
Source-Version: 5.10-0.1

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated tk-brief 
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: Wed, 18 Jan 2017 07:31:01 +0100
Source: tk-brief
Binary: tk-brief
Architecture: source all
Version: 5.10-0.1
Distribution: unstable
Urgency: medium
Maintainer: Yven Johannes Leist 
Changed-By: Christoph Biedl 
Description:
 tk-brief   - GUI for easily writing letters with LaTeX
Closes: 223915 249196
Changes:
 tk-brief (5.10-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #249196
   * Build as a package with orig tarball. Closes: #223915
Checksums-Sha1:
 21a949f5624c5923ab8cac92e99d949750543b24 1651 tk-brief_5.10-0.1.dsc
 0742bda99d99df2185262abda103ff7f94cc72a9 99516 tk-brief_5.10.orig.tar.gz
 67f53dbb5001d84d89d06b9a7b4a188274e3fc67 2708 tk-brief_5.10-0.1.debian.tar.xz
 030a951b05a487daa196f6580d440ea4e4dabf92 90440 tk-brief_5.10-0.1_all.deb
 ef1b130c4fe1031c6feef0e95112ba210b25d956 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Checksums-Sha256:
 4f8dc032c89a174fc8ce6dcef13682dced5879c49f967873e58f492225064ad8 1651 
tk-brief_5.10-0.1.dsc
 6b93d6fa31ac98c44086ca19be1eb4d9cbea51728d1d02b090fd1f5a757d0379 99516 
tk-brief_5.10.orig.tar.gz
 4ccbd69cd3f2b06141323e7f656f8f40c1c14d32035b4b89b19f4f15dabd367e 2708 
tk-brief_5.10-0.1.debian.tar.xz
 6d272742d62c0762979f765fbbb4133901a8f046e0cc2901ec282eaaf479676b 90440 
tk-brief_5.10-0.1_all.deb
 1767861f48d0b5c8e4b9378fd3b91344a0d96ca3bd19e548c5936b09f8aa2ab8 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Files:
 37268b01522a815364627ac2dadb8aa0 1651 tex optional tk-brief_5.10-0.1.dsc
 452db4d7b4bdaffd13d0af634e835509 99516 tex optional tk-brief_5.10.orig.tar.gz
 f68f3d1c77f6c69fa45fbdd1da1f70c3 2708 tex optional 
tk-brief_5.10-0.1.debian.tar.xz
 86f0e003e202646a50b96e982cb3b6b3 90440 tex optional tk-brief_5.10-0.1_all.deb
 d80567b3d0f14abeb2ff7d149bf7e3ff 4219 tex optional 
tk-brief_5.10-0.1_powerpc.buildinfo

-BEGIN 

Bug#223915: marked as done (tk-brief: Please don't package it as a native package)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id 
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: Please don't package it as a native 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.)


-- 
223915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tk-brief
Version: 5.9-1
Severity: normal


seesat5 is not a native Debian package. Please change the packaging to
a non-native packaging (.orig.tar.gz + .diff.gz + .dsc).

TIA
Adrian




--- End Message ---
--- Begin Message ---
Source: tk-brief
Source-Version: 5.10-0.1

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated tk-brief 
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: Wed, 18 Jan 2017 07:31:01 +0100
Source: tk-brief
Binary: tk-brief
Architecture: source all
Version: 5.10-0.1
Distribution: unstable
Urgency: medium
Maintainer: Yven Johannes Leist 
Changed-By: Christoph Biedl 
Description:
 tk-brief   - GUI for easily writing letters with LaTeX
Closes: 223915 249196
Changes:
 tk-brief (5.10-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #249196
   * Build as a package with orig tarball. Closes: #223915
Checksums-Sha1:
 21a949f5624c5923ab8cac92e99d949750543b24 1651 tk-brief_5.10-0.1.dsc
 0742bda99d99df2185262abda103ff7f94cc72a9 99516 tk-brief_5.10.orig.tar.gz
 67f53dbb5001d84d89d06b9a7b4a188274e3fc67 2708 tk-brief_5.10-0.1.debian.tar.xz
 030a951b05a487daa196f6580d440ea4e4dabf92 90440 tk-brief_5.10-0.1_all.deb
 ef1b130c4fe1031c6feef0e95112ba210b25d956 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Checksums-Sha256:
 4f8dc032c89a174fc8ce6dcef13682dced5879c49f967873e58f492225064ad8 1651 
tk-brief_5.10-0.1.dsc
 6b93d6fa31ac98c44086ca19be1eb4d9cbea51728d1d02b090fd1f5a757d0379 99516 
tk-brief_5.10.orig.tar.gz
 4ccbd69cd3f2b06141323e7f656f8f40c1c14d32035b4b89b19f4f15dabd367e 2708 
tk-brief_5.10-0.1.debian.tar.xz
 6d272742d62c0762979f765fbbb4133901a8f046e0cc2901ec282eaaf479676b 90440 
tk-brief_5.10-0.1_all.deb
 1767861f48d0b5c8e4b9378fd3b91344a0d96ca3bd19e548c5936b09f8aa2ab8 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Files:
 37268b01522a815364627ac2dadb8aa0 1651 tex optional tk-brief_5.10-0.1.dsc
 452db4d7b4bdaffd13d0af634e835509 99516 tex optional tk-brief_5.10.orig.tar.gz
 f68f3d1c77f6c69fa45fbdd1da1f70c3 2708 tex optional 
tk-brief_5.10-0.1.debian.tar.xz
 86f0e003e202646a50b96e982cb3b6b3 90440 tex optional tk-brief_5.10-0.1_all.deb
 d80567b3d0f14abeb2ff7d149bf7e3ff 4219 tex optional 
tk-brief_5.10-0.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYfxh7AAoJEMQsWOtZFJL9b1EP/3gTw5Q8Q/1HrllC1DO93wH3
UVKg3TRo8JzvOCTNmDDZgzZRxZIPSPrH4TQr4+MPAD9dAclv7Tdb41ro7vbQhnMn
fuL/UettDM4h7sRQAgLguydgwiNoLt56ITiVOyzcKYlPP7YwHRsiCxbST8/mJA8E
5IogLDx0UlFMvuLiikOX7Dp/4jN9pP/ZtDMQzgWK/MLkdapOZTk8pJHzA5c5n2X+
iETfGWhCTH6CxME76q6xTJSGsP+JzPPqCRcpcDhaE1iUAFvqu77VdXc17ETfFF6r
Tc436IvH9YXxaCN6xVQH9WhXE4wsT01GNfMaA8JIgx/z6TLE8+3/bXMkkHbA4hTP
CM7+Y804DJN3Y60E9TriYjPxy6dNMcMtjzeK6VZWv2XXg3zlvUWA7M0f09col36X
Wd2v2ICq54L8YWi+e28b5tbnbexHlfOL/SSVflaTdE+UZs1rfTOewNll0u3coU/+
cmwXppA4n2LTiKpycGGarklp3mL9BzXxdZ+FlWEjrIPLZtyi9lQmFOHTuTrtoH6V
BeP15nF3jKyQ6HMmNCqRK30/lkApI6OmIlIV6dOa3HTjZpMtg5HA7BJXXlupYPiq
UUm+ngDhiXcaOD73RT1aBZpMzaKU6qi6EWDROf1Tgn72RLeHxvAE03NmW+4/A8Mz
huz8rr+/6UJtcR/ay2ZK
=oKBV
-END PGP SIGNATURE End Message ---

Bug#851779: chromium: crashes at startup

[Guy Durrieu]

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last recent release, chromium does not start anymore.

Wen typing the command in a shell, I get the following message:

---

chromium
/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected 
(expecting "}")---


--

but when having a look to the script, I do not understand why this 
syntax error appears.


Thanks in advance for your help !

Regards.

-- GD.


System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 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 chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 10:3.2.2-dmo3
ii  libavformat5710:3.2.2-dmo3
ii  libavutil55  10:3.2.2-dmo3
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#851741: python-jinja2: New major version breaks ansible templates

[Jeremy Bicha]

On 18 January 2017 at 06:29, Piotr Ożarowski  wrote:
> could you check if this commit fixes it for you?
> https://github.com/pallets/jinja/commit/c6ddeb7d5f64789ed0bbc1ffef8596a79bc06fd9

Thanks for the quick response.

I'm still getting the KeyError: undefined variable after I built
jinja2 with that patch and installed it. :(

Thanks,
Jeremy Bicha

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> > 
> >
> > https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches
> 
> Oh, cool, adding the (build)-dep is really enough, no patching
> required. Nice.

Yes, we needed this for another package ...
  
> For stretch, I think there's still one thing to do:
> autopkgtest still fails with
> 
> pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to 
> overwrite 
> '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz', which is 
> also in package libbio-perl-perl 1.7.1-2

Urgs - Lincoln, I guess it makes sense to remove this copy of bioperl
even in your distribution.  What do you think?

Kind regards

   Andreas.


-- 
http://fam-tille.de

Processed: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj
Bug #851775 [libgcj-bc] libgcj-bc shlibs creates dependency that cannot be 
fulfilled in unstable
Added indication that 851775 affects libecj-java-gcj, ecj1, ecj-gcj, ant-gcj, 
and ant-optional-gcj

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

Bug#851775: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

[Adrian Bunk]

Package: libgcj-bc
Version: 6.2.1-1
Severity: grave
Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj

$ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs 
libgcj_bc 1 libgcj-bc (>= 6.2.1-3~)
$ 


That seems to be the reason why several packages can currently
not be installed in unstable:

  libecj-java-gcj,libgcj-bc 6.2.1-3~
  ecj1,libgcj-bc 6.2.1-3~
  ecj-gcj,libgcj-bc 6.2.1-3~
  ant-gcj,libgcj-bc 6.2.1-3~
  ant-optional-gcj,libgcj-bc 6.2.1-3~

Bug#847577: marked as done (Embeds dietlibc (GPL) but does not have a Built-Using field)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:48:31 +
with message-id 
and subject line Bug#847577: fixed in integrit 4.1-1.1
has caused the Debian Bug report #847577,
regarding Embeds dietlibc (GPL) but does not have a Built-Using field
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.)


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

integrit is statically linked to dietlibc which is licensed under
GNU GPL.  integrit must have a Built-Using field to record which
version was used and ensure that the corresponding source package is
kept in the archive.

Ben.

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: integrit
Source-Version: 4.1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated integrit 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: Wed, 18 Jan 2017 16:50:19 +0200
Source: integrit
Binary: integrit
Architecture: source
Version: 4.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Adrian Bunk 
Description:
 integrit   - A file integrity verification program
Closes: 776973 846891 847577
Changes:
 integrit (4.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply change from Andreas Henriksson to add a Built-Using field.
 (Closes: #847577)
   * Apply changes from Chris Lamb and Valerie R Young to make the
 build reproducible. (Closes: #776973, #846891)
Checksums-Sha1:
 e938a2c7b915c5aa81e6e2dcb4057449776bcb61 1704 integrit_4.1-1.1.dsc
 0e1c559e5447b26e3f33697794480007dd1095ee 9875 integrit_4.1-1.1.diff.gz
Checksums-Sha256:
 e19dae338df5f9185e9e0d922a5ca2669f9e6fc44dfa213a12fd24400f7ee41d 1704 
integrit_4.1-1.1.dsc
 84751076a8c967367cc69212f458f867c4f84d6550356ea146334a6e5e2c54de 9875 
integrit_4.1-1.1.diff.gz
Files:
 e26441418b3bd66cec0acaf0bb78d209 1704 admin optional integrit_4.1-1.1.dsc
 8e156807b45ba4feb15f877744566cb4 9875 admin optional integrit_4.1-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh/mXsACgkQiNJCh6LY
mLHOJxAAoe7zFNuk9Qn4HzPTJm+yTN5bYVEntK0AJmR+iUw7NaVwT/6wFZOCdloy
AJw82oy4TvhAczrAS9maZwQX97vrJGt5aV0JzL3ICbIsx6wkxjh3VBMOHB75TTnZ
Iby9GJ6IUIdHYFo7sgCsA6118dLzgapHo1/KK7XiMW1eEExTWXgDp/TGkZFzjiPV
PFoabPnxYh7jgQ0ikWOCpFaQnedcwYYcTxYaL6P9RgtEfDHrX80OyEQL4eEuF1eQ
jaWLcQS1sSQalaIf/KlBik5H2LHu20wtar5H1rT/v4L9js+g0EUrJrjlGFQCh+UI
yCQr3zEbJqmPFEOlP2bpoNIdyeZck9SWZfeKZ3kdYvtvP9c5dxbRjSvYk0CrW5k2
D7b+qveLfO5gmD9lujKvbma8FbcyLdGrbOd6BrGgSuAcoUmfF2Vuq8K/xXf2JEfa
+1Gg4GF7CPf3e3kHBO2PY2NjR5gNvA/JdTKDOfKPltQNAyFE3Ne5jJmn7IGWBosU
iEgT4lXbLT7WqMf/eUfZwj6Oqc49em0irE+PUpP83FWGKvuoVHaodPF1z+I6JkRT
iAA0ERdyIEECJPv9N+QDi9aZHrkziTt3lBKEwmlyBg6ZmhabwyGUiIqXng5WfQmp
+dcE1se8XUJGc1wN6HUwW0ckpB4QL0O7TfVO5E49IYkW7DZ8SgU=
=JOaE
-END PGP SIGNATURE End Message ---

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[gregor herrmann]

On Wed, 18 Jan 2017 17:27:21 +0100, Andreas Tille wrote:

> > Cool.  In Debian terminology this means a new "Build-Depends" and after 
> > adding
> > libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot 
> > for
> > your help and patience!
> > 
> > I now need to sort out some other issues with packaging and think I'll 
> > upload
> > soon.
> 
> This is done now.
> 
> I'd recommend you have a look at several patches for the Debian package which
> are available here:
> 
>https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches

Oh, cool, adding the (build)-dep is really enough, no patching
required. Nice.
 
For stretch, I think there's still one thing to do:
autopkgtest still fails with

pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to 
overwrite '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz', 
which is also in package libbio-perl-perl 1.7.1-2

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Schmetterlinge: Kommt ihr tausend Haufen


signature.asc
Description: Digital Signature

Bug#848236: marked as done (src:gbrowse: Fails to build from source since bioperl upgrade has broken libbio-graphics-perl)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:34:04 +
with message-id 
and subject line Bug#848236: fixed in gbrowse 2.56+dfsg-1
has caused the Debian Bug report #848236,
regarding src:gbrowse: Fails to build from source since bioperl upgrade has 
broken libbio-graphics-perl
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.)


-- 
848236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gbrowse
Severity: serious
Justification: FTBFS

Hi,

when trying to build gbrowse it fails to build from source:

...
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render.pm line 2348, 
this can lead to vulnerabilities. See the warning in "Fetching the value or 
values of a single named parameter" at /usr/share/perl5/CGI.pm line 412.
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm line 
271, this can lead to vulnerabilities. See the warning in "Fetching the value 
or values of a single named parameter" at /usr/share/perl5/CGI.pm line 412, 
 line 1.
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm line 
271, this can lead to vulnerabilities. See the warning in "Fetching the value 
or values of a single named parameter" at /usr/share/perl5/CGI.pm line 412, 
 line 1.
RenderPanels error: 
- EXCEPTION -
MSG: The requested glyph class, ``span'' is not available: Attempt to reload 
Bio/Graphics/Glyph/span.pm aborted.
Compilation failed in require at (eval 180) line 2, <> line 45.

STACK Bio::Graphics::Glyph::Factory::make_glyph 
/usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
STACK Bio::Graphics::Glyph::add_feature 
/usr/share/perl5/Bio/Graphics/Glyph.pm:424
STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1842
STACK (eval) 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1570
STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1524
STACK Bio::Graphics::Browser2::RenderPanels::request_panels 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:195
STACK Bio::Graphics::Browser2::Render::render_deferred 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render.pm:3589
STACK toplevel t/05.deferredrendering.t:102
-
...


The cause is most probably that libbio-graphics-perl does not work
together with bioperl 1.7.1 (see also #848105).  I'm now becoming aware
that with the naive upgrade to bioperl 1.7.1 we have triggered problems
that should have solved inside a transition via experimental.  My
proposed course of action is as follows:

  1. Revert the version bump of bioperl and upload the old version
 with an epoch (1:1.6.924-6).
  2. Upload 1.7.1-2 to experimental
  3. Solve all issues with BioPerl 1.7.x after Stretch release.

Does anybody have a better plan?

Kind regards

Andreas.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: gbrowse
Source-Version: 2.56+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gbrowse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 17:16:19 +0100
Source: gbrowse
Binary: gbrowse gbrowse-data gbrowse-calign
Architecture: source amd64 all
Version: 2.56+dfsg-1
Distribution: unstable

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

[droping debian-perl list from CC]

On Wed, Jan 18, 2017 at 02:30:32PM +0100, Andreas Tille wrote:
> Hi Lincoln,
> 
> On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
> > 
> > There appears to be a new dependency on libbio-coordinate. Probably best to
> > add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
> > problem will disappear.
> 
> Cool.  In Debian terminology this means a new "Build-Depends" and after adding
> libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot for
> your help and patience!
> 
> I now need to sort out some other issues with packaging and think I'll upload
> soon.

This is done now.

I'd recommend you have a look at several patches for the Debian package which
are available here:

   https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches

They apply in the sequence of the series file and I guess several of them are
useful also for your upstream code.

Thanks a lot for your help

  Andreas.

-- 
http://fam-tille.de

Bug#851771: php-gettext: CVE-2016-6175

[Salvatore Bonaccorso]

Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream
Forwarded: https://bugs.launchpad.net/php-gettext/+bug/1606184

Hi,

the following vulnerability was published for php-gettext.

CVE-2016-6175[0]:
Use of eval too unrestrictive 

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-6175
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6175
[1] https://bugs.launchpad.net/php-gettext/+bug/1606184

Regards,
Salvatore

Bug#851770: php-gettext: CVE-2015-8980

[Salvatore Bonaccorso]

Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for php-gettext.

CVE-2015-8980[0]:
|Arbitrary code execution in select_string, ngettext and npgettext
|count parameter

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-2015-8980
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8980
[1] http://seclists.org/fulldisclosure/2016/Aug/76

Regards,
Salvatore

Processed: forcibly merging 648208 794849

[Debian Bug Tracking System]

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

> forcemerge 648208 794849
Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm 
instances
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #806273 [os-prober] os-prober: remove or disable-per default the non 
grub-mount based probing
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Bug #794849 [os-prober] linux: custom linux-image packages fail to install
Severity set to 'critical' from 'serious'
Marked as found in versions os-prober/1.65 and os-prober/1.42.
Added tag(s) patch.
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #806273 [os-prober] os-prober: remove or disable-per default the non 
grub-mount based probing
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Merged 648208 788062 794849 806273 810121
> thanks
Stopping processing here.

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

Bug#851769: 389-ds-base: CVE-2017-2591

[Salvatore Bonaccorso]

Source: 389-ds-base
Version: 1.3.5.15-1
Severity: grave
Tags: security upstream patch
Justification: user security hole

Hi,

the following vulnerability was published for 389-ds-base. Choosed
severity > important, since possibly as well triggerable by
unauthenticated attackers, but I'm not too familiar if that setup is
common.

CVE-2017-2591[0]:
DoS via OOB heap read in "attribute uniqueness" plugin

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-2017-2591
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2591

Regards,
Salvatore

Bug#835189: python-pyrax: FTBFS (failing tests)

[Sascha Girrulat]

thx for the update. I try to handle it asap. I'm only short of time at
the moment.

Regards
Sascha

Am 17.01.2017 um 01:50 schrieb Santiago Vila:
> retitle 835189 python-pyrax: FTBFS (failing tests)
> thanks
> 
> Hi.
> 
> After building this package many times today, it always fail
> and not just sometimes, so I'm retitling accordingly.
> 
> As a summary, I see that the following tests always fail:
> 
> ERROR: test_set_http_debug (tests.unit.test_module.PyraxInitTest)
> ERROR: test_connect_to_cloudservers (tests.unit.test_module.PyraxInitTest)
> 
> and the following one fails approximately 70% of the time:
> 
> ERROR: test_rax_endpoints (tests.unit.test_identity.IdentityTest)
> 
> [ The first two failing tests are the ones reported by Lucas Nussbaum
>   in Bug #841623 ].
> 
> Thanks.
> 



signature.asc
Description: OpenPGP digital signature

Bug#737167: marked as done (xfonts-wqy: prompting due to modified conffiles which were not modified by the user)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:06:02 +
with message-id 
and subject line Bug#737167: fixed in xfonts-wqy 1.0.0~rc1-3
has caused the Debian Bug report #737167,
regarding xfonts-wqy: prompting due to modified conffiles which were not 
modified by the user
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.)


-- 
737167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfonts-wqy
Version: 0.9.9-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

http://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In http://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

This was observed on an upgrade from wheezy to jessie to sid.

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

  Setting up xfonts-wqy (0.9.9-8) ...
  
  Configuration file '/etc/X11/fonts/misc/xfonts-wqy.alias'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** xfonts-wqy.alias (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package xfonts-wqy (--configure):
   EOF on stdin at conffile prompt
  Processing triggers for libc-bin (2.17-97) ...
  Errors were encountered while processing:
   xfonts-wqy
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,

Andreas


xfonts-wqy_0.9.9-8.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: xfonts-wqy
Source-Version: 1.0.0~rc1-3

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated xfonts-wqy 
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: Wed, 18 Jan 2017 23:44:24 +0800
Source: xfonts-wqy
Binary: xfonts-wqy
Architecture: source
Version: 1.0.0~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 xfonts-wqy - WenQuanYi Bitmap Song CJK font for X
Closes: 737167
Changes:
 xfonts-wqy (1.0.0~rc1-3) unstable; urgency=medium
 .
   * Rename /etc/X11/fonts/misc/xfonts-wqy.alias to fix wrongly placed
 fonts.alias file (Closes: #737167).
Checksums-Sha1:
 a45a04b151a6970d624f89c2cb2e0adef9c046c6 2053 xfonts-wqy_1.0.0~rc1-3.dsc
 89575a1b97b8a0268b4169c5e1ae5b5647d2baae 13056 
xfonts-wqy_1.0.0~rc1-3.debian.tar.xz
Checksums-Sha256:
 9ebb1a4d45b758b667912205625bf5e4ce112e52337bc15a508b724a04bb0fff 2053 
xfonts-wqy_1.0.0~rc1-3.dsc
 a5fa6ad4a847272f31a90e521213f9fb32cdf1508cad6f23c7c828d27de2039f 13056 
xfonts-wqy_1.0.0~rc1-3.debian.tar.xz
Files:
 8eef6d92952df514a55b4821a0b55a56 2053 fonts optional xfonts-wqy_1.0.0~rc1-3.dsc
 ac276225131ac769e22107c0f9d5dbac 13056 fonts optional 

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

- car...@debian.org wrote:

> Hi Lars,
> 
> On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> > 
> > - car...@debian.org wrote:
> > 
> > 
> > > > >With that fixed, and build with -sa (to include the orig
> tarball)
> > > > >please do upload to security-master.
> > > > Do we have access to upload here? I think the security team
> have
> > > handled the
> > > > upload in the past.
> > > 
> > > yes it nees to be a key in the DD keyring. Do you have a DD in
> the
> > > mysql-pkg team who could sponsor the upload?
> > > 
> > 
> > Not really, unfortunately (Otto is a DD, but he's only involved
> with
> > the MariaDB packaging).
> > It's an issue for us, since it also causes problems with uploads to
> > unstable.
> 
> Ok. I though in the past James Page was sponsoring the uploads.
> Alright, in that case, let me know when you have finished the
> packaging with the small changes mentioned, I can take care of
> sponsoring the upload.
> 
I might be going a bit senile, since I forgot he's got access as well, but for 
the last months he's been occupied, so I don't think he's available now.
I'll let you know when the new build is ready, thanks.

--
Lars
> Regards,
> Salvatore

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Yann Richard]

Le 17/01/2017 à 14:01, Felipe Sateler a écrit :

Hi Yann,

On 17 January 2017 at 06:54, Yann Richard  wrote:

Hi,

We have made a package from fcoe-utils source version 1.0.31 which fix init bug 
:

https://github.com/DSI-Universite-Rennes2/fcoe-utils

Tested on HP 465c G8 on Ethernet controller: Broadcom Limited BCM57840 
NetXtreme II 10/20-Gigabit Ethernet (rev 11) in HP C7000 enclosure with
HP VC FlexFabric-20/40 F8 Module

Any Debian maintainer or developer would like to verify and push this into 
stretch ?

Could you please post this as a patch against the current debian
package? The linked git repository contains the entire debian
directory as a single commit. Moreover, that commit includes build
artifacts (eg, the scripts generated by debhelper), so that makes
review harder.


Hi,

In attachement debian's directory patch for 
fcoe-utils-1.0.29+git20140505 version.


It contains 9 patchs from OpenSuse.

At boot both systemd service and socket are successfully loaded and 
active but no host in /sys/class/fc_host/ are present (we expected them 
to be..). But they are after ifdown/ifup the interface.


We think there is a bug on this version and we'll try to test 1.0.31 or 
HEAD git version (not modified since 6 month).


Best Regards,

--
  M. Yann Richard
  Université Rennes 2
 Direction du Système d'Information
  Pôle Infrastructure / Serveurs
  http://www.univ-rennes2.fr/dsi

diff --git a/patches/0028-systemctl-cannot-start-fcoemon.socket.patch b/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
index e69de29..a80f1a8 100644
--- a/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
+++ b/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
@@ -0,0 +1,31 @@
+From 444f3c66ee5a2b59a563d78cb70db7da2326d446 Mon Sep 17 00:00:00 2001
+From: Hannes Reinecke 
+Date: Fri, 21 Mar 2014 14:46:40 +0100
+Subject: systemctl cannot start fcoemon.socket
+
+systemctl start fcoemon.socket fails, as systemd cannot find
+the referenced service.
+
+References: bnc#869392
+
+Signed-off-by: Hannes Reinecke 
+---
+ etc/systemd/fcoemon.socket | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/etc/systemd/fcoemon.socket b/etc/systemd/fcoemon.socket
+index 4de8715..fdf7141 100644
+--- a/etc/systemd/fcoemon.socket
 b/etc/systemd/fcoemon.socket
+@@ -1,4 +1,8 @@
++[Unit]
++Description=Open-FCoE daemon control socket
++
+ [Socket]
++Service=fcoe.service
+ ListenDatagram=@/com/intel/fcoemon
+ PassCredentials=true
+ 
+-- 
+1.8.1.4
+
diff --git a/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch b/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
index e69de29..b99cbef 100644
--- a/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
+++ b/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
@@ -0,0 +1,121 @@
+From 5216ae2ef4434d92ff3d49c4d5a7b73b438aee2d Mon Sep 17 00:00:00 2001
+From: Hannes Reinecke 
+Date: Fri, 11 Apr 2014 15:38:26 +0200
+Subject: fcoemon: Correctly handle options in the service file
+
+When runnig under systemd we can't really modify the arguments
+to provide an 'FCOEMON_OPTS' variable. Instead we should be
+modifying fcoemon --debug and --syslog to accept 'yes' or 'no'
+as parameters; that way we can use the variables directly.
+
+References: bnc#872732
+
+Signed-off-by: Hannes Reinecke 
+---
+ doc/fcoemon.txt  |  6 +++---
+ etc/systemd/fcoe.service |  4 ++--
+ fcoemon.c| 24 +++-
+ 3 files changed, 20 insertions(+), 14 deletions(-)
+
+diff --git a/doc/fcoemon.txt b/doc/fcoemon.txt
+index 7ccf892..7449601 100644
+--- a/doc/fcoemon.txt
 b/doc/fcoemon.txt
+@@ -53,13 +53,13 @@ OPTIONS
+ ---
+ *-f*, *--foreground*::
+ 	Run *fcoemon* in the foreground.
+-*-d*, *--debug*::
+-	Enable debugging messages.
++*-d*, *--debug=yes|no*::
++	Enable or disable debugging messages.
+ *-l*, *--legacy*::
+ 	Force fcoemon to use the legacy /sys/module/libfcoe/parameters/
+ 	interface. The default is to use the newer /sys/bus/fcoe/ interfaces
+ 	if they are available.
+-*-s*, *--syslog*::
++*-s*, *--syslog=yes|no*::
+ 	Use syslogd for logging. The default behavior is to log to stdout
+ 	and stderr.
+ *-h*, *--help*::
+diff --git a/etc/systemd/fcoe.service b/etc/systemd/fcoe.service
+index 5e5c8a2..2e10bcd 100644
+--- a/etc/systemd/fcoe.service
 b/etc/systemd/fcoe.service
+@@ -4,9 +4,9 @@ After=syslog.target network.target
+ 
+ [Service]
+ Type=simple
+-EnvironmentFile=/etc/sysconfig/fcoe
++EnvironmentFile=/etc/fcoe/config
+ ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS
+-ExecStart=/usr/sbin/fcoemon $FCOEMON_OPTS
++ExecStart=/usr/sbin/fcoemon --debug=$DEBUG --syslog=$SYSLOG
+ 
+ [Install]
+ WantedBy=multi-user.target
+diff --git a/fcoemon.c b/fcoemon.c
+index 5e4f8d7..23fc2f6 100644
+--- a/fcoemon.c
 b/fcoemon.c
+@@ -336,9 +336,9 @@ static int 

Bug#851767: chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.

[Grigor Gatchev]

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser 
would not run.
I browsed the starting script /usr/bin/chromium and noticed that the string in 
line 21 is
missing a terminating quote. After adding that quote, the script worked OK.

Could you please add that quote?

Thank you for your service to the Debian community and users,

Grigor


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

Kernel: Linux 4.8.0-2-amd64 (SMP w/8 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 chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#851714: marked as done (gitlab: Cannot push to gitlab repositories with git >= 2.11.0)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:33:49 +
with message-id 
and subject line Bug#851714: fixed in gitlab 8.13.11+dfsg-1
has caused the Debian Bug report #851714,
regarding gitlab: Cannot push to gitlab repositories with git >= 2.11.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.)


-- 
851714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.6+dfsg2-2
Severity: grave

Dear Maintainer,

Gitlab repositories will no longer accept remote pushes to protected branches
(which is the default!) with git 2.11.0 installed on the gitlab system, failing
with:

remote: GitLab: You are not allowed to force push code to a protected branch on 
this project.
To (sitename):(user)/(repo).git
 ! [remote rejected] master -> master (pre-receive hook declined)

even for ordinary, non-forced pushes.

This is upstream bug https://gitlab.com/gitlab-org/gitlab-ce/issues/25301

Since gitlab seems pretty useless without the ability to push to a repository
by default, I've marked this grave.


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

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

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  apache2 [httpd]   2.4.25-1
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b2
ii  bundler   1.13.6-2
ii  debconf [debconf-2.0] 1.5.59
ii  git   1:2.11.0-2
ii  gitlab-shell  3.6.6-1
ii  gitlab-workhorse  0.8.5+debian-3
ii  init-system-helpers   1.46
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nodejs4.7.2~dfsg-1
ii  openssh-client1:7.4p1-5
ii  postfix [mail-transport-agent]3.1.3-6
ii  postgresql-client 9.6+178
ii  postgresql-client-9.6 [postgresql-client  9.6.1-2
ii  postgresql-contrib9.6+178
ii  rake  10.5.0-2
pn  redis-server  
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-3
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  0.7.3+dfsg-2+b3
ii  ruby-chronic  0.10.2-3
ii  ruby-chronic-duration 0.10.6-1
ii  ruby-coffee-rails 4.1.0-2
ii  ruby-coffee-script-source 1.10.0-1
ii  ruby-connection-pool  2.2.0-1
ii  ruby-creole   0.5.0-2
ii  ruby-d3-rails 3.5.6+dfsg-1
ii  ruby-default-value-for3.0.1-1
ii  ruby-devise   4.2.0-1
ii  ruby-devise-two-factor3.0.0-2
ii  ruby-diffy3.0.6-1
ii  ruby-doorkeeper   4.2.0-3
ii  ruby-dropzonejs-rails 

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> 
> - car...@debian.org wrote:
> 
> 
> > > >With that fixed, and build with -sa (to include the orig tarball)
> > > >please do upload to security-master.
> > > Do we have access to upload here? I think the security team have
> > handled the
> > > upload in the past.
> > 
> > yes it nees to be a key in the DD keyring. Do you have a DD in the
> > mysql-pkg team who could sponsor the upload?
> > 
> 
> Not really, unfortunately (Otto is a DD, but he's only involved with
> the MariaDB packaging).
> It's an issue for us, since it also causes problems with uploads to
> unstable.

Ok. I though in the past James Page was sponsoring the uploads.
Alright, in that case, let me know when you have finished the
packaging with the small changes mentioned, I can take care of
sponsoring the upload.

Regards,
Salvatore

Bug#845899: marked as done (python-mysqldb: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:08:44 +
with message-id 
and subject line Bug#845899: fixed in python-mysqldb 1.3.7-1.1
has caused the Debian Bug report #845899,
regarding python-mysqldb: switch to build depend on the metapackage 
default-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.)


-- 
845899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mysqldb
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: python-mysqldb
Source-Version: 1.3.7-1.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-mysqldb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Jan 2017 14:51:04 +0100
Source: python-mysqldb
Binary: python-mysqldb python-mysqldb-dbg python3-mysqldb python3-mysqldb-dbg
Architecture: source
Version: 1.3.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Beckmann 
Description:
 python-mysqldb - Python interface to MySQL
 python-mysqldb-dbg - Python interface to MySQL (debug extension)
 python3-mysqldb - Python interface to MySQL
 python3-mysqldb-dbg - Python interface to MySQL (debug extension)
Closes: 738180 845899 848484 848485
Changes:
 python-mysqldb (1.3.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch Build-Depends to default-libmysqlclient-dev.  (Closes: #845899)
   * Switch Suggests to default-mysql-* | virtual-mysql-*.
 (Closes: #848484, #848485)
   * Remove Monty Taylor from Uploaders.  (Closes: #738180)
   * Run dh_strip with option --no-automatic-dbgsym to avoid generation of
 -dbg-dbgsym packages.
Checksums-Sha1:
 75615306158f96bdd42a92483f06313aa7182490 2425 python-mysqldb_1.3.7-1.1.dsc
 4bee7c89d5c9f9b84a7217aa26af66b4ba6a4666 8992 
python-mysqldb_1.3.7-1.1.debian.tar.xz
Checksums-Sha256:
 758d7153836f8085c7e0ac6c424bfad2623faadde8341de7eb0276e4d6c0 2425 
python-mysqldb_1.3.7-1.1.dsc
 b969f64e88a8f8a6cd356f3f206f6ea7ae466e50986b4c87588fc3921e4c6a6d 8992 
python-mysqldb_1.3.7-1.1.debian.tar.xz
Files:
 94b3368d51eb4a6b63a6ea8916b9243b 2425 python optional 
python-mysqldb_1.3.7-1.1.dsc
 b9c089939a25aa9e1777220db0f99e4b 8992 python optional 
python-mysqldb_1.3.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfNCXAAoJEF+zP5NZ6e0Iw4cP/3WQ4i/CL6dUIVihi33vTvbP
N5i/YiclyzvtqVlRUXbAExSqpBlJ1uG69C0MU+pR7qFCR6VUyRTLWmUwsG6AY+3m
jbBPB4780IeHOLNT8J6N4Gd/okVC2PHORZJPfttifS6J+YYdA6tmmPxpMXPpSU/3
4MJ6BXX24BS0DnMZRpxp1zF6v7SycC6cDnNLfWLgQIqe+4mlJCv8NsA9VSQBYeYy
br2E11agGpbNVEJw1emufgJo9IIdlm/hVkx8Ag0zTkSixPuI9a8fkRXd5OgvJgXH
62jIwcJGEYM7WE5+D/O2k9eTi3Lxw8rkXbZ1QrzbJx+vqPat7YqXiLYU/+9+gHtL
vmBZJtKFQEhjKiCVtKnpFqZG8ik7t11782x9TDe4JFqqtJrTol03B0oSY1SZuH6V
QbTmrNsWLMZjbyhScUzCzBaYsg7Mmk0KH24CvlOt4xdA/9ZPNQpfhRo2HlDUiSCH
FJ/+bURugyCga3YWg+0mc6aDju7iSN48ko9tYsALmMJ5K2lrYUf7HSAODqi7Adu/
e/nOeqTL677BzpPNE6Wk0i0igJiPIf1LjjUa4sJXXz3MwpB+/Img/LnnuZLx794g
47htNDfyqFumCbSLLJHlsTGsXh6ZGfDpcGeRjx07mFIXQunmXFX6ts5Octx4BkSR
RrhUIncLwfJkR7aDeg8k
=4vzP

Bug#851293: marked as done (CVE-2016-9590)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:08:39 +
with message-id 
and subject line Bug#851293: fixed in puppet-module-swift 9.4.4-1
has caused the Debian Bug report #851293,
regarding CVE-2016-9590
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.)


-- 
851293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-module-swift
Severity: grave
Tags: security

Hi,
please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9590
for details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: puppet-module-swift
Source-Version: 9.4.4-1

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

Debian distribution maintenance software
pp.
Ondřej Kobližek  (supplier of updated puppet-module-swift 
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: Wed, 18 Jan 2017 14:23:19 +0100
Source: puppet-module-swift
Binary: puppet-module-swift
Architecture: source all
Version: 9.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Ondřej Kobližek 
Description:
 puppet-module-swift - Puppet module for OpenStack Swift
Closes: 851293
Changes:
 puppet-module-swift (9.4.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (Closes: #851293, CVE-2016-9590)
Checksums-Sha1:
 f77732e3a52b2587b0cade7ccc32536a244fd143 2096 puppet-module-swift_9.4.4-1.dsc
 1bf7563abec35c7552d481d36749853008c5dc8b 64588 
puppet-module-swift_9.4.4.orig.tar.xz
 fec6dc2315fbc762640dfe26ef0b6075962ef112 2720 
puppet-module-swift_9.4.4-1.debian.tar.xz
 203c3ce5d18058e7505aa89280140f2483b1d108 61716 
puppet-module-swift_9.4.4-1_all.deb
 a9ab06dc1a00f46fc589259134ba7b93cc1267ea 6562 
puppet-module-swift_9.4.4-1_amd64.buildinfo
Checksums-Sha256:
 8deb8caaf1f19b4054b605d4bc8d5d49c6a4c86996347404f44fd9d0410cb708 2096 
puppet-module-swift_9.4.4-1.dsc
 c2dbdd84605fa547f0741c1e6cca22d0639f70227fa084ca7e90e006e10b5d45 64588 
puppet-module-swift_9.4.4.orig.tar.xz
 321a7a4df28a0a44bb0c9da257f005b390f6a508c86b54b9be098f848497362a 2720 
puppet-module-swift_9.4.4-1.debian.tar.xz
 199143275e731aca63a280a1faa2206e5dce72ac08a7ddbbcc0004d59d84b73e 61716 
puppet-module-swift_9.4.4-1_all.deb
 b448da09b61c2a2e9b6fb8890d988b95ce75779f46031c3e85e70825fb708339 6562 
puppet-module-swift_9.4.4-1_amd64.buildinfo
Files:
 51dd73294b1572198ed71099e9c550da 2096 admin extra 
puppet-module-swift_9.4.4-1.dsc
 5a4e42e7393655a151fb2c5b363efef9 64588 admin extra 
puppet-module-swift_9.4.4.orig.tar.xz
 f7370c6cf957d42c06b92f8fe0fcbdaf 2720 admin extra 
puppet-module-swift_9.4.4-1.debian.tar.xz
 a1ec66ffe873330b2eeefb88beb5d042 61716 admin extra 
puppet-module-swift_9.4.4-1_all.deb
 7af43f2548c6aaad64d85e9c2ca273eb 6562 admin extra 
puppet-module-swift_9.4.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlh/fesACgkQNXMSVZ0e
BktmmA/+KJEkodvTKETn5dRowF1CXa1y8/mZesSBQcjlHuSVBq4PCqVnLeyC8ixI
yrU7btbXXKyauJ7iSnssX38PdHljd3HZmLx1AOBzbWhQ8VuuFAAFH+w6ElDfqWjX
Jyk66KLDhXnMC9HqkgrvZYvEaYJFUa0uPlyYqSFZD/OJQnrRRDClq3yeewZjKmtK
O/G/aJ8q0Dh0N8RC+9DKqZs9UEdUrEEpn1N6pTskeuHMN10YYoRrpxCWHKjxR/jv
OxduIlLfCMoeA3qYNX9LScJA3dAjX6xpzdTCeXxOaJ1zcQoHXL5Fdr8WcOaZalc8
xqqApYBqddOgx3zEN90tnW5kJPCq4wchznMYnr0dH80I/o700zUjGe0cdf3KbXyy
dGzXWER9lg01vcDVSGuuwI8JSPFiAw7ytBWJ5yt+kPeqr948IcoHViahw0pBTTpE
RAiGEL86xvMsM1rEwb7FF1BjOB2FCKM0yklezm/wxNVZcNRXrHO498ZkA4z6Qdkl
7VmlveNZBqmO5mMPyvfH8xnaxBXQszhV7OjXL3aEcFk04KN9DILJS+7gJDlNMEyw
qur2UHbYk3o8ViYUzBegEErHaKwEhOEiMe8r84mV+snAsdv9OxzNZCLFOQnPBKMU
/UCR1pA+lFYvKn1CkZchrRVy5HDqOn5UGIoeSNxcvLvqcMlhPs0=
=g9er
-END PGP SIGNATURE End Message ---

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

- car...@debian.org wrote:


> > >With that fixed, and build with -sa (to include the orig tarball)
> > >please do upload to security-master.
> > Do we have access to upload here? I think the security team have
> handled the
> > upload in the past.
> 
> yes it nees to be a key in the DD keyring. Do you have a DD in the
> mysql-pkg team who could sponsor the upload?
> 

Not really, unfortunately (Otto is a DD, but he's only involved with the 
MariaDB packaging).
It's an issue for us, since it also causes problems with uploads to unstable.

--
Lars

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[gregor herrmann]

On Wed, 18 Jan 2017 14:00:47 +, Lincoln Stein wrote:

> Glad to be of help. No source changes to bio::graphics needed then?

Probably that too :)
I'll take a look later today.
 
Thanks for your efforts and your enormous help!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   BOFH excuse #267:  The UPS is on strike. 

Bug#845829: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

[Andreas Beckmann]

Control: tag -1 pending

On 2017-01-17 02:21, Andreas Beckmann wrote:
> attached is a patch to fix this (and another) issue.
> If you need help, I could also upload this as a NMU.

I now uploaded this as a NMU to DELAYED/2 since cfengine3 is the last
(fixable) package in stretch blocking the mariadb transition. All others
are fixed in sid (or a delayed NMU to sid) waiting to migrate, except
for two ruby packages that need more work and will probably be removed
from stretch.


Andreas

Processed: Re: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #845829 [cfengine3] cfengine3: switch to build depend on the metapackage 
default-libmysqlclient-dev
Added tag(s) pending.

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

Processed: retitle 851755 to mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318 ...

[Debian Bug Tracking System]

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

> # including CVE-2016-6664 as well in list
> retitle 851755 mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
> CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
> CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Changed Bug title to 'mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318' from 'mariadb-10.0: CVE-2017-3238 
CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 
CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318'.
> # including CVE-2016-6664 as well in list
> retitle 851759 mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
> CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
> CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Bug #851759 [src:mariadb-10.1] mariadb-10.1: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Changed Bug title to 'mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318' from 'mariadb-10.1: CVE-2017-3238 
CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 
CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318'.
> thanks
Stopping processing here.

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

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Glad to be of help. No source changes to bio::graphics needed then?

At some point in near future I will be making changes to the exception
reporting in bio::graphics so that the error messages are more informative.

Lincoln

On Wed, Jan 18, 2017 at 8:30 AM Andreas Tille  wrote:

> Hi Lincoln,
>
>
>
> On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
>
> >
>
> > There appears to be a new dependency on libbio-coordinate. Probably best
> to
>
> > add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
>
> > problem will disappear.
>
>
>
> Cool.  In Debian terminology this means a new "Build-Depends" and after
> adding
>
> libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot
> for
>
> your help and patience!
>
>
>
> I now need to sort out some other issues with packaging and think I'll
> upload
>
> soon.
>
>
>
> Kind regards
>
>
>
>Andreas.
>
>
>
> --
>
> http://fam-tille.de
>
> --
Written on my cell phone. Anything that seems odd is the fault of
auto-correct.

Processed: Re: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 851131
Bug #841583 [src:ruby-dataobjects-mysql] ruby-dataobjects-mysql: FTBFS: 
mysql_install_db: [ERROR] unknown option '--force'
841583 was not blocked by any bugs.
841583 was not blocking any bugs.
Added blocking bug(s) of 841583: 851131

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

Bug#841583: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Andreas Beckmann]

Followup-For: Bug #841583
Control: block -1 with 851131

The --force problem is specific to mysql, it does not happen with
mariadb. But it fails differently on mariadb:

[...]
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld 
10.1.20-MariaDB-3) starting as process 3768 ...
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using mutexes to ref count 
buffer pool pages
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: The InnoDB memory heap is 
disabled
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Mutexes and rw_locks use GCC 
atomic builtins
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: GCC builtin 
__atomic_thread_fence() is used for memory barrier
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Compressed tables use zlib 
1.2.8
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using Linux native AIO
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using SSE crc32 instructions
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Initializing buffer pool, 
size = 128.0M
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Completed initialization of 
buffer pool
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Highest supported file 
format is Barracuda.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: 128 rollback segment(s) are 
active.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Waiting for purge to start
2017-01-18 13:52:53 140102037378944 [Note] InnoDB:  Percona XtraDB 
(http://www.percona.com) 5.6.34-79.1 started; log sequence number 1622838
2017-01-18 13:52:53 140102037378944 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-18 13:52:53 140101342430976 [Note] InnoDB: Dumping buffer pool(s) not 
yet started
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld: ready for 
connections.
Version: '10.1.20-MariaDB-3'  socket: '/tmp/tmp.mXSW0s03Pw/mysql.sock'  port: 0 
 Debian unstable
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost''
ERROR 1698 (28000): Access denied for user 'root'@'localhost'
debian/rules:19: recipe for target 'override_dh_auto_install' failed

which seems to be another instance of #851131


Andreas

Bug#851759: mariadb-10.1: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

[Salvatore Bonaccorso]

Source: mariadb-10.1
Version: 10.1.20-3
Severity: grave
Tags: upstream security fixed-upstream
Justification: user security hole

Hi

The following CVEs were fixed with a new upstream version 10.1.21,
whereas CVE-2016-6664 has already a separate bug in the BTS:

CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3317
CVE-2017-3318 

https://mariadb.com/kb/en/mariadb/mariadb-10121-release-notes/

Regards,
Salvatore

Processed: tagging 851755

[Debian Bug Tracking System]

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

> tags 851755 + fixed-upstream
Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#851755: mariadb-10.0: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

[Salvatore Bonaccorso]

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

Hi

The following CVE's were addressed in 10.0.29 upstream, whereas
CVE-2016-6664 has already a seprate bug in the BTS:

CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3317
CVE-2017-3318 

https://mariadb.com/kb/en/mariadb/mariadb-10029-release-notes/

Regards,
Salvatore

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Jan 18, 2017 at 12:45:45PM +0100, Lars Tangvald wrote:
> Hi,
> 
> On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
> >Hi Lars,
> >
> >On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> >>Hi,
> >>
> >>The update builds and passes testing.
> >>I've attached debdiff output for Wheezy and Jessie for this update. Aside
> >>from the changelog, the only change to packaging is a patch for a test
> >>(main.events_2) that was failing because of a hardcoded date.
> >Thanks for preparing the update.
> >
> >>diff -r mysql-5.5-5.5.53/debian/changelog 
> >>../mysql-5.5/mysql-5.5/debian/changelog
> >>0a1,14
> >>>mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
> >>>
> >>>   * Imported upstream version 5.5.54 to fix security issues:
> >>> - 
> >>> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> >>> - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
> >>> - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
> >>> - CVE-2017-3317 CVE-2017-3318
> >>> (Closes: #851233)
> >>>   * Fix failing test main.events_2
> >>> The test was failing due to hardcoded date (2017-01-01). Added patch
> >>> pending upstream fix.
> >>>
> >>>  -- Lars Tangvald   Tue, 17 Jan 2017 13:04:58 
> >>> +0100
> >This looks good, but see one change which seem included below:
> >
> >>5c19
> >>< - CVE-2016-7440 CVE-2016-5584
> >>---
> >>> - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
> >Did you build not on top of the last update? Because we corrected the
> >CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
> >there, and was already fixed in the DSA-3666-1 with mysql-5.5
> >5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
> >https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
> >remember exactly, but I though I had asked someone of the mysql
> >packaging team to import the final changes to the packaging
> >repository.
> Aha, yes. I see the vcs hasn't got the 5.5.53 packages imported properly.
> I'll do the import and rebuild, thanks.

Thanks!

> >With that fixed, and build with -sa (to include the orig tarball)
> >please do upload to security-master.
> Do we have access to upload here? I think the security team have handled the
> upload in the past.

yes it nees to be a key in the DD keyring. Do you have a DD in the
mysql-pkg team who could sponsor the upload?

Regards,
Salvatore

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

Hi Lincoln,

On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
> 
> There appears to be a new dependency on libbio-coordinate. Probably best to
> add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
> problem will disappear.

Cool.  In Debian terminology this means a new "Build-Depends" and after adding
libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot for
your help and patience!

I now need to sort out some other issues with packaging and think I'll upload
soon.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#851549: marked as done (dbus: Segmentation fault in dbus.postinst on mips64el)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id 
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding dbus: Segmentation fault in dbus.postinst on mips64el
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.)


-- 
851412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbus
Version: 1.10.14-1
Severity: grave
Justification: renders package unusable

Current package on mips64el won't install. Segmentation fault will occur in
postinst script.

I don't have a mips64el box so cannot reproduce it, but examples are *all
around* official buildd.

This bug is preventing many packages from building and migrating to testing.

Examples: [1] [2]

[1] https://buildd.debian.org/status/fetch.php?pkg=kwallet-
kf5=mips64el=5.28.0-3=1484543446
[2]
https://buildd.debian.org/status/fetch.php?pkg=xfce4-terminal=0.8.3-1=mips64el=1484543729



-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dbus depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libapparmor1 2.11.0-1
ii  libaudit11:2.6.7-1
ii  libc62.24-8
ii  libcap-ng0   0.7.7-3
ii  libdbus-1-3  1.10.14-1
ii  libexpat12.2.0-2
ii  libselinux1  2.6-3
ii  libsystemd0  232-10
ii  lsb-base 9.20161125

dbus recommends no packages.

Versions of packages dbus suggests:
ii  dbus-user-session [default-dbus-session-bus]  1.10.14-1
ii  dbus-x11 [dbus-session-bus]   1.10.14-1

Versions of packages dbus is related to:
ii  dbus-x11  1.10.14-1
ii  systemd   232-10
ii  systemd-sysv  232-10

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-11

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-11
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 851412 851445 851475 851492 851688
Changes:
 systemd (232-11)