Processed: your mail

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

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

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

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

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

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

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

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

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

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

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

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

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

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 > >

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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:

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

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

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

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):

Bug#849598: marked as done (amarok: FTBFS (cannot find -lmysqlclient))

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

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

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

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

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

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

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

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

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

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

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

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

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

Processed: tagging 849326

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

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

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

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

> 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

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

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

Bug#851384: Fixed upstream

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

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

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

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

Bug#848236: 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

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

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

Processed: Bug #808654 closed accidentally (it seems)

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]

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

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

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

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

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

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

Processed: Mark as forwarded and fixed upstream

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

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

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

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

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

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)

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

Processed: Merge duplicates

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

Processed: found 851380 in 8:6.7.7.10-4

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

Bug#851505: Xvfb segfaults on mips64el

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):

Processed: your mail

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

Bug#851412: #851412: libsystemd segfaults on mips64el

* 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: >

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

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

Bug#822369: marked as done (xfsprogs: FTBFS: error: redefinition of 'struct fsxattr')

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

Bug#851412: #851412: libsystemd segfaults on mips64el

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

Processed: Proper version tracking

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. --

Processed: found in stable and unstable

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

Processed: found in stable and unstable

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 -

Processed: found in stable and unstable

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

Processed: found in stable and unstable

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

Processed: found in stable and unstable

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

Processed: found in stable and unstable

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

Bug#851374: found in stable and unstable

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

-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: >>> >>>

Processed: severity of 851471 is important

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

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")

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

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

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

Processed: Also add an affects

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:

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

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#851498: g-s-d has an undocumented and unstable tmp-cleaner

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

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

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

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

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.

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

-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

Bug#849401: restart silently fails

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

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

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

Bug#851497: hashcat builds with -march=native

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

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

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

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

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: OK

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

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

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

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

Processed: limit source to imagemagick, tagging 851382

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

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

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

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

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

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

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

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

Processed: limit source to imagemagick, tagging 851376

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

Processed: limit source to imagemagick, tagging 851381

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 -

Processed: found 851483 in 8:6.7.7.10-5

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

Processed: limit source to imagemagick, tagging 851374

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

Processed: found 851485 in 8:6.7.7.10-5

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

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

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

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

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

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

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

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

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

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

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

Processed: Re: #851412: libsystemd segfaults on mips64el

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

Bug#851412: #851412: libsystemd segfaults on mips64el

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

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])

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

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

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

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

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

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

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

Bug#845150: marked as done (gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev)

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

Bug#822412: What about these WSDL-Schema files?

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

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

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

Bug#851471: linux-image-4.8.0-2-686-pae: premature oom killer invocation running 4.8.15

pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information syslog-20170115-oom.txt.gz Description: application/gzip

  1   2   >