Bug#977077: marked as done (pydantic FTBFS with pytest 6)

Your message dated Fri, 08 Jan 2021 07:48:27 + with message-id and subject line Bug#977077: fixed in pydantic 1.7.3-1 has caused the Debian Bug report #977077, regarding pydantic FTBFS with pytest 6 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: 979041 affects pysph

Processing commands for cont...@bugs.debian.org: > affects 979041 + pysph Bug #979041 [libopenmpi3] libopempi3: aborts python code due to libfabric fork() issues Added indication that 979041 affects pysph > thanks Stopping processing here. Please contact me if you need assistance. -- 979041: ht

Processed: Re: upgrade severity on: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath

Processing commands for cont...@bugs.debian.org: > severity 972294 serious Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath Severity set to 'serious' from 'important' > severity 972297 serious Bug #972297 [scram] scram: FTBFS w

Processed: retitle 979546 to version in Buster does not support rootless mode ...

Processing commands for cont...@bugs.debian.org: > retitle 979546 version in Buster does not support rootless mode Bug #979546 [docker.io] docker.io: version in Buster does not support Changed Bug title to 'version in Buster does not support rootless mode' from 'docker.io: version in Buster does

Bug#892275: Working redshift setup

I have redshift working on both my desktop and laptop, here's how I have things set up: * If you don't have "normal" desktop environment like GNOME, then you need to start the geoclue agent manually (note that the path to it recently changed, which may be way people have having problems again recen

Bug#979286: marked as done (gitsome autopkgtests fail with pytest 6)

Your message dated Fri, 08 Jan 2021 05:33:35 + with message-id and subject line Bug#979286: fixed in gitsome 0.8.0+ds-5 has caused the Debian Bug report #979286, regarding gitsome autopkgtests fail with pytest 6 to be marked as done. This means that you claim that the problem has been dealt w

Bug#979546: docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial

Hi Chris, I believe what you refer to is a well-known issue with docker. I have this reference from Apr. 2015: https://fosterelli.co/privilege-escalation-via-docker.html This is how docker works. The most easy mitigation is NOT to add a user to the docker group. This way, you will always invoke d

Bug#979546: docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial

Control: retitle -1 docker.io: version in Buster does not support "rootless mode" Control: fixed -1 20.10.0~rc1+dfsg2-1 Control: severity -1 wishlist On Fri, Jan 8, 2021 at 11:55 AM Chris wrote: > > Package: docker.io > Version: 18.09.1+dfsg1-7.1+deb10u2 > Severity: critical > Tags: security > Ju

Processed: Re: Bug#979546: docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial

Processing control commands: > retitle -1 docker.io: version in Buster does not support Bug #979546 [docker.io] docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial Changed Bug title to 'docker.io: version in Buster does not support' from 'docker.io

Bug#979546: docker.io: version in Bullseye does not support "rootless mode", makes privilege escalation trivial

Package: docker.io Version: 18.09.1+dfsg1-7.1+deb10u2 Severity: critical Tags: security Justification: root security hole Dear Maintainer, Unless I'm missing something, any program running in a Docker container using the Docker version currently available in Debian stable has a trivial-to-exploit

Bug#956958: simple-cdd on Bullseye gives reprepro error

That issue does seem fixed in git. Ideally it'd be good to have this fix in time to test simple-cdd with debian-installer bullseye release candidates. (Although using the files from git is an available option as you say, but less convenient in automated flows) -AA. On 8 January 2021 12:14:

Processed: Re: webalizer: ftbfs with GCC-10

Processing control commands: > tags -1 patch Bug #957923 [src:webalizer] webalizer: ftbfs with GCC-10 Added tag(s) patch. -- 957923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957923: webalizer: ftbfs with GCC-10

Package: webalizer Version: 2.23.08-3.1 Followup-For: Bug #957923 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: F

Bug#974779: [Pkg-julia-devel] Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11

Hi Sebastian, coming back to the llvm-9 vs -10 vs -11 issue. So, julia fails to build on ppc64el with llvm-9 because llvm-9 has bugs there, and we cannot use llvm-11 since this is not supported in the current version of julia. There are thus the following options: - keep llvm-10 - drop julia on

Bug#957954: wmwave: ftbfs with GCC-10

Package: wmwave Version: 0.4-11 Followup-For: Bug #957954 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix compi

Processed: Re: wmwave: ftbfs with GCC-10

Processing control commands: > tags -1 patch Bug #957954 [src:wmwave] wmwave: ftbfs with GCC-10 Added tag(s) patch. -- 957954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957991: xneur: ftbfs with GCC-10

Package: xneur Version: 0.20.0-2 Followup-For: Bug #957991 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix comp

Processed: Re: xneur: ftbfs with GCC-10

Processing control commands: > tags -1 patch Bug #957991 [src:xneur] xneur: ftbfs with GCC-10 Added tag(s) patch. -- 957991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957326: gwc: ftbfs with GCC-10

Package: gwc Version: 0.22.04-1 Followup-For: Bug #957326 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix compi

Processed: Re: gwc: ftbfs with GCC-10

Processing control commands: > tags -1 patch Bug #957326 [src:gwc] gwc: ftbfs with GCC-10 Added tag(s) patch. -- 957326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#979524: debian-reference: build-depends on libopencc2-data, which no longer exists

Hi,     libopencc2-data had change name to libopencc-data in bullseye sid. As the opencc upstream had changed the version number, SONAME, etc. Update debian-reference build-depends on libopencc-data should fix this bug. Thanks for your bugreport! 在 2021/1/8 上午12:55, Ivo De Decker 写道: packa

Bug#979545: the stretch-pu: package courier/0.76.3-5+deb9u1 still are broken

Package: courier-mlm Version: 0.76.3-5+deb9u1 Severity: grave Justification: renders package unusable the upload of Andreas from #875696 that backported the "fix" to stretch, is still broken cos package still are unusable.. it never finishes to install cos lists directories missing from configur

Processed: Re: Bug#956958: simple-cdd on Bullseye gives reprepro error

Processing control commands: > severity 956958 serious Bug #956958 [simple-cdd] simple-cdd on Bullseye gives reprepro error Severity set to 'serious' from 'normal' -- 956958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956958 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#957161: echoping: ftbfs with GCC-10

Package: echoping Version: 6.0.2-10 Followup-For: Bug #957161 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix F

Processed: Re: echoping: ftbfs with GCC-10

Processing control commands: > tags -1 patch Bug #957161 [src:echoping] echoping: ftbfs with GCC-10 Added tag(s) patch. -- 957161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment

Processing control commands: > severity -1 grave Bug #971946 [libdebian-installer] libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment Severity set to 'grave' from 'normal' -- 971946: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#977248: FTBFS against opencv 4.5.0

tags 977248 +patch thanks The issue is a change in opencv4.pc, 4.2 has includedir_old=${prefix}/include/opencv4/opencv includedir_new=${prefix}/include/opencv4 But 4.5 has includedir=${prefix}/include/opencv4 I whipped up a patch for this, soon after doing so I noticed that upstream had also

Processed: re: FTBFS against opencv 4.5.0

Processing commands for cont...@bugs.debian.org: > tags 977248 +patch Bug #977248 [src:php-facedetect] FTBFS against opencv 4.5.0 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 977248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977248 D

Bug#971309: marked as done (ansible: Switch to python3-pycryptodome)

Your message dated Thu, 07 Jan 2021 23:18:38 + with message-id and subject line Bug#971309: fixed in ansible 2.10.4-1 has caused the Debian Bug report #971309, regarding ansible: Switch to python3-pycryptodome to be marked as done. This means that you claim that the problem has been dealt wit

Processed: Re: Bug#979540: kde-config-gtk-style: Configuring gtk theme on KDE result in abnormal output on stdout

Processing commands for cont...@bugs.debian.org: > Severity 979540 important Bug #979540 [kde-config-gtk-style] kde-config-gtk-style: Configuring gtk theme on KDE result in abnormal output on stdout Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me

Bug#979540: kde-config-gtk-style: Configuring gtk theme on KDE result in abnormal output on stdout

Severity 979540 important thanks > supposed to be either "ext" or "int" it used "WINDOW DECORATIONS RELOADED". That is a message from Gtk I guess. > Any application using gtk windows and using stdout to provide usefull data to > file > storage/pipes, may be broken. What the version of the pac

Bug#979540: kde-config-gtk-style: Configuring gtk theme on KDE result in abnormal output on stdout

Package: kde-config-gtk-style Version: 4:5.20.5-1 Severity: critical Justification: breaks unrelated software I have been hunting a bug that after this morning update it took me the day long and one of the visible effect was that it broke my vpn application that is using yad to display some sim

Bug#957971: xblast-tnt: diff for NMU version 2.10.4-4.1

Control: tags 957971 + pending -- Dear maintainer, I've prepared an NMU for xblast-tnt (versioned as 2.10.4-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru xblast-tnt-2.10.4/debian/changelog xblast-tnt-2.10.4/debian/changelog ---

Processed: xblast-tnt: diff for NMU version 2.10.4-4.1

Processing control commands: > tags 957971 + pending Bug #957971 [src:xblast-tnt] xblast-tnt: ftbfs with GCC-10 Added tag(s) pending. -- 957971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1

X-Debbugs-CC: jbi...@debian.org,bi...@debian.org Adding the geary uploaders directly in CC since they might not have received emails from the BTS for this bug as the maintainer is set to Debian GNOME Maintainers. Best regards, -- Henry-Nicolas Tourneur mxid: @hntourne:matrix.nilux.be irc: hnt

Bug#892275: redshift: Unable to connect to GeoClue.

Le Thu, Jan 07, 2021 at 09:14:46PM +, Mike Gabriel a écrit : > I can confirm this. After upgrading geoclue-2.0 from 2.5.6-1 to 2.5.7-2, > gtk-redshift is broken (again). I can confirm as well. > user@host#:~ kill -9 `ps aux | grep redshift | grep -v grep | awk '{ print > $2 }'` Also in my ca

Bug#977243: Still not fixed

On Tue, Jan 5, 2021 at 2:46 AM Thomas Goirand wrote: > > On 1/4/21 4:40 PM, Casey Bodley wrote: > > you probably need the first commit from > > https://github.com/ceph/ceph/pull/38263 > > I have included it in debian/patches, but that's not enough. :/ > > Cheers, > > Thomas Goirand (zigo) > foll

Bug#979537: pipewire occupies devices preventing driver unbinding

Package: pipewire Version: 0.3.15-1 Severity: serious Tags: upstream patch Justification: makes unrelated software on the system break X-Debbugs-Cc: schmid...@gmx.de Dear Maintainer, Im suffering from the same Upstream Bug https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/369 (fixed) >

Bug#968573: marked as done (wham-align: autopkgtest arm64 failure: times out after ./sequences:,chr1_100k.fa,Test 1)

Your message dated Thu, 07 Jan 2021 21:20:28 + with message-id and subject line Bug#968573: fixed in wham-align 0.1.5-6 has caused the Debian Bug report #968573, regarding wham-align: autopkgtest arm64 failure: times out after ./sequences:,chr1_100k.fa,Test 1 to be marked as done

Processed: Re: redshift: Unable to connect to GeoClue.

Processing control commands: > severity -1 grave Bug #892275 [redshift] redshift: Unable to connect to GeoClue. Severity set to 'grave' from 'important' -- 892275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969640: marked as done (guile-gnutls: FTBFS against guile 3.0.4-1+b1)

Your message dated Thu, 7 Jan 2021 22:01:12 +0100 with message-id and subject line Re: guile-gnutls: FTBFS against guile 3.0.4-1+b1 has caused the Debian Bug report #969640, regarding guile-gnutls: FTBFS against guile 3.0.4-1+b1 to be marked as done. This means that you claim that the problem has

Bug#966714: marked as done (guile-gnutls: FTBFS against guile 3.0.4-1+b1)

Your message dated Thu, 7 Jan 2021 21:59:02 +0100 with message-id and subject line Re: guile-gnutls: FTBFS against guile 3.0.4-1+b1 has caused the Debian Bug report #966714, regarding guile-gnutls: FTBFS against guile 3.0.4-1+b1 to be marked as done. This means that you claim that the problem has

Processed: fixed 942634 in 3.2.1-1

Processing commands for cont...@bugs.debian.org: > fixed 942634 3.2.1-1 Bug #942634 {Done: Eduard Bloch } [apt-cacher-ng] apt-cacher-ng: fails to work on debian/sid suite (too small BUFSIZEMAX) Marked as fixed in versions apt-cacher-ng/3.2.1-1. > thanks Stopping processing here. Please contact m

Bug#979519: marked as done (stockfish: FTBFS on any-i386, x86-32-old architecture is gone)

Your message dated Thu, 07 Jan 2021 20:35:34 + with message-id and subject line Bug#979519: fixed in stockfish 12-2 has caused the Debian Bug report #979519, regarding stockfish: FTBFS on any-i386, x86-32-old architecture is gone to be marked as done. This means that you claim that the proble

Bug#979533: chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-21111 CVE-2021-21112 CVE-2021-21113 CVE-2021-

Michel is preparing an new version and I update the buster branch as soon as the unstable version is uploaded. Best, Jan On Thu, 07 Jan 2021 21:01:43 +0100 Salvatore Bonaccorso wrote: > Source: chromium > Version: 87.0.4280.88-0.4 > Severity: grave > Tags: security upstream > Justification: user

Bug#718272: Processed: reopening 718272

FWIW, I brought this up at our weekly developer meeting, and there was also another concern about apt upgrades across softforks: It could be problematic to not deploy a softfork, and problematic to deploy one without the user's consent. I think I recall Debian has a way for packages to interact

Bug#979534: wolfssl: CVE-2020-36177

Source: wolfssl Version: 4.5.0+dfsg-4 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/wolfSSL/wolfssl/pull/3426 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for wolfssl. CVE-2020-36177

Bug#979184: rust-lazycell: newly introduced binary packages uninstallable.

Hi Peter, On Mon, 4 Jan 2021 00:20:17 + plugwash wrote: > If noone objects I will make an upload dropping these features in a week > or so. I thank you for caring. Paul OpenPGP_signature Description: OpenPGP digital signature

Processed: chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-21111 CVE-2021-21112 CVE-2021-21113 CVE-2021-2

Processing control commands: > found -1 87.0.4280.88-0.4~deb10u1 Bug #979533 [src:chromium] chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-2 CVE-2021-21112 CVE-2021-21113 CVE-2021-21114 CVE-2021

Bug#979533: chromium: New 87.0.4280.141 (CVE-2020-15995 CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 CVE-2021-21110 CVE-2021-21111 CVE-2021-21112 CVE-2021-21113 CVE-2021-

Source: chromium Version: 87.0.4280.88-0.4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 87.0.4280.88-0.4~deb10u1 Hi Please see https://chromereleases.googleblog.com/2021/01/stable-channel-update-

Bug#971754: ABI breakage from 1.4.1 to 1.4.2

Hi Federico, On Tue, 06 Oct 2020 16:38:49 +0300 =?utf-8?q?Sebastian_Dr=C3=B6ge?= wrote: > 1.4.2 broke ABI by adding some fields to the CBytePerfMon structure. > See https://github.com/Haivision/srt/issues/1592 for details. Any progress on this? The freeze for bullseye is around the corner, and t

Bug#974940: marked as done (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el)

Your message dated Thu, 7 Jan 2021 20:49:04 +0100 with message-id <623fbf8f-6e12-4c3d-97f4-0eb4c9d52...@debian.org> and subject line Re: Bug#974940 closed by Paul Gevers (src:xserver-xorg-video-ati: fails to migrate to testing for too long: FTBFS on mips*el) has caused the Debian Bug report #974

Bug#957166: efingerd: diff for NMU version 1.6.5+nmu1

Control: tags 957166 + patch Control: tags 957166 + pending -- Dear maintainer, I've prepared an NMU for efingerd (versioned as 1.6.5+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru efingerd-1.6.5/CHANGES efingerd-1.6.5+nmu1/CHAN

Processed: efingerd: diff for NMU version 1.6.5+nmu1

Processing control commands: > tags 957166 + patch Bug #957166 [src:efingerd] efingerd: ftbfs with GCC-10 Added tag(s) patch. > tags 957166 + pending Bug #957166 [src:efingerd] efingerd: ftbfs with GCC-10 Added tag(s) pending. -- 957166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957166 D

Processed: cavezofphear: diff for NMU version 0.5.1-1.1

Processing control commands: > tags 957068 + pending Bug #957068 [src:cavezofphear] cavezofphear: ftbfs with GCC-10 Added tag(s) pending. -- 957068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957068: cavezofphear: diff for NMU version 0.5.1-1.1

Control: tags 957068 + pending -- Dear maintainer, I've prepared an NMU for cavezofphear (versioned as 0.5.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru cavezofphear-0.5.1/debian/changelog cavezofphear-0.5.1/debian/changelog

Bug#974586:

According to upstream changelog: https://github.com/rsyslog/loganalyzer/blob/master/ChangeLog multiple php 7.x issues are also fixed in 4.1.7 and 4.1.8. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956621 -- Informativa sulla Privacy: http://www.unibs.it/node/8155

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 974586 grave Bug #974586 [loganalyzer] loganalyzer: depends on php5 to use mysql db as a backend. Severity set to 'grave' from 'important' > tags 974586 fixed-upstream Bug #974586 [loganalyzer] loganalyzer: depends on php5 to use mysql d

Bug#718272: Processed: reopening 718272

Quoting Luke Dashjr (2021-01-07 18:26:43) > We (upstream) already elaborated many years ago, copied here: > > http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md.asc > > At a minimum, to be safe, Debian would need to: > > 1) Either: > 1a) Build with the bundled L

Bug#979530: src:blag-fortune: invalid maintainer address

Source: blag-fortune Version: 1.2-1 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address bounces, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning messag

Bug#979529: src:libdbix-class-htmlwidget-perl: invalid maintainer address

Source: libdbix-class-htmlwidget-perl Version: 0.16-5 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address (@d.o) forwards to a non-existing address, see below. Ansgar Start of forwarded message From: Mail Delivery Sys

Bug#718272: Processed: reopening 718272

We (upstream) already elaborated many years ago, copied here: http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-bitcoin.md.asc At a minimum, to be safe, Debian would need to: 1) Either: 1a) Build with the bundled LevelDB statically linked. 1b) Guarantee LevelDB package re

Processed: [bts-link] source package src:libseqlib

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:libseqlib > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org S

Processed: [bts-link] source package darktable

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package darktable > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Bug#976929: parsinsert: FTBFS on ppc64el: incorrect result

Hi David, thanks a lot for your quick response. On Thu, Jan 07, 2021 at 09:49:06AM -0700, David Knox wrote: > How are you using the package? Its about building the package which means compiling the source code and running its test suite - which results in errors for a view architectures. Here yo

Bug#979524: debian-reference: build-depends on libopencc2-data, which no longer exists

package: src:debian-reference version: 2.76 tags: bullseye sid ftbfs severity: serious Hi, It seems debian-reference build-depends on libopencc2-data, which no longer exists. Cheers, Ivo

Processed: Re: parsinsert: FTBFS on ppc64el: incorrect result

Processing control commands: > tags -1 upstream Bug #976929 [src:parsinsert] parsinsert: FTBFS on ppc64el: incorrect result Added tag(s) upstream. > tags -1 help Bug #976929 [src:parsinsert] parsinsert: FTBFS on ppc64el: incorrect result Added tag(s) help. > forwarded -1 David Knox Bug #976929 [s

Bug#976929: parsinsert: FTBFS on ppc64el: incorrect result

Control: tags -1 upstream Control: tags -1 help Control: forwarded -1 David Knox Hi David, there is a bug[1] report filed against the Debian packaged version of ParsInsert. The full build log for ppc64el can be found here[2]. The problem is also present for other architectures like mips64el[3]

Bug#979521: openboard-common depends on libjs-jquery-i18n-properties that was removed from unstable

Package: openboard-common Version: 1.5.4+dfsg1-1 Severity: serious The following packages have unmet dependencies: openboard-common : Depends: libjs-jquery-i18n-properties but it is not installable https://tracker.debian.org/pkg/jquery-i18n-properties

Processed: tagging 979519

Processing commands for cont...@bugs.debian.org: > tags 979519 + ftbfs Bug #979519 [src:stockfish] stockfish: FTBFS on any-i386, x86-32-old architecture is gone Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 979519: https://bugs.debian.org/cg

Bug#979519: stockfish: FTBFS on any-i386, x86-32-old architecture is gone

Source: stockfish Version: 12-1 Severity: serious Tags: patch Your package FTBFS on {,hurd-,kfreebsd-}i386: , | Testing config sanity. If this fails, try 'make help' ... | | make[2]: *** [Makefile:824: config-sanity] Error 1 ` This was not too helpful at first glance, but a closer inspec

Bug#969597: libzstd: Please correct version in symbol file

Hi Alex, did you possibly by chance forgot to close #969597 in your latest upload of libzstd 1.4.8+dfsg-1 ? Kind regards Andreas. -- http://fam-tille.de

Bug#961814: marked as pending in golang-google-protobuf

On Thu, Jan 7, 2021 at 11:12 PM Shengjing Zhu wrote: > > On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli > wrote: > > But those issues are not made worse by allowing golang-google-protobuf > > to go in, right? > > > > Let golang-google-protobuf go in is one thing, it's not difficult. > However w

Bug#961814: marked as pending in golang-google-protobuf

On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli wrote: > But those issues are not made worse by allowing golang-google-protobuf > to go in, right? > Let golang-google-protobuf go in is one thing, it's not difficult. However without golang-goprotobuf 1.4.x it's not useful currently. But it will b

Bug#961814: marked as pending in golang-google-protobuf

On Thu, Jan 07, 2021 at 04:43:43PM +0800, Shengjing Zhu wrote: On Thu, Jan 7, 2021 at 2:51 PM Anthony Fok wrote: Hi Shengjing, On Tue, Jan 5, 2021 at 8:42 AM Shengjing Zhu wrote: > > Hi Anthony, Thanks for writing to me! Sorry for the late reply. I was going to re-open this with the pseudo

Bug#976536: marked as done (rapidjson: FTBFS: reader.h:1476:57: error: comparison is always true due to limited range of data type [-Werror=type-limits])

Your message dated Thu, 07 Jan 2021 14:29:17 + with message-id and subject line Bug#976536: fixed in rapidjson 1.1.0+dfsg2-7 has caused the Debian Bug report #976536, regarding rapidjson: FTBFS: reader.h:1476:57: error: comparison is always true due to limited range of data type [-Werror=type

Bug#976944: marked as done (rapidjson: FTBFS on ppc64el (arch:all-only src pkg): c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?)

Your message dated Thu, 07 Jan 2021 14:29:17 + with message-id and subject line Bug#976944: fixed in rapidjson 1.1.0+dfsg2-7 has caused the Debian Bug report #976944, regarding rapidjson: FTBFS on ppc64el (arch:all-only src pkg): c++: error: unrecognized command-line option ‘-march=native’; d

Bug#979232: lighttpd: does not start with media-types 1.1.0

On Thu, Jan 07, 2021 at 02:53:17PM +0100, Alexandre Duret-Lutz wrote: > FWIW more uppercase variants are now present in media-types 2.0.0 > > audio/AMR amr AMR > audio/AMR-WBawb AWB > audio/EVRC-QCP

Bug#979513: src:wsl: invalid maintainer address

Source: wsl Version: 0.2.1-1 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message Date: Thu, 7 Jan 2021 08:08:47 -0500 From: Mail Delivery Subsystem Subject: Re

Bug#979232: lighttpd: does not start with media-types 1.1.0

FWIW more uppercase variants are now present in media-types 2.0.0 audio/AMR amr AMR audio/AMR-WBawb AWB audio/EVRC-QCP qcp QCP image/t38 t38 T38 image/vn

Bug#718272: marked as done (upstream does not support stable releases (block migration to testing))

Your message dated Thu, 07 Jan 2021 14:51:50 +0100 with message-id <161002751041.1585395.8615807898528325...@auryn.jones.dk> and subject line Re: Processed: reopening 718272 has caused the Debian Bug report #718272, regarding upstream does not support stable releases (block migration to testing) to

Bug#976536: marked as pending in rapidjson

Control: tag -1 pending Hello, Bug #976536 in rapidjson 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/rapidjson/-/commit/50202e20fd1563a6dd2a869550e3ec

Processed: Bug#976536 marked as pending in rapidjson

Processing control commands: > tag -1 pending Bug #976536 [src:rapidjson] rapidjson: FTBFS: reader.h:1476:57: error: comparison is always true due to limited range of data type [-Werror=type-limits] Added tag(s) pending. -- 976536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976536 Debia

Processed: Bug#976944 marked as pending in rapidjson

Processing control commands: > tag -1 pending Bug #976944 [src:rapidjson] rapidjson: FTBFS on ppc64el (arch:all-only src pkg): c++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’? Added tag(s) pending. -- 976944: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#976944: marked as pending in rapidjson

Control: tag -1 pending Hello, Bug #976944 in rapidjson 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/rapidjson/-/commit/c9ff554e77ca06dd77276d75d4b5c0

Processed: bug 976536 is forwarded to https://github.com/Tencent/rapidjson/issues/655

Processing commands for cont...@bugs.debian.org: > forwarded 976536 https://github.com/Tencent/rapidjson/issues/655 Bug #976536 [src:rapidjson] rapidjson: FTBFS: reader.h:1476:57: error: comparison is always true due to limited range of data type [-Werror=type-limits] Set Bug forwarded-to-addres

Bug#978245: marked as done (aide: FTBFS: configure: error: You don't have libaudit properly installed. Install it or try --without-audit.)

Your message dated Thu, 7 Jan 2021 14:25:56 +0100 with message-id <20210107132556.ga1888...@sulfur.vonhaugwitz.com> and subject line Re: Bug#978245: aide: FTBFS: configure: error: You don't have libaudit properly installed. Install it or try --without-audit. has caused the Debian Bug report #97824

Bug#975430: [libcutl-users] Re: Bug#975430: libcutl: FTBFS against boost_1.74

László Böszörményi (GCS) writes: > This might be prevented by Boost include std/version (making the path > more unique), libcutl to place standard C++ header include paths first > or by renaming its version file to version.txt or something like that. > I think the Boost solution would be the best

Bug#978168: marked as done (obconf-qt: FTBFS: maindialog.cpp:36:51: error: ‘QString::QString(const char*)’ is private within this context)

Your message dated Thu, 07 Jan 2021 12:33:55 + with message-id and subject line Bug#978168: fixed in obconf-qt 0.16.0-1 has caused the Debian Bug report #978168, regarding obconf-qt: FTBFS: maindialog.cpp:36:51: error: ‘QString::QString(const char*)’ is private within this context to be marke

Bug#979504: src:libtext-string-hexconvert-perl: invalid maintainer address

Source: libtext-string-hexconvert-perl Version: 0.01-2 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Cyril Bouthors , Cyril Bouthors , Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Deliver

Bug#979502: src:liblingua-en-namecase-perl: invalid maintainer address

Source: liblingua-en-namecase-perl Version: 1.15-1 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed

Bug#979377: marked as done (tlf: FTBFS on mips*: test failures)

Your message dated Thu, 07 Jan 2021 11:51:15 + with message-id and subject line Bug#979377: fixed in tlf 1.4.1-3 has caused the Debian Bug report #979377, regarding tlf: FTBFS on mips*: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#978564: marked as done (src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating)

Your message dated Thu, 07 Jan 2021 11:50:01 + with message-id and subject line Bug#978564: fixed in gst-plugins-bad1.0 1.18.2-1~deb11u1 has caused the Debian Bug report #978564, regarding src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating to be mark

Processed: Bug#979377 marked as pending in tlf

Processing control commands: > tag -1 pending Bug #979377 [src:tlf] tlf: FTBFS on mips*: test failures Added tag(s) pending. -- 979377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#979377: marked as pending in tlf

Control: tag -1 pending Hello, Bug #979377 in tlf 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-hamradio-team/tlf/-/commit/8a0cbff093ac8846aa73ff012668

Bug#976914: marked as done (git-buildpackage FTBFS when /etc/lsb-release does not exist)

Your message dated Thu, 07 Jan 2021 11:18:26 + with message-id and subject line Bug#976914: fixed in git-buildpackage 0.9.21 has caused the Debian Bug report #976914, regarding git-buildpackage FTBFS when /etc/lsb-release does not exist to be marked as done. This means that you claim that the

Bug#979419: marked as done (nfs-ganesha build depends on the removed dh-systemd transitional package)

Your message dated Thu, 07 Jan 2021 11:04:00 + with message-id and subject line Bug#979419: fixed in nfs-ganesha 3.3-3 has caused the Debian Bug report #979419, regarding nfs-ganesha build depends on the removed dh-systemd transitional package to be marked as done. This means that you claim

Bug#979302: marked as done (libgtkextra-3.0: ships libgtkextra-x11-3.0.so)

Your message dated Thu, 07 Jan 2021 11:03:30 + with message-id and subject line Bug#979302: fixed in gtkextra 3.3.4-3 has caused the Debian Bug report #979302, regarding libgtkextra-3.0: ships libgtkextra-x11-3.0.so to be marked as done. This means that you claim that the problem has been dea

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

On Tue, 5 Jan 2021 19:09:04 +0100 Paul Gevers wrote: > > > This is solely blocked on srt currently, and the maintainer will have > > to figure out a solution there for the ABI breakage. > > Ack. Although, you *could* help them find a solution. RC bugs in key > packages are a shared responsibility

Bug#979495: clang_delta (creduce, cvise) segfaults when built with LLVM 11

Package: src:llvm-toolchain-11 Version: 1:11.0.1-1 Severity: serious Tags: sid bullseye Forwarded: https://bugs.llvm.org/show_bug.cgi?id=48682 First seen at https://gcc.gnu.org/PR98557, at least on armhf $ cat > wxe_funcs.ii static __typeof() a __attribute__((__weakref__("pthread_mutex_destro

  1   2   >