Bug#1008464: marked as done (sia: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/NebulousLabs/Sia/api [..] github.com/NebulousLabs/Sia/sync github.com/

Your message dated Sun, 01 May 2022 06:48:43 + with message-id and subject line Bug#1008464: fixed in sia 1.3.0-2 has caused the Debian Bug report #1008464, regarding sia: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/NebulousLabs/Sia/api [..]

Bug#1008464: marked as pending in sia

Control: tag -1 pending Hello, Bug #1008464 in sia 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/go-team/packages/sia/-/commit/ebaddea177062f8effdf8771f9b03b9

Processed: Bug#1008464 marked as pending in sia

Processing control commands: > tag -1 pending Bug #1008464 [src:sia] sia: FTBFS: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/NebulousLabs/Sia/api [..] github.com/NebulousLabs/Sia/sync github.com/NebulousLabs/Sia/types returned exit code 2 Added tag(s

Processed: Re: Bug#1009308: libopenexr-dev: Missing Breaks/Replaces libilmbase-dev

Processing control commands: > severity -1 serious Bug #1009308 [libopenexr-dev] libopenexr-dev: Missing Breaks/Replaces libilmbase-dev Severity set to 'serious' from 'normal' -- 1009308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009308 Debian Bug Tracking System Contact ow...@bugs.deb

Processed: chromium 1010407

Processing commands for cont...@bugs.debian.org: > retitle 1010407 chromium: does not support older CPUs that lack SSE3 > instructions Bug #1010407 [chromium] chromium: Chromium immediately crashes on Illegal instruction on Buster i386 Changed Bug title to 'chromium: does not support older CPUs

Bug#1010407: chromium: Chromium immediately crashes on Illegal instruction on Buster i386

Severity: normal Control: retitle 1010407 chromium: does not support older CPUs without SSE3 instructions Tags: wontfix Thanks for the report! It looks like chromium officially dropped older CPU support: https://www.tomshardware.com/news/chrome-stops-working-on-old-processors There's not

Bug#1010408: ftbfs: Error: Failed to find "global.fs = fs;" in Go JS shim code

Source: golang-github-evanw-esbuild Version: 0.14.25-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, your package FTBFS, however a trivial upstream update fixes it (took me a minute to rebuild it). Jérémy. -- System Informatio

Bug#986130: ,fetchmailconf: No update/upgrade possible due to error

Does this warrant "grave"? This looks like trying to configure fetchmailconf before fetchmail is configured, and before fetchmail saw configuration. However why is fetchmail being "restart"ed? It could not have been running before...

Processed: severity of 1008702 is normal, reassign 1008702 to ftp.debian.org ...

Processing commands for cont...@bugs.debian.org: > severity 1008702 normal Bug #1008702 [src:ketchup] Should ketchup be removed? Severity set to 'normal' from 'serious' > reassign 1008702 ftp.debian.org Bug #1008702 [src:ketchup] Should ketchup be removed? Bug reassigned from package 'src:ketchup'

Bug#1010057: marked as done (digikam: Failed when generated data-base)

Your message dated Sat, 30 Apr 2022 13:30:52 -0500 with message-id <4395186.LvFx2qVVIh@riemann> and subject line Re: Bug#1010057: digikam: Failed when generated data-base has caused the Debian Bug report #1010057, regarding digikam: Failed when generated data-base to be marked as done. This means

Bug#1010112: virtualbox: 6.1.34-dfsg-2 broken, guest VM display window stays black with blinking cursor

False alarm. The answer is given here: https://forums.virtualbox.org/viewtopic.php?f=7&t=105468 In my case after exiting QEMU-KVM virt-manager the qemu-system-x86 and kvm-nx-lpage-re processes remain live. Since only one hypervisor is active at a time the fix is to simply kill these processes

Bug#1006981: marked as done (rails: flaky autopkgtest on some ci.d.n architectures)

Your message dated Sat, 30 Apr 2022 13:20:23 + with message-id and subject line Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2 has caused the Debian Bug report #1006981, regarding rails: flaky autopkgtest on some ci.d.n architectures to be marked as done. This means that you claim that the prob

Bug#1010195: marked as done (astroquery: autopkgtest regression: No module named 'PIL')

Your message dated Sat, 30 Apr 2022 12:03:47 + with message-id and subject line Bug#1010195: fixed in astroquery 0.4.6+dfsg-2 has caused the Debian Bug report #1010195, regarding astroquery: autopkgtest regression: No module named 'PIL' to be marked as done. This means that you claim that the

Bug#1008095: marked as done (qemu-system-data: missing Breaks: qemu-system-ppc (<< 1:6.1-4~))

Your message dated Sat, 30 Apr 2022 11:49:52 + with message-id and subject line Bug#1008095: fixed in qemu 1:7.0+dfsg-2 has caused the Debian Bug report #1008095, regarding qemu-system-data: missing Breaks: qemu-system-ppc (<< 1:6.1-4~) to be marked as done. This means that you claim that the

Bug#1010355: marked as forwarded (CVE-2022-0530: null pointer dereference on invalid UTF-8 input)

Your message dated Sat, 30 Apr 2022 13:31:01 +0200 with message-id <02708249-7dc8-ab96-1165-0ebe948ac...@unex.es> has caused the report #1010355, regarding CVE-2022-0530: null pointer dereference on invalid UTF-8 input to be marked as having been forwarded to the upstream software author(s) "Step

Bug#1010355: Fwd: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid UTF-8 input

Hello Stephen. Can you take a look at this? The Debian version of procmail in unstable has a patch for this which I took from git, and I was planning to just apply it to bullseye and buster, but apparently it's not enough to fix the issue. Thanks. Mensaje reenviado Asunto:

Bug#1010392: golang-github-smallstep-certificates: FTBFS on arm64

Source: golang-github-smallstep-certificates Version: 0.15.15-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) golang-github-smallstep-certificates FTBFS on arm64: okgithub.com/smallstep/certificates/templates 0.064s FAIL dh_auto_t

Processed: src:ccache: fails to migrate to testing for too long: FTBFS on s390x and autopkgtest regression

Processing control commands: > close -1 4.6-1 Bug #1010389 [src:ccache] src:ccache: fails to migrate to testing for too long: FTBFS on s390x and autopkgtest regression Marked as fixed in versions ccache/4.6-1. Bug #1010389 [src:ccache] src:ccache: fails to migrate to testing for too long: FTBFS

Bug#1003933: marked as done (w3c-sgml-lib: catalogs for MathML 2.0 are incomplete)

Your message dated Sat, 30 Apr 2022 09:49:11 + with message-id and subject line Bug#1003933: fixed in w3c-sgml-lib 1.3-3 has caused the Debian Bug report #1003933, regarding w3c-sgml-lib: catalogs for MathML 2.0 are incomplete to be marked as done. This means that you claim that the problem h

Bug#1010389: src:ccache: fails to migrate to testing for too long: FTBFS on s390x and autopkgtest regression

Source: ccache Version: 4.5.1-1 Severity: serious Control: close -1 4.6-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1007732 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and uns

Bug#1010344: FTBFS: some test fails with "An export name cannot include a lone surrogate"

Hi, could you take a look at this issue ? It seems related to node-eslint-* updates. Cheers, Yadd

Bug#1010387: golang-github-google-wire: FTBFS on armhf

Source: golang-github-google-wire Version: 0.5.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org golang-github-google-wire FTBFS on armhf: === CONT TestWire/FieldsOfStructDoNotProvidePtrToField runt

Bug#1010386: golang-v2ray-core: FTBFS on armel and armhf

Source: golang-v2ray-core Version: 4.34.0-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org golang-v2ray-core FTBFS on armel and armhf: ok v2ray.com/core/transport/internet/websocket 5.116s ==