Bug#1065973: kmod: FTBFS due to time64 transition
Hi Marco, last week you offered in #debian-devel to upload kmod with tests disabled for 32 bit arm to work around the current situation. Could you please do that? Cheers Jochen * Simon McVittie [2024-03-21 12:23]: On Thu, 21 Mar 2024 at 15:45:13 +0500, Andrey Rakhmatullin wrote: On Wed, Mar 13, 2024 at 08:23:07AM +0100, Helge Deller wrote: > The patch below builds for me on the hppa platform. Unfortunately tests fail here with it in an armhf chroot, I don't know if it's generic or because the chroot is a qemu-based one on amd64. I think the root cause (both for needing to unset _FILE_OFFSET_BITS, and for the tests failing) is that kmod's test suite is interposing mock/wrapped versions of the stat() family. With the transition to 64-bit time_t, there are new members of the stat() family that will also need interposing on 32-bit architectures: __lstat64_time64() is the replacement for lstat(), and __stat64_time64() for stat(). There are also __fstat64_time64() and __fstatat64_time64(), but kmod doesn't seem to interpose fstat() or fstatat(), so those are probably unnecessary in this case. fakeroot, fakechroot and other LD_PRELOAD modules that interpose stat() will already be doing something similar, and might provide a useful reference for what is needed. Here's the equivalent in fakechroot: https://github.com/dex4er/fakechroot/pull/104/commits/dac74cd68cfb6eeaae9cd13bdc48737a44980df9 smcv signature.asc Description: PGP signature
Bug#1069904: Autopkgtests failed
Hi Elena, I have opened a MR to fix this: https://salsa.debian.org/python-team/packages/python-gnupg/-/merge_requests/1 Due to #1071561 I will not do more but it would be great if we could get this fixed. Cheers Jochen * Andrey Rakhmatullin [2024-04-27 00:32]: Package: python3-gnupg Version: 0.5.2-1 Severity: serious https://ci.debian.net/packages/p/python-gnupg/unstable/amd64/45884087/ 277s + python3.11 test_gnupg.py 493s ...F... 493s == 493s FAIL: test_search_keys (__main__.GPGTestCase.test_search_keys) 493s Test that searching for keys works 493s -- 493s Traceback (most recent call last): 493s File "/tmp/autopkgtest- lxc.s9943af9/downtmp/build.Ev1/src/test_gnupg.py", line 1252, in test_search_keys 493s self.assertEqual(0, r.returncode, 'Non-zero return code') 493s AssertionError: 0 != 2 : Non-zero return code -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-gnupg depends on: ii gnupg2.2.40-3 ii python3 3.11.8-1 python3-gnupg recommends no packages. python3-gnupg suggests no packages. signature.asc Description: PGP signature
Bug#1069904: marked as pending in python-gnupg
Control: tag -1 pending Hello, Bug #1069904 in python-gnupg 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-gnupg/-/commit/ed1d9477c00fea5e11c365cb66a6a9992bd712ab Switch to autopkgtest-pkg-pybuild Helmut confirmed that the gpg workaround for #682648 is no longer needed. Closes: #1069904 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069904
Bug#1070952: ros-vcstools: FTBFS in bullseye
Hi Santiago, thanks for the report. This seems to be due to git 1:2.30.2-1+deb11u1 as it works with the version before (1:2.30.2-1). Give that it is a security fix and a testing only problem that could worked around easily, I would leave this as is. Cheers Jochen * Santiago Vila [2024-05-11 21:53]: Package: src:ros-vcstools Version: 0.1.42-3 Severity: serious Control: close -1 0.1.42-7 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp [... snipped ...] 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_into_subdir_without_existing_parent (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_specific_version_and_update (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_current_version_label (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 5 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 5 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_environment_metadata (test.test_hg.HGClientTest) ... ok test_get_remote_version (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved abort: destination '/tmp/tmp18ac112f/local' is not empty pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_type_name (test.test_hg.HGClientTest) ... ok test_get_url_by_reading (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_url_nonexistant (test.test_hg.HGClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved testStatusUntracked (test.test_hg.HGDiffStatClientTest) ... ok test_diff (test.test_hg.HGDiffStatClientTest) ... ok test_diff_relpath (test.test_hg.HGDiffStatClientTest) ... ok test_get_version_modified (test.test_hg.HGDiffStatClientTest) ... ok test_hg_diff_path_change_None (test.test_hg.HGDiffStatClientTest) ... ok test_status (test.test_hg.HGDiffStatClientTest) ... ok test_status_relpath (test.test_hg.HGDiffStatClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_export_repository (test.test_hg.HGExportRepositoryClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_get_branches (test.test_hg.HGGetBranchesClientTest) ... pulling from
Bug#1070410: golang-github-pion-webrtc.v3 accesses the internet during build
Source: golang-github-pion-webrtc.v3
Version: 3.1.56-2
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
golang-github-pion-webrtc.v3 attempts network access during build.
This is forbidden by Policy 4.9:
For packages in the main archive, required targets must not attempt
network access, except, via the loopback interface, to services on the
build host that have been started by the build.
This can be tested with the sbuild unshare backend:
=== NAME TestDataChannelParamters_Go
util.go:41: Unexpected routines on test end:
goroutine 34 [select]:
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).loop(0xc240a0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:139
+0x12d
created by
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:74
+0x115
goroutine 35 [select]:
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).loop(0xc0001303c0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:97
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:86
+0x115
goroutine 36 [select]:
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).loop(0xc000130420,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:98
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:87
+0x115
[...]
Cheers Jochen
Bug#1070409: golang-github-pion-ice.v2: accesses the internet during build
Source: golang-github-pion-ice.v2 Version: 2.3.1-1 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-pion-ice.v2 attempts network access during build. This is forbidden by Policy 4.9: For packages in the main archive, required targets must not attempt network access, except, via the loopback interface, to services on the build host that have been started by the build. This can be tested with the sbuild unshare backend: === RUN TestConnectionStateCallback goroutine profile: total 16 2 @ 0x43f36e 0x40999f 0x4095d2 0x71a847 0x476061 # 0x71a846 github.com/pion/ice/v2.(*Agent).startOnConnectionStateChangeRoutine.func1+0x46 /<>/_build/src/github.com/pion/ice/v2/agent.go:424 2 @ 0x43f36e 0x438057 0x470a85 0x4a1ec7 0x4a4f0a 0x4a4ef3 0x565516 0x5a2004 0x5a568e 0x5a567c 0x5a8745 0x476061 # 0x470a84internal/poll.runtime_pollWait+0x84 /usr/lib/go-1.22/src/runtime/netpoll.go:345 # 0x4a1ec6internal/poll.(*pollDesc).wait+0x26 /usr/lib/go-1.22/src/internal/poll/fd_poll_runtime.go:84 # 0x4a4f09internal/poll.(*pollDesc).waitRead+0x129 /usr/lib/go-1.22/src/internal/poll/fd_poll_runtime.go:89 # 0x4a4ef2internal/poll.(*FD).RawRead+0x112 /usr/lib/go-1.22/src/internal/poll/fd_unix.go:708 # 0x565515net.(*rawConn).Read+0x35 /usr/lib/go-1.22/src/net/rawconn.go:44 # 0x5a2003golang.org/x/net/internal/socket.(*Conn).recvMsg+0x143 /<>/_build/src/golang.org/x/net/internal/socket/rawconn_msg.go:27 # 0x5a568dgolang.org/x/net/internal/socket.(*Conn).RecvMsg+0x4ad /<>/_build/src/golang.org/x/net/internal/socket/socket.go:247 # 0x5a567bgolang.org/x/net/ipv4.(*payloadHandler).ReadFrom+0x49b /<>/_build/src/golang.org/x/net/ipv4/payload_cmsg.go:31 # 0x5a8744github.com/pion/mdns.(*Conn).start+0xe4 /<>/_build/src/github.com/pion/mdns/conn.go:295 2 @ 0x43f36e 0x4510c5 0x4ea5b8 0x476061 # 0x4ea5b7context.(*cancelCtx).propagateCancel.func2+0x97 /usr/lib/go-1.22/src/context/context.go:510 2 @ 0x43f36e 0x4510c5 0x719098 0x476061 # 0x719097github.com/pion/ice/v2.(*Agent).taskLoop+0x137 /<>/_build/src/github.com/pion/ice/v2/agent.go:230 2 @ 0x43f36e 0x4510c5 0x71a5c5 0x476061 # 0x71a5c4 github.com/pion/ice/v2.(*Agent).startOnConnectionStateChangeRoutine.func2+0xa4 /<>/_build/src/github.com/pion/ice/v2/agent.go:433 2 @ 0x43f36e 0x4510c5 0x71b113 0x476061 # 0x71b112 github.com/pion/ice/v2.(*Agent).connectivityChecks+0x1b2 /<>/_build/src/github.com/pion/ice/v2/agent.go:550 1 @ 0x434a31 0x4706bd 0x531871 0x5316a5 0x52e4cb 0x7748bd 0x476061 # 0x4706bcruntime/pprof.runtime_goroutineProfileWithLabels+0x1c /usr/lib/go-1.22/src/runtime/mprof.go:1079 # 0x531870runtime/pprof.writeRuntimeProfile+0xb0 /usr/lib/go-1.22/src/runtime/pprof/pprof.go:774 # 0x5316a4runtime/pprof.writeGoroutine+0x44 /usr/lib/go-1.22/src/runtime/pprof/pprof.go:734 # 0x52e4caruntime/pprof.(*Profile).WriteTo+0x14a /usr/lib/go-1.22/src/runtime/pprof/pprof.go:369 # 0x7748bc github.com/pion/ice/v2.TestConnectionStateCallback.TimeOut.func2+0x3c /<>/_build/src/github.com/pion/transport/test/util.go:21 1 @ 0x43f36e 0x40999f 0x4095b2 0x4faeeb 0x4fd037 0x4fa01b 0x4fcf25 0x4fb92b 0x77c2ac 0x43ef1d 0x476061 # 0x4faeeatesting.(*T).Run+0x3aa /usr/lib/go-1.22/src/testing/testing.go:1750 # 0x4fd036testing.runTests.func1+0x36 /usr/lib/go-1.22/src/testing/testing.go:2161 # 0x4fa01atesting.tRunner+0xfa /usr/lib/go-1.22/src/testing/testing.go:1689 # 0x4fcf24testing.runTests+0x444 /usr/lib/go-1.22/src/testing/testing.go:2159 # 0x4fb92atesting.(*M).Run+0x68a /usr/lib/go-1.22/src/testing/testing.go:2027 # 0x77c2abmain.main+0x16b _testmain.go:225 # 0x43ef1cruntime.main+0x29c /usr/lib/go-1.22/src/runtime/proc.go:271 1 @ 0x43f36e 0x4510c5 0x73a965 0x766c5b 0x766c32 0x746425 0x4fa01b 0x476061 # 0x73a964github.com/pion/ice/v2.(*Agent).connect+0x124 /<>/_build/src/github.com/pion/ice/v2/transport.go:53 # 0x766c5agithub.com/pion/ice/v2.(*Agent).Dial+0xfa /<>/_build/src/github.com/pion/ice/v2/transport.go:15 # 0x766c31github.com/pion/ice/v2.connect+0xd1 /<>/_build/src/github.com/pion/ice/v2/transport_test.go:219 # 0x746424
Bug#1070334: libnet-frame-device-perl needs network access during build
Source: libnet-frame-device-perl Version: 1.12-1 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, libnet-frame-device-perl fails to build with no network connection: 1..1 # Running under perl version 5.038002 for linux # Current time local: Sat Apr 27 12:53:04 2024 # Current time GMT: Sat Apr 27 12:53:04 2024 # Using Test.pm version 1.31 ok 1 # skip Test::Pod 1.00 required for testing ok Net::Frame::Device: updateFromDefault: unable to get dnet This can be tested with the sbuild unshare backend. Cheers Jochen
Bug#1069809: xhtml2pdf accesses network resources during the build
Source: xhtml2pdf Version: 0.2.15+dfsg-1 Severity: serious Tags: sid trixie ftbfs xhtml2pdf accesses network resources during the build: == FAIL: test_document_cannot_identify_image (tests.test_document.DocumentTest.test_document_cannot_identify_image) Test that images which cannot be identified don't cause stack trace to be printed -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 189, in test_document_cannot_identify_image self.assertEqual( AssertionError: Lists differ: ['WAR[16 chars]ags:Could not get image data from src attribut[265 chars]>\''] != ['WAR[16 chars]ags:Cannot identify image file:\n\'\'' + ['WARNING:xhtml2pdf.tags:Cannot identify image file:\n' - ['WARNING:xhtml2pdf.tags:Could not get image data from src attribute: ' - 'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif\n' "'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif"/>\''] == FAIL: test_document_with_broken_image (tests.test_document.DocumentTest.test_document_with_broken_image) Test that broken images don't cause unhandled exception -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 169, in test_document_with_broken_image self.assertEqual( AssertionError: Lists differ: [] != ["WARNING:xhtml2pdf.xhtml2pdf_reportlab:SV[151 chars]ml'"] Second list contains 1 additional elements. First extra element 0: "WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: 'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'" - [] + ['WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: ' + "'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'"]
Bug#1069805: scikit-build tries pip install during build
Source: scikit-build
Version: 0.17.6-1
Severity: serious
Tags: trixie sid ftbfs
scikit-build accesses network resources during the build:
process =
stdout = None, stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them,
or pass capture_output=True to capture both.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except: # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
> raise CalledProcessError(retcode, process.args,
output=stdout, stderr=stderr)
E subprocess.CalledProcessError: Command '['/usr/bin/python3.12',
'-m', 'pip', 'wheel', '--wheel-dir',
'/tmp/pytest-of-jspricke/pytest-21/wheelhouse0', '/build/package/package']'
returned non-zero exit status 1.
Bug#1069804: rust-mio-0.6 accesses network resources during the build
Source: rust-mio-0.6
Version: 0.6.23-3
Severity: serious
Tags: sid trixie ftbfs
rust-mio-0.6 accesses network resources during the build:
Test executable failed (exit status: 101).
stderr:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }',
src/sys/unix/ready.rs:22:16
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::result::unwrap_failed
at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
3: core::result::Result::unwrap
4: rust_out::main
5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
src/poll.rs - poll::Poll (line 267)
src/poll.rs - poll::Poll::deregister (line 877)
src/poll.rs - poll::Poll::register (line 735)
src/poll.rs - poll::Poll::reregister (line 820)
src/sys/unix/ready.rs - sys::unix::ready::UnixReady (line 66)
test result: FAILED. 74 passed; 5 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 4.37s
Bug#1069803: php-codeigniter-framework tries pip install during build
Source: php-codeigniter-framework
Version: 3.1.13+dfsg1-3
Severity: serious
Tags: sid trixie ftbfs
php-codeigniter-framework accesses network resources during the build:
python3 -m venv --system-site-packages --without-pip debian/build-doc/pythonvenv
if ! debian/build-doc/pythonvenv/bin/python -m pip show pycilexer; then \
echo "Installing pycilexer" && \
cd user_guide_src/cilexer && \
../../debian/build-doc/pythonvenv/bin/python -m pip install .; \
fi
WARNING: Package(s) not found: pycilexer
Installing pycilexer
Processing /build/package/package/user_guide_src/cilexer
Installing build dependencies: started
Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [7 lines of output]
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None,
status=None)) after connection broken by
'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement
setuptools>=40.8.0 (from versions: none)
ERROR: No matching distribution found for setuptools>=40.8.0
[end of output]
note: This error originates from a subprocess, and is likely not a problem
with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with
pip.
Bug#1067934: jameica: Jameica cannot load plugins | service "database" not found
Control: severity -1 normal Hi Ferdinand, * Ferdinand Rau [2024-03-29 08:51]: * What led up to the situation? The plugin Hibiscus, arguably the most important plugin for jameica, was updated. Version 2.10.15 used to work fine and still does work fine with the jameica packages in Debian Bookworm and Trixie. Versions 2.10.16 and the current version 2.10.17 do not work with either Debian package, but do work fine with the latest version of jameica (2.10.4) downloaded from the upstream source willuhn.de: https://www.willuhn.de/products/hibiscus/download.php Plugin-updates/installs were performed using the integrated plugin management of jameica. That is expected, software in stable is only supported with other software in stable, i.e. with the Hibiscus plugin in stable. Staying with hibiscus 2.10.15 is not an option in the long term, because updates introduce bug fixes and, most importantly, fix access for several German banks that changed their online access to different servers and protocols. Without the update to hibiscus 2.10.17, lots of bank accounts are inaccessible for the users. This is too unspecific to call for an update in stable. From my understanding all updates are configuration changes that can be done with the stable version as well. Downgrading the bug accordingly. Note that Debian stable updates have a strict policy noted here: https://lists.debian.org/debian-devel-announce/2019/08/msg0.html * Ferdinand Rau [2024-03-29 12:41]: The upstream author suggests that the issue may be related to the "H2 Database Engine" (Debian package: jameica-h2database) in a similar, but not identical case here: https://homebanking-hilfe.de/forum/topic.php?p=170111#real170111 Upstream H2 is at version 2.2.224, whereas Debian is at 1.4.197-7, which is approx. six years old. An update of jameica-h2database will likely fix this issue? Sadly no, while upstream H2 is at 2.2.224 and the Debian package (libh2-java) is at 2.2.220, Jameica ships 1.4.199, this is why the jameica-h2database was created in the first first place. I will update it to 1.4.199 together with Jameica in unstable. Cheers Jochen signature.asc Description: PGP signature
Bug#1067297: marked as pending in taskw
Control: tag -1 pending Hello, Bug #1067297 in taskw 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/taskw/-/commit/8a061fb95ba06d5abae05248efab04d2ebb70ed5 Fix tests with new pytest Closes: #1067297 (this message was generated automatically) -- Greetings https://bugs.debian.org/1067297
Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst
Control: severity -1 normal Hi Andreas, * Andreas Beckmann [2024-03-24 10:23]: On Thu, 21 Mar 2024 18:39:00 +0100 Jochen Sprickerhof wrote: dpkg -S configuration.rst bugwarrior: /usr/share/doc/bugwarrior/html/_sources/common_configuration.rst.txt bugwarrior: /usr/share/doc/bugwarrior/html/_sources/configuration.rst.txt The second one is the same file. I will push new version with a fixed path. Does the package work with /usr/share/doc excluded from installation? https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation. "Packages must not require the existence of any files in /usr/share/doc/ in order to function. [6] Any files that are used or read by programs but are also useful as stand alone documentation should be installed elsewhere, such as under /usr/share/package/, and then included via symbolic links in /usr/share/doc/package." It works fine. The only missing bit is printing an example configuration if the config is wrong, which I think is not RC and fine if the documentation is not installed. Thus downgrading the bug. Cheers Jochen signature.asc Description: PGP signature
Bug#1067444: marked as pending in bugwarrior
Control: tag -1 pending Hello, Bug #1067444 in bugwarrior 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/tasktools-team/bugwarrior/-/commit/feb568da9b02f1c84f7aac27c129fe878beb22be Add patch for documentation path Closes: #1067444 (this message was generated automatically) -- Greetings https://bugs.debian.org/1067444
Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst
Hi Tj,
* Tj [2024-03-21 16:08]:
Severity: grave
Justification: renders package unusable
I disagree here. Any reason why you did it?
With a fresh install and manually creating the user's configuration file
I hit this error. The path reported seems to indicate the package is not
shipping the file mentioned. I tried moving the user config directory and
saw the error caused by it being missing, put it back, and hit this package
config file issue agian.
$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory:
'/home/tj/.config/bugwarrior/bugwarriorrc'
$ mv ~/.config/bugwarrior{.bak,}
$ bugwarrior-pull
CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not
created a configuration file.
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst'
$ cat ~/.config/bugwarrior/bugwarriorrc
[general]
targets = debianbts my_github
Delete my_github here, as you don't have a section on it.
[debianbts]
service = bts
bts.email = deb...@iam.tj
Add bts.udd = True to get your bugs ;).
$ dpkg -S docs/configuration.rst
dpkg-query: no path found matching pattern *docs/configuration.rst*
$ apt-file search docs/configuration.rst
$
dpkg -S configuration.rst
bugwarrior: /usr/share/doc/bugwarrior/html/_sources/common_configuration.rst.txt
bugwarrior: /usr/share/doc/bugwarrior/html/_sources/configuration.rst.txt
The second one is the same file. I will push new version with a fixed
path.
Cheers Jochen
signature.asc
Description: PGP signature
Bug#1066432: closing 1066432
close 1066432 thanks Builds again, probably same as #1066399.
Bug#1066409: Linker fails to find libraries in unstable but succeeds in testing
Hi Andreas, * Andreas Tille [2024-03-15 07:31]: Hi, thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one package of the R pkg team is affected by some strange linker issue #1066409 r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or directory which boils down to[1] g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so RcppExports.o bindings.o -lv8 -lv8_libplatform -L/usr/lib/R/lib -lR /usr/bin/ld: cannot find -lv8: No such file or directory /usr/bin/ld: cannot find -lv8_libplatform: No such file or directory The Build-Depends libnode-dev provides both libraries and when I try to build the package under testing all is fine. Is there any linker issue involved that might be introduced in unstable? I guess that's the same as #1066399. libnode-dev: libv8.so -> libnode.so libnode.so -> libnode.so.108t64 But libnode.so.108t64 does not exist Cheers Jochen signature.asc Description: PGP signature
Bug#1064139: Bug #1064139 ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’
Hi Flavien, * Flavien Bridault [2024-03-07 08:07]: I just cloned the repository to open the MR but then I realized there is already a branch opened two weeks ago exactly with the fix I proposed... So I guess it is on its way ? I guess you mean: https://salsa.debian.org/games-team/ogre/-/tree/fix_imgui That was my try to fix it but it fails later on in the build (as can be seen in CI). Help appreciated. Cheers Jochen signature.asc Description: PGP signature
Bug#1064734: libhx/hxtools: FTBFS: ./smath/./smath/graph-fanout.c:263:(.text.startup+0x139): undefined reference to `BUILD_BUG_ON_EXPR'
Control: reassign -1 src:libhx 4.19-1 Control: retitle -1 Please include upstream patch Control: affects -1 src:hxtools Hi Jörg, can you please upload a new libhx either containing this upstream patch or the new upstream release to unbreak hxtools? https://codeberg.org/jengelh/libhx/commit/e55e06348d1e5b531c8bffe435bddc31e2010ab1 Thanks! Jochen * Lucas Nussbaum [2024-02-25 20:27]: Source: hxtools Version: 20231224-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/bin/ld: graph-fanout.o: in function `fanout_get_options': ./smath/./smath/graph-fanout.c:263:(.text.startup+0x139): undefined reference to `BUILD_BUG_ON_EXPR' collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/02/24/hxtools_20231224-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. signature.asc Description: PGP signature
Bug#1062865: closing 1062865
close 1062865 thanks According to Steve this is a false positive (in #debian-devel)
Bug#999989: poco 1.1 uses PCRE3, Mumble 1.5 depends on poco
* Chris Knadle [2024-01-07 00:29]: The main thing I'd like to understand is how to do coordinate the transition (i.e. the release) with the Release Team. I found some hints about that here: https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#lib-trans The wiki page linked there seems correct. Please ask if you have more specific questions. There is also Debian Mentors to help: https://wiki.debian.org/DebianMentors Cheers Jochen signature.asc Description: PGP signature
Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco
* Chris Knadle [2024-01-02 16:53]: The way to orphan a package is to do an upload and setting the maintainer to be . Until that's done the package ends up in maintainership limbo. See the bottom of Policy 3.3, and Developer's Reference section 5.9.4. Agreed but I think that is something for the Maintainer: to do, who seems to be active in Debian, otherwise. I may be able to prepare an updated version to upload as an NMU (i.e. it would be Debian version 1.13.0-0.1), but I can't take over maintaining this package long-term because I don't use it and am not familiar with it -- I only maintain a package that has it as a required build dependency. I also haven't maintained a library yet, but I've been in this situation of needing to upload a newer version of a library before so I might be able to figure out what's required to prepare an upload. It would be interesting to upload a new version as an NMU with the maintainer marked as but strangely that seems to be what's called for here. Feel free to ask if you have questions regarding maintaining a library. Cheers Jochen signature.asc Description: PGP signature
Bug#1058343: marked as pending in ros2-colcon-metadata
Control: tag -1 pending Hello, Bug #1058343 in ros2-colcon-metadata 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/robotics-team/ros2-colcon-metadata/-/commit/4a955f1e33712ff44e28112270677f614be6a74c Skip linter tests Closes: #1058343 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058343
Bug#999989: poco 1.2 uses PCRE2, Mumble 1.5 depends on poco
Hi Chris, * Chris Knadle [2024-01-02 03:06]: Can the poco library be updated? Can I help in some way? poco is basically orphaned, as I dropped myself from Uploaders in git and did not hear from the other maintainers for some time. The best way to help is to step up as a maintainer and update it ;). Unless the Poco library can be updated the only way to save Mumble will be to introduce an epoch in the package version to upload the now well outdated mumble 1.3.4 again which upstream cannot support anymore. Nit: please don't use epochs for that, also see Policy 5.6.12.1. Cheers Jochen signature.asc Description: PGP signature
Bug#1056415: marked as pending in isbg
Control: tag -1 pending Hello, Bug #1056415 in isbg 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/isbg/-/commit/4217495a213c64a3162c167f69900135120856d4 Drop extra TypeVar, fails in Python 3.12 Closes: #1056415 (this message was generated automatically) -- Greetings https://bugs.debian.org/1056415
Bug#1042244: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Hi Andreas, * Andreas Tille [2023-12-11 16:42]: Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244. Unfortunately this is not the case and now with Python3.12 we also have to deal with the removal of imp (which affects bug #1056419). I'd like to ask for help on debian-python list since I'm pretty overworked with other stuff. Please also review my rude patch[1] to hack around a shinx issue. It would be great to have some better solution here. You can find a full build log of the latest upstream version in Salsa CI[2]. I think the right thing here is to package the new uncertainties version which drops the past import: https://github.com/lebigot/uncertainties/releases/tag/3.1.7 Also we should probably get rid of python-future at some point. Cheers Jochen signature.asc Description: PGP signature
Bug#1056231: marked as pending in bugwarrior
Control: tag -1 pending Hello, Bug #1056231 in bugwarrior 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/tasktools-team/bugwarrior/-/commit/6db847e5c3c4b0488a36ef4fb970f60852bf2a5d Drop future import Closes: #1056231 (this message was generated automatically) -- Greetings https://bugs.debian.org/1056231
Bug#1054536: cyrus-sasl2 FTBFS: sphinx failure: AttributeError("'str' object has no attribute 'attributes'")
Hi Helmut,
* Helmut Grohne [2023-10-25 11:47]:
Source: cyrus-sasl2
Version: 2.1.28+dfsg1-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
cyrus-sasl2 fails to build from source in unstable. A non-parallel build
ends as follows:
| /usr/bin/sphinx-build -d docsrc/.doctrees -n -q -D today=2023-08-03 -b html
./docsrc ./doc/html
| WARNING: extlinks: Sphinx-6.0 will require a caption string to contain
exactly one '%s' and all other '%' need to be escaped as '%%'.
| WARNING: extlinks: Sphinx-6.0 will require a caption string to contain
exactly one '%s' and all other '%' need to be escaped as '%%'.
|
| Theme error:
| An error happened in rendering the page developer.
| Reason: AttributeError("'str' object has no attribute 'attributes'")
| make[2]: *** [Makefile:1165: doc/html/.sphinx-build.stamp] Error 2
| make[2]: Leaving directory '/<>/build-mit'
| dh_auto_build: error: cd build-mit && make -j1
sasldir=/usr/lib/x86_64-linux-gnu/sasl2 all doc-html returned exit code 2
| make[1]: *** [debian/rules:166: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:127: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I don't quit see the cause of this failure just yet, maybe someone else
does?
This is due to this line:
https://sources.debian.org/src/cyrus-sasl2/2.1.28%2Bdfsg1-3/docsrc/_templates/layout.html/#L2
and a simple workaround is to remove it.
I think a proper fix is to add
html_css_files = ['cyrus.css']
to docsrc/conf.py instead, as per
https://docs.readthedocs.io/en/stable/guides/adding-custom-css.html
But I have not verified that it gives the same result.
Cheers Jochen
signature.asc
Description: PGP signature
Bug#1052814: marked as pending in python-recurring-ical-events
Control: tag -1 pending Hello, Bug #1052814 in python-recurring-ical-events 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-recurring-ical-events/-/commit/f15c7ce4b81ab8e9454b1cdb07e5e48f2d310ca8 Use non legacy timzone names Closes: #1052814 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052814
Bug#1052862: marked as pending in python-icalendar
Control: tag -1 pending Hello, Bug #1052862 in python-icalendar 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-icalendar/-/commit/10cef8c43e5d0a2a38adf13970c2a0d3b3a2230a Use non legacy timezone name Closes: #1052862 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052862
Bug#1050902: closing 1050902
close 1050902 0.19.0-1 thanks
Bug#1050530: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1050530: fixed in python3.11 3.11.5-2)
Hi Matthias, I think it would be enough to add the tzdata-legacy dependency to libpython3.11-testsuite. I've also send a patch upstream to switch to the normal name: https://github.com/python/cpython/pull/108533 Cheers Jochen * Debian Bug Tracking System [2023-08-26 19:09]: This is an automatic notification regarding your Bug report which was filed against the src:python3.11 package: #1050530: python3.11: autopkgtest needs update for new version of tzdata It has been closed by Debian FTP Masters (reply to Matthias Klose ). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Debian FTP Masters (reply to Matthias Klose ) by replying to this email. -- 1050530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Date: Sat, 26 Aug 2023 19:05:36 + To: 1050530-cl...@bugs.debian.org Reply-To: Matthias Klose From: Debian FTP Masters Subject: Bug#1050530: fixed in python3.11 3.11.5-2 Date: Fri, 25 Aug 2023 21:08:52 +0200 To: sub...@bugs.debian.org User-Agent: Mozilla Thunderbird From: Paul Gevers Subject: python3.11: autopkgtest needs update for new version of tzdata Source: python3.11 Version: 3.11.4-1 Severity: serious X-Debbugs-CC: tzd...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:tzdata Dear maintainer(s), With a recent upload of tzdata the autopkgtest of python3.11 fails in testing when that autopkgtest is run with the binary packages of tzdata from unstable. It passes when run with only packages from testing. In tabular form: passfail tzdata from testing2023c-10 python3.11 from testing3.11.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that src:tzdata recently introduced a tzdata-legacy package although I don't know if that has to do with the failure. Currently this regression is blocking the migration of tzdata to testing [1]. Of course, tzdata shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in tzdata was intended and your package needs to update to the new situation. 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=tzdata https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.11/37127326/log.gz 1107s == 1107s FAIL: test_variable_tzname (test.test_email.test_utils.LocaltimeTests.test_variable_tzname) 1107s -- 1107s Traceback (most recent call last): 1107s File "/usr/lib/python3.11/test/support/__init__.py", line 847, in inner 1107s return func(*args, **kwds) 1107s^^^ 1107s File "/usr/lib/python3.11/test/test_email/test_utils.py", line 155, in test_variable_tzname 1107s self.assertEqual(t1.tzname(), 'MSK') 1107s AssertionError: 'Europe' != 'MSK' 1107s - Europe 1107s + MSK signature.asc Description: PGP signature
Bug#1037698: j4-dmenu-desktop: diff for NMU version 2.16-1.1
Control: tags 1037698 + patch Dear maintainer, I've prepared an NMU for j4-dmenu-desktop (versioned as 2.16-1.1). The diff is attached to this message. Regards. Jochen diff -Nru j4-dmenu-desktop-2.16/debian/changelog j4-dmenu-desktop-2.16/debian/changelog --- j4-dmenu-desktop-2.16/debian/changelog 2018-09-10 21:26:15.0 +0200 +++ j4-dmenu-desktop-2.16/debian/changelog 2023-07-30 16:19:24.0 +0200 @@ -1,3 +1,10 @@ +j4-dmenu-desktop (2.16-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix build with GCC 13 (Closes: #1037698) + + -- Jochen Sprickerhof Sun, 30 Jul 2023 16:19:24 +0200 + j4-dmenu-desktop (2.16-1) unstable; urgency=medium * New upstream release diff -Nru j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch --- j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch 1970-01-01 01:00:00.0 +0100 +++ j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch 2023-07-30 16:18:44.0 +0200 @@ -0,0 +1,28 @@ +From: Sam James +Date: Tue, 18 Apr 2023 11:08:53 +0100 +Subject: Fix build with GCC 13 + +GCC 13 (as usual for new compiler releases) shuffles around some internal includes so some +are no longer transitively included. + +See https://gnu.org/software/gcc/gcc-13/porting_to.html. + +Bug: https://bugs.gentoo.org/895200 +--- + src/Application.hh | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/src/Application.hh b/src/Application.hh +index 355be9b..d24ff1c 100644 +--- a/src/Application.hh b/src/Application.hh +@@ -19,7 +19,8 @@ + #define APPLICATION_DEF + + #include +-#include ++#include ++#include + #include + + #include "Utilities.hh" diff -Nru j4-dmenu-desktop-2.16/debian/patches/series j4-dmenu-desktop-2.16/debian/patches/series --- j4-dmenu-desktop-2.16/debian/patches/series 2018-09-10 21:26:15.0 +0200 +++ j4-dmenu-desktop-2.16/debian/patches/series 2023-07-30 16:18:48.0 +0200 @@ -1,2 +1,3 @@ 0001-remove-catch-download.patch 0002-remove-testcase-for-desktop-systems.patch +0003-Fix-build-with-GCC-13.patch signature.asc Description: PGP signature
Bug#1037698: j4-dmenu-desktop: ftbfs with GCC-13
Control: forwared -1 https://github.com/enkore/j4-dmenu-desktop/pull/139 Hi Peter, j4-dmenu-desktop is a dependency of sxmo-utils and so I would like to prevent it's removal from testing. The patch linked above is really simple and I would be happy if you could upload a fixed version. I can also sponsor the upload, if needed. There where also multiple new upstream versions and I would be happy to help maintain this package if you would be ok with that. In case you don't have time to do the upload, I can do an NMU. If you don't answer by end of next week I will assume that you are ok with an NMU containing the above patch and will upload. Cheers Jochen * Matthias Klose [2023-06-14 09:25]: Package: src:j4-dmenu-desktop Version: 2.16-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/j4-dmenu-desktop_2.16-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] | ^~~ /<>/src/Application.hh:149:22: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [11]’, ‘long unsigned int’ arguments 149 | case "OnlyShowIn"_istr: | ^ /<>/src/Application.hh:161:22: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ arguments 161 | case "NotShowIn"_istr: | ^~~~ /<>/src/Application.hh:173:22: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [7]’, ‘long unsigned int’ arguments 173 | case "Hidden"_istr: | ^ /<>/src/Application.hh:174:22: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ arguments 174 | case "NoDisplay"_istr: | ^~~~ /<>/src/Application.hh:182:22: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [9]’, ‘long unsigned int’ arguments 182 | case "Terminal"_istr: | ^~~ /<>/src/Application.hh:183:61: error: unable to find string literal operator ‘operator""_istr’ with ‘const char [5]’, ‘long unsigned int’ arguments 183 | this->terminal = make_istring(value) == "true"_istr; | ^~~ In file included from /<>/src/TestFormatters.cc:8: /<>/src/Application.hh: In member function ‘bool Application::read(const char*, char**, size_t*)’: /<>/src/Application.hh:94:19: warning: ignoring return value of ‘char* getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 94 | getcwd(pwd, 100); | ~~^~ /<>/src/Main.hh: In member function ‘bool Main::read_args(int, char**)’: /<>/src/Main.hh:167:33: warning: this statement may fall through [-Wimplicit-fallthrough=] 167 | exclude_generic = true; | ^~ /<>/src/Main.hh:168:13: note: here 168 | case 'l': | ^~~~ /<>/src/Main.hh: In member function ‘void Main::collect_files()’: /<>/src/Main.hh:187:15: warning: ignoring return value of ‘char* getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 187 | getcwd(original_wd, 384); | ~~^~ /<>/src/Main.hh:195:18: warning: ignoring return value of ‘int chdir(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 195 | chdir(path.c_str()); | ~^~ /<>/src/Main.hh:204:14: warning: ignoring return value of ‘int chdir(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 204 | chdir(original_wd); |
Bug#1039616: marked as pending in python-lsp-server
Control: tag -1 pending Hello, Bug #1039616 in python-lsp-server 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-lsp-server/-/commit/4c136b1ab811b1ba2bae67469f6228615a597121 Fix python3-pydocstyle version Closes: #1039616 (this message was generated automatically) -- Greetings https://bugs.debian.org/1039616
Bug#1033822: marked as pending in oscrypto
Control: tag -1 pending Hello, Bug #1033822 in oscrypto 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/oscrypto/-/commit/2785beddf7f492fb728df9fdfa53724ee3192bdc Switch to autopkgtest-pkg-pybuild This has also the effect that test_tls.py is no longer executed which fails due to expired certificates. Closes: #1033822 (this message was generated automatically) -- Greetings https://bugs.debian.org/1033822
Bug#1037165: vit: Python TypeError: 'str' object does not support item assignment
Control: severity -1 normal
Hi Matthew,
On Tue, 6 Jun 2023 19:43:34 +0100 Matthew Lemon wrote:
> Traceback (most recent call last):
> File "/usr/bin/vit", line 33, in
> sys.exit(load_entry_point('vit==2.2.0', 'console_scripts', 'vit')())
> ^^
> File "/usr/lib/python3/dist-packages/vit/command_line.py", line 5, in main
> Application(options, filters)
> File "/usr/lib/python3/dist-packages/vit/application.py", line 77, in
> __init__
> self.refresh(False)
> File "/usr/lib/python3/dist-packages/vit/application.py", line 920, in
> refresh
> self.bootstrap(load_early_config)
> File "/usr/lib/python3/dist-packages/vit/application.py", line 110, in
> bootstrap
> self.load_contexts()
> File "/usr/lib/python3/dist-packages/vit/application.py", line 104, in
> load_contexts
> self.contexts = self.task_config.get_contexts()
> ^^^
> File "/usr/lib/python3/dist-packages/vit/config_parser.py", line 333, in
> get_contexts
> subtree = self.subtree('context.')
>
> File "/usr/lib/python3/dist-packages/vit/config_parser.py", line 292, in
> subtree
> tree_location[part] = {} if len(parts) else value
> ~^^
> TypeError: 'str' object does not support item assignment
I can't reproduce this in a fresh system (downgrading severity accordingly). Do
you have any taskwarrior or vit config files in your home? Judging from the
trace above I guess it is a custom taskwarrior config. Can you try without that?
Cheers Jochen
Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed
* James Addison [2023-06-01 12:44]: Would reverting the Install.WantedBy modification[1][2], restoring e2scrub_reap enablement using 'default.target' on relevant systems, be a sensible approach for bookworm until we can figure out the debhelper-system behaviour when that setting changes? No, bookworm is frozen and done: "In the last week prior to the freeze, testing will be completely frozen and only emergency bug fixes will be considered in this period." https://lists.debian.org/debian-devel-announce/2023/04/msg7.html Cheers Jochen signature.asc Description: PGP signature
Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed
Hi Michael, * Michael Biebl [2023-05-30 13:23]: bullseye chroot upgraded to bookworm: # find /etc/systemd/system/ -name e2scrub_reap.service /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service /etc/systemd/system/default.target.wants/e2scrub_reap.service But when you use a VM: $ debvm-create -r bullseye $ debvm-run # apt install e2fsprogs # find / -name e2scrub_reap.service /var/lib/systemd/deb-systemd-helper-enabled/default.target.wants/e2scrub_reap.service /lib/systemd/system/e2scrub_reap.service /etc/systemd/system/default.target.wants/e2scrub_reap.service # cat /var/lib/systemd/deb-systemd-helper-enabled/e2scrub_reap.service.dsh-also /etc/systemd/system/default.target.wants/e2scrub_reap.service # sed -i 's/bullseye/bookworm/' /etc/apt/sources.list # apt update # apt dist-upgrade # find / -name e2scrub_reap.service /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/e2scrub_reap.service /var/lib/systemd/deb-systemd-helper-enabled/default.target.wants/e2scrub_reap.service /usr/lib/systemd/system/e2scrub_reap.service /etc/systemd/system/default.target.wants/e2scrub_reap.service # cat /var/lib/systemd/deb-systemd-helper-enabled/e2scrub_reap.service.dsh-also /etc/systemd/system/default.target.wants/e2scrub_reap.service /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service So what I would suggest is a if dpkg --compare-versions "$2" lt "$ver of your next upload"; then rm -f /etc/systemd/system/default.target.wants/e2scrub_reap.service fi in your postinst to clean up the stray enablement symlink. I think this would disable the service for users that upgraded from bullseye as shown above. Cheers Jochen signature.asc Description: PGP signature
Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed
Hi Ted, * Theodore Ts'o [2023-05-27 19:45]: So sure, /etc/systemd.d/system/multi-user.target.wants/e2scrub_reap.service doesn't exist. *But* it still exists in .../default.target.wants/... which seems to be enough to keep the e2scrub_reap service enabled. Right? Yes, that's fine. In any case, I am still unclear (a) what is actually broken in this particular setup, since according to systemctl status the systemd unit is apparently still appropriate enabled, even if it isn't via the expected Wanted-b: multi-user.target. The point of piuparts is that an upgraded system is different to a newly installed system, i.e. that the e2scrub_reap.service symlink lies in a different directory. And secondly, (b) what is e2fsprogs's control scripts supposed to have done differently? That is, if this is indeed this is a bug in e2fsprogs --- what did I do wrong, and how do I fix it? Arguably nothing and init-system-helpers/dh_installsystemd should detect the change and move the symlink. And if the answer is you should never, ever, try to change a Wanted-by line in a systemd script, because debian's systemd unit file infrastructure is too fragile to handle this correctly, given that bookworm is about to ship with "Wanted-by: multi-user.target", what's the best path forward at this point? For now the best way is to do nothing and wait for the bookworm release. In general there are two things. One is to fix the immediate problem this issue is about and we can still do that in a point release. The other one is to have general support for changing Wanted-by: (or state that it is not supported). I would propose to ask the init-system-helpers/dh_installsystemd maintainers for a general solution and then apply that for a bookworm point release. Cheers Jochen signature.asc Description: PGP signature
Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)
Control: severity -1 minor Control: tags -1 + moreinfo Hi Claude, given your information and that the package builds fine on the buildds I downgrade this to minor and add a moreinfo tag. Cheers Jochen * Jochen Sprickerhof [2023-05-25 14:56]: Thanks for the information. I don't see why it should use llvm, on the other hand the kernel Makefile is rather clear when to use it. Can you check if you an still reproduce the problem? * Claude Heiland-Allen [2023-05-25 11:47]: Hi Jochen, I didn't set any non-standard compiler options as far as I recall. I certainly was not intending to build with LLVM. Unfortunately I have not kept the log of the failing build, but I remember seeing that gcc was used for the majority of the compilation. Regards, Claude signature.asc Description: PGP signature
Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)
Thanks for the information. I don't see why it should use llvm, on the other hand the kernel Makefile is rather clear when to use it. Can you check if you an still reproduce the problem? * Claude Heiland-Allen [2023-05-25 11:47]: Hi Jochen, I didn't set any non-standard compiler options as far as I recall. I certainly was not intending to build with LLVM. Unfortunately I have not kept the log of the failing build, but I remember seeing that gcc was used for the majority of the compilation. Regards, Claude PS: export output as requested: $ export declare -x ANDROID_HOME="/home/claude/opt/android" declare -x ANDROID_NDK_HOME="/home/claude/opt/android/ndk/21.4.7075529" declare -x CLUTTER_IM_MODULE="ibus" declare -x COLORTERM="truecolor" declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" declare -x DESKTOP_SESSION="xfce" declare -x DISPLAY=":0.0" declare -x GDMSESSION="xfce" declare -x GNOME_TERMINAL_SCREEN="/org/gnome/Terminal/screen/0b1a867e_925f_4768_96f3_643cc3c21d91" declare -x GNOME_TERMINAL_SERVICE=":1.84" declare -x GTK_IM_MODULE="ibus" declare -x GTK_MODULES="gail:atk-bridge" declare -x HOME="/home/claude" declare -x LANG="en_GB.UTF-8" declare -x LANGUAGE="en_GB:en" declare -x LD_LIBRARY_PATH="/home/claude/opt/lib" declare -x LOGNAME="claude" declare -x LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35 :*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:" declare -x OLDPWD declare -x PANEL_GDK_CORE_DEVICE_EVENTS="0" declare -x PATH="/home/claude/opt/vbcc/vbcc/bin:/opt/amiga/bin:/home/claude/opt/android/ndk/21.4.7075529:/home/claude/opt/android/platform-tools:/home/claude/opt/android/tools:/home/claude/opt/bin:/home/claude/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/claude/opt/bin" declare -x PWD="/home/claude" declare -x QT_ACCESSIBILITY="1" declare -x QT_IM_MODULE="ibus" declare -x QT_QPA_PLATFORMTHEME="gtk2" declare -x SESSION_MANAGER="local/eiskaffee:@/tmp/.ICE-unix/1911,unix/eiskaffee:/tmp/.ICE-unix/1911" declare -x SHELL="/bin/bash" declare -x SHLVL="1" declare -x SSH_AGENT_PID="2048" declare -x SSH_AUTH_SOCK="/tmp/ssh-XXtd5uft/agent.1911" declare -x TERM="xterm-256color" declare -x USER="claude" declare -x VBCC="/opt/amiga/vbcc" declare -x VTE_VERSION="7003" declare -x XAUTHORITY="/home/claude/.Xauthority" declare -x XDG_CONFIG_DIRS="/etc/xdg" declare -x XDG_CURRENT_DESKTOP="XFCE" declare -x XDG_DATA_DIRS="/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm/data/claude" declare -x XDG_MENU_PREFIX="xfce-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_CLASS="user" declare -x XDG_SESSION_DESKTOP="xfce" declare -x XDG_SESSION_ID="2" declare -x XDG_SESSION_PATH="/org/freedesktop/Display
Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)
Hi Claude, the Debian kernel is compiled with GCC: https://buildd.debian.org/status/fetch.php?pkg=linux=amd64=6.1.27-1=1683630698=0 and compiles just fine. To compile the kernel with llvm you either need to set CC or LLVM variables: https://www.kernel.org/doc/html/latest/kbuild/llvm.html Can you send the output of `export` to check what is set in your environment? Given that you don't use the default compiler and that the default toolchain is provided by the build-essential package, I don't think this is a dependency issue and I would close this bug. Cheers Jochen * Claude Heiland-Allen [2023-05-11 12:57]: Package: linux-image-6.1.0-8-amd64-unsigned Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: cla...@mathr.co.uk Dear Maintainer, * What led up to the situation? I wanted to patch the kernel source to see if it would help an issue I was having, so I followed my usual steps when changing a Debian package locally: sudo apt build-dep linux-image-6.1.0-8-amd64-unsigned mkdir linux cd linux apt source linux-image-6.1.0-8-amd64-unsigned cd linux-6.1.25 # make changes to the source code # specfically some warning prints in devices/usb/host/xhci-ring.c debuild -i -us -uc -b * What was the outcome of this action? The build failed after some time with: ... llvm-strip -g /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/profiler.bpf.o make[4]: llvm-strip: No such file or directory make[4]: *** [Makefile:187: /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/profiler.bpf.o] Error 127 make[4]: *** Waiting for unfinished jobs llvm-strip -g /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/pid_iter.bpf.o make[4]: llvm-strip: No such file or directory make[4]: *** [Makefile:187: /home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool/pid_iter.bpf.o] Error 127 make[4]: Leaving directory '/home/claude/linux/linux-6.1.25/tools/bpf/bpftool' make[3]: *** [/home/claude/linux/linux-6.1.25/debian/rules.d/tools/bpf/bpftool/Makefile:15: all] Error 2 make[3]: Leaving directory '/home/claude/linux/linux-6.1.25/debian/build/build-tools/tools/bpf/bpftool' make[2]: *** [debian/rules.real:538: build_bpftool] Error 2 make[2]: Leaving directory '/home/claude/linux/linux-6.1.25' make[1]: *** [debian/rules.gen:1494: build-arch_amd64_real_bpftool] Error 2 make[1]: Leaving directory '/home/claude/linux/linux-6.1.25' make: *** [debian/rules:39: build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -i -b failed * What outcome did you expect instead? I expected apt to have fetched all the build-time dependencies of the package, and the build to have succeeded. * What exactly did you do (or not do) that was effective (or ineffective)? After sudo apt install llvm then debuild -i -us -uc -b worked as expected. Thanks for your work on this package, Claude -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-8-amd64-unsigned depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-8-amd64-unsigned recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-8-amd64-unsigned suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-12 pn linux-doc-6.1 signature.asc Description: PGP signature
Bug#1034694: closing 1034694
close 1034694 thanks
Bug#1034694: gnome-core: Cannot install due to pipewire-audio dependency
Thanks for the additional information. To my understanding pipewire-alsa and pipewire-audio are put on hold on your system, not allowing it's installation. You can verify that with: apt-mark showhold But the latest gnome-core depends on pipewire-audio so apt can't find a solution. You can reset the state with: sudo apt-mark unhold pipewire-alsa pipewire-audio I can imagine apt printing a more helpful error message there but not sure what to do otherwise. I would close the bug if you agree. Cheers Jochen * Witold Baryluk [2023-05-09 21:14]: Package: gnome-core Version: 1:43+1 Followup-For: Bug #1034694 X-Debbugs-Cc: witold.bary...@gmail.com Hi Jochen. In attachment you should find debug output of apt (stdout + stderr), as well as a dpkg status file. If you want to reproduce the problem, I have a live-build iso image you can boot in qemu. wget -c http://185.108.112.63/smooth/smooth-amd64_20230421T002521Z.iso # 4.0GB sha256sums: cf8818a8989489c0314ee9cddc0650c3d33c0442fa8eb1d103879063ea41c02d smooth-amd64_20230421T002521Z.iso Run in qemu: qemu-system-x86_64 -enable-kvm -M q35 -smp 8 -m 8192 -cdrom smooth-amd64_20230421T002521Z.iso Once loaded into MATE, in terminal emulator: sudo apt update # optionally dist-upgrade sudo apt install gnome-core Hope that helps. Thanks! Witold signature.asc Description: PGP signature
Bug#1034694: gnome-core: Cannot install due to pipewire-audio dependency
Hi Witold, The friendly people in #debian-apt proposed to run: sudo apt install -o Debug::pkgProblemResolver=true -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 gnome-core And could you also send your /var/lib/dpkg/status file? More information on this: https://salsa.debian.org/apt-team/apt#debugging Thanks! Jochen * Witold Baryluk [2023-05-08 19:02]: Package: gnome-core Version: 1:43+1 Followup-For: Bug #1034694 X-Debbugs-Cc: witold.bary...@gmail.com Here: root@debian:~# sudo apt -V --simulate remove pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: bind9-host (1:9.18.12-1) bind9-libs (1:9.18.12-1) libfstrm0 (0.6.1-1) libjemalloc2 (5.3.0-1) libmaxminddb0 (1.7.1-1) libprotobuf-c1 (1.4.1-1+b1) libuv1 (1.44.2-1) Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: liblua5.3-0 (5.3.6-2) libpipewire-0.3-modules (0.3.65-3) libwireplumber-0.4-0 (0.4.13-1) pipewire (0.3.65-3) pipewire-bin (0.3.65-3) pipewire-pulse (0.3.65-3) wireplumber (0.4.13-1) Suggested packages: libspa-0.2-bluetooth (0.3.65-3) wireplumber-doc (0.4.13-1) The following packages will be REMOVED: libcanberra-pulse (0.30-10) pulseaudio (16.1+dfsg1-2+b1) The following NEW packages will be installed: liblua5.3-0 (5.3.6-2) libpipewire-0.3-modules (0.3.65-3) libwireplumber-0.4-0 (0.4.13-1) pipewire (0.3.65-3) pipewire-bin (0.3.65-3) pipewire-pulse (0.3.65-3) wireplumber (0.4.13-1) 0 upgraded, 7 newly installed, 2 to remove and 0 not upgraded. Remv libcanberra-pulse [0.30-10] Remv pulseaudio [16.1+dfsg1-2+b1] Inst liblua5.3-0 (5.3.6-2 Debian:testing [amd64]) Inst libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64]) Inst libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64]) Inst pipewire-bin (0.3.65-3 Debian:testing [amd64]) Inst pipewire (0.3.65-3 Debian:testing [amd64]) Inst pipewire-pulse (0.3.65-3 Debian:testing [amd64]) Inst wireplumber (0.4.13-1 Debian:testing [amd64]) Conf liblua5.3-0 (5.3.6-2 Debian:testing [amd64]) Conf libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64]) Conf libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64]) Conf pipewire-bin (0.3.65-3 Debian:testing [amd64]) Conf pipewire (0.3.65-3 Debian:testing [amd64]) Conf pipewire-pulse (0.3.65-3 Debian:testing [amd64]) Conf wireplumber (0.4.13-1 Debian:testing [amd64]) root@debian:~# Regards, Witold signature.asc Description: PGP signature
Bug#1033701: closing 1033701
close 1033701 thanks Fixed with a rebuild as discussed in #1034691.
Bug#1034694: gnome-core: Cannot install due to pipewire-audio dependency
Hi Witold, can you please send the output of: sudo apt -o Debug::pkgProblemResolver=yes install gnome-core pipewire-audio should replace all of pulseaudio but there is probably a missing relation. Cheers Jochen * Witold Baryluk [2023-04-21 20:42]: Package: gnome-core Severity: grave Justification: renders package unusable X-Debbugs-Cc: witold.bary...@gmail.com Dear Maintainer, root@debian:~# sudo apt install gnome-core -V Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gnome-core : Depends: pipewire-audio but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@debian:~# -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 'bookworm'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-rc7 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-core depends on: ii adwaita-icon-theme 43-1 ii at-spi2-core2.46.0-5 pn baobab pn dconf-cli ii dconf-gsettings-backend 0.40.0-4 pn eog pn evince pn evolution-data-server ii fonts-cantarell 0.303.1-1 pn gdm3 pn gkbd-capplet ii glib-networking 2.74.0-4 pn gnome-backgrounds pn gnome-bluetooth-sendto pn gnome-calculator pn gnome-characters pn gnome-contacts pn gnome-control-center pn gnome-disk-utility pn gnome-font-viewer ii gnome-keyring 42.1-1+b2 pn gnome-logs pn gnome-menus pn gnome-online-accounts pn gnome-session pn gnome-settings-daemon pn gnome-shell pn gnome-shell-extensions pn gnome-software pn gnome-sushi pn gnome-system-monitor pn gnome-terminal | gnome-console pn gnome-text-editor ii gnome-themes-extra 3.28-2 pn gnome-user-docs pn gnome-user-share ii gsettings-desktop-schemas 43.0-1 pn gstreamer1.0-packagekit ii gstreamer1.0-plugins-base 1.22.0-3 ii gstreamer1.0-plugins-good 1.22.0-5 ii gvfs-backends 1.50.3-1 ii gvfs-fuse 1.50.3-1 ii libatk-adaptor 2.46.0-5 ii libcanberra-pulse 0.30-10 ii libglib2.0-bin 2.74.6-2 ii libpam-gnome-keyring42.1-1+b2 pn libproxy1-plugin-gsettings pn libproxy1-plugin-webkit ii librsvg2-common 2.54.5+dfsg-1 pn nautilus pn pipewire-audio ii sound-theme-freedesktop 0.8-2 pn system-config-printer-common pn system-config-printer-udev pn totem pn tracker pn xdg-desktop-portal-gnome ii yelp42.2-1 ii zenity 3.44.0-1 Versions of packages gnome-core recommends: ii firefox-esr [gnome-www-browser] 102.10.0esr-1 pn libproxy1-plugin-networkmanager pn low-memory-monitor ii network-manager-gnome1.30.0-2 Versions of packages gnome-core suggests: pn gnome signature.asc Description: PGP signature
Bug#1034233: closing 1034233
close 1034233 1.5.0-2 thanks
Bug#1034629: pdf-presenter-console: pdfpc terminates with symbol lookup error
* Robert Jäschke [2023-04-22 13:56]: libvmaf.so.1 => /lib/x86_64-linux-gnu/libvmaf.so.1 (0x7fa6dc39a000) I don't have this in my ldd output and I don't find the file in Debian. Can you try moving it away and see if it helps? Cheers Jochen signature.asc Description: PGP signature
Bug#1034629: pdf-presenter-console: pdfpc terminates with symbol lookup error
Hi Robert, I was not able to reproduce this in an up to date testing VM. Steps I tried: $ debvm-create --size=10G -r testing -- --include=task-gnome-desktop --aptopt='Apt::Install-Recommends "true"' --include=linux-image-amd64 --hook-dir=/usr/share/mmdebstrap/hooks/useradd $ debvm-run -g -- -m 4G in the running VM: $ sudo apt install pdf-presenter-console $ wget https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial $ pdfpc packaging-tutorial Can you check that your system is fine by running: $ sudo dpkg --verify Also send the output of $ ldd /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 In case there is an old library somewhere in the path. Cheers Jochen * Robert Jäschke [2023-04-20 09:57]: Package: pdf-presenter-console Version: 4.6.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: jaesc...@l3s.de Dear Maintainer, When starting pdfpc it immediately dies with the following error message: pdfpc slides.pdf pdfpc: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gst_transcoder_get_sync_signal_adapter -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pdf-presenter-console depends on: ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgee-0.8-20.20.6-1 ii libglib2.0-02.74.6-2 ii libgstreamer-plugins-base1.0-0 1.22.0-3 ii libgstreamer1.0-0 1.22.0-2 ii libgtk-3-0 3.24.37-2 ii libjson-glib-1.0-0 1.6.6-1 ii libmarkdown22.2.7-2 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii libpoppler-glib822.12.0-2+b1 ii libqrencode44.1.1-1 ii libsoup2.4-12.74.3-1 ii libwebkit2gtk-4.0-372.40.0-3 ii libx11-62:1.8.4-2 Versions of packages pdf-presenter-console recommends: ii gstreamer1.0-gtk3 1.22.0-5 pdf-presenter-console suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1032914: phog: ships /etc/pam.d/greetd
Hi, I've filled #1034595 to get phog unblocked as well. (also this hopefully delays the autoremoval of phog). Cheers Jochen * Marc Dequènes [2023-04-07 19:45]: Quack Arnaud, greetd was unblocked today. Thanks for your help :-). \_o< -- Marc Dequènes signature.asc Description: PGP signature
Bug#1027439: elementpath breaks python-xmlschema autopkgtest: 'XMLSchemaContext' object has no attribute 'iter'
Hi Emmanuel, note that the new upstream version of python-xmlschema fixes this and other errors but Debian unstable is frozen and the change would be too big. On the other hand this currently keeps the new upstream version of elementpath from transition to testing which is a viable outcome at the current release state as well. So there is not really something to do for this bug till the release of bookworm and afterwards an upload of the new upstream version should fix it. Cheers Jochen * Emmanuel Arias [2023-03-27 07:35]: Hello, Applying the patch all the tests are fixed except one: == FAIL: test_xml_document_validation (xmlschema.testing._builders.TestValidator004.test_xml_document_validation) -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py", line 623, in test_xml_document_validation self.check_data_conversion_with_lxml() File "/<>/.pybuild/cpython3_3.11_xmlschema/build/xmlschema/testing/_builders.py", line 507, in check_data_conversion_with_lxml self.assertEqual(len(lxml_errors), len(self.errors), msg=xml_file) AssertionError: 2 != 1 : tests/test_cases/examples/collection/collection3bis.xml - I will investigate a little bit today. Cheers, eamanu signature.asc Description: PGP signature
Bug#1033421: newt: nopython not full respected
Control: severity -1 normal Failing to cross build is not release critical, updating the severity accordingly. Hi, * henrynmail-deb...@yahoo.com [2023-03-24 19:08]: the build option "nopython" was not respected in all cases. In rules exist a check for nopython in DEB_BUILD_PROFILES, but later in Makefile.in it will overritten by setting PYTHONVERS again. If libpython*-dev is not installed, the build breaks with Python.h: No such file or directory The fail was detected by cross builing, but also exist in native builds. # apt remove python3-all libpython3.11-dev libpython3.11-dbg python3-minimal # dpkg-buildpackage -B "-Pnocheck noinsttest noudeb nopython" -uc -us ... /bin/sh: 1: python3.11-config: not found /bin/sh: 1: python3.11-config: not found /bin/sh: 1: python3.11-config: not found /bin/sh: 1: python3.11-config: not found gcc -fPIC -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl8.6 -g -O2 -ffile-prefix-map=/tmp/newt/newt-0.52.23=. -fstack-protector-strong -Wformat -Werror=format-security -DMARCH="x86_64-linux-gnu" -fPIC -c -o python3.11/snack.o snack.c snack.c:2:10: fatal error: Python.h: No such file or directory 2 | #include "Python.h" | ^~ compilation terminated. This is actually interesting as the build continues despite the error (which maybe RC itself). An easy way to reproduce is: sbuild --no-arch-all --profiles=nocheck,noinsttest,noudeb,nopython -d unstable newt --host=arm64 --build amd64 Cheers Jochen signature.asc Description: PGP signature
Bug#1030496: fop: FTBFS: [javadoc] /<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29: error: package javax.servlet does not exist
Hi Lucas, I was not able to reproduce this and RB seems to be fine as well: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fop.html Note that the error in your log seems to have been: E: Build killed with signal TERM after 150 minutes of inactivity Can you try this again? Thanks! Jochen * Lucas Nussbaum [2023-02-04 08:56]: Source: fop Version: 1:2.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230203 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.apache.fop.configuration.DefaultConfigurationTestCase [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.131 s - in org.apache.fop.configuration.DefaultConfigurationTestCase [INFO] Running org.apache.fop.HyphenationTestCase [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.162 s - in org.apache.fop.HyphenationTestCase [INFO] Running org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.073 s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerTestCase [INFO] Running org.apache.fop.layoutmgr.BreakElementTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.apache.fop.layoutmgr.BreakElementTestCase [INFO] Running org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 s - in org.apache.fop.layoutmgr.table.TableContentLayoutManagerTestCase [INFO] Running org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.373 s - in org.apache.fop.layoutmgr.table.TableCellLayoutManagerTestCase [INFO] Running org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.139 s - in org.apache.fop.layoutmgr.table.TableLayoutManagerTestCase [INFO] Running org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.322 s - in org.apache.fop.layoutmgr.PageSequenceLayoutManagerTestCase [INFO] Running org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 s - in org.apache.fop.layoutmgr.RetrieveTableMarkerLayoutManagerMakerTestCase [INFO] Running org.apache.fop.intermediate.IFMimickingTestCase [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.304 s - in org.apache.fop.intermediate.IFMimickingTestCase [INFO] Running org.apache.fop.intermediate.AreaTreeParserTestCase [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.284 s - in org.apache.fop.intermediate.AreaTreeParserTestCase [INFO] Running org.apache.fop.intermediate.IFTestCase [ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.351 s <<< FAILURE! - in org.apache.fop.intermediate.IFTestCase [ERROR] runTest[3](org.apache.fop.intermediate.IFTestCase) Time elapsed: 0.015 s <<< FAILURE! java.lang.AssertionError: Expected XPath expression to evaluate to 'true', but got '' (XPath: /descendant::if:text[1]/@hyphenated) at org.apache.fop.intermediate.IFTestCase.runTest(IFTestCase.java:103) [INFO] Running org.apache.fop.intermediate.IFParserTestCase [INFO] Tests run: 695, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.409 s - in org.apache.fop.intermediate.IFParserTestCase [INFO] Running org.apache.fop.pdf.PDFAttachmentTestCase [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 s - in org.apache.fop.pdf.PDFAttachmentTestCase [INFO] Running org.apache.fop.pdf.PDFReferenceTestCase [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.apache.fop.pdf.PDFReferenceTestCase [INFO] Running org.apache.fop.pdf.PDFNumberTestCase [INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in org.apache.fop.pdf.PDFNumberTestCase [INFO] Running org.apache.fop.pdf.PDFPageLabelsTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.041 s - in org.apache.fop.pdf.PDFPageLabelsTestCase [INFO] Running org.apache.fop.pdf.PDFImageXObjectTestCase [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.118 s - in org.apache.fop.pdf.PDFImageXObjectTestCase [INFO] Running org.apache.fop.pdf.PDFPagePieceTestCase [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 s - in org.apache.fop.pdf.PDFPagePieceTestCase [INFO] Running org.apache.fop.pdf.ObjectStreamTestCase [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped:
Bug#1027649: marked as pending in aspectj
Control: tag -1 pending Hello, Bug #1027649 in aspectj 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/java-team/aspectj/-/commit/a3a0dd2b76911a59f5df3418203ae50877ae277f Add missing bootstrap dependency Closes: #1027649 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027649
Bug#1028727: marked as pending in maven-debian-helper
Control: tag -1 pending Hello, Bug #1028727 in maven-debian-helper 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/java-team/maven-debian-helper/-/commit/2c8f72ba0c315583469e451472b486fec490c5a1 Add missing build dependency Closes: #1028727 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028727
Bug#1012108: marked as pending in spymemcached
Control: tag -1 pending Hello, Bug #1012108 in spymemcached 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/java-team/spymemcached/-/commit/a41be7e450bc4bd4023a94738caecf94b2d9ea6c Add patch to fix FTBFS Closes: #1012108 (this message was generated automatically) -- Greetings https://bugs.debian.org/1012108
Bug#1031880: unattended-upgrades: requires on_ac_power from package powermgmt-base to function at all
Hi Steve,
* Steve Lane [2023-02-24 09:23]:
Currently unattended-upgrades marks the powermgmt-base package
as Suggested. powermgmt-base provides the /sbin/on_ac_power and
/usr/sbin/on_ac_power script(s), which unattended-upgrades requires to
function at all, because of this check in /usr/bin/unattended-upgrade
at line 676:
if apt_pkg.config.find_b("Unattended-Upgrade::OnlyOnACPower", True) \
and subprocess.call("on_ac_power") == 1:
The absence of the powermgmt-base package, and thus the on_ac_power
script, results in the following error:
root# /usr/bin/unattended-upgrade
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2522, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1993, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2061, in run
if should_stop():
File "/usr/bin/unattended-upgrade", line 676, in should_stop
and subprocess.call("on_ac_power") == 1:
File "/usr/lib/python3.9/subprocess.py", line 349, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.9/subprocess.py", line 1823, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: 'on_ac_power'
I can't reproduce this error on a fresh stable nor unstable VM without
powermgmt-base installed.
(Note that it's not clear to me why this is a PermissionError, since
the script doesn't actually exist, but that is a secondary point.)
But this makes it reproducible:
touch /usr/bin/on_ac_power
So I guess you have a non executable on_ac_power in your $PATH.
The powermgmt-base package needs to be installed in order for
unattended-upgrades to function at all. Thus, the powermgmt-base package
needs to be marked as Depends for unattended-upgrades.
I disagree and propose this patch instead:
https://github.com/mvo5/unattended-upgrades/pull/341
Cheers Jochen
signature.asc
Description: PGP signature
Bug#1029439: feynmf: FTBFS in bookworm (I can't open file `fmfsamp4')
Hi Hilmar,
* Hilmar Preuße [2023-02-24 00:12]:
On 2/23/23 14:28, James Addison wrote:
On Thu, 23 Feb 2023 at 12:53, James Addison wrote:
Hi,
pass: texlive-base (2022.20220605-1) unstable; urgency=low
fail: texlive-base (2022.20220923-2) unstable; urgency=medium
It should be possible to look at the differences between those (and
maybe the related packages such as texlive-latex-base) to find further
clues. I'm going to start on that fairly soon.
Ok, it turns out that the problem was a compatibility-break between v2
and v3 of the base doc.sty file. Fortunately the texlive-latex-base
package ships the previous (v2, feynmf-compatible) version of that
file along with v3.
This seems to be just a temporary solution, as the TL upstream people,
will stop providing the old doc.sty at any time in the future. You may
lower the severity, but not close the issue.
Fair point, attached is an alternative patch that works with the current
doc package version.
Cheers Jochen
From bd81a1b231c57cd10d1b26026ace00ebec714e85 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Fri, 24 Feb 2023 10:44:44 +0100
Subject: [PATCH] Set nohyperref to fix FTBFS
Closes: #1029439
---
.../0003-Set-nohyperref-for-doc-package.patch | 21 +++
debian/patches/series | 1 +
2 files changed, 22 insertions(+)
create mode 100644 debian/patches/0003-Set-nohyperref-for-doc-package.patch
diff --git a/debian/patches/0003-Set-nohyperref-for-doc-package.patch b/debian/patches/0003-Set-nohyperref-for-doc-package.patch
new file mode 100644
index 000..6be4acf
--- /dev/null
+++ b/debian/patches/0003-Set-nohyperref-for-doc-package.patch
@@ -0,0 +1,21 @@
+From: Jochen Sprickerhof
+Date: Fri, 24 Feb 2023 10:41:54 +0100
+Subject: Set nohyperref for doc package
+
+Closes: #1029439
+---
+ feynmf.dtx | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/feynmf.dtx b/feynmf.dtx
+index 4ed5c70..78bd8df 100644
+--- a/feynmf.dtx
b/feynmf.dtx
+@@ -7696,6 +7696,7 @@ endinput;
+ %<*!209>
+ \documentclass[a4paper]{article}
+ \usepackage{doc}
++\SetupDoc{nohyperref}
+ \usepackage[T1]{fontenc}
+ %\end{macrocode}
+ % The \MF{} and \MP{} logos come out much nicer if you have |mflogo|
diff --git a/debian/patches/series b/debian/patches/series
index c6bf829..64622c8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
reproducible-build.patch
docu.patch
+0003-Set-nohyperref-for-doc-package.patch
--
2.39.2
signature.asc
Description: PGP signature
Bug#1029439: help fixing this bug
Hi Thorsten,
/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty changed in
texlive-latex-base_2022.20220722-1. But it also ships doc-2021-06-01.sty
so the attached patch fixes the FTBFS.
Cheers Jochen
* Thorsten Alteholz [2023-02-14 09:28]:
In case somebody has any idea how to fix this bug, I would be happy to
apply a patch.
Thorsten
From d99bbd41e95a27849e611b11dee7688568dfc70c Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Thu, 23 Feb 2023 13:53:42 +0100
Subject: [PATCH] Add patch for build failure
Closes: #1029439
---
debian/patches/0003-Use-old-doc-package.patch | 22 +++
debian/patches/series | 1 +
2 files changed, 23 insertions(+)
create mode 100644 debian/patches/0003-Use-old-doc-package.patch
diff --git a/debian/patches/0003-Use-old-doc-package.patch b/debian/patches/0003-Use-old-doc-package.patch
new file mode 100644
index 000..87b12c4
--- /dev/null
+++ b/debian/patches/0003-Use-old-doc-package.patch
@@ -0,0 +1,22 @@
+From: Jochen Sprickerhof
+Date: Thu, 23 Feb 2023 13:53:01 +0100
+Subject: Use old doc package
+
+Closes: #1029439
+---
+ feynmf.dtx | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/feynmf.dtx b/feynmf.dtx
+index 4ed5c70..890579f 100644
+--- a/feynmf.dtx
b/feynmf.dtx
+@@ -7695,7 +7695,7 @@ endinput;
+ %<*driver>
+ %<*!209>
+ \documentclass[a4paper]{article}
+-\usepackage{doc}
++\usepackage{doc-2021-06-01}
+ \usepackage[T1]{fontenc}
+ %\end{macrocode}
+ % The \MF{} and \MP{} logos come out much nicer if you have |mflogo|
diff --git a/debian/patches/series b/debian/patches/series
index c6bf829..e3220cd 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
reproducible-build.patch
docu.patch
+0003-Use-old-doc-package.patch
--
2.39.2
signature.asc
Description: PGP signature
Bug#1031606: Bug#1031578: lightproof: FTBFS in testing: make[1]: *** [debian/rules:38: override_dh_auto_install] Error 1
</pre><tt>/home/rene/lightproof-1.6/make.py:39: DeprecationWarning: The
</tt><tt>SafeConfigParser class has been renamed to ConfigParser in Python
</tt><tt>3.2. This alias will be removed in Python 3.12. Use ConfigParser
</tt><tt>directly instead.
</tt><pre style="margin: 0em;">
fArgs = cp.SafeConfigParser()
Traceback (most recent call last):
</pre><tt> File "/home/rene/lightproof-1.6/pythonpath/lightproof_compile___implname__.py",
</tt><tt>line 170, in mysplit
</tt><pre style="margin: 0em;">
compr = re.compile(sc)
^^
File "/usr/lib/python3.11/re/__init__.py", line 227, in compile
return _compile(pattern, flags)
File "/usr/lib/python3.11/re/__init__.py", line 294, in _compile
p = _compiler.compile(pattern, flags)
^
File "/usr/lib/python3.11/re/_compiler.py", line 743, in compile
p = _parser.parse(p, flags)
^^^
File "/usr/lib/python3.11/re/_parser.py", line 980, in parse
p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
^^
File "/usr/lib/python3.11/re/_parser.py", line 455, in _parse_sub
itemsappend(_parse(source, state, verbose, nested + 1,
^^
File "/usr/lib/python3.11/re/_parser.py", line 841, in _parse
raise source.error('global flags not at the start '
re.error: global flags not at the start of the expression at position 28
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/rene/lightproof-1.6/make.py", line 43, in <module>
dist(i[:-4], fArgs._sections['args'])
File "/home/rene/lightproof-1.6/make.py", line 15, in dist
</pre><tt> code = pythonpath.lightproof_compile___implname__.c(f.read(),
</tt><tt>a['lang'])
</tt><pre style="margin: 0em;">
^
</pre><tt> File "/home/rene/lightproof-1.6/pythonpath/lightproof_compile___implname__.py",
</tt><tt>line 270, in c
</tt><pre style="margin: 0em;">
item = mysplit(lines[i].strip(), i + 1, oldlinenums[lines[i]], debug)
^^
</pre><tt> File "/home/rene/lightproof-1.6/pythonpath/lightproof_compile___implname__.py",
</tt><tt>line 174, in mysplit
</tt><pre style="margin: 0em;">
raise Exception(str(e), oldline)
</pre><tt>Exception: ('global flags not at the start of the expression at
</tt><tt>position 28', 75)
</tt><pre style="margin: 0em;">
missing config file or options: src/ru_RU/ru_RU.cfg
</pre><tt>/home/rene/lightproof-1.6/make.py:39: DeprecationWarning: The
</tt><tt>SafeConfigParser class has been renamed to ConfigParser in Python
</tt><tt>3.2. This alias will be removed in Python 3.12. Use ConfigParser
</tt><tt>directly instead.
</tt><pre style="margin: 0em;">
fArgs = cp.SafeConfigParser()
</pre></blockquote><pre style="margin: 0em;">
</pre><tt>Making a new bug out of this since the actual original bug is not
</tt><tt>reproducible.
</tt><pre style="margin: 0em;">
Regards,
Rene
</pre></blockquote><pre>From: Jochen Sprickerhof <jspri...@debian.org>
Date: Sun, 19 Feb 2023 11:06:50 +0100
X-Dgit-Generated: 1.6-2 f7281d3d6950e5e9edf187fee6e3d8a89187c7d2
Subject: Move ignore case flag to the start of the regex
Fixes:
re.error: global flags not at the start of the expression at position 28
---
diff --git a/pythonpath/lightproof_compile___implname__.py b/pythonpath/lightproof_compile___implname__.py
index c56c928..d13b1bf 100644
--- a/pythonpath/lightproof_compile___implname__.py
+++ b/pythonpath/lightproof_compile___implname__.py
@@ -103,11 +103,17 @@ def mysplit(s, line, oldline, debug):
for i in repl:
s1 = re.sub("[{]" + i + "}", repl[i], s1)
# modes
+ignore_case = False
+if s1.startswith("(?i)"):
+ignore_case = True
+s1 = s1[4:]
if mode == "[Word]" or mode == "[word]":
if s1[0] == '^':
s1 = r"((?<=[!?.] )|^)" + s1[1:] + r"(?![-\w\u2013\u00AD])"
else:
s1 = r"(?<![-\w\u2013.,\u00AD])" + s1 + r"(?![-\w\u2013\u00AD])"
+if ignore_case:
+s1 = "(?i)" + s1
# modes with casing ([Word] or [Char])
if mode == "[Word]" or mode == "[Char]":
s1 = "(?i)" + s1
</pre>
<p><strong><a href="msg645057/signature.asc" ><img src="../attachment.gif" align="left" border=0 alt="Attachment:"></a>
<a href="msg645057/signature.asc" ><tt>signature.asc</tt></a></strong><br>
<em>Description:</em> PGP signature</p>
Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12
Hi Hans, * Hans-Christoph Steiner [2023-02-13 09:17]: Roger, it is great to see your progress on android-platform-tools. Are you thinking of trying to get it into bookworm? If so, let me know how I can help. It would be really valuable to have there, but I don't know how much work it'll be. ähm, soft freeze started yesterday so no new upstream versions, please: https://release.debian.org/testing/freeze_policy.html#soft Cheers Jochen signature.asc Description: PGP signature
Bug#1030431: marked as pending in sphinxcontrib-autoprogram
Control: tag -1 pending Hello, Bug #1030431 in sphinxcontrib-autoprogram 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/sphinxcontrib-autoprogram/-/commit/43dc5ca4cacd9508220f320cdbf1f3aa06004f61 Mock state_machine in AutoprogramDirectiveTestCase Closes: #1030431 (this message was generated automatically) -- Greetings https://bugs.debian.org/1030431
Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12
* Roger Shimizu [2023-02-09 13:42]:
Please try the version in experimental.
and also refer the version info of this ticket:
Found in versions android-platform-frameworks-base/1:10.0.0+r36-5,
android-platform-frameworks-base/13~beta3-1~exp1
Fixed in version android-platform-frameworks-base/1:10.0.0+r36-6
Oups, sorry. The attached patch against android-platform-tools fixes the
issue for me.
Cheers Jochen
From: Jochen Sprickerhof
Date: Fri, 10 Feb 2023 11:46:23 +0100
Subject: Implement const_iterator::operator--
Needed for
android-platform-frameworks-base/libs/androidfw/LoadedArsc.cpp
when compiling against libstdc++.
---
.../incremental_delivery/incfs/util/include/util/map_ptr.h | 12
1 file changed, 12 insertions(+)
diff --git a/system/incremental_delivery/incfs/util/include/util/map_ptr.h b/system/incremental_delivery/incfs/util/include/util/map_ptr.h
index 304540f..836b320 100644
--- a/system/incremental_delivery/incfs/util/include/util/map_ptr.h
+++ b/system/incremental_delivery/incfs/util/include/util/map_ptr.h
@@ -180,6 +180,11 @@ public:
return *this;
}
+const const_iterator& operator--() {
+safe_ptr_--;
+return *this;
+}
+
const_iterator& operator+=(int n) {
safe_ptr_ = safe_ptr_ + n;
return *this;
@@ -321,6 +326,13 @@ public:
return temp;
}
+template = 0>
+const map_ptr& operator--() {
+LIBINCFS_MAP_PTR_DEBUG_CODE(verified_ = false);
+--ptr_;
+return *this;
+}
+
template = 0>
map_ptr operator+(const S n) const {
return map_ptr(map_, ptr_ + n, verified_block_);
signature.asc
Description: PGP signature
Bug#1030920: marked as pending in ipyparallel
Control: tag -1 pending Hello, Bug #1030920 in ipyparallel 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/ipyparallel/-/commit/ec63d0ee7a43d84615802c76816519f52482e36e Drop python-distributed-doc (build) dependency Closes: #1030920 (this message was generated automatically) -- Greetings https://bugs.debian.org/1030920
Bug#1012890: android-platform-frameworks-base: ftbfs with GCC-12
Hi Roger, * Roger Shimizu [2023-02-04 10:47]: On Sat, Feb 4, 2023 at 12:09 AM Roger Shimizu wrote: control: reopen -1 Yes, it ftbfs on sid now. And I tried latest upstream 13.0.0_r24, result is the same. Have to fix this issue before we can migrate to sid. Error log is not originally reported, for latest error log please refer to: - https://bugs.debian.org/1012890#17 I guess the issue is caused due to upstream using clang stdc++ lib, but we're using gcc/g++ one. Those two have slight differences. I can't reproduce this. The unstable version (1:10.0.0+r36-10) builds fine in sbuild and also reproducible builds shows no ftbfs: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/i386/android-platform-frameworks-base.html What exactly did you test? Cheers Jochen signature.asc Description: PGP signature
Bug#1027965: Fix for the RC bug in vtk
Hi Steven, * Steven Robbins [2023-02-05 10:26]: Was looking yesterday for an RC bug to fix and noticed #1027965 against VTK -- a build failure in gdcm caused by missing dependency. The fix proposed by Mathieu seems reasonable to me. I assume you mean the proposal to add a libvtk9-qt-dev dependency to libvtk9-dev? Note that libvtk9-dev already has a dependency to libvtk9-qt-dev resulting in a cyclic dependency between both. Those are known to not work well in Debian and should be avoided. The underlying problem here is that the vtk9 cmake files are not separated between libvtk9-dev and libvtk9-qt-dev so the split seems artificial to Debian and both packages should probably be merged into one or the cmake files need rewriting. Cheers Jochen signature.asc Description: PGP signature
Bug#1020973: closing 1020973
close 1020973 2.23.0 thanks
Bug#1030220: closing 1030220
close 1030220 thanks Fixed in 1.7.4-1+b3.
Bug#1030424: marked as pending in recommonmark
Control: tag -1 pending Hello, Bug #1030424 in recommonmark 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/recommonmark/-/commit/aea1ec3124e77cbf74b16c7b6d0f29f646f6c5fc Adopt test to new sphinx version Closes: #1030424 (this message was generated automatically) -- Greetings https://bugs.debian.org/1030424
Bug#1028894: marked as pending in python-stack-data
Control: tag -1 pending Hello, Bug #1028894 in python-stack-data 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-stack-data/-/commit/afb5148fafb151fccf77ba3174956cd9ab920006 Add patch for test failure with pygments 2.14 Closes: #1028894 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028894
Bug#1028619: marked as pending in rich
Control: tag -1 pending Hello, Bug #1028619 in rich 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/rich/-/commit/694a0d14de73e9a48f3f5da0f97a21720b3c7689 Add patch for pygments 2.14.0 Closes: #1028619 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028619
Bug#1028616: closing 1028616
close 1028616 2.7-5 thanks
Bug#1028620: ruby-pygments.rb: diff for NMU version 2.3.0+ds-2.2
Control: tags 1028620 + patch Dear maintainer, I've prepared an NMU for ruby-pygments.rb (versioned as 2.3.0+ds-2.2). The diff is attached to this message. Regards. diff -Nru ruby-pygments.rb-2.3.0+ds/debian/changelog ruby-pygments.rb-2.3.0+ds/debian/changelog --- ruby-pygments.rb-2.3.0+ds/debian/changelog 2022-03-13 12:31:00.0 +0100 +++ ruby-pygments.rb-2.3.0+ds/debian/changelog 2023-01-20 09:51:53.0 +0100 @@ -1,3 +1,10 @@ +ruby-pygments.rb (2.3.0+ds-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch for pygments 2.24 (Closes: #1028620) + + -- Jochen Sprickerhof Fri, 20 Jan 2023 09:51:53 +0100 + ruby-pygments.rb (2.3.0+ds-2.1) unstable; urgency=medium * Non-maintainer upload diff -Nru ruby-pygments.rb-2.3.0+ds/debian/patches/0016-Adopt-to-pygments-2.24.patch ruby-pygments.rb-2.3.0+ds/debian/patches/0016-Adopt-to-pygments-2.24.patch --- ruby-pygments.rb-2.3.0+ds/debian/patches/0016-Adopt-to-pygments-2.24.patch 1970-01-01 01:00:00.0 +0100 +++ ruby-pygments.rb-2.3.0+ds/debian/patches/0016-Adopt-to-pygments-2.24.patch 2023-01-20 09:49:57.0 +0100 @@ -0,0 +1,21 @@ +From: Jochen Sprickerhof +Date: Fri, 20 Jan 2023 09:04:03 +0100 +Subject: Adopt to pygments 2.24 + +--- + test/test_pygments.rb | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/test/test_pygments.rb b/test/test_pygments.rb +index b8c0292..25bd75f 100644 +--- a/test/test_pygments.rb b/test/test_pygments.rb +@@ -29,7 +29,7 @@ class PygmentsHighlightTest < Test::Unit::TestCase + code = P.highlight(RUBY_CODE) + assert_match '#!/usr/bin/ruby', code + assert_equal %(#!/usr/bin/ruby +-puts foo ++puts foo + ), code + end + diff -Nru ruby-pygments.rb-2.3.0+ds/debian/patches/series ruby-pygments.rb-2.3.0+ds/debian/patches/series --- ruby-pygments.rb-2.3.0+ds/debian/patches/series 2022-03-13 12:31:00.0 +0100 +++ ruby-pygments.rb-2.3.0+ds/debian/patches/series 2023-01-20 09:50:15.0 +0100 @@ -6,3 +6,4 @@ 0013-test-drop-test-that-depends-on-Python-internals.patch 0014-no-relative-path-to-mentos-py.patch test-update-for-latest-pygments.patch +0016-Adopt-to-pygments-2.24.patch signature.asc Description: PGP signature
Bug#1028617: marked as pending in ipython4
Control: tag -1 pending Hello, Bug #1028617 in ipython4 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/ipython/-/commit/2253653a27dfbdb7d998aea446fa39bf055c20de Add upstream patch for pygments > 2.14 Closes: #1028617 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028617
Bug#1026476: marked as pending in python-django
Control: tag -1 pending Hello, Bug #1026476 in python-django 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/-/commit/8a412be6bee1a89e400fc63ecc7cf685b2e89bd9 Make unit tests compatible with Python 3.11 to fix build errors Closes: #1026476 LP: #2002012 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026476
Bug#1028243: closing 1028243
close 1028243 thanks
Bug#1028243: dexdump: symbol lookup error: /.../libart.so.0: undefined symbol
Hi Philipp, * Philipp Marek [2023-01-08 20:46]: ii android-libart 11.0.0+r48-4 ii android-libbacktrace 1:33.0.1-1~exp9 ii android-libbase 1:33.0.1-1~exp9 ii android-liblog 1:33.0.1-1~exp9 ii android-libnativeloader 1:11.0.0+r48-4 ii android-libziparchive1:33.0.1-1~exp9 Seems like you are mixing unstable and experimental. Please try with the packages from unstable (version 1:29.0.6-21). Cheers Jochen signature.asc Description: PGP signature
Bug#1027593: closing 1027593
close 1027593 4.26-1 thanks
Bug#1027502: closing 1027502
close 1027502 4.26-1 thanks
Bug#1027507: closing 1027507
close 1027507 4.26-2 thanks
Bug#1027579: closing 1027579
close 1027579 4.26-1 thanks
Bug#1027577: closing 1027577
close 1027577 thanks
Bug#1016963: Please test u-boot for Mini-X
* Vagrant Cascadian [2023-01-05 12:29]: On 2023-01-04, Jochen Sprickerhof wrote: * Vagrant Cascadian [2022-12-28 16:56]: If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. Mini-X Works fine with unstable, I've updated the wiki page. Thanks! Any chance you could also test 2023.01-rc* from experimental? At this point 2023.01 is the version I am most likely to try to push to bookworm. 2023.01~rc4+dfsg-2 from unstable also works fine (updated the wiki page). Cheers Jochen signature.asc Description: PGP signature
Bug#1016963: Please test u-boot for Mini-X
Hi Vagrant, * Vagrant Cascadian [2022-12-28 16:56]: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. Mini-X Works fine with unstable, I've updated the wiki page. Cheers Jochen signature.asc Description: PGP signature
Bug#1027934: libflann-dev: pkg-config file now requires hdf5 but doesn't find it
Control: reassign -1 src:hugin 2022.0.0+dfsg
* Adrian Bunk [2023-01-04 22:02]:
https://buildd.debian.org/status/fetch.php?pkg=hugin=amd64=2022.0.0%2Bdfsg-1%2Bb2=1672840532=0
...
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security
-Wall -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs -fopenmp
CMakeFiles/cpfind.dir/PanoDetector.cpp.o CMakeFiles/cpfind.dir/PanoDetectorLogic.cpp.o CMakeFiles/cpfind.dir/TestCode.cpp.o
CMakeFiles/cpfind.dir/Utils.cpp.o CMakeFiles/cpfind.dir/main.cpp.o -o cpfind
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/src/hugin_cpfind/localfeatures:/<>/obj-x86_64-linux-gnu/src/celeste:/<>/obj-x86_64-linux-gnu/src/hugin_base:
../localfeatures/liblocalfeatures.so.0.0 /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so
/usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libtiff.so
/usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libz.so
/usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/libpano13.so ../../foreign/levmar/libhuginlevmar.a
/usr/lib/x86_64-linux-gnu/libGLEW.so /usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so
/usr/lib/x86_64-linux-gnu/libOpenEXR.so /usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so
/usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so
/usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so
../../celeste/libceleste.so.0.0 -lflann -lflann_cpp -lhdf5 -lmpi -llz4 ../../hugin_base/libhuginbase.so.0.0
/usr/lib/x86_64-linux-gnu/libX11.so /usr/lib/x86_64-linux-gnu/libOpenGL.so /usr/lib/x86_64-linux-gnu/libGLX.so
/usr/lib/x86_64-linux-gnu/libGLU.so /usr/lib/x86_64-linux-gnu/libsqlite3.so /usr/lib/x86_64-linux-gnu/libpano13.so
../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libfftw3.so /usr/lib/x86_64-linux-gnu/libvigraimpex.so /usr/lib/x86_64-linux-gnu/libOpenEXR.so
/usr/lib/x86_64-linux-gnu/libImath-3_1.so /usr/lib/x86_64-linux-gnu/libIex-3_1.so /usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so
/usr/lib/x86_64-linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so
/usr/bin/ld: cannot find -lhdf5: No such file or directory
collect2: error: ld returned 1 exit status
make[3]: *** [src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/build.make:221:
src/hugin_cpfind/cpfind/cpfind] Error 1
Relevant /usr/lib/x86_64-linux-gnu/pkgconfig/flann.pc diff:
│ │ │ -Version: 1.9.1
│ │ │ -Requires: liblz4
│ │ │ +Version: 1.9.2
│ │ │ +Requires: hdf5 liblz4
$ pkgconf --libs flann
-L/usr/lib/x86_64-linux-gnu\;-llz4 -lflann -lflann_cpp
-L/usr/lib/x86_64-linux-gnu/hdf5/openmpi -lhdf5
-L/usr/lib/x86_64-linux-gnu/openmpi/lib -lmpi -llz4
$ dpkg -S libhdf5.so
libhdf5-openmpi-dev: /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so
$
From the log above:
Unpacking libopenmpi-dev:amd64 (4.1.4-3) ...
The problem is that hugin ignores the FLANN_LIBRARY_DIRS. This patch
fixes it:
--- hugin-2022.0.0+dfsg/CMakeModules/FindFLANN.cmake2018-11-01
18:26:55.0 +0100
+++ hugin-2022.0.0+dfsg-1/CMakeModules/FindFLANN.cmake 2023-01-04
22:49:27.667327549 +0100
@@ -11,6 +11,7 @@
if(UNIX)
find_package(PkgConfig QUIET)
pkg_check_modules(FLANN flann)
+ link_directories(${FLANN_LIBRARY_DIRS})
else()
find_path(FLANN_INCLUDE_DIRS flann/flann.hpp)
Cheers Jochen
signature.asc
Description: PGP signature
Bug#999524: closing 999524
close 999524 thanks Package no longer in Debian.
Bug#1027603: closing 1027603
close 1027603 4.26-1 thanks
Bug#1027508: closing 1027508
close 1027508 4.26-1 thanks
Bug#1026575: closing 1026575
close 1026575 2.0.1-1 thanks
Bug#1027534: closing 1027534
close 1027534 4.26-1 thanks
Bug#1027460: marked as pending in python-scipy
Control: tag -1 pending Hello, Bug #1027460 in python-scipy 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/scipy/-/commit/3dc8326ef7210366ccb7164778aecfb8a4891c20 Add upstream patch to fix flapack This is actually a numpy-f2py bug tracked in: https://github.com/numpy/numpy/issues/20771 Closes: #1027460 (this message was generated automatically) -- Greetings https://bugs.debian.org/1027460
Bug#1026731: marked as pending in python-tblib
Control: tag -1 pending Hello, Bug #1026731 in python-tblib 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-tblib/-/commit/adae416029d06f0fb8bffa4c7136de72d0aa90d0 Ignore doctest in Python 3.11 Closes: #1026731 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026731
Bug#1004869: python-xarray: diff for team upload version 2022.12.0-2
Dear maintainer,
I've prepared an team upload for python-xarray (versioned as 2022.12.0-2) and
uploaded it. Can you please push the missing commits to Salsa so I can
push this patch?
Cheers Jochen
diff -Nru python-xarray-2022.12.0/debian/changelog python-xarray-2022.12.0/debian/changelog
--- python-xarray-2022.12.0/debian/changelog 2022-12-03 08:28:13.0 +0100
+++ python-xarray-2022.12.0/debian/changelog 2022-12-29 09:18:29.0 +0100
@@ -1,3 +1,13 @@
+python-xarray (2022.12.0-2) unstable; urgency=medium
+
+ * Team upload.
+ * Add patch to fix FTBFS on i386.
+Thanks to Adrian Bunk (Closes: 1004869)
+ * Use execute_after_ in d/rules
+ * Set R³ in d/control
+
+ -- Jochen Sprickerhof Thu, 29 Dec 2022 09:18:29 +0100
+
python-xarray (2022.12.0-1) unstable; urgency=medium
* New upstream release
diff -Nru python-xarray-2022.12.0/debian/control python-xarray-2022.12.0/debian/control
--- python-xarray-2022.12.0/debian/control 2022-12-03 08:28:13.0 +0100
+++ python-xarray-2022.12.0/debian/control 2022-12-29 09:18:29.0 +0100
@@ -49,6 +49,7 @@
Vcs-Browser: https://salsa.debian.org/science-team/python-xarray
Vcs-Git: https://salsa.debian.org/science-team/python-xarray.git
Homepage: http://xarray.pydata.org/
+Rules-Requires-Root: no
Package: python3-xarray
Architecture: all
diff -Nru python-xarray-2022.12.0/debian/patches/0015-Mark-failing-test-on-i386-as-xfail.patch python-xarray-2022.12.0/debian/patches/0015-Mark-failing-test-on-i386-as-xfail.patch
--- python-xarray-2022.12.0/debian/patches/0015-Mark-failing-test-on-i386-as-xfail.patch 1970-01-01 01:00:00.0 +0100
+++ python-xarray-2022.12.0/debian/patches/0015-Mark-failing-test-on-i386-as-xfail.patch 2022-12-29 09:16:44.0 +0100
@@ -0,0 +1,20 @@
+From: Adrian Bunk
+Date: Thu, 29 Dec 2022 09:05:39 +0100
+Subject: Mark failing test on i386 as xfail
+
+---
+ xarray/tests/test_interp.py | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/xarray/tests/test_interp.py b/xarray/tests/test_interp.py
+index b3c94e3..1dc8aff 100644
+--- a/xarray/tests/test_interp.py
b/xarray/tests/test_interp.py
+@@ -854,6 +854,7 @@ def test_interpolate_chunk_1d(
+ @requires_dask
+ @pytest.mark.parametrize("method", ["linear", "nearest"])
+ @pytest.mark.filterwarnings("ignore:Increasing number of chunks")
++@pytest.mark.xfail
+ def test_interpolate_chunk_advanced(method: InterpOptions) -> None:
+ """Interpolate nd array with an nd indexer sharing coordinates."""
+ # Create original array
diff -Nru python-xarray-2022.12.0/debian/patches/series python-xarray-2022.12.0/debian/patches/series
--- python-xarray-2022.12.0/debian/patches/series 2022-12-03 08:28:13.0 +0100
+++ python-xarray-2022.12.0/debian/patches/series 2022-12-29 09:16:55.0 +0100
@@ -12,3 +12,4 @@
xfail-pad-constant.patch
no-sphinx-design.patch
xfail-on-random-patch
+0015-Mark-failing-test-on-i386-as-xfail.patch
diff -Nru python-xarray-2022.12.0/debian/rules python-xarray-2022.12.0/debian/rules
--- python-xarray-2022.12.0/debian/rules 2022-12-03 08:28:13.0 +0100
+++ python-xarray-2022.12.0/debian/rules 2022-12-29 09:18:29.0 +0100
@@ -4,7 +4,7 @@
export DH_VERBOSE=1
export PYBUILD_NAME=xarray
-PY3VERS:= $(shell py3versions -s)
+export http_proxy=127.0.0.1:9 https_proxy=127.0.0.1:9
# Disable checking for this release:
DEB_BUILD_OPTIONS += nocheck
@@ -12,30 +12,19 @@
%:
dh $@ --buildsystem=pybuild
-override_dh_auto_clean:
- dh_auto_clean
+execute_after_dh_auto_clean:
ifeq (,$(findstring nodoc,$(DEB_BUILD_PROFILES)))
$(MAKE) -C doc clean
endif
-override_dh_auto_install: $(PYTHON3:%=install-python%)
- dh_auto_install
+execute_after_dh_auto_install: $(PYTHON3:%=install-python%)
find debian/python3-xarray -name '*.idx' -exec chmod -x {} \;
-override_dh_auto_build:
- http_proxy=127.0.0.1:9 https_proxy=127.0.0.1:9 dh_auto_build
+execute_after_dh_auto_build:
ifeq (,$(findstring nodoc,$(DEB_BUILD_PROFILES)))
PYTHONPATH=$(CURDIR) $(MAKE) -C doc html
endif
-override_dh_auto_test:
-ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
- for p in $(PY3VERS); do \
- PY3VERNUM=`echo $$p | sed -e 's/python//' `; \
- pybuild --test --test-pytest -i $$p -p $$PY3VERNUM ; \
- done
-endif
-
override_dh_sphinxdoc:
dh_sphinxdoc --exclude=MathJax.js
find debian/python-xarray-doc -name '*.html' \
signature.asc
Description: PGP signature
Bug#1026700: reassign 1026652 to ruby-asciidoctor-pdf, affects 1026652, closing 1026652 ..., affects 1026700 ...
reassign 1026652 ruby-asciidoctor-pdf 2.3.4-2 affects 1026652 src:nickle close 1026652 2.3.4-3 reassign 1026700 ruby-asciidoctor-pdf 2.3.4-2 affects 1026700 src:snek close 1026700 2.3.4-3 thanks
Bug#1026020: closing 1026020
close 1026020 0.12.0-2 thanks
Bug#1019989: python-reportlab: diff for NMU version 3.6.11-1.1
Control: tags 1019989 + patch Control: tags 1019989 + pending Dear maintainer, I've prepared an NMU for python-reportlab (versioned as 3.6.11-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru python-reportlab-3.6.11/debian/changelog python-reportlab-3.6.11/debian/changelog --- python-reportlab-3.6.11/debian/changelog 2022-07-17 14:14:52.0 +0200 +++ python-reportlab-3.6.11/debian/changelog 2022-12-26 15:13:28.0 +0100 @@ -1,3 +1,10 @@ +python-reportlab (3.6.11-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix PYTHONPATH in d/rules to fix FTBFS (Closes: #1019989) + + -- Jochen Sprickerhof Mon, 26 Dec 2022 15:13:28 +0100 + python-reportlab (3.6.11-1) unstable; urgency=medium * New upstream version. diff -Nru python-reportlab-3.6.11/debian/rules python-reportlab-3.6.11/debian/rules --- python-reportlab-3.6.11/debian/rules 2022-03-10 19:14:33.0 +0100 +++ python-reportlab-3.6.11/debian/rules 2022-12-26 15:13:23.0 +0100 @@ -5,7 +5,7 @@ # all versions PY3VERS := $(shell py3versions -vs) -VER3 := $(shell py3versions -vd) +VER3 := $(shell py3versions -vd | tr -d .) include /usr/share/python3/python.mk signature.asc Description: PGP signature
Bug#1013385: marked as pending in recommonmark
Control: tag -1 pending Hello, Bug #1013385 in recommonmark 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/recommonmark/-/commit/5c8268144f9b91b7f5f37fed76d25cf4c0bfa561 Add patch for Sphinx 5 Closes: #1013385 (this message was generated automatically) -- Greetings https://bugs.debian.org/1013385
