Bug#1016828: marked as done (poc-streamer: flaky autopkgtest: regularly times out on i386)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Aug 2022 05:19:15 + with message-id and subject line Bug#1016828: fixed in poc-streamer 0.4.2-7 has caused the Debian Bug report #1016828, regarding poc-streamer: flaky autopkgtest: regularly times out on i386 to be marked as done. This means that you claim that

Bug#1016828: poc-streamer: flaky autopkgtest: regularly times out on i386

2022-08-21 Thread Eriberto
> I looked at the results of the autopkgtest of you package because it was > showing up on our "slow" page [1]. I noticed that there were several > runs that took 8:21 (our timeout time per test times 3), while > successful runs more in the order of a minute. > > Because the unstable-to-testing

Bug#952159: rust-nodrop-union: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2022-08-21 Thread Eric Long
> Was this patch just a result of general QA activity or is there some > program you are trying to package? Yes, this patch is for QA. I assumed there are important packages that rely on this abandoned crate, hence the workaround. Otherwise removing it from Debian seems a better choice.

Processed: unarchiving 574317, reopening 574317, closing 574317

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:libdatetime-format-datemanip-perl was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 574317 Bug #574317 {Done: Alexander Reichle-Schmehl }

Bug#1016831: marked as done (libminc: FTBFS on mipsel, mips64el)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 21:05:58 -0500 with message-id <3191568.44csPzL39Z@riemann> and subject line Re: libminc: FTBFS on mipsel, mips64el has caused the Debian Bug report #1016831, regarding libminc: FTBFS on mipsel, mips64el to be marked as done. This means that you claim that the

Processed: built now

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1017537 dietlibc: may FTBFS on armel due to buildd misconfiguration Bug #1017537 [src:dietlibc] dietlibc: FTBFS on armel: illegal instruction Changed Bug title to 'dietlibc: may FTBFS on armel due to buildd misconfiguration' from

Bug#1017537: armel buildd misconfiguration (was Re: Bug#1017537: dietlibc: FTBFS on armel)

2022-08-21 Thread Thorsten Glaser
outlook 1017537 some armel buildds are misconfigured and lack SWP emulation thanks Dixi quod… ># if __ARM_ARCH__ < 6 > swp r0, r1, [r2] ># else And this, after some research, is it. This is needed for armel, which is v5. Apparently, Linux has SWP emulation for v7/v8 hosts, but at

Processed: armel buildd misconfiguration (was Re: Bug#1017537: dietlibc: FTBFS on armel)

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > outlook 1017537 some armel buildds are misconfigured and lack SWP emulation Outlook replaced with message bug 1017537 message > thanks Stopping processing here. Please contact me if you need assistance. -- 1017537:

Processed: Re: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > found -1 1:28.1+1-2 Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB coredump Marked as found in versions emacs/1:28.1+1-2. > severity -1 serious Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB coredump Severity

Processed: forcibly merging 1017853 1017698 1017798 1017779

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1017853 1017698 1017798 1017779 Bug #1017853 [emacs-common] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Bug #1017779 [emacs-common] emacs-common dies in postinst with "corrupted double-linked list"

Processed: reassign 1017698 to emacs-common

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1017698 emacs-common Bug #1017698 [emacs-gtk] emacs-gtk: core dump with unsorted double linked list corrupted Bug reassigned from package 'emacs-gtk' to 'emacs-common'. Ignoring request to alter found versions of bug #1017698 to the

Processed: reassign 1017853 to emacsen-common

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1017853 emacsen-common Bug #1017853 [emacs-nox] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Bug reassigned from package 'emacs-nox' to 'emacsen-common'. No longer marked as found in versions

Processed: reassign 1017853 to emacs-common

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1017853 emacs-common Bug #1017853 [emacsen-common] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Bug reassigned from package 'emacsen-common' to 'emacs-common'. Ignoring request to alter found versions

Processed: affects 1017853

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017853 emacsen-nox Bug #1017853 [emacsen-common] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Added indication that 1017853 affects emacsen-nox > thanks Stopping processing here. Please contact me if

Bug#1017537: dietlibc: FTBFS on armel

2022-08-21 Thread Thorsten Glaser
Dixi quod… >In case this makes anyone immediately think of whatever it is: Code looks right enough (with an explanation of why this only fails on armel but not on armhf which is perfectly fine): $ cat arm/__testandset.S #include "arm-features.h" FUNC_START __testandset mov r2,

Processed: your mail

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > outlook 1017537 fails on porterbox/bullseye as well, suspect 64-bit host to > be an issue Outlook recorded from message bug 1017537 message > thanks Stopping processing here. Please contact me if you need assistance. -- 1017537:

Bug#1017538: marked as done (dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Mon, 22 Aug 2022 00:23:57 + (UTC) with message-id and subject line Re: Bug#1017538: dietlibc: FTBFS on armhf has caused the Debian Bug report #1017538, regarding dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode to be marked as done. This

Processed (with 1 error): forcibly merging 1017853 1017698 1017798 1017779

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1017853 1017698 1017798 1017779 Bug #1017853 [emacs-nox] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Unable to merge bugs because: package of #1017779 is 'emacs-common' not 'emacs-nox' package of

Bug#1017537: dietlibc: FTBFS on armel

2022-08-21 Thread Thorsten Glaser
>but it ALSO fails in a bullseye chroot, so this is possibly not related In case this makes anyone immediately think of whatever it is: (gdb) r Starting program: /home/tg/dietlibc-0.34~cvs20160606-el-11/debian/unittests/ttt Program received signal SIGILL, Illegal instruction. __testandset () at

Processed: affects 1017853

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017853 emacs-lucid Bug #1017853 [emacs-nox] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Added indication that 1017853 affects emacs-lucid > thanks Stopping processing here. Please contact me if you

Processed: affects 1017853

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017853 emacs-gtk Bug #1017853 [emacs-nox] emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed Added indication that 1017853 affects emacs-gtk > thanks Stopping processing here. Please contact me if you need

Processed (with 1 error): Bug#1017537: dietlibc: FTBFS on armel

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > outcome 1017537 fails on porterbox/bullseye as well, suspect 64-bit host to > be an issue Unknown command or malformed arguments to command. > tags 1017537 + help Bug #1017537 [src:dietlibc] dietlibc: FTBFS on armel: illegal instruction Added

Bug#1017537: dietlibc: FTBFS on armel

2022-08-21 Thread Thorsten Glaser
outcome 1017537 fails on porterbox/bullseye as well, suspect 64-bit host to be an issue tags 1017537 + help thanks In contrast to armhf, which works fine on the porterbox (amdahl; abel, which I normally use, is currently down) for me, this one also fails, but it ALSO fails in a bullseye chroot,

Processed: Re: Bug#1017538: dietlibc: FTBFS on armhf

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1017538 + unreproducible Bug #1017538 [src:dietlibc] dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1017538: dietlibc: FTBFS on armhf

2022-08-21 Thread Thorsten Glaser
tags 1017538 + unreproducible thanks This builds fine in a sid-armhf chroot on amdahl.

Processed: bump severity for poppler transition

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1012818 [inkscape] inkscape: Please update for Poppler 22.06 Severity set to 'serious' from 'important' -- 1012818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012818 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: bump severity for poppler transition

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1012809 [openboard] openboard: Update for Poppler 22.06 Severity set to 'serious' from 'normal' -- 1012809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1017041: marked as done (golang-github-bmatsuo-lmdb-go: flaky autopkgtest on s390x: segfaults)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 22:50:02 + with message-id and subject line Bug#1017041: fixed in golang-github-bmatsuo-lmdb-go 1.8.0+git20170215.a14b5a3-4 has caused the Debian Bug report #1017041, regarding golang-github-bmatsuo-lmdb-go: flaky autopkgtest on s390x: segfaults to be

Bug#1016750: [Sbcl-bugs] Heap exhaustion problem with SBCL 2.2.6 on armel, armhf

2022-08-21 Thread Sean Whitton
Hello, On Tue 09 Aug 2022 at 02:53PM -04, Douglas Katzman wrote: > > https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-ironclad/24441370/log.gz > shows a GC invariant failure, not a heap exhaustion. > How do I identify the exact git revision of SBCL you're using? I can only > guess at

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-08-21 Thread Axel Beckert
Control: severity -1 grave Control: retitle -1 emacs-common: Endless fork loop at installation and at run time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el Hi, raising from serious (package installation fails) to grave (unusable) as

Processed: Re: Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #1017845 [emacs-common] Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el Severity set to 'grave' from 'serious' > retitle

Bug#1009917: marked as done (gtk4 applications randomly crash on Mobian Pinephone)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 22:05:59 + with message-id and subject line Bug#1009917: fixed in gtk4 4.7.2+ds-3 has caused the Debian Bug report #1009917, regarding gtk4 applications randomly crash on Mobian Pinephone to be marked as done. This means that you claim that the problem has

Bug#1017256: marked as done (pandoc-citeproc-preamble: FTBFS: pandoc-citeproc: Error in $: Incompatible API versions: encoded with [1,22,2] but attempted to decode with [1,20].)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 21:52:34 + with message-id and subject line Bug#1017256: fixed in pandoc-citeproc-preamble 1.7-1 has caused the Debian Bug report #1017256, regarding pandoc-citeproc-preamble: FTBFS: pandoc-citeproc: Error in $: Incompatible API versions: encoded with

Bug#1006026: marked as done (ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations.)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 21:52:41 + with message-id and subject line Bug#1006026: fixed in ruby-axiom-types 0.1.1-3 has caused the Debian Bug report #1006026, regarding ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for

Processed: bug 1017850 is forwarded to https://github.com/ruby-grape/grape/issues/2278

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1017850 https://github.com/ruby-grape/grape/issues/2278 Bug #1017850 [src:ruby-grape] ruby-grape: FTBFS with ruby-rack-test 2.0: ERROR: Test "ruby3.0" failed: Failure/Error: Set Bug forwarded-to-address to

Bug#1017753: autopkgtest-virt-lxc regularly fails to start or return from reboot

2022-08-21 Thread Simon McVittie
On Sun, 21 Aug 2022 at 21:53:02 +0200, Paul Gevers wrote: > I think I found part of the issue: > > paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- "runlevel" > ; echo $? && sudo lxc-stop test > unknown > 1 > paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- "if [

Processed: Bug#1006026 marked as pending in ruby-axiom-types

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1006026 [src:ruby-axiom-types] ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations. Added tag(s) pending. -- 1006026:

Bug#1006026: marked as pending in ruby-axiom-types

2022-08-21 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1006026 in ruby-axiom-types 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:

Processed: affects 1017845

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017845 + elpa-ement Bug #1017845 [emacs-common] Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el Added indication

Bug#1017870: gnome-shell-extension-gsconnect: Not compatible with gnome-shell 43

2022-08-21 Thread Jeremy Bicha
Source: gnome-shell-extension-gsconnect Version: 50-3 Severity: serious Tags: upstream Forwarded: https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1428 gnome-shell-extension-gsconnect isn't compatible with gnome-shell 43, currently available in Debian Experimental. Thank you,

Bug#1016574: marked as done (adduser: dpkg conffile prompt for adduser.conf even though unmodified)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 20:23:31 + with message-id and subject line Bug#1016574: fixed in adduser 3.127 has caused the Debian Bug report #1016574, regarding adduser: dpkg conffile prompt for adduser.conf even though unmodified to be marked as done. This means that you claim that

Bug#1017348: autopkgtest regression on ppc64el

2022-08-21 Thread Alexis Bienvenüe
Hi. Thanks for the report. This autopkgtest fail comes from a call to cv::boundingRect that works differently between OpenCV versions 4.6.0+dfsg-4+b1 from testing and 4.6.0+dfsg-6+b1 from unstable, on a ppc64el virtual machine. Running the sample code below, which computes a bounding rectangle

Bug#1017798: emacs-common can't be installed

2022-08-21 Thread Kurt Meyer
I've upgraded emacs-common on both of my computers without issue, so the issue that the OP is experiencing may be unique to the elpa-htmlize package, which I do not have installed on either of my computers.

Bug#1017753: autopkgtest-virt-lxc regularly fails to start or return from reboot

2022-08-21 Thread Paul Gevers
Hi, I think I found part of the issue: paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- "runlevel" ; echo $? && sudo lxc-stop test unknown 1 paul@mulciber ~ $ sudo lxc-start test && sudo lxc-attach test -- "if [ -d /run/systemd/system ]; then echo systemd ; exit 0 ; else echo

Bug#1017853: emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed

2022-08-21 Thread David Bremner
David Bremner writes: > Package: emacs-nox > Version: 1:28.1+1-2 > Severity: serious > Justification: does not install > X-Debbugs-Cc: debian-emac...@lists.debian.org Here is the output of strace in case it is useful. It uncompresses to 16M, just FYI. strace.log.xz Description:

Bug#1017204: marked as done (elastix: FTBFS: build-dependency not installable: libinsighttoolkit5-dev)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 13:45:38 -0500 with message-id <2113895.irdbgypaU6@riemann> and subject line Re: elastix: FTBFS: build-dependency not installable: libinsighttoolkit5-dev has caused the Debian Bug report #1017204, regarding elastix: FTBFS: build-dependency not installable:

Bug#952159: rust-nodrop-union: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2022-08-21 Thread Peter Michael Green
I have written a merge request [1] to fix FTBFS on all platforms. Tested on my dev machine on amd64 and riscv64. If more helps are needed, please let me know. Thanks for the patch, Was this patch just a result of general QA activity or is there some program you are trying to package? We can

Bug#991082: marked as done (gir1.2-gtd-1.0 has empty Depends)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 18:34:21 + with message-id and subject line Bug#991082: fixed in endeavour 42.0-2 has caused the Debian Bug report #991082, regarding gir1.2-gtd-1.0 has empty Depends to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: scipy: FTBFS on 32 bit arches: TestMLS: Invalid call to pythranized function

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/scipy/scipy/pull/16646 Bug #1017862 [src:scipy] scipy: FTBFS on 32 bit arches: TestMLS: Invalid call to pythranized function Set Bug forwarded-to-address to 'https://github.com/scipy/scipy/pull/16646'. -- 1017862:

Bug#1017862: scipy: FTBFS on 32 bit arches: TestMLS: Invalid call to pythranized function

2022-08-21 Thread Drew Parsons
Source: scipy Version: 1.8.1-8 Severity: serious Justification: FTBFS Control: forwarded -1 https://github.com/scipy/scipy/pull/16646 scipy FTBFS on 32 bits arches after pythran support was recently activated. The error looks like: ___ TestMLS.test_mls_inputs

Bug#1016830: marked as done (insighttoolkit5: FTBFS on amd64)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 13:04:02 -0500 with message-id <2250986.ElGaqSPkdT@riemann> and subject line Re: insighttoolkit5: FTBFS on amd64 has caused the Debian Bug report #1016830, regarding insighttoolkit5: FTBFS on amd64 to be marked as done. This means that you claim that the

Bug#991082: marked as done (gir1.2-gtd-1.0 has empty Depends)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 18:00:11 + with message-id and subject line Bug#991082: fixed in endeavour 42.0-1 has caused the Debian Bug report #991082, regarding gir1.2-gtd-1.0 has empty Depends to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1017075: #1017075 dask - autopkgtest regression on i386 and armhf

2022-08-21 Thread Drew Parsons
On 2022-08-21 19:04, Drew Parsons wrote: In regards to bug severity, the dask debci failures are now marked as "Not a regression" so they won't hold up migration of dask. Graham, should the bug severity therefore be reduced from Serious back down to Important to enable migration of both dask

Processed: closing 1012936

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1012936 Bug #1012936 [src:juce] giada: ftbfs with GCC-12 Bug #1015036 [src:juce] giada: FTBFS: pluginHost.h:63:22: error: ‘bool giada::m::PluginHost::Info::getCurrentPosition(juce::AudioPlayHead::CurrentPositionInfo&)’ marked ‘override’,

Bug#1017075: #1017075 dask - autopkgtest regression on i386 and armhf

2022-08-21 Thread Drew Parsons
Control: forwarded 1017075 https://github.com/dask/dask/issues/8620 As far as I can tell this issue will be fixed by the patch discussed in upstream Issue#8620. In regards to bug severity, the dask debci failures are now marked as "Not a regression" so they won't hold up migration of dask.

Processed: Re: #1017075 dask - autopkgtest regression on i386 and armhf

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded 1017075 https://github.com/dask/dask/issues/8620 Bug #1017075 [dask] dask - autopkgtest regression on i386 and armhf Set Bug forwarded-to-address to 'https://github.com/dask/dask/issues/8620'. -- 1017075:

Processed: Re: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #1011165 [mediathekview] org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found Severity set to 'wishlist' from 'serious' > retitle -1 mediathekview update discussion Bug #1011165 [mediathekview]

Bug#1011165: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found

2022-08-21 Thread Markus Koschany
Control: severity -1 wishlist Control: retitle -1 mediathekview update discussion I have fixed the underlying problem by using an internal version of the h2 database now. I will try to package tilesfx and glazedlists next. signature.asc Description: This is a digitally signed message part

Bug#1017281: marked as done (golang-github-pascaldekloe-goe: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/pascaldekloe/goe/el github.com/pascaldekloe/goe/metrics github

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 16:08:04 + with message-id and subject line Bug#1017281: fixed in golang-github-pascaldekloe-goe 0.1.0-4 has caused the Debian Bug report #1017281, regarding golang-github-pascaldekloe-goe: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8

Processed: re: dwarf2sources FTBFS with rust-object 0.20

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 998306 serious Bug #998306 [dwarf2sources] dwarf2sources FTBFS with rust-object 0.20 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 998306:

Bug#1017853: emacs-nox: byte compiling debian-startup.el fails if emacs-el is not installed

2022-08-21 Thread David Bremner
Package: emacs-nox Version: 1:28.1+1-2 Severity: serious Justification: does not install X-Debbugs-Cc: debian-emac...@lists.debian.org Recipe to duplicate === (assuming schroot is set up in a more or less standard way with a chroot called sid, and session support). % schroot -c

Bug#1017798: please test

2022-08-21 Thread David Bremner
Can you test if having emacs-el installed (e.g. via recommends) allows the installation / postinst to complete? That will help narrow down what the bug is. d

Processed (with 1 error): Re: rust-fasteval FTBFS: test failure

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > tags 1011628 + patch Bug #1011628 [src:rust-fasteval] rust-fasteval FTBFS: test failure Added tag(s) patch. > thanks Unknown command or malformed arguments to command. -- 1011628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011628 Debian Bug Tracking

Bug#1011628: rust-fasteval FTBFS: test failure

2022-08-21 Thread Eric Long
Control: tags 1011628 + patch Control: thanks Hello Adrian and Maintainers, I have submitted a merge request [1] that fixes the tests and FTBFS. Please let me know if I missed something. Cheers, Eric [1]: https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/378

Bug#1017279: marked as done (golang-github-hashicorp-go-sockaddr: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/hashicorp/go-sockaddr returned exit code 1)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 15:19:33 + with message-id and subject line Bug#1017279: fixed in golang-github-hashicorp-go-sockaddr 1.0.2-1 has caused the Debian Bug report #1017279, regarding golang-github-hashicorp-go-sockaddr: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu &&

Processed: Re: ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations.

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy > frozen objects, rspec-mocks relies on proxies for method stubbing and > expectations. Bug #1006026 [src:ruby-axiom-types] ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed:

Bug#1006026: ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations.

2022-08-21 Thread Antonio Terceiro
Control: retitle -1 ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for method stubbing and expectations. I tried this locally and couldn't reproduce twice in row, first on my main system, then with sbuild. I then tried 10 times in a

Bug#1012987: marked as done (libpodofo: ftbfs with GCC-12)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 14:49:18 + with message-id and subject line Bug#1012987: fixed in libpodofo 0.9.8+dfsg-3 has caused the Debian Bug report #1012987, regarding libpodofo: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1016452: marked as done (loggerhead: autopkgtest regression: No module named 'loggerhead.tests')

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 14:36:14 + with message-id and subject line Bug#1016452: fixed in loggerhead 2.0.0-1 has caused the Debian Bug report #1016452, regarding loggerhead: autopkgtest regression: No module named 'loggerhead.tests' to be marked as done. This means that you claim

Bug#1013545: marked as done (gradle: FTBFS: WindowsConsoleDetector.java:19: error: cannot find symbol)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 14:35:53 + with message-id and subject line Bug#1013545: fixed in gradle 4.4.1-15 has caused the Debian Bug report #1013545, regarding gradle: FTBFS: WindowsConsoleDetector.java:19: error: cannot find symbol to be marked as done. This means that you claim

Bug#1012214: marked as done (gradle: FTBFS with jansi 2)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 14:35:53 + with message-id and subject line Bug#1012214: fixed in gradle 4.4.1-15 has caused the Debian Bug report #1012214, regarding gradle: FTBFS with jansi 2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1005427: marked as done (ruby-rack-test: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(body).to receive(:close))

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 14:36:31 + with message-id and subject line Bug#1005427: fixed in ruby-rack-test 2.0.2-1 has caused the Debian Bug report #1005427, regarding ruby-rack-test: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(body).to receive(:close) to be marked

Processed: Bug#1012987 marked as pending in libpodofo

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1012987 [src:libpodofo] libpodofo: ftbfs with GCC-12 Added tag(s) pending. -- 1012987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1012987: marked as pending in libpodofo

2022-08-21 Thread Mattia Rizzolo
Control: tag -1 pending Hello, Bug #1012987 in libpodofo 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:

Bug#1013932: marked as done (yade: FTBFS in unstable and testing)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 13:49:23 + with message-id and subject line Bug#1013932: fixed in yade 2022.01a-10 has caused the Debian Bug report #1013932, regarding yade: FTBFS in unstable and testing to be marked as done. This means that you claim that the problem has been dealt

Bug#1013072: marked as done (yade: ftbfs with GCC-12)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 13:49:23 + with message-id and subject line Bug#1013072: fixed in yade 2022.01a-10 has caused the Debian Bug report #1013072, regarding yade: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: affects 1017834

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017834 + emacs emacs-gtk Bug #1017834 [elpa-cider] elpa-cider: emacs 28.1 upgrade fails with byte compiling elpa-cider Added indication that 1017834 affects emacs and emacs-gtk > thanks Stopping processing here. Please contact me if

Processed: affects 1017845

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1017845 + elpa-smart-mode-line-powerline-theme Bug #1017845 [emacs-common] Endless fork loop at installation time: /usr/bin/emacs --batch -l

Processed: Re: Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + elpa-git-commit Bug #1017845 [emacs-common] Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el Added indication that 1017845 affects

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-08-21 Thread Axel Beckert
Control: affects -1 + elpa-git-commit Hi, Axel Beckert wrote: > upgrading emacs respectively emacs-gtk from 27.1 to 28.1 causes an > endless fork loops during package configuration time: One more interesting line of output at the very beginning: Setting up emacs-gtk (1:28.1+1-2) ... Deep

Processed: severity of 1017834 is serious

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1017834 serious Bug #1017834 [elpa-cider] elpa-cider: emacs 28.1 upgrade fails with byte compiling elpa-cider Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: severity of 1017833 is serious, affects 1017833

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1017833 serious Bug #1017833 [elpa-elscreen] elpa-elscreen: emacs 28.1 upgrade failure with byte compiling of elpa-elscreen Severity set to 'serious' from 'normal' > affects 1017833 + emacs emacs-gtk Bug #1017833 [elpa-elscreen]

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-08-21 Thread Axel Beckert
Package: emacs-common Version: 1:28.1+1-2 Severity: serious X-Debbugs-Cc: a...@debian.org Control: affects -1 elpa-folding elpa-org elpa-git-timemachine elpa-password-store Hi, upgrading emacs respectively emacs-gtk from 27.1 to 28.1 causes an endless fork loops during package configuration

Processed: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > affects -1 elpa-folding elpa-org elpa-git-timemachine elpa-password-store Bug #1017845 [emacs-common] Endless fork loop at installation time: /usr/bin/emacs --batch -l

Bug#1011165: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found

2022-08-21 Thread Markus Koschany
Hi Helge, Am Sonntag, dem 21.08.2022 um 08:46 +0200 schrieb Helge Kreutzmann: > Hello Markus, > On Tue, Aug 09, 2022 at 03:09:08PM +0200, Markus Koschany wrote: > > I have pushed a new branch which includes version 13.9.1. > > … > > > Those are the major issues we have to fix in order to

Bug#1017270: marked as done (golang-github-biogo-hts: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/biogo/hts/bam github.com/biogo/hts/bgzf github.com/biog

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 11:34:12 + with message-id and subject line Bug#1017270: fixed in golang-github-biogo-hts 1.4.3+dfsg1-2 has caused the Debian Bug report #1017270, regarding golang-github-biogo-hts: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v

Bug#1017717: cp2k: FTBFS: symbol lookup error: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_ext3x.so: undefined symbol: pmix_value_load

2022-08-21 Thread Graham Inggs
Hi Andrius This is due to the bad upload of pmix, see #1017107 and #1017356. Regards Graham

Processed: glibc 2.34 is now in testing/unstable

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # clasp > reassign 1004022 src:clasp Bug #1004022 [clasp] clasp: Clasp FTBFS with glibc 2.34 Bug reassigned from package 'clasp' to 'src:clasp'. No longer marked as found in versions clasp/3.3.5-4. Ignoring request to alter fixed versions of bug

Processed (with 1 error): glibc 2.34 is now in testing/unstable

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # knxd > reassign 1004310 src:knxd Bug #1004310 [knxd] knxd: ftbfs with glibc 2.34: don't use common unix function name as variable name Bug reassigned from package 'knxd' to 'src:knxd'. No longer marked as found in versions knxd/0.14.46-1.

Processed: your mail

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 952159 + patch Bug #952159 [src:rust-nodrop-union] rust-nodrop-union: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need

Bug#952159: rust-nodrop-union: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

2022-08-21 Thread Eric Long
tags 952159 + patch thanks Hello Lucas and Maintainers, I have written a merge request [1] to fix FTBFS on all platforms. Tested on my dev machine on amd64 and riscv64. If more helps are needed, please let me know. Cheers, Eric [1]:

Processed: Re: gr-funcube FTBFS witn fmtlib 9.0.0 (?)

2022-08-21 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/dl1ksv/gr-funcube/pull/8 Bug #1017802 [src:gr-funcube] gr-funcube FTBFS witn fmtlib 9.0.0 (?) Set Bug forwarded-to-address to 'https://github.com/dl1ksv/gr-funcube/pull/8'. > tags -1 + patch Bug #1017802 [src:gr-funcube] gr-funcube

Bug#1017802: gr-funcube FTBFS witn fmtlib 9.0.0 (?)

2022-08-21 Thread Shengjing Zhu
Control: forwarded -1 https://github.com/dl1ksv/gr-funcube/pull/8 Control: tags -1 + patch Please see the patch https://github.com/dl1ksv/gr-funcube/pull/8

Processed: tagging 965710

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 965710 + ftbfs Bug #965710 [src:lua5.1-policy] lua5.1-policy: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965710 to the same tags previously set > thanks Stopping processing here. Please

Processed: found 1014717 in 2.0.8.1-2

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1014717 2.0.8.1-2 Bug #1014717 {Done: Antonio Terceiro } [src:ruby-sinatra] ruby-sinatra: CVE-2022-29970 Marked as found in versions ruby-sinatra/2.0.8.1-2. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1017199: marked as done (rumur: FTBFS: AssertionError: Unexpected checker exit status -31:)

2022-08-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Aug 2022 07:52:04 + with message-id and subject line Bug#1017199: fixed in rumur 2022.08.20-1 has caused the Debian Bug report #1017199, regarding rumur: FTBFS: AssertionError: Unexpected checker exit status -31: to be marked as done. This means that you claim that

Bug#1011165: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found

2022-08-21 Thread Helge Kreutzmann
Hello Markus, On Tue, Aug 09, 2022 at 03:09:08PM +0200, Markus Koschany wrote: > I have pushed a new branch which includes version 13.9.1. … > Those are the major issues we have to fix in order to package a new upstream > release of mediathekview. And we also need to fix kotlin in unstable. If >

Bug#1017818: elpa-jabber: Fails to compile with Emacs 28: Error: Wrong number of arguments: make-obsolete, 2

2022-08-21 Thread Yavor Doganov
Package: elpa-jabber Version: 0.8.92+git98dc8e-7 Severity: serious The upgrade from Emacs 27 to 28 aborts because byte-compilation of elpa-jabber fails with the following error(s): | In toplevel form: | jabber-vcard.el:67:1: Error: Wrong number of arguments: make-obsolete, 2 The full log is:

Processed: tagging 1005719 ...

2022-08-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1005719 + patch Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Added tag(s) patch. > forwarded 1005719 > https://patches.ubuntu.com/m/mumble/mumble_1.3.4-1ubuntu1.patch >

Bug#1001661: notcurses: flaky autopkgtests on armhf

2022-08-21 Thread Paul Gevers
Hi bunk, On 20-08-2022 21:38, Adrian Bunk wrote: A package with a flaky autopkgtest is worse than a package without an autopkgtest. Not having working and used software in the next stable is also worse than disabling the autopkgtest. One possible mitigation would be to disable the autopkgtest

  1   2   >