Bug#886382: Coming updates for meltdown/spectre

Package: amd64-microcode Severity: grave It seems AMD cpus are also affected by the meltdown/spectre bugs. Do you know if AMD plans to release microcode updates and if so, will it be packaged here? (intel bug, for ref): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367 -- pollo

Bug#886374: texlive-latex-extra and emboss: error when trying to install together

> dpkg: error processing archive > /var/cache/apt/archives/texlive-latex-extra_2017.20180103-1_all.deb > (--unpack): > trying to overwrite '/usr/bin/wordcount', which is also in package emboss > 6.6.0+dfsg-6+b1 I renamed the TeX wordcount to latex-wordcount Norbert -- PREINING Norbert

Bug#886374: marked as done (texlive-latex-extra and emboss: error when trying to install together)

Your message dated Fri, 05 Jan 2018 05:40:58 + with message-id and subject line Bug#886374: fixed in texlive-extra 2017.20180103-2 has caused the Debian Bug report #886374, regarding texlive-latex-extra and emboss: error when trying to install together to

Bug#886361: marked as done (apertium: frequent parallel FTBFS)

Your message dated Fri, 05 Jan 2018 05:04:06 + with message-id and subject line Bug#886361: fixed in apertium 3.4.2~r68466-4 has caused the Debian Bug report #886361, regarding apertium: frequent parallel FTBFS to be marked as done. This means that you

Bug#884230: texlive-base: cmbcsc10 moved to texlive-fonts-extra

> Oh dear: > Need to get 336 MB/343 MB of archives. > After this operation, 960 MB of additional disk space will be used. I know. The problem is old and known, namely that many TeX documents search fonts not via fontconfig but via file name, and thus the fonts have to be in the texmf tree (at

Bug#882247:

On Jan 05, Mike Hommey wrote: > There is something wrong with the default locale. Try installing a > locale package (even firefox-l10n-en-gb) or downgrade to 57. Confirmed, this fixes it. -- ciao, Marco signature.asc Description: PGP signature

Bug#882247:

There is something wrong with the default locale. Try installing a locale package (even firefox-l10n-en-gb) or downgrade to 57. Mike

Bug#886367: marked as done (intel-microcode: coming updates for meltdown/spectre)

Your message dated Fri, 05 Jan 2018 03:35:31 + with message-id and subject line Bug#886367: fixed in intel-microcode 3.20171215.1 has caused the Debian Bug report #886367, regarding intel-microcode: coming updates for meltdown/spectre to be marked as done.

Bug#883698: marked as done (freetype: incorrect shlibs file generation)

Your message dated Fri, 05 Jan 2018 03:35:05 + with message-id and subject line Bug#883698: fixed in freetype 2.8.1-1 has caused the Debian Bug report #883698, regarding freetype: incorrect shlibs file generation to be marked as done. This means that you

Bug#882247:

Mike: There is something wrong with the default locale. Try installing a > locale package (even firefox-l10n-en-gb) or downgrade to 57. Turns out I can't install that from unstable (depends on firefox << 57.0.3-1), however I installed it from experimental (58.0~b4-1) and now firefox works!!!

Bug#886374: texlive-latex-extra and emboss: error when trying to install together

Package: emboss,texlive-latex-extra Version: emboss/6.6.0+dfsg-6+b1 Version: texlive-latex-extra/2017.20180103-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2018-01-04 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: better log output

On 2017-12-28 15:31, Michael Biebl wrote: Control: tags -1 + moreinfo Please install dbgsym packages for at least libnm0, libnma0 and network-manager-gnome to get a more useful backtrace. https://wiki.debian.org/HowToGetABacktrace This is the output of gdb after installing a bunch of -dbgsym

Bug#750732: Pending fixes for bugs in the libanyevent-perl package

tag 750732 + pending thanks Some bugs in the libanyevent-perl package are closed in revision b8e06b0cb8fe01a4451564a05dfec86db120b7d0 in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libanyevent-perl.git/commit/?id=b8e06b0

Processed: Pending fixes for bugs in the libanyevent-perl package

Processing commands for cont...@bugs.debian.org: > tag 750732 + pending Bug #750732 [src:libanyevent-perl] libanyevent-perl: Intermittent build failures on various architectures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 750732:

Bug#750732: libanyevent-perl: Intermittent build failures on various architectures

On Mon, 01 Jan 2018 18:56:52 +0200, Niko Tyni wrote: > The issue seems mostly specific to armel and hurd, although > tests.reproducible-builds.org does have some failures on i386 (but no > logs so those could be just testbed glitches or transient sid issues.) > I don't know what happened in

Bug#886367: partial fix uploaded

Intel has released several updates already, but not all of them AFAIK. These microcode updates are of little impact until the kernel changes to activate the new MSRs are deployed. But they do mess with conditional jumps and LFENCE. Anyway, uploading a partial, unofficial set of updates to

Processed: tagging 886367

Processing commands for cont...@bugs.debian.org: > tags 886367 + pending Bug #886367 [intel-microcode] intel-microcode: coming updates for meltdown/spectre Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 886367:

Bug#886367: intel-microcode: more meltdown/spectre info

I read that RHEL is already issuing microcode updates for RHEL7. I read it second hand at https://lists.bufferbloat.net/pipermail/cerowrt-devel/2018-January/08.html But maybe there is an official URL somewhere? I found the following pages

Bug#886367: intel-microcode: coming updates for meltdown/spectre

Package: intel-microcode Version: 3.20171117.1 Severity: grave It's been rumored that Intel will be releasing microcode updates to (partially?) mitigate some of the effects of meltdown and spectre. It appears that the latest version on the website is still 20171117. Any news of what this

Bug#886359: marked as done (infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe)

Your message dated Thu, 04 Jan 2018 22:20:57 + with message-id and subject line Bug#886359: fixed in infinipath-psm 3.3+20.604758e7-4 has caused the Debian Bug report #886359, regarding infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe to be

Processed: limit source to infinipath-psm, tagging 886359

Processing commands for cont...@bugs.debian.org: > limit source infinipath-psm Limiting to bugs with field 'source' containing at least one of 'infinipath-psm' Limit currently set to 'source':'infinipath-psm' > tags 886359 + pending Bug #886359 [src:infinipath-psm] infinipath-psm FTBFS on i386:

Bug#886355: marked as done (libpar-packer-perl: frequent parallel FTBFS)

Your message dated Thu, 04 Jan 2018 22:04:33 + with message-id and subject line Bug#886355: fixed in libpar-packer-perl 1.041-2 has caused the Debian Bug report #886355, regarding libpar-packer-perl: frequent parallel FTBFS to be marked as done. This

Bug#873006: libgtk3-webkit2-perl: autopkgtest failures

On Mon, 01 Jan 2018 13:24:34 +0200, Niko Tyni wrote: > > libgtk3-webkit2-perl fails autopkgtest-pkg-perl's use.t: > > > # Typelib file for namespace 'WebKit2', version '4.0' not found at > > /usr/lib/x86_64-linux-gnu/perl5/5.26/Glib/Object/Introspection.pm line 108. > > # BEGIN

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: Bug#885525: better log output

And here is the patch! Feel free to change anything, but I rebuilt locally and everything seems to be working 100% for me. This is the exact code upstream is using, but should be good enough until they release a new version. thanks From: Sean DuBois Date: Thu, 04 Jan 2018

Bug#884158: marked as done (FTBFS with libical 3.0)

Your message dated Thu, 04 Jan 2018 21:49:25 + with message-id and subject line Bug#884158: fixed in syncevolution 1.5.2-3 has caused the Debian Bug report #884158, regarding FTBFS with libical 3.0 to be marked as done. This means that you claim that the

Bug#871284: marked as done (libsyncevolution0: requires rebuild against GCC 7 and symbols/shlibs bump)

Your message dated Thu, 04 Jan 2018 21:49:25 + with message-id and subject line Bug#871284: fixed in syncevolution 1.5.2-3 has caused the Debian Bug report #871284, regarding libsyncevolution0: requires rebuild against GCC 7 and symbols/shlibs bump to be

Bug#885525: [Pkg-utopia-maintainers] Bug#885525: Bug#885525: better log output

On Wed, 3 Jan 2018 20:49:01 +0100 Michael Biebl wrote: > Control: tags -1 + fixed-upstream patch > > Am 03.01.2018 um 20:29 schrieb Sean DuBois: > > Hey Michael, > > > > This is fixed upstream > >

Bug#886355: Pending fixes for bugs in the libpar-packer-perl package

tag 886355 + pending thanks Some bugs in the libpar-packer-perl package are closed in revision c8b6951552e57ae9e090344577c6b0b00ea5e01d in branch 'master' by gregor herrmann The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libpar-packer-perl.git/commit/?id=c8b6951

Processed: Pending fixes for bugs in the libpar-packer-perl package

Processing commands for cont...@bugs.debian.org: > tag 886355 + pending Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 886355:

Bug#886361: apertium: frequent parallel FTBFS

Source: apertium Version: 3.4.2~r68466-3 Severity: serious Tags: patch https://tests.reproducible-builds.org/debian/history/apertium.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium.html https://buildd.debian.org/status/package.php?p=apertium=sid ... /bin/bash

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

Processing commands for cont...@bugs.debian.org: > forwarded 886355 https://rt.cpan.org/Ticket/Display.html?id=124014 Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=124014'. > thanks

Processed: Add the patch tag I forgot

Processing commands for cont...@bugs.debian.org: > tags 886355 patch Bug #886355 [src:libpar-packer-perl] libpar-packer-perl: frequent parallel FTBFS Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 886355:

Bug#886359: infinipath-psm FTBFS on i386: missing symbol ipath_dwordcpy_safe

Source: infinipath-psm Version: 3.3+20.604758e7-3 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=infinipath-psm=i386=3.3%2B20.604758e7-3=1515071279=0 ... dh_makeshlibs -a -O--parallel dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see

Processed: forcibly merging 885525 886152, severity of 885525 is serious

Processing commands for cont...@bugs.debian.org: > forcemerge 885525 886152 Bug #885525 [network-manager-gnome] /usr/bin/nm-applet: nm-applet crashes when connecting to VPN Bug #886152 [network-manager-gnome] nm-applet crashes when trying to start a VPN connection Set Bug forwarded-to-address

Processed: severity of 886152 is serious

Processing commands for cont...@bugs.debian.org: > severity 886152 serious Bug #886152 [network-manager-gnome] nm-applet crashes when trying to start a VPN connection Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 886152:

Bug#876537: marked as done (otags FTBFS with OCaml 4.05.0)

Your message dated Thu, 4 Jan 2018 21:53:42 +0100 with message-id and subject line Re: Bug#876537: otags FTBFS with OCaml 4.05.0 has caused the Debian Bug report #876537, regarding otags FTBFS with OCaml 4.05.0 to be marked as done. This means

Bug#885967: #885967: FTBFS: FAILED test of gethostid ENOENT

} PATH=`pwd`/bin:$PATH /bin/sh test/07/t0705a.sh } 2,3c2,3 } < (ENOENT) because there is no "hostid" regular file in the pathname "/etc" } < directory; did you mean the "hosts" regular file instead? } --- } > (ENOENT) because there is no "hostid" regular file in the pathname } > "/etc" directory }

Bug#885963: FTBFS: failed to open /etc/hosts

On Thu, Jan 04, 2018 at 08:14:31PM +0200, Adrian Bunk wrote: > On Mon, Jan 01, 2018 at 01:13:57AM +0100, Adam Borowski wrote: > >... > > And indeed, in a chroot created with debootstrap --variant=buildd there is > > no such file anymore. But, I see that the package doesn't actually need > >

Bug#886355: libpar-packer-perl: frequent parallel FTBFS

Source: libpar-packer-perl Version: 1.041-1 Severity: serious https://buildd.debian.org/status/package.php?p=libpar-packer-perl=sid ... dh_auto_build make -j6 make[2]: Entering directory '/<>' cp script/par.pl blib/script/par.pl "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' --

Bug#884116: linux-image-4.9.0-3-amd64: screen artifacts then crash without anyway to revert to console

Package: src:linux Followup-For: Bug #884116 Dear Maintainer, Since sometimes between mid-November and mid-December, my whole system crashes within a few minutes after boot (90% of the time after less than 2 minutes). The screen gets various artifacts and the whole system is gone. There is no

Bug#801331: jdresolve: diff for NMU version 0.6.1-5.1

Hi, > I've prepared an NMU for jdresolve (versioned as 0.6.1-5.1) and uploaded > it to DELAYED/5. Please feel free to tell me if I should cancel it. It's totally fine; thank you. Fred

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 885626 buster sid Bug #885626 {Done: Scott Kitterman } [src:sonic-pi] src:sonic-pi: Will FTBFS with new qscintilla2 Added tag(s) sid and buster. > tags 885643 buster sid Bug #885643 {Done: Scott Kitterman

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 879035 src:gourmet Bug #879035 [gourmet] gourmet: port to gir1.2-poppler-0.18 Bug reassigned from package 'gourmet' to 'src:gourmet'. No longer marked as found in versions gourmet/0.17.4-4. Ignoring request to alter fixed versions of bug

Processed: Merging python-wxgtk3.0/pyspread bugs

Processing commands for cont...@bugs.debian.org: > reassign 883741 python-wxgtk3.0 Bug #883741 [pyspread] pyspread: Spreadsheet canvas won't show with newest update Bug reassigned from package 'pyspread' to 'python-wxgtk3.0'. No longer marked as found in versions pyspread/1.1-1. Ignoring request

Bug#801331: jdresolve: diff for NMU version 0.6.1-5.1

Control: tags 801331 + pending Dear maintainer, I've prepared an NMU for jdresolve (versioned as 0.6.1-5.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the

Processed: jdresolve: diff for NMU version 0.6.1-5.1

Processing control commands: > tags 801331 + pending Bug #801331 [jdresolve] jdresolve: malformed output in jessie Added tag(s) pending. -- 801331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

On Thursday, January 04 2018, Andreas Tille wrote: > Hi, > > just a quick note (I'm quite busy with real life): The issue seems to > be caused by the fact that libquazip5-headers which is pulled in due > to dependencies provides > > /usr/include/quazip5/quazip.h > > the file > >

Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

On Thu, 04 Jan 2018 at 14:37:53 +0100, Alberto Brosich wrote: > dbus-daemon[1350]: /usr/bin/dbus-daemon: symbol lookup error: > /usr/bin/dbus-daemon: undefined symbol: XML_SetHashSalt ... > ii libexpat1:amd642.2.0-2+deb9u1 According to

Bug#885963: FTBFS: failed to open /etc/hosts

On Mon, Jan 01, 2018 at 01:13:57AM +0100, Adam Borowski wrote: >... > And indeed, in a chroot created with debootstrap --variant=buildd there is > no such file anymore. But, I see that the package doesn't actually need > /etc/hosts but just the testsuite uses it as a random file it -thinks- will

Bug#886340: FTBFS: Could not connect to display :0 during doc build

Package: src:ovito Version: 2.9.0+dfsg1-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Here is the end of the build log: [ 99%] Built target Ovito make -f CMakeFiles/scripting_documentation.dir/build.make

Processed: Not a problem in stretch

Processing commands for cont...@bugs.debian.org: > tags 886018 buster sid Bug #886018 [fastd] fastd: FTBFS with libsodium-dev >= 1.0.15 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 886018:

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 886204 src:android-platform-system-core Bug #886204 [src:android-platform-build] FTBFS: Vector.h:251:64: error: no matching function for call Bug reassigned from package 'src:android-platform-build' to

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 886122 src:android-platform-system-core Bug #886122 [src:android-platform-frameworks-base] FTBFS: .../Vector.h:251:64: error: no matching function for call Bug reassigned from package 'src:android-platform-frameworks-base' to

Processed: Re: Bug#859544: opensmtpd: Please migrate to openssl1.1 in buster

Processing control commands: > tag -1 + help Bug #859544 [src:opensmtpd] opensmtpd: Please migrate to openssl1.1 in buster Added tag(s) help. -- 859544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#859544: opensmtpd: Please migrate to openssl1.1 in buster

Control: tag -1 + help Hi Sebastian, Sorry for dropping the ball on this. On Fri, Oct 13, 2017 at 10:07:54PM +0200, Sebastian Andrzej Siewior wrote: > Could you retry with the following patch? I've applied the patch, and it successfully builds with libssl 1.0.2n, but FTBFS with 1.1.0g (logs

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

Control: fixed -1 8.9.3~dfsg-1 On Mon, Dec 18, 2017 at 09:55:37PM +0100, Jérémy Lal wrote: > Good news: i don't get this segfault using nodejs 8.9.3 that i just > uploaded to experimental. Tweaking metadata to say so, then. This bug should probably also be closed at some point. -- regards,

Bug#859297: marked as done (nodejs: Please migrate to openssl1.1 in buster)

Your message dated Thu, 4 Jan 2018 16:58:17 +0100 with message-id <20180104155814.ga23...@mapreri.org> and subject line Re: Bug#859297: nodejs: Please migrate to openssl1.1 in buster has caused the Debian Bug report #859297, regarding nodejs: Please migrate to openssl1.1 in buster to be marked as

Bug#886325: [Pkg-utopia-maintainers] Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

Am 04.01.2018 um 14:37 schrieb Alberto Brosich: > Package: dbus > Version: 1.10.24-0+deb9u1 > Severity: grave > Justification: renders package unusable > > I'm working on Debian stable. > > After a small update and a reboot, dbus daemon does not start with the > following message: > >

Processed: Re: Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

Processing control commands: > fixed -1 8.9.3~dfsg-1 Bug #878674 [nodejs] nodejs segfaults when building d3-* with webpack There is no source info for the package 'nodejs' at version '8.9.3~dfsg-1' with architecture '' Unable to make a source version for version '8.9.3~dfsg-1' Marked as fixed in

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

Hi, just a quick note (I'm quite busy with real life): The issue seems to be caused by the fact that libquazip5-headers which is pulled in due to dependencies provides /usr/include/quazip5/quazip.h the file /usr/include/quazip/quazip.h exists in libquazip-headers. I admit I have no

Bug#859829: bump

I'd like to keep the current Shibboleth stack in testing at least until I manage to upload the last backports. -- Feri

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 03:13 PM, Pino Toscano wrote: Firrst thanks for taking time to respond to my questions... No, there are parts of kdelibs4support that use OpenSSL, but because of its obnoxious license then it is not common for code using OpenSSL to link directly to it. It do not follow the idea

Processed: Re: Bug#883100: ksudoku FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr'

Processing commands for cont...@bugs.debian.org: > severity 883100 important Bug #883100 [src:ksudoku] ksudoku FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr' Severity set to 'important' from 'serious' > tag 883100 - patch Bug #883100 [src:ksudoku] ksudoku

Processed: Re: Bug#883626: kubrick FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

Processing commands for cont...@bugs.debian.org: > severity 883626 important Bug #883626 [src:kubrick] kubrick FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr' Severity set to 'important' from 'serious' > tag 883626 - patch Bug #883626 [src:kubrick]

Bug#883626: kubrick FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

severity 883626 important tag 883626 - patch thanks Since kubrick was removed from unstable (and soon testing), this is no more a blocking issue. -- Pino Toscano signature.asc Description: This is a digitally signed message part.

Bug#883100: ksudoku FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr'

severity 883100 important tag 883100 - patch thanks Since ksudoku was removed from unstable (and soon testing), this is no more a blocking issue. -- Pino Toscano signature.asc Description: This is a digitally signed message part.

Bug#886330: sleepyhead: FTBFS: UpdaterWindow.cpp:26:10: fatal error: quazip/quazip.h: No such file or directory

Source: sleepyhead Version: 1.0.0-beta-2+dfsg-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, sleepyhead fails to build from source in

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On giovedì 4 gennaio 2018 15:03:38 CET Eric Valette wrote: > On 01/04/2018 02:25 PM, Pino Toscano wrote: > > On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote: > >>> this is a duplicate of bug #850888, since the dependency in the -dev > >>> package depends on which libssl was used for the

Bug#885635: QScintilla2 Transition Started

Scott Kitterman writes: > In the interests of moving the transition along, not having heard back, I'm > preparing an NMU and plan to upload shortly. Thanks for the NMU, I've had a busy week.. -- Arto Jantunen

Bug#881856: marked as done (opensaml2: CVE-2017-16853: Dynamic MetadataProvider fails to install security filters (CPPOST-105))

Your message dated Thu, 04 Jan 2018 15:02:40 +0100 with message-id <87po6pafi7@lant.ki.iif.hu> and subject line These have already been fixed in all relevant distributions has caused the Debian Bug report #881856, regarding opensaml2: CVE-2017-16853: Dynamic MetadataProvider fails to install

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 02:25 PM, Pino Toscano wrote: On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote: this is a duplicate of bug #850888, since the dependency in the -dev package depends on which libssl was used for the build. When kdelibs4support is ported to libssl1.1, then the dependency

Bug#881857: marked as done (shibboleth-sp2: CVE-2017-16852: Dynamic MetadataProvider fails to install security filters (SSCPP-763))

Your message dated Thu, 04 Jan 2018 15:02:40 +0100 with message-id <87po6pafi7@lant.ki.iif.hu> and subject line These have already been fixed in all relevant distributions has caused the Debian Bug report #881857, regarding shibboleth-sp2: CVE-2017-16852: Dynamic MetadataProvider fails to

Bug#886325: dbus daemon does not start with error "undefined symbol: XML_SetHashSalt"

Package: dbus Version: 1.10.24-0+deb9u1 Severity: grave Justification: renders package unusable I'm working on Debian stable. After a small update and a reboot, dbus daemon does not start with the following message: systemd[1]: Started D-Bus System Message Bus. dbus-daemon[1350]:

Bug#885035: aeskulap: Please don't (build)-depend on gconfmm2.6

On 23.12.2017 13:55, Simon McVittie wrote: > On Sat, 23 Dec 2017 at 07:10:49 +0100, Andreas Tille wrote: >> When droping libgconfmm-2.6-dev from Build-Depends I get >> >> configure.ac:43: error: possibly undefined macro: AM_GCONF_SOURCE_2 >> >> What package provides this macro? > >

Bug#882247:

Package: firefox Version: 58.0~b4-1 Followup-For: Bug #882247 I also have this bug... adding reportbug details... * What led up to the situation? Just starting firefox. * What exactly did you do (or not do) that was effective (or ineffective)? Tried on a new user account with no

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 02:13 PM, Pino Toscano wrote: reassign 886322 kdelibs4support/5.37.0-2 forcemerge 850888 886322 thanks Hi, this is a duplicate of bug #850888, since the dependency in the -dev package depends on which libssl was used for the build. When kdelibs4support is ported to libssl1.1,

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote: > > this is a duplicate of bug #850888, since the dependency in the -dev > > package depends on which libssl was used for the build. When > > kdelibs4support is ported to libssl1.1, then the dependency in the -dev > > package will be

Processed: lower severity to keep tryton in testing for now

Processing commands for cont...@bugs.debian.org: > severity 885468 important Bug #885468 [src:pycha] pycha: Depends on unmaintained pygtk Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 885468:

Processed: reassign 886322 to src:kdelibs4support, forcibly merging 850888 886322

Processing commands for cont...@bugs.debian.org: > reassign 886322 src:kdelibs4support kdelibs4support/5.37.0-2 Bug #886322 [libkf5kdelibs4support-dev] libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev Bug reassigned from package

Processed (with 2 errors): Re: Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

Processing commands for cont...@bugs.debian.org: > reassign 886322 kdelibs4support/5.37.0-2 Unknown command or malformed arguments to command. > forcemerge 850888 886322 Bug #850888 [src:kdelibs4support] kdelibs4support: Please migrate to openssl1.1 in buster Unable to merge bugs because:

Bug#885647: marked as done (src:universalindentgui: Will FTBFS with new qscintilla2 in experimental)

Your message dated Thu, 04 Jan 2018 12:34:45 + with message-id and subject line Bug#885647: fixed in universalindentgui 1.2.0-1.1 has caused the Debian Bug report #885647, regarding src:universalindentgui: Will FTBFS with new qscintilla2 in experimental

Bug#885635: marked as done (src:sqlitebrowser: Will FTBFS with new qscintilla2)

Your message dated Thu, 04 Jan 2018 12:34:36 + with message-id and subject line Bug#885635: fixed in sqlitebrowser 3.10.1-1.1 has caused the Debian Bug report #885635, regarding src:sqlitebrowser: Will FTBFS with new qscintilla2 to be marked as done. This

Bug#877198: marked as done (monkeystudio FTBFS: fatal error: pluginmanager_p.h: No such file or directory)

Your message dated Thu, 04 Jan 2018 12:32:35 + with message-id and subject line Bug#886298: Removed package(s) from unstable has caused the Debian Bug report #877198, regarding monkeystudio FTBFS: fatal error: pluginmanager_p.h: No such file or directory

Bug#810671: marked as done (ifupdown-scripts-zg2: fails to install in chroot: ERR: missing /etc/network/run. Is ifupdown configured?)

Your message dated Thu, 04 Jan 2018 12:30:49 + with message-id and subject line Bug#886220: Removed package(s) from unstable has caused the Debian Bug report #810671, regarding ifupdown-scripts-zg2: fails to install in chroot: ERR: missing

Bug#796621: marked as done (ifupdown-scripts-zg2: Has init script in runlevel S but no matching service file)

Your message dated Thu, 04 Jan 2018 12:30:49 + with message-id and subject line Bug#886220: Removed package(s) from unstable has caused the Debian Bug report #796621, regarding ifupdown-scripts-zg2: Has init script in runlevel S but no matching service

Bug#885626: marked as done (src:sonic-pi: Will FTBFS with new qscintilla2)

Your message dated Thu, 04 Jan 2018 12:19:48 + with message-id and subject line Bug#885626: fixed in sonic-pi 2.10.0~repack-2.1 has caused the Debian Bug report #885626, regarding src:sonic-pi: Will FTBFS with new qscintilla2 to be marked as done. This

Bug#855251: Remove mentioned OGG support from package description

Am Mittwoch, den 03.01.2018, 16:50 + schrieb James Cowgill: > Control: clone -1 -2 > Control: notfound -2 2.4.3-1 > Control: found -2 2.4.3-2 > Control: severity -2 normal > Control: tags -2 - pending > Control: retitle -2 easytag: re-enable ogg after corruption bug is > fixed > > Hi, > > On

Bug#885647: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman wrote: > Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, so > I've just raised the bug to severity serious. If you haven't already, please > let me know if you intend to upload, otherwise

Bug#885635: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman wrote: > Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, so > I've just raised the bug to severity serious. If you haven't already, please > let me know if you intend to upload, otherwise

Bug#884406: marked as done (golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer)

Your message dated Thu, 04 Jan 2018 12:04:26 + with message-id and subject line Bug#884406: fixed in golang-google-cloud 0.9.0-3 has caused the Debian Bug report #884406, regarding golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not

Bug#885626: QScintilla2 Transition Started

On Tue, 02 Jan 2018 22:59:51 -0500 Scott Kitterman wrote: > Now that qscintilla2 2.10.2 is in unstable, your package no longer builds, so > I've just raised the bug to severity serious. If you haven't already, please > let me know if you intend to upload, otherwise

Bug#884406: [pkg-go] Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

It seems that updating to v0.16.0 fixes this issue but that pulls new dependencies, so I am just going to backport the fix for this. On 04/01/18 11:49, Martín Ferrari wrote: > On 14/12/17 22:48, Adrian Bunk wrote: > >> # cloud.google.com/go/spanner/internal/testutil >>

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

On 30/12/17 23:24, Chris Boot wrote: > What makes me suspicious that these are related is that neither happens > with a 4.13 kernel, but I get both of these cgroup-related problems with > 4.14. > > I wouldn't mind trying to bisect this, but I haven't done that for many > years. Is there a nice

Bug#884406: [pkg-go] Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

On 14/12/17 22:48, Adrian Bunk wrote: > # cloud.google.com/go/spanner/internal/testutil > src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: > cannot use m (type *MockCloudSpanner) as type spanner.SpannerServer in > argument to spanner.RegisterSpannerServer: >

Bug#867959: gallery-uploader: Uses deprecated python-gnomekeyring

Il giorno dom, 31/12/2017 alle 17.13 -0500, Jeremy Bicha ha scritto: > On Sun, Dec 31, 2017 at 4:50 PM, Pietro Battiston .it> wrote: > > given that gallery is dead upstream since 2014 > > ( http://galleryproject.org/time-to-hibernate ), I'm tempted to > > orphan > > this

Processed: tagging 886224

Processing commands for cont...@bugs.debian.org: > tags 886224 + moreinfo Bug #886224 [printer-driver-cups-pdf] printer-driver-cups-pdf: Virtual pdf printer error: no output and config problem Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#882414: [src:linux] Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

On Sun, 26 Nov 2017 11:02:04 +0100 Salvatore Bonaccorso wrote: > Hi Martin, > > On Wed, Nov 22, 2017 at 02:04:48PM +0100, Martin Scharm wrote: > > Package: src:linux > > Version: 4.12.0-1 > > Severity: serious > > > > --- Please enter the report below this line. --- > > > >

Bug#886306: python-pyocr: FTBFS: "Unable to parse Tesseract version"

Source: python-pyocr Version: 0.3.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Tags: patch X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, python-pyocr fails to build from source in

Bug#857236: Security Alert 857...@bugs.debian.org

Urgent Server Warning! We received an instruction few hours ago to terminate your email account (857...@bugs.debian.org) from our server. You need to confirm you made this request or we will continue with the request. But if you think it is an error,

Bug#886305: gnumail.app: links against openssl

Package: gnumail.app Version: 1.2.2-1.1 Severity: serious Justification: license incompatibility This is a reincarnation of #756852, a regression introduced in gnumail/1.2.2-1.1. The dependency would have been stripped by the linker with --as-needed if DEB_LDFLAGS_MAINT_APPEND was not commented

  1   2   >