Processed: your mail

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 960131 + pending confirmed Bug #960131 [src:swi-prolog] swi-prolog: flaky autopkgtest: test set "file" ... aborted Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 960131:

Bug#960131: swi-prolog: flaky autopkgtest: test set "file" ... aborted

2020-05-09 Thread Lev Lamberov
Hi, Сб 09 мая 2020 @ 20:59 Paul Gevers : > Source: swi-prolog > Version: 8.1.29+dfsg-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > You package has an autopkgtest, great.

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

2020-05-09 Thread Allan Wind
Package: nvidia-driver Version: 418.113-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, I upgraded to 10.4 and on the subsequent reboot lightdm and X failed to start, and in syslog I found the following error message: 2020-05-10T03:28:57.914+00:00 vent kernel:

Bug#936317: marked as done (codeville: Python2 removal in sid/bullseye)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 May 2020 03:02:02 + with message-id and subject line Bug#960068: Removed package(s) from unstable has caused the Debian Bug report #936317, regarding codeville: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#959994: marked as done (codeville: Consider removing this package)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 May 2020 03:02:02 + with message-id and subject line Bug#960068: Removed package(s) from unstable has caused the Debian Bug report #959994, regarding codeville: Consider removing this package to be marked as done. This means that you claim that the problem has been

Bug#943282: marked as done (syslog-summary: Python2 removal in sid/bullseye)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 May 2020 03:01:07 + with message-id and subject line Bug#959993: Removed package(s) from unstable has caused the Debian Bug report #943282, regarding syslog-summary: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#945636: marked as done (discus: Python2 removal in sid/bullseye)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 May 2020 02:33:30 + with message-id and subject line Bug#945636: fixed in discus 0.3.0-1 has caused the Debian Bug report #945636, regarding discus: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#960153: ca-certificates-java: Failed to install ca-certificates-java on Beagle Bone Black

2020-05-09 Thread Kristian Nygaard Jensen
Package: ca-certificates-java Version: 20190405 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * I tried to install ca-certificates-java * apt get install -y ca-certificates-java *

Bug#960151: petsc: FTBFS during arch:all build: petscrules: No such file or directory

2020-05-09 Thread Andreas Beckmann
Package: petsc Version: 3.13.0+dfsg2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, petsc/experimental FTBFS during the arch:all build (on amd64): Completed test examples make[2]: Leaving directory '/build/petsc-3.13.0+dfsg2'

Processed: Re: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

2020-05-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #932779 [lirc] lirc: Fails to install due to missing /etc/lirc/lirc_options.conf Added tag(s) patch. -- 932779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#932779: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

2020-05-09 Thread Andreas Beckmann
Control: tag -1 patch Hi Sebastien, thanks for the analysis! On Fri, 8 May 2020 11:16:09 +0200 Sebastien Bacher wrote: > There are a few possible options there now that I can see > - restore the .postinst 'test -e /etc/lirc/$f || cp /etc/lirc/${f}.dist > /etc/lirc/$f || :' calls But we want to

Bug#950015: marked as done (haskell-hledger-lib: FTBFS on s390x)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sun, 10 May 2020 00:56:12 +0200 with message-id and subject line closing has caused the Debian Bug report #950015, regarding haskell-hledger-lib: FTBFS on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#959940: hdmf FTBFS with h5py 2.10.0

2020-05-09 Thread Yaroslav Halchenko
Package: python3-h5py Version: 2.10.0-7 Followup-For: Bug #959940 Please see https://github.com/hdmf-dev/hdmf/issues/343#issuecomment-625972582 for possibly more info: @tillea @yarikoptic the debian port contains this code in h5py_2.10.0-7.debian/debian/wrapper_module/h5py/__init__.py

Bug#960143: sagetex: FTBFS in unstable

2020-05-09 Thread Graham Inggs
Source: sagetex Version: 3.4+ds-1 Severity: serious Tags: ftbfs Hi Maintainer Sagetex currently FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sagetex.html kpathsea:

Processed: reassign 960101 to src:node-jsonld, fixed 960101 in 1.6.2-5, reassign 959390 to src:gtk+3.0 ...

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 960101 src:node-jsonld 1.6.2-3 Bug #960101 {Done: Jonas Smedegaard } [node-jsonld,node-rdf-canonize] node-jsonld: Build with babel version 7 Bug reassigned from package 'node-jsonld,node-rdf-canonize' to 'src:node-jsonld'. Ignoring

Bug#953081: lambda-align2: empty package on !amd64

2020-05-09 Thread Andreas Beckmann
Followup-For: Bug #953081 Control: severity -1 normal The useless empty packages have been removed from stable, too. Therefore downgrading the severity to allow for bug archival. Andreas

Processed: Re: lambda-align2: empty package on !amd64

2020-05-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #953081 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} [lambda-align2] lambda-align2: empty package on !amd64 Severity set to 'normal' from 'grave' -- 953081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953081 Debian Bug

Processed: Re: Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'

2020-05-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #953235 [src:vtkplotter] vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython' Severity set to 'important' from 'serious' -- 953235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953235 Debian Bug Tracking

Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'

2020-05-09 Thread Paul Gevers
Control: severity -1 important Hi Adrian, On 07-05-2020 12:16, Adrian Bunk wrote: > On Thu, May 07, 2020 at 10:28:33AM +0200, Paul Gevers wrote: >> On 07-05-2020 10:07, Adrian Bunk wrote: >>> This is a toolchain problem affecting many packages: >>>

Bug#943287: tcpwatch-httpproxy: Python2 removal in sid/bullseye

2020-05-09 Thread Moritz Mühlenhoff
On Fri, Apr 24, 2020 at 08:13:42PM +0200, Moritz Mühlenhoff wrote: > On Wed, Oct 23, 2019 at 02:33:34AM +, mo...@debian.org wrote: > > Source: tcpwatch-httpproxy > > Version: 1.3.1-3 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal >

Bug#937806: python-halberd: Python2 removal in sid/bullseye

2020-05-09 Thread Moritz Mühlenhoff
On Thu, Apr 16, 2020 at 10:03:14PM +0200, Moritz Mühlenhoff wrote: > On Wed, Sep 04, 2019 at 11:16:28AM +, Gianfranco Costamagna wrote: > > control: forwared -1 https://github.com/jmbr/halberd/issues/2 > > Upstream seems dead, let's remove? Filed an RM bug now. Cheers, Moritz

Processed: closing 960125

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # done by fixing #959064 in cmake > close 960125 Bug #960125 [src:ignition-transport] Subject: FTBFS: collect2: error: ld returned 1 exit status Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#945646: marked as done (android-platform-system-core: Python2 removal in sid/bullseye)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 19:18:29 + with message-id and subject line Bug#945646: fixed in android-platform-system-core 1:8.1.0+r23-6 has caused the Debian Bug report #945646, regarding android-platform-system-core: Python2 removal in sid/bullseye to be marked as done. This means

Processed: block 960125 with 959064

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 960125 with 959064 Bug #960125 [src:ignition-transport] Subject: FTBFS: collect2: error: ld returned 1 exit status 960125 was not blocked by any bugs. 960125 was not blocking any bugs. Added blocking bug(s) of 960125: 959960, 959064, and

Bug#960131: swi-prolog: flaky autopkgtest: test set "file" ... aborted

2020-05-09 Thread Paul Gevers
Source: swi-prolog Version: 8.1.29+dfsg-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), You package has an autopkgtest, great. However, it seems to regularly fail [1] on both amd64 and arm64.

Bug#960128: csound: autopkgtest regression: libcsound64.so: cannot open shared object file

2020-05-09 Thread Paul Gevers
Source: csound Version: 1:6.14.0~dfsg-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of csound the autopkgtest of csound fails in testing when that autopkgtest is run with the binary

Bug#958058: marked as done (flex: Maintainer address bounces)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 11:23:57 -0700 with message-id <87k11lklvm@glaurung.internal.golden-gryphon.com> and subject line Re: flex: Maintainer address bounces has caused the Debian Bug report #958058, regarding flex: Maintainer address bounces to be marked as done. This means that

Bug#933439: (no subject)

2020-05-09 Thread ZenWalker
did you try with this change? https://github.com/amule-project/amule/commit/cf63429667953088c7cf93846c892eed7bdde617 It seems to work fine here with this change in a quick test.

Bug#960127: Tk::Error: Can't locate object method "resolve_names" via package "App::ClusterSSH::Window"

2020-05-09 Thread Francois Marier
Package: clusterssh Version: 4.14-1 Severity: grave Justification: renders package unusable It looks like cssh doesn't work anymore on my Debian unstable machine. When I add a host, I see the following on the console: Tk::Error: Can't locate object method "resolve_names" via package

Bug#960126: FTBFS: No cached version of :osmosis-core-0.47.2: available for offline mode.

2020-05-09 Thread Hans Joachim Desserud
Source: mapsforge Version: 0.13.0+dfsg.1-2 Severity: serious Tags: ftbfs Dear Maintainer, mapsforge 0.13.0+dfsg.1-2 currently fails to build: All input files are considered out-of-date for incremental task ':mapsforge-map:compileJava'. Compiling with JDK Java compiler API.

Bug#960125: Subject: FTBFS: collect2: error: ld returned 1 exit status

2020-05-09 Thread Hans Joachim Desserud
Source: ignition-transport Version: 8.0.0+dfsg-3 Severity: serious Tags: ftbfs Dear Maintainer, ignition-transport 8.0.0+dfsg-3 currently fails to build: Run Build Command(s):/usr/bin/make cmTC_64ca3/fast && make[2]: Entering directory

Bug#959520: marked as done (csoundqt FTBFS: fails to find libcsound)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 16:03:34 + with message-id and subject line Bug#959520: fixed in csoundqt 0.9.7-2 has caused the Debian Bug report #959520, regarding csoundqt FTBFS: fails to find libcsound to be marked as done. This means that you claim that the problem has been dealt

Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2

2020-05-09 Thread Bdale Garbee
أحمد المحمودي writes: > On Mon, Apr 27, 2020 at 08:48:59PM -0600, Bdale Garbee wrote: >> As far as I'm concerned, you can feel free to remove geda-gaf from Debian. >> >> I'm personally quite happily living on the fork that I've packaged of >> lepton-eda. Lepton-eda is very actively maintained

Bug#959391: marked as done (wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:17 + with message-id and subject line Bug#959391: fixed in wordpress 5.0.4+dfsg1-1+deb10u2 has caused the Debian Bug report #959391, regarding wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030 to be

Bug#959684: marked as done (salt: CVE-2020-11651 and CVE-2020-11652)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:05 + with message-id and subject line Bug#959684: fixed in salt 2018.3.4+dfsg1-6+deb10u1 has caused the Debian Bug report #959684, regarding salt: CVE-2020-11651 and CVE-2020-11652 to be marked as done. This means that you claim that the problem has

Bug#949222: marked as done (salt: CVE-2019-17361)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:05 + with message-id and subject line Bug#949222: fixed in salt 2018.3.4+dfsg1-6+deb10u1 has caused the Debian Bug report #949222, regarding salt: CVE-2019-17361 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#949991: marked as done (haskell-hledger ftbfs on s390x)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:35:13 + with message-id and subject line Bug#949991: fixed in haskell-hledger-lib 1.14.1-2 has caused the Debian Bug report #949991, regarding haskell-hledger ftbfs on s390x to be marked as done. This means that you claim that the problem has been dealt

Bug#959900: marked as done (keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:03 + with message-id and subject line Bug#959900: fixed in keystone 2:14.2.0-0+deb10u1 has caused the Debian Bug report #959900, regarding keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692 to be marked as done. This means that you

Bug#959391: marked as done (wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:48 + with message-id and subject line Bug#959391: fixed in wordpress 4.7.5+dfsg-2+deb9u6 has caused the Debian Bug report #959391, regarding wordpress: CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030 to be

Bug#959684: marked as done (salt: CVE-2020-11651 and CVE-2020-11652)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:44 + with message-id and subject line Bug#959684: fixed in salt 2016.11.2+ds-1+deb9u3 has caused the Debian Bug report #959684, regarding salt: CVE-2020-11651 and CVE-2020-11652 to be marked as done. This means that you claim that the problem has

Bug#949222: marked as done (salt: CVE-2019-17361)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:33:44 + with message-id and subject line Bug#949222: fixed in salt 2016.11.2+ds-1+deb9u3 has caused the Debian Bug report #949222, regarding salt: CVE-2019-17361 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#885212: marked as done (libmatheval: please migrate to guile-2.2)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 15:18:41 + with message-id and subject line Bug#885212: fixed in libmatheval 1.1.11+dfsg-4 has caused the Debian Bug report #885212, regarding libmatheval: please migrate to guile-2.2 to be marked as done. This means that you claim that the problem has

Bug#885195: [Pkg-electronics-devel] Bug#885195: Bug#885195: geda-gaf: please migrate to guile-2.2

2020-05-09 Thread أحمد المحمودي
On Mon, Apr 27, 2020 at 08:48:59PM -0600, Bdale Garbee wrote: > As far as I'm concerned, you can feel free to remove geda-gaf from Debian. > > I'm personally quite happily living on the fork that I've packaged of > lepton-eda. Lepton-eda is very actively maintained and improved, and > while

Bug#959064: marked as done (cmake breaks on -isystem)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 13:48:30 + with message-id and subject line Bug#959064: fixed in cmake 3.16.3-3 has caused the Debian Bug report #959064, regarding cmake breaks on -isystem to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#958842: marked as done (fsplib: autopkgtest failure: Assertion `fsp_transaction(s,,)==0' failed.)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 12:03:54 + with message-id and subject line Bug#958842: fixed in fsplib 0.14-5 has caused the Debian Bug report #958842, regarding fsplib: autopkgtest failure: Assertion `fsp_transaction(s,,)==0' failed. to be marked as done. This means that you claim

Bug#958109: marked as done (macs: FTBFS on amd64/unstable: ERROR: Could not find an activated virtualenv (required).)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 May 2020 13:46:16 +0200 with message-id and subject line Already fixed has caused the Debian Bug report #958109, regarding macs: FTBFS on amd64/unstable: ERROR: Could not find an activated virtualenv (required). to be marked as done. This means that you claim that the

Bug#959201: jami-daemon: dring does not start due to a symbol lookup error

2020-05-09 Thread Bruno Kleinert
Am Samstag, den 09.05.2020, 11:35 +0200 schrieb Yuri D'Elia: > Package: libyaml-cpp0.6 > Version: 0.6.3-4 > Followup-For: Bug #959201 > > This ABI breakage also affects blender (indirecly via opencolorio). > Version 0.6.3-4 does fix the symbol lookup error, however blender will > incur a crash

Bug#947720: marked as done (sollya ftbfs with libfplll6)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 May 2020 13:56:53 +0400 with message-id <7e3b13cf-aafb-6a4b-1ed3-45cd415e3...@rezozer.net> and subject line [SOLVED]: sollya ftbfs with libfplll6 has caused the Debian Bug report #947720, regarding sollya ftbfs with libfplll6 to be marked as done. This means that you

Bug#959201: jami-daemon: dring does not start due to a symbol lookup error

2020-05-09 Thread Yuri D'Elia
Package: libyaml-cpp0.6 Version: 0.6.3-4 Followup-For: Bug #959201 This ABI breakage also affects blender (indirecly via opencolorio). Version 0.6.3-4 does fix the symbol lookup error, however blender will incur a crash soon after with a segmentation fault. Downgrading libyaml-cpp0.6 to 0.6.2-4

Processed: Re: mailnag: Python2 removal in sid/bullseye

2020-05-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch pending Bug #936981 [src:mailnag] mailnag: Python2 removal in sid/bullseye Added tag(s) patch and pending. -- 936981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tagging 936288

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 936288 + upstream Bug #936288 [src:cfv] cfv: Python2 removal in sid/bullseye Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936288:

Bug#959473: marked as done (orthanc-dicomweb build-dependencies unsatisfiable on armel)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 May 2020 12:13:16 +0300 with message-id <20200509091316.GA26837@localhost> and subject line Re: Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel has caused the Debian Bug report #959473, regarding orthanc-dicomweb build-dependencies unsatisfiable on

Processed: tagging 960087

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 960087 - ipv6 Bug #960087 [wireguard] wireguard missing bc as a dependency for building kernel module Removed tag(s) ipv6. > thanks Stopping processing here. Please contact me if you need assistance. -- 960087:

Bug#960087: wireguard missing bc as a dependency for building kernel module

2020-05-09 Thread Stefan dns2utf8
Package: wireguard Version: 1.0.20200319-1~bpo10+1 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, * What led up to the situation? * I updated the package that I had installed for a couple of months now. * What exactly did you do (or not do) that

Processed: closing 954535

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954535 0.8.12-1 Bug #954535 [src:guymager] guymager: FTBFS: aewf.cpp:143:12: error: flexible array member ‘::OffsetArr’ not at end of ‘struct’ Bug #957321 [src:guymager] guymager: ftbfs with GCC-10 Marked as fixed in versions

Bug#958362: marked as done (pdfrw: fails with python 3.7+ -- abandoned upstream)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 06:49:05 + with message-id and subject line Bug#958362: fixed in img2pdf 0.3.6-1 has caused the Debian Bug report #958362, regarding pdfrw: fails with python 3.7+ -- abandoned upstream to be marked as done. This means that you claim that the problem has

Processed: affects 959064

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 959064 src:ignition-transport Bug #959064 [cmake] cmake breaks on -isystem Bug #959960 [cmake] ignition-transport: FTBFS in sid Bug #960081 [cmake] src:ignition-transport: FTBFS with pkg-config 0.29.2-1 Added indication that 959064

Bug#960079: Acknowledgement (undefined symbol: _PyNautilusInfoProvider_Type)

2020-05-09 Thread Michael Biebl
This was broken by debian/patches/gcc10.patch Bringing Andreas into the loop here. signature.asc Description: OpenPGP digital signature

Processed: Re: Bug#959940: hdmf FTBFS with h5py 2.10.0

2020-05-09 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-h5py 2.10.0-7 Bug #959940 [src:hdmf] hdmf FTBFS with h5py 2.10.0 Bug reassigned from package 'src:hdmf' to 'python3-h5py'. No longer marked as found in versions hdmf/1.5.4-1. Ignoring request to alter fixed versions of bug #959940 to the same

Bug#959940: hdmf FTBFS with h5py 2.10.0

2020-05-09 Thread Adrian Bunk
Control: reassign -1 python3-h5py 2.10.0-7 Control: affects -1 src:hdmf Control: tags -1 - upstream Control: block 956420 by -1 On Thu, May 07, 2020 at 01:17:05PM +0200, Andreas Tille wrote: > Control: forwarded -1 https://github.com/hdmf-dev/hdmf/issues/343 Reassigning to h5py based on the

Processed: reassign 960081 to cmake, forcibly merging 959064 960081

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 960081 cmake Bug #960081 [src:ignition-transport] src:ignition-transport: FTBFS with pkg-config 0.29.2-1 Bug reassigned from package 'src:ignition-transport' to 'cmake'. No longer marked as found in versions

Processed: fixed 952629 in 10.19.0~dfsg-2

2020-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 952629 10.19.0~dfsg-2 Bug #952629 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } [src:nodejs] nodejs: FTBFS: make[2]: *** No rule to make target '../deps/acorn/dist/walk.js', needed by '/<>/out/Release/obj/gen/node_javascript.cc'. Stop. Marked

Bug#960082: nautilus extension fails to load: libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize

2020-05-09 Thread Michael Biebl
Package: eiciel Version: 0.9.12.1-2 Severity: serious The nautilus extension provided by eiciel no longer works with nautilus 3.36. Starting nautilus from the command line: ** (org.gnome.Nautilus:7715): WARNING **: 08:07:07.542: 'nautilus_module_initialize':

Bug#959942: marked as done (src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu)

2020-05-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 May 2020 06:03:30 + with message-id and subject line Bug#959942: fixed in caffe 1.0.0+git20180821.99bd997-7 has caused the Debian Bug report #959942, regarding src:caffe: missing (unversioned) Breaks+Replaces:

Bug#960079: undefined symbol: _PyNautilusInfoProvider_Type

2020-05-09 Thread Michael Biebl
Package: python3-nautilus Version: 1.2.3-2 Severity: serious File: /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus-python.so Hi, today I was investigating, why nautilus-nextcloud is no longer working for me. nautilus-nextcloud is using python3-nautilus and starting nautilus from