Processed: your mail

[Debian Bug Tracking System]

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

> reassign 851548 gnustep-back-common
Bug #851548 [paje and vite] error when installing Paje and Vite in the ubuntu 
subsystem in win10
Warning: Unknown package 'paje'
Bug reassigned from package 'paje and vite' to 'gnustep-back-common'.
Ignoring request to alter found versions of bug #851548 to the same values 
previously set
Ignoring request to alter fixed versions of bug #851548 to the same values 
previously set
> severity 851548 serious
Bug #851548 [gnustep-back-common] error when installing Paje and Vite in the 
ubuntu subsystem in win10
Severity set to 'serious' from 'normal'
> --
Stopping processing here.

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

Bug#851549: [Pkg-utopia-maintainers] Bug#851549: dbus: Segmentation fault in dbus.postinst on mips64el

[Michael Biebl]

Control: reassign -1 src:systemd
Control: forcemerge 851412 -1
Control: affects 851412 + dbus

Am 16.01.2017 um 06:58 schrieb Boyuan Yang:
> 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.
> 

The bug is ttbomk in binutils, which creates a broken libsystemd0 on
mips*. Merging with existing bug report.
It's currently assigned to systemd but will eventually be re-assigned to
binutils once we have confirmation from the mips porters.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-utopia-maintainers] Bug#851549: dbus: Segmentation fault in dbus.postinst on mips64el

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:systemd
Bug #851549 [dbus] dbus: Segmentation fault in dbus.postinst on mips64el
Bug reassigned from package 'dbus' to 'src:systemd'.
No longer marked as found in versions dbus/1.10.14-1.
Ignoring request to alter fixed versions of bug #851549 to the same values 
previously set
> forcemerge 851412 -1
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Severity set to 'serious' from 'grave'
Added indication that 851549 affects pdns,pdns-recursor,xvfb,src:octave
Marked as found in versions systemd/232-10.
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Merged 851412 851505 851549
> affects 851412 + dbus
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Added indication that 851412 affects dbus
Added indication that 851505 affects dbus
Added indication that 851549 affects dbus

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

Bug#851549: dbus: Segmentation fault in dbus.postinst on mips64el

[Boyuan Yang]

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

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

[Andreas Tille]

Hi Lincoln,

On Sun, Jan 15, 2017 at 04:25:46PM -0500, Lincoln Stein wrote:
> The bug in the memory adaptor that Scott found turns out to have been from
> using the old perl 1.6.9 installed by the Debian package. Updating to 1.7.1
> (1.007001) fixes the problem.
> 
> I have merged all GBrowse changes into git version 2.56 and have made a
> CPAN release. I think you can go ahead and package it.

thanks a lot for your work on this.

For the Debian packaging[1] I imported the new version and tried to
adapt the patches[2] (BTW, I have no idea whether any previous
maintainer of the package pointed to it but some of these might be
interesting to integrate into the upstream code).

Since I learned from Perl team (in CC) that I can exclude tests via

   debian/tests/pkg-perl/smoke-skip

I tried to use this feature.  Unfortunately this does not work as
expected - at least in the build process.  Could anybody with better
Perl skills than me please have a look at the failed build time tests?

Thanks to all who provided help so far to finally fix gbrowse for the
next Debian stable release

 Andreas.

[1] https://anonscm.debian.org/git/debian-med/gbrowse.git
[2] https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches

-- 
http://fam-tille.de

Bug#851372: marked as done (prometheus-alertmanager FTBFS on mipsel and mips64el: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2017 04:48:40 +
with message-id 
and subject line Bug#851372: fixed in prometheus-alertmanager 0.5.1+ds-7
has caused the Debian Bug report #851372,
regarding prometheus-alertmanager FTBFS on mipsel and mips64el: test failures
to be marked as done.

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

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


-- 
851372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-alertmanager
Version: 0.5.1+ds-5
Severity: serious

prometheus-alertmanager FTBFS on mipsel and mips64el
(but not on the big endian mips):

https://buildd.debian.org/status/package.php?p=prometheus-alertmanager

...
=== RUN   TestSilencing
=== RUN   TestSilenceDelete
--- FAIL: TestInhibiting (3.51s)
acceptance.go:131: AM on 127.0.0.1:35417
acceptance.go:304: Error pushing [InstanceDown[27bbfd8][active]]: Post 
http://127.0.0.1:35417/api/v1/alerts: dial tcp 127.0.0.1:35417: getsockopt: 
connection refused
acceptance.go:304: Error pushing [InstanceDown[27b9fd8][active]]: Post 
http://127.0.0.1:35417/api/v1/alerts: dial tcp 127.0.0.1:35417: getsockopt: 
connection refused
acceptance.go:304: Error pushing [test1[38692d7][active]]: Post 
http://127.0.0.1:35417/api/v1/alerts: dial tcp 127.0.0.1:35417: getsockopt: 
connection refused
acceptance.go:195: 
collector "webhook":

interval [3,3.5]
---
- test1[38692d7][active][1:]
- InstanceDown[27b9fd8][active][1:]
- JobDown[13c0540][active][2.2:]
  [ ✗ ]
interval [2,2.5]
---
- test1[38692d7][active][1:]
- InstanceDown[27bbfd8][active][1:]
- InstanceDown[27b9fd8][active][1:]
  [ ✗ ]

Expected total of 6 alerts, got 1
received:
@ 3.30512607
- JobDown[13c0540][active][2.261620366:]

acceptance.go:199: stdout:
acceptance.go:200: stderr:
time="2017-01-14T09:41:46Z" level=info msg="Starting 
alertmanager (version=, branch=, revision=)" source="main.go:102" 
time="2017-01-14T09:41:46Z" level=info msg="Build context 
(go=go1.6.1 gccgo (Debian 6.3.0-2) 6.3.0 20161229, user=, date=)" 
source="main.go:103" 
time="2017-01-14T09:41:46Z" level=info msg="Loading 
configuration file" file="/tmp/am_test858103233/config.yml" 
source="main.go:196" 
time="2017-01-14T09:41:46Z" level=info msg="Listening on 
127.0.0.1:35417" source="main.go:251" 
time="2017-01-14T09:41:47Z" level=debug msg="Received alert" 
alert=JobDown[13c0540][active] component=dispatcher source="dispatch.go:168" 
time="2017-01-14T09:41:48Z" level=debug msg="flushing 
[JobDown[13c0540][active]]" aggrGroup=cbf29ce484222325 source="dispatch.go:405" 
--- FAIL: TestMergeAlerts (6.50s)
acceptance.go:131: AM on 127.0.0.1:46231
acceptance.go:304: Error pushing [test[1f56cb8][active]]: Post 
http://127.0.0.1:46231/api/v1/alerts: dial tcp 127.0.0.1:46231: getsockopt: 
connection refused
acceptance.go:195: 
collector "webhook":

interval [6,6.5]
---
- test[1f56cb8][active][5.3:]
  [ ✓ ]
interval [5,5.5]
---
- test[1f56cb8][resolved][1:4.8]
  [ ✓ ]
interval [4,4.5]
---
- test[1f56cb8][active][1:]
  [ ✓ ]
interval [3,3.5]
---
- test[1f56cb8][active][1:]
  [ ✓ ]
interval [2,2.5]
---
- test[1f56cb8][active][1:]
  [ ✗ ]

received:
@ 6.112938927
- test[1f56cb8][active][5.302080842:]
@ 5.155567758
- test[1f56cb8][resolved][1:4.8]
@ 4.122295102
- test[1f56cb8][active][1:]
@ 3.11564389
- test[1f56cb8][active][1:]
@ 2.140577375
- test[1f56cb8][active][1:]

acceptance.go:199: stdout:
acceptance.go:200: stderr:
time="2017-01-14T09:41:49Z" level=info msg="Starting 
alertmanager 

Bug#851372: [pkg-go] Bug#851372: Bug#851372: prometheus-alertmanager FTBFS on mipsel and mips64el: test failures

[Martín Ferrari]

OK, I've finally managed to reproduce the problem, by running the build
with low prioirty in a very CPU-starved environment. It is again a
timing issue when starting the test server.

Will produce a patch and upload ASAP.


-- 
Martín Ferrari (Tincho)

Bug#818875: konqueror: green SSL checkbox despite expired server certificate

[Lisandro Damián Nicanor Pérez Meyer]

Disclaimer: I normally just look at Qt stuff, so I don't have a broad view on 
the issue nor an authoritative say in this.

On domingo, 15 de enero de 2017 20:55:52 ART Didier 'OdyX' Raboud wrote:
> Le lundi, 21 mars 2016, 11.03:13 h CET Thorsten Glaser a écrit :
> > Package: konqueror
> > Version: 4:15.08.3-1
> > Severity: grave
> > Tags: security
> > Justification: user security hole
> > 
> > See attached screenshot – konqueror does not error out when the
> > certificate is expired and even shows a green checkbox. (I may
> > or may not have ACK’d the certificate in an earlier session, I
> > don’t know right now, but showing a green checkbox is still
> > wrong.)
> 
> https://expired.identrustssl.com/ is an online example to test that
> use-case, which I can reproduce.
> 
> konqueror is RC-buggy in stretch because of that (IMHO rightful) bug. It is
> also plagued by other bugs, I wonder if konqueror should really be shipped
> in stretch. How feasible is it to remove it ?

Well, konqueror is part of kde-baseapps. One could imagine not shipping the 
binary and maybe some desktop files, but that source package also provides 
konqueror-related libs, and removing them will definitely be hard. And I don't 
know for sure if those bugs are really related to the front end konqueror is 
or the libs themselves.

As far as I understand konqueror is not supported by Debian's security team 
since ages, and we have always been recommending it for local/safe stuff. 

Moreover, on the same grounds, I personally tried to remove Qt4's webkit:

  https://wiki.debian.org/Qt4WebKitRemoval

but when I asked the security team they simply say something along "we don't 
support it, we don't care" which is fairly understandable.

So, all in all, I don't think it will be easy and before getting konqueror out 
I'll prefer removing Qt4' webkit.

But then again, I should not be considerer an authoritative voice here. Maxy 
should probably know much better than I.

Kinds rgeards, Lisandro.

-- 
Los estadounidenses no tienen la culpa, la guerra tiene la culpa. La falta de
voluntad de la gente para comprender a aquellos que tienen valores diferentes,
eso es lo que tiene la culpa.
  Shinji Mikamo
  


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#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Fields, Christopher J]

That’s great news Lincoln, fantastic!

chris

From: Lincoln Stein >
Date: Sunday, January 15, 2017 at 3:25 PM
To: Andreas Tille >
Cc: Scott Cain >, 
"848...@bugs.debian.org" 
<848...@bugs.debian.org>, Chris Fields 
>, Debian Med Project List 
>, Charles 
Plessy >, Olivier Sallou 
>, Sascha Steinbiss 
>, Carnë Draug 
>
Subject: Re: Remaining issue with gbrowse - any help (Was: Urgent call to 
BioPerl users (Was: Bug#848236: src:gbrowse: ...)

Hi,

The bug in the memory adaptor that Scott found turns out to have been from 
using the old perl 1.6.9 installed by the Debian package. Updating to 1.7.1 
(1.007001) fixes the problem.

I have merged all GBrowse changes into git version 2.56 and have made a CPAN 
release. I think you can go ahead and package it.

Lincoln

On Thu, Jan 12, 2017 at 11:37 PM, Andreas Tille 
> wrote:
Thanks to you both.  I think the only question targeted directly at my
was the "how much time question":  On Februrar 5 is full freeze.  You
need to cut 10 days from this since a package has a 10 day migration
time until it makes it from unstable to the release candidates in
testing.  So this would make 2017-01-25 - but if there is a single (even
unrelated to gbrowse) issue that might prevent the migration gbrowse is
doomed.  So I'd recommend to get something out until beginning of next
week.

Kind regards

  Andreas.

On Thu, Jan 12, 2017 at 02:23:42PM -0500, Scott Cain wrote:
> I made a few changes in a branch off that security-bug-fixes branch that
> quieted several warning messages, though I still need to sort out at least
> one problem (the memory adaptor doesn't seem to be reading fasta files, but
> also doesn't emit a warning about a problem).  Lincoln, if you want to look
> at this pull request, you could pull those changes into the security bug
> fix branch:
>
> https://github.com/GMOD/GBrowse/pull/59
>
> Scott
>
>
> On Thu, Jan 12, 2017 at 1:57 PM, Lincoln Stein 
> >
> wrote:
>
> > Hi Andreas,
> >
> > I was able to remove the vast majority of the warnings and other
> > incompatibility issues, but need to do more testing to identify areas of
> > the code that were not covered. How much time do I have? If you want to go
> > with a fully functional version that may issue warnings when the user takes
> > certain rare actions, it is the "security-bug-fixes" branch at
> > https://github.com/GMOD/GBrowse
> >
> > Lincoln
> >
> > On Thu, Jan 12, 2017 at 1:39 PM, Andreas Tille 
> > > wrote:
> >
> >> Hi Lincoln,
> >>
> >> On Wed, Dec 21, 2016 at 06:25:46PM -0500, Lincoln Stein wrote:
> >> > I am devoting several days over the Christmas holidays to fixing the
> >> > various outstanding bugs in gbrowse. Stay tuned!
> >>
> >> Did you managed to managed to work on this?  If not we probably can not
> >> include gbrowse in the next Debian stable release which would be a
> >> shame.
> >>
> >> 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
> > 

Bug#851408: marked as done (CVE-2016-6814)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2017 00:48:48 +
with message-id 
and subject line Bug#851408: fixed in groovy 2.4.8-1
has caused the Debian Bug report #851408,
regarding CVE-2016-6814
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.)


-- 
851408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: groovy
Severity: grave
Tags: security

Hi,
please see http://seclists.org/oss-sec/2017/q1/92

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: groovy
Source-Version: 2.4.8-1

We believe that the bug you reported is fixed in the latest version of
groovy, 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.
Emmanuel Bourg  (supplier of updated groovy 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 00:44:33 +0100
Source: groovy
Binary: groovy groovy-doc groovy2
Architecture: source all
Version: 2.4.8-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 groovy - Agile dynamic language for the Java Virtual Machine
 groovy-doc - Agile dynamic language for the Java Virtual Machine (documentatio
 groovy2- Agile dynamic language for the Java Virtual Machine (transitional
Closes: 851408
Changes:
 groovy (2.4.8-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream release
 - Fixes CVE-2016-6814: serialization vulnerability (Closes: #851408)
 - Refreshed the patches
 - Updated the poms
   * Disabled parallel building
Checksums-Sha1:
 9c8012c83a65ba03e7ee01d8db3493cc4d702549 2390 groovy_2.4.8-1.dsc
 9a91e716cdc13bb44cb1ae858f1a37ce2f92bad7 2985236 groovy_2.4.8.orig.tar.xz
 40c60f840d99062122caa13328c021cc1c4f4783 24256 groovy_2.4.8-1.debian.tar.xz
 d7f332dd5c5171c2152675364c1c6cb0e554d5be 3170454 groovy-doc_2.4.8-1_all.deb
 5240ff0a8da814784f79baffba85db8d54601e40 12162 groovy2_2.4.8-1_all.deb
 4fe5d1a53da0f51ab30ee0a3483da9d694dda0fb 14659052 groovy_2.4.8-1_all.deb
 20ee6b8bd9a6cd8a49379ca1c29f09ca1dc47bb8 14001 groovy_2.4.8-1_amd64.buildinfo
Checksums-Sha256:
 d910b8426db25acad45177d8ebc95b2d1a522bd5d5ded5da71ff2cb1dae552f8 2390 
groovy_2.4.8-1.dsc
 ed9cda4eedfe3eb49c8fdb0ec8e38e0517c2565f4046f2897e0108465c4b8fa1 2985236 
groovy_2.4.8.orig.tar.xz
 f99906d539eb3de0d21398485bb26c825819155b8d19773bf3872cbb8b0cdab1 24256 
groovy_2.4.8-1.debian.tar.xz
 7399711203eb4956be49f5fa64e942fac3e166c8ea7cc6583f8b822013bc6dac 3170454 
groovy-doc_2.4.8-1_all.deb
 faf67185172ed225b3f7865d188dd869ebc47c1cca4cd673713b663d2e0a103c 12162 
groovy2_2.4.8-1_all.deb
 af3235cdc64741ffd17d51baf331c92d90b4b732c15d4e582ecdb15c349ab38f 14659052 
groovy_2.4.8-1_all.deb
 e7057bbb1b2517586e2c9ef9d9eff4bc24777ec9e34bf9f063f5f6a9813e5372 14001 
groovy_2.4.8-1_amd64.buildinfo
Files:
 7d9417f636be7bfcb431b1cd454aa2e1 2390 java optional groovy_2.4.8-1.dsc
 4120d63a3c5f0ab2f3e8f37bb1130f21 2985236 java optional groovy_2.4.8.orig.tar.xz
 c81a078dcf1cc0a746ea9a2b40a49562 24256 java optional 
groovy_2.4.8-1.debian.tar.xz
 8db36f71c64abd90ebb410e285fc21ba 3170454 doc optional 
groovy-doc_2.4.8-1_all.deb
 91c194c9b908ff221f792f2efc2d9029 12162 oldlibs extra groovy2_2.4.8-1_all.deb
 ec12f9562f63e33f52144aedaff16c17 14659052 java optional groovy_2.4.8-1_all.deb
 65023e56a0adee4dc3ecaf758bafebad 14001 java optional 
groovy_2.4.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlh8EdUACgkQ9RPEGeS5
0KwSAA/+JQ8MbJK93SSpXeizBUPwhdN7rRrMtsDvnF39ABOI1VH3lHcjGyFj6i+j
3M0aeGBz4XAvdiIkULF8xiqEbJCZuF0vCtlR1kdowoV3FNxn2ixH0lSDJ9vs55QZ
USuBZHHUV5uQdYJtL6iXAB2SWGlsfPbFtypot1Fz2BsxdnPObL1vioSVIIJJ+r3B
btTF5h/GBdVG1cBgmNekruWJVXr+vXzvS7jydWkNWz2P/LvwQ3EaSZsZsyTnPG/s
5hJxVIMqXQ0h4khHiUgGSnYAsWc84+7pSsB9jGgAXc/0Ey0Abt6PRDBAcOrQlqbt
KUy47Nf5sya81k/bvt9niF7BDHx/Gq6NVne1mKQzm/vfWh+tfc4/GeZbl+TalYGR
KaSupvWPDurjUraUH4Iil6pWJyxVqZTkVZHQPb1pFNzYjUKdbBmVAQp90DXtnl2o

Bug#851372: [pkg-go] Bug#851372: prometheus-alertmanager FTBFS on mipsel and mips64el: test failures

[Martín Ferrari]

Adrian,

On 15/01/17 20:08, Adrian Bunk wrote:
> On Sun, Jan 15, 2017 at 07:40:57PM -0300, Martín Ferrari wrote:

> Looking at the error message "getsockopt: connection refused",
> it is possible that there might be different network related
> configuration or permissions on these buildds?

That would be weird. This is an end-to-end test that starts an instance
of the server and connects through localhost.

> A web search finds for example
>   
> https://buildd.raspbian.org/status/fetch.php?pkg=prometheus-alertmanager=armhf=0.3.0+ds-2=1469110396

That link does not work for me, but from the logs I find in that site,
the failures were unrelated, and the latest attempt to build succeeded:

https://buildd.raspbian.org/status/logs.php?pkg=prometheus-alertmanager=armhf


-- 
Martín Ferrari (Tincho)

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages]

[Raphaël Halimi]

Le 15/01/2017 à 15:52, Ian Jackson a écrit :
> tl;dr
>   TYVM to Michael Biebl
>   I intend QA upload of systemd-shim with Michael's wrapper

Hi,

I just installed the updated systemd-shim from experimental, removed the
hold on systemd packages to update them to their latest version from
sid, and I can confirm that now everything works as expected (shutdown
entries in lightdm, polkit auth agent, and obsession menu logout entries).

Michael, Ian, thank you very much to both of you.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#808654: Bug #808654 closed accidentally (it seems)

[Santiago Vila]

On Sun, Jan 15, 2017 at 11:24:12PM +0100, Piotr Ożarowski wrote:
> > Hello Piotr. For reasons I still don't understand, your commands
> > above made the bug to be closed.
> 
> the bug was actually not in fedmsg but in moksha.hub and I fixed it in 
> 1.4.1-2 
> (hence different source package/version that was closing bug).
> 
> I just checked (build logs you pointed me to are really old, before my
> fix) and this package still FTBFS but for a completely different reason
> (I guess it's OK to reopen this one as the final result is the same - it
> doesn't build)

There are actually several schools of thought about that :-). One of
them says that when the reason for the bug changes, we need another
bug report. I do not always agree with that [*], so if it's ok for you
to recycle this bug (because of the observed effect), it's also ok for
me.

[*] For example, for bugs of type "FTBFS with dpkg-buildpackage -A",
I usually reopen when the package still FTBFS with dpkg-buildpackage -A
after an incomplete fix, because at least in this case I was reporting
the "end effect" and not the cause.

Thanks.

Processed: Re: uncertainties: FTBFS randomly (FAIL: Full comparison to a Monte-Carlo calculation)

[Debian Bug Tracking System]

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

> severity 844572 important
Bug #844572 [src:uncertainties] uncertainties: FTBFS randomly (FAIL: Full 
comparison to a Monte-Carlo calculation)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#844572: uncertainties: FTBFS randomly (FAIL: Full comparison to a Monte-Carlo calculation)

[Santiago Vila]

severity 844572 important
thanks

Hello.

I'm setting the severity of this bug to "important" not because
I don't think it is not RC (as Release Policy still says that
packages must autobuild *without* failure), but because the
Release Managers are considering to decide about RC-ness
of this kind of bugs based on the probability of failure.

We don't know what kind of threshold there will be for stretch, so I
strongly recommend that you act as if this bug was serious and RC,
especially if the failures happen very often on any kind of
autobuilder which is not misconfigured.

Unfortunately this package was already autoremoved because of this bug.

This is probably not ok if we consider that other packages which FTBFS
a lot more often are still in stretch. I'm going to ask Release
Managers if it's possible to reallow this in stretch.

Thanks.

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

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2017 00:03:45 +
with message-id 
and subject line Bug#851018: fixed in dpmb 0~2017.01.16
has caused the Debian Bug report #851018,
regarding dpmb: 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.)


-- 
851018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpmb
Version: 0~2016.06.30
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 '/<>'
> echo ":revdate: "$(date --utc --date="@${SOURCE_DATE_EPOCH:-$(date +%s)}"  
> '+%FT%T%:z') > version.adoc
> echo -n ":revnumber: " >> version.adoc; \
> if [ -d .git ] && `which git >/dev/null`; then \
> git describe --tags --always >> version.adoc; \
> elif [ -d debian/changelog ] && `which dpkg-parsechangelog >/dev/null`; then \
> dpkg-parsechangelog | fgrep Version | awk '{print $2}' >> version.adoc; \
> fi
> # There seems to be a bug in the images macro if data-uri is
> a2x  -f pdf -L debian-paketmanagement.adoc
> a2x  -f epub -L debian-paketmanagement.adoc
> # set and images are in subdirectories. Hence we override the
> # original macros with fixed ones.
> asciidoc  -f asciidoc-macros/data-uri-fixup.conf -a data-uri -o 
> debian-paketmanagement.allinone.html debian-paketmanagement.adoc
> asciidoc: WARNING: version.adoc: line 2: 
> {include:/<>/debian-paketmanagement-docinfo.html}: file does not 
> exist
> a2x: ERROR: missing configuration file: 
> /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
> Makefile:32: recipe for target 'debian-paketmanagement.pdf' failed
> make[2]: *** [debian-paketmanagement.pdf] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/dpmb_0~2016.06.30_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: dpmb
Source-Version: 0~2017.01.16

We believe that the bug you reported is fixed in the latest version of
dpmb, 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.
Axel Beckert  (supplier of updated dpmb 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 00:18:47 +0100
Source: dpmb
Binary: debian-paketmanagement-buch
Architecture: source all
Version: 0~2017.01.16
Distribution: unstable
Urgency: low
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 debian-paketmanagement-buch - book about Debian package management written in 
German
Closes: 851018
Changes:
 dpmb (0~2017.01.16) unstable; urgency=low
 .
   * New snapshot.
   * Add build-dependency on "asciidoc-dblatex (>= 8.6.9-5) | asciidoc (<=
 8.6.9-3.1)" to fix FTBFS with newer asciidoc packages due to other
 packages now containing the required files for using asciidoc with
 dblatex. (Closes: #851018)
Checksums-Sha1:
 8ab3d39ce7652d192b98ba4670daeb046f1880cf 1741 dpmb_0~2017.01.16.dsc
 82ea006080fc34bb2acb51a6b156c69659ef49b1 9079344 dpmb_0~2017.01.16.tar.xz
 54cf4c9d9832e96e048afca77c20df00b5a871c2 39153910 
debian-paketmanagement-buch_0~2017.01.16_all.deb
 eb57e00aa47694bda79702a74ee0b9e5e1554fa1 12150 
dpmb_0~2017.01.16_amd64.buildinfo
Checksums-Sha256:
 6a54a62f8db98f8228cf705e1b5dc57d1c01c92d64eaf303a87002b43be2c7ed 1741 
dpmb_0~2017.01.16.dsc
 3fecda6af2cec9426bed531fae31d876a4aa876b0d6a3d152429e310e1b94134 9079344 
dpmb_0~2017.01.16.tar.xz
 

Bug#849069: marked as done (sdb: depends on libreadline6 which is going away)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:35:28 +
with message-id 
and subject line Bug#849069: fixed in sdb 1.2-1.1
has caused the Debian Bug report #849069,
regarding sdb: depends on libreadline6 which is going away
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.)


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

Hi,

We are removing readline6 from stretch. Please build-dep on libreadline-dev
to move to readline7.

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: sdb
Source-Version: 1.2-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated sdb 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: Mon, 16 Jan 2017 01:14:02 +0200
Source: sdb
Binary: sdb
Architecture: source
Version: 1.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jo Shields 
Changed-By: Adrian Bunk 
Description:
 sdb- a command line client for Mono's soft debugger
Closes: 849069
Changes:
 sdb (1.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch to libreadline7. (Closes: #849069)
Checksums-Sha1:
 b84cbfe7f2e51877da2faacd6100474d8485d4fe 1986 sdb_1.2-1.1.dsc
 00472c0ec4fab7b2aaf2077025383a51a5324e8c 2856 sdb_1.2-1.1.debian.tar.xz
Checksums-Sha256:
 59bccd8acd91e297c41237dc31b16f321546df00e466cf4c08d3186dca8c0659 1986 
sdb_1.2-1.1.dsc
 75517929295ed1d150655ba51429c2668c9d79532064eb10b1c54f04827e786f 2856 
sdb_1.2-1.1.debian.tar.xz
Files:
 4075a4e77bc81090a19faf808dc8678f 1986 cli-mono extra sdb_1.2-1.1.dsc
 352cab2df7eb42acffae410bd66caf56 2856 cli-mono extra sdb_1.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh8A6QACgkQiNJCh6LY
mLF1iBAAhkdT6tSNQYqdm8ADd6tkeVuT6ljeqrXm7Gi1fsTrULW/+cxU12TDI13J
NTHBE465std08SGmzuOk9nHDnz4+CxdS+CnCEk9UfINTlrRfzQW8ZiOyQ+OZiMu0
dRb+0UFntY8Qb+/iQwjWJR8zNNuxNkllaNelSlBjp7SC1kVed8Jmca5UylEHZ2J/
dg2G3l3nR7FGCzpWLoikkgqKBwCCkBzsnqTY4aL89tuhTyc2nJ/istYqKriprHc6
hz6x8XXVD5bUMYFfSvVBFXHYree6YGue22QnJR8ZfWkuUlRkc/vYMX0MiUVjQFKT
08h3S7kWPjQwNNXst3huky9CARGUCsdbOkQHaecsbrHV5thamQ13JDJ1FRbtElrO
WHz8NvgNm6PuGOkFy0E3GdT1R41KbxPNf3ULQ5XWosv8LftubRueLfLGI6el5TTz
IWwOyOyw1BTSZhAPlgeC6UTRYuwj8c2E7nbQfIRIJy/EohhPLoDuQrgc7uCwQJbV
UasKEu+j3GbDgorU4fETGNHMPuDiZ6Gh85/tsr0dfUJ9Fmd5iSEX+luPDAPgWjbK
PTZ/GE0kbdnOV/fqNsx4DeQZPnUtkjdmrBLnart4bdDmtqV0P7bHEWD4AhCAcirL
FGW2sQQQ+C1WiyX1T1YoejpGKrOoTTuh+8Q3Conlx6oSxvVZzQI=
=5Xuk
-END PGP SIGNATURE End Message ---

Bug#851372: [pkg-go] Bug#851372: prometheus-alertmanager FTBFS on mipsel and mips64el: test failures

[Adrian Bunk]

On Sun, Jan 15, 2017 at 07:40:57PM -0300, Martín Ferrari wrote:
> Adrian,
> 
> On 14/01/17 10:17, Adrian Bunk wrote:
> > Source: prometheus-alertmanager
> > Version: 0.5.1+ds-5
> > Severity: serious
> > 
> > prometheus-alertmanager FTBFS on mipsel and mips64el
> > (but not on the big endian mips):
> 
> Were you able to reproduce these failures?
> 
> I saw the buildds are failing, but I can't reproduce this in the porterbox.

I haven't tried, I am just submitting issues from buildd logs.

Looking at the error message "getsockopt: connection refused",
it is possible that there might be different network related
configuration or permissions on these buildds?

A web search finds for example
  
https://buildd.raspbian.org/status/fetch.php?pkg=prometheus-alertmanager=armhf=0.3.0+ds-2=1469110396

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#849598: marked as done (amarok: FTBFS (cannot find -lmysqlclient))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:04:43 +
with message-id 
and subject line Bug#849598: fixed in amarok 2.8.0-8
has caused the Debian Bug report #849598,
regarding amarok: FTBFS (cannot find -lmysqlclient)
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.)


-- 
849598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:amarok
Version: 2.8.0-7
Severity: serious

Dear maintainer:

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


[...]
cd 
/<>/obj-x86_64-linux-gnu/src/core-impl/collections/db/sql/mysqlservercollection
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/amarok_collection-mysqlservercollection.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fmessage-length=0 -Wl,--as-needed -Wnon-virtual-dtor 
-Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith 
-Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common 
-Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden 
-Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG 
-Wl,--enable-new-dtags  -Wl,--no-undefined -lc -Wl,-z,relro -shared  -o 
../../../../../../lib/amarok_collection-mysqlservercollection.so 
CMakeFiles/amarok_collection-mysqlservercollection.dir/amarok_collection-mysqlservercollection_automoc.cpp.o
 
CMakeFiles/amarok_collection-mysqlservercollection.dir/__/mysql-shared/MySqlStorage.cpp.o
 
CMakeFiles/amarok_collection-mysqlservercollection.dir/MySqlServerCollection.cpp.o
 -Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib: ../../../../../../lib
 /libamarok-sqlcollection.so.1.0.0 ../../../../../../lib/libamaroklib.so.1.0.0 
/usr/lib/x86_64-linux-gnu/libQtCore.so /usr/lib/x86_64-linux-gnu/libQtGui.so 
-L/usr/lib/x86_64-linux-gnu  -lmysqlclient -lpthread -lz -lm -ldl -ldl -lz 
-lcrypt -lpthread ../../../../../../lib/libamarokcore.so.1.0.0 
/usr/lib/x86_64-linux-gnu/libQtGui.so /usr/lib/libkdecore.so.5.14.26 
/usr/lib/x86_64-linux-gnu/libQtDBus.so /usr/lib/x86_64-linux-gnu/libQtCore.so 
-Wl,-rpath-link,/<>/obj-x86_64-linux-gnu/lib 
/usr/bin/ld: cannot find -lmysqlclient
collect2: error: ld returned 1 exit status
src/core-impl/collections/db/sql/mysqlservercollection/CMakeFiles/amarok_collection-mysqlservercollection.dir/build.make:159:
 recipe for target 'lib/amarok_collection-mysqlservercollection.so' failed
make[3]: *** [lib/amarok_collection-mysqlservercollection.so] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:2176: recipe for target 
'src/core-impl/collections/db/sql/mysqlservercollection/CMakeFiles/amarok_collection-mysqlservercollection.dir/all'
 failed
make[2]: *** 
[src/core-impl/collections/db/sql/mysqlservercollection/CMakeFiles/amarok_collection-mysqlservercollection.dir/all]
 Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Makefile:141: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: make -j1 returned exit code 2
debian/rules:27: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


I know it's strange because it was uploaded just five days ago,
but it also fails here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: amarok
Source-Version: 2.8.0-8

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated amarok 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: 

Bug#850561: marked as done (amarok: 'errmsg.sys' had only 969 error messages)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:04:43 +
with message-id 
and subject line Bug#849326: fixed in amarok 2.8.0-8
has caused the Debian Bug report #849326,
regarding amarok: 'errmsg.sys' had only 969 error messages
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.)


-- 
849326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok-common
Version: 2.8.0-7
Severity: normal

Dear Maintainer,

when trying to start Amarok the following error message is displayed:

The amarok database reported the following errors:
GREPME MySQLe query failed! (2000) Error message file 
'/usr/share/kde4/apps/amarok/mysqle/errmsg.sys' had only 969 error
messages, but it should contain at least 982 error messages.
Check that the above file is the right version for this program!
on init
In most cases you will need to resolve these errors before Amarok will
run properly.

Best regards

Heinrich Schuchardt

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

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

Versions of packages amarok-common depends on:
pn  perl:any  

Versions of packages amarok-common recommends:
ii  amarok  2.8.0-7

amarok-common suggests no packages.

Versions of packages amarok depends on:
ii  amarok-utils  2.8.0-7
ii  kde-runtime   4:16.08.3-1
ii  libavcodec57  7:3.2.2-1
ii  libavformat57 7:3.2.2-1
ii  libavutil55   7:3.2.2-1
ii  libc6 2.24-8
ii  libcurl3-gnutls   7.51.0-1
ii  libgcrypt20   1.7.5-2
ii  libgdk-pixbuf2.0-02.36.2-1
ii  libgl1-mesa-glx [libgl1]  13.0.2-3
ii  libglib2.0-0  2.50.2-2
ii  libgpod4-nogtk0.8.3-8
ii  libkcmutils4  4:4.14.26-1
ii  libkdecore5   4:4.14.26-1
ii  libkdeui5 4:4.14.26-1
ii  libkdewebkit5 4:4.14.26-1
ii  libkdnssd44:4.14.26-1
ii  libkfile4 4:4.14.26-1
ii  libkio5   4:4.14.26-1
ii  libknewstuff3-4   4:4.14.26-1
ii  liblastfm11.0.9-1
ii  libloudmouth1-0   1.5.3-2
ii  libmariadbclient1810.1.20-3
ii  libmariadbd18 10.1.20-3
ii  libmtp9   1.1.12-1
ii  libmygpo-qt1  1.0.9-2
ii  libofa0   0.9.3-13
ii  libphonon44:4.9.0-4
ii  libplasma34:4.14.26-1
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.7+dfsg-11
ii  libqt4-network4:4.8.7+dfsg-11
ii  libqt4-opengl 4:4.8.7+dfsg-11
ii  libqt4-script 4:4.8.7+dfsg-11
ii  libqt4-sql4:4.8.7+dfsg-11
ii  libqt4-svg4:4.8.7+dfsg-11
ii  libqt4-xml4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libqtgui4 4:4.8.7+dfsg-11
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.3.4.dfsg-9.1
ii  libsolid4 4:4.14.26-1
ii  libstdc++66.2.1-5
ii  libthreadweaver4  4:4.14.26-1
ii  libx11-6  2:1.6.4-2
ii  libxml2   2.9.4+dfsg1-2.1
ii  phonon4:4.9.0-4

Versions of packages amarok recommends:
ii  clamz0.5-2+b1
ii  kio-audiocd  4:16.08.3-1

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.7+dfsg-11
pn  libqt4-sql-psql
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
pn  moodbar

Versions of packages amarok-common is related to:
ii  phonon-backend-vlc [phonon-backend]  0.9.0-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: amarok
Source-Version: 2.8.0-8

We believe that the bug you reported is fixed in the latest version of
amarok, 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 849...@bugs.debian.org,
and the maintainer will 

Bug#849326: marked as done ([amarok] Collection is disabled due to failing MySQL operation (errmsg.sys) at startup)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:04:43 +
with message-id 
and subject line Bug#849326: fixed in amarok 2.8.0-8
has caused the Debian Bug report #849326,
regarding [amarok] Collection is disabled due to failing MySQL operation 
(errmsg.sys) 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.)


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

Package: amarok
Version: 2.8.0-7
Severity: important

--- Please enter the report below this line. ---
After upgrading everything from Testing to Unstable, Amarok cannot use 
the music collection anymore. An error related to the MySQL error type 
version is displayed at startup:


GREPME MySQLe query failed! (2000) Error message file 
'/usr/share/kde4/apps/amarok/mysqle/errmsg.sys' had only 969 error 
messages, but it should contain at least 982 error messages.

Check that the above file is the right version for this program! on init
In most cases you will need to resolve these errors before Amarok will 
run properly.


Amarok is able to play music, but all features related to the collection 
are gone.


--- System information. ---
Architecture:
Kernel: Linux 4.9.0-rc8-amd64

Debian Release: stretch/sid
900 testing ftp.debian.org
500 unstable ftp.debian.org
500 stable www.trillian.im
500 stable repo.vivaldi.com
500 stable dl.google.com
500 stable deb.opera.com
500 sid linux.dropbox.com
1 experimental ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
==-+-==
amarok-common (= 2.8.0-7) | 2.8.0-7
amarok-utils (= 2.8.0-7) | 2.8.0-7
kde-runtime (>> 4:4.10) | 4:16.08.3-1
libavcodec57 (>= 7:3.2.2) |
OR libavcodec-extra57 (>= 7:3.2.2) |
libavformat57 (>= 7:3.2.2) |
libavutil55 (>= 7:3.2.2) |
libc6 (>= 2.14) |
libcurl3-gnutls (>= 7.16.2) |
libgcrypt20 (>= 1.7.0) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libgl1-mesa-glx |
OR libgl1 |
libglib2.0-0 (>= 2.37.3) |
libgpod4-nogtk (>= 0.7.92) |
OR libgpod4 (>= 0.7.92) |
libkcmutils4 (>= 4:4.8.4) |
libkdecore5 (>= 4:4.8.4) |
libkdeui5 (>= 4:4.9.98) |
libkdewebkit5 (>= 4:4.8.4) |
libkdnssd4 (>= 4:4.8.4) |
libkfile4 (>= 4:4.8.4) |
libkio5 (>= 4:4.8.4) |
libknewstuff3-4 (>= 4:4.8.4) |
liblastfm1 (>= 1.0.0) |
libloudmouth1-0 (>= 1.1.4) |
libmariadbclient18 (>= 5.5.36) |
libmariadbd18 |
libmtp9 (>= 1.1.0) |
libmygpo-qt1 (>= 1.0.2) |
libofa0 (>= 0.9.3) |
libphonon4 (>= 4:4.7.0.0) |
libplasma3 (>= 4:4.8.4) |
libqjson0 (>= 0.7.1) |
libqt4-dbus (>= 4:4.6.1) |
libqt4-network (>= 4:4.5.3) |
libqt4-opengl (>= 4:4.8.0) |
libqt4-script (>= 4:4.5.3) |
libqt4-sql (>= 4:4.5.3) |
libqt4-svg (>= 4:4.5.3) |
libqt4-xml (>= 4:4.5.3) |
libqtcore4 (>= 4:4.8.0) |
libqtgui4 (>= 4:4.8.0) |
libqtwebkit4 (>= 2.1.0~2011week13) |
libsolid4 (>= 4:4.8.4) |
libstdc++6 (>= 5) |
libthreadweaver4 (>= 4:4.8.4) |
libx11-6 |
libxml2 (>= 2.7.4) |
phonon |
libqtscript4-core |
libqtscript4-gui |
libqtscript4-network |
libqtscript4-xml |
libqtscript4-sql |
libqtscript4-uitools |
amarok-common (= 2.8.0-7) | 2.8.0-7
amarok-utils (= 2.8.0-7) | 2.8.0-7
kde-runtime (>> 4:4.10) | 4:16.08.3-1
libavcodec57 (>= 7:3.2.2) |
OR libavcodec-extra57 (>= 7:3.2.2) |
libavformat57 (>= 7:3.2.2) |
libavutil55 (>= 7:3.2.2) |
libc6 (>= 2.14) |
libcurl3-gnutls (>= 7.16.2) |
libgcrypt20 (>= 1.7.0) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libgl1-mesa-glx |
OR libgl1 |
libglib2.0-0 (>= 2.37.3) |
libgpod4-nogtk (>= 0.7.92) |
OR libgpod4 (>= 0.7.92) |
libkcmutils4 (>= 4:4.8.4) |
libkdecore5 (>= 4:4.8.4) |
libkdeui5 (>= 4:4.9.98) |
libkdewebkit5 (>= 4:4.8.4) |
libkdnssd4 (>= 4:4.8.4) |
libkfile4 (>= 4:4.8.4) |
libkio5 (>= 4:4.8.4) |
libknewstuff3-4 (>= 4:4.8.4) |
liblastfm1 (>= 1.0.0) |
libloudmouth1-0 (>= 1.1.4) |
libmariadbclient18 (>= 5.5.36) |
libmariadbd18 |
libmtp9 (>= 1.1.0) |
libmygpo-qt1 (>= 1.0.2) |
libofa0 (>= 0.9.3) |
libphonon4 (>= 4:4.7.0.0) |
libplasma3 (>= 4:4.8.4) |
libqjson0 (>= 0.7.1) |
libqt4-dbus (>= 4:4.6.1) |
libqt4-network (>= 4:4.5.3) |
libqt4-opengl (>= 4:4.8.0) |
libqt4-script (>= 4:4.5.3) |
libqt4-sql (>= 4:4.5.3) |
libqt4-svg (>= 4:4.5.3) |
libqt4-xml (>= 4:4.5.3) |
libqtcore4 (>= 4:4.8.0) |
libqtgui4 (>= 4:4.8.0) |
libqtwebkit4 (>= 2.1.0~2011week13) |
libsolid4 (>= 4:4.8.4) |
libstdc++6 (>= 5) |
libthreadweaver4 (>= 4:4.8.4) |
libx11-6 |
libxml2 (>= 2.7.4) |
phonon |
libqtscript4-core |
libqtscript4-gui |
libqtscript4-network |
libqtscript4-xml |
libqtscript4-sql |
libqtscript4-uitools |
perl:any |


Package Status (Version) | Installed

Bug#850716: marked as done (python-pysaml2: CVE-2016-10127: XML External Entity attack)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:02:54 +
with message-id 
and subject line Bug#850716: fixed in python-pysaml2 2.0.0-1+deb8u1
has caused the Debian Bug report #850716,
regarding python-pysaml2: CVE-2016-10127: XML External Entity attack
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.)


-- 
850716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysaml2
Severity: serious
Tags: security patch

As per report from user:

 Forwarded Message 
Subject: python-pysaml2 XEE vulnerability
Date: Mon, 9 Jan 2017 14:50:41 +0100
From: Florian Best 
Organization: Univention GmbH
To: z...@debian.org
CC: openstack-de...@lists.alioth.debian.org

Dear debian python-pysaml2 maintainers,

there was a security hole fixed in python-pysaml2, which allowed XML
External Entity attacks:
https://github.com/rohe/pysaml2/pull/379
https://github.com/rohe/pysaml2/commit/6e09a25d9b4b7aa7a506853210a9a14100b8bc9b

Could you please release a security update?

Best regards,
Florian
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 2.0.0-1+deb8u1

We believe that the bug you reported is fixed in the latest version of
python-pysaml2, 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.
Thomas Goirand  (supplier of updated python-pysaml2 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, 09 Jan 2017 16:54:24 +0100
Source: python-pysaml2
Binary: python-pysaml2 python-pysaml2-doc
Architecture: source all
Version: 2.0.0-1+deb8u1
Distribution: jessie-security
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-pysaml2 - SAML Version 2 to be used in a WSGI environment - Python 2.x
 python-pysaml2-doc - SAML Version 2 to be used in a WSGI environment - doc
Closes: 850716
Changes:
 python-pysaml2 (2.0.0-1+deb8u1) jessie-security; urgency=medium
 .
   * Fix XXE issues on anything where pysaml2 parses XML directly:
 - CVE-2016-10127: backporting upstream patch (Closes: #850716).
 - add python-defusedxml as runtime depends.
 - switch debian/gbp.conf to use debian/jessie as packaging branch.
   * Add python-pymongo as (build-)depends.
Checksums-Sha1:
 0bbf1194d95c45f1fdd9c20cfb5ced27812a404a 2383 python-pysaml2_2.0.0-1+deb8u1.dsc
 f1fe1d6a295686640b147519711577b328c9d17a 2615832 
python-pysaml2_2.0.0.orig.tar.xz
 fe368731d7f97ebbb0be245d1320ae52137e399c 5944 
python-pysaml2_2.0.0-1+deb8u1.debian.tar.xz
 ff1a794513f23be464e3cc2f5badf82ee46a0259 176868 
python-pysaml2_2.0.0-1+deb8u1_all.deb
 25b6b3d497909f8b68d300dd939b4621ae0618ea 37866 
python-pysaml2-doc_2.0.0-1+deb8u1_all.deb
Checksums-Sha256:
 651009543559ba6fff0dc051bb717f69f717255a9eaa259dc57584f6dcbcee50 2383 
python-pysaml2_2.0.0-1+deb8u1.dsc
 c62d179ba27d345d9159d9a3f2bddea7567973720cbf916bbd05eda3e18e935f 2615832 
python-pysaml2_2.0.0.orig.tar.xz
 78209ca2e4ee6c6fd00a0c735646f668f1e5d0187d98c120c49a821ac20375c7 5944 
python-pysaml2_2.0.0-1+deb8u1.debian.tar.xz
 3e85114f08d18f3c64ca2b9d6703de44c2655298c6262701665ad1790f47784a 176868 
python-pysaml2_2.0.0-1+deb8u1_all.deb
 b581372519713ba817645d96acf4d633d069ffede03cec702dc7343605ff603b 37866 
python-pysaml2-doc_2.0.0-1+deb8u1_all.deb
Files:
 0a21478383a7f075b00477cdf3007aa2 2383 python optional 
python-pysaml2_2.0.0-1+deb8u1.dsc
 ff545022ba4ba6bbfe27e020001b9eb0 2615832 python optional 
python-pysaml2_2.0.0.orig.tar.xz
 43077bb4c9864f93b2db54252154294f 5944 python optional 
python-pysaml2_2.0.0-1+deb8u1.debian.tar.xz
 efbc1b2f04f03a08ff6fa9b9ce49e912 176868 python optional 
python-pysaml2_2.0.0-1+deb8u1_all.deb
 80dc4fae343c8c5bf34b9b9f39083674 37866 doc optional 
python-pysaml2-doc_2.0.0-1+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYdnRoAAoJENQWrRWsa0P+1OQQAInAMrUW7KScS+RLQ5U9Z0oL
6sTmRSlZ7tcumrRtMgXW7dKguwCEKFf+vL2JEQ1LNkt7KcjwYunPfywphhaE1Qlm

Bug#850900: marked as done (amarok: 6GREPME MySQLe query failed! (2000))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:04:43 +
with message-id 
and subject line Bug#849326: fixed in amarok 2.8.0-8
has caused the Debian Bug report #849326,
regarding amarok: 6GREPME MySQLe query failed! (2000)
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.)


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

Hello, I've written in some detail about the bug here:

https://bugs.kde.org/show_bug.cgi?id=374891

I have marked this as grave because it generates data loss
(the collection metadata, which is an integral part of Amarok
and most users wouldn't enjoy losing their statistic, favorites,
etc, built over years since this is a major part of Amarok). It also
renders the packages unusable. It should be marked as grave so as
to prevent the package from going to stable in its current state.

My issue is similar to #849326 - the major difference being that
Amarok also crashes when trying to play any file.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages amarok depends on:
ii  amarok-common 2.8.0-7
ii  amarok-utils  2.8.0-7
ii  kde-runtime   4:16.08.3-1
ii  libavcodec57  7:3.2.2-1
ii  libavformat57 7:3.2.2-1
ii  libavutil55   7:3.2.2-1
ii  libc6 2.24-8
ii  libcurl3-gnutls   7.51.0-1
ii  libgcrypt20   1.7.5-2
ii  libgdk-pixbuf2.0-02.36.2-1
ii  libgl1-mesa-glx [libgl1]  13.0.2-3
ii  libglib2.0-0  2.50.2-2
ii  libgpod4  0.8.3-8
ii  libkcmutils4  4:4.14.26-1
ii  libkdecore5   4:4.14.26-1
ii  libkdeui5 4:4.14.26-1
ii  libkdewebkit5 4:4.14.26-1
ii  libkdnssd44:4.14.26-1
ii  libkfile4 4:4.14.26-1
ii  libkio5   4:4.14.26-1
ii  libknewstuff3-4   4:4.14.26-1
ii  liblastfm11.0.9-1
ii  libloudmouth1-0   1.5.3-2
ii  libmariadbclient1810.1.20-3
ii  libmariadbd18 10.1.20-3
ii  libmtp9   1.1.12-1
ii  libmygpo-qt1  1.0.9-2
ii  libofa0   0.9.3-13
ii  libphonon44:4.9.0-4
ii  libplasma34:4.14.26-1
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.7+dfsg-11
ii  libqt4-network4:4.8.7+dfsg-11
ii  libqt4-opengl 4:4.8.7+dfsg-11
ii  libqt4-script 4:4.8.7+dfsg-11
ii  libqt4-sql4:4.8.7+dfsg-11
ii  libqt4-svg4:4.8.7+dfsg-11
ii  libqt4-xml4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libqtgui4 4:4.8.7+dfsg-11
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.3.4.dfsg-9.1
ii  libsolid4 4:4.14.26-1
ii  libstdc++66.2.1-5
ii  libthreadweaver4  4:4.14.26-1
ii  libx11-6  2:1.6.4-2
ii  libxml2   2.9.4+dfsg1-2.1
ii  phonon4:4.9.0-4

Versions of packages amarok recommends:
ii  clamz0.5-2+b1
ii  kio-audiocd  4:16.08.3-1

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.7+dfsg-11
pn  libqt4-sql-psql
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
pn  moodbar

Versions of packages amarok-common depends on:
pn  perl:any  

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-gstreamer [phonon-backend]  4:4.9.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: amarok
Source-Version: 2.8.0-8

We believe that the bug you reported is fixed in the latest version of
amarok, 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 

Bug#849849: marked as done (rabbitmq-server: CVE-2016-9877)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 23:02:55 +
with message-id 
and subject line Bug#849849: fixed in rabbitmq-server 3.3.5-1.1+deb8u1
has caused the Debian Bug report #849849,
regarding rabbitmq-server: CVE-2016-9877
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.)


-- 
849849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rabbitmq-server
Version: 3.6.5-1
Severity: grave
Tags: upstream security
Justification: user security hole

Hi,

the following vulnerability was published for rabbitmq-server.

CVE-2016-9877[0]:
| An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x
| before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before
| 1.6.12, and 1.7.x before 1.7.7. MQTT (MQ Telemetry Transport)
| connection authentication with a username/password pair succeeds if an
| existing username is provided but the password is omitted from the
| connection request. Connections that use TLS with a client-provided
| certificate are not affected.

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-9877
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9877
[1] https://github.com/rabbitmq/rabbitmq-mqtt/pull/98
[2] https://github.com/rabbitmq/rabbitmq-mqtt/issues/96

Please adjust the affected versions in the BTS as needed. I was only
able to check the vulnerability sourcewise for 3.6.5 in unstable,
older version have not been checked so far.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: rabbitmq-server
Source-Version: 3.3.5-1.1+deb8u1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated rabbitmq-server 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, 11 Jan 2017 02:17:32 +0100
Source: rabbitmq-server
Binary: rabbitmq-server
Architecture: source all
Version: 3.3.5-1.1+deb8u1
Distribution: jessie-security
Urgency: medium
Maintainer: RabbitMQ Team 
Changed-By: Thomas Goirand 
Description:
 rabbitmq-server - AMQP server written in Erlang
Closes: 849849
Changes:
 rabbitmq-server (3.3.5-1.1+deb8u1) jessie-security; urgency=medium
 .
   * CVE-2016-9877: apply backported upstream patch (Closes: #849849).
Checksums-Sha1:
 bb6ba8064f84de074a3a5b4e7fa0bad6e2b4083f 1893 
rabbitmq-server_3.3.5-1.1+deb8u1.dsc
 f945dd837ce637677b2d80b6fe14ef665233731d 3648221 
rabbitmq-server_3.3.5.orig.tar.gz
 01aa51850b772519e041c3ff49d774d25a9fb024 28801 
rabbitmq-server_3.3.5-1.1+deb8u1.diff.gz
 dbf7b2c3bf9e16ae6149ad4b9370985149b56d06 4118512 
rabbitmq-server_3.3.5-1.1+deb8u1_all.deb
Checksums-Sha256:
 1dd6224ca08aeb7f120ecd01725221fa181312b17e3e749bea36a6a4814cfc1a 1893 
rabbitmq-server_3.3.5-1.1+deb8u1.dsc
 7a6bf8af684b2087a1c534ffcd2db1b7c15b137a38bb9f00dfdf0227f69d70c2 3648221 
rabbitmq-server_3.3.5.orig.tar.gz
 4978240807984e2d03194168d954463f34395124a571c6ed58f2c1676928c078 28801 
rabbitmq-server_3.3.5-1.1+deb8u1.diff.gz
 2c8e448754603787195aa05b80c3c4149768310182cccfcb82b460db7bc7ad0f 4118512 
rabbitmq-server_3.3.5-1.1+deb8u1_all.deb
Files:
 dfbaf4ea247eafe3a6675527d01ffe6d 1893 net extra 
rabbitmq-server_3.3.5-1.1+deb8u1.dsc
 3bf0c4be1aaa6fdb483470aba14a6c81 3648221 net extra 
rabbitmq-server_3.3.5.orig.tar.gz
 f4e9b1687b8ae8a55253415ef1a70083 28801 net extra 
rabbitmq-server_3.3.5-1.1+deb8u1.diff.gz
 4f60376adf694ace8772f2eefe0b21bc 4118512 net extra 
rabbitmq-server_3.3.5-1.1+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYdYx9AAoJENQWrRWsa0P+yd4QAJwqQZflz4+nyn+Yx2l6jBSM
ZA1aOYia0ud06WWgMHDvRSLGDGSSd9fyRD5Nquj6dxtqjD3QDey4f8c4Y+GPvSZR
SQatrYrpojEHsCJCfXdis+YZIy8WvfzgutFlGYA7ui/QmU5hJv9H8PjmcT1U+1Nj

Bug#851372: [pkg-go] Bug#851372: prometheus-alertmanager FTBFS on mipsel and mips64el: test failures

[Martín Ferrari]

Adrian,

On 14/01/17 10:17, Adrian Bunk wrote:
> Source: prometheus-alertmanager
> Version: 0.5.1+ds-5
> Severity: serious
> 
> prometheus-alertmanager FTBFS on mipsel and mips64el
> (but not on the big endian mips):

Were you able to reproduce these failures?

I saw the buildds are failing, but I can't reproduce this in the porterbox.

-- 
Martín Ferrari (Tincho)

Processed: tagging 849326

[Debian Bug Tracking System]

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

> tags 849326 + pending
Bug #849326 [amarok] [amarok] Collection is disabled due to failing MySQL 
operation (errmsg.sys) at startup
Bug #850561 [amarok] amarok: 'errmsg.sys' had only 969 error messages
Bug #850900 [amarok] amarok: 6GREPME MySQLe query failed! (2000)
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Hilmar Preuße]

On 13.01.2017 20:28, Adrian Bunk wrote:
> On Thu, Sep 22, 2016 at 01:19:07PM +0200, Hilmar Preuße wrote:

Hi,

>> I assume that it has been fixed in [1], Further I suspect(!) that the fix is
>> already in our git repository. I've build packages based on our git[2] for
>> i386. Would you be so kind to test them?
>>
>> If you need other arches (e.g. amd64) please call back.
> 
> Has there been any feedback regarding whether this might already be fixed?
> 
> Currently this bug would prevent that proftpd-mod-clamav could be in 
> stretch.
> 
We don't have the fix for that in our git, but version 0.14 fixes the
problem
(as described by submitters). We have to import the latest version of the
module from upstream.

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

Bug#808654: Bug #808654 closed accidentally (it seems)

[Piotr Ożarowski]

> Hello Piotr. For reasons I still don't understand, your commands
> above made the bug to be closed.

the bug was actually not in fedmsg but in moksha.hub and I fixed it in 1.4.1-2 
(hence different source package/version that was closing bug).

I just checked (build logs you pointed me to are really old, before my
fix) and this package still FTBFS but for a completely different reason
(I guess it's OK to reopen this one as the final result is the same - it
doesn't build)

Bug#850147: marked as done (mysql-defaults: switch to mariadb-10.1)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 22:04:49 +
with message-id 
and subject line Bug#850147: fixed in mysql-defaults 1.0.2
has caused the Debian Bug report #850147,
regarding mysql-defaults: switch to mariadb-10.1
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.)


-- 
850147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.0
Version: 10.0.28-2
Severity: serious

Hi,

the remaining bits needed for the transition from mariadb-10.0 to
mariadb-10.1 are updates to the dependencies in mysql-defaults
(and this RC bug to get 10.0 removed at some point).


Andreas
--- End Message ---
--- Begin Message ---
Source: mysql-defaults
Source-Version: 1.0.2

We believe that the bug you reported is fixed in the latest version of
mysql-defaults, 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.
Otto Kekäläinen  (supplier of updated mysql-defaults 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: Sun, 15 Jan 2017 21:46:13 +0200
Source: mysql-defaults
Binary: mysql-common default-mysql-client-core default-mysql-client 
default-mysql-server-core default-mysql-server default-libmysqlclient-dev
Architecture: source amd64 all
Version: 1.0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 default-libmysqlclient-dev - MySQL database development files (metapackage)
 default-mysql-client - MySQL database client binaries (metapackage)
 default-mysql-client-core - MySQL database core client binaries (metapackage)
 default-mysql-server - MySQL database server binaries and system database 
setup (metapac
 default-mysql-server-core - MySQL database server binaries (metapackage)
 mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf
Closes: 844048 850147
Changes:
 mysql-defaults (1.0.2) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * Do not install alternatives pointing to conffiles that were removed by the
 local admin (Closes: #844048)
 .
   [ Otto Kekäläinen ]
   * Update the versioned dependencies from MariaDB 10.0 to 10.1 now when
 MariaDB 10.1 has entered Debian unstable and testing (Closes: #850147)
Checksums-Sha1:
 facbefeb1fb887bd9ef1dae76fa0cca1985dcf80 2171 mysql-defaults_1.0.2.dsc
 7139012b20300775632d8b748c0ad3668ecded61 5424 mysql-defaults_1.0.2.tar.xz
 32206a8c21a2bb8bfde03b3f56c952711d5807d3 3272 
default-libmysqlclient-dev_1.0.2_amd64.deb
 6fceed63b1544b1c5c6259b2137c0b92bd9b525f 3046 
default-mysql-client-core_1.0.2_all.deb
 2e9dbaf70f989cbd421a5888e41498b1ff90b426 3050 
default-mysql-client_1.0.2_all.deb
 fc21d32bb72863f0e7d2c34b5c1a7afeeae50a7e 3062 
default-mysql-server-core_1.0.2_all.deb
 1e9102ee2e01bdb0bd241c58397b6757edd01883 3048 
default-mysql-server_1.0.2_all.deb
 c67dde951adfb818fb459614b7bb73be43b7d120 5608 mysql-common_5.8+1.0.2_all.deb
 c5cd5b82869050f00369b85bd567a22be416f150 5976 
mysql-defaults_1.0.2_amd64.buildinfo
Checksums-Sha256:
 30859f6b6f589644624b04da33ab86f978df2a37ebdf09da63b8076f664ca189 2171 
mysql-defaults_1.0.2.dsc
 cf5597fbb134f99222d61101d0a7115bc3cc63476f6577d840600727a7b4a38c 5424 
mysql-defaults_1.0.2.tar.xz
 e72231b4df380cfda6c6259c9695e34ea99d75ee44cf21315fa1901de1b67244 3272 
default-libmysqlclient-dev_1.0.2_amd64.deb
 4fcad7f1095eaded57491a2743bce97c7851590aeda8ebf82009191fb6264a07 3046 
default-mysql-client-core_1.0.2_all.deb
 163f8c49ee3c87aa9c4e65a33d127436a279072a2fc96d55b6cfea09482e8185 3050 
default-mysql-client_1.0.2_all.deb
 d5f27ada120a9878abee0d851597602836f24abc6b8a0e87873ca3c231f969dc 3062 
default-mysql-server-core_1.0.2_all.deb
 0f3de40078e20e30fe54de367dc0a4096a22677d7c4362f64789e3d201bac0f9 3048 
default-mysql-server_1.0.2_all.deb
 c2ad585279140f12768056f9b28e9247a3d9d30154f158f104f7cb3000929909 5608 
mysql-common_5.8+1.0.2_all.deb
 5219f782f90cf4a40ba6161482137d3e4d5fc78b4eb1ba508f46aff9c8c530f0 5976 

Bug#851384: Fixed upstream

[Thomas Klute]

This is a bug in the program which generates the OCSP database used in
the failed test. I believe I have fixed this issue upstream in version
0.8.2. A build in a qemubuilder mips environment produced a correct test
database.

Bug#851518: cinnamon won't start

[Carsten Kosthorst]

Package: cinnamon
Version: 3.2.7-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

on startup, cinnamon enters a loop, trying to start over and over again.

When booting in rescue mode, I can start X via xinit. Trying to start cinnamon 
via the "cinnamon" command results in an error message (see attachment).

Carsten

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

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

Versions of packages cinnamon depends on:
ii  caribou  0.4.21-1
ii  cinnamon-common  3.2.7-1
ii  cinnamon-control-center  3.2.1-3
ii  cinnamon-desktop-data3.2.4-3
ii  cinnamon-screensaver 3.2.13-1
ii  cinnamon-session 3.2.0-4
ii  cinnamon-settings-daemon 3.2.1-3
ii  cjs  3.2.0-3
ii  cups-pk-helper   0.2.6-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gir1.2-accountsservice-1.0   0.6.43-1
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-clutter-1.0   1.26.0+dfsg-2
ii  gir1.2-cmenu-3.0 3.2.0-3
ii  gir1.2-cogl-1.0  1.22.2-2
ii  gir1.2-cvc-1.0   3.2.4-3
ii  gir1.2-gdkpixbuf-2.0 2.36.2-1
ii  gir1.2-gkbd-3.0  3.22.0.1-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.2-1
ii  gir1.2-gtk-3.0   3.22.5-1
ii  gir1.2-gtkclutter-1.01.8.2-1
ii  gir1.2-javascriptcoregtk-3.0 2.4.11-3
ii  gir1.2-keybinder-3.0 0.3.1-1
ii  gir1.2-meta-muffin-0.0   3.2.1-2
ii  gir1.2-networkmanager-1.01.4.4-1
ii  gir1.2-notify-0.70.7.7-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  gir1.2-polkit-1.00.105-17
ii  gir1.2-soup-2.4  2.56.0-2
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gir1.2-xapp-1.0  1.0.2-1
ii  gkbd-capplet 3.22.0.1-1
ii  gnome-backgrounds3.22.1-1
ii  gnome-themes-standard3.22.2-1
ii  gsettings-desktop-schemas3.22.0-1
ii  iso-flags-png-320x2401.0.1-1
ii  libatk-bridge2.0-0   2.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-8
ii  libcairo21.14.8-1
ii  libcinnamon-menu-3-0 3.2.0-3
ii  libcjs0  3.2.0-3
ii  libclutter-1.0-0 1.26.0+dfsg-2
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libcroco30.6.11-2
ii  libgdk-pixbuf2.0-0   2.36.2-1
ii  libgirepository-1.0-11.50.0-1
ii  libgl1-mesa-glx [libgl1] 13.0.2-3
ii  libglib2.0-0 2.50.2-2
ii  libglib2.0-bin   2.50.2-2
ii  libgstreamer1.0-01.10.2-1
ii  libgtk-3-0   3.22.5-1
ii  libjs-jquery 3.1.1-2
ii  libmozjs-24-024.2.0-5
ii  libmuffin0   3.2.1-2
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libstartup-notification0 0.12-4
ii  libx11-6 2:1.6.4-2
ii  libxfixes3   1:5.0.3-1
ii  libxml2  2.9.4+dfsg1-2.1
ii  mesa-utils   8.3.0-3
ii  muffin   3.2.1-2
ii  nemo 3.2.2-3
ii  policykit-1-gnome0.105-5
ii  python   2.7.13-1
ii  python-dbus  1.2.4-1
ii  python-gi-cairo  3.22.0-2
ii  python-imaging   3.4.2-1
ii  python-lxml  3.6.4-1
ii  python-pam   

Bug#850190: marked as done (dbc: db-dump must use root credentials when needed)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 21:37:32 +
with message-id 
and subject line Bug#850190: fixed in dbconfig-common 2.0.8
has caused the Debian Bug report #850190,
regarding dbc: db-dump must use root credentials when needed
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.)


-- 
850190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tango-db
Version: 9.2.5~rc1+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

  Setting up tango-db (9.2.5~rc1+dfsg1-2) ...
  Installing new version of config file /etc/init.d/tango-db ...
  Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
  dbconfig-common: writing config to /etc/dbconfig-common/tango-db.conf
  Replacing config file /etc/dbconfig-common/tango-db.conf with new version
  creating database backup in 
/var/cache/dbconfig-common/backups/tango-db_8.1.2c+dfsg-5.2016-12-14-10.08.39.
  error encountered backing up the old database:
  mysqldump: tango has insufficent privileges to SHOW CREATE PROCEDURE 
`class_att_prop`!
  dbconfig-common: tango-db configure: aborted.
  dbconfig-common: flushing administrative password
  dpkg: error processing package tango-db (--configure):
   subprocess installed post-installation script returned error exit status 1

In jessie, tango-db used mysql-server-5.5 (via mysql-server).
The upgrade of tango-db was performed after mysql-server had been upgraded
to mariadb-server-10.0 (via default-mysql-server) and was started again.


cheers,

Andreas


tango-db_9.2.5~rc1+dfsg1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dbconfig-common
Source-Version: 2.0.8

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 14 Jan 2017 08:19:23 +0100
Source: dbconfig-common
Binary: dbconfig-common dbconfig-mysql dbconfig-pgsql dbconfig-sqlite 
dbconfig-sqlite3 dbconfig-no-thanks
Architecture: source
Version: 2.0.8
Distribution: unstable
Urgency: medium
Maintainer: Paul Gevers 
Changed-By: Paul Gevers 
Description:
 dbconfig-common - framework that helps packages to manage databases
 dbconfig-mysql - dbconfig-common MySQL/MariaDB support
 dbconfig-no-thanks - dbconfig-common bypass
 dbconfig-pgsql - dbconfig-common PostgreSQL support
 dbconfig-sqlite - dbconfig-common SQLite support
 dbconfig-sqlite3 - dbconfig-common SQLite3 support
Closes: 849049 849112 849190 849274 850044 850190
Changes:
 dbconfig-common (2.0.8) unstable; urgency=medium
 .
   * Update translations, thanks to:
 - Atila KOÇ (Closes: #849049)
 - Iñaki Larrañaga Murgoitio (Closes: #850044)
 - Javier Fernandez-Sanguino (Closes: #849112)
 - Julien Patriarca (Closes: #849190)
 - Miguel Figueiredo (Closes: #849274)
   * Improve reproducibility by forcing SOURCE_DATE_EPOCH in PostScript
 documentation
   * Ask for administrator credentials in case dumping a database as user
 doesn't work (Closes: #850190)
Checksums-Sha1:
 b9aad0ba0303b05fc5ead432d814374a06618b27 1888 dbconfig-common_2.0.8.dsc
 e63d7807f6e726328d9eca016dcf05336fd8b83a 217880 dbconfig-common_2.0.8.tar.xz
Checksums-Sha256:
 326a8ff8f7b5b3a03aa19a8ba5609b02ceb8e9b5491e89b2bd01c2f5071c785f 1888 
dbconfig-common_2.0.8.dsc
 2d054273e6b55e25cdbf3723dad47c87b9a783e77b4f5625a502f2bdabfc766a 217880 
dbconfig-common_2.0.8.tar.xz
Files:
 0dfeb07f351b8a743cebfd278e2186d1 1888 admin optional dbconfig-common_2.0.8.dsc
 993af6afdf48f866bf9198eb0104288a 217880 admin optional 
dbconfig-common_2.0.8.tar.xz

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

[Lincoln Stein]

Hi,

The bug in the memory adaptor that Scott found turns out to have been from
using the old perl 1.6.9 installed by the Debian package. Updating to 1.7.1
(1.007001) fixes the problem.

I have merged all GBrowse changes into git version 2.56 and have made a
CPAN release. I think you can go ahead and package it.

Lincoln

On Thu, Jan 12, 2017 at 11:37 PM, Andreas Tille 
wrote:

> Thanks to you both.  I think the only question targeted directly at my
> was the "how much time question":  On Februrar 5 is full freeze.  You
> need to cut 10 days from this since a package has a 10 day migration
> time until it makes it from unstable to the release candidates in
> testing.  So this would make 2017-01-25 - but if there is a single (even
> unrelated to gbrowse) issue that might prevent the migration gbrowse is
> doomed.  So I'd recommend to get something out until beginning of next
> week.
>
> Kind regards
>
>   Andreas.
>
> On Thu, Jan 12, 2017 at 02:23:42PM -0500, Scott Cain wrote:
> > I made a few changes in a branch off that security-bug-fixes branch that
> > quieted several warning messages, though I still need to sort out at
> least
> > one problem (the memory adaptor doesn't seem to be reading fasta files,
> but
> > also doesn't emit a warning about a problem).  Lincoln, if you want to
> look
> > at this pull request, you could pull those changes into the security bug
> > fix branch:
> >
> > https://github.com/GMOD/GBrowse/pull/59
> >
> > Scott
> >
> >
> > On Thu, Jan 12, 2017 at 1:57 PM, Lincoln Stein 
> > wrote:
> >
> > > Hi Andreas,
> > >
> > > I was able to remove the vast majority of the warnings and other
> > > incompatibility issues, but need to do more testing to identify areas
> of
> > > the code that were not covered. How much time do I have? If you want
> to go
> > > with a fully functional version that may issue warnings when the user
> takes
> > > certain rare actions, it is the "security-bug-fixes" branch at
> > > https://github.com/GMOD/GBrowse
> > >
> > > Lincoln
> > >
> > > On Thu, Jan 12, 2017 at 1:39 PM, Andreas Tille 
> wrote:
> > >
> > >> Hi Lincoln,
> > >>
> > >> On Wed, Dec 21, 2016 at 06:25:46PM -0500, Lincoln Stein wrote:
> > >> > I am devoting several days over the Christmas holidays to fixing the
> > >> > various outstanding bugs in gbrowse. Stay tuned!
> > >>
> > >> Did you managed to managed to work on this?  If not we probably can
> not
> > >> include gbrowse in the next Debian stable release which would be a
> > >> shame.
> > >>
> > >> 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 <(416)%20673-8514>
> > > Mobile: 416-817-8240 <(416)%20817-8240>
> > > Email: lincoln.st...@gmail.com
> > > Toll-free: 1-866-678-6427 <(866)%20678-6427>
> > > Twitter: @OICR_news
> > >
> > > *Executive Assistant*
> > > *Frances Dirnbeck*
> > > Tel: 647-259-4253 <(647)%20259-4253>
> > > Email:frances.dirnb...@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.
> > >
> >
> >
> >
> > --
> > 
> > Scott Cain, Ph. D.   scott at scottcain
> dot
> > net
> > GMOD Coordinator (http://gmod.org/) 216-392-3087
> > Ontario Institute for Cancer Research
>
> --
> 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: 

Bug#818875: konqueror: green SSL checkbox despite expired server certificate

[Didier 'OdyX' Raboud]

Le lundi, 21 mars 2016, 11.03:13 h CET Thorsten Glaser a écrit :
> Package: konqueror
> Version: 4:15.08.3-1
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> See attached screenshot – konqueror does not error out when the
> certificate is expired and even shows a green checkbox. (I may
> or may not have ACK’d the certificate in an earlier session, I
> don’t know right now, but showing a green checkbox is still
> wrong.)

https://expired.identrustssl.com/ is an online example to test that use-case, 
which I can reproduce.

konqueror is RC-buggy in stretch because of that (IMHO rightful) bug. It is 
also plagued by other bugs, I wonder if konqueror should really be shipped in 
stretch. How feasible is it to remove it ?

-- 
OdyX

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

Processed: Bug #808654 closed accidentally (it seems)

[Debian Bug Tracking System]

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

> found 808654 0.9.3-2
Bug #808654 {Done: Piotr Ożarowski } [src:fedmsg] fedmsg: 
FTBFS offline: Download error on https://pypi.python.org/simple/Twisted_Core/
Bug #827738 {Done: Piotr Ożarowski } [src:fedmsg] fedmsg: 
Package unusable in sid (pkg_resources.DistributionNotFound: The 'Twisted_Core')
Did not alter found versions and reopened.
Did not alter found versions and reopened.
> thanks
Stopping processing here.

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

Bug#808654: Bug #808654 closed accidentally (it seems)

[Santiago Vila]

found 808654 0.9.3-2
thanks

On Fri, 13 Jan 2017, Piotr Ożarowski wrote:

> reassign 827738 src:fedmsg
> forcemerge 827738 808654
> thanks

Hello Piotr. For reasons I still don't understand, your commands
above made the bug to be closed.

But I can still reproduce it in version 0.9.3-2, and it also
fails to build here:

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

Thanks.

Bug#850190: [/sid] When dumping database fails as_user, try as dbadmin

[Paul Gevers]

tag 850190 pending
thanks

Date: Sat Jan 14 08:05:03 2017 +0100
Author: Paul Gevers 
Commit ID: 3d0c5ec010a87dc186b89591c7d04b536ccbf23f
Commit URL: 
https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git;a=commitdiff;h=3d0c5ec010a87dc186b89591c7d04b536ccbf23f
Patch URL: 
https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git;a=commitdiff_plain;h=3d0c5ec010a87dc186b89591c7d04b536ccbf23f

When dumping database fails as_user, try as dbadmin

Closes: #850190
  

Processed: [/sid] When dumping database fails as_user, try as dbadmin

[Debian Bug Tracking System]

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

> tag 850190 pending
Bug #850190 [dbconfig-common] dbc: db-dump must use root credentials when needed
Ignoring request to alter tags of bug #850190 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Mark as forwarded and fixed upstream

[Debian Bug Tracking System]

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

> tags 844145 fixed-upstream
Bug #844145 [src:elektra] elektra: FTBFS: kdberrors.h:489:0: error: invalid 
storage class for function 'elektraSetErrorf8'
Added tag(s) fixed-upstream.
> forwarded 844145 https://github.com/ElektraInitiative/libelektra/issues/1247
Bug #844145 [src:elektra] elektra: FTBFS: kdberrors.h:489:0: error: invalid 
storage class for function 'elektraSetErrorf8'
Set Bug forwarded-to-address to 
'https://github.com/ElektraInitiative/libelektra/issues/1247'.
> tags 846200 fixed-upstream
Bug #846200 [src:elektra] FTBFS: test_kdb failing: libelektra-resolver.so: 
cannot open shared object file: No such file or directory
Added tag(s) fixed-upstream.
> forwarded 846200 https://github.com/ElektraInitiative/libelektra/issues/1247
Bug #846200 [src:elektra] FTBFS: test_kdb failing: libelektra-resolver.so: 
cannot open shared object file: No such file or directory
Set Bug forwarded-to-address to 
'https://github.com/ElektraInitiative/libelektra/issues/1247'.
> thanks
Stopping processing here.

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

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

[Paul Gevers]

Hi Picca,

On 01/14/17 11:12, PICCA Frederic-Emmanuel wrote:
> Hello Paul
> 
>> I really hope I can upload this weekend. I have code that I believe does
>> what I want. I am in the process of testing it.
> 
> thanks a lot.

I'll upload in the next hour.

>>  What I meant,
>> instead of the mysql code that runs as user, run a script for the
>> upgrade (they are run with database administrator credentials) and in
>> that script do two things: call the DROP PROCEDURES... and then use the
>> user credentials to run the normal script.
> 
>> Apart from this repair, do you see more use cases? The problem is that
>> you would need nearly all the logic that is now in dbc_go for this to
>> work. What I am considering is if I could guarantee the order of
>> script/user mysql/admin mysql (or the last two reversed). I guess that
>> if I would guarantee the script to always come first, it would be easier
>> to solve the tango-db issue at hand (which was originally created by
>>  dbconfig-common).
> 
> 
> ok, so If I understand correctl.
> 
> In my tango-db postinst, I will add a script 
> 
> /usr/share/dbconfig-common/scripts/PACKAGE/upgrade/DBTYPE/VERSION
> 
> which does the fix (drop all the procedures)

That is the idea.

> then 
> 
> dbconfig-common will run my normal
> 
>  /usr/share/dbconfig-common/data/PACKAGE/upgrade/DBTYPE/VERSION
> 
> script.
> 
> right ?

Officially, no, because the documentation says: "If files exist in both
data and scripts, they will both be executed in an unspecified order."
However, the current behavior of dbconfig-common is to first run the
script and then run the admin code and then run the user code. So you
should be fine (but please test) and I'll make sure this behavior
doesn't change in stretch.

> I have more than one version of 'normal' upgrade scripts,
> 
> 7.2.6
> 8.0.5
> 8.2.0
> 9.2.5
> 
> so I need to add the same amount of fix scripts in order to be sure
> that the database is fixed from the first upgrade.
> 7.2.6 -> 8.0.5 etc...

I hadn't realized this, but yes. However, as Debian doesn't support
upgrading from (stable - 2) to stable, you may consider to only add the
fix to the update from the current stable version to the first in
stretch version, i.e. (8.1.2 to) 9.1.0. I don't think it is worth the
reduction thought.

> I just need to be sure that the database dump is done after the fix
> except if you run the dump at dbadmin, but In that case I would  have
> a dump with the non fixed database.

Once my fix is in (as said, I expect to upload shortly), I don't think
it is worth it to worry about the unfixed database. The database dump
will be retried with dbadmin credentials when doing it with dbuser
credentials fails.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

[Willi Mann]

Hi Klaus,

Am 2017-01-15 um 17:43 schrieb Klaus Ethgen:
> Hi Willi,
> 
> Am Sa den 14. Jan 2017 um 16:43 schrieb Willi Mann:
>> in order to come closer to a fix for this issue, I propose the following
>> two patches:
> 
> 
>> 0001-Add-outputencoding-parameter.patch
> 
>> This patch allows to configure the value for the charset in the
>> Content-Type line in mail output. This should address Klaus Ethgen's
>> original concern.
> 
> Well, partly. It will, in fact, let me configure it the way, that it
> solves my issue.
> 
> However, It does not fix the issue itself as it does not ensure that the
> output in mail is that charset. As I mentioned before, this is exactly
> the issue. The mail could be easily in UTF-8. But then there has to be
> logic to keep sure that the mail is in that charset. Without, you could
> still end with logical incorrect mails that are (partly) in different
> charsets that is illegal for UTF-8.

I understand that the illegal UTF-8 is bad. But I have to admit that I'm
not yet sure why it is bad in terms of security, especially since we are
talking about mail - and anyone could send you an e-mail with illegal
UTF-8 sequences.

>> Since most people use UTF-8, I left the default at UTF-8.
> 
> No objection about that. But you cannot be sure that log stuff is in the
> same charset.

Yeah, that I'm aware of.

>> 0002-Use-pager-on-stdout-output-to-terminal.patch
> [...]
>> Let me know what you think about these patches.
> 
> Patches looks good for me for fixing the bug partly. Nevertheless I
> would expect some use of iconv for really ensure the choosed charset.
> Maybe even encguess can come to use for guessing the input.

Does anybody have a good idea on how to implement this? Concerning the
second part (guessing the input encoding), I'm not really sure at
what point logwatch should try to guess and assume a particular charset.
Especially for the first part, does anybody know some example code?
Maybe some other project that had to solve the same issue in Perl?

Willi

Bug#850216: [debian-mysql] Bug#850216: Bug#850216: Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

[Otto Kekäläinen]

Hello!

2017-01-13 13:18 GMT+02:00 Robie Basak :
> So I think the configure-symlinks code needs to move from mariadb-common
> to mariadb-server-10.1 in addition.

The MariaDB client programs might also have MariaDB specific
configuration lines, which according to this new config scheme should
be placed in /etc/mysql/mariadb.cnf.d/, and for them to be read,
mariadb-common must control the configure-symlinks.

Maybe we should mark both the client and server packages to conflict
each other, and for mariadb-common to conflict on mysql-client and
mysql-server?



-- 
Otto Kekäläinen
https://keybase.io/ottok
Seravo Oy and MariaDB Foundation

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 851505 src:systemd
Bug #851505 [xvfb] Xvfb segfaults on mips64el
Bug reassigned from package 'xvfb' to 'src:systemd'.
No longer marked as found in versions xorg-server/2:1.19.0-3.
Ignoring request to alter fixed versions of bug #851505 to the same values 
previously set
> forcemerge 851412 851505
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Severity set to 'serious' from 'grave'
Added indication that 851505 affects pdns,pdns-recursor
Marked as found in versions systemd/232-10.
Merged 851412 851505
> affects 851412 xvfb src:octave
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Added indication that 851412 affects xvfb and src:octave
Added indication that 851505 affects xvfb and src:octave
> thanks
Stopping processing here.

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

Processed: found 851380 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 851380 8:6.7.7.10-4
Bug #851380 {Done: Bastien ROUCARIÈS } 
[imagemagick] [imagemagick]  memory leak in caption and label handling
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Bug#851505: Xvfb segfaults on mips64el

[Sébastien Villemot]

Package: xvfb
Version: 2:1.19.0-3
Severity: grave

Xvfb segfaults on mips64el:

(sid_mips64el-dchroot)sebastien@eller:~$ Xvfb
Segmentation fault

As a consequence, octave FTBFS on mips64el (it uses xvfb-run for its testsuite):

  
https://buildd.debian.org/status/fetch.php?pkg=octave=mips64el=4.0.3-3=1484413473

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 848739 https://github.com/rocky/zshdb/issues/9
Bug #848739 [src:zshdb] zshdb: FTBFS: configure: error: You might want to retry 
with another zsh using the --with-zsh option.
Set Bug forwarded-to-address to 'https://github.com/rocky/zshdb/issues/9'.
> kthxbye
Stopping processing here.

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

Bug#851412: #851412: libsystemd segfaults on mips64el

[Christian Hofstaedtler]

* Michael Biebl  [170115 19:09]:
> Am 15.01.2017 um 14:12 schrieb Christian Hofstaedtler:
> > PS: libsystemd does not appear to have a -dbgsym package.
> > 
> 
> It does, at least on amd64
> 
> libsystemd0-dbgsym:
>   Installed: (none)
>   Candidate: 232-10
>   Version table:
>  232-10 500
> 500 http://debug.mirrors.debian.org/debian-debug
> unstable-debug/main amd64 Packages
> 
> Did you miss the "0" ?

No; appears to be some other, unidentified issue with the mips64el
schroot on eller.d.o.

Best,
  -ch

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#822470: marked as done (qemu: FTBFS: error: redefinition of 'struct fsxattr')

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 20:12:03 +0200
with message-id <20170115181203.hre34x37wsalbrnu@localhost>
and subject line 4.9.0 builds
has caused the Debian Bug report #822369,
regarding qemu: FTBFS: error: redefinition of 'struct fsxattr'
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.)


-- 
822369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu
Version: 1:2.5+dfsg-5
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> cc -I/<>/qemu-2.5+dfsg/tcg -I/<>/qemu-2.5+dfsg/tcg/i386 
> -I/<>/qemu-2.5+dfsg/linux-headers 
> -I/<>/qemu-2.5+dfsg/qemu-build/linux-headers -I. 
> -I/<>/qemu-2.5+dfsg -I/<>/qemu-2.5+dfsg/include 
> -I/<>/qemu-2.5+dfsg/block -Iblock -I/usr/include/pixman-1  
> -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes 
> -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes 
> -fno-strict-aliasing -fno-common  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
>  -DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body 
> -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self 
> -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition 
> -Wtype-limits -fstack-protector-strong  -I/usr/include/p11-kit-1
> -I/usr/incl
> ude/libpng16 -I/usr/include/spice-server -I/usr/include/spice-1 
> -I/usr/include/cacard -I/usr/include/libusb-1.0  
> -I/<>/qemu-2.5+dfsg/tests -MMD -MP -MT block/iscsi.o -MF 
> block/iscsi.d -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g  
> -fPIC -DBUILD_DSO  -c -o block/iscsi.o 
> /<>/qemu-2.5+dfsg/block/iscsi.c
> In file included from /usr/include/xfs/xfs.h:58:0,
>  from /<>/qemu-2.5+dfsg/block/raw-posix.c:97:
> /usr/include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
>  struct fsxattr {
> ^
> In file included from /<>/qemu-2.5+dfsg/block/raw-posix.c:60:0:
> /usr/include/linux/fs.h:155:8: note: originally defined here
>  struct fsxattr {
> ^
> cc -I/<>/qemu-2.5+dfsg/tcg -I/<>/qemu-2.5+dfsg/tcg/i386 
> -I/<>/qemu-2.5+dfsg/linux-headers 
> -I/<>/qemu-2.5+dfsg/qemu-build/linux-headers -I. 
> -I/<>/qemu-2.5+dfsg -I/<>/qemu-2.5+dfsg/include 
> -I/<>/qemu-2.5+dfsg/block -Iblock -I/usr/include/pixman-1  
> -DHAS_LIBSSH2_SFTP_FSYNC -fPIE -DPIE -m64 -D_GNU_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes 
> -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes 
> -fno-strict-aliasing -fno-common  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -DCONFIG_QEMU_DATAPATH='"/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu"'
>  -DVENDOR_DEBIAN -Wendif-labels -Wmissing-include-dirs -Wempty-body 
> -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self 
> -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition 
> -Wtype-limits -fstack-protector-strong  -I/usr/include/p11-kit-1
> -I/usr/incl
> ude/libpng16 -I/usr/include/spice-server -I/usr/include/spice-1 
> -I/usr/include/cacard -I/usr/include/libusb-1.0  
> -I/<>/qemu-2.5+dfsg/tests -MMD -MP -MT block/curl.o -MF 
> block/curl.d -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g  
> -fPIC -DBUILD_DSO  -c -o block/curl.o /<>/qemu-2.5+dfsg/block/curl.c
> /<>/qemu-2.5+dfsg/rules.mak:57: recipe for target 
> 'block/raw-posix.o' failed
> make[1]: *** [block/raw-posix.o] Error 1

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

Version 4.9.0 built successfully on the autobuilders:
  https://buildd.debian.org/status/package.php?p=xfsprogs

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#822369: marked as done (xfsprogs: FTBFS: error: redefinition of 'struct fsxattr')

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 20:12:03 +0200
with message-id <20170115181203.hre34x37wsalbrnu@localhost>
and subject line 4.9.0 builds
has caused the Debian Bug report #822369,
regarding xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
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.)


-- 
822369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfsprogs
Version: 4.3.0+nmu1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> [CC] fiemap.o
> In file included from ../include/xfs.h:58:0,
>  from io.h:19,
>  from fiemap.c:24:
> ../include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
>  struct fsxattr {
> ^
> In file included from fiemap.c:22:0:
> /usr/include/linux/fs.h:155:8: note: originally defined here
>  struct fsxattr {
> ^
> ../include/buildrules:59: recipe for target 'fiemap.o' failed
> make[3]: *** [fiemap.o] Error 1
> include/buildrules:35: recipe for target 'io' failed

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

Version 4.9.0 built successfully on the autobuilders:
  https://buildd.debian.org/status/package.php?p=xfsprogs

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#851412: #851412: libsystemd segfaults on mips64el

[Michael Biebl]

Am 15.01.2017 um 14:12 schrieb Christian Hofstaedtler:

> 
> PS: libsystemd does not appear to have a -dbgsym package.
> 

It does, at least on amd64

libsystemd0-dbgsym:
  Installed: (none)
  Candidate: 232-10
  Version table:
 232-10 500
500 http://debug.mirrors.debian.org/debian-debug
unstable-debug/main amd64 Packages

Did you miss the "0" ?

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



signature.asc
Description: OpenPGP digital signature

Processed: Proper version tracking

[Debian Bug Tracking System]

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

> fixed 851002 0.9-14
Bug #851002 {Done: Alastair McKinstry } [src:ggcov] 
ggcov: FTBFS: Test failures
Marked as fixed in versions ggcov/0.9-14.
> thanks
Stopping processing here.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851377 [imagemagick] [imagemagick]  out of bound in psd file handling
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851377 [imagemagick] [imagemagick]  out of bound in psd file handling
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851377 [imagemagick] [imagemagick]  out of bound in psd file handling
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851377 [imagemagick] [imagemagick]  out of bound in psd file handling
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851381 [imagemagick] [imagemagick]  Crash - PushQuantumPixel - 
Heap-Buffer-Overflow (TIFF)
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851381 [imagemagick] [imagemagick]  Crash - PushQuantumPixel - 
Heap-Buffer-Overflow (TIFF)
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851381 [imagemagick] [imagemagick]  Crash - PushQuantumPixel - 
Heap-Buffer-Overflow (TIFF)
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851381 [imagemagick] [imagemagick]  Crash - PushQuantumPixel - 
Heap-Buffer-Overflow (TIFF)
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851382 [imagemagick] [imagemagick]  memory leak in MPC file handling
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851382 [imagemagick] [imagemagick]  memory leak in MPC file handling
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851382 [imagemagick] [imagemagick]  memory leak in MPC file handling
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851382 [imagemagick] [imagemagick]  memory leak in MPC file handling
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851383 [imagemagick] [imagemagick]  double free in profile
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851383 [imagemagick] [imagemagick]  double free in profile
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851383 [imagemagick] [imagemagick]  double free in profile
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851383 [imagemagick] [imagemagick]  double free in profile
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Processed: found in stable and unstable

[Debian Bug Tracking System]

Processing control commands:

> found -1 8:6.8.9.9-5+deb8u6
Bug #851374 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.8.9.9-5+deb8u6.
> found -1 8:6.8.9.9-5
Bug #851374 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.8.9.9-5.
> found -1 8:6.9.6.6+dfsg-1
Bug #851374 [imagemagick] [imagemagick] memory corruption heap overflow
Marked as found in versions imagemagick/8:6.9.6.6+dfsg-1.
> found -1  8:6.9.6.6+dfsg-2
Bug #851374 [imagemagick] [imagemagick] memory corruption heap overflow
There is no source info for the package 'imagemagick' at version 
'8:6.9.6.6+dfsg-2' with architecture ''
Unable to make a source version for version '8:6.9.6.6+dfsg-2'
Marked as found in versions 8:6.9.6.6+dfsg-2.

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

Bug#851374: found in stable and unstable

[Bastien ROUCARIÈS]

control: found -1 8:6.8.9.9-5+deb8u6
control: found -1 8:6.8.9.9-5
control: found -1 8:6.9.6.6+dfsg-1
control: found -1  8:6.9.6.6+dfsg-2

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

Bug#849401: restart silently fails

[Daniel Pocock]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 15/01/17 17:34, Francesco Poli wrote:
> On Sun, 15 Jan 2017 10:28:40 +0100 Daniel Pocock wrote:
> 
>> 
>> 
>> On 10/01/17 23:49, Christian Hofstaedtler wrote:
> [...]
>>> here are some test packages with a systemd service file:
>>> 
>>> https://people.debian.org/~zeha/apcupsd/
>>> 
>>> Please report back if those work for you and if the restart
>>> issue is fixed. Note that successful testing also needs to
>>> include a powerfail test really.
>>> 
>> 
>> 
>> I installed that and tested with this loop:
>> 
>> systemctl start apcupsd && while ps -C apcupsd ; do systemctl
>> stop apcupsd ; sleep 0 ; systemctl start apcupsd ; ps -C apcupsd
>> || echo FAILED ; done
>> 
>> 
>> For about 3 minutes, it appears to restart correctly every time.
>> 
>> I haven't done a full powerfail test so far.
> 
> Hello Daniel, thanks for your feedback.
> 
> I hope that Christian may soon finalize the NMU in order to have
> this bug fixed once and for all.
> 
> Christian, have you decided which strategy should be adopted for
> the ISCONFIGURED handling?
> 
> 

One other aspect of this issue remains: if apcupsd doesn't start for
any reason (whether it is because of a rapid restart or some other
fault), we need to verify that the init script or systemd realizes
that the process failed to start.  I think that for daemon processes,
systemd may be more capable of detecting the case where the daemon
fails after forking.

Regards,

Daniel
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYe61HAAoJEGxlgOd711bEbhoP/3It2UA8/TCmo5aT57Wdo2QL
Vd1lt56zMq/snw+OOkDcQCYPhOuAsk9Ijz2qtX3f1Ou4/CKSsQaz3WTXDY/xJzMu
7o6qCPM80EuI5/txig1+d2asalkzztRv9b5H/LkbQcSOHtxmP2sylnQpzc7QnauP
8FYXunVkieNicbs4zTvFkJYH7PxUqmM5rLgA5d2gJZiNi/FKf8px+l+0WVDFk9nh
gg4a1WpHVpm/mcABjXZRPicwa90oKw8dvxxJ/JiHo0BgdjwxjcLNr/wwSjdFjTAe
+BVuVERkgVthsFPQfSJQL56zwWg/WMHhYRkUpaaMGrsgigVrge2AixvWZU9zSVXO
gqui1dJLGQ7nRCEtdbUABOmpvH4+XZJZeqaq/spIJz9Y05nrTBFO9DRQpPu291+V
BdQNry9lqJJBxwln9XkXA9Dn2RLjaKm/FBq+hsQsUz3OCC4vigA+iPoVhzjRlGI+
Q971lP1wEKGQnT6ZRJax6cZFrOQFOQyfxShQh9BlKfPkt5oMzShkNEsXUf2z0arY
pf4K1vpMi8fODHs/angpxkxlHxMHt0FQ2OK5Gtl7++VMWt6x4cjgeWT6QvWOYMPE
t5nbiGGNEiJ0aLbBb0mxXgYLY7uEjzZfmCQQwM4OusITYBXTe/yv2KQpMJ0Nyrb1
0ZWeezgxYUVHJ4qYVXWJ
=j1i0
-END PGP SIGNATURE-

Processed: severity of 851471 is important

[Debian Bug Tracking System]

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

> severity 851471 important
Bug #851471 [src:linux] linux-image-4.8.0-2-686-pae: premature oom killer 
invocation running 4.8.15
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#846230: marked as done (policykit-1-gnome: Fails to start with warning: "Unable to determine the session we are in: No session for pid")

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 17:05:12 +
with message-id 
and subject line Bug#844785: fixed in systemd-shim 10-3~exp1
has caused the Debian Bug report #844785,
regarding policykit-1-gnome: Fails to start with warning: "Unable to determine 
the session we are in: No session for pid"
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.)


-- 
844785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: policykit-1-gnome
Version: 0.105-5
Severity: important

Dear Maintainer,

I use lightdm and Xfce.

The agent is not started on start
up, so many functions do not work, such as controlling network through
NetworkManager, mounting disks with Nano, running Gparted, powering off
or suspending through Xfce's log out panel and possibly others.

I tried starting polkit-gnome-authentication-agent-1 manually, but the
process closes/crashes immediately, reporting the following message:

(polkit-gnome-authentication-agent-1:7502): polkit-gnome-1-WARNING **:
Unable to determine the session we are in: No session for pid 7502

I read several threads on the internet describing similar issues, but
they none of them helped in solving the issue or identifying its cause.

This problem presented itself after a recent update. I think that the
package itself was not updated, however this is my best bet on where
to report this bug.

Please let me know if I should provide more information.

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

Kernel: Linux 4.8.0-1-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: sysvinit (via /sbin/init)

Versions of packages policykit-1-gnome depends on:
ii  libc6  2.24-7
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.2-2
ii  libgtk-3-0 3.22.4-1
ii  libpolkit-agent-1-00.105-17
ii  libpolkit-gobject-1-0  0.105-17
ii  policykit-10.105-17

policykit-1-gnome recommends no packages.

policykit-1-gnome suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd-shim
Source-Version: 10-3~exp1

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated 
systemd-shim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jan 2017 14:54:49 +
Source: systemd-shim
Binary: systemd-shim
Architecture: amd64 source
Version: 10-3~exp1
Distribution: experimental
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Ian Jackson 
Closes: 844785
Description: 
 systemd-shim - shim for systemd
Changes:
 systemd-shim (10-3~exp1) experimental; urgency=high
 .
   QA upload:
   * Install wrapper script to mount /sys/fs/cgroup/systemd.
 Fixes "not authorised" problem with various desktop services,
 when running with newer systemd.  Closes:#844785 in Debian.
 [Michael Biebl, Ian Jackson]
   * Add debian/.gitignore.
Checksums-Sha1: 
 f2f161885a3f8d0364083fb1905c9cc762aa09e9 1830 systemd-shim_10-3~exp1.dsc
 c2e4d0cf3bbf5d04eb7e28400047f0160b330b1c 7016 
systemd-shim_10-3~exp1.debian.tar.xz
 608cd4e0299cd573ab644113977fdc2b17dbb403 50694 
systemd-shim-dbgsym_10-3~exp1_amd64.deb
 c75dd2fb97cf3c9151e2ff65a24674e2c1459fd1 5576 
systemd-shim_10-3~exp1_amd64.buildinfo
 e67bc7b7c5d1736d7fd3964387ff03b4d20b280d 19470 systemd-shim_10-3~exp1_amd64.deb
Checksums-Sha256: 
 774ba3912a49cacd6e583b1d7a14dc9078b999d397b0fe9ac979c2e8805a6617 1830 
systemd-shim_10-3~exp1.dsc
 92f8e3658a23a6026b08d4b76934fb969e2c74ef73fe7453b52c009476bd391a 7016 
systemd-shim_10-3~exp1.debian.tar.xz
 78d8e61b869abec846ceb6f7ad2229405d13d18ea957ed41fe1a82005649f68b 50694 

Bug#844785: marked as done (systemd-shim not fully compatible with systemd 232)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 17:05:12 +
with message-id 
and subject line Bug#844785: fixed in systemd-shim 10-3~exp1
has caused the Debian Bug report #844785,
regarding systemd-shim not fully compatible with systemd 232
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.)


-- 
844785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-1

Since systemd 232, lightdm's menu entries to
shutdown/reboot/suspend/hibernate the system are grayed out.

Furthermore, GNOME polkit authentication agent fails to start (I use
openbox, with the agent normally started from
~/.config/openbox/autostart). When manually run in a terminal, it
immediately exits with the error message:

"polkit-gnome-1-WARNING **: Unable to determine the session we are in:
No session for pid ..."

Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
the problem (I also tried 232-1 and 232-2, but they didn't work either).

Sorry for the vague bug title (and the probably wrong binary package),
but it's the best I can do since I'm not at all familiar with the way
systemd/polkit/pam/lightdm/whatever interact with each other.

Also, I just spotted this bug today despite the fact that it was
introduced two weeks ago, because I rarely shutdown my sid box.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: systemd-shim
Source-Version: 10-3~exp1

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

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

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated 
systemd-shim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jan 2017 14:54:49 +
Source: systemd-shim
Binary: systemd-shim
Architecture: amd64 source
Version: 10-3~exp1
Distribution: experimental
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Ian Jackson 
Closes: 844785
Description: 
 systemd-shim - shim for systemd
Changes:
 systemd-shim (10-3~exp1) experimental; urgency=high
 .
   QA upload:
   * Install wrapper script to mount /sys/fs/cgroup/systemd.
 Fixes "not authorised" problem with various desktop services,
 when running with newer systemd.  Closes:#844785 in Debian.
 [Michael Biebl, Ian Jackson]
   * Add debian/.gitignore.
Checksums-Sha1: 
 f2f161885a3f8d0364083fb1905c9cc762aa09e9 1830 systemd-shim_10-3~exp1.dsc
 c2e4d0cf3bbf5d04eb7e28400047f0160b330b1c 7016 
systemd-shim_10-3~exp1.debian.tar.xz
 608cd4e0299cd573ab644113977fdc2b17dbb403 50694 
systemd-shim-dbgsym_10-3~exp1_amd64.deb
 c75dd2fb97cf3c9151e2ff65a24674e2c1459fd1 5576 
systemd-shim_10-3~exp1_amd64.buildinfo
 e67bc7b7c5d1736d7fd3964387ff03b4d20b280d 19470 systemd-shim_10-3~exp1_amd64.deb
Checksums-Sha256: 
 774ba3912a49cacd6e583b1d7a14dc9078b999d397b0fe9ac979c2e8805a6617 1830 
systemd-shim_10-3~exp1.dsc
 92f8e3658a23a6026b08d4b76934fb969e2c74ef73fe7453b52c009476bd391a 7016 
systemd-shim_10-3~exp1.debian.tar.xz
 78d8e61b869abec846ceb6f7ad2229405d13d18ea957ed41fe1a82005649f68b 50694 
systemd-shim-dbgsym_10-3~exp1_amd64.deb
 913cb5b08ca40654cc87281f6230865f9c8cac8c53b735a12c1fd89e22a3491e 5576 
systemd-shim_10-3~exp1_amd64.buildinfo
 4485c3e6aed156d4a156c2b9b3ccd79a34970d7161489b4b55b59b60d97f7210 19470 
systemd-shim_10-3~exp1_amd64.deb
Files: 
 8d1f243874bcad963d3c3311ac5c7c82 1830 admin extra systemd-shim_10-3~exp1.dsc
 ef7a6e9365636fc0643f31b9199b0ae2 7016 admin extra 
systemd-shim_10-3~exp1.debian.tar.xz
 6a0b960340eebda342f9540389c90234 50694 debug extra 
systemd-shim-dbgsym_10-3~exp1_amd64.deb
 071bc6603dcb3025538ce4b7e55efb79 5576 admin extra 
systemd-shim_10-3~exp1_amd64.buildinfo
 f9ae58ff7f67c59297d91530841bfc88 19470 admin extra 
systemd-shim_10-3~exp1_amd64.deb

-BEGIN PGP SIGNATURE-

Processed: Also add an affects

[Debian Bug Tracking System]

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

> affects 851263 vbetool
Bug #851263 [libx86-1] libx86-1: illegal instruction
Added indication that 851263 affects vbetool
> thanks
Stopping processing here.

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

Processed: Re: Bug#851263: vbetool: crashes by executing illegal hardware instruction

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libx86-1 1.1+ds1-10.1
Bug #851263 [vbetool] vbetool: crashes by executing illegal hardware instruction
Bug reassigned from package 'vbetool' to 'libx86-1'.
No longer marked as found in versions vbetool/1.1-4.
Ignoring request to alter fixed versions of bug #851263 to the same values 
previously set
Bug #851263 [libx86-1] vbetool: crashes by executing illegal hardware 
instruction
Marked as found in versions libx86/1.1+ds1-10.1.
> severity -1 serious
Bug #851263 [libx86-1] vbetool: crashes by executing illegal hardware 
instruction
Severity set to 'serious' from 'normal'
> retitle -1 libx86-1: illegal instruction
Bug #851263 [libx86-1] vbetool: crashes by executing illegal hardware 
instruction
Changed Bug title to 'libx86-1: illegal instruction' from 'vbetool: crashes by 
executing illegal hardware instruction'.

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

Bug#851498: g-s-d has an undocumented and unstable tmp-cleaner

[Ben Hutchings]

Control: severity -1 important
Control: retitle -1 g-s-d crashes due to FD leak in tmp-cleaner

After looking through the code, now I see this seems to be controlled
by a setting under Privacy that is *not* enabled by default.  I don't
recall enabling it, but presumably I did.

The FD leak is still an important bug, though.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get
out.



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

Processed: Re: g-s-d has an undocumented and unstable tmp-cleaner

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #851498 [gnome-settings-daemon] g-s-d has an undocumented and unstable 
tmp-cleaner
Severity set to 'important' from 'grave'
> retitle -1 g-s-d crashes due to FD leak in tmp-cleaner
Bug #851498 [gnome-settings-daemon] g-s-d has an undocumented and unstable 
tmp-cleaner
Changed Bug title to 'g-s-d crashes due to FD leak in tmp-cleaner' from 'g-s-d 
has an undocumented and unstable tmp-cleaner'.

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

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages]

[Ian Jackson]

Ian Jackson writes ("Re: "not authorised" doing various desktoppy things [and 1 
more messages]"):
> More news later today.

I have just uploaded systemd-shim 10-3~exp1 to experimental.  I seems
to fix the problem for me.  Depending on feedback, I will upload this
to sid in the next few days.

Thanks,
Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Willi,

Am Sa den 14. Jan 2017 um 16:43 schrieb Willi Mann:
> in order to come closer to a fix for this issue, I propose the following
> two patches:
> 
> 
> 0001-Add-outputencoding-parameter.patch
> 
> This patch allows to configure the value for the charset in the
> Content-Type line in mail output. This should address Klaus Ethgen's
> original concern.

Well, partly. It will, in fact, let me configure it the way, that it
solves my issue.

However, It does not fix the issue itself as it does not ensure that the
output in mail is that charset. As I mentioned before, this is exactly
the issue. The mail could be easily in UTF-8. But then there has to be
logic to keep sure that the mail is in that charset. Without, you could
still end with logical incorrect mails that are (partly) in different
charsets that is illegal for UTF-8.

> Since most people use UTF-8, I left the default at UTF-8.

No objection about that. But you cannot be sure that log stuff is in the
same charset.

> 0002-Use-pager-on-stdout-output-to-terminal.patch
[...]
> Let me know what you think about these patches.

Patches looks good for me for fixing the bug partly. Nevertheless I
would expect some use of iconv for really ensure the choosed charset.
Maybe even encguess can come to use for guessing the input.

Regards
   Klaus
- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlh7pqYACgkQpnwKsYAZ
9qzURAwAvO09xg/6VmP4PyI4jJd5lnULPJtbCcIsxypOut7fYuZATF6RrUfe1at1
GyTKhQ2aayFK1TIzwMifkD96fj3wbCV35WZm2LBAAiGkKBFs1ZasN+Zj1JkGuYiL
frFHBmO49TP5YKWWRCNGrg16mxfn6QdyIqKOpPqRJeNUhuhWE05vhecjG+MzJZ9C
d25JO12IooHk3np7BzXHmLn4HtJawHoKHdob6WlnyIhg2rJG8WgE44zrNYlYrO5T
IbRXuiLRTGmuxuNfPqEuwLohkFbP/tPGhpgeUPV6G26THhPy0aZBENKzPoLvwJ8/
1/RxpIe++gr5uil9xS/0zjFYZwn+TrD3rkobuIArkpmEH17v733tP9922t1YWLTU
bxRtKWg6sGQMY0QsFC+0+GATJD5FHQOHQQ+fHByU+kvLHYnKvD/gPprzNuWr3Mye
QF/6zHSqSzdGTDfPyl3dYz438iSOnZemsuPBTEtzL9L+0+KuRRKUgPgV5omLt4oT
BZ9YB7JA
=qup2
-END PGP SIGNATURE-

Bug#849401: restart silently fails

[Francesco Poli]

On Sun, 15 Jan 2017 10:28:40 +0100 Daniel Pocock wrote:

> 
> 
> On 10/01/17 23:49, Christian Hofstaedtler wrote:
[...]
> > here are some test packages with a systemd service
> > file:
> > 
> > https://people.debian.org/~zeha/apcupsd/
> > 
> > Please report back if those work for you and if the restart issue
> > is fixed.
> > Note that successful testing also needs to include a powerfail test
> > really.
> > 
> 
> 
> I installed that and tested with this loop:
> 
> systemctl start apcupsd && while ps -C apcupsd ; do systemctl stop
> apcupsd ; sleep 0 ; systemctl start apcupsd ; ps -C apcupsd || echo
> FAILED ; done
> 
> 
> For about 3 minutes, it appears to restart correctly every time.
> 
> I haven't done a full powerfail test so far.

Hello Daniel,
thanks for your feedback.

I hope that Christian may soon finalize the NMU in order to have this
bug fixed once and for all.

Christian, have you decided which strategy should be adopted for the
ISCONFIGURED handling?




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


pgpiq4vUSlv9U.pgp
Description: PGP signature

Bug#851498: g-s-d has an undocumented and unstable tmp-cleaner

[Ben Hutchings]

Package: gnome-settings-daemon
Version: 3.22.1-1
Severity: grave

I noticed that gnome-settings-daemon regularly crashes and restarts
on my system.

I investigated this with gdb and got the following backtrace:

#0  0x7f00e6aac261 in _g_log_abort (breakpoint=1) at 
././glib/gmessages.c:487
#1  0x7f00e6aad2b7 in g_log_default_handler (log_domain=0x7f00e6aeed2e 
"GLib", log_level=6, message=, unused_data=) at 
././glib/gmessages.c:2816
#2  0x7f00e6aad5c4 in g_logv (log_domain=0x7f00e6aeed2e "GLib", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd0faba4c0) at ././glib/gmessages.c:1275
#3  0x7f00e6aad7cf in g_log (log_domain=log_domain@entry=0x7f00e6aeed2e 
"GLib", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x7f00e6b4eaa0 "Creating pipes for GWakeup: %s\n") at 
././glib/gmessages.c:1337
#4  0x7f00e6aeabf2 in g_wakeup_new () at ././glib/gwakeup.c:161
#5  0x7f00e6aa4083 in g_main_context_new () at ././glib/gmain.c:656
#6  0x7f00e708080e in g_dbus_connection_send_message_with_reply_sync 
(connection=connection@entry=0x769190 [GDBusConnection], 
message=message@entry=0xb802d0 [GDBusMessage], 
flags=flags@entry=G_DBUS_SEND_MESSAGE_FLAGS_NONE, 
timeout_msec=timeout_msec@entry=-1, out_serial=out_serial@entry=0x0, 
cancellable=cancellable@entry=0x0, error=0x7ffd0faba6a0) at 
././gio/gdbusconnection.c:2138
#7  0x7f00e7080c74 in g_dbus_connection_call_sync_internal 
(connection=0x769190 [GDBusConnection], bus_name=bus_name@entry=0xaea530 
":1.114", object_path=0xcfb7d0 "/org/gtk/vfs/metadata", 
interface_name=interface_name@entry=0xb6f440 "org.gtk.vfs.Metadata", 
method_name=method_name@entry=0x7f00dc269d2a "GetTreeFromDevice", 
parameters=parameters@entry=0x986f90, reply_type=0xb2cec0, 
flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1, fd_list=0x0, out_fd_list=0x0, 
cancellable=0x0, error=0x7ffd0faba880) at ././gio/gdbusconnection.c:5935
#8  0x7f00e7083025 in g_dbus_connection_call_with_unix_fd_list_sync 
(connection=, bus_name=bus_name@entry=0xaea530 ":1.114", 
object_path=, interface_name=interface_name@entry=0xb6f440 
"org.gtk.vfs.Metadata", method_name=method_name@entry=0x7f00dc269d2a 
"GetTreeFromDevice", parameters=parameters@entry=0x986f90, reply_type=0xb2cec0, 
flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1, fd_list=0x0, out_fd_list=0x0, 
cancellable=0x0, error=0x7ffd0faba880) at ././gio/gdbusconnection.c:6281
#9  0x7f00e708cd1d in g_dbus_proxy_call_sync_internal (proxy=0x7f009c011d60 
[GVfsMetadataProxy], method_name=, parameters=0x986f90, 
flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=, 
fd_list=fd_list@entry=0x0, out_fd_list=0x0, cancellable=0x0, 
error=0x7ffd0faba880)
at ././gio/gdbusproxy.c:2857
#10 0x7f00e708e0a4 in g_dbus_proxy_call_sync (proxy=, 
method_name=, parameters=, flags=, 
timeout_msec=, cancellable=, 
error=0x7ffd0faba880) at ././gio/gdbusproxy.c:3049
#11 0x7f00dc267248 in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
#12 0x7f00dc2640de in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
#13 0x7f00dc24e685 in  () at 
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
#14 0x7f00e70a132a in g_local_file_delete (file=0xba22c0, 
cancellable=, error=0x0) at ././gio/glocalfile.c:1551
#15 0x7f00dc47a485 in delete_subdir (source=, res=0xb04c40, 
user_data=0x924d30) at gsd-disk-space.c:383
#16 0x7f00e704d4e3 in g_task_return_now (task=0xb04c40 [GTask]) at 
././gio/gtask.c:1121
#17 0x7f00e704d519 in complete_in_idle_cb (task=0xb04c40) at 
././gio/gtask.c:1135
#18 0x7f00e6aa66aa in g_main_dispatch (context=0x750600) at 
././glib/gmain.c:3203
#19 0x7f00e6aa66aa in g_main_context_dispatch 
(context=context@entry=0x750600) at ././glib/gmain.c:3856
#20 0x7f00e6aa6a60 in g_main_context_iterate (context=0x750600, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
././glib/gmain.c:3929
#21 0x7f00e6aa6d82 in g_main_loop_run (loop=0x795c60) at 
././glib/gmain.c:4125
#22 0x7f00e787ccc5 in gtk_main () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#23 0x004036c0 in main ()

Examining frame #14:

(gdb) print *local
$1 = {parent_instance = {g_type_instance = {g_class = 0x7f00d000be10}, 
ref_count = 2, qdata = 0x0}, 
  filename = 0xc5dfa0 
"/var/tmp/0QI_OkZMk7/linux-3.16.36/debian/linux-image-3.16.0-4-m68k.templates"}

So gnome-settings-daemon is cleaning up /var/tmp.  That is a useful
function, but this behaviour is not documented anywhere.  It is *not*
normal for /var/tmp to be cleaned up automatically so this is a bug.

Now, why is it crashing?  The log format string (which never actually
makes it into the log - that seems a bug in _g_log_abort()) - is
"Creating pipes for GWakeup: %s".  The only likely reason for pipe
creation failure is a limit on number of FDs.  Sure enough, this
process has 1024 FDs open, mostly for directories under /var/tmp.
That looks like an FD leak.

Ben.

-- System Information:
Debian Release: stretch/sid
  APT prefers 

Bug#851497: hashcat builds with -march=native

[Adrian Bunk]

Source: hashcat
Version: 3.20-1
Severity: grave

src/Makefile sets -march=native

This means the code will only run on machines with a CPU
compatible with the one on the machine where the package
was built.

Building on a different buildd machine can also change
where the code can run - including breaking existing
setups in stable updates.

Please remove -march=native from src/Makefile

Processed: Re: Bug#851379: dietlibc FTBFS on arm64: Bus error when running tst-calloc.c

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #851379 [src:dietlibc] dietlibc FTBFS on arm64: Bus error when running 
tst-calloc.c
Added tag(s) confirmed.

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

Bug#851379: dietlibc FTBFS on arm64: Bus error when running tst-calloc.c

[Christian Seiler]

Control: tags -1 + confirmed

On 01/14/2017 02:30 PM, Adrian Bunk wrote:
> Source: dietlibc
> Version: 0.34~cvs20160606-4
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=dietlibc=arm64=0.34~cvs20160606-4=1483685322
> 
> ...
>   test/stdlib/testrand.c : build: OKrun: OK
>   test/stdlib/tst-calloc.c   : build: OKrun: ERROR
>   test/stdlib/tst-system.c   : build: OKrun: OK
> 
> RUN ERROR for test/stdlib/tst-calloc.c in variant pthreads (rc = 135), test 
> output is:
> 
> Bus error
> 

Yeah, I noticed that earlier. I've tried to reproduce this here, but
I don't have ARM hardware. (Not ARMv8 anyway.) I can't reproduce it
in qemu-user chroots and I've now tried to setup a full VM (via
qemu-system) but the test works there as well.

I suspect that "Bus error" stems from an unaligned memory access;
but this is one area where qemu is less strict than the CPU it
emulates...

I'll try to figure this out on a porterbox.

Regards,
Christian

Bug#851380: marked as done ([imagemagick] memory leak in caption and label handling)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 16:50:06 +0100
with message-id <9398851.JRKpixbmUG@portable2015-bastien>
and subject line Done: [imagemagick]  memory leak in caption and label handling
has caused the Debian Bug report #851380,
regarding [imagemagick]  memory leak in caption and label handling
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.)


-- 
851380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Version:  8:6.7.7.10-5
Severity: serious
Tags: patch security fixed-upstream
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
forwarded: 
https://github.com/ImageMagick/ImageMagick/commit/aeff00de228bc5a158c2a975ab47845d8a1db456

Fixed here 
https://github.com/ImageMagick/ImageMagick/commit/aeff00de228bc5a158c2a975ab47845d8a1db456


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Package: imagemagick
Version: 8:6.9.7.0+dfsg-1

Fixed in unstable



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

Bug#851116: marked as done (zygrib: violates font license)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 15:09:04 +
with message-id 
and subject line Bug#851116: fixed in zygrib 8.0.1+dfsg.1-1
has caused the Debian Bug report #851116,
regarding zygrib: violates font license
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.)


-- 
851116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zygrib
Version: 8.0.1-1
Severity: serious
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: license-violation
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

Your source package contains an GPL/LGPL font:

data/fonts/liberation-fonts/LiberationSans-BoldItalic.ttf
data/fonts/liberation-fonts/LiberationMono-BoldItalic.ttf
data/fonts/liberation-fonts/LiberationSerif-BoldItalic.ttf
data/fonts/liberation-fonts/LiberationSans-Italic.ttf
data/fonts/liberation-fonts/LiberationSerif-Bold.ttf
data/fonts/liberation-fonts/LiberationMono-Bold.ttf
data/fonts/liberation-fonts/LiberationSans-Regular.ttf
data/fonts/liberation-fonts/LiberationMono-Regular.ttf
data/fonts/liberation-fonts/LiberationSerif-Regular.ttf
data/fonts/liberation-fonts/LiberationSans-Bold.ttf
data/fonts/liberation-fonts/LiberationSerif-Italic.ttf
data/fonts/liberation-fonts/LiberationMono-Italic.ttf

This looks to be from here:

https://fedorahosted.org/liberation-fonts/

The font's source code appears to be here:

https://git.fedorahosted.org/cgit/liberation-fonts.git/tree/src

Your source package does not contain the font source code, therefore
your distribution of the font constitutes a violation of the license.

Please notify your upstream that they are violating the font license.

Please remove the font from the source package and build-depend or
depend on the fonts-liberation binary font package instead.

Please contact your upstream and ask them to use fontconfig or similar
to get fonts for use by the software instead of using a specific font.

This message is brought to you by the Debian Fonts Task Force:

http://wiki.debian.org/Fonts

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: zygrib
Source-Version: 8.0.1+dfsg.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 12 Jan 2017 16:21:13 +
Source: zygrib
Binary: zygrib zygrib-maps
Architecture: source amd64 all
Version: 8.0.1+dfsg.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 zygrib - Weather data visualization,  GRIB file viewer
 zygrib-maps - Maps for zyGrib weather visualization
Closes: 851116
Changes:
 zygrib (8.0.1+dfsg.1-1) unstable; urgency=medium
 .
   * Don't ship liberation-font in source. Create DFSG package. Closes: #851116.
Checksums-Sha1:
 244599c5ea82b2bb5415604a7ae7449fb1bde4c8 1989 zygrib_8.0.1+dfsg.1-1.dsc
 958a9169516bb9c677b76993ac9480c3e0fdc792 79495016 
zygrib_8.0.1+dfsg.1.orig.tar.xz
 31575c043d5b1b47b9ef0d06af22822f62098b13 10540 
zygrib_8.0.1+dfsg.1-1.debian.tar.xz
 79250a72066a15bc97b2b86abad3e50861d9a759 55680 
zygrib-dbgsym_8.0.1+dfsg.1-1_amd64.deb
 299826c9eb82f6ebd57b80788d32212e5505de05 77066714 
zygrib-maps_8.0.1+dfsg.1-1_all.deb
 533b4e8e015f483edde6e5cc077636f5f71f3d1b 9333 
zygrib_8.0.1+dfsg.1-1_amd64.buildinfo
 202586cb7906b930de1d16c71a4a5f09967030a0 746596 zygrib_8.0.1+dfsg.1-1_amd64.deb
Checksums-Sha256:
 2a685f120f67c4f3c300c2ef067d8ff877ee987024eba1b3c1383a2649a91bf1 1989 
zygrib_8.0.1+dfsg.1-1.dsc
 bda694e4e9cb5560821a4b86a7a1458c8e093b988a2892a6ec463c39620da5e9 79495016 
zygrib_8.0.1+dfsg.1.orig.tar.xz
 a1506f6aa31b9f12f661bc74a8994b7eca530849af7f35fed64c0ea9fc456f4f 10540 
zygrib_8.0.1+dfsg.1-1.debian.tar.xz
 

Processed: limit source to imagemagick, tagging 851382

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 851382 + pending
Bug #851382 [imagemagick] [imagemagick]  memory leak in MPC file handling
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#851437: astroplan: FTBFS (requires Internet to build)

[Ole Streicher]

The problem here is that with astropy-1.3, doctests are buggy:

https://github.com/astropy/astropy/issues/5670

A workaround currently is to disable doctests during the build:

python$* setup.py test --skip-docs -vv --args -v

Cheers

Ole

Processed: limit source to imagemagick, tagging 849439, tagging 851383

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 849439 + pending
Bug #849439 [src:imagemagick] imagemagick: CVE-2016-10062: fwrite issue in 
ReadGROUP4Image
Ignoring request to alter tags of bug #849439 to the same tags previously set
> tags 851383 + pending
Bug #851383 [imagemagick] [imagemagick]  double free in profile
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages]

[Ian Jackson]

tl;dr
  TYVM to Michael Biebl
  I intend QA upload of systemd-shim with Michael's wrapper

Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and 
1 more messages]"):
> Am 05.01.2017 um 19:56 schrieb Michael Biebl:
> > Then copy the attached wrapper script to /usr/lib/x86_64-linux-gnu/
> > and make it executable.
> 
> Obviously, the wrapper script should start systemd-shim.orig.

Well, I only previously glanced at this script.  I thought it was a
way to collect more information.  Now that I sit down to deal with
this problem properly, I discover that actually it fixes the problem!

Thank you very much (and I'm sorry now that I was a bit avoidant about
trying this, thinking that it would be part of a big and stressy
debugging and spelunking session).

Correct me if I'm wrong, but I think the right thing is probably to do
is ship this comaptibility workaround in stretch.  I looked on my
system and filesystems of type cgroup are not mounted anywhere else.

And I'm not sure what is using /sys/fs/cgroup/systemd but it doesn't
seem to be systemd-shim.  I guess then that this is something that
used to be done by one bit of systemd and is now done by another bit,
so that it now has to also be done by systemd-shim ?

So my plan is to do a QA upload of systemd-shim which includes a
variant of your wrapper script (perhaps with set -e added...).  I
looked at the code in systemd-shim and implementing this code in its C
code doesn't look very convenient.  (It's also possible that this
should be done in an init script but I haven't considered that
properly.)

I haven't decided whether to put give the wrapper the name
`/usr/lib/x86_64-linux-gnu/systemd-shim' as you did, or alternatively
whether to give it a new name and change the reference in
  /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
Unless anyone has an opinion I'll do whatever is easier.

More news later today.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Processed: limit source to imagemagick, tagging 851377, tagging 851376

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 851377 + pending
Bug #851377 [imagemagick] [imagemagick]  out of bound in psd file handling
Added tag(s) pending.
> tags 851376 + pending
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
Ignoring request to alter tags of bug #851376 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: limit source to imagemagick, tagging 851376

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 851376 + pending
Bug #851376 [imagemagick] [imagemagick] memory corruption heap overflow
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to imagemagick, tagging 851381

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 851381 + pending
Bug #851381 [imagemagick] [imagemagick]  Crash - PushQuantumPixel - 
Heap-Buffer-Overflow (TIFF)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 851483 in 8:6.7.7.10-5

[Debian Bug Tracking System]

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

> # common anchestor
> found 851483 8:6.7.7.10-5
Bug #851483 [src:imagemagick] [imagemagick]  wpg file off by one
Ignoring request to alter found versions of bug #851483 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: limit source to imagemagick, tagging 851374

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 851374 + pending
Bug #851374 [imagemagick] [imagemagick] memory corruption heap overflow
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 851485 in 8:6.7.7.10-5

[Debian Bug Tracking System]

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

> # common anchestor
> found 851485 8:6.7.7.10-5
Bug #851485 [src:imagemagick] [imagemagick]  ipl file missing malloc check
Ignoring request to alter found versions of bug #851485 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: limit source to imagemagick, tagging 849507, tagging 793629, tagging 851485, tagging 851483 ...

[Debian Bug Tracking System]

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

> limit source imagemagick
Limiting to bugs with field 'source' containing at least one of 'imagemagick'
Limit currently set to 'source':'imagemagick'

> tags 849507 + pending
Bug #849507 [imagemagick-6.q16] imagemagick-6.q16: convert generates monochrome 
images with inverted colors (black and white)
Added tag(s) pending.
> tags 793629 + pending
Bug #793629 [imagemagick] imagemgick 8:6.8.9.9-5: display -loop option not 
working/missing
Added tag(s) pending.
> tags 851485 + pending
Bug #851485 [src:imagemagick] [imagemagick]  ipl file missing malloc check
Added tag(s) pending.
> tags 851483 + pending
Bug #851483 [src:imagemagick] [imagemagick]  wpg file off by one
Added tag(s) pending.
> tags 791460 + pending
Bug #791460 [imagemagick-6.q16] [regression] convert: ignores TMP TMPDIR TEMP 
TEMPDIR environment variables
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#851485: [imagemagick] ipl file missing malloc check

[Bastien ROUCARIÈS]

Package: src:imagemagick
Version:  8:6.7.7.10-5
Severity: serious
Tags: patch security fixed-upstream
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

Fixed 
https://github.com/ImageMagick/ImageMagick/commit/97566cf2806c0a5a86e884c96831a0c3b1ec6c20


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

Bug#851483: [imagemagick] wpg file off by one

[Bastien ROUCARIÈS]

Package: src:imagemagick
Version:  8:6.7.7.10-5
Severity: serious
Tags: patch security fixed-upstream
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

Fix a off by one error 
Fixed 
https://github.com/ImageMagick/ImageMagick/commit/d23beebe7b1179fb75db1e85fbca3100e49593d9


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

Processed: fixed 820026 in 1:45.2.0-1~deb8u1

[Debian Bug Tracking System]

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

> fixed 820026 1:45.2.0-1~deb8u1
Bug #820026 {Done: Christoph Goehre } [icedove] icedove 
crashes (segfaults) when installed along with xul-ext-foxyproxy-standard
Marked as fixed in versions icedove/1:45.2.0-1~deb8u1.
> thanks
Stopping processing here.

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

Bug#851002: marked as done (ggcov: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:25:05 +
with message-id 
and subject line closed
has caused the Debian Bug report #851002,
regarding ggcov: FTBFS: Test failures
to be marked as done.

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

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


-- 
851002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ggcov
Version: 0.9-13
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):
> ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> PASS: (test021) unit test for libpopt / fakepopt.c
> ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log
> Total: 2/20 tests passed
> debian/rules:34: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/01/11/ggcov_0.9-13_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 ---
close 851002

thanks


This bug was fixed in upload 0.9-14 but the wrong number was entered in
the changelog.



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




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

Processed: Re: #851412: libsystemd segfaults on mips64el

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + pdns pdns-recursor
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Added indication that 851412 affects pdns and pdns-recursor

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

Bug#851412: #851412: libsystemd segfaults on mips64el

[Christian Hofstaedtler]

Control: affects -1 + pdns pdns-recursor

Hi,

pdns and pdns-recursor link against libsystemd, and this bug causes
both of them to just segfault on startup on mips64el.

Tiny reproducer:

(sid_mips64el-dchroot)zeha@eller:~$ cat foo.c 
int main() {
}
(sid_mips64el-dchroot)zeha@eller:~$ make foo LDFLAGS=-lsystemd
cc   -lsystemd  foo.c   -o foo
(sid_mips64el-dchroot)zeha@eller:~$ gdb --args foo
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
Reading symbols from foo...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/zeha/foo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (warning: GDB can't find the start of the function at 
0xfff7f2fd27.

GDB is unable to find the start of the function at 0xfff7f2fd27
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0xfff7f2fd27 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
fp=0x1) at iofclose.c:48
48  iofclose.c: No such file or directory.
(gdb) bt full
#0  _IO_new_fclose (fp=0x1) at iofclose.c:48
status = 
#1  0x00fff7f2fd28 in ?? () from 
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
No symbol table info available.
(gdb) quit
A debugging session is active.

Inferior 1 [process 11890] will be killed.

Quit anyway? (y or n) y
(sid_mips64el-dchroot)zeha@eller:~$ ls -la /etc/machine-id
ls: cannot access '/etc/machine-id': No such file or directory


PS: libsystemd does not appear to have a -dbgsym package.

-- 
christian hofstaedtler 

Bug#851005: marked as done (clementine: FTBFS: chromaprinter.cpp:146:33: error: invalid conversion from 'void*' to 'const int16_t* {aka const short int*}' [-fpermissive])

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:03:38 +
with message-id 
and subject line Bug#851005: fixed in clementine 1.3.1+git276-g3485bbe43+dfsg-1
has caused the Debian Bug report #851005,
regarding clementine: FTBFS: chromaprinter.cpp:146:33: error: invalid 
conversion from 'void*' to 'const int16_t* {aka const short int*}' 
[-fpermissive]
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.)


-- 
851005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clementine
Version: 1.3.1+git240-g1a2f6e2+dfsg-1
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):
> cd 
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu/src 
> && /usr/bin/c++   -DBOOST_BIND_NO_PLACEHOLDERS -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
> -DQT_NO_URL_CAST_FROM_STRING -DQT_OPENGL_LIB -DQT_SQL_LIB 
> -DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER -DQT_XML_LIB 
> -I/usr/include/taglib -isystem /usr/include/qt4 -isystem 
> /usr/include/qt4/QtCore -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -isystem 
> /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtGui -isystem 
> /usr/include/qt4/QtDBus -isystem /usr/include/qt4/QtXml -isystem 
> /usr/include/qt4/QtSql -isystem /usr/include/qt4/QtNetwork 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/3rdparty/qsqlite 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu/src
>  -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/../3rdparty/gmock/gtest/include
>  -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/3rdparty/qtsingleapplication
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/3rdparty/qtiocompressor 
> -I/usr/include/qxt/QxtCore -I/usr/include/qxt/QxtGui 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/3rdparty/sha2 
> -I/usr/include/mygpo-qt 
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/ext/libclementine-common
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/ext/libclementine-tagreader
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu/ext/libclementine-tagreader
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/ext/libclementine-remote
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu/ext/libclementine-remote
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/ext/libclementine-spotifyblob
>  
> -I/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/obj-x86_64-linux-gnu/ext/libclementine-spotifyblob
>  -I/usr/include/gpod-1.0 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/libpng16 -I/usr/include/p11-kit-1 -I/usr/include/libusb-1.0  
> -g -O2 
> -fdebug-prefix-map=/<>/clementine-1.3.1+git240-g1a2f6e2+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -DQT_NO_DEBUG_OUTPUT -DQT_NO_WARNING_OUTPUT -Wdate-time -D_FORTIFY_SOURCE=2 
> -Woverloaded-virtual -Wall -Wno-sign-compare -Wno-deprecated-declarations 
> -Wno-unused-local-typedefs --std=c++0x -U__STRICT_ANSI__ -Werror   -o 
> CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o -c 
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/musicbrainz/chromaprinter.cpp
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/musicbrainz/chromaprinter.cpp:
>  In member function 'QString Chromaprinter::CreateFingerprint()':
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/musicbrainz/chromaprinter.cpp:146:33:
>  error: invalid conversion from 'void*' to 'const int16_t* {aka const short 
> int*}' [-fpermissive]
>chromaprint_feed(chromaprint, reinterpret_cast(data.data()),
>  ^~~~
> In file included from 
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/musicbrainz/chromaprinter.cpp:27:0:
> /usr/include/chromaprint.h:235:21: note:   initializing argument 2 of 'int 
> chromaprint_feed(ChromaprintContext*, const int16_t*, int)'
>  CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const int16_t 
> *data, int size);
>  ^~~~
> /<>/clementine-1.3.1+git240-g1a2f6e2+dfsg/src/musicbrainz/chromaprinter.cpp:152:58:
>  error: invalid conversion from 'void**' to 'uint32_t** {aka unsigned 

Bug#851104: marked as done (frama-c: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/frama-c/analyses_manager.cmi)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 12:33:48 +
with message-id 
and subject line Bug#851104: fixed in frama-c 20161101+silicon+dfsg-5
has caused the Debian Bug report #851104,
regarding frama-c: fails to upgrade from 'jessie' - trying to overwrite 
/usr/lib/frama-c/analyses_manager.cmi
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.)


-- 
851104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: frama-c
Version: 20161101+silicon+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 20161101+silicon+dfsg-2

Hi,

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

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

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

  Preparing to unpack .../frama-c_20161101+silicon+dfsg-4_amd64.deb ...
  Unpacking frama-c (20161101+silicon+dfsg-4) over (20140301+neon+dfsg-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/frama-c_20161101+silicon+dfsg-4_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/frama-c/analyses_manager.cmi', which is also 
in package frama-c-base 20140301+neon+dfsg-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../frama-c-base_20161101+silicon+dfsg-4_amd64.deb ...
  Unpacking frama-c-base (20161101+silicon+dfsg-4) over (20140301+neon+dfsg-3) 
...


cheers,

Andreas


frama-c_20161101+silicon+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: frama-c
Source-Version: 20161101+silicon+dfsg-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jan 2017 13:00:55 +0100
Source: frama-c
Binary: frama-c frama-c-base
Architecture: source amd64
Version: 20161101+silicon+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Mehdi Dogguy 
Description:
 frama-c- Platform dedicated to the analysis of source code written in C
 frama-c-base - Platform dedicated to the analysis of source code written in C 
(w
Closes: 851104
Changes:
 frama-c (20161101+silicon+dfsg-5) unstable; urgency=medium
 .
   * Add Breaks/Replaces frama-c-base (<= 20140301+neon+dfsg-3) to
 frama-c (Closes: #851104)
Checksums-Sha1:
 1d07c56da35a2e7660de9d58fdf066efc1c0de81 2408 
frama-c_20161101+silicon+dfsg-5.dsc
 cbe5a0c5043dce94e8f36dd0ed5412af76f22cc9 26904 
frama-c_20161101+silicon+dfsg-5.debian.tar.xz
 87c6491ca48b5168c48c398d67b8a03db9041185 1054358 
frama-c-base-dbgsym_20161101+silicon+dfsg-5_amd64.deb
 467132312c47554ad4c60343390a4d0295eb4a6c 19985076 
frama-c-base_20161101+silicon+dfsg-5_amd64.deb
 62d16908c99db2e95fd770b341b2e8134eeadd1d 1105508 
frama-c-dbgsym_20161101+silicon+dfsg-5_amd64.deb
 d1643d5e8d6b493fe5f4f259c2cce8eed2887c53 14868 
frama-c_20161101+silicon+dfsg-5_amd64.buildinfo
 87bc40ee33dc29c7d59086e51585356abd310a15 10607904 
frama-c_20161101+silicon+dfsg-5_amd64.deb
Checksums-Sha256:
 76a43db7b5d907008601a47f1b3768e102e74b388b2aa7312eb03b3f649210f6 2408 
frama-c_20161101+silicon+dfsg-5.dsc
 ce26cb525e28f9de9fc47a3654c2b22e7e0d32898dd636c3d5ee7f03a5729ca2 26904 
frama-c_20161101+silicon+dfsg-5.debian.tar.xz
 77fc61e7a57c6c299c62a1b9dfb133806445c5f4f5a8ee2c80b513d5cf9e9517 1054358 
frama-c-base-dbgsym_20161101+silicon+dfsg-5_amd64.deb
 bd897f5c70377d8db8b7cfc6fffd2e61bf5b73ae89a0c369d6f7fd6c51f2ebbd 19985076 
frama-c-base_20161101+silicon+dfsg-5_amd64.deb
 0417b0b714349e6842fb792a62cd17148af548dd8b7a2bc3e524d1cb27c3e39b 1105508 

Bug#845152: marked as done (systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:27:54 +0200
with message-id <20170115112754.mnxc3hktnoq6ju6o@localhost>
and subject line systemd-docker was removed from stretch
has caused the Debian Bug report #845152,
regarding systemd-docker FTBFS in stretch due to missing 
golang-github-docker-docker-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.)


-- 
845152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd-docker
Version: 0.2.1+dfsg-2
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

systemd-docker build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530
--- End Message ---
--- Begin Message ---
systemd-docker was removed from stretch and won't be able to enter 
again, closing this obsolete bug.

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#845151: marked as done (nomad FTBFS in stretch due to missing golang-github-docker-docker-dev)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:27:01 +0200
with message-id <20170115112701.otipsslfgo6ax6x4@localhost>
and subject line nomad was removed from stretch
has caused the Debian Bug report #845151,
regarding nomad FTBFS in stretch due to missing golang-github-docker-docker-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.)


-- 
845151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad
Version: 0.4.0+dfsg-1
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

nomad build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530
--- End Message ---
--- Begin Message ---
nomad was removed from stretch and won't be able to enter again,
closing this obsolete bug.

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#845150: marked as done (gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:25:22 +0200
with message-id <20170115112522.otoix3e6kpr6qgib@localhost>
and subject line gitlab-ci-multi-runner was removed from stretch
has caused the Debian Bug report #845150,
regarding gitlab-ci-multi-runner FTBFS in stretch due to missing 
golang-github-docker-docker-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.)


-- 
845150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab-ci-multi-runner
Version: 1.7.1+dfsg-2
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

gitlab-ci-multi-runner build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530
--- End Message ---
--- Begin Message ---
gitlab-ci-multi-runner was removed from stretch and won't be able to 
enter again, closing this obsolete bug.

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#822412: What about these WSDL-Schema files?

[Andreas Tille]

Hi Filippo,

its a shame to stumble upon this to late since at least the other RC bug
of openms might have been easy to fix and now the package is doomed for
next stable.  It would be nice to know whether the package would work after
removing the WSDL-Schema files affected by the non-free license or whether
we need something to do to investigate.

BTW, it would help if you would at least answer such bug reports and make
some noise on the DebiChem list if you need help to fix it.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#845149: marked as done (containerd FTBFS in stretch due to missing golang-github-docker-docker-dev)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jan 2017 13:22:43 +0200
with message-id <20170115112243.zj3oolgjafblo6xa@localhost>
and subject line containerd was removed from stretch
has caused the Debian Bug report #845149,
regarding containerd FTBFS in stretch due to missing 
golang-github-docker-docker-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.)


-- 
845149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: containerd
Version: 0.2.1~ds1-3
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

containerd build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530
--- End Message ---
--- Begin Message ---
containerd was removed from stretch and won't be able to enter again,
closing this obsolete bug.

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#851471: linux-image-4.8.0-2-686-pae: premature oom killer invocation running 4.8.15

[Florian Siegesmund]

Technisat SkyStar2 DVB card [13d0:2103] (rev 02)
Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / 
Technisat SkyStar2 DVB card [13d0:2103]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- 
ii  grub-pc 2.02~beta3-3
ii  linux-doc-4.8   4.8.15-2

Versions of packages linux-image-4.8.0-2-686-pae is related to:
ii  firmware-amd-graphics 20161130-2
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
ii  firmware-ivtv 20161130-2
pn  firmware-iwlwifi  
pn  firmware-libertas 
ii  firmware-linux-nonfree20161130-2
ii  firmware-misc-nonfree 20161130-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information


syslog-20170115-oom.txt.gz
Description: application/gzip