Processed: Re: openjpeg2: FTBFS: cd obj-x86_64-linux-gnu && make -j8 -Oline returned exit code 2

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 873997 899126 Bug #873997 [src:openjpeg2] FTBFS with Java 9 due to -source/-target only Bug #899126 [src:openjpeg2] openjpeg2: FTBFS: cd obj-x86_64-linux-gnu && make -j8 -Oline returned exit code 2 Marked as found in versions openjpeg2/2.1.2-1.3. Added ta

Bug#899126: openjpeg2: FTBFS: cd obj-x86_64-linux-gnu && make -j8 -Oline returned exit code 2

2018-05-19 Thread Juhani Numminen
Control: forcemerge 873997 899126 On Sat, 19 May 2018 16:58:33 +0200 Dominic Hargreaves wrote: > When testing packages against the upcoming release of perl, we found > an unrelated FTBFS on a clean sid chroot: ... > [ 57%] Built target openjp2_static > make[2]: Leaving directory '/<>/obj-x86_64

Bug#896616: marked as done (sfepy FTBFS with sphinx 1.7.2)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 06:32:38 + with message-id and subject line Bug#896616: fixed in sfepy 2018.1-1 has caused the Debian Bug report #896616, regarding sfepy FTBFS with sphinx 1.7.2 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#882913: marked as done (php-react-promise FTBFS with phpunit 6.4.4-2)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 06:31:02 + with message-id and subject line Bug#882913: fixed in php-react-promise 2.5.1-1 has caused the Debian Bug report #882913, regarding php-react-promise FTBFS with phpunit 6.4.4-2 to be marked as done. This means that you claim that the problem has

Bug#896485: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 06:31:18 + with message-id and subject line Bug#896485: fixed in pyfr 1.5.0-2 has caused the Debian Bug report #896485, regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive' to be marked as done. This means that you claim that the pro

Bug#892188: marked as done (foodcritic: FTBFS and Debci failure with Ruby 2.5)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 06:27:18 + with message-id and subject line Bug#892188: fixed in foodcritic 13.1.1-1 has caused the Debian Bug report #892188, regarding foodcritic: FTBFS and Debci failure with Ruby 2.5 to be marked as done. This means that you claim that the problem has b

Bug#899157: gstreamer1.0: FTBFS on every architecture

2018-05-19 Thread Boyuan Yang
On Sun, 20 May 2018 12:01:36 +0800 Boyuan Yang <073p...@gmail.com> wrote: > Source: gstreamer1.0 > Version: 1.14.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Source package gstreamer1.0 FTBFS on all architectures according to buildd > logs: > > https:/

Bug#897526: marked as done (4ti2: FTBFS: pdflatex fails)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 06:20:04 + with message-id and subject line Bug#897526: fixed in 4ti2 1.6.7+ds-3 has caused the Debian Bug report #897526, regarding 4ti2: FTBFS: pdflatex fails to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#899159: marked as done ([numpy/grave] Incorrect Memory offset in numpy.uint8 arrays)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 05:53:21 + with message-id <20180520055321.GB12306@Asuna> and subject line closing has caused the Debian Bug report #899159, regarding [numpy/grave] Incorrect Memory offset in numpy.uint8 arrays to be marked as done. This means that you claim that the proble

Bug#899159: Acknowledgement ([numpy/grave] Incorrect Memory offset in numpy.uint8 arrays)

2018-05-19 Thread Lumin
Sorry, I made a stupid mistake. uint8 ranges from 0 to 255. signature.asc Description: PGP signature

Bug#899159: [numpy/grave] Incorrect Memory offset in numpy.uint8 arrays

2018-05-19 Thread Lumin
Package: python3-numpy Version: 1:1.14.3-2 Severity: grave X-Debbugs-CC: debian-scie...@lists.debian.org Dear Numpy maintainers, As a student/researcher, I cannot bear any library that *SILENTLY* produces totally wrong result. This time numpy just triggered me, and I wish you can understand that

Bug#899157: gstreamer1.0: FTBFS on every architecture

2018-05-19 Thread Boyuan Yang
Source: gstreamer1.0 Version: 1.14.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, Source package gstreamer1.0 FTBFS on all architectures according to buildd logs: https://buildd.debian.org/status/package.php?p=gstreamer1.0 The error information in log shows: dh_au

Processed: severity of 899117 is serious

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 899117 serious Bug #899117 [gnome-music] gnome-music: missing dependency gir1.2-goa-1.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 899117: https://bugs.debi

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

2018-05-19 Thread Hideki Yamane
On Sat, 19 May 2018 20:18:17 +0200 Philipp Kern wrote: > You local'ed from and dest and now don't pass it anymore to > wgetprogress. How does this work? It is passed to wget via $@ -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#895226: marked as done (FTBFS on amd64 in testing/unstable - a number of tests failures)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sun, 20 May 2018 00:43:06 +0200 with message-id <20180519224306.rdbr75nvigeql...@elgar.kardiogramm.net> and subject line Re: Bug#895226: FTBFS on amd64 in testing/unstable - a number of tests failures has caused the Debian Bug report #895226, regarding FTBFS on amd64 in testing/

Bug#898433: FTBFS: README.md -> README.rst

2018-05-19 Thread Lee Garrett
Hi Daniel, I've fixed it again. However, I'm not sure how this FTBFS for you. It built fine before, and also on the buildds. Maybe you have some setting that turns lintian warnings into errors? Regards, Lee On 18/05/18 20:55, Harlan Lieberman-Berg wrote: > Oh, I see what's happening. > > Lee, c

Processed: [src:sphinx-rtd-theme] This bug is serious

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #892993 [src:sphinx-rtd-theme] sphinx-rtd-theme CSS is not properly rebuilt from source Severity set to 'serious' from 'important' -- 892993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892993 Debian Bug Tracking System Contact ow...@

Processed: Re: FTBFS: Can't exec "gtkdocize": No such file or directory

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 gstreamer1.0: run gtkdocize during build Bug #899116 [src:gstreamer1.0] FTBFS: Can't exec "gtkdocize": No such file or directory Changed Bug title to 'gstreamer1.0: run gtkdocize during build' from 'FTBFS: Can't exec "gtkdocize": No such file or director

Bug#899116: FTBFS: Can't exec "gtkdocize": No such file or directory

2018-05-19 Thread Simon McVittie
Control: retitle -1 gstreamer1.0: run gtkdocize during build Control: severity -1 wishlist On Sat, 19 May 2018 at 13:08:12 +0100, Simon McVittie wrote: > Recent versions of dh-autoreconf automatically run gtkdocize if gtk-doc > is found in configure.ac. This caused gstreamer1.0/1.14.1-1 to FTBFS o

Bug#898916: marked as done (dh-autoreconf: Unconditionally invokes gtkdocize without dependency)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 20:40:23 + with message-id and subject line Bug#898916: fixed in dh-autoreconf 19 has caused the Debian Bug report #898916, regarding dh-autoreconf: Unconditionally invokes gtkdocize without dependency to be marked as done. This means that you claim that th

Bug#899062: marked as done (chezscheme: FTBFS on armhf armel)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 20:40:17 + with message-id and subject line Bug#899062: fixed in chezscheme 9.5+dfsg-4 has caused the Debian Bug report #899062, regarding chezscheme: FTBFS on armhf armel to be marked as done. This means that you claim that the problem has been dealt with.

Bug#898630: enigmail: efail attack against enigmail

2018-05-19 Thread Carsten Schoenert
Hello Daniel, On Wed, May 16, 2018 at 01:47:45PM +0200, Carsten Schoenert wrote: > I guess the "only" problem with enigmail is the recent package version > isn't available in unstable/testing. The main issue of Efail in Enigmail > is fixed since Enigmail 2.0.0 > > https://sourceforge.net/p/enig

Bug#895492: marked as done (tiemu FTBFS: error: macro "abort" passed 1 arguments, but takes just 0)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 19:49:46 + with message-id and subject line Bug#895492: fixed in tiemu 3.04~git20110801-nogdb+dfsg-2 has caused the Debian Bug report #895492, regarding tiemu FTBFS: error: macro "abort" passed 1 arguments, but takes just 0 to be marked as done. This means

Processed: Bug #898916 in dh-autoreconf marked as pending

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #898916 [dh-autoreconf] dh-autoreconf: Unconditionally invokes gtkdocize without dependency Added tag(s) pending. -- 898916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898916 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#898916: Bug #898916 in dh-autoreconf marked as pending

2018-05-19 Thread jak
Control: tag -1 pending Hello, Bug #898916 in dh-autoreconf 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: https://salsa.debian.org/debian/dh-autoreconf/commit/9f66b177dfcb5a757493721

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

2018-05-19 Thread Philipp Kern
On 19.05.2018 07:14, Hideki Yamane wrote: > On Mon, 14 May 2018 00:48:53 +0200 > Philipp Kern wrote: >> any new about incorporating Raphael's suggestion? There's still a grave >> bug opened against debootstrap right now (on a version that is in testing). > > Sorry for late reply, revert previous

Bug#898433: marked as done (FTBFS: README.md -> README.rst)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 18:04:39 + with message-id and subject line Bug#898433: fixed in ansible 2.5.3+dfsg-2 has caused the Debian Bug report #898433, regarding FTBFS: README.md -> README.rst to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#899135: always includes manpages in first binary package being built, resulting in fileconflicts

2018-05-19 Thread Daniel Baumann
tag 899135 + patch thanks Here's the patch. Regards, Daniel commit c434b390682deb2140980526693bfb6c39195244 Author: Daniel Baumann Date: Sat May 19 19:55:35 2018 +0200 Correcting dh_installman in rules to install manapages into the powerline package only (Closes: #899135). Signed

Processed: Re: always includes manpages in first binary package being built, resulting in fileconflicts

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 899135 + patch Bug #899135 [powerline] always includes manpages in first binary package being built, resulting in fileconflicts Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 899135: http

Bug#899135: always includes manpages in first binary package being built, resulting in fileconflicts

2018-05-19 Thread Daniel Baumann
Package: powerline Version: 2.6-1 Severity: serious Hi, thank you for maintaining powerline in debian. When locally rebuilding the package, I found the following issue: * dh_installman in rules is called unconditionally wrt/ to which package it acts upon. that means that debhelper chooses

Bug#898465: marked as done (ICU must not migrate to testing before the boost ABI breakage is resolved)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 19:51:28 +0200 with message-id <7da84910-ac19-773d-26ac-bc1165b8d...@debian.org> and subject line Re: ICU transition: ICU version is part of the boost ABI has caused the Debian Bug report #898465, regarding ICU must not migrate to testing before the boost ABI bre

Processed: reopening 899062

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 899062 Bug #899062 {Done: Göran Weinholt } [src:chezscheme] chezscheme: FTBFS on armhf armel 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Processed: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 +patch Bug #899128 [kdepim] Limit CVE-2017-17689 (EFAIL) for kmail Added tag(s) patch. -- 899128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#899128: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

2018-05-19 Thread Sandro Knauß
Control: tags -1 +patch Hey, I now created a debdiff for kdepim. The patch depdends on the new symbol that was added in new messageviewer (see #899127). hefeediff -Nru kdepim-16.04.3/debian/changelog kdepim-16.04.3/debian/changelog --- kdepim-16.04.3/debian/changelog 2017-06-17 12:12:03.000

Bug#898883: marked as done (libtf2-kdl-dev: pkgconfig and cmake files refer to non-existing liborocos-kdl.so.1.3.1)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 17:05:09 + with message-id and subject line Bug#898883: fixed in orocos-kdl 1.4.0-4 has caused the Debian Bug report #898883, regarding libtf2-kdl-dev: pkgconfig and cmake files refer to non-existing liborocos-kdl.so.1.3.1 to be marked as done. This means

Bug#899133: FTBFS on Architecture:all

2018-05-19 Thread Lumin
Package: caffe-cpu Version: 1.0.0-7 Severity: serious d/rules will install a file that won't be built during an arch-indep build. That's the root of this FTBFS.

Processed: forcibly merging 898501 899124

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 898501 899124 Bug #898501 [fonts-font-awesome] Broken symlinks Bug #899124 [fonts-font-awesome] fonts-font-awesome: completely breaks web applications, with no notice 898920 was blocked by: 898501 898920 was not blocking any bugs. Adde

Bug#898883: libtf2-kdl-dev: pkgconfig and cmake files refer to non-existing liborocos-kdl.so.1.3.1

2018-05-19 Thread Jochen Sprickerhof
Control: reassign -1 liborocos-kdl-dev * Adrian Bunk [2018-05-17 21:09]: Hardcoding this part of the filename that is not part of the soname in the cmake file is simply wrong, and after a rebuild it would be expected that the same bug would hit again with 1.4.1. This is actually in /usr/share

Processed: Re: Bug#898883: libtf2-kdl-dev: pkgconfig and cmake files refer to non-existing liborocos-kdl.so.1.3.1

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 liborocos-kdl-dev Bug #898883 [libtf2-kdl-dev] libtf2-kdl-dev: pkgconfig and cmake files refer to non-existing liborocos-kdl.so.1.3.1 Bug reassigned from package 'libtf2-kdl-dev' to 'liborocos-kdl-dev'. No longer marked as found in versions ros-geometry2

Bug#899130: stunnel4: FTBFS: tests failing returned exit code 2

2018-05-19 Thread Dominic Hargreaves
Source: stunnel4 Version: 3:5.44-1 Severity: serious Justification: FTBFS User: debian-p...@lists.debian.org Usertags: hh2018 When testing packages against the upcoming release of perl, we found an unrelated FTBFS on a clean sid chroot: ./make_test Sat May 19 16:06:30 UTC 2018 stunnel 5.44 on x86

Bug#899129: prime-phylo: FTBFS: cd obj-x86_64-linux-gnu && make -j8 -Oline returned exit code 2

2018-05-19 Thread Dominic Hargreaves
Source: prime-phylo Version: 1.0.11-4 Severity: serious Justification: FTBFS User: debian-p...@lists.debian.org Usertags: hh2018 When testing packages against the upcoming release of perl, we found an unrelated FTBFS on a clean sid chroot: cd /<>/obj-x86_64-linux-gnu/src/cxx/libraries/prime && /

Processed: Added patch tag

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 899127 +patch Bug #899127 [kf5-messagelib] Limit CVE-2017-17689 (EFAIL) for kmail Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 899127: https://bugs.debian.org/cgi-bin/bugreport

Bug#898651: marked as done (fakemachine: missing dependencies)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:50:52 + with message-id and subject line Bug#898651: fixed in golang-github-go-debos-fakemachine 0.0~git20180517.7d8d48a-1 has caused the Debian Bug report #898651, regarding fakemachine: missing dependencies to be marked as done. This means that you cl

Bug#898650: marked as done (golang-github-go-debos-fakemachine: non-amd64 binaries are unusable)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:50:52 + with message-id and subject line Bug#898650: fixed in golang-github-go-debos-fakemachine 0.0~git20180517.7d8d48a-1 has caused the Debian Bug report #898650, regarding golang-github-go-debos-fakemachine: non-amd64 binaries are unusable to be marke

Bug#899127: kf5-messagelib: Limit CVE-2017-17689 (EFAIL) even more for kmail

2018-05-19 Thread Sandro Knauß
Hey, I now created a debdiff for kf5-messagelib. This patch touches the public ABI and adds one function, but this should not be a problem. Should I update the messageveiwer.symbols, too? And what I should add there, as there should not been Debian revision added. hefeediff -Nru kf5-messagelib

Processed: Limit CVE-2017-17689 (EFAIL) even more for kmail

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 898634 -1 Bug #898634 [src:kmail] kmail: efail attack against S/MIME Bug 898634 cloned as bug 899128 > reassign -1 kdepim Bug #899128 [src:kmail] kmail: efail attack against S/MIME Bug reassigned from package 'src:kmail' to 'kdepim'. Ignorin

Bug#899114: marked as done (xye.xpm is in both xye and xye-data)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:34:35 + with message-id and subject line Bug#899114: fixed in xye 0.12.2+dfsg-7 has caused the Debian Bug report #899114, regarding xye.xpm is in both xye and xye-data to be marked as done. This means that you claim that the problem has been dealt with.

Bug#897362: marked as done (wayland: Incomplete debian/copyright?)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:32:53 + with message-id and subject line Bug#897362: fixed in wayland 1.15.0-2 has caused the Debian Bug report #897362, regarding wayland: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem has been dealt with.

Bug#898631: marked as done (thunderbird: efail attack against S/MIME and PGP/MIME)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:31:56 + with message-id and subject line Bug#898631: fixed in thunderbird 1:52.8.0-1 has caused the Debian Bug report #898631, regarding thunderbird: efail attack against S/MIME and PGP/MIME to be marked as done. This means that you claim that the proble

Bug#891596: marked as done (CVE-2018-7409)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:32:27 + with message-id and subject line Bug#891596: fixed in unixodbc 2.3.6-0.1 has caused the Debian Bug report #891596, regarding CVE-2018-7409 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Processed (with 1 error): Limit CVE-2017-17689 (EFAIL) even more for kmail

2018-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 898634 -1 Bug #898634 [src:kmail] kmail: efail attack against S/MIME Bug 898634 cloned as bug 899127 > reassign -1 kf5-messagelib Bug #899127 [src:kmail] kmail: efail attack against S/MIME Bug reassigned from package 'src:kmail' to 'kf5-mess

Bug#896774: marked as done (python-enigma: missing build dependency on python3-distutils)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:23:00 + with message-id and subject line Bug#896774: fixed in python-enigma 0.1-2 has caused the Debian Bug report #896774, regarding python-enigma: missing build dependency on python3-distutils to be marked as done. This means that you claim that the pr

Bug#898369: marked as done (boost: ICU version used is part of the ABI)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 15:05:35 + with message-id and subject line Bug#898369: fixed in boost1.62 1.62.0+dfsg-5.1 has caused the Debian Bug report #898369, regarding boost: ICU version used is part of the ABI to be marked as done. This means that you claim that the problem has be

Bug#899126: openjpeg2: FTBFS: cd obj-x86_64-linux-gnu && make -j8 -Oline returned exit code 2

2018-05-19 Thread Dominic Hargreaves
Source: openjpeg2 Version: 2.3.0-1 Severity: serious Justification: FTBFS User: debian-p...@lists.debian.org Usertags: hh2018 When testing packages against the upcoming release of perl, we found an unrelated FTBFS on a clean sid chroot: /usr/bin/ar qc ../../../bin/libopenjp2.a CMakeFiles/openjp

Bug#823510: marked as done (Useless in Debian)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 14:33:47 + (UTC) with message-id and subject line php-react-promise: r-dependency of movim-pod has caused the Debian Bug report #823510, regarding Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

2018-05-19 Thread Antonio Terceiro
Package: fonts-font-awesome Version: 5.0.10-1 Severity: grave Font-Awesome version completely changed everything, and any web applications that use it are now broken unless they go through some manual intervention. https://fontawesome.com/how-to-use/upgrading-from-4 As a maintainer of multiple p

Bug#899123: nuxwdog: FTBFS: javah missing with openjdk-10

2018-05-19 Thread Dominic Hargreaves
Source: nuxwdog Version: 1.0.3-4 Severity: serious Justification: FTBFS User: debian-p...@lists.debian.org Usertags: hh2018 When testing packages against the upcoming release of perl, we found an unrelated FTBFS on a clean sid chroot: BUILD FAILED /<>/build.xml:85: Execute failed: java.io.IOExcep

Bug#862373: Bug#862475: The State of the YAML

2018-05-19 Thread intrigeri
Damyan Ivanov: > -=| gregor herrmann, 18.05.2018 11:09:23 +0200 |=- >> So I guess we have to consider if we're happy with the ability to >> turn off loading objects and recommend it to consumers and close the >> bugs; or if we want to change the defaults, which means setting >> $YAML::LoadBlessed t

Bug#899114: xye.xpm is in both xye and xye-data

2018-05-19 Thread Stephen Kitt
Hi Göran, On Sat, 19 May 2018 12:08:27 +0200, Göran Weinholt wrote: > The latest xye package can't be installed: Aargh, thanks for reporting this! Combined builds were fine (which is what I tested), but building the arch-independent package on its own pulled in the XPM :-(. Fix incoming... Reg

Bug#899116: FTBFS: Can't exec "gtkdocize": No such file or directory

2018-05-19 Thread Simon McVittie
Source: gstreamer1.0 Version: 1.14.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Recent versions of dh-autoreconf automatically run gtkdocize if gtk-doc is found in configure.ac. This caused gstreamer1.0/1.14.1-1 to FTBFS on all architectures

Bug#899115: pasco FTCBFS: hard codes plain gcc, policy 4.6 violation

2018-05-19 Thread Helmut Grohne
Source: pasco Version: 20040505-2 Severity: serious Justification: policy 4.6 Tags: patch User: helm...@debian.org Usertags: rebootstrap pasco fails to cross build from source, because its upstream Makefile hard codes the build architecture compiler. While fixing it, I spotted a policy 4.6 (error

Bug#899062: marked as done (chezscheme: FTBFS on armhf armel)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 11:04:37 + with message-id and subject line Bug#899062: fixed in chezscheme 9.5+dfsg-3 has caused the Debian Bug report #899062, regarding chezscheme: FTBFS on armhf armel to be marked as done. This means that you claim that the problem has been dealt with.

Bug#899114: xye.xpm is in both xye and xye-data

2018-05-19 Thread Göran Weinholt
Package: xye Version: 0.12.2+dfsg-6 Severity: serious Justification: can't be installed Hello! The latest xye package can't be installed: Unpacking xye (0.12.2+dfsg-6) over (0.12.2+dfsg-5+b1) ... Preparing to unpack .../229-xye-data_0.12.2+dfsg-6_all.deb ... Unpacking xye-data (0.12.2+dfsg

Bug#899077: marked as done (openmpi: libmca_common_monitoring.so* does not get installed)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 09:05:02 + with message-id and subject line Bug#899077: fixed in openmpi 3.1.0-2 has caused the Debian Bug report #899077, regarding openmpi: libmca_common_monitoring.so* does not get installed to be marked as done. This means that you claim that the proble

Bug#897100: kicad FTBFS with cmake 3.11.1

2018-05-19 Thread Juhani Numminen
Control: forwarded -1 https://lists.launchpad.net/kicad-developers/msg35237.html Control: tags -1 fixed-upstream On Sat, 28 Apr 2018 16:40:47 +0300 Adrian Bunk wrote: > Source: kicad > Version: 4.0.7+dfsg1-1 > ... > CMake Error at CMakeModules/CheckCXXSymbolExists.cmake:41 > (_CHECK_SYMBOL_EXIS

Processed: Re: kicad FTBFS with cmake 3.11.1

2018-05-19 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://lists.launchpad.net/kicad-developers/msg35237.html Bug #897100 [src:kicad] kicad FTBFS with cmake 3.11.1 Set Bug forwarded-to-address to 'https://lists.launchpad.net/kicad-developers/msg35237.html'. > tags -1 fixed-upstream Bug #897100 [src:kica

Bug#896449: dewalls FTBFS with qbs 1.11.0+dfsg-1

2018-05-19 Thread Juhani Numminen
On Sat, 21 Apr 2018 11:05:03 +0300 Adrian Bunk wrote: > Source: dewalls > Version: 1.0.0+ds1-5 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dewalls.html > > ... >debian/rules override_dh_auto_build > make[1]: Entering directory '/build/1st/dewall

Bug#896483: marked as done (beast-mcmc FTBFS with TeX Live 2018)

2018-05-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 May 2018 07:04:29 + with message-id and subject line Bug#896483: fixed in beast-mcmc 1.8.4+dfsg.1-3 has caused the Debian Bug report #896483, regarding beast-mcmc FTBFS with TeX Live 2018 to be marked as done. This means that you claim that the problem has been deal