Bug#976734: lacme: unhelpful error message: accept: Invalid argument at /usr/libexec/lacme/webserver line 80.

Quoting Jonas Smedegaard (2020-12-08 13:25:28) > Quoting Guilhem Moulin (2020-12-08 12:04:15) > > Could you suggest a better error message here? > > Generally, I think is might help if informed who says what. I.e. when > passing on an error message either received from Letsencrypt or captured

Bug#976936: wpewebkit: FTBFS on ppc64el: dh_auto_build: error: cd obj-powerpc64le-linux-gnu && LC_ALL=C.UTF-8 ninja -j160 -v returned exit code 1

Control: tags -1 moreinfo On Wed 09 Dec 2020 09:42:53 AM CET, Lucas Nussbaum wrote: > Source: wpewebkit > Version: 2.30.3-1 > Severity: serious > Justification: FTBFS on ppc64el > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el > > Hi, >

Bug#976959: systemd: Please package systemd-repart

Package: systemd Version: 246.6-2~bpo10+1 Severity: wishlist Dear systemd maintainers, judging from salsa [1] and the file lists of the systemd package on buster-backports and sid, systemd is currently built without the the systemd-repart binary. It would be great if this tool could be

Bug#976958: U-boot expects environment on FAT, however default is ext2

Package: u-boot-sunxi Version: 2019.01+dfsg-7 U-Boot images are configured with CONFIG_ENV_IS_IN_FAT=y, however the default debian install configures all partitions (even /boot) as ext2/4 filesystem. Although this don't impact on proper boot as u-boot supports ext2 and can load the boot-script,

Bug#974530: SyntaxWarning: "is not" with a literal. Did you mean "!="?

Package: bleachbit Version: 3.9.0-1 Followup-For: Bug #974530 X-Debbugs-Cc: witold.bary...@gmail.com This was fixed upstream in April 2020: https://github.com/bleachbit/bleachbit/commit/e5cc3263ad8038d1e274f67ba5071b027c59cca2 Updating a Debian package to 4.1.x from upstream would be the best

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

Package: nvidia-legacy-340xx-driver Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com Thank you very much! I promise to do my best to keep the driver in the repo. -- Package-specific info: uname -a: Linux mitsos 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux

Bug#976957: bochs.postinst tries to exectue non existing ./MAKEDEV

Package: bochs Version: 2.6.11+dfsg-3 Severity: normal X-Debbugs-Cc: witold.bary...@gmail.com Hi. Setting up bochs (2.6.11+dfsg-3) ... /var/lib/dpkg/info/bochs.postinst: 33: ./MAKEDEV: not found Setting up ... The bochs.postinst says this: configure) DEVICE=/dev/net/tun if [ ! -e

Bug#976956: ReadyMedia 1.3.0 is out !

Source: minidlna Version: 1.2.1+dfsg-2 The wait is over, 1.3.0 is out: https://sourceforge.net/projects/minidlna/files/minidlna/1.3.0/

Bug#968935: Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5...

Package: python3-xlsxwriter Version: 1.1.2-0.2 Followup-For: Bug #968935 X-Debbugs-Cc: witold.bary...@gmail.com It would be nice to see it fixed in Debian. It was fixed in 1.2.2 upstream over a year ago. Upstream is now at 1.3.7 , which contains many bugs fixes since 1.1.2. Upstream has a full

Bug#976932: gnome-photos: FTBFS on machines with more than 128 cores

Control: retitle -1 gnome-photos: FTBFS on machines with more than 128 cores On Wed, 09 Dec 2020 at 09:35:05 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on ppc64el. At the same time, it did not fail on amd64. > > > cd

Bug#964496: libjson-validator-perl: URL is gone, this is now RC

Hi Wouter, On 2020-12-09 11:27, Wouter Verhelst wrote: > On Wed, Dec 09, 2020 at 09:29:01AM +0200, Andrius Merkys wrote: >> I have uploaded libjson-validator-perl with cache links for OpenAPI >> schemas. Please upload sreview-web 0.6.1-2 without the obstructing cache >> files. > > Yeah. That was

Bug#976955: FTBFS: semver not found

Package: ts-node Version: 9.0.0-1 Severity: serious Tags: ftbfs Here is the relevant part of build log: make[1]: Entering directory '/<>' tsc src/index.spec.ts(4,25): error TS2307: Cannot find module 'semver' or its corresponding type declarations. make[1]: *** [debian/rules:7:

Bug#976919: edk2: FTBFS on ppc64el (arch:all-only src pkg): Could not detected HOST_ARCH from uname results

> Tags: bullseye sid ftbfs > > Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on ppc64el. At the same time, it did not fail on amd64. > > Since this

Bug#971571: transition: libgit2

Hello, On Wed, Dec 9, 2020 at 2:23 AM Sebastian Ramacher wrote: > > So I conclude that it's probably fine to upload libgit2 1.1.0 to unstable > > now? > Okay, then let's do this now. Please go ahead. Awesome, uploaded! I'll take a look at python-pygit2 today as well. So leaves us with

Bug#976912: coyote: FTBFS on ppc64el (arch:all-only src pkg): Magick: abort due to signal 6 (SIGABRT) "Abort"...

Control: reassign -1 gnudatalanguage 1.0.0~rc.3-1 Control: severity -1 important Control: affects -1 src:coyote Control: forwarded -1 https://github.com/gnudatalanguage/gdl/issues/559 This is a known, unresolved problem with gnudatalanguage itself. Best Ole

Bug#976953: NIS account and usb mount

Package: policykit-1 Version: 0.105-25 Severity: important -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US,

Bug#976952: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Source: lmfit-py Version: 1.0.1-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976951: ospd-openvas: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13

Source: ospd-openvas Version: 20.8.0-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976949: golang-github-pkg-term: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/pkg/term github.com/pkg/term/te

Source: golang-github-pkg-term Version: 1.1.0-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976950: xmds2: FTBFS on ppc64el (arch:all-only src pkg): E: Build killed with signal TERM after 150 minutes of inactivity

Source: xmds2 Version: 3.0.0+dfsg-4 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976948: jnr-unixsocket: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.hom

Source: jnr-unixsocket Version: 0.18-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976947: mapbox-variant: FTBFS on ppc64el (arch:all-only src pkg): g++: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?

Source: mapbox-variant Version: 1.2.0-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976945: ruby-awesome-print: FTBFS on ppc64el (arch:all-only src pkg): ERROR: Test "ruby2.7" failed: Failure/Error: expect(my.ai(plain: true)).to eq("#{my.inspect}\n" << `ls -alF #{my.pat

Source: ruby-awesome-print Version: 1.8.0-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

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

Source: rapidjson Version: 1.1.0+dfsg2-6 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec

Source: golang-github-seccomp-libseccomp-golang Version: 0.9.1-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time

Bug#976942: multiboot: FTBFS on ppc64el (arch:all-only src pkg): boot.S:44: Error: unrecognized opcode: `jmp'

Source: multiboot Version: 0.6.96+20101113-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976941: python-prometheus-client: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Source: python-prometheus-client Version: 0.7.1-1.1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did

Bug#976940: golang-refraction-networking-utls: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/refraction-networkin

Source: golang-refraction-networking-utls Version: 0.0~git20201112.f7e7360-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el

Bug#976939: golang-golang-x-arch: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 golang.org/x/arch/arm/armasm golang.org/x/ar

Source: golang-golang-x-arch Version: 0.0~git20200511.f7c7858-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time

Bug#976938: idlastro: FTBFS on ppc64el (arch:all-only src pkg): tests failed

Source: idlastro Version: 2020.10.29+dfsg-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976937: python-trio: FTBFS on ppc64el (arch:all-only src pkg): E: Build killed with signal TERM after 150 minutes of inactivity

Source: python-trio Version: 0.13.0-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976568: My bad

Hi, My bad, I was building with buster, and not unstable. I uploaded the fix anyways. Cheers, Thomas Goirand (zigo)

Bug#976437: libwebkit2gtk-4.0-37: Websocket sends appens extra bytes to messages

Hey there, Could someone point out to the libsoup changes needed exactly? Are we confident they would apply on the 2.64 serie without issue? (and not impact applications that would need changes to adapt) Cheers, Sebastien Bacher Le 08/12/2020 à 19:35, Alberto Garcia a écrit : > On Mon, Dec 07,

Bug#964496: libjson-validator-perl: URL is gone, this is now RC

Control: tags -1 + pending thanks Hi Andrius, On Wed, Dec 09, 2020 at 09:29:01AM +0200, Andrius Merkys wrote: > Hi Wouter, > > I have uploaded libjson-validator-perl with cache links for OpenAPI > schemas. Please upload sreview-web 0.6.1-2 without the obstructing cache > files. Yeah. That was

Bug#976905: src:cyrus-imapd: Please consider enabling JMAP support

Le 09/12/2020 à 10:04, Clement Hermann a écrit : > Package: src:cyrus-imapd > Severity: wishlist > > Hi, > > JMAP is a (relatively) new open standard for mailboxes access, more > mobile friendly and faster than IMAP. Think open source gmail api or > MAPI. It has been developed by people at

Bug#972134: RE: chromium: please, consider moving the package to

team-maintainance to properly maintain it Message-Id: <20201209091550.4b05d60910d92ca4078eb...@gmail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 2 Dec 2020 22:48:40 -0300

Bug#976568: zvmcloudconnector: FTBFS: make[1]: pyversions: No such file or directory

Hi, I tried rebuilding zvmcloudconnector, and I couldn't reproduce the FTBFS. Any idea what's going on? I've downgraded the bug to severity important, and added the tag "moreinfo" in the mean while. Cheers, Thomas Goirand (zigo)

Bug#976919: edk2: FTBFS on ppc64el (arch:all-only src pkg): Could not detected HOST_ARCH from uname results

Control: severity -1 wishlist Control: tag -1 wishlist 09.12.2020 11:59, Lucas Nussbaum wrote: Source: edk2 Version: 2020.08-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages

Bug#976933: libsys-cpuaffinity-perl: FTBFS on ppc64el: lib/xs/cpusetGetCPUCount.xs:5:10: fatal error: cpuset.h: No such file or directory

Source: libsys-cpuaffinity-perl Version: 1.12-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976935: inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.

Source: inkscape Version: 1.0.1-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976934: notmuch: FTBFS on ppc64el: FileNotFoundError: [Errno 2] No such file or directory: '/<>/emacs/notmuch.rsti'

Source: notmuch Version: 0.31.2-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976931: backward-cpp: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && make -j160 test ARGS\+=-j160 returned exit code 2

Source: backward-cpp Version: 1.5-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976930: arduino: FTBFS on ppc64el (arch:all-only src pkg): Target "${platform}-build" does not exist in the project "Arduino".

Source: arduino Version: 2:1.0.5+dfsg2-4.1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976928: spass: FTBFS on ppc64el: iascanner.l:50:10: fatal error: iaparser.h: No such file or directory

Source: spass Version: 3.9-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm

Bug#976926: golang-github-coreos-bbolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short go.etcd.io/bbolt returned exit

Source: golang-github-coreos-bbolt Version: 1.3.5-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did

Bug#976927: cimg: FTBFS on ppc64el (arch:all-only src pkg): g++: error: unrecognized argument in option ‘-mtune=generic’

Source: cimg Version: 2.8.4+dfsg-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976925: scrappie: FTBFS on ppc64el: cc: error: unrecognized command-line option ‘-march=native’; did you mean ‘-mcpu=native’?

Source: scrappie Version: 1.4.2-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976923: cross-toolchain-base: FTBFS on ppc64el (arch:all-only src pkg): build-dependency not installable: binutils-powerpc64le-linux-gnu (= 2.35.1-4)

Source: cross-toolchain-base Version: 47 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976921: flatbuffers: FTBFS on ppc64el: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Source: flatbuffers Version: 1.12.1~git20200711.33e2d80+dfsg1-0.3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

Source: systemd-bootchart Version: 233-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976920: liburcu: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 regtest returned exit code 2

Source: liburcu Version: 0.12.1-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976918: memkind: FTBFS on ppc64el: GetArenaTest.test_TC_MEMKIND_ThreadHash failed

Source: memkind Version: 1.10.1-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976919: edk2: FTBFS on ppc64el (arch:all-only src pkg): Could not detected HOST_ARCH from uname results

Source: edk2 Version: 2020.08-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm

Bug#976917: simavr: FTBFS on ppc64el: obj-powerpc64le-linux-gnu/avr_adc.d:5: *** missing separator. Stop.

Source: simavr Version: 1.6+dfsg-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976916: dune-functions: FTBFS on ppc64el (arch:all-only src pkg): Dune reported error: Dune::Exception [testScalarBasisConst:/<>/dune/functions/functionspacebases/test/gridviewfunctio

Source: dune-functions Version: 2.7.0-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976915: service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow'

Source: service-wrapper-java Version: 3.5.30-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976914: git-buildpackage: FTBFS on ppc64el (arch:all-only src pkg): AssertionError: GitRepositoryError not raised

Source: git-buildpackage Version: 0.9.20 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976913: golang-github-henrydcase-nobs: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_build: error: cd obj-powerpc64le-linux-gnu && go install -trimpath -v -p 160 github.com/henrydcase/nobs/dh/

Source: golang-github-henrydcase-nobs Version: 0.1+git20200305.7d891c7-4 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el

Bug#976912: coyote: FTBFS on ppc64el (arch:all-only src pkg): Magick: abort due to signal 6 (SIGABRT) "Abort"...

Source: coyote Version: 2019.08.19-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976911: node-opencv: FTBFS on ppc64el: not ok 197 Error: Command failed: node /<>/examples/motion-track.js terminate called after throwing an instance of 'cv::Exception' what(): OpenC

Source: node-opencv Version: 7.0.0+git20200310.6c13234-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did

Bug#976910: python-blosc: FTBFS on ppc64el: KeyError: 'flags'

Source: python-blosc Version: 1.9.2+ds1-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail

Bug#976909: h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main'

Source: h2o Version: 2.2.5+dfsg2-5 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976908: spaln: FTBFS on ppc64el: codepot.h:37:55: error: narrowing conversion of ‘-2’ from ‘int’ to ‘char’ [-Wnarrowing]

Source: spaln Version: 2.4.1+dfsg-1 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64

Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

Source: golang-github-boltdb-bolt Version: 1.3.1-7 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did

Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory

Source: libpll Version: 0.3.2-3 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm

Bug#976905: src:cyrus-imapd: Please consider enabling JMAP support

Package: src:cyrus-imapd Severity: wishlist Hi, JMAP is a (relatively) new open standard for mailboxes access, more mobile friendly and faster than IMAP. Think open source gmail api or MAPI. It has been developed by people at Fastmail and is now an IETF standard. Cyrus imapd has jmap support,

Bug#976894: telegram-desktop: Telegram crashes because X11 connection broke

forwarded 976894 https://github.com/telegramdesktop/tdesktop/issues/8506 thanks See also https://gitlab.freedesktop.org/xorg/xserver/-/issues/1072 -- Moritz Schlarb Unix und Cloud Zentrum für Datenverarbeitung Johannes Gutenberg-Universität Mainz OpenPGP-Fingerprint: DF01 2247 BFC6 5501 AFF2

Bug#976894: telegram-desktop: Telegram crashes because X11 connection broke

Sorry, missed to add the following: Manually installing qtwayland5 and then running with QT_QPA_PLATFORM=wayland telegram-desktop makes it run again. On 09.12.20 09:47, Moritz Schlarb wrote: forwarded 976894 https://github.com/telegramdesktop/tdesktop/issues/8506 thanks See also

Bug#976904: prometheus-nginx-exporter: New upstream version 0.8.0 available

Package: prometheus-nginx-exporter Version: 0.6.0+ds-1 Severity: wishlist Hi, prometheus-nginx-exporter v0.8.0 is available since 2020-06-18, the version we have in Debian unstable/testing (0.6.0+ds-1) is ~1 year old. Would be nice to have a current version available in bullseye. regards -mika-

Bug#976902: topydo: provides /usr/bin/todo with incompatible interface compared to devtodo

Package: topydo Version: 0.13-5 Severity: serious Example use of `todo` from devtodo: +--- | Add a task, like so: | | $ todo -a I should really update my homepage | | List all open tasks: | | $ todo | | Mark a task as complete: | | $ todo -d 1.2 +---[ https://swapoff.org/devtodo1.html ] Example

Bug#976903: prometheus-haproxy-exporter: New upstream version 0.11.0 available

Package: prometheus-haproxy-exporter Version: 0.9.0+git20180917+ds-3 Severity: wishlist Hi, prometheus-haproxy-exporter v0.11.0 is available since 2020-06-21, the version we have in Debian (0.9.0+git20180917+ds-3) is >1 year old. Would be nice to have a current version available in bullseye.

Bug#976008: webtest: updating package version to 2.0.35

Hi again, Am Sat, Nov 28, 2020 at 06:32:43AM +0100 schrieb Carsten Schoenert: ... > version 2.0.35 was released in spring of 2020 (2020-04-27) and is > including some Python 3.8 compatibilty fixes. > > With the soft freeze of Bullseye in mind updating the webtest package to > the current most

Bug#976402: Proposed official virtual packages - todo and todo.txt

David Steele writes: > On Fri, Dec 4, 2020 at 1:15 PM Bill Allombert wrote: > >> What about devtodo ? >> >> Reading your summary, it seems that the todo.txt virtual package >> is well specified, but the todo one is not. >> >> Do you envision to have packages depending on todo and then use the >>

Bug#974533: new upstream (20201110 ) for RAPL/Platypus fixes

When will this get fixed in buster? I had thought it might go into the buster stable release update but I don't see it (but also it's non-free so weird). -- Matt Taggart tagg...@debian.org

Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64

Hi Lars, David, On 12/9/20 8:39 AM, Lars Wirzenius wrote: > On Tue, Dec 08, 2020 at 05:12:57PM +, David Edmondson wrote: >> I figured that out today (need to specify a 64 bit CPU) and provided an >> updated set of patches. > > I'll just note that David updated his patches and that I've

Bug#957037: biboumi: ftbfs with GCC-10

Package: biboumi Followup-For: Bug #957037 I have checked that current upstream (9.0) builds flawlessly, and made my release available at https://salsa.debian.org/aluaces-guest/biboumi . Can I be sponsored so we can upload to at least experimental? Thanks!

Bug#976900: pyside2 hard-codes Python 3.8 in it's install files

Package: src:pyside2 Version: 5.15.0-5 Tags: ftbfs sid bullseye Severity: serious $ fgrep 3.8 debian/shiboken2-doc.docs pyside3_build/py3.8-*-relwithdebinfo/shiboken2/doc/html

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

...and my (probably) final report to this mailing list: The most recent crashes/hangs I experienced have no relation to Debian release or Linux kernel, but most likely a hardware issue. I initially experienced a crash similar to what the original report in this bug-thread showed. Suspecting

<    1   2   3