Bug#997516: marked as done (guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check VERBOSE=1 returned exit code 2)
Your message dated Thu, 11 Nov 2021 07:33:41 +
with message-id
and subject line Bug#997516: fixed in guile-ssh 0.13.1-5
has caused the Debian Bug report #997516,
regarding guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 &&
make -j1 check VERBOSE=1 returned exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guile-ssh
Version: 0.13.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering directory '/<>/debian/build/guile-3.0/tests'
> PASS: log.scm
> PASS: server.scm
> PASS: session.scm
> PASS: client-server.scm
> PASS: popen.scm
> PASS: shell.scm
> PASS: server-client.scm
> PASS: sssh-ssshd.scm
> PASS: key.scm
> PASS: tunnel.scm
> FAIL: dist.scm
>
>Guile-SSH 0.13.1: tests/test-suite.log
>
>
> # TOTAL: 11
> # PASS: 10
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: dist
> ==
>
> Starting test dist
> Group begin: dist
> Test begin:
> test-name: "make-node"
> source-file: "tests/dist.scm"
> source-line: 44
> source-form: (test-assert "make-node" (begin (set-log-userdata!
> "make-node") (run-client-test (lambda (server) (start-server/exec server
> (const #t))) (lambda () (call-with-connected-session/shell (lambda (session)
> (let ((n (make-node session))) (and n (eq? (node-session n) session)
> Test end:
> result-kind: pass
> actual-value: #t
> Test begin:
> test-name: "split, 1"
> source-file: "tests/dist.scm"
> source-line: 57
> source-form: (test-equal "split, 1" (quote ((a b) (c d) (e f g))) (split
> (quote (a b c d e f g)) 3))
> Test end:
> result-kind: pass
> actual-value: ((a b) (c d) (e f g))
> expected-value: ((a b) (c d) (e f g))
> Test begin:
> test-name: "split, 2"
> source-file: "tests/dist.scm"
> source-line: 61
> source-form: (test-equal "split, 2" (quote ((a))) (split (quote (a)) 2))
> Test end:
> result-kind: pass
> actual-value: ((a))
> expected-value: ((a))
> Test begin:
> test-name: "make-job"
> source-file: "tests/dist.scm"
> source-line: 66
> source-form: (test-assert "make-job" (begin (set-log-userdata! "make-job")
> (run-client-test (lambda (server) (start-server/exec server (const #f)))
> (lambda () (call-with-connected-session/shell (lambda (session) (let* ((node
> (make-node session)) (data (quote (1 2 3))) (proc (quote (lambda (n) (#{1+}#
> n (j (make-job (quote map) node data proc))) (and (eq? (job-type j)
> (quote map)) (eq? (job-node j) node) (eq? (job-data j) data) (eq? (job-proc
> j) proc)
> Test end:
> result-kind: pass
> actual-value: #t
> Test begin:
> test-name: "set-job-node"
> source-file: "tests/dist.scm"
> source-line: 85
> source-form: (test-assert "set-job-node" (begin (set-log-userdata!
> "set-job-node") (run-client-test (lambda (server) (start-server/exec server
> (const #t))) (lambda () (call-with-connected-session/shell (lambda (session)
> (let* ((n1 (make-node session)) (n2 (make-node session)) (data (quote ()))
> (proc (quote (lambda (n) (#{1+}# n (j1 (make-job (quote map) n1 data
> proc)) (j2 (set-job-node j1 n2))) (and (not (eq? j1 j2)) (eq? (job-type j1)
> (job-type j2)) (eq? (job-node j1) n1) (eq? (job-node j2) n2) (eq? (job-data
> j1) (job-data j2)) (eq? (job-proc j1) (job-proc j2))
> Test end:
> result-kind: pass
> actual-value: #t
> Test begin:
> test-name: "hand-out-job, invalid type"
> source-file: "tests/dist.scm"
> source-line: 107
> source-form: (test-assert "hand-out-job, invalid type" (begin
> (set-log-userdata! "hand-out-job, invalid type") (catch #t (lambda ()
> (run-client-test (lambda (server) (start-server/exec server (const #t)))
> (lambda () (call-with-connected-session/shell (lambda (session) (let ((n
> (make-node session))) (hand-out-job (make-job (quote invalid-job) n (quote
> ()) (const #t #f) (const #t
> Test end:
> result-kind: pass
> actual-value: #t
> Test begin:
> test-name: "assign-eval"
> source-file: "tests/dist.scm"
> source-line: 120
> source-form: (test-assert "assign-eval" (begin (set-log-userdata!
> "assign-eval") (run-client-test (lambda
Processed: 1.1.3 builds
Processing commands for cont...@bugs.debian.org: > tags 996364 fixed-upstream Bug #996364 [src:ruby-recursive-open-struct] ruby-recursive-open-struct: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: alias_method :modifiable?, :modifiable Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pynfft: Removal of the python3-*-dbg packages in sid/bookworm
Processing control commands: > severity -1 serious Bug #994335 [src:pynfft] pynfft: Removal of the python3-*-dbg packages in sid/bookworm Severity set to 'serious' from 'important' -- 994335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm
Processing control commands: > severity -1 serious Bug #994304 [src:libgpuarray] libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm Severity set to 'serious' from 'important' -- 994304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998449: marked as done (autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2)
Your message dated Thu, 11 Nov 2021 03:18:31 + with message-id and subject line Bug#998449: fixed in golang-github-containernetworking-plugins 0.9.1+ds1-1 has caused the Debian Bug report #998449, regarding autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libpod Version: 3.4.1+ds1-2 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org The libpod autopkgtest curently fails in unstable. I have seen #993532, but I don't know if it's the same issue. See the log below, slightly edited for brevity. Unfortunately there is zero diagnostics output, it just exits non-zero failing the test. Maybe this is something that could be improved in dh_golang_autopkgtest, I don't know. 8<8<8<- autopkgtest [08:39:48]: test dh-golang-autopkgtest: /usr/bin/dh_golang_autopkgtest autopkgtest [08:39:48]: test dh-golang-autopkgtest: [--- [info] Testing github.com/containers/podman... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang,bash-completion --builddirectory=_output dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_output dh_autoreconf -O--buildsystem=golang -O--builddirectory=_output debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' mkdir -p "_output" cp -a /usr/share/gocode/src "_output" make[1]: Leaving directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' /usr/bin/make docs docker-docs make[2]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' mkdir -p "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/tmp/go/src/github.com/containers" ln -sfn "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp" "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/tmp/go/src/github.com/containers/podman" touch .gopathok if [ ! -x "/usr/bin/go-md2man" ]; then \ env GO111MODULE=off go get -u github.com/cpuguy83/go-md2man; \ fi mkdir -p docs/build/man (cd docs; ./dckrman.sh ./build/man/*.1) make[2]: Leaving directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' dh_auto_build -v --builddirectory=_output -- -tags "apparmor,ostree,seccomp,selinux,systemd" \ -ldflags "-X main.buildInfo=3.4.1+ds1-2" cd _output && go version go version go1.17.2 linux/amd64 cd _output && go env GO111MODULE="off" GOARCH="amd64" GOBIN="" GOCACHE="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output/go-build" GOENV="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/.debhelper/generated/_source/home/.config/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output" GOPRIVATE="" GOPROXY="off" GOROOT="/usr/lib/go-1.17" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/usr/lib/go-1.17/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.17.2" GCCGO="gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong -Wformat -Werror=format-security" CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CGO_CXXFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong -Wformat -Werror=format-security" CGO_FFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong" CGO_LDFLAGS="-Wl,-z,relro" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2850767338=/tmp/go-build -gno-record-gcc-switches" cd _output && go generate -v -tags apparmor,ostree,seccomp,selinux,systemd -ldflags "-X main.buildInfo=3.4.1+ds1-2" github.com/containers/podman/cmd/podman github.com/containers/podman/cmd/podman/common github.com/containers/podman/cmd/podman/completion github.com/containers/podman/cmd/podman/containers
Bug#999440: golang-github-containerd-stargz-snapshotter: Build access network
Source: golang-github-containerd-stargz-snapshotter Version: 0.8.0-3 Severity: serious X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/fetch.php?pkg=golang-github-containerd-stargz-snapshotter=all=0.8.0-4=1636327998=0 === RUN TestLayerConvertFunc estargz_test.go:37: Get "https://github.com/AkihiroSuda/test-oci-archives/releases/download/v20210101/hello-world.tar.gz": dial tcp 140.82.121.3:443: connect: network is unreachable --- FAIL: TestLayerConvertFunc (0.13s) FAIL FAILgithub.com/containerd/stargz-snapshotter/nativeconverter/estargz 0.170s === RUN TestLayerConvertFunc zstdchunked_test.go:40: Get "https://github.com/AkihiroSuda/test-oci-archives/releases/download/v20210101/hello-world.tar.gz": dial tcp 140.82.121.3:443: connect: network is unreachable --- FAIL: TestLayerConvertFunc (0.00s) FAIL
Bug#998358: marked as done (Subject: grepmail: autopkgtest doesn't do anything)
Your message dated Thu, 11 Nov 2021 03:03:29 + with message-id and subject line Bug#998358: fixed in grepmail 5.3104-4 has caused the Debian Bug report #998358, regarding Subject: grepmail: autopkgtest doesn't do anything to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grepmail X-Debbugs-Cc: mar...@talau.info, eribe...@debian.org Version: 5.3104-1 Severity: serious Justification: RC policy Dear Marcos, Joao, I appreciate your attention to the orphaned package grepmail and the fact that you try to save it from removal from testing, but in the process you added and autopkgtest that doesn't do anything at all. I played around with it a tiny bit, and the reason it doesn't run anything is because dh_auto_test doesn't detect a known framework. Why dh_auto_test works during building is that during build a Makefile is generated in one of the steps before testing and dh_auto_test executes the test target in that. For this to work, the autopkgtest at least needs more of the Build-Depends, otherwise the test fails. I ran the following manually in the testbed after checking what code was actually run during the test on the buildd and it currently fails all tests: PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 'blib/arch')" t/*.t Before fixing this, please ensure you're testing the as-installed binary instead of the code in the source tree, as the intention of autopkgtest is to test the package, not the source, as I believe you're not testing /usr/bin/grepmail Paul -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: grepmail Source-Version: 5.3104-4 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of grepmail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated grepmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 23:37:30 -0300 Source: grepmail Architecture: source Version: 5.3104-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Joao Eriberto Mota Filho Closes: 998358 Changes: grepmail (5.3104-4) unstable; urgency=medium . * QA upload. * debian/tests/control: removed because the current CI test was useless. Thanks to Paul Gevers . (Closes: #998358) Checksums-Sha1: 2adfc0a91d1a78edf3d1c337080ad20e67763c1d 2004 grepmail_5.3104-4.dsc f34e83c9ce6cc846eaef58163c22e32dc4b4c353 6512 grepmail_5.3104-4.debian.tar.xz f04f5f76cbbcb2367b5290edfdd8f2461eebfa76 5475 grepmail_5.3104-4_source.buildinfo Checksums-Sha256: dc8cd5b5e4774462c7409f22b1eb3af71d00e2569d2a024748013d976e58443b 2004 grepmail_5.3104-4.dsc 1f6b1a5512520a5c629dc4136e20fbd3495c87c19b9db9d4f5bfa4ab686b2f06 6512 grepmail_5.3104-4.debian.tar.xz 0781fbf95633feb9e05088697d9bfd5846edd24e41782993553a8bc49e6b8045 5475 grepmail_5.3104-4_source.buildinfo Files: e35310e90c4a9bc9afc4e6802c2ab16c 2004 mail optional grepmail_5.3104-4.dsc 4dd17aafaf4f526bd818d7eeb3e274f8 6512 mail optional grepmail_5.3104-4.debian.tar.xz 42af22472f10d3c2395f71cbde261565 5475 mail optional grepmail_5.3104-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmGMhJcACgkQ3mO5xwTr 6e+ZTBAAlqjVLYb+cTa+61/9Bt7XXH2sz644uL1rksdh/wO/dg8IVPRKw66o6P9Y cVPc906XN4jlVZvVvBTw0HygdSMNNJCiFaFlHE9ztCsOMzgOjo8+/DqIZslgIBc4
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Em qua., 10 de nov. de 2021 às 18:55, Paul Gevers escreveu: > > Hi Eriberto, > > On Tue, 2 Nov 2021 19:57:37 -0300 Eriberto wrote: > > ow, Marcos will package the new upstream > > release and he will fix this mistake. In a final action, he will send > > a SPU to fix a specific issue. > > Please be aware that grepmail will be removed from testing in 7 days if > the issue isn't fixed. Obviously, the package can come back later too, > but just so you know. Thanks Paul. Marcos is a bit busy these days, so I will fix this issue now. Regards, Eriberto
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
On Tue, 2021-11-09 at 22:56 +1100, David Bannon wrote: > No, sorry, I cannot do a sensible test of my app using FPC and/or > Lazarus from sid. > > I can install FPC3.2.2 from Sid by using priorities. > > But the Lazarus in Sid is non functional, blocked, because of an > issue OK, I have made this work. Instead of cherry picking just fpc and lazarus from Sid, I 'updated' my whole Testing (VM) install to Sid and that worked as expected. Tests all passed, I will push it up, as a new release (closing this ticket) as soon as I get a fresh Spanish translation. My translator is sometimes out of direct contact so not sure how long that will be. Davo
Bug#997300: marked as done (ruby-mini-portile2: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError: Failed to complete configure task)
Your message dated Thu, 11 Nov 2021 01:18:47 + with message-id and subject line Bug#997300: fixed in ruby-mini-portile2 2.5.0-3 has caused the Debian Bug report #997300, regarding ruby-mini-portile2: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError: Failed to complete configure task to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mini-portile2 Version: 2.5.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > RuntimeError: Failed to complete configure task > > /<>/debian/ruby-mini-portile2/usr/share/rubygems-integration/all/gems/mini_portile2-2.5.0/lib/mini_portile2/mini_portile.rb:405:in > `block in execute' > > /<>/debian/ruby-mini-portile2/usr/share/rubygems-integration/all/gems/mini_portile2-2.5.0/lib/mini_portile2/mini_portile.rb:376:in > `chdir' > > /<>/debian/ruby-mini-portile2/usr/share/rubygems-integration/all/gems/mini_portile2-2.5.0/lib/mini_portile2/mini_portile.rb:376:in > `execute' > > /<>/debian/ruby-mini-portile2/usr/share/rubygems-integration/all/gems/mini_portile2-2.5.0/lib/mini_portile2/mini_portile_cmake.rb:22:in > `configure' > > /<>/debian/ruby-mini-portile2/usr/share/rubygems-integration/all/gems/mini_portile2-2.5.0/lib/mini_portile2/mini_portile.rb:153:in > `cook' > /<>/test/test_cmake.rb:25:in `block (2 levels) in before_all' > /<>/test/helper.rb:56:in `with_custom_git_dir' > /<>/test/test_cmake.rb:24:in `block in before_all' > /<>/test/test_cmake.rb:19:in `tap' > /<>/test/test_cmake.rb:19:in `before_all' > /usr/lib/ruby/vendor_ruby/minitest/hooks/test.rb:74:in `block (2 levels) > in with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/hooks/test.rb:72:in `block in > with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/hooks/test.rb:26:in `around_all' > /usr/lib/ruby/vendor_ruby/minitest/hooks/test.rb:70:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 19 runs, 37 assertions, 0 failures, 1 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_cmake.rb" "test/test_cook.rb" "test/test_download.rb" > "test/test_proxy.rb" -v] > /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in ` (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2021/10/23/ruby-mini-portile2_2.5.0-2_unstable.log 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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-mini-portile2 Source-Version: 2.5.0-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-mini-portile2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-mini-portile2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 Nov 2021
Processed: tagging 996529
Processing commands for cont...@bugs.debian.org: > # https://github.com/hashicorp/vagrant/pull/12427 > tags 996529 + patch Bug #996529 [src:vagrant] vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 996529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998903: src:libidn: fails to migrate to testing for too long
On 11/10/21 16:25, Simon Josefsson wrote: James Valleroy via "Discussion list for GNU Internationalized Domain Name library (Libidn)" writes: On 11/10/21 6:40 AM, Simon Josefsson wrote: James, what do you think? Is the libidn11-java package important for you to have in Debian? My perception was that nobody really used it, and IDNA2003/StringPrep is old technology so it feels strange that new code is coming around using. While I am also upstream of this Java code, I'm not familiar with how Java stuff is packaged/used in Debian, and maybe there is another way of doing things that is just as easy for you. Hello, (Adding Sunil who did most of the packaging work for libjxmpp-java.) libjxmpp-java was packaged as a dependency of jitsi-videobridge. Specifically for Jitsi we need the -core, -jid, and -util-cache modules. It looks like libidn is only used for jxmpp-stringprep-libidn module. Possibly we can disable building this module. Is it not used by anything else? If so, I agree it makes sense to disable it, unless you think it is useful elsewhere. I could add libidn11-java back if there is real usage of it, but if it is not needed for anything particular right now, I would prefer if you disable it until there is real interest in using it. When/if that occurs, we can always add libidn11-java and jxmpp-stringprep-libidn back again. Hopefully, XMPP will be updated to use something newer than StringPrep meanwhile. Simon, thank you for offering to build the library again if needed. My understanding was that one of the three stringprep implementations is needed to use the jxmpp library. They are based on libidn, icu4j and rocksxmppprecis. Of these, we have only built the stringprep library based on libidn and assumed it to be critical. However, I dug up a bit more in jitsi-xmpp-extenstions and other jitsi-videobridge code. To use the jxmpp-stringprep-libidn library one needs to import the class and call setup() on it. This does seem to be happening anywhere as far as I can tell. In this case, the jxmpp library seems to use a fallback implementation. It appears we can drop building the library jxmpp-stringprep-libidn although I can't say for sure without going through jitsi and all of its dependencies more thoroughly. When we progress more on the packaging effort we might know better and can then request libidn to build libidn11-java again. James, let us drop building jxmpp-stringprep-libidn for now and drop dependency on libidn11-java. Thanks, -- Sunil
Bug#997394: marked as done (libjpeg-turbo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE
Your message dated Thu, 11 Nov 2021 00:33:29 + with message-id and subject line Bug#997394: fixed in libjpeg-turbo 1:2.1.1-1 has caused the Debian Bug report #997394, regarding libjpeg-turbo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu --with-build-date=1:2.0.6-4 -DWITH_SIMD=1 -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DCMAKE_INSTALL_MANDIR=/usr/share/man/ .. returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libjpeg-turbo Version: 1:2.0.6-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- --with-build-date=1:2.0.6-4 \ > -DWITH_SIMD=1 \ > -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu \ > -DCMAKE_INSTALL_MANDIR=/usr/share/man/ > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > --with-build-date=1:2.0.6-4 -DWITH_SIMD=1 > -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu > -DCMAKE_INSTALL_MANDIR=/usr/share/man/ .. > CMake Error: Unknown argument --with-build-date=1:2.0.6-4 > CMake Error: Run 'cmake --help' for all supported options. > dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake > -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > --with-build-date=1:2.0.6-4 -DWITH_SIMD=1 > -DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu > -DCMAKE_INSTALL_MANDIR=/usr/share/man/ .. returned exit code 1 > make[1]: *** [debian/rules:49: override_dh_auto_configure] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/libjpeg-turbo_2.0.6-4_unstable.log 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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libjpeg-turbo Source-Version: 1:2.1.1-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of libjpeg-turbo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated libjpeg-turbo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Nov 2021 01:17:59 +0100 Source: libjpeg-turbo Architecture: source Version: 1:2.1.1-1 Distribution: unstable Urgency:
Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
On Fri, 5 Nov 2021 05:55:52 +0100 Florian Schlichting wrote: > Hi Ryan (and Max please see below): > > please, for now, delete or comment out the pid_file line I'm responding to this bug as commenting out the pid_file line was the solution for me too, but my 'symptoms' are (a bit) different. For me it wasn't a new install of mpd, but an upgrade: root@soundserver:~# grep 'upgrade mpd' /var/log/dpkg.log 2021-11-10 21:03:37 upgrade mpd:arm64 0.22.10-1+b1 0.23.3-2 The system upgrade brought a lot of updated and also new packages (pipewire), but in hindsight it's probably not important. I also installed a new kernel and therefor rebooted my system. After reboot I noticed a problem with mpd: diederik@soundserver:~$ systemctl | grep -i fail ● mpd.service loaded failed failedMusic Player Daemon ● mpd.socket loaded failed failedmpd.socket diederik@soundserver:~$ systemctl status mpd.service × mpd.service - Music Player Daemon Loaded: loaded (/lib/systemd/system/mpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2021-11-10 23:30:21 CET; 1min 11s ago TriggeredBy: × mpd.socket Docs: man:mpd(1) man:mpd.conf(5) file:///usr/share/doc/mpd/html/user.html Process: 1466 ExecStart=/usr/bin/mpd --no-daemon $MPDCONF (code=exited, status=1/FAILURE) Main PID: 1466 (code=exited, status=1/FAILURE) CPU: 1.876s nov 10 23:30:19 soundserver systemd[1]: Starting Music Player Daemon... nov 10 23:30:21 soundserver mpd[1466]: Nov 10 23:30 : exception: Tag list mismatch, discarding database file nov 10 23:30:21 soundserver mpd[1466]: Nov 10 23:30 : exception: Failed to create pid file "/run/mpd/pid": Permission denied nov 10 23:30:21 soundserver systemd[1]: mpd.service: Main process exited, code=exited, status=1/FAILURE nov 10 23:30:21 soundserver systemd[1]: mpd.service: Failed with result 'exit-code'. nov 10 23:30:21 soundserver systemd[1]: Failed to start Music Player Daemon. nov 10 23:30:21 soundserver systemd[1]: mpd.service: Consumed 1.876s CPU time. nov 10 23:30:21 soundserver systemd[1]: mpd.service: Start request repeated too quickly. nov 10 23:30:21 soundserver systemd[1]: mpd.service: Failed with result 'exit-code'. nov 10 23:30:21 soundserver systemd[1]: Failed to start Music Player Daemon. I found https://github.com/MusicPlayerDaemon/MPD/issues/1299 which seem to indicate that the first exception is expected. I did a "mpc rescan" both as user (me) and as root, but got "MPD error: Connection refused", which indicates a premission issue. So I checked the /run/ directory and saw that there wasn't a 'mpd' subdir. Then I checked Debian's BTS and found this bug. After disabling the pidfile-line, mpd did start up successfully (it still printed the "exception: Tag list mismatch, discarding database file", but it now did start successfully. root@soundserver:~# ls -ld /run/mpd drwxr-xr-x 2 root root 60 Nov 10 23:53 /run/mpd root@soundserver:~# ls -l /run/mpd/ total 0 srw-rw-rw- 1 root root 0 Nov 10 23:53 socket I'm _assuming_ that it's the same issue, but as my symptoms are somewhat different, I thought I'd mention mine. If this is actually a different issue which should be filed separately, let me know and I'll do that. If you want me to run (some) tests, I can do that too. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#998224: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so
Unfortunately the system which exhibited the problem has now been updated with a working version after I kludged it to work. However, what happens is the shared libraries are all linked twice. The first time it is linked to libraries in the build tree (and do not have links to the old . They are then relinked, I assume as part of installing the files for packaging. At that stage, libhpdiscovery.so* will not be found in debian/tmp/usr/lib/x86_64-linux-gnu, and it picks it up from the local system, if installed, or fails, if not. If the build picks it up to the local system, and the one in the local system is linked to libnetsnmp.so.30, then this dependency propagates through the other libraries, resulting in libraries that cannot be loaded at all. I eventually got the build to work by removing all old copies of libhpdiscovery.so* from the system library directories, manually copying libhpdiscovery.so* from the build tree to the system library directories, then freshly extracting the source and rebuilding. I built using debuild on a live system. I suspect reproducing will not be straight-forward as it requires a system that still has the version of hplip from buster, but has otherwise been upgraded to bullseye. I cannot spare the time right now to set up a test environment and make the attempt to reproduce this, so perhaps this should be closed and left as a record for anybody who encounters the problem later. On 7/11/21 11:30 am, Thorsten Alteholz wrote: Control: tag -1 moreinfo Hi Troy, thanks for your bugreport. Unfortunately I have problems understanding what is going on. How can HPLIP link to a missing libhpdiscovery.so. I assume you are building the package in a minimal chroot. How can there be an old version of libhpdiscovery.so available? Can you please be a bit more verbose about what you are doing and what fails? Best regards, Thorsten smime.p7s Description: S/MIME Cryptographic Signature
Bug#984199: marked as done (libpappsomspp: ftbfs with GCC-11)
Your message dated Wed, 10 Nov 2021 23:03:50 + with message-id and subject line Bug#984199: fixed in libpappsomspp 0.8.39-1 has caused the Debian Bug report #984199, regarding libpappsomspp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libpappsomspp Version: 0.8.15-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libpappsomspp_0.8.15-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /<>/src/pappsomspp/processing/tandemwrapper/xtandempresetsaxhandler.cpp:184:72: warning: ‘QXmlParseException’ is deprecated [-Wdeprecated-declarations] 184 | XtandemPresetSaxHandler::fatalError(const QXmlParseException ) |^ [ 10%] Building CXX object src/CMakeFiles/pappsomspp-shared.dir/pappsomspp/massspectrum/massspectrumid.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_THREAD_DYN_LINK -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -DWITHOUT_MZ5 -Dpappsomspp_shared_EXPORTS -I/<>/obj-x86_64-linux-gnu/src/pappsomspp-shared_autogen/include -isystem /usr/include/pwizlite -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x 86_64-linux-gnu/qt5/QtConcurrent -isystem /usr/include/libalglib -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -Wno-unknown-pragmas -Wall -Wextra -fPIC -fPIC -std=gnu++17 -o CMakeFiles/pappsomspp-shared.dir/pappsomspp/massspectrum/massspectrumid.cpp.o -c /<>/src/pappsomspp/massspectrum/massspectrumid.cpp In file included from /<>/src/pappsomspp/massspectrum/massspectrumid.cpp:25: /<>/src/pappsomspp/massspectrum/massspectrumid.h:54:38: error: ‘numeric_limits’ is not a member of ‘std’ 54 | std::size_t m_spectrumIndex = std::numeric_limits::max(); | ^~ /<>/src/pappsomspp/massspectrum/massspectrumid.h:54:64: error: expected primary-expression before ‘>’ token 54 | std::size_t m_spectrumIndex = std::numeric_limits::max(); |^ /<>/src/pappsomspp/massspectrum/massspectrumid.h:54:67: error: ‘::max’ has not been declared 54 | std::size_t m_spectrumIndex = std::numeric_limits::max(); |
Bug#994055: cunit NMU
On Thu, 11 Nov 2021 at 10:49, Paul Gevers wrote: > Hi Michael, > > On Wed, 10 Nov 2021 16:16:53 +1300 Michael Hudson-Doyle > wrote: > > Hi, thanks for this fix. I think it meets the threshold for NMU (and also > > the maintainer seems to have been awol since 2015) so I'm uploading it to > > DELAYED/10. > > I was working on this yesterday and uploaded to DELAYED too, because I > forgot to check the bug history. As I uploaded to DELAYED/2, I decided > to dcut my upload, but apparently I was able to dcut your upload... > Ha. > Log of processing your commands file /paul-1636580073.commands: > > > cancel cunit_2.1-3-dfsg-2.4_source.changes > Files removed from 10-day: cunit_2.1-3-dfsg-2.4_source.changes > cunit_2.1-3-dfsg-2.4.dsc cunit_2.1-3-dfsg-2.4.debian.tar.xz > cunit_2.1-3-dfsg-2.4_source.buildinfo > > Could you reupload your changes, or do you want me to upload mine? > If you have yours close at hand, feel free to upload them? Otherwise I think I still have the changes file around... > Sorry for the mess. > So long as we get a fixed package I'm not bothered!
Bug#998358: Subject: grepmail: autopkgtest doesn't do anything
Hi Eriberto, On Tue, 2 Nov 2021 19:57:37 -0300 Eriberto wrote: > ow, Marcos will package the new upstream > release and he will fix this mistake. In a final action, he will send > a SPU to fix a specific issue. Please be aware that grepmail will be removed from testing in 7 days if the issue isn't fixed. Obviously, the package can come back later too, but just so you know. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#994055: cunit NMU
Hi Michael, On Wed, 10 Nov 2021 16:16:53 +1300 Michael Hudson-Doyle wrote: > Hi, thanks for this fix. I think it meets the threshold for NMU (and also > the maintainer seems to have been awol since 2015) so I'm uploading it to > DELAYED/10. I was working on this yesterday and uploaded to DELAYED too, because I forgot to check the bug history. As I uploaded to DELAYED/2, I decided to dcut my upload, but apparently I was able to dcut your upload... Log of processing your commands file /paul-1636580073.commands: > cancel cunit_2.1-3-dfsg-2.4_source.changes Files removed from 10-day: cunit_2.1-3-dfsg-2.4_source.changes cunit_2.1-3-dfsg-2.4.dsc cunit_2.1-3-dfsg-2.4.debian.tar.xz cunit_2.1-3-dfsg-2.4_source.buildinfo Could you reupload your changes, or do you want me to upload mine? Sorry for the mess. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#995655: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Control: tags -1 + patch
Hi Simon
On 10.11.21 20:44, Michael Biebl wrote:
Simon,
any news here?
Would you mind if I prepare an NMU with
26bbf5a314d833beaf0f147d24409969f05f3dba ?
I decided to follow the rules in [1] and uploaded a fixed package to
DELAYED/2. Please holler if you want me to cancel the NMU.
debdiff is attached.
Regards,
Michael
[1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmu
diff -u dnsmasq-2.86/debian/changelog dnsmasq-2.86/debian/changelog
--- dnsmasq-2.86/debian/changelog
+++ dnsmasq-2.86/debian/changelog
@@ -1,3 +1,10 @@
+dnsmasq (2.86-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix --address=/#/.. which was lost in 2.86. (closes: #995655)
+
+ -- Michael Biebl Wed, 10 Nov 2021 22:05:45 +0100
+
dnsmasq (2.86-1) unstable; urgency=low
* Fix debian/changelog format error. (closes: #986626)
only in patch2:
unchanged:
--- dnsmasq-2.86.orig/CHANGELOG
+++ dnsmasq-2.86/CHANGELOG
@@ -1,3 +1,11 @@
+version 2.87
+Allow arbitrary prefix lengths in --rev-server and
+ --domain=,local
+
+ Replace --address=/#/. functionality which got
+ missed in the 2.86 domain search rewrite.
+
+
version 2.86
Handle DHCPREBIND requests in the DHCPv6 server code.
Thanks to Aichun Li for spotting this omission, and the initial
only in patch2:
unchanged:
--- dnsmasq-2.86.orig/src/network.c
+++ dnsmasq-2.86/src/network.c
@@ -1623,7 +1623,8 @@
continue;
if ((serv->flags & SERV_LITERAL_ADDRESS) &&
- !(serv->flags & (SERV_6ADDR | SERV_4ADDR | SERV_ALL_ZEROS)))
+ !(serv->flags & (SERV_6ADDR | SERV_4ADDR | SERV_ALL_ZEROS)) &&
+ strlen(serv->domain))
{
count--;
if (++locals <= LOCALS_LOGGED)
only in patch2:
unchanged:
--- dnsmasq-2.86.orig/src/option.c
+++ dnsmasq-2.86/src/option.c
@@ -2684,7 +2684,7 @@
if (!arg || !*arg)
flags = SERV_LITERAL_ADDRESS;
- else if (option == 'A')
+ else if (option != 'S')
{
/* # as literal address means return zero address for 4 and 6 */
if (strcmp(arg, "#") == 0)
@@ -2708,11 +2708,18 @@
while (1)
{
/* server=//1.2.3.4 is special. */
- if (strlen(domain) == 0 && lastdomain)
- flags |= SERV_FOR_NODOTS;
- else
- flags &= ~SERV_FOR_NODOTS;
+ if (lastdomain)
+ {
+ if (strlen(domain) == 0)
+ flags |= SERV_FOR_NODOTS;
+ else
+ flags &= ~SERV_FOR_NODOTS;
+ /* address=/#/ matches the same as without domain */
+ if (option != 'S' && domain[0] == '#' && domain[1] == 0)
+ domain[0] = 0;
+ }
+
if (!add_update_server(flags, _addr, _addr, interface,
domain, ))
ret_err(gen_err);
OpenPGP_signature
Description: OpenPGP digital signature
Processed: Re: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Processing control commands: > tags -1 + patch Bug #995655 [dnsmasq] dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143 Added tag(s) patch. -- 995655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999429: src:guix: fails to migrate to testing for too long: FTBFS on i386
Source: guix Version: 1.2.0-4 Severity: serious Control: close -1 1.3.0-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:guix has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=guix OpenPGP_signature Description: OpenPGP digital signature
Processed: src:guix: fails to migrate to testing for too long: FTBFS on i386
Processing control commands: > close -1 1.3.0-2 Bug #999429 [src:guix] src:guix: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions guix/1.3.0-2. Bug #999429 [src:guix] src:guix: fails to migrate to testing for too long: FTBFS on i386 Marked Bug as done -- 999429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972146: /usr/share/applications/mono-runtime-common.desktop: should not handle MIME type by executing arbitrary code
Hi, Any help needed for this? Regards, Gabriel
Processed: golang-github-containernetworking-plugins breaks libpod autopkgtest
Processing commands for cont...@bugs.debian.org: > reassign 998449 src:golang-github-containernetworking-plugins,src:libpod Bug #998449 [src:golang-github-containernetworking-plugin,src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Warning: Unknown package 'src:golang-github-containernetworking-plugin' Bug reassigned from package 'src:golang-github-containernetworking-plugin,src:libpod' to 'src:golang-github-containernetworking-plugins,src:libpod'. No longer marked as found in versions libpod/3.4.1+ds1-2 and golang-github-containernetworking-plugins/0.9.1-1. Ignoring request to alter fixed versions of bug #998449 to the same values previously set > found 998449 golang-github-containernetworking-plugins/0.9.1-1 Bug #998449 [src:golang-github-containernetworking-plugins,src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Marked as found in versions golang-github-containernetworking-plugins/0.9.1-1. > found 998449 libpod/3.4.1+ds1-2 Bug #998449 [src:golang-github-containernetworking-plugins,src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Marked as found in versions libpod/3.4.1+ds1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 998449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: golang-github-containernetworking-plugins breaks libpod autopkgtest
Processing commands for cont...@bugs.debian.org: > reassign 998449 src:golang-github-containernetworking-plugin,src:libpod Bug #998449 [src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Bug reassigned from package 'src:libpod' to 'src:golang-github-containernetworking-plugin,src:libpod'. Warning: Unknown package 'src:golang-github-containernetworking-plugin' Warning: Unknown package 'src:golang-github-containernetworking-plugin' No longer marked as found in versions libpod/3.4.1+ds1-2. Warning: Unknown package 'src:golang-github-containernetworking-plugin' Warning: Unknown package 'src:golang-github-containernetworking-plugin' Ignoring request to alter fixed versions of bug #998449 to the same values previously set Warning: Unknown package 'src:golang-github-containernetworking-plugin' > found 998449 golang-github-containernetworking-plugins/0.9.1-1 Bug #998449 [src:golang-github-containernetworking-plugin,src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Warning: Unknown package 'src:golang-github-containernetworking-plugin' Marked as found in versions golang-github-containernetworking-plugins/0.9.1-1. Warning: Unknown package 'src:golang-github-containernetworking-plugin' > found 998449 libpod/3.4.1+ds1-2 Bug #998449 [src:golang-github-containernetworking-plugin,src:libpod] autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2 Warning: Unknown package 'src:golang-github-containernetworking-plugin' Marked as found in versions libpod/3.4.1+ds1-2. Warning: Unknown package 'src:golang-github-containernetworking-plugin' > thanks Stopping processing here. Please contact me if you need assistance. -- 998449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998449: golang-github-containernetworking-plugins breaks libpod autopkgtest
reassign 998449 src:golang-github-containernetworking-plugin,src:libpod found 998449 golang-github-containernetworking-plugins/0.9.1-1 found 998449 libpod/3.4.1+ds1-2 thanks Hi, I'm seeing this bug as caused by the golang-github-containernetworking-plugin upload in the excuses of that package. Hence [1] reassigning to both. Paul [1] https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation OpenPGP_signature Description: OpenPGP digital signature
Bug#994239: micropython: diff for NMU version 1.17+ds-1.1
Control: tags 994239 + patch Control: tags 994239 + pending Dear maintainer, I've prepared an NMU for micropython (versioned as 1.17+ds-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru micropython-1.17+ds/debian/changelog micropython- 1.17+ds/debian/changelog --- micropython-1.17+ds/debian/changelog2021-09-04 02:41:03.0 -0400 +++ micropython-1.17+ds/debian/changelog2021-11-10 15:51:19.0 -0500 @@ -1,3 +1,11 @@ +micropython (1.17+ds-1.1) unstable; urgency=high + + * Non-maintainer upload. + * debian/rules: Circumvent FTBFS with gcc 11 using +-Wno-error=maybe-uninitialized cflag. (Closes: #994239) + + -- Boyuan Yang Wed, 10 Nov 2021 15:51:19 -0500 + micropython (1.17+ds-1) unstable; urgency=medium * New upstream release diff -Nru micropython-1.17+ds/debian/rules micropython-1.17+ds/debian/rules --- micropython-1.17+ds/debian/rules2021-09-04 02:41:03.0 -0400 +++ micropython-1.17+ds/debian/rules2021-11-10 15:51:19.0 -0500 @@ -3,7 +3,7 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-format -export DEB_CFLAGS_MAINT_APPEND = -Wformat -Werror=format-security +export DEB_CFLAGS_MAINT_APPEND = -Wformat -Werror=format-security -Wno- error=maybe-uninitialized export DEB_LDFLAGS_MAINT_APPEND = export BUILD_VERBOSE = 1 signature.asc Description: This is a digitally signed message part
Processed: micropython: diff for NMU version 1.17+ds-1.1
Processing control commands: > tags 994239 + patch Bug #994239 [src:micropython] work around ftbfs with GCC 11 Added tag(s) patch. > tags 994239 + pending Bug #994239 [src:micropython] work around ftbfs with GCC 11 Added tag(s) pending. -- 994239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: Acknowledgement (firefox freezes shortly after start)
On Wed, 10 Nov 2021 00:59:02 +0100 Christoph Anton Mitterer wrote: > Not sure if this is related, but since a while I've noted even bigger > than the usual performance problems of firefox... > > Crackling sound is something I've heard for a month now... but since > about FF93 came out CPU utilisation seems to be much higher. > I just load simple webpages and may CPU goes up to 70-80°C. > > Anyone else seen this, too? > This is offtopic for the bug, but: Other way round for me. some version around 92 i see huge speed up, at least for youtube. seems before that it was sotwareish (typically 1080p took around 300% cpu) now it is around 130% for all processes. Firefox for the first time in 6 years on same hw could play 4k on intel. I spent some time investigating my 300% before, and learned a lot - that they enabling va-api and etc. slowness/fastness seems depend on the content you trying, configuration of your hardware, etc etc discussion would be way out of scope of this bug.
Bug#999422: Deluge fails with ModuleNotFoundError
Package: deluge
Version: 2.0.3-3.1
Severity: grave
When starting Deluge it fails when it attempts to import deluge.libtorrent.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/deluge/_libtorrent.py", line 23, in
import deluge.libtorrent as lt
ModuleNotFoundError: No module named 'deluge.libtorrent'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/deluged", line 33, in
sys.exit(load_entry_point('deluge==2.0.3', 'console_scripts',
'deluged')())
File "/usr/lib/python3/dist-packages/deluge/core/daemon_entry.py",
line 90, in start_daemon
from deluge.core.daemon import is_daemon_running
File "/usr/lib/python3/dist-packages/deluge/core/daemon.py", line 22,
in
from deluge.core.core import Core
File "/usr/lib/python3/dist-packages/deluge/core/core.py", line 28,
in
from deluge._libtorrent import LT_VERSION, lt
File "/usr/lib/python3/dist-packages/deluge/_libtorrent.py", line 25,
in
import libtorrent as lt
ImportError: /lib/arm-linux-gnueabihf/libtorrent-rasterbar.so.10:
undefined symbol: __atomic_fetch_add_8
OpenPGP_0xCB52D8AAC4292B05.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#988462: A little more info please?
On 2021-11-09 19:26, Chris Carr wrote: > - please could you explain why it is not suitable for inclusion in > bullseye? What is it that I am not seeing or experiencing in my daily > use of it? Problem is, that Trac (up to version 1.4) used to be a Python 2 program. Python 2 is not supported anymore (or only in a very limited way), so many dependencies for Trac are removed from Debian. It was impossible to keep Trac with Python 2 in Debian. Now Trac (>= 1.5) is based on Python 3, but the new code is not yet considered stable by upstream. I hoped, that there were a Trac release 1.6 just in time for Debian 11, e.g. around 2021-01, but Trac development happens a little bit slower even than Debians. > Also, please could you recommend an alternative ticket management > package that is included in bullseye. Preferably one that will import > my trac db so I don't have to re-enter 11 years of history. If Trac works fine for you (it does for me!), just stay with Debian 10, e.g. in a systemd-nspawn or docker container. That's what we do in my company: We run a server with Debian 11 and a systemd-nspawn container of Debian 10 with Trac and PostgreSQL on it. As soon as Trac 1.6 is released, I'll try to get it into Debian, as well as some of the plugins, and hopefully it will be part of Debian 12. Cheers
Bug#995655: dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143
Simon, any news here? Would you mind if I prepare an NMU with 26bbf5a314d833beaf0f147d24409969f05f3dba ? Regards, Michael On Sun, 3 Oct 2021 21:32:53 +0200 Michael Biebl wrote: > Control: reassign -1 dnsmasq/2.86-1 > > It's a (known) regression in dnsmasq 2.86-1 > > CCing what I sent Simon privately a couple of days ago > > > Hi Simon, > > > > as you probably know, the recent update of dnsmasq 2.86 to unstable broke the systemd autopkgtests, namely test-networkd.py, and more specifically > > > > == > > ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) > > resolved: domain-restricted DNS servers > > -- > > Traceback (most recent call last): > > File "/tmp/autopkgtest- lxc.knebmh6r/downtmp/build.00t/src/test/networkd-test.py", line 659, in test_resolved_domain_restricted_dns > > out = subprocess.check_output(['resolvectl', 'query', 'search.example.com']) > > File "/usr/lib/python3.9/subprocess.py", line 424, in check_output > > return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, > > File "/usr/lib/python3.9/subprocess.py", line 528, in run > > raise CalledProcessError(retcode, process.args, > > subprocess.CalledProcessError: Command '['resolvectl', 'query', 'search.example.com']' returned non-zero exit status 1. > > > > -- > > Ran 35 tests in 143.025s > > > > FAILED (errors=1, skipped=2) > > > > > > Afaics, this is a regression introduced by > > https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=12a9aa7c628e2d7dcd34949603848a3fb53fce9c > > > > and should be fixed by > > https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=26bbf5a314d833beaf0f147d24409969f05f3dba > > > > Am 03.10.21 um 19:23 schrieb Paul Gevers: > > Source: dnsmasq, systemd > > Control: found -1 dnsmasq/2.86-1 > > Control: found -1 systemd/247.9-1 > > Severity: serious > > Tags: sid bookworm > > X-Debbugs-CC: debian...@lists.debian.org > > User: debian...@lists.debian.org > > Usertags: breaks needs-update > > > > Dear maintainer(s), > > > > With a recent upload of dnsmasq the autopkgtest of systemd fails in > > testing when that autopkgtest is run with the binary packages of dnsmasq > > from unstable. It passes when run with only packages from testing. In > > tabular form: > > > > pass fail > > dnsmasq from testing 2.86-1 > > systemd from testing 247.9-1 > > all others from testing from testing > > > > I copied some of the output at the bottom of this report. signature.asc Description: This is a digitally signed message part
Bug#997940: marked as done (view3dscene: FTBFS with fpc 3.2.2)
Your message dated Wed, 10 Nov 2021 18:38:33 +0100 with message-id and subject line Re: view3dscene: FTBFS with fpc 3.2.2 has caused the Debian Bug report #997940, regarding view3dscene: FTBFS with fpc 3.2.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: view3dscene Version: 3.18.0-4 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer view3dscene fails to build from source since fpc 3.2.2 was uploaded to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham fpc -k"-z relro -z now" -dRELEASE -Mobjfpc -Sh -Ci -Sm -Sc -Sg -Si -O2 -Xs -Fu/usr/lib/x86_64-linux-gnu/fp-units-3.2.2/castle-game-engine-6.4/ code/view3dscene.lpr Compiling Release Version Free Pascal Compiler version 3.2.2+dfsg-3 [2021/10/23] for x86_64 Copyright (c) 1993-2021 by Florian Klaempfl and others Target OS: Linux for x86-64 Compiling code/view3dscene.lpr view3dscene.lpr(55,3) Fatal: Can't find unit CastleUtils used by view3dscene Fatal: Compilation aborted Error: /usr/bin/ppcx64 returned an error exitcode --- End Message --- --- Begin Message --- Control: fixed -1 4.0.0-1 detection of units path was wrong for CGE alpha versions. This was fixed in 4.0.0-1. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#997565: marked as done (golang-github-xeipuuv-gojsonschema: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/xeipuuv/gojsonschema returned exit code 1)
Your message dated Wed, 10 Nov 2021 17:34:34 + with message-id and subject line Bug#997565: fixed in golang-github-xeipuuv-gojsonschema 1.2.0-2 has caused the Debian Bug report #997565, regarding golang-github-xeipuuv-gojsonschema: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/xeipuuv/gojsonschema returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-xeipuuv-gojsonschema Version: 1.2.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package golang-github-xeipuuv-gojsonschema > dpkg-buildpackage: info: source version 1.2.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Shengjing Zhu > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=golang --with=golang >dh_auto_clean -O--buildsystem=golang >dh_autoreconf_clean -O--buildsystem=golang >dh_clean -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-xeipuuv-gojsonschema using existing > ./golang-github-xeipuuv-gojsonschema_1.2.0.orig.tar.gz > dpkg-source: info: building golang-github-xeipuuv-gojsonschema in > golang-github-xeipuuv-gojsonschema_1.2.0-1.debian.tar.xz > dpkg-source: info: building golang-github-xeipuuv-gojsonschema in > golang-github-xeipuuv-gojsonschema_1.2.0-1.dsc > debian/rules binary > dh binary --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/xeipuuv/gojsonschema > internal/unsafeheader > internal/goexperiment > internal/cpu > runtime/internal/atomic > internal/abi > runtime/internal/sys > runtime/internal/math > internal/race > sync/atomic > unicode/utf8 > unicode > internal/bytealg > encoding > math/bits > internal/itoa > unicode/utf16 > math > internal/nettrace > container/list > runtime > crypto/internal/subtle > crypto/subtle > vendor/golang.org/x/crypto/cryptobyte/asn1 > vendor/golang.org/x/crypto/internal/subtle > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > runtime/cgo > errors > sort > io > strconv > internal/oserror > syscall > bytes > reflect > path > strings > vendor/golang.org/x/net/dns/dnsmessage > internal/syscall/unix > time > internal/syscall/execenv > bufio > encoding/binary > internal/fmtsort > internal/poll > io/fs > context > encoding/base64 > hash > crypto/cipher > hash/crc32 > crypto > os > crypto/elliptic/internal/fiat > crypto/internal/randutil > crypto/aes > crypto/des > crypto/sha512 > crypto/ed25519/internal/edwards25519/field > crypto/hmac > crypto/md5 > fmt > path/filepath > io/ioutil > net > crypto/ed25519/internal/edwards25519 > crypto/rc4 > crypto/sha1 > crypto/sha256 > encoding/pem > encoding/json > github.com/xeipuuv/gojsonpointer > net/url > log > math/big > github.com/xeipuuv/gojsonreference > compress/flate > encoding/hex > vendor/golang.org/x/crypto/chacha20 > compress/gzip > vendor/golang.org/x/crypto/poly1305 > vendor/golang.org/x/sys/cpu > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/crypto/chacha20poly1305 > vendor/golang.org/x/crypto/hkdf > vendor/golang.org/x/text/transform > crypto/rand > crypto/elliptic > encoding/asn1 > crypto/ed25519 > crypto/rsa > crypto/dsa > vendor/golang.org/x/text/unicode/bidi > vendor/golang.org/x/text/unicode/norm > vendor/golang.org/x/crypto/cryptobyte > crypto/x509/pkix > crypto/ecdsa > vendor/golang.org/x/text/secure/bidirule > vendor/golang.org/x/net/http2/hpack > mime > vendor/golang.org/x/net/idna > mime/quotedprintable > net/http/internal > crypto/x509 > net/textproto > net/http/internal/ascii > regexp/syntax > vendor/golang.org/x/net/http/httpproxy > vendor/golang.org/x/net/http/httpguts > mime/multipart > net/mail > text/template/parse > regexp > crypto/tls > text/template >
Bug#984372: marked as done (tripwire: ftbfs with GCC-11)
Your message dated Wed, 10 Nov 2021 17:35:31 + with message-id and subject line Bug#984372: fixed in tripwire 2.4.3.7-4 has caused the Debian Bug report #984372, regarding tripwire: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tripwire Version: 2.4.3.7-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/tripwire_2.4.3.7-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 404 | enum class byte : unsigned char; | ^~~~ In file included from pch.h:4, from integer.cpp:3: config.h:85:23: note: ‘typedef unsigned char byte’ 85 | typedef unsigned char byte; | ^~~~ integer.cpp:1438:6: error: no declaration matches ‘void Integer::BERDecode(const int*)’ 1438 | void Integer::BERDecode(const byte *input) | ^~~ In file included from integer.cpp:4: integer.h:169:14: note: candidates are: ‘void Integer::BERDecode(BufferedTransformation&)’ 169 | void BERDecode(BufferedTransformation ); | ^ integer.h:167:14: note: ‘void Integer::BERDecode(const byte*)’ 167 | void BERDecode(const byte *input); | ^ integer.h:16:7: note: ‘class Integer’ defined here 16 | class Integer | ^~~ integer.cpp: In member function ‘void Integer::BERDecode(BufferedTransformation&)’: integer.cpp:1459:5: error: reference to ‘byte’ is ambiguous 1459 | byte b; | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/bits/char_traits.h:39, from /usr/include/c++/11/string:40, from cryptlib.h:11, from integer.h:4, from integer.cpp:4: /usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’ 404 | enum class byte : unsigned char; | ^~~~ In file included from pch.h:4, from integer.cpp:3: config.h:85:23: note: ‘typedef unsigned char byte’ 85 | typedef unsigned char byte; | ^~~~ integer.cpp:1460:17: error: ‘b’ was not declared in this scope; did you mean ‘bt’? 1460 | if (!bt.Get(b) || b != INTEGER) | ^ | bt integer.cpp: In member function ‘void Integer::Randomize(RandomNumberGenerator&, unsigned int)’: integer.cpp:1478:29: error: reference to ‘byte’ is ambiguous 1478 | buf[(unsigned int)0] = (byte)Crop(buf[(unsigned int)0], nbits % 8); | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/bits/char_traits.h:39, from /usr/include/c++/11/string:40, from cryptlib.h:11, from integer.h:4, from integer.cpp:4:
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
Control: tag -1 patch On Wed, Nov 10, 2021 at 7:55 AM Shengjing Zhu wrote: > > > > Cloud you backport following commit? > > > > > > > https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b > > > > > This patch updates libocispec/Makefile.am, which is needed to be > backported. > > This patch looks like doing nothing to C part, because the generated source > is removed in upstream repo. Theses files(which are added in Makefile.am) > can > be generated by `make -C libocispec generate`. So please also uncomment > this > line in debian/rules. > > > D'oh, my bad, I've overlooked the Makefile.am parts. So the generator *is* already invoked, but the automake system doesn't pick up all files, leading to the linker failures. I've implemented your suggestion in https://salsa.debian.org/debian/crun/-/merge_requests/1/diffs and can confirm that the package now builds fine. Dmitry, please let me know if you are comfortable with me NMU'ing the package with the patch from salsa. -- regards, Reinhard
Processed: Re: Vendoring image-spec and runtime-spec seem to be the issue
Processing control commands: > tag -1 patch Bug #997225 [src:crun] crun: FTBFS: ./libocispec/src/runtime_spec_schema_config_schema.c:2661: undefined reference to `gen_runtime_spec_schema_config_zos' Added tag(s) patch. -- 997225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988462: Apologies
Sorry, the second copy of my previous email was actually sent first, from a defunct email account, I had accidentally set the From field wrong. Apologies for the duplication.
Bug#998894: marked as done (wlcs FTBFS with GTest 1.11)
Your message dated Wed, 10 Nov 2021 16:48:57 + with message-id and subject line Bug#998894: fixed in wlcs 1.3.0-3 has caused the Debian Bug report #998894, regarding wlcs FTBFS with GTest 1.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wlcs Version: 1.2.1-1 Severity: serious Tags: ftbfs bookworm sid Forwarded: https://github.com/MirServer/wlcs/issues/205 https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/wlcs.html ... /src/version_specifier.cpp.o -c /build/wlcs-1.2.1/src/version_specifier.cpp /build/wlcs-1.2.1/tests/pointer_constraints.cpp:45:5: error: reference to 'Pointer' is ambiguous 45 | Pointer cursor = the_server().create_pointer(); | ^~~ ... wlcs builds with the two commits from the issue linked above applied. --- End Message --- --- Begin Message --- Source: wlcs Source-Version: 1.3.0-3 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of wlcs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated wlcs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Nov 2021 17:03:08 +0100 Source: wlcs Architecture: source Version: 1.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Mir Team Changed-By: Mike Gabriel Closes: 998894 Changes: wlcs (1.3.0-3) unstable; urgency=medium . [ Marius Gripsgard ] * debian/patches: + Add 0001-cmake-always-set-GTEST_LIBRARY-if-it-isn-t.patch and 0002-Fix-build-when-using-GTest-1.11.patch. Fix FTBFS (cmake: always set GTEST_LIBRARY if it isn't; fix build when using GTest-1.11). (Closes: #998894). . [ Debian Janitor ] * debian/upstream/metadata: + Set upstream metadata fields: Repository. + Remove obsolete field Name from debian/upstream/metadata (already present in machine-readable debian/copyright). . [ Mike Gabriel ] * debian/copyright: + Update copyright attributions. Checksums-Sha1: c3576e9de2eab4da4c7e8f9e3129ec690b63bebc 2273 wlcs_1.3.0-3.dsc a7cd8b77048b19cf12eedbf2998dee4219dc3dd7 14548 wlcs_1.3.0-3.debian.tar.xz 46f9800743247266b43fcde9e939f6178ebbaaa3 7229 wlcs_1.3.0-3_source.buildinfo Checksums-Sha256: ee6b6ed783c150a246aa82afec5df53ff2fef18a02b002f0205a3f12f1b427da 2273 wlcs_1.3.0-3.dsc 93b720ca6413bdf4fdcc2654941a2e37eefca6547e97a16abe532282275091bb 14548 wlcs_1.3.0-3.debian.tar.xz 519539ea02ca14b4da23e664d29a6f9c60d087898c01e24d41c00f4348fbd14b 7229 wlcs_1.3.0-3_source.buildinfo Files: 282969b272243f9d83b615cf1f140d4d 2273 devel optional wlcs_1.3.0-3.dsc c873449b16618617ba8085b6580eea11 14548 devel optional wlcs_1.3.0-3.debian.tar.xz 4f5e9cf29c385018e3a6a5b22171ac12 7229 devel optional wlcs_1.3.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmGL8s4VHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxzpUP/3CAq34skE2eWle7leNIPtTqOGCo fK7xat42wNd61Msqn40Gb6Enpxx/FVy5nFEGeH/n1cJbYdBOJiOKiLBKGn8iUj6S SKymNwpwDyKyc9QySqDAXAfYf7rhuf0COTqSiJgn371tcfFvC4su/1WcEjBcIWUG Ybf4XRTmFT4fiHi6zShzHAYQUPz88wicmtIWKfAN7/0vOKOuD17ge4+Dt/zywLqY tFf9exgxDhbDJP/Ris2VUChBw9GgwrWrDBTYJw1NKlZ1lJ87lVPxw1cIUxrjudr6 dAaCpGEw5XPwgkRiMxIwBSYlJvkcmDbEdkZXLih5B6wNAov3IWH/ZWvNxobvdRN+ u33Va7q16hJ7w2mmP6d1oyz93KKcfHVK+aIOVvJfNbAF3xYQtT6FL3hfT5ZG4nB+ DLxwgwatWB+oAJ4Ueo7c0VDrsgt4zKZ0jdI37QsHE8yZcMwcUhMQJagwsT9faAhQ Yq1WPS7GRur1IoGkimYwEUHuIkQMu+ChGwtSWkl/uUTTOrpMNd5P0qhgTsVA3JkT abf6laPVUXyycGQ72hrPL/JWjguIGTNbiXa8PYQZcGTr3CImK2ELa4BQNBXtDYE4 2/1qHLZFQ2MVYRzU37QsLJQ1a8Bnoyx0SokpdQ11WKzfZvuCJfqBtWARtFm0wJdh n9cR5AW+NNPAAYr4 =bmNx -END PGP SIGNATURE End Message ---
Processed: Re: Bug#998854: undefined symbol: _PyUnicode_DecodeUnicodeEscape
Processing control commands: > reassign -1 python3-typed-ast Bug #998854 [python3.9] undefined symbol: _PyUnicode_DecodeUnicodeEscape Bug reassigned from package 'python3.9' to 'python3-typed-ast'. No longer marked as found in versions python3.9/3.9.8-1. Ignoring request to alter fixed versions of bug #998854 to the same values previously set > severity -1 serious Bug #998854 [python3-typed-ast] undefined symbol: _PyUnicode_DecodeUnicodeEscape Severity set to 'serious' from 'important' -- 998854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998414: marked as done (mimeo: autopkgtest regression: test depends on postgresql-14-pgtap which doesn't exist (yet))
Your message dated Wed, 10 Nov 2021 17:05:30 +0100 with message-id and subject line Re: Bug#998414: mimeo: autopkgtest regression: test depends on postgresql-14-pgtap which doesn't exist (yet) has caused the Debian Bug report #998414, regarding mimeo: autopkgtest regression: test depends on postgresql-14-pgtap which doesn't exist (yet) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mimeo Version: 1.5.1-11 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of mimeo the autopkgtest of mimeo fails in testing when that autopkgtest is run with the binary packages of mimeo from unstable. It passes when run with only packages from testing. In tabular form: passfail mimeo from testing1.5.1-11 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems you need to fix bug #997762 (in pgtap) first. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=mimeo https://ci.debian.net/data/autopkgtest/testing/amd64/m/mimeo/16383770/log.gz autopkgtest [22:48:37]: apt-source mimeo Get:1 http://deb.debian.org/debian unstable/main mimeo 1.5.1-11 (dsc) [2,054 B] Get:2 http://deb.debian.org/debian unstable/main mimeo 1.5.1-11 (tar) [591 kB] Get:3 http://deb.debian.org/debian unstable/main mimeo 1.5.1-11 (diff) [3,400 B] gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/tmp/dpkg-verify-sig.2uqyXVyi/trustedkeys.kbx': General error gpgv: Signature made Thu 28 Oct 2021 08:44:44 AM UTC gpgv:using RSA key 5C48FE6157F49179597087C64C5A6BAB12D2A7AE gpgv: Can't check signature: No public key dpkg-source: warning: failed to verify signature on ./mimeo_1.5.1-11.dsc autopkgtest [22:48:38]: testing package mimeo version 1.5.1-11 autopkgtest [22:48:38]: build not needed autopkgtest [22:48:38]: test prove: preparing testbed Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib > Broken autopkgtest-satdep:amd64 Depends on postgresql-14-pgtap:amd64 < none @un H > Removing autopkgtest-satdep:amd64 because I can't find postgresql-14-pgtap:amd64 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: autopkgtest-satdep 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 13121 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest: WARNING: package postgresql-14-mimeo is not installed though it should be autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from unstable Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib > Broken autopkgtest-satdep:amd64 Depends on postgresql-14-pgtap:amd64 < none @un H > Removing autopkgtest-satdep:amd64 because I can't find postgresql-14-pgtap:amd64 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver
Bug#996781: marked as done (luarocks: Installation fails with dpkg error)
Your message dated Wed, 10 Nov 2021 15:34:14 + with message-id and subject line Bug#996781: fixed in luarocks 3.8.0+dfsg1-1 has caused the Debian Bug report #996781, regarding luarocks: Installation fails with dpkg error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: luarocks Version: 3.7.0+dfsg1-1 Severity: grave Justification: renders package unusable Hi, thanks for reviving the package. Now I'm getting this when attempting to install however: Error: Cannot access repository at /root/.luarocks/lib/luarocks/rocks-5.3 dpkg: error processing package luarocks (--configure): installed luarocks package post-installation script subprocess returned error exit status 1 luarocks.postinst: mkdir -p /usr/local/lib/luarocks/rocks/ luarocks-admin make_manifest --local-tree <--- Using local-tree here is probably wrong. Regards, Oliver Versions of packages luarocks depends on: ii liblua5.3-dev 5.3.6-1 ii lua-any27 ii lua5.3 5.3.6-1 ii unzip 6.0-26 ii wget 1.21.2-2+b1 ii zip3.0-12 Versions of packages luarocks recommends: ii lua-sec 1.0.1-1 luarocks suggests no packages. --- End Message --- --- Begin Message --- Source: luarocks Source-Version: 3.8.0+dfsg1-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of luarocks, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated luarocks package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 15:35:37 +0100 Source: luarocks Architecture: source Version: 3.8.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Lua Team Changed-By: Jérémy Lal Closes: 996781 Changes: luarocks (3.8.0+dfsg1-1) unstable; urgency=medium . * New upstream version 3.8.0+dfsg1 * Basic test, thanks Chris MacNaughton * Support multiple lua versions in /usr/local (Closes:#996781) * Lessen configuration flags, luarocks is smarter now. * Install /usr/bin/luarocks(-admin)-5.x helpers Checksums-Sha1: 17929917b6d4adc56adc27f78e601e989979e597 2041 luarocks_3.8.0+dfsg1-1.dsc 8ebf242ec38d3245531c647b67c6b35d78122519 188344 luarocks_3.8.0+dfsg1.orig.tar.xz 58483f45027bd5182cea5b44bf21d7aa4de0eccf 5348 luarocks_3.8.0+dfsg1-1.debian.tar.xz 25e54e8326cc13ab07b77a56c2231f767e69b5f1 7407 luarocks_3.8.0+dfsg1-1_source.buildinfo Checksums-Sha256: b0a6fecf25a4880641e2abc23c56da0a53dfed99c31db4fd685423c3fd869f57 2041 luarocks_3.8.0+dfsg1-1.dsc 6c691772a341d1873d9bcfb63c91ad0ae213df56a002067f1f9619a8f09e0f77 188344 luarocks_3.8.0+dfsg1.orig.tar.xz aff9b9dbb577a262fb9d2b0bfd8d7bad48f4f79bd08c7c5692dad22e309f6956 5348 luarocks_3.8.0+dfsg1-1.debian.tar.xz 96d5b680719a9927ebecf123d3c45c0c330c666771a1acdc25a95c931ca71a9b 7407 luarocks_3.8.0+dfsg1-1_source.buildinfo Files: c948193cc54390c9725d7457c1e4ec48 2041 interpreters optional luarocks_3.8.0+dfsg1-1.dsc 946886190e56c23eeb6ee16a569ec2b8 188344 interpreters optional luarocks_3.8.0+dfsg1.orig.tar.xz 7dc82f475b69bc9c76caf8af7ee970a9 5348 interpreters optional luarocks_3.8.0+dfsg1-1.debian.tar.xz 7d9e5337afb003adfa00267eb2b798c7 7407 interpreters optional luarocks_3.8.0+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmGL37oSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0KkYP/2f2VwhadxVAW46xtiGJq1vunTweZdoR 1f8YABWJo8cfu0ui9i0SCSUig3RFz4+9bk8CI4OLDP6Kx6o6p3OYH0ur6I5+BOjw w+RlzT1nZoy+C+PWt/cM3vo9N94ZeZixh8CGsBqzwEYcGW8TK224WosLaFfNVUMj HGHGAOFcIg1vTYDQI5C5ckJ3x7xR+Y68KLKCvyLHbRb0CE/zY4K3tdRkSke12Js4 FJ7Bb+uNCqjROmMy0jFrH4QwO1ico4iwdSDjMtziNU4YGcOO/sM3qlYhU6fMLrAt ChZIK+DxMfPWS8X7HWhtO9EZ/jcIPSbbok16SS+XnTwdv/tU2u6t0+sBzBYnQWyt ru7/zVA1UUtLBSbp9pGRmU1+dRBiWmbX6NFoMZPKTfnXSF/ZU6We2QkkSTKSDd9f zsep6WEGEDCfZXoXjcKt4pKeQiuoUzTCmMSNYVkbzcrqOeoQg0D8gLiB9AWK85B3 h0Uy5a5namCqahaRHpAb8d7jK0fItBF0Zeyv49JcVdf+YLhkg8xwoBiHfsHgnq2O
Bug#996931: marked as done (python3-django needs Breaks for the bullseye lava-server)
Your message dated Wed, 10 Nov 2021 15:22:37 + with message-id and subject line Bug#996931: fixed in python-django 2:3.2.9-2 has caused the Debian Bug report #996931, regarding python3-django needs Breaks for the bullseye lava-server to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django, lava Control: found -1 python-django/2:3.2.7-4 Control: found -1 lava/2020.12-5 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python-django the autopkgtest of lava fails in testing when that autopkgtest is run with the binary packages of python-django from unstable. It passes when run with only packages from testing. In tabular form: passfail python-django from testing2:3.2.7-4 lava from testing2020.12-5 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. The error message suggests a misconfiguration, but the fact that the test passed until now suggests that python-django used to be more forgiving which isn't nice to give up. Currently this regression is blocking the migration of python-django to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from python-django/2:3.2.7-4. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=python-django https://ci.debian.net/data/autopkgtest/testing/amd64/l/lava/15232624/log.gz lava-server manage migrate --noinput --fake-initial Traceback (most recent call last): File "/usr/bin/lava-server", line 68, in main() File "/usr/bin/lava-server", line 64, in main execute_from_command_line([sys.argv[0]] + options.command) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 419, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 413, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 354, in run_from_argv self.execute(*args, **cmd_options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 398, in execute output = self.handle(*args, **options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 86, in wrapped saved_locale = translation.get_language() File "/usr/lib/python3/dist-packages/django/utils/translation/__init__.py", line 254, in get_language return _trans.get_language() File "/usr/lib/python3/dist-packages/django/utils/translation/__init__.py", line 57, in __getattr__ if settings.USE_I18N: File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 82, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 69, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 190, in __init__ raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: PASSWORD_RESET_TIMEOUT_DAYS/PASSWORD_RESET_TIMEOUT are mutually exclusive. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-django Source-Version: 2:3.2.9-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of python-django, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio
Bug#983618: marked as done (python3-django 3.2 breaks python3-django-pyscss)
Your message dated Wed, 10 Nov 2021 15:22:37 + with message-id and subject line Bug#983618: fixed in python-django 2:3.2.9-2 has caused the Debian Bug report #983618, regarding python3-django 3.2 breaks python3-django-pyscss to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-zaqar-ui Version: 9.0.0~rc1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + src:horizon src:zaqar-ui Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Setting up openstack-dashboard (3:18.6.1-1) ... Warning: Could not import Horizon dependencies. This is normal during installation. RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().Traceback (most recent call last): File "/usr/share/openstack-dashboard/manage.py", line 23, in execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 419, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 395, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 91, in populate app_config = AppConfig.create(entry) File "/usr/lib/python3/dist-packages/django/apps/config.py", line 224, in create import_module(entry) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1030, in _gcd_import File "", line 1007, in _find_and_load File "", line 986, in _find_and_load_unlocked File "", line 680, in _load_unlocked File "", line 790, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/django_pyscss/__init__.py", line 1, in from .compiler import DjangoScssCompiler # NOQA File "/usr/lib/python3/dist-packages/django_pyscss/compiler.py", line 6, in from django.utils.six.moves import StringIO ModuleNotFoundError: No module named 'django.utils.six' dpkg: error processing package openstack-dashboard (--configure): installed openstack-dashboard package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of python3-zaqar-ui: python3-zaqar-ui depends on openstack-dashboard (>= 3:17.1.0); however: Package openstack-dashboard is not configured yet.
Bug#998542: marked as done (devscripts: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2)
Your message dated Wed, 10 Nov 2021 15:19:02 + with message-id and subject line Bug#998542: fixed in devscripts 2.21.5 has caused the Debian Bug report #998542, regarding devscripts: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: devscripts Version: 2.21.4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/scripts' > perl -I ../lib -c bts; \ > > perl -I ../lib -c build-rdeps; \ > > perl -I ../lib -c chdist; \ > > perl -I ../lib -c checkbashisms; \ > > checkbashisms syntax OK > perl -I ../lib -c cvs-debuild; \ > > build-rdeps syntax OK > perl -I ../lib -c dd-list; \ > > chdist syntax OK > cvs-debuild syntax OK > perl -I ../lib -c deb-why-removed; \ > > perl -I ../lib -c debc; \ > > dd-list syntax OK > perl -I ../lib -c debchange; \ > > debc syntax OK > perl -I ../lib -c debcheckout; \ > > bts syntax OK > perl -I ../lib -c debcommit; \ > > deb-why-removed syntax OK > perl -I ../lib -c debdiff; \ > > debchange syntax OK > debcommit syntax OK > perl -I ../lib -c debi; \ > > perl -I ../lib -c debpkg; \ > > debpkg syntax OK > perl -I ../lib -c debrebuild; \ > > debdiff syntax OK > perl -I ../lib -c debsnap; \ > > debcheckout syntax OK > perl -I ../lib -c debuild; \ > > debi syntax OK > perl -I ../lib -c dep3changelog; \ > > debsnap syntax OK > debuild syntax OK > dep3changelog syntax OK > perl -I ../lib -c desktop2menu; \ > > perl -I ../lib -c dget; \ > > perl -I ../lib -c dpkg-depcheck; \ > > desktop2menu syntax OK > perl -I ../lib -c dscverify; \ > > dpkg-depcheck syntax OK > perl -I ../lib -c git-deborig; \ > > dget syntax OK > debrebuild syntax OK > perl -I ../lib -c grep-excuses; \ > > perl -I ../lib -c hardening-check; \ > > grep-excuses syntax OK > perl -I ../lib -c mass-bug; \ > > dscverify syntax OK > perl -I ../lib -c mk-build-deps; \ > > mass-bug syntax OK > perl -I ../lib -c mk-origtargz; \ > > hardening-check syntax OK > perl -I ../lib -c namecheck; \ > > git-deborig syntax OK > perl -I ../lib -c origtargz; \ > > namecheck syntax OK > perl -I ../lib -c plotchangelog; \ > > mk-build-deps syntax OK > perl -I ../lib -c rc-alert; \ > > origtargz syntax OK > perl -I ../lib -c rmadison; \ > > plotchangelog syntax OK > perl -I ../lib -c salsa; \ > > rmadison syntax OK > perl -I ../lib -c svnpath; \ > > mk-origtargz syntax OK > perl -I ../lib -c tagpending; \ > > svnpath syntax OK > perl -I ../lib -c transition-check; \ > > rc-alert syntax OK > perl -I ../lib -c uscan; \ > > transition-check syntax OK > perl -I ../lib -c who-permits-upload; \ > > tagpending syntax OK > bash -n annotate-output > bash -n archpath > bash -n cowpoke > bash -n cvs-debi > bash -n cvs-debrelease > bash -n dcmd > bash -n deb-reversion > bash -n debclean > bash -n debrelease > bash -n debrepro > bash -n debrsign > bash -n debsign > bash -n diff2patches > bash -n dpkg-genbuilddeps > bash -n dscextract > bash -n edit-patch > bash -n getbuildlog > bash -n list-unreleased > bash -n ltnu > bash -n manpage-alert > bash -n mergechanges > bash -n nmudiff > bash -n pts-subscribe > bash -n run_bisect > who-permits-upload syntax OK > bash -n run_bisect_qemu > bash -n uupdate > bash -n what-patch > bash -n who-uploads > bash -n whodepends > bash -n wnpp-alert > bash -n wnpp-check > py3versions: no X-Python3-Version in control file, using supported versions > python3.9 setup.py test > salsa syntax OK > uscan syntax OK > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating devscripts.egg-info > writing devscripts.egg-info/PKG-INFO > writing dependency_links to devscripts.egg-info/dependency_links.txt > writing top-level names to devscripts.egg-info/top_level.txt > writing manifest file 'devscripts.egg-info/SOURCES.txt' > reading manifest file 'devscripts.egg-info/SOURCES.txt' > writing manifest file 'devscripts.egg-info/SOURCES.txt' > running build_ext > testArgs (devscripts.test.test_logger.LoggerTestCase) ... ok > testCommand (devscripts.test.test_logger.LoggerTestCase) ... ok > testNoArgs
Processed: Bug#983618 marked as pending in python-django
Processing control commands: > tag -1 pending Bug #983618 [python3-django] python3-django 3.2 breaks python3-django-pyscss Added tag(s) pending. -- 983618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983618: marked as pending in python-django
Control: tag -1 pending Hello, Bug #983618 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/5d11c2460b21da8c2c832b5808e5070a2803b7e5 Add Breaks: on python-django-pyscss << 2.0.2-10 The issue has been fixed in that version of python-django-pyscss Closes: #983618 (this message was generated automatically) -- Greetings https://bugs.debian.org/983618
Bug#998911: node-string-width: file conflict with node-slice-ansi
yep, that, sorry. I mean it's missing a Replaces. On Wed, Nov 10, 2021 at 3:24 PM Axel Beckert wrote: > > Hi Mattia, > > Mattia Rizzolo wrote: > > Control: reopen -1 > > > > On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote: > > > I also noticed just now that I got it the wrong way around in that > > > comment: These headers need to go into node-slice-ansi, not into > > > node-string-width. But luckily Mattia got it right: > > > > > > Mattia Rizzolo wrote: > > > > Without too many checks, I believe node-slice-ansi should have a > > > > Breaks+Replace: node-string-width (<< 4.2.3+~9.2.2-1) > > > > I also noticed that the last upload seems to have added Breaks but not > > Conflicts. I don't think that's enough (haven't tested). > > I think you mean "Replaces". Breaks and Conflicts are AFAIK "either or". > > Regards, Axel > -- > ,''`. | Axel Beckert , https://people.debian.org/~abe/ > : :' : | Debian Developer, ftp.ch.debian.org Admin > `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 > `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo
Bug#996931: marked as pending in python-django
Control: tag -1 pending Hello, Bug #996931 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/55f258c3d1234700fd475b006ffabf0b911132e5 Add Breaks: on lava-server << 2021.11 The 2021.11 release will incorporate the needed changes to work with Django 3.2. Closes: #996931 (this message was generated automatically) -- Greetings https://bugs.debian.org/996931
Processed: Bug#996931 marked as pending in python-django
Processing control commands: > tag -1 pending Bug #996931 [python3-django] python3-django needs Breaks for the bullseye lava-server Added tag(s) pending. -- 996931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997150: marked as done (bitwise: FTBFS: src/interactive.c:117:17: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Wed, 10 Nov 2021 14:48:39 + with message-id and subject line Bug#997150: fixed in bitwise 0.43-1 has caused the Debian Bug report #997150, regarding bitwise: FTBFS: src/interactive.c:117:17: error: format not a string literal and no format arguments [-Werror=format-security] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bitwise Version: 0.42-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I./inc -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pedantic -c -o src/cmd.o src/cmd.c > src/interactive.c: In function ‘update_history_win’: > src/interactive.c:117:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 117 | mvwprintw(history_win, j, 2, history[history_pos - > i].line); > | ^ > src/interactive.c: In function ‘set_fields_width’: > src/interactive.c:176:44: warning: ‘min_field_distance’ may be used > uninitialized [-Wmaybe-uninitialized] > 176 | hex_pos = dec_pos + max_dec_digits + min_field_distance - 2; > | ~^~~~ > gcc -DHAVE_CONFIG_H -I. -I./inc -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pedantic -c -o src/stack.o src/stack.c > gcc -DHAVE_CONFIG_H -I. -I./inc -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pedantic -c -o src/shunting-yard.o > src/shunting-yard.c > gcc -DHAVE_CONFIG_H -I. -I./inc -Wdate-time -D_FORTIFY_SOURCE=2-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -pedantic -c -o src/help.o src/help.c > cc1: some warnings being treated as errors > make[1]: *** [Makefile:681: src/interactive.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/bitwise_0.42-1_unstable.log 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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: bitwise Source-Version: 0.43-1 Done: Ramon Fried We believe that the bug you reported is fixed in the latest version of bitwise, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ramon Fried (supplier of updated bitwise package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 14:38:23 +0200 Source: bitwise Architecture: source Version: 0.43-1 Distribution: unstable Urgency: medium Maintainer: Ramon Fried Changed-By: Ramon Fried Closes: 997150 Changes: bitwise (0.43-1) unstable; urgency=medium . * Fixed build warnings Closes: Bug#997150 * Add support for IPv4 in command line mode. Checksums-Sha1: 88ce21a3f60f7e268be6da54fcbdf19c6fe4a506 1580 bitwise_0.43-1.dsc 90a45c251cd505402b387070ff5fa9b2ace45815 127364 bitwise_0.43.orig.tar.gz 56aa4556777d5ddad67fb9b7f84e2b1e6a87b38b 2704 bitwise_0.43-1.debian.tar.xz 233daf91ae580a11508d128323a23c625eebdce3 5592 bitwise_0.43-1_source.buildinfo Checksums-Sha256: 8f006b0af83763c9d2fccef4d22265b6d82efb6438c63cee62f4a8cd5d8fbc5f 1580 bitwise_0.43-1.dsc f524f794188a10defc4df673d8cf0b3739f93e58e93aff0cdb8a99fbdcca2ffb 127364 bitwise_0.43.orig.tar.gz
Bug#998911: node-string-width: file conflict with node-slice-ansi
Hi Mattia, Mattia Rizzolo wrote: > Control: reopen -1 > > On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote: > > I also noticed just now that I got it the wrong way around in that > > comment: These headers need to go into node-slice-ansi, not into > > node-string-width. But luckily Mattia got it right: > > > > Mattia Rizzolo wrote: > > > Without too many checks, I believe node-slice-ansi should have a > > > Breaks+Replace: node-string-width (<< 4.2.3+~9.2.2-1) > > I also noticed that the last upload seems to have added Breaks but not > Conflicts. I don't think that's enough (haven't tested). I think you mean "Replaces". Breaks and Conflicts are AFAIK "either or". Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: node-string-width: file conflict with node-slice-ansi
Processing control commands:
> reopen -1
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-slice-ansi/5.0.0+~4.0.0-3 and
node-string-width/4.2.3+~9.2.2-1.
No longer marked as fixed in versions node-slice-ansi/5.0.0+~4.0.0-3 and
node-string-width/4.2.3+~9.2.2-1.
--
998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886
998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998911: node-string-width: file conflict with node-slice-ansi
Control: reopen -1 On Wed, Nov 10, 2021 at 03:01:11PM +0100, Axel Beckert wrote: > I also noticed just now that I got it the wrong way around in that > comment: These headers need to go into node-slice-ansi, not into > node-string-width. But luckily Mattia got it right: > > Mattia Rizzolo wrote: > > Without too many checks, I believe node-slice-ansi should have a > > Breaks+Replace: node-string-width (<< 4.2.3+~9.2.2-1) I also noticed that the last upload seems to have added Breaks but not Conflicts. I don't think that's enough (haven't tested). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: fixed 998886 in node-string-width/4.2.3+~9.2.2-1
Processing commands for cont...@bugs.debian.org:
> # Re-add fixed version again as well
> fixed 998886 node-string-width/4.2.3+~9.2.2-1
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
Marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
Marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886
998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 998886 in node-string-width/4.2.3+~9.2.2-1
Processing commands for cont...@bugs.debian.org:
> # Missing Breaks and Replaces headers were actually in node-slice-ansi, sorry
> for the confusion
> notfound 998886 node-string-width/4.2.3+~9.2.2-1
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
No longer marked as found in versions node-string-width/4.2.3+~9.2.2-1.
No longer marked as found in versions node-string-width/4.2.3+~9.2.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886
998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999360: libayatana-indicator_0.8.4-3_all-buildd.changes REJECTED
Source: libayatana-indicator Version: 0.8.4-2 Severity: serious On 2021-11-10 13:49, Debian FTP Masters wrote: > Version check failed: > Your upload included the binary package ayatana-indicator-common, version > 0.8.4-3, for all, > however testing already has version 0.9.5-1. > Uploads to unstable must have a higher version than present in testing. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#998911: node-string-width: file conflict with node-slice-ansi
Hi Yadd, Yadd wrote: > you reopened this bug, however node-string-width is really fixed in > version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ? I mentioned it in my mail which reopened the bug: | # Missing Breaks and Replaces headers in node-string-width/4.2.3+~9.2.2-1 | found 998886 node-string-width/4.2.3+~9.2.2-1 Sorry that it might have been it a bit hidden. Thought, it would be clear. Here's my original error: […] Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-PfhX58/103-node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1 Preparing to unpack .../104-node-spdx-exceptions_2.3.0-2_all.deb ... […] Note that 5.0.0+~4.0.0-2 only came in through that dependency in the newer node-string-width without these files. So yes, the file conflict is no more present, but this doesn't solve the issue alone. I also noticed just now that I got it the wrong way around in that comment: These headers need to go into node-slice-ansi, not into node-string-width. But luckily Mattia got it right: Mattia Rizzolo wrote: > Without too many checks, I believe node-slice-ansi should have a > Breaks+Replace: node-string-width (<< 4.2.3+~9.2.2-1) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#998911: marked as done (node-string-width: file conflict with node-slice-ansi)
Your message dated Wed, 10 Nov 2021 13:34:59 + with message-id and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-3 has caused the Debian Bug report #998886, regarding node-string-width: file conflict with node-slice-ansi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-string-width Version: 4.2.3+~3.0.0+~9.2.2-1 Severity: serious Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-DvqJPE/12-node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1 --- End Message --- --- Begin Message --- Source: node-slice-ansi Source-Version: 5.0.0+~4.0.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-slice-ansi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-slice-ansi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 14:17:05 +0100 Source: node-slice-ansi Architecture: source Version: 5.0.0+~4.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 998886 Changes: node-slice-ansi (5.0.0+~4.0.0-3) unstable; urgency=medium . * Team upload * Add Breaks node-string-width < 4.2.3+~9.2.2-1 (Closes: #998886) Checksums-Sha1: 82fb142bb24fb454eb676b5ef4ce15ad74b3b157 2498 node-slice-ansi_5.0.0+~4.0.0-3.dsc acbe219f60a2768e6ce853279ae6dfe6f0435d4a 3372 node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz Checksums-Sha256: 14e9b9b067792ababc3854e21a61076954a6c9032f22d24e4452765b17d96ccb 2498 node-slice-ansi_5.0.0+~4.0.0-3.dsc 443955ec47b139016b5c1e28af067dd4d91fc45420d7c9be50e49cdcb626aadb 3372 node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz Files: 64fb356fbf9f52eaf6f9d37600800b48 2498 javascript optional node-slice-ansi_5.0.0+~4.0.0-3.dsc f06562b7758020e64725c69d60035878 3372 javascript optional node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGLxpoACgkQ9tdMp8mZ 7uk/8Q/9HmHlRqSD04IFMZS1sGSRPkvcbD/b38g7kIxjtYaoVY13Jsfv5CzvgIPh LkkTUS+1O/aW9sA3GUlirp+EO1GSgHAcj3cI0+QiV4HvHVKFvyjwPOmMkASoFL5w 8Yc/LCaoD0J+DVxDPhJAOfUuUS8F8lI6W75NZ6MX/a8m7HC25KWGFgON/i0LfaCQ 7anWIcXdjg989SARmotKCwSTFgwZd3g2T0aIg7PNjtcQOvfJag7AYMFOrrx8Rq2k JArPb9Tp9s38zgp6428/TNt0unfwXPVm5KDNVwYEQwWNxomYarNN1iQpvgewrT47 /Cqmp8X6mfBwBqxwZa44xr/XQM8fNIhxX8Sy1wh4L5/BL4DUdAquMsGubEOoIBLC 5rBPhEh8zZCcydZMfgyhrEnkbEEj1qb1n+efFS2Cg3n6z5lEDP20B1nGlRrAxl6x 7ugYmDmeIJOKjed4QVyYAjxyG9ZaWvclxDQsdaWmvwJRoBdkgFGdMyZa7EVrVOO1 8ZysJnuiZrLLqDnAFu2q1kuIPpsHK1IK13f/C6jDabHQ5Ip1nbXrExppzoQnv7pk nznh3bFyerTSk6CC1VpfkFUNGK34VWBMF0FYyL53FDS9Oki5IkyokgplyP8Muj/b kVPbEVQldSTPIPVHmX02QtKYXe13wn0oKWjyzwI6G8MIUynwLWQ= =tItr -END PGP SIGNATURE End Message ---
Bug#998886: marked as done (node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/*)
Your message dated Wed, 10 Nov 2021 13:34:59 + with message-id and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-3 has caused the Debian Bug report #998886, regarding node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-string-width,node-slice-ansi Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 4.2.3+~3.0.0+~9.2.2-1 Control: found -1 5.0.0+~4.0.0-2 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package node-slice-ansi. Preparing to unpack .../node-slice-ansi_5.0.0+~4.0.0-2_all.deb ... Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1 Errors were encountered while processing: /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb The following files are in conflict between the two packages: usr/share/nodejs/is-fullwidth-code-point/index.d.ts usr/share/nodejs/is-fullwidth-code-point/index.js usr/share/nodejs/is-fullwidth-code-point/package.json cheers, Andreas node-string-width=4.2.3+~3.0.0+~9.2.2-1_node-slice-ansi=5.0.0+~4.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-slice-ansi Source-Version: 5.0.0+~4.0.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-slice-ansi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-slice-ansi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 14:17:05 +0100 Source: node-slice-ansi Architecture: source Version: 5.0.0+~4.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 998886 Changes: node-slice-ansi (5.0.0+~4.0.0-3) unstable; urgency=medium . * Team upload * Add Breaks node-string-width < 4.2.3+~9.2.2-1 (Closes: #998886) Checksums-Sha1: 82fb142bb24fb454eb676b5ef4ce15ad74b3b157 2498 node-slice-ansi_5.0.0+~4.0.0-3.dsc acbe219f60a2768e6ce853279ae6dfe6f0435d4a 3372 node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz Checksums-Sha256: 14e9b9b067792ababc3854e21a61076954a6c9032f22d24e4452765b17d96ccb 2498 node-slice-ansi_5.0.0+~4.0.0-3.dsc 443955ec47b139016b5c1e28af067dd4d91fc45420d7c9be50e49cdcb626aadb 3372 node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz Files: 64fb356fbf9f52eaf6f9d37600800b48 2498 javascript optional node-slice-ansi_5.0.0+~4.0.0-3.dsc f06562b7758020e64725c69d60035878 3372 javascript optional node-slice-ansi_5.0.0+~4.0.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGLxpoACgkQ9tdMp8mZ 7uk/8Q/9HmHlRqSD04IFMZS1sGSRPkvcbD/b38g7kIxjtYaoVY13Jsfv5CzvgIPh LkkTUS+1O/aW9sA3GUlirp+EO1GSgHAcj3cI0+QiV4HvHVKFvyjwPOmMkASoFL5w 8Yc/LCaoD0J+DVxDPhJAOfUuUS8F8lI6W75NZ6MX/a8m7HC25KWGFgON/i0LfaCQ 7anWIcXdjg989SARmotKCwSTFgwZd3g2T0aIg7PNjtcQOvfJag7AYMFOrrx8Rq2k JArPb9Tp9s38zgp6428/TNt0unfwXPVm5KDNVwYEQwWNxomYarNN1iQpvgewrT47 /Cqmp8X6mfBwBqxwZa44xr/XQM8fNIhxX8Sy1wh4L5/BL4DUdAquMsGubEOoIBLC 5rBPhEh8zZCcydZMfgyhrEnkbEEj1qb1n+efFS2Cg3n6z5lEDP20B1nGlRrAxl6x 7ugYmDmeIJOKjed4QVyYAjxyG9ZaWvclxDQsdaWmvwJRoBdkgFGdMyZa7EVrVOO1 8ZysJnuiZrLLqDnAFu2q1kuIPpsHK1IK13f/C6jDabHQ5Ip1nbXrExppzoQnv7pk nznh3bFyerTSk6CC1VpfkFUNGK34VWBMF0FYyL53FDS9Oki5IkyokgplyP8Muj/b kVPbEVQldSTPIPVHmX02QtKYXe13wn0oKWjyzwI6G8MIUynwLWQ= =tItr -END PGP SIGNATURE End Message ---
Bug#998911: [Pkg-javascript-devel] Bug#998911: node-string-width: file conflict with node-slice-ansi
On Wed, Nov 10, 2021 at 02:13:46PM +0100, Yadd wrote: > you reopened this bug, however node-string-width is really fixed in > version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ? Without too many checks, I believe node-slice-ansi should have a Breaks+Replace: node-string-width (<< 4.2.3+~9.2.2-1) though I'm not sure (please double check!) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#998886: marked as pending in node-slice-ansi
Control: tag -1 pending Hello, Bug #998886 in node-slice-ansi 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/js-team/node-slice-ansi/-/commit/55b4a3725ace58c24971ca1784421cc5de30e40a Add Breaks node-string-width < 4.2.3+~9.2.2-1 Closes: #998886 (this message was generated automatically) -- Greetings https://bugs.debian.org/998886
Processed: Bug#998886 marked as pending in node-slice-ansi
Processing control commands: > tag -1 pending Bug #998886 [node-string-width,node-slice-ansi] node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file conflict with node-slice-ansi Added tag(s) pending. Added tag(s) pending. -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998233: marked as done (gcc-doc-defaults: FTBFS with gcc-11 being the default)
Your message dated Wed, 10 Nov 2021 13:18:38 + with message-id and subject line Bug#998233: fixed in gcc-doc-defaults 5:23 has caused the Debian Bug report #998233, regarding gcc-doc-defaults: FTBFS with gcc-11 being the default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-doc-defaults Version: 5:22 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) debian/rules override_dh_gencontrol-arch make[1]: Entering directory '/build/gcc-doc-defaults-22' # call dh_gencontrol one at a time for *-doc packages dh_gencontrol -p cpp-doc -- -v5:; dh_gencontrol -p gcc-doc -- -v5:; dh_gencontrol -p gfortran-doc -- -v5:; dh_gencontrol -p gnat-doc -- -v5:10.1.0-2; dh_gencontrol -p gccgo-doc -- -v5:; ... dh_builddeb dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 package 'gcc-doc': 'Version' field value '5:': nothing after colon in version number dpkg-deb: error: parsing file 'debian/gfortran-doc/DEBIAN/control' near line 3 package 'gfortran-doc': 'Version' field value '5:': nothing after colon in version number dpkg-deb: error: parsing file 'debian/gccgo-doc/DEBIAN/control' near line 3 package 'gccgo-doc': 'Version' field value '5:': nothing after colon in version number dh_builddeb: error: dpkg-deb --build debian/gfortran-doc .. returned exit code 2 dh_builddeb: error: dpkg-deb --build debian/gcc-doc .. returned exit code 2 dh_builddeb: error: dpkg-deb --build debian/gccgo-doc .. returned exit code 2 dh_builddeb: error: Aborting due to earlier error make: *** [debian/rules:113: binary] Error 25 There are some versions missing ... Andreas --- End Message --- --- Begin Message --- Source: gcc-doc-defaults Source-Version: 5:23 Done: Dmitry Baryshkov We believe that the bug you reported is fixed in the latest version of gcc-doc-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Baryshkov (supplier of updated gcc-doc-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 13:56:26 +0300 Source: gcc-doc-defaults Architecture: source Version: 5:23 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Dmitry Baryshkov Closes: 998233 Changes: gcc-doc-defaults (5:23) unstable; urgency=medium . * Build using gcc-11 (gnat is still using gnat-10) (Closes: #998233) Checksums-Sha1: 62f85bae79bffd14909e89a467b8ceb4286dd614 2394 gcc-doc-defaults_23.dsc b85813035ba9b834750afa0d2d66f89b31e236b1 31496 gcc-doc-defaults_23.tar.xz f2d5b6e822a6d2f34549a182d2941c020b34b343 6158 gcc-doc-defaults_23_source.buildinfo Checksums-Sha256: d04672558a164f75587bfe7fddad55d4aa1e7e7bec6ad9293525a6f95ac63c3f 2394 gcc-doc-defaults_23.dsc a7a8c88d0f7cd33ad985ab5f4b9f7773640aad04e3e34ef9b468e2692f752346 31496 gcc-doc-defaults_23.tar.xz b564c10f7c860a1bad212b01886414429175c52b79b317f38ff46d3801a2a7e0 6158 gcc-doc-defaults_23_source.buildinfo Files: b9906006e815312b371627fbbd66fb47 2394 contrib/doc optional gcc-doc-defaults_23.dsc 6005eaa0298b0aeeece0f1a8c5c00dbc 31496 contrib/doc optional gcc-doc-defaults_23.tar.xz 3507d39c58b30e272ed29b444aa1b2be 6158 contrib/doc optional gcc-doc-defaults_23_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmGLwFwACgkQweDZLphv fH4Z6g//dMrCYv+LI0uqQ24+M9uw1UCdxy/uiqKnkoaMlc+Ds08zbIlm6H1w76hy 1mQsS+ATmPPAIUL6JBeSetxj4WCfI7zNeUxBG1ybzimyZQXdprTufc9md+yKLVJQ KINh/805wHub9E7AxQKidajQeIw5raZQjUlci3KfoNXjTYJEOrPqgBeniGWVyei5 n3xX6s4LZ3L9JQdYuyiMRUd9yRkbaM2z3oU0nG/Bcfui3CcFMs20SrBBCV/rxcSB 7ViVwU76mPe2T0ojzNbFWH8ZScvnx/QsBa5mRYDYSVoEDCB6TpMwp8FF9oKO2jPC pC2wMMueui3h5itYgQP3NP9Mrxb/l/bBBkHP9j68UxlHPJSrnuFxJUDwKUYg71k5 +9emFbMfltrcy2B9S067Cb7MMD/1rJZW2/rPmvpUHXs3UaPuP7TfrzFjUfJ63OEd NMLW/3RS90AvdNTEu+zGecJ0xKH07zecWkfjULPnem4lDTq2FtofWzJUqixAbIe0
Bug#998911: node-string-width: file conflict with node-slice-ansi
Control: tags -1 + moreinfo Hi Axel, you reopened this bug, however node-string-width is really fixed in version 4.2.3+~9.2.2-1 (no more is-fullwidth-code-point). What should I do ? Cheers, Yadd $ dpkg -l node-string-width && dpkg -L node-string-width ||/ Name VersionArchitecture Description +++-=-==--= ii node-string-width 4.2.3+~9.2.2-1 all Get the visual width.. /. /usr /usr/share /usr/share/doc /usr/share/doc/node-string-width /usr/share/doc/node-string-width/changelog.Debian.gz /usr/share/doc/node-string-width/copyright /usr/share/doc/node-string-width/readme.md /usr/share/nodejs /usr/share/nodejs/emoji-regex /usr/share/nodejs/emoji-regex/RGI_Emoji.d.ts /usr/share/nodejs/emoji-regex/RGI_Emoji.js /usr/share/nodejs/emoji-regex/es2015 /usr/share/nodejs/emoji-regex/es2015/RGI_Emoji.d.ts /usr/share/nodejs/emoji-regex/es2015/RGI_Emoji.js /usr/share/nodejs/emoji-regex/es2015/index.d.ts /usr/share/nodejs/emoji-regex/es2015/index.js /usr/share/nodejs/emoji-regex/es2015/text.d.ts /usr/share/nodejs/emoji-regex/es2015/text.js /usr/share/nodejs/emoji-regex/index.d.ts /usr/share/nodejs/emoji-regex/index.js /usr/share/nodejs/emoji-regex/package.json /usr/share/nodejs/emoji-regex/text.d.ts /usr/share/nodejs/emoji-regex/text.js /usr/share/nodejs/string-width /usr/share/nodejs/string-width/index.d.ts /usr/share/nodejs/string-width/index.js /usr/share/nodejs/string-width/package.json
Processed: Re: node-string-width: file conflict with node-slice-ansi
Processing control commands: > tags -1 + moreinfo Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file conflict with node-slice-ansi Bug #998886 [node-string-width,node-slice-ansi] node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* Added tag(s) moreinfo. Added tag(s) moreinfo. -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > forwarded 996323 > https://github.com/steveklabnik/mono_logger/commit/58b71f0fb830272dd45bdf01c0fe03c478a9e085 Bug #996323 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1) Set Bug forwarded-to-address to 'https://github.com/steveklabnik/mono_logger/commit/58b71f0fb830272dd45bdf01c0fe03c478a9e085'. > tags 996323 fixed-upstream patch Bug #996323 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1) Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > forwarded 996320 > https://github.com/seattlerb/minitest-excludes/commit/7ed688995be9a49c0f6b65bd07eb9cb87053676a Bug #996320 [src:ruby-minitest-excludes] ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/seattlerb/minitest-excludes/commit/7ed688995be9a49c0f6b65bd07eb9cb87053676a'. > tags 996320 patch fixed-upstream Bug #996320 [src:ruby-minitest-excludes] ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: 0.16.4 builds
Processing commands for cont...@bugs.debian.org: > tags 996296 fixed-upstream Bug #996296 [src:ruby-ice-cube] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
On Wed, Nov 10, 2021 at 07:27:58AM -0500, Reinhard Tartler wrote: > That's not sufficient. > > the commit you point out does two things: > > - update the submodules for 'image-spec' and 'runtime-spec' (which the > Debian package currently overrides with the distro-provided copies) > - zos-related changes to the rust bindings (which the Debian package > doesn't have at all at this point) > > The missing definitions that the linker stumbles over are generated from > the json files. But I haven't found where that generation exactly happens > and what change is missing to it. > > Thanks for your swift reply! > > On Tue, Nov 9, 2021 at 8:47 PM Shengjing Zhu wrote: > > > Cloud you backport following commit? > > > > https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b > > This patch updates libocispec/Makefile.am, which is needed to be backported. This patch looks like doing nothing to C part, because the generated source is removed in upstream repo. Theses files(which are added in Makefile.am) can be generated by `make -C libocispec generate`. So please also uncomment this line in debian/rules. Thanks.
Processed: tagging 984028
Processing commands for cont...@bugs.debian.org:
> tags 984028 + fixed-in-experimental
Bug #984028 {Done: Kari Pahula } [src:cxxtools] cxxtools:
ftbfs with GCC-11
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Fixed in the 1.5.1 development version
Processing commands for cont...@bugs.debian.org: > tags 984053 fixed-upstream Bug #984053 [src:etl] etl: ftbfs with GCC-11 Bug #984355 [src:etl] synfig: ftbfs with GCC-11 Bug #984357 [src:etl] synfigstudio: ftbfs with GCC-11 Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 984053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984053 984355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984355 984357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
Looking more into it, here are more observations: - crun upstream has a git submodule on 'libocispec' (the repo you asked me to backport). The release tarballs contain a copy of the submodule contents at the time of the release - the 'libocispec' submodule contains two additional submodules 'image-spec' and 'runtime-spec' - the debian package replaces only the two "inner" submodules 'image-spec' and 'runtime-spec' with sources found in Debian packages, but not the outer 'libocispec', which isn't found in debian - the Debian packages of 'image-spec' and 'runtime-spec' have been updated last August, and contain specification for the "zos" platform - the 'libocispec' repository contains a generator that reads those specifications and generates code. It seems to me that this is the code generator that lacks some zos related definition and thus causes the linker failure - the 'libocispec' repository has last synced with 'image-spec' and 'runtime-spec' last January, and thus is missing the zos related changes This is very messy. I can totally understand upstream's stance to just vendor the specs so that the generator is only used with versions of the specifications that have actually been tested. I don't think it is a good use of Debian's developers' time to play this game of catching up. On Wed, Nov 10, 2021 at 7:27 AM Reinhard Tartler wrote: > That's not sufficient. > > the commit you point out does two things: > > - update the submodules for 'image-spec' and 'runtime-spec' (which the > Debian package currently overrides with the distro-provided copies) > - zos-related changes to the rust bindings (which the Debian package > doesn't have at all at this point) > > The missing definitions that the linker stumbles over are generated from > the json files. But I haven't found where that generation exactly happens > and what change is missing to it. > > Thanks for your swift reply! > > On Tue, Nov 9, 2021 at 8:47 PM Shengjing Zhu wrote: > >> Cloud you backport following commit? >> >> https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b >> >> >> (Sent on my mobile phone) >> >> Reinhard Tartler 于 2021年11月10日周三 07:05写道： >> >>> I took a look at the issue and here are my thoughts: >>> >>> - the build error is a failure to link some test binaries. excluding >>> them from the build might be possible with some patching. >>> - I've upgraded the package to the latest upstream 1.3, and was seeing >>> exactly the same build failure >>> - the build failure goes away when not stripping the bundled copies of >>> runtime-spec and image-spec >>> - Dimtry had a conversation about this with upstream at >>> https://github.com/containers/crun/issues/240. It seems to be that >>> upstream strongly recommends to just use the vendored copies of image-spc >>> and runtime-spec >>> - I've pushed my work to >>> https://salsa.debian.org/debian/crun/-/merge_requests/1 >>> - I believe the issue was introduced by Shengjing's update in >>> https://tracker.debian.org/news/1249177/accepted-golang-github-opencontainers-specs-10266g20a2d97-1-source-into-unstable/ >>> -- but that was already months ago. So that may not be true >>> >>> With this, I'd like to suggest to move ahead with my merge request and >>> don't strip image-spec and runtime-spec from the package. >>> >>> Any thoughts? >>> >>> -- >>> regards, >>> Reinhard >>> >> > > -- > regards, > Reinhard > -- regards, Reinhard
Bug#984191: libodb: ftbfs with GCC-11
Control: forwarded -1
https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2
Control: tags -1 patch
On Wed, Mar 03, 2021 at 04:14:40PM +, Matthias Klose wrote:
> Package: src:libodb
> Version: 2.4.0-1
> Severity: normal
> Tags: sid bookworm
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-11
>...
The attached patch derived extracted from the upstream fix linked above
fixes the build with gcc 11.
cu
Adrian
diff --git a/odb/details/shared-ptr/base.cxx b/odb/details/shared-ptr/base.cxx
index b95797b..5bfc0af 100644
--- a/odb/details/shared-ptr/base.cxx
+++ b/odb/details/shared-ptr/base.cxx
@@ -15,7 +15,7 @@ namespace odb
share exclusive = share (2);
const char* not_shared::
-what () const throw ()
+what () const noexcept
{
return "object is not shared";
}
@@ -54,7 +54,11 @@ namespace odb
}
void*
+#ifdef ODB_CXX11
+operator new (size_t n, odb::details::share s)
+#else
operator new (size_t n, odb::details::share s) throw (std::bad_alloc)
+#endif
{
if (s == odb::details::shared)
{
@@ -74,7 +78,7 @@ operator new (size_t n, odb::details::share s) throw (std::bad_alloc)
}
void
-operator delete (void* p, odb::details::share s) throw ()
+operator delete (void* p, odb::details::share s) noexcept
{
// This version of operator delete is only called when the c-tor
// fails. In this case there is no object and we can just free the
diff --git a/odb/details/shared-ptr/base.hxx b/odb/details/shared-ptr/base.hxx
index 4a38945..90053e8 100644
--- a/odb/details/shared-ptr/base.hxx
+++ b/odb/details/shared-ptr/base.hxx
@@ -10,6 +10,7 @@
#include
#include// std::size_t
+#include // ODB_CXX11, noexcept
#include
#include
@@ -34,11 +35,16 @@ namespace odb
}
}
+#ifdef ODB_CXX11
+LIBODB_EXPORT void*
+operator new (std::size_t, odb::details::share);
+#else
LIBODB_EXPORT void*
operator new (std::size_t, odb::details::share) throw (std::bad_alloc);
+#endif
LIBODB_EXPORT void
-operator delete (void*, odb::details::share) throw ();
+operator delete (void*, odb::details::share) noexcept;
namespace odb
{
@@ -61,17 +67,25 @@ namespace odb
std::size_t
_ref_count () const;
+#ifdef ODB_CXX11
+ void*
+ operator new (std::size_t);
+
+ void*
+ operator new (std::size_t, share);
+#else
void*
operator new (std::size_t) throw (std::bad_alloc);
void*
operator new (std::size_t, share) throw (std::bad_alloc);
+#endif
void
- operator delete (void*, share) throw ();
+ operator delete (void*, share) noexcept;
void
- operator delete (void*) throw ();
+ operator delete (void*) noexcept;
struct refcount_callback
{
diff --git a/odb/details/shared-ptr/base.ixx b/odb/details/shared-ptr/base.ixx
index 9bf7c94..3ed1339 100644
--- a/odb/details/shared-ptr/base.ixx
+++ b/odb/details/shared-ptr/base.ixx
@@ -63,6 +63,19 @@ namespace odb
return counter_;
}
+#ifdef ODB_CXX11
+inline void* shared_base::
+operator new (std::size_t n)
+{
+ return ::operator new (n);
+}
+
+inline void* shared_base::
+operator new (std::size_t n, share)
+{
+ return ::operator new (n);
+}
+#else
inline void* shared_base::
operator new (std::size_t n) throw (std::bad_alloc)
{
@@ -74,15 +87,16 @@ namespace odb
{
return ::operator new (n);
}
+#endif
inline void shared_base::
-operator delete (void* p, share) throw ()
+operator delete (void* p, share) noexcept
{
::operator delete (p);
}
inline void shared_base::
-operator delete (void* p) throw ()
+operator delete (void* p) noexcept
{
::operator delete (p);
}
Processed: Re: Bug#984191: libodb: ftbfs with GCC-11
Processing control commands: > forwarded -1 > https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2 Bug #984191 [src:libodb] libodb: ftbfs with GCC-11 Bug #984189 [src:libodb] libodb-boost: ftbfs with GCC-11 Bug #984192 [src:libodb] libodb-qt: ftbfs with GCC-11 Bug #984193 [src:libodb] libodb-mysql: ftbfs with GCC-11 Bug #984194 [src:libodb] libodb-pgsql: ftbfs with GCC-11 Bug #984197 [src:libodb] libodb-sqlite: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. Set Bug forwarded-to-address to 'https://git.codesynthesis.com/cgit/odb/libodb/commit/?id=13dd928ae18ef9610bc820b7b3e65629addea1d2'. > tags -1 patch Bug #984191 [src:libodb] libodb: ftbfs with GCC-11 Bug #984189 [src:libodb] libodb-boost: ftbfs with GCC-11 Bug #984192 [src:libodb] libodb-qt: ftbfs with GCC-11 Bug #984193 [src:libodb] libodb-mysql: ftbfs with GCC-11 Bug #984194 [src:libodb] libodb-pgsql: ftbfs with GCC-11 Bug #984197 [src:libodb] libodb-sqlite: ftbfs with GCC-11 Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. -- 984189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984189 984191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984191 984192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984192 984193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984193 984194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984194 984197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
That's not sufficient. the commit you point out does two things: - update the submodules for 'image-spec' and 'runtime-spec' (which the Debian package currently overrides with the distro-provided copies) - zos-related changes to the rust bindings (which the Debian package doesn't have at all at this point) The missing definitions that the linker stumbles over are generated from the json files. But I haven't found where that generation exactly happens and what change is missing to it. Thanks for your swift reply! On Tue, Nov 9, 2021 at 8:47 PM Shengjing Zhu wrote: > Cloud you backport following commit? > > https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b > > > (Sent on my mobile phone) > > Reinhard Tartler 于 2021年11月10日周三 07:05写道： > >> I took a look at the issue and here are my thoughts: >> >> - the build error is a failure to link some test binaries. excluding them >> from the build might be possible with some patching. >> - I've upgraded the package to the latest upstream 1.3, and was seeing >> exactly the same build failure >> - the build failure goes away when not stripping the bundled copies of >> runtime-spec and image-spec >> - Dimtry had a conversation about this with upstream at >> https://github.com/containers/crun/issues/240. It seems to be that >> upstream strongly recommends to just use the vendored copies of image-spc >> and runtime-spec >> - I've pushed my work to >> https://salsa.debian.org/debian/crun/-/merge_requests/1 >> - I believe the issue was introduced by Shengjing's update in >> https://tracker.debian.org/news/1249177/accepted-golang-github-opencontainers-specs-10266g20a2d97-1-source-into-unstable/ >> -- but that was already months ago. So that may not be true >> >> With this, I'd like to suggest to move ahead with my merge request and >> don't strip image-spec and runtime-spec from the package. >> >> Any thoughts? >> >> -- >> regards, >> Reinhard >> > -- regards, Reinhard
Bug#984027: darkice: diff for NMU version 1.3-0.3
Control: tags 984027 + patch Control: tags 984027 + pending Dear maintainer, I've prepared an NMU for darkice (versioned as 1.3-0.3) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru darkice-1.3/debian/changelog darkice-1.3/debian/changelog --- darkice-1.3/debian/changelog 2017-10-14 12:17:23.0 +0300 +++ darkice-1.3/debian/changelog 2021-11-10 14:16:46.0 +0200 @@ -1,3 +1,11 @@ +darkice (1.3-0.3) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -std=gnu++14 to workaround FTBFS with gcc 11. +(Closes: #984027) + + -- Adrian Bunk Wed, 10 Nov 2021 14:16:46 +0200 + darkice (1.3-0.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru darkice-1.3/debian/rules darkice-1.3/debian/rules --- darkice-1.3/debian/rules 2016-08-05 23:07:25.0 +0300 +++ darkice-1.3/debian/rules 2021-11-10 14:16:46.0 +0200 @@ -5,6 +5,8 @@ DEB_BUILD_MAINT_OPTIONS := hardening=+all include /usr/share/dpkg/default.mk +export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14 + POLICY_TARGETS := binary binary-arch binary-indep build build-arch \ build-indep clean .PHONY: $(POLICY_TARGETS)
Processed: darkice: diff for NMU version 1.3-0.3
Processing control commands: > tags 984027 + patch Bug #984027 [src:darkice] darkice: ftbfs with GCC-11 Added tag(s) patch. > tags 984027 + pending Bug #984027 [src:darkice] darkice: ftbfs with GCC-11 Added tag(s) pending. -- 984027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#998141: opencv breaks auto-multiple-choice autopkgtest
Processing control commands: > reassign -1 src:opencv Bug #998141 [src:opencv, src:auto-multiple-choice] opencv breaks auto-multiple-choice autopkgtest Bug reassigned from package 'src:opencv, src:auto-multiple-choice' to 'src:opencv'. No longer marked as found in versions auto-multiple-choice/1.5.1-2 and opencv/4.5.4+dfsg-1. Ignoring request to alter fixed versions of bug #998141 to the same values previously set -- 998141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998141: opencv breaks auto-multiple-choice autopkgtest
control: reassign -1 src:opencv On Sun, 31 Oct 2021 22:04:15 +0100 Paul Gevers wrote: > I think that means you must bump the SONAME (if not done upstream, with > a Debian specific version), go through NEW, ask for a transition block > with the release team and have all reverse dependencies rebuild. I think these apply to opencv, so I reassign to this package to let current working version of auto-multiple-choice in testing. Regards, Alexis.
Bug#997783: marked as done (silkaj: FTBFS: test -s debian/bash-completion => fails)
Your message dated Wed, 10 Nov 2021 11:20:35 +
with message-id
and subject line Bug#997783: fixed in silkaj 0.9.0-2
has caused the Debian Bug report #997783,
regarding silkaj: FTBFS: test -s debian/bash-completion => fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: silkaj
Version: 0.9.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PATH="/<>/debian/silkaj/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
> PYTHONPATH="/<>/debian/silkaj/usr/lib/python3.9/dist-packages"
> help2man --name "command-line client for Duniter" --no-info --output
> debian/silkaj.1 silkaj || {
> PATH="/<>/debian/silkaj/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
> PYTHONPATH="/<>/debian/silkaj/usr/lib/python3.9/dist-packages"
> silkaj --help; false; }
> perl -i -pe 's/\?\?(?=1|Test)/ \\\[u011E\]/g' \
> debian/silkaj.1
> PATH="/<>/debian/silkaj/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
> PYTHONPATH="/<>/debian/silkaj/usr/lib/python3.9/dist-packages" \
> _SILKAJ_COMPLETE=source silkaj \
> > debian/bash-completion || true
> test -s debian/bash-completion
> make[1]: *** [debian/rules:25: execute_after_dh_auto_install] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/silkaj_0.9.0-1_unstable.log
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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: silkaj
Source-Version: 0.9.0-2
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
silkaj, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated silkaj package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 10 Nov 2021 17:05:47 +0100
Source: silkaj
Architecture: source
Version: 0.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team
Changed-By: Jonas Smedegaard
Closes: 997783
Changes:
silkaj (0.9.0-2) unstable; urgency=medium
.
* update shell completion commands;
tighten build-dependency on python3-click;
closes: bug#997783, thanks to Lucas Nussbaum
* declare compliance with Debian Policy 4.6.0
* update copyright info:
+ use Reference field (not License-Reference);
tighten lintian overrides
+ update coverage
Checksums-Sha1:
435dbed96fbe7332b1797549ad1c5e63bbbf9c57 2262 silkaj_0.9.0-2.dsc
f123e961ae88af6da0c2c4c18ca95f7e7cab01c7 18948 silkaj_0.9.0-2.debian.tar.xz
66f14823471673ca882e574d479f1beda6328c8a 7206 silkaj_0.9.0-2_amd64.buildinfo
Checksums-Sha256:
2c28b5df676de34884e1b90a066f71efbfebcad656c2698ed4db9e6506a88a91 2262
silkaj_0.9.0-2.dsc
cf2fe798aaa8a5b8b1e2c90c2f5cf809c461ffe8e2639e01f7846013b5c60176 18948
silkaj_0.9.0-2.debian.tar.xz
9d21e0de682d61486343089fbe3fa9365c01d32abff08ebe39e85034cd1d8336 7206
silkaj_0.9.0-2_amd64.buildinfo
Files:
4343076cd129085f4daf3681817267aa 2262 utils optional silkaj_0.9.0-2.dsc
73740c9d62b6cb1f0dd9934ce2b837d3 18948 utils optional
silkaj_0.9.0-2.debian.tar.xz
bc1e0819009a15626ac6fd0bfb583457 7206 utils optional
silkaj_0.9.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGL7tAACgkQLHwxRsGg
Processed: reopening 998886, found 998886 in node-string-width/4.2.3+~9.2.2-1
Processing commands for cont...@bugs.debian.org:
> reopen 998886
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
No longer marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
> # Missing Breaks and Replaces headers in node-string-width/4.2.3+~9.2.2-1
> found 998886 node-string-width/4.2.3+~9.2.2-1
Bug #998886 [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file
conflict with node-slice-ansi
Marked as found in versions node-string-width/4.2.3+~9.2.2-1.
Marked as found in versions node-string-width/4.2.3+~9.2.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886
998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997481: marked as done (textdistance: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Wed, 10 Nov 2021 10:20:48 +
with message-id
and subject line Bug#997481: fixed in textdistance 4.2.2-1
has caused the Debian Bug report #997481,
regarding textdistance: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: textdistance
Version: 4.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package textdistance
> dpkg-buildpackage: info: source version 4.2.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Julian Gilbey
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building textdistance using existing
> ./textdistance_4.2.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building textdistance in textdistance_4.2.0-2.debian.tar.xz
> dpkg-source: info: building textdistance in textdistance_4.2.0-2.dsc
> debian/rules binary
> dh binary --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
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of
> dash-separated 'description-file' will not be supported in future versions.
> Please use the underscore name 'description_file' instead
> warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/textdistance
> copying textdistance/libraries.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance
> copying textdistance/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance
> copying textdistance/benchmark.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance
> copying textdistance/utils.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance
> creating /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/simple.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/compression_based.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/token_based.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/phonetic.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/sequence_based.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/vector_based.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/edit_based.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying textdistance/algorithms/base.py ->
> /<>/.pybuild/cpython3_3.9/build/textdistance/algorithms
> copying
Bug#997335: marked as done (python-fakeredis: FTBFS: unsatisfiable build-dependency: python3-pytest-cov (< 3.0) but 3.0.0-1 is to be installed)
Your message dated Wed, 10 Nov 2021 09:50:10 + with message-id and subject line Bug#997335: fixed in python-fakeredis 1.6.1-1 has caused the Debian Bug report #997335, regarding python-fakeredis: FTBFS: unsatisfiable build-dependency: python3-pytest-cov (< 3.0) but 3.0.0-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-fakeredis Version: 1.4.5-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-aioredis, > python3-all, python3-future, python3-hypothesis, python3-lupa, python3-pytest > (>= 4.6.4), python3-pytest-cov (>= 2.7.1), python3-pytest-cov (<< 3.0), > python3-pytest-mock, python3-redis, python3-setuptools, python3-six, > python3-sortedcontainers, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-aioredis, > python3-all, python3-future, python3-hypothesis, python3-lupa, python3-pytest > (>= 4.6.4), python3-pytest-cov (>= 2.7.1), python3-pytest-cov (<< 3.0), > python3-pytest-mock, python3-redis, python3-setuptools, python3-six, > python3-sortedcontainers, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [466 B] > Get:5 copy:/<>/apt_archive ./ Packages [550 B] > Fetched 1973 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-pytest-cov (< 3.0) but > 3.0.0-1 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-fakeredis_1.4.5-4_unstable.log 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 marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-fakeredis Source-Version: 1.6.1-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-fakeredis, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-fakeredis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Nov 2021 01:31:44 -0800 Source: python-fakeredis Architecture: source Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera
Bug#997335: marked as pending in python-fakeredis
Control: tag -1 pending Hello, Bug #997335 in python-fakeredis 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-fakeredis/-/commit/5aae69c1c7dc4ff40cd75914c52ca3546124ac6b Remove Build-Dep restriction on pytest-cov >= 3. (Closes: #997335) (this message was generated automatically) -- Greetings https://bugs.debian.org/997335
Processed: Bug#997335 marked as pending in python-fakeredis
Processing control commands: > tag -1 pending Bug #997335 [src:python-fakeredis] python-fakeredis: FTBFS: unsatisfiable build-dependency: python3-pytest-cov (< 3.0) but 3.0.0-1 is to be installed Added tag(s) pending. -- 997335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999348: gtk-d: FTBFS with ldc 1.28.0
Source: gtk-d Version: 3.9.0-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) | ldc2 -O -g -release -wi -Igenerated/gtkd -Idemos/gtkD/TestWindow -c demos/gtkD/TestWindow/TestText.d -ofdemos/gtkD/TestWindow/TestText.o | demos/gtkD/TestWindow/TestWindow.d(207): Error: import `TestWindow.TestEntries` is used as a type | demos/gtkD/TestWindow/TestWindow.d(212): Error: import `TestWindow.TestStock` is used as a type | demos/gtkD/TestWindow/TestWindow.d(219): Error: import `TestWindow.TestScales` is used as a type | demos/gtkD/TestWindow/TestWindow.d(222): Error: import `TestWindow.TestTreeView` is used as a type | demos/gtkD/TestWindow/TestWindow.d(228): Error: import `TestWindow.TestDrawingArea` is used as a type | demos/gtkD/TestWindow/TestWindow.d(229): Error: import `TestWindow.TestText` is used as a type | demos/gtkD/TestWindow/TestWindow.d(230): Error: import `TestWindow.TestImage` is used as a type | demos/gtkD/TestWindow/TestWindow.d(233): Error: import `TestWindow.TestAspectFrame` is used as a type | demos/gtkD/TestWindow/TestWindow.d(234): Error: import `TestWindow.TestIdle` is used as a type | demos/gtkD/TestWindow/TestWindow.d(949): Error: import `TestWindow.TTextView` is used as a type | make[2]: *** [GNUmakefile:257: demos/gtkD/TestWindow/TestWindow.o] Error 1 https://buildd.debian.org/status/fetch.php?pkg=gtk-d=amd64=3.9.0-4%2Bb1=1636493509=0 Cheers -- Sebastian Ramacher
Bug#998575: [Pkg-freeipa-devel] Bug#998575: Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
On 9.11.2021 10.53, Ondřej Surý wrote: Hi Timo, On 5. 11. 2021, at 8:09, Timo Aaltonen wrote: On 5.11.2021 1.37, peter green wrote: bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be installed It looks like bind8 no longer builds the bind9-dev package. It's still present in unstable as a cruft package but is uninstallable due to version constraints, it's completely gone from testing. I don't know what's going on here, but at least the current bind9 packaging is not available on salsa, debian/main is on 9.16.22-1 and according to d/changelog it was uploaded to unstable on the same day as 9.17.19-1... (which has now migrated to testing already) The 9.17 packaging is available from the isc/9.17 branch which should be up to date. The new bind9 doesn't mention dropping bind9-dev on d/changelog. Ondrej, why was it dropped? We need to figure out what to do with bind-dyndb-ldap in the future. The BIND 9 libraries are not meant for public consumption since 9.14.0. The upstream (which is incidentally also me) has declare the libraries private and the symbols could change even between patch releases. There’s absolutely no guarantee about symbol stability even on stable branch. Unfortunately, bind-dyndb-ldap is licensed under GPL-2.0 which makes it impossible to include it directly in the src:bind9 package. I see no easy way from this. I will reintroduce the bind9-dev package, but this will make the bind-dyndb-ldap package to regularly FTBFS anyway and it needs to be fixed before the next stable release. Ok thanks. I asked about plans to upstream the ldap plugin, but apparently "upstream was not interested in it". Would it be possible to get merged now? :) (if the license is changed, of course) -- t
Bug#999342: shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev
Control: forcemerge 998633 -1 Control: tags = 998633 ftbfs bookworm pending sid On 2021-11-10 07:58:54 +0100, Helmut Grohne wrote: > Source: shadow > Version: 1:4.8.1-1.1 > Severity: serious > Tags: ftbfs patch > User: helm...@debian.org > Usertags: rebootstrap > > shadow fails to build from source in unstable, because the selinux > people started a transition, bumped soname and in that process moved to > unversioned -dev packages. The final result is that for now shadow > exhibits a conflict on libsepol1-dev, but before too long it will miss a > versioned -dev package. Switching to unversioned ones fixes the issue in > practice and completes the transition for shadow. There's #998633 already Cheers > > Helmut > diff --minimal -Nru shadow-4.8.1/debian/changelog > shadow-4.8.1/debian/changelog > --- shadow-4.8.1/debian/changelog 2021-10-23 21:04:57.0 +0200 > +++ shadow-4.8.1/debian/changelog 2021-11-10 07:51:53.0 +0100 > @@ -1,3 +1,11 @@ > +shadow (1:4.8.1-1.2) UNRELEASED; urgency=medium > + > + * Non-maintainer upload. > + * Fix FTBFS: Use unversioned selinux and semanage dependencies. > +(Closes: #-1) > + > + -- Helmut Grohne Wed, 10 Nov 2021 07:51:53 +0100 > + > shadow (1:4.8.1-1.1) unstable; urgency=medium > >[ Johannes Schauer Marin Rodrigues ] > diff --minimal -Nru shadow-4.8.1/debian/control shadow-4.8.1/debian/control > --- shadow-4.8.1/debian/control 2021-10-23 20:29:33.0 +0200 > +++ shadow-4.8.1/debian/control 2021-11-10 07:51:49.0 +0100 > @@ -12,8 +12,8 @@ > docbook-xsl, > docbook-xml, > libxml2-utils, > - libselinux1-dev [linux-any], > - libsemanage1-dev [linux-any], > + libselinux-dev [linux-any], > + libsemanage-dev [linux-any], > itstool, > bison, > libaudit-dev [linux-any] -- Sebastian Ramacher signature.asc Description: PGP signature
Processed (with 1 error): Re: Bug#999342: shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev
Processing control commands: > forcemerge 998633 -1 Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to libsemanage-dev Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to libsemanage-dev Added tag(s) ftbfs and patch. Bug #999342 [src:shadow] shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev 998067 was blocked by: 929484 998633 998634 998067 was not blocking any bugs. Added blocking bug(s) of 998067: 999342 Added tag(s) pending, sid, and bookworm. Merged 998633 999342 > tags = 998633 ftbfs bookworm pending sid Unknown command or malformed arguments to command. -- 998067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998067 998633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998633 999342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
