Bug#1001669: closed by Debian FTP Masters
On Thu, 28 Jul 2022 22:11:34 +0200 =?UTF-8?Q?Aniol_Mart=c3=ad?= wrote: On Thu, 28 Jul 2022 19:09:46 +0200 Gianfranco Costamagna wrote: > On Sun, 27 Mar 2022 19:24:05 +0200 =?UTF-8?Q?Aniol_Mart=c3=ad?= wrote: > > On Wed, 23 Mar 2022 09:09:00 +0100 Aniol Martí > > wrote:> I've tried several times and I can't reproduce the bug. I would > > need > > > further details or assistance. Besides, I also noticed that the last > > > test passed fine: > > > https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/log.gz > > > > I've added some verbosity to the test and I've tried in with Salsa and > > the problem seems to be the following: > > > > ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted > > (errno=1) > > > > Although I've added "isolation-container" to the test restrictions it > > still fails. Maybe there have been some changes in the Docker configuration? > > > > Regards, > > Aniol > > > > Hello, I tested on Ubuntu the following patch > http://launchpadlibrarian.net/615132752/openvpn-auth-ldap_2.0.4-2_2.0.4-2ubuntu1.diff.gz > due to new easy-rsa requiring one single "vars" file in the directory, > and now at least in Ubuntu autopkgtests are passing. > > G. > Hi, I've just tested it but autopkgtest still fails in Salsa because it cannot open a TUN/TAP device in the container: 2022-07-28 20:05:06 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) If I can fix this I will need to temporary disable this test. https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/s390x/o/openvpn-auth-ldap/20220728_161439_07125@/log.gz In Ubuntu it works correctly, maybe its something related to the test environment? You can also mark the test as superficial if I remember correctly, or as flaky, so it runs but doesn't stop migration, and then in case the infrastructure gets "fixed" you can notice the change of status. G. Regards, Aniol
Bug#1003165: scikit-learn testing migration
Am Thu, Jul 28, 2022 at 08:15:45PM -0700 schrieb M. Zhou: > I have a long-term power 9 VM (not QEMU) as testbed. > I'm trying to investigate the issues for release architectures, > but this package is too slow to build with QEMU (multiple hours). > (abel.debian.org is also extremely slow for scikit-learn) > I've not yet given up, but the build speed means I cannot > address this issue in timely manner. I just like to repeat my point: If the package is to slow on release architectures, that we will not manage to fix it, it is in the interest of our users to not support the problematic architectures in favour of providing it for the architetures where the package is used in practice. I have perfectly understood that we will loose several packages on that architectures and that this is not a good step. But having those packages not at all is eve worse. Kind regards Andreas. -- http://fam-tille.de
Bug#1016195: podman: fails to run any container
Package: podman
Version: 3.0.1+dfsg1-3+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vincent.olivert.ri...@gmail.com
Dear Maintainer,
I'm strictly running Debian stable with no packages from testing or
unstable.
When trying to run any container with podman I see the following error:
$ podman run --rm -it debian:bullseye-slim bash
Error: OCI runtime error: container_linux.go:367: starting container process
caused: process_linux.go:340: applying cgroup configuration for process caused:
error while starting unit
"libpod-410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3.scope"
with properties [{Name:Description Value:"libcontainer container
410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3"} {Name:Slice
Value:"user.slice"} {Name:PIDs Value:@au [69240]} {Name:Delegate Value:true}
{Name:MemoryAccounting Value:true} {Name:CPUAccounting Value:true}
{Name:IOAccounting Value:true} {Name:DefaultDependencies Value:false}
{Name:DevicePolicy Value:"strict"} {Name:DeviceAllow Value:@a(ss) []}
{Name:DeviceAllow Value:["INVALID", "INVALID", "INVALID", "INVALID", "INVALID",
"INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID"]}
{Name:TasksAccounting Value:true} {Name:TasksMax Value:@t 2048}]: error
creating systemd unit
`libpod-410aba7b65566d9ddf2f0d2f188a22ed53577b90eea67e773c8294fa8bd252f3.scope`:
got `failed`
I tried replacing runc with crun, but the same problem persist, although
the error message is shorter:
$ podman run --rm -it debian:bullseye-slim bash
Error: OCI runtime error: error creating systemd unit
`libpod-df9c347e24f4ea213f8c81d6211f60e015e48b2f4b9118558f9fa95f8c7610fd.scope`:
got `failed`
Just in case it matters, my system is up to date and the version of
systemd I have installed is 247.3-7.
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.10.0-16-arm64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1.1
ii containernetworking-plugins 0.9.0-1+b6
ii golang-github-containers-common 0.33.4+ds1-1+deb11u1
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc62.31-13+deb11u3
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.14.0-1+b2
ii libseccomp2 2.5.1-1+deb11u1
ii runc 1.0.0~rc93+ds1-5+deb11u2
Versions of packages podman recommends:
ii buildah 1.19.6+dfsg1-1+b6
ii fuse-overlayfs1.4.0-1
ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b7
ii slirp4netns 1.0.1-2
ii tini 0.19.0-1
ii uidmap1:4.8.1-1
Versions of packages podman suggests:
pn containers-storage
pn docker-compose
-- no debconf information
Processed: Re: Bug#1012941: Info received and FILED only (no " warning: ‘unsigned char* MD5" now)
Processing commands for cont...@bugs.debian.org: > found 1012941 5.2.1-1 Bug #1012941 [src:grub-customizer] grub-customizer: ftbfs with GCC-12 Marked as found in versions grub-customizer/5.2.1-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 1012941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012941: no " warning: ‘unsigned char* MD5" now
Control: find -1 5.2.1-1 I build the 5.2.1-1 in my notebook. apt install g++ -t=sid There is not " warning: ‘unsigned char* MD5" error lines now. The last error logs is: In file included from /home/atzlinux/devel/office/grub-customizer/src/main/proxy.cpp:32: /home/atzlinux/devel/office/grub-customizer/src/main/../Model/ListCfg.hpp: In member function 'bool Model_ListCfg::compare(const Model_ListCfg&) const': /home/atzlinux/devel/office/grub-customizer/src/main/../Model/ListCfg.hpp:884:71: error: aggregate 'std::array >, 2> rlist' has incomplete type and cannot be defined 884 | std::array>, 2> rlist; | ^ In file included from /home/atzlinux/devel/office/grub-customizer/src/main/../Bootstrap/Factory.hpp:34, from /home/atzlinux/devel/office/grub-customizer/src/main/client.cpp:33: /home/atzlinux/devel/office/grub-customizer/src/main/../Bootstrap/../Model/ListCfg.hpp: In member function 'bool Model_ListCfg::compare(const Model_ListCfg&) const': /home/atzlinux/devel/office/grub-customizer/src/main/../Bootstrap/../Model/ListCfg.hpp:884:71: error: aggregate 'std::array >, 2> rlist' has incomplete type and cannot be defined 884 | std::array>, 2> rlist; | ^ make[3]: *** [CMakeFiles/grubcfg-proxy.dir/build.make:85: CMakeFiles/grubcfg-proxy.dir/src/main/proxy.cpp.o] Error 1 make[3]: Leaving directory '/home/atzlinux/devel/office/grub-customizer/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:128: CMakeFiles/grubcfg-proxy.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs [ 62%] Building CXX object CMakeFiles/grub-customizer.dir/src/Bootstrap/FactoryImpl/GlibThread.cpp.o /usr/bin/c++ -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 -I/usr/lib/x86_64-linux-gnu/atkmm-1.6/include -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/atk-1.0 -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -ffile-prefix-map=/home/atzlinux/devel/office/grub-customizer=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -std=c++11 -o CMakeFiles/grub-customizer.dir/src/Bootstrap/FactoryImpl/GlibThread.cpp.o -c /home/atzlinux/devel/office/grub-customizer/src/Bootstrap/FactoryImpl/GlibThread.cpp [ 75%] Building CXX object CMakeFiles/grub-customizer.dir/src/Bootstrap/FactoryImpl/GLibRegex.cpp.o /usr/bin/c++ -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 -I/usr/lib/x86_64-linux-gnu/atkmm-1.6/include -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/atk-1.0 -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -ffile-prefix-map=/home/atzlinux/devel/office/grub-customizer=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -std=c++11 -o CMakeFiles/grub-customizer.dir/src/Bootstrap/FactoryImpl/GLibRegex.cpp.o -c /home/atzlinux/devel/office/grub-customizer/src/Bootstrap/FactoryImpl/GLibRegex.cpp In file included from /home/atzlinux/devel/office/grub-customizer/src/B
Bug#1003165: scikit-learn testing migration
I have a long-term power 9 VM (not QEMU) as testbed. I'm trying to investigate the issues for release architectures, but this package is too slow to build with QEMU (multiple hours). (abel.debian.org is also extremely slow for scikit-learn) I've not yet given up, but the build speed means I cannot address this issue in timely manner. On Thu, 2022-07-28 at 10:15 +0200, Andreas Tille wrote: > Hi Graham, > > Am Thu, Jul 28, 2022 at 09:15:06AM +0200 schrieb Graham Inggs: > > Hi > > > > On Wed, 27 Jul 2022 at 17:57, M. Zhou wrote: > > > The previous segfault on armel becomes Bus Error on armel and armhf. > > > I can build it on Power9, but it seems that the test fails on power8 (our > > > buildd). > > > > In #1003165, one of the arm porters wrote they are happy to look at > > the bus errors, but the baseline issue should be fixed first. > > ... this was five months ago and silence since then. We've lost lots of > packages in testing and I see no progress here. It seems upstream is not > actually keen on working on this as well. Meanwhile they stepped forward > with new releases and I simply refreshed the issues for the new version > (which are the same and not solved). > > Currently we have bus errors on arm 32 bit architectures and a baseline > violation on power. If there is no solution at the horizon I'd vote for > excluding these three architectures instead of sit and wait (which is all > I can personally do in this topic). > > > > I have skimmed over the build logs and one of the main issues is the use > > > of > > > -march flags to enforce a certain baseline [1]: > > > > > > powerpc64le-linux-gnu-gcc: error: unrecognized command-line option > > > ‘-march=native’; did you mean ‘-mcpu=native’? > > > > This may be the cause of the test failures on power8. > > Could someone give this a try? I know I could use a porter box to do > so but my time is to limited to do it in a sensible time frame. > > Kind regards > > Andreas. >
Processed: reassign 1015044 to python3-setuptools-scm
Processing commands for cont...@bugs.debian.org: > reassign 1015044 python3-setuptools-scm 7.0.5-1 Bug #1015044 [src:sshuttle] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Bug reassigned from package 'src:sshuttle' to 'python3-setuptools-scm'. No longer marked as found in versions sshuttle/1.1.0-1. Ignoring request to alter fixed versions of bug #1015044 to the same values previously set Bug #1015044 [python3-setuptools-scm] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Marked as found in versions setuptools-scm/7.0.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978830: about gtkhash ITA
Hi Arnaud, Do you want ITA gtkhash package now? This package had orphan now, see #1015845. If you don't want ITA it, I would do ITA. Regards, -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature Description: OpenPGP digital signature
Bug#1012904: marked as done (ceph: ftbfs with GCC-12)
Your message dated Fri, 29 Jul 2022 03:16:30 +0300
with message-id
and subject line Fixed in 16.2.10+ds-1
has caused the Debian Bug report #1012904,
regarding ceph: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1012904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ceph
Version: 16.2.7+ds-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/ceph_16.2.7+ds-4_unstable_gcc12.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
/<>/src/osd/osd_types.h:3621:11: note: in expansion of macro
‘ldpp_dout’
3621 | ldpp_dout(dpp, 10) << "build_prior prior osd." << so.osd
| ^
/<>/src/common/dout.h:106:21: note:
‘ceph::dout::dynamic_marker_t ceph::dout::need_dynamic(T&&) [with T =
unsigned int]’ declared here
106 | dynamic_marker_t need_dynamic(T&& t) {
| ^~~~
/<>/src/osd/osd_types.h: In lambda function:
/<>/src/common/dout.h:185:56: error: call to non-‘constexpr’
function ‘ceph::dout::dynamic_marker_t ceph::dout::need_dynamic(T&&) [with T
= unsigned int]’
185 | dout_impl(pdpp->get_cct(),
ceph::dout::need_dynamic(pdpp->get_subsys()), v) \
|
^~~~
/<>/src/common/dout.h:156:58: note: in definition of macro
‘dout_impl’
156 | return (cctX->_conf->subsys.template should_gather());
\
| ^~~
/<>/src/osd/osd_types.h:3635:9: note: in expansion of macro
‘ldpp_dout’
3635 | ldpp_dout(dpp, 10) << "build_prior possibly went active+rw,"
| ^
/<>/src/common/dout.h:106:21: note:
‘ceph::dout::dynamic_marker_t ceph::dout::need_dynamic(T&&) [with T =
unsigned int]’ declared here
106 | dynamic_marker_t need_dynamic(T&& t) {
| ^~~~
/<>/src/osd/osd_types.h: In lambda function:
/<>/src/common/dout.h:185:56: error: call to non-‘constexpr’
function ‘ceph::dout::dynamic_marker_t ceph::dout::need_dynamic(T&&) [with T
= unsigned int]’
185 | dout_impl(pdpp->get_cct(),
ceph::dout::need_dynamic(pdpp->get_subsys()), v) \
|
^~~~
/<>/src/common/dout.h:156:58: note: in definition of macro
‘dout_impl’
156 | return (cctX->_conf->subsys.template should_gather());
\
| ^~~
/<>/src/osd/osd_types.h:3645:3: note: in expansion of macro
‘ldpp_dout’
3645 | ldpp_dout(dpp, 10) << "build_prior final: probe " << probe
| ^
/<>/src/common/dout.h:106:21: note:
‘ceph::dout::dynamic_marker_t ceph::dout::need_dynamic(T&&) [with T =
unsigned int]’ declared here
106 | dynamic_marker_t need_dynamic(T&& t) {
| ^~~~
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:2116: src/CMakeFiles/common-objs.dir/all]
Error 2
[ 3%] Building CXX object
src/auth/CMakeFiles/common-auth-objs.dir/cephx/CephxClientHandler.cc.o
cd /<>/obj-x86_64-linux-gnu/src/auth && /usr/bin/c++
-DBOOST_ASIO_D
Bug#1016045: marked as done (sbcl FTBFS on !amd64)
Your message dated Thu, 28 Jul 2022 22:20:01 +
with message-id
and subject line Bug#1016045: fixed in sbcl 2:2.2.6-2
has caused the Debian Bug report #1016045,
regarding sbcl FTBFS on !amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbcl
Version: 2:2.2.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=sbcl&ver=2%3A2.2.6-1
...
cd doc/manual && make docstrings && make
make[2]: Entering directory '/<>/doc/manual'
touch tempfiles-stamp
sh make-tempfiles.sh "" ""docstrings/"" && touch "docstrings/"
/creating docstring snippets
from SBCL='../../src/runtime/sbcl --core ../../output/sbcl.core'
for documented contribs
(sb-aclrepl sb-bsd-sockets sb-concurrency sb-cover sb-graph sb-grovel
sb-md5 sb-posix sb-queue sb-rotate-byte sb-simd sb-simple-streams sb-sprof)
for packages
(COMMON-LISP SB-ACLREPL SB-ALIEN SB-BSD-SOCKETS SB-CONCURRENCY SB-COVER
SB-DEBUG SB-EXT SB-GRAPH SB-GRAY SB-GROVEL SB-MD5 SB-MOP SB-PCL SB-POSIX
SB-PROFILE SB-QUEUE SB-ROTATE-BYTE SB-SEQUENCE SB-SIMD SB-SIMPLE-STREAMS
SB-SPROF SB-SYS SB-THREAD SB-UNICODE)
Unhandled SB-INT:EXTENSION-FAILURE in thread #:
Don't know how to REQUIRE sb-simd.
See also:
The SBCL Manual, Variable *MODULE-PROVIDER-FUNCTIONS*
The SBCL Manual, Function REQUIRE
Backtrace for: #
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK # # :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #)
2: (INVOKE-DEBUGGER #)
3: (ERROR SB-INT:EXTENSION-FAILURE :FORMAT-CONTROL "Don't know how to ~S ~A."
:FORMAT-ARGUMENTS (REQUIRE "sb-simd") :REFERENCES ((:SBCL :VARIABLE
*MODULE-PROVIDER-FUNCTIONS*) (:SBCL :FUNCTION REQUIRE)))
4: (REQUIRE "sb-simd" NIL)
5: (SB-KERNEL:%MAP-FOR-EFFECT-ARITY-1 # (("sb-aclrepl" . "SB-ACLREPL")
("sb-bsd-sockets" . "SB-BSD-SOCKETS") ("sb-concurrency" . "SB-CONCURRENCY")
("sb-cover" . "SB-COVER") ("sb-graph" . "SB-GRAPH") ("sb-grovel" . "SB-GROVEL")
("sb-md5" . "SB-MD5") ("sb-posix" . "SB-POSIX") ("sb-queue" . "SB-QUEUE")
("sb-rotate-byte" . "SB-ROTATE-BYTE") ("sb-simd" . "SB-SIMD")
("sb-simple-streams" . "SB-SIMPLE-STREAMS") ...))
6: (GENERATE-DOCSTRINGS-TEXINFO "../../src/runtime/sbcl --core
../../output/sbcl.core" :DOCSTRING-DIRECTORY "docstrings/")
7: ((LAMBDA NIL :IN "/<>/doc/manual/generate-texinfo.lisp"))
8: (SB-INT:SIMPLE-EVAL-IN-LEXENV (DESTRUCTURING-BIND (PROGRAM RUNTIME
DOCSTRING-DIRECTORY) *POSIX-ARGV* (DECLARE (IGNORE PROGRAM))
(GENERATE-DOCSTRINGS-TEXINFO RUNTIME :DOCSTRING-DIRECTORY DOCSTRING-DIRECTORY)
(EXPAND-VARIABLES) (GENERATE-EXTERNAL-FORMAT-TEXINFO)) #)
9: (EVAL-TLF (DESTRUCTURING-BIND (PROGRAM RUNTIME DOCSTRING-DIRECTORY)
*POSIX-ARGV* (DECLARE (IGNORE PROGRAM)) (GENERATE-DOCSTRINGS-TEXINFO RUNTIME
:DOCSTRING-DIRECTORY DOCSTRING-DIRECTORY) (EXPAND-VARIABLES)
(GENERATE-EXTERNAL-FORMAT-TEXINFO)) 11 NIL)
10: ((LABELS SB-FASL::EVAL-FORM :IN SB-INT:LOAD-AS-SOURCE) (DESTRUCTURING-BIND
(PROGRAM RUNTIME DOCSTRING-DIRECTORY) *POSIX-ARGV* (DECLARE (IGNORE PROGRAM))
(GENERATE-DOCSTRINGS-TEXINFO RUNTIME :DOCSTRING-DIRECTORY DOCSTRING-DIRECTORY)
(EXPAND-VARIABLES) (GENERATE-EXTERNAL-FORMAT-TEXINFO)) 11)
11: ((LAMBDA (SB-KERNEL:FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN
SB-INT:LOAD-AS-SOURCE) (DESTRUCTURING-BIND (PROGRAM RUNTIME
DOCSTRING-DIRECTORY) *POSIX-ARGV* (DECLARE (IGNORE PROGRAM))
(GENERATE-DOCSTRINGS-TEXINFO RUNTIME :DOCSTRING-DIRECTORY DOCSTRING-DIRECTORY)
(EXPAND-VARIABLES) (GENERATE-EXTERNAL-FORMAT-TEXINFO)) :CURRENT-INDEX 11)
12: (SB-C::%DO-FORMS-FROM-INFO #
# SB-C::INPUT-ERROR-IN-LOAD)
13: (SB-INT:LOAD-AS-SOURCE #>/doc/manual/generate-texinfo.lisp" {1005A40093}> :VERBOSE NIL
:PRINT NIL :CONTEXT "loading")
14: ((LABELS SB-FASL::LOAD-STREAM-1 :IN LOAD) #>/doc/manual/generate-texinfo.lisp" {1005A40093}> NIL)
15: (SB-FASL::CALL-WITH-LOAD-BINDINGS # #>/doc/manual/generate-texinfo.lisp" {1005A40093}> NIL
#>/doc/manual/generate-texinfo.lisp"
{1005A40093}>)
16: (LOAD #>/doc/manual/generate-texinfo.lisp" {1005A40093}> :VERBOSE NIL
:PRINT NIL :IF-DOES-NOT-EXIST :ERROR :EXTERNAL-FORMAT :DEFAULT)
17: ((FLET SB-IMPL::LOAD-SCRIPT :IN SB-IMPL::PROCESS-SCRIPT) #>/doc/manual/generate-texinfo.lisp" {1005A40093}>)
18: ((FLET SB-UNIX::BODY :IN SB-IMPL::PROCESS-SCRIPT))
19: ((FLET "WITHOUT-INTERRUPTS-BODY-11" :IN SB-IMPL::PROCESS-SCRIPT))
20: (SB-IMPL::PROCESS-SCRIPT "generate-texinfo.lisp")
21: (SB-IMPL::TOPLEVEL-INIT)
22: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP))
23: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::S
Bug#1015105: marked as done (senlin-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.
Your message dated Thu, 28 Jul 2022 21:50:50 +
with message-id
and subject line Bug#1015105: fixed in senlin-dashboard 5.0.0-2
has caused the Debian Bug report #1015105,
regarding senlin-dashboard: FTBFS: ImportError: cannot import name
'ugettext_lazy' from 'django.utils.translation'
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
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.)
--
1015105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: senlin-dashboard
Version: 5.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> NOSE_WITH_OPENSTACK=1 \
> NOSE_OPENSTACK_COLOR=1 \
> NOSE_OPENSTACK_RED=0.05 \
> NOSE_OPENSTACK_YELLOW=0.025 \
> NOSE_OPENSTACK_SHOW_ELAPSED=1 \
> DJANGO_SETTINGS_MODULE=senlindash_board.test.settings \
> python3-coverage run \
> /<>/manage.py test senlin_dashboard
> --settings=senlin_dashboard.test.settings
> Creating test database for alias 'default'...
> Found 13 test(s).
> Destroying test database for alias 'default'...
> Traceback (most recent call last):
> File "/<>/manage.py", line 23, in
> execute_from_command_line(sys.argv)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 440, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 24, in run_from_argv
> super().run_from_argv(argv)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 414, in run_from_argv
> self.execute(*args, **cmd_options)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 460, in execute
> output = self.handle(*args, **options)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 68, in handle
> failures = test_runner.run_tests(test_labels)
> File "/usr/lib/python3/dist-packages/django/test/runner.py", line 1006, in
> run_tests
> self.run_checks(databases)
> File "/usr/lib/python3/dist-packages/django/test/runner.py", line 925, in
> run_checks
> call_command("check", verbosity=self.verbosity, databases=databases)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 198, in call_command
> return command.execute(*args, **defaults)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 460, in execute
> output = self.handle(*args, **options)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/check.py",
> line 76, in handle
> self.check(
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 487, in check
> all_issues = checks.run_checks(
> File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line
> 88, in run_checks
> new_errors = check(app_configs=app_configs, databases=databases)
> File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 14,
> in check_url_config
> return check_resolver(resolver)
> File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 24,
> in check_resolver
> return check_method()
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 480,
> in check
> for pattern in self.url_patterns:
> File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 49,
> in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 696,
> in url_patterns
> patterns = getattr(self.urlconf_module, "urlpatterns",
> self.urlconf_module)
> File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 49,
> in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 689,
> in urlconf_module
> return import_module(self.urlconf_name)
> File "/usr/lib/python3.10/importlib/__i
Processed: Bug#1015105 marked as pending in senlin-dashboard
Processing control commands: > tag -1 pending Bug #1015105 [src:senlin-dashboard] senlin-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) Added tag(s) pending. -- 1015105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015105: marked as pending in senlin-dashboard
Control: tag -1 pending Hello, Bug #1015105 in senlin-dashboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/senlin-dashboard/-/commit/4bd93a8bc3807d07b1442fc1573398c49964f2a6 * Add Django 4 compat patches (Closes: #1015105): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015105
Bug#1015050: marked as done (heat-dashboard: FTBFS: KeyError: 'template_generator')
Your message dated Thu, 28 Jul 2022 21:35:44 +
with message-id
and subject line Bug#1015050: fixed in heat-dashboard 7.0.0-2
has caused the Debian Bug report #1015050,
regarding heat-dashboard: FTBFS: KeyError: 'template_generator'
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.)
--
1015050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heat-dashboard
Version: 7.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> for i in 3.9 3.10 ; do \
> PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages \
> NOSE_WITH_OPENSTACK=1 \
> NOSE_OPENSTACK_COLOR=1 \
> NOSE_OPENSTACK_RED=0.05 \
> NOSE_OPENSTACK_YELLOW=0.025 \
> NOSE_OPENSTACK_SHOW_ELAPSED=1 \
> python$i /<>/manage.py test heat_dashboard.test -v
> 2 --settings=heat_dashboard.test.settings --exclude-tag integration ; \
> done
> WARNING:root:Error importing
> heat_dashboard.enabled._1610_project_orchestration_panel
> ERROR:root:cannot import name 'ugettext_lazy' from 'django.utils.translation'
> (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
> Traceback (most recent call last):
> File
> "/usr/lib/python3/dist-packages/openstack_dashboard/utils/settings.py", line
> 58, in import_submodules
> submodule = import_module(name)
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File
> "/<>/heat_dashboard/enabled/_1610_project_orchestration_panel.py",
> line 13, in
> from django.utils.translation import ugettext_lazy as _
> ImportError: cannot import name 'ugettext_lazy' from
> 'django.utils.translation'
> (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
> Excluding test tag(s): integration.
> Found 26 test(s).
> Creating test database for alias 'default'
> ('file:memorydb_default?mode=memory&cache=shared')...
> Operations to perform:
> Synchronize unmigrated apps: admin, compressor, horizon, humanize,
> identity, messages, openstack_auth, openstack_dashboard, project, settings,
> staticfiles
> Apply all migrations: auth, contenttypes, sessions
> Synchronizing apps without migrations:
> Creating tables...
> Creating table openstack_auth_user
> Running deferred SQL...
> Running migrations:
> Applying contenttypes.0001_initial... OK
> Applying contenttypes.0002_remove_content_type_name... OK
> Applying auth.0001_initial... OK
> Applying auth.0002_alter_permission_name_max_length... OK
> Applying auth.0003_alter_user_email_max_length... OK
> Applying auth.0004_alter_user_username_opts... OK
> Applying auth.0005_alter_user_last_login_null... OK
> Applying auth.0006_require_contenttypes_0002... OK
> Applying auth.0007_alter_validators_add_error_messages... OK
> Applying auth.0008_alter_user_username_max_length... OK
> Applying auth.0009_alter_user_last_name_max_length... OK
> Applying auth.0010_alter_group_name_max_length... OK
> Applying auth.0011_update_proxy_permissions... OK
> Applying auth.0012_alter_user_first_name_max_length... OK
> Applying sessions.0001_initial... OK
> System check identified no issues (0 silenced).
> heat_dashboard.test.tests.content.test_stacks (unittest.loader._FailedTest)
> ... ERROR
> heat_dashboard.test.tests.content.test_template_versions
> (unittest.loader._FailedTest) ... ERROR
> test_get_template_files
> (heat_dashboard.test.tests.api.test_heat.HeatApiTests) ... ok
> test_get_template_files_invalid
> (heat_dashboard.test.tests.api.test_heat.HeatApiTests) ... ok
> test_get_template_files_with_template_data
> (heat_dashboard.test.tests.api.test_heat.HeatApiTests) ... ok
> test_get_template_files_with_template_url
> (heat_dashboard.test.tests.api.test_heat.HeatApiTests) ... ok
> test_snapshot_create (heat_dashboard.test.tests.api.test_heat.H
Processed: Bug#1015050 marked as pending in heat-dashboard
Processing control commands: > tag -1 pending Bug #1015050 [src:heat-dashboard] heat-dashboard: FTBFS: KeyError: 'template_generator' Added tag(s) pending. -- 1015050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015050: marked as pending in heat-dashboard
Control: tag -1 pending Hello, Bug #1015050 in heat-dashboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/heat-dashboard/-/commit/a8046d5e32d506fe20098017f86d0d837f9225ae * Add Django 4 support patches (Closes: #1015050): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch - django-4-django.utils.urlunquote-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015050
Processed: add tag and URL
Processing commands for cont...@bugs.debian.org: > tags 997623 + fixed-upstream Bug #997623 [src:funcparserlib] funcparserlib: FTBFS: error in funcparserlib setup command: use_2to3 is invalid. Added tag(s) fixed-upstream. > forwarded 997623 https://github.com/vlasovskikh/funcparserlib/pull/57 Bug #997623 [src:funcparserlib] funcparserlib: FTBFS: error in funcparserlib setup command: use_2to3 is invalid. Set Bug forwarded-to-address to 'https://github.com/vlasovskikh/funcparserlib/pull/57'. > End of message, stopping processing here. Please contact me if you need assistance. -- 997623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1013628 marked as pending in python-django-extra-views
Processing control commands: > tag -1 pending Bug #1013628 [src:python-django-extra-views] python-django-extra-views: FTBFS: tests fail Added tag(s) pending. -- 1013628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013628: marked as pending in python-django-extra-views
Control: tag -1 pending Hello, Bug #1013628 in python-django-extra-views reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-django-extra-views/-/commit/5c6bc35f84de7960991d797421dc9ec9c70a1c3a Add patch for Django 4 compatibility (Closes: #1013628). (this message was generated automatically) -- Greetings https://bugs.debian.org/1013628
Bug#1016187: collectd: FTBFS with gcc 12 (bookworm)
Source: collectd
Version: 5.12.0-9
Severity: serious
Tags: ftbfs
`collectd` fails to build from source, both when compiled locally and
when run from a salsa pipeline.
Full log: https://salsa.debian.org/gioele/pkg-collectd/-/jobs/3046171
```
src/capabilities.c: In function 'cap_http_handler':
src/capabilities.c:209:23: error: storing the address of local variable
'({anonymous})' in '*connection_state' [-Werror=dangling-pointer=]
209 | *connection_state = &(int){44};
| ~~^~~~
src/capabilities.c:209:31: note: '({anonymous})' declared here
209 | *connection_state = &(int){44};
| ^
src/capabilities.c:209:31: note: 'connection_state' declared here
cc1: all warnings being treated as errors
make[2]: *** [Makefile:7785: src/capabilities_la-capabilities.lo] Error 1
make[2]: Leaving directory '/build/collectd-5.12.0'
make[1]: *** [Makefile:5456: all] Error 2
make[1]: Leaving directory '/build/collectd-5.12.0'
make: *** [debian/rules:277: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2
```
Regards,
--
Gioele Barabucci
Bug#1001669: closed by Debian FTP Masters
On Thu, 28 Jul 2022 19:09:46 +0200 Gianfranco Costamagna wrote: On Sun, 27 Mar 2022 19:24:05 +0200 =?UTF-8?Q?Aniol_Mart=c3=ad?= wrote: > On Wed, 23 Mar 2022 09:09:00 +0100 Aniol Martí > wrote:> I've tried several times and I can't reproduce the bug. I would > need > > further details or assistance. Besides, I also noticed that the last > > test passed fine: > > https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/log.gz > > I've added some verbosity to the test and I've tried in with Salsa and > the problem seems to be the following: > > ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted > (errno=1) > > Although I've added "isolation-container" to the test restrictions it > still fails. Maybe there have been some changes in the Docker configuration? > > Regards, > Aniol > Hello, I tested on Ubuntu the following patch http://launchpadlibrarian.net/615132752/openvpn-auth-ldap_2.0.4-2_2.0.4-2ubuntu1.diff.gz due to new easy-rsa requiring one single "vars" file in the directory, and now at least in Ubuntu autopkgtests are passing. G. Hi, I've just tested it but autopkgtest still fails in Salsa because it cannot open a TUN/TAP device in the container: 2022-07-28 20:05:06 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) If I can fix this I will need to temporary disable this test. Regards, Aniol
Bug#1013484: marked as pending in python-django-braces
Control: tag -1 pending Hello, Bug #1013484 in python-django-braces reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-django-braces/-/commit/54e41e39588575234b709c4f1fba263a4e13b181 Add patch for Django 4 compatibility (Closes: #1013484). (this message was generated automatically) -- Greetings https://bugs.debian.org/1013484
Processed: Bug#1013484 marked as pending in python-django-braces
Processing control commands: > tag -1 pending Bug #1013484 [src:python-django-braces] python-django-braces: FTBFS: AttributeError: 'WSGIRequest' object has no attribute 'is_ajax' Added tag(s) pending. -- 1013484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1013550
Processing commands for cont...@bugs.debian.org: > tags 1013550 + pending Bug #1013550 [src:sddm] sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted function ‘QCharRef& QCharRef::operator=(char)’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016127: marked as done (src:guestfs-tools: fails to migrate to testing for too long: FTBFS on i386 and ppc64el)
Your message dated Thu, 28 Jul 2022 20:29:07 +0200 with message-id <87v8rhum4s@msgid.hilluzination.de> and subject line Re: Bug#1016127: src:guestfs-tools: fails to migrate to testing for too long: FTBFS on i386 and ppc64el has caused the Debian Bug report #1016127, regarding src:guestfs-tools: fails to migrate to testing for too long: FTBFS on i386 and ppc64el 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.) -- 1016127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guestfs-tools Version: 1.48.1-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:guestfs-tools has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on i386 and ppc64el while it built there successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=guestfs-tools OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- It turned out that triggering rebuilds was enough to get guestfs-tools built, so it can migrate now. Closing the issue. Cheers, -Hilko--- End Message ---
Processed: [bts-link] source package src:ruby-jwt
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-jwt > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1011711 (http://bugs.debian.org/1011711) > # Bug title: ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: expect(e).to > be_a(TypeError) > # * https://github.com/jwt/ruby-jwt/pull/496 > # * remote status changed: open -> closed > # * closed upstream > tags 1011711 + fixed-upstream Bug #1011711 [src:ruby-jwt] ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: expect(e).to be_a(TypeError) Added tag(s) fixed-upstream. > usertags 1011711 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1011711 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001669: closed by Debian FTP Masters
On Sun, 27 Mar 2022 19:24:05 +0200 =?UTF-8?Q?Aniol_Mart=c3=ad?= wrote: On Wed, 23 Mar 2022 09:09:00 +0100 Aniol Martí wrote:> I've tried several times and I can't reproduce the bug. I would need > further details or assistance. Besides, I also noticed that the last > test passed fine: > https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/log.gz I've added some verbosity to the test and I've tried in with Salsa and the problem seems to be the following: ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) Although I've added "isolation-container" to the test restrictions it still fails. Maybe there have been some changes in the Docker configuration? Regards, Aniol Hello, I tested on Ubuntu the following patch http://launchpadlibrarian.net/615132752/openvpn-auth-ldap_2.0.4-2_2.0.4-2ubuntu1.diff.gz due to new easy-rsa requiring one single "vars" file in the directory, and now at least in Ubuntu autopkgtests are passing. G.
Bug#948318: marked as done (openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2)
Your message dated Thu, 28 Jul 2022 18:50:24 +0200 with message-id and subject line Re: Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2 has caused the Debian Bug report #948318, regarding openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openssh-server Version: 1:8.1p1-2 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading openssh-server from version 8.1p1-1 to version 8.1p1-2, using the apt command line tool, the sshd service failed on restart. Please see below the corresponding log entries : janv. 06 11:10:46 sigismund systemd[1]: Starting OpenBSD Secure Shell server... janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd: /lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/sbin/sshd) janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Failed with result 'exit-code'. janv. 06 11:10:46 sigismund systemd[1]: Failed to start OpenBSD Secure Shell server. janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. janv. 06 11:10:46 sigismund systemd[1]: Stopped OpenBSD Secure Shell server. Manual installation of the previous version brought sshd functionnal again. Best regards, Guillaume -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 5.3.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openssh-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii dpkg 1.19.7 ii libaudit1 1:2.8.5-2+b1 ii libc6 2.29-7 ii libcom-err21.45.4-1 ii libcrypt1 1:4.4.10-10 ii libgssapi-krb5-2 1.17-6 ii libkrb5-3 1.17-6 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libselinux13.0-1 ii libssl1.1 1.1.1d-2 ii libsystemd0244-3 ii libwrap0 7.6.q-30 ii lsb-base 11.1.0 ii openssh-client 1:8.1p1-2 ii openssh-sftp-server1:8.1p1-2 ii procps 2:3.3.15-2+b1 ii runit-helper 2.8.14 ii ucf3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages openssh-server recommends: ii libpam-systemd [logind] 244-3 ii ncurses-term 6.1+20191019-1 ii xauth1:1.0.10-1 Versions of packages openssh-server suggests: pn molly-guard pn monkeysphere pn rssh pn ssh-askpass pn ufw -- Configuration Files: /etc/ufw/applications.d/openssh-server [Errno 2] Aucun fichier ou dossier de ce type: '/etc/ufw/applications.d/openssh-server' -- debconf information: * ssh/use_old_init_script: true openssh-server/permit-root-login: true ssh/vulnerable_host_keys: ssh/disable_cr_auth: false ssh/new_config: true ssh/encrypted_host_key_but_no_keygen: openssh-server/password-authentication: true --- End Message --- --- Begin Message --- On 2022-07-28 01:09, Chris Hofstaedtler wrote: > Control: reassign -1 glibc > > Dear glibc Maintainers, > > this bug appears to be an upgrade issue where (old versions?) of > libc6 might have done something wrong. Maybe you can decide what to > do with/about this bug. This rather looks like a user issue with an old package that has been unpacked by hand at some point. In any case it this package version is not supported anymore. I am therefore closing the bug. Feel free to reopen if the problem is reproducible. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net--- End Message ---
Bug#1014306: RFH: crun -- lightweight OCI runtime for running containers
Package: wnpp The crun maintainer has requested help in #1014306. On Mon, 25 Jul 2022 17:54:53 +1000 Dmitry Smirnov wrote: On Friday, 22 July 2022 11:43:56 PM AEST Faidon Liambotis wrote: > Dmitry, are you still working on this package? I noticed that it's under > the debian group in Salsa -- would you be OK if someone else made an > upload? I'm not ready to abandon the package yet but can't spare any time for it at the moment, unfortunately... Of course it would be awesome if anyone could help, provided they preserve the current repository layout. > @Faidon, I suppose it would be fine to NMU and put it into DELAYED/10 > atleast till we have time for an ACK. This is triggering a bunch of > auto-rm and hence it is prudent. > Do consider doing so if you agree. Nilesh, of course NMU is OK but it would be nice if changes could be committed to repository... Note that Reinhard already uploaded 0.17+dfsg-1.1 which is committed to branch "bug.997225" which is due to be merged into "master" branch. Thank you all for your help.
Bug#1012892: marked as done (android-platform-tools: ftbfs with GCC-12)
Your message dated Thu, 28 Jul 2022 16:19:08 + with message-id and subject line Bug#1012892: fixed in android-platform-tools 29.0.6-20 has caused the Debian Bug report #1012892, regarding android-platform-tools: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:android-platform-tools Version: 29.0.6-18 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/android-platform-tools_29.0.6-18_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] make -j8 "INSTALL=install --strip-program=true" --file=debian/system/core/fastboot.mk make[2]: Entering directory '/<>' clang++ -c -o system/core/fastboot/bootimg_utils.o system/core/fastboot/bootimg_utils.cpp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -std=gnu++2a -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -D_FILE_OFFSET_BITS=64 -DPLATFORM_TOOLS_VERSION='"29.0.6"' -I/usr/include/android -Iexternal/avb -Isystem/core/adb -Isystem/core/base/include -Isystem/core/demangle/include -Isystem/core/diagnose_usb/include -Isystem/core/fs_mgr/include -Isystem/core/fs_mgr/include_fstab -Isystem/core/fs_mgr/liblp/include -Isystem/core/include -Isystem/core/libcutils/include -Isystem/core/libsparse/include -Isystem/core/libziparchive/include -Isystem/extras/ext4_utils/include -Isystem/tools/mkbootimg/include/bootimg clang++ -c -o system/core/fastboot/fastboot.o system/core/fastboot/fastboot.cpp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -std=gnu++2a -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -D_FILE_OFFSET_BITS=64 -DPLATFORM_TOOLS_VERSION='"29.0.6"' -I/usr/include/android -Iexternal/avb -Isystem/core/adb -Isystem/core/base/include -Isystem/core/demangle/include -Isystem/core/diagnose_usb/include -Isystem/core/fs_mgr/include -Isystem/core/fs_mgr/include_fstab -Isystem/core/fs_mgr/liblp/include -Isystem/core/include -Isystem/core/libcutils/include -Isystem/core/libsparse/include -Isystem/core/libziparchive/include -Isystem/extras/ext4_utils/include -Isystem/tools/mkbootimg/include/bootimg clang++ -c -o system/core/fastboot/fastboot_driver.o system/core/fastboot/fastboot_driver.cpp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -std=gnu++2a -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -D_FILE_OFFSET_BITS=64 -DPLATFORM_TOOLS_VERSION='"29.0.6"' -I/usr/include/android -Iexternal/avb -Isystem/core/adb -Isystem/core/base/include -Isystem/core/demangle/include -Isystem/core/diagnose_usb/include -Isystem/core/fs_mgr/include -Isystem/core/fs_mgr/include_fstab -Isystem/core/fs_mgr/liblp/include -Isystem/core/include -Isystem/core/libcutils/include -Isystem/core/libsparse/include -Isystem/core/libziparchive/include -Isystem/extras/ext4_utils/include -Isystem/tools/mkbootimg/include/bootimg clang++ -c -o system/core/fastboot/fs.o system/core/fastboot/fs.cpp -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-s
Bug#1015117: marked as done (manila-ui: FTBFS: AttributeError: 'NoneType' object has no attribute 'action')
Your message dated Thu, 28 Jul 2022 16:06:57 +
with message-id
and subject line Bug#1015117: fixed in manila-ui 7.0.0-2
has caused the Debian Bug report #1015117,
regarding manila-ui: FTBFS: AttributeError: 'NoneType' object has no attribute
'action'
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.)
--
1015117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: manila-ui
Version: 7.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for i in 3.9 3.10 ; do \
> PYTHON=python3 PYTHONPATH=/<>/debian/tmp
> NOSE_WITH_OPENSTACK=1 \
> NOSE_OPENSTACK_COLOR=1 \
> NOSE_OPENSTACK_RED=0.05 \
> NOSE_OPENSTACK_YELLOW=0.025 \
> NOSE_OPENSTACK_SHOW_ELAPSED=1 \
> DJANGO_SETTINGS_MODULE=manila_ui.tests.settings \
> python$i -m coverage run \
> /<>/manage.py test manila_ui -v 2
> --settings=manila_ui.tests.settings --exclude-tag integration; \
> done
> WARNING:root:"dashboards" and "default_dashboard" in (local_)settings is
> DEPRECATED now and may be unsupported in some future release. The preferred
> way to specify the order of dashboards and the default dashboard is the
> pluggable dashboard mechanism (in /<>/manila_ui/local/enabled,
> /usr/lib/python3/dist-packages/openstack_dashboard/enabled).
> Excluding test tag(s): integration.
> Found 220 test(s).
> Creating test database for alias 'default'
> ('file:memorydb_default?mode=memory&cache=shared')...
> Operations to perform:
> Synchronize unmigrated apps: admin, compressor, horizon, humanize,
> identity, messages, openstack_auth, openstack_dashboard, project, settings,
> staticfiles
> Apply all migrations: auth, contenttypes, sessions
> Synchronizing apps without migrations:
> Creating tables...
> Creating table openstack_auth_user
> Running deferred SQL...
> Running migrations:
> Applying contenttypes.0001_initial... OK
> Applying contenttypes.0002_remove_content_type_name... OK
> Applying auth.0001_initial... OK
> Applying auth.0002_alter_permission_name_max_length... OK
> Applying auth.0003_alter_user_email_max_length... OK
> Applying auth.0004_alter_user_username_opts... OK
> Applying auth.0005_alter_user_last_login_null... OK
> Applying auth.0006_require_contenttypes_0002... OK
> Applying auth.0007_alter_validators_add_error_messages... OK
> Applying auth.0008_alter_user_username_max_length... OK
> Applying auth.0009_alter_user_last_name_max_length... OK
> Applying auth.0010_alter_group_name_max_length... OK
> Applying auth.0011_update_proxy_permissions... OK
> Applying auth.0012_alter_user_first_name_max_length... OK
> Applying sessions.0001_initial... OK
> System check identified no issues (0 silenced).
> manila_ui.dashboards.project.shares (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.security_services.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_group_snapshots.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_group_types.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_groups.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_instances.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_networks.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_servers.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_snapshots.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_types.test_forms
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.share_types.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.shares.replicas.tests
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.shares.test_forms
> (unittest.loader._FailedTest) ... ERROR
> manila_ui.tests.dashboards.admin.shares.tests (unittest.loader._FailedTest)
> ... ERROR
> manila_ui.tests.das
Bug#1012999: Uploaded
FWIW Uploads did happen ( https://tracker.debian.org/news/1349600/accepted-msc-generator-81-1-source-into-unstable/ and https://tracker.debian.org/news/1349742/accepted-msc-generator-81-2-source-into-unstable/ ). At https://buildd.debian.org/status/package.php?p=msc-generator is currently: | Buildd exposure stats all 8.1-2 Installed 1h 5m x86-grnet-02 miscold | all (1) giveback | Buildd exposure stats amd64 8.1-2 Installed 1h 6m x86-ubc-01 miscold | all (1) giveback | Buildd exposure stats arm64 8.1-2 Installed 51m arm-arm-03 miscold | all (1) giveback | Buildd exposure stats armel 8.1-2 Installed 51m arm-ubc-06 miscold | all (1) giveback | Buildd exposure stats armhf 8.1-2 Installed 8m arm-arm-04 miscold | all (2) giveback | Buildd exposure stats i3868.1-2 Installed 1h 6m x86-grnet-01 miscold | all (1) giveback | Buildd exposure stats mips64el8.1-2 Installed 51m mipsel-osuosl-03miscold | all (1) giveback | Buildd exposure stats mipsel 8.1-2 Installed 28m mipsel-manda-04 miscold | all (1) giveback | Buildd exposure stats ppc64el 8.1-2 Installed 1h 6m ppc64el-osuosl-01 miscold | all (1) giveback | Buildd exposure stats s390x 8.1-2 Installed 1h 5m zani misc old | all (1) giveback In other words: Succesfull builds on all release architectures. Groeten Geert Stappers -- Silence is hard to parse
Bug#1012999: keep the issue open until the package can be built in a follow-up test rebuild.
Hello, Where to find information about the rebuild schedule? The some what template text |[This bug is targeted to the upcoming bookworm release] | |Please keep this issue open in the bug tracker for the package it |was filed for. If a fix in another package is required, please |file a bug for the other package (or clone), and add a block in this |package. Please keep the issue open until the package can be built in |a follow-up test rebuild. | |The package fails to build in a test rebuild on at least amd64 with |gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The |severity of this report will be raised before the bookworm release. does not provide any information about it. Groeten Geert Stappers P.S. Please keep 1012...@bugs.debian.org in the loop. -- Silence is hard to parse
Processed: Bug#1015117 marked as pending in manila-ui
Processing control commands: > tag -1 pending Bug #1015117 [src:manila-ui] manila-ui: FTBFS: AttributeError: 'NoneType' object has no attribute 'action' Added tag(s) pending. -- 1015117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015117: marked as pending in manila-ui
Control: tag -1 pending Hello, Bug #1015117 in manila-ui reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/manila-ui/-/commit/da2bd30c29ab32dbb8e9da44986fb2359463ff65 * Add a few Django 4 patches (Closes: #1015117): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015117
Bug#1015125: marked as pending in trove-dashboard
Control: tag -1 pending Hello, Bug #1015125 in trove-dashboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/trove-dashboard/-/commit/f763ab5ffc45bdd1168a2173a26d698f433fee1b * Add patches for Django 4 support (Closes: #1015125): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015125
Processed: Bug#1015125 marked as pending in trove-dashboard
Processing control commands: > tag -1 pending Bug #1015125 [src:trove-dashboard] trove-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) Added tag(s) pending. -- 1015125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 919697 to arc,arcanist, forcibly merging 919697 930722, severity of 930722 is serious
Processing commands for cont...@bugs.debian.org: > reassign 919697 arc,arcanist Bug #919697 [arcanist] arcanist: file conflict with arc Bug reassigned from package 'arcanist' to 'arc,arcanist'. No longer marked as found in versions phabricator/0~git20160726-3. Ignoring request to alter fixed versions of bug #919697 to the same values previously set > forcemerge 919697 930722 Bug #919697 [arc,arcanist] arcanist: file conflict with arc Bug #930722 [arc,arcanist] arc, arcanist: Both ship arc binary Merged 919697 930722 > severity 930722 serious Bug #930722 [arc,arcanist] arc, arcanist: Both ship arc binary Bug #919697 [arc,arcanist] arcanist: file conflict with arc Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 919697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919697 930722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1003463 in 0~git20200925-1
Processing commands for cont...@bugs.debian.org: > found 1003463 0~git20200925-1 Bug #1003463 [arcanist] Functionally broken with current PHP Marked as found in versions phabricator/0~git20200925-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015137: marked as done (mistral-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__
Your message dated Thu, 28 Jul 2022 13:50:00 +
with message-id
and subject line Bug#1015137: fixed in mistral-dashboard 14.0.0-2
has caused the Debian Bug report #1015137,
regarding mistral-dashboard: FTBFS: ImportError: cannot import name
'ugettext_lazy' from 'django.utils.translation'
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
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.)
--
1015137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mistral-dashboard
Version: 14.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> NOSE_WITH_OPENSTACK=1 \
> NOSE_OPENSTACK_COLOR=1 \
> NOSE_OPENSTACK_RED=0.05 \
> NOSE_OPENSTACK_YELLOW=0.025 \
> NOSE_OPENSTACK_SHOW_ELAPSED=1 \
> DJANGO_SETTINGS_MODULE=mistraldashboard.test.settings \
> python3-coverage run \
> /<>/manage.py test mistraldashboard
> --settings=mistraldashboard.test.settings
> Found 7 test(s).
> Traceback (most recent call last):
> File "/<>/manage.py", line 23, in
> execute_from_command_line(sys.argv)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 440, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 24, in run_from_argv
> super().run_from_argv(argv)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 414, in run_from_argv
> self.execute(*args, **cmd_options)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 460, in execute
> output = self.handle(*args, **options)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py",
> line 68, in handle
> failures = test_runner.run_tests(test_labels)
> File "/usr/lib/python3/dist-packages/django/test/runner.py", line 1006, in
> run_tests
> self.run_checks(databases)
> File "/usr/lib/python3/dist-packages/django/test/runner.py", line 925, in
> run_checks
> call_command("check", verbosity=self.verbosity, databases=databases)
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 198, in call_command
> return command.execute(*args, **defaults)
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 460, in execute
> output = self.handle(*args, **options)
> File
> "/usr/lib/python3/dist-packages/django/core/management/commands/check.py",
> line 76, in handle
> self.check(
> File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
> 487, in check
> all_issues = checks.run_checks(
> File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line
> 88, in run_checks
> new_errors = check(app_configs=app_configs, databases=databases)
> File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 14,
> in check_url_config
> return check_resolver(resolver)
> File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 24,
> in check_resolver
> return check_method()
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 480,
> in check
> for pattern in self.url_patterns:
> File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 49,
> in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 696,
> in url_patterns
> patterns = getattr(self.urlconf_module, "urlpatterns",
> self.urlconf_module)
> File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 49,
> in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 689,
> in urlconf_module
> return import_module(self.urlconf_name)
> File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], packag
Processed: Re: Bug#1015062: node-shiny-server: FTBFS: ModuleNotFoundError: No module named 'six'
Processing control commands:
> tags -1 moreinfo
Bug #1015062 {Done: Yadd } [gyp] node-shiny-server: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015041 {Done: Yadd } [gyp] node-opencv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015051 {Done: Yadd } [gyp] node-re2: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015058 {Done: Yadd } [gyp] node-expat: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015061 {Done: Yadd } [gyp] node-websocket: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015101 {Done: Yadd } [gyp] node-sqlite3: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015113 {Done: Yadd } [gyp] node-modern-syslog: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015114 {Done: Yadd } [gyp] node-iconv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015119 {Done: Yadd } [gyp] node-nan: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015121 {Done: Yadd } [gyp] node-leveldown: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015130 {Done: Yadd } [gyp] node-node-sass: FTBFS:
ModuleNotFoundError: No module named 'six'
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
> tags -1 unreproducible
Bug #1015062 {Done: Yadd } [gyp] node-shiny-server: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015041 {Done: Yadd } [gyp] node-opencv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015051 {Done: Yadd } [gyp] node-re2: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015058 {Done: Yadd } [gyp] node-expat: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015061 {Done: Yadd } [gyp] node-websocket: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015101 {Done: Yadd } [gyp] node-sqlite3: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015113 {Done: Yadd } [gyp] node-modern-syslog: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015114 {Done: Yadd } [gyp] node-iconv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015119 {Done: Yadd } [gyp] node-nan: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015121 {Done: Yadd } [gyp] node-leveldown: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015130 {Done: Yadd } [gyp] node-node-sass: FTBFS:
ModuleNotFoundError: No module named 'six'
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
Added tag(s) unreproducible.
> severity -1 important
Bug #1015062 {Done: Yadd } [gyp] node-shiny-server: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015041 {Done: Yadd } [gyp] node-opencv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015051 {Done: Yadd } [gyp] node-re2: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015058 {Done: Yadd } [gyp] node-expat: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015061 {Done: Yadd } [gyp] node-websocket: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015101 {Done: Yadd } [gyp] node-sqlite3: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015113 {Done: Yadd } [gyp] node-modern-syslog: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015114 {Done: Yadd } [gyp] node-iconv: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015119 {Done: Yadd } [gyp] node-nan: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015121 {Done: Yadd } [gyp] node-leveldown: FTBFS:
ModuleNotFoundError: No module named 'six'
Bug #1015130 {Done: Yadd } [gyp] node-node-sass: FTBFS:
ModuleNotFoundError: No module named 'six'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
--
1015041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015041
1015051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015051
1015058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015058
1015061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015061
1015062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015062
1015101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015101
1015113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015113
1015114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015114
1015119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015119
10
Bug#1015062: node-shiny-server: FTBFS: ModuleNotFoundError: No module named 'six'
Control: tags -1 moreinfo
Control: tags -1 unreproducible
Control: severity -1 important
Hi Lucas,
I can't reproduce the issue at my side. It somehow smells like an
issue of some Build-Depends which might have been solved meanwhile.
Kind regards
Andreas.
Am Sat, Jul 16, 2022 at 03:31:35PM +0200 schrieb Lucas Nussbaum:
> Source: node-shiny-server
> Version: 1.5.17.973-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220716 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> > [ 50%] Building CXX object src/CMakeFiles/shiny-server.dir/launcher.cc.o
> > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -g -O2
> > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT
> > src/CMakeFiles/shiny-server.dir/launcher.cc.o -MF
> > CMakeFiles/shiny-server.dir/launcher.cc.o.d -o
> > CMakeFiles/shiny-server.dir/launcher.cc.o -c
> > /<>/src/launcher.cc
> > /<>/src/launcher.cc: In function ‘int main(int, char**)’:
> > /<>/src/launcher.cc:38:13: warning: ignoring return value of
> > ‘int daemon(int, int)’ declared with attribute ‘warn_unused_result’
> > [-Wunused-result]
> >38 | daemon(1, 0);
> > | ~~^~
> > [100%] Linking CXX executable ../../bin/shiny-server
> > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E
> > cmake_link_script CMakeFiles/shiny-server.dir/link.txt --verbose=1
> > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic
> > "CMakeFiles/shiny-server.dir/launcher.cc.o" -o ../../bin/shiny-server
> > make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> > [100%] Built target shiny-server
> > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> > /usr/bin/cmake -E cmake_progress_start
> > /<>/obj-x86_64-linux-gnu/CMakeFiles 0
> > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> > node-gyp rebuild
> > gyp info it worked if it ends with ok
> > gyp info using node-gyp@9.0.0
> > gyp info using node@16.15.1 | linux | x64
> > gyp info find Python using Python version 3.10.5 found at "/usr/bin/python3"
> > gyp info spawn /usr/bin/python3
> > gyp info spawn args [
> > gyp info spawn args '/usr/share/nodejs/node-gyp/gyp/gyp_main.py',
> > gyp info spawn args 'binding.gyp',
> > gyp info spawn args '-f',
> > gyp info spawn args 'make',
> > gyp info spawn args '-I',
> > gyp info spawn args '/<>/build/config.gypi',
> > gyp info spawn args '-I',
> > gyp info spawn args '/usr/share/nodejs/node-gyp/addon.gypi',
> > gyp info spawn args '-I',
> > gyp info spawn args '/usr/include/nodejs/common.gypi',
> > gyp info spawn args '-Dlibrary=shared_library',
> > gyp info spawn args '-Dvisibility=default',
> > gyp info spawn args '-Dnode_root_dir=/usr/include/nodejs',
> > gyp info spawn args '-Dnode_gyp_dir=/usr/share/nodejs/node-gyp',
> > gyp info spawn args
> > '-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',
> > gyp info spawn args '-Dmodule_root_dir=/<>',
> > gyp info spawn args '-Dnode_engine=v8',
> > gyp info spawn args '--depth=.',
> > gyp info spawn args '--no-parallel',
> > gyp info spawn args '--generator-output',
> > gyp info spawn args 'build',
> > gyp info spawn args '-Goutput_dir=.'
> > gyp info spawn args ]
> > Traceback (most recent call last):
> > File "/usr/share/nodejs/node-gyp/gyp/gyp_main.py", line 33, in
> > sys.exit(load_entry_point('gyp==0.1', 'console_scripts', 'gyp')())
> > File "/usr/share/nodejs/node-gyp/gyp/gyp_main.py", line 25, in
> > importlib_load_entry_point
> > return next(matches).load()
> > File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in
> > load
> > module = import_module(match.group('module'))
> > File "/usr/lib/python3.10/importlib/__init__.py", line 126, in
> > import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> > File "", line 1050, in _gcd_import
> > File "", line 1027, in _find_and_load
> > File "", line 1006, in
> > _find_and_load_unlocked
> > File "", line 688, in _load_unlocked
> > File "", line 883, in exec_module
> > File "", line 241, in
> > _call_with_frames_removed
> > File "/usr/lib/python3/dist-packages/gyp/__init__.py", line 10, in
> >
> > import gyp.input
> > File "/usr/lib/python3/dist-packages/gyp/input.py", line 8, in
> > import gyp.common
> > File "/usr/lib/python3/dist-packages/gyp/common.py", line 14, in
> > from six.moves import collections_abc
> > ModuleNotFoundError: No module named 'six'
> > gyp ERR! configure error
> > gyp ERR! stack Error: `gyp` failed with exit code: 1
> > gyp ERR! stack at ChildProcess.onCpExit
>
Processed (with 1 error): RM: gnome-shell-xrdesktop -- RoQA; unbuildable, uninstallable, unmaintained
Processing commands for cont...@bugs.debian.org: > reassign 1008471 ftp.debian.org Bug #1008471 [src:gnome-shell-xrdesktop] gnome-shell-xrdesktop: intent to remove from Debian Bug reassigned from package 'src:gnome-shell-xrdesktop' to 'ftp.debian.org'. No longer marked as found in versions gnome-shell-xrdesktop/3.36.1-2. Ignoring request to alter fixed versions of bug #1008471 to the same values previously set > severity 1008471 normal Bug #1008471 [ftp.debian.org] gnome-shell-xrdesktop: intent to remove from Debian Severity set to 'normal' from 'serious' > retitle 1008471 RM: gnome-shell-xrdesktop -- RoQA; unbuildable, Bug #1008471 [ftp.debian.org] gnome-shell-xrdesktop: intent to remove from Debian Changed Bug title to 'RM: gnome-shell-xrdesktop -- RoQA; unbuildable,' from 'gnome-shell-xrdesktop: intent to remove from Debian'. > uninstallable, unmaintained Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1008471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015137: marked as pending in mistral-dashboard
Control: tag -1 pending Hello, Bug #1015137 in mistral-dashboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/mistral-dashboard/-/commit/186cbd9104c8117e892cea14008ed5436170056e * Added Django 4 compat (Closes: #1015137): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015137
Processed: Bug#1015137 marked as pending in mistral-dashboard
Processing control commands: > tag -1 pending Bug #1015137 [src:mistral-dashboard] mistral-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) Added tag(s) pending. -- 1015137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015135: marked as done (zaqar-ui: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py))
Your message dated Thu, 28 Jul 2022 13:04:03 + with message-id and subject line Bug#1015135: fixed in zaqar-ui 12.0.0-2 has caused the Debian Bug report #1015135, regarding zaqar-ui: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) 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.) -- 1015135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zaqar-ui Version: 12.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > for i in 3.9 3.10 ; do \ > > PYTHONPATH=/<>/debian/python3-zaqar-ui/usr/lib/python3/dist-packages > \ > NOSE_WITH_OPENSTACK=1 \ > NOSE_OPENSTACK_COLOR=1 \ > NOSE_OPENSTACK_RED=0.05 \ > NOSE_OPENSTACK_YELLOW=0.025 \ > NOSE_OPENSTACK_SHOW_ELAPSED=1 \ > PYTHON=python$i \ > python$i /<>/manage.py test zaqar_ui > --settings=zaqar_ui.test.settings ; \ > done > WARNING:root:Error importing zaqar_ui.enabled._1510_project_messaging_group > ERROR:root:cannot import name 'ugettext_lazy' from 'django.utils.translation' > (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/openstack_dashboard/utils/settings.py", line > 58, in import_submodules > submodule = import_module(name) > File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "", line 1030, in _gcd_import > File "", line 1007, in _find_and_load > File "", line 986, in _find_and_load_unlocked > File "", line 680, in _load_unlocked > File "", line 850, in exec_module > File "", line 228, in _call_with_frames_removed > File "/<>/zaqar_ui/enabled/_1510_project_messaging_group.py", > line 15, in > from django.utils.translation import ugettext_lazy as _ > ImportError: cannot import name 'ugettext_lazy' from > 'django.utils.translation' > (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) > WARNING:root:Error importing zaqar_ui.enabled._2510_admin_messaging_group > ERROR:root:cannot import name 'ugettext_lazy' from 'django.utils.translation' > (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/openstack_dashboard/utils/settings.py", line > 58, in import_submodules > submodule = import_module(name) > File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "", line 1030, in _gcd_import > File "", line 1007, in _find_and_load > File "", line 986, in _find_and_load_unlocked > File "", line 680, in _load_unlocked > File "", line 850, in exec_module > File "", line 228, in _call_with_frames_removed > File "/<>/zaqar_ui/enabled/_2510_admin_messaging_group.py", > line 15, in > from django.utils.translation import ugettext_lazy as _ > ImportError: cannot import name 'ugettext_lazy' from > 'django.utils.translation' > (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) > Found 3 test(s). > System check identified no issues (0 silenced). > EEE > == > ERROR: zaqar_ui.api.rest (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: zaqar_ui.api.rest > Traceback (most recent call last): > File "/usr/lib/python3.9/unittest/loader.py", line 470, in _find_test_path > package = self._get_module_from_name(name) > File "/usr/lib/python3.9/unittest/loader.py", line 377, in > _get_module_from_name > __import__(name) > File "/<>/zaqar_ui/api/rest/__init__.py", line 24, in > from zaqar_ui.api.rest import zaqar # noqa: F401 > File "/<>/zaqar_ui/api/rest/zaqar.py", line 18, in > from django.utils.translation import ugettext_lazy as _ > ImportError: cannot import name 'ugettext_
Bug#1015861: bamtools: FTBFS with upcoming doxygen 1.9.4
Control: tags -1 pending This is fixed in Git. Unfortunately the new version is in NEW since 4 months and I do not want to fiddle around with this package. A fix will be uploaded with source-only upload once the package is finally accepted. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#1015861: bamtools: FTBFS with upcoming doxygen 1.9.4
Processing control commands: > tags -1 pending Bug #1015861 [bamtools] bamtools: FTBFS with upcoming doxygen 1.9.4 Added tag(s) pending. -- 1015861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015135: marked as pending in zaqar-ui
Control: tag -1 pending Hello, Bug #1015135 in zaqar-ui reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/horizon-plugins/zaqar-ui/-/commit/cab3d30553d387ff4dd859fc3070ba7901bb9f7d * Add Django 4 compat patches (Closes: #1015135): - django-4-ugettext_lazy-is-removed.patch - django-4-django.conf.urls.url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1015135
Processed: Bug#1015135 marked as pending in zaqar-ui
Processing control commands: > tag -1 pending Bug #1015135 [src:zaqar-ui] zaqar-ui: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py) Added tag(s) pending. -- 1015135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999134: marked as done (dns323-firmware-tools: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 28 Jul 2022 12:33:55 +
with message-id
and subject line Bug#999134: fixed in dns323-firmware-tools 0.7.3-1.2
has caused the Debian Bug report #999134,
regarding dns323-firmware-tools: missing required debian/rules targets
build-arch and/or build-indep
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.)
--
999134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dns323-firmware-tools
Version: 0.7.3-1.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.
Best,
Lucas
--- End Message ---
--- Begin Message ---
Source: dns323-firmware-tools
Source-Version: 0.7.3-1.2
Done: Håvard F. Aasen
We believe that the bug you reported is fixed in the latest version of
dns323-firmware-tools, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Håvard F. Aasen (supplier of updated
dns323-firmware-tools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 28 Jul 2022 09:12:19 +0200
Source: dns323-firmware-tools
Architecture: source
Version: 0.7.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: Matt Palmer
Changed-By: Håvard F. Aasen
Closes: 999134 1007083
Changes:
dns323-firmware-tools (0.7.3-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Include missing build target. Closes: #999134
- Using dh sequencer.
- Add runtime dependency on ${misc:Depends}.
* Switch to dpkg-source 3.0 (quilt) format. Closes: #1007083
Checksums-Sha1:
0dff17084272f2a1947900e991716c67d9ce6212 1844
dns323-firmware-tools_0.7.3-1.2.dsc
075b1b2571a0c74763f8b2d1364c9340fb9b75ee 2204
dns323-firmware-tools_0.7.3-1.2.debian.tar.xz
4979c5b5b580b738f2f0ab6b422a482a81ab7206 5803
dns323-firmware-tools_0.7.3-1.2_source.buildinfo
Checksums-Sha256:
4f923563339d1fdcfb46c0307f87f0b19e2d92465cb76a66d4a15482db557b40 1844
dns323-firmware-tools_0.7.3-1.2.dsc
5c09ce4618850800771ddd4385f2224c95f0b24bf695171788a18fdcc047363a 2204
dns323-firmware-tools_0.7.3-1.2.debian.tar.xz
8aef01fc4f2fabd022a5f72e0d0442aa82fac7c8b5369f2fdc7c68777a44fc83 5803
dns323-firmware-tools_0.7.3-1.2_source.buildinfo
Files:
0764dfb269cbb4e4cb807add7f69ece0 1844 otherosfs optional
dns323-firmware-tools_0.7.3-1.2.dsc
bd115a640ae7a4a8337b47d2ea83f730 2204 otherosfs optional
dns323-firmware-tools_0.7.3-1.2.debian.tar.xz
806ef0bb48eefa0695ed89100f6c8239 5803 otherosfs optional
dns323-firmware-tools_0.7.3-1.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmLifMUACgkQweDZLphv
fH743g/7Bp0rcpm7ho3TZdfUjcqa4HgQdP1Eg9NSzl9UI3fXCsoz2eaocfD4Tbbs
5bgcTHqbM12nv98K4psP0bDFEz/kmkMLqNsILuaWvUzM/Yhkqo18FuY4DQ7CQuyw
uylXYkmR3+lz9XnrW2UQ+fU2JhSW5t0/p3EZsCLpj/ALSYJUKJkHXha5vscqvGTd
8nsnVJtLUrO3jXMF/Bwi1fklZxp1kIib9RBO4+fHgSfY0ZSjzM/nqNwVc+ZRcwmG
HBT2hfePMQMv88QsBpqViA5ksAUozVzWODEbGnGhJ7wcefjbvH4QHwArTEmqnutl
dArw5Lf+srXqlJeh5ZhpBudHZhuWvtIEsbqrcj///KjMdG4H1UWpjVTR7GVtYDQo
bBlMDzh+PBNV5rQ1l5rruoJ7gnMov8nuZdtCGoXB+pk/BCkP9cSKA/X8b+xt5J5Y
dDOwHn8xDuIqW7x5hQ14QgTfre/5QRArKafY/ZMQq+OR0H4Ljj3YiyqmMj1N0UhB
oeoxGZ5EenefN+5BQ+Lbj+wf8j2mUoZ4x4H70WkVgOigumWhKHz8HL0KSQYrIJZd
0yBtmEtx7V/2ZZBhXvkdNwP7zdk4cUWyKSor9Frw0gmbf+QUYc6gHpttbfQ38UH6
PfozwZ3zeZQqgcH4gn4OnyUtnH3ulYSTbu784Ib57wiWhyeVA9o=
=zEc7
-END PGP SIGNATURE End Message ---
Processed: bug 979095 is forwarded to https://github.com/opensvc/multipath-tools/issues/36
Processing commands for cont...@bugs.debian.org: > forwarded 979095 https://github.com/opensvc/multipath-tools/issues/36 Bug #979095 [multipath-tools] Legally problematic GPL-3+ readline dependency Set Bug forwarded-to-address to 'https://github.com/opensvc/multipath-tools/issues/36'. > thanks Stopping processing here. Please contact me if you need assistance. -- 979095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016139: (net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805)
I said: > I had uploaded net-snmp 5.9.3 anyway but I'll add those CVEs to the > changelog. > I'm trying to find where they've made the changes to see if it is possible > to get at least bullseye fixed. > I've had a look and believe these two commits are the fixes: snmpd: fix bounds checking in NET-SNMP-AGENT-MIB, NET-SNMP-VACM-MIB, SNMP-VIEW-BASED-ACM-MIB, SNMP-USER-BASED-SM-MIB https://github.com/net-snmp/net-snmp/commit/67ebb43e9038b2dae6e74ae8838b36fcc10fc937 snmpd: recover SET status from delegated request https://github.com/net-snmp/net-snmp/commit/9a0cd7c00947d5e1c6ceb54558d454f87c3b8341 Both sets of commits look pretty clear and simple to implement. I've asked upstream to confirm these are the only two patches. - Craig
Bug#1011393: marked as done (openpace: frequent parallel FTBFS)
Your message dated Thu, 28 Jul 2022 11:33:53 + with message-id and subject line Bug#1011393: fixed in openpace 1.1.2+ds+git20220117+453c3d6b03a0-1.1 has caused the Debian Bug report #1011393, regarding openpace: frequent parallel FTBFS 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.) -- 1011393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openpace Version: 1.1.2+ds+git20220117+453c3d6b03a0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=openpace&arch=arm64&ver=1.1.2%2Bds%2Bgit20220117%2B453c3d6b03a0-1&stamp=1652780709&raw=0 libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto make[6]: Leaving directory '/<>/src' /usr/bin/help2man \ --output=cvc-print.1 \ --no-info \ --source='OpenPACE 1.1.2' \ ./cvc-print /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o libeac.la libvc.la -lcrypto help2man: can't get `--help' info from ./cvc-print Try `--no-discard-stderr' if option outputs to stderr make[5]: *** [Makefile:1532: cvc-print.1] Error 127 make[5]: *** Waiting for unfinished jobs libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/eactest eactest-eactest.o eactest-ssl_compat.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cvc-create cvc_create-cvc-create.o cvc_create-read_file.o cvc_create-cvc-create-cmdline.o libeac.la libvc.la -lcrypto libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-create cvc_create-cvc-create.o cvc_create-read_file.o cvc_create-cvc-create-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto make[6]: Leaving directory '/<>/src' /usr/bin/help2man \ --output=cvc-create.1 \ --no-info \ --source='OpenPACE 1.1.2' \ ./cvc-create make[5]: Leaving directory '/<>/src' make[4]: *** [Makefile:1149: all-recursive] Error 1 make[4]: Leaving directory '/<>/src' make[3]: *** [Makefile:566: all] Error 2 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:522: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:433: all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j4 returned exit code 2 make: *** [debian/rules:11: binary-arch] Error 25 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: openpace Source-Version: 1.1.2+ds+git20220117+453c3d6b03a0-1.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of openpace, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated openpace 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
Bug#999310: Bug#1016152: RFS: libxml-dumper-perl/0.81-1.4 [NMU] [RC] -- Perl module for dumping Perl objects from/to XML
Control: tag 999310 + pending
On Thu, 28 Jul 2022 08:25:47 +0200, Håvard F. Aasen wrote:
> libxml-dumper-perl (0.81-1.4) unstable; urgency=medium
> .
>* Non-maintainer upload.
>* Include missing build target. (Closes: #999310)
> - Using dh sequencer.
> - Add libxml-parser-perl as build dependency, for testsuite.
> - Add runtime dependency on ${misc:Depends}.
>* d/watch
> - Bump to version 4.
> - Update URI.
>* Remove superfluous dot '.' in package description
>* d/copyright: Change to UTF-8 encoding.
Uploaded to DELAYED/5, thanks for fixing this RC bug.
(For future reference: You changed a bit more than what is necessary
to fix th ebug, which is a bit unusual for NMUs. But is the changes
are all sane, I just went ahead with the upload.)
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
signature.asc
Description: Digital Signature
Processed: Re: Bug#1016152: RFS: libxml-dumper-perl/0.81-1.4 [NMU] [RC] -- Perl module for dumping Perl objects from/to XML
Processing control commands: > tag 999310 + pending Bug #999310 [src:libxml-dumper-perl] libxml-dumper-perl: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #999310 to the same tags previously set -- 999310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011393: openpace: FTBFS on arm64, armel and mips64el
control: tags -1 patch pending Uploaded. G. On Sun, 22 May 2022 15:32:34 +0300 Adrian Bunk wrote: Control: retitle -1 openpace: frequent parallel FTBFS Control: forwarded -1 https://github.com/frankmorgner/openpace/pull/56 Control: tags -1 patch On Sat, May 21, 2022 at 07:22:29PM +0200, Sebastian Ramacher wrote: > Source: openpace > Version: 1.1.2+ds+git20220117+453c3d6b03a0-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > > https://buildd.debian.org/status/fetch.php?pkg=openpace&arch=arm64&ver=1.1.2%2Bds%2Bgit20220117%2B453c3d6b03a0-1&stamp=1652780709&raw=0 > > > libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o ./.libs/libeac.so ./.libs/libvc.a -lcrypto > make[6]: Leaving directory '/<>/src' > /usr/bin/help2man \ >--output=cvc-print.1 \ >--no-info \ >--source='OpenPACE 1.1.2' \ >./cvc-print > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cvc-print cvc_print-cvc-print.o cvc_print-read_file.o cvc_print-cvc-print-cmdline.o libeac.la libvc.la -lcrypto > help2man: can't get `--help' info from ./cvc-print > Try `--no-discard-stderr' if option outputs to stderr > make[5]: *** [Makefile:1532: cvc-print.1] Error 127 > make[5]: *** Waiting for unfinished jobs >... This is not architecture specific, it is a parallel build failure. Fix linked above. > Cheers cu Adrian diff -Nru openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/changelog openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/changelog --- openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/changelog 2022-05-17 11:17:33.0 +0200 +++ openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/changelog 2022-07-28 13:17:25.0 +0200 @@ -1,3 +1,12 @@ +openpace (1.1.2+ds+git20220117+453c3d6b03a0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch: +- Add upstream patch from Adrian Bunk to fix a race condition in parallel + builds (Closes: #1011393). + + -- Gianfranco Costamagna Thu, 28 Jul 2022 13:17:25 +0200 + openpace (1.1.2+ds+git20220117+453c3d6b03a0-1) unstable; urgency=medium * New upstream snapshot (Closes: #1006513). diff -Nru openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch --- openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch 1970-01-01 01:00:00.0 +0100 +++ openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch 2022-07-28 13:17:25.0 +0200 @@ -0,0 +1,39 @@ +From 7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314 Mon Sep 17 00:00:00 2001 +From: Adrian Bunk +Date: Sun, 22 May 2022 15:15:29 +0300 +Subject: [PATCH] src/Makefile.am: Fix race condition in parallel builds + +Calling "make" from a Makefile results in several make invocations +in parallel that do not know about each other and might generate +the same files in parallel: +https://buildd.debian.org/status/logs.php?pkg=openpace&ver=1.1.2%2Bds%2Bgit20220117%2B453c3d6b03a0-1 + +Just tell make about the correct dependencies and everything works +automatically. +--- + src/Makefile.am | 6 ++ + 1 file changed, 2 insertions(+), 4 deletions(-) + +diff --git a/src/Makefile.am b/src/Makefile.am +index 22338ba..1f17372 100644 +--- a/src/Makefile.am b/src/Makefile.am +@@ -97,16 +97,14 @@ ENV = env \ + + endif + +-cvc-create.1: cvc-create.ggo.in +- make -C $(builddir) cvc-create$(EXEEXT) ++cvc-create.1: cvc-create$(EXEEXT) + $(ENV) $(HELP2MAN) \ + --output=$@ \ + --no-info \ + --source='$(PACKAGE_STRING)' \ + $(builddir)/cvc-create$(EXEEXT) + +-cvc-print.1: cvc-print.ggo.in +- make -C $(builddir) cvc-print$(EXEEXT) ++cvc-print.1: cvc-print$(EXEEXT) + $(ENV) $(HELP2MAN) \ + --output=$@ \ + --no-info \ diff -Nru openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/series openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/series --- openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ openpace-1.1.2+ds+git20220117+453c3d6b03a0/debian/patches/series 2022-07-28 13:15:15.0 +0200 @@ -0,0 +1 @@ +7de0b27a3d5dfb3ffeb82c37ce7ba4e85f764314.patch
Processed: Re: Bug#1011393: openpace: FTBFS on arm64, armel and mips64el
Processing control commands: > tags -1 patch pending Bug #1011393 [src:openpace] openpace: frequent parallel FTBFS Added tag(s) pending. -- 1011393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938492: marked as pending in six
Control: tag -1 pending Hello, Bug #938492 in six reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/six/-/commit/b9af11b202f99460f5146b349ad2699df5441caf Remove Python 2 support (Closes: #938492). (this message was generated automatically) -- Greetings https://bugs.debian.org/938492
Processed: Bug#938492 marked as pending in six
Processing control commands: > tag -1 pending Bug #938492 [src:six] six: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938492 to the same tags previously set -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016139: marked as done (net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805)
Your message dated Thu, 28 Jul 2022 20:58:24 +1000 with message-id and subject line Fixed in net-snmp 5.9.3+dfsg-1 has caused the Debian Bug report #1016139, regarding net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805 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.) -- 1016139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: net-snmp X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for net-snmp. 5.9.3 fixes the following issues: - These two CVEs can be exploited by a user with read-only credentials: - CVE-2022-24805 A buffer overflow in the handling of the INDEX of NET-SNMP-VACM-MIB can cause an out-of-bounds memory access. - CVE-2022-24809 A malformed OID in a GET-NEXT to the nsVacmAccessTable can cause a NULL pointer dereference. - These CVEs can be exploited by a user with read-write credentials: - CVE-2022-24806 Improper Input Validation when SETing malformed OIDs in master agent and subagent simultaneously - CVE-2022-24807 A malformed OID in a SET request to SNMP-VIEW-BASED-ACM-MIB::vacmAccessTable can cause an out-of-bounds memory access. - CVE-2022-24808 A malformed OID in a SET request to NET-SNMP-AGENT-MIB::nsLogTable can cause a NULL pointer dereference - CVE-2022-24810 A malformed OID in a SET to the nsVacmAccessTable can cause a NULL pointer dereference. - To avoid these flaws, use strong SNMPv3 credentials and do not share them. If you must use SNMPv1 or SNMPv2c, use a complex community string and enhance the protection by restricting access to a given IP address range. - Thanks are due to Yu Zhang of VARAS@IIE and Nanyu Zhong of VARAS@IIE for reporting the following CVEs that have been fixed in this release, and to Arista Networks for providing fixes. Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: net-snmp Version: 5.9.3+dfsg-1 I had uploaded net-snmp 5.9.3 anyway but I'll add those CVEs to the changelog. I'm trying to find where they've made the changes to see if it is possible to get at least bullseye fixed. --- End Message ---
Processed: unarchive for bullseye
Processing commands for cont...@bugs.debian.org:
> unarchive 997222
Bug #997222 {Done: Håvard Flaget Aasen }
[src:libexplain] libexplain: FTBFS: libexplain/iocontrol/siocadddlci.c:51:12:
error: invalid application of ‘sizeof’ to incomplete type ‘struct dlci_add’
Unarchived Bug 997222
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014503: bind9-libs: please provide libraries that enable reverse dependencies to use them
Hi, On 28-07-2022 12:27, Bernhard Turmann wrote: you mentioned bug 1004729 which is marked as done. That might be indeed the case for unstable/testing. Unfortunately, this is not the case for the version bind-dyndb-ldap/11.6-3 in bullseye stable after several newer bind9 releases merged into stable with 9.16.27 being the latest. Means, currently, bind-dyndb-ldap is broken in stable. What is the correct way to get this resolved and maintain it like that? bind-dyndb-ldap needs to be binNMUed in stable too. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#965498: marked as done (dsdp: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 28 Jul 2022 10:34:00 + with message-id and subject line Bug#965498: fixed in dsdp 5.8-10 has caused the Debian Bug report #965498, regarding dsdp: 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.) -- 965498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dsdp Version: 5.8-9.4 Severity: normal Usertags: compat-5-6-removal Hi, The package dsdp 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 --- Source: dsdp Source-Version: 5.8-10 Done: Håvard F. Aasen We believe that the bug you reported is fixed in the latest version of dsdp, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard F. Aasen (supplier of updated dsdp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Jul 2022 11:20:16 +0200 Source: dsdp Architecture: source Version: 5.8-10 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard F. Aasen Closes: 939548 965498 Changes: dsdp (5.8-10) unstable; urgency=medium . * QA upload. * Mark package as orphaned, see #881843. * d/control: - Bump debhelper to 7. Closes: #965498 - Change section, extra -> optional. - Change Vcs-* fields, point to salsa. - Add Multi-Arch: foreign, to dsdp-doc package. * Make package build reproducible, don't install log files in *-doc package. Thanks to Chris Lamb. Closes: #939548 * d/rules: - Make sure directory 'lib' actually exist before use. * Add d/gbp.conf, specify branch layout. Checksums-Sha1: ce1b1a6dbfbaf562c6cd2de0f46511b2a932d1c3 1851 dsdp_5.8-10.dsc 1fb49fd0e9682aec87bbf870d0d36824523c9e62 7312 dsdp_5.8-10.debian.tar.xz 4f8fee7f758ef6fd8447ff635e68b53f3d8e9363 5750 dsdp_5.8-10_source.buildinfo Checksums-Sha256: 46040a9876fd3ce0c6ab5ca7e890ec45f18d19f69c45850e20bfbe25d13368fa 1851 dsdp_5.8-10.dsc e12e9e7226bde23e85d6e563e2b3c4d53797196bbefdb50cf81a771c6dd058c3 7312 dsdp_5.8-10.debian.tar.xz 553658ac4ab07ee07d2b8c0c8112bbc4b38b09871cbbd6948a777d770c98ff35 5750 dsdp_5.8-10_source.buildinfo Files: bc15103dfd7b9084f483c23ddf1c763e 1851 science optional dsdp_5.8-10.dsc e797e133e0d01d2eafc2603a2f690c7c 7312 science optional dsdp_5.8-10.debian.tar.xz 3220047787a040e9f11e6dea5532a85e 5750 science optional dsdp_5.8-10_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmLiYf0QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFOvVC/90K7DQGebzwmLtd1t20rhjsh67w5oapk1l juwzWl3ELGfrpDQWuuQNavFCMb3G9asjWtY52aYCXKfUYzzDn62vqmn2cl86KsaK JVB80FO10mb25tIiiuAv1obsEUCoFL49Uh3EIj+77rcfkMeqtzooLZshsuWnj4xr wPlD3RqHqlV3BxRRmPQu0sKUhXyJYps6gwSQuRxWEIpdBCWc/WiarsDZIpYwzyuK RWQs17I4lpcA40cJMODx8cUkYhkX4gb/0FoE/mKnL++z5l25Dyzm448XYyzfXHC7 lpsYDySYR9WZOK8YjjGdz6UK8AaWcDIFYclrxZ+p0HLAvxvovYtixkYrw88OHV2A L2w/NDQSWCuegK+w8Qsf5tQaTQ2t58HX2KXSn+Np3ICDjCmFjbEQ5ThrdqEJevlM jd0WjSczK2PEPrrq+bD8iqLuCwyKQBF4DwBs8i7cLvm+tMG6RCBbX
Bug#1014503: bind9-libs: please provide libraries that enable reverse dependencies to use them
Paul, Ondřej, you mentioned bug 1004729 which is marked as done. That might be indeed the case for unstable/testing. Unfortunately, this is not the case for the version bind-dyndb-ldap/11.6-3 in bullseye stable after several newer bind9 releases merged into stable with 9.16.27 being the latest. Means, currently, bind-dyndb-ldap is broken in stable. What is the correct way to get this resolved and maintain it like that? For now, I use apt mark of older bind9 9.16.15 as an emergency workaround until a solution is found. Thanks Berni
Processed: Re: xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures
Processing control commands: > tag -1 ftbfs Bug #1016156 [src:xtl] xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures Added tag(s) ftbfs. -- 1016156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016156: xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures
Control: tag -1 ftbfs [CC-ing the i386 porter so they are aware.] Hi, On Thu, 28 Jul 2022 10:02:52 +0200 Paul Gevers wrote: With a recent upload of gcc-defaults the autopkgtest of xtl fails in testing on i386 when that autopkgtest is run with the binary packages of gcc-defaults from unstable. It passes when run with only packages from testing. In tabular form: This can now also be seen as a fails-to-build-from-source issue: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/xtl.html Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#938492: marked as pending in six
Control: tag -1 pending Hello, Bug #938492 in six reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/six/-/commit/8589558d6f78979e9b4137499d5e62c2b7b16019 Remove Python 2 support (Closes: #938492). (this message was generated automatically) -- Greetings https://bugs.debian.org/938492
Processed: Bug#938492 marked as pending in six
Processing control commands: > tag -1 pending Bug #938492 [src:six] six: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938492 to the same tags previously set -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#938492 marked as pending in six
Processing control commands: > tag -1 pending Bug #938492 [src:six] six: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938492 to the same tags previously set -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938492: marked as pending in six
Control: tag -1 pending Hello, Bug #938492 in six reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/six/-/commit/238bf6fa278df4d4d54e236e8b58e14e1e0ce57d Remove Python 2 support (Closes: #938492). (this message was generated automatically) -- Greetings https://bugs.debian.org/938492
Processed: Bug#938492 marked as pending in six
Processing control commands: > tag -1 pending Bug #938492 [src:six] six: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938492 to the same tags previously set -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938492: marked as pending in six
Control: tag -1 pending Hello, Bug #938492 in six reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/six/-/commit/11ee8e2045775d2406518696a9bdee3c41eaa71a Remove Python 2 support (Closes: #938492). (this message was generated automatically) -- Greetings https://bugs.debian.org/938492
Bug#938492: marked as pending in six
Control: tag -1 pending Hello, Bug #938492 in six reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/six/-/commit/a3bba1513b3c06a6fc256287e829d5ab1a04df52 Remove Python 2 support (Closes: #938492). (this message was generated automatically) -- Greetings https://bugs.debian.org/938492
Processed: Bug#938492 marked as pending in six
Processing control commands: > tag -1 pending Bug #938492 [src:six] six: Python2 removal in sid/bullseye Added tag(s) pending. -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994193: marked as done (iptstate FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Thu, 28 Jul 2022 09:49:37 + with message-id and subject line Bug#994193: fixed in iptstate 2.2.7-0.1 has caused the Debian Bug report #994193, regarding iptstate FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 994193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: iptstate Version: 2.2.6-1 Severity: serious Tags: ftbfs iptstate fails to build from source in unstable. A build ends as follows: | g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security iptstate.cc -o iptstate -lncurses -lnetfilter_conntrack | iptstate.cc: In function ‘void get_input(WINDOW*, std::string&, const string&, const flags_t&)’: | iptstate.cc:685:30: error: format not a string literal and no format arguments [-Werror=format-security] | 685 | wprintw(cmd, prompt.c_str()); | | ^ | iptstate.cc: In function ‘void c_warn(WINDOW*, const string&, const flags_t&)’: | iptstate.cc:750:32: error: format not a string literal and no format arguments [-Werror=format-security] | 750 | wprintw(warn, warning.c_str()); | |^ | iptstate.cc: In function ‘int conntrack_hook(nf_conntrack_msg_type, nf_conntrack*, void*)’: | iptstate.cc:1002:30: warning: ‘:’ directive output may be truncated writing 1 byte into a region of size between 0 and 5 [-Wformat-truncation=] | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); | | ^ | iptstate.cc:1002:21: note: directive argument in the range [-59, 59] | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); | | ^~~ | iptstate.cc:1002:11: note: ‘snprintf’ output between 10 and 16 bytes into a destination of size 11 | 1002 | snprintf(ttlc,11, "%3i:%02i:%02i", hours, minutes, seconds); | | ^~~ | cc1plus: some warnings being treated as errors | make[1]: *** [Makefile:34: iptstate] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: error: make -j1 returned exit code 2 | make: *** [debian/rules:4: build] Error 25 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: iptstate Source-Version: 2.2.7-0.1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of iptstate, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated iptstate 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: Thu, 28 Jul 2022 09:32:06 + Source: iptstate Architecture: source Version: 2.2.7-0.1 Distribution: unstable Urgency: medium Maintainer: Chris Taylor Changed-By: Chris Hofstaedtler Closes: 994193 Changes: iptstate (2.2.7-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #994193). Checksums-Sha1: 1c2ad43cbecb448126a19bf5e41bea19e7e975c3 1770 iptstate_2.2.7-0.1.dsc e79a016b533829292e25e0595587d397faf6f12f 29994 iptstate_2.2.7.orig.tar.bz2 b4201943226b9c1d0692b1d9d3672933b066ed94 4180 iptstate_2.2.7-0.1.debian.tar.xz 98f227853c9e9fa933bf570a37af3bf94809791f 6502 iptstate_2.2.7-0.1_source.buildinfo Checksums-Sha256: ca4a5ccae98a21a027bcc6995ae5837d89b0fba085a00608d69c056ddfa24fea 1770 iptstate_2.2.7-0.1.dsc 896df0602885456a2631f795d634fc21311e505f8c910348e6312860f2097955 29994 iptstate_2.2.7.orig.tar.bz2 7d87b8cb0ea2513417a53fc73e7151c04c63a94ab7cf45dc293446faa5389fd1 4180 iptstate_2.2.7-0.1.debian.tar.xz ad8dda23da10ef8286f20375436cb3db8c20614d692a4754d40ab40c7049ba08 6502 iptstate_2.2.7-0.1_source.buildinfo Files: 64ff028e12bc864281ab5e7d75e97fc3 1770 admin optional iptstate_2.2.7-0.1.dsc 43da9202e0d42ea033eb14cff830c743 29994 admin optional iptstate_2.2.7.orig.tar.bz2 2bdc
Processed: tagging 994193
Processing commands for cont...@bugs.debian.org: > tags 994193 + upstream fixed-upstream Bug #994193 [src:iptstate] iptstate FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 994193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003165: Is march=native used for anything but probing the compiler?
Hi, > I admit I'm not sure at what point / what tool might inject this > string and I'm also not sure whether the option -march=native is > really used in the amd64 case. From my (very limited!) understanding, this is just setuptools(?) trying out various compiler options. The actual C compiler invocations look more à la: x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.10/sklearn/ensemble/_hist_gradient_boosting/_bitset.o -Lbuild/temp.linux-x86_64-3.10 -o /<>/.pybuild/cpython3_3.10/build/sklearn/ensemble/_hist_gradient_boosting/_bitset.cpython-310-x86_64-linux-gnu.so -fopenmp Moreover, the build finishes with: ### EXT COMPILER OPTIMIZATION ### Platform : Architecture: x64 Compiler: gcc CPU baseline : Requested : 'min' Enabled : SSE SSE2 SSE3 Flags : -msse -msse2 -msse3 Extra checks: none CPU dispatch : Requested : 'max -xop -fma4' Enabled : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL Generated : none CCompilerOpt.cache_flush[809] : write cache to path -> /<>/build/temp.linux-x86_64-3.10/ccompiler_opt_cache_ext.py ### CLIB COMPILER OPTIMIZATION ### Platform : Architecture: x64 Compiler: gcc CPU baseline : Requested : 'min' Enabled : SSE SSE2 SSE3 Flags : -msse -msse2 -msse3 Extra checks: none CPU dispatch : Requested : 'max -xop -fma4' Enabled : SSSE3 SSE41 POPCNT SSE42 AVX F16C FMA3 AVX2 AVX512F AVX512CD AVX512_KNL AVX512_KNM AVX512_SKX AVX512_CLX AVX512_CNL AVX512_ICL Generated : none ... and similarly on armel. I don't know the internal magic of these tools at all, but it seems superficially plausible that the march=native invocations are just instances of the compiler being probed. -- Gard signature.asc Description: PGP signature
Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35
> Maybe now is the time?Indeed my plan is to tackle this issue in about four > weeks. - Fabian Von meinem/meiner Galaxy gesendet Ursprüngliche Nachricht Von: Chris Hofstaedtler Datum: 28.07.22 01:02 (GMT+01:00) An: Fabian Greffrath , 977...@bugs.debian.org Cc: Jonas Smedegaard , Paul Gevers Betreff: Re: Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35 * Fabian Greffrath [220727 23:01]:[..]> My stance on this: In theory it should be technically possible to replace> the gsfonts (and gsfonts-x11) package with fonts-urw-base35 and I believe> this would be the right step, given that the latter font set is actively> maintained and extended - and actually used by ghostscript both upstream and> in Debian. And as a matter of fact, I have prepared this transition since I> uploaded the fonts-urw-base35 package for the first time. So, why haven't I> triggered this transition yet?[..]> So, to summarize: Yes, I think we should replace gsfonts+gsfonts-x11 with> fonts-urw-base35 at a given time and this transition is already prepared for> the most part. But I don't see this as a pressing issue right now, given the> lack of real-world issues this apparently causes, given the lack of bug> reports we received during the past 5 years - and given how late in the> release cycle we are to introduce a potentially disruptive change like this.Maybe now is the time?Chris
Bug#1003165: scikit-learn testing migration
Hi Graham, Am Thu, Jul 28, 2022 at 09:15:06AM +0200 schrieb Graham Inggs: > Hi > > On Wed, 27 Jul 2022 at 17:57, M. Zhou wrote: > > The previous segfault on armel becomes Bus Error on armel and armhf. > > I can build it on Power9, but it seems that the test fails on power8 (our > > buildd). > > In #1003165, one of the arm porters wrote they are happy to look at > the bus errors, but the baseline issue should be fixed first. ... this was five months ago and silence since then. We've lost lots of packages in testing and I see no progress here. It seems upstream is not actually keen on working on this as well. Meanwhile they stepped forward with new releases and I simply refreshed the issues for the new version (which are the same and not solved). Currently we have bus errors on arm 32 bit architectures and a baseline violation on power. If there is no solution at the horizon I'd vote for excluding these three architectures instead of sit and wait (which is all I can personally do in this topic). > > I have skimmed over the build logs and one of the main issues is the use of > > -march flags to enforce a certain baseline [1]: > > > > powerpc64le-linux-gnu-gcc: error: unrecognized command-line option > > ‘-march=native’; did you mean ‘-mcpu=native’? > > This may be the cause of the test failures on power8. Could someone give this a try? I know I could use a porter box to do so but my time is to limited to do it in a sensible time frame. Kind regards Andreas. -- http://fam-tille.de
Processed: affects mesa
Processing commands for cont...@bugs.debian.org: > affects 1015039 src:mesa Bug #1015039 [src:mesa] gtk4 memorytexture test-case regresses with Mesa 22.1 Added indication that 1015039 affects src:mesa > thanks Stopping processing here. Please contact me if you need assistance. -- 1015039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012923: marked as done (fenics-dolfinx: ftbfs with GCC-12)
Your message dated Thu, 28 Jul 2022 10:06:17 +0200 with message-id and subject line Re: fenics-dolfinx: ftbfs with GCC-12 has caused the Debian Bug report #1012923, regarding fenics-dolfinx: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fenics-dolfinx Version: 1:0.3.0-15 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/fenics-dolfinx_0.3.0-15_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] [ 32%] Building CXX object dolfinx/CMakeFiles/dolfinx.dir/fem/dofmapbuilder.cpp.o cd /<>/obj-x86_64-linux-gnu-real/dolfinx && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_CHRONO_DYN_LINK -DBOOST_TIMER_DYN_LINK -DDOLFINX_VERSION=\"0.3.0\" -DHAS_SLEPC -DXTENSOR_USE_XSIMD -Ddolfinx_EXPORTS -I/<>/cpp -I/<>/cpp/dolfinx -isystem /usr/lib/python3/dist-packages/ffcx/codegeneration -isystem /usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/lib/petscdir/petsc3.16/x86_64-linux-gnu-real/include -isystem /usr/include/hdf5/openmpi -isystem /usr/lib/slepcdir/slepc3.16/x86_64-linux-gnu-real/include -fpermissive -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -DNDEBUG -fPIC -pthread -std=c++17 -MD -MT dolfinx/CMakeFiles/dolfinx.dir/fem/dofmapbuilder.cpp.o -MF CMakeFiles/dolfinx.dir/fem/dofmapbuilder.cpp.o.d -o CMakeFiles/dolfinx.dir/fem/dofmapbuilder.cpp.o -c /<>/cpp/dolfinx/fem/dof mapbuilder.cpp [ 34%] Building CXX object dolfinx/CMakeFiles/dolfinx.dir/fem/interpolate.cpp.o cd /<>/obj-x86_64-linux-gnu-real/dolfinx && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_CHRONO_DYN_LINK -DBOOST_TIMER_DYN_LINK -DDOLFINX_VERSION=\"0.3.0\" -DHAS_SLEPC -DXTENSOR_USE_XSIMD -Ddolfinx_EXPORTS -I/<>/cpp -I/<>/cpp/dolfinx -isystem /usr/lib/python3/dist-packages/ffcx/codegeneration -isystem /usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/lib/petscdir/petsc3.16/x86_64-linux-gnu-real/include -isystem /usr/include/hdf5/openmpi -isystem /usr/lib/slepcdir/slepc3.16/x86_64-linux-gnu-real/include -fpermissive -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -DNDEBUG -fPIC -pthread -std=c++17 -MD -MT dolfinx/CMakeFiles/dolfinx.dir/fem/interpolate.cpp.o -MF CMakeFiles/dolfinx.dir/fem/interpolate.cpp.o.d -o CMakeFiles/dolfinx.dir/fem/interpolate.cpp.o -c /<>/cpp/dolfinx/fem/interpola te.cpp [ 35%] Building CXX object dolfinx/CMakeFiles/dolfinx.dir/fem/petsc.cpp.o cd /<>/obj-x86_64-linux-gnu-real/dolfinx && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_CHRONO_DYN_LINK -DBOOST_TIMER_DYN_LINK -DDOLFINX_VERSION=\"0.3.0\" -DHAS_SLEPC -DXTENSOR_USE_XSIMD -Ddolfinx_EXPORTS -I/<>/cpp -I/<>/cpp/dolfinx -isystem /usr/lib/python3/dist-packages/ffcx/codegeneration -isystem /usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/lib/petscdir/petsc3.16/x86_64-linux-g
Bug#1016156: xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures
Source: xtl Version: 0.7.2-2 Severity: serious X-Debbugs-CC: gcc-defau...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gcc-defaults Dear maintainer(s), With a recent upload of gcc-defaults the autopkgtest of xtl fails in testing on i386 when that autopkgtest is run with the binary packages of gcc-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail gcc-defaults from testing1.200 xtlfrom testing0.7.2-2 all others from testingfrom testing I copied some of the output at the bottom of this report. (Maybe you want to enable --output-on-failure such that info is available in the log). Currently this regression is blocking the migration of gcc-defaults to testing [1]. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gcc-defaults https://ci.debian.net/data/autopkgtest/testing/i386/x/xtl/24112985/log.gz Running tests... Test project /tmp/autopkgtest-lxc.yj53u3hj/downtmp/build.sSz/src/test Start 1: test_xbase64 1/23 Test #1: test_xbase64 . Passed0.00 sec Start 2: test_xbasic_fixed_string 2/23 Test #2: test_xbasic_fixed_string . Passed0.00 sec Start 3: test_xcomplex 3/23 Test #3: test_xcomplex Passed0.00 sec Start 4: test_xcomplex_sequence 4/23 Test #4: test_xcomplex_sequence ... Passed0.00 sec Start 5: test_xclosure 5/23 Test #5: test_xclosure Passed0.00 sec Start 6: test_xdynamic_bitset 6/23 Test #6: test_xdynamic_bitset . Passed0.00 sec Start 7: test_xfunctional 7/23 Test #7: test_xfunctional . Passed0.00 sec Start 8: test_xhalf_float 8/23 Test #8: test_xhalf_float . Passed0.00 sec Start 9: test_xhash 9/23 Test #9: test_xhash ... Passed6.46 sec Start 10: test_xhierarchy_generator 10/23 Test #10: test_xhierarchy_generator Passed0.00 sec Start 11: test_xiterator_base 11/23 Test #11: test_xiterator_base .. Passed0.00 sec Start 12: test_xmasked_value 12/23 Test #12: test_xmasked_value ...***Failed0.00 sec Start 13: test_xmeta_utils 13/23 Test #13: test_xmeta_utils . Passed0.00 sec Start 14: test_xmultimethods 14/23 Test #14: test_xmultimethods ... Passed0.00 sec Start 15: test_xoptional 15/23 Test #15: test_xoptional ... Passed0.00 sec Start 16: test_xsequence 16/23 Test #16: test_xsequence ... Passed0.00 sec Start 17: test_xtype_traits 17/23 Test #17: test_xtype_traits Passed0.00 sec Start 18: test_xplatform 18/23 Test #18: test_xplatform ... Passed0.00 sec Start 19: test_xproxy_wrapper 19/23 Test #19: test_xproxy_wrapper .. Passed0.00 sec Start 20: test_xsystem 20/23 Test #20: test_xsystem . Passed0.00 sec Start 21: test_xvariant 21/23 Test #21: test_xvariant Passed0.00 sec Start 22: test_xvisitor 22/23 Test #22: test_xvisitor Passed0.00 sec Start 23: xtest 23/23 Test #23: xtest ***Failed6.43 sec 91% tests passed, 2 tests failed out of 23 Total Test time (real) = 12.95 sec The following tests FAILED: 12 - test_xmasked_value (Failed) 23 - xtest (Failed) Errors while running CTest Output from these tests are in: /tmp/autopkgtest-lxc.yj53u3hj/downtmp/build.sSz/src/test/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. make: *** [Makefile:71: test] Error 8 autopkgtest [12:17:15]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures
Processing control commands: > affects -1 src:gcc-defaults Bug #1016156 [src:xtl] xtl: autopkgtest needs update on i386 for gcc-12 as default: 2 failures Added indication that 1016156 affects src:gcc-defaults -- 1016156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: pythran: autopkgtest needs update for gcc-12 as default
Processing control commands: > affects -1 src:gcc-defaults Bug #1016155 [src:pythran] pythran: autopkgtest needs update for gcc-12 as default Added indication that 1016155 affects src:gcc-defaults -- 1016155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dns323-firmware-tools: diff for NMU version 0.7.3-1.2
Processing control commands: > tags 999134 + patch Bug #999134 [src:dns323-firmware-tools] dns323-firmware-tools: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #999134 to the same tags previously set > tags 999134 + pending Bug #999134 [src:dns323-firmware-tools] dns323-firmware-tools: missing required debian/rules targets build-arch and/or build-indep Ignoring request to alter tags of bug #999134 to the same tags previously set > tags 1007083 + patch Bug #1007083 [src:dns323-firmware-tools] dns323-firmware-tools: please consider upgrading to 3.0 source format Ignoring request to alter tags of bug #1007083 to the same tags previously set > tags 1007083 + pending Bug #1007083 [src:dns323-firmware-tools] dns323-firmware-tools: please consider upgrading to 3.0 source format Ignoring request to alter tags of bug #1007083 to the same tags previously set -- 1007083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007083 999134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dns323-firmware-tools: diff for NMU version 0.7.3-1.2
Processing control commands: > tags 999134 + patch Bug #999134 [src:dns323-firmware-tools] dns323-firmware-tools: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999134 + pending Bug #999134 [src:dns323-firmware-tools] dns323-firmware-tools: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. > tags 1007083 + patch Bug #1007083 [src:dns323-firmware-tools] dns323-firmware-tools: please consider upgrading to 3.0 source format Added tag(s) patch. > tags 1007083 + pending Bug #1007083 [src:dns323-firmware-tools] dns323-firmware-tools: please consider upgrading to 3.0 source format Added tag(s) pending. -- 1007083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007083 999134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
