Bug#1051090: emacsql: FTBFS: 5 unexpected results
control: tags -1 patch Hi, I have prepare a patch set that sync to the latest head version that fixes the test failures. The patch set also contains upstream patches, and Debian related work starts from 0043-Update-changelog-for-new-upstream-3.1.1-git20230417..patch. Thanks, and PTAL! emacsql-patches.tar.xz Description: application/xz -- Manphiz
Processed: Re: emacsql: FTBFS: 5 unexpected results
Processing control commands: > tags -1 patch Bug #1051090 [src:emacsql] emacsql: FTBFS: 5 unexpected results Added tag(s) patch. -- 1051090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037636: marked as done (dyssol: ftbfs with GCC-13)
Your message dated Mon, 04 Sep 2023 04:18:58 +
with message-id
and subject line Bug#1037636: fixed in dyssol 1.1.1+ds1-2
has caused the Debian Bug report #1037636,
regarding dyssol: ftbfs with GCC-13
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.)
--
1037636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dyssol
Version: 1.1.1+ds1-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/dyssol_1.1.1+ds1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
18 | enum class ESolverTypes : uint32_t
| ^
| ::
/<>/BaseSolvers/BaseSolver.h:18:12: error: ‘ESolverTypes’ has not
been declared
18 | enum class ESolverTypes : uint32_t
|^~~~
/<>/BaseSolvers/BaseSolver.h:19:1: error: expected unqualified-id
before ‘{’ token
19 | {
| ^
/<>/BaseSolvers/BaseSolver.h:42:9: error: ‘ESolverTypes’ does not
name a type
42 | ESolverTypes m_type{ ESolverTypes::SOLVER_NONE }; // Type
of the solver (SOLVER_AGGLOMERATION_1/SOLVER_PBM_1/...).
| ^~~~
/<>/BaseSolvers/BaseSolver.h:58:9: error: ‘ESolverTypes’ does not
name a type
58 | ESolverTypes GetType() const;
| ^~~~
/<>/BaseSolvers/BaseSolver.cpp:6:1: error: ‘ESolverTypes’ does not
name a type
6 | ESolverTypes CBaseSolver::GetType() const
| ^~~~
make[3]: *** [CMakeFiles/libdyssol_static.dir/build.make:93:
CMakeFiles/libdyssol_static.dir/BaseSolvers/BaseSolver.cpp.o] Error 1
make[3]: Leaving directory '/<>/debian/build'
make[2]: *** [CMakeFiles/Makefile2:233: CMakeFiles/libdyssol_static.dir/all]
Error 2
/<>/ModelsAPI/UnitParameters.h:274:9: error: ‘ESolverTypes’ does
not name a type
274 | ESolverTypes m_solverType; ///< Solver's type.
| ^~~~
/<>/ModelsAPI/UnitParameters.h:279:75: error: ‘ESolverTypes’ has
not been declared
279 | CSolverUnitParameter(std::string _name, std::string
_description, ESolverTypes _type);
|
^~~~
/<>/ModelsAPI/UnitParameters.h:284:9: error: ‘ESolverTypes’ does
not name a type
284 | ESolverTypes GetSolverType() const; ///< Returns solver's
type.
| ^~~~
/<>/ModelsAPI/UnitParameters.h:288:28: error: ‘ESolverTypes’ has
not been declared
288 | void SetSolverType(ESolverTypes _type); ///< Sets solver's type.
|^~~~
/<>/ModelsAPI/UnitParameters.h:438:92: error: ‘ESolverTypes’ has
not been declared
438 | void AddSolverParameter(const std::string& _name, const
std::string& _description, ESolverTypes _type);
|
^~~~
make[3]: *** [Units/CMakeFiles/Agglomerator.dir/build.make:79:
Units/CMakeFiles/Agglomerator.dir/Agglomerator/Agglomerator.cpp.o] Error 1
make[3]: Leaving directory '/<>/debian/build'
make[2]: *** [CMakeFiles/Makefile2:285: Units/CMakeFiles/Agglomerator.dir/all]
Error 2
[ 6%] Linking CXX shared library libGranulator.so
cd /<>/debian/build/Units && /usr/bin/cmake -E cmake_link_script
CMakeFiles/Granulator.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat
Bug#1051181: more info
# id test uid=1001(test) gid=1001(test) groups=1001(test),1003(),1004(zzz2), 1005(test2),1006(test6),1007(test7),1008(test8),1009(test9),1010(test10), 1011(test11),1012(test12),1013(test13),1014(test14),1015(test15),1016(test16), 1017(test17),1018(test18),1019(test19) The above is the test user I used for compiling. The real use case was a user in a corporate network with 30+ groups from Active Directory. This sort of AD configuration is increasingly common and should work. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/
Bug#1051181: FTBFS: can't build package when user has more than 16 supplementary groups
Package: fapolicyd
Version: 1.1.7-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
# TOTAL: 2
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: gid_proc_test
===
./gid_proc_test: Too many groups
FAIL gid_proc_test (exit status: 1)
Above are the relevant parts of the compile output when trying to build it by a
user with more than 16 supplementary groups.
Below is the patch to fix this:
Index: fapolicyd-1.1.7/src/tests/gid_proc_test.c
===
--- fapolicyd-1.1.7.orig/src/tests/gid_proc_test.c
+++ fapolicyd-1.1.7/src/tests/gid_proc_test.c
@@ -2,6 +2,7 @@
#include
#include
#include
+#include
#include
#include "attr-sets.h"
#include "process.h"
@@ -9,7 +10,7 @@
int main(void)
{
int res, num, i, check_intersect = 0;
- gid_t gid, gids[16];
+ gid_t gid, gids[NGROUPS_MAX];
attr_sets_entry_t *groups = get_gid_set_from_pid(getpid());
gid = getgid();
@@ -17,7 +18,7 @@ int main(void)
if (!res)
error(1, 0, "Group %d not found", gid);
- num = getgroups(16, gids);
+ num = getgroups(NGROUPS_MAX, gids);
if (num < 0)
error(1, 0, "Too many groups");
-- System Information:
Debian Release: trixie/sid
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Bug#1050680: marked as done (yubikey-luks: Depends on removed package cryptsetup-run)
Your message dated Mon, 04 Sep 2023 00:33:56 + with message-id and subject line Bug#1050680: fixed in yubikey-luks 0.5.1+29.g5df2b95-6.2 has caused the Debian Bug report #1050680, regarding yubikey-luks: Depends on removed package cryptsetup-run 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.) -- 1050680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yubikey-luks Version: 0.5.1+29.g5df2b95-6.1 Severity: serious Hi, cryptsetup-run has been a transitional package since the buster release, and has now been removed following #1038285. Looks like I failed to properly check reverse depends; yubikey-luks should replace ‘Depends: cryptsetup-run’ with ‘Depends: cryptsetup’. Cheers, -- Guilhem. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: yubikey-luks Source-Version: 0.5.1+29.g5df2b95-6.2 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of yubikey-luks, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated yubikey-luks 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: Mon, 28 Aug 2023 01:59:49 +0200 Source: yubikey-luks Architecture: source Version: 0.5.1+29.g5df2b95-6.2 Distribution: unstable Urgency: medium Maintainer: Debian Authentication Maintainers Changed-By: Guilhem Moulin Closes: 1050680 Changes: yubikey-luks (0.5.1+29.g5df2b95-6.2) unstable; urgency=medium . * Non-maintainer upload. * Replace ‘Depends: cryptsetup-run’ with ‘Depends: cryptsetup’ as src:cryptsetup no longer ships the former (Closes: #1050680) Checksums-Sha1: b1f16466dd87f63ed3246da8086d087300a1b3c2 2109 yubikey-luks_0.5.1+29.g5df2b95-6.2.dsc b3aa926f6801e29d808b0c401b6e2e322f92e819 5368 yubikey-luks_0.5.1+29.g5df2b95-6.2.debian.tar.xz f5f16bf7318ade7fbe5d08c8408132ce7dc4a59e 6026 yubikey-luks_0.5.1+29.g5df2b95-6.2_amd64.buildinfo Checksums-Sha256: 4b4219c3085fe7ae6a85073b8498f45a7e5ed395fb76eb5cf51b66e8499d9302 2109 yubikey-luks_0.5.1+29.g5df2b95-6.2.dsc b6cc6974391b23af7057ace31703695b98674e0c5df5ec29f2371785908edaef 5368 yubikey-luks_0.5.1+29.g5df2b95-6.2.debian.tar.xz 5326818c86090a9981ffdc7fe4ebedff67f6694f1e11174ffa198ffe0b66 6026 yubikey-luks_0.5.1+29.g5df2b95-6.2_amd64.buildinfo Files: dfa4eb2705619f4b32348d541e1e8f8a 2109 admin optional yubikey-luks_0.5.1+29.g5df2b95-6.2.dsc 64cca03980d7df58b94ea31c3bcaac47 5368 admin optional yubikey-luks_0.5.1+29.g5df2b95-6.2.debian.tar.xz 8ef06718aef28a6681c8e535624a523c 6026 admin optional yubikey-luks_0.5.1+29.g5df2b95-6.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmTr4/sACgkQ05pJnDwh pVLXRQ//fQhvatCskCs20fW6JYo9zhHGdzkRprdaiTaxyYK/z2UDCkQu+61xtzbn mlTaB12YlyaV2OBp57/Kf/DjKZQv1MX8Qe5wics1WtJwka3QZcoFCvnVsBtTfBRy tee26mPf5nTEDcrcDT6B8m4vMlkfAKCbas2tKWAKufMo2C1LF4VDlhMtBjNg4F0d STgY2y89rQyZWRFDahs0NsIF/6OWnhxIm1oWM7K7negQehN+Z6QKPmoZlE9ABqbH /LUYcEA2H8WtcX4houKAjnNs/XPC2BNgVycL1aFNWC2zfFOZU3/HQbSg1LXV0tRr FsbiVJ1O72+3WbHkBJX2iVtX3S8ZxM5pElcsP4KeWxtZjdBIuhzYUOiS6V8jQe+9 V2e8BrVV61H9blgp8erVqrtnIzQ3CY3F5zg2bzKRG7zUCHK9h/j9aPRZZZRmGcWw xedoTh7eA5wxcICHdajwPhTaF8wvuvkyCr0hxTkAQhZZDKEGov074haKuZ6oL4oD WvEsPoUmUMy+4YsV7jAL1yoFduZnbZOkvDwra1eghBJkWjftqg31hNLNxsCfJDxH g5Q3UAE388b1OpSXo0kVRnpH02w3Fx4V/aJFR9w2QvRc+nmtzkhIQJWt952eNzyE Bo44grarPKCtU2sojaE1NGPu/51ZYdgf1pPEnUp4lFkL1v12BFI= =aJA9 -END PGP SIGNATURE End Message ---
Bug#1050256: autopkgtest fails on debci
Am 03.09.23 um 10:50 schrieb Paul Gevers: Hi, On 03-09-2023 02:56, Michael Biebl wrote: ng? Do the debci maintainers / lxc maintainers / release team have any preference regarding a/, b/ and c/ ? One part of me likes the ci.d.n infrastructure to run stable as an example of "eat your own dogfood". Another part of me agrees with Antonio that it makes sense if it would run a backports kernel to be as close as possible to testing as we can reasonably (maintenance wise) can get. Because we have a known issue at hand, the balance goes to backports for me. If Antonio doesn't beat me to it, I'll get to it (although I don't know yet how to do that in our configuration [1] and exclude riscv64 too). I have manually upgraded the s390x host and rebooted, so that can serve as a test arch. Seems it worked, the latest run succeeded: https://ci.debian.net/data/autopkgtest/testing/s390x/s/systemd/37374052/log.gz Thanks! OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1041508: tex-common: fmutil fails to rebuild formats
On 03.09.2023 07:20, Paul Gevers wrote: Hello Paul, I've just added an ignore hint for texlive-extra, as the r-bioc-biocstyle issue is clearly less of a problem than this one (and bug reports are filed). Thanks for your response! When will the ignore hint be effective? Hilmar -- sigfault
Bug#1043336: closing 1043336
close 1043336 thanks binNMUs scheduled. Cheers
Processed: closing 1043336
Processing commands for cont...@bugs.debian.org: > close 1043336 Bug #1043336 [collectd] collectd: Recommends unavailable package "libgps28" Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1043336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1043336
Processing commands for cont...@bugs.debian.org: > tags 1043336 + sid trixie Bug #1043336 [collectd] collectd: Recommends unavailable package "libgps28" Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1044138
Processing commands for cont...@bugs.debian.org: > tags 1044138 + sid trixie Bug #1044138 [src:pcmanx-gtk2] RM: pcmanx-gtk2 -- RoQA; dead upstream; depends on gtk2 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1044138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1043523
Processing commands for cont...@bugs.debian.org: > tags 1043523 + sid trixie Bug #1043523 [src:bitmeter] RM: bitmeter -- RoQA; unmaintained; depends on gtk2 Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1045144
Processing commands for cont...@bugs.debian.org:
> tags 1045144 + sid trixie
Bug #1045144 {Done: Olek Wojnar } [src:grpc-java] grpc-java:
binary-any FTBFS with recent jdupes
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1045144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1045688
Processing commands for cont...@bugs.debian.org:
> tags 1045688 + sid trixie
Bug #1045688 {Done: Christian Kastner } [src:rocm-device-libs]
FTBFS: Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR)
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1045688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1049380
Processing commands for cont...@bugs.debian.org: > tags 1049380 + sid trixie Bug #1049380 [src:gliv] RM: gliv -- RoQA; unmaintained; depends on gtk2 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1049380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1043510
Processing commands for cont...@bugs.debian.org: > tags 1043510 + sid trixie Bug #1043510 [src:rox] RM: rox -- RoQA; dead upstream; depends on gtk2 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1051144: reportbug: tex-common fails to install due to fmtutil error
Processing control commands: > reassign -1 texlive-binaries Bug #1051144 [tex-common] reportbug: tex-common fails to install due to fmtutil error Bug reassigned from package 'tex-common' to 'texlive-binaries'. No longer marked as found in versions tex-common/6.18. Ignoring request to alter fixed versions of bug #1051144 to the same values previously set > severity -1 serious Bug #1051144 [texlive-binaries] reportbug: tex-common fails to install due to fmtutil error Severity set to 'serious' from 'normal' > merge -1 1051080 Bug #1051144 [texlive-binaries] reportbug: tex-common fails to install due to fmtutil error Bug #1051144 [texlive-binaries] reportbug: tex-common fails to install due to fmtutil error Marked as found in versions texlive-bin/2023.20230311.66589-3. Bug #1051080 [texlive-binaries] texlive-binaries: Failed tex-common fmtutil trigger Merged 1051080 1051144 -- 1051080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051080 1051144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1042965
Processing commands for cont...@bugs.debian.org:
> tags 1042965 + sid trixie
Bug #1042965 {Done: Sandro Tosi } [src:py7zr] py7zr: Remove
unneeded build-depends on deprecate pep517
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1042869
Processing commands for cont...@bugs.debian.org:
> tags 1042869 + sid trixie
Bug #1042869 {Done: Andreas Tille } [src:sniffles] sniffles:
Please update to newer version without python3-pep517 requirement
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1049330, tagging 1049331, tagging 1050028, tagging 1050168, tagging 1050182, tagging 1050183 ...
Processing commands for cont...@bugs.debian.org:
> tags 1049330 + sid trixie
Bug #1049330 [python3-seqdiag] python3-seqdiag: fails with Pil 10
Added tag(s) trixie and sid.
> tags 1049331 + sid trixie
Bug #1049331 [python3-blockdiag] python3-blockdiag: fails with Pil 10
Added tag(s) trixie and sid.
> tags 1050028 + sid trixie
Bug #1050028 {Done: Jonas Smedegaard } [src:rust-tokio-rustls]
rust-tokio-rustls: recent upgrade breaks reverse dependencies: keep from
testing till resolved
Added tag(s) trixie and sid.
> tags 1050168 + sid trixie
Bug #1050168 {Done: Shengjing Zhu } [src:kxd] FTBFS:
test_no_local_cert: tlsv13 alert certificate required
Added tag(s) sid and trixie.
> tags 1050182 + sid trixie
Bug #1050182 [python3-sage] python3-sage: depends on obsolete pcre3 library
Added tag(s) sid and trixie.
> tags 1050183 + sid trixie
Bug #1050183 [src:httest] httest: depends on obsolete pcre3 library
Added tag(s) sid and trixie.
> tags 1050184 + sid trixie
Bug #1050184 {Done: Bastian Germann } [src:libgetdata]
libgetdata: depends on obsolete pcre3 library
Added tag(s) trixie and sid.
> tags 1050187 + sid trixie
Bug #1050187 [src:mvdsv] mvdsv: depends on obsolete pcre3 library
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1049330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049330
1049331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049331
1050028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050028
1050168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050168
1050182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050182
1050183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050183
1050184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050184
1050187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): tagging 1050671, tagging 1050676, tagging 1050683, tagging 105024, tagging 1050522, tagging 1050521 ...
Processing commands for cont...@bugs.debian.org:
> tags 1050671 + sid trixie
Bug #1050671 [src:zabbix] zabbix: FTBFS: malformed import path "[cmd/compile]":
invalid char '['
Added tag(s) sid and trixie.
> tags 1050676 + sid trixie
Bug #1050676 [src:enblend-enfuse] enblend-enfuse: FTBFS: dot: maze.c:311:
chkSgraph: Assertion `np->cells[0]' failed.
Added tag(s) sid and trixie.
> tags 1050683 + sid trixie
Bug #1050683 [src:pep517] pep517: Should not be released with Trixie
Added tag(s) trixie and sid.
> tags 105024 + sid trixie
Failed to alter tags of Bug 105024: Not altering archived bugs; see unarchive.
> tags 1050522 + sid trixie
Bug #1050522 {Done: Axel Beckert } [src:wdm] wdm: FTBFS: fatal
error: pango/pango.h: No such file or directory
Added tag(s) trixie and sid.
> tags 1050521 + sid trixie
Bug #1050521 [mdevctl] mdevctl: FTBFS: error: failed to select a version for
the requirement `env_logger = "^0.9.0"`
Added tag(s) sid and trixie.
> tags 1050359 + sid trixie
Bug #1050359 [src:gpr] RM: gpr -- RoQA; dead upstream; depends on gtk2
Added tag(s) trixie and sid.
> tags 1050350 + sid trixie
Bug #1050350 {Done: Sean Whitton } [src:flycheck]
flycheck: keep flycheck out of testing until it finds an uploader
Bug #1050404 {Done: Sean Whitton } [src:flycheck]
flycheck: keep flycheck out of testing
Added tag(s) sid and trixie.
Added tag(s) sid and trixie.
> tags 1050366 + sid trixie
Bug #1050366 {Done: Gianfranco Costamagna }
[src:opencolorio] opencolorio: FTBFS with newer yaml-cpp [PATCH]
Added tag(s) sid and trixie.
> tags 1050399 + sid trixie
Bug #1050399 [src:starplot] RM: starplot -- RoQA; low popcon; depends on gtk2
Added tag(s) sid and trixie.
> tags 1050459 + sid trixie
Bug #1050459 {Done: David Bremner } [elpa-buttercup]
elpa-buttercup: FTBFS with Emacs 29.1
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1050350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050350
1050359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050359
1050366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050366
1050399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050399
1050404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050404
1050459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050459
1050521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050521
1050522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050522
1050671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050671
1050676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050676
1050683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1050902, tagging 1050952, tagging 1051029, tagging 1051031, tagging 1051070, tagging 1051081 ...
Processing commands for cont...@bugs.debian.org:
> tags 1050902 + sid trixie
Bug #1050902 {Done: Jochen Sprickerhof }
[librust-multihash-dev] librust-multihash-dev: impossible to install: depends
on missing package librust-unsigned-varint-0.5+default-dev
Added tag(s) sid and trixie.
> tags 1050952 + sid trixie
Bug #1050952 {Done: Andreas Tille } [src:r-bioc-rhdf5lib]
r-bioc-rhdf5lib: autopkgtest regression: Expected '1.10.8', got '1.10.10'
Added tag(s) sid and trixie.
> tags 1051029 + sid trixie
Bug #1051029 {Done: Philipp Kern } [src:libinfinity]
libinfinity: build-depends on old libgsasl7-dev
Added tag(s) sid and trixie.
> tags 1051031 + sid trixie
Bug #1051031 [src:libvmime] libvmime: build-depends on old libgsasl7-dev
Added tag(s) trixie and sid.
> tags 1051070 + sid trixie
Bug #1051070 [src:gtimer] RM: gtimer -- RoQA; low popcon; depends on gtk2
Added tag(s) trixie and sid.
> tags 1051081 + sid trixie
Bug #1051081 [src:dart] dart: binary-any FTBFS with recent jdupes
Added tag(s) trixie and sid.
> tags 1051090 + sid trixie
Bug #1051090 [src:emacsql] emacsql: FTBFS: 5 unexpected results
Added tag(s) sid and trixie.
> tags 1051091 + sid trixie
Bug #1051091 [src:giara] giara: FTBFS: error: Expected string or translated
string
Added tag(s) sid and trixie.
> tags 1051108 + sid trixie
Bug #1051108 [src:anjuta] anjuta: FTBFS: 1 failed unexpectedly
Added tag(s) sid and trixie.
> tags 1051109 + sid trixie
Bug #1051109 [src:gtkpod] gtkpod: Intent to request removal from Debian
Added tag(s) sid and trixie.
> tags 105 + sid trixie
Bug #105 [src:notmuch] notmuch: FTBFS: 6 tests failed.
Added tag(s) sid and trixie.
> tags 1051112 + sid trixie
Bug #1051112 [src:planetblupi] planetblupi: FTBFS: /usr/bin/ld:
/usr/lib/riscv64-linux-gnu/libSDL_kitchensink.so: undefined reference to
`av_register_all'
Added tag(s) sid and trixie.
> tags 1051154 + sid trixie
Bug #1051154 {Done: Sebastian Ramacher } [libcaca-dev]
FTBFS with doxygen 1.9.8
Added tag(s) trixie and sid.
> tags 1051158 + sid trixie
Bug #1051158 [src:aseba] aseba: FTBFS: error: ‘uint16_t’ does not name a type
Added tag(s) sid and trixie.
> tags 1051159 + sid trixie
Bug #1051159 [src:gnome-packagekit] gnome-packagekit: FTBFS:
gnome-packagekit-self-test FAIL
Added tag(s) sid and trixie.
> tags 1051160 + sid trixie
Bug #1051160 {Done: Alexis Bienvenüe }
[src:auto-multiple-choice] auto-multiple-choice: FTBFS: Error: The font "DejaVu
Serif" cannot be found.
Added tag(s) trixie and sid.
> tags 1051165 + sid trixie
Bug #1051165 [libstxxl-doc] FTBFS with doxygen 1.9.8
Added tag(s) trixie and sid.
> tags 1051174 + sid trixie
Bug #1051174 [src:clickhouse] clickhouse: build-depends on old libgsasl7-dev
Added tag(s) sid and trixie.
> tags 1051175 + sid trixie
Bug #1051175 [src:jabberd2] jabberd2: build-depends on old libgsasl7-dev
Added tag(s) sid and trixie.
> tags 1051176 + sid trixie
Bug #1051176 [src:jreen] jreen: build-depends on old libgsasl7-dev
Added tag(s) sid and trixie.
> tags 1051177 + sid trixie
Bug #1051177 [src:pokerth] pokerth: build-depends on old libgsasl7-dev
Added tag(s) trixie and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1050902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050902
1050952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050952
1051029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051029
1051031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051031
1051070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051070
1051081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051081
1051090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051090
1051091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051091
1051108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051108
1051109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051109
105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105
1051112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051112
1051154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051154
1051158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051158
1051159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051159
1051160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051160
1051165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051165
1051174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051174
1051175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051175
1051176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051176
1051177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1050831 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 1050831 wishlist Bug #1050831 [wrk] wrk: No manual page Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1050831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1050766, tagging 1050767
Processing commands for cont...@bugs.debian.org: > tags 1050766 + sid trixie Bug #1050766 [src:classified-ads] classified-ads: FTBFS: /usr/include/natpmp.h:52:10: fatal error: natpmp_declspec.h: No such file or directory Added tag(s) sid and trixie. > tags 1050767 + sid trixie Bug #1050767 [textedit.app] texedit.app: FTBFS: dh_install: error: missing files, aborting Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050766 1050767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050674: marked as done (ispell-czech: FTBFS: Can't exec "/<>/debian/myspell-cs.install")
Your message dated Sun, 03 Sep 2023 21:05:16 + with message-id and subject line Bug#1050674: fixed in ispell-czech 20040229-7 has caused the Debian Bug report #1050674, regarding ispell-czech: FTBFS: Can't exec "/<>/debian/myspell-cs.install" 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.) -- 1050674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ispell-czech Version: 20040229-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, ispell-czech fails to build from source: | install -o 0 -g 0 -m 644 ./czech.aff /<>/debian/tmp/usr/lib/ispell | install -o 0 -g 0 -m 644 ./czech.hash /<>/debian/tmp/usr/lib/ispell | rm -f ./czech.hash | make[1]: Leaving directory '/<>' |dh_install -a | Can't exec "/<>/debian/myspell-cs.install": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 1616. | dh_install: error: cannot run debian/myspell-cs.install: No such file or directory | make: *** [debian/rules:4: binary-arch] Error 25 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 A full build log is available: https://buildd.debian.org/status/fetch.php?pkg=ispell-czech=arm64=20040229-6=1692525149=0 Regards Aurelien --- End Message --- --- Begin Message --- Source: ispell-czech Source-Version: 20040229-7 Done: Petr Čech We believe that the bug you reported is fixed in the latest version of ispell-czech, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petr Čech (supplier of updated ispell-czech package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Sep 2023 22:50:02 +0200 Source: ispell-czech Binary: iczech myspell-cs Architecture: source amd64 all Version: 20040229-7 Distribution: unstable Urgency: medium Maintainer: Petr Čech Changed-By: Petr Čech Description: iczech - Czech dictionary for ispell myspell-cs - Czech dictionary for myspell Closes: 1050674 Changes: ispell-czech (20040229-7) unstable; urgency=medium . * Add Build-Depends: on dh-exec (closes: 1050674) Checksums-Sha1: 6d5b3c93cd2df5a4c93a6f7a57fcd5fe2b9a4dd0 1864 ispell-czech_20040229-7.dsc 1552f0e4d9b08b48b1c8e5d8238eb8421ced39ba 5572 ispell-czech_20040229-7.debian.tar.xz eae164110c9e2d2d8db411cbc45a7ba38d2f92a5 2199380 iczech_20040229-7_amd64.deb c5c83f8bd78c1495afb9e6f8ac0630c9c7e09abf 6919 ispell-czech_20040229-7_amd64.buildinfo 9a2856bb3df66981774a4dfa4b29c65d20cd32b8 772272 myspell-cs_20040229-7_all.deb Checksums-Sha256: bea20a27d544ddfd227582279e2df47e04646443ef6d55952709043773a6ef55 1864 ispell-czech_20040229-7.dsc 4a2a51a3415deef6c1c91f576d69b2575b7eba41671e8dd1a1bbccd8ede48039 5572 ispell-czech_20040229-7.debian.tar.xz 6b1a44f45089df4f08a5aa9d8b689a6d779e43280f70ed2c6243c2478d5d936e 2199380 iczech_20040229-7_amd64.deb bab77e2738f1140386d6a66e3a1f262e0b848ea05cdc69f86505e153d36dd1f6 6919 ispell-czech_20040229-7_amd64.buildinfo f30bebc8f443c95c976830ee75e31a52a08ec8d507c9563972dbe56dfcb27e0a 772272 myspell-cs_20040229-7_all.deb Files: 6e79804ad5d321e8dc0d4cdbc665fbd0 1864 text optional ispell-czech_20040229-7.dsc fdf30d1261c25cbe543cb128704ce388 5572 text optional ispell-czech_20040229-7.debian.tar.xz a4324165a65576eb50551e4ac2b071d9 2199380 text optional iczech_20040229-7_amd64.deb 0961b6c65f4e0e191410f35ec3fa6457 6919 text optional ispell-czech_20040229-7_amd64.buildinfo 58d57aa58396f25895669c78182abbb6 772272 text optional myspell-cs_20040229-7_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE3zMMbuIBef/SspMK9oK57rnpnPgFAmT08h8ACgkQ9oK57rnp nPgn9A//c/lwx3eLn9dpryIbWE11dl9j05E5F0uayOM48DeQmXj/fCZZxds4ucs1 L90ZNu+l1jGZZh0WBrkyzA3Re/iqH3SqGdtaQWxx3obGMeES5d2APqvu6Q6kI/VD 2w4rLSjV/FsJtrKtiZPw5WyBxxd87GlhhU9eQk8zQ1tGn3kUCR+O+RMaeLrUO+8/ 3RcODvHl8Jio2QxdScuCEiwhrUaEWChFpzfvj4x36A8FSb8rfe/mzPFEkcoNRK5K wfE+OH43gFCk9vJeRhM43yzgRnD5G/NJS415m7BF0PyIqMAdOaikqhcCNF3FpjHM
Bug#1050525: marked as done (elan: FTBFS: error: failed to select a version for the requirement `dirs = "^4.0.0"`)
Your message dated Sun, 03 Sep 2023 20:50:46 +
with message-id
and subject line Bug#1050525: fixed in elan 2.0.0-2
has caused the Debian Bug report #1050525,
regarding elan: FTBFS: error: failed to select a version for the requirement
`dirs = "^4.0.0"`
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.)
--
1050525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elan
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
elan fails to build from source. From my build log on amd64:
|dh_auto_test -a -O--buildsystem=cargo
| debian cargo wrapper: options, profiles, parallel: ['parallel=12'] [] ['-j12']
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
'-j12', '--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `dirs = "^4.0.0"`
| candidate versions found which didn't match: 5.0.1
| location searched: directory source `/<>/debian/cargo_registry`
(which is replacing registry `crates-io`)
| required by package `elan-utils v1.11.0 (/<>/src/elan-utils)`
| ... which satisfies path dependency `elan-utils` of package `elan v2.0.0
(/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:19: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=elan=riscv64=2.0.0-1=1692960457=0
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: elan
Source-Version: 2.0.0-2
Done: Christopher Hoskin
We believe that the bug you reported is fixed in the latest version of
elan, 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 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christopher Hoskin (supplier of updated elan package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 03 Sep 2023 20:59:42 +0100
Source: elan
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin
Changed-By: Christopher Hoskin
Closes: 1050525
Changes:
elan (2.0.0-2) unstable; urgency=medium
.
* Fix "FTBFS: error: failed to select a version for the requirement
`dirs = "^4.0.0"`" update dependencies (Closes: #1050525)
Checksums-Sha1:
8cfcc34e3df99788551064236db6653f5743f378 2718 elan_2.0.0-2.dsc
18df460928ee77a7b3f06ebc1f34b4427e3b78d2 5872 elan_2.0.0-2.debian.tar.xz
7bc635662a9e84f84152644baee2d59561a23a6a 18152 elan_2.0.0-2_amd64.buildinfo
Checksums-Sha256:
b0b172e10e76c887be8942bd17d15410030bdaf73a342b8737494e11c4ab3352 2718
elan_2.0.0-2.dsc
ee68aa143a69059923e7c47225879f6b7dac08ad95af3f4d4d899f802457aedc 5872
elan_2.0.0-2.debian.tar.xz
a0c238906ffcc1cdcf741bae56ac9785bca8cae327b69f8a5355e32d99c7ea9a 18152
elan_2.0.0-2_amd64.buildinfo
Files:
2e6c5ae78d7af27116497719ddb291ef 2718 math optional elan_2.0.0-2.dsc
a91b3542d83f53e982743b59766b9737 5872 math optional elan_2.0.0-2.debian.tar.xz
d3353cc59e8303ec57acec6c4a25c0b4 18152 math optional
elan_2.0.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmT05p4ACgkQf6qUsnUU
SprD+xAAoZANQ4pY8ic9ZRSsOPff1hyq4wFySStyupRFW305iQPI1R/uu/QognNF
w5Jfqns7/XPq1mwkAcGeScNwfLWqBOvsPsd5tN7l8vvkk1uLH8uQEN8PMoCIrCnZ
gVpy4gLo9fdX4AqH0yUkfkO/PKBhA9Ad/RyliD/LwcVoIg2ksgA3C7uClPq3Q3xP
F3ZUFUju9IE8EtnrxLQlZEXDiqNZ9fowqB7gb+VfIuVD8oFHe2UEBS/5/3jcAsvH
VoWWcW9dIe45qY+GQliNcRQ33ELdHlJKEJV4Va0kB+r/ur8I9Do89wX10y2WTMiO
So2vSOu0Us+MqRzBI/gjq2MeVFae1RA7ywKydZt9ikR/GjXflr1V/bqlh+zRfydx
kABOaJIX8UWBWBGsigxBtkrZVmKfqrN+eWS3VUQ4Uxc+km7z3yNIRc1S1LWCdOZz
kmXu4fHIEOKTWO4oh6YvtipId4tNHVA8eqbpweV6O3ijk2DKVZ3/rIV3jFQO86Vq
Bug#1051154: marked as done (FTBFS with doxygen 1.9.8)
Your message dated Sun, 03 Sep 2023 20:51:24 +
with message-id
and subject line Bug#1051154: fixed in libcaca 0.99.beta20-4
has caused the Debian Bug report #1051154,
regarding FTBFS with doxygen 1.9.8
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.)
--
1051154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcaca-dev
Version: 0.99.beta20-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the
past)
X-Debbugs-Cc: paolo.gre...@libpf.com
While preparing to upload doxygen 1.9.8, I did a partial rebuild of
packages that build-depend on it.
More info here:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial
Of 510 packages I tried, 6 failed and one is libcaca-dev.
The build error was:
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! TeX capacity exceeded, sorry [text input levels=15].
\tabu@textbar ...ar \m@ne \scantokens {\def \:{|}}
\expandafter
\endgroup \ex...
l.46 \begin{DoxyParams}{Parameters}
^^M
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.
Here is how much of TeX's memory you used:
18690 strings out of 477695
304727 string characters out of 5831649
1925759 words of memory out of 500
38172 multiletter control sequences out of 15000+60
560241 words of font info for 97 fonts, out of 800 for 9000
14 hyphenation exceptions out of 8191
101i,15n,117p,1820b,797s stack positions out of
1i,1000n,2p,20b,20s
! ==> Fatal error occurred, no output PDF file produced!
make[3]: *** [Makefile:663: stamp-latex] Error 1
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libcaca-dev depends on:
ii libcaca0 0.99.beta20-3
ii libslang2-dev 2.3.3-3
libcaca-dev recommends no packages.
libcaca-dev suggests no packages.
-- no debconf information
libcaca_0.99.beta20-3.xz
Description: application/xz
--- End Message ---
--- Begin Message ---
Source: libcaca
Source-Version: 0.99.beta20-4
Done: Sebastian Ramacher
We believe that the bug you reported is fixed in the latest version of
libcaca, 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 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated libcaca package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 03 Sep 2023 22:34:35 +0200
Source: libcaca
Architecture: source
Version: 0.99.beta20-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 1051154
Changes:
libcaca (0.99.beta20-4) unstable; urgency=medium
.
* debian/: Do not build PDF documentation (Closes: #1051154)
* debian/control:
- Bump Standards-Version
- Replace pkg-config with pkgconf
Checksums-Sha1:
f10e9c47ac9a698599fd9571ffd200ba63f7edac 1625 libcaca_0.99.beta20-4.dsc
f17b94e6c806b92e43e39cd8ea750ee7466219f4 10456
libcaca_0.99.beta20-4.debian.tar.xz
Checksums-Sha256:
21b3eee7a636400ccd3969dfa729fc716d0a9b09b90919df6cad9296c35a69b8 1625
libcaca_0.99.beta20-4.dsc
f090a54e20440cd8d440bcc3dbb9181bfbff01414954698b83c5e3f71f7ea309 10456
libcaca_0.99.beta20-4.debian.tar.xz
Files:
04ce357901dc5f1be75b3cec92d1b648 1625 libs optional libcaca_0.99.beta20-4.dsc
1c7cd0c947b71bdea5b7d40ff218b9e0 10456 libs optional
Bug#1051160: marked as done (auto-multiple-choice: FTBFS: Error: The font "DejaVu Serif" cannot be found.)
Your message dated Sun, 03 Sep 2023 20:49:50 +
with message-id
and subject line Bug#1051160: fixed in auto-multiple-choice 1.6.0-2
has caused the Debian Bug report #1051160,
regarding auto-multiple-choice: FTBFS: Error: The font "DejaVu Serif" cannot be
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.)
--
1051160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: auto-multiple-choice
Version: 1.6.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
auto-multiple-choice fails to build from source. From my build log on
amd64:
| rsvg-convert -f pdf img_src/warning.svg -o img_pdf/warning.pdf
| set -e ; xelatex -halt-on-error -interaction=nonstopmode
auto-multiple-choice.en.tex; xelatex -halt-on-error -interaction=nonstopmode
auto-multiple-choice.en.tex
| This is XeTeX, Version 3.141592653-2.6-0.95 (TeX Live 2023/Debian)
(preloaded format=xelatex)
| restricted \write18 enabled.
| entering extended mode
| (./auto-multiple-choice.en.tex
| LaTeX2e <2023-06-01>
| L3 programming layer <2023-06-05>
| (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
| Document Class: article 2023/05/17 v1.4n Standard LaTeX document class
| (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
| (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifxetex.sty
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-xetex.def)))
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
| (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
| (/usr/share/texlive/texmf-dist/tex/xelatex/xltxtra/xltxtra.sty
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifluatex.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/metalogo/metalogo.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/xetex.def)
|
| ! Package fontspec Error: The font "DejaVu Serif" cannot be found.
|
| For immediate help type H .
| ...
|
| l.23 \setsansfont
| {DejaVu Sans}
| No pages of output.
| Transcript written on auto-multiple-choice.en.log.
| make[3]: *** [Makefile:73: auto-multiple-choice.en.pdf] Error 1
| rm img_pdf/important.pdf img_pdf/warning.pdf auto-multiple-choice.en.tex
img_pdf/note.pdf
| make[3]: Leaving directory '/<>/doc'
| make[2]: *** [Makefile:165: doc] Error 2
| rm icons/auto-multiple-choice.png
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:118: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true"
returned exit code 2
| make: *** [debian/rules:8: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=auto-multiple-choice=riscv64=1.6.0-1=1693738582=0
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: auto-multiple-choice
Source-Version: 1.6.0-2
Done: Alexis Bienvenüe
We believe that the bug you reported is fixed in the latest version of
auto-multiple-choice, 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 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexis Bienvenüe (supplier of updated auto-multiple-choice
package)
(This message was generated automatically at their request; if you
believe that there is a
Bug#1051177: pokerth: build-depends on old libgsasl7-dev
Source: pokerth Version: 1.1.2-2 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1051176: jreen: build-depends on old libgsasl7-dev
Source: jreen Version: 1.2.0+ds-1 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1051175: jabberd2: build-depends on old libgsasl7-dev
Source: jabberd2 Version: 2.7.0-4 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1051174: clickhouse: build-depends on old libgsasl7-dev
Source: clickhouse Version: 18.16.1+ds-7.3 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1037837: marked as done (rdkit: ftbfs with GCC-13)
Your message dated Sun, 03 Sep 2023 19:46:08 + with message-id and subject line Bug#1037837: fixed in rdkit 202303.3-1 has caused the Debian Bug report #1037837, regarding rdkit: ftbfs with GCC-13 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.) -- 1037837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rdkit Version: 202209.3-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/rdkit_202209.3-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] from /<>/Code/RDGeneral/types.h:27, from /<>/Code/RDGeneral/types.cpp:12: /<>/Code/RDGeneral/RDLog.h:131:8: error: ‘uint64_t’ in namespace ‘std’ does not name a type; did you mean ‘wint_t’? 131 | std::uint64_t d_origState = 0; |^~~~ |wint_t In file included from /<>/Code/RDGeneral/RDLog.cpp:10: /<>/Code/RDGeneral/RDLog.h:131:8: error: ‘uint64_t’ in namespace ‘std’ does not name a type; did you mean ‘wint_t’? 131 | std::uint64_t d_origState = 0; |^~~~ |wint_t /<>/Code/RDGeneral/RDLog.cpp: In constructor ‘RDLog::LogStateSetter::LogStateSetter()’: /<>/Code/RDGeneral/RDLog.cpp:36:7: error: ‘d_origState’ was not declared in this scope 36 | d_origState |= 1 << i; | ^~~ /<>/Code/RDGeneral/RDLog.cpp: In constructor ‘RDLog::LogStateSetter::LogStateSetter(RDLog::RDLoggerList)’: /<>/Code/RDGeneral/RDLog.cpp:46:7: error: ‘d_origState’ was not declared in this scope 46 | d_origState ^= 1 << i; | ^~~ /<>/Code/RDGeneral/RDLog.cpp: In destructor ‘RDLog::LogStateSetter::~LogStateSetter()’: /<>/Code/RDGeneral/RDLog.cpp:55:36: error: ‘d_origState’ was not declared in this scope 55 | (*allLogs[i])->df_enabled ^= d_origState >> i & 1; |^~~ [ 5%] Building CXX object External/GA/CMakeFiles/ga.dir/util/RandomUtil.cpp.o cd /<>/obj-x86_64-linux-gnu/External/GA && /usr/bin/c++ -DBOOST_SERIALIZATION_DYN_LINK -DRDKIT_DYN_LINK -DRDK_64BIT_BUILD -DRDK_BUILD_COORDGEN_SUPPORT -DRDK_BUILD_DESCRIPTORS3D -DRDK_BUILD_MAEPARSER_SUPPORT -DRDK_BUILD_THREADSAFE_SSS -DRDK_HAS_EIGEN3 -DRDK_TEST_MULTITHREADED -DRDK_USE_BOOST_SERIALIZATION -DRDK_USE_STRICT_ROTOR_DEFINITION -Dga_EXPORTS -I/<>/External -I/usr/include/python3.11 -I/usr/lib/python3/dist-packages/numpy/core/include -I/<>/Code -isystem /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated -Wno-unused-function -fno-strict-aliasing -Wall -Wextra -fPIC -fPIC -std=gnu++17 -MD -MT External/GA/CMakeFiles/ga.dir/util/RandomUtil.cpp.o -MF CMakeFiles/ga.dir/util/RandomUtil.cpp.o.d -o CMakeFiles/ga.dir/util/RandomUtil.cpp.o -c /<>/External/GA/util/RandomUtil.cpp In file included from /<>/Code/RDGeneral/Invariant.h:22, from /<>/Code/RDGeneral/types.h:27, from /<>/Code/RDGeneral/utils.h:15, from /<>/Code/RDGeneral/utils.cpp:10: /<>/Code/RDGeneral/RDLog.h:131:8: error: ‘uint64_t’ in namespace ‘std’ does not name a type; did you mean ‘wint_t’? 131 | std::uint64_t d_origState = 0; |^~~~ |wint_t make[4]: *** [Code/RDGeneral/CMakeFiles/RDGeneral.dir/build.make:135:
Bug#1050462: gtg: crashes on startup often
Hi Antonio, > We probably want to fix the code to *not* segfault when the workaround > is not in place. Agreed! > I'm not sure whether this is a bug in gtg itself, or > in pango. The issue is likely in the g_object_get_property or in pango_font_description_to_string, or in the code calling both methods in GTG/gtk/general_preferences.py For now, I've followed the upstream advice to revert the behavior to get a default font when font_name is not available, hence by-passing the two problematic methods. I've just committed the patch [1], and I'll likely upload a new package shortly to prevent package removal. Let me know if this sounds acceptable to you. Best, François [1] https://salsa.debian.org/python-team/packages/gtg/-/commit/e9ac644f40629704a4e85b56ff887a59d6748d58 signature.asc Description: This is a digitally signed message part
Processed: closing 1050805
Processing commands for cont...@bugs.debian.org: > # fixed upstream in 10.0.2 > close 1050805 1:10.0.2-1 Bug #1050805 [dhcpcd-base] dhcpcd-base: DoS: zero-length packet cause eventual lease expiration Marked as fixed in versions dhcpcd/1:10.0.2-1. Bug #1050805 [dhcpcd-base] dhcpcd-base: DoS: zero-length packet cause eventual lease expiration Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1050805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#877016: Time to drop cpufrequtils?
Processing commands for cont...@bugs.debian.org: > severity 877016 serious Bug #877016 [cpufrequtils] Time to drop cpufrequtils? Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 877016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051154: FTBFS with doxygen 1.9.8
Control: tags -1 moreinfo unreproducible
On 2023-09-03 17:50:52 +0200, Paolo Greppi wrote:
> Package: libcaca-dev
> Version: 0.99.beta20-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
> past)
> X-Debbugs-Cc: paolo.gre...@libpf.com
>
> While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages
> that build-depend on it.
> More info here:
> https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial
>
> Of 510 packages I tried, 6 failed and one is libcaca-dev.
>
> The build error was:
>
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.
>
> ! TeX capacity exceeded, sorry [text input levels=15].
> \tabu@textbar ...ar \m@ne \scantokens {\def \:{|}}
> \expandafter \endgroup
> \ex...
> l.46 \begin{DoxyParams}{Parameters}
> ^^M
> If you really absolutely need more capacity,
> you can ask a wizard to enlarge me.
>
>
> Here is how much of TeX's memory you used:
> 18690 strings out of 477695
> 304727 string characters out of 5831649
> 1925759 words of memory out of 500
> 38172 multiletter control sequences out of 15000+60
> 560241 words of font info for 97 fonts, out of 800 for 9000
> 14 hyphenation exceptions out of 8191
> 101i,15n,117p,1820b,797s stack positions out of
> 1i,1000n,2p,20b,20s
> ! ==> Fatal error occurred, no output PDF file produced!
> make[3]: *** [Makefile:663: stamp-latex] Error 1
>
> I attach the full build log.
I'm afraid I am unable to reproduce the issue. Any hint how to reproduce
it?
Cheers
--
Sebastian Ramacher
Processed: Re: Bug#1051154: FTBFS with doxygen 1.9.8
Processing control commands: > tags -1 moreinfo unreproducible Bug #1051154 [libcaca-dev] FTBFS with doxygen 1.9.8 Added tag(s) moreinfo and unreproducible. -- 1051154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1051162 is important
Processing commands for cont...@bugs.debian.org: > severity 1051162 important Bug #1051162 [src:netcdf] netcdf: FTBFS with doxygen 1.9.8 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1051162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051162: FTBFS with doxygen 1.9.8
On 9/3/23 18:16, Paolo Greppi wrote: While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. doxygen 1.9.8 is not in experimental, so we can't test potential fixes. When will 1.9.8 be available in the archive? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: tagging 1051162
Processing commands for cont...@bugs.debian.org: > tags 1051162 + upstream Bug #1051162 [src:netcdf] netcdf: FTBFS with doxygen 1.9.8 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1051162 to src:netcdf, found 1051162 in 1:4.9.2-1 ...
Processing commands for cont...@bugs.debian.org: > reassign 1051162 src:netcdf Bug #1051162 [netcdf-doc] FTBFS with doxygen 1.9.8 Bug reassigned from package 'netcdf-doc' to 'src:netcdf'. No longer marked as found in versions netcdf/1:4.9.2-1. Ignoring request to alter fixed versions of bug #1051162 to the same values previously set > found 1051162 1:4.9.2-1 Bug #1051162 [src:netcdf] FTBFS with doxygen 1.9.8 Marked as found in versions netcdf/1:4.9.2-1. > retitle 1051162 netcdf: FTBFS with doxygen 1.9.8 Bug #1051162 [src:netcdf] FTBFS with doxygen 1.9.8 Changed Bug title to 'netcdf: FTBFS with doxygen 1.9.8' from 'FTBFS with doxygen 1.9.8'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051166: FTBFS with doxygen 1.9.8
Package: breathe-doc Version: 4.35.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More info here: https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial Of 510 packages I tried, 6 failed and one is breathe-doc. The build error was: Exception occurred while building, starting debugger: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 281, in build_main app.build(args.force_all, args.filenames) File "/usr/lib/python3/dist-packages/sphinx/application.py", line 341, in build self.builder.build_update() File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 310, in build_update self.build(to_build, File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py", line 325, in build with logging.pending_warnings(): File "/usr/lib/python3.11/contextlib.py", line 144, in __exit__ next(self.gen) File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 218, in pending_warnings memhandler.flushTo(logger) File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 183, in flushTo logger.handle(record) File "/usr/lib/python3.11/logging/__init__.py", line 1644, in handle self.callHandlers(record) File "/usr/lib/python3.11/logging/__init__.py", line 1706, in callHandlers hdlr.handle(record) File "/usr/lib/python3.11/logging/__init__.py", line 974, in handle rv = self.filter(record) ^^^ File "/usr/lib/python3.11/logging/__init__.py", line 830, in filter result = f.filter(record) File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 426, in filter raise exc sphinx.errors.SphinxWarning: /<>/documentation/source/specific.rst:195:Invalid C++ declaration: Expected identifier in nested name. [error at 0] ^ > /usr/lib/python3/dist-packages/sphinx/util/logging.py(426)filter() -> raise exc (Pdb) make[3]: *** [Makefile:56: html] Error 2 I attach the full build log. Paolo -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages breathe-doc depends on: ii libjs-mathjax2.7.9+dfsg-1 ii libjs-sphinxdoc 5.3.0-7 breathe-doc recommends no packages. breathe-doc suggests no packages. -- no debconf information breathe_4.35.0-2.xz Description: application/xz
Bug#1051165: FTBFS with doxygen 1.9.8
Package: libstxxl-doc
Version: 1.4.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the
past)
X-Debbugs-Cc: paolo.gre...@libpf.com
While preparing to upload doxygen 1.9.8, I did a partial rebuild of
packages that build-depend on it.
More info here:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial
Of 510 packages I tried, 6 failed and one is libstxxl-doc.
The build error was:
! LaTeX Error: File `topics.tex' not found.
Type X to quit or to proceed,
or enter new name. (Default extension: tex)
Enter file name:
! Emergency stop.
l.211 \input{topics}
^^M
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libstxxl-doc depends on:
ii libjs-jquery 3.6.1+dfsg+~3.5.14-1
libstxxl-doc recommends no packages.
libstxxl-doc suggests no packages.
-- no debconf information
libstxxl_1.4.1-3.xz
Description: application/xz
Bug#1051162: FTBFS with doxygen 1.9.8
Package: netcdf-doc Version: 1:4.9.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More info here: https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial Of 510 packages I tried, 6 failed and one is netcdf-doc. The build error was: /<>/docs/dispatch.md:392: error: Unexpected subsubsection command found inside section! (warning treated as error, aborting now) make[3]: *** [docs/CMakeFiles/doc_all.dir/build.make:74: docs/CMakeFiles/doc_all] Error 1 I attach the full build log. Paolo -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information netcdf_1:4.9.2-1.xz Description: application/xz
Bug#1051160: auto-multiple-choice: FTBFS: Error: The font "DejaVu Serif" cannot be found.
Source: auto-multiple-choice
Version: 1.6.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
auto-multiple-choice fails to build from source. From my build log on
amd64:
| rsvg-convert -f pdf img_src/warning.svg -o img_pdf/warning.pdf
| set -e ; xelatex -halt-on-error -interaction=nonstopmode
auto-multiple-choice.en.tex; xelatex -halt-on-error -interaction=nonstopmode
auto-multiple-choice.en.tex
| This is XeTeX, Version 3.141592653-2.6-0.95 (TeX Live 2023/Debian)
(preloaded format=xelatex)
| restricted \write18 enabled.
| entering extended mode
| (./auto-multiple-choice.en.tex
| LaTeX2e <2023-06-01>
| L3 programming layer <2023-06-05>
| (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
| Document Class: article 2023/05/17 v1.4n Standard LaTeX document class
| (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
| (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifxetex.sty
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
| (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-xetex.def)))
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
| (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
| (/usr/share/texlive/texmf-dist/tex/xelatex/xltxtra/xltxtra.sty
| (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifluatex.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/realscripts/realscripts.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/metalogo/metalogo.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
| (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
| (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/xetex.def)
|
| ! Package fontspec Error: The font "DejaVu Serif" cannot be found.
|
| For immediate help type H .
| ...
|
| l.23 \setsansfont
| {DejaVu Sans}
| No pages of output.
| Transcript written on auto-multiple-choice.en.log.
| make[3]: *** [Makefile:73: auto-multiple-choice.en.pdf] Error 1
| rm img_pdf/important.pdf img_pdf/warning.pdf auto-multiple-choice.en.tex
img_pdf/note.pdf
| make[3]: Leaving directory '/<>/doc'
| make[2]: *** [Makefile:165: doc] Error 2
| rm icons/auto-multiple-choice.png
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:118: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true"
returned exit code 2
| make: *** [debian/rules:8: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=auto-multiple-choice=riscv64=1.6.0-1=1693738582=0
Regards
Aurelien
Bug#1051159: gnome-packagekit: FTBFS: gnome-packagekit-self-test FAIL
Source: gnome-packagekit Version: 43.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, gnome-packagekit fails to build from source due to an issue in the testsuite. From my build log on amd64: | xvfb-run dh_auto_test | cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 meson test | ninja: Entering directory `/<>/obj-x86_64-linux-gnu' | ninja: no work to do. | 1/1 gnome-packagekit-self-test FAIL0.22s killed by signal 5 SIGTRAP | >>> MALLOC_PERTURB_=101 /<>/obj-x86_64-linux-gnu/src/gpk-self-test | | | Ok: 0 | Expected Fail: 0 | Fail: 1 | Unexpected Pass:0 | Skipped:0 | Timeout:0 | | Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt | cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt | ==> meson-logs/testlog.txt <== | Log of Meson test suite run on 2023-09-03T10:39:44.785950 | | Inherited environment: DEB_HOST_GNU_SYSTEM=linux-gnu DFLAGS=-frelease DEB_BUILD_ARCH_BITS=64 DEB_TARGET_GNU_CPU=x86_64 DEB_HOST_ARCH_OS=linux USER=aurel32 CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_MULTIARCH=x86_64-linux-gnu OBJCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' DH_INTERNAL_OPTIONS=-a DEB_BUILD_ARCH_CPU=amd64 DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_ABI=base HOME=/<>/debian/.debhelper/generated/_source/home APT_CONFIG=/var/lib/sbuild/apt.conf SCHROOT_CHROOT_NAME=sid-amd64-sbuild DEB_BUILD_ARCH_ENDIAN=little LDFLAGS=-Wl,-z,relro DEB_TARGET_ARCH_BITS=64 DEB_BUILD_GNU_SYSTEM=linux-gnu MAKEFLAGS=w SCHROOT_UID=1000 DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_CPU=amd64 LOGNAME=aurel32 DEB_BUILD_ARCH_LIBC=gnu DEB_BUILD_ARCH_ABI=base DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DH_INTERNAL_OVERRIDE=dh_auto_test DEB_HOST_GNU_CPU=x86_64 LC_COLLATE=C.UTF-8 DEB_TARGET_GNU_SYSTEM=linux-gnu PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_TARGET_ARCH_OS=linux CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' MAKELEVEL=2 DEB_HOST_MULTIARCH=x86_64-linux-gnu SOURCE_DATE_EPOCH=1668444324 FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' SCHROOT_SESSION_ID=sid-amd64-sbuild-de330d22-e06b-4bad-9ea9-b7730d412354 SCHROOT_COMMAND='dpkg-buildpackage --sanitize-env -us -uc -mAurelien Jarno -eAurelien Jarno -B -rfakeroot' DISPLAY=:99 OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' LANG=fr_FR.UTF-8 SCHROOT_ALIAS_NAME=sid-amd64-sbuild DEB_TARGET_ARCH_LIBC=gnu DEB_TARGET_ARCH_ABI=base XAUTHORITY=/tmp/xvfb-run.G9VJQT/Xauthority DEB_BUILD_OPTIONS=parallel=1 SCHROOT_GROUP=aurel32 SCHROOT_USER=aurel32 CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' DH_INTERNAL_BUILDFLAGS=1 SHELL=/bin/sh DEB_HOST_ARCH_BITS=64 DEB_BUILD_ARCH=amd64 DEB_BUILD_GNU_CPU=x86_64 ASFLAGS='' DEB_HOST_GNU_TYPE=x86_64-linux-gnu LC_ALL=C.UTF-8 DEB_HOST_ARCH_CPU=amd64 DEB_RULES_REQUIRES_ROOT=no PWD=/<> FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' DEB_BUILD_MULTIARCH=x86_64-linux-gnu SCHROOT_GID=1000 MFLAGS=-w GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' DEB_HOST_ARCH_ENDIAN=little DEB_TARGET_ARCH=amd64 XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-f0RupSXS DEB_PYTHON_INSTALL_LAYOUT=deb MESON_TESTTHREADS=1 | | 1/1 = | test: gnome-packagekit-self-test | start time: 10:39:44 | duration: 0.22s | result: killed by signal 5 SIGTRAP | command: MALLOC_PERTURB_=101 /<>/obj-x86_64-linux-gnu/src/gpk-self-test | --- stdout --- | TAP version 13 | # random seed: R02S25cbff34a39c57c81b4b9d67ffa07155 | 1..2 | # Start of gnome-packagekit tests | not ok /gnome-packagekit/enum - GnomePackageKit-FATAL-WARNING: group unrecognized: 35 | Bail out! | == | | | Summary of Failures: | | 1/1 gnome-packagekit-self-test FAIL0.22s killed by signal 5 SIGTRAP | | Ok: 0 | Expected Fail: 0 | Fail: 1 | Unexpected Pass:0 | Skipped:0 | Timeout:0 | dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb
Bug#1051158: aseba: FTBFS: error: ‘uint16_t’ does not name a type
Source: aseba Version: 1.6.99+dfsg-7 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, aseba fails to build from source. From my build log on amd64: | [ 2%] Building CXX object aseba/common/CMakeFiles/asebacommon.dir/msg/TargetDescription.cpp.o | cd /<>/obj-x86_64-linux-gnu/aseba/common && /usr/bin/c++ -DASEBA_ASSERT -I/<>/aseba -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -fPIC -MD -MT aseba/common/CMakeFiles/asebacommon.dir/msg/TargetDescription.cpp.o -MF CMakeFiles/asebacommon.dir/msg/TargetDescription.cpp.o.d -o CMakeFiles/asebacommon.dir/msg/TargetDescription.cpp.o -c /<>/aseba/common/msg/TargetDescription.cpp | In file included from /<>/aseba/common/msg/TargetDescription.cpp:20: | /<>/aseba/common/msg/TargetDescription.h:88:17: error: ‘uint16_t’ does not name a type |88 | uint16_t crc() const; | | ^~~~ | /<>/aseba/common/msg/TargetDescription.h:26:1: note: ‘uint16_t’ is defined in header ‘’; did you forget to ‘#include ’? |25 | #include | +++ |+#include |26 | | /<>/aseba/common/msg/TargetDescription.cpp:26:18: error: no declaration matches ‘uint16_t Aseba::TargetDescription::crc() const’ |26 | uint16_t TargetDescription::crc() const | | ^ | /<>/aseba/common/msg/TargetDescription.cpp:26:18: note: no functions named ‘uint16_t Aseba::TargetDescription::crc() const’ | /<>/aseba/common/msg/TargetDescription.h:39:16: note: ‘struct Aseba::TargetDescription’ defined here |39 | struct TargetDescription | |^ | make[3]: *** [aseba/common/CMakeFiles/asebacommon.dir/build.make:163: aseba/common/CMakeFiles/asebacommon.dir/msg/TargetDescription.cpp.o] Error 1 | make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' | make[2]: *** [CMakeFiles/Makefile2:993: aseba/common/CMakeFiles/asebacommon.dir/all] Error 2 | make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' | make[1]: *** [Makefile:169: all] Error 2 | make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' | dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 | make: *** [debian/rules:18: build-arch] Error 25 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 A full build log on riscv64 is also available: https://buildd.debian.org/status/fetch.php?pkg=aseba=riscv64=1.6.99%2Bdfsg-7=1693729588=0 Regards Aurelien
Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl
On 2023-09-03 17:48, Niko Tyni wrote: > Control: reassign -1 libc6-dev 2.37-2 > Control: found -1 2.36-9+deb12u1 > Control: tag -1 bookworm > > On Mon, Aug 28, 2023 at 11:46:14PM +0200, Aurelien Jarno wrote: > > > > I think it's an ABI breakage that should be fixed, but just reverting > > > the patch will break the case without -D_FILE_OFFSET_BITS=64. I'll check > > > with upstream and try to get the issue fixed in both testing/sid and > > > stable. I'll keep you updated. In the meantime feel free to reassign the > > > bug to the glibc. > > > > I have opened a bug upstream: > > https://sourceware.org/bugzilla/show_bug.cgi?id=30804 > > > > And submitted a possible patch: > > https://sourceware.org/pipermail/libc-alpha/2023-August/151199.html > > Many thanks! I'm reassigning this. Hope I got the versions right. > > Looks like the discussion upstream has quieted down now. I have submitted the v3 of the patch and I am waiting for it to be rebuilt: https://sourceware.org/pipermail/libc-alpha/2023-August/151273.html Unfortunately upstream does not consider it as an ABI breakage on the glibc side, just an API breakage. But it causes an ABI breakage on the perl side. > My understanding is that for sid/trixie we'll just need a binNMU of perl > on ppc64el afterwards. I'll request that once glibc has the fix. I believe so (well probably on all architectures for multiarch sync). > For stable I don't think anything needs to be done on the perl side. > Both perl and libfile-fcntllock-perl were build with the old constants > before the regression. So just fixing glibc should be enough. I agree. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1051156: FTBFS with doxygen 1.9.8
Package: seqan-raptor-doc Version: 3.0.1+ds-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More info here: https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial Of 510 packages I tried, 6 failed and one is seqan-raptor-doc. The build error was: xelatex refman This is XeTeX, Version 3.141592653-2.6-0.95 (TeX Live 2023/Debian) (preloaded format=xelatex) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2023-06-01> L3 programming layer <2023-06-05> make[2]: *** [Makefile:12: refman.pdf] Error 1 I attach the full build log. Paolo -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information seqan-raptor_3.0.1+ds-3.xz Description: application/xz
Bug#1050902: closing 1050902
close 1050902 0.19.0-1 thanks
Processed: closing 1050902
Processing commands for cont...@bugs.debian.org: > close 1050902 0.19.0-1 Bug #1050902 [librust-multihash-dev] librust-multihash-dev: impossible to install: depends on missing package librust-unsigned-varint-0.5+default-dev There is no source info for the package 'librust-multihash-dev' at version '0.19.0-1' with architecture '' Unable to make a source version for version '0.19.0-1' Marked as fixed in versions 0.19.0-1. Bug #1050902 [librust-multihash-dev] librust-multihash-dev: impossible to install: depends on missing package librust-unsigned-varint-0.5+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1050902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051155: FTBFS with doxygen 1.9.8
Package: wxpython-tools Version: 4.2.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: paolo.gre...@libpf.com While preparing to upload doxygen 1.9.8, I did a partial rebuild of packages that build-depend on it. More info here: https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial Of 510 packages I tried, 5 failed and one is wxpython-tools. The build error was: Running command: etg "/usr/bin/python3.11" etg/_core.py --sip --nodoc "/usr/bin/python3.11" etg/_html2.py --sip --nodoc "/usr/bin/python3.11" etg/_xml.py --sip --nodoc "/usr/bin/python3.11" etg/_xrc.py --sip --nodoc "/usr/bin/python3.11" etg/_richtext.py --sip --nodoc "/usr/bin/python3.11" etg/_stc.py --sip --nodoc "/usr/bin/python3.11" etg/_grid.py --sip --nodoc "/usr/bin/python3.11" etg/_msw.py --sip --nodoc "/usr/bin/python3.11" etg/_propgrid.py --sip --nodoc "/usr/bin/python3.11" etg/_dataview.py --sip --nodoc "/usr/bin/python3.11" etg/_glcanvas.py --sip --nodoc Traceback (most recent call last): File "/<>/etg/_glcanvas.py", line 137, in run() File "/<>/etg/_glcanvas.py", line 49, in run etgtools.parseDoxyXML(module, ITEMS) File "/<>/etgtools/__init__.py", line 91, in parseDoxyXML item = module.addElement(element) ^^ File "/<>/etgtools/extractors.py", line 1576, in addElement self.addElement(node) File "/<>/etgtools/extractors.py", line 1547, in addElement item = EnumDef(element, inClass) ^ File "/<>/etgtools/extractors.py", line 1185, in __init__ self.extract(element) File "/<>/etgtools/extractors.py", line 1189, in extract super(EnumDef, self).extract(element) File "/<>/etgtools/extractors.py", line 65, in extract if '::' in self.name: ^ TypeError: argument of type 'NoneType' is not iterable I attach the full build log. Paolo -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wxpython-tools depends on: ii python3 3.11.4-5+b1 ii python3-wxgtk4.0 4.2.1+dfsg-1 wxpython-tools recommends no packages. wxpython-tools suggests no packages. -- no debconf information wxpython4.0_4.2.1+dfsg-1.xz Description: application/xz
Bug#1051154: FTBFS with doxygen 1.9.8
Package: libcaca-dev
Version: 0.99.beta20-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the
past)
X-Debbugs-Cc: paolo.gre...@libpf.com
While preparing to upload doxygen 1.9.8, I did a partial rebuild of
packages that build-depend on it.
More info here:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.9.8+ds-1_amd64-partial
Of 510 packages I tried, 6 failed and one is libcaca-dev.
The build error was:
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! TeX capacity exceeded, sorry [text input levels=15].
\tabu@textbar ...ar \m@ne \scantokens {\def \:{|}}
\expandafter
\endgroup \ex...
l.46 \begin{DoxyParams}{Parameters}
^^M
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.
Here is how much of TeX's memory you used:
18690 strings out of 477695
304727 string characters out of 5831649
1925759 words of memory out of 500
38172 multiletter control sequences out of 15000+60
560241 words of font info for 97 fonts, out of 800 for 9000
14 hyphenation exceptions out of 8191
101i,15n,117p,1820b,797s stack positions out of
1i,1000n,2p,20b,20s
! ==> Fatal error occurred, no output PDF file produced!
make[3]: *** [Makefile:663: stamp-latex] Error 1
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libcaca-dev depends on:
ii libcaca0 0.99.beta20-3
ii libslang2-dev 2.3.3-3
libcaca-dev recommends no packages.
libcaca-dev suggests no packages.
-- no debconf information
libcaca_0.99.beta20-3.xz
Description: application/xz
Bug#1042167: marked as done (rust-multihash: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev)
Your message dated Sun, 03 Sep 2023 15:55:41 + with message-id and subject line Bug#1042167: fixed in rust-multihash 0.19.0-1 has caused the Debian Bug report #1042167, regarding rust-multihash: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-multihash Version: 0.11.4-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-blake2b-simd-0.5-dev (>= 0.5.9-~~), > librust-blake2s-simd-0.5-dev (>= 0.5.9-~~), librust-digest-0.9-dev, > librust-sha-1-0.9-dev, librust-sha2-0.9-dev, librust-sha3-0.9-dev, > librust-unsigned-varint-0.5+default-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-blake2b-simd-0.5-dev (>= 0.5.9-~~), > librust-blake2s-simd-0.5-dev (>= 0.5.9-~~), librust-digest-0.9-dev, > librust-sha-1-0.9-dev, librust-sha2-0.9-dev, librust-sha3-0.9-dev, > librust-unsigned-varint-0.5+default-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [960 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [479 B] > Get:5 copy:/<>/apt_archive ./ Packages [551 B] > Fetched 1990 B in 0s (177 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-block-buffer-0.9+block-padding-dev : Depends: > librust-block-padding-0.2+default-dev but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-multihash_0.11.4-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=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: rust-multihash Source-Version: 0.19.0-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-multihash, 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 1042...@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-multihash 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
Processed: affects 1050349
Processing commands for cont...@bugs.debian.org: > affects 1050349 - field3d Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python bindings Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 Removed indication that 1050349 affects field3d Removed indication that 1051110 affects field3d > thanks Stopping processing here. Please contact me if you need assistance. -- 1050349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050349 1051110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1050349
Processing commands for cont...@bugs.debian.org: > affects 1050349 src:field3d Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python bindings Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 Added indication that 1050349 affects src:field3d Added indication that 1051110 affects src:field3d > thanks Stopping processing here. Please contact me if you need assistance. -- 1050349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050349 1051110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1050349
Processing commands for cont...@bugs.debian.org: > affects 1050349 field3d Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python bindings Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 Added indication that 1050349 affects field3d Added indication that 1051110 affects field3d > thanks Stopping processing here. Please contact me if you need assistance. -- 1050349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050349 1051110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050524: marked as done (solfege: binary-any FTBFS with recent jdupes)
Your message dated Sun, 03 Sep 2023 15:01:38 +
with message-id
and subject line Bug#1050524: fixed in solfege 3.23.4-12
has caused the Debian Bug report #1050524,
regarding solfege: binary-any FTBFS with recent jdupes
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.)
--
1050524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: solfege
Version: 3.23.4-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
solfege fails to build from source when building only binary-any and
not binary-all. From my build log on amd64:
| make[1]: Leaving directory '/<>'
|dh_install -a
|dh_installdocs -a
|dh_installchangelogs -a
|dh_python3 -a
| E: dh_python3 dh_python3:197: no package to act on (python3-foo or one with
${python3:Depends} in Depends)
|dh_perl -a
|debian/rules override_dh_link
| make[1]: Entering directory '/<>'
| dh_link
| jdupes -rl debian/solfege-doc/usr/share/doc
|
| could not stat dir debian/solfege-doc/usr/share/doc
| No duplicates found.
| make[1]: *** [debian/rules:30: override_dh_link] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:10: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=solfege=riscv64=3.23.4-11=1692931581=0
The return value of jdupes changed after bookworm to no longer return
success when the given paths do not exist, which causes this failure in
binary-any builds.
A possible untested patch is:
--- a/debian/rules
+++ b/debian/rules
@@ -25,6 +25,5 @@
iconv --from-code=iso-8859-1 --to-code=utf-8 --output=$$ifile
$$ifile; \
done
-override_dh_link:
- dh_link
+execute_after_dh_link-indep:
jdupes -rl debian/solfege-doc/usr/share/doc
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: solfege
Source-Version: 3.23.4-12
Done: Francois Mazen
We believe that the bug you reported is fixed in the latest version of
solfege, 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 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Francois Mazen (supplier of updated solfege package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 03 Sep 2023 15:54:35 +0200
Source: solfege
Architecture: source
Version: 3.23.4-12
Distribution: unstable
Urgency: medium
Maintainer: Francois Mazen
Changed-By: Francois Mazen
Closes: 1050524
Changes:
solfege (3.23.4-12) unstable; urgency=medium
.
[ Debian Janitor ]
* Set upstream metadata fields: Archive.
* Remove obsolete field Name from debian/upstream/metadata (already present
in
machine-readable debian/copyright).
* Fix day-of-week for changelog entry 3.11.3-1.
.
[ Francois Mazen ]
* Set Gtk version to 3.0 explicitly.
* Use execute_after_dh_link-indep target instead of override_dh_link
to work around jdupes behavior change (Closes: #1050524).
* Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
3c1405d415cffdf6e385db28393c12f72f060955 2199 solfege_3.23.4-12.dsc
772ad5e48899324caeed92552dc4d8e8fdcbe64b 16844 solfege_3.23.4-12.debian.tar.xz
26153bff2cdd70a5bf0be5c7e14665ca2cc76564 14143
solfege_3.23.4-12_source.buildinfo
Checksums-Sha256:
0b41ec5a99ae722a2ccdcaff50ffc9aa06d9b231537405ead12edf04e09e4069 2199
solfege_3.23.4-12.dsc
f8be253e1ebc3474fe8ce543e222a9b201de35df0559c50ef773cd4c5ea4979d 16844
solfege_3.23.4-12.debian.tar.xz
de35ab68695df1293d3b7e490a65c005ba4302dab41a4e447bc0d743a145be83 14143
solfege_3.23.4-12_source.buildinfo
Files:
e05f84b3378f8ca131ca9a29b145434b 2199 gnome optional solfege_3.23.4-12.dsc
497278b79bf3747495727673720774da 16844 gnome optional
solfege_3.23.4-12.debian.tar.xz
18df4bd22cd9f1dabb64e6243c7656a0 14143 gnome optional
solfege_3.23.4-12_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEEhqWr1v/bCgx/UFfTR5f6chw1HJ4FAmT0mP0QHGZyYW5jb2lz
Processed: Re: Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl
Processing control commands: > reassign -1 libc6-dev 2.37-2 Bug #1050592 [perl] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Bug reassigned from package 'perl' to 'libc6-dev'. No longer marked as found in versions perl/5.36.0-8. Ignoring request to alter fixed versions of bug #1050592 to the same values previously set Bug #1050592 [libc6-dev] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Marked as found in versions glibc/2.37-2. > found -1 2.36-9+deb12u1 Bug #1050592 [libc6-dev] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Marked as found in versions glibc/2.36-9+deb12u1. > tag -1 bookworm Bug #1050592 [libc6-dev] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Added tag(s) bookworm. -- 1050592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl
Control: reassign -1 libc6-dev 2.37-2 Control: found -1 2.36-9+deb12u1 Control: tag -1 bookworm On Mon, Aug 28, 2023 at 11:46:14PM +0200, Aurelien Jarno wrote: > > I think it's an ABI breakage that should be fixed, but just reverting > > the patch will break the case without -D_FILE_OFFSET_BITS=64. I'll check > > with upstream and try to get the issue fixed in both testing/sid and > > stable. I'll keep you updated. In the meantime feel free to reassign the > > bug to the glibc. > > I have opened a bug upstream: > https://sourceware.org/bugzilla/show_bug.cgi?id=30804 > > And submitted a possible patch: > https://sourceware.org/pipermail/libc-alpha/2023-August/151199.html Many thanks! I'm reassigning this. Hope I got the versions right. Looks like the discussion upstream has quieted down now. My understanding is that for sid/trixie we'll just need a binNMU of perl on ppc64el afterwards. I'll request that once glibc has the fix. For stable I don't think anything needs to be done on the perl side. Both perl and libfile-fcntllock-perl were build with the old constants before the regression. So just fixing glibc should be enough. -- Niko
Processed: fixed 1051111 in 0.38~rc1-1
Processing commands for cont...@bugs.debian.org: > fixed 105 0.38~rc1-1 Bug #105 [src:notmuch] notmuch: FTBFS: 6 tests failed. Marked as fixed in versions notmuch/0.38~rc1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051141: mfem: broken build system?
Source: mfem
Version: 4.5.2+ds-1.1
Severity: serious
Justification: the directories hardcoded in header file points to unexisting
locations.
Hello, I found some issues on the packaging of mfem, and I would like to see
them fixed
because I don't think the package is good for stable in this way, but feel free
to close
if you think this isn't the case!
First issue:
this is passed in configure:
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu
instead of DEB_HOST_MULTIARCH, causing a lot of pain a little bit after:
dh_fixperms
chrpath -d debian/libmfem4*/usr/lib/*-*/libmfem.so*
# one day this will also work on non x86_64-linux-gnu
# debian/libmfem-dev/usr/lib/cmake/mfem/*.cmake are with absolute wrong/build
paths
sed -i
"s,/.*/lib/.*/libmfem.so.4.5.2,/usr/lib/x86_64-linux-gnu/libmfem.so.4.5.2,g"
debian/libmfem-dev/usr/lib/cmake/mfem/MFEMTargets-*.cmake
# one day someone will fix the -ffile-prefix-map
sed -i "s,/.*/lib/.*x86_64-linux-gnu,/usr/lib/x86_64-linux-gnu,g"
debian/libmfem-dev/usr/lib/cmake/mfem/MFEMConfig.cmake
(for some reasons the DESTDIR contains the full path of the build, not the
relative one, so this causes a lot of other issues)
Second issue:
cat /usr/include/mfem/config/_config.hpp |grep build
#define MFEM_SOURCE_DIR "/build/reproducible-path/mfem-4.5.2+ds"
MFEM_SOURCE_DIR and MFEM_INSTALL_DIR are used in many places in the code, and
this will fail.
fem/ceed/interface/util.cpp: const char *install_dir = MFEM_INSTALL_DIR
"/include/mfem/fem/ceed";
fem/ceed/interface/util.cpp: MFEM_ABORT("Cannot find libCEED kernels in
MFEM_INSTALL_DIR or "
general/device.cpp: if (occa::io::exists(MFEM_INSTALL_DIR "/include/mfem/"))
general/device.cpp: mfemDir = MFEM_INSTALL_DIR "/include/mfem/";
general/device.cpp: MFEM_ABORT("Cannot find OCCA kernels in MFEM_INSTALL_DIR or
MFEM_SOURCE_DIR");
fem/ceed/interface/util.cpp: const char *source_dir = MFEM_SOURCE_DIR
"/fem/ceed";
fem/ceed/interface/util.cpp:"MFEM_SOURCE_DIR");
general/device.cpp: else if (occa::io::exists(MFEM_SOURCE_DIR))
general/device.cpp: mfemDir = MFEM_SOURCE_DIR;
general/device.cpp: MFEM_ABORT("Cannot find OCCA kernels in MFEM_INSTALL_DIR or
MFEM_SOURCE_DIR");
Third issue: the shipped cmake file looks wrong and broken (this is a good
candidate for autopkgtest :) )
cat ../CMakeLists.txt
cmake_minimum_required(VERSION 3.27)
project(foo)
find_package(MFEM)
cmake ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/lib/cmake/mfem/MFEMConfig.cmake:88 (message):
File or directory /usr/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi
referenced by variable MFEM_INCLUDE_DIR does not exist !
Call Stack (most recent call first):
/usr/lib/cmake/mfem/MFEMConfig.cmake:106 (set_and_check)
CMakeLists.txt:3 (find_package)
-- Configuring incomplete, errors occurred!
I'm stopping here, but I think we need some fixes before considering it good
enough for stable, what do you think?
Gianfranco
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1051029: marked as done (libinfinity: build-depends on old libgsasl7-dev)
Your message dated Sun, 03 Sep 2023 12:07:34 + with message-id and subject line Bug#1051029: fixed in libinfinity 0.7.2-2 has caused the Debian Bug report #1051029, regarding libinfinity: build-depends on old libgsasl7-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libinfinity Version: 0.7.2-1 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libinfinity Source-Version: 0.7.2-2 Done: Philipp Kern We believe that the bug you reported is fixed in the latest version of libinfinity, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern (supplier of updated libinfinity package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Sep 2023 13:45:54 +0200 Source: libinfinity Architecture: source Version: 0.7.2-2 Distribution: unstable Urgency: medium Maintainer: Philipp Kern Changed-By: Philipp Kern Closes: 1051029 Changes: libinfinity (0.7.2-2) unstable; urgency=medium . * Change build-dependency from libgsasl7-dev (removed) to libgsasl-dev. (Closes: #1051029) Checksums-Sha1: 044ca38c3d9ca3032b8d6edf8a9d755c52a23bf9 2223 libinfinity_0.7.2-2.dsc c3c486556059cd0c5c057f68cf310b17fa52cab4 15952 libinfinity_0.7.2-2.debian.tar.xz dae1eee5087c0ee3595d1b4d21169a5f7d3cc99e 17275 libinfinity_0.7.2-2_amd64.buildinfo Checksums-Sha256: 3c75dc58028dcd70bb106a943a0f89c05decd6c5cec3acdb00633524a2de4b43 2223 libinfinity_0.7.2-2.dsc 1b392293d46babff14f0cda73f0e1030eac55841be8a29fe634584a4d88c 15952 libinfinity_0.7.2-2.debian.tar.xz 6c7ad38e0aa5bf2db2dea96767d41a148aac74079cd20cde61dfc4d356a60270 17275 libinfinity_0.7.2-2_amd64.buildinfo Files: 467d30143f685943a0f97b67815bb0c9 2223 libs optional libinfinity_0.7.2-2.dsc 37440d8fcb419f6f807c569849690219 15952 libs optional libinfinity_0.7.2-2.debian.tar.xz e22cf11e528c2886b684373576f8298e 17275 libs optional libinfinity_0.7.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAmT0cukRHHBrZXJuQGRl Ymlhbi5vcmcACgkQRG4lRTXQVuw/NQf/XHSNJwaqU9XSGB/OeIQSCV7OMIMx3r8e lyymHKKTPraa4DoIQWcPLv3fh5odtvWtv+XzYfB7oQHrI+AZPEnoJz5Tr3H2xHGO +RlzKg1trquhjlKY3DtwTcw8vUvDGgxGt6a1abhHoKCRHQ2yO0ckpibYtTIhfujP ZxInioQfLhblSoHnNr18eSFUuG0OuwwuvP75PNBC3R41+kugqXHrMOoBS95Yfphk 9So/KjousoHqlaMBN4HUBsObH+gt4nmyUbi/jblyAHKDYLbSfSP9VbdpXihkf+cS 8/a/QuLWsZAzZfehukfS132eZj6/HS8KsTVfpl3A83v7tCwnCQDudQ== =Ne1d -END PGP SIGNATURE End Message ---
Bug#1051066: [Pkg-netatalk-devel] Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches
Quoting Daniel Markstedt (2023-09-03 08:40:35) > --- Original Message --- > On Saturday, September 2nd, 2023 at 1:33 AM, Jonas Smedegaard > wrote: > > > > > This is one bugreport about multiple issues. That easily gets confusing > > to track, e.g. if some of the issues are solved and some are not, for a > > certain release of the package (and consequently a Debian release where > > that package release is included). > > > > It is generally easier to track when instead filing one bugreport per > > issue. > > > > I can see how this is the preferred approach for a clean tracking of each > security issue. In this case it gets a bit hairy since we have cases where > one patch fixed multiple CVEs, and elsewhere multiple patches were required > to fix regressions introduced by a CVE fix. It was a journey of >1 year to > get to the present state. > > > I tried lookup one of above CVEs inn the Debian security tracker: > > https://security-tracker.debian.org/tracker/CVE-2022-43634 > > > > It references an already filed bugreport about that issue, bug#1034170, > > which is tagged as found only as early as 3.1.14~ds-1. If earlier > > Debian package releases are also affected by that particular issue, then > > please update that bugreport to reflect that fact. > > > > This bugreport is flagged as "archived" (which is done automatically > > after being done for a while, to reduce spam). Before doing other > > changes you therefore need to first unachive it. > > > > E.g. something like this: > > > > bts unarchive 1034170 . found 1034170 3.1.13~ds-1 > > > > Will do, thanks for the command. > > > The other CVEs seemingly have no related bugreport (from a quick look at > > the security tracker - but I suspect that database does not list > > bugreports not involving the security team at first, and only later > > mentioning a CVE if at all). If you don't happen to be aware of > > bugreports exisisting for those other issues, then I suggest to file new > > individual bugreports for each issue (also because it is easy to merge > > issues later as needed). > > > > That's a fairly big undertaking, especially if clean and atomic patches are > required for each... Minimal patching is required for stable releases, but it can be one patch solving 9 issues, or a combination of multiple patches solving a single issue. > I was really hoping the batch approach would be accepted. > > That said I can definitely create the individual bug tickets for starters and > we can take it from there. Let me set aside some time next week for this. I don't mean to bother you with silly paperwork. I don't mean to imply that each issue need to be *solved* separately, only that it generally is easier to *track* issues separately. E.g. it makes great sense to close several bugreports with a single patch. And if that patch turns out to not actually solve all issues then we can "reopen" or "unseen" individual bugreports as needed. If 9 issues are tracked in one bugreport, then it is not possible to structurally (only sloppily in prose) communicate if "2nd and 5th of the 9 issues reported here was not yet fixed after all"... Hope that makes sense. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1050937: protobuf: FTBFS: ModuleNotFoundError: No module named 'tzdata'
Hi, On Sat, Sep 2, 2023 at 10:33 AM Gianfranco Costamagna wrote: > Hello, probably tzdata split in legacy made this package FTBFS. Seems to be the case. > Solutions are: > 1) fix the test to work with main tzdata It's Python 3.11 itself which can't handle tzdata related things. It has a proposed patch applied for the Debian package [1] but seems not fully tested / complete. > 2) add dependency on tzdata-legacy package No, it's Python which tries to import a module that doesn't exist. Static data has nothing to do with it. Will test with the mentioned patch removed Python package version. Regards, Laszlo/GCS [1] https://tracker.debian.org/news/1458326/accepted-python311-3115-3-source-into-unstable/
Processed: Re: elpa-persp-projectile: broken with recent elpa-perspective
Processing control commands: > tags -1 patch Bug #919035 [elpa-persp-projectile] elpa-persp-projectile: broken with recent elpa-perspective Added tag(s) patch. -- 919035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919035: elpa-persp-projectile: broken with recent elpa-perspective
control: tags -1 patch I have prepared a merge request[1] as a fix. PTAL. [1] elpa-persp-projectile: broken with recent elpa-perspective -- Manphiz
Bug#1051076: dash: test does not support s1 < s2 or s1 > s2
Control: severity -1 normal Control: tag -1 wontfix On Sat, 02 Sep 2023 12:55:34 +0200 Gian Piero Carrubba wrote: dash supposedly implements test s1 < s2 and test s1 > s2 for string comparisons. A cursory glance at [0], [1] and [2] seems to confirm this. Anyway the shell redirection seems to take precedence so that the test is not actually performed. > dash $ type test test is a shell builtin $ ls -l bar ls: cannot access 'bar': No such file or directory $ test "foo" < "bar" dash: 2: cannot open bar: No such file $ test "foo" > "bar" $ ls -l bar -rw-r--r-- 1 gpiero gpiero 0 Sep 2 12:51 bar You forgot to escape the < and >: $ test foo '>' bar $ echo $? 0 $ test foo '<' bar $ echo $? 1 -- Cheers, Andrej
Processed: Re: dash: test does not support s1 < s2 or s1 > s2
Processing control commands: > severity -1 normal Bug #1051076 [dash] dash: test does not support s1 < s2 or s1 > s2 Severity set to 'normal' from 'grave' > tag -1 wontfix Bug #1051076 [dash] dash: test does not support s1 < s2 or s1 > s2 Added tag(s) wontfix. -- 1051076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051129: src:haskell-haskell-gi: fails to migrate to testing for too long: dependencies unsatisfiable
Source: haskell-haskell-gi Version: 0.26.1-1 Severity: serious Control: close -1 0.26.7-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:haskell-haskell-gi has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The migration software reports that the right dependencies are missing. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=haskell-haskell-gi OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:haskell-haskell-gi: fails to migrate to testing for too long: dependencies unsatisfiable
Processing control commands: > close -1 0.26.7-1 Bug #1051129 [src:haskell-haskell-gi] src:haskell-haskell-gi: fails to migrate to testing for too long: dependencies unsatisfiable Marked as fixed in versions haskell-haskell-gi/0.26.7-1. Bug #1051129 [src:haskell-haskell-gi] src:haskell-haskell-gi: fails to migrate to testing for too long: dependencies unsatisfiable Marked Bug as done -- 1051129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050256: autopkgtest fails on debci
Hi, On 03-09-2023 02:56, Michael Biebl wrote: My main concern is to "stop the bleeding" quickly, so to speak, especially/mainly for debci. I agree with you, but also consider that with this issue being there since ~ April 2023 we don't need to rush. I guess we have three options here: a/ upgrade the kernels to the one from backports as suggested by Antonio b/ disable apparmor confinement for lxc on debci via some debci specific configuration c/ disable apparmor confinement for lxc in bookworm via a stable upload of the lxc package That said, I would be fine with a/ and b/ as well, as this would buy us time to investigate this issue without being under the pressure of causing debci failures. What I fear a bit, is that if we do either of the three, Debian infra is not affected anymore which removes some incentive to find the root cause. Those debci failures are hard to debug and I would like to avoid having individual maintainers waste time on it. a, b, or c means that Debian maintainers don't need to dive into it anymore, but who knows which downstream project (volunteers or paid alike) will need to look into the problem in the future if we don't fix it inside packaging? Do the debci maintainers / lxc maintainers / release team have any preference regarding a/, b/ and c/ ? One part of me likes the ci.d.n infrastructure to run stable as an example of "eat your own dogfood". Another part of me agrees with Antonio that it makes sense if it would run a backports kernel to be as close as possible to testing as we can reasonably (maintenance wise) can get. Because we have a known issue at hand, the balance goes to backports for me. If Antonio doesn't beat me to it, I'll get to it (although I don't know yet how to do that in our configuration [1] and exclude riscv64 too). I have manually upgraded the s390x host and rebooted, so that can serve as a test arch. Paul [1] https://salsa.debian.org/ci-team/debian-ci-config OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: affects 1050349
Processing commands for cont...@bugs.debian.org: > affects 1050349 + src:olive-editor Bug #1050349 [libimath-dev] libimath-dev: CMake fails because of missing python bindings Bug #1051110 [libimath-dev] kimageformats: FTBFS: CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake:115 Added indication that 1050349 affects src:olive-editor Added indication that 1051110 affects src:olive-editor > thanks Stopping processing here. Please contact me if you need assistance. -- 1050349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050349 1051110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041508: tex-common: Installation fails if system is missing the set locale
On Sat, Sep 02, 2023 at 06:39:07PM +0100, Samuel Henrique wrote: > > This has happened now, every testing user is getting the following error: > """ > Building format(s) --all. > This may take some time... > fmtutil failed. Output has been stored in > /tmp/fmtutil.isqbK6Rx > Please include this file if you report a bug. Confirmed. I am seeing this on my testing boxes. ael
Processed: src:upower: fails to migrate to testing for too long: i386 autopkgtest regression
Processing control commands:
> close -1 1.90.2-4
Bug #1051127 [src:upower] src:upower: fails to migrate to testing for too long:
i386 autopkgtest regression
Marked as fixed in versions upower/1.90.2-4.
Bug #1051127 [src:upower] src:upower: fails to migrate to testing for too long:
i386 autopkgtest regression
Marked Bug as done
> block -1 by 1050436
Bug #1051127 {Done: Paul Gevers } [src:upower] src:upower:
fails to migrate to testing for too long: i386 autopkgtest regression
1051127 was not blocked by any bugs.
1051127 was not blocking any bugs.
Added blocking bug(s) of 1051127: 1050436
--
1051127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051127: src:upower: fails to migrate to testing for too long: i386 autopkgtest regression
Source: upower Version: 0.99.20-2 Severity: serious Control: close -1 1.90.2-4 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1050436 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:upower has been trying to migrate for 31 days [2]. Hence, I am filing this bug. As reported in bug 1050436, there's an autopkgtest regression on i386. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=upower OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1038910: marked as done (licenseutils: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023)
Your message dated Sun, 03 Sep 2023 07:34:40 + with message-id and subject line Bug#1038910: fixed in licenseutils 0.0.9-7 has caused the Debian Bug report #1038910, regarding licenseutils: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 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.) -- 1038910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: licenseutils Tags: trixie sid User: c...@packages.debian.org Usertags: curl-nss-deprecation X-Debbugs-Cc: samuel...@debian.org, sergi...@debian.org Control: block 1038907 by -1 Hello, This package build-depends on the NSS variant of libcurl "libcurl4-nss-dev". Curl's upstream announced support for NSS is going to be dropped in August 2023: https://curl.se/dev/deprecate.html#nss Please make sure to switch your build-dependency to something else before the due date. You might try switching to "libcurl4-openssl-dev" and in the big majority of the cases this won't cause any issues. Thank you, -- Samuel Henrique --- End Message --- --- Begin Message --- Source: licenseutils Source-Version: 0.0.9-7 Done: Fukui Daichi We believe that the bug you reported is fixed in the latest version of licenseutils, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fukui Daichi (supplier of updated licenseutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Sep 2023 05:21:43 + Source: licenseutils Architecture: source Version: 0.0.9-7 Distribution: unstable Urgency: medium Maintainer: Fukui Daichi Changed-By: Fukui Daichi Closes: 971262 1038910 Changes: licenseutils (0.0.9-7) unstable; urgency=medium . [ Fukui Daichi ] * Switch to libcurl4-openssl-dev (Closes: #1038910) * New maintainer (Closes: #971262) . [ Mattia Rizzolo ] * Bump Standards-Version to 4.6.2, no changes needed. * Fix lintian override for spelling-error-in-binary. * Update copyright years. . [ Debian Janitor ] * Remove constraints unnecessary since buster. Checksums-Sha1: bd98c793caba05620932e98bd97f20b19734e230 1975 licenseutils_0.0.9-7.dsc 24ee7c23ebfbcbfab660b91e1e7bfd3b9ed72809 6948 licenseutils_0.0.9-7.debian.tar.xz 24c34ccf58f263b2fa2c9e463a0420eecf90b1cf 8607 licenseutils_0.0.9-7_amd64.buildinfo Checksums-Sha256: afa5d64147b90611ca89db6c7a14b28332ba9d6edbba76446d26f8e7652203f1 1975 licenseutils_0.0.9-7.dsc d866e9c7674864d343d8f994e9b805ad38f99abb7dad70e6eb978c213e479b71 6948 licenseutils_0.0.9-7.debian.tar.xz 5d52e328787c8d60b504f763b8e24f78934d644168e1bcf878427ff1df470773 8607 licenseutils_0.0.9-7_amd64.buildinfo Files: 307fc1e55e3d7bbac8e0e5345bb8bf1f 1975 devel optional licenseutils_0.0.9-7.dsc c885b21de899139e7f053baffadcf3ed 6948 devel optional licenseutils_0.0.9-7.debian.tar.xz 72853d852b2542843329181dac436a2d 8607 devel optional licenseutils_0.0.9-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmT0MikACgkQCBa54Yx2 K63OHRAAlLX9xz4f8imzbsOx96RWy3H986Je/HVJvTmQg6TbKBsZ5an/+HJN4utY 85BmF4dhbS8/x6YewDK6vrcqRcqIsLeRZzbg+TSOi4GV9IXN8pHwbXCqSdaQ8/qt OHZGl8cKVZhU5rUmMaXTq1G/pVfgHSxYUoyhYWzyEikNP/V+Vn91rnRBPtJPSS+M OGhEtyxjk8x90k8RAGRWssv7NyZQgeKoSQ7tcuksL8ttQ9DZBaNVnWTFyOIB/MOe yyAFjsI961BS7cOrZ0x2YIw7N0s6B7XZ8Ajt9vY5uGLP6X95qW9w0gSdytNSBLoB OX1FS/mL+0RqjqexgDcaM7Qk4SQTBgOOOCPtZezQYNgOtWZSqOXt0s1TTsi8RPX8 Sdim71cgApCrEMLwFQ+iXOSNAME1pvCFQriwddeRRlhkRthgAKgFhDSYCvnrt5D4 8Mduw2udCnovfa/1ry0TSWDkMGpoQ3kl68tXWqf86PQgCDW0IjRPBp53ova7M7SR GwkRJGuAYDLmiopP+KIsC1WsImYOap4YcYpHXkO1c+PXDbrO8YD4AQuzUAWwWCKX Sa5XVe5TTSxRHDNCHhNXMC2E7xYn5fwRANTsBz86Rx5CBQ3zKPyDOerxc1JdIr0q 0U2Uy1ph6PDj8wXVSjOH4wbQ3BytbJ6yI8qBmYDwT+t7UErGXjE= =EnOp -END PGP SIGNATURE End Message ---
Bug#1050063: marked as done (src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Sun, 03 Sep 2023 07:19:45 + with message-id and subject line Bug#1050063: fixed in gcc-11-cross-mipsen 6+c1+nmu1 has caused the Debian Bug report #1050063, regarding src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries 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.) -- 1050063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-11-cross-mipsen Version: 5+c3 Severity: serious Control: close -1 6+c1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:gcc-11-cross-mipsen has been trying to migrate for 35 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=gcc-11-cross-mipsen OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gcc-11-cross-mipsen Source-Version: 6+c1+nmu1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of gcc-11-cross-mipsen, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated gcc-11-cross-mipsen 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, 19 Aug 2023 08:10:14 +0200 Source: gcc-11-cross-mipsen Architecture: source Version: 6+c1+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Paul Gevers Closes: 1050063 Changes: gcc-11-cross-mipsen (6+c1+nmu1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1050063) Checksums-Sha1: aee1a438e7ac576a3f949bd4561574b7f115 50174 gcc-11-cross-mipsen_6+c1+nmu1.dsc 5b8496f780643586803c4a65a673d62ca4c273ef 42716 gcc-11-cross-mipsen_6+c1+nmu1.tar.xz Checksums-Sha256: edc2dbee24be67b20c5bf2ad4e6b372717691ad5281bf9b324bea3c1f4bdfb2d 50174 gcc-11-cross-mipsen_6+c1+nmu1.dsc f90432735b596448ac894ffec5ace8bb99b82669db6ddf9d122d94ff8ee807aa 42716 gcc-11-cross-mipsen_6+c1+nmu1.tar.xz Files: 8a9beb2eca67670417d48d70c4dea553 50174 devel optional gcc-11-cross-mipsen_6+c1+nmu1.dsc c30795a828a71341af14a8e8e2d3a91e 42716 devel optional gcc-11-cross-mipsen_6+c1+nmu1.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmTgXNgACgkQnFyZ6wW9 dQpH+QgAsmaMCLdikRR6XpIrCzcyFri/MQwQnAxP4OTdTnTW1t7qTy97UuJdZI3g 397d+hsxjV4nk4+pK6Zu1whj442hOCsGkZJx+JXIaM4Q58el0pnxLL3AakGnva0P Joi6mGEg2G9NRai5GJVeGZn3UgaaKNJOyWOHKRMme4rwT7joI0Bx1hWwKePo5ax+
Processed: Bug#1038910 marked as pending in licenseutils
Processing control commands: > tag -1 pending Bug #1038910 [licenseutils] licenseutils: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 Added tag(s) pending. -- 1038910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1051080: texlive-binaries: Failed tex-common fmtutil trigger
Processing control commands: > severity -1 serious Bug #1051080 [texlive-binaries] texlive-binaries: Failed tex-common fmtutil trigger Severity set to 'serious' from 'normal' > merge -1 1041508 Bug #1051080 [texlive-binaries] texlive-binaries: Failed tex-common fmtutil trigger Unable to merge bugs because: blockedby of #1041508 is '1050807' not '' Failed to merge 1051080: Did not alter merged bugs. -- 1041508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041508 1051080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038910: marked as pending in licenseutils
Control: tag -1 pending Hello, Bug #1038910 in licenseutils reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/licenseutils/-/commit/62bfbf1c06e8d0325a58ccf4845c551281f68915 Switch to libcurl4-nss-dev (Closes: #1038910) (this message was generated automatically) -- Greetings https://bugs.debian.org/1038910
Processed: Re: Bug#1041508: tex-common: fmutil fails to rebuild formats
Processing control commands: > reassign -1 texlive-binaries Bug #1041508 [tex-common] tex-common: fmutil fails to rebuild formats Bug reassigned from package 'tex-common' to 'texlive-binaries'. No longer marked as found in versions tex-common/6.18. Ignoring request to alter fixed versions of bug #1041508 to the same values previously set -- 1041508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041508: tex-common: fmutil fails to rebuild formats
Control: reassign -1 texlive-binaries On 20.07.2023 00:06, ಚಿರಾಗ್ ನಟರಾಜ್ wrote: Hi, Upgrading tex-common seems to fail when attempting to rebuild formats (log attached). That issue is in texlive-binaries and has been solved there. H. -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1050903: segmentation fault
One of my contacts has published a story and telegram just crashes immediately after I login. I downgraded to the version in testing. -- Salvo Tomaselli "Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno." -- Galileo Galilei http://ltworf.github.io/ltworf/
Bug#1004477: marked as done (virt-top fails to start with OCaml 4.13.1)
Your message dated Sun, 03 Sep 2023 06:49:07 + with message-id and subject line Bug#1004477: fixed in virt-top 1.0.9-3 has caused the Debian Bug report #1004477, regarding virt-top fails to start with OCaml 4.13.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1004477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virt-top Version: 1.0.9-1.1 Severity: serious X-Debbugs-Cc: Debian OCaml Maintainers $ virt-top the file '/usr/bin/virt-top' has not the right magic number: expected Caml1999X030, got Caml1999X028 $ --- End Message --- --- Begin Message --- Source: virt-top Source-Version: 1.0.9-3 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of virt-top, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated virt-top package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Sep 2023 08:25:08 +0200 Source: virt-top Architecture: source Version: 1.0.9-3 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Stéphane Glondu Closes: 1004477 Changes: virt-top (1.0.9-3) unstable; urgency=medium . * Use dh_ocaml to compute proper OCaml dependencies (Closes: #1004477) Checksums-Sha1: a19451e761f08b9c737b2aa9825bc897baff2b34 1909 virt-top_1.0.9-3.dsc b0a3e2858200ce21d0d4d088a2d748e5ce72d21b 4940 virt-top_1.0.9-3.debian.tar.xz Checksums-Sha256: 1a47faf362e3c50e19650473df486c18bb8f8e019341a7e693ea8a1f7bf1e5b6 1909 virt-top_1.0.9-3.dsc 0b56597ac4cfe08b34f09874f95ec9a867993209b4c8e8972a0707f95b472cd8 4940 virt-top_1.0.9-3.debian.tar.xz Files: 8cd08de32400c4352fc075273956fa2e 1909 admin optional virt-top_1.0.9-3.dsc b3013e9f5031ac93bd20fea9c904775c 4940 admin optional virt-top_1.0.9-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmT0J6QSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBytIH/jsMT/PYrb/QiQGjaSlV1oNlPr+LQe2r 7zij1YMej9O723tSZPDCff2VkjhqoGOcjqeeF6YwlUVqKZLrkBmSJBVDn+90Ytlw s9HmbFAg4t4Q2Q4aeLiZ2JYNzo6jJIhAgQkWK+gvyxW/X/1KYn0HkCxQWe4nFQfg q6rVcefxr45KkEAi/U0pLFh27wpFsVdzrFkXkMR602MXLoY6IcKw79+Eebc15dij b9VsoMy1EPDu/0wAac5mAb5x8IfoEK1YTjOBZuAv4taHKpSMSVO5JQdsKUanLMNj JzBMULq1aCvDoNfC5yWQGF7+j1AxS/nJxq4NCWKkrjC4GFBe63wffGs= =62+s -END PGP SIGNATURE End Message ---
Bug#1051066: [Pkg-netatalk-devel] Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches
--- Original Message --- On Saturday, September 2nd, 2023 at 1:33 AM, Jonas Smedegaard wrote: > > This is one bugreport about multiple issues. That easily gets confusing > to track, e.g. if some of the issues are solved and some are not, for a > certain release of the package (and consequently a Debian release where > that package release is included). > > It is generally easier to track when instead filing one bugreport per > issue. > I can see how this is the preferred approach for a clean tracking of each security issue. In this case it gets a bit hairy since we have cases where one patch fixed multiple CVEs, and elsewhere multiple patches were required to fix regressions introduced by a CVE fix. It was a journey of >1 year to get to the present state. > I tried lookup one of above CVEs inn the Debian security tracker: > https://security-tracker.debian.org/tracker/CVE-2022-43634 > > It references an already filed bugreport about that issue, bug#1034170, > which is tagged as found only as early as 3.1.14~ds-1. If earlier > Debian package releases are also affected by that particular issue, then > please update that bugreport to reflect that fact. > > This bugreport is flagged as "archived" (which is done automatically > after being done for a while, to reduce spam). Before doing other > changes you therefore need to first unachive it. > > E.g. something like this: > > bts unarchive 1034170 . found 1034170 3.1.13~ds-1 > Will do, thanks for the command. > The other CVEs seemingly have no related bugreport (from a quick look at > the security tracker - but I suspect that database does not list > bugreports not involving the security team at first, and only later > mentioning a CVE if at all). If you don't happen to be aware of > bugreports exisisting for those other issues, then I suggest to file new > individual bugreports for each issue (also because it is easy to merge > issues later as needed). > That's a fairly big undertaking, especially if clean and atomic patches are required for each... I was really hoping the batch approach would be accepted. That said I can definitely create the individual bug tickets for starters and we can take it from there. Let me set aside some time next week for this. > > Kind regards, and thanks a lot for looking into this, > > - Jonas > You're welcome! Daniel
Bug#1041508: tex-common: fmutil fails to rebuild formats
Le samedi 02 septembre 2023 à 23:47 +0200, Preuße, Hilmar a écrit : > Control: block -1 by 1050807 > > On 02.09.2023 07:57, Emmanuel Charpentier wrote: > > Hi, > > > *** Reporter, please consider answering these questions, where > > appropriate *** > > > > * What led up to the situation? > > > > routine upgrade of testing's tex-common > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > I guess you run Debian testing right? Right. > The texlive-binaries recently migrated to testing, but the > texlive-base/texlive-extra/texlive-lang did not due to #1050807. > Therefore the fix for this issue did not enter testing yet. > > Sorry, for the trouble, I should have added a "Breaks" statement to > texlive-binaries. Maybe it makes sense to do that now? Yes, it does : that would avoid the same problem to other poor sods... -- Emmanuel Charpentier > > Hilmar > -- > sigfault >
Bug#1004477: marked as pending in virt-top
Control: tag -1 pending Hello, Bug #1004477 in virt-top 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/ocaml-team/virt-top/-/commit/cf7f1f2b77139fe0ab8d73ef9ad81a839fab0871 Use dh_ocaml to compute proper OCaml dependencies (Closes: #1004477) (this message was generated automatically) -- Greetings https://bugs.debian.org/1004477
Processed: Bug#1004477 marked as pending in virt-top
Processing control commands: > tag -1 pending Bug #1004477 [virt-top] virt-top fails to start with OCaml 4.13.1 Added tag(s) pending. -- 1004477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1043020: marked as done (adapta-kde: Intent of package removal)
Your message dated Sun, 03 Sep 2023 05:58:15 + with message-id and subject line Bug#1051053: Removed package(s) from unstable has caused the Debian Bug report #1043020, regarding adapta-kde: Intent of package removal 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.) -- 1043020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: adapta-kde Severity: serious Version: 20180828-2 Tags: sid trixie X-Debbugs-CC: prof.franciscar...@gmail.com Dear Debian adapta-kde package maintainer, As stated in https://bugs.debian.org/1031184 , the upstream development of this package has ended. I intend to remove this package after 3 weeks (after Aug 25, 2023) if no disagreement appears. If you have any comments, please let me know as soon as possible by replying this bug report. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 20180828-2+rm Dear submitter, as the package adapta-kde has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1051053 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1017901: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)
Your message dated Sun, 03 Sep 2023 05:57:40 + with message-id and subject line Bug#1051050: Removed package(s) from experimental has caused the Debian Bug report #1017901, regarding Ships autogenerated files that can't be renegerated with the code in Debian main 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.) -- 1017901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gudev-sharp-3.0 Version: 3.0.0-1 Severity: serious Tags: upstream See the discussion on the Debian Rust maintainers list for background: https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html While that discussion is about Rust packages that were rejected, the same situation also applies to gtk-sharp2 unfortunately. For more details how to solve this in a way that makes ftp-masters happy, please refer to them. Affected file is gudev/gudev-api.raw. This file was autogenerated from specific versions of the underlying C libraries and it's not clear which versions were used. Debian ships these C libraries but certainly in different versions so it's not possible to regenerate these files with what is available in Debian. It will be necessary to either include the source code of the C libraries in the exact version, or regenerate the files at build time with whatever is available in Debian. The latter will probably generate different bindings, potentially even with different API, so is probably not a useful solution. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'unstable-debug'), (100, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 3.0.0-1+rm Dear submitter, as the package gudev-sharp-3.0 has just been removed from the Debian archive experimental we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1051050 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1031184: marked as done (adapta-kde: Development has completely and officially ended)
Your message dated Sun, 03 Sep 2023 05:58:15 + with message-id and subject line Bug#1051053: Removed package(s) from unstable has caused the Debian Bug report #1031184, regarding adapta-kde: Development has completely and officially ended 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.) -- 1031184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: adapta-kde Version: 20180828-2 Severity: serious Tags: upstream X-Debbugs-Cc: samuel...@debian.org This bug report is based on a similar one opened against adapta-gtk-theme: https://bugs.debian.org/1010199 Dear maintainer, development has completely ended in 2018 and the official repository has been archived in 2020. This project was heavily based on adapta-gtk-theme, which had its development stopped at around the same time. I'm setting the severity to "serious" with the intention of keeping this outside of the next stable and then removing it from unstable after it's gone from testing. Regards, -- Samuel Henrique --- End Message --- --- Begin Message --- Version: 20180828-2+rm Dear submitter, as the package adapta-kde has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1051053 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
