Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade
Package: dhcpcd-base Version: 9.4.1-24~deb12u2 Severity: serious Justification: file loss during upgrade X-Debbugs-Cc: debian-rele...@lists.debian.org User: helm...@debian.org Usertags: dep17p1 Unfortunately, the stable update of dhcpcd5 introduced a regression relevant to upgrades from bullseye. The bullseye dhcpcd5 package contained the files - /lib/dhcpcd/dhcpcd-hooks/01-test - /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf - /lib/dhcpcd/dhcpcd-hooks/30-hostname - /lib/dhcpcd/dhcpcd-hooks/60-ntp-common.conf - /lib/dhcpcd/dhcpcd-hooks/62-chrony.conf - /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf - /lib/dhcpcd/dhcpcd-hooks/68-openntpd.conf - /lib/dhcpcd/dhcpcd-run-hooks and these have been moved into dhcpcd-base in that particular stable update. The update correctly declares Replaces for this. Unfortunately, it also moves these files from /lib to /usr/lib. Therefore, the declared Replaces have no effect (regarding these files) and as a consequence, an upgrade may delete the affected files. Fortunately, a very simple upgrade from bullseye to bookworm with only dhcpcd5 installed unpacks the new dhcpcd5 package before unpacking dhcpcd-base and therefore the issue is not trivially reproducible and probably does not affect the majority of users. We cannot rule out other upgrade scenarios though and we can also construct a breaking scenario using mmdebstrap. mmdebstrap bullseye /dev/null --variant=apt --include dhcpcd5 --chrooted-customize-hook='sed -i -e s/bullseye/bookworm/ /etc/apt/sources.list && apt update && apt-get install -y libc6 usrmerge && apt-get download dhcpcd-base && dpkg --auto-deconfigure --unpack ./dhcpcd-base_*.deb && dpkg -r dhcpcd5 && ls /usr/lib/dhcpcd/dhcpcd-hooks' If you run this, it ends with: | Selecting previously unselected package dhcpcd-base. | dpkg: considering deconfiguration of dhcpcd5, which would be broken by installation of dhcpcd-base ... | dpkg: yes, will deconfigure dhcpcd5 (broken by dhcpcd-base) | (Reading database ... 6731 files and directories currently installed.) | Preparing to unpack .../dhcpcd-base_9.4.1-24~deb12u2_amd64.deb ... | De-configuring dhcpcd5 (7.1.0-2+b1) ... | Unpacking dhcpcd-base (9.4.1-24~deb12u2) ... | Replacing files in old package dhcpcd5 (7.1.0-2+b1) ... | (Reading database ... 6752 files and directories currently installed.) | Removing dhcpcd5 (7.1.0-2+b1) ... | ls: cannot access '/usr/lib/dhcpcd/dhcpcd-hooks': No such file or directory This kind of problem has been categorized in the https://subdivi.de/~helmut/dep17.html as P1 and the recommended mitigation M7 is changing Breaks+Replaces to Conflicts. I think this mitigation is fully applicable here, because apt will by default unpack the updated dhcpcd5 package first and then the conflict is resolved. The additional constraint is satisfied by the default solution of apt. I am not sure why dhcpcd-base has moved these files from / to /usr in violation of the file move moratorium that was meant to prevent precisely this kind of bug. In any case, please do *not* move them back as that could cause further trouble. I'm sorry for not having spotted this before the point release and will now monitor stable p-u suites for similar problems to raise this earlier. Can I assume that a package sits in p-u for at least three days before migrating to a stable release? Helmut
Bug#982034: marked as done (forked-daapd: autopkgtest regression in testing: Job for forked-daapd.service failed.)
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #982034, regarding forked-daapd: autopkgtest regression in testing: Job for forked-daapd.service failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: forked-daapd Version: 26.4+dfsg1-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change somewhere outside of your package the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? As a service, I have also generated a diff between the installed packages during the test of the last successful run on amd64 and the first that failed. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/f/forked-daapd/10113463/log.gz autopkgtest [22:13:27]: test basic: [--- Job for forked-daapd.service failed. See "systemctl status forked-daapd.service" and "journalctl -xe" for details. autopkgtest [22:13:30]: test basic: ---] paul@mulciber /tmp $ diff -u passed/testbed-packages failed/testbed-packages --- passed/testbed-packages 2020-11-19 22:54:43.0 +0100 +++ failed/testbed-packages 2020-11-27 03:18:26.0 +0100 @@ -6,7 +6,7 @@ binutils 2.35.1-2 binutils-common2.35.1-2 binutils-x86-64-linux-gnu 2.35.1-2 -bsdutils 1:2.36-3+b2 +bsdutils 1:2.36.1-1 bzip2 1.0.8-4 coreutils 8.32-4+b1 dash 0.5.11+git20200708+dd9ef66-2 @@ -17,7 +17,7 @@ dialog 1.3-20190808-1 diffutils 1:3.7-3 dirmngr2.2.20-1 -dmsetup2:1.02.171-3 +dmsetup2:1.02.173-1 dpkg 1.20.5 dpkg-dev 1.20.5 e2fsprogs 1.45.6-1 @@ -40,8 +40,8 @@ gzip 1.10-2 hostname 3.23 ifupdown 0.8.36 -init 1.58 -init-system-helpers1.58 +init 1.59 +init-system-helpers1.59 iproute2 5.9.0-1 isc-dhcp-client4.4.1-2.1+b2 libacl12.2.53-8 @@ -53,7 +53,7 @@ libaudit-common1:2.8.5-3.1 libaudit1 1:2.8.5-3.1 libbinutils2.35.1-2 -libblkid1 2.36-3+b2 +libblkid1 2.36.1-1 libbsd00.10.0-1 libbz2-1.0 1.0.8-4 libc-bin 2.31-4 @@ -71,7 +71,7 @@ libdb5.3 5.3.28+dfsg1-0.6 libdbus-1-31.12.20-1 libdebconfclient0 0.255 -libdevmapper1.02.1 2:1.02.171-3 +libdevmapper1.02.1 2:1.02.173-1 libdns-export1110 1:9.11.19+dfsg-1 libdpkg-perl 1.20.5 libeatmydata1 105-9 @@ -85,27 +85,27 @@ libgcrypt201.8.7-2 libgdbm-compat41.18.1-5.1 libgdbm6 1.18.1-5.1 -libgmp10 2:6.2.0+dfsg-6 +libgmp10 2:6.2.1+dfsg-1 libgnutls303.6.15-4 libgpg-error0 1.38-2 -libgssapi-krb5-2 1.17-10 +libgssapi-krb5-2 1.18.3-4 libhogweed63.6-2 -libidn2-0 2.3.0-3 +libidn2-0 2.3.0-4 libip4tc2 1.8.6-1 libisc-export1105 1:9.11.19+dfsg-1 libjson-c5 0.15-1 -libk5crypto3 1.17-10 +libk5crypto3 1.18.3-4 libkeyutils1 1.6.1-2 libkmod2 27+20200310-2 -libkrb5-3 1.17-10 -libkrb5support01.17-10 +libkrb5-3 1.18.3-4 +libkrb5support01.18.3-4 libksba8 1.4.0-2 libldap-2.4-2 2.4.56+dfsg-1 libldap-common 2.4.56+dfsg-1 liblz4-1 1.9.2-2 liblzma5 5.2.4-1+b1 libmnl01.0.4-3 -libmount1 2.36-3+b2 +libmount1 2.36.1-1 libncurses66.2+20200918-1 libncursesw6 6.2+20200918-1 libnettle8 3.6-2 @@ -117,7 +117,7 @@ libpam-modules 1.3.1-5 libpam-modules-bin 1.3.1-5 libpam-runtime 1.3.1-5 -libpam-systemd 246.6-2 +libpam-systemd 246.6-4 libpam0g 1.3.1-5 libpcre2-8-0 10.34-7 libpcre3 2:8.39-13 @@ -133,19 +133,19 @@ libsemanage-common 3.1-1 libsemanage1 3.1-1+b1 libsepol1 3.1-1 -libsmartcols1 2.36-3+b2 +libsmartcols1 2.36.1-1 libsqlite3-0 3.33.0-1 libss2 1.45.6-1 libssl1.1 1.1.1h-1 libstdc++6 10.2.0-16 -libsystemd0246.6-2 +libsystemd0246.6-4 libtasn1-6 4.16.0-2 libtinfo6 6.2+20200918-1 libtirpc-common1.2.6-3 libtirpc3 1.2.6-3 -libudev1 246.6-2 +libudev1 246.6-4 libunistring2 0.9.10-4 -libuuid1 2.36-3+b2 +libuuid1 2.3
Bug#957758: marked as done (restbed: ftbfs with GCC-10)
Your message dated Sat, 07 Oct 2023 21:54:50 +
with message-id
and subject line Bug#1053534: Removed package(s) from unstable
has caused the Debian Bug report #957758,
regarding restbed: ftbfs with GCC-10
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.)
--
957758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:restbed
Version: 4.0~dfsg1-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/restbed_4.0~dfsg1-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html
[...]
|
~^
/<>/source/corvusoft/restbed/response.cpp: In member function
‘void restbed::Response::get_header(const string&, long long int&, long long
int) const’:
/<>/source/corvusoft/restbed/response.cpp:146:23: error: ISO C++
forbids declaration of ‘invalid_argument’ with no type [-fpermissive]
146 | catch ( const invalid_argument& )
| ^~~~
/<>/source/corvusoft/restbed/response.cpp:146:39: error: expected
‘)’ before ‘&’ token
146 | catch ( const invalid_argument& )
| ~ ^
| )
/<>/source/corvusoft/restbed/response.cpp:146:39: error: expected
‘{’ before ‘&’ token
/<>/source/corvusoft/restbed/response.cpp:146:41: error: expected
primary-expression before ‘)’ token
146 | catch ( const invalid_argument& )
| ^
/<>/source/corvusoft/restbed/response.cpp:140:86: warning: unused
parameter ‘default_value’ [-Wunused-parameter]
140 | void Response::get_header( const string& name, long long& value,
const long long default_value ) const
|
^
/<>/source/corvusoft/restbed/response.cpp: In member function
‘void restbed::Response::get_header(const string&, unsigned int&, unsigned int)
const’:
/<>/source/corvusoft/restbed/response.cpp:158:23: error: ISO C++
forbids declaration of ‘invalid_argument’ with no type [-fpermissive]
158 | catch ( const invalid_argument& )
| ^~~~
/<>/source/corvusoft/restbed/response.cpp:158:39: error: expected
‘)’ before ‘&’ token
158 | catch ( const invalid_argument& )
| ~ ^
| )
/<>/source/corvusoft/restbed/response.cpp:158:39: error: expected
‘{’ before ‘&’ token
/<>/source/corvusoft/restbed/response.cpp:158:41: error: expected
primary-expression before ‘)’ token
158 | catch ( const invalid_argument& )
| ^
/<>/source/corvusoft/restbed/response.cpp:152:92: warning: unused
parameter ‘default_value’ [-Wunused-parameter]
152 | void Response::get_header( const string& name, unsigned int& value,
const unsigned int default_value ) const
|
~~~^
/<>/source/corvusoft/restbed/response.cpp: In member function
‘void restbed::Response::get_header(const string&, long unsigned int&, long
unsigned int) const’:
/<>/source/corvusoft/restbed/response.cpp:170:23: error: ISO C++
forbids declaration of ‘invalid_argument’ with no type [-fpermiss
Bug#1031173: marked as done (arcanist-clang-format-linter: prevents arcanist tool from working (PHP Fatal error: Uncaught Error))
Your message dated Sat, 07 Oct 2023 21:55:47 +
with message-id
and subject line Bug#960425: Removed package(s) from unstable
has caused the Debian Bug report #1031173,
regarding arcanist-clang-format-linter: prevents arcanist tool from working
(PHP Fatal error: Uncaught Error)
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.)
--
1031173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arcanist-clang-format-linter
Version: 0.git20161021-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When arcanist-clang-format-linter is installed, arcanist will fail to run with
this error:
$ arcanist help
PHP Fatal error: Uncaught Error: Call to undefined function
arcanist_load_libraries() in
/usr/share/arcanist/src/extensions/clang-format-linter.php:3
Stack trace:
#0 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(247): include_once()
#1 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(287):
PhutilBootloader->executeInclude('...')
#2 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(106):
PhutilBootloader->loadExtension('...', '...', '...')
#3 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(21):
PhutilBootloader->registerLibrary('...', '...')
#4 /usr/share/arcanist/src/init/init-library.php(70):
PhutilBootloader::newLibrary('...', '...')
#5 /usr/share/arcanist/support/init/init-script.php(114): require_once('...')
#6 /usr/share/arcanist/support/init/init-script.php(131):
__arcanist_init_script__()
#7 /usr/share/arcanist/support/init/init-arcanist.php(3): require_once('...')
#8 /usr/share/arcanist/bin/arc(10): require_once('...')
#9 {main}
thrown in /usr/share/arcanist/src/extensions/clang-format-linter.php on line 3
The error does not appear when using arcanist without having this package
installed.
As this render the arcanist tool unusable, I've marked this bug as grave.
The most probable cause to this is the fact that arcanist-clang-format-linter
version is from 2016 but arcanist is from 2022.
I guess there were breaking changes in arcanist since then.
Upstream seem to have stopped any development on it as the last commit is from
2016.
See https://github.com/pwithnall/morefas-phabricator.
I installed this package to do development on LLVM (which use phabricator).
But it seems that it is in fact not needed, LLVM having its own lint script for
code style (which use clang-format too).
So I guess the solution is to remove this package from Debian as it doesn't
work anymore and was not updated upstream ?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (950, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages arcanist-clang-format-linter depends on:
ii arcanist 0~git20220903-2
ii clang-format 1:14.0-55.5+b1
ii diffutils 1:3.8-4
arcanist-clang-format-linter recommends no packages.
arcanist-clang-format-linter suggests no packages.
--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F |
--- End Message ---
--- Begin Message ---
Version: 0.git20161021-3+rm
Dear submitter,
as the package arcanist-clang-format-linter 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/960425
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#1004626: marked as done (forked-daapd: FTBFS with ffmpeg 5.0)
Your message dated Sat, 07 Oct 2023 21:55:20 + with message-id and subject line Bug#986740: Removed package(s) from unstable has caused the Debian Bug report #1004626, regarding forked-daapd: FTBFS with ffmpeg 5.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.) -- 1004626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: forked-daapd Version: 26.4+dfsg1-2 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 forked-daapd FTBFS with ffmpeg 5.0 (in experimental): | gcc -DHAVE_CONFIG_H -I. -I.. -Wall -I/usr/include/x86_64-linux-gnu -I/usr/include/json-c -I/usr/include/p11-kit-1 -D_REENTRANT -pthread -I/usr/include/x86_64-linux-gnu -D_GNU_SOURCE -DDATADIR=\"/usr/share/forked-daapd\" -DCONFDIR=\"/etc\" -DSTATEDIR=\"/var\" -DPKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/forked-daapd\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o remote_pairing.o remote_pairing.c | main.c:451:36: warning: ‘enum AVLockOp’ declared inside parameter list will not be visible outside of this definition or declaration | 451 | ffmpeg_lockmgr(void **pmutex, enum AVLockOp op) | |^~~~ | main.c:451:45: error: parameter 2 (‘op’) has incomplete type | 451 | ffmpeg_lockmgr(void **pmutex, enum AVLockOp op) | | ~~^~ | main.c: In function ‘ffmpeg_lockmgr’: | main.c:455:12: error: ‘AV_LOCK_CREATE’ undeclared (first use in this function); did you mean ‘AV_LOG_TRACE’? | 455 | case AV_LOCK_CREATE: | |^~ | |AV_LOG_TRACE | main.c:455:12: note: each undeclared identifier is reported only once for each function it appears in | main.c:462:12: error: ‘AV_LOCK_OBTAIN’ undeclared (first use in this function) | 462 | case AV_LOCK_OBTAIN: | |^~ | main.c:466:12: error: ‘AV_LOCK_RELEASE’ undeclared (first use in this function) | 466 | case AV_LOCK_RELEASE: | |^~~ | main.c:470:12: error: ‘AV_LOCK_DESTROY’ undeclared (first use in this function) | 470 | case AV_LOCK_DESTROY: | |^~~ | main.c: In function ‘main’: | main.c:663:9: warning: implicit declaration of function ‘av_lockmgr_register’ [-Wimplicit-function-declaration] | 663 | ret = av_lockmgr_register(ffmpeg_lockmgr); | | ^~~ | main.c:672:3: warning: implicit declaration of function ‘av_register_all’ [-Wimplicit-function-declaration] | 672 | av_register_all(); | | ^~~ | main.c:673:3: warning: implicit declaration of function ‘avfilter_register_all’ [-Wimplicit-function-declaration] | 673 | avfilter_register_all(); | | ^ | make[4]: *** [Makefile:845: main.o] Error 1 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 26.4+dfsg1-2+rm Dear submitter, as the package forked-daapd 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/986740 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#1052768: marked as done (lttnganalyses: FTBFS: AssertionError: '20:57:08.123456789' != '16:57:08.123456789')
Your message dated Sat, 07 Oct 2023 21:52:31 + with message-id and subject line Bug#1053376: Removed package(s) from unstable has caused the Debian Bug report #1052768, regarding lttnganalyses: FTBFS: AssertionError: '20:57:08.123456789' != '16:57:08.123456789' 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.) -- 1052768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lttnganalyses Version: 0.6.1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:291: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses > copying lttnganalyses/_version.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses > copying lttnganalyses/__init__.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses > creating > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/time_utils.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/__init__.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/parse_utils.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/format_utils.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/version_utils.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > copying lttnganalyses/common/trace_utils.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/common > creating > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/sched.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/syscalls.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/period.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/__init__.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/cputop.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/io.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/memtop.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/irq.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/analysis.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/periods.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/event.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > copying lttnganalyses/core/stats.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/core > creating > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/period_parsing.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/sched.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/mi.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/__init__.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/cputop.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/io.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/memtop.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli > copying lttnganalyses/cli/irq.py -> > /<>/.pybuild/cpython3_3.11_lttnganalyses/build/lttnganalyses/cli >
Bug#1052836: marked as done (firmware-tomu: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-1))
Your message dated Sat, 07 Oct 2023 21:47:02 + with message-id and subject line Bug#1053315: Removed package(s) from unstable has caused the Debian Bug report #1052836, regarding firmware-tomu: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-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.) -- 1052836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: firmware-tomu Version: 2.0~rc7-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 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: gcc-arm-none-eabi, libnewlib-arm-none-eabi, > libstdc++-arm-none-eabi-newlib, dfu-util, debhelper-compat (= 12), > build-essential, fakeroot > Filtered Build-Depends: gcc-arm-none-eabi, libnewlib-arm-none-eabi, > libstdc++-arm-none-eabi-newlib, dfu-util, debhelper-compat (= 12), > 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 [609 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [703 B] > Get:5 copy:/<>/apt_archive ./ Packages [735 B] > Fetched 2047 B in 0s (0 B/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: > libstdc++-arm-none-eabi-newlib : Depends: libstdc++-arm-none-eabi-dev (= > 15:12.2.rel1-1+23) but it is not going to be installed > Depends: gcc-arm-none-eabi (= > 15:12.2.rel1-1) but 15:12.3.rel1-1 is to be installed > 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/09/25/firmware-tomu_2.0~rc7-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- Version: 2.0~rc7-2+rm Dear submitter, as the package firmware-tomu 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/1053315 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#1052960: marked as done (pgaudit-1.7: FTBFS: make: *** [debian/rules:10: clean] Error 1)
Your message dated Sat, 07 Oct 2023 21:44:43 + with message-id and subject line Bug#1053268: Removed package(s) from unstable has caused the Debian Bug report #1052960, regarding pgaudit-1.7: FTBFS: make: *** [debian/rules:10: clean] Error 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.) -- 1052960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pgaudit-1.7 Version: 1.7.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with pgxs >dh_auto_clean --buildsystem=pgxs > pg_buildext clean build-%v postgresql-%v-pgaudit > rm -rf build-*/ > rm -rf debian/postgresql-*-pgaudit/ debian/postgresql-*-pgaudit.substvars > make[1]: Entering directory '/<>' > rm -f pgaudit.so libpgaudit.a libpgaudit.pc > rm -f pgaudit.o pgaudit.bc > rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/ > log/ output_iso/ > make[1]: Leaving directory '/<>' >dh_clean >pg_buildext checkcontrol > pg_buildext: error: No current PostgreSQL versions are supported by this > package > make: *** [debian/rules:10: clean] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/pgaudit-1.7_1.7.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- Version: 1.7.0-2+rm Dear submitter, as the package pgaudit-1.7 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/1053268 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#1052876: marked as done (bless: FTBFS: ../tests/meson.build:5:4: ERROR: Problem encountered: nunit not found, cannot build tests. You can disable with -Dtests=false)
Your message dated Sat, 07 Oct 2023 21:38:55 + with message-id and subject line Bug#1053152: Removed package(s) from unstable has caused the Debian Bug report #1052876, regarding bless: FTBFS: ../tests/meson.build:5:4: ERROR: Problem encountered: nunit not found, cannot build tests. You can disable with -Dtests=false 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.) -- 1052876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bless Version: 0.6.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- --libdir=/usr/lib -Dhtml_user_doc=false > cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 > meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 --libdir=/usr/lib > -Dhtml_user_doc=false > The Meson build system > Version: 1.2.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: bless > Project version: 0.6.3 > C sharp compiler for the host machine: mcs (mono 6.8.0.105) > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (1.8.1) > Run-time dependency gtk-sharp-2.0 found: YES 2.12.40 > Run-time dependency glib-sharp-2.0 found: YES 2.12.40 > Configuring ConfigureDefines.cs using configuration > Configuring bless using configuration > Program nunit-console found: YES (/usr/bin/nunit-console) > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency nunit found: NO (tried pkgconfig and cmake) > > ../tests/meson.build:5:4: ERROR: Problem encountered: nunit not found, cannot > build tests. You can disable with -Dtests=false > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2023-09-26T06:39:24.909115 > Main binary: /usr/bin/python3 > Build Options: -Dpython.bytecompile=-1 -Dhtml_user_doc=false -Dprefix=/usr > -Dlibdir=/usr/lib -Dlibexecdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var > -Dsysconfdir=/etc -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 1.2.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: bless > Project version: 0.6.3 > --- > Detecting compiler via: `mcs --version` -> 0 > stdout: > Mono C# compiler version 6.8.0.105 > --- > C sharp compiler for the host machine: mcs (mono 6.8.0.105) > --- > Detecting compiler via: `mcs --version` -> 0 > stdout: > Mono C# compiler version 6.8.0.105 > --- > C sharp compiler for the build machine: mcs (mono 6.8.0.105) > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 > Pkg-config binary for 1 is not cached. > Pkg-config binary missing from cross or native file, or env var undefined. > Trying a default Pkg-config fallback at pkg-config > Found pkg-config: /usr/bin/pkg-config (1.8.1) > Determining dependency 'gtk-sharp-2.0' with pkg-config executable > '/usr/bin/pkg-config' > env[PKG_CONFIG_PATH]: > --- > Called: `/usr/bin/pkg-config --modversion gtk-sharp-2.0` -> 0 > stdout: > 2.12.40 > --- > env[PKG_CONFIG_PATH]: > --- > Called: `/usr/bin/pkg-config --cflags gtk-sharp-2.0` -> 0 > stdout: > -I:/usr/lib/pkgconfig/../../share/gapi-2.0/pango-api.xml > -I:/usr/lib/pkgconfig/../../share/gapi-2.0/atk-api.xml > -I:/usr/lib/pkgconfig/../../share/gapi-2.0/gdk-api.xml > -I:/usr/lib/pkgconfig/../../share/gapi-2.0/gtk-api.xml > -I:/usr/lib/pkgconfig/../../share/gapi-2.0/glib-api.xml > --- > env[PKG_CONFIG_ALLOW_SYSTEM_LIBS]: 1 > env[PKG_CONFIG_PATH]: > --- > Called: `/usr/bin/pkg-config --libs gtk-sharp-2.0` -> 0 > stdout: > -r:/usr/lib/pkgconfig/../../lib/cli/pango-sharp-2.0/pango-sharp.dll > -r:/usr/lib/pkgconfig/../../lib/cli/atk-sharp-2.0/atk-sharp.dll > -r:/usr/lib/pkgconfig/../../lib/cli/gdk-sharp-2.0/gdk-sharp.dll > -r:/usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll > -r:/u
Bug#1052237: marked as done (FTBFS with OCaml 4.14.1)
Your message dated Sat, 07 Oct 2023 21:32:50 + with message-id and subject line Bug#1052295: Removed package(s) from unstable has caused the Debian Bug report #1052237, regarding FTBFS with OCaml 4.14.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.) -- 1052237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xmlrpc-light Version: 0.6.1-6 Severity: important Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.14.1-transition Dear Maintainer, Your package FTBFS with OCaml 4.14.1 with the following error: [...] dh_auto_test make -j1 test make[1]: Entering directory '/tmp/build/xmlrpc-light-0.6.1' make[2]: Entering directory '/tmp/build/xmlrpc-light-0.6.1' make[2]: 'xmlrpc-light.cma' is up to date. make[2]: Leaving directory '/tmp/build/xmlrpc-light-0.6.1' ocaml -I . test/test.ml Exception: Failure "int_of_string". make[1]: *** [Makefile:19: test] Error 125 make[1]: Leaving directory '/tmp/build/xmlrpc-light-0.6.1' dh_auto_test: error: make -j1 test returned exit code 2 make: *** [debian/rules:22: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Packages rebuilt with OCaml 4.14.1 are available at: http://ocaml.debian.net/transitions/ocaml-4.14.1/ Cheers, -- Stéphane --- End Message --- --- Begin Message --- Version: 0.6.1-6+rm Dear submitter, as the package xmlrpc-light 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/1052295 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#995847: marked as done (paulstretch: Program crashes on Play or Render Selection - for debian Bullseye and Bookworm)
Your message dated Sat, 07 Oct 2023 21:31:26 + with message-id and subject line Bug#1052258: Removed package(s) from unstable has caused the Debian Bug report #995847, regarding paulstretch: Program crashes on Play or Render Selection - for debian Bullseye and Bookworm 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.) -- 995847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: paulstretch Version: 2.2-2-4.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: a...@yahoo.com Dear Maintainer, paulstretch works for Buster, has not worked for later releases It seems to be related to connecting to jack server. -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages paulstretch depends on: ii jackd 5+nmu1 ii libaudiofile1 0.3.6-5 ii libc6 2.31-13 ii libfftw3-single3 3.3.8-2 ii libfltk1.11.1.10-29 ii libgcc-s1 10.2.1-6 ii libjack0 [libjack-0.125] 1:0.125.0-3+b1 ii libmad0 0.15.1b-10 ii libmxml1 3.2-1 ii libogg0 1.3.4-0.1 ii libportaudio2 19.6.0-1.1 ii libsamplerate00.2.1+ds0-1 ii libstdc++610.2.1-6 ii libvorbis0a 1.3.7-1 ii libvorbisenc2 1.3.7-1 ii libvorbisfile31.3.7-1 ii zlib1g1:1.2.11.dfsg-2 paulstretch recommends no packages. paulstretch suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.2-2-4.1+rm Dear submitter, as the package paulstretch 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/1052258 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#1052236: marked as done (FTBFS with OCaml 4.14.1)
Your message dated Sat, 07 Oct 2023 21:32:23 + with message-id and subject line Bug#1052294: Removed package(s) from unstable has caused the Debian Bug report #1052236, regarding FTBFS with OCaml 4.14.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.) -- 1052236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: otags Version: 4.05.1-4 Severity: important Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.14.1-transition Dear Maintainer, Your package FTBFS with OCaml 4.14.1 with the following error: [...] ocamlopt.opt -c -w A-44 -safe-string -g -I +compiler-libs -I +ocaml-migrate-parsetree otags.ml File "otags.ml", line 40, characters 4-23: 40 | Parse.interface lex ^^^ Error: This expression has type Parsetree.signature = Parsetree.signature_item list but an expression was expected of type Migrate_parsetree__.Ast_413.Parsetree.signature = Migrate_parsetree__.Ast_413.Parsetree.signature_item list Type Parsetree.signature_item is not compatible with type Migrate_parsetree__.Ast_413.Parsetree.signature_item = Migrate_parsetree.Ast_413.Parsetree.signature_item make[1]: *** [Makefile:120: otags.cmx] Error 2 make[1]: Leaving directory '/tmp/build/otags-4.05.1' dh_auto_build: error: make -j1 returned exit code 2 make: *** [debian/rules:10: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Packages rebuilt with OCaml 4.14.1 are available at: http://ocaml.debian.net/transitions/ocaml-4.14.1/ Cheers, -- Stéphane --- End Message --- --- Begin Message --- Version: 4.05.1-4+rm Dear submitter, as the package otags 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/1052294 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#1052231: marked as done (FTBFS with OCaml 4.14.1)
Your message dated Sat, 07 Oct 2023 21:31:54 + with message-id and subject line Bug#1052293: Removed package(s) from unstable has caused the Debian Bug report #1052231, regarding FTBFS with OCaml 4.14.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.) -- 1052231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmetadom Version: 0.2.6-8 Severity: important Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.14.1-transition Dear Maintainer, Your package FTBFS with OCaml 4.14.1 with the following error: > [...] > ml_EventListener.c:99:13: warning: "callback" is deprecated: use > "caml_callback" instead >99 | *cb = callback; > | ^ > > ml_EventListener.c:100:13: warning: "register_global_root" is deprecated: use > "caml_register_global_root" instead > 100 | register_global_root(cb); > | ^~~ > > make[6]: *** [Makefile:473: ml_EventListener.lo] Error 1 > make[6]: Leaving directory '/tmp/build/gmetadom-0.2.6/src/gdome_caml/events' > make[5]: *** [Makefile:388: all] Error 2 > make[5]: Leaving directory '/tmp/build/gmetadom-0.2.6/src/gdome_caml/events' > make[4]: *** [Makefile:523: all-recursive] Error 1 > make[4]: Leaving directory '/tmp/build/gmetadom-0.2.6/src/gdome_caml' > make[3]: *** [Makefile:387: all-recursive] Error 1 > make[3]: Leaving directory '/tmp/build/gmetadom-0.2.6/src' > make[2]: *** [Makefile:490: all-recursive] Error 1 > make[2]: Leaving directory '/tmp/build/gmetadom-0.2.6' > make[1]: *** [Makefile:397: all] Error 2 > make[1]: Leaving directory '/tmp/build/gmetadom-0.2.6' > dh_auto_build: error: make -j1 returned exit code 2 > make: *** [debian/rules:4: binary] Error 25 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 Packages rebuilt with OCaml 4.14.1 are available at: http://ocaml.debian.net/transitions/ocaml-4.14.1/ Cheers, -- Stéphane -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 0.2.6-8+rm Dear submitter, as the package gmetadom 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/1052293 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#1052165: marked as done (foo-yc20: Terminates directly)
Your message dated Sat, 07 Oct 2023 21:29:04 + with message-id and subject line Bug#1052167: Removed package(s) from unstable has caused the Debian Bug report #1052165, regarding foo-yc20: Terminates directly 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.) -- 1052165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: foo-yc20 Severity: serious Version: 1.3.0-6 The program is terminated directly with the following message, no matter if I try tro run the GUI or CLI version: terminate called after throwing an instance of 'char const*' Aborted --- End Message --- --- Begin Message --- Version: 1.3.0-6+rm Dear submitter, as the package foo-yc20 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/1052167 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#965451: marked as done (cernlib: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 07 Oct 2023 21:21:07 + with message-id and subject line Bug#1052478: Removed package(s) from unstable has caused the Debian Bug report #965451, regarding cernlib: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cernlib Version: 20061220+dfsg3-4.4 Severity: normal Usertags: compat-5-6-removal Hi, The package cernlib uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 20061220+dfsg3-4.4+rm Dear submitter, as the package cernlib 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/1052478 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#957080: marked as done (cernlib: ftbfs with GCC-10)
Your message dated Sat, 07 Oct 2023 21:21:07 + with message-id and subject line Bug#1052478: Removed package(s) from unstable has caused the Debian Bug report #957080, regarding cernlib: ftbfs with GCC-10 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.) -- 957080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cernlib Version: 20061220+dfsg3-4.4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/cernlib_20061220+dfsg3-4.4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:136:72: 136 | IF (I2) 3,3,2 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:138:72: 138 | IF(ICMPCH(AI,A(I22)))3,3,21 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:142:72: 142 | 3 INDEX (I3) = I33 |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 3 at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:147:72: 147 | IF (N-1) 12,12,5 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:151:72: 151 | IF (I2-N) 7,9,11 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:153:72: 153 | IF (ICMPCH(A(I22),A(I222))) 8,9,9 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:156:72: 156 | 9 IF (ICMPCH(AI,A(I22))) 10,11,11 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:178:72: 178 | IF(I1-I2)80,70,60 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:179:72: 179 | 40 IF(I1-I2)60,70,80 |1 Warning: Fortran 2018 deleted feature: Arithmetic IF statement at (1) /<>/src/kernlib/kerngen/tcgen/sortzv.F:26:72: 26 |10 CALL SORTTI (A,INDEX,N) |1 Error: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) /<>/src/kernlib/kerngen/tcgen/sortzv.F:29:72: 29 |20 CALL SORTTC(A,INDEX,N) |1 Error: Type mismatch in argument 'a' at (1); passed REAL(4) to INTEGER(4) Failing command: gfortran -g -c -O -D_FORTIFY_SOURCE=2 -fno-range-check -fno-automatic -fno-second-un
Bug#1023171: marked as done (cernlib: unsatisfiable dependency on geant321-doc)
Your message dated Sat, 07 Oct 2023 21:21:07 + with message-id and subject line Bug#1052478: Removed package(s) from unstable has caused the Debian Bug report #1023171, regarding cernlib: unsatisfiable dependency on geant321-doc 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.) -- 1023171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cernlib Version: 20061220+dfsg3-4.4 Severity: serious Hi, cernlib is not installable in sid as it depends on geant321-doc, which is not available in sid. -Ralf. --- End Message --- --- Begin Message --- Version: 20061220+dfsg3-4.4+rm Dear submitter, as the package cernlib 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/1052478 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#965715: marked as done (mclibs: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 07 Oct 2023 21:20:27 + with message-id and subject line Bug#1051708: Removed package(s) from unstable has caused the Debian Bug report #965715, regarding mclibs: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mclibs Version: 20061220+dfsg3-3.1 Severity: normal Usertags: compat-5-6-removal Hi, The package mclibs uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 20061220+dfsg3-3.1+rm Dear submitter, as the package mclibs 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/1051708 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#957522: marked as done (mclibs: ftbfs with GCC-10)
Your message dated Sat, 07 Oct 2023 21:20:27 + with message-id and subject line Bug#1051708: Removed package(s) from unstable has caused the Debian Bug report #957522, regarding mclibs: ftbfs with GCC-10 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.) -- 957522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mclibs Version: 20061220+dfsg3-3.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/mclibs_20061220+dfsg3-3.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] 37 | 11V1(J)=P(I,J) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 11 at (1) /<>/src/mclibs/cojets/code/bboost.F:41:72: 41 | 12PARHAD(NPART,J)=V2(J) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 12 at (1) /<>/src/mclibs/cojets/code/bboost.F:48:72: 48 | 31V1(J)=PFLABV(J,I,1) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 31 at (1) /<>/src/mclibs/cojets/code/bboost.F:51:72: 51 | 32PFLABV(J,I,1)=V2(J) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 32 at (1) /<>/src/mclibs/cojets/code/bboost.F:60:72: 60 | 20PARHAD(I,7)=-ABS(IORIG(I))/IPACK |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 20 at (1) /<>/src/mclibs/cojets/code/bboost.F:67:72: 67 | 27PARQUA(IQ,J)=0. |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 27 at (1) /<>/src/mclibs/cojets/code/bboost.F:71:72: 71 | 29PARQUA(IQ,J)=PARQUA(IQ,J)+PARHAD(I,J) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 29 at (1) /<>/src/mclibs/cojets/code/bboost.F:82:72: 82 | 40JDCAY(JQ)=-JDCAY(JQ) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 40 at (1) /<>/src/mclibs/cojets/code/bboost.F:87:72: 87 | 41PJSET(J,JQ)=PARQUA(IQ,J) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 41 at (1) /<>/src/mclibs/cojets/code/bboost.F:102:72: 102 | 44PJSET(J,JQ)=PJSET(J,JQ1)+PJSET(J,JQ2) |1 Warning: Fortran 2018 deleted feature: DO termination statement which is not END DO or CONTINUE with label 44 at (1) gfortran bdecay.F /<>/src/mclibs/cojets/code/bdecay.F:50:21: 44 | TBR=CJRN(0) | 2 ...
Bug#1043383: marked as done (python-pcre: depends on obsolete pcre3 library)
Your message dated Sat, 07 Oct 2023 21:18:20 + with message-id and subject line Bug#1052242: Removed package(s) from unstable has caused the Debian Bug report #1043383, regarding python-pcre: depends on obsolete pcre3 library 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.) -- 1043383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pcre Severity: serious Version: 0.7-1 User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, When the pcre3 -> pcre2 mass bug was filed, python-pcre had not yet been in the archive. I am filing this (edited copy) after the fact: Your package still depends on the old, obsolete PCRE3 libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, we would like to remove the pcre3 libraries from Debian. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html A possible replacement for your package is at https://github.com/grtetrault/pcre2.py Thanks, Bastian --- End Message --- --- Begin Message --- Version: 0.7-1+rm Dear submitter, as the package python-pcre 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/1052242 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 ---
Processed: found 1053259 in 1.18.4-3, found 1053260 in 1.18.4-3, found 1053261 in 1.18.4-3
Processing commands for cont...@bugs.debian.org: > found 1053259 1.18.4-3 Bug #1053259 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40476 Marked as found in versions gst-plugins-bad1.0/1.18.4-3. > found 1053260 1.18.4-3 Bug #1053260 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40475 Marked as found in versions gst-plugins-bad1.0/1.18.4-3. > found 1053261 1.18.4-3 Bug #1053261 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40474 Marked as found in versions gst-plugins-bad1.0/1.18.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053259 1053260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053260 1053261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1053259 in 1.22.0-4, found 1053260 in 1.22.0-4, found 1053261 in 1.22.0-4
Processing commands for cont...@bugs.debian.org: > found 1053259 1.22.0-4 Bug #1053259 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40476 Marked as found in versions gst-plugins-bad1.0/1.22.0-4. > found 1053260 1.22.0-4 Bug #1053260 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40475 Marked as found in versions gst-plugins-bad1.0/1.22.0-4. > found 1053261 1.22.0-4 Bug #1053261 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40474 Marked as found in versions gst-plugins-bad1.0/1.22.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053259 1053260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053260 1053261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053638: [Pkg-rust-maintainers] Bug#1053638: rust-pbr: Remove from Debian?
It has no reverse dependencies and is one of the last things keeping rust-time-0.1 in Debian. Not speaking for or against removal, but updating it to the latest version would get rid of the dependency on time 0.1.
Processed: block 1053259 with 1052660, block 1053260 with 1052660, block 1053261 with 1052660
Processing commands for cont...@bugs.debian.org: > block 1053259 with 1052660 Bug #1053259 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40476 1053259 was not blocked by any bugs. 1053259 was not blocking any bugs. Added blocking bug(s) of 1053259: 1052660 > block 1053260 with 1052660 Bug #1053260 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40475 1053260 was not blocked by any bugs. 1053260 was not blocking any bugs. Added blocking bug(s) of 1053260: 1052660 > block 1053261 with 1052660 Bug #1053261 [src:gst-plugins-bad1.0] gst-plugins-bad1.0: CVE-2023-40474 1053261 was not blocked by any bugs. 1053261 was not blocking any bugs. Added blocking bug(s) of 1053261: 1052660 > thanks Stopping processing here. Please contact me if you need assistance. -- 1053259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053259 1053260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053260 1053261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053570: marked as done (haskell-config-value FTBFS with alex 3.3.0.0)
Your message dated Sat, 07 Oct 2023 18:19:07 + with message-id and subject line Bug#1053570: fixed in haskell-config-value 0.8.3-3 has caused the Debian Bug report #1053570, regarding haskell-config-value FTBFS with alex 3.3.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.) -- 1053570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-config-value Version: 0.8.3-2 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/glguy/config-value/commit/c5558c8258598fab686c259bff510cc1b19a0c50 https://buildd.debian.org/status/fetch.php?pkg=haskell-config-value&arch=loong64&ver=0.8.3-2&stamp=1696604219&raw=0 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-config-value.html ... CallStack (from HasCallStack): withMetadata, called at libraries/Cabal/Cabal/src/Distribution/Simple/Utils.hs:370:14 in Cabal-3.8.1.0:Distribution.Simple.Utils Error: hlibrary.setup: The program 'alex' version ^>=3.2.4 is required but the version found at /usr/bin/alex is version 3.3.0.0 ... --- End Message --- --- Begin Message --- Source: haskell-config-value Source-Version: 0.8.3-3 Done: Clint Adams We believe that the bug you reported is fixed in the latest version of haskell-config-value, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Clint Adams (supplier of updated haskell-config-value package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2023 13:39:58 -0400 Source: haskell-config-value Architecture: source Version: 0.8.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Clint Adams Closes: 1053570 Changes: haskell-config-value (0.8.3-3) unstable; urgency=medium . * Patch for newer alex. closes: #1053570. Checksums-Sha1: b8e6673b0f4b0163bdec3b4772fadaabe3926c46 2404 haskell-config-value_0.8.3-3.dsc 225dd453fa25373e756495fc9bf719f81aef394f 20540 haskell-config-value_0.8.3.orig.tar.gz 99a920844dfc79ad3ddff5acb4c1d0745fa777df 3172 haskell-config-value_0.8.3-3.debian.tar.xz e3740fe672124b81613917a640ee430ae175767d 8167 haskell-config-value_0.8.3-3_source.buildinfo Checksums-Sha256: bb22e2ee9f54cfa994d1b30cdfec6b40e387fac87772a5253ea72e8b82d1f33d 2404 haskell-config-value_0.8.3-3.dsc 7cb8d046be5adc09b19dae6b0ad1010b0292f069034c83d28954f1905ee76c5e 20540 haskell-config-value_0.8.3.orig.tar.gz 3264ff00d471d4bae8afcfb5ac22bcece8aa5a5bb604d4b7ee9cc46a9717e120 3172 haskell-config-value_0.8.3-3.debian.tar.xz caaf9624ed2169cea7a709d0468e85db22743b46b1716d9fb7c1db16ec478738 8167 haskell-config-value_0.8.3-3_source.buildinfo Files: 16d64ab628b11e975e3dc380a830743a 2404 haskell optional haskell-config-value_0.8.3-3.dsc 063dafc7704a19a6db4934fc42135170 20540 haskell optional haskell-config-value_0.8.3.orig.tar.gz d3555e1450cda979a9a839c948dc3010 3172 haskell optional haskell-config-value_0.8.3-3.debian.tar.xz 47e92d1dd895ffc76366cd6e70daf890 8167 haskell optional haskell-config-value_0.8.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAmUhmH8RHGNsaW50QGRl Ymlhbi5vcmcACgkQVZIzHhmdOKiQ1Q//WBLtL5Yc8JwH3vCzZ1/2X2G9jsDdDriK 4L2jfNdzfAM7+9Mg73MfQNgXZ6pouPnXiAW6AVoDlrDocDzP3gKPOUmBHvJcdLpO fst9m5AbExbDIBE3Jb6/hb8Vk6IYjhP3Ke75H4TfyQpqrkt1xKA+zPH3anfkUNco jonI2C0dW1NNOFUPKdjWQBh1H73SLc6rpCmiHOiCkDyqSzaZyFhToqPduyUe34fr D8Nsj6tWeJUNSc0IxY/Kh5zxCQ9a/kZPiC6cAlkQU9FlUemS9X1aVCUx6B6nnTWj /JoKEW+eGivo8zQfZhDlHM4A06tb3OT0UbtJxFuqTQbQKLlRq9/GjBlq06Wv93Nm Eqc/cb14Pu7r6tyeYykX7YDSccYA3TeUktJmitEdr+pdrF29/iRCWXpU0ZVluRJ/ 5anhosZ7s2noGOVxqfeslxbU162ljlu+GAm9ync6Ekd/hptRPttbh8ndp6yX7Hgd PVUPuitJLPMNMofGdtdfjhIcxZ0m/4jzOxMFUdzfhEo0NOddrB/fJY+TOypsR6mg /EsZ1pahzIgKIxNZUgy+Lu775cb3bLCCBTzUvZ2ihTZRq/4ODQsIP+WlGs3PEw18 YBgOMpA6XuvKkG7WGB9LM91fL/ivMvD3eeDuuz4Hyldpht9Gqu355/Zek27PCa2W tiGrd01pUh4= =PQMo -END PGP SIGNATURE End Message ---
Bug#1052486: marked as done (jpeg-xl: FTBFS with libwebp 1.3.2: Use static libwebp library without linking libsharpyuv)
Your message dated Sat, 07 Oct 2023 18:19:39 +
with message-id
and subject line Bug#1052486: fixed in jpeg-xl 0.7.0-10.1
has caused the Debian Bug report #1052486,
regarding jpeg-xl: FTBFS with libwebp 1.3.2: Use static libwebp library without
linking libsharpyuv
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.)
--
1052486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpeg-xl
Severity: serious
Version: 0.7.0-10
X-Debbugs-CC: ma...@debian.org
Control: tags -1 +patch
Dear Debian jpeg-xl packager,
Unfortunately jpeg-xl in Sid now FTBFS more due to a corner case in searching
of its
build-dependency libwebp.
In jpeg-xl CMakeLists.txt, it searches libwebp in order to build some test
binaries.
Unfortunately the CMakeList.txt is hardcoding the logic to prefer static
library if
present, and fall back to using shared library. However, with libwebp 1.3.x
series,
the static library of libwebp also depends on symbols in libsharpyuv (which is
built
together with libwebp). The building of jpeg-xl will unfortunately FTBFS if the
static
libsharpyuv is not linked together with libwebp explicitly.
I am preparing a patch to solve this problem, which adds the logic of static
libsharpyuv
linkage. Unfortunately this patch will be incompatible with libwebp (<< 1.3).
The
alternative solution is to enforce dynamic linking at all time, which will be
compatible
with all libwebp versions.
Thanks,
Boyuan Yang
From: Boyuan Yang
Date: Fri, 22 Sep 2023 17:12:33 -0400
Subject: tools/CMakeLists.txt: Fix compatibility with static libwebp 1.3.x
---
tools/CMakeLists.txt | 5 +
1 file changed, 5 insertions(+)
diff --git a/tools/CMakeLists.txt b/tools/CMakeLists.txt
index 934ed89..6556845 100644
--- a/tools/CMakeLists.txt
+++ b/tools/CMakeLists.txt
@@ -249,7 +249,12 @@ if(JPEGXL_ENABLE_BENCHMARK AND JPEGXL_ENABLE_TOOLS)
message(WARNING "Using dynamic libwebp")
target_link_libraries(benchmark_xl PkgConfig::WebP)
else()
+ # Debian-specific patch
+ # libwebp 1.3.x: libsharpyuv static library must be linked as well
+ find_library(SHARPYUV_STATIC_LINK_LIBRARY NAMES libsharpyuv.a
+ PATHS "${WebP_LIBDIR}" REQUIRED)
target_link_libraries(benchmark_xl "${WebP_STATIC_LINK_LIBRARY}")
+ target_link_libraries(benchmark_xl "${SHARPYUV_STATIC_LINK_LIBRARY}")
target_include_directories(benchmark_xl
PRIVATE ${WebP_STATIC_INCLUDE_DIRS})
target_compile_options(benchmark_xl PRIVATE ${WebP_STATIC_CFLAGS_OTHER})
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: jpeg-xl
Source-Version: 0.7.0-10.1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
jpeg-xl, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated jpeg-xl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 23 Sep 2023 12:52:43 -0400
Source: jpeg-xl
Architecture: source
Version: 0.7.0-10.1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers
Changed-By: Boyuan Yang
Closes: 1051560 1052486
Changes:
jpeg-xl (0.7.0-10.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Boyuan Yang ]
* debian/patches/:
+ 0007-tools-CMakeLists.txt-Fix-compatibility-with-static-l.patch:
Fix compatibility with libwebp 1.3.x. (Closes: #1052486)
* 0008-Fix-conformance-test.patch: Fix unit test that was previously
skipped but now failing. (Closes: #1051560)
* debian/control: Require libwebp-dev (>= 1.3) due to patch 0007.
Checksums-Sha1:
1db21c99001cd5522b1647e2e455d5e6f62ff89f 3092 jpeg-xl_0.7.0-10.1.dsc
43f9515e0c50dc1049de7a55fea1df9b033b0069 1505917 jpeg-xl_0.7.0.orig.tar.gz
5871f3e92d2c639e340183117f02695178a986eb 22860 jpeg-xl_0.7.0-10.1.debian.tar.xz
e7a9b0b470a663960e923dfa828970d832b4f182 15346
jpeg-xl_0.7.0-10.1_amd64.buildinfo
Checksums-Sha256:
00166ee63c11923d41ee3aa05
Bug#1041332: marked as done (mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg)
Your message dated Sat, 07 Oct 2023 17:49:29 + with message-id and subject line Bug#1041332: fixed in mrtg 2.17.10-5+deb12u2 has caused the Debian Bug report #1041332, regarding mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg 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.) -- 1041332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mrtg Version: 2.17.10-5+deb12u1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 1040860 with -1 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/mrtg/mrtg.cfg My impression is that the unmodified new conffile (from bookworm) gets overwritten with the unmodified old conffile (from bullseye), something that shouldn't happen. I'd suggest to withdraw the 2.17.10-5+deb12u1 bookworm-pu update and revisit that for the next point release (there is no time left to fix this properly before saturday). I have some idea how this could be solved better, but I need to try that first. cheers, Andreas PS: piuparts runs under DEBIAN_FRONTEND=noninteractive mrtg_2.17.10-5+deb12u1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mrtg Source-Version: 2.17.10-5+deb12u2 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of mrtg, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated mrtg 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: Wed, 27 Sep 2023 22:59:14 -0300 Source: mrtg Architecture: source Version: 2.17.10-5+deb12u2 Distribution: bookworm Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Closes: 1039103 1041332 Changes: mrtg (2.17.10-5+deb12u2) bookworm; urgency=medium . * Changed a debconf template to honor Debian Policy (10.7.3), not changing the place a conffile, discarding any user changes. Thanks to Andreas Beckmann . Consequently: - debian/mrtg.config: changed a comment. - debian/mrtg.postinst: dropped the first conditional block, related to moving the /etc/mrtg.cfg to /etc/mrtg/. - debian/mrtg.templates: updated to show a specific message to users. - debian/po/: ran debconf-updatepo to update all templates. - Closes: #1039103, #1041332 * debian/po/: - mrtg.templates: reviewed all messages. Thanks to Justin B Rye for all help in debian-l10n-english list and to Jonathan Wiltshire for the suggestion
Bug#1053142: marked as done (chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1)
Your message dated Sat, 07 Oct 2023 17:47:21 + with message-id and subject line Bug#1053142: fixed in chromium 117.0.5938.132-1~deb12u1 has caused the Debian Bug report #1053142, regarding chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1 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.) -- 1053142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 117.0.5938.62-1~deb12u1 Severity: grave Justification: renders package unusable Dear Maintainer, chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1. In the latest changes of libfreetype6, macro PUT_COLOR_LAYERS_V1 was set to NULL pointer, which would make function FT_Get_Color_Glyph_Paint() become an invalid function. SkScalerContext_FreeType::generateMetrics() will call FT_Get_Color_Glyph_Paint() when chromium starts up. Backtrace: Core was generated by `/usr/lib/chromium/chromium --show-component-extension- options --ignore-gpu-blac'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x in ?? () [Current thread is 1 (Thread 0x7f849a4530c0 (LWP 1450075))] (gdb) bt #0 0x in () #1 0x55b7eea342d4 in SkScalerContext_FreeType::generateMetrics(SkGlyph*, SkArenaAlloc*) () #2 0x55b7ea18af08 in SkScalerContext::internalMakeGlyph(SkPackedGlyphID, SkMask::Format, SkArenaAlloc*) () #3 0x55b7ea18ae85 in SkScalerContext::makeGlyph(SkPackedGlyphID, SkArenaAlloc*) () #4 0x55b7ea1a2f7a in SkStrike::digestFor(skglyph::ActionType, SkPackedGlyphID) () #5 0x55b7ea1a22b3 in SkStrike::metrics(SkSpan, SkGlyph const**) () #6 0x55b7ea10a727 in SkFont::getWidthsBounds(unsigned short const*, int, float*, SkRect*, SkPaint const*) const () #7 0x55b7ef4ed573 in gfx::(anonymous namespace)::GetGlyphHorizontalAdvance(hb_font_t*, void*, unsigned int, void*) () #8 0x55b7ea2b70d2 in hb_font_get_glyph_h_advances_default(hb_font_t*, void*, unsigned int, unsigned int const*, unsigned int, int*, unsigned int, void*) () #9 0x55b7ea2fba2f in _hb_ot_shape () #10 0x55b7ea314cbf in hb_shape_plan_execute () #11 0x55b7ea315095 in hb_shape_full () #12 0x55b7ef4e0740 in gfx::RenderTextHarfBuzz::ShapeRunsWithFont(std::__cxx11::basic_stringstd::char_traits, std::allocator >--Type for more, q to quit, c to continue without paging-- const&, gfx::internal::TextRunHarfBuzz::FontParams const&, std::vector >*, std::vector >*) () #13 0x55b7ef4de5a1 in gfx::RenderTextHarfBuzz::ShapeRuns(std::__cxx11::basic_string, std::allocator > const&, gfx::internal::TextRunHarfBuzz::FontParams const&, std::vector >) () #14 0x55b7ef4dc343 in gfx::RenderTextHarfBuzz::ItemizeAndShapeText(std::__cxx11::basic_string, std::allocator > const&, gfx::internal::TextRunList*) () #15 0x55b7ef4d9de5 in gfx::RenderTextHarfBuzz::EnsureLayoutRunList() () #16 0x55b7ef4db289 in gfx::RenderTextHarfBuzz::EnsureLayout() () #17 0x55b7ef4cebcd in gfx::RenderText::GetCursorBounds(gfx::SelectionModel const&, bool) () #18 0x55b7ef4d1a47 in gfx::RenderText::UpdateCachedBoundsAndOffset() () #19 0x55b7ef4d19ee in gfx::RenderText::GetUpdatedCursorBounds() () #20 0x55b7f12a422f in views::Textfield::Scroll(std::vectorlong, std::allocator > const&) () #21 0x55b7f3b65a94 in OmniboxViewViews::SetTextAndSelectedRanges(std::__cxx11::basic_string, std::allocator > const&, std::vector > const&) () #22 0x55b7f3b65ce1 in OmniboxViewViews::SetWindowTextAndCaretPos(std::__cxx1--Type for more, q to quit, c to continue without paging-- 1::basic_string, std::allocator > const&, unsigned long, bool, bool) () #23 0x55b7f3707750 in OmniboxEditModel::Revert() () #24 0x55b7f3703da1 in OmniboxView::RevertAll() () #25 0x55b7f3b64d83 in OmniboxViewViews::Update() () #26 0x55b7f3b2fa44 in LocationBarView::Update(content::WebContents*) () #27 0x55b7f3b2f421 in LocationBarView::Init() () #28 0x55b7f3d34ba6 in ToolbarView::Init() () #29 0x55b7f3a6533e in BrowserView::AddedToWidget() () #30 0x55b7f12e1eeb in views::View::PropagateAddNotifications(views::ViewHierarchyChangedDetails const&, bool) () #31 0x55b7f12e16c8 in views::View::AddChildViewAtImpl(views::View*, unsigned long) () #32 0x55b7f130de5b in views::NonClientView::ViewHierarchyChanged(views::ViewHierarchyChangedDetails const&) () #33 0x55b7f12e1b8d in views::View::ViewHierarchyChangedImpl(views::ViewHierarchyChangedDetails const&) () #34 0x55b7f12e1ed2 in views::View::PropagateAd
Bug#1053638: rust-pbr: Remove from Debian?
Source: rust-pbr Version: 1.0.1-1 Severity: serious X-Debbugs-CC: and...@shadura.me Can we remove rust-pbr from Debian? It has no reverse dependencies and is one of the last things keeping rust-time-0.1 in Debian. Thank you, Jeremy Bícha
Processed: Re: squeekboard FTBFS with version 0.18 of rust gtk stack.
Processing commands for cont...@bugs.debian.org: > tags 1053536 ftbfs sid trixie Bug #1053536 [squeekboard] squeekboard FTBFS with version 0.18 of rust gtk stack. Added tag(s) sid, trixie, and ftbfs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1053536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053632: rust-libslirp: Remove from Debian?
Hi, On Sat, 7 Oct 2023, at 17:39, Jeremy Bícha wrote: > On Sat, Oct 7, 2023 at 11:32 AM Andrej Shadura wrote: >> Debos uses libslirp in some modes of operation. > > How would I be able to find dependencies like this? Before removing packages? $ apt rdepends libslirp-helper libslirp-helper Reverse Depends: Depends: libslirp-helper-dbgsym (= 4.3.0-4+b2) Suggests: fakemachine Suggests: debos -- Cheers, Andrej
Bug#1053633: haskell-yi-core: FTBFS with haskell-unix-compat >= 0.7
Source: haskell-yi-core Version: 0.19.2-2 Severity: serious Tags: ftbfs Justification: ftbfs Forwarded: https://github.com/yi-editor/yi/issues/1133 This package FTBFS with the latest version of haskell-unix-compat, which is part of Stackage LTS 21 and available in Debian unstable. -- Ilias
Bug#1053632: rust-libslirp: Remove from Debian?
On Sat, Oct 7, 2023 at 11:32 AM Andrej Shadura wrote: > On Sat, 7 Oct 2023, at 17:20, Jeremy Bícha wrote: > > rust-libslirp has no reverse dependencies in Debian. > > Debos uses libslirp in some modes of operation. How would I be able to find dependencies like this? Before removing packages? Thank you, Jeremy Bícha
Bug#1053632: [Pkg-rust-maintainers] Bug#1053632: rust-libslirp: Remove from Debian?
Hi, On Sat, 7 Oct 2023, at 17:36, Peter Green wrote: > We discussed this on irc a while back, and apparently the package is important > to debos. Though the package relationship is only a "suggests". Because it’s needed in the UML mode, but UML is not the main mode of operation. UML is in Suggests, so it libslirp-helper. -- Cheers, Andrej
Bug#1053632: [Pkg-rust-maintainers] Bug#1053632: rust-libslirp: Remove from Debian?
rust-libslirp has no reverse dependencies in Debian. https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-libslirp&perpkg=1 It is also one of the blockers for removing the old rust-zbus-1 from Debian. See https://bugs.debian.org/1053631 Can we remove rust-libslirp and rust-libslirp-sys from Debian? We discussed this on irc a while back, and apparently the package is important to debos. Though the package relationship is only a "suggests". rust-libslirp depends on the obsolete rust-zbus-1 (instead of the current rust-zbus-3) and rust-zvariant-2 (instead of rust-zvariant-3). I looked at porting this, but came to the conclusion that is beyond what I could reasonablly do. IIRC zbus moved from sync rust to async rust and there was no porting guide.
Bug#1053632: rust-libslirp: Remove from Debian?
Control: tag 1053632 wontfix On Sat, 7 Oct 2023, at 17:20, Jeremy Bícha wrote: > rust-libslirp has no reverse dependencies in Debian. Debos uses libslirp in some modes of operation.
Bug#1053632: marked as done (rust-libslirp: Remove from Debian?)
Your message dated Sat, 07 Oct 2023 17:31:42 +0200 with message-id <088fa39f-289e-4d8f-bd83-764d67ca7...@app.fastmail.com> and subject line Re: Bug#1053632: rust-libslirp: Remove from Debian? has caused the Debian Bug report #1053632, regarding rust-libslirp: Remove from Debian? 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.) -- 1053632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-libslirp Version: 4.3.0-4 Severity: serious X-Debbugs-CC: andre...@debian.org Control: affects -1 src:rust-libslirp-sys rust-libslirp has no reverse dependencies in Debian. https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-libslirp&perpkg=1 It is also one of the blockers for removing the old rust-zbus-1 from Debian. See https://bugs.debian.org/1053631 Can we remove rust-libslirp and rust-libslirp-sys from Debian? On behalf of the Debian Rust Team, Jeremy Bícha --- End Message --- --- Begin Message --- Control: tag 1053632 wontfix On Sat, 7 Oct 2023, at 17:20, Jeremy Bícha wrote: > rust-libslirp has no reverse dependencies in Debian. Debos uses libslirp in some modes of operation.--- End Message ---
Processed: Re: Bug#1053632: rust-libslirp: Remove from Debian?
Processing control commands: > tag 1053632 wontfix Bug #1053632 [src:rust-libslirp] rust-libslirp: Remove from Debian? Added tag(s) wontfix. -- 1053632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053632: rust-libslirp: Remove from Debian?
Source: rust-libslirp Version: 4.3.0-4 Severity: serious X-Debbugs-CC: andre...@debian.org Control: affects -1 src:rust-libslirp-sys rust-libslirp has no reverse dependencies in Debian. https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+rust-libslirp&perpkg=1 It is also one of the blockers for removing the old rust-zbus-1 from Debian. See https://bugs.debian.org/1053631 Can we remove rust-libslirp and rust-libslirp-sys from Debian? On behalf of the Debian Rust Team, Jeremy Bícha
Processed: rust-libslirp: Remove from Debian?
Processing control commands: > affects -1 src:rust-libslirp-sys Bug #1053632 [src:rust-libslirp] rust-libslirp: Remove from Debian? Added indication that 1053632 affects src:rust-libslirp-sys -- 1053632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053630: flask-dance: build-depends on package that is not in testing.
Package: flask-dance Version: 6.2.0.2-1 Severity: serious Justification: rc policy - "packages must be buildable within the same release". Tags: trixie, sid flask-dance build-depends on python3-sphinxcontrib.seqdiag which is not in testing, it was removed because it FTBFS and was badly broken, but for some reason flask-dance was not removed at the same time (dependency handling in auto-removals is far from perfect). This issue affects both versions 6:2.0.2-1 in testing and 7.0.0-1 which is trying to migrate to testing but failing to do so due to the aforementioned build-dependency.
Bug#1040901: Upcoming changes to Debian Linux kernel packages
Moin On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote: > ## Kernel modules will be signed with an ephemeral key This is now https://salsa.debian.org/kernel-team/linux/-/merge_requests/607. > ## Image packages contains more version info > > Example: linux-image-6.5.3-cloud-arm64 > It will not longer be possible to reliably derive the package name from > kernel release (see above), as both values are not really related > anymore. I missed that apt does something similar (maintainers cced). It wants to see if a particular package matches the current kernel to make the autoremove prevention work. That lookup is quite a hard problem. What should work: We define a new control field. It contains both the kernel name and a version prefix. Example: - Linux 6.6 (would match 6.6-1, 6.6.1-1) - Linux 6.6.3 (would match 6.6.3-1, but not 6.6.3+2-1) - Linux 6.6.3+2 The algorithm would be something like this: - Check $(uname -s) against the first word. Otherwise completely ignore. - Check if $(uname -r) matches the version prefix in this field. Mark as keep if it matches. - Aggregate packages by version prefix. - Sort as version, keep newest two(?). This means: - Images and headers are always kept with the same versions. - Different images (-arm64, -rt-arm64) are always kept together. Counter proposal: Use see the kernel release as debian version and match on the upstream version. But then we need to re-define what we put into the kernel release field. In 6.6.1-1-cloud-arm64, the upstream version is 6.6.1-1-cloud, not 6.6.1 as we would need. We could of course change that to: 6.6.1-1~cloud+arm64. That should always sort correctly in regard of the package version. > ## Header and tool packages will not longer contain version This is obsolete with the counter proposal of a meta package that always pulls in image and headers of the same version. Regards, Bastian -- Without followers, evil cannot spread. -- Spock, "And The Children Shall Lead", stardate 5029.5
Bug#1038145: marked as done (cgreen: FTBFS on s390x)
Your message dated Sat, 07 Oct 2023 14:42:52 + with message-id and subject line Bug#1038145: fixed in cgreen 1.6.3-1 has caused the Debian Bug report #1038145, regarding cgreen: FTBFS on s390x 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.) -- 1038145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cgreen Version: 1.5.1-1 Severity: serious Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu mantic Dear maintainers, cgreen > 1.4.1-1 fails to build from source on s390x: [...] Total Test time (real) = 3.57 sec The following tests FAILED: 3 - runner_test_cgreen_c (Failed) 6 - runner_test_cgreen_cpp (Failed) Errors while running CTest Output from these tests are in: /<>/build/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. make[2]: *** [Makefile:33: test] Error 8 [...] (https://buildd.debian.org/status/fetch.php?pkg=cgreen&arch=s390x&ver=1.5.1-1&stamp=1681718579&raw=0) This is a regression in architecture coverage, so will block the package from testing until fixed or you get the ftp team to remove the old binaries. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: cgreen Source-Version: 1.6.3-1 Done: Gavin Lai (賴建宇) We believe that the bug you reported is fixed in the latest version of cgreen, 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. Gavin Lai (賴建宇) (supplier of updated cgreen 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: Tue, 03 Oct 2023 23:11:21 +0800 Source: cgreen Architecture: source Version: 1.6.3-1 Distribution: unstable Urgency: medium Maintainer: Gavin Lai (賴建宇) Changed-By: Gavin Lai (賴建宇) Closes: 1038145 Changes: cgreen (1.6.3-1) unstable; urgency=medium . * Import new upstream release (Closes: #1038145) * Remove patch files which are fixed by upstream * Update symbols Checksums-Sha1: 0fb2c32dacd954b80f163909cc95fc967d8d6864 2103 cgreen_1.6.3-1.dsc 8ba29145351b9fe725365758500f4fd7478750a8 461875 cgreen_1.6.3.orig.tar.gz 5dd164f7e05478cf68f0cddf6a9e15397be1647e 5872 cgreen_1.6.3-1.debian.tar.xz Checksums-Sha256: 21391dedd32c79d234a2f83efc5b7111af565b94e1914234637557dfb313a29d 2103 cgreen_1.6.3-1.dsc 209041133af7581df0f8c57b1225ddd94587988bb2c2cd7cb85bf5fe7f8090b0 461875 cgreen_1.6.3.orig.tar.gz 0d87ff902ea6db16a99f19b557765ffc8046afceabe8a9f38c3951f61ea1f87b 5872 cgreen_1.6.3-1.debian.tar.xz Files: 7ac4e0cb2017b05d3ace44d7e0a6d0aa 2103 libs optional cgreen_1.6.3-1.dsc 41752dc86b09810e4d02d05222914c20 461875 libs optional cgreen_1.6.3.orig.tar.gz 2a58a6caf352ba7ba891676a7c84619e 5872 libs optional cgreen_1.6.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOqx5beTsH5XZFt4rQPKZLOx+xqsFAmUhYMoACgkQQPKZLOx+ xqsJRA//SITtM8RmnPpdoJvqmxpOpnT3uU9PPZ6znaRQczC0ZFRAxOz9wR+6XUed Y/fUL6Oz1tKQxiWoydzA0dNX00sdwr4KJUcTzV1k7kQ/6RHthsZ3Uu8VoQinWJ8W S/3IhttCQAZ5Jc9DV9OE0quDUhTIUH3MmQVLfECUThl3KXy5nYHkmY65B2j9GY6s OH1zIeC5JbuWO3TXXLyeGSKiY+8wRwjDQQj9EjVc5HsXdXYvHWxs4P1naUOpiLWm Yy+8nmUSvwZYuOpZpWOy55w6Oj9V5IPAgWChBmyKUSDEs88/95VDytlV19WgSar4 U2OI9wYa94K2ZGcXaYvdV8awPSVh2p0nnI0ltVtGWlN2dJuetfX9dp2j6ogNyET1 GCe+44Sn8UBuPcE7LJuq7WUm3fzgQsBzN0cHD55AAb/rdkCUWNjWg6evbbN/kPfK fO1vWIPIyTEsvByB0XnHYWyaLhkBuw5LVIi400DJ+bxVPbBTV8QcWSfwIPSVVzRF OizijKGAdbr56KXUjyKPzyuVwHnRpemYOC/ThHj2BsdYotQcejIajO9WCOrlPGjx JXRrj55dZVSeJV5N+LoE08H1LSsRdPQObw0KGz0JNo1xOIbRKJxow8cv0WcvIC4T V2rObLi5FG0/IyQud6Kbw3OyMyXJMvtV4iIlBua7zBJmknkEY24= =oeO4 -END PGP SIGNATURE End Message ---
Bug#1053625: rust-extprim: Remove from Debian?
Source: rust-extprim Version: 1.7.1-1 Severity: serious Tags: trixie sid X-Debbugs-CC: sylves...@debian.org rust-extprim has no reverse dependencies. Should we remove it from Debian? This was proposed here: https://lists.debian.org/debian-rust/2022/10/msg0.html Dropping the old semver dependency was easy; it was basically half done already, so rust-extprim isn't currently causing problems in Debian. Thank you, Jeremy Bícha
Bug#1042123: python-aiortc: FTBFS: unsatisfiable build-dependency: python3-aioice (< 0.9) but 0.9.0-1 is to be installed
Source: python-aiortc Version: 1.4.0-2 Followup-For: Bug #1042123 Tags: patch Dear Maintainer, I just rebuild the package with normal python3-aioice but it seems it works. So am I missing something here? -- Regards, -- Bo YU diff -Nru python-aiortc-1.4.0/debian/changelog python-aiortc-1.4.0/debian/changelog --- python-aiortc-1.4.0/debian/changelog2023-02-01 19:53:51.0 +0800 +++ python-aiortc-1.4.0/debian/changelog2023-10-07 21:22:34.0 +0800 @@ -1,3 +1,10 @@ +python-aiortc (1.4.0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * No limited version on B-D for pyhon3-aioice + + -- Bo YU Sat, 07 Oct 2023 21:22:34 +0800 + python-aiortc (1.4.0-2) unstable; urgency=medium * add patch cherry-picked upstream diff -Nru python-aiortc-1.4.0/debian/control python-aiortc-1.4.0/debian/control --- python-aiortc-1.4.0/debian/control 2023-02-01 19:53:51.0 +0800 +++ python-aiortc-1.4.0/debian/control 2023-09-28 10:50:33.0 +0800 @@ -8,8 +8,7 @@ dh-sequence-sphinxdoc, libopus-dev, libvpx-dev, - python3-aioice (<< 0.9) , - python3-aioice (>= 0.8) , + python3-aioice , python3-all-dev, python3-av (<< 11) , python3-av (>= 9) , signature.asc Description: PGP signature
Bug#1053612: marked as done (driftnet: FTBFS on s390x)
Your message dated Sat, 07 Oct 2023 13:49:13 + with message-id and subject line Bug#1053612: fixed in driftnet 1.5.0-0.2 has caused the Debian Bug report #1053612, regarding driftnet: FTBFS on s390x 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.) -- 1053612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: driftnet Version: 1.5.0-0.1 Severity: serious My NMU does not build on s390x. I have created a fix at https://github.com/deiv/driftnet/pull/50 --- End Message --- --- Begin Message --- Source: driftnet Source-Version: 1.5.0-0.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of driftnet, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated driftnet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2023 13:31:13 + Source: driftnet Architecture: source Version: 1.5.0-0.2 Distribution: unstable Urgency: medium Maintainer: David Suárez Changed-By: Bastian Germann Closes: 1053612 Changes: driftnet (1.5.0-0.2) unstable; urgency=medium . * Non-maintainer upload * Patch: Recover else clause in endianess if (Closes: #1053612) * d/watch: Terminate opts before URL Checksums-Sha1: 804fc73e2dd8fff5571c3b78c7db045b01e8dcb5 1795 driftnet_1.5.0-0.2.dsc e269d74a6b2ebbee330aadd04b451d9da21d87d6 5468 driftnet_1.5.0-0.2.debian.tar.xz facceb1c82897413db69e06cf2d235082d97f783 5813 driftnet_1.5.0-0.2_source.buildinfo Checksums-Sha256: ed7f0386813c72317eac55ef6c2e7b8b1cc5f475451afa00576e4e35ba0e56e9 1795 driftnet_1.5.0-0.2.dsc e76351676f3a8e15c307c09f29770328dc77414e51fb453346c241dd0d7fb3ca 5468 driftnet_1.5.0-0.2.debian.tar.xz bdf16bf99c685cb01efc36ec8482a1df5ffc4f65baa0a7c6cb04edd808e7 5813 driftnet_1.5.0-0.2_source.buildinfo Files: 3cbe5d01623d4a69386269ed4c425387 1795 admin optional driftnet_1.5.0-0.2.dsc b118bd1a04c61a13dcd67c2f0ed54d73 5468 admin optional driftnet_1.5.0-0.2.debian.tar.xz 2e2945937fd039ce7f32358a78ca27a2 5813 admin optional driftnet_1.5.0-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUhXtwQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFNjwDADFetNEEaYh/D7EzqULmsnqFhkT8hqvLH6e MRqHXMxZA6vSTlLIu89uNLcTeae3d9LaNzGdMKyzS9I4/yqBK2nB55zIo0tEERJz hB/idnUyzu/tFpDo2aAzB8Zjw1w9msXh5Z03D8Ni090tRTn/JE5tc3lDyocCsMhB xOK7UUsfOT0i1OBw976ddrJj4/HdoOuHjCUZjjDqs0JJuEdas6iE5NxsqnlSswo1 9ZADlgh8efX+GOPzhSdhaWvVXTiYprFh3jAdCOLtvkpHD612qpnD9uxFJFm1vNvj TDGqPn6HDNEEoLGyAO3KKaszX0dLt8m8ABDg9NQAlLregwQOYOwk7F1PWGQWO/Si DReSZTz/IWSa6wwjzgtYIOmxHO8uEZqr+IH9YyLSM0vr9Sfh0kTaNY0oWREkiFQI epFP1M1yw47Xdje+2Ac2SgZtUYZwSqUxYO5kuduIi0L/OPHGAp6QRNfmUNL/kH2E 5bb1YXI4bXpdyPSo8nFyb44R0h4ELEo= =RMf3 -END PGP SIGNATURE End Message ---
Bug#1053612: driftnet: FTBFS on s390x
I am uploading a NMU to fix this. The debdiff is attached.diff -Nru driftnet-1.5.0/debian/changelog driftnet-1.5.0/debian/changelog --- driftnet-1.5.0/debian/changelog 2023-09-22 22:35:48.0 +0200 +++ driftnet-1.5.0/debian/changelog 2023-10-07 15:31:13.0 +0200 @@ -1,3 +1,11 @@ +driftnet (1.5.0-0.2) unstable; urgency=medium + + * Non-maintainer upload + * Patch: Recover else clause in endianess if (Closes: #1053612) + * d/watch: Terminate opts before URL + + -- Bastian Germann Sat, 07 Oct 2023 13:31:13 + + driftnet (1.5.0-0.1) unstable; urgency=medium * Non-maintainer upload diff -Nru driftnet-1.5.0/debian/patches/Recover-else-clause-in-endianess-if.patch driftnet-1.5.0/debian/patches/Recover-else-clause-in-endianess-if.patch --- driftnet-1.5.0/debian/patches/Recover-else-clause-in-endianess-if.patch 1970-01-01 01:00:00.0 +0100 +++ driftnet-1.5.0/debian/patches/Recover-else-clause-in-endianess-if.patch 2023-10-07 15:31:13.0 +0200 @@ -0,0 +1,23 @@ +Origin: https://github.com/deiv/driftnet/pull/50 +From: Bastian Germann +Date: Sat, 7 Oct 2023 15:06:52 +0200 +Subject: Recover else clause in endianess if + +The else clause was included in the inner (GTK3) if clause in +465a1ff68a (Add RGB byte ordering implementation in PEL related macros). +--- + src/display/img.h | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/src/display/img.h b/src/display/img.h +index 331095b..2f99ada 100644 +--- a/src/display/img.h b/src/display/img.h +@@ -69,6 +69,7 @@ typedef uint32_t pel; + # define GETB(p) ((chan)(((p) & (pel)0xff00) >> 24)) + # define GETA(p) ((chan)(((p) & (pel)0x00ff) )) + #endif ++#else + # error "no endianness defined" + #endif + diff -Nru driftnet-1.5.0/debian/patches/series driftnet-1.5.0/debian/patches/series --- driftnet-1.5.0/debian/patches/series1970-01-01 01:00:00.0 +0100 +++ driftnet-1.5.0/debian/patches/series2023-10-07 15:31:13.0 +0200 @@ -0,0 +1 @@ +Recover-else-clause-in-endianess-if.patch diff -Nru driftnet-1.5.0/debian/watch driftnet-1.5.0/debian/watch --- driftnet-1.5.0/debian/watch 2023-09-22 22:35:48.0 +0200 +++ driftnet-1.5.0/debian/watch 2023-10-07 15:31:13.0 +0200 @@ -1,5 +1,5 @@ version=4 opts=\ repacksuffix=+dfsg,\ -dversionmangle=auto,\ +dversionmangle=auto \ https://github.com/deiv/driftnet/tags .*/v?(\d[\d\.]+)\.tar\.gz
Bug#1053612: driftnet: FTBFS on s390x
Source: driftnet Version: 1.5.0-0.1 Severity: serious My NMU does not build on s390x. I have created a fix at https://github.com/deiv/driftnet/pull/50
Bug#1052973: marked as done (octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1)
Hi Rafael, Le samedi 07 octobre 2023 à 14:15 +0200, Rafael Laboissière a écrit : > I have a question for the Debian Octave Group, related to Bug#1052973, > which has been fixed in version 8.3.0-3 of octave-dev. This bug was > preventing the building of the octave-image package. Should we include > octave-dev >= 8.3.0-3 in Build-Depends of the otave-image package ? I would say no. If every time that a bug is fixed in a dependency, we were to bump the version requirement, then we would basically always depend on the latest version of every package. Also, it may be possible that octave-image builds against an old version of octave-dev that was not affected by the bug. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Bug#1052973: marked as done (octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1)
Hi, I have a question for the Debian Octave Group, related to Bug#1052973, which has been fixed in version 8.3.0-3 of octave-dev. This bug was preventing the building of the octave-image package. Should we include octave-dev >= 8.3.0-3 in Build-Depends of the otave-image package ? Best, Rafael * Debian Bug Tracking System [2023-09-30 19:09]: Your message dated Sat, 30 Sep 2023 19:04:59 + with message-id and subject line Bug#1052973: fixed in octave 8.3.0-3 has caused the Debian Bug report #1052973, regarding octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 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.) -- 1052973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems From: Lucas Nussbaum Subject: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Date: Tue, 26 Sep 2023 15:46:13 +0200 To: sub...@bugs.debian.org Message-ID: Source: octave-image Version: 2.14.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Summary: 2073 tests, 1744 passed, 36 known failures, 0 skipped Some tests failed. Giving up... make: *** [debian/rules:12: binary] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/octave-image_2.14.0-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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. From: Debian FTP Masters Subject: Bug#1052973: fixed in octave 8.3.0-3 Date: Sat, 30 Sep 2023 19:04:59 + To: 1052973-cl...@bugs.debian.org Reply-To: Rafael Laboissière Message-Id: Source: octave Source-Version: 8.3.0-3 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of octave, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated octave 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, 30 Sep 2023 10:35:07 -0300 Source: octave Architecture: source Version: 8.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissière Closes: 1052973 Changes: octave (8.3.0-3) unstable; urgency=medium . * d/p/mkoctfile-skip-options.patch: Update patch. Thanks to Markus Mützel (Closes: #1052973) Checksums-Sha1: cede5a06bc26a1717cf59f29e3daf0a132867020 3452 octave_8.3.0-3.dsc 44d80983a0848c228544957a373b2a72422f8225 63276 octave_8.3.0-3.debian.tar.xz Checksums-Sha256: 5c725301cd046ef5a62e3d6039ad0e7ad333864c8c0a578f6c9a72bc21080f4f 3452 octave_8.3.0-3.dsc 34f4f8d890a5a9268102241a2847d76d2bb1e72c9738ea5151a023a7d54f95fa 63276 octave_8.3.0-3.debian.tar.xz Files: a4a7d3b2ebfee85ae8d90a9c6fab6e8c 3452 math optional octave_8.3.0-3.dsc 1bdf47d3560fdbf1bbd656eacaa7307f 63276 math optional octave_8.3.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAmUYaOoSHHJhZmFlbEBk ZWJpYW4ub3JnAAoJECEkqhmDeFyQzuIQAIVEaYdWmkJjSUx2D+4EBLKxOEqDOZhv 4GlAOIvYCRwM/OOe8UQJY/cXAg89KVMFKGnewuAljKz+sR7hGdt4EQp1GAcujAsQ QXHqh3UhNNn6t8oiDE5LXyu8I8Apy/EqdNss1cLQWq03D4WVNP2YttAEfXs3KRd5 NJQRMEZ8QIgEGeUad80lLtKqIQoIM75iUMUKcwPx7BwgfAp3PJDV6tuY5
Processed: affects 1053405
Processing commands for cont...@bugs.debian.org: > affects 1053405 = src:darktable Bug #1053405 [src:gcc-13] darktable: FTBFS on arm64 (gcc bug?) Removed indication that 1053405 affects src:darktable. Added indication that 1053405 affects src:darktable > thanks Stopping processing here. Please contact me if you need assistance. -- 1053405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
