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

[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 the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: poc-streamer
Version: 0.4.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

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 migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put your package on our reject_list for i386.


Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/status/slow/


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: poc-streamer
Source-Version: 0.4.2-7
Done: Joao Eriberto Mota Filho 

We believe that the bug you reported is fixed in the latest version of
poc-streamer, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated 
poc-streamer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 20 Aug 2022 16:15:15 -0300
Source: poc-streamer
Architecture: source
Version: 0.4.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Joao Eriberto Mota Filho 
Closes: 1016828
Changes:
 poc-streamer (0.4.2-7) unstable; urgency=medium
 .
   * QA upload.
   * Fixed flaky autopkgtest over i386. Consequently:
   - debian/salsa-ci.yml: added autopkgtest for testing release.
   - /debian/tests/control: set a timeout and the restriction 'flacky' for
 pob-2250, pob-3119 and pob-fec.
   - Closes: #1016828
Checksums-Sha1:
 9f4c40cd01a157c70ee5ce4adf7b1f9750bcd922 1936 poc-streamer_0.4.2-7.dsc
 24cd4b394ae80a3fa369ac7f3ba7ddf928e0e02f 72104 
poc-streamer_0.4.2-7.debian.tar.xz
 b755a32cb98b924a6940523cd4456d3cbca15780 6608 
poc-streamer_0.4.2-7_source.buildinfo
Checksums-Sha256:
 3f325ce904423456bc188fd99b2cba406a68c9c558076ac9191e8b4f07bf 1936 
poc-streamer_0.4.2-7.dsc
 d764369e390e815c6e34ce8d1719fced3e0c3194609160a1db3009ab3aa29d9a 72104 
poc-streamer_0.4.2-7.debian.tar.xz
 99be0f76ac520c2584eb07dab70b3367572e6e3a46aba8bf827e83c151969550 6608 
poc-streamer_0.4.2-7_source.buildinfo
Files:
 b8651185d728ec3d31e386e6846fefd9 1936 sound optional poc-streamer_0.4.2-7.dsc
 3d2c1fb7e74263a736068f5e16ec7bd8 72104 sound optional 
poc-streamer_0.4.2-7.debian.tar.xz
 329bc0002cafea9d1ce63373c2abdd9c 6608 sound optional 
poc-streamer_0.4.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmMDCz0ACgkQ3mO5xwTr
6e+Rvg/9FE/Txa9SjHTPsPaSHmiR83HG24+oSGLH/jpoPUei+3vXncDqWy6jPUI4
ZVQsjzWchmMNClZOFeutQk+SPhP6I6TCx2HNVTWcmn3k6cAeujPVCyTX6GAvjYiu
4PzuufGvO352CBZPJ1GX4ny7ZM7s3pCkOwvAmxhQT+jdz6+bIJJFaeafy8DASd+I
WcALas05c+Mfcsit2jK/jnoW9O4iGpd0gpdoRs1e2nbUjRJt8jzSNb+noedvgNFe
gz+Q6g7TkWCr1DXzz1+sHJ6JbUQwWQ/L42IHKRMOrCqFK5Ax604fMfvAs5tEicyE
vFCXSooQhWwUJbslOIOy5xRxebDZZKQPzzMAE2dgbV6Xuh4tD/eCy7zw9vcks9t5
GF2Tuu7WT0orn9KmJ9/RPm0AhfE0lpc+Nalg8uqgL9/EP2Ad3ZcR5obdZIOx88D2
riXSUjkTWQ0CIAA2otIpoK79QNPHFQD1nzCxOD6iHSaBCYYrwpBuMbhWJN2Cesjs
NofyAwU7aPTeIKABj43z+nUGu8hzNP5YWQt4b+zb69SA+HBeJnNBx/l8zUU5r33X
mFw8Dxo7l3DZNnBMwKkN3yuY4FvSF1zkg/VKcYPrYbMWr/P9XGOzuQvbFCD4XsBc
p/+Mx/h2JnMweArL40EqmOcTEn8VlnqdGxvYhR6bneKnhzCkPjg=
=t3qs
-END PGP 

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

[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 migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
[...]
>
> [1] https://ci.debian.net/status/slow/

Hi Paul,

I noticed that superficial tests around pob-2250, pob-3119 and pob-fec
are failing. I set a timeout (3 minutes) for these tests and I set
them as flaky. I hope these procedures fix all issues.

Cheers,

Eriberto

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

[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

[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 } 
[src:libdatetime-format-datemanip-perl] libdatetime-format-datemanip-perl: 
FTBFS: tests failed
Unarchived Bug 574317
> reopen 574317
Bug #574317 {Done: Alexander Reichle-Schmehl } 
[src:libdatetime-format-datemanip-perl] libdatetime-format-datemanip-perl: 
FTBFS: tests failed
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.04-1+rm.
> close 574317 0.04-2
Bug #574317 [src:libdatetime-format-datemanip-perl] 
libdatetime-format-datemanip-perl: FTBFS: tests failed
Marked as fixed in versions libdatetime-format-datemanip-perl/0.04-2.
Bug #574317 [src:libdatetime-format-datemanip-perl] 
libdatetime-format-datemanip-perl: FTBFS: tests failed
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
574317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libminc
Version: 2.4.03-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org


1: Test command: 
/<>/obj-mips64el-linux-gnuabi64/ezminc/tests/ezminc_rw_test 
"/<>/obj-mips64el-linux-gnuabi64/ezminc/tests"
1: Working Directory: /<>/obj-mips64el-linux-gnuabi64/ezminc/tests
1: Test timeout computed to be: 1500
 1/52 Test  #1: ezminc_rw_test ...   Passed0.09 sec
test 2
  Start  2: minc_types-1

2: Test command: /<>/testdir/run_test_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
2: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
2: Test timeout computed to be: 1500
2: 364c364
2: image[1] = 0
2: 373c373
2: image[1] = -128
2: 382c382
2: image[1] = 0
2: 391c391
2: image[1] = -32768
2: 400c400
2: image[1] = 0
2: 409c409
2: image[1] = -2.14748e+09
2: 418c418
2: image[1] = -2.14748e+09
2: 427c427
2: image[1] = -2.14748e+09
2: 481c481
2: image[1] = -2.14748e+09
2: 553c553
2: image[1] = -2.14748e+09
 2/52 Test  #2: minc_types-1 .***Failed0.09 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

test 3
  Start  3: minc_types-2

3: Test command: /<>/testdir/run_test2_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
3: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
3: Test timeout computed to be: 1500
3: 364c364
3: image[1] = 0
3: 373c373
3: image[1] = -128
3: 382c382
3: image[1] = 0
3: 391c391
3: image[1] = -32768
3: 400c400
3: image[1] = 0
3: 409c409
3: image[1] = -2.14748e+09
3: 418c418
3: image[1] = -2.14748e+09
3: 427c427
3: image[1] = -2.14748e+09
3: 481c481
3: image[1] = -2.14748e+09
3: 553c553
3: image[1] = -2.14748e+09
 3/52 Test  #3: minc_types-2 .***Failed0.27 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

...

96% tests passed, 2 tests failed out of 52

Total Test time (real) = 126.06 sec

The following tests FAILED:
  2 - minc_types-1 (Failed)
  3 - minc_types-2 (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

Processed: built now

[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 'dietlibc: FTBFS on armel: illegal instruction'.
> severity 1017537 normal
Bug #1017537 [src:dietlibc] dietlibc: may FTBFS on armel due to buildd 
misconfiguration
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 least
one buildd listed does not have this enabled, breaking the armel ABI.

Please ensure that only hosts with working SWP emulation run armel.

(Can I reassign this bugreport to the buildd? Does it have a virtual
package in debbugs?)

Until then, I guess I’ll keep giveback’ing dietlibc on armel until
it builds…

bye,
//mirabilos
-- 
 den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt…
oder netzteile, an die man auch den monitor angeschlossen hat und die dann für
ein elektrisch aufgeladenes gehäuse gesorgt haben […] für lacher gut auf jeder
LAN party │  damals, als der pizzateig noch auf dem monior "gegangen" ist

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 set to 'serious' from 'important'

-- 
1017711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 1017853 1017698 1017798 1017779

[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"
Severity set to 'serious' from 'normal'
Added indication that 1017779 affects emacsen-nox,emacs-lucid,emacs-gtk
Added tag(s) ftbfs.
Bug #1017798 [emacs-common] emacs-common can't be installed: segfault in 
postinst
Severity set to 'serious' from 'grave'
Added indication that 1017798 affects emacsen-nox,emacs-lucid,emacs-gtk
Added tag(s) ftbfs.
Bug #1017853 [emacs-common] emacs-nox: byte compiling debian-startup.el fails 
if emacs-el is not installed
Marked as found in versions emacs/1:28.1+1-1.
Added tag(s) ftbfs.
Bug #1017698 [emacs-common] emacs-gtk: core dump with unsorted double linked 
list corrupted
Severity set to 'serious' from 'grave'
Removed indication that 1017698 affects src:gettext and src:gnuplot
Added indication that 1017698 affects emacsen-nox,emacs-lucid,emacs-gtk
Marked as found in versions emacs/1:28.1+1-1.
Merged 1017698 1017779 1017798 1017853
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698
1017779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017779
1017798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017798
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1017698 to emacs-common

[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 same values 
previously set
Ignoring request to alter fixed versions of bug #1017698 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1017853 to emacsen-common

[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 emacs/1:28.1+1-2.
Ignoring request to alter fixed versions of bug #1017853 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1017853 to emacs-common

[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 of bug #1017853 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1017853 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 1017853

[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 you need assistance.
-- 
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017537: dietlibc: FTBFS on armel

[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, r0
mov r1, #1
# if __ARM_ARCH__ < 6
swp r0, r1, [r2]
# else
1:  ldrex   r0, [r2]
strex   r3, r1, [r2]
cmp r3, #0
bne 1b
# endif
RET
FUNC_END__testandset

bye,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

Processed: your mail

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dietlibc
Version: 0.34~cvs20160606-14
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=dietlibc=armhf=0.34%7Ecvs20160606-14=1658252860=0

arm/__longjmp.S: Assembler messages:
arm/__longjmp.S:9: Error: selected processor does not support `vldm 
ip!,{d0-d15}' in ARM mode
make[2]: *** [Makefile:206: bin-arm/__longjmp.o] Error 1
make[2]: *** Waiting for unfinished jobs
: -x -R .comment -R .note bin-arm/realpath.o
: -x -R .comment -R .note bin-arm/fnmatch.o
: -x -R .comment -R .note bin-arm/glob.o
: -x -R .comment -R .note bin-arm/sha256crypt.o
: -x -R .comment -R .note bin-arm/rx.o
: -x -R .comment -R .note bin-arm/sha512crypt.o
make[2]: Leaving directory '/<>'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" 
prefix=/usr/lib/arm-linux-gnueabihf/diet MYARCH=arm 
VERSION=0.34\~cvs20160606-14 DEBUG=1 "CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -fno-pie -specs=/usr/share/dpkg/no-pie-link.specs 
-Wl,-z,relro -Wl,-z,now -no-pie -pipe -nostdinc -D_REENTRANT -Os 
-fomit-frame-pointer -fstrict-aliasing -W -Wall -Wextra -Wchar-subscripts 
-Wmissing-prototypes -Wmissing-declarations -Wno-switch -Wno-unused 
-Wredundant-decls -Wshadow" returned exit code 2
make[1]: *** [debian/rules:94: override_dh_auto_build-arch] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Dixi quod…

>This builds fine in a sid-armhf chroot on amdahl.

Yeah, after a give-back it builds.--- End Message ---

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

[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 #1017798 is 'emacs-common' not 'emacs-nox'
package of #1017698 is 'emacs-gtk' not 'emacs-nox'
Failed to forcibly merge 1017853: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017698
1017779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017779
1017798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017798
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017537: dietlibc: FTBFS on armel

[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 arm/__testandset.S:7
7   swp r0, r1, [r2]
(gdb) bt
#0  __testandset () at arm/__testandset.S:7
#1  0x000113d4 in __pthread_lock (lock=lock@entry=0x25054 <_main_thread+20>) at 
libpthread/pthread_spinlock.c:84
#2  0x0001052c in __thread_find_ (pid=) at 
libpthread/pthread_internal.c:98
#3  0x00010578 in __thread_self () at libpthread/pthread_internal.c:127
#4  0x00010280 in malloc (size=32) at libpthread/pthread_sys_alloc.c:20
#5  0x00010124 in main ()
(gdb) info r
r0 0x25054 151636
r1 0x1 1
r2 0x25054 151636
r3 0x0 0
r4 0x0 0
r5 0x25054 151636
r6 0x0 0
r7 0x1e8481201
r8 0x1016
r9 0xfffef684  4294899332
r100xfffef68c  4294899340
r110xfffef67c  4294899324
r120x1420
sp 0xfffef3c0  0xfffef3c0
lr 0x113d4 70612
pc 0x11480 0x11480 <__testandset+8>
cpsr   0x6010  1610612752
fpscr  0x0 0
(gdb) disas
Dump of assembler code for function __testandset:
   0x00011478 <+0>: mov r2, r0
   0x0001147c <+4>: mov r1, #1
=> 0x00011480 <+8>: swp r0, r1, [r2]
   0x00011484 <+12>:bx  lr
End of assembler dump.

Processed: affects 1017853

[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 need assistance.
-- 
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 1017853

[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 assistance.
-- 
1017853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017537: dietlibc: FTBFS on armel

[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, so this is possibly not related
to a toolchain change.

I think I’ll have to track down a 32-bit ARM machine and test-build it
there. I recently got gifted a Raspbery Pi v1.2 so that’d be running
armel anyway, so I guess it’s installing Debian on that thing for me now.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

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

[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.
-- 
1017538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1017538: dietlibc: FTBFS on armhf

[Thorsten Glaser]

tags 1017538 + unreproducible
thanks

This builds fine in a sid-armhf chroot on amdahl.

Processed: bump severity for poppler transition

[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 problems

Processed: bump severity for poppler transition

[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)

[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 marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: golang-github-bmatsuo-lmdb-go
Version: 1.8.0+git20170215.a14b5a3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up as a regression for the upload of glibc [0]. I noticed that 
it regularly fails on s390x in what I quickly spotted as always the same 
place. It segfaults.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[0] 
https://ci.debian.net/data/autopkgtest/testing/s390x/g/golang-github-bmatsuo-lmdb-go/24525427/log.gz


=== RUN   TestTxn_Drop
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x3ff8af8 
pc=0x3ffb7e98052]


runtime stack:
runtime.throw({0x11b7cba, 0x2a})
/usr/lib/go-1.18/src/runtime/panic.go:992 +0x70
runtime.sigpanic()
/usr/lib/go-1.18/src/runtime/signal_unix.go:802 +0x2a4

goroutine 88 [syscall, locked to thread]:
runtime.cgocall(0x1169570, 0xc5dd50)
	/usr/lib/go-1.18/src/runtime/cgocall.go:157 +0x72 fp=0xc5dd20 
sp=0xc5dcf0 pc=0x1008472
github.com/bmatsuo/lmdb-go/lmdb._Cfunc_mdb_txn_begin(0x3ff74263140, 0x0, 
0x0, 0xcfe018)

_cgo_gotypes.go:885 +0x3a fp=0xc5dd48 sp=0xc5dd20 pc=0x115ab0a
github.com/bmatsuo/lmdb-go/lmdb.beginTxn.func1(0xc000194060, 0x0, 0x0, 
0xcfe000)


/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/txn.go:99
 +0x108 fp=0xc5dd88 sp=0xc5dd48 pc=0x1162518
github.com/bmatsuo/lmdb-go/lmdb.beginTxn(0xc000194060, 0x0, 0x0)

/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/txn.go:99
 +0x24e fp=0xc5ddd0 sp=0xc5dd88 pc=0x116228e
github.com/bmatsuo/lmdb-go/lmdb.(*Env).run(0xc000194060, 0x1, 0x0, 
0xc5de58)


/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/env.go:507
 +0x74 fp=0xc5de18 sp=0xc5ddd0 pc=0x1161544
github.com/bmatsuo/lmdb-go/lmdb.(*Env).Update(...)

/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/env.go:478
github.com/bmatsuo/lmdb-go/lmdb.openDBI(0xc000194060, {0x11ad4e4, 0x2}, 
0x4)


/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/txn_test.go:1391
 +0x72 fp=0xc5de80 sp=0xc5de18 pc=0x1157a62
github.com/bmatsuo/lmdb-go/lmdb.TestTxn_Drop(0xc000102340)

/tmp/autopkgtest-lxc.9o42tkd3/downtmp/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/bmatsuo/lmdb-go/lmdb/txn_test.go:152
 +0xb6 fp=0xc5df68 sp=0xc5de80 pc=0x1149e16
testing.tRunner(0xc000102340, 0x11bac28)
	/usr/lib/go-1.18/src/testing/testing.go:1439 +0x122 fp=0xc5dfc0 
sp=0xc5df68 pc=0x10dfa52

testing.(*T).Run.func1()
	/usr/lib/go-1.18/src/testing/testing.go:1486 +0x5e fp=0xc5dfd8 
sp=0xc5dfc0 pc=0x10e0bee

runtime.goexit()
	/usr/lib/go-1.18/src/runtime/asm_s390x.s:742 +0x2 fp=0xc5dfd8 
sp=0xc5dfd8 pc=0x1079482

created by testing.(*T).Run
/usr/lib/go-1.18/src/testing/testing.go:1486 +0x442

goroutine 1 [chan receive]:
testing.(*T).Run(0xca0820, {0x11af3ba, 0xc}, 0x11bac28)
/usr/lib/go-1.18/src/testing/testing.go:1487 +0x466
testing.runTests.func1(0xca0820)
/usr/lib/go-1.18/src/testing/testing.go:1839 +0x8a
testing.tRunner(0xca0820, 0xc95cf8)
/usr/lib/go-1.18/src/testing/testing.go:1439 +0x122
testing.runTests(0xc0e060, {0x12a8c00, 0x49, 0x49}, 
{0xc0b48ae619a94ce3, 0x8bb2cc3cd7, 0x12c0e80})

/usr/lib/go-1.18/src/testing/testing.go:1837 +0x4d6
testing.(*M).Run(0xca6140)

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

[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 what
> line# failed an assertion in my current tree.

I've just updated SBCL in Debian to 2.2.7 and dropped two patches
included in that release, which simplifies things a bit.  ci.debian.net
will re-run the cl-ironclad test suite soon.  Let me know if it would be
useful for me to file a Launchpad bug gathering the various links
together.

-- 
Sean Whitton


signature.asc
Description: PGP signature

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

[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 starting emacs ends (or rather does not starting) in an endless
loop for me now as well:

Axel Beckert wrote:
> > So far I had to unsinstall the following packages to make it go away,
> > i.e. these packages trigger the issue:
[List fixed to give actual package names]
> > elpa-folding
> > elpa-org
> > elpa-git-timemachine
> > elpa-password-store
> > 
> > There might be more.
> 
> Another one:
> 
> elpa-git-commit

In the meanwhile I also found elpa-smart-mode-line-powerline-theme and
elpa-ement being affected.

After removing all these packages and their reverse dependencies,
emacs' package installation finally passed through without endless
loops.

But when starting emacs, a very similar despite not identical endless
loop showed up — even twice and in parallel:

abe  25900  1.4  0.0 249576 60944 pts/14   Sl   23:53   0:01  \_ 
emacs
abe  25902  2.4  0.0 254052 61232 pts/20   Ssl+ 23:53   0:03  |   
\_ /usr/bin/emacs --batch -l /tmp/emacs-async-comp-seq-25-EX7HYr.el
abe  25908  2.4  0.0 254056 61284 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Oknfek.el
abe  25913  2.4  0.0 254060 61256 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-LRg59v.el
abe  25917  2.5  0.0 254056 61060 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-V984rp.el
abe  25927  2.5  0.0 254060 63184 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-36KQ3Y.el
abe  25931  2.6  0.0 254056 61212 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-rc7Hc7.el
abe  25943  2.8  0.0 254060 61184 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-iHJ6VG.el
abe  25959  2.8  0.0 254056 61176 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-KPWHZf.el
abe  25973  2.8  0.0 254060 61284 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-ujNMu4.el
abe  25987  2.8  0.0 254056 61292 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-5spOXr.el
abe  25998  3.0  0.0 254060 61228 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-QU5Rk4.el
abe  26002  3.1  0.0 254056 61220 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-knkQvC.el
abe  26006  3.3  0.0 254060 61248 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-emW4ym.el
abe  26016  3.3  0.0 254056 61352 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-CGyFmX.el
abe  26035  3.4  0.0 254060 61276 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs --batch 
-l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Rfnh3y.el
abe  26050  3.6  0.0 254056 63220 ?Ssl  23:54   0:02  |   | 
  \_ /usr/bin/emacs 
--batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-yb58VI.el
abe  26062  3.8  0.0 254060 61228 ?Ssl  23:54   0:03  |   | 
  \_ /usr/bin/emacs 
--batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Y0EkN7.el
abe  

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-

[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 -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
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
Changed Bug title to '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'
 from 'Endless fork loop at installation time: /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el'.

-- 
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1009917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-4-1
Version: 4.6.2+ds-1
Severity: grave
Tags: patch
X-Debbugs-Cc: s...@riseup.net

Unable to run these applications 10 times without crash with mobian pinephone:

megapixels, gnome-calculator, and gnome-clocks and probably more gtk4 apps

the crash, running in terminal:

Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1266:gsk_gl_command_queue_create_render_target:
 assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == 
GL_FRAMEBUFFER_COMPLETE): (0x8cd6 == 0x8cd5)
Bail out! 
Gsk:ERROR:../../../gsk/gl/gskglcommandqueue.c:1266:gsk_gl_command_queue_create_render_target:
 assertion failed (glCheckFramebufferStatus (GL_FRAMEBUFFER) == 
GL_FRAMEBUFFER_COMPLETE): (0x8cd6 == 0x8cd5)
Aborted (core dumped)

The issue in gtk repo:
https://gitlab.gnome.org/GNOME/gtk/-/issues/4763

This patch fixes the bug:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4570.patch


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.15-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgtk-4-1 depends on:
ii  adwaita-icon-theme42~really41.0-1
ii  hicolor-icon-theme0.17-2
ii  libc6 2.33-7
ii  libcairo-gobject2 1.16.0-5
ii  libcairo-script-interpreter2  1.16.0-5
ii  libcairo2 1.16.0-5
ii  libcloudproviders00.3.1-2
ii  libcolord21.4.6-1
ii  libcups2  2.4.1op1-2
ii  libepoxy0 1.5.10-1
ii  libfontconfig12.13.1-4.4
ii  libfribidi0   1.0.8-2.1
ii  libgdk-pixbuf-2.0-0   2.42.8+dfsg-1
ii  libglib2.0-0  2.72.0-1+b1
ii  libgraphene-1.0-0 1.10.8-1
ii  libgtk-4-common   4.6.2+ds-1
ii  libharfbuzz0b 2.7.4-1
ii  libjpeg62-turbo   1:2.1.2-1
ii  libpango-1.0-01.50.6+ds-2
ii  libpangocairo-1.0-0   1.50.6+ds-2
ii  libpangoft2-1.0-0 1.50.6+ds-2
ii  libpng16-16   1.6.37-3
ii  libtiff5  4.3.0-6
ii  libwayland-client01.20.0-1
ii  libwayland-egl1   1.20.0-1
ii  libx11-6  2:1.7.5-1
ii  libxcursor1   1:1.2.0-2
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.4-1
ii  libxfixes31:6.0.0-1
ii  libxi62:1.8-1
ii  libxinerama1  2:1.1.4-3
ii  libxkbcommon0 1.4.0-1
ii  libxrandr22:1.5.2-1
ii  shared-mime-info  2.1-2

Versions of packages libgtk-4-1 recommends:
ii  iso-codes4.9.0-1
ii  libgtk-4-bin 4.6.2+ds-1
ii  librsvg2-common  2.52.5+dfsg-3+b1

Versions of packages libgtk-4-1 suggests:
ii  gvfs  1.50.0-1
pn  libgtk-4-media-gstreamer | libgtk-4-media-ffmpeg  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.7.2+ds-3
Done: Jeremy Bicha 

We believe that the bug you reported is fixed in the latest version of
gtk4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gtk4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 17:40:46 -0400
Source: gtk4

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].)

[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 [1,22,2] but attempted to decode with 
[1,20].
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc-citeproc-preamble
Version: 1.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> test/test
> testing with pandoc 2.17.1.1
> [WARNING] Deprecated: pandoc-citeproc filter. Use --citeproc instead.
> pandoc-citeproc: Error in $: Incompatible API versions: encoded with [1,22,2] 
> but attempted to decode with [1,20].
> CallStack (from HasCallStack):
>   error, called at ./Text/Pandoc/JSON.hs:112:48 in 
> pandoc-types-1.20-JP83YEZp4VZ5qbwCPN8866:Text.Pandoc.JSON
> Error running filter pandoc-citeproc:
> Filter returned error status 1
> readline() on closed filehandle $fh at test/test line 46.
> neither preamble nor references found!
> make[1]: *** [debian/rules:32: override_dh_auto_test] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/pandoc-citeproc-preamble_1.6-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pandoc-citeproc-preamble
Source-Version: 1.7-1
Done: Sean Whitton 

We believe that the bug you reported is fixed in the latest version of
pandoc-citeproc-preamble, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated 
pandoc-citeproc-preamble package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 14:36:30 -0700
Source: pandoc-citeproc-preamble
Architecture: source
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 1017256
Changes:
 pandoc-citeproc-preamble (1.7-1) unstable; urgency=medium
 .
   * Replace references to pandoc-citeproc.
 We now say "Pandoc's citeproc filter", "Pandoc's bibliography", etc..
   * Replace '--filter pandoc-citeproc' -> '--citeproc' (Closes: #1017256).
   * Drop build-dep and autopkgtest dep on pandoc-citeproc.
 .
   * Update homepage in pandoc-citeproc-preamble.cabal.
   * Fix a manpage typo.
Checksums-Sha1:
 fc5dad7c8c0c7f2fe26b2439175d6d1d2e9af7c1 2317 
pandoc-citeproc-preamble_1.7-1.dsc
 8bc0221a88eafc28aaa7f592beaf6f4131b4f85c 18840 
pandoc-citeproc-preamble_1.7.orig.tar.xz
 37f123cfa23996a5ebe52bedc2f2a7bb80e27901 3444 
pandoc-citeproc-preamble_1.7-1.debian.tar.xz
Checksums-Sha256:
 5d9df5b322fa16253ed7c9967bf77843c7e918f5a311128074aff11b8fa51911 2317 
pandoc-citeproc-preamble_1.7-1.dsc
 72ead5dd561e55076a4a06745605fb6632594620ad675112c1a81ff9042b35fe 18840 
pandoc-citeproc-preamble_1.7.orig.tar.xz
 38be8a0d20df47768fefaef28989793eb876f8570bc3e816897986e217395a79 3444 
pandoc-citeproc-preamble_1.7-1.debian.tar.xz
Files:
 44b1b83c605c0d1bba3f5858c5406fe3 2317 haskell optional 
pandoc-citeproc-preamble_1.7-1.dsc
 

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.)

[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 method stubbing and expectations.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1006026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-axiom-types
Version: 0.1.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  ArgumentError:
>Cannot proxy frozen objects, rspec-mocks relies on proxies for method 
> stubbing and expectations.
>  # ./spec/unit/axiom/types/class_methods/finalize_spec.rb:14:in `block (2 
> levels) in '
> 
> Top 10 slowest examples (0.02984 seconds, 11.5% of total time):
>   Axiom::Types::Hash.infer with Axiom::Types::Hash with an Hash with a nil 
> key and value primitive key_type is expected to equal Axiom::Types::Object 
> (BasicObject)
> 0.00549 seconds 
> ./spec/unit/axiom/types/hash/class_methods/infer_spec.rb:95
>   Axiom::Types::Encodable.extended delegates to the ancestor
> 0.00394 seconds 
> ./spec/unit/axiom/types/encodable/class_methods/extended_spec.rb:10
>   Axiom::Types::Object.infer with the type when the argument is ::Object is 
> expected to equal Axiom::Types::Object (BasicObject)
> 0.00356 seconds 
> ./spec/unit/axiom/types/object/class_methods/infer_spec.rb:26
>   Axiom::Types::Object.infer with the type when the argument is ::DateTime is 
> expected to equal Axiom::Types::Object (BasicObject)
> 0.00353 seconds 
> ./spec/unit/axiom/types/object/class_methods/infer_spec.rb:42
>   Axiom::Types.infer when the type is Axiom::Types::Symbol is expected to 
> equal Axiom::Types::Symbol (Symbol)
> 0.00328 seconds ./spec/unit/axiom/types/class_methods/infer_spec.rb:18
>   Axiom::Types::Encodable#finalize when an ascii compatible encoding (UTF-8) 
> is used adds a constraint that returns true for TIS-620 encoding
> 0.00294 seconds ./spec/unit/axiom/types/encodable/finalize_spec.rb:35
>   Axiom::Types::Collection.infer with a a non-base class when the argument is 
> nil is expected to be nil
> 0.00288 seconds 
> ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:130
>   Axiom::Types::Object.finalize adds a constraint that returns true for a 
> valid primitive
> 0.00145 seconds 
> ./spec/unit/axiom/types/object/class_methods/finalize_spec.rb:22
>   Axiom::Types::Object.coercion_method with a symbol sets the coercion_method
> 0.0014 seconds 
> ./spec/unit/axiom/types/object/class_methods/coercion_method_spec.rb:22
>   Axiom::Types::Object.finalize is expected to be frozen
> 0.00136 seconds 
> ./spec/unit/axiom/types/object/class_methods/finalize_spec.rb:18
> 
> Top 10 slowest example groups:
>   Axiom::Types::Encodable.extended
> 0.00158 seconds average (0.00473 seconds / 3 examples) 
> ./spec/unit/axiom/types/encodable/class_methods/extended_spec.rb:5
>   Axiom::Types::Object.coercion_method
> 0.00143 seconds average (0.00287 seconds / 2 examples) 
> ./spec/unit/axiom/types/object/class_methods/coercion_method_spec.rb:5
>   Axiom::Types::Object.finalize
> 0.00097 seconds average (0.00388 seconds / 4 examples) 
> ./spec/unit/axiom/types/object/class_methods/finalize_spec.rb:5
>   Axiom::Types::Object.infer
> 0.00086 seconds average (0.03592 seconds / 42 examples) 
> ./spec/unit/axiom/types/object/class_methods/infer_spec.rb:5
>   Axiom::Types::Hash.infer
> 0.0008 seconds average (0.03042 seconds / 38 examples) 
> ./spec/unit/axiom/types/hash/class_methods/infer_spec.rb:5
>   Axiom::Types::Collection.infer
> 0.00073 seconds average (0.0131 seconds / 18 examples) 
> ./spec/unit/axiom/types/collection/class_methods/infer_spec.rb:5
>   Axiom::Types::Array.infer
> 0.0006 seconds average (0.00961 seconds / 16 examples) 
> ./spec/unit/axiom/types/array/class_methods/infer_spec.rb:5
>   Axiom::Types.finalize
> 0.00058 seconds average (0.00058 seconds / 1 example) 
> ./spec/unit/axiom/types/class_methods/finalize_spec.rb:5
>   Axiom::Types::Set.infer
> 0.00056 seconds average (0.00896 seconds / 16 examples) 
> ./spec/unit/axiom/types/set/class_methods/infer_spec.rb:5
>   Axiom::Types::ValueComparable#range
> 0.00055 seconds average (0.0011 seconds / 2 examples) 
> 

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

[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 
'https://github.com/ruby-grape/grape/issues/2278'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 [ -d
> /run/systemd/system ]; then echo systemd ; exit 0 ; else echo unknown ; exit
> 0 ; fi" ; echo $? && sudo lxc-stop test
> lxc-attach: test: ../src/lxc/attach.c: lxc_attach_run_command: 1839 No such
> file or directory - Failed to exec "if [ -d /run/systemd/system ]; then echo
> systemd ; exit 0 ; else echo unknown ; exit 0 ; fi"
> 127

Does lxc-attach expect a single shell one-liner as argument (like su -c),
or an argv (like sudo)?

I would have expected that it wants an argv, in which case the first one
is searching PATH for /bin/runlevel or similar, which succeeds, but the
second is searching path for something like "/bin/if [ -d ..." which
doesn't exist (hence exit status 127).

If it wants argv as individual arguments, like I would have expected,
then the second command should be more like:

sudo lxc-start test && sudo lxc-attach test -- sh -ec "if [ -d ..."

which is how lib/VirtSubproc.py actually runs it.

If the root cause was me mixing up commands that want a shell one-liner
with commands that want argv, then I would have expected that virt-lxc
would *never* work in the current version, rather than only intermittently
working (but I'm fairly sure it passed its autopkgtest run in my
autopkgtest-virt-qemu, so it must work at least sometimes).

smcv

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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:

https://salsa.debian.org/ruby-team/ruby-axiom-types/-/commit/796f33353513fe46e7b04af6536182910111b086


debian/ruby-tests.rake: test class finalizer separately

If this gets run together with the rest of the tests, it will fail
randomly at approximately 60% of the time (I assume based on the test
ordering).

Closes: #1006026
Gbp-Dch: full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006026

Processed: affects 1017845

[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 that 1017845 affects elpa-ement
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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,
Jeremy Bicha

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

[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 the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.22
Severity: minor
X-Debbugs-Cc: ja...@oneway.dev

Hi,

Severity: minor because this is probably an exotic corner case. I'm
filing this anyway becuse it is probably easily fixed.

I'm on the adduser team. Adduser is part of the minimal install and is
therefore installed in every environment that autopkgtest is run in. In
current experimental, adduser has migrated /etc/adduser.conf to being an
dpkg-conffile. Before that, adduser.conf was kind of "managed" in
postinst.

adduser.conf suddenly becoming a dpkg-conffile causes dpkg to emit a
conffile prompt in every case of adduser <= 3.123 being updated to
adduse >= 3.125.

This also happens when the newly built adduser.deb gets installed during
autopkgtest. The autopkgtest run stalls in this case and needs manual
intervention to continue.

Is this autopkgtest's intended behavior? If not, would passing
--force-confnew to dpkg solve this issue?

This most probably only happens iff:

- the package in test is already part of the base install AND
- the package in test has recently changed a maintainer-managed
  configuration file to being a dpkg-conffile.

Since this is probably exotic, I'm holding off uploading a new version
of adduser to unstable until Friday Aug 5 to give you a chance to
reproduce this behavior. Let me know when I can upload earlier please.

I am setting Jason Franklin, my team colleague who investgated this in
depth, as Cc so that he can give additional information that I might
have forgotten.

Greetings
Marc
--- End Message ---
--- Begin Message ---
Source: adduser
Source-Version: 3.127
Done: Marc Haber 

We believe that the bug you reported is fixed in the latest version of
adduser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Haber  (supplier of updated adduser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Aug 2022 21:42:09 +0200
Source: adduser
Architecture: source
Version: 3.127
Distribution: unstable
Urgency: medium
Maintainer: Debian Adduser Developers 
Changed-By: Marc Haber 
Closes: 57280 152195 398802 440801 541620 609114 678615 682156 1012492 1015283 
1015907 1016574 1017694
Changes:
 adduser (3.127) unstable; urgency=low
 .
   [ Jason Franklin ]
   * Document the intent of the --no-create-home option (Closes: #152195)
 .
   [ Marc Haber ]
   * create home directory with primary group of the user (Closes: #1017694)
   * update and extend README
 .
 adduser (3.126) experimental; urgency=medium
 .
   * more clear conffile handling in debian/preinst.
 Thanks to Simon McVittie (Closes: #1016574)
   * add postrm script cleaning up better after purge
   * add a Debian README, move too long DIR_MODE explanation from
 NEWS.Debian to README.
 .
 adduser (3.125) experimental; urgency=medium
 .
   [ Marc Haber ]
   * remove debconf. (Closes: #57280, #398802)
   * install (add|del)user.conf as examples.
   * install adduser.conf as dpkg-conffile directly to /etc.
 (Closes: #541620)
   * remove postinst/postrm. (Closes: #1012492)
 .
   [ Jason Franklin ]
   * Remove the unused "get_users_groups" subroutine. (Closes: #1015907)
 .
   [ Matt Barry ]
   * Do not check for group being empty on 'delgroup'. (Closes: #682156)
 .
 adduser (3.124) experimental; urgency=medium
 .
   * experimental upload
   * implement new USERS_GROUP semantics
 * adapt documentation
 * implement testcases
 * re-work adduser logic to support USERGROUPS mechanics.
   This also kind of drive-by implements --firstgid and --lastgid
   (Closes: #609114, #678615, #440801)
 * rework adduser.conf
   * improve test 

Bug#1017348: autopkgtest regression on ppc64el

[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 for
three points, the output with OpenCV 4.6.0+dfsg-4+b1 is
  x: 3+4   y: 98+13
(which is what I was waiting for), and with OpenCV 4.6.0+dfsg-6+b1 is
  x: 3+4   y: 0+1
(I think the values for y are not correct here).
However, the output seems correct with both versions of OpenCV on
amd64.

As far as I understand this issue, I would say that the problem comes
from OpenCV and not auto-multiple-choice.

Regards,
Alexis Bienvenüe.

--
// gcc -o bounding bounding.cc -O2 -lstdc++ -lm -I/usr/include/opencv4
-lopencv_imgproc

#include 
#include 
#include "opencv2/core/core.hpp"
#include "opencv2/imgproc/imgproc.hpp"

int main(int argc, char** argv)
{

  std::vector pts;

  pts.push_back(cv::Point(3,100));
  pts.push_back(cv::Point(5,98));
  pts.push_back(cv::Point(6,110));

  cv::Rect rect = cv::boundingRect(pts);

  std::cout << "x: " << rect.x << "+" << rect.width
<< "   y: " << rect.y << "+" << rect.height
<< "\n";

}

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

[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

[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 unknown 
; exit 0 ; fi" ; echo $? && sudo lxc-stop test
lxc-attach: test: ../src/lxc/attach.c: lxc_attach_run_command: 1839 No 
such file or directory - Failed to exec "if [ -d /run/systemd/system ]; 
then echo systemd ; exit 0 ; else echo unknown ; exit 0 ; fi"

127
paul@mulciber ~ $

It seems the first command in the new flow is not suitable to run while 
the container is still starting up.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

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

[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: application/xz

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

[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: 
libinsighttoolkit5-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elastix
Version: 5.0.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-exec, cmake, 
> libinsighttoolkit5-dev, libcharls-dev, libdcmtk-dev, zlib1g-dev, libpng-dev, 
> libtiff-dev, libnifti-dev, libfftw3-dev, build-essential, fakeroot, doxygen, 
> graphviz, texlive-latex-base, texlive-latex-extra, texlive-latex-recommended, 
> texlive-fonts-recommended, texlive-publishers, ghostscript
> Filtered Build-Depends: debhelper-compat (= 13), dh-exec, cmake, 
> libinsighttoolkit5-dev, libcharls-dev, libdcmtk-dev, zlib1g-dev, libpng-dev, 
> libtiff-dev, libnifti-dev, libfftw3-dev, build-essential, fakeroot, doxygen, 
> graphviz, texlive-latex-base, texlive-latex-extra, texlive-latex-recommended, 
> texlive-fonts-recommended, texlive-publishers, ghostscript
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [504 B]
> Get:5 copy:/<>/apt_archive ./ Packages [578 B]
> Fetched 2039 B in 0s (184 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libinsighttoolkit5-dev but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/elastix_5.0.1-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
The build-dep is available again.
-Steve

signature.asc
Description: This is a digitally signed message part.
--- End Message ---

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

[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 fix this up if there is a good reason, but i'm more inclined to 
say a crate that is abandoned upstream, fails to build with current 
rustc and has been superseeded by funcationality in the standard library 
probablly doesn't belong in Debian.

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

[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 this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
991082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-gtd-1.0
Version: 3.28.1-2
Severity: serious

${gir:Depends} needs "dh --with gir" in debian/rules.

Something might still go wrong after that,
when trying it did not generate dependencies
on any library:
 Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.19.5)
--- End Message ---
--- Begin Message ---
Source: endeavour
Source-Version: 42.0-2
Done: Jeremy Bicha 

We believe that the bug you reported is fixed in the latest version of
endeavour, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated endeavour package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 14:19:23 -0400
Source: endeavour
Built-For-Profiles: noudeb
Architecture: source
Version: 42.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 991082
Changes:
 endeavour (42.0-2) unstable; urgency=medium
 .
   * debian/control.in: Bump minimum libadwaita to 1.2~alpha
 .
 endeavour (42.0-1) unstable; urgency=medium
 .
   * App has been renamed to Endeavour
   * New upstream release
   * Add gnome-todo transitional package
   * Disable introspection and drop the unused gir package (Closes: #991082)
   * Stop providing a -dev package. Use debian/not-installed for those files
   * debian/endeavour.links: Add /usr/bin/gnome-todo symlink
   * Update debian/copyright
   * debian/docs: NEWS is no longer provided
   * Drop all patches except the gsettings patch: applied in new release
   * Cherry-pick patch to fix build with -Werror=format-security
   * Set Rules-Requires-Root:no and X-Ubuntu-Use-Langpack: yes
Checksums-Sha1:
 16cb8f02f6c021dd68fc0d3dc9d446514dbb863c 2463 endeavour_42.0-2.dsc
 d3af97a187889a7cc0dbc241850ae2e22c3e2f3c 6256 endeavour_42.0-2.debian.tar.xz
 5833e7b379136a5f5799afc676241a69c223b3a7 11291 
endeavour_42.0-2_source.buildinfo
Checksums-Sha256:
 3d9ef750934e0c18c5b7c227b8315092cc7e94d06de86f5f32637a7913cca491 2463 
endeavour_42.0-2.dsc
 087e6be8c62dbb4fefb07f349f5111db3f2772d1a9cb9552b43a1bb66601ceec 6256 
endeavour_42.0-2.debian.tar.xz
 317aeb957371bfec6e7f1bc073eefb24c036e1929c217ecbe785838096a471a1 11291 
endeavour_42.0-2_source.buildinfo
Files:
 79d7e0325b7f2a9e694b5be985fcd74e 2463 gnome optional endeavour_42.0-2.dsc
 7df57d90a1931a957e03db48f72d1f12 6256 gnome optional 
endeavour_42.0-2.debian.tar.xz
 627e031b51a1882ef11ef05599dda9ff 11291 gnome optional 
endeavour_42.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMCd0wACgkQ5mx3Wuv+
bH0lWxAApmyyEtl9LdzXujxLwk6tGsFfnkdjAobBmidzOJeJMLiQiBb6RpfqgzcZ
uuD9D/UDY4p34ECrc5ehhrRoLR59cH23+yaakaKJk6nqQ0Bwl/E+hEhCEFfuZcss
E+iSyWQ+PqniI9ntqVmjgKaKDqt/eAkmCPGMetuH3BfRgE7Q8jFWso4bm/HPCSSZ
KGNMnuuC6wwmgmBwNUmpXWjoXWzIR6hprkDVQ8Ubj4gL/R9T0dSA3e2MDnY+ssYU
yGCwlYjseXCY+yo5yabnVBPeYUgxGVyPRXtRs5h75MrYuQrHU450olKlvQXY0quZ
2lHiSlLyurv4ZgCLInQqp96LgMQhU+mVcsfksot/zbkuk4GhjREPC7CHpnHeKmBs
jrepghahPy3oHGaYMAB6JTrtasFqWpxC9ZtH1nOC12NgwZGlWeJXlvYTZLLQSnSf
gw4ug4PirPyBxVerZUHxsrNJfX0G45BEpmzg/hvqv4za5eXemJaueA4u4J8dagsG
qJF3sDtmFGEkoTuInNepdoeBUnAdEv2dBObCShopy/Iu++c3NNrKpnr9d/7WLKkH
9R5azK6sci25PQNOdqgO+SpMKHow9SZ2R7fk8ko1DshxQR3cvS017iLniKZdtzWE
0fow6qQU/KOUUqgTy/yHEnb1rlkA819DiFmE+fWLQ1QUgq1V0XE=
=Z7ko
-END PGP SIGNATURE End Message ---

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 
/<>/.pybuild/cpython3_3.10_scipy/build/scipy/signal/tests/test_max_len_seq.py:21:
 in test_mls_inputs
assert_array_equal(max_len_seq(10, length=0)[0], [])
self   = 
/<>/.pybuild/cpython3_3.10_scipy/build/scipy/signal/_max_len_seq.py:136:
 in max_len_seq
state = _max_len_seq_inner(taps, state, nbits, length, seq)
E   TypeError: Invalid call to pythranized function 
`_max_len_seq_inner(intc[:], int8[:], int, int, int8[:])'
E   Candidates are:
E   
E   - _max_len_seq_inner(int[:], int8[:], int, int, int8[:])
E   - _max_len_seq_inner(int64[:], int8[:], int, int, int8[:])
length = 0
n_max  = 1023
nbits  = 10
seq= array([], dtype=int8)
state  = array([1, 1, 1, 1, 1, 1, 1, 1, 1, 1], dtype=int8)
taps   = array([7], dtype=int32)


Likewise with TestMLS.test_mls_output.

1.8.1-8 introduced debian patch pythran_type_PR16646.patch which
applied scipy upstream PR16646 to fix such pythran issues. The patch
fixed the problems reported at
https://github.com/serge-sans-paille/pythran/issues/2002
but two tests in TestMLS remain to be fixed.

This is the main problem keeping scipy 1.8 from migrating to testing,
hence marking bug severity Serioes.

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

[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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: insighttoolkit5
Version: 5.2.1-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit5=amd64=5.2.1-5%2Bb2=1659928626=0


ITKPolynomials =   0.03 sec*proc

ITKQuadEdgeMesh =   1.34 sec*proc

ITKQuadEdgeMeshFiltering =  26.18 sec*proc

ITKRegionGrowing =   0.53 sec*proc

ITKRegistrationCommon =  87.72 sec*proc

ITKRegistrationMethodsv4 =  70.63 sec*proc

ITKReview =  48.79 sec*proc

ITKSignedDistanceFunction =   0.08 sec*proc

ITKSmoothing =   1.09 sec*proc

ITKSpatialFunction =   0.04 sec*proc

ITKSpatialObjects =   1.25 sec*proc

ITKStatistics =   7.16 sec*proc

ITKSuperPixel =   1.24 sec*proc

ITKTestKernel =   0.17 sec*proc

ITKThresholding =   4.59 sec*proc

ITKTransform =  20.72 sec*proc

ITKTransformFactory =   0.10 sec*proc

ITKVideoCore =   0.30 sec*proc

ITKVideoFiltering =   0.40 sec*proc

ITKVideoIO =   0.33 sec*proc

ITKVoronoi =   0.57 sec*proc

ITKWatersheds =   2.08 sec*proc

RUNS_LONG = 517.95 sec*proc

Test log end =:
make[1]: *** [debian/rules:93: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:77: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
On Mon, 8 Aug 2022 08:27:44 +0200 Sebastian Ramacher  
wrote:
> Source: insighttoolkit5
> Version: 5.2.1-5
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the 
past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?
pkg=insighttoolkit5=amd64=5.2.1-5+b2=1659928626=0
> 

I think this must be spurious.  I can't reproduce today on my amd64, so I did 
"give-back" and it has now successfully built: 

https://buildd.debian.org/status/fetch.php?
pkg=insighttoolkit5=amd64=5.2.1-5%2Bb2=1661103666=0

-Steve


signature.asc
Description: This is a digitally signed message part.
--- End Message ---

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

[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 this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
991082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-gtd-1.0
Version: 3.28.1-2
Severity: serious

${gir:Depends} needs "dh --with gir" in debian/rules.

Something might still go wrong after that,
when trying it did not generate dependencies
on any library:
 Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.19.5)
--- End Message ---
--- Begin Message ---
Source: endeavour
Source-Version: 42.0-1
Done: Jeremy Bicha 

We believe that the bug you reported is fixed in the latest version of
endeavour, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated endeavour package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 18 Aug 2022 16:00:27 -0400
Source: endeavour
Binary: endeavour endeavour-common endeavour-dbgsym gnome-todo
Architecture: source all amd64
Version: 42.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 endeavour  - minimalistic personal task manager designed to fit GNOME desktop
 endeavour-common - common files for Endeavour
 gnome-todo - minimalistic personal task manager - transitional package
Closes: 991082
Changes:
 endeavour (42.0-1) unstable; urgency=medium
 .
   * App has been renamed to Endeavour
   * New upstream release
   * Add gnome-todo transitional package
   * Disable introspection and drop the unused gir package (Closes: #991082)
   * Stop providing a -dev package. Use debian/not-installed for those files
   * debian/endeavour.links: Add /usr/bin/gnome-todo symlink
   * Update debian/copyright
   * debian/docs: NEWS is no longer provided
   * Drop all patches except the gsettings patch: applied in new release
   * Cherry-pick patch to fix build with -Werror=format-security
   * Set Rules-Requires-Root:no and X-Ubuntu-Use-Langpack: yes
Checksums-Sha1:
 3707c3743840d31b6429e98bb5607306fc1495f9 2459 endeavour_42.0-1.dsc
 a62f7f7a8eb1824b1c02353d014c52f78779583f 556636 endeavour_42.0.orig.tar.xz
 2bce7d5add69f0bb5be35528135649a480f7611c 6220 endeavour_42.0-1.debian.tar.xz
 1be8c6aee804f4838242bf94603200eeb5d002b5 182600 endeavour-common_42.0-1_all.deb
 1a23a90073f192cd194e7f014325152f24518886 636108 
endeavour-dbgsym_42.0-1_amd64.deb
 b40d23fb330c402f0f805c1563d1a584b67617b5 20321 endeavour_42.0-1_amd64.buildinfo
 fc077b3802ae2f30c359a46053e7aa98e01f10a1 186348 endeavour_42.0-1_amd64.deb
 f589cbd5c533ba95533d4ee545c4d0064a7cfce1 4880 gnome-todo_42.0-1_all.deb
Checksums-Sha256:
 afa667b0bd04aa9c9ed0e13a2d546399e14be7f0a030bf16b6b23714708d1f9c 2459 
endeavour_42.0-1.dsc
 08e0308304b31601200256d755cb7ce6fdb0e349441e0126603df9fa3b5b36b2 556636 
endeavour_42.0.orig.tar.xz
 9320ec0c739396c0e586bc1e8bafd7debccce326adc9206f7291ce38cad815c7 6220 
endeavour_42.0-1.debian.tar.xz
 e6c39fc7f144289eea46a2e5298142176c236508e53410d7ff5dabaa 182600 
endeavour-common_42.0-1_all.deb
 8855fc5257ab598978c77a1e25c79925a0f84adcee3eaeef390c87a95cf038a0 636108 
endeavour-dbgsym_42.0-1_amd64.deb
 544721bf5f7ae06b15b5b77349397ff12c544b12604710aef68b4732747433c2 20321 
endeavour_42.0-1_amd64.buildinfo
 6cc3d4dc2ea44d52d58c3078e3b98f622de58a2660599213c427c6e5ce2b6907 186348 
endeavour_42.0-1_amd64.deb
 798a1b9be2e18a402d59a601011e22ba2312fee4529bc73eed1ba6c1760ec938 4880 
gnome-todo_42.0-1_all.deb
Files:
 c7f00fdff39c2a2a35171292e1d816e4 2459 gnome optional endeavour_42.0-1.dsc
 1d69802b04f7a24d2ae987c769fc8eb9 556636 gnome optional 
endeavour_42.0.orig.tar.xz
 6de4d8782a5f182dad3cc9172b91624e 6220 gnome optional 
endeavour_42.0-1.debian.tar.xz
 253bcb86c86c4b3ce07490797f8adb51 182600 gnome optional 
endeavour-common_42.0-1_all.deb
 b3248e1ca1bfd7763e715ca590551775 636108 debug optional 
endeavour-dbgsym_42.0-1_amd64.deb

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

[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 and scipy?


To be fair, we're still waiting for another pythran fix for scipy, so no 
need to rush dask through on scipy's behalf.


I'll file an RC bug against scipy so we don't get confused about what's 
holding scipy up.

Processed: closing 1012936

[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’, but does not override
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1012936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012936
1015036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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.


Graham, should the bug severity therefore be reduced from Serious back 
down to Important to enable migration of both dask and scipy?


Drew

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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] org.h2.jdbc.JdbcSQLSyntaxErrorException: schema 
"MEDIATHEKVIEW" not found
Changed Bug title to 'mediathekview update discussion' from 
'org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found'.

-- 
1011165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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

[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 github.com/pascaldekloe/goe/el 
github.com/pascaldekloe/goe/metrics github.com/pascaldekloe/goe/rest 
github.com/pascaldekloe/goe/verify returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pascaldekloe-goe
Version: 0.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 
> github.com/pascaldekloe/goe/el github.com/pascaldekloe/goe/metrics 
> github.com/pascaldekloe/goe/rest github.com/pascaldekloe/goe/verify
> internal/goos
> internal/goarch
> internal/unsafeheader
> internal/itoa
> internal/goexperiment
> runtime/internal/syscall
> internal/cpu
> runtime/internal/atomic
> math/bits
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> unicode/utf8
> internal/race
> sync/atomic
> encoding
> unicode/utf16
> container/list
> unicode
> crypto/internal/subtle
> crypto/subtle
> crypto/internal/boring/sig
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> internal/bytealg
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> math/rand
> internal/singleflight
> internal/sysinfo
> runtime/cgo
> errors
> sort
> internal/oserror
> io
> path
> strconv
> vendor/golang.org/x/net/dns/dnsmessage
> crypto/internal/nistec/fiat
> syscall
> bytes
> hash
> strings
> hash/crc32
> crypto/internal/randutil
> vendor/golang.org/x/text/transform
> crypto
> reflect
> crypto/rc4
> net/http/internal/ascii
> bufio
> internal/syscall/execenv
> internal/syscall/unix
> time
> io/fs
> github.com/pascaldekloe/goe/metrics
> context
> internal/poll
> embed
> encoding/binary
> internal/fmtsort
> os
> encoding/base64
> crypto/cipher
> crypto/internal/edwards25519/field
> crypto/md5
> vendor/golang.org/x/crypto/curve25519/internal/field
> vendor/golang.org/x/crypto/internal/poly1305
> crypto/internal/nistec
> encoding/pem
> crypto/internal/edwards25519
> crypto/internal/boring
> crypto/des
> vendor/golang.org/x/crypto/chacha20
> internal/godebug
> path/filepath
> fmt
> crypto/aes
> crypto/sha512
> crypto/hmac
> crypto/sha1
> crypto/sha256
> internal/intern
> io/ioutil
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/sys/cpu
> net/netip
> vendor/golang.org/x/crypto/chacha20poly1305
> encoding/json
> log
> github.com/pascaldekloe/goe/el
> mime
> compress/flate
> math/big
> encoding/hex
> net
> net/url
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/text/unicode/bidi
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> compress/gzip
> mime/quotedprintable
> net/http/internal
> flag
> runtime/debug
> runtime/trace
> vendor/golang.org/x/text/secure/bidirule
> testing
> crypto/elliptic
> crypto/internal/boring/bbig
> encoding/asn1
> crypto/rand
> crypto/dsa
> vendor/golang.org/x/net/idna
> crypto/ed25519
> crypto/rsa
> crypto/x509/pkix
> vendor/golang.org/x/crypto/cryptobyte
> github.com/pascaldekloe/goe/verify
> crypto/ecdsa
> net/textproto
> vendor/golang.org/x/net/http/httpproxy
> crypto/x509
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> crypto/tls
> net/http/httptrace
> net/http
> github.com/pascaldekloe/goe/rest
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go test -vet=off -v -p 8 github.com/pascaldekloe/goe/el 
> github.com/pascaldekloe/goe/metrics github.com/pascaldekloe/goe/rest 
> github.com/pascaldekloe/goe/verify
> === RUN   TestPaths
> --- PASS: TestPaths (0.00s)
> === RUN   TestPathFails
> --- PASS: TestPathFails (0.00s)
> === RUN   TestWildCards
> --- PASS: TestWildCards 

Processed: re: dwarf2sources FTBFS with rust-object 0.20

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 sid -n test -b

# the following fails with crash [1].
% sudo schroot -c test -r -- apt install --no-install-recommends emacs-nox

# the following succeeds:

sudo schroot -c test -r -- apt install --no-install-recommends emacs-nox 
emacs-el

Discussion
==

This is most likely the same bug as #1017798 and #1017779 (and probably others).

I don't think it depends on the flavour of emacs (I tested also emacs-gtk, same 
results).

[1]: crash log:

Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
corrupted size vs. prev_size
Fatal error 6: Aborted
Backtrace:
emacs(+0xe9d13)[0x55ec81734d13]
emacs(+0x30fed)[0x55ec8167bfed]
emacs(+0x314b7)[0x55ec8167c4b7]
emacs(+0xe8058)[0x55ec81733058]
emacs(+0xe8149)[0x55ec81733149]
/lib/x86_64-linux-gnu/libc.so.6(+0x3daf0)[0x7f9f70c64af0]
/lib/x86_64-linux-gnu/libc.so.6(+0x8983c)[0x7f9f70cb083c]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x12)[0x7f9f70c64a52]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xcf)[0x7f9f70c4f469]
/lib/x86_64-linux-gnu/libc.so.6(+0x7dc18)[0x7f9f70ca4c18]
/lib/x86_64-linux-gnu/libc.so.6(+0x9355a)[0x7f9f70cba55a]
/lib/x86_64-linux-gnu/libc.so.6(+0x93eb6)[0x7f9f70cbaeb6]
/lib/x86_64-linux-gnu/libc.so.6(+0x967a1)[0x7f9f70cbd7a1]
/lib/x86_64-linux-gnu/libc.so.6(malloc+0x1a2)[0x7f9f70cbe382]
emacs(+0x12ba45)[0x55ec81776a45]
emacs(+0x12bbb6)[0x55ec81776bb6]
emacs(+0x12bdf2)[0x55ec81776df2]
emacs(+0x12bf21)[0x55ec81776f21]
emacs(+0x102c38)[0x55ec8174dc38]
emacs(+0x173a36)[0x55ec817bea36]
emacs(+0x17790b)[0x55ec817c290b]
emacs(+0x17850a)[0x55ec817c350a]
emacs(+0x14df36)[0x55ec81798f36]
emacs(+0x14e165)[0x55ec81799165]
emacs(+0x14e3af)[0x55ec817993af]
emacs(+0x1737a8)[0x55ec817be7a8]
emacs(+0x174170)[0x55ec817bf170]
emacs(+0x17790b)[0x55ec817c290b]
emacs(+0x17850a)[0x55ec817c350a]
emacs(+0x14df36)[0x55ec81798f36]
emacs(+0x14e165)[0x55ec81799165]
emacs(+0x14e3af)[0x55ec817993af]
emacs(+0x1737a8)[0x55ec817be7a8]
emacs(+0x174170)[0x55ec817bf170]
emacs(+0x17790b)[0x55ec817c290b]
emacs(+0x17850a)[0x55ec817c350a]
emacs(+0x14df36)[0x55ec81798f36]
emacs(+0x14e165)[0x55ec81799165]
emacs(+0x14e3af)[0x55ec817993af]
emacs(+0x1737a8)[0x55ec817be7a8]
emacs(+0x174170)[0x55ec817bf170]
...
Aborted

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs-nox depends on:
ii  emacs-bin-common  1:27.1+1-3.1+b1
ii  emacs-common  1:27.1+1-3.1
ii  libacl1   2.3.1-1
ii  libasound21.2.7.2-1
ii  libc6 2.34-3
ii  libdbus-1-3   1.14.0-2
pn  libgccjit0
ii  libgmp10  2:6.2.1+dfsg1-1
ii  libgnutls30   3.7.7-2
ii  libgpm2   1.20.7-10
ii  libjansson4   2.14-2
ii  liblcms2-22.13.1-1
ii  libselinux1   3.4-1+b1
ii  libsystemd0   251.3-1
ii  libtinfo6 6.3+20220423-2
ii  libxml2   2.9.14+dfsg-1+b1
ii  zlib1g1:1.2.11.dfsg-4

emacs-nox recommends no packages.

Versions of packages emacs-nox suggests:
pn  emacs-common-non-dfsg  

Bug#1017798: please test

[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

[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 System
Contact ow...@bugs.debian.org with problems

Bug#1011628: rust-fasteval FTBFS: test failure

[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)

[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 && go test -vet=off -v -p 8 
github.com/hashicorp/go-sockaddr returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-hashicorp-go-sockaddr
Version: 0.0~git20170627.41949a1+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/hashicorp/go-sockaddr
> === RUN   Test_parseBSDDefaultIfName
> === RUN   Test_parseBSDDefaultIfName/macOS_Sierra_10.12_-_Common
> --- PASS: Test_parseBSDDefaultIfName (0.00s)
> --- PASS: Test_parseBSDDefaultIfName/macOS_Sierra_10.12_-_Common (0.00s)
> === RUN   Test_parseLinuxDefaultIfName
> === RUN   Test_parseLinuxDefaultIfName/Linux_Ubuntu_14.04_-_Common
> === RUN   
> Test_parseLinuxDefaultIfName/Chromebook_-_8743.85.0_(Official_Build)_stable-channel_gandof,_Milestone_54
> --- PASS: Test_parseLinuxDefaultIfName (0.00s)
> --- PASS: Test_parseLinuxDefaultIfName/Linux_Ubuntu_14.04_-_Common (0.00s)
> --- PASS: 
> Test_parseLinuxDefaultIfName/Chromebook_-_8743.85.0_(Official_Build)_stable-channel_gandof,_Milestone_54
>  (0.00s)
> === RUN   Test_parseWindowsDefaultIfName
> === RUN   Test_parseWindowsDefaultIfName/Windows_10_-_Enterprise
> --- PASS: Test_parseWindowsDefaultIfName (0.00s)
> --- PASS: Test_parseWindowsDefaultIfName/Windows_10_-_Enterprise (0.00s)
> === RUN   Test_VisitComands
> --- PASS: Test_VisitComands (0.00s)
> === RUN   TestGetPrivateIP
> --- PASS: TestGetPrivateIP (0.00s)
> === RUN   TestGetPrivateIPs
> --- PASS: TestGetPrivateIPs (0.00s)
> === RUN   TestGetPublicIP
> --- PASS: TestGetPublicIP (0.00s)
> === RUN   TestGetPublicIPs
> --- PASS: TestGetPublicIPs (0.00s)
> === RUN   TestGetInterfaceIP
> --- PASS: TestGetInterfaceIP (0.00s)
> === RUN   TestIfAddrAttr
> --- PASS: TestIfAddrAttr (0.00s)
> === RUN   TestIfAddrMath
> --- PASS: TestIfAddrMath (0.00s)
> === RUN   TestCmpIfAddrFunc
> --- PASS: TestCmpIfAddrFunc (0.00s)
> === RUN   TestFilterIfByFlags
> === RUN   TestFilterIfByFlags/broadcast
> === RUN   TestFilterIfByFlags/down
> === RUN   TestFilterIfByFlags/forwardable_IPv4
> === RUN   TestFilterIfByFlags/forwardable_IPv6
> === RUN   TestFilterIfByFlags/global_unicast
> === RUN   TestFilterIfByFlags/interface-local_multicast
> === RUN   TestFilterIfByFlags/link-local_multicast
> === RUN   TestFilterIfByFlags/link-local_unicast_IPv4
> === RUN   TestFilterIfByFlags/link-local_unicast_IPv6
> === RUN   TestFilterIfByFlags/loopback_ipv4
> === RUN   TestFilterIfByFlags/loopback_ipv6
> === RUN   TestFilterIfByFlags/multicast_IPv4
> === RUN   TestFilterIfByFlags/multicast_IPv6
> === RUN   TestFilterIfByFlags/point-to-point
> === RUN   TestFilterIfByFlags/unspecified
> === RUN   TestFilterIfByFlags/up
> === RUN   TestFilterIfByFlags/invalid
> --- PASS: TestFilterIfByFlags (0.00s)
> --- PASS: TestFilterIfByFlags/broadcast (0.00s)
> --- PASS: TestFilterIfByFlags/down (0.00s)
> --- PASS: TestFilterIfByFlags/forwardable_IPv4 (0.00s)
> --- PASS: TestFilterIfByFlags/forwardable_IPv6 (0.00s)
> --- PASS: TestFilterIfByFlags/global_unicast (0.00s)
> --- PASS: TestFilterIfByFlags/interface-local_multicast (0.00s)
> --- PASS: TestFilterIfByFlags/link-local_multicast (0.00s)
> --- PASS: TestFilterIfByFlags/link-local_unicast_IPv4 (0.00s)
> --- PASS: TestFilterIfByFlags/link-local_unicast_IPv6 (0.00s)
> --- PASS: TestFilterIfByFlags/loopback_ipv4 (0.00s)
> --- PASS: TestFilterIfByFlags/loopback_ipv6 (0.00s)
> --- PASS: TestFilterIfByFlags/multicast_IPv4 (0.00s)
> --- PASS: TestFilterIfByFlags/multicast_IPv6 (0.00s)
> --- PASS: TestFilterIfByFlags/point-to-point (0.00s)
> --- PASS: TestFilterIfByFlags/unspecified (0.00s)
> --- PASS: TestFilterIfByFlags/up (0.00s)
> --- PASS: TestFilterIfByFlags/invalid (0.00s)
> === RUN   TestIfByNetwork
> === RUN   TestIfByNetwork/exact_match
> === RUN   TestIfByNetwork/exact_match_plural
> === 

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.

[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: ArgumentError: Cannot proxy frozen objects, rspec-mocks 
relies on proxies for method stubbing and expectations.
Changed Bug title to 'ruby-axiom-types: FTBFS randomly: ArgumentError: Cannot 
proxy frozen objects, rspec-mocks relies on proxies for method stubbing and 
expectations.' from 'ruby-axiom-types: FTBFS: ERROR: Test "ruby3.0" failed: 
ArgumentError: Cannot proxy frozen objects, rspec-mocks relies on proxies for 
method stubbing and expectations.'.

-- 
1006026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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.

[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 row, and got a
60% failure rate. Tried again 20 times, then 55% failure rate.

I tried debugging this with the upstream sources from git and
ruby-standalone + bundler, but the upstream tree has broken dependencies
and I lost my patience.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


signature.asc
Description: PGP signature

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

[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.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1012987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpodofo
Version: 0.9.8+dfsg-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/libpodofo_0.9.8+dfsg-2_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:615:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const char*)’
  615 | operator<<(basic_ostream& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/ostream:615:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const PoDoFo::PdfString’) to type ‘const char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:628:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’
  628 | operator<<(basic_ostream& __out, const signed char* 
__s)
  | ^~~~
/usr/include/c++/12/ostream:628:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const PoDoFo::PdfString’) to type ‘const signed char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:633:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’
  633 | operator<<(basic_ostream& __out, const unsigned 
char* __s)
  | ^~~~
/usr/include/c++/12/ostream:633:5: note:   template argument 
deduction/substitution failed:
/usr/include/cppunit/tools/StringHelper.h:25:9: note:   cannot convert ‘x’ 
(type ‘const PoDoFo::PdfString’) to type ‘const unsigned char*’
   25 | ost << x;
  | ^~~~
/usr/include/c++/12/ostream:754:5: note: candidate: ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&)’
  754 | operator<<(_Ostream&& __os, const _Tp& __x)
  | ^~~~
/usr/include/c++/12/ostream:754:5: note:   template argument 
deduction/substitution failed:
/usr/include/c++/12/ostream: In substitution of ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&) [with _Ostream = 
std::__cxx11::basic_ostringstream&; _Tp = PoDoFo::PdfString]’:
/usr/include/cppunit/tools/StringHelper.h:25:9:   required from ‘typename 
std::enable_if<(! std::is_enum<_Tp>::value), std::__cxx11::basic_string 
>::type CppUnit::StringHelper::toString(const T&) [with T = PoDoFo::PdfString; 
typename std::enable_if<(! std::is_enum<_Tp>::value), 
std::__cxx11::basic_string >::type = std::__cxx11::basic_string]’
/usr/include/cppunit/TestAssert.h:74:50:   required from ‘static std::string 
CppUnit::assertion_traits::toString(const T&) [with T = PoDoFo::PdfString; 
std::string = std::__cxx11::basic_string]’
/usr/include/cppunit/TestAssert.h:168:58:   required from ‘void 
CppUnit::assertEquals(const T&, 

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

[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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1016452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: loggerhead
Version: 1.19~bzr524-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of loggerhead the autopkgtest of loggerhead fails 
in testing when that autopkgtest is run with the binary packages of 
loggerhead from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
loggerhead from testing1.19~bzr524-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=loggerhead

https://ci.debian.net/data/autopkgtest/testing/amd64/l/loggerhead/24205849/log.gz

running 0 tests...
brz selftest: /usr/bin/brz
   /usr/lib/python3/dist-packages/breezy
   bzr-3.2.2 python-3.10.5 Linux-5.10.0-16-amd64-x86_64-with-glibc2.33

unittest.loader._FailedTest.breezy.plugins.loggerheadERROR1ms
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", 
line 112, in load_tests

from .loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'breezy.plugins.loggerhead.loggerhead'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", 
line 114, in load_tests

from loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'loggerhead.tests'

==
ERROR: unittest.loader._FailedTest.breezy.plugins.loggerhead
--
testtools.testresult.real._StringException: Traceback (most recent call 
last):
  File 
"/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", 
line 112, in load_tests

from .loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'breezy.plugins.loggerhead.loggerhead'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/breezy/plugins/loggerhead/__init__.py", 
line 114, in load_tests

from loggerhead.tests import test_suite
ModuleNotFoundError: No module named 'loggerhead.tests'

--
Ran 1 test in 0.087s

FAILED (errors=1)
autopkgtest [12:12:39]: test testsuite



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: loggerhead
Source-Version: 2.0.0-1
Done: Jelmer Vernooij 

We believe that the bug you reported is fixed in the latest version of
loggerhead, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated loggerhead package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 14:38:51 +0100
Source: loggerhead
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bazaar Maintainers 
Changed-By: Jelmer Vernooij 
Closes: 1016452
Changes:
 loggerhead (2.0.0-1) unstable; urgency=medium
 .
   * Drop dependency on simpletal, move to chameleon.
   * New upstream release.
+ Fixes FTBFS. Closes: #1016452
   * Bump debhelper from old 

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

[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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1013545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gradle
Version: 4.4.1-14
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> sed '/@GENERATED@/,$d' debian/gradle.pod.in > debian/gradle.pod
> # process items: `-?`, `-h`, `--help`:: → =item `-?`, `-h`, `--help`
> # process bold: `-?` → B<-?>
> # remove empty line markers
> # drop text from links: https://gradle.com/build-scans[...]
> # drop underscores from documentation links
> # replace documentation links by UPPERCASE LABELS
> # ... but not those where the link is in a middle of a sentence
> # ... since otherwise it breaks the sentence structure
> # ... so just make it *bold* instead
> # move parethesed option "(comments)" outside of the bold parts
> # cut off everything after and including the [[daemon_cli]] section
> # cut off the introduction
> sed \
>   -e 's/\(.*\):: *$/\n=item \1\n/' \
>   -e 's/`\([^`]*\)`/B<\1>/g' \
>   -e 's/^+$//g' \
>   -e 's/\(https:[^[]*\)[[][^]]*\]/L<\1>/g' \
>   -e '/<]*>>/y/_/ /' \
>   -e 's/\([Tt]he\) <]*\)>>/\1 documentation section 
> B<\U\2\E>/g' \
>   -e 's/<]*\)>>/the documentation section B<\U\1\E>/g' \
>   -e '/<<[^>]*>>/y/_/ /' \
>   -e 's/<<.[^,]*,\([^>]*\)>>/B<\1>/g' \
>   -e 's/\([Tt]he\) <<\([^>]*\)>>/\1 documentation section B<\U\2\E>/g' \
>   -e 's/<<\([^>]*\)>>/the documentation section B<\U\1\E>/g' \
>   -e 's/ (\([^)]*\))>/> (\1)/g' \
>   -e '/^\[\[.*]]$/d' \
>   -e 's/GRADLE OPTS/GRADLE_OPTS/g' \
>   -e 's/^=== \(.*\)$/=back\n\n=head1 \U\1\n\n/g' \
>   -e '0,/The command-line options available/d' \
>   subprojects/docs/src/docs/userguide/commandLine.adoc >> 
> debian/gradle.pod
> sed '0,/@GENERATED@/d' debian/gradle.pod.in >> debian/gradle.pod
> touch -d@1654004578 debian/gradle.pod
> pod2man --errors=stderr --utf8 -r "Gradle 4.4.1" -c "Gradle Command Line 
> Manual" debian/gradle.pod > debian/gradle.1
> debian/gradle.pod around line 196: '=item' outside of any '=over'
> debian/gradle.pod around line 229: '=item' outside of any '=over'
> debian/gradle.pod around line 244: '=item' outside of any '=over'
> Wide character in printf at /usr/share/perl/5.34/Pod/Simple.pm line 573.
> debian/gradle.pod around line 250: Non-ASCII character seen before =encoding 
> in '“B”'. Assuming UTF-8
> rm -f gradle.properties # Some properties here breaks the latest JVM
> mkdir --parents buildSrc/src/main/java/tmp # Symlinks are for building Gradle 
> 4 using Gradle 3
> ln --symbolic --force --target-directory=buildSrc/src/main/java/tmp/ 
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/Directory.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/DirectoryProperty.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/FileSystemLocation.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFile.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFileProperty.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/NonNullApi.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Property.java
>  
> ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Provider.java
>  
> ../../../../../subprojects/core/src/main/java/org/gradle/api/internal/file/TaskFileVarFactory.java
> gradle assemble startScripts --project-prop finalRelease=true --offline 
> --stacktrace --gradle-user-home debian/.gradlehome --no-daemon 
> -Dgradle-debian-helper.hook.enabled=false -x :distributions:assemble -x 
> :internalTesting:assemble -x :internalIntegTesting:assemble -x 
> :internalPerformanceTesting:assemble -x :integTest:assemble -x 
> :performance:assemble -x :smokeTest:assemble -x :soak:assemble --parallel 
> --max-workers=8
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on 
> 

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

[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 is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1012214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gradle
Version: 4.4.1-14
Severity: serious
X-Debbugs-Cc: a...@debian.org

Hi,

The newly added --add-opens option is only valid for OpenJDK 17. I
understand that we switch to it for Debian 12 but it currently breaks
all packages that are built with OpenJDK 11. I am currently in the
process to update gradle to a newer upstream release. We should try to
use a conditional clause depending on the JVM in use.

Markus
--- End Message ---
--- Begin Message ---
Source: gradle
Source-Version: 4.4.1-15
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
gradle, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1012...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated gradle package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 15:26:04 +0200
Source: gradle
Architecture: source
Version: 4.4.1-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 1012214 1013545
Changes:
 gradle (4.4.1-15) unstable; urgency=medium
 .
   [ 殷啟聰 | Kai-Chung Yan ]
   * Team upload.
   * Remove myself from Uploaders
 .
   [ Markus Koschany ]
   * Depend on libjansi1-java instead of libjansi-java.
 (Closes: #1012214, #1013545)
   * maven.rules: use only libjansi1-java.
   * substituteDependencies.gradle: Fix substitution rule for jansi1.
   * Declare compliance with Debian Policy 4.6.1.
Checksums-Sha1:
 c52f11d8e63b9a2dfb6ddf87f1080f4c436a6cd5 3419 gradle_4.4.1-15.dsc
 34ceefb1f0aa08f264bef482667ebda46e2c4b58 59236 gradle_4.4.1-15.debian.tar.xz
 10f155baf8fbaac29300259b1c92ec5dd70aee11 16306 gradle_4.4.1-15_amd64.buildinfo
Checksums-Sha256:
 4238bcb4996413252ebed9f1a83656c0b9bfa25ab2ec49b33228128f13ea7f87 3419 
gradle_4.4.1-15.dsc
 668412a8addae10cfa8062a10be913792ace20b4936d6ba3c11f46ff3ecf242a 59236 
gradle_4.4.1-15.debian.tar.xz
 1a3adb61c3e573c93bed1cc5a2b1f86219d53e8decedcd2e9525434179891e44 16306 
gradle_4.4.1-15_amd64.buildinfo
Files:
 e2782f66aa0f3ed36db19d1774530fe6 3419 java optional gradle_4.4.1-15.dsc
 6863640ae439a060210142071973159c 59236 java optional 
gradle_4.4.1-15.debian.tar.xz
 14cf709bc7f05f556c653a3d8e269af0 16306 java optional 
gradle_4.4.1-15_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmMCOaFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkRPAP/3rZrQRt7NDTG9WoOR9nYGyyBYtqJYZuwA3Q
V6a5rt1tN50SeXNZcj69foU9WdSd3K3FbpFN4fByUbQXA+CKVZFvL+7H0C5A+ApN
dgUm2gergb5VsK5pj8/97ZDzK4CKsxzRs0zQN3coD3o+Na9Vm/KtqVG9vUNxZtd/
qosFzkxQzRwyKkmuJEsc2H1tyA+e9MxsqnXAmAwkYKtYleaDlAb/EHkVkQG/50Pc
8xEiC1g+VXGzNvcOFWVpKjDS7gQ8EVxSQgV20a/xLS+Po1h44qaaX/lcnZSMee4L
jvCxTQ2xiHFZjjy2NYHhjp8tK4tiJEt8TYo+2kf4tBBdZAAx27znwHGss4jyw15v
iGM7xdw3TaC5V6jZRq3IotSw75clP14Z3ACpnaX8cK/ZK01NDjfnGNV+N+O4nspq
v2J/8YuFrIZOnER0RF3Jo8O+pU2Jyv7lcvJiHQWGECvz7jqUb3krtupZQ+5KRMXp
C9B0rhdlkhXZ/WSo02dsVRbMDq3vMYAIL+lcis0uQfDgT6N3JoOYicw88oD+R1mE
GwjZCLbp3oTtrVs0hIOk4qUej2BGvZSkzYmvWrFJ511iE+aEhL+SftWvFpZQS85X
oC8H5Ibd+Qx+UKRApUNGGRYw/rcd7ooS3iIJS4ztTIdCSYAA0Z1cmTpEcVIOKD5V
DdxufzR/
=i3cm
-END PGP SIGNATURE End Message ---

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

[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 as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1005427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack-test
Version: 0.7.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  Failure/Error: expect(body).to receive(:close)
> 
>(#).close(*(any args))
>expected: 1 time with any arguments
>received: 2 times with any arguments
>  # ./spec/rack/test_spec.rb:168:in `block (4 levels) in '
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/rack/test/cookie_spec.rb:49:in `block (3 levels) in 
> '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 0.17521 seconds (files took 0.627 seconds to load)
> 204 examples, 1 failure, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/rack/test_spec.rb:166 # Rack::Test::Session#request when the 
> response body responds_to?(:close) closes response's body
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/ruby-rack-test_0.7.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-rack-test
Source-Version: 2.0.2-1
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-rack-test, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-rack-test 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 21 Aug 2022 11:12:15 -0300
Source: ruby-rack-test
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1005427
Changes:
 ruby-rack-test (2.0.2-1) unstable; urgency=medium
 .
   * Team upload
   * debian/watch: point at github to get tests
   * New upstream version 2.0.2
 - Upstream changed the test suite from rspec to minitest, so the reported
   build failure no longer applies (Closes: #1005427)
   * debian/upstream/metadata: update with dh-make-ruby
   * debian/rules: stop setting DH_RUBY_GEMSPEC, no longer needed
   * debian/control: update with dh-make-ruby
 - Bump Standards-Version to 4.6.1; no changes needed
 - Drop alternative build dependency on ruby-rack1.4 (it no longer exists)
 - Update homepage to point to the new upstream homepage
   

Processed: Bug#1012987 marked as pending in libpodofo

[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

[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:

https://salsa.debian.org/debian/libpodofo/-/commit/4523284f7c2d19a81351ae6b35947acd499c4c07


Fix declaration of operator<< for PoDoFo::PdfString (Closes: #1012987)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1012987

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

[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 with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1013932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2022.01a-9
Severity: serious
Tags: ftbfs

Hi Maintainer

yade currently FTBFS in unstable and testing.  The  failure [1] was
picked up during the onetbb transition, but might not be related as
yade was test built before the transition was started.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=yade


--
Ran 93 tests in 9.139s

OK
 [92m*** ALL TESTS PASSED *** [0m
[x86-csail-01:2352391] *** Process received signal ***
[x86-csail-01:2352391] Signal: Segmentation fault (11)
[x86-csail-01:2352391] Signal code: Address not mapped (1)
[x86-csail-01:2352391] Failing at address: 0x7fee112ef5e0
Segmentation fault
--- End Message ---
--- Begin Message ---
Source: yade
Source-Version: 2022.01a-10
Done: Anton Gladky 

We believe that the bug you reported is fixed in the latest version of
yade, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated yade package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Aug 2022 12:23:09 +0200
Source: yade
Architecture: source
Version: 2022.01a-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 1013072 1013932
Changes:
 yade (2022.01a-10) unstable; urgency=medium
 .
   * [5528878] Fix GCC-12 FTBFS. (Closes: #1013072)
   * [884074b] Fix tests. (Closes: #1013932)
   * [2641285] Set Standards-Version: 4.6.1
Checksums-Sha1:
 fb0856bdc23ba5586b700f03671cae386811aaa3 3251 yade_2022.01a-10.dsc
 fda1b45e2a36a9d10489e6b18d4cc278370a24b2 48284 yade_2022.01a-10.debian.tar.xz
 e933efaf68ee53dd4352257d5f06d79c0103556d 30043 
yade_2022.01a-10_source.buildinfo
Checksums-Sha256:
 f1dc2478737a730aa657f59b97ded4b1bf0ea20724844755d26a3eb204a2515d 3251 
yade_2022.01a-10.dsc
 47d213e8408348fd2aaccb220ed909d4d9dbb338114b25533dd7548e1794e791 48284 
yade_2022.01a-10.debian.tar.xz
 72d4e35eb3f061bfa72b8f815e975a30bf6276f3f9f1ffe4a9ed99a80303d6d6 30043 
yade_2022.01a-10_source.buildinfo
Files:
 9a6f845a6558a4204f4c46a9e596f1d6 3251 science optional yade_2022.01a-10.dsc
 1a8f613ec46b5f3598d30cfb8256a873 48284 science optional 
yade_2022.01a-10.debian.tar.xz
 08c25239a60c5f634e2b915fd64107e5 30043 science optional 
yade_2022.01a-10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmMCNe8ACgkQ0+Fzg8+n
/wYJig/+LnyZLNiqf/2bSfCjnBIICIZ4dsAsQj0g/UNDiQXbtw5vEW+gQAgqtmhS
jp6Js06L7vdw16QD+r+tKbc+xHmXm/MuEmkLl0wGL65UhOrqbpj7CaTNQejnr9m8
/rKVhbJjg0sN6/LPbJt02f2Hg4T+EC6M1uYjzsM0E3babuZEsLARtfdjbvcJac+T
2TI6Xq2Fd85PEOcS9TSMom2IWDqrcg/YtxU+CNQrg8NucGoiUp8rV5aASfp8K7S0
xrHnxFArFkzfm/WxwjoaUcwD9QWDLcFS0l09elQPlIveeBX8I8NegH/XRZYLza6a
OdSnd4Umzau4UFkAoEL70NCb3Vq9aobPL6y8eu9Iy63wTRRyRF6PkZE528giRIgZ
toh5lmHEXKc5mn9v8zP4Ql86e/ZYPCgzMjP4RTXvFsbZwsvUVBjkVI1/0LkR5jnL
ZnNaitUD9Y1RaHYx4BHWjyCk2kwHFbFBr9TDE9kJb3DjFNrUURV9fHootRu37/3Y
j2ufn5FL8yJhrxsAUGOpxuLp4VXWvUSdgBecDYG4h7Nz4bZjAder13fDlT3K2U4K
v0WL4S5J3rhMVdiBWKb35OK0tV0Onrn/feRGS58lMIDMbik59rnhbbnzv6de3P/A
vm54r5M/2y6J1dJmSL9OQRmFB8qXqB2pwJR5noo1LkdDcdJkQUM=
=+jDd
-END PGP SIGNATURE End Message ---

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

[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 not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1013072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yade
Version: 2022.01a-9
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

[This bug is targeted to the upcoming bookworm release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/yade_2022.01a-9_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
/<>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox]’:
/<>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 | const Box& self = py::extract(obj)();
  |   ^
In member function ‘const Eigen::AlignedBox::VectorType& 
Eigen::AlignedBox::max() const [with _Scalar = double; int 
_AmbientDim = 3]’,
inlined from ‘static std::string AabbVisitor::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox]’ at 
/<>/py/high-precision/minieigen/visitors.hpp:980:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:146:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  146 |   EIGEN_DEVICE_FUNC inline const VectorType& (max)() const { return 
m_max; }
  |   ^
/<>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox]’:
/<>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 | const Box& self = py::extract(obj)();
  |   ^
In member function ‘const Eigen::AlignedBox::VectorType& 
Eigen::AlignedBox::min() const [with _Scalar = double; int 
_AmbientDim = 3]’,
inlined from ‘static std::string AabbVisitor::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox]’ at 
/<>/py/high-precision/minieigen/visitors.hpp:978:78:
/usr/include/eigen3/unsupported/Eigen/../../Eigen/src/Geometry/AlignedBox.h:142:51:
 error: dangling pointer to an unnamed temporary may be used 
[-Werror=dangling-pointer=]
  142 |   EIGEN_DEVICE_FUNC inline const VectorType& (min)() const { return 
m_min; }
  |   ^
/<>/py/high-precision/minieigen/visitors.hpp: In static member 
function ‘static std::string AabbVisitor::__str__(const 
boost::python::api::object&) [with Box = Eigen::AlignedBox]’:
/<>/py/high-precision/minieigen/visitors.hpp:975:39: note: unnamed 
temporary defined here
  975 | const Box& self = py::extract(obj)();
  |   ^
In member function ‘const Eigen::AlignedBox::VectorType& 
Eigen::AlignedBox::max() const [with _Scalar = 
boost::multiprecision::number; int _AmbientDim = 3]’,

Processed: affects 1017834

[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 you need assistance.
-- 
1017834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 1017845

[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 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el
Added indication that 1017845 affects elpa-smart-mode-line-powerline-theme
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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-

[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 elpa-git-commit

-- 
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 recursion on subroutine 
"main::generate_relevant_tsort_dependencies_internals" at 
/usr/lib/emacsen-common/lib.pl line 127.

> So far I had to unsinstall the following packages to make it go away,
> i.e. these packages trigger the issue:
> 
> aelpa-folding
> org-mode
> git-timemachine
> elpa-password-store
> 
> There might be more.

Another one:

elpa-git-commit

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: severity of 1017834 is serious

[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.
-- 
1017834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1017833 is serious, affects 1017833

[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] elpa-elscreen: emacs 28.1 upgrade failure with 
byte compiling of elpa-elscreen
Added indication that 1017833 affects emacs and emacs-gtk
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1017833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 time:

root 31971  0.0  0.0   2708   944 pts/10   S+   14:05   0:00  | 
  \_ /bin/sh /var/lib/dpkg/info/emacs-gtk.postinst configure 1:27.1+1-3.1+b1
root 31975  0.0  0.0  21200 13980 pts/10   S+   14:05   0:00  | 
  \_ /usr/bin/perl -w /usr/lib/emacsen-common/emacs-install emacs
root 32250  0.0  0.0  0 0 pts/10   Z+   14:05   0:00  | 
  \_ [emacs-install] 
root  1496  0.0  0.0   2708   952 pts/10   S+   14:08   0:00  | 
  \_ /bin/sh 
/usr/lib/emacsen-common/packages/install/elpa-password-store emacs
root  1497  0.0  0.0   2708   952 pts/10   S+   14:08   0:00  | 
  \_ /bin/sh /usr/lib/dh-elpa/helper/install emacs password-store 
2.1.4
root  1500  0.0  0.0   2708   120 pts/10   S+   14:08   0:00  | 
  \_ /bin/sh /usr/lib/dh-elpa/helper/install emacs 
password-store 2.1.4
root  1501  0.6  0.0 253396 62048 pts/10   Sl+  14:08   0:01  | 
  \_ emacs --quick --batch -l package --eval (setq 
package-user-dir "/nonexistent") --eval (add-to-list 'package-directory-list 
"/usr/share/emacs/site-lisp/elpa-src") -f package-initialize -f 
batch-byte-compile password-store-autoloads.el password-store-pkg.el 
password-store.el
root  1534  1.1  0.0 254684 61876 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-6d616b652d70726f63657373_make_process_0-rZME2o.el
root  1536  1.1  0.0 254680 61848 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-hNB5Cs.el
root  1538  1.1  0.0 254684 61872 ?Ssl  14:09   0:02  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-ybucTI.el
root  1543  1.2  0.0 254680 62036 ?Ssl  14:09   0:02  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-h2cpn1.el
root  1545  1.3  0.0 254684 61920 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-xAswlm.el
root  1547  1.3  0.0 254680 61980 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-nJWdN3.el
root  1555  1.2  0.0 254684 61992 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-BB0YM6.el
root  1557  1.2  0.0 254680 62004 ?Ssl  14:09   0:02  | 
  \_ /usr/bin/emacs --batch 
-l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-XiRm2f.el
root  1559  1.3  0.0 254684 61968 ?Ssl  14:09   0:03  | 
  \_ /usr/bin/emacs 
--batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-bEF8Rf.el
root  1561  1.2  0.0 254680 61808 ?Ssl  14:09   0:02  | 
  \_ /usr/bin/emacs 
--batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-Pk7AH2.el
root  1563  1.3  0.0 254684 61932 ?Ssl  14:09   0:03  | 
  \_ 
/usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-2sptbI.el
root  1565  1.3  0.0 254680 62028 ?Ssl  14:09   0:02  | 
  \_ 
/usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-cHWZzN.el
root  1567  1.3  0.0 254684 61964 ?Ssl  14:09   0:02  | 
  \_ 
/usr/bin/emacs --batch -l 

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

[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 
/tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el
Added indication that 1017845 affects elpa-folding, elpa-org, 
elpa-git-timemachine, and elpa-password-store

-- 
1017845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 package a new
> > upstream
> > release of mediathekview. And we also need to fix kotlin in unstable. If
> > someone wants to help, that's our todo list.
> 
> This sounds like a plan. Unfortunately, I basically don't have a clue
> on these issues, so I cannot help. Since I'm only a DM, I can't even
> push an upload. But if I should test something, please let me know.

[...]

I intend to embed the H2 engine into Mediathekview and revert back to the
previous working state. That should resolve the current issues at least for the
short term. I hope all the new dependencies of mediathekview can be packaged at
some point but realistically it will take more time and the new dependency on
kotlin complicates future maintenance even more. If someone wants to help then
my previous todo list is a good starting point.

Regards,

Markus


signature.asc
Description: This is a digitally signed message part

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

[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 -p 8 github.com/biogo/hts/bam 
github.com/biogo/hts/bgzf github.com/biogo/hts/bgzf/cache 
github.com/biogo/hts/bgzf/index github.com/biogo/hts/cram 
github.com/biogo/hts/cram/encoding/itf8 github.com/biogo/hts/cram/encoding/ltf8 
github.com/biogo/hts/csi github.com/biogo/hts/fai github.com/biogo/hts/internal 
github.com/biogo/hts/sam github.com/biogo/hts/tabix returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-biogo-hts
Version: 1.4.3+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f bgzf/line_example_test.go
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/biogo/hts/bam github.com/biogo/hts/bgzf 
> github.com/biogo/hts/bgzf/cache github.com/biogo/hts/bgzf/index 
> github.com/biogo/hts/cram github.com/biogo/hts/cram/encoding/itf8 
> github.com/biogo/hts/cram/encoding/ltf8 github.com/biogo/hts/csi 
> github.com/biogo/hts/fai github.com/biogo/hts/internal 
> github.com/biogo/hts/sam github.com/biogo/hts/tabix
> internal/unsafeheader
> internal/goexperiment
> internal/goarch
> internal/race
> internal/goos
> runtime/internal/atomic
> sync/atomic
> runtime/internal/syscall
> internal/cpu
> unicode
> unicode/utf8
> internal/itoa
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> math/bits
> github.com/ulikunitz/xz/internal/hash
> internal/bytealg
> github.com/biogo/hts/cram/encoding/itf8
> github.com/biogo/hts/cram/encoding/ltf8
> math
> runtime
> sync
> internal/reflectlite
> internal/testlog
> errors
> sort
> internal/oserror
> path
> strconv
> io
> syscall
> container/heap
> hash
> strings
> bytes
> hash/crc32
> bufio
> reflect
> compress/bzip2
> internal/syscall/execenv
> internal/syscall/unix
> time
> internal/poll
> io/fs
> os
> internal/fmtsort
> encoding/binary
> io/ioutil
> fmt
> github.com/ulikunitz/xz/internal/xlog
> encoding/hex
> encoding/csv
> net/url
> compress/flate
> github.com/biogo/hts/fai
> github.com/ulikunitz/xz/lzma
> compress/gzip
> github.com/biogo/hts/bgzf
> github.com/biogo/hts/bgzf/cache
> github.com/biogo/hts/bgzf/index
> github.com/biogo/hts/csi
> github.com/biogo/hts/internal
> github.com/biogo/hts/sam
> github.com/biogo/hts/tabix
> github.com/biogo/hts/cram
> github.com/biogo/hts/bam
>dh_auto_test -O--buildsystem=golang
>   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/biogo/hts/bgzf/cache github.com/biogo/hts/bgzf/index 
> github.com/biogo/hts/cram github.com/biogo/hts/cram/encoding/itf8 
> github.com/biogo/hts/cram/encoding/ltf8 github.com/biogo/hts/csi 
> github.com/biogo/hts/fai github.com/biogo/hts/internal 
> github.com/biogo/hts/sam github.com/biogo/hts/tabix
> === RUN   Test
> OK: 15 passed
> --- PASS: Test (0.07s)
> === RUN   TestFuzzCrashers
> --- PASS: TestFuzzCrashers (3.16s)
> === RUN   TestMerger
> --- PASS: TestMerger (0.12s)
> PASS
> okgithub.com/biogo/hts/bam3.512s
> === RUN   TestEmpty
> --- PASS: TestEmpty (0.00s)
> === RUN   TestEOF
> --- PASS: TestEOF (0.00s)
> === RUN   TestRoundTrip
> --- PASS: TestRoundTrip (0.01s)
> === RUN   TestRoundTripMulti
> --- PASS: TestRoundTripMulti (0.01s)
> === RUN   TestHeaderIssue57
> --- PASS: TestHeaderIssue57 (0.00s)
> === RUN   TestRoundTripMultiSeek
> --- PASS: TestRoundTripMultiSeek (0.00s)
> === RUN   TestSeekErrorDeadlock
> --- PASS: TestSeekErrorDeadlock (0.00s)
> === RUN   TestSeekFast
> --- PASS: TestSeekFast (0.05s)
> === RUN   TestCache
> --- PASS: TestCache (0.30s)
> === RUN   TestBlocked
> --- PASS: TestBlocked (0.00s)
> === RUN   TestFuzzCrashers
> bgzf_test.go:1139: unexpected error creating reader: unexpected EOF
> --- FAIL: TestFuzzCrashers (0.01s)
> === RUN   TestZeroNonZero
> --- PASS: TestZeroNonZero (0.00s)
> === RUN   TestWriteByteCount
> 

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

[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

[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 #1004022 to the same values 
previously set
> forcemerge 1004022 1017170
Bug #1004022 [src:clasp] clasp: Clasp FTBFS with glibc 2.34
Bug #1017170 [src:clasp] clasp: FTBFS: catch.hpp:6415:41: error: array bound is 
not an integer constant before ‘]’ token
Added tag(s) patch.
Bug #1004022 [src:clasp] clasp: Clasp FTBFS with glibc 2.34
Marked as found in versions clasp/3.3.5-4.
Merged 1004022 1017170
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1004022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004022
1017170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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.
Ignoring request to alter fixed versions of bug #1004310 to the same values 
previously set
> tag 1004310 + ftbfs bookworm sid
Bug #1004310 [src:knxd] knxd: ftbfs with glibc 2.34: don't use common unix 
function name as variable name
Added tag(s) sid, ftbfs, and bookworm.
> tag 1004310 - experimental
Bug #1004310 [src:knxd] knxd: ftbfs with glibc 2.34: don't use common unix 
function name as variable name
Removed tag(s) experimental.
> forcemerge 1004310 1017139
Bug #1004310 [src:knxd] knxd: ftbfs with glibc 2.34: don't use common unix 
function name as variable name
Bug #1017139 [src:knxd] knxd: FTBFS: knxd_args.cpp:71:13: error: ‘char link 
[99]’ redeclared as different kind of entity
Added tag(s) patch.
Bug #1004310 [src:knxd] knxd: ftbfs with glibc 2.34: don't use common unix 
function name as variable name
Marked as found in versions knxd/0.14.46-1.
Merged 1004310 1017139
> # massivethreads
> tag 1014566 + ftbfs bookworm sid
Bug #1014566 [massivethreads] massivethreads: FTBFS with glibc 2.34
Added tag(s) bookworm, ftbfs, and sid.
> tag 1014566 - experimental
Bug #1014566 [massivethreads] massivethreads: FTBFS with glibc 2.34
Removed tag(s) experimental.
> # gtk-gnutella
> tag 1014924 + ftbfs
Bug #1014924 [gtk-gnutella] gtk-gnutella: FTBFS with glibc >= 2.34
Ignoring request to alter tags of bug #1014924 to the same tags previously set
> # monado
> tag 1001262 + ftbfs
Bug #1001262 [monado] monado: FTBFS with glibc 2.34
Added tag(s) ftbfs.
> severity 1001262 serious
Bug #1001262 [monado] monado: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> # tarantool
> severity 1001354 serious
Bug #1001354 [tarantool] tarantool: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> # openmw
> severity 1009684 serious
Bug #1009684 [src:openmw] openmw: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> # aspcud
> tag 1000852 + ftbfs bookworm sid
Bug #1000852 [src:aspcud] aspcud: FTBFS with glibc 2.34
Added tag(s) sid, bookworm, and ftbfs.
> severity 1000852 serious
Bug #1000852 [src:aspcud] aspcud: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> forcemerge 1000852 1000852
Bug #1000852 [src:aspcud] aspcud: FTBFS with glibc 2.34
Merged 1000852
> # salmon
> severity 1008254 serious
Bug #1008254 [src:salmon] salmon: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> # clasp
> tag 1004022 + ftbfs bookworm sid
Bug #1004022 [clasp] clasp: Clasp FTBFS with glibc 2.34
Added tag(s) ftbfs, bookworm, and sid.
> severity 1004022 serious
Bug #1004022 [clasp] clasp: Clasp FTBFS with glibc 2.34
Severity set to 'serious' from 'normal'
> forcemerge 1004022 1017170
Bug #1004022 [clasp] clasp: Clasp FTBFS with glibc 2.34
Unable to merge bugs because:
package of #1017170 is 'src:clasp' not 'clasp'
Failed to forcibly merge 1004022: Did not alter merged bugs.

> # apitrace
> tag 992145 + ftbfs
Bug #992145 [src:apitrace] apitrace ftbfs with glibc 2.34
Added tag(s) ftbfs.
> severity 992145 serious
Bug #992145 [src:apitrace] apitrace ftbfs with glibc 2.34
Severity set to 'serious' from 'important'
> # segyio
> tag 1000851 + ftbfs bookworm sid
Bug #1000851 [src:segyio] segyio: FTBFS with glibc 2.34
Added tag(s) sid, bookworm, and ftbfs.
> severity 1000851 serious
Bug #1000851 [src:segyio] segyio: FTBFS with glibc 2.34
Severity set to 'serious' from 'important'
> forcemerge 1000851 1017156
Bug #1000851 [src:segyio] segyio: FTBFS with glibc 2.34
Bug #1017156 [src:segyio] segyio: FTBFS: catch.hpp:7431:58: error: call to 
non-‘constexpr’ function ‘long int sysconf(int)’
Set Bug forwarded-to-address to 'https://github.com/equinor/segyio/issues/520'.
Marked as found in versions segyio/1.8.3-1.1.
Merged 1000851 1017156
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1000851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000851
1000852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000852
1001262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001262
1001354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001354
1004022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004022
1004310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004310
1008254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008254
1009684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009684
1014566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014566
1014924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014924
1017139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017139
1017156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017156
1017170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017170
992145: 

Processed: your mail

[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 assistance.
-- 
952159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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]: https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/377

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

[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 FTBFS witn fmtlib 9.0.0 (?)
Added tag(s) patch.

-- 
1017802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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

[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 contact me if you need assistance.
-- 
965710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 1014717 in 2.0.8.1-2

[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.
-- 
1014717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1017199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rumur
Version: 2022.03.05-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> ==
> FAIL: test_strace_sandbox_sh (__main__.executable)
> --
> Traceback (most recent call last):
>   File "/<>/tests/run-tests.py", line 556, in 
> setattr(executable, name, lambda self, p=p: self._run(p))
>   File "/<>/tests/run-tests.py", line 71, in _run
> self.fail(output)
> AssertionError: /tmp/tmp.qbzy57r9Bf /<>/obj-x86_64-linux-gnu
> /<>/obj-x86_64-linux-gnu
> ++ mktemp -d
> + TMP=/tmp/tmp.qbzy57r9Bf
> + pushd /tmp/tmp.qbzy57r9Bf
> + cat -
> + rumur --sandbox on --output model.c model.m
> + '[' True = True ']'
> + MCX16=-mcx16
> + '[' False '!=' False ']'
> + LIBATOMIC=
> + /usr/bin/cc -std=c11 -mcx16 model.c -o model.exe -lpthread
> model.c:133:2: warning: #warning you are compiling without optimizations 
> enabled. I would suggest -march=native -O3 -fwhole-program -mcx16. [-Wcpp]
>   133 | #warning you are compiling without optimizations enabled. I would 
> suggest -march=native -O3 -fwhole-program -mcx16.
>   |  ^~~
> + strace ./model.exe
> execve("./model.exe", ["./model.exe"], 0x7ffcf62e67e0 /* 88 vars */) = 0
> brk(NULL)   = 0x55877f1aa000
> mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
> 0x7f389142a000
> access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
> directory)
> openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=10918, ...}, AT_EMPTY_PATH) 
> = 0
> mmap(NULL, 10918, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3891427000
> close(3)= 0
> openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> read(3, 
> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\223\2\0\0\0\0\0"..., 832) 
> = 832
> pread64(3, 
> "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784, 64) 
> = 784
> pread64(3, 
> "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\200\0\300\4\0\0\0\1\0\0\0\0\0\0\0", 32, 
> 848) = 32
> pread64(3, 
> "\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\315E\254\255\254\211\23\254\2436j!!F\322\f"...,
>  68, 880) = 68
> newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=2049032, ...}, 
> AT_EMPTY_PATH) = 0
> pread64(3, 
> "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784, 64) 
> = 784
> mmap(NULL, 2101136, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
> 0x7f3891226000
> mmap(0x7f389124e000, 1499136, PROT_READ|PROT_EXEC, 
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x28000) = 0x7f389124e000
> mmap(0x7f38913bc000, 360448, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
> 3, 0x196000) = 0x7f38913bc000
> mmap(0x7f3891414000, 24576, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1ed000) = 0x7f3891414000
> mmap(0x7f389141a000, 53136, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f389141a000
> close(3)= 0
> mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
> 0x7f3891223000
> arch_prctl(ARCH_SET_FS, 0x7f3891223840) = 0
> set_tid_address(0x7f3891223b10) = 3222871
> set_robust_list(0x7f3891223b20, 24) = 0
> mprotect(0x7f3891414000, 16384, PROT_READ) = 0
> mprotect(0x55877d65d000, 4096, PROT_READ) = 0
> mprotect(0x7f389145c000, 8192, PROT_READ) = 0
> prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, 
> rlim_max=RLIM64_INFINITY}) = 0
> munmap(0x7f3891427000, 10918)   = 0
> ioctl(1, TCGETS, 0x7ffca343f7f0)= -1 ENOTTY (Inappropriate ioctl for 
> device)
> close(0)= 0
> prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0)  = 0
> prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, {len=44, filter=0x55877d65e160}) = > 0
> newfstatat(1, "", {st_mode=S_IFIFO|0600, st_size=0, ...}, AT_EMPTY_PATH) = 0
> 

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

[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
> someone wants to help, that's our todo list.

This sounds like a plan. Unfortunately, I basically don't have a clue
on these issues, so I cannot help. Since I'm only a DM, I can't even
push an upload. But if I should test something, please let me know.

Unfortunately, since yesterday mediathekview does not start anymore
(i.e. hangs during startup). I might try to debug it a little, but
probably will have to use the version provided by upstream; hopefully
the new Debian version can be provided soon. I really use it a lot.

Thanks for maintaining and working on the new version.

Greetings

 Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

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

[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:

Install elpa-jabber for emacs
install/jabber-0.8.92: Handling install of emacsen flavor emacs
install/jabber-0.8.92: byte-compiling for emacs

In toplevel form:
fsm.el:108:1: Warning: Package cl is deprecated
fsm.el:131:1: Warning: ‘defmacro*’ is an obsolete alias (as of 27.1); use
‘cl-defmacro’ instead.

In define-state-machine:
fsm.el:166:18: Warning: ‘destructuring-bind’ is an obsolete alias (as of
27.1); use ‘cl-destructuring-bind’ instead.
fsm.el:183:1: Warning: ‘defmacro*’ is an obsolete alias (as of 27.1); use
‘cl-defmacro’ instead.
fsm.el:214:1: Warning: ‘defmacro*’ is an obsolete alias (as of 27.1); use
‘cl-defmacro’ instead.
fsm.el:233:1: Warning: ‘defmacro*’ is an obsolete alias (as of 27.1); use
‘cl-defmacro’ instead.

In define-fsm:
fsm.el:255:29: Warning: ‘loop’ is an obsolete alias (as of 27.1); use
‘cl-loop’ instead.

In fsm-goodbye-cruel-world:
fsm.el:283:8: Warning: ‘remprop’ is an obsolete function (as of 27.1); use
‘cl-remprop’ instead.
fsm.el:283:21: Warning: ‘remprop’ is an obsolete function (as of 27.1); use
‘cl-remprop’ instead.

In fsm-update:
fsm.el:333:12: Warning: ‘destructuring-bind’ is an obsolete alias (as of
27.1); use ‘cl-destructuring-bind’ instead.

In fsm-send-sync:
fsm.el:374:30: Warning: ‘destructuring-bind’ is an obsolete alias (as of
27.1); use ‘cl-destructuring-bind’ instead.

In hexrgb-read-color:
hexrgb.el:349:14: Warning: ‘interactive-p’ is an obsolete function (as of
23.2); use ‘called-interactively-p’ instead.

In hexrgb-complement:
hexrgb.el:373:10: Warning: ‘interactive-p’ is an obsolete function (as of
23.2); use ‘called-interactively-p’ instead.

In hexrgb-hsv-to-rgb:
hexrgb.el:497:25: Warning: ‘case’ is an obsolete alias (as of 27.1); use
‘cl-case’ instead.

In end of data:
hexrgb.el:332:35: Warning: the function ‘eyedrop-background-at-mouse’ is not
known to be defined.
hexrgb.el:328:35: Warning: the function ‘eyedrop-foreground-at-mouse’ is not
known to be defined.
hexrgb.el:326:66: Warning: the function ‘eyedrop-background-at-point’ is not
known to be defined.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘return’ is an obsolete 
alias (as of 27.1); use ‘cl-return’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘loop’ is an obsolete 
alias (as of 27.1); use ‘cl-loop’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘loop’ is an obsolete 
alias (as of 27.1); use ‘cl-loop’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘return’ is an obsolete 
alias (as of 27.1); use ‘cl-return’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘case’ is an obsolete 
alias (as of 27.1); use ‘cl-case’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘return’ is an obsolete 
alias (as of 27.1); use ‘cl-return’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘destructuring-bind’ is 
an obsolete alias (as of 27.1); use ‘cl-destructuring-bind’ instead.
../../elpa-src/jabber-0.8.92/jabber-util.el: Warning: ‘do’ is an obsolete alias 
(as of 27.1); use ‘cl-do’ instead.
../../elpa-src/jabber-0.8.92/jabber-xml.el: Warning: ‘loop’ is an obsolete 
alias (as of 27.1); use ‘cl-loop’ instead.
../../elpa-src/jabber-0.8.92/jabber-xml.el: Warning: ‘return’ is an obsolete 
alias (as of 27.1); use ‘cl-return’ instead.

In toplevel form:
jabber-activity.el:42:1: Warning: Package tls is deprecated
jabber-activity.el:42:1: Warning: Package starttls is deprecated
../../elpa-src/jabber-0.8.92/srv.el: Warning: ‘incf’ is an obsolete alias (as 
of 27.1); use ‘cl-incf’ instead.
../../elpa-src/jabber-0.8.92/srv.el: Warning: ‘return’ is an obsolete alias (as 
of 27.1); use ‘cl-return’ instead.
../../elpa-src/jabber-0.8.92/jabber-conn.el: Warning: ‘labels’ is an obsolete 
macro (as of 24.3); use ‘cl-labels’ instead.
../../elpa-src/jabber-0.8.92/jabber-conn.el: Warning: ‘labels’ is an obsolete 
macro (as of 24.3); use ‘cl-labels’ instead.
../../elpa-src/jabber-0.8.92/jabber-conn.el: Warning: ‘case’ is an obsolete 
alias (as of 27.1); use ‘cl-case’ instead.
../../elpa-src/jabber-0.8.92/fsm.el: Warning: ‘destructuring-bind’ is an 
obsolete alias (as of 27.1); use ‘cl-destructuring-bind’ instead.
../../elpa-src/jabber-0.8.92/fsm.el: Warning: ‘loop’ is an obsolete alias (as 
of 27.1); use ‘cl-loop’ instead.
../../elpa-src/jabber-0.8.92/fsm.el: Warning: ‘destructuring-bind’ is an 
obsolete alias (as of 27.1); use ‘cl-destructuring-bind’ instead.
../../elpa-src/jabber-0.8.92/fsm.el: Warning: ‘destructuring-bind’ is an 
obsolete alias (as of 27.1); use ‘cl-destructuring-bind’ instead.
../../elpa-src/jabber-0.8.92/jabber-core.el: Warning: ‘destructuring-bind’ is 

Processed: tagging 1005719 ...

[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 
> https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1962721 
> https://github.com/mumble-voip/mumble/commit/02ddcf8c5dbd71e6e72c7ad81a6b66e62ea0fa6f
Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0
Set Bug forwarded-to-address to 
'https://patches.ubuntu.com/m/mumble/mumble_1.3.4-1ubuntu1.patch 
https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1962721 
https://github.com/mumble-voip/mumble/commit/02ddcf8c5dbd71e6e72c7ad81a6b66e62ea0fa6f'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1005719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1001661: notcurses: flaky autopkgtests on armhf

[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 until the
issue has been fixed.


For avoidance of doubt, I totally agree with you (I have already NMUed 
packages to only turn of tests). Maybe I should suggest that more often 
explicitly?


Paul


OpenPGP_signature
Description: OpenPGP digital signature