Bug#962813: does not build with ghc 8.8

Hi, On So 14 Jun 2020 16:41:31 CEST, Picca Frédéric-Emmanuel wrote: Source: haskell-tree-monad Severity: critical Hello, this package does not build with the up-comming ghc 8.8 version. It is not part of stackage LTS, and it was not updated by upstream since 2009. It means that there is

Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs

Package: mdadm Version: 4.1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, I created a RAID 5 volume over 4 disks using the BIOS support for Intel RST. Install proceeded correctly, however after a reboot in to the installed system, the root device was not found.

Bug#962323: python-django: CVE-2020-13254 CVE-2020-13596

Chris Lamb wrote: > I will wait a few days to see what upstream says. I will also have to > re-release for jessie LTS, alas. Okay, this is now fixed in the following versions (without and with the regression fix): DistributionUpload with regressionUpload with regression fixed

Bug#962841: python3-nanomath: ships /usr/LICENSE

Package: python3-nanomath Version: 0.23.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files ... but a file like /usr/LICENSE should be shipped by *no*

Bug#962840: python3-nanoget: ships /usr/LICENSE

Package: python3-nanoget Version: 1.12.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files ... but a file like /usr/LICENSE should be shipped by *no*

Bug#962685: marked as done (wordpress 5.4.2 security release)

Your message dated Sun, 14 Jun 2020 22:19:42 + with message-id and subject line Bug#962685: fixed in wordpress 5.4.2+dfsg1-1 has caused the Debian Bug report #962685, regarding wordpress 5.4.2 security release to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 961490

Processing commands for cont...@bugs.debian.org: > tags 961490 + buster Bug #961490 [fwupd] fwupd: version in stable too old, no updates possible Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 961490:

Bug#946068: marked as done (lv2dynparam1 FTCBFS: lv2core.pc not found)

Your message dated Sun, 14 Jun 2020 21:03:50 + with message-id and subject line Bug#946068: fixed in lv2dynparam1 2-6.1 has caused the Debian Bug report #946068, regarding lv2dynparam1 FTCBFS: lv2core.pc not found to be marked as done. This means that you claim that the problem has been

Bug#959386: php-imagick: diff for NMU version 3.4.4-4.1

Adrian, please do a direct upload to unstable and thanks for the fix. No need to wait 15 days. -- Ondřej Surý > On 14 Jun 2020, at 18:51, Adrian Bunk wrote: > > Control: tags 959386 + patch > Control: tags 959386 + pending > > Dear maintainer, > > I've prepared an NMU for php-imagick

Bug#962824: marked as done (r-cran-v8: FTBFS against nodejs 12.18.0)

Your message dated Sun, 14 Jun 2020 20:49:52 + with message-id and subject line Bug#962824: fixed in r-cran-v8 3.1.0+dfsg-2 has caused the Debian Bug report #962824, regarding r-cran-v8: FTBFS against nodejs 12.18.0 to be marked as done. This means that you claim that the problem has been

Bug#962518: marked as done (cegui-mk2 FTBFS on mipsel/mips64el: symbol differences)

Your message dated Sun, 14 Jun 2020 20:48:30 + with message-id and subject line Bug#962518: fixed in cegui-mk2 0.8.7-9 has caused the Debian Bug report #962518, regarding cegui-mk2 FTBFS on mipsel/mips64el: symbol differences to be marked as done. This means that you claim that the problem

Bug#962832: openms-doc: missing Breaks+Replaces: openms (<< 2.5)

Package: openms-doc Version: 2.5.0+cleaned1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite

Bug#962831: libmumps-headers-dev: missing Breaks+Replaces: libmumps-seq-dev (<= 5.3.1-2)

Package: libmumps-headers-dev Version: 5.3.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to

Bug#817954: Does this bug prevent firefox from entering backports also?

On Sun, Jun 14, 2020 at 08:25:10PM +0530, Pirate Praveen wrote: > > > On Sun, Jun 14, 2020 at 7:31 am, Mike Hommey wrote: > > On Thu, Jun 11, 2020 at 03:22:40PM +0530, Pirate Praveen wrote: > > > On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr > > > wrote: > > > > It would be great to have

Bug#956694: marked as done (spdlog refers to header files that it does not ship)

Your message dated Sun, 14 Jun 2020 19:48:54 + with message-id and subject line Bug#956694: fixed in spdlog 1:1.5.0+ds-4 has caused the Debian Bug report #956694, regarding spdlog refers to header files that it does not ship to be marked as done. This means that you claim that the problem

Bug#962804: marked as done (wfmath: autopkgtest failure: no acceptable C compiler found in $PATH)

Your message dated Sun, 14 Jun 2020 19:34:28 + with message-id and subject line Bug#962804: fixed in wfmath 1.0.2+dfsg1-9 has caused the Debian Bug report #962804, regarding wfmath: autopkgtest failure: no acceptable C compiler found in $PATH to be marked as done. This means that you claim

Processed: libphp-phpmailer: CVE-2020-13625

Processing control commands: > found -1 6.0.6-0.1 Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625 Marked as found in versions libphp-phpmailer/6.0.6-0.1. > found -1 5.2.14+dfsg-2.3+deb9u1 Bug #962827 [src:libphp-phpmailer] libphp-phpmailer: CVE-2020-13625 Marked as found in

Bug#962827: libphp-phpmailer: CVE-2020-13625

Source: libphp-phpmailer Version: 6.1.5-0.1 Severity: grave Tags: security upstream Control: found -1 6.0.6-0.1 Control: found -1 5.2.14+dfsg-2.3+deb9u1 Control: found -1 5.2.14+dfsg-2.3 Hi, The following vulnerability was published for libphp-phpmailer. Filling as RC severity as currently as

Bug#962825: node-opencv: FTBFS against nodejs 12.18 - fixed in upstream version 7.0.0

Package: node-opencv Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi this package fails to build against node 12.18, and upstream has already version 7.0.0 fixing the issue. However, upstream forgot to push git tags:

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

Ah, ok. Good to know and that makes sense. Thanks to you both. I'm still a bit new to this autopkgtest thing but it seems worthwhile to get it figured out. I'll add build-essential explicitly since none of the other build dependencies should be necessary to compile the test. -Olek

Bug#962824: r-cran-v8: FTBFS against nodejs 12.18.0

Package: r-cran-v8 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, this package cannot be built against nodejs 12.18.0. this blocks nodejs migration to testing. I pinged upstream about that: https://github.com/jeroen/V8/pull/87

Bug#962518: cegui-mk2 FTBFS on mipsel/mips64el: symbol differences

Thanks to all of you for taking a look at this and for your insights and advice!I think I've definitely learned a couple things about how to do symbols better in the future. In the near term, I'm going to take the advice to just get rid of the symbols file. I've been so busy with Bazel [1]

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

On Sun, 14 Jun 2020 at 14:15:02 -0400, Olek Wojnar wrote: > Hmm, is build-essential not automatically installed in the CI environment? > That > seems to be the most likely reason for this failure. I assumed that all > packages (e.g. build-essential) that we assume to be present for packaging >

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

Hi Olek, On 14/06/2020 20.15, Olek Wojnar wrote: > checking for gcc... no > checking for cc... no > checking for cl.exe... no > configure: error: in > `/tmp/autopkgtest-lxc.nwce0fke/downtmp/build.tAZ/src': > configure: error: no acceptable C compiler found in $PATH > > >

Processed: lv2dynparam1: diff for NMU version 2-6.1

Processing control commands: > tags 946068 + patch Bug #946068 [src:lv2dynparam1] lv2dynparam1 FTCBFS: lv2core.pc not found Added tag(s) patch. > tags 946068 + pending Bug #946068 [src:lv2dynparam1] lv2dynparam1 FTCBFS: lv2core.pc not found Added tag(s) pending. -- 946068:

Bug#946068: lv2dynparam1: diff for NMU version 2-6.1

Control: tags 946068 + patch Control: tags 946068 + pending Dear maintainer, I've prepared an NMU for lv2dynparam1 (versioned as 2-6.1) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru lv2dynparam1-2/debian/changelog

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

Hi Paul, Thanks for the bug report. I'd noticed the error on DDPO but hadn't had time to investigate. On Sun, Jun 14, 2020 at 7:18 AM Paul Gevers wrote: > I copied some of the output at the bottom of this report. Are you > missing a test dependency? > > checking for gcc... no > checking

Processed: php-imagick: diff for NMU version 3.4.4-4.1

Processing control commands: > tags 959386 + patch Bug #959386 {Done: Paul Gevers } [src:php-imagick] src:php-imagick: fails to migrate to testing for too long: FTBFS on armel Added tag(s) patch. > tags 959386 + pending Bug #959386 {Done: Paul Gevers } [src:php-imagick] src:php-imagick: fails

Bug#959386: php-imagick: diff for NMU version 3.4.4-4.1

Control: tags 959386 + patch Control: tags 959386 + pending Dear maintainer, I've prepared an NMU for php-imagick (versioned as 3.4.4-4.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru php-imagick-3.4.4/debian/changelog

Bug#962805: marked as done (python-geotiepoints: autopkgtest regression: No module named 'h5py)

Your message dated Sun, 14 Jun 2020 16:34:43 + with message-id and subject line Bug#962805: fixed in python-geotiepoints 1.2.0-2 has caused the Debian Bug report #962805, regarding python-geotiepoints: autopkgtest regression: No module named 'h5py to be marked as done. This means that you

Bug#962784: [Pkg-puppet-devel] Bug#962784: facter aborts with free(): invalid pointer

Stig Sandbeck Mathisen writes: > Looks like the same bug as http://bugs.debian.org/962692 and related to > https://bugs.debian.org/962320 Ah, indeed, thank you! Somehow I missed those. #962320 seems like it should be assigned to facter and merged with this bug; I don't think it's Boost's

Bug#956694: Clarification: [RFS] spdlog

> For sopt, the build fails with the logs same as what Ole sharedearlier - but > looking at them, it seems that spdlog is probably not responsible for the > failure. By same logs, I do not mean the one in the original bug report, but the logs which Ole got after workaround: #953855 cd

Bug#817954: Does this bug prevent firefox from entering backports also?

On Sun, Jun 14, 2020 at 7:31 am, Mike Hommey wrote: On Thu, Jun 11, 2020 at 03:22:40PM +0530, Pirate Praveen wrote: On Thu, 25 Jul 2019 12:10:45 +0200 Johannes Rohr wrote: > It would be great to have firefox (or the next firefox-esr) in > buster-backports, as it has important new

Bug#962813: does not build with ghc 8.8

Source: haskell-tree-monad Severity: critical Hello, this package does not build with the up-comming ghc 8.8 version. It is not part of stackage LTS, and it was not updated by upstream since 2009. It means that there is few chance to see the upstream fix this issue. so it is considere to remove

Bug#956694: [RFS] spdlog

Hi, I've pushed a patch to the team repo[1] to fix this. I patched ./include/spdlog/tweakme.h: Since this file wasn't getting included to other .h files, I included this bit. It looks fine to me. To test this, I did the following: 1. I wrote my own sample code to just include the libs, and it

Bug#948074: marked as done (din FTBFS: cannot find X11/X.h)

Your message dated Sun, 14 Jun 2020 13:15:58 +0100 with message-id and subject line Re: Bug#948074: din FTBFS: cannot find X11/X.h has caused the Debian Bug report #948074, regarding din FTBFS: cannot find X11/X.h to be marked as done. This means that you claim that the problem has been dealt

Bug#914369: marked as done (haskell-simple-templates: FTBFS with ghc-8.4)

Your message dated Sun, 14 Jun 2020 14:59:39 +0300 with message-id <20200614115939.d3be523o7cqp7...@iliastsi.net> and subject line Re: Bug#914369: haskell-simple-templates: FTBFS with ghc-8.4 has caused the Debian Bug report #914369, regarding haskell-simple-templates: FTBFS with ghc-8.4 to be

Processed: notfound 914369 in haskell-simple-templates/0.11.2-2

Processing commands for cont...@bugs.debian.org: > notfound 914369 haskell-simple-templates/0.11.2-2 Bug #914369 [src:haskell-simple-templates] haskell-simple-templates: FTBFS with ghc-8.4 The source haskell-simple-templates and version 0.11.2-2 do not appear to match any binary packages No

Bug#944265: marked as done (mailutils: local privilege escalation in maidag utility (fixed in 3.8) (CVE-2019-18862))

Your message dated Sun, 14 Jun 2020 13:34:12 +0200 with message-id <20200614113411.ga17...@debian.org> and subject line Re: Bug#944265: mailutils: local privilege escalation in maidag utility (fixed in 3.8) has caused the Debian Bug report #944265, regarding mailutils: local privilege escalation

Bug#962805: python-geotiepoints: autopkgtest regression: No module named 'h5py

Source: python-geotiepoints Version: 1.2.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-geotiepoints the autopkgtest of python-geotiepoints fails in testing when that

Bug#962804: wfmath: autopkgtest failure: no acceptable C compiler found in $PATH

Source: wfmath Version: 1.0.2+dfsg1-8 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package wfmath, great. However, it fails. Currently this failure is blocking the

Bug#962803: rust-csv: autopkgtest failure: could not compile `csv`

Source: rust-csv Version: 1.1.3-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package rust-csv, great. However, it fails. Currently this failure is blocking the

Bug#935614: marked as done (libinfinity: FTBFS on all architectures)

Your message dated Sun, 14 Jun 2020 09:48:37 + with message-id and subject line Bug#935614: fixed in libinfinity 0.7.1-2 has caused the Debian Bug report #935614, regarding libinfinity: FTBFS on all architectures to be marked as done. This means that you claim that the problem has been dealt

Bug#962796: r-cran-dplyr: breaks multiple autopkgtests

Source: r-cran-dplyr Version: 1.0.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Hi Maintainer The recent upload of r-cran-dplyr causes the autopkgtests of multiple packages to fail [1][2][3][4], including its own. This prevents

Bug#962794: r-cran-stanheaders: breaks r-cran-rstanarm autopkgtests

Source: r-cran-stanheaders Version: 2.21.0-3-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Hi Maintainer The recent upload of r-cran-stanheaders causes the autopkgtests of r-cran-rstanarm to fail [1]. This prevents the migration of

Bug#962784: [Pkg-puppet-devel] Bug#962784: facter aborts with free(): invalid pointer

Russ Allbery writes: > Package: facter > Version: 3.11.0-4.1 > Severity: grave > > facter no longer works at all on amd64. When invoked, it dies with > an invalid pointer error: Looks like the same bug as http://bugs.debian.org/962692 and related to https://bugs.debian.org/962320 A quick

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 959543 src:pbcopper Bug #959543 [src:pbdagcon] pbdagcon: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libblasr.so: undefined reference to `PacBio::Data::QualityValues::cend() const' Bug reassigned from package

Bug#961076: marked as done (NXNS Attack (CVE-2020-12667))

Your message dated Sun, 14 Jun 2020 07:03:29 + with message-id and subject line Bug#961076: fixed in knot-resolver 5.1.1-0.1 has caused the Debian Bug report #961076, regarding NXNS Attack (CVE-2020-12667) to be marked as done. This means that you claim that the problem has been dealt with.