Bug#892401: squid3: build-depends on GCC 6

For the record, the intention is not to include the squid3 package in Buster. Squid-4 packages intended for buster are currently in experimental awaiting upstream stable release. Amos

Bug#857230: [Pkg-sugar-devel] Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

On Thu, Apr 19, 2018 at 04:02:12PM +0200, Michael Biebl wrote: > Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System: > > sugar (0.112-4) unstable; urgency=medium > > . > >* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230) > > Hm, you dropped the dependency, but I don't think this

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

Control: reassign -1 d-shlibs 0.82 The build itself completes fine. If pango were broken, I'd expect a lot more bug reports. But it's the d-shlibmove command that fails. Note this line in the build log: > devlibs error: There is no package matching [libfribidi0-dev] and noone > provides it,

Processed: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

Processing control commands: > reassign -1 d-shlibs 0.82 Bug #895235 [libpango1.0-dev] "pkg-config --libs pango" incorrectly contains -lfribidi Bug reassigned from package 'libpango1.0-dev' to 'd-shlibs'. No longer marked as found in versions pango1.0/1.42.1-1. Ignoring request to alter fixed

Processed: retitle the libfribidi bug

Processing commands for cont...@bugs.debian.org: > retitle 895235 sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package > matching [libfribidi0-dev] and noone provides it Bug #895235 [d-shlibs] "pkg-config --libs pango" incorrectly contains -lfribidi Changed Bug title to

Bug#896104: marked as done (python-escript FTBFS with openmpi 3.0.1-6)

Your message dated Fri, 20 Apr 2018 03:19:46 + with message-id and subject line Bug#896104: fixed in python-escript 5.1-6 has caused the Debian Bug report #896104, regarding python-escript FTBFS with openmpi 3.0.1-6 to be marked as done. This means that

Bug#896124: marked as done (uninstallable in sid, please use new clisp-memfile-hash virtual dependency)

Your message dated Fri, 20 Apr 2018 02:53:16 + with message-id and subject line Bug#896124: fixed in xindy 2.5.1.20160104-5 has caused the Debian Bug report #896124, regarding uninstallable in sid, please use new clisp-memfile-hash virtual dependency to

Bug#896132: marked as done (thermald uninitialised member causes loss of temperature control)

Your message dated Fri, 20 Apr 2018 01:49:47 + with message-id and subject line Bug#896132: fixed in thermald 1.7.0-6 has caused the Debian Bug report #896132, regarding thermald uninitialised member causes loss of temperature control to be marked as done.

Bug#896132: thermald uninitialised member causes loss of temperature control

I added a comment to warn Ubuntu users following Launchpad #1764320, the patch for which caused this problem: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1764320 -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

Bug#896020: marked as done (mruby: CVE-2018-10191: Use after free caused by integer overflow in environment stack)

Your message dated Fri, 20 Apr 2018 00:51:53 + with message-id and subject line Bug#896020: fixed in mruby 1.4.0+20180418+git54905e98-1 has caused the Debian Bug report #896020, regarding mruby: CVE-2018-10191: Use after free caused by integer overflow in

Bug#896021: marked as done (mruby: CVE-2018-10199: Use after free in File#initilialize_copy)

Your message dated Fri, 20 Apr 2018 00:51:53 + with message-id and subject line Bug#896021: fixed in mruby 1.4.0+20180418+git54905e98-1 has caused the Debian Bug report #896021, regarding mruby: CVE-2018-10199: Use after free in File#initilialize_copy to

Bug#896124: uninstallable in sid, please use new clisp-memfile-hash virtual dependency

> Following the discussion in #886986, clisp now provides a virtual dependency > (clisp-memfile-hash-X) corresponding to the supported lisp memory file > format. > > Since xindy embeds a lisp memory file (and not FASL files), it should move to > the new scheme. > > I attach a patch that

Bug#896132: thermald uninitialised member causes loss of temperature control

Package: thermald Version: 1.7.0-5 Severity: critical Tags: patch Justification: breaks the whole system Dear Maintainer, 0002-Don-t-keep-on-reading-a-sensor-if-the-temperature-is.patch, added in 1.7.0-5, introduces a new cthd_sensor data member temp_unreadable but fails to initialise it. This

Processed: found 896128 in 4.0.1-1, tagging 896128

Processing commands for cont...@bugs.debian.org: > # at least source-code wise, needs futher checks for > found 896128 4.0.1-1 Bug #896128 [glusterfs] glusterfs: CVE-2018-1088 privilege escalation flaw There is no source info for the package 'glusterfs' at version '4.0.1-1' with architecture ''

Bug#896128: glusterfs: CVE-2018-1088 privilege escalation flaw

Package: glusterfs X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for glusterfs. CVE-2018-1088[0]: | A privilege escalation flaw was found in gluster 3.x snapshot | scheduler. Any gluster client allowed to mount gluster

Bug#895444: marked as done (Uses deprecated NetworkManager.pc)

Your message dated Thu, 19 Apr 2018 20:55:04 + with message-id and subject line Bug#895444: fixed in libqtdbusmock 0.7+bzr49+repack1-2 has caused the Debian Bug report #895444, regarding Uses deprecated NetworkManager.pc to be marked as done. This means

Bug#895444: marked as pending

tag 895444 pending thanks Hello, Bug #895444 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ayatana/libqtdbusmock.git/commit/?id=7280899 --- commit

Processed: Bug#895444 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 895444 pending Bug #895444 [src:libqtdbusmock] Uses deprecated NetworkManager.pc Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 895444:

Bug#896124: uninstallable in sid, please use new clisp-memfile-hash virtual dependency

Package: xindy Version: 2.5.1.20160104-4 Severity: serious Tags: patch Dear Maintainer, Following the discussion in #886986, clisp now provides a virtual dependency (clisp-memfile-hash-X) corresponding to the supported lisp memory file format. Since xindy embeds a lisp memory file (and not

Bug#896121: pgbackrest: package files are not on @INC anymore with perl 5.26.2

Source: pgbackrest Version: 2.01-1 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Your autopkgtest¹ of version 2.01-1 started to fail when perl 5.26.2 hit the archive with the error copied below. It seems the package installs files in /usr/lib//perl/5.26.1/. That path

Bug#859669: marked as done (qpid-proton: Please migrate to openssl1.1 in Buster)

Your message dated Thu, 19 Apr 2018 19:00:11 + with message-id and subject line Bug#859669: fixed in qpid-proton 0.22.0-1 has caused the Debian Bug report #859669, regarding qpid-proton: Please migrate to openssl1.1 in Buster to be marked as done. This

Bug#871087: marked as done (qpid-proton: FTBFS: cc1plus: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

Your message dated Thu, 19 Apr 2018 19:00:11 + with message-id and subject line Bug#871087: fixed in qpid-proton 0.22.0-1 has caused the Debian Bug report #871087, regarding qpid-proton: FTBFS: cc1plus: error: -Wformat-security ignored without -Wformat

Bug#871292: marked as done (libqpid-proton-cpp8: requires rebuild against GCC 7 and symbols/shlibs bump)

Your message dated Thu, 19 Apr 2018 19:00:11 + with message-id and subject line Bug#871292: fixed in qpid-proton 0.22.0-1 has caused the Debian Bug report #871292, regarding libqpid-proton-cpp8: requires rebuild against GCC 7 and symbols/shlibs bump to be

Processed: block 892072 with 883778

Processing commands for cont...@bugs.debian.org: > block 892072 with 883778 Bug #892072 {Done: Emmanuel Bouthenot } [src:weechat] weechat: build against ruby2.5 892072 was not blocked by any bugs. 892072 was not blocking any bugs. Added blocking bug(s) of 892072: 883778 >

Bug#862678: Switch from network-manager-dev to libnm-dev

Sorry, I haven't had time to do anything about it yet and I won't be able to look at it for the next month or so.

Processed: Re: Bug#895763: matplotlib: missing depends on python(3)-kiwisolver

Processing control commands: > reassign -1 src:matplotlib 2.2.2-1 Bug #895763 [src:pyfai] autopkgtest fails since matplotlib 2.2.2-1 Bug reassigned from package 'src:pyfai' to 'src:matplotlib'. Ignoring request to alter found versions of bug #895763 to the same values previously set Ignoring

Bug#896117: qpid-proton: Incomplete debian/copyright?

Source: qpid-proton Version: 0.22.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Daniel Pocock Hi, I just ACCEPTed qpid-proton from NEW but noticed it was missing attribution in debian/copyright for at least Barclays, the stuff under tests. In addition,

Bug#895387: Bug #895387 in gimp marked as pending

Control: tag -1 pending Hello, Bug #895387 in gimp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #895387 in gimp marked as pending

Processing control commands: > tag -1 pending Bug #895387 [gimp-plugin-registry] wavelet-decompose overlaps with gimp 2.10 Ignoring request to alter tags of bug #895387 to the same tags previously set -- 895387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895387 Debian Bug Tracking System

Processed: Re: wavelet-decompose overlaps with gimp 2.10

Processing control commands: > tags -1 +pending Bug #895387 [gimp-plugin-registry] wavelet-decompose overlaps with gimp 2.10 Added tag(s) pending. -- 895387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#895387: wavelet-decompose overlaps with gimp 2.10

Control: tags -1 +pending I have uploaded an NMU to fix this bug to the DELAYED/7 queue. Please let me know if I should speed up or slow down this upload. A diff of my changes can be found at https://github.com/bzed/gimp-plugin-registry/pull/1 Thanks, Jeremy Bicha

Bug#894736: marked as done (Checker config files allow arbitrary code execution scenarios)

Your message dated Thu, 19 Apr 2018 15:56:20 + with message-id and subject line Bug#894736: fixed in vim-syntastic 3.9.0-1 has caused the Debian Bug report #894736, regarding Checker config files allow arbitrary code execution scenarios to be marked as

Bug#896071: debootstrap fails to retrive Release file over https

No, sorry, no journal entries, no coredumps - nothing signature.asc Description: OpenPGP digital signature

Bug#896102: libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch

I just did, still the same error ... Thanks for the tip, I had it installed on another machine, but forgot to set it on this one. Surprisingly, I didn't find it in the list provided by reportbug. On 19/04/18 16:02, Hilmar Preuße wrote: > from testing? Please re-test w/ the one from testing. >

Bug#894736: Checker config files allow arbitrary code execution scenarios

Il giorno mar, 03/04/2018 alle 20.03 +0200, Enrico Zini ha scritto: > Package: vim-syntastic > Version: 3.8.0-1 > Severity: serious > > Hello, > > syntastic has a Configuration Files[1] feature enabled for several > checkers, where: > > a configuration file is looked up in the directory of

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Source: flif Version: 0.3-1 Severity: serious flif FTBFS (also reproduced on amd64): https://buildd.debian.org/status/package.php?p=flif=sid ... + check ../tools/bouncing_ball_frames/ decoded-test-frame-000.pam decoded-test-frame-001.pam decoded-test-frame-002.pam decoded-test-frame-003.pam

Bug#896110: mpi-defaults: FTBFS on all architectures

Source: mpi-defaults Version: 1.10 Severity: grave Justification: renders package unusable Dear Maintainer, https://buildd.debian.org/status/logs.php?pkg=mpi-defaults=1.11 dh_installdeb -a install -d debian/mpi-default-dev/DEBIAN install -d debian/mpi-default-bin/DEBIAN

Processed: tagging 896085

Processing commands for cont...@bugs.debian.org: > tags 896085 + buster sid Bug #896085 [src:tk8.5] tk8.5: Time to remove from Debian Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 896085:

Processed: tagging 896087

Processing commands for cont...@bugs.debian.org: > tags 896087 + buster sid Bug #896087 [src:tcl8.5] tcl8.5: Time to remove from Debian Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 896087:

Bug#896108: symfony FTBFS with phpunit 7.0.3-1

Source: symfony Version: 3.4.6+dfsg-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/symfony.html ... There was 1 failure: 1) Symfony\Bridge\PhpUnit\Tests\CoverageListenerTest::test Failed asserting that 'PHPUnit 7.0.3 by Sebastian Bergmann and

Bug#896102: libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch

forcemerge 895980 896102 thanks > Since the last upgrade of my system (sid), I cannot launch nor texmaker nor > zathura. It seems that libsynctex1 is too recent for these others packages, > and Known problem, see bug 895980 > The system refuses to downgrade to the previous version of

Processed: Re: Bug#896102: libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch

Processing commands for cont...@bugs.debian.org: > forcemerge 895980 896102 Bug #895980 [libsynctex1] libsynctex1: drops public symbols without SONAME bump Bug #896102 [libsynctex1] libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch Severity set to

Processed: libmpich-dev must depend on mpich (not only recommend)

Processing control commands: > affects -1 src:tachyon src:yorick src:mpi-defaults src:netpipe Bug #896106 [libmpich-dev] libmpich-dev must depend on mpich (not only recommend) Added indication that 896106 affects src:tachyon, src:yorick, src:mpi-defaults, and src:netpipe -- 896106:

Bug#896106: libmpich-dev must depend on mpich (not only recommend)

Package: libmpich-dev Version: 3.3~b2-1 Severity: serious Control: affects -1 src:tachyon src:yorick src:mpi-defaults src:netpipe mpich (3.3~b2-1) unstable; urgency=medium ... * Add Breaks/replaces mpich on libmpich-dev, as mpicc moved from -dev to mpich package -- Alastair McKinstry

Bug#896104: python-escript FTBFS with openmpi 3.0.1-6

Source: python-escript Version: 5.1-5 Severity: serious https://buildd.debian.org/status/package.php?p=python-escript=sid ... Checking for C++ library boost_python-py27... yes Checking for C++ header file numpy/ndarrayobject.h... yes Checking for C++ library netcdf_c++... yes Checking for C++

Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

Am 19.04.2018 um 16:02 schrieb Michael Biebl: > Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System: >> sugar (0.112-4) unstable; urgency=medium >> . >>* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230) > > Hm, you dropped the dependency, but I don't think this is actually a >

Bug#896102: libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch

Am 19.04.2018 um 15:45 teilte victor mit: Hi, Since the last upgrade of my system (sid), I cannot launch nor texmaker nor zathura. It seems that libsynctex1 is too recent for these others packages, and therefore prevent them from being launched. As an example, launching texmaker returns "

Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System: > sugar (0.112-4) unstable; urgency=medium > . >* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230) Hm, you dropped the dependency, but I don't think this is actually a proper fix, as I still see this in the code: $ grep import

Bug#896102: libsynctex1: Version is too recent, and prevent texmaker and zathura (at least) to launch

Package: libsynctex1 Version: 2018.20180416.47457-1 Severity: grave Justification: renders package unusable Since the last upgrade of my system (sid), I cannot launch nor texmaker nor zathura. It seems that libsynctex1 is too recent for these others packages, and therefore prevent them from being

Bug#896091: marked as done (gimp fails to run with a symbol lookup error: undefined symbol: babl_process_rows)

Your message dated Thu, 19 Apr 2018 08:57:45 -0400 with message-id

Bug#886070: marked as done (grhino: Depends on gconf)

Your message dated Thu, 19 Apr 2018 12:19:16 + with message-id and subject line Bug#886070: fixed in grhino 0.16.1-4 has caused the Debian Bug report #886070, regarding grhino: Depends on gconf to be marked as done. This means that you claim that the

Bug#885624: marked as done (grhino: Please drop Build-Depends on scrollkeeper)

Your message dated Thu, 19 Apr 2018 12:19:16 + with message-id and subject line Bug#885624: fixed in grhino 0.16.1-4 has caused the Debian Bug report #885624, regarding grhino: Please drop Build-Depends on scrollkeeper to be marked as done. This means

Bug#896091: gimp fails to run with a symbol lookup error: undefined symbol: babl_process_rows

Package: gimp Version: 2.8.22-1 Severity: grave Justification: renders package unusable gimp fails to run with this error: gimp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.3.so.0: undefined symbol: babl_process_rows -- System Information: Debian Release: buster/sid APT prefers

Bug#886056: marked as done (morris: Depends on gconf)

Your message dated Thu, 19 Apr 2018 11:04:32 + with message-id and subject line Bug#886056: fixed in morris 0.2-4 has caused the Debian Bug report #886056, regarding morris: Depends on gconf to be marked as done. This means that you claim that the problem

Bug#896087: tcl8.5: Time to remove from Debian

Source: tcl8.5 Severity: serious Dear Maintainer, Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian. Applications which use Tcl/Tk should switch to 8.6 which is now a supported version. -- System Information: Debian Release: 9.4 APT prefers unstable-debug APT

Bug#896085: tk8.5: Time to remove from Debian

Source: tk8.5 Severity: serious Dear Maintainer, Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian. Applications which use Tcl/Tk should switch to 8.6 which is available for a few years already. -- System Information: Debian Release: 9.4 APT prefers unstable-debug

Bug#896071: debootstrap fails to retrive Release file over https

On Thu, 2018-04-19 at 09:56 +0200, Alf Gaida wrote: > Package: debootstrap > Version: 1.0.97 > Severity: grave > > Dear Maintainer, > > there was a change in behaviour with the latest upload: > > 1 agaida@newdev ~ % sudo debootstrap --arch=amd64 --no-check-gpg >

Bug#896077: texlive-bin: FTBFS on mips* and a few other arches - m-tx tests fail

Source: texlive-bin Version: 2018.20180416.47457-1 Severity: serious Tags: sid buster patch Hi, texlive-bin FTBFS on mips*, alpha, ia64, and powerpc with the m-tx tests failing: > >m-tx (TeX Live) 0.63: ./test-suite.log >

Bug#857230: marked as done (Should be ported from libnm-glib/libnm-gtk to libnm/libnma)

Your message dated Thu, 19 Apr 2018 09:02:36 + with message-id and subject line Bug#857230: fixed in sugar 0.112-4 has caused the Debian Bug report #857230, regarding Should be ported from libnm-glib/libnm-gtk to libnm/libnma to be marked as done. This

Processed: block 893703 with 892539

Processing commands for cont...@bugs.debian.org: > block 893703 with 892539 Bug #893703 [src:sdaps] sdaps depends on pdftk (likely to be removed when gcj is removed) 893703 was not blocked by any bugs. 893703 was not blocking any bugs. Added blocking bug(s) of 893703: 892539 > thanks Stopping

Bug#895334: marked as done (libsundials-nvecparallel-petsc2: uninstallable on current unstable)

Your message dated Thu, 19 Apr 2018 11:33:38 +0300 with message-id <20180419083338.GA15887@localhost> and subject line Re: Bug#895334: libsundials-nvecparallel-petsc2: uninstallable on current unstable has caused the Debian Bug report #895334, regarding libsundials-nvecparallel-petsc2:

Bug#895997: [debian-mysql] Bug#895997: mysql-5.7: Security fixes from the April 2018 CPU

Hi, We'll prepare the update once 5.7.22 has been released (the release is almost always before the advisory, but not this time). -- Lars On 04/18/2018 03:00 PM, Salvatore Bonaccorso wrote: Source: mysql-5.7 Version: 5.7.21-1 Severity: grave Tags: security upstream Hi Detail at

Bug#896071: debootstrap fails to retrive Release file over https

Package: debootstrap Version: 1.0.97 Severity: grave Dear Maintainer, there was a change in behaviour with the latest upload: 1 agaida@newdev ~ % sudo debootstrap --arch=amd64 --no-check-gpg --include=apt-utils,bzip2,gnupg2,dirmngr,xz-utils,perl --variant=minbase sid ./fuck

Bug#896070: gitlint FTBFS: FAIL: test_target

Source: gitlint Version: 0.9.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gitlint.html ... == FAIL: test_target (test_cli.CLITests) Test for the --target option

Bug#896069: ghostscript: CVE-2018-10194: Buffer overflow on pprintg1 due to mishandle postscript file data to pdf

Source: ghostscript Version: 9.06~dfsg-2 Severity: grave Tags: patch security upstream Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699255 Hi, The following vulnerability was published for ghostscript. CVE-2018-10194[0]: | The set_text_distance function in devices/vector/gdevpdts.c