Processed: [Help] Re: Bug#1070839: r-cran-data.table: autopkgtest regression on i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1070839 [src:r-cran-data.table] r-cran-data.table: autopkgtest regression 
on i386
Added tag(s) help.

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

Bug#1070839: [Help] Re: Bug#1070839: r-cran-data.table: autopkgtest regression on i386

[Andreas Tille]

Control: tags -1 help

Hi Graham,

Am Fri, May 10, 2024 at 10:44:48AM + schrieb Graham Inggs:
> Source: r-cran-data.table
> Version: 1.15.4+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> r-cran-data.table's autopkgtest has regressed on i386 [1].  I've
> copied what I hope is the relevant part of the log below.
> 
> Regards
> Graham
> 
> [1] https://ci.debian.net/packages/r/r-cran-data.table/testing/i386/

I need help for this package which seems to be urgent and is blocking
some migrations.  I will not be able to do anything on this bug before
June.

Maybe the most straightforward way to tackle this is to simply remove
the one failing test?  Anyone is kindly invited to work on this /
contact upstream (or even remove the package and packages depending from
it for i386 / 32bit architectures).  The package is team maintained
and everybody can do a team upload.

Kind regards
Andreas.

-- 
https://fam-tille.de

Bug#1065722: FTBFS: /usr/lib/python3/dist-packages/torch/include/c10/util/C++17.h:27:2: error: #error You need C++17 to compile PyTorch

[Yadd]

Control: tags -1 + patch

Hi,

updating to 0.18 fixes the build issue: see 
https://salsa.debian.org/deeplearning-team/pytorch-vision/-/merge_requests/2


Best regards,
Xavier

Processed: Re: FTBFS: /usr/lib/python3/dist-packages/torch/include/c10/util/C++17.h:27:2: error: #error You need C++17 to compile PyTorch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1065722 [src:pytorch-vision] pytorch-vision: FTBFS: 
/usr/lib/python3/dist-packages/torch/include/c10/util/C++17.h:27:2: error: 
#error You need C++17 to compile PyTorch
Added tag(s) patch.

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

Bug#1070836: marked as done (rust-apple-nvram: Switch from rust-nix 0.26 to 0.27)

[Debian Bug Tracking System]

Your message dated Sat, 11 May 2024 01:19:40 +
with message-id 
and subject line Bug#1070836: fixed in rust-apple-nvram 0.2.0-3
has caused the Debian Bug report #1070836,
regarding rust-apple-nvram: Switch from rust-nix 0.26 to 0.27
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.)


-- 
1070836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-apple-nvram
Version: 0.2.0-1
Severity: serious
Tags: ftbfs upstream sid
X-Debbugs-CC: andr...@fatal.se

rust-apple-nvram Depends and Build-Depends: rust-nix 0.26 but Unstable
has rust-nix 0.27 instead. I tried doing a simple version bump from
0.26 to 0.27 in the package but dh_auto_test failed.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: rust-apple-nvram
Source-Version: 0.2.0-3
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-apple-nvram, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-apple-nvram 
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: Sat, 11 May 2024 00:37:42 +
Source: rust-apple-nvram
Architecture: source
Version: 0.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1070836
Changes:
 rust-apple-nvram (0.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Package apple-nvram 0.2.0 from crates.io using debcargo 2.6.1
   * Support nix 0.27 and 0.28 (Closes: #1070836)
 + Relax depedency on nix.
 + Explicitly enable ioctl feature in nix, which is no longer enabled by
   default.
Checksums-Sha1:
 9093ae5fee77a031fe68147f0bdca26cab48759b 2445 rust-apple-nvram_0.2.0-3.dsc
 f5be9a614e8079c7dc501c8a75b552259f34fcd2 2976 
rust-apple-nvram_0.2.0-3.debian.tar.xz
 2fa9083d4a3abe331299071314ac53331d828a9f 8557 
rust-apple-nvram_0.2.0-3_source.buildinfo
Checksums-Sha256:
 7563a34cb78d99b46d0a52da6429378d1de81f3cccfa69af9340edee450a4aa4 2445 
rust-apple-nvram_0.2.0-3.dsc
 8d5bcbce0001a7bad9f68b55c3213b2d49b8f7cfcb49d0e01dc06275e51e235f 2976 
rust-apple-nvram_0.2.0-3.debian.tar.xz
 c084a8a7ed565b2d63baf5ad2ec645daeb8483cc6820e6add0e4cbc5b92ebc35 8557 
rust-apple-nvram_0.2.0-3_source.buildinfo
Files:
 64eb7a58b3bbb038949b8d240632bdcb 2445 rust optional 
rust-apple-nvram_0.2.0-3.dsc
 31adcdf3bd546b3e4907682ea3b690b9 2976 rust optional 
rust-apple-nvram_0.2.0-3.debian.tar.xz
 ca318eb6945a65f79d78fe86d587b7c0 8557 rust optional 
rust-apple-nvram_0.2.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmY+whoUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuohQ//UKBHdx2eCdqCr8eIoiKruw2r9avx
NBzyut3Aaz2+G8ODdXhvBEdRqv8xyCR+dVYztjqtvGwrgG+sqPwTOPGkRDSuTbYb
sNBo/jsm1h22jW0xdl8j+n2+AljrLMps8UleLb3rj7aouZx4+2puJgyJVzjOxcZU
S2C0eJ5ZQ+conBmOmTheFGe5QyTS0rmBTslKfMz3EJ1lMVe8mS3S2hoLsw/nZlt8
/UmrJ/dWX777JudQQatws93IJBlXhINQ3RkzIAzAs+L/dIoIjW/3+fRv37dMPJ9+
j773yzNqO4JI347OKFh7J8rZlILxCJZ+/iT45YG/c6fdFZWwZT/f7bZXZTm0mEl7
g2gz9cbV9mw3ZRrwpY/PWNy1A2J90tjceuNaGCCeiAIMGBzHWdkW9GLM2XScT8f3
OjUVOh26A0z0hiNmdBIJbeBNX0xASvD7V/tKlALF7wZk3o37lfaL3uAJ7YZglK6X
0hrh6f5vhiuLhSpJf5xuNyA+DhS6SmG18kN8q3v5/exXV7LQrX7fywiWYp2oXkEL
+jNOmDYY+A7VPMWXihEEpFB5U0bXPArbmr6Smr/Ud0X8XIe0fd+cRdadDhsQClG9
ZUfweeouWTHjSysC7v4/GirS5O6H0vKQMfKylrALAzUlnxc18UzfgmVp/pQsVzrl
wLUJRimAKHabfZg=
=rIq8
-END PGP SIGNATURE-



pgpfJsILDunwd.pgp
Description: PGP signature
--- End Message ---

Bug#1070836: rust-apple-nvram: Switch from rust-nix 0.26 to 0.27

[peter green]

I got the following error when trying the same thing.
I have no idea why, since the ioctl_write_ptr and ioctl_read macros are
still supposed to be around. I can't spot any relevant change in nix
that would cause this to happen. Help would be appreciated.


The relavent change is.


All Cargo features have been removed from the default set. Users will
need to specify which features they depend on in their Cargo.toml.


I've bumped the dependency, added the feature, run the autopkgtest
and uploaded the package.

Bug#1070872: libm.a lost fmod + fmodf on i386 + m68k

[Adrian Bunk]

Package: libc6-dev
Version: 2.38-7
Severity: serious
Tags: ftbfs
Control: affects -1 src:zsh

https://buildd.debian.org/status/logs.php?pkg=zsh=5.9-6%2Bb1

...
gcc -static   -o zsh main.o  `cat stamp-modobjs`   -lpcre2-8 -lgdbm -lcap 
-lncursesw -ltinfo -ltinfo -lrt -lm  -lc
...
./obj-static/Src/../../Src/math.c:1260:(.text+0x1d8e): undefined reference to 
`fmod'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:228: zsh] Error 1



$ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod
w_fmodl_compat.o: file format elf32-i386
w_fmod_compat.o: file format elf32-i386
w_fmodf_compat.o: file format elf32-i386
e_fmodl.o: file format elf32-i386
 g F .text  0013 __ieee754_fmodl
w_fmodl.o: file format elf32-i386
 g F .text  0085 __fmodl
 *UND*   __ieee754_fmodl
  wF .text  0085 fmodf64x
  wF .text  0085 fmodl
e_fmod.o: file format elf32-i386
 g F .text  0013 __ieee754_fmod
w_fmod.o: file format elf32-i386
e_fmodf.o: file format elf32-i386
 g F .text  0013 __ieee754_fmodf
w_fmodf.o: file format elf32-i386
e_fmodf128.o: file format elf32-i386
 g F .text  0c9b __ieee754_fmodf128
 *UND*   __ieee754_fmodf128
 *UND*   __ieee754_fmodf128
w_fmodf128.o: file format elf32-i386
 g F .text  0237 __fmodf128
 *UND*   __ieee754_fmodf128
  wF .text  0237 fmodf128
$


With 2.37-13 this is instead:

$ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod
w_fmodl_compat.o: file format elf32-i386
w_fmod_compat.o: file format elf32-i386
w_fmodf_compat.o: file format elf32-i386
e_fmodl.o: file format elf32-i386
 g F .text  0013 __ieee754_fmodl
w_fmodl.o: file format elf32-i386
 g F .text  0085 __fmodl
 *UND*   __ieee754_fmodl
  wF .text  0085 fmodf64x
  wF .text  0085 fmodl
e_fmod.o: file format elf32-i386
 g F .text  0013 __ieee754_fmod
w_fmod.o: file format elf32-i386
 g F .text  006b __fmod
 *UND*   __ieee754_fmod
  wF .text  006b fmodf32x
  wF .text  006b fmodf64
  wF .text  006b fmod
e_fmodf.o: file format elf32-i386
 g F .text  0013 __ieee754_fmodf
w_fmodf.o: file format elf32-i386
 g F .text  0063 __fmodf
 *UND*   __ieee754_fmodf
  wF .text  0063 fmodf32
  wF .text  0063 fmodf
e_fmodf128.o: file format elf32-i386
 g F .text  0cc5 __ieee754_fmodf128
 *UND*   __ieee754_fmodf128
 *UND*   __ieee754_fmodf128
w_fmodf128.o: file format elf32-i386
 g F .text  0237 __fmodf128
 *UND*   __ieee754_fmodf128
  wF .text  0237 fmodf128
$

Processed: libm.a lost fmod + fmodf on i386 + m68k

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:zsh
Bug #1070872 [libc6-dev] libm.a lost fmod + fmodf on i386 + m68k
Added indication that 1070872 affects src:zsh

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

Bug#1069693: ppp >=2.5.0 breaks network-manager-fortisslvpn

[Maurizio Avogadro]

Some more info gathered this afternoon.

It seems that network-manager-fortisslvpn also makes a mess with the routing 
table after the connection has been established.


I could easily get a working VPN by adding

ipcp-accept-remote

to /etc/ppp/options and manually launching openfortivpn; such setting also 
allowed NetworkManager to accept the IP address supplied by the counterpart (it 
was the default until ppp v2.4.9), but in this case the connection didn't work 
until I deleted a rule in the routing table which routed the IP address of the 
remote gateway through the ppp0 interface (!).


A duplicate default route through the main physical network interface was 
created too and the spawned pppd process didn't exit after the connection has 
been terminated and had to be killed manually: none of these issues happened 
when openfortivpn was launched manually.


Thanks

Bug#1064486: marked as done (rnp: FTBFS: Errors while running CTest)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 22:25:40 +
with message-id 
and subject line Bug#1064486: fixed in rnp 0.17.1-1
has caused the Debian Bug report #1064486,
regarding rnp: FTBFS: Errors while running CTest
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.)


-- 
1064486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rnp
Version: 0.17.0-3
Severity: serious 

Dear Maintainer,

The package has a ftbfs issue on my local amd64 build:

```
260/260 Test #255: cli_tests-Encryption 
..   Passed   60.86 sec

98% tests passed, 6 tests failed out of 260

Total Test time (real) =  71.61 sec

The following tests FAILED:
 90 - rnp_tests.test_ffi_security_profile (Failed)
159 - rnp_tests.test_rnp_access (Failed)
166 - rnp_tests.rnpkeys_generatekey_verifykeyHomeDirNoPermission 
(Failed)
174 - rnp_tests.test_key_add_userid (Failed)
258 - cli_tests-EncryptElgamal (Failed)
259 - cli_tests-Misc (Failed)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
make[1]: Leaving directory '/<>/build'
dh_auto_test: error: cd build && make -j16 test ARGS\+=--verbose ARGS\+=-j16 
returned exit code 2
make: *** [debian/rules:33: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Build finished at 2024-02-22T22:48:30Z
```

It was failed on riscv64 also, but less test cases than amd64:

```
The following tests FAILED:
 90 - rnp_tests.test_ffi_security_profile (Failed)
174 - rnp_tests.test_key_add_userid (Failed)
251 - cli_tests-EncryptElgamal (Failed)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
```

The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=rnp=riscv64=0.17.0-3%2Bb2=1708576037=0


-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rnp
Source-Version: 0.17.1-1
Done: Daniel Kahn Gillmor 

We believe that the bug you reported is fixed in the latest version of
rnp, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated rnp 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: Fri, 10 May 2024 17:15:05 -0400
Source: rnp
Architecture: source
Version: 0.17.1-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Closes: 1064486 1065948
Changes:
 rnp (0.17.1-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #1064486)
   * Drop build-dep on python3-distutils (Closes: #1065948)
   * Stop shipping librnp.a, following upstream
   * Permit normal testing when gpg-from-sq is installed
   * debian/librnp0.symbols: add rnp_signature_get_features
   * move from pkg-config to pkgconf
   * fix manpage grammar
Checksums-Sha1:
 42f5bd8e99469c37df9d7472a1dd6f8a0453d3bd 1556 rnp_0.17.1-1.dsc
 198f095c229213a521298fad58abc33b246a320f 3515288 rnp_0.17.1.orig.tar.gz
 13b9a4f4177bb30e400f60fef09675ec158c090c 10268 rnp_0.17.1-1.debian.tar.xz
 b4b59e375e71c36f3849c86c51c1ecc037f52780 18190 rnp_0.17.1-1_amd64.buildinfo
Checksums-Sha256:
 33da2578bb71455212afcb7247badb18b1c96569b104ea015f93ddc64dd6b419 1556 
rnp_0.17.1-1.dsc
 ec486bb2c25abb0ddbd95973fd135e3922ea68b4e6919c7c18d992078baaf50c 3515288 
rnp_0.17.1.orig.tar.gz
 6157772a901bcbaae49f3fb03998af2e2cf03c155fc46b7fc16d7140c9be9e71 10268 
rnp_0.17.1-1.debian.tar.xz
 15c0ff5b2d9621e6385dc16f1e6849fdb355ad0e3842ce993ff123fadb7f9ab3 18190 
rnp_0.17.1-1_amd64.buildinfo
Files:
 761591b1920245b97cfb58aa4464b980 1556 utils optional rnp_0.17.1-1.dsc
 e29f0992969bbb71c2a1686399573c48 3515288 utils optional rnp_0.17.1.orig.tar.gz
 0377b64c7df66563acfc80e6db3c9c34 10268 utils optional 
rnp_0.17.1-1.debian.tar.xz
 528a9ccebae06d6d4c95adf246f5165f 18190 utils optional 
rnp_0.17.1-1_amd64.buildinfo

-BEGIN PGP 

Bug#1060976: marked as done (obs-downstream-keyer: FTBFS: downstream-keyer-dock.cpp:34:30: error: ‘void* obs_frontend_add_dock(void*)’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 21:21:01 +
with message-id 
and subject line Bug#1060976: fixed in obs-downstream-keyer 0.3.2-1
has caused the Debian Bug report #1060976,
regarding obs-downstream-keyer: FTBFS: downstream-keyer-dock.cpp:34:30: error: 
‘void* obs_frontend_add_dock(void*)’ is deprecated 
[-Werror=deprecated-declarations]
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.)


-- 
1060976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obs-downstream-keyer
Version: 0.2.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -Ddownstream_keyer_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/downstream-keyer_autogen/include 
> -isystem /usr/include/obs -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wextra -Wvla -Wformat 
> -Wformat-security -Wswitch -Wunused-parameter -Wno-unused-function 
> -Wno-missing-field-initializers -fno-strict-aliasing 
> -Werror-implicit-function-declaration -Wno-missing-braces -fPIC -mmmx -msse 
> -msse2 -MD -MT CMakeFiles/downstream-keyer.dir/output-source.c.o -MF 
> CMakeFiles/downstream-keyer.dir/output-source.c.o.d -o 
> CMakeFiles/downstream-keyer.dir/output-source.c.o -c 
> /<>/output-source.c
> /<>/downstream-keyer-dock.cpp: In function ‘bool 
> obs_module_load()’:
> /<>/downstream-keyer-dock.cpp:34:30: error: ‘void* 
> obs_frontend_add_dock(void*)’ is deprecated [-Werror=deprecated-declarations]
>34 | obs_frontend_add_dock(_dsk);
>   | ~^~
> In file included from /<>/downstream-keyer-dock.hpp:6,
>  from /<>/downstream-keyer-dock.cpp:1:
> /usr/include/obs/obs-frontend-api.h:142:14: note: declared here
>   142 | EXPORT void *obs_frontend_add_dock(void *dock);
>   |  ^
> cc1plus: all warnings being treated as errors
> make[3]: *** [CMakeFiles/downstream-keyer.dir/build.make:100: 
> CMakeFiles/downstream-keyer.dir/downstream-keyer-dock.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/obs-downstream-keyer_0.2.7-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=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 mark 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: obs-downstream-keyer
Source-Version: 0.3.2-1
Done: Joao Eriberto Mota Filho 

We believe that the bug you reported is fixed in the latest version of
obs-downstream-keyer, 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 1060...@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 
obs-downstream-keyer 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, 09 May 2024 09:04:48 -0300
Source: obs-downstream-keyer
Architecture: source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium

Bug#1060974: marked as done (obs-scene-notes-dock: FTBFS: scene-notes-dock.cpp:32:30: error: ‘void* obs_frontend_add_dock(void*)’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 21:21:09 +
with message-id 
and subject line Bug#1060974: fixed in obs-scene-notes-dock 0.2.0-3
has caused the Debian Bug report #1060974,
regarding obs-scene-notes-dock: FTBFS: scene-notes-dock.cpp:32:30: error: 
‘void* obs_frontend_add_dock(void*)’ is deprecated 
[-Werror=deprecated-declarations]
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.)


-- 
1060974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obs-scene-notes-dock
Version: 0.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -Dscene_notes_dock_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/scene-notes-dock_autogen/include 
> -isystem /usr/include/obs -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wextra -Wvla -Wformat 
> -Wformat-security -Wswitch -Wunused-parameter -Wno-unused-function 
> -Wno-missing-field-initializers -fno-strict-aliasing -Wconversion-null -fPIC 
> -mmmx -msse -msse2 -MD -MT 
> CMakeFiles/scene-notes-dock.dir/scene-notes-dock.cpp.o -MF 
> CMakeFiles/scene-notes-dock.dir/scene-notes-dock.cpp.o.d -o 
> CMakeFiles/scene-notes-dock.dir/scene-notes-dock.cpp.o -c 
> /<>/scene-notes-dock.cpp
> /<>/scene-notes-dock.cpp: In function ‘bool obs_module_load()’:
> /<>/scene-notes-dock.cpp:32:30: error: ‘void* 
> obs_frontend_add_dock(void*)’ is deprecated [-Werror=deprecated-declarations]
>32 | obs_frontend_add_dock(new SceneNotesDock(main_window));
>   | ~^
> In file included from /<>/scene-notes-dock.hpp:3,
>  from /<>/scene-notes-dock.cpp:1:
> /usr/include/obs/obs-frontend-api.h:142:14: note: declared here
>   142 | EXPORT void *obs_frontend_add_dock(void *dock);
>   |  ^
> cc1plus: all warnings being treated as errors
> make[3]: *** [CMakeFiles/scene-notes-dock.dir/build.make:100: 
> CMakeFiles/scene-notes-dock.dir/scene-notes-dock.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/obs-scene-notes-dock_0.2.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=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 mark 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: obs-scene-notes-dock
Source-Version: 0.2.0-3
Done: Joao Eriberto Mota Filho 

We believe that the bug you reported is fixed in the latest version of
obs-scene-notes-dock, 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 1060...@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 
obs-scene-notes-dock 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: Fri, 10 May 2024 16:37:16 -0300
Source: obs-scene-notes-dock
Architecture: source
Version: 0.2.0-3
Distribution: unstable
Urgency: medium

Processed: Re: Bug#1070853: strace: test failures on 32bit with 64bit time_t

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 strace: test failures on 32bit
Bug #1070853 [src:strace] strace: test failures on 32bit with 64bit time_t
Changed Bug title to 'strace: test failures on 32bit' from 'strace: test 
failures on 32bit with 64bit time_t'.

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

Bug#1070853: strace: test failures on 32bit with 64bit time_t

[Adrian Bunk]

Control: retitle -1 strace: test failures on 32bit

The tests also fail on i386, so do not seem to be related to time_t.

cu
Adrian

Bug#1062249: tagging 1046274, fixed 1062998 in 4.19.0-1.1~exp1, tagging 1062998, tagging 1062072 ...

[Micha Lenk]

Control: tags -1 = patch
Control: fixed -1 libchipcard/5.99.1beta-2
Control: close -1

The versions in the archive are already fixed. Nothing left to do. Closing...

Regards,
Micha

Processed: Re: tagging 1046274, fixed 1062998 in 4.19.0-1.1~exp1, tagging 1062998, tagging 1062072 ...

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = patch
Bug #1062249 [src:libchipcard] libchipcard: NMU diff for 64-bit time_t 
transition
Removed tag(s) experimental, sid, and trixie.
> fixed -1 libchipcard/5.99.1beta-2
Bug #1062249 [src:libchipcard] libchipcard: NMU diff for 64-bit time_t 
transition
Marked as fixed in versions libchipcard/5.99.1beta-2.
> close -1
Bug #1062249 [src:libchipcard] libchipcard: NMU diff for 64-bit time_t 
transition
Marked Bug as done

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

Bug#1070768: bpfcc: ftbfs on ppc64el

[Luca Boccassi]

On Fri, 10 May 2024 at 20:03, Nilesh Patra  wrote:
>
> Quoting Luca Boccassi:
> >  Source: bpfcc
> >  Version: 0.29.1+ds-1
> >  Severity: serious
> >  Tags: ftbfs
> >
> >  Hi,
> >
> >  bpfcc has been failing to build on ppc64el for a long time, and this is
> >  keeping it out of testing.
> >
> >  If you don't have time to fix it, could you please consider at least a
> >  quick upload to remove ppc64el from the list of architectures, so that
> >  it can go back to testing?
> >
> >  Thanks!
> >
>
> Vasudev, Ritesh, this bug is causing a bunch of packages getting removed from
> testing (bpfcc and transitive reverse depends). Can I ask you to please take
> care of this, maybe dropping ppc64el altogether if it is not feasible to fix?

Unless there are objections, I am going to NMU to delayed/3 tomorrow
to remove ppc64el

Bug#1070768: bpfcc: ftbfs on ppc64el

[Nilesh Patra]

Quoting Luca Boccassi:
>  Source: bpfcc
>  Version: 0.29.1+ds-1
>  Severity: serious
>  Tags: ftbfs
>  
>  Hi,
>  
>  bpfcc has been failing to build on ppc64el for a long time, and this is
>  keeping it out of testing.
>  
>  If you don't have time to fix it, could you please consider at least a
>  quick upload to remove ppc64el from the list of architectures, so that
>  it can go back to testing?
>  
>  Thanks!
>  

Vasudev, Ritesh, this bug is causing a bunch of packages getting removed from
testing (bpfcc and transitive reverse depends). Can I ask you to please take
care of this, maybe dropping ppc64el altogether if it is not feasible to fix?

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: tagging 1070858, tagging 1070859, tagging 1070860, tagging 1070861

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1070858 + upstream
Bug #1070858 [src:golang-github-opencontainers-go-digest] 
golang-github-opencontainers-go-digest: CVE-2024-3727
Added tag(s) upstream.
> tags 1070859 + upstream
Bug #1070859 [src:npgsql] npgsql: CVE-2024-32655
Added tag(s) upstream.
> tags 1070860 + upstream
Bug #1070860 [src:musescore3] musescore3: CVE-2023-44428
Ignoring request to alter tags of bug #1070860 to the same tags previously set
> tags 1070861 + upstream
Bug #1070861 [src:hdf5] hdf5: CVE-2024-33877 CVE-2024-33876 CVE-2024-33875 
CVE-2024-33874 CVE-2024-33873 CVE-2024-32624 CVE-2024-32623 CVE-2024-32622 
CVE-2024-32621 CVE-2024-32620 CVE-2024-32619 CVE-2024-32618 CVE-2024-32617 
CVE-2024-32616 CVE-2024-32615 CVE-2024-32614 CVE-2024-32613 CVE-2024-32612 
CVE-2024-32611 CVE-2024-32610 CVE-2024-32609 CVE-2024-32607 CVE-2024-32606 
CVE-2024-32605 CVE-2024-29166 CVE-2024-29165 CVE-2024-29164 CVE-2024-29163 
CVE-2024-29162 CVE-2024-29161 CVE-2024-29160 CVE-2024-29159 CVE-2024-29158 
CVE-2024-29157
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1070865: webkit2gtk/experimental FTBFS on big endian

[Adrian Bunk]

Source: webkit2gtk
Version: 2.45.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=webkit2gtk=2.45.1-1

...
In file included from 
/<>/Source/ThirdParty/skia/include/private/base/SkAPI.h:11,
 from 
/<>/Source/ThirdParty/skia/include/private/base/SkAssert.h:11,
 from 
/<>/Source/ThirdParty/skia/src/base/SkArenaAlloc.h:11,
 from 
/<>/Source/ThirdParty/skia/src/base/SkArenaAlloc.cpp:8:
/<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:57:6:
 error: #error "The Skia team is not endian-savvy enough to support big-endian 
CPUs."
   57 | #error "The Skia team is not endian-savvy enough to support 
big-endian CPUs."
  |  ^
/<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:58:6:
 error: #error "If you still want to use Skia,"
   58 | #error "If you still want to use Skia,"
  |  ^
/<>/Source/ThirdParty/skia/include/private/base/SkLoadUserConfig.h:59:6:
 error: #error "please define I_ACKNOWLEDGE_SKIA_DOES_NOT_SUPPORT_BIG_ENDIAN."
   59 | #error "please define 
I_ACKNOWLEDGE_SKIA_DOES_NOT_SUPPORT_BIG_ENDIAN."
  |  ^
...

Bug#1070862: marked as done (poppler: possibly unintended revert of t64 renames for non-main library in 24.x)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 18:35:38 +
with message-id 
and subject line Bug#1070862: fixed in poppler 24.02.0-3
has caused the Debian Bug report #1070862,
regarding poppler: possibly unintended revert of t64 renames for non-main 
library in 24.x
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.)


-- 
1070862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 24.02.0-1
Severity: important
X-Debbugs-Cc: po...@debian.org, jeremy.bi...@canonical.com

Attempting to summarize recent discussion with _rene_ on #debian-devel:

poppler in trixie builds these libraries:

- libpoppler126t64
- libpoppler-glib8t64
- libpoppler-qt5-1t64
- libpoppler-qt6-3t64
- libpoppler-cpp0t64

It is not obvious to me whether the -glib, -qt, -cpp libraries genuinely
broke their ABIs during the time64 transition, or whether they were only
renamed out of an abundance of caution.

poppler in experimental and (since today) unstable builds these libraries:

- libpoppler134
- libpoppler-glib8
- libpoppler-qt5-1
- libpoppler-qt6-3
- libpoppler-cpp0v5

In other words, it correctly drops the t64 suffix from the main libpoppler
across a SONAME bump, but it also reverts the renaming of the -glib,
-qt, -cpp libraries.

Was this intentional?

If the higher-level libraries never actually broke their ABI, then renaming
them back to their Debian 12 names might be OK, but they're probably going
to need versioned Breaks/Replaces on their ...t64 names.

If the higher-level libraries *did* break their ABI, then they need to
keep the new t64 names.

Please bump this up to RC if analysis shows that it is a genuine problem,
or close it if analysis shows that I'm being overly cautious.

smcv
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 24.02.0-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
poppler, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated poppler 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: Fri, 10 May 2024 14:18:27 -0400
Source: poppler
Built-For-Profiles: noudeb
Architecture: source
Version: 24.02.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Jeremy Bícha 
Closes: 1070862
Changes:
 poppler (24.02.0-3) unstable; urgency=medium
 .
   * Team upload
   * Restore t64 changes from 22.12.0-2.2 and bump Breaks/Replaces.
 Use standard versioned Replaces instead of unversioned. (Closes: #1070862)
Checksums-Sha1:
 fa8a6f404dbaad5d713b7da8e76706e043cac954 3500 poppler_24.02.0-3.dsc
 f4fa3ac2a45818f119daccd0e087bc34e77ca9a4 38096 poppler_24.02.0-3.debian.tar.xz
 a18998aacdece78b57c654dab1283857f4292d85 17633 
poppler_24.02.0-3_source.buildinfo
Checksums-Sha256:
 5c997ea54f5540cbc8caa10edcebd87e14769f8156431d7253c81d4fa0b00818 3500 
poppler_24.02.0-3.dsc
 08c7cb69db03dd4bab3a42481aee6a2fe237657f8def3f5a29426d69eceda4f1 38096 
poppler_24.02.0-3.debian.tar.xz
 1da21e8c8f12e04f55071c8b5d3212318c43fadb9693443b4b2f0127620597ed 17633 
poppler_24.02.0-3_source.buildinfo
Files:
 87d95c0c77261a109327634938a216e9 3500 devel optional poppler_24.02.0-3.dsc
 adedc8e1c158a892fc86861303a76d8f 38096 devel optional 
poppler_24.02.0-3.debian.tar.xz
 f3456b5470d71e0ac49dba8d4f6a0703 17633 devel optional 
poppler_24.02.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmY+ZwYACgkQ5mx3Wuv+
bH2+IBAAsM1UIftNK/A6+ccGXEmqPtdIZeuwztulv6jN5god3yBiBY0r8VAuU/IY
w+GO4EAvcs0/SojTGOVPB7l28T8CRWVEMukDHU4t5ePV3/F5y7XeZBabaVJeFKlB
Iervr5iMVoSkYGNeSvLdE+uR//TpKfmXB2ykoWIX+1nhtb7Nj4aTR1Ry2Ve/LThK
6ENknVFP0vQ9hG7R58jMASUoROeVOtsHXtDgyS3H92c4hCOicBUW2VlYs6TbU9m9
joKFuZeAVJ29fNtx8ovQrbD0OPTpCkFVQvVJOQqZ4B4EoUsoRhXv739PObkmol2M
vKoP4aUNhWw26Iz8Np5/An/NYg/T0bDz0qRUAp78XsZ2L8biGQmxuu2seGGybipD
R499yzANIb8/AumXjf/EpAoC1SzKbPxsC2d2IJpW0eZFP+PPIB80o/fZgM83VOjU
9m0nac3NTzp3YzGV/xRecKXkFEWdm455FE32IGbPhHmX/AQRoLR89oWiY77tLijC

Bug#1070862: and this looses files

[Rene Engelhard]

severity 1070862 serious
thanks

Hi,

this is even worse. It looses  the library file for the "non-main" 
libraries after cleanup:


Clean testing chroot.

# apt install libpoppler-dev libpoppler-cpp-dev
[...]

# apt update
# apt dist-upgrade
The following packages were automatically installed and are no longer 
required:

  libpoppler-cpp0t64 libpoppler126t64
Use 'sudo apt autoremove' to remove them.

Upgrading:
  gcc-14-base libaudit-common libc-bin libgcc-s1 libncursesw6 
libpoppler-dev libslang2  libtinfo6 nano ncurses-bin
  kmodlibaudit1   libc6libkmod2  libpoppler-cpp-dev 
libsharpyuv0   libstdc++6 libwebp7  ncurses-base zlib1g


Installing dependencies:
  ca-certificateslibldap-2.5-0  libnghttp2-14 libpoppler134 
librtmp1   libsasl2-moduleslibssh2-1t64 publicsuffix
  libcurl3t64-gnutls libldap-common libpoppler-cpp0v5 libpsl5t64 
libsasl2-2 libsasl2-modules-db openssl


Suggested packages:
  libsasl2-modules-gssapi-mit | libsasl2-modules-gssapi-heimdal 
libsasl2-modules-ldap libsasl2-modules-otp libsasl2-modules-sql


Summary:
  Upgrading: 20, Installing: 15, Removing: 0, Not Upgrading: 0
  Download size: 11.3 MB
  Space needed: 10.1 MB / 133 GB available

Continue? [Y/n]
Get:1 http://deb.debian.org/debian sid/main amd64 ncurses-bin amd64 
6.5-2 [433 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 gcc-14-base amd64 
14-20240429-1 [43.9 kB]
Get:3 http://deb.debian.org/debian sid/main amd64 libgcc-s1 amd64 
14-20240429-1 [72.4 kB]
Get:4 http://deb.debian.org/debian sid/main amd64 libstdc++6 amd64 
14-20240429-1 [715 kB]
Get:5 http://deb.debian.org/debian sid/main amd64 libc6 amd64 2.38-8 
[2771 kB]
Get:6 http://deb.debian.org/debian sid/main amd64 libc-bin amd64 2.38-8 
[610 kB]
Get:7 http://deb.debian.org/debian sid/main amd64 ncurses-base all 6.5-2 
[270 kB]
Get:8 http://deb.debian.org/debian sid/main amd64 libaudit-common all 
1:3.1.2-2.1 [11.4 kB]
Get:9 http://deb.debian.org/debian sid/main amd64 libaudit1 amd64 
1:3.1.2-2.1 [48.5 kB]
Get:10 http://deb.debian.org/debian sid/main amd64 libncursesw6 amd64 
6.5-2 [135 kB]
Get:11 http://deb.debian.org/debian sid/main amd64 libtinfo6 amd64 6.5-2 
[344 kB]
Get:12 http://deb.debian.org/debian sid/main amd64 zlib1g amd64 
1:1.3.dfsg+really1.3.1-1 [87.9 kB]

Get:13 http://deb.debian.org/debian sid/main amd64 kmod amd64 32-1 [95.7 kB]
Get:14 http://deb.debian.org/debian sid/main amd64 libkmod2 amd64 32-1 
[60.1 kB]

Get:15 http://deb.debian.org/debian sid/main amd64 nano amd64 8.0-1 [659 kB]
Get:16 http://deb.debian.org/debian sid/main amd64 openssl amd64 3.2.1-3 
[1360 kB]
Get:17 http://deb.debian.org/debian sid/main amd64 ca-certificates all 
20240203 [158 kB]
Get:18 http://deb.debian.org/debian sid/main amd64 libsasl2-modules-db 
amd64 2.1.28+dfsg1-6 [19.5 kB]
Get:19 http://deb.debian.org/debian sid/main amd64 libsasl2-2 amd64 
2.1.28+dfsg1-6 [56.9 kB]
Get:20 http://deb.debian.org/debian sid/main amd64 libldap-2.5-0 amd64 
2.5.17+dfsg-1 [186 kB]
Get:21 http://deb.debian.org/debian sid/main amd64 libnghttp2-14 amd64 
1.61.0-1+b1 [75.6 kB]
Get:22 http://deb.debian.org/debian sid/main amd64 libpsl5t64 amd64 
0.21.2-1.1 [56.8 kB]
Get:23 http://deb.debian.org/debian sid/main amd64 librtmp1 amd64 
2.4+20151223.gitfa8646d.1-2+b4 [58.5 kB]
Get:24 http://deb.debian.org/debian sid/main amd64 libssh2-1t64 amd64 
1.11.0-4.1+b2 [215 kB]
Get:25 http://deb.debian.org/debian sid/main amd64 libcurl3t64-gnutls 
amd64 8.7.1-5 [433 kB]
Get:26 http://deb.debian.org/debian sid/main amd64 libldap-common all 
2.5.17+dfsg-1 [31.5 kB]
Get:27 http://deb.debian.org/debian sid/main amd64 libpoppler134 amd64 
24.02.0-2 [1029 kB]
Get:28 http://deb.debian.org/debian sid/main amd64 libpoppler-cpp0v5 
amd64 24.02.0-2 [41.3 kB]
Get:29 http://deb.debian.org/debian sid/main amd64 libpoppler-cpp-dev 
amd64 24.02.0-2 [14.7 kB]
Get:30 http://deb.debian.org/debian sid/main amd64 libpoppler-dev amd64 
24.02.0-2 [8080 B]
Get:31 http://deb.debian.org/debian sid/main amd64 libsasl2-modules 
amd64 2.1.28+dfsg1-6 [66.0 kB]
Get:32 http://deb.debian.org/debian sid/main amd64 libsharpyuv0 amd64 
1.4.0-0.1 [113 kB]
Get:33 http://deb.debian.org/debian sid/main amd64 libslang2 amd64 
2.3.3-5 [551 kB]
Get:34 http://deb.debian.org/debian sid/main amd64 libwebp7 amd64 
1.4.0-0.1 [311 kB]
Get:35 http://deb.debian.org/debian sid/main amd64 publicsuffix all 
20231001.0357-0.1 [125 kB]

Fetched 11.3 MB in 2s (6218 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "de_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Extracting templates from packages: 100%
Preconfiguring 

Processed: and this looses files

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1070862 serious
Bug #1070862 [src:poppler] poppler: possibly unintended revert of t64 renames 
for non-main library in 24.x
Ignoring request to change severity of Bug 1070862 to the same value.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1070862: poppler: possibly unintended revert of t64 renames for non-main library in 24.x

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1070862 [src:poppler] poppler: possibly unintended revert of t64 renames 
for non-main library in 24.x
Severity set to 'serious' from 'important'

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

Bug#1070859: npgsql: CVE-2024-32655

[Moritz Mühlenhoff]

Source: npgsql
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for npgsql.

CVE-2024-32655[0]:
| Npgsql is the .NET data provider for PostgreSQL. The `WriteBind()`
| method in `src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs`
| uses `int` variables to store the message length and the sum of
| parameter lengths. Both variables overflow when the sum of parameter
| lengths becomes too large. This causes Npgsql to write a message
| size that is too small when constructing a Postgres protocol message
| to send it over the network to the database. When parsing the
| message, the database will only read a small number of bytes and
| treat any following bytes as new messages while they belong to the
| old message. Attackers can abuse this to inject arbitrary Postgres
| protocol messages into the connection, leading to the execution of
| arbitrary SQL statements on the application's behalf. This
| vulnerability is fixed in 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7, and
| 8.0.3.

https://github.com/npgsql/npgsql/security/advisories/GHSA-x9vc-6hfv-hg8c
https://github.com/npgsql/npgsql/commit/f7e7ead0702d776a8f551f5786c4cac2d65c4bc6


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-32655
https://www.cve.org/CVERecord?id=CVE-2024-32655

Please adjust the affected versions in the BTS as needed.

Bug#1070515: marked as done (dipy: FTBFS with nocheck profile)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 17:19:24 +
with message-id 
and subject line Bug#1070515: fixed in dipy 1.9.0-2
has caused the Debian Bug report #1070515,
regarding dipy: FTBFS with nocheck profile
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.)


-- 
1070515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 1.8.0-2
Severity: serious
Tags: ftbfs patch

Hi Maintainer

dipy FTBFS when built with the 'nocheck' profile.  I've copied what I
hope is the relevant part of the log below.

The following patch worked for me:

--- a/debian/rules
+++ b/debian/rules
@@ -111,11 +111,11 @@
  ; done
 endif
  # Cleanup files landing unnecessarily in the python3 modules directory.
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk
- rm -v debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.nii.gz
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/*.trk
+ rm -fv debian/$(PACKAGE3_NAME)/usr/lib/python3*/dist-packages/affine.txt
  # Cleanup files landing in non-standard path
- rm -rv debian/$(PACKAGE3_NAME)/usr/doc
+ rm -rfv debian/$(PACKAGE3_NAME)/usr/doc

 ## "Instantiate" both rules so dh sees them
 override_dh_python3:
@@ -136,9 +136,9 @@
  -X.par -X.bin -Xobjects.inv

 execute_before_dh_link-indep:
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js
- rm -v 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/doctools.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/language_data.js
+ rm -fv 
debian/python-dipy-doc/usr/share/doc/python-dipy-doc/html/_static/searchtools.js

 execute_after_dh_fixperms-arch:
  # Fix a couple of executables neither elf nor scripts.

Regards
Graham


find debian/ -name LICENSE -delete
# Only now lets build docs
# Run tests later on
# cd build to prevent use of local/not-built source tree
# Cleanup files landing unnecessarily in the python3 modules directory.
rm -v debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz
rm: cannot remove
'debian/python3-dipy/usr/lib/python3*/dist-packages/*.nii.gz': No such
file or directory
make[1]: *** [debian/rules:81: execute_after_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: dipy
Source-Version: 1.9.0-2
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated dipy 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: Fri, 10 May 2024 19:12:08 +0200
Source: dipy
Architecture: source
Version: 1.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 1068146 1070515
Changes:
 dipy (1.9.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Graham Inggs ]
   * Fix FTBFS when built with the 'nocheck' profile
 Closes: #1070515
 .
   [ Andreas Tille ]
   * Standards-Version: 4.7.0 (routine-update)
 .
   [ Étienne Mollier ]
   * d/control: python3-nibabel is also needed for the doc.
 .
   [ Michael R. Crusoe ]
   * d/control: h5py, trx, and tqdm are also required to build the docs.
   * Added test patch to fix pytest module-level setup. Closes: #1068146
   * Standards-Version: 4.6.2 (routine-update)
   * d/control: remove obsolete "XB-Python3-Version" field.
Checksums-Sha1:
 3849ca2da5f1f5facb8784b274e0403b3010ae94 2947 dipy_1.9.0-2.dsc
 c5bc0c8838807926b7d47738fb644d378447897b 16400 dipy_1.9.0-2.debian.tar.xz
 db375e44351860475523046670d84ad32925d0c4 11395 dipy_1.9.0-2_source.buildinfo
Checksums-Sha256:
 

Bug#1068146: marked as done (FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 17:19:24 +
with message-id 
and subject line Bug#1068146: fixed in dipy 1.9.0-2
has caused the Debian Bug report #1068146,
regarding FTBFS: tests failed
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.)


-- 
1068146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 1.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dipy=armel=1.9.0-1=1711658317=0

=== short test summary info

FAILED dipy/reconst/tests/test_shore.py::test_shore_fitting_no_constrain_e0
FAILED dipy/viz/tests/test_util.py::test_check_img_shapes -
numpy.core._excep...


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: dipy
Source-Version: 1.9.0-2
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated dipy 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: Fri, 10 May 2024 19:12:08 +0200
Source: dipy
Architecture: source
Version: 1.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 1068146 1070515
Changes:
 dipy (1.9.0-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Graham Inggs ]
   * Fix FTBFS when built with the 'nocheck' profile
 Closes: #1070515
 .
   [ Andreas Tille ]
   * Standards-Version: 4.7.0 (routine-update)
 .
   [ Étienne Mollier ]
   * d/control: python3-nibabel is also needed for the doc.
 .
   [ Michael R. Crusoe ]
   * d/control: h5py, trx, and tqdm are also required to build the docs.
   * Added test patch to fix pytest module-level setup. Closes: #1068146
   * Standards-Version: 4.6.2 (routine-update)
   * d/control: remove obsolete "XB-Python3-Version" field.
Checksums-Sha1:
 3849ca2da5f1f5facb8784b274e0403b3010ae94 2947 dipy_1.9.0-2.dsc
 c5bc0c8838807926b7d47738fb644d378447897b 16400 dipy_1.9.0-2.debian.tar.xz
 db375e44351860475523046670d84ad32925d0c4 11395 dipy_1.9.0-2_source.buildinfo
Checksums-Sha256:
 6e1265f57b87de43dda0cd89cf5ac34baf02736e66a311d05a97d4ed5b9d5ee8 2947 
dipy_1.9.0-2.dsc
 fdc622b2b1221df71af911e6586b5cb8d1349a85611a5becbbdca812d657d93c 16400 
dipy_1.9.0-2.debian.tar.xz
 441b44eaeb214162b02e595633a51d414bc893f66dc1c504f8e9e7da29b29ad8 11395 
dipy_1.9.0-2_source.buildinfo
Files:
 16123a45e067fe14dea3ab3baf7121ba 2947 python optional dipy_1.9.0-2.dsc
 e717e68da7f21157c2cae9bb8c2f8980 16400 python optional 
dipy_1.9.0-2.debian.tar.xz
 ef836591914e06cddc1dae35f81ce921 11395 python optional 
dipy_1.9.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmY+Vd4ACgkQPCZ2P2xn
5uJgGhAAy22ZyWXQPO+7z1P8QpA2RrpctTlSOA6H9eUFcEFXgIWM1W70rV3Ek+y6
Gz/u7K/F4vl/1u5dx1px9cVW2YPk/Qhrc7Eg6yYXSszDtBOHrxhApVt6XxLTSREY
LPQY3wS9UrbUwuFaq/aOHFJOgc6XKWUbPu2/nUA8xCW6T8UP4QtUKoldCYNWjTFF
HDbcYAwMMHVsmpmKijWw2Sp3tywhtShYWnxCXYKHxqKwXHU8L4O4DZzSJ0DbR/m7
dXUZk1Uljq8qNKZdqb1uInIIEMcE/tYDUL+s7tkXahSQLWaeAtpI7Z1Ye2VNengV
A88isU3szMzcYZlnKJxwg8d0VuCqbw6Fsf0bYRW8f8D9VJ9buKvSH+Fge3MKymPa
p6frPRGnkhe+LEeYxEg21Rt07Q/8bpdzDdWUh8ir03NpwZVdc5Ou+66L1MagoNUb
CMZx/41HMjneijBgrjQz2Xu3HttZWs0N0TBpLSPYfJWVgB2o3Kb/jh6+1NLSxawU
EmbzJVQ7rKmDB94olxfws6R8ppH/q8Dj1oRMAm7OcVkeBTLaCqoyxDhHIANWEdLd

Bug#1070857: nix: FTBFS: /usr/bin/ld: cannot find src/libutil/tests/libnixutil-tests.a: No such file or directory

[Santiago Vila]

As promised, here is the patch.

Note: I have actually tested it, and it fixed the build failure for me.
(Thanks to Sergei Trofimovich who helped me to find the fix in the git repo)

Thanks.commit e1cc73faee68409dfdac07a39dca517813a40e2c
Author: Santiago Vila 
Date:   Fri May 10 14:45:00 2024 +0200

Cherry-pick two upstream patches to fix makefile bug. Closes: #1070857.

diff --git a/debian/patches/0013-fix-makefile-bug.patch 
b/debian/patches/0013-fix-makefile-bug.patch
new file mode 100644
index 0..3765db1ec
--- /dev/null
+++ b/debian/patches/0013-fix-makefile-bug.patch
@@ -0,0 +1,22 @@
+From: John Ericson 
+Date: Tue Nov 14 11:42:25 2023 -0500
+Subject: Fix makefile bug confusing `libnixutil-test` exe vs lib
+Bug-Debian: https://bugs.debian.org/1070857
+Origin: upstream, 
https://github.com/NixOS/nix/commit/9c7749e13508996eb9df83b1692664cc8cdbf952
+Forwarded: not-needed
+Last-Update: 2024-05-10
+
+The `-exe` variant is the program, the unsuffixed variant is the library.
+
+The corrected usage matches `libnixstore-test`.
+
+--- a/src/libutil/tests/local.mk
 b/src/libutil/tests/local.mk
+@@ -1,6 +1,6 @@
+ check: libutil-tests_RUN
+ 
+-programs += libutil-tests
++programs += libutil-tests-exe
+ 
+ libutil-tests-exe_NAME = libnixutil-tests
+ 
diff --git a/debian/patches/0014-fix-make-check.patch 
b/debian/patches/0014-fix-make-check.patch
new file mode 100644
index 0..f96519e34
--- /dev/null
+++ b/debian/patches/0014-fix-make-check.patch
@@ -0,0 +1,19 @@
+From: John Ericson 
+Date: Fri Nov 17 11:26:45 2023 -0500
+Subject: Fix `make check`
+Bug-Debian: https://bugs.debian.org/1070857
+Origin: upstream, 
https://github.com/NixOS/nix/commit/293ae592576bb9c48975466613fcba6a30d06f5e
+Forwarded: not-needed
+Last-Update: 2024-05-10
+
+After 9c7749e13508996eb9df83b1692664cc8cdbf952, `libutil-tests_RUN`
+doesn't exist. It needs to become `libutil-tests-exe_RUN`.
+
+--- a/src/libutil/tests/local.mk
 b/src/libutil/tests/local.mk
+@@ -1,4 +1,4 @@
+-check: libutil-tests_RUN
++check: libutil-tests-exe_RUN
+ 
+ programs += libutil-tests-exe
+ 
diff --git a/debian/patches/series b/debian/patches/series
index ef37b55cc..cd4bc73d9 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -10,3 +10,5 @@
 0010-libexpr-Add-various-files-to-clean-files.patch
 0011-manual-Add-various-files-to-clean-files.patch
 0012-nix-Add-various-files-to-clean-files.patch
+0013-fix-makefile-bug.patch
+0014-fix-make-check.patch

Bug#1070836: rust-apple-nvram: Switch from rust-nix 0.26 to 0.27

[Andreas Henriksson]

Hello Jeremy Bicha,

Thanks for explicitly CCing me on this. See below. There's no urgency to
fix this as the relevant rdeps are still stuck in NEW (for 6+ months).

On Fri, May 10, 2024 at 05:31:54AM -0400, Jeremy Bícha wrote:
> Source: rust-apple-nvram
> Version: 0.2.0-1
> Severity: serious
> Tags: ftbfs upstream sid
> X-Debbugs-CC: andr...@fatal.se
> 
> rust-apple-nvram Depends and Build-Depends: rust-nix 0.26 but Unstable
> has rust-nix 0.27 instead. I tried doing a simple version bump from
> 0.26 to 0.27 in the package but dh_auto_test failed.
> 
> Thank you,
> Jeremy Bícha

I got the following error when trying the same thing.
I have no idea why, since the ioctl_write_ptr and ioctl_read macros are
still supposed to be around. I can't spot any relevant change in nix
that would cause this to happen. Help would be appreciated.

```
error[E0433]: failed to resolve: could not find `ioctl_write_ptr` in `nix`
  --> src/mtd.rs:50:6
   |
50 | nix::ioctl_write_ptr!(mtd_mem_erase, b'M', 2, EraseInfoUser);
   |  ^^^ could not find `ioctl_write_ptr` in `nix`

error[E0433]: failed to resolve: could not find `ioctl_read` in `nix`
  --> src/mtd.rs:51:6
   |
51 | nix::ioctl_read!(mtd_mem_get_info, b'M', 1, MtdInfoUser);
   |  ^^ could not find `ioctl_read` in `nix`

error[E0425]: cannot find function `mtd_mem_get_info` in this scope
  --> src/mtd.rs:54:17
   |
54 | if unsafe { mtd_mem_get_info(file.as_raw_fd(),  
MtdInfoUser::default()) }.is_err() {
   |  not found in this scope

error[E0425]: cannot find function `mtd_mem_erase` in this scope
  --> src/mtd.rs:62:9
   |
62 | mtd_mem_erase(file.as_raw_fd(), _info).unwrap();
   | ^ not found in this scope

Some errors have detailed explanations: E0425, E0433.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `apple-nvram` (lib test) due to 4 previous errors
```

Regards,
Andreas Henriksson

Bug#1070857: nix: FTBFS: /usr/bin/ld: cannot find src/libutil/tests/libnixutil-tests.a: No such file or directory

[Santiago Vila]

Package: src:nix
Version: 2.18.1+dfsg-1
Severity: serious
Tags: ftbfs fixed-upstream patch

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
g++ -o src/libstore/tests/nar-info-disk-cache.o -c src/libstore/tests/nar-info-disk-cache.cc 
-Wdate-time -D_FORTIFY_SOURCE=2  -fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3  -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-Wno-deprecated-declarations -Werror=switch -g -Wall -include config.h -std=c++2a -I src 
-I/usr/include/x86_64-linux-gnu -I/usr/include/libcpuid -DREADLINE -I/usr/include/x86_64-linux-gnu 
-DLIBARCHIVE_STATIC -I/usr/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I 
src/libstore -I src/libutil -Werror=switch-enum -MMD -MF src/libstore/tests/.nar-info-disk-cache.o.dep 
-MP
g++ -o src/libstore/tests/outputs-spec.o -c src/libstore/tests/outputs-spec.cc -Wdate-time 
-D_FORTIFY_SOURCE=2  -fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3  -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-Wno-deprecated-declarations -Werror=switch -g -Wall -include config.h -std=c++2a -I src 
-I/usr/include/x86_64-linux-gnu -I/usr/include/libcpuid -DREADLINE -I/usr/include/x86_64-linux-gnu 
-DLIBARCHIVE_STATIC -I/usr/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I 
src/libstore -I src/libutil -Werror=switch-enum -MMD -MF src/libstore/tests/.outputs-spec.o.dep -MP
g++ -o src/libstore/tests/path.o -c src/libstore/tests/path.cc -Wdate-time -D_FORTIFY_SOURCE=2  
-fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3  -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-Wno-deprecated-declarations -Werror=switch -g -Wall -include config.h -std=c++2a -I src 
-I/usr/include/x86_64-linux-gnu -I/usr/include/libcpuid -DREADLINE -I/usr/include/x86_64-linux-gnu 
-DLIBARCHIVE_STATIC -I/usr/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I 
src/libstore -I src/libutil -Werror=switch-enum -MMD -MF src/libstore/tests/.path.o.dep -MP
g++ -o src/libstore/tests/references.o -c src/libstore/tests/references.cc -Wdate-time 
-D_FORTIFY_SOURCE=2  -fstack-protector-strong -Wformat -Werror=format-security 
-ffile-prefix-map=/<>=. -O3  -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-Wno-deprecated-declarations -Werror=switch -g -Wall -include config.h -std=c++2a -I src 
-I/usr/include/x86_64-linux-gnu -I/usr/include/libcpuid -DREADLINE -I/usr/include/x86_64-linux-gnu 
-DLIBARCHIVE_STATIC -I/usr/include -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I 
src/libstore -I src/libutil -Werror=switch-enum -MMD -MF src/libstore/tests/.references.o.dep -MP
ld  -r -o tests/test-libstoreconsumer/libnixstore-tests.o 
src/libstore/tests/derivation.o src/libstore/tests/derived-path.o 
src/libstore/tests/downstream-placeholder.o src/libstore/tests/machines.o 
src/libstore/tests/nar-info-disk-cache.o src/libstore/tests/outputs-spec.o 
src/libstore/tests/path.o src/libstore/tests/references.o
ar crs src/libstore/tests/libnixstore-tests.a 
tests/test-libstoreconsumer/libnixstore-tests.o
g++ -o src/libstore/tests/libnixstore-tests -L/usr/lib/x86_64-linux-gnu 
-Wl,-z,relro -Wl,-z,now  -L/usr/lib/x86_64-linux-gnu -Wl,-z,relro -Wl,-z,now  
-lgtest_main -lgtest  src/libstore/tests/libnixstore-tests.a -lrapidcheck 
-lgtest_main -lgtest  src/libutil/tests/libnixutil-tests.a -lrapidcheck 
-lgtest_main -lgtest  src/libutil/libnixutil.a -pthread -lcrypto -ldl -pthread 
-lbrotlienc -lbrotlicommon -lbrotlidec -lbrotlicommon -larchive -lnettle -lacl 
-llzma -lzstd -llz4 -lbz2 -lz -lxml2 -lz -L/usr/lib/x86_64-linux-gnu 
-lboost_context -lcpuid   src/libstore/libnixstore.a -lsqlite3 -lm -lz -lcurl 
-lnghttp2 -lidn2 -lrtmp -lssh2 -lssh2 -lpsl -lnettle -lgnutls -lgssapi_krb5 
-llber -lldap -llber -lzstd -lbrotlidec -lz -lsodium -pthread -pthread -ldl 
-lseccomp  src/libutil/libnixutil.a -pthread -lcrypto -ldl -pthread -lbrotlienc 
-lbrotlicommon -lbrotlidec -lbrotlicommon -larchive -lnettle -lacl -llzma 
-lzstd -llz4 -lbz2 -lz -lxml2 -lz -L/usr/lib/x86_64-linux-gnu -lboost_context 
-lcpuid   src/libutil/libnixutil.a -pthread -lcrypto -ldl -pthread -lbrotlienc 
-lbrotlicommon -lbrotlidec -lbrotlicommon -larchive -lnettle -lacl -llzma 
-lzstd -llz4 -lbz2 -lz -lxml2 -lz -L/usr/lib/x86_64-linux-gnu -lboost_context 
-lcpuid
/usr/bin/ld: cannot find src/libutil/tests/libnixutil-tests.a: No such file or 
directory
collect2: error: ld returned 1 exit status
make[1]: *** [mk/lib.mk:120: src/libstore/tests/libnixstore-tests] Error 1
rm src/nix/doc/files/profiles.md
make[1]: Leaving directory '/<>'

Processed: Bug#1068146 marked as pending in dipy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068146 [src:dipy] FTBFS: tests failed
Added tag(s) pending.

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

Bug#1068146: marked as pending in dipy

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1068146 in dipy 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/med-team/dipy/-/commit/9f36ad39687b04fe51cbb9f95158c037d98166cc


Added test patch to fix pytest module-level setup. Closes: #1068146


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068146

Bug#1070270: marked as done (riseup-vpn: client no longer works due to cert verification problem)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 15:01:04 +
with message-id 
and subject line Bug#1070270: fixed in riseup-vpn 0.24.5+ds1-1
has caused the Debian Bug report #1070270,
regarding riseup-vpn: client no longer works due to cert verification problem
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.)


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

Package: riseup-vpn
Version: 0.21.11+ds1-5+b1
Severity: grave

When attempting to run the bookworm riseup-vpn package, it fails to 
connect to riseup's servers and gives the following output:


2024/05/01 18:21:23 Error fetching eip v3 
json:https://api.black.riseup.net/3/config/eip-service.json


My understanding is that this is due to the package failing to be able 
to verify the current LetsEncrypt cert that host is using. More details at


https://0xacab.org/leap/bitmask-vpn/-/issues/768

(supposedly the current upstream snap has this fixed, but I haven't 
tried it)


As this breaks what the package is supposed to do (at least when using 
riseup as provider, maybe there is a way to point it elsewhere?) I think 
this is grave. Also I think it might be a good candidate for being fixed 
in a stable release update.


Thanks,

--
Matt Taggart
m...@lackof.org
--- End Message ---
--- Begin Message ---
Source: riseup-vpn
Source-Version: 0.24.5+ds1-1
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
riseup-vpn, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated riseup-vpn 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: Fri, 10 May 2024 19:17:51 +0530
Source: riseup-vpn
Architecture: source
Version: 0.24.5+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 1070270
Changes:
 riseup-vpn (0.24.5+ds1-1) unstable; urgency=medium
 .
   * New upstream version 0.24.5+ds1 (Rebase patches)
 Closes: #1070270
   * Exclude more vendored stuff, update copyrights
   * Update copyright, remove superfluous licenses
   * Update d/install to install helpers from non-symlinks
   * Update d/rules to
 + Use changed location of qmake and lrelease
 + Update PROVIDER and TARGET
 + Add some non-included files via DH_GOLANG_INSTALL_EXTRA
   * Update builddeps and Depends to qt6 variants.
   * Take up upstream patch to fixup package with qt 6.4
   * Add qml6-module-qt5compat-graphicaleffects to depends
Checksums-Sha1:
 4d137367e25fab4e0123d7a1886d61ca8c26275f 2524 riseup-vpn_0.24.5+ds1-1.dsc
 e344242a5437c41eefab188d59671d6b50448320 6035988 
riseup-vpn_0.24.5+ds1.orig.tar.gz
 be36544b8deeab435faa8ea01961ab124f0b3d88 9988 
riseup-vpn_0.24.5+ds1-1.debian.tar.xz
 0606441093ad30485610c66056d895cc89751b9e 17344 
riseup-vpn_0.24.5+ds1-1_amd64.buildinfo
Checksums-Sha256:
 49a952adf408294b30bddb725bd15cdd4ecf152ca4ecb64789756630c019037c 2524 
riseup-vpn_0.24.5+ds1-1.dsc
 ca76e9792d540ddd7ff94c075f817bb955df6e22bfd2a57561f56ed588f30fa4 6035988 
riseup-vpn_0.24.5+ds1.orig.tar.gz
 429913003c2233423791c3ebe40bdfd20d051c5e5f57b44e3b491a39baedb4d4 9988 
riseup-vpn_0.24.5+ds1-1.debian.tar.xz
 418016ee7e14f84ae93c7f318dfb2572931a3dae8eacfb8a91813c079a00a015 17344 
riseup-vpn_0.24.5+ds1-1_amd64.buildinfo
Files:
 87366382083a75b118dce3cfd28088ac 2524 net optional riseup-vpn_0.24.5+ds1-1.dsc
 f53c29b78c768050a10e03fdfe970a04 6035988 net optional 
riseup-vpn_0.24.5+ds1.orig.tar.gz
 83da4e38c395b97807e96ff3d3bd5080 9988 net optional 
riseup-vpn_0.24.5+ds1-1.debian.tar.xz
 661a6026bdc5ebe402a1847f95798749 17344 net optional 
riseup-vpn_0.24.5+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZj4xSQAKCRAqJ5BL1yQ+
2uDSAQCjMXYRyE9ntOJsuCzuI4lLU4TA6aDzcTWOLxwdI61gbQEA1/ku91dwRc6y
fMRJsGRkpDH4mgGtfgB8YLvLezw6SQQ=
=qreZ
-END PGP SIGNATURE-



pgpJozbGIwTsJ.pgp
Description: PGP signature
--- End Message ---

Bug#1070713: how-can-i-help: undefined local variable or method autorm_header_done

[Vincent Lefevre]

On 2024-05-10 12:20:43 +0200, Diederik de Haas wrote:
> Control: severity -1 grave
> 
> On 07 May 2024 19:35:30 +0200 Nicolas Noirbent  wrote:
> > Package: how-can-i-help
> > Version: 18
> > Severity: important
> > Tags: patch
> > 
> > Running how-can-i-help outputs nothing past the initial banner, due to an
> > undefined variable:
> 
> Which makes the package unusable, so upgrading severity accordingly

More or less. I got the error after a bug listed at
"New bugs where assistance is requested":

New bugs where assistance is requested (tagged 'help'):
 - libglib2.0-dev - https://bugs.debian.org/1070773 - libglib2.0-dev:i386 on 
amd64 should not require qemu-user

/usr/bin/how-can-i-help:338:in `': undefined local variable or method 
`autorm_header_done' for main:Object (NameError)

autorm_header_done == 0
^^
Did you mean?  autorm_date

BTW, I hadn't got any error after 6 upgrades (not involving ruby) with
how-can-i-help 18, but now I get an error. It should probably have a
testsuite to be able to trigger issues under various conditions.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1070270: riseup-vpn: client no longer works due to cert verification problem

[Nilesh Patra]

On Sun, May 05, 2024 at 09:47:40PM +0530, Nilesh Patra wrote:
> On Sat, May 04, 2024 at 08:59:19PM +0530, Nilesh Patra wrote:
> > Hi Matt,
> > 
> > Quoting Matt Taggart:
> > >  Package: riseup-vpn
> > >  Version: 0.21.11+ds1-5+b1
> > >  Severity: grave
> > >  
> > >  When attempting to run the bookworm riseup-vpn package, it fails to 
> > >  connect to riseup's servers and gives the following output:
> > >  
> > >  2024/05/01 18:21:23 Error fetching eip v3 
> > >  json:https://api.black.riseup.net/3/config/eip-service.json
> > >  
> > >  My understanding is that this is due to the package failing to be able 
> > >  to verify the current LetsEncrypt cert that host is using. More details 
> > > at
> > >  
> > >  https://0xacab.org/leap/bitmask-vpn/-/issues/768
> > >  
> > >  (supposedly the current upstream snap has this fixed, but I haven't 
> > >  tried it)
> > >  
> > >  As this breaks what the package is supposed to do (at least when using 
> > >  riseup as provider, maybe there is a way to point it elsewhere?) I think 
> > >  this is grave. Also I think it might be a good candidate for being fixed 
> > >  in a stable release update.
> > 
> > If I am not mistaken, as per the said, issue, it is fixed in the commit
> > referenced here, right?
> > 
> > 
> > https://0xacab.org/leap/bitmask-vpn/-/commit/14cf64b10a97c29688f252a7d9d3481c8484aa1d
> > 
> > I tried this in my testing system and it seems I am able to connect to the 
> > VPN
> > with this patch applied. Can you confirm?
> 
> I tried with this commit using my stable `.deb` in a fresh stable VM and it
> seems things are working.

I got more extensive testing done. This definitely fixes the issue as it helps
verify the letsencrypt certificate.

> > Consequently, I also did some work to cherry-pick this and prepare a 
> > stable-p-u
> > upload (not yet uploaded, will do after confirmation) and pushed my changes
> > at[1]. I have also compiled the `.deb` for stable and it is ready to be
> > consumed[2]. Do you think you could ask someone to check the same?
> > 
> > Other than that, I also tried to update the package in unstable to the 
> > latest
> > version to fixup this properly. I was able to build it, pushed my changes
> > here[3] and the `.deb` is available here[4]. Again, if you/someone else 
> > could
> > try this, it'd be great. It is working for me on my debian/testing system.
> 
> I asked a friend to check on their testing system and it seems to be working 
> as
> well. I will proceed to upload these in a week or so. Until then I am awaiting
> your response.

OK, so now the time is up and I've got some spare time now - I am going ahead
with an upload. This look fine and the package works.

> > I would have attemped the update much sooner but unfortunately an update 
> > with
> > 0xacab's gitlab broke my d/watch file and I did not notice a new version is 
> > out
> > there sooner.
> > 
> > I was thinking to go ahead with an upload, but there are a few things that I
> > would like to clarify before I do so (btw thanks to the maintainers for
> > committing a patch to use with qt6.4):

To be clear: these questions do not apply to the stable update. Only to the
unstable one.

> > 1. Why is the default provider set to "provider = bitmask" in
> > providers/vendor.conf? This leads to building the binary called bitmask-vpn
> > instead of riseup-vpn. Is there a thought of changing the binary name?
> > 
> > In current stage it points to just dummy APIs and hence I overrode it in 
> > d/rules
> > to build riseup-vpn instead.

I am keeping this as is.

> > 2. In the vendor/gitlab.com/yawning/obfs4.git/ package, there are 3 license.
> > BSD-2-Clause, BSD-3-Clause and also GPL-3 for
> > vendor/gitlab.com/yawning/obfs4.git/internal/x25519ell2/x25519ell2.go - so 
> > what
> > exactly is the exact license? Is it redistributable under all the three? (I
> > don't think so?)

I found a comment from yawning and added the internal/* under GPL.

Going for an upload to unstable followed by an s-p-u.

> > [1]: 
> > https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/bookworm-pu?ref_type=heads
> > [2]: https://people.debian.org/~nilesh/riseup-vpn-stable/
> > [3]: 
> > https://salsa.debian.org/go-team/packages/riseup-vpn/-/tree/debian/sid?ref_type=heads
> > [4]: https://people.debian.org/~nilesh/riseup-vpn-0.24.5/
[5]: https://gitlab.com/yawning/obfs4/-/issues/5

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1070854: clc-intercal FTBFS: dpkg-genbuildinfo: error: binary build with no binary artifacts found

[Adrian Bunk]

Source: clc-intercal
Version: 1:1.00-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=clc-intercal=1%3A1.00-1

...
chmod +x `pwd`/debian/clc-intercal/usr/bin/*
 dpkg-genbuildinfo --build=any -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo
dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=any 
-O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo subprocess returned exit 
status 25

Bug#1070853: strace: test failures on 32bit with 64bit time_t

[Adrian Bunk]

Source: strace
Version: 6.8-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=strace=armhf=6.8-1=1715348223=0
https://buildd.debian.org/status/fetch.php?pkg=strace=armel=6.8-1=1715346678=0
https://buildd.debian.org/status/fetch.php?pkg=strace=powerpc=6.8-1=1715349316=0

...
FAIL: strace-k.test
PASS: umovestr_cached.test
FAIL: strace-k-with-depth-limit.test
FAIL: strace-k-demangle.test
PASS: strace-DD.test
FAIL: strace-k-p.test
PASS: strace--tips-full.test
PASS: qual_fault-syscall.test
PASS: qual_fault.test
PASS: filtering_syscall-syntax.test
PASS: looping_threads.test
==
   strace 6.8: tests/test-suite.log
==

# TOTAL: 1350
# PASS:  1057
# SKIP:  289
# XFAIL: 0
# FAIL:  4
# XPASS: 0
# ERROR: 0
...
FAIL: strace-k
==

+ ../src/strace -V
+ TIMEOUT=timeout -k 5 -s XCPU 1500
+ timeout -k 5 -s XCPU 1500 true
+ [ 1 -eq 0 ]
+ exec timeout -k 5 -s XCPU 1500 ../../tests/strace-k.test
+ : 0
+ : -k
+ : --stack-trace
+ : 
+ [ -f /proc/self/maps ]
+ check_prog grep
+ type grep
+ check_prog readlink
+ type readlink
+ check_prog sed
+ type sed
+ check_prog tr
+ type tr
+ command -v sed
+ path_to_sed=/usr/bin/sed
+ [ -x /usr/bin/sed ]
+ readlink -ev -- /usr/bin/sed
+ path_to_sed=/usr/bin/sed
+ /usr/bin/sed -n s/^[^/]\+[[:space:]]\(\/.*\)$/\1/p /proc/self/maps
+ grep -F -x -e /usr/bin/sed
+ run_prog ../stack-fcall
+ [ 1 -eq 0 ]
+ args=../stack-fcall
+ ../stack-fcall
+ [ x0 = x1 ]
+ run_strace -e chdir -k ../stack-fcall
+ 
+ args=-e chdir -k ../stack-fcall
+ ../../src/strace -o log -e chdir -k ../stack-fcall
+ expected=../../../tests/strace-k.expected
+ awk_script_common=
/^[^ ]/ {
if (out != "")
print out

syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)

if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}

/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}


+ awk_script_symbol=
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}


+ awk_script_source=
/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\] ([^:]+):([0-9]+)$/ && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
if (sym == "main" || sym ~ /f[0-9]/) {
file = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\] 
([^:]+):([0-9]+)$/, "\\2", 1)
line = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) \[0x[a-f0-9]+\] 
([^:]+):([0-9]+)$/, "\\3", 1)
sub(".*/", "", file)
out = out " " sym "<" file ":" line ">"
if (sym == "main")
stop = 1
}
}


+ [ --stack-trace = --stack-trace ]
+ awk_script=
/^[^ ]/ {
if (out != "")
print out

syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)

if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}

/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}


/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}


+ awk 
/^[^ ]/ {
if (out != "")
print out

syscall = gensub(/^([[:alnum:]_]+)\(.*/, "\\1", 1)
signal = gensub(/^--- ([A-Z]+) .*/, "\\1", 1)

if (syscall != $0) {
out = syscall
stop = 0
} else if (signal != $0) {
out = signal
stop = 0
} else {
out = ""
}
}

/^ > too many stack frames/ {
out = out " _too_many_stack_frames_"
stop = 1
}


/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) / && !stop {
sym = gensub(/^ >[^(]+\(([^+]+)\+0x[a-f0-9]+\) .*$/, "\\1", 1)
out = out " " sym
if (sym == "main")
stop = 1
}

 log
+ LC_ALL=C grep -E -x -f ../../../tests/strace-k.expected
+ cat ../../../tests/strace-k.expected
+ cat out
+ cat
Failed pattern of expected output:
^chdir (__kernel_vsyscall )?(__)?chdir f3 f2 f1 f0 main
^SIGURG (__kernel_vsyscall )?(__)?kill f3 f2 f1 f0 main
Actual output:
chdir chdir f3
SIGURG kill f3
+ pattern=
+ pattern=No DWARF information found
+ [ -n No DWARF information found ]
+ LC_ALL=C grep -x  > No DWARF information found
+ dump_log_and_fail_with ../../src/strace -e chdir -k ../stack-fcall 

Bug#1070515: marked as pending in dipy

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1070515 in dipy 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/med-team/dipy/-/commit/48de65ef11354ed3daa42a046f160bac52cec0d6


d/control: h5py, trx, and tqdm are also required to build the docs.

I can confirm that this now Closes: #1070515


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070515

Processed: Bug#1070515 marked as pending in dipy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070515 [src:dipy] dipy: FTBFS with nocheck profile
Added tag(s) pending.

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

Bug#1067367: marked as done (mathgl: FTBFS: debian/tests/run-tests: 37: python3.12: not found)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 15:41:56 +0200
with message-id 
and subject line Re: Bug#1067367: mathgl: FTBFS: debian/tests/run-tests: 37: 
python3.12: not found
has caused the Debian Bug report #1067367,
regarding mathgl: FTBFS: debian/tests/run-tests: 37: python3.12: not found
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.)


-- 
1067367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mathgl
Version: 8.0.1-7.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 
> 'examples/CMakeFiles/mgl_mpi_example.dir/build'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [100%] Built target mgl_mpi_example
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_start 
> /<>/obj-x86_64-linux-gnu/CMakeFiles 0
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu/examples'
> 3wave.png: ok
> alpha.png: ok
> apde.png: ok
> area.png: ok
> aspect.png: ok
> axial.png: ok
> axis.png: ok
> background.png: ok
> barh.png: ok
> bars.png: ok
> belt.png: ok
> beltc.png: ok
> bifurcation.png: ok
> box.png: ok
> boxplot.png: ok
> boxs.png: ok
> candle.png: ok
> chart.png: ok
> cloud.png: ok
> colorbar.png: ok
> combined.png: ok
> cones.png: ok
> cont.png: ok
> cont3.png: ok
> cont_xyz.png: ok
> contd.png: ok
> contf.png: ok
> contf3.png: ok
> contf_xyz.png: ok
> conts.png: ok
> contv.png: ok
> correl.png: ok
> curvcoor.png: ok
> cut.png: ok
> daisy.png: ok
> dat_diff.png: ok
> dat_extra.png: ok
> data1.png: ok
> data2.png: ok
> dcont.png: ok
> dens.png: ok
> dens3.png: ok
> dens_xyz.png: ok
> detect.png: ok
> dew.png: ok
> diffract.png: ok
> dilate.png: ok
> dots.png: ok
> earth.png: ok
> error.png: ok
> error2.png: ok
> export.png: ok
> fall.png: ok
> fexport.png: ok
> fit.png: ok
> flame2d.png: ok
> flow.png: ok
> flow3.png: ok
> fog.png: ok
> fonts.png: ok
> grad.png: ok
> hist.png: ok
> ifs2d.png: ok
> ifs3d.png: ok
> indirect.png: ok
> inplot.png: ok
> iris.png: ok
> keep.png: ok
> label.png: ok
> lamerey.png: ok
> legend.png: ok
> light.png: ok
> lines.png: ok
> loglog.png: ok
> map.png: ok
> mark.png: ok
> mask.png: ok
> mesh.png: ok
> minmax.png: ok
> mirror.png: ok
> molecule.png: ok
> ode.png: ok
> ohlc.png: ok
> param1.png: ok
> param2.png: ok
> param3.png: ok
> paramv.png: ok
> parser.png: ok
> pde.png: ok
> pendelta.png: ok
> pipe.png: ok
> plot.png: ok
> pmap.png: ok
> primitives.png: ok
> projection.png: ok
> projection5.png: ok
> pulse.png: ok
> qo2d.png: ok
> quality0.png: ok
> quality1.png: ok
> quality2.png: ok
> quality4.png: ok
> quality5.png: ok
> quality6.png: ok
> quality8.png: ok
> radar.png: ok
> refill.png: ok
> region.png: ok
> scanfile.png: ok
> schemes.png: ok
> section.png: ok
> several_light.png: ok
> solve.png: ok
> stem.png: ok
> step.png: ok
> stereo.png: ok
> stfa.png: ok
> style.png: ok
> surf.png: ok
> surf3.png: ok
> surf3a.png: ok
> surf3c.png: ok
> surf3ca.png: ok
> surfa.png: ok
> surfc.png: ok
> surfca.png: ok
> table.png: ok
> tape.png: ok
> tens.png: ok
> ternary.png: ok
> text.png: ok
> text2.png: ok
> textmark.png: ok
> ticks.png: ok
> tile.png: ok
> tiles.png: ok
> torus.png: ok
> traj.png: ok
> triangulation.png: ok
> triplot.png: ok
> tube.png: ok
> type0.png: ok
> type1.png: ok
> type2.png: ok
> vect.png: ok
> vect3.png: ok
> venn.png: ok
> debian/tests/run-tests: 37: python3.12: not found
> make[1]: *** [debian/rules:54: override_dh_auto_test] Error 127


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/mathgl_8.0.1-7.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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 mark 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 

Bug#1068758: marked as done (strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 12:22:13 +
with message-id 
and subject line Bug#1068758: fixed in strace 6.8-1
has caused the Debian Bug report #1068758,
regarding strace fails to build it's tests on arm-linux-gnueabihf with 64bit 
time_t
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.)


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

Package: src:strace
Version: 6.5-0.1
Severity: serious
Tags: sid trixie ftbfs
Forwarded: https://github.com/strace/strace/issues/296

strace fails to build it's tests on arm-linux-gnueabihf with 64bit time_t:

make[5]: Entering directory '/<>/build/tests'
depbase=echo _newselect.o | sed 's|[^/]*$|.deps/&|;s|\.o$||';
gcc -DHAVE_CONFIG_H -I. -I../src/linux/arm -I../../src/linux/arm 
-I../src/linux/generic -I../../src/linux/generic -I../src -I../../src 
-I../../bundled/linux/arch/arm/include/uapi 
-I../../bundled/linux/include/uapi -DSTRACE_SIZEOF_KERNEL_LONG_T=4 
-DTESTS_SIZEOF_KERNEL_LONG_T=4 -DSTRACE_SIZEOF_LONG=4 
-DTESTS_SIZEOF_LONG=4 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 
-I../bundled/linux/arch/arm/include/uapi -I../bundled/linux/include/uapi 
-Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter 
-Wdate-time -Wformat-security -Wimplicit-fallthrough=5 -Winit-self 
-Wlogical-op -Wmissing-prototypes -Wnested-externs 
-Wold-style-definition -Wtrampolines -Wundef -Wwrite-strings -Werror -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/strace-6.8-0ubuntu1 -Wall -g -O2 -MT 
_newselect.o -MD -MP -MF $depbase.Tpo -c -o _newselect.o 
../../tests/_newselect.c &&

mv -f $depbase.Tpo $depbase.Po
mv -f .deps/libstrace_a-xmalloc.Tpo .deps/libstrace_a-xmalloc.Po
In file included from ../../tests/_newselect.c:16:
../../tests/xselect.c: In function ‘main’:
gcc -DHAVE_CONFIG_H -I./linux/arm -I../../src/linux/arm 
-I./linux/generic -I../../src/linux/generic -I. -I../../src 
-I../../bundled/linux/arch/arm/include/uapi 
-I../../bundled/linux/include/uapi -DIN_STRACE=1 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 
-I../bundled/linux/arch/arm/include/uapi -I../bundled/linux/include/uapi 
-Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter 
-Wdate-time -Wformat-security -Wimplicit-fallthrough=5 -Winit-self 
-Wlogical-op -Wmissing-prototypes -Wnested-externs 
-Wold-style-definition -Wtrampolines -Wundef -Wwrite-strings -Werror -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/strace-6.8-0ubuntu1 -Wall -g -O2 -MT 
libstrace_a-bpf_attr_check.o -MD -MP -MF 
.deps/libstrace_a-bpf_attr_check.Tpo -c -o libstrace_a-bpf_attr_check.o 
test -f 'bpf_attr_check.c' || echo '../../src/'bpf_attr_check.c
../../tests/xselect.c:216:24: error: overflow in conversion from ‘long 
long int’ to ‘kernel_long_t’ {aka ‘long int’} changes value from 
‘-3819351491602432273’ to ‘-559038737’ [-Werror=overflow]

216 | tv_in.tv_sec = (time_t) 0xcafef00ddeadbeefLL;
| ^
--- End Message ---
--- Begin Message ---
Source: strace
Source-Version: 6.8-1
Done: Bo YU 

We believe that the bug you reported is fixed in the latest version of
strace, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated strace 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: Fri, 10 May 2024 14:53:53 +0800
Source: strace
Architecture: source
Version: 6.8-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Bo YU 
Closes: 1060789 1068758
Changes:
 strace (6.8-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Adrien Nader ]
   * debian/control: use commas before "i.e." in description rather than colon
 .
   [ Bo YU ]
   * New upstream 

Bug#1069351: marked as done (strace: FTBFS on arm64: ../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 12:22:13 +
with message-id 
and subject line Bug#1060789: fixed in strace 6.8-1
has caused the Debian Bug report #1060789,
regarding strace: FTBFS on arm64: ../../src/xlat/btrfs_key_types.h:167:37: 
error: ‘BTRFS_EXTENT_REF_V0_KEY’ undeclared here (not in a function); did you 
mean ‘BTRFS_EXTENT_DATA_KEY’?
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.)


-- 
1060789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strace
Version: 6.5-0.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H   -I./linux/aarch64 -I../../src/linux/aarch64 
> -I./linux/generic -I../../src/linux/generic -I. -I../../src  -DIN_STRACE=1
>   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
> -Wno-missing-field-initializers -Wno-unused-parameter -Wdate-time 
> -Wformat-security -Wimplicit-fallthrough=5 -Winit-self -Wlogical-op 
> -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wtrampolines 
> -Wundef -Wwrite-strings -Werror   -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -Wall -g -O2 -MT 
> libstrace_a-btrfs.o -MD -MP -MF .deps/libstrace_a-btrfs.Tpo -c -o 
> libstrace_a-btrfs.o `test -f 'btrfs.c' || echo '../../src/'`btrfs.c
> In file included from ../../src/btrfs.c:51:
> ../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ 
> undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’?
>   167 | static_assert((unsigned long long) (BTRFS_EXTENT_REF_V0_KEY)
>   | ^~~
>   | BTRFS_EXTENT_DATA_KEY
> ../../src/xlat/btrfs_key_types.h:167:15: error: expression in static 
> assertion is not an integer
>   167 | static_assert((unsigned long long) (BTRFS_EXTENT_REF_V0_KEY)
>   |   ^
> ../../src/xlat/btrfs_key_types.h:175:15: error: expression in static 
> assertion is not an integer
>   175 | static_assert((unsigned long long) (BTRFS_SHARED_BLOCK_REF_KEY)
>   |   ^
> make[4]: *** [Makefile:4695: libstrace_a-btrfs.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/strace_6.5-0.1_unstable-arm64.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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: strace
Source-Version: 6.8-1
Done: Bo YU 

We believe that the bug you reported is fixed in the latest version of
strace, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated strace 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: Fri, 10 May 2024 14:53:53 +0800
Source: strace
Architecture: source
Version: 6.8-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Bo YU 
Closes: 1060789 1068758
Changes:
 strace (6.8-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Adrien Nader ]
   * debian/control: use commas before "i.e." in description rather than colon
 .
   [ Bo YU ]
   * New upstream version 

Bug#1060789: marked as done (strace FTBFS with linux-libc-dev >= 6.6)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 12:22:13 +
with message-id 
and subject line Bug#1060789: fixed in strace 6.8-1
has caused the Debian Bug report #1060789,
regarding strace FTBFS with linux-libc-dev >= 6.6
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.)


-- 
1060789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strace
Version: 6.5-0.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=strace=riscv64=6.5-0.1%2Bb1=1705203098=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/strace.html

...
In file included from ../../src/btrfs.c:51:
../../src/xlat/btrfs_key_types.h:167:37: error: ‘BTRFS_EXTENT_REF_V0_KEY’ 
undeclared here (not in a function); did you mean ‘BTRFS_EXTENT_DATA_KEY’?
  167 | static_assert((unsigned long long) (BTRFS_EXTENT_REF_V0_KEY)
  | ^~~
  | BTRFS_EXTENT_DATA_KEY
../../src/xlat/btrfs_key_types.h:167:15: error: expression in static assertion 
is not an integer
  167 | static_assert((unsigned long long) (BTRFS_EXTENT_REF_V0_KEY)
  |   ^
../../src/xlat/btrfs_key_types.h:175:15: error: expression in static assertion 
is not an integer
  175 | static_assert((unsigned long long) (BTRFS_SHARED_BLOCK_REF_KEY)
  |   ^
make[4]: *** [Makefile:4695: libstrace_a-btrfs.o] Error 1
...
--- End Message ---
--- Begin Message ---
Source: strace
Source-Version: 6.8-1
Done: Bo YU 

We believe that the bug you reported is fixed in the latest version of
strace, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bo YU  (supplier of updated strace 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: Fri, 10 May 2024 14:53:53 +0800
Source: strace
Architecture: source
Version: 6.8-1
Distribution: unstable
Urgency: medium
Maintainer: Steve McIntyre <93...@debian.org>
Changed-By: Bo YU 
Closes: 1060789 1068758
Changes:
 strace (6.8-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Adrien Nader ]
   * debian/control: use commas before "i.e." in description rather than colon
 .
   [ Bo YU ]
   * New upstream version 6.8. (Closes: #1060789).
   * Rebase debian/patches/*
   * Add 03-fix-arm-time_t-ftbfs.patch to fix FTBFS. (Closes: #1068758)
   * Depend libunwind and libiberty on more architectures.
 Thanks to Balint Reczey. See MR!3.
Checksums-Sha1:
 cfdd06f998c81e120685c017ae1baf068ba005d9 2155 strace_6.8-1.dsc
 713cc8b8c4c62294b6cb0490f4b4f0de5a6d4c8d 2457948 strace_6.8.orig.tar.xz
 9ef28785e23798c9411e80474ec406e797b23e64 21772 strace_6.8-1.debian.tar.xz
 437b27b09f700743fd86487bf0841f58d308e902 6580 strace_6.8-1_source.buildinfo
Checksums-Sha256:
 7b79d512663084164d97239b5b5cb7c58c8ac18281751014013d10a6de53214e 2155 
strace_6.8-1.dsc
 ba6950a96824cdf93a584fa04f0a733896d2a6bc5f0ad9ffe505d9b41e970149 2457948 
strace_6.8.orig.tar.xz
 473ede431cb07ef82df11c72ada778718fb6f818d292074abad8bebc29c986bd 21772 
strace_6.8-1.debian.tar.xz
 6415938b74bd59119d9e03f7908293ae73bf021561828bcbc6349b669c254f1a 6580 
strace_6.8-1_source.buildinfo
Files:
 546c7de8e60cb8eb7dc5fb6100ee52ec 2155 utils optional strace_6.8-1.dsc
 1c7aca3fad1f309fdb54031866fad6d9 2457948 utils optional strace_6.8.orig.tar.xz
 dfed5cf8abccf0f014ea1f56524cf9d9 21772 utils optional 
strace_6.8-1.debian.tar.xz
 99b063ba66bab9bf395a0878be3c70f5 6580 utils optional 
strace_6.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAmY+DhwACgkQryKDqnbi
rHuY7A//ZZkLgfpKTH3E0JFTMF5v+c/FrIBb8rKeW4kYMV4lGdMv5NZGlL1Vyo/v
jq2LgmDVva6oeenXOVRsUSSMvhkzZlC6jvUgLYjIxXrmotq/l5M4DmPPBhzd/OJH
hdhca8kMOxqXqaWYtHz3Y8qards5wrIqbim63okrqXVBiBdt37MvNT9UNcoAfQOm
KseD62Rcv20nLfxGP1K6Ieujj9aKJwdaWFtVqP2sqFa30iA9pAB7k131HUMcX8iT
ctCRuGo2lcpUIQixnAAiYrDHwBLz6QseHLp7gLVXmQtW1DHUvvzdP2iKy6XKukcW
VrM+EBmPCEyI5h7URXA5caAzI4+j8A9FRV9VECZLN/Gs90uBKTf6ih57cPUPuXq/
CmLNJ0mwtQMR5VJ/HBzGnr23aNgw/QQhnTzsHMp/Dwu+F2DFeEBkrW8jrjFS8NIb

Bug#1066671: marked as done (geki3: FTBFS: boss.c:205:11: error: implicit declaration of function ‘CreateEnemyBomb’; did you mean ‘CreateEnemyShot’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 12:20:24 +
with message-id 
and subject line Bug#1066671: fixed in geki3 1.0.3-11
has caused the Debian Bug report #1066671,
regarding geki3: FTBFS: boss.c:205:11: error: implicit declaration of function 
‘CreateEnemyBomb’; did you mean ‘CreateEnemyShot’? 
[-Werror=implicit-function-declaration]
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.)


-- 
1066671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geki3
Version: 1.0.3-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" 
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"geki3-KXL\" 
> -DVERSION=\"1.0.3\" -DHAVE_LIBKXL=1 -DHAVE_LIBKXL=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_UNISTD_H=1 -DDATA_PATH=\"/usr/share/games/geki3/data\" 
> -DBMP_PATH=\"/usr/share/games/geki3/bmp\" 
> -DWAV_PATH=\"/usr/share/games/geki3/wav\" -DTITLE=\"geki3-KXL\ 1.0.3\"  -I. 
> -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c boss.c
> boss.c: In function ‘MovePenguin’:
> boss.c:205:11: error: implicit declaration of function ‘CreateEnemyBomb’; did 
> you mean ‘CreateEnemyShot’? [-Werror=implicit-function-declaration]
>   205 |   CreateEnemyBomb(my->X + 20,
>   |   ^~~
>   |   CreateEnemyShot
> boss.c: In function ‘MoveTurtle’:
> boss.c:302:11: error: implicit declaration of function ‘CreateMissile’; did 
> you mean ‘CreateBoss’? [-Werror=implicit-function-declaration]
>   302 |   CreateMissile(my, my->X - 8, my->Y);
>   |   ^
>   |   CreateBoss
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:233: boss.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/geki3_1.0.3-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=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 mark 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: geki3
Source-Version: 1.0.3-11
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
geki3, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated geki3 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: Fri, 10 May 2024 13:57:54 +0200
Source: geki3
Architecture: source
Version: 1.0.3-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Alexandre Detiste 
Closes: 1066671
Changes:
 geki3 (1.0.3-11) unstable; urgency=medium
 .
   * Switch to dh sequencer & compat 13
   * Fix implicit declarations (Closes: #1066671)
   * Fix manpage 

Processed: network-manager-fortisslvpn: ppp >=2.5.0 breaks network-manager-fortisslvpn

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1069693 ppp >=2.5.0 breaks network-manager-fortisslvpn
Bug #1069693 [network-manager-fortisslvpn] network-manager-fortisslvpn: ppp 
>=2.5.0 breaks
Changed Bug title to 'ppp >=2.5.0 breaks network-manager-fortisslvpn' from 
'network-manager-fortisslvpn: ppp >=2.5.0 breaks'.
> thanks
Stopping processing here.

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

Processed (with 1 error): network-manager-fortisslvpn: ppp >=2.5.0 breaks network-manager-fortisslvpn

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1069693 network-manager-fortisslvpn: ppp >=2.5.0 breaks
Bug #1069693 [network-manager-fortisslvpn] network-manager-fortisslvpn: 
upgrading the stack from network-manager-fortisslvpn-gnome to ppp broke a 
current working VPN configuration
Changed Bug title to 'network-manager-fortisslvpn: ppp >=2.5.0 breaks' from 
'network-manager-fortisslvpn: upgrading the stack from 
network-manager-fortisslvpn-gnome to ppp broke a current working VPN 
configuration'.
> network-manager-fortisslvpn
Unknown command or malformed arguments to command.
> severity 1069693 grave
Bug #1069693 [network-manager-fortisslvpn] network-manager-fortisslvpn: ppp 
>=2.5.0 breaks
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#1070840: r-cran-ff: autopkgtest regression with r-base 4.4.0

[Dirk Eddelbuettel]

On 10 May 2024 at 06:28, Dirk Eddelbuettel wrote:
| 
| On 10 May 2024 at 10:54, Graham Inggs wrote:
| | Source: r-cran-ff
| | Version: 4.0.12+ds-1
| | Severity: serious
| | X-Debbugs-Cc: Dirk Eddelbuettel 
| | User: debian...@lists.debian.org
| | Usertags: regression
| | 
| | Hi Maintainer
| | 
| | r-cran-ff's autopkgtest regresses when tested with r-base 4.4.0 [1].
| | I've copied what I hope is the relevant part of the log below.
| 
| FYI, I am not the maintainer of r-cran-ff.
| 
| The package is perfectly clean at CRAN on all hardware-os combinations,
| including amd64 so maybe the maintainer needs to turn this test off:
| 
|https://cloud.r-project.org/web/checks/check_results_ff.html

Also, for what it is worth, installing r-cran-ff and its one dependency in a
container along with r-cran-testthat and its twenty (ick!), and then running
'bash run-unit-test' leads to no issue:

   [ FAIL 0 | WARN 52 | SKIP 0 | PASS 966 ]

Maybe something for the package maintainer to consider.

Dirk

| 
| Dirk
|  
| | Regards
| | Graham
| | 
| | 
| | [1] https://ci.debian.net/packages/r/r-cran-ff/testing/amd64/
| | 
| | 
| | 42s ══ Failed tests
| | 
| | 42s ── Failure ('test-zero_lengths.R:34:3'): file size is correct when
| | creating ff integer from scratch ──
| | 42s file.exists(f1) is not TRUE
| | 42s
| | 42s `actual`: FALSE
| | 42s `expected`: TRUE
| | 42s
| | 42s [ FAIL 1 | WARN 52 | SKIP 0 | PASS 965 ]
| | 42s Error: Test failures
| | 42s Execution halted
| 
| -- 
| dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
| 

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1070842: r-bioc-mutationalpatterns: autopkgtest regression with r-base 4.4.0

[Dirk Eddelbuettel]

On 10 May 2024 at 11:01, Graham Inggs wrote:
| Source: r-bioc-mutationalpatterns
| Version: 3.12.0+dfsg-1
| Severity: serious
| X-Debbugs-Cc: Dirk Eddelbuettel 
| User: debian...@lists.debian.org
| Usertags: regression
| 
| Hi Maintainer
| 
| r-bioc-mutationalpatterns' autopkgtest regresses when tested with r-base 4.4.0
| [1].  I've copied what I hope is the relevant part of the log below.

FYI, I am not the maintainer of r-bioc-mutationalpatterns.

As you likely know, BioConductor aligns its releases with R releases and is
now at release 3.19 (matching R 4.4.0) for which this package is now at
version 3.14.0.

I suggest the maintainer look into upgrading BioConductor to 3.19.

Dirk

| 
| Regards
| Graham
| 
| 
| [1] https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/testing/amd64/
| 
| 
| 125s > test_check("MutationalPatterns")
| 172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
| 172s
| 172s ══ Failed tests
| 
| 172s ── Error ('test-fit_to_signatures_bootstrapped.R:12:3'): Output
| has correct class ──
| 172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
| of class NULL
| 172s Backtrace:
| 172s ▆
| 172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
| test-fit_to_signatures_bootstrapped.R:12:3
| 172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
| 172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
| 172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
| 172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
| 172s 6. │ ├─S4Vectors::isEmpty(sims)
| 172s 7. │ └─S4Vectors::isEmpty(sims)
| 172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
| 172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
| 172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
| 172s 11. └─base::unlist(.)
| 172s ── Error ('test-fit_to_signatures_bootstrapped.R:31:3'): Output
| is equal to expected ──
| 172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
| of class NULL
| 172s Backtrace:
| 172s ▆
| 172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
| test-fit_to_signatures_bootstrapped.R:31:3
| 172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
| 172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
| 172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
| 172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
| 172s 6. │ ├─S4Vectors::isEmpty(sims)
| 172s 7. │ └─S4Vectors::isEmpty(sims)
| 172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
| 172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
| 172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
| 172s 11. └─base::unlist(.)
| 172s ── Error ('test-fit_to_signatures_strict.R:11:1'): (code run
| outside of `test_that()`) ──
| 172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
| of class NULL
| 172s Backtrace:
| 172s ▆
| 172s 1. ├─MutationalPatterns::fit_to_signatures_strict(...) at
| test-fit_to_signatures_strict.R:11:1
| 172s 2. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
| 172s 3. │ └─MutationalPatterns:::.plot_sim_decay(...)
| 172s 4. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
| 172s 5. │ ├─S4Vectors::isEmpty(sims)
| 172s 6. │ └─S4Vectors::isEmpty(sims)
| 172s 7. │ └─base::vapply(x, isEmpty, logical(1L))
| 172s 8. │ ├─S4Vectors (local) FUN(X[[i]], ...)
| 172s 9. │ └─S4Vectors (local) FUN(X[[i]], ...)
| 172s 10. └─base::unlist(.)
| 172s
| 172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
| 173s Error: Test failures
| 173s Execution halted

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1070843: r-bioc-s4vectors: autopkgtest regression with r-base 4.4.0

[Dirk Eddelbuettel]

On 10 May 2024 at 11:04, Graham Inggs wrote:
| Source: r-bioc-s4vectors
| Version: 0.40.2+dfsg-1
| Severity: serious
| X-Debbugs-Cc: Dirk Eddelbuettel 
| User: debian...@lists.debian.org
| Usertags: regression
| 
| Hi Maintainer
| 
| r-bioc-s4vectors' autopkgtest regresses when tested with r-base 4.4.0
| [1].  I've copied what I hope is the relevant part of the log below.

FYI, I am not the maintainer of r-bioc-s4vectors.

As you likely know, BioConductor aligns its releases with R releases and is
now at release 3.19 (matching R 4.4.0) for which this package is now at
version 0.42.0.

I suggest the maintainer look into upgrading BioConductor to 3.19.

Dirk

| 
| Regards
| Graham
| 
| 
| [1] https://ci.debian.net/packages/r/r-bioc-s4vectors/testing/amd64/
| 
| 
| 125s > S4Vectors:::.test()
| 129s Timing stopped at: 0.009 0 0.009
| 129s Error in var(x) : is.atomic(y) is not TRUE
| 129s In addition: Warning messages:
| 129s 1: In combineUniqueCols(X, Y, Z, use.names = FALSE) :
| 129s different values in multiple instances of column 'dup', ignoring this
| 129s column in DFrame 2
| 129s 2: In combineUniqueCols(X, Y, Z) :
| 129s different values for shared rows in multiple instances of column 'dup',
| 129s ignoring this column in DFrame 2
| 129s 3: In combineUniqueCols(x, y2) :
| 129s different values for shared rows in multiple instances of column 'X',
| 129s ignoring this column in DFrame 2
| 130s Loading required package: GenomeInfoDb
| 132s
| 132s
| 132s RUNIT TEST PROTOCOL -- Thu May 9 22:12:10 2024
| 132s ***
| 132s Number of test functions: 74
| 132s Number of errors: 1
| 132s Number of failures: 0
| 132s
| 132s
| 132s 1 Test Suite :
| 132s S4Vectors RUnit Tests - 74 test functions, 1 error, 0 failures
| 132s ERROR in test_Rle_numerical: Error in var(x) : is.atomic(y) is not TRUE
| 132s
| 132s Test files with failing tests
| 132s
| 132s test_Rle-utils.R
| 132s test_Rle_numerical
| 132s
| 132s
| 132s Error in BiocGenerics:::testPackage("S4Vectors") :
| 132s unit tests failed for package S4Vectors
| 132s Calls:  -> 
| 132s Execution halted

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1070841: r-bioc-iranges: autopkgtest regression with r-base 4.4.0

[Dirk Eddelbuettel]

On 10 May 2024 at 10:58, Graham Inggs wrote:
| Source: r-bioc-iranges
| Version: 2.36.0-1
| Severity: serious
| X-Debbugs-Cc: Dirk Eddelbuettel 
| User: debian...@lists.debian.org
| Usertags: regression
| 
| Hi Maintainer
| 
| r-bioc-iranges' autopkgtest regresses when tested with r-base 4.4.0
| [1].  I've copied what I hope is the relevant part of the log below.

FYI, I am not the maintainer of r-bioc-iranges.

As you likely know, BioConductor aligns releases with R releases at is now at
release 3.19 for which this package is at version 2.38.0. I suggest the
maintainer look into upgrading BioConductor to 3.19.

Dirk

| 
| Regards
| Graham
| 
| 
| [1] https://ci.debian.net/packages/r/r-bioc-iranges/testing/amd64/
| 
| 
| 194s ***
| 194s Number of test functions: 98
| 194s Number of errors: 1
| 194s Number of failures: 0
| 194s
| 194s
| 194s 1 Test Suite :
| 194s IRanges RUnit Tests - 98 test functions, 1 error, 0 failures
| 194s ERROR in test_AtomicList_numerical: Error in FUN(X[[i]], ...) :
| is.atomic(y) is not TRUE
| 194s
| 194s Test files with failing tests
| 194s
| 194s test_AtomicList-utils.R
| 194s test_AtomicList_numerical
| 194s
| 194s
| 194s Warning messages:
| 194s 1: In recycleListElements(e1, en) :
| 194s Some element lengths are not multiples of their corresponding
| element length in e1
| 194s 2: In x + y :
| 194s longer object length is not a multiple of shorter object length
| 194s 3: In recycleListElements(e1, en) :
| 194s Some element lengths are not multiples of their corresponding
| element length in e1
| 194s 4: In x + y :
| 194s longer object length is not a multiple of shorter object length
| 194s Execution halted

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1070840: r-cran-ff: autopkgtest regression with r-base 4.4.0

[Dirk Eddelbuettel]

On 10 May 2024 at 10:54, Graham Inggs wrote:
| Source: r-cran-ff
| Version: 4.0.12+ds-1
| Severity: serious
| X-Debbugs-Cc: Dirk Eddelbuettel 
| User: debian...@lists.debian.org
| Usertags: regression
| 
| Hi Maintainer
| 
| r-cran-ff's autopkgtest regresses when tested with r-base 4.4.0 [1].
| I've copied what I hope is the relevant part of the log below.

FYI, I am not the maintainer of r-cran-ff.

The package is perfectly clean at CRAN on all hardware-os combinations,
including amd64 so maybe the maintainer needs to turn this test off:

   https://cloud.r-project.org/web/checks/check_results_ff.html

Dirk
 
| Regards
| Graham
| 
| 
| [1] https://ci.debian.net/packages/r/r-cran-ff/testing/amd64/
| 
| 
| 42s ══ Failed tests
| 
| 42s ── Failure ('test-zero_lengths.R:34:3'): file size is correct when
| creating ff integer from scratch ──
| 42s file.exists(f1) is not TRUE
| 42s
| 42s `actual`: FALSE
| 42s `expected`: TRUE
| 42s
| 42s [ FAIL 1 | WARN 52 | SKIP 0 | PASS 965 ]
| 42s Error: Test failures
| 42s Execution halted

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: Re: gst-plugins-bad1.0: Circular build-dependency on wpewebkit prevents bootstrap

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 1051447 by 1052660
Bug #1051447 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: Circular 
build-dependency on wpewebkit prevents bootstrap
1051447 was blocked by: 1052660
1051447 was not blocking any bugs.
Removed blocking bug(s) of 1051447: 1052660
>
End of message, stopping processing here.

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

Bug#1070843: r-bioc-s4vectors: autopkgtest regression with r-base 4.4.0

[Graham Inggs]

Source: r-bioc-s4vectors
Version: 0.40.2+dfsg-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-bioc-s4vectors' autopkgtest regresses when tested with r-base 4.4.0
[1].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-s4vectors/testing/amd64/


125s > S4Vectors:::.test()
129s Timing stopped at: 0.009 0 0.009
129s Error in var(x) : is.atomic(y) is not TRUE
129s In addition: Warning messages:
129s 1: In combineUniqueCols(X, Y, Z, use.names = FALSE) :
129s different values in multiple instances of column 'dup', ignoring this
129s column in DFrame 2
129s 2: In combineUniqueCols(X, Y, Z) :
129s different values for shared rows in multiple instances of column 'dup',
129s ignoring this column in DFrame 2
129s 3: In combineUniqueCols(x, y2) :
129s different values for shared rows in multiple instances of column 'X',
129s ignoring this column in DFrame 2
130s Loading required package: GenomeInfoDb
132s
132s
132s RUNIT TEST PROTOCOL -- Thu May 9 22:12:10 2024
132s ***
132s Number of test functions: 74
132s Number of errors: 1
132s Number of failures: 0
132s
132s
132s 1 Test Suite :
132s S4Vectors RUnit Tests - 74 test functions, 1 error, 0 failures
132s ERROR in test_Rle_numerical: Error in var(x) : is.atomic(y) is not TRUE
132s
132s Test files with failing tests
132s
132s test_Rle-utils.R
132s test_Rle_numerical
132s
132s
132s Error in BiocGenerics:::testPackage("S4Vectors") :
132s unit tests failed for package S4Vectors
132s Calls:  -> 
132s Execution halted

Bug#1070842: r-bioc-mutationalpatterns: autopkgtest regression with r-base 4.4.0

[Graham Inggs]

Source: r-bioc-mutationalpatterns
Version: 3.12.0+dfsg-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-bioc-mutationalpatterns' autopkgtest regresses when tested with r-base 4.4.0
[1].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-mutationalpatterns/testing/amd64/


125s > test_check("MutationalPatterns")
172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
172s
172s ══ Failed tests

172s ── Error ('test-fit_to_signatures_bootstrapped.R:12:3'): Output
has correct class ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:12:3
172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 6. │ ├─S4Vectors::isEmpty(sims)
172s 7. │ └─S4Vectors::isEmpty(sims)
172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 11. └─base::unlist(.)
172s ── Error ('test-fit_to_signatures_bootstrapped.R:31:3'): Output
is equal to expected ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_bootstrapped(...) at
test-fit_to_signatures_bootstrapped.R:31:3
172s 2. │ └─MutationalPatterns::fit_to_signatures_strict(...)
172s 3. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 4. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 5. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 6. │ ├─S4Vectors::isEmpty(sims)
172s 7. │ └─S4Vectors::isEmpty(sims)
172s 8. │ └─base::vapply(x, isEmpty, logical(1L))
172s 9. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 10. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 11. └─base::unlist(.)
172s ── Error ('test-fit_to_signatures_strict.R:11:1'): (code run
outside of `test_that()`) ──
172s Error in `FUN(X[[i]], ...)`: isEmpty() is not defined for objects
of class NULL
172s Backtrace:
172s ▆
172s 1. ├─MutationalPatterns::fit_to_signatures_strict(...) at
test-fit_to_signatures_strict.R:11:1
172s 2. │ └─MutationalPatterns:::.strict_refit_backwards_selection_sample(...)
172s 3. │ └─MutationalPatterns:::.plot_sim_decay(...)
172s 4. │ ├─sims[!S4Vectors::isEmpty(sims)] %>% unlist()
172s 5. │ ├─S4Vectors::isEmpty(sims)
172s 6. │ └─S4Vectors::isEmpty(sims)
172s 7. │ └─base::vapply(x, isEmpty, logical(1L))
172s 8. │ ├─S4Vectors (local) FUN(X[[i]], ...)
172s 9. │ └─S4Vectors (local) FUN(X[[i]], ...)
172s 10. └─base::unlist(.)
172s
172s [ FAIL 3 | WARN 275 | SKIP 0 | PASS 280 ]
173s Error: Test failures
173s Execution halted

Bug#1070841: r-bioc-iranges: autopkgtest regression with r-base 4.4.0

[Graham Inggs]

Source: r-bioc-iranges
Version: 2.36.0-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-bioc-iranges' autopkgtest regresses when tested with r-base 4.4.0
[1].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-iranges/testing/amd64/


194s ***
194s Number of test functions: 98
194s Number of errors: 1
194s Number of failures: 0
194s
194s
194s 1 Test Suite :
194s IRanges RUnit Tests - 98 test functions, 1 error, 0 failures
194s ERROR in test_AtomicList_numerical: Error in FUN(X[[i]], ...) :
is.atomic(y) is not TRUE
194s
194s Test files with failing tests
194s
194s test_AtomicList-utils.R
194s test_AtomicList_numerical
194s
194s
194s Warning messages:
194s 1: In recycleListElements(e1, en) :
194s Some element lengths are not multiples of their corresponding
element length in e1
194s 2: In x + y :
194s longer object length is not a multiple of shorter object length
194s 3: In recycleListElements(e1, en) :
194s Some element lengths are not multiples of their corresponding
element length in e1
194s 4: In x + y :
194s longer object length is not a multiple of shorter object length
194s Execution halted

Bug#1066721: marked as done (netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of function ‘helpme’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:52:50 +
with message-id 
and subject line Bug#1066721: fixed in netcat 1.10-48.1
has caused the Debian Bug report #1066721,
regarding netcat: FTBFS: netcat.c:1557:9: error: implicit declaration of 
function ‘helpme’ [-Werror=implicit-function-declaration]
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.)


-- 
1066721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netcat
Version: 1.10-48
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now-DLINUX 
> -DTELNET -DGAPING_SECURITY_HOLE -DIP_TOS -DDEBIAN_VERSION=\"1.10-48\" -DLINUX 
>  -o nc netcat.c 
> netcat.c:33:33: warning: "/*" within comment [-Wcomment]
>33 | /* #undef _POSIX_SOURCE /* might need this for something? */
>   |  
> netcat.c:36:33: warning: "/*" within comment [-Wcomment]
>36 | /* #define ANAL /* if you want case-sensitive DNS 
> matching */
>   |  
> netcat.c:62:33: warning: "/*" within comment [-Wcomment]
>62 | /* #define POSIX_SETJMP /* If you want timeouts to work under 
> the */
>   |  
> netcat.c:609:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   609 | doexec (fd)
>   | ^~
> netcat.c: In function ‘dolisten’:
> netcat.c:877:46: warning: pointer targets in passing argument 3 of 
> ‘getsockname’ differ in signedness [-Wpointer-sign]
>   877 | rr = getsockname (nnetfd, (SA *) lclend, );
>   |  ^~
>   |  |
>   |  int *
> In file included from netcat.c:73:
> /usr/include/x86_64-linux-gnu/sys/socket.h:117:47: note: expected ‘socklen_t 
> * restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
>   117 | socklen_t *__restrict __len) __THROW;
>   | ~~^
> netcat.c:904:63: warning: pointer targets in passing argument 6 of ‘recvfrom’ 
> differ in signedness [-Wpointer-sign]
>   904 | (nnetfd, bigbuf_net, BIGSIZ, MSG_PEEK, (SA *) remend, );
>   |   ^~
>   |   |
>   |   int *
> In file included from /usr/include/x86_64-linux-gnu/sys/socket.h:343:
> /usr/include/x86_64-linux-gnu/bits/socket2.h:62:56: note: expected ‘socklen_t 
> * restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
>62 |   __SOCKADDR_ARG __addr, socklen_t *__restrict __addr_len)
>   |  ~~^~
> netcat.c:929:40: warning: pointer targets in passing argument 3 of ‘accept’ 
> differ in signedness [-Wpointer-sign]
>   929 | rr = accept (nnetfd, (SA *)remend, );
>   |^~
>   ||
>   |int *
> /usr/include/x86_64-linux-gnu/sys/socket.h:307:42: note: expected ‘socklen_t 
> * restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
>   307 |socklen_t *__restrict __addr_len);
>   |~~^~
> netcat.c:956:60: warning: pointer targets in passing argument 5 of 
> ‘getsockopt’ differ in signedness [-Wpointer-sign]
>   956 |   rr = getsockopt (nnetfd, IPPROTO_IP, IP_OPTIONS, optbuf, );
>   |^~
>   ||
>   |  

Bug#1070769: marked as done (nbdkit: BD-Uninstallable on armel: linux-image-marvell)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:52:42 +
with message-id 
and subject line Bug#1070769: fixed in nbdkit 1.38.2-2
has caused the Debian Bug report #1070769,
regarding nbdkit: BD-Uninstallable on armel: linux-image-marvell
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.)


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

>From https://buildd.debian.org/status/package.php?p=nbdkit:

Dependency installability problem for nbdkit on armel:

nbdkit build-depends on missing:
- linux-image-marvell:armel

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: nbdkit
Source-Version: 1.38.2-2
Done: Hilko Bengen 

We believe that the bug you reported is fixed in the latest version of
nbdkit, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated nbdkit 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: Fri, 10 May 2024 12:38:26 +0200
Source: nbdkit
Architecture: source
Version: 1.38.2-2
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Closes: 1070769
Changes:
 nbdkit (1.38.2-2) unstable; urgency=medium
 .
   * Allow -rpi kernel to be used for running tests on armel (Closes: #1070769)
Checksums-Sha1:
 fe07eb06987144128eb5ec570a1bc9cace4124ff 3718 nbdkit_1.38.2-2.dsc
 bb920431d82098a5a73bcd0cfe7b81553019d621 11688 nbdkit_1.38.2-2.debian.tar.xz
 105e8df571f845b57365122fcf081e14830f1c75 16936 nbdkit_1.38.2-2_source.buildinfo
Checksums-Sha256:
 699d0db9a04dc0010317bccba0be721c72ac554cd196904b62613c9cd19722cf 3718 
nbdkit_1.38.2-2.dsc
 6ea95ca7b66b632c64864832cbd1ee124ff3f5939b694184f0a7b5c7f05e84c9 11688 
nbdkit_1.38.2-2.debian.tar.xz
 e97d7b6e35f863cbe4024bcd9980c22eca8f2a3fd0abfa07c14c97b8a42e0c55 16936 
nbdkit_1.38.2-2_source.buildinfo
Files:
 13719b1324bac2892a097c1bead72bb6 3718 admin optional nbdkit_1.38.2-2.dsc
 c70eb3a9795ebf13ae1df94aa1f9cc07 11688 admin optional 
nbdkit_1.38.2-2.debian.tar.xz
 328e1ae226ee84400edaab7c1e75bdfb 16936 admin optional 
nbdkit_1.38.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmY9+VsACgkQdbcQY1wh
On6aPBAAlAP0tubiubTI21ADlZO4af8xewzXdEwZwOqUBXqBEY9iSI5YIHL0O7Hd
AifNQ5IbgAvl3DJgn5M6mdnS8T9prerz+nwezsBzczpJnJm5DcnTlN51RBffG8qW
H0WlfuV3KF6B4HmgCV4l8PwmbUChgYuf64yOY4WWlQ87v+pq5fCHv9pwi9puIFDR
X9Y76DL6RTSR5qreEJfL0VQ/R7bEThyICFp9fWQN+z6nY/CvyW3c2xWJoTw6VRVv
TbyffrM5Fcfx2DMXa2QD6mG0u8BOnxPkaW41gNcx0k4dFgt3y3ggo7lozweeJLT7
AtiDrein6bBYgHJgnYNiFwUxcS9vW2CESdU6ZAQelAfzba+NxYy5vqAv/cKtwazM
H+uLr/cL6JZT7aW8ojf/vlApFZi7WeCTbgVKnYFufZrfWfOa9BV2vvtRZfJhEW+l
n7Z53XSfzzebtIg5ABDIldpUglvEyIDUg6dJysnc5YHaDwUNcunqIU41nfl76hlq
6br3IF8JxN96zQwjkS4xDojKk1pfkyHzEUnf/qbGR1dISpMy29NMjrif5dVWlpoT
YCibU0yozC+YPHT5Q9Uahb7kQA6ycXiHBNXNm0BPmPXa12bz3rQk4e0g+iJ7s3Hd
SjGdmm35aEMYpXckvA9otU2XgMV22ZM72zeSCBVC25vJ3u6CeRk=
=ejU/
-END PGP SIGNATURE-



pgpyRfKjMFhUL.pgp
Description: PGP signature
--- End Message ---

Bug#1070840: r-cran-ff: autopkgtest regression with r-base 4.4.0

[Graham Inggs]

Source: r-cran-ff
Version: 4.0.12+ds-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-cran-ff's autopkgtest regresses when tested with r-base 4.4.0 [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-ff/testing/amd64/


42s ══ Failed tests

42s ── Failure ('test-zero_lengths.R:34:3'): file size is correct when
creating ff integer from scratch ──
42s file.exists(f1) is not TRUE
42s
42s `actual`: FALSE
42s `expected`: TRUE
42s
42s [ FAIL 1 | WARN 52 | SKIP 0 | PASS 965 ]
42s Error: Test failures
42s Execution halted

Bug#1070839: r-cran-data.table: autopkgtest regression on i386

[Graham Inggs]

Source: r-cran-data.table
Version: 1.15.4+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-cran-data.table's autopkgtest has regressed on i386 [1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-data.table/testing/i386/


104s Test 2150.025 produced 0 warnings but expected 1
104s Expected: datetimes before 1902 may not be accurate: warns once per session
104s Observed:
109s
109s Fri May 10 06:13:18 2024 endian==little, sizeof(long double)==12,
longdouble.digits==64, sizeof(pointer)==4, TZ==unset,
Sys.timezone()=='Etc/UTC',
Sys.getlocale()=='LC_CTYPE=C.UTF-8;LC_NUMERIC=C;LC_TIME=C.UTF-8;LC_COLLATE=C.UTF-8;LC_MONETARY=C.UTF-8;LC_MESSAGES=C.UTF-8;LC_PAPER=C.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C.UTF-8;LC_IDENTIFICATION=C',
l10n_info()=='MBCS=TRUE; UTF-8=TRUE; Latin-1=FALSE; codeset=UTF-8',
getDTthreads()=='OpenMP version (_OPENMP)==201511;
omp_get_num_procs()==2; R_DATATABLE_NUM_PROCS_PERCENT==unset (default
50); R_DATATABLE_NUM_THREADS==unset; R_DATATABLE_THROTTLE==unset
(default 1024); omp_get_thread_limit()==2147483647;
omp_get_max_threads()==2; OMP_THREAD_LIMIT==unset;
OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 1
threads with throttle==1024. See ?setDTthreads.', zlibVersion()==1.3
ZLIB_VERSION==1.3
109s Error: 1 error(s) out of 9702. Search tests/tests.Rraw.bz2 for
test number(s) 2150.025. Duration: 35.0s elapsed (34.1s cpu).
109s Execution halted

Bug#1070833: marked as done (evolution: Failed to load module: /usr/lib/evolution/modules/module-rss.so)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:34:41 +
with message-id 
and subject line Bug#1070833: fixed in evolution 3.52.1-3
has caused the Debian Bug report #1070833,
regarding evolution: Failed to load module: 
/usr/lib/evolution/modules/module-rss.so
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.)


-- 
1070833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: evolution
Version: 3.52.1-1
Severity: serious

Hello,

When starting evolution, I see the following messages in the terminal:

(process:20505): e-data-server-WARNING **: 09:48:19.447: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
Failed to load module: /usr/lib/evolution/modules/module-rss.so

(evolution:20505): camel-CRITICAL **: 09:48:19.525: camel_provider_list: Could 
not load /usr/lib/evolution-data-server/camel-providers/libcamelrss.so: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory

It seems that libcamelrss.so is loading libevolution-rss-common.so but
the file is installed in evolution-dev instead of libevolution.

Please move that file

Kind regards,
Laurent Bigonville

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

Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: evolution
Source-Version: 3.52.1-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
evolution, 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 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated evolution 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: Fri, 10 May 2024 06:19:45 -0400
Source: evolution
Built-For-Profiles: noudeb
Architecture: source
Version: 3.52.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1070833
Launchpad-Bugs-Fixed: 2061744
Changes:
 evolution (3.52.1-3) unstable; urgency=medium
 .
   * Move libevolution-rss-common.so to libevolution package (Closes: #1070833)
 (LP: #2061744)
Checksums-Sha1:
 c49bdcfe6f3629522932c983105d63da534655c7 3946 evolution_3.52.1-3.dsc
 1a66969386af1fdd1b94ead0c721a8c6e6af1bb0 41148 evolution_3.52.1-3.debian.tar.xz
 0ee42b9a804b49e3dcef6395f75205aa8c56a86c 18442 
evolution_3.52.1-3_source.buildinfo
Checksums-Sha256:
 32bd11eba0c7cfde4fcc3e7692f76b51399ac7bea9d46af39078b593d9919292 3946 
evolution_3.52.1-3.dsc
 8985c8563efe0f7e62ce12e88d9ab45c25d18d64a8f18bc0bbc6a418a24e6f8b 41148 
evolution_3.52.1-3.debian.tar.xz
 d4d97df10cd3a73fd0b5c47ca7ab071a714536125d1d9aae8cc63905a0cca558 18442 
evolution_3.52.1-3_source.buildinfo
Files:
 5476b2240f6f042500db6b44b61a89b4 3946 gnome optional evolution_3.52.1-3.dsc
 05199cc21e9d97a3948b84d0d6e8b827 41148 gnome optional 
evolution_3.52.1-3.debian.tar.xz
 083645328f49d60f440b896c3f1e1ae2 18442 gnome optional 
evolution_3.52.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmY99PMACgkQ5mx3Wuv+
bH3BcBAAtFzb8iyX7oNA8NZ4uQS64FVC9Ss3kfmqhdMeIJcYMLlw5hQ0ri6gnbyx
+bMAlktBvCSp3/3Sd+xXTw/s96gDANiSx6bjl7y4KFd1rQG/DvUg1IA84YYzK8lB
RWovftdLibtxUMQ4WvcQb3gP4LwcWUAbPGV2giKnFqh+Kydba6lvt/jI3yJgvSSa
tJ0V6DhispGDLKouveVjPAmqkVQAebCE8zoVZJbAsvB0RHAIQmJsBof1TUBtjjos
ZUQ11smJRyo/BECiaj1PmsXKsY6wTuIkCZOzCHqE4BDATBugMF3NCU09bzpQFdZp
KqwXx5JL0tL3cyiMB6qkq4ElOb42G5bVjGHcyfxes49hUzBOpR6pEJIq9ZPjdmYK
nlawnMS7CX8B3SzygGx3qrHc8oPxSsEuL4kHvIRl5cddCqaswuVOUX0rvuBbj9P7
6zlIo16BdcDgV9hU1adok0y3CXIh4/8Dvdv+BefswetKCA0Zkby7qipXNXfoP+lw
8DuCCKL6Vt13rL+GYtAFfXna8HXzqqAgXRj47l6qr7Bft89I/Gy/sRyJ2YwQfmI2

Bug#1070833: marked as pending in evolution

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1070833 in evolution 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/gnome-team/evolution/-/commit/4d2f69e0d05ff38984a06484fad83b82446e5408


Move libevolution-rss-common.so to libevolution package

Closes: #1070833
LP: #2061744


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1070833

Processed: Bug#1070833 marked as pending in evolution

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1070833 [src:evolution] evolution: Failed to load module: 
/usr/lib/evolution/modules/module-rss.so
Added tag(s) pending.

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

Processed: Re: how-can-i-help: undefined local variable or method autorm_header_done

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1070713 [how-can-i-help] how-can-i-help: undefined local variable or 
method autorm_header_done
Severity set to 'grave' from 'important'

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

Processed: r-cran-data.table: Update to current upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1070009 serious
Bug #1070009 {Done: Andreas Tille } [r-cran-data.table] 
r-cran-data.table: Update to current upstream
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1070838: xine-lib-1.2 FTBFS with glibc 2.38

[Adrian Bunk]

Source: xine-lib-1.2
Version: 1.2.13+hg20230710-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xine-lib-1.2=1.2.13%2Bhg20230710-2%2Bb6

...
   dh_makeshlibs -a
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libxine2-bin/DEBIAN/symbols doesn't match 
completely debian/libxine2-bin.symbols
--- debian/libxine2-bin.symbols (libxine2-bin_1.2.13+hg20230710-2+b6_amd64)
+++ dpkg-gensymbolsgeNc6J   2024-05-10 10:16:36.253605552 +
@@ -404,8 +404,8 @@
  xine_post_wire@Base 1.2.0
  xine_post_wire_audio_port@Base 1.2.0
  xine_post_wire_video_port@Base 1.2.0
- xine_private_strlcat@Base 1.2.9
- xine_private_strlcpy@Base 1.2.9
+#MISSING: 1.2.13+hg20230710-2+b6# xine_private_strlcat@Base 1.2.9
+#MISSING: 1.2.13+hg20230710-2+b6# xine_private_strlcpy@Base 1.2.9
  xine_profiler_allocate_slot@Base 1.2.0
  xine_profiler_init@Base 1.2.0
  xine_profiler_print_results@Base 1.2.0
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:43: binary-arch] Error 25

Bug#1069529: marked as done (tua: FTBFS on armhf: tua.c:614:24: error: conflicting types for ‘time’; have ‘time_t(long int *)’ {aka ‘long long int(long int *)’})

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:11:47 +
with message-id 
and subject line Bug#1069529: fixed in tua 4.3-15
has caused the Debian Bug report #1069529,
regarding tua: FTBFS on armhf: tua.c:614:24: error: conflicting types for 
‘time’; have ‘time_t(long int *)’ {aka ‘long long int(long int *)’}
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.)


-- 
1069529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tua
Version: 4.3-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> gcc -c -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -DLIBDIR=\"/etc\" 
> -I. -I.. -I../intl -I../intl -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -Wall  tua.c
> In file included from tua.h:81,
>  from tua.c:25:
> tua.c: In function ‘main’:
> tua.c:614:24: error: conflicting types for ‘time’; have ‘time_t(long int *)’ 
> {aka ‘long long int(long int *)’}
>   614 |   extern time_t EXFUN (time, (long *));
>   |^~~~
> ansidecl.h:85:41: note: in definition of macro ‘EXFUN’
>85 | #define EXFUN(name, proto)  name proto
>   | ^~~~
> In file included from /usr/include/features.h:490,
>  from 
> /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,
>  from /usr/include/string.h:26,
>  from tua.h:40:
> /usr/include/time.h:86:15: note: previous declaration of ‘time’ with type 
> ‘time_t(time_t *)’ {aka ‘long long int(long long int *)’}
>86 | extern time_t __REDIRECT_NTH (time, (time_t *__timer), __time64);
>   |   ^~
> make[2]: *** [Makefile:68: tua.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/tua_4.3-14_unstable-armhf.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=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 mark 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: tua
Source-Version: 4.3-15
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
tua, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated tua 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: Fri, 10 May 2024 10:17:32 +0100
Source: tua
Architecture: source
Version: 4.3-15
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 1069529
Changes:
 tua (4.3-15) unstable; urgency=low
 .
   * Remove spurious redeclaration of time() (closes: #1069529).
Checksums-Sha1:
 c0b4caf7994f4e1c150d8884fe469a69797b2472 1301 tua_4.3-15.dsc
 63f3a298e02240d95d87810a6e40290d95454d94 8364 tua_4.3-15.diff.gz
Checksums-Sha256:
 e5142d69e1b3e0a1f9d3e9d1cc98558d82921b7af7bf2b7854673d8163129275 1301 
tua_4.3-15.dsc
 0353b086a015d3fc553fab1ee07d92016ee23ccbb1b002c401a0a36b2429cb08 8364 
tua_4.3-15.diff.gz
Files:
 6812b0db893f46af37d737e28077832f 1301 comm extra tua_4.3-15.dsc
 08887ea817226e529762f2b912de970e 8364 comm extra tua_4.3-15.diff.gz

Bug#1012532: marked as done (inkscape: PDF import no longer works)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:11:18 +
with message-id 
and subject line Bug#969907: fixed in poppler 24.02.0-2
has caused the Debian Bug report #969907,
regarding inkscape: PDF import no longer works
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.)


-- 
969907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inkscape
Version: 1.2-1
Severity: important
X-Debbugs-Cc: gsmec...@threespeedlogic.com

Dear Maintainer,

Versions 1.2-1 and 1.1.2-3+b1 are both currently unable to import PDFs.
Searching on-line suggests that a poppler dependency was missing or disabled at
build time.

Symptoms: (lightly edited to obscure path and filename)

$ inkscape /path/to/file.pdf
PDFInput::open: error opening document: file:///path/to/file.pdf
/path/to/file.pdf:1: parser error : Start tag expected, '<' not found
%PDF-1.6
^
ink_file_open: '/path/to/file.pdf' cannot be opened!
InkscapeApplication::document_open: Failed to open: /path/to/file.pdf
ConcreteInkscapeApplication::on_open: failed to create document!


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

Kernel: Linux 5.14.0-4-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 inkscape depends on:
ii  lib2geom1.1.0  1.1-2+b1
ii  libatkmm-1.6-1v5   2.28.2-1
ii  libboost-filesystem1.74.0  1.74.0-14
ii  libc6  2.33-7
ii  libcairo-gobject2  1.16.0-5
ii  libcairo2  1.16.0-5
ii  libcairomm-1.0-1v5 1.12.2-4
ii  libcdr-0.1-1   0.1.6-2
ii  libfontconfig1 2.13.1-4.4
ii  libfreetype6   2.11.1+dfsg-1
ii  libgc1 1:8.0.6-1.1
ii  libgcc-s1  12-20220319-1
ii  libgdk-pixbuf-2.0-02.42.8+dfsg-1
ii  libglib2.0-0   2.72.0-1+b1
ii  libglibmm-2.4-1v5  2.66.2-2+b1
ii  libgomp1   12-20220319-1
ii  libgsl27   2.7.1+dfsg-3
ii  libgspell-1-2  1.9.1-4
ii  libgtk-3-0 3.24.33-1
ii  libgtkmm-3.0-1v5   3.24.5-1
ii  libharfbuzz0b  2.7.4-1
ii  libjpeg62-turbo1:2.1.2-1
ii  liblcms2-2 2.12~rc1-2
ii  libmagick++-6.q16-88:6.9.11.60+dfsg-1.3+b2
ii  libpango-1.0-0 1.50.6+ds-2
ii  libpangocairo-1.0-01.50.6+ds-2
ii  libpangoft2-1.0-0  1.50.6+ds-2
ii  libpangomm-1.4-1v5 2.46.2-1
ii  libpng16-161.6.37-3
ii  libpoppler-glib8   20.09.0-3.1
ii  libpoppler118  22.02.0-3
ii  libpotrace01.16-2
ii  libreadline8   8.1.2-1
ii  librevenge-0.0-0   0.0.4-6+b1
ii  librsvg2-common2.52.5+dfsg-3+b1
ii  libsigc++-2.0-0v5  2.10.4-2
ii  libsoup2.4-1   2.74.1-1
ii  libstdc++6 12-20220319-1
ii  libvisio-0.1-1 0.1.7-1+b1
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.7.2-2+b1
ii  libxml22.9.13+dfsg-1
ii  libxslt1.1 1.1.34-4
ii  python33.9.8-1
ii  zlib1g 1:1.2.11.dfsg-4

Versions of packages inkscape recommends:
ii  aspell   0.60.8-4
ii  fig2dev  1:3.2.8b-1
ii  imagemagick  8:6.9.11.60+dfsg-1.3+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3+b2
ii  libimage-magick-perl 8:6.9.11.60+dfsg-1.3
ii  libwmf-bin   0.2.12-5
ii  python3-lxml 4.8.0-1
ii  python3-numpy1:1.21.5-1
ii  python3-scour0.38.2-2

Versions of packages inkscape suggests:
pn  dia   
pn  inkscape-tutorials
pn  libsvg-perl   
pn  pstoedit  
pn  python3-cssselect 
ii  python3-packaging 21.3-1
pn  python3-uniconvertor  
ii  ruby  1:2.7.6

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 24.02.0-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
poppler, 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.

Bug#969907: marked as done (inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 10:11:18 +
with message-id 
and subject line Bug#969907: fixed in poppler 24.02.0-2
has caused the Debian Bug report #969907,
regarding inkscape, etc. crashing with mismatched libpoppler102 and 
libpoppler-glib8
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.)


-- 
969907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-pdf-tools-server
Version: 0.90-3+b2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Here's a script to reproduce the segfault (path needs adjusting, must
be absolute). I suspect any pdf will be the same, but I will attach
the pdf in question. I say grave because this is the first command
sent by the emacs package elpa-pdf-tools to verify the server is
working.


/usr/bin/epdfinfo <

wt8.pdf
Description: Adobe PDF document
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 24.02.0-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
poppler, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated poppler 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: Fri, 10 May 2024 05:43:01 -0400
Source: poppler
Built-For-Profiles: noudeb
Architecture: source
Version: 24.02.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Jeremy Bícha 
Closes: 969907 1042811
Changes:
 poppler (24.02.0-2) unstable; urgency=medium
 .
   * Team upload
   * Release to unstable
 .
 poppler (24.02.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
   * Update library name to libpoppler134 to match soname
   * debian/copyright: Update path of a moved file
 .
 poppler (23.12.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
   * Update library name to libpoppler133 to match soname
   * Add new symbols to symbols files
   * Build-Depend on libcurl4-gnutls-dev
 .
 poppler (23.08.0-2) experimental; urgency=medium
 .
   * Team upload
 .
   [ Jeremy Bicha ]
   * Explicitly disable gpg support for now
 .
   [ Amin Bandali ]
   * 23.08.0 upstream release addresses CVE-2023-34872 (Closes: #1042811)
   * debian/rules: Opt into LTO (to minimize symbols diff with Ubuntu)
   * Drop most optional symbols from libpoppler-qt5-1 and libpoppler-qt6-3
 .
 poppler (23.08.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release (Closes: #969907)
   * Update library name to libpoppler130 to match soname
   * Address some lintian error and warnings:
 - E: libpoppler-private-dev: depends-on-obsolete-package
   Suggests: libfreetype6-dev => libfreetype-dev
 - W: poppler source: build-depends-on-obsolete-package
   Build-Depends: libfontconfig1-dev => libfontconfig-dev
 - W: poppler source: build-depends-on-obsolete-package
   Build-Depends: libfreetype6-dev => libfreetype-dev
   * Update standards version to 4.6.2, no changes needed
   * Update minimum version of several Build-Depends and Depends
 per upstream
Checksums-Sha1:
 205a21c05b050e6986dc9fa0cebb5c3eeaad851f 3471 poppler_24.02.0-2.dsc
 0c62660f6c985f81e698fc00e081ba8efe18e61f 37852 poppler_24.02.0-2.debian.tar.xz
 581a91dd10eb51de180fa44304402a3c5a79604b 17633 
poppler_24.02.0-2_source.buildinfo
Checksums-Sha256:
 22d1380016632326f1ac979c9ad77d4f4481d7e117b67a79668633921a95d00f 3471 
poppler_24.02.0-2.dsc
 8ebe1748d6ccb30bd8b7eb50ca622bc57b5e991c8647974fa03a6d4eb2481ac5 37852 
poppler_24.02.0-2.debian.tar.xz
 4c6f8f8bd0eb44ec96d417e7b1be76a76178d540d8286d2907b361c06364fa16 17633 
poppler_24.02.0-2_source.buildinfo
Files:
 6585224b265b683ceb6c51419170664e 3471 devel optional poppler_24.02.0-2.dsc
 4bcdc0df838d1a397693d54a84837015 37852 devel optional 
poppler_24.02.0-2.debian.tar.xz
 ec221c4cb60b59e5b000e5e53d1188ad 17633 devel optional 
poppler_24.02.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1070836: rust-apple-nvram: Switch from rust-nix 0.26 to 0.27

[Jeremy Bícha]

Source: rust-apple-nvram
Version: 0.2.0-1
Severity: serious
Tags: ftbfs upstream sid
X-Debbugs-CC: andr...@fatal.se

rust-apple-nvram Depends and Build-Depends: rust-nix 0.26 but Unstable
has rust-nix 0.27 instead. I tried doing a simple version bump from
0.26 to 0.27 in the package but dh_auto_test failed.

Thank you,
Jeremy Bícha

Bug#1070747: marked as done (c-blosc2: FTBFS on ppc64el: error: implicit declaration of function ‘malloc’)

[Debian Bug Tracking System]

Your message dated Fri, 10 May 2024 09:06:09 +
with message-id 
and subject line Bug#1070747: fixed in c-blosc2 2.13.1+ds-4
has caused the Debian Bug report #1070747,
regarding c-blosc2: FTBFS on ppc64el: error: implicit declaration of function 
‘malloc’
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.)


-- 
1070747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: c-blosc2
Version: 2.13.1+ds-3
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=c-blosc2=ppc64el=2.13.1%2Bds-3=1714853092=0

cd /<>/obj-powerpc64le-linux-gnu/blosc && /usr/bin/cc 
-DUSING_CMAKE -I/<>/obj-powerpc64le-linux-gnu/blosc 
-I/<>/include -I/<>/plugins/codecs/zfp/include 
-I/<>/blosc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu99 -O2 -g -DNDEBUG 
-fPIC -fvisibility=hidden -Wall -Wextra -MD -MT 
blosc/CMakeFiles/blosc2_static.dir/directories.c.o -MF 
CMakeFiles/blosc2_static.dir/directories.c.o.d -o 
CMakeFiles/blosc2_static.dir/directories.c.o -c 
/<>/blosc/directories.c
[ 37%] Building C object 
blosc/CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o
cd /<>/obj-powerpc64le-linux-gnu/blosc && /usr/bin/cc 
-DBLOSC_SHARED_LIBRARY -DBLOSC_TESTING -DUSING_CMAKE 
-I/<>/obj-powerpc64le-linux-gnu/blosc -I/<>/include 
-I/<>/plugins/codecs/zfp/include -I/<>/blosc 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=gnu99 -O2 -g -DNDEBUG -Wall -Wextra 
-DNO_WARN_X86_INTRINSICS -MD -MT 
blosc/CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o -MF 
CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o.d -o 
CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o -c 
/<>/blosc/bitshuffle-altivec.c
/<>/blosc/bitshuffle-altivec.c: In function 
‘bshuf_trans_bit_elem_altivec’:
/<>/blosc/bitshuffle-altivec.c:370:19: error: implicit declaration 
of function ‘malloc’ [-Werror=implicit-function-declaration]
  370 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:32:1: note: include ‘’ or 
provide a declaration of ‘malloc’
   31 | #include "transpose-altivec.h"
  +++ |+#include 
   32 | 
/<>/blosc/bitshuffle-altivec.c:370:19: warning: incompatible 
implicit declaration of built-in function ‘malloc’ 
[-Wbuiltin-declaration-mismatch]
  370 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:370:19: note: include ‘’ 
or provide a declaration of ‘malloc’
/<>/blosc/bitshuffle-altivec.c:380:3: error: implicit declaration 
of function ‘free’ [-Werror=implicit-function-declaration]
  380 |   free(tmp_buf);
  |   ^~~~
/<>/blosc/bitshuffle-altivec.c:380:3: note: include ‘’ 
or provide a declaration of ‘free’
/<>/blosc/bitshuffle-altivec.c:380:3: warning: incompatible 
implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
/<>/blosc/bitshuffle-altivec.c:380:3: note: include ‘’ 
or provide a declaration of ‘free’
/<>/blosc/bitshuffle-altivec.c: In function 
‘bshuf_untrans_bit_elem_altivec’:
/<>/blosc/bitshuffle-altivec.c:583:19: warning: incompatible 
implicit declaration of built-in function ‘malloc’ 
[-Wbuiltin-declaration-mismatch]
  583 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:583:19: note: include ‘’ 
or provide a declaration of ‘malloc’
/<>/blosc/bitshuffle-altivec.c:590:3: warning: incompatible 
implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
  590 |   free(tmp_buf);
  |   ^~~~
/<>/blosc/bitshuffle-altivec.c:590:3: note: include ‘’ 
or provide a declaration of ‘free’

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: c-blosc2
Source-Version: 2.13.1+ds-4
Done: Antonio Valentino 

We believe that the bug you reported is fixed in the latest version of
c-blosc2, 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 

Bug#1070833: evolution: Failed to load module: /usr/lib/evolution/modules/module-rss.so

[Laurent Bigonville]

Source: evolution
Version: 3.52.1-1
Severity: serious

Hello,

When starting evolution, I see the following messages in the terminal:

(process:20505): e-data-server-WARNING **: 09:48:19.447: module_load: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory
Failed to load module: /usr/lib/evolution/modules/module-rss.so

(evolution:20505): camel-CRITICAL **: 09:48:19.525: camel_provider_list: Could 
not load /usr/lib/evolution-data-server/camel-providers/libcamelrss.so: 
libevolution-rss-common.so: cannot open shared object file: No such file or 
directory

It seems that libcamelrss.so is loading libevolution-rss-common.so but
the file is installed in evolution-dev instead of libevolution.

Please move that file

Kind regards,
Laurent Bigonville

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

Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: fixed 1067657 in frameworkintegration/5.115.0-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1067657 frameworkintegration/5.115.0-2
Bug #1067657 {Done: Patrick Franz } 
[src:frameworkintegration] B-D: libqt5widgets5, blocking time64 rebuilds
Marked as fixed in versions frameworkintegration/5.115.0-2.
> thanks
Stopping processing here.

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

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Jussi Pakkanen]

On Thu, 9 May 2024 at 19:51, Shmerl  wrote:

> Do you think it's worth it it to file the bug to rust
> upstream too: https://github.com/rust-lang/rust/issues
> May be wider Rust developers can have an insight.
> Or it's something very Debian specific?

I don't use Rust, but I would imagine that if someone manages to
replicate the issue with an up to date rustup or whatever it is that
that people use to get their up to date toolchain, then it might make
sense to for them to report it upstream.