Processed: reassign 997143 to python3-sphinxcontrib.plantuml, forcibly merging 995365 997143, affects 995365
Processing commands for cont...@bugs.debian.org:
> reassign 997143 python3-sphinxcontrib.plantuml 0.5-6
Bug #997143 [src:autosuspend] autosuspend: FTBFS: Could not import extension
sphinxcontrib.plantuml (exception: cannot import name 'ENOENT' from
'sphinx.util.osutil' (/usr/lib/python3/dist-packages/sphinx/util/osutil.py))
Bug reassigned from package 'src:autosuspend' to
'python3-sphinxcontrib.plantuml'.
No longer marked as found in versions autosuspend/3.0-2.
Ignoring request to alter fixed versions of bug #997143 to the same values
previously set
Bug #997143 [python3-sphinxcontrib.plantuml] autosuspend: FTBFS: Could not
import extension sphinxcontrib.plantuml (exception: cannot import name 'ENOENT'
from 'sphinx.util.osutil'
(/usr/lib/python3/dist-packages/sphinx/util/osutil.py))
Marked as found in versions python-sphinxcontrib.plantuml/0.5-6.
> forcemerge 995365 997143
Bug #995365 {Done: Thomas Goirand }
[python3-sphinxcontrib.plantuml] Cannot import module: ImportError: cannot
import name 'ENOENT' from 'sphinx.util.osutil'
Bug #995365 {Done: Thomas Goirand }
[python3-sphinxcontrib.plantuml] Cannot import module: ImportError: cannot
import name 'ENOENT' from 'sphinx.util.osutil'
Added tag(s) ftbfs.
Bug #997143 [python3-sphinxcontrib.plantuml] autosuspend: FTBFS: Could not
import extension sphinxcontrib.plantuml (exception: cannot import name 'ENOENT'
from 'sphinx.util.osutil'
(/usr/lib/python3/dist-packages/sphinx/util/osutil.py))
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 997143 affects trafficserver
Marked as fixed in versions python-sphinxcontrib.plantuml/0.5-8.
Added tag(s) fixed-upstream.
Merged 995365 997143
> affects 995365 src:autosuspend
Bug #995365 {Done: Thomas Goirand }
[python3-sphinxcontrib.plantuml] Cannot import module: ImportError: cannot
import name 'ENOENT' from 'sphinx.util.osutil'
Bug #997143 {Done: Thomas Goirand }
[python3-sphinxcontrib.plantuml] autosuspend: FTBFS: Could not import extension
sphinxcontrib.plantuml (exception: cannot import name 'ENOENT' from
'sphinx.util.osutil' (/usr/lib/python3/dist-packages/sphinx/util/osutil.py))
Added indication that 995365 affects src:autosuspend
Added indication that 997143 affects src:autosuspend
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
995365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995365
997143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:python-fastimport: fails to migrate to testing for too long: autopkgtest regression and uploader built arch:all binaries
Processing control commands:
> close -1 0.9.14-1
Bug #999895 [src:python-fastimport] src:python-fastimport: fails to migrate to
testing for too long: autopkgtest regression and uploader built arch:all
binaries
Marked as fixed in versions python-fastimport/0.9.14-1.
Bug #999895 [src:python-fastimport] src:python-fastimport: fails to migrate to
testing for too long: autopkgtest regression and uploader built arch:all
binaries
Marked Bug as done
> block -1 by 996414
Bug #999895 {Done: Paul Gevers } [src:python-fastimport]
src:python-fastimport: fails to migrate to testing for too long: autopkgtest
regression and uploader built arch:all binaries
999895 was not blocked by any bugs.
999895 was not blocking any bugs.
Added blocking bug(s) of 999895: 996414
--
999895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999895: src:python-fastimport: fails to migrate to testing for too long: autopkgtest regression and uploader built arch:all binaries
Source: python-fastimport Version: 0.9.8-5 Severity: serious Control: close -1 0.9.14-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 996414 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:python-fastimport has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The package has two issues, an autopkgtest regression (bug #996414) and arch:all binaries built by the uploader (which unfortunately can't be fixed with a binNMU with the current infrastructure). 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. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=python-fastimport OpenPGP_signature Description: OpenPGP digital signature
Bug#997324: pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py)
Package: pyliblo
Version: 0.10.0-4
Followup-For: Bug #997324
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Attached is a patch which fixes this build failure. As far as I can tell,
the monkeypatching of PyClassmember no longer has any effect, so it might as
well be dropped.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pyliblo-0.10.0/debian/patches/series
pyliblo-0.10.0/debian/patches/series
--- pyliblo-0.10.0/debian/patches/series2020-01-14 23:24:03.0
-0800
+++ pyliblo-0.10.0/debian/patches/series2021-11-17 22:11:36.0
-0800
@@ -1 +1,2 @@
test-hostname.patch
+sphinx-4.2.patch
diff -Nru pyliblo-0.10.0/debian/patches/sphinx-4.2.patch
pyliblo-0.10.0/debian/patches/sphinx-4.2.patch
--- pyliblo-0.10.0/debian/patches/sphinx-4.2.patch 1969-12-31
16:00:00.0 -0800
+++ pyliblo-0.10.0/debian/patches/sphinx-4.2.patch 2021-11-17
22:22:04.0 -0800
@@ -0,0 +1,40 @@
+Description: Compatibility with sphinx 4.2
+ Drop the monkey patching of PyClassmember; this no longer exists and
+ the monkey patching doesn't appear to change the output of the current
+ docs
+Author: Steve Langasek
+Bug-Debian: https://bugs.debian.org/997324
+Last-Update: 2021-11-17
+
+Index: pyliblo-0.10.0/doc/conf.py
+===
+--- pyliblo-0.10.0.orig/doc/conf.py
pyliblo-0.10.0/doc/conf.py
+@@ -30,7 +30,7 @@
+
+ from sphinx.ext.autodoc import py_ext_sig_re
+ from sphinx.util.docstrings import prepare_docstring
+-from sphinx.domains.python import PyClassmember, PyObject, py_sig_re
++from sphinx.domains.python import PyObject, py_sig_re
+
+
+ def process_docstring(app, what, name, obj, options, lines):
+@@ -62,18 +62,6 @@
+ return (signature, return_annotation)
+
+
+-# monkey-patch PyClassmember.handle_signature() to replace __init__
+-# with the class name.
+-handle_signature_orig = PyClassmember.handle_signature
+-def handle_signature(self, sig, signode):
+-if '__init__' in sig:
+-m = py_sig_re.match(sig)
+-name_prefix, name, arglist, retann = m.groups()
+-sig = sig.replace('__init__', name_prefix[:-1])
+-return handle_signature_orig(self, sig, signode)
+-PyClassmember.handle_signature = handle_signature
+-
+-
+ # prevent exception fields from collapsing
+ PyObject.doc_field_types[2].can_collapse = False
+
Processed: Re: pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py)
Processing control commands: > tags -1 patch Bug #997324 [src:pyliblo] pyliblo: FTBFS: ImportError: cannot import name 'PyClassmember' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py) Added tag(s) patch. -- 997324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: xfsprogs FTCBFS: [TEST] CRC32 fails to compile
Processing control commands: > block -1 by 999743 Bug #999879 [src:xfsprogs] xfsprogs FTCBFS: [TEST] CRC32 fails to compile 999879 was not blocked by any bugs. 999879 was not blocking any bugs. Added blocking bug(s) of 999879: 999743 -- 999879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999873: python3-eventlet: Eventlet greendns incompatible with dnspython 2.1.0
Package: python3-eventlet Version: 0.30.2-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Once again, eventlet is incompatible with dnspython and needs fixing. The specific test that is failing is tests.socket_test.test_dns_methods_are_green. I attempted to trouble shoot it a bit and determined that there is a socket error: [Errno -2] Name or service not known. Note: Used the FTBFS tag since that's the closest thing we have to a autopkgttest regression. Scott K
Bug#999862: sso.debian.org: SSO no longer seems to work
On Wed, 2021-11-17 at 20:55 +, Julian Gilbey wrote: > So it would seem that sso.debian.org may no longer be functional, > which prevents me from logging into tracker.debian.org. My current certificate still works on tracker.d.o and the sso test URL. I created a new cert and imported it into my browser (Firefox ESR 91) and it worked for the sso.d.o test site and for tracker.d.o. I wasn't able to get curl working with either the old or new certs. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#997064: marked as done (emscripten: FTBFS: BlockingIOError: [Errno 11] write could not complete without blocking)
Your message dated Thu, 18 Nov 2021 01:18:50 + with message-id and subject line Bug#997064: fixed in emscripten 2.0.26~dfsg-5 has caused the Debian Bug report #997064, regarding emscripten: FTBFS: BlockingIOError: [Errno 11] write could not complete without blocking 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.) -- 997064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emscripten Version: 2.0.26~dfsg-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): [...] > test_llvmswitch (test_core.wasm2js2) ... ok > test_llvmswitch (test_core.wasm2js3) ... ok > test_llvmswitch (test_core.wasm2jss) ... ok > test_llvmswitch (test_core.wasm2jsz) ... ok > test_llvmswitch (test_core.wasm3) ... ok > test_llvmswitch (test_core.wasms) ... > DONE: combining results on main thread > > Traceback (most recent call last): > File "/<>/tests/runner.py", line 398, in > sys.exit(main(sys.argv)) > File "/<>/tests/runner.py", line 387, in main > num_failures = run_tests(options, suites) > File "/<>/tests/runner.py", line 280, in run_tests > res = testRunner.run(suite) > File "/usr/lib/python3.9/unittest/runner.py", line 176, in run > test(result) > File "/usr/lib/python3.9/unittest/suite.py", line 84, in __call__ > return self.run(*args, **kwds) > File "/<>/tests/parallel_testsuite.py", line 53, in run > return self.combine_results(result, results) > File "/<>/tests/parallel_testsuite.py", line 112, in > combine_results > r.updateResult(result) > File "/<>/tests/parallel_testsuite.py", line 129, in > updateResult > result.startTest(self.test) > File "/usr/lib/python3.9/unittest/runner.py", line 56, in startTest > self.stream.flush() > BlockingIOError: [Errno 11] write could not complete without blocking > make[1]: *** [debian/rules:188: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/emscripten_2.0.26~dfsg-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: emscripten Source-Version: 2.0.26~dfsg-5 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of emscripten, 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 emscripten 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, 18 Nov 2021 04:44:14 +0100 Source: emscripten Architecture: source Version: 2.0.26~dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 997064 Changes: emscripten (2.0.26~dfsg-5) unstable; urgency=medium . * add patch 2015 to bump expected binaryen version; update and tighten (build-)dependency on binaryen, and while at it add an upper limit as well * update copyright info: + use Reference field (not License-Reference); tighten lintian overrides * add patch cherry-picked upstream to use command -v (not which) * limit parallel builds to max 2 cores; hopefully closes: bug#997064, thanks to Lucas Nussbaum * add patch 2013 to use system shared NodeJS modules * work around dh_sphinx mysteriously failing Checksums-Sha1: f54ce677be915d975259e60b34b1d504c4575c5b 2565 emscripten_2.0.26~dfsg-5.dsc 121ef75961ee5531fa0da25e9e1eafd992a913b2 81928
Bug#996386: other error with mechanize 2.7.7-3
The error in the log comes from ruby-mechanize < 2.7.7-3 not depending
on ruby-webrick.
Now, there are 7 test failures of the following kind:
> 1) ShamRack mounted Rack application can be accessed using open-uri
> Failure/Error: response = open("http://www.greetings.com;)
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://www.greetings.com
> # ./spec/sham_rack_spec.rb:42:in `initialize'
> # ./spec/sham_rack_spec.rb:42:in `open'
> # ./spec/sham_rack_spec.rb:42:in `block (3 levels) in '
>
> 2) ShamRack.at with a block mounts associated block as an app
> Failure/Error: expect(open("http://simple.xyz;).read).to eq("Easy, huh?")
>
> Errno::ENOENT:
>No such file or directory @ rb_sysopen - http://simple.xyz
> # ./spec/sham_rack_spec.rb:76:in `initialize'
> # ./spec/sham_rack_spec.rb:76:in `open'
> # ./spec/sham_rack_spec.rb:76:in `block (4 levels) in '
log attached.
Cheers,
Cédricsbuild (Debian sbuild) 0.81.2 (31 January 2021) on kashan
+==+
| ruby-sham-rack 1.4.1-2 (amd64) Thu, 18 Nov 2021 00:00:33 + |
+==+
Package: ruby-sham-rack
Version: 1.4.1-2
Source Version: 1.4.1-2
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-7945e2af-3685-497b-8e1b-182c61bf38b0'
with '<>'
I: NOTICE: Log filtering will replace
'build/ruby-sham-rack-hdLhOr/resolver-A62XUh' with '<>'
+--+
| Update chroot|
+--+
Get:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Ign:1 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ InRelease
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:2 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Release
[951 B]
Get:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Ign:3 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./
Release.gpg
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[659 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Err:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
Could not open file
/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive/./Packages - open (13:
Permission denied)
Get:4 file:/build/ruby-sham-rack-hdLhOr/resolver-1wnZQ4/apt_archive ./ Packages
[1084 B]
Get:6 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Ign:6 http://deb.debian.org/debian unstable/main Sources.diff/Index
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
[63.6 kB]
Ign:7 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:8 http://deb.debian.org/debian unstable/main Sources [9378 kB]
Get:9 http://deb.debian.org/debian unstable/main amd64 Packages [8838 kB]
Fetched 18.5 MB in 2s (8057 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were automatically installed and are no longer required:
fontconfig-config fonts-dejavu-core libbrotli1 libbsd0 libc-devtools
libdeflate0 libexpat1 libfontconfig1 libfreetype6 libgd3 libjbig0
libjpeg62-turbo libmd0 libpng16-16 libtiff5 libwebp6 libx11-6 libx11-data
libxau6 libxcb1 libxdmcp6 libxpm4 manpages manpages-dev sensible-utils ucf
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
libsemanage2 libsepol2
The following packages will be upgraded:
apt bash binutils binutils-common binutils-x86-64-linux-gnu coreutils cpp-10
dash debconf g++-10 gcc-10 gcc-10-base libapt-pkg6.0 libbinutils
libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libdebconfclient0 libexpat1
libgcc-10-dev libgmp10 libjpeg62-turbo libpcre2-8-0 libselinux1
libsemanage-common libsemanage1 libstdc++-10-dev libsystemd0 libtasn1-6
libtinfo6 libudev1 linux-libc-dev login ncurses-base ncurses-bin passwd
tzdata
38 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.1 MB/58.4 MB of archives.
After this operation, 980 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 g++-10 amd64 10.3.0-12
[9433 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 gcc-10 amd64 10.3.0-12
[17.1 MB]
Get:3 http://deb.debian.org/debian unstable/main amd64 cpp-10 amd64 10.3.0-12
[8571 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 35.1 MB
Processed: Re: blist: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #983996 [src:blist] blist: ftbfs with GCC-11 Added tag(s) patch. -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983996: blist: ftbfs with GCC-11
Package: blist Version: 1.3.6-7 Followup-For: Bug #983996 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Hello, I've been able to get blist to build with gcc-11 in Ubuntu by reducing the optimization level from -O2 (default) to -O1. Please see the attached patch. Trying to debug the binary built with -O2 under gdb, I find that all the variables are optimized out, making it difficult to figure out what's actually happening. So at least for now, reducing the optimization seems a reasonable workaround IMHO. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru blist-1.3.6/debian/rules blist-1.3.6/debian/rules --- blist-1.3.6/debian/rules2020-10-15 10:05:56.0 -0700 +++ blist-1.3.6/debian/rules2021-11-17 15:45:43.0 -0800 @@ -1,5 +1,7 @@ #!/usr/bin/make -f +export DEB_CFLAGS_MAINT_APPEND=-O1 + export DH_VERBOSE=1 export PYBUILD_NAME=blist
Bug#997102: marked as done (ktexteditor: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Wed, 17 Nov 2021 23:57:38 +
with message-id
and subject line Bug#997102: fixed in ktexteditor 5.88.0-1
has caused the Debian Bug report #997102,
regarding ktexteditor: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output below
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.)
--
997102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ktexteditor
Version: 5.86.0-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):
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkf5texteditor5/DEBIAN/symbols doesn't
> match completely debian/libkf5texteditor5.symbols
> --- debian/libkf5texteditor5.symbols (libkf5texteditor5_5.86.0-1_amd64)
> +++ dpkg-gensymbols6KvvtC 2021-10-23 07:16:09.239078676 +
> @@ -2164,7 +2164,7 @@
> _ZNK11KTextEditor9Attribute4nameEv@Base 5.9.0
> _ZNK11KTextEditor9Attribute7outlineEv@Base 5.9.0
> _ZNK11KTextEditor9Attribute8fontBoldEv@Base 5.9.0
> -
> (optional=templinst)_ZNK12KConfigGroup9readEntryI10QByteArrayEET_PKcRKS2_@Base
> 5.49.0
> +#MISSING: 5.86.0-1#
> (optional=templinst)_ZNK12KConfigGroup9readEntryI10QByteArrayEET_PKcRKS2_@Base
> 5.49.0
> (optional=templinst|arch=amd64 arm64 hppa
> x32)_ZNK12KConfigGroup9readEntryI5QFontEET_PKcRKS2_@Base 5.9.0
> (optional=templinst)_ZNK12KConfigGroup9readEntryI6QColorEET_PKcRKS2_@Base
> 5.9.0
> (optional=templinst)_ZNK12KConfigGroup9readEntryIbEE5QListIT_EPKcRKS3_@Base
> 5.9.0
> @@ -2423,14 +2423,15 @@
> _ZNK7KateCmd11fromHistoryEi@Base 5.9.0
> _ZNK7KateCmd12queryCommandERK7QString@Base 5.9.0
> _ZNK7KateCmd8commandsEv@Base 5.9.0
> -
> (optional=templinst|subst)_ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIPN19KateCompletionModel4ItemESt6vectorIS3_SaIS3_S3_EC1ES8_{ssize_t}@Base
> 5.85.0
> -
> (optional=templinst|subst)_ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIPN19KateCompletionModel4ItemESt6vectorIS3_SaIS3_S3_EC2ES8_{ssize_t}@Base
> 5.85.0
> +
> _ZNSt10_HashtableItSt4pairIKtsESaIS2_ENSt8__detail10_Select1stESt8equal_toItESt4hashItENS4_18_Mod_range_hashingENS4_20_Default_ranged_hashENS4_20_Prime_rehash_policyENS4_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNS4_10_Hash_nodeIS2_Lb0EEEm@Base
> 5.86.0-1
> +#MISSING: 5.86.0-1#
> (optional=templinst|subst)_ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIPN19KateCompletionModel4ItemESt6vectorIS3_SaIS3_S3_EC1ES8_{ssize_t}@Base
> 5.85.0
> +#MISSING: 5.86.0-1#
> (optional=templinst|subst)_ZNSt17_Temporary_bufferIN9__gnu_cxx17__normal_iteratorIPN19KateCompletionModel4ItemESt6vectorIS3_SaIS3_S3_EC2ES8_{ssize_t}@Base
> 5.85.0
>
> _ZNSt6vectorI7QStringSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
> 5.84.0
>
> (optional=templinst)_ZNSt6vectorIN11KTextEditor5RangeESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
> 5.54.0
> (optional=templinst|arch=!alpha !amd64 !arm64 !mips64el !ppc64 !ppc64el
> !riscv64
> !s390x)_ZNSt6vectorIN19KSyntaxHighlighting6FormatESaIS1_EE17_M_default_appendEj@Base
> 5.51.0
> (optional=templinst|arch=alpha amd64 arm64 mips64el ppc64 ppc64el riscv64
> s390x)_ZNSt6vectorIN19KSyntaxHighlighting6FormatESaIS1_EE17_M_default_appendEm@Base
> 5.50.0
>
> (optional=templinst)_ZNSt6vectorIN19KSyntaxHighlighting6FormatESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
> 5.50.0
> -
> (optional=templinst)_ZNSt6vectorIN19KateCompletionModel4ItemESaIS1_EE13_M_insert_auxIS1_EEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEOT_@Base
> 5.84.0
> +#MISSING: 5.86.0-1#
> (optional=templinst)_ZNSt6vectorIN19KateCompletionModel4ItemESaIS1_EE13_M_insert_auxIS1_EEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEOT_@Base
> 5.84.0
>
> _ZNSt6vectorIN19KateCompletionModel4ItemESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
> 5.84.0
>
> _ZNSt6vectorIN19KateCompletionModel4ItemESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
> 5.84.0
>
>
Bug#996518: marked as done (ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m)
Your message dated Wed, 17 Nov 2021 23:58:19 + with message-id and subject line Bug#996518: fixed in ruby-typhoeus 1.4.0-2 has caused the Debian Bug report #996518, regarding ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m 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.) -- 996518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-typhoeus Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-typhoeus was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: require 'rack/handler/webrick' > > LoadError: > cannot load such file -- webrick > # > :85:in > `require' > # > :85:in > `require' > # /usr/lib/ruby/vendor_ruby/rack/handler/webrick.rb:3:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/support/localhost_server.rb:2:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/spec_helper.rb:9:in `block in ' > # ./spec/spec_helper.rb:9:in `each' > # ./spec/spec_helper.rb:9:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/typhoeus_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in > `load' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in > `load_file_handling_errors' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1606:in > `block in load_spec_files' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in > `each' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in > `load_spec_files' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:102:in > `setup' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:86:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45:in > `invoke' > # /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4:in > `' > No examples found. > > Finished in 0.6 seconds (files took 2.62 seconds to load) > 0 examples, 0 failures, 35 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-typhoeus/ruby-typhoeus_1.4.0-1+rebuild1633397810_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-typhoeus Source-Version: 1.4.0-2 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-typhoeus, 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. Cédric Boutillier (supplier of updated ruby-typhoeus 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, 18 Nov 2021 00:28:31 +0100 Source: ruby-typhoeus Architecture: source Version: 1.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier
Processed: Bug#996518 marked as pending in ruby-typhoeus
Processing control commands: > tag -1 pending Bug #996518 [src:ruby-typhoeus] ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m Added tag(s) pending. -- 996518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996518: marked as pending in ruby-typhoeus
Control: tag -1 pending Hello, Bug #996518 in ruby-typhoeus 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/ruby-team/ruby-typhoeus/-/commit/2c84dedfbe670b56f271ff22f0299d875f5ff68b build-depend on ruby-webrick (Closes: #996518) (this message was generated automatically) -- Greetings https://bugs.debian.org/996518
Bug#996871: wmnet: crashes on launch
On Tue, Oct 19, 2021 at 07:48:57PM -0700, Thomas Groman wrote: > Package: wmnet > Version: 1.06-1+b2 > Severity: grave > Justification: renders package unusable > > Launching wmnet causes it to crash on launch with the following output: > $ wmnet > wmnet: using devstats driver to monitor eth0 > X Error of failed request: BadName (named color or font does not exist) > Major opcode of failed request: 45 (X_OpenFont) > Serial number of failed request: 36 > Current serial number in output stream: 39 > > I expect it to launch an Xwindow and display things. If it requires a > specific > font I expect that to be part of the package's dependencies. Thanks for the bug report. Can you confirm that xfonts-base is the package that is missing in the dependencies? Thanks Adrian
Bug#996523: marked as done (ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)
Your message dated Wed, 17 Nov 2021 23:18:40 +
with message-id
and subject line Bug#996523: fixed in ruby-websocket 1.2.9-2
has caused the Debian Bug report #996523,
regarding ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
cannot load such file -- webrick
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.)
--
996523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-websocket
Version: 1.2.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-websocket was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> cannot load such file -- webrick
> # ./spec/support/all_server_drafts.rb:3:in `'
> # ./spec/spec_helper.rb:6:in `block in '
> # ./spec/spec_helper.rb:6:in `each'
> # ./spec/spec_helper.rb:6:in `'
> # ./spec/handshake/server_76_spec.rb:3:in `'
> No examples found.
>
> Finished in 0.5 seconds (files took 1.11 seconds to load)
> 0 examples, 0 failures, 20 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-websocket/ruby-websocket_1.2.8-2+rebuild1633398813_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-websocket
Source-Version: 1.2.9-2
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-websocket, 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.
Cédric Boutillier (supplier of updated ruby-websocket
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, 17 Nov 2021 23:35:39 +0100
Source: ruby-websocket
Architecture: source
Version: 1.2.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Cédric Boutillier
Closes: 996523
Changes:
ruby-websocket (1.2.9-2) unstable; urgency=medium
.
* Team upload
.
[ Utkarsh Gupta ]
* Add salsa-ci.yml
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update watch file format version to 4.
* Bump debhelper from old 12 to 13.
.
[ Manas Kashyap ]
* New Upstream release
.
[ Cédric Boutillier ]
* Build-depend on ruby-webrick (Closes: #996523)
* Use gem install layout
* Rules-Requires-Root set to 'no'
* Remove explicit dependency on ruby interpreter
* Add ${ruby:Depends}
Checksums-Sha1:
22728e7ad3b3c1171fedf48415f49399240aa491 1484 ruby-websocket_1.2.9-2.dsc
e1dfb721e09777435ba3aeddd9114c7b394c7a78 24939 ruby-websocket_1.2.9.orig.tar.gz
cfacc1c1e95c10d7797a26a2fdbbd64a04227be2 2500
ruby-websocket_1.2.9-2.debian.tar.xz
1bf086cd74fc0da4383c03448a372d9b534b8109 8723
ruby-websocket_1.2.9-2_amd64.buildinfo
Checksums-Sha256:
e5adc3d3eddfeea163ca1f822207cb76d48ab940f5af3b8d2991c64f83e17eff 1484
ruby-websocket_1.2.9-2.dsc
3687100b2636684e7a40d3fda9ea5a13ce1a32f0f45acee267d04cc89328e6e5 24939
ruby-websocket_1.2.9.orig.tar.gz
f5070474d4209bad83cae494acfa37f8c8f51a48758578e809bc2177a49b3c2f 2500
ruby-websocket_1.2.9-2.debian.tar.xz
Processed: Bug#996523 marked as pending in ruby-websocket
Processing control commands: > tag -1 pending Bug #996523 [src:ruby-websocket] ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick Added tag(s) pending. -- 996523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996523: marked as pending in ruby-websocket
Control: tag -1 pending Hello, Bug #996523 in ruby-websocket 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/ruby-team/ruby-websocket/-/commit/5c6191644cb3e7b4a1c253a191eda21f2132e4ea Build-depend on ruby-webrick (Closes: #996523) (this message was generated automatically) -- Greetings https://bugs.debian.org/996523
Bug#995220: Components to add to ts-node
$ pkgjs-depends ts-node DEPENDENCIES: node-acorn (acorn, acorn-walk) node-arg (arg) node-create-require (create-require) node-diff (diff) node-make-error (make-error) node-yn (yn) MISSING: ts-node └── @cspotcode/source-map-support (0.7.0) └── @cspotcode/source-map-consumer (0.8.0) └── @tsconfig/node10 (1.0.8) └── @tsconfig/node12 (1.0.9) └── @tsconfig/node14 (1.0.1) └── @tsconfig/node16 (1.0.2)
Bug#998575: marked as done (bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1))
Your message dated Wed, 17 Nov 2021 21:48:39 + with message-id and subject line Bug#998575: fixed in bind-dyndb-ldap 11.9-4 has caused the Debian Bug report #998575, regarding bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-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.) -- 998575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind-dyndb-ldap Version: 11.9-3 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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), bind9-dev, libkrb5-dev, > libldap2-dev, libsasl2-dev, uuid-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), bind9-dev, libkrb5-dev, > libldap2-dev, libsasl2-dev, uuid-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [397 B] > Get:5 copy:/<>/apt_archive ./ Packages [481 B] > Fetched 1835 B in 0s (179 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going 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/11/04/bind-dyndb-ldap_11.9-3_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: bind-dyndb-ldap Source-Version: 11.9-4 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of bind-dyndb-ldap, 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. Timo Aaltonen (supplier of updated bind-dyndb-ldap 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, 17 Nov 2021 23:24:37 +0200 Source: bind-dyndb-ldap Built-For-Profiles: noudeb Architecture: source Version: 11.9-4 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team Changed-By: Timo Aaltonen Closes: 998575 999463 Changes: bind-dyndb-ldap (11.9-4) unstable; urgency=medium . * Rebuild against bind9 9.17.19-3. (Closes: #998575, #999463) * Fix keytab name. * hardcode-version.diff: Hardcode the abi version. * fix-atomics.diff: Set GNUC_ATOMICS. * use-isc_result_totext.diff: Migrate to isc_result_totext. * use-dns_name_copy.diff: Use dns_name_copy.
Bug#999764: marked as done (gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming)
Your message dated Wed, 17 Nov 2021 21:34:04 + with message-id and subject line Bug#999764: fixed in gcc-12 12-2027-1 has caused the Debian Bug report #999764, regarding gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming 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.) -- 999764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-12 Version: 12-2023-1 Severity: serious To avoid repeating this bug on every new major upstrema release, I'd suggest to add Conflicts+Replaces+Provides: some-new-virtual-package to all intentionally not co-installable packages in addition to the Breaks+Replaces that is needed now. File conflicts with src:gcc-11: gcc-12-locales: usr/share/locale/be/LC_MESSAGES/cpplib-11.mo usr/share/locale/be/LC_MESSAGES/gcc-11.mo usr/share/locale/ca/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/gcc-11.mo usr/share/locale/de/LC_MESSAGES/cpplib-11.mo usr/share/locale/de/LC_MESSAGES/gcc-11.mo usr/share/locale/el/LC_MESSAGES/cpplib-11.mo usr/share/locale/el/LC_MESSAGES/gcc-11.mo usr/share/locale/eo/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/gcc-11.mo usr/share/locale/fi/LC_MESSAGES/cpplib-11.mo usr/share/locale/fi/LC_MESSAGES/gcc-11.mo usr/share/locale/fr/LC_MESSAGES/cpplib-11.mo usr/share/locale/fr/LC_MESSAGES/gcc-11.mo usr/share/locale/hr/LC_MESSAGES/gcc-11.mo usr/share/locale/id/LC_MESSAGES/cpplib-11.mo usr/share/locale/id/LC_MESSAGES/gcc-11.mo usr/share/locale/ja/LC_MESSAGES/cpplib-11.mo usr/share/locale/ja/LC_MESSAGES/gcc-11.mo usr/share/locale/nl/LC_MESSAGES/cpplib-11.mo usr/share/locale/nl/LC_MESSAGES/gcc-11.mo usr/share/locale/pt_BR/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/gcc-11.mo usr/share/locale/sr/LC_MESSAGES/cpplib-11.mo usr/share/locale/sr/LC_MESSAGES/gcc-11.mo usr/share/locale/sv/LC_MESSAGES/cpplib-11.mo usr/share/locale/sv/LC_MESSAGES/gcc-11.mo usr/share/locale/tr/LC_MESSAGES/cpplib-11.mo usr/share/locale/tr/LC_MESSAGES/gcc-11.mo usr/share/locale/uk/LC_MESSAGES/cpplib-11.mo usr/share/locale/uk/LC_MESSAGES/gcc-11.mo usr/share/locale/vi/LC_MESSAGES/cpplib-11.mo usr/share/locale/vi/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_CN/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_CN/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_TW/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_TW/LC_MESSAGES/gcc-11.mo gnat-12: usr/bin/gnat usr/bin/gnatbind usr/bin/gnatchop usr/bin/gnatclean usr/bin/gnatgcc usr/bin/gnathtml usr/bin/gnatkr usr/bin/gnatlink usr/bin/gnatls usr/bin/gnatmake usr/bin/gnatname usr/bin/gnatprep usr/bin/x86_64-linux-gnu-gnat usr/bin/x86_64-linux-gnu-gnatbind usr/bin/x86_64-linux-gnu-gnatchop usr/bin/x86_64-linux-gnu-gnatclean usr/bin/x86_64-linux-gnu-gnatgcc usr/bin/x86_64-linux-gnu-gnathtml usr/bin/x86_64-linux-gnu-gnatkr usr/bin/x86_64-linux-gnu-gnatlink usr/bin/x86_64-linux-gnu-gnatls usr/bin/x86_64-linux-gnu-gnatmake usr/bin/x86_64-linux-gnu-gnatname usr/bin/x86_64-linux-gnu-gnatprep usr/lib/x86_64-linux-gnu/libgnarl.so usr/lib/x86_64-linux-gnu/libgnat.so usr/share/man/man1/gnat.1.gz usr/share/man/man1/gnatbind.1.gz usr/share/man/man1/gnatchop.1.gz usr/share/man/man1/gnatclean.1.gz usr/share/man/man1/gnathtml.1.gz usr/share/man/man1/gnatkr.1.gz usr/share/man/man1/gnatlink.1.gz usr/share/man/man1/gnatls.1.gz usr/share/man/man1/gnatmake.1.gz usr/share/man/man1/gnatname.1.gz usr/share/man/man1/gnatprep.1.gz usr/share/man/man1/x86_64-linux-gnu-gnat.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatbind.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatchop.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatclean.1.gz usr/share/man/man1/x86_64-linux-gnu-gnathtml.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatkr.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatlink.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatls.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatmake.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatname.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatprep.1.gz libstdc++6-12-dbg: usr/lib/x86_64-linux-gnu/debug/libstdc++.a usr/lib/x86_64-linux-gnu/debug/libstdc++.so usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6 usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a lib32stdc++6-12-dbg: usr/lib32/debug/libstdc++.a usr/lib32/debug/libstdc++.so usr/lib32/debug/libstdc++.so.6 usr/lib32/debug/libstdc++fs.a libx32stdc++6-12-dbg: usr/libx32/debug/libstdc++.a usr/libx32/debug/libstdc++.so usr/libx32/debug/libstdc++.so.6 usr
Bug#984006: marked as done (caja-eiciel: ftbfs with GCC-11)
Your message dated Wed, 17 Nov 2021 21:33:43 + with message-id and subject line Bug#984006: fixed in caja-eiciel 1.20.1-3 has caused the Debian Bug report #984006, regarding caja-eiciel: 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.) -- 984006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:caja-eiciel Version: 1.20.1-2 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/caja-eiciel_1.20.1-2_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. [...] checking for caja extensions directory... /usr/lib/x86_64-linux-gnu/caja/extensions-2.0 checking for extended user attributes support... yes, since we are in GNU/Linux checking sys/xattr.h usability... yes checking sys/xattr.h presence... yes checking for sys/xattr.h... yes checking sys/acl.h usability... yes checking sys/acl.h presence... yes checking for sys/acl.h... yes checking acl/libacl.h usability... yes checking acl/libacl.h presence... yes checking for acl/libacl.h... yes checking for acl_get_perm_np... no checking for acl_get_perm in -lacl... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating img/Makefile config.status: creating po/Makefile.in config.status: creating man/Makefile config.status: creating doc/Makefile config.status: creating doc/C/Makefile config.status: creating doc/C/figures/Makefile config.status: creating config.hpp config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile config.status: executing depfiles commands config.status: executing libtool commands dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -DDATADIR="\"/usr/share\"" -DPKGDATADIR="\"/usr/share/mate-eiciel\"" -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -I/usr/include/atkmm-1.6 -I/usr/include/gtk-3.0/unix-print -I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/caja -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include /fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
Bug#984006: marked as pending in caja-eiciel
Control: tag -1 pending Hello, Bug #984006 in caja-eiciel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-mate-team/caja-eiciel/-/commit/2166da9391291b58e8831d185e991e52056a6e58 debian/patches: Add 1004_remove-dynamic-exception-specifications.patch. Dynamic exception specifications are deprecated since C++11 and fail in C++17. (Closes: #984006). (this message was generated automatically) -- Greetings https://bugs.debian.org/984006
Processed: Bug#984006 marked as pending in caja-eiciel
Processing control commands: > tag -1 pending Bug #984006 [src:caja-eiciel] caja-eiciel: ftbfs with GCC-11 Added tag(s) pending. -- 984006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996353: marked as done (ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Wed, 17 Nov 2021 21:20:45 + with message-id and subject line Bug#996353: fixed in ruby-rack 2.1.4-4 has caused the Debian Bug report #996353, regarding ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rack Version: 2.2.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rack was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rack\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-rack/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -I"lib:test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" > "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" > "test/spec_chunked.rb" "test/spec_common_logger.rb" > "test/spec_conditional_get.rb" "test/spec_config.rb" > "test/spec_content_length.rb" "test/spec_content_type.rb" > "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" > "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" > "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" > "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" > "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" > "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" > "test/spec_request.rb" "test/spec_response.rb" > "test/spec_rewindable_input.rb" "test/spec_runtime.rb" > "test/spec_sendfile.rb" "test/spec_server.rb" > "test/spec_session_abstract_id.rb" "test/spec_session_abstract_persisted.rb" > "test/spec_session_abstract_persisted_secure_secure_session_hash.rb" > "test/spec_session_abstract_session_hash.rb" "test/spec_session_cookie.rb" > "test/spec_session_pool.rb" "test/spec_show_exceptions.rb" > "test/spec_show_status.rb" "test/spec_static.rb" > "test/spec_tempfile_reaper.rb" "test/spec_thin.rb" "test/spec_urlmap.rb" > "test/spec_utils.rb" "test/spec_version.rb" "test/spec_webrick.rb" > "test/gemloader.rb" > > File does not exist: webrick > > rake aborted! > Command failed with status (1): [ruby -I"lib:test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" > "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" > "test/spec_chunked.rb" "test/spec_common_logger.rb" > "test/spec_conditional_get.rb" "test/spec_config.rb" > "test/spec_content_length.rb" "test/spec_content_type.rb" > "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" > "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" > "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" > "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" > "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" > "test/spec_multipart.rb" "test/spec_null_logger.rb"
Bug#996353: marked as pending in ruby-rack
Control: tag -1 pending Hello, Bug #996353 in ruby-rack 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/ruby-team/ruby-rack/-/commit/a8c225e28999038432249af1b24e85a9203723cc Build-depend on ruby-webrick (Closes: #996353) (this message was generated automatically) -- Greetings https://bugs.debian.org/996353
Processed: Bug#996353 marked as pending in ruby-rack
Processing control commands: > tag -1 pending Bug #996353 [src:ruby-rack] ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999819: marked as done (node-regexpu-core build-depends on removed package.)
Your message dated Wed, 17 Nov 2021 21:05:51 + with message-id and subject line Bug#999819: fixed in node-regexpu-core 4.8.0-1 has caused the Debian Bug report #999819, regarding node-regexpu-core build-depends on removed package. 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.) -- 999819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-regexpu-core Version: 4.7.1-3 Severity: serious node-regexpu-core build-depends on node-unicode-13.0.0 which is no longer built by the node-unicode-data source package. It is still present in unstable as a cruft package but is completely gone from testing. The package appears to have been replaced by node-unicode-14.0.0 --- End Message --- --- Begin Message --- Source: node-regexpu-core Source-Version: 4.8.0-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-regexpu-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-regexpu-core 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, 17 Nov 2021 21:35:51 +0100 Source: node-regexpu-core Architecture: source Version: 4.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 999819 Changes: node-regexpu-core (4.8.0-1) unstable; urgency=medium . * Team upload * Fix filenamemangle * Drop dependency to nodejs * New upstream version 4.8.0 (Closes: #999819) * Drop patch * Update build dependencies Checksums-Sha1: 4ab56d746b13b46f2f1082c2952b24c7bd746ddb 2317 node-regexpu-core_4.8.0-1.dsc e97988d668bafa82cb1097d6a20a077b22355036 20951 node-regexpu-core_4.8.0.orig.tar.gz 7558dbbebfa7b828520a83c8dcdd488fa9791cda 5200 node-regexpu-core_4.8.0-1.debian.tar.xz Checksums-Sha256: 2a80eefd0702663c062751c706fccb8bbff0579eb7b4eba36ecdf1509f2f6c52 2317 node-regexpu-core_4.8.0-1.dsc 26ef74a56fdce8c883e50368ecee6c828c3fe15b0479062391da14fc87a621ad 20951 node-regexpu-core_4.8.0.orig.tar.gz 7213d19d014d6c8c2943a39a4afc2b004e5b7236f5dbdf3894a093d486783242 5200 node-regexpu-core_4.8.0-1.debian.tar.xz Files: c4d9ad2515f8f0eeb9f27341266df289 2317 javascript optional node-regexpu-core_4.8.0-1.dsc a3307281f1831b9edb03bef8215a882b 20951 javascript optional node-regexpu-core_4.8.0.orig.tar.gz 51752cf81f1f71e3739c5e94c23868c8 5200 javascript optional node-regexpu-core_4.8.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGVaCMACgkQ9tdMp8mZ 7ukkORAAjQbAENuhpGPtWS76+TIqyOX+uULRcQVQLJXLfiTdPK+Lk9ti8MfewWFA Ab3H/y6BzKXwtwRUEtJKKXU5UQOPhv5pZtx4R+3xmcbY2LsATaNx1zR3xWNXd4NK Nfeiw5kWqe0k8RZtMWJHZXFad/sz1rMcYZchZ3pD7foNkM7Q5q2CeonwBjdN//gQ 0cyb3ZguUfnVqYrBQlXo+z56URJD+Co7F3vlaZm70PdvG9TXitq6uRIfQyK43BLj VjLhqi7j2MiBeGKt74SLVZAB3QnWq0TTjW+DjMEwctIGKvJIl019wOtvoka+mc2X Pi8TR4E8vMZe+g/+rXJ7iKlHzbidkYs4pqhyCLhRx7TOUBB1njnvxVN1A+Ki2wdC D0fCWncyWJi/wQ1497i/iIO1VsS4gVVJx2nWO8vRCf/OyFoYBIreeNaSsAue2tvf 1rt5TXiAb+FRTKrAN/1bnJ75PnXMKANq4O0NfYqwLZ1/2D7M7qSjb8Mvg464n9Nv CglgJ5xj5TH74f8Q0QzLkbayPfRQRjLH5gAI3lnf3mgRLeJ2OV26S6PS7Y53pHly vSLhOZzDr3TI0+TWWJjKAQfLrAuwhPR6ueyQ9xS0WB2OZICMLmr6UfMXkvFJb9Fa +tMAaCWKdZ/Y516BB/BItkU9fi9uj1sVh2Hb61nqx4lsiNdl3/8= =g+Tq -END PGP SIGNATURE End Message ---
Bug#996366: marked as done (ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax) { [min, max] } })
Your message dated Wed, 17 Nov 2021 21:06:25 +
with message-id
and subject line Bug#996366: fixed in ruby-regexp-parser 1.7.1-2
has caused the Debian Bug report #996366,
regarding ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax) {
[min, max] } }
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.)
--
996366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-regexp-parser
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-regexp-parser was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax)
> { [min, max] } }
>
> FrozenError:
> can't modify frozen object: 2..4
> # ./lib/regexp_parser/expression.rb:84:in `define_singleton_method'
> # ./lib/regexp_parser/expression.rb:84:in `block in repetitions'
> # :90:in `tap'
> # ./lib/regexp_parser/expression.rb:84:in `repetitions'
> # ./lib/regexp_parser/expression/methods/match_length.rb:11:in
> `initialize'
> # ./lib/regexp_parser/expression/methods/match_length.rb:102:in `new'
> # ./lib/regexp_parser/expression/methods/match_length.rb:102:in
> `match_length'
> # ./spec/expression/methods/match_length_spec.rb:157:in `block (3
> levels) in '
>
> Finished in 5.25 seconds (files took 1.46 seconds to load)
> 1498 examples, 23 failures
>
> Failed examples:
>
> rspec ./spec/expression/base_spec.rb:88 # Regexp::Expression::Base
> #repetitions
> rspec ./spec/expression/methods/match_length_spec.rb:15 # Regexp::MatchLength
> fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:16 # Regexp::MatchLength
> range quantified
> rspec ./spec/expression/methods/match_length_spec.rb:17 # Regexp::MatchLength
> nested quantified
> rspec ./spec/expression/methods/match_length_spec.rb:18 # Regexp::MatchLength
> open-end quantified
> rspec ./spec/expression/methods/match_length_spec.rb:24 # Regexp::MatchLength
> backreference
> rspec ./spec/expression/methods/match_length_spec.rb:25 # Regexp::MatchLength
> subexp call
> rspec ./spec/expression/methods/match_length_spec.rb:28 # Regexp::MatchLength
> quantified alternation
> rspec ./spec/expression/methods/match_length_spec.rb:65 #
> Regexp::MatchLength#include? fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:72 #
> Regexp::MatchLength#include? variably quantified
> rspec ./spec/expression/methods/match_length_spec.rb:78 #
> Regexp::MatchLength#include? nested quantified
> rspec ./spec/expression/methods/match_length_spec.rb:95 #
> Regexp::MatchLength#include? called on leaf node
> rspec ./spec/expression/methods/match_length_spec.rb:105 #
> Regexp::MatchLength#fixed? fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:106 #
> Regexp::MatchLength#fixed? variably quantified
> rspec ./spec/expression/methods/match_length_spec.rb:109 #
> Regexp::MatchLength#fixed? equal quantified branches
> rspec ./spec/expression/methods/match_length_spec.rb:110 #
> Regexp::MatchLength#fixed? unequal quantified branches
> rspec ./spec/expression/methods/match_length_spec.rb:115 #
> Regexp::MatchLength#each returns an Enumerator if called without a block
> rspec ./spec/expression/methods/match_length_spec.rb:123 #
> Regexp::MatchLength#each is aware of limit option even if called without a
> block
> rspec ./spec/expression/methods/match_length_spec.rb:130 #
> Regexp::MatchLength#each is limited to 1000 iterations in case there are
> infinite match lengths
> rspec ./spec/expression/methods/match_length_spec.rb:134 #
> Regexp::MatchLength#each scaffolds the Enumerable interface
> rspec ./spec/expression/methods/match_length_spec.rb:142 #
> Regexp::MatchLength#endless_each returns an Enumerator if called without a
> block
> rspec ./spec/expression/methods/match_length_spec.rb:150 #
> Regexp::MatchLength#endless_each never stops iterating for infinite match
> lengths
> rspec ./spec/expression/methods/match_length_spec.rb:156 #
> Regexp::MatchLength#inspect is nice
>
> /usr/bin/ruby3.0
>
Bug#996147: marked as done (ruby-capybara: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Wed, 17 Nov 2021 21:06:19 +
with message-id
and subject line Bug#996147: fixed in ruby-capybara 3.36.0+ds-1
has caused the Debian Bug report #996147,
regarding ruby-capybara: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
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.)
--
996147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara
Version: 3.12.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-capybara was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> ArgumentError:
> wrong number of arguments (given 4, expected 3)
> # ./lib/capybara/selector/filters/node_filter.rb:9:in `initialize'
> # ./lib/capybara/selector/filter_set.rb:115:in `new'
> # ./lib/capybara/selector/filter_set.rb:115:in `add_filter'
> # ./lib/capybara/selector/filter_set.rb:19:in `node_filter'
> # ./lib/capybara/selector.rb:5:in `block in '
> # ./lib/capybara/selector/filter_set.rb:15:in `instance_eval'
> # ./lib/capybara/selector/filter_set.rb:15:in `initialize'
> # ./lib/capybara/selector/filter_set.rb:77:in `new'
> # ./lib/capybara/selector/filter_set.rb:77:in `add'
> # ./lib/capybara/selector.rb:4:in `'
> # ./lib/capybara.rb:430:in `'
> # ./lib/capybara.rb:9:in `'
> # ./lib/capybara/spec/spec_helper.rb:5:in `'
> # ./spec/spec_helper.rb:4:in `'
> # ./spec/xpath_builder_spec.rb:3:in `'
> No examples found.
>
>
> Finished in 0.6 seconds (files took 1.85 seconds to load)
> 0 examples, 0 failures, 21 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-capybara/ruby-capybara_3.12.0-1+rebuild1633376144_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-capybara
Source-Version: 3.36.0+ds-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-capybara, 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.
Daniel Leidert (supplier of updated ruby-capybara 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, 17 Nov 2021 21:29:03 +0100
Source: ruby-capybara
Architecture: source
Version: 3.36.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 705739 996147
Changes:
ruby-capybara (3.36.0+ds-1) unstable; urgency=medium
.
* Team upload.
* New upstream version 3.36.0.
- Fixes keyword argument handling (closes: #996147).
.
[ Utkarsh Gupta ]
* Refresh patches
* Add Selenium::WebDriver BD dependency (closes: #705739).
* Add myself as the uploader
* Fix package wrt cme
* Drop dependency on ruby-interpreter
* Add salsa-ci.yml
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
* d/copyright: Exclude jquery files from the tarball. Add Upstream-Contact.
(Copyright): Add team.
* d/ruby-capybara.links: Remove file. Must be handled in d/rules.
* d/ruby-capybara.lintian-overrides: Adjust override.
* d/ruby-tests.rake: Update with gem2deb template.
* d/rules: Use gem installation layout. Ignore the test result with Ruby 3.0.
The tests explicitly mention to not have been tested with Ruby 3, but we
require this version of capybara urgently.
(override_dh_link): Add override to create jquery
Processed: Bug#996366 marked as pending in ruby-regexp-parser
Processing control commands:
> tag -1 pending
Bug #996366 [src:ruby-regexp-parser] ruby-regexp-parser: FTBFS with ruby3.0:
ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r|
r.define_singleton_method(:minmax) { [min, max] } }
Added tag(s) pending.
--
996366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996366: marked as pending in ruby-regexp-parser
Control: tag -1 pending Hello, Bug #996366 in ruby-regexp-parser 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/ruby-team/ruby-regexp-parser/-/commit/82a4d330a36ec918ed68ce49c677fcb36f324169 Fix FTBFS and Riby 3 compatibility * d/patches/996366-fix-frozenerror.patch: Add patch. - Don't modify range for Ruby 2.7+ (closes: #996366). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996366
Bug#999862: sso.debian.org: SSO no longer seems to work
Package: sso.debian.org Severity: serious I'm trying to log in to tracker.debian.org. I've manually created a fresh certificate and loaded it into both Firefox (94.0-1) and Chrome (from Google), I visit tracker.debian.org but it does not recognise it at all. I also tried curl, as described on the wiki page https://wiki.debian.org/DebianSingleSignOn: curl --key $USER.key --cert $USER.crt https://sso.debian.org/ca/test/env but that fails too. So it would seem that sso.debian.org may no longer be functional, which prevents me from logging into tracker.debian.org. I don't know if this is a bug with tracker.debian.org or with sso.debian.org so I'm starting with sso.debian.org. I know the Wiki says that SSO is deprecated, but it doesn't say that it's stopped entirely! Best wishes, Julian
Processed: teach the bts the right meta data
Processing commands for cont...@bugs.debian.org:
> reassign 999619 src:glusterfs 10.0-1
Bug #999619 {Done: Christian Ehrhardt }
[src:glusterfs, src:tgt] glusterfs breaks tgt autopkgtest: glfs not supported
Bug reassigned from package 'src:glusterfs, src:tgt' to 'src:glusterfs'.
No longer marked as found in versions glusterfs/10.0-1 and tgt/1:1.0.80-1.
No longer marked as fixed in versions glusterfs/10.0-1.2.
Bug #999619 {Done: Christian Ehrhardt }
[src:glusterfs] glusterfs breaks tgt autopkgtest: glfs not supported
Marked as found in versions glusterfs/10.0-1.
> fixed 999619 10.0-1.2
Bug #999619 {Done: Christian Ehrhardt }
[src:glusterfs] glusterfs breaks tgt autopkgtest: glfs not supported
Marked as fixed in versions glusterfs/10.0-1.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
999619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978836: marked as done (heimdal: ftbfs with autoconf 2.70)
Your message dated Thu, 18 Nov 2021 07:36:24 +1100
with message-id <87sfvuzfhz@canidae.wired.pri>
and subject line Re: Bug#978836: heimdal: ftbfs with autoconf 2.70
has caused the Debian Bug report #978836,
regarding heimdal: ftbfs with autoconf 2.70
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.)
--
978836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:heimdal
Version: 7.7.0+dfsg-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/heimdal_7.7.0+dfsg-2_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
./lib/autoconf/headers.m4:217: AC_CHECK_HEADERS is expanded from...
cf/test-package.m4:6: rk_TEST_PACKAGE is expanded from...
configure.ac:301: the top level
configure.ac:325: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:325: You should run autoupdate.
./lib/autoconf/headers.m4:696: AC_HEADER_TIME is expanded from...
configure.ac:325: the top level
configure.ac:329: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:329: You should run autoupdate.
./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from...
configure.ac:329: the top level
configure.ac:388: warning: Checking for headers with the preprocessor is
configure.ac:388: deprecated. Specify prerequisite code to AC_CHECK_HEADER
configure.ac:388: instead of using fourth argument `-'. (Many headers need
configure.ac:388: no prerequisites. If you truly need to test whether
configure.ac:388: something passes the preprocessor but not the compiler,
configure.ac:388: use AC_PREPROC_IFELSE.)
./lib/autoconf/headers.m4:115: _AC_CHECK_HEADER_PREPROC is expanded from...
./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from...
./lib/autoconf/headers.m4:217: AC_CHECK_HEADERS is expanded from...
configure.ac:388: the top level
configure.ac:575: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:575: You should run autoupdate.
./lib/autoconf/general.m4:190: AC_FOREACH is expanded from...
cf/destdirs.m4:5: rk_DESTDIRS is expanded from...
configure.ac:575: the top level
configure.ac:14: installing './compile'
configure.ac:10: installing './missing'
admin/Makefile.am: installing './depcomp'
patching file ./ltmain.sh
Hunk #1 succeeded at 7312 (offset 92 lines).
Hunk #2 succeeded at 7710 (offset 95 lines).
patching file ./lib/libedit/ltmain.sh
Hunk #1 succeeded at 7312 (offset 92 lines).
Hunk #2 succeeded at 7710 (offset 95 lines).
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security"
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" FCFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong" FFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong" GCJFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong"
LDFLAGS="-Wl,-z,relro -Wl,-z,now" OBJCFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" OBJCXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" \
--libexecdir="\${prefix}/sbin" \
--enable-shared \
--prefix=/usr \
--includedir="\${prefix}/include" \
--with-openldap=/usr \
--with-sqlite3=/usr \
--with-libedit=/usr \
--enable-kcm \
--with-hdbdir=/var/lib/heimdal-kdc \
--without-openssl \
--infodir="\${prefix}/share/info" \
--datarootdir="\${prefix}/share" \
--libdir="\${prefix}/lib/x86_64-linux-gnu" \
--without-krb4
./configure: line 2183: 5: Bad file descriptor
checking whether CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 is declared...
./configure: line 2185: test: too many arguments
cat: confdefs.h: No such file or directory
./configure: line 1867: 5: Bad file descriptor
./configure: line 1884: 5: Bad file descriptor
./configure: line
Bug#999860: python3-cylc fails to install
Package: python3-cylc Version: 8.0~b3-1 Severity: serious https://piuparts.debian.org/sid/fail/python3-cylc_8.0~b3-1.log ... Setting up python3-cylc (8.0~b3-1) ... File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/at.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/at.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/background.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/background.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/loadleveler.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/loadleveler.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/moab.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/moab.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/pbs.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/pbs.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/pbs_multi_cluster.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/pbs_multi_cluster.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/sge.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/sge.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_broadcast.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_broadcast.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_cat_log.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_cat_log.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_cycle_point.py", line 4 <<< HEAD:cylc/flow/scripts/cylc_cycle_point.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_diff.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_diff.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_ext_trigger.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_ext_trigger.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_function_run.py", line 2 <<< HEAD:cylc/flow/scripts/cylc_function_run.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_list.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_list.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_message.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_message.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_remote_tidy.py", line 2 <<< HEAD:cylc/flow/scripts/cylc_remote_tidy.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_report_timings.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_report_timings.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_run.py", line 1 <<< HEAD:cylc/flow/scripts/cylc_run.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_suite_state.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_suite_state.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_view.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_view.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/suite_events.py", line 1 <<< HEAD:cylc/flow/suite_events.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/cycling/__init__.py", line 1 <<< HEAD:cylc/flow/tests/cycling/__init__.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/cycling/test_cycling.py", line 1 <<< HEAD:cylc/flow/tests/cycling/test_cycling.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/cycling/test_integer.py", line 1 <<< HEAD:cylc/flow/tests/cycling/test_integer.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/cycling/test_iso8601.py", line 1 <<< HEAD:cylc/flow/tests/cycling/test_iso8601.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/parsec/test_empysupport.py", line 1 <<< HEAD:cylc/flow/tests/parsec/test_empysupport.py ^ SyntaxError: invalid syntax File
Bug#999819: marked as pending in node-regexpu-core
Control: tag -1 pending Hello, Bug #999819 in node-regexpu-core 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-regexpu-core/-/commit/ee0c32fa5b61d0a558997acaf2a5898a78759ff8 New upstream version 4.8.0 (Closes: #999819) (this message was generated automatically) -- Greetings https://bugs.debian.org/999819
Processed: Bug#999819 marked as pending in node-regexpu-core
Processing control commands: > tag -1 pending Bug #999819 [node-regexpu-core] node-regexpu-core build-depends on removed package. Ignoring request to alter tags of bug #999819 to the same tags previously set -- 999819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999819: marked as pending in node-regexpu-core
Control: tag -1 pending Hello, Bug #999819 in node-regexpu-core 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-regexpu-core/-/commit/ee0c32fa5b61d0a558997acaf2a5898a78759ff8 New upstream version 4.8.0 (Closes: #999819) (this message was generated automatically) -- Greetings https://bugs.debian.org/999819
Processed: Bug#999819 marked as pending in node-regexpu-core
Processing control commands: > tag -1 pending Bug #999819 [node-regexpu-core] node-regexpu-core build-depends on removed package. Added tag(s) pending. -- 999819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996147: marked as pending in ruby-capybara
Control: tag -1 pending Hello, Bug #996147 in ruby-capybara 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/ruby-team/ruby-capybara/-/commit/d8c2ed1980c13f17e9d2a2e4cfc2da4f284f84d4 ruby-capybara (3.36.0+ds-1) UNRELEASED * New upstream version 3.36.0. - Fixes keyword argument handling (closes: #996147). (this message was generated automatically) -- Greetings https://bugs.debian.org/996147
Processed: Bug#996147 marked as pending in ruby-capybara
Processing control commands: > tag -1 pending Bug #996147 [src:ruby-capybara] ruby-capybara: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984208: marked as done (libsass: ftbfs with GCC-11)
Your message dated Wed, 17 Nov 2021 19:51:09 +
with message-id
and subject line Bug#984208: fixed in libsass 3.6.5+2021-2
has caused the Debian Bug report #984208,
regarding libsass: 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.)
--
984208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsass
Version: 3.6.4+20201122-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/libsass_3.6.4+20201122-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.
[...]
+
_ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PKN4Sass10Color_RGBAEESaISC_ENSt8__detail10_Select1stESt8equal_toIS5_ESt4hashIS5_ENSE_18_Mod_range_hashingENSE_20_Default_ranged_hashENSE_20_Prime_rehash_policyENSE_17_Hashtable_traitsILb1ELb0ELb1D2Ev@Base
3.6.4+20201122-1
(optional=templinst|subst)_ZNSt10_HashtableIPKN4Sass14SimpleSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb19_M_rehashE{size_t}RK{size_t}@Base
3.6.4-2~
(optional=templinst)_ZNSt10_HashtableIPKN4Sass14SimpleSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb1D1Ev@Base
3.6.4-2~
(optional=templinst)_ZNSt10_HashtableIPKN4Sass14SimpleSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb1D2Ev@Base
3.6.4-2~
(optional=templinst|subst)_ZNSt10_HashtableIPKN4Sass15ComplexSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb19_M_rehashE{size_t}RK{size_t}@Base
3.6.4-2~
(optional=templinst)_ZNSt10_HashtableIPKN4Sass15ComplexSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb1D1Ev@Base
3.6.4-2~
(optional=templinst)_ZNSt10_HashtableIPKN4Sass15ComplexSelectorES3_SaIS3_ENSt8__detail9_IdentityENS0_14PtrObjEqualityENS0_10PtrObjHashENS5_18_Mod_range_hashingENS5_20_Default_ranged_hashENS5_20_Prime_rehash_policyENS5_17_Hashtable_traitsILb1ELb1ELb1D2Ev@Base
3.6.4-2~
-
(optional=templinst|subst)_ZNSt10_HashtableIiSt4pairIKiPKcESaIS4_ENSt8__detail10_Select1stESt8equal_toIiESt4hashIiENS6_18_Mod_range_hashingENS6_20_Default_ranged_hashENS6_20_Prime_rehash_policyENS6_17_Hashtable_traitsILb0ELb0ELb1C1IPKS4_EET_SL_{size_t}RKSB_RKSC_RKSD_RKS9_RKS7_RKS5_@Base
3.6.4-2~
-
Bug#999857: mod-wsgi FTBFS with python 3.10 as supported version
Source: mod-wsgi Version: 4.7.1-3 Severity: serious Tags: ftbfs bookworm sid Forwarded: https://github.com/GrahamDumpleton/mod_wsgi/pull/688 https://buildd.debian.org/status/logs.php?pkg=mod-wsgi=4.7.1-3%2Bb2 ... In file included from src/server/mod_wsgi.c:22: src/server/wsgi_python.h:44:10: fatal error: node.h: No such file or directory 44 | #include "node.h" | ^~~~ compilation terminated. apxs:Error: Command failed with rc=65536 . make[2]: *** [Makefile:31: src/server/mod_wsgi.la] Error 1
Bug#999856: cheetah with python 3.10 as supported version
Source: cheetah
Version: 3.2.6-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=cheetah=3.2.6-2%2Bb1
...
==
ERROR: test_import_bootlocale (Cheetah.Tests.ImportHooks.ImportHooksTest)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.10_cheetah/build/Cheetah/Tests/ImportHooks.py",
line 95, in test_import_bootlocale
import _bootlocale # noqa: F401 '_bootlocale' imported but unused
File
"/<>/.pybuild/cpython3_3.10_cheetah/build/Cheetah/ImportManager.py",
line 479, in importHook
raise ImportError("No module named %s" % fqname)
ImportError: No module named _bootlocale
--
Ran 2177 tests in 10.629s
FAILED (errors=1)
E: pybuild pybuild:354: test: plugin custom failed with: exit code=1: cp -va
Cheetah/Tests/ImportHooksTemplates
/<>/.pybuild/cpython3_3.10_cheetah/build/Cheetah/Tests/;
PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
python3.10
/<>/.pybuild/cpython3_3.10_cheetah/build/Cheetah/Tests/Test.py
I: pybuild base:237:cp -va Cheetah/Tests/ImportHooksTemplates
/<>/.pybuild/cpython3_3.9_cheetah/build/Cheetah/Tests/;
PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
python3.9
/<>/.pybuild/cpython3_3.9_cheetah/build/Cheetah/Tests/Test.py
'Cheetah/Tests/ImportHooksTemplates' ->
'/<>/.pybuild/cpython3_3.9_cheetah/build/Cheetah/Tests/ImportHooksTemplates'
'Cheetah/Tests/ImportHooksTemplates/index.tmpl' ->
'/<>/.pybuild/cpython3_3.9_cheetah/build/Cheetah/Tests/ImportHooksTemplates/index.tmpl'
'Cheetah/Tests/ImportHooksTemplates/layout.tmpl' ->
'/<>/.pybuild/cpython3_3.9_cheetah/build/Cheetah/Tests/ImportHooksTemplates/layout.tmpl'
...Sorry: RecursionError: maximum recursion depth exceeded during
compilation
..
--
Ran 2177 tests in 15.313s
OK
dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned
exit code 13
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 25
Bug#978836: heimdal: ftbfs with autoconf 2.70
There is an upstream fix available here: https://github.com/heimdal/heimdal/pull/771
Bug#996589: marked as done (cloudcompare FTBFS on !amd64)
Your message dated Wed, 17 Nov 2021 19:18:39 + with message-id and subject line Bug#996589: fixed in cloudcompare 2.11.3-4 has caused the Debian Bug report #996589, regarding cloudcompare FTBFS on !amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cloudcompare Version: 2.11.3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cloudcompare=2.11.3-2 There are at least two separate errors: ... /<>/plugins/core/Standard/qRANSAC_SD/RANSAC_SD_orig/MiscLib/AlignedAllocator.h: In member function ‘T* MiscLib::AlignedAllocator::allocate(MiscLib::AlignedAllocator::size_type, std::allocator::const_pointer)’: /<>/plugins/core/Standard/qRANSAC_SD/RANSAC_SD_orig/MiscLib/AlignedAllocator.h:30:29: error: there are no arguments to ‘aligned_alloc’ that depend on a template parameter, so a declaration of ‘aligned_alloc’ must be available [-fpermissive] 30 | #define a_malloc(sz, align) aligned_alloc((align), (sz)) | ^ ... ... make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libavutil.so', needed by 'plugins/core/Standard/qAnimation/libQANIMATION_PLUGIN.so'. Stop. make[3]: *** Waiting for unfinished jobs ... --- End Message --- --- Begin Message --- Source: cloudcompare Source-Version: 2.11.3-4 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of cloudcompare, 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. Gürkan Myczko (supplier of updated cloudcompare 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, 17 Nov 2021 12:08:34 +0100 Source: cloudcompare Architecture: source Version: 2.11.3-4 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 996589 Changes: cloudcompare (2.11.3-4) unstable; urgency=medium . * Apply patch to fix FTBFS. (Closes: #996589) Thanks Adrian Bunk. Checksums-Sha1: 803ae6d6ecab63dd25905fb21ac5cab6b362f865 2137 cloudcompare_2.11.3-4.dsc d637c5882aa8852335f14bd7de7ff0bc7b1e3d13 10648 cloudcompare_2.11.3-4.debian.tar.xz dd759182ef499798373a0475fb875be19fc54396 25073 cloudcompare_2.11.3-4_source.buildinfo Checksums-Sha256: c7f7058dfab5dfbf0dfe752fe5b3ab8bac9cdb43fdde87d8808e94f4bd1f1360 2137 cloudcompare_2.11.3-4.dsc e810c251fcf356cf5146d1151198b0ea4f5e8e1a611ef1da4a1064aa68970980 10648 cloudcompare_2.11.3-4.debian.tar.xz e04c8e2eb57446a122037e239a8b83e08ad923a06e68d3e13920004a23406469 25073 cloudcompare_2.11.3-4_source.buildinfo Files: 99191d91766d496123e25929300a7d18 2137 graphics optional cloudcompare_2.11.3-4.dsc 60c2b6c8f4fdccae1da6c11f6758437f 10648 graphics optional cloudcompare_2.11.3-4.debian.tar.xz 9d63ab2128752694ca7de7c1d8517d11 25073 graphics optional cloudcompare_2.11.3-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmGVUDEACgkQEWhSvN91 FcC9kRAAhK5LtAVlE3ZYRcU9VoPP1GNizqsHitGMZ9ZlYn+ZjVCEGB572HgxlgXY Ll3ZMSRF5XvJGKkIO7UHc3Rp4TYBVhZfwoecMA7ZNiM7OsZFSuJ7zlcOY6IDV+Bk U4/QGX8YllUjda10FkdjJrA2gFer65UEg0HhfljOf4glHqCMxeYIxmKyuIz1/bLI BE+drE1bLCrbRIwXD3XDdu/MdVTSM9JnURQSAgKxb9t78J/PR7DYSxWV/EZ0KwjE 9yc6abDIxeMV8toJwhbhMtOqHMSozQt3tasOXTUcPyjhx+J0xAOntoiFpKYIAC4J h2A+qX2PYkdSHGl2msAzkV6bPyp5ch5byvL9oRqWDI2b9FIT2ZypvhpoT5TFwF4E 4ttUcpYykkE/FOtNG2SOo9iRkLb+81ECWX8D9trkXbP4HFEU1KxulxbCqujtm/lA 82zqBRf70QiP4jAJDHOczr5wSZDcNz9GZ+0J60GtPjfPzCAozWAZbzhJow5tiBck ppTQKgZf7sesdv1OzaOL+6RkyiHVSmWI+C1UnDHLxJBbEKqYPH39Z+n/BzuLDlPN 8mzDWRBR0BJB1toleR/+fvFaew53xxp8ID/ZjfY8W6LIHn1HbfOQGVrDPtcmMD54 vSf9LD3fy+YZcSpYRLhkVpOdR60IC7PYIrZ3SN11oLqesG9NxH0= =+uQ2 -END PGP SIGNATURE End Message ---
Bug#998608: marked as done (canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17]
Your message dated Wed, 17 Nov 2021 18:19:07 + with message-id and subject line Bug#998608: fixed in canl-java 2.7.0-2 has caused the Debian Bug report #998608, regarding canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] is not abstract and does not override abstract method accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in org.apache.commons.io.file.PathFilter 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.) -- 998608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: canl-java Version: 2.7.0-1 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): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibcanl-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project eu.eu-emi.security:canl:jar:2.7.0 uses prerequisites > which is only intended for maven-plugin projects but not for non maven-plugin > projects. For such purposes you should use the maven-enforcer-plugin. See > https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html > [INFO] > [INFO] --< eu.eu-emi.security:canl > >--- > [INFO] Building canl 2.7.0 > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ canl > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ canl --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 167 source files to /<>/target/classes > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Some input files use or override a deprecated API. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] > eu.emi.security.authn.x509.helpers.trust.OpensslTruststoreHelper$1> is not > abstract and does not override abstract method > accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in > org.apache.commons.io.file.PathFilter > [INFO] 1 error > [INFO] - > [INFO] > [INFO] > > [INFO] Skipping canl > [INFO] This project has been banned from the build due to previous failures. > [INFO] > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.558 s > [INFO] Finished at: 2021-11-04T09:29:19Z > [INFO] > > [ERROR] Failed
Bug#999853: src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf
Source: boost1.74 Version: 1.74.0-9 Severity: serious Control: close -1 1.74.0-12 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:boost1.74 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build on armhf. 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=boost1.74 OpenPGP_signature Description: OpenPGP digital signature
Processed: src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf
Processing control commands: > close -1 1.74.0-12 Bug #999853 [src:boost1.74] src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf Marked as fixed in versions boost1.74/1.74.0-12. Bug #999853 [src:boost1.74] src:boost1.74: fails to migrate to testing for too long: FTBFS on armhf Marked Bug as done -- 999853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign bug to the package that closed it
Processing commands for cont...@bugs.debian.org:
> # The version tracking systems get confused if a package is closed by a
> package other than the one it's filed against
> reassign 999817 gcc-arm-none-eabi
Bug #999817 {Done: Keith Packard } [libstdc++-arm-none-eabi]
libstdc++-arm-none-eabi build-depends on removed package.
Bug reassigned from package 'libstdc++-arm-none-eabi' to 'gcc-arm-none-eabi'.
No longer marked as found in versions 13.
No longer marked as fixed in versions gcc-arm-none-eabi/15:10.3-2021.07-4.
> close 999817 15:10.3-2021.07-4
Bug #999817 {Done: Keith Packard } [gcc-arm-none-eabi]
libstdc++-arm-none-eabi build-depends on removed package.
There is no source info for the package 'gcc-arm-none-eabi' at version
'15:10.3-2021.07-4' with architecture ''
Unable to make a source version for version '15:10.3-2021.07-4'
Marked as fixed in versions 15:10.3-2021.07-4.
Bug #999817 {Done: Keith Packard } [gcc-arm-none-eabi]
libstdc++-arm-none-eabi build-depends on removed package.
Bug 999817 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
999817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999817: marked as done (libstdc++-arm-none-eabi build-depends on removed package.)
Your message dated Wed, 17 Nov 2021 17:49:02 + with message-id and subject line Bug#999817: fixed in gcc-arm-none-eabi 15:10.3-2021.07-4 has caused the Debian Bug report #999817, regarding libstdc++-arm-none-eabi build-depends on removed package. 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.) -- 999817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-arm-none-eabi Version: 13 Severity: serious x-debbugs-cc: kei...@debian.org libstdc++-arm-none-eabi build-depends on the gcc-arm-none-eabi-source binary package which is no longer built by the gcc-arm-none-eabi source package. It is still present in unstable as a cruft package but is completely gone from testing. Keith's comment when removing the package was "Why did this exist?", so I would guess that he did not check reverse build-dependencies. --- End Message --- --- Begin Message --- Source: gcc-arm-none-eabi Source-Version: 15:10.3-2021.07-4 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of gcc-arm-none-eabi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated gcc-arm-none-eabi 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, 17 Nov 2021 08:56:53 -0800 Source: gcc-arm-none-eabi Architecture: source Version: 15:10.3-2021.07-4 Distribution: unstable Urgency: medium Maintainer: Agustin Henze Changed-By: Keith Packard Closes: 999817 Changes: gcc-arm-none-eabi (15:10.3-2021.07-4) unstable; urgency=medium . * Re-add gcc-arm-none-eabi-source package. (Closes: #999817) Checksums-Sha1: 885e256327b373e8d608a920ca855ec0abd9839b 2532 gcc-arm-none-eabi_10.3-2021.07-4.dsc f00d427484b2e1456f3d6fb631fba643e1c0ac0d 20904 gcc-arm-none-eabi_10.3-2021.07-4.debian.tar.xz b8061cef9d5cc5452630002abeb43fdc77d395f2 8481 gcc-arm-none-eabi_10.3-2021.07-4_amd64.buildinfo Checksums-Sha256: 146883d8d6f65d240b442dcb6c8cef277d54be94eb9d6ff592a244609b88e238 2532 gcc-arm-none-eabi_10.3-2021.07-4.dsc f6b6432140d9e8c4030a333e2978f1bb7e23be71485a7b131e46e628596617fb 20904 gcc-arm-none-eabi_10.3-2021.07-4.debian.tar.xz 8e51d56e3ae88485357a1744f9536df6e560076af4b43f10f997949726d06c20 8481 gcc-arm-none-eabi_10.3-2021.07-4_amd64.buildinfo Files: 6cc20aaff6099907e188dc1cb9a77bc7 2532 devel optional gcc-arm-none-eabi_10.3-2021.07-4.dsc 018e5700b1e09139679a85cffd7c707e 20904 devel optional gcc-arm-none-eabi_10.3-2021.07-4.debian.tar.xz 942fa56f86358706a8d056d009ab6b82 8481 devel optional gcc-arm-none-eabi_10.3-2021.07-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmGVPU0ACgkQ2yIaaQAA ABEggQ//U3dLjg2jq3iBQeHQluYjIGnbzPSIsLHH1hUIpbNSRFhQryVB4WFWXdLE 9oCvU/96sITcsZRuFaTfu1uiprioxKeUQs2fo33io0/UYWxc0NhyA9j02viJy5MZ o4gSuG4o0axz4hf6SMMA+6dD4xD3ew4KOac7VPP5ugox9pQuBSFc0ZqlwsoB5dps y4Cucfg1bx2Myq1YibI7XORwg5YSCq+Aa0/nH6pIDPbamdKxniKDz8fo/80LxMIm be89h4Pkdd6gnj3zBjLmafwedEa7kBE5HzyO+NwPMFw/pyw8bgGQrBddOef23M7J rqFepdHP+/PoPHB03oFqgsifKI3fewxTetZ2m8o5FTSal1ezlF4qN/OPKZ7vVaHk rCVSj7+Anq4WJ79xt9ml311aAF0HRVVYxgEWeds/hPzfucA2u17pMZnNS/oF/uT0 uzOWTXG6+0gNDeDj1OoAh8e60ocMuhhQuyXfg26bxNazkEXgQCKLpOiiXiFSRfVB +g7I/51bjtwgLBxPguPrgSAUjwrMtvcIj3Ap+YJiuoyADFdC6XsJlT+GmhNRyq3z XZsKK6m2HlNqnqnyedRjvg32ji/jLeti+rRamrVvc62xDGxyBDvz5OE9MHhO0lfN n5wIvoYbOhY7egh/gkqT2kqIlwiBHabfcc9DX+GmQW4aYE7tzTE= =Ky2U -END PGP SIGNATURE End Message ---
Bug#908017: network-manager-iodine: diff for NMU version 1.2.0-3.1
Control: tags 908017 + pending X-Debbugs-CC: a...@sigxcpu.org a...@debian.org Dear maintainer, I've prepared an NMU for network-manager-iodine (versioned as 1.2.0-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. I believe the correct patch should be https://gitlab.gnome.org/GNOME/network-manager-iodine/-/merge_requests/1 . Please also consider merging it in upstream development repo. Regards. diff -Nru network-manager-iodine-1.2.0/debian/changelog network-manager- iodine-1.2.0/debian/changelog --- network-manager-iodine-1.2.0/debian/changelog 2018-01-22 09:57:01.0 -0500 +++ network-manager-iodine-1.2.0/debian/changelog 2021-11-17 12:37:25.0 -0500 @@ -1,3 +1,18 @@ +network-manager-iodine (1.2.0-3.1) unstable; urgency=high + + * Non-maintainer upload. + * debian/control: Set Vcs-* fields to use git packaging repo under +Salsa Debian Group. They previously point to upstream development +repo that do not contain any packaging information. + * Apply patch from Ubuntu: (Closes: #908017) + + [ Logan Rosen ] + * d/rules: Set --enable-more-warnings to "yes" so that it doesn't default to +"error," which turns every warning into an error and causes an FTBFS due +to deprecated declarations. + + -- Boyuan Yang Wed, 17 Nov 2021 12:37:25 -0500 + network-manager-iodine (1.2.0-3) unstable; urgency=medium * Drop build-dep on libnm-gtk-dev (Closes: #862836) diff -Nru network-manager-iodine-1.2.0/debian/control network-manager-iodine- 1.2.0/debian/control --- network-manager-iodine-1.2.0/debian/control 2018-01-22 09:55:43.0 -0500 +++ network-manager-iodine-1.2.0/debian/control 2021-11-17 12:33:01.0 -0500 @@ -15,8 +15,8 @@ automake, libtool Standards-Version: 4.1.3 -Vcs-Git: https://git.gnome.org/browse/network-manager-iodine -Vcs-Browser: https://git.gnome.org/browse/network-manager-iodine +Vcs-Git: https://salsa.debian.org/debian/network-manager-iodine.git +Vcs-Browser: https://salsa.debian.org/debian/network-manager-iodine Homepage: https://honk.sigxcpu.org/piki/projects/network-manager-iodine Package: network-manager-iodine diff -Nru network-manager-iodine-1.2.0/debian/rules network-manager-iodine- 1.2.0/debian/rules --- network-manager-iodine-1.2.0/debian/rules 2018-01-22 03:55:32.0 -0500 +++ network-manager-iodine-1.2.0/debian/rules 2021-11-17 12:36:06.0 -0500 @@ -6,12 +6,14 @@ %: dh $@ +# See https://bugs.debian.org/908017 for --enable-more-warnings override_dh_auto_configure: [ -f ./configure ] || ./autogen.sh dh_auto_configure -- \ --libexecdir=/usr/lib/NetworkManager \ --disable-static \ - --without-libnm-glib + --without-libnm-glib \ + --enable-more-warnings=yes override_dh_makeshlibs: dh_makeshlibs -X/usr/lib/$(DEB_HOST_MULTIARCH)/NetworkManager/ signature.asc Description: This is a digitally signed message part
Processed: network-manager-iodine: diff for NMU version 1.2.0-3.1
Processing control commands: > tags 908017 + pending Bug #908017 [src:network-manager-iodine] network-manager-iodine FTBFS with glib 2.58 Added tag(s) pending. -- 908017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 999751 ftbfs Bug #999751 [src:di-netboot-assistant] di-netboot-assistant: please drop shellcheck autopkgtest Added tag(s) ftbfs. > -- Stopping processing here. Please contact me if you need assistance. -- 999751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 986487
Processing commands for cont...@bugs.debian.org: > tags 986487 + pending Bug #986487 [caftools] caftools: FTBFS with glibc >= 2.32 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 986487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986770: marked as done (shapetools: FTBFS with glibc 2.32)
Your message dated Wed, 17 Nov 2021 17:21:18 +
with message-id
and subject line Bug#986770: fixed in shapetools 1.4pl6-15
has caused the Debian Bug report #986770,
regarding shapetools: FTBFS with glibc 2.32
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.)
--
986770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shapetools
Version: 1.4pl6-14
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
Hi,
shapetools currently FTBFS against glibc 2.32, which is used in the
development release of Ubuntu (and should be in Debian soon).
This is because it uses sys_errlist instead of strerror(), which is also
supported in earlier versions of glibc.
In Ubuntu, the attached patch was applied to achieve the following:
* Use strerror() instead of sys_errlist to fix FTBFS with glibc 2.32.
Thanks for considering the patch.
Logan
diff -u shapetools-1.4pl6/src/atfs/aferror.c
shapetools-1.4pl6/src/atfs/aferror.c
--- shapetools-1.4pl6/src/atfs/aferror.c
+++ shapetools-1.4pl6/src/atfs/aferror.c
@@ -272,7 +272,7 @@
switch (af_errno) {
case AF_ESYSERR:
-sprintf (errMsg, "%s: %s", string, sys_errlist[errno]);
+sprintf (errMsg, "%s: %s", string, strerror(errno));
break;
case AF_EMISC:
sprintf (errMsg, "%s: %s", string, diagstr);
diff -u shapetools-1.4pl6/src/atfs/atfsrepair.c
shapetools-1.4pl6/src/atfs/atfsrepair.c
--- shapetools-1.4pl6/src/atfs/atfsrepair.c
+++ shapetools-1.4pl6/src/atfs/atfsrepair.c
@@ -495,7 +495,7 @@
lockInfo.l_pid = (pid_t)0;
if (fcntl (fileno(inFile), F_GETLK, ) == -1) {
fprintf (stderr, "-> Error:\tCannot get lock info for %s -- fcntl
failed (%s)!\n",
- arFilename, sys_errlist[errno]);
+ arFilename, strerror(errno));
fclose (inFile);
cleanup ();
}
@@ -525,7 +525,7 @@
lockInfo.l_pid = (pid_t)0;
if (fcntl (fileno(inFile), F_SETLK, ) == -1) {
fprintf (stderr, "-> Error:\tCannot unlock %s -- fcntl failed (%s)!\n",
- arFilename, sys_errlist[errno]);
+ arFilename, strerror(errno));
fclose (inFile);
cleanup ();
}
@@ -1437,7 +1437,7 @@
if (modeConfirmed) {
if (chmod (attrArPath, atfsIbuf.st_mode) == -1)
fprintf (stderr, "Error:\tCannot change protection of '%s':
%s\n",
-attrArPath, sys_errlist[errno]);
+attrArPath, strerror(errno));
}
}
if (atfsIbuf.st_gid != subIbuf.st_gid) {
@@ -1454,7 +1454,7 @@
if (chown (attrArPath, atfsIbuf.st_uid, atfsIbuf.st_gid) == -1)
if (chown (attrArPath, geteuid(), atfsIbuf.st_gid) == -1) {
fprintf (stderr, "Error:\tCannot change Owner/Group of '%s':
%s\n",
- attrArPath, sys_errlist[errno]);
+ attrArPath, strerror(errno));
}
}
}
diff -u shapetools-1.4pl6/src/atfs/cacheadm.c
shapetools-1.4pl6/src/atfs/cacheadm.c
--- shapetools-1.4pl6/src/atfs/cacheadm.c
+++ shapetools-1.4pl6/src/atfs/cacheadm.c
@@ -132,7 +132,7 @@
retCode += setCacheSize (argv[i+optind]);
}
else {
- fprintf (stderr, " Error -- %s: %s\n", argv[i+optind],
sys_errlist[errno]);
+ fprintf (stderr, " Error -- %s: %s\n", argv[i+optind],
strerror(errno));
}
}
}
diff -u shapetools-1.4pl6/src/shape/parser.h
shapetools-1.4pl6/src/shape/parser.h
--- shapetools-1.4pl6/src/shape/parser.h
+++ shapetools-1.4pl6/src/shape/parser.h
@@ -39,5 +39,5 @@
extern char *sys_errlist[] ; /* ... these strings by myself */
#endif
-#define fatal_perror(string)fatal(sys_errlist[errno], string)
+#define fatal_perror(string)fatal(strerror(errno), string)
diff -u shapetools-1.4pl6/src/vc/rcs2atfs/utils.c
shapetools-1.4pl6/src/vc/rcs2atfs/utils.c
--- shapetools-1.4pl6/src/vc/rcs2atfs/utils.c
+++ shapetools-1.4pl6/src/vc/rcs2atfs/utils.c
@@ -387,16 +387,16 @@
switch (errno) {
case EACCES:
if (! recursive) {
- error(sys_errlist[errno], fname) ;
+ error(strerror(errno), fname) ;
}
return f_error ;
case EFAULT:
- fatal(sys_errlist[errno], MUSTNOT) ;
+ fatal(strerror(errno), MUSTNOT) ;
case ENOENT:
/* can be RCS working file without busy version */
return f_plain ;
default:
-
Bug#998261: marked as done (jsbundle-web-interfaces: autopkgtest regression: node: command not found)
Your message dated Wed, 17 Nov 2021 16:03:55 + with message-id and subject line Bug#998261: fixed in jsbundle-web-interfaces 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3 has caused the Debian Bug report #998261, regarding jsbundle-web-interfaces: autopkgtest regression: node: command not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jsbundle-web-interfaces Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of jsbundle-web-interfaces the autopkgtest of jsbundle-web-interfaces fails in testing when that autopkgtest is run with the binary packages of jsbundle-web-interfaces from unstable. It passes when run with only packages from testing. In tabular form: passfail jsbundle-web-interfaces from testing 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems that when you dropped the (Build-)Depends, you forgot it was needed for the test. 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=jsbundle-web-interfaces https://ci.debian.net/data/autopkgtest/testing/amd64/j/jsbundle-web-interfaces/16336344/log.gz bash: line 1: node: command not found autopkgtest [15:09:56]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: jsbundle-web-interfaces Source-Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of jsbundle-web-interfaces, 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. Jonas Smedegaard (supplier of updated jsbundle-web-interfaces 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, 17 Nov 2021 17:41:55 +0100 Source: jsbundle-web-interfaces Architecture: source Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 998261 Changes: jsbundle-web-interfaces (1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3) unstable; urgency=medium . * fix have autopkgtests depend on nodejs, and stop build-depend on nodejs: really closes: bug#998261; tighten autopkgtests to do require test in root dir Checksums-Sha1: 5cd496418e71bbd25fdfeac95d4722ceb1f50032 3760 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.dsc 76604b9dba985ee5bc956b88310686cf93eb4845 17084 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.debian.tar.xz 4e8f7e105bab83f21c4a93732206d5cfe42f1821 13324 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3_amd64.buildinfo Checksums-Sha256: 1dcf03f9356aae95a020213005696ccdd54a3dea58e8d3ee3fc597b337b2f08d 3760 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.dsc c63d0f04fc0f65aa66b6390894122d7c384882a51db4e435e38bea82f859a525 17084 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.debian.tar.xz 91f4b2e34f2be38df4e5d4b510bee7a0ea224ba7272a2a422bc0255c5e24a65a 13324 jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3_amd64.buildinfo Files: 9adf00ad01580902de1b3afdcf50c016 3760 javascript optional jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.dsc c049b03b8793f22319639d568356777a 17084 javascript optional jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-3.debian.tar.xz ef38b7592f311eba6cd6cdeee610c6b8 13324 javascript optional
Processed: ripperx: diff for NMU version 2.8.0-2.1
Processing control commands: > tags 978893 + patch Bug #978893 [src:ripperx] ripperx: ftbfs with autoconf 2.70 Added tag(s) patch. > tags 978893 + pending Bug #978893 [src:ripperx] ripperx: ftbfs with autoconf 2.70 Added tag(s) pending. -- 978893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999353: marked as done (gkrelluim: broken rebuild)
Your message dated Wed, 17 Nov 2021 14:49:06 + with message-id and subject line Bug#999353: fixed in gkrelluim 0.3.1-8 has caused the Debian Bug report #999353, regarding gkrelluim: broken rebuild 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.) -- 999353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gkrelluim Version: 0.3.1-7+b2 Severity: normal The latest NMU made gkrelluim completely unusbale. It seems to be missing all of its dependencies and doesn't load at all. The "Install Log" tab in the gkrellm's configuration window says: Error: /usr/lib/gkrellm2/plugins/gkrelluim.so: undefined symbol: uim_quit The previous build (0.3.1-7+b1) works without any problems. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (700, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gkrelluim depends on: ii gkrellm 2.3.11-2 ii libc62.32-4 gkrelluim recommends no packages. gkrelluim suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gkrelluim Source-Version: 0.3.1-8 Done: HIGUCHI Daisuke (VDR dai) We believe that the bug you reported is fixed in the latest version of gkrelluim, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated gkrelluim 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, 17 Nov 2021 20:49:37 +0900 Source: gkrelluim Architecture: source Version: 0.3.1-8 Distribution: unstable Urgency: medium Maintainer: HIGUCHI Daisuke (VDR dai) Changed-By: HIGUCHI Daisuke (VDR dai) Closes: 999353 Changes: gkrelluim (0.3.1-8) unstable; urgency=medium . * Bump debhelper compatibility level to 13. * Update Standards-Version to 4.6.0.1. * set Rules-Requires-Root: as no. * Update d/watch Version to 4. * set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Add salsa-ci.yml * d/p/link_order.patch: fix link order (Closes: #999353). - Thanks to Andreas Beckmann . Checksums-Sha1: 5a1932cd2eab46329219191d37239d0424c8a48a 1913 gkrelluim_0.3.1-8.dsc 37f4d64081a9d8cc8e3d1db76cc935af06f6beb3 9892 gkrelluim_0.3.1-8.debian.tar.xz Checksums-Sha256: 6d29a35cdf153c817f50dfad0bee49814918766d6240e3052cf967682d8f1ac2 1913 gkrelluim_0.3.1-8.dsc 7133fb87d1c503546299600ccd5341aa1dcdf37996039562c590d9ace21eeab2 9892 gkrelluim_0.3.1-8.debian.tar.xz Files: 8d46c2f32ceefde80078c036fae692e4 1913 x11 optional gkrelluim_0.3.1-8.dsc 64d86d914ed1d9a428bdf0ce0a543145 9892 x11 optional gkrelluim_0.3.1-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmGVEs8ACgkQeDlhndQ5 Zo4RFxAAphn9itP7AzqWInnmPokuO11ouOtifSJ49EwStnYmlQxiJA4yz/qgl9he rx/Xm0oTgYf0SfEc/AEM/TPgyhURBY6D3Ix90yL/rlR/EgwFESOtVuzEoT1TkBPv x7LFW1TBIBwSNO6JItIEM+hRflrQz5LQih8BXnhsZgCtYUe/gLGxQ2Sx/CYyYKww 7DHkjKRAbjmok07sO/CcNV2RR8U24hhLb1wZI1cPJQ1MGZM3ObrDjCGghxzRXkfD EMN4ACTHy0vY+MHXQ5L2lNvirop315CJfepFNXKLp8DpDSJTkthgMOE881K1wOEc IHH2UoZO1pLj/VOf6dMa9/DHFtG4Rep4FG+UzCTKzrXHo+nnxNEKqPONOOqbhhSZ tuArkOxpPsyXdX5JMCC2QZoPZxVtMLYgC67rDVTsi/suGneaCWCBoUGm7LgJdKEs EmhkCrevkNyPQG3/Y12m2lanmEy8qBJbWE334uG9C9dufu3Y5SLFI0mER2xS3xnu V+kZEZl+2lKUSaN+g/Oaf6iHMKOQVAgAb57x3CFwVZKaQQLANZDCBF/HIjhv7gwm 2Jhef8dX2DoCBHzmW6DLxUv2wm80Y57CLWLKzLtQUFLAAwwBKEDxD1Ij+lB0AfxL eDNcwzay10QPnABo8jZ+L/z92lNUYI6dRFbyG81ywh2+YNRZbDk= =VFcC -END PGP SIGNATURE End Message ---
Processed: block 996125 with 996147
Processing commands for cont...@bugs.debian.org: > block 996125 with 996147 Bug #996125 [src:ruby-arbre] ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996125 was blocked by: 996377 996125 was not blocking any bugs. Added blocking bug(s) of 996125: 996147 > thanks Stopping processing here. Please contact me if you need assistance. -- 996125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 992419 to src:u-boot, tagging 996353, tagging 998772, tagging 998541, tagging 999429 ...
Processing commands for cont...@bugs.debian.org:
> reassign 992419 src:u-boot 2021.07+dfsg-1
Bug #992419 [u-boot-sifive] U-Boot using wrong memory type for device-trees.
Warning: Unknown package 'u-boot-sifive'
Bug reassigned from package 'u-boot-sifive' to 'src:u-boot'.
No longer marked as found in versions 2021.07+dfsg-1.
Ignoring request to alter fixed versions of bug #992419 to the same values
previously set
Bug #992419 [src:u-boot] U-Boot using wrong memory type for device-trees.
Marked as found in versions u-boot/2021.07+dfsg-1.
> tags 996353 + experimental
Bug #996353 [src:ruby-rack] ruby-rack: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed.
Added tag(s) experimental.
> tags 998772 + experimental
Bug #998772 {Done: Paul Gevers }
[src:ruby-omniauth-openid-connect] src:ruby-omniauth-openid-connect: fails to
migrate to testing for too long: unresolved RC bug
Added tag(s) experimental.
> tags 998541 + experimental
Bug #998541 {Done: Sébastien Villemot } [src:dynare]
dynare: FTBFS: TypeError: 'DynareLexer' object is not callable
Added tag(s) experimental.
> tags 999429 + experimental
Bug #999429 {Done: Paul Gevers } [src:guix] src:guix: fails
to migrate to testing for too long: FTBFS on i386
Added tag(s) experimental.
> tags 998703 + experimental
Bug #998703 {Done: Paul Gevers } [src:gnuastro]
src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el
Added tag(s) experimental.
> tags 998293 + experimental
Bug #998293 {Done: Paul Gevers } [src:phosh] src:phosh:
fails to migrate to testing for too long
Added tag(s) experimental.
> tags 998033 + experimental
Bug #998033 {Done: Paul Gevers } [src:emscripten]
src:emscripten: fails to migrate to testing for too long: depends on
llvm-toolchain-13 which isn't ready for testing yet
Added tag(s) experimental.
> tags 996451 + experimental
Bug #996451 {Done: Paul Gevers } [src:gsl] src:gsl: fails to
migrate to testing for too long: unresolved RC bug (found by autopkgtest
breakage)
Added tag(s) experimental.
> tags 995410 + sid bookworm
Bug #995410 [src:breezy] breezy: FTBFS:
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
992419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992419
995410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995410
996353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996353
996451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996451
998033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998033
998293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998293
998541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998541
998703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998703
998772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998772
999429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: block 996125 with 996377
Processing commands for cont...@bugs.debian.org: > block 996125 with 996377 Bug #996125 [src:ruby-arbre] ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996125 was not blocked by any bugs. 996125 was not blocking any bugs. Added blocking bug(s) of 996125: 996377 > thanks Stopping processing here. Please contact me if you need assistance. -- 996125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999818: marked as done (node-regenerate-unicode-properties build-depends on removed package.)
Your message dated Wed, 17 Nov 2021 13:03:59 + with message-id and subject line Bug#999818: fixed in node-regenerate-unicode-properties 9.0.0+ds-1 has caused the Debian Bug report #999818, regarding node-regenerate-unicode-properties build-depends on removed package. 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.) -- 999818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-regenerate-unicode-properties Version: 8.2.0+ds-2 Severity: serious node-regenerate-unicode-properties build-depends on node-unicode-13.0.0 which is no longer built by the node-unicode-data source package. It is still present in unstable as a cruft package but is completely gone from testing. The package appears to have been replaced by node-unicode-14.0.0 --- End Message --- --- Begin Message --- Source: node-regenerate-unicode-properties Source-Version: 9.0.0+ds-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-regenerate-unicode-properties, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-regenerate-unicode-properties 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, 17 Nov 2021 13:52:08 +0100 Source: node-regenerate-unicode-properties Architecture: source Version: 9.0.0+ds-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 999818 Changes: node-regenerate-unicode-properties (9.0.0+ds-1) unstable; urgency=medium . * Team upload * Add debian/gbp.conf * Fix filenamemangle * Use dh-sequence-nodejs auto install * New upstream version 9.0.0+ds (Closes: #999818) * Require node-unicode-14.0.0 * Enable upstream test using tape instead of ava Checksums-Sha1: bc1ad8d6f1f799d6b3dd4faeeac2b9540ec088be 2436 node-regenerate-unicode-properties_9.0.0+ds-1.dsc 64aff35c50474f01293e6f080ba80d0cf4606dbf 4260 node-regenerate-unicode-properties_9.0.0+ds.orig.tar.xz 3d48abf15acea4f5bb0bd968e4a16621a5e65994 3492 node-regenerate-unicode-properties_9.0.0+ds-1.debian.tar.xz Checksums-Sha256: 5cc8c9a4c13105b8f8c2141125ce201d1f7d50276a77638ef9f5244fe57eb5a3 2436 node-regenerate-unicode-properties_9.0.0+ds-1.dsc c6bdafaa0d9a20170c7a1d83bb9c63765a55268ac3f9a0accbb8a811c0784320 4260 node-regenerate-unicode-properties_9.0.0+ds.orig.tar.xz 244d3574ba5581dfd833f60e668bfce41ee76552d5befc177b934d01e37025b7 3492 node-regenerate-unicode-properties_9.0.0+ds-1.debian.tar.xz Files: a35b7f0dcbb8a164ff6c05383dd4e673 2436 javascript optional node-regenerate-unicode-properties_9.0.0+ds-1.dsc 2cec99a8195a2a0ea7881c42abd23915 4260 javascript optional node-regenerate-unicode-properties_9.0.0+ds.orig.tar.xz 939488b32f7577e3d74d2f078f6ffa38 3492 javascript optional node-regenerate-unicode-properties_9.0.0+ds-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGU+z8ACgkQ9tdMp8mZ 7ulvgw//UKxuZkwuJTM3zwA24LATN9QMi1ZfI8pTSedmheTtDhDRoC4Oa7oHEGMF +DX/JqZk9wETwai+jm+9EyeD3xEcCdpUp3hkk6e4ypAt7cbguGKOfW1PK7E241jh nWXTrOimW8g785tSJsQzEjZl4uHAikldMOtEC91IT4POpjkac9xNoo8+k112g4mZ mvYEubBMIVBu8tZY50JSDGjCSnZdpJKAohtG5Z8JRzI6CK9fJMc8pLXRNukakTR+ afj1b1EyeqCtzjUd6FlYGaDU/N4WqwCHUYVFdCzadI3RkNeAh9BeYiMfycZMUnrE hCdVpN7XdAlqbV21NCh6z6mQV/eWy+EJcPj05q7mPpDoN76wAGNLLrMQOyBx+RtC kEegVyur13S4aNRs6PTFsvQpY4HzHVdY/yFHGzAtNE+0LBQ/oIO16OREQhLnwVbz 3swbX/YYxkYGwPiXCKS/9IPSoZ39C/VKxwTCU7hfl+/Q4ymbO/nnTw9LtLdu4G46 5IFiErJVg+Bm6OCh8It41c/ujFRodIbVGgPMaXjr2OIpCDhq3fzmS3FZHKnoaocx opgzR/RydH4obrvAIxeWG8pWS0y7DULQsEQ+Qfp7EAmB0w0qMKRc0Dx26a1sJTc7 IccSTqyh3Y+IQNN/Ycny4hVLPmH/52ldCB2c4UGMsfQsHfq3kVg= =zyVz -END PGP SIGNATURE End Message ---
Processed: Bug#999818 marked as pending in node-regenerate-unicode-properties
Processing control commands: > tag -1 pending Bug #999818 [node-regenerate-unicode-properties] node-regenerate-unicode-properties build-depends on removed package. Ignoring request to alter tags of bug #999818 to the same tags previously set -- 999818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999818: marked as pending in node-regenerate-unicode-properties
Control: tag -1 pending Hello, Bug #999818 in node-regenerate-unicode-properties 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-regenerate-unicode-properties/-/commit/51a4c3fecf8bc7f3d7d94145811dab1e2f84e078 New upstream version 9.0.0+ds (Closes: #999818) (this message was generated automatically) -- Greetings https://bugs.debian.org/999818
Bug#999818: marked as pending in node-regenerate-unicode-properties
Control: tag -1 pending Hello, Bug #999818 in node-regenerate-unicode-properties 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-regenerate-unicode-properties/-/commit/51a4c3fecf8bc7f3d7d94145811dab1e2f84e078 New upstream version 9.0.0+ds (Closes: #999818) (this message was generated automatically) -- Greetings https://bugs.debian.org/999818
Processed: Bug#999818 marked as pending in node-regenerate-unicode-properties
Processing control commands: > tag -1 pending Bug #999818 [node-regenerate-unicode-properties] node-regenerate-unicode-properties build-depends on removed package. Added tag(s) pending. -- 999818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997153: marked as done (asyncpg: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Wed, 17 Nov 2021 12:33:32 +
with message-id
and subject line Bug#997153: fixed in asyncpg 0.25.0-1
has caused the Debian Bug report #997153,
regarding asyncpg: 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.)
--
997153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asyncpg
Version: 0.24.0-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):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build build_ext --cython-always
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/types.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/introspection.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/__init__.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/connresource.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/transaction.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/connection.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/cursor.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/compat.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/_version.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/connect_utils.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/prepared_stmt.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/pool.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/serverversion.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/cluster.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> copying asyncpg/utils.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg
> running egg_info
> writing asyncpg.egg-info/PKG-INFO
> writing dependency_links to asyncpg.egg-info/dependency_links.txt
> writing requirements to asyncpg.egg-info/requires.txt
> writing top-level names to asyncpg.egg-info/top_level.txt
> reading manifest file 'asyncpg.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.py' under directory 'examples'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'asyncpg.egg-info/SOURCES.txt'
> creating
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/_testbase
> copying asyncpg/_testbase/__init__.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/_testbase
> copying asyncpg/_testbase/fuzzer.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/_testbase
> creating
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/exceptions
> copying asyncpg/exceptions/__init__.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/exceptions
> copying asyncpg/exceptions/_base.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/exceptions
> creating /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/__init__.pxd ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/__init__.py ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/buffer.pxd ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/buffer.pyx ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/consts.pxi ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/cpythonx.pxd ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/debug.h ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/debug.pxd ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/frb.pxd ->
> /<>/.pybuild/cpython3_3.9_asyncpg/build/asyncpg/pgproto
> copying asyncpg/pgproto/frb.pyx ->
>
Processed: Re: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so
Processing control commands: > severity -1 normal Bug #998224 [hplip] hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so Severity set to 'normal' from 'grave' -- 998224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998224: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so
Control: severity -1 normal On Thu, 11 Nov 2021 09:53:08 +1100 Troy Rollo wrote: 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. As this is not happening in the "normal" way Debian packages get built on the buildd network (in minimal chroots, using only packages from the target distribution), I'm downgrading the severity. Andreas
Processed: Re: Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]
Processing control commands: > severity -1 important Bug #999823 [src:liboqs] liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=] Severity set to 'important' from 'serious' -- 999823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]
control: severity -1 important On 2021-11-17 10:52, Andrius Merkys wrote: > Hi Aurelien, > > Thanks for the report. > > On 2021-11-17 09:09, Aurelien Jarno wrote: > > Source: liboqs > > Version: 0.7.0.15.g9be13d21+dfsg-1 > > Severity: serious > > Tags: ftbfs > > Justification: fails to build from source (but built successfully in the > > past) > > Not sure if "(but built successfully in the past)" is appropriate here, as > to my knowledge this is the first build for liboqs on arm64. > Oops sorry about that. Then the bug is definitely not serious, downgrading the severity. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: tagging 999817, tagging 998345
Processing commands for cont...@bugs.debian.org:
> tags 999817 + bookworm sid
Bug #999817 [libstdc++-arm-none-eabi] libstdc++-arm-none-eabi build-depends on
removed package.
Added tag(s) sid and bookworm.
> tags 998345 + bookworm sid
Bug #998345 {Done: Jonas Smedegaard }
[librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev:
uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998345
999817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: prototypejs: FTBFS
Processing control commands: > tag -1 moreinfo Bug #993301 [src:prototypejs] prototypejs: FTBFS Added tag(s) moreinfo. -- 993301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993301: prototypejs: FTBFS
Control: tag -1 moreinfo On Mon, 30 Aug 2021 12:23:22 + "=?utf-8?q?Bastien_Roucari=C3=A8s?=" wrote: Source: prototypejs Severity: serious Justification: 4 Dear Maintainer, The source is https://github.com/prototypejs/prototype/tree/master and need rake for building... So FTBFS I can rebuild prototypejs/1.7.1-3.1 in sid and bullseye without problems. What errors do you encounter? There is a new upstream release 1.7.3 (from 2015) available on github. Does that version fail? And how is this related to rake? Andreas
Bug#999353: gkrelluim: broken rebuild
Control: tag -1 bullseye bookworm sid patch
On Wed, 10 Nov 2021 13:03:16 +0100 mwgam...@gmail.com wrote:
Package: gkrelluim
Version: 0.3.1-7+b2
The latest NMU made gkrelluim completely unusbale. It seems to be
missing all of its dependencies and doesn't load at all.
debdiff says:
Control files: lines which differ (wdiff format)
Depends: gkrellm, [-libatk1.0-0 (>= 1.12.4),-] libc6 (>= [-2.4), libcairo2 (>= 1.2.4), libfontconfig1 (>=
2.12.6), libfreetype6 (>= 2.2.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.16.0), libgtk2.0-0
(>= 2.8.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0),
libuim-scm0 (>= 1:1.5.7), libuim8 (>= 1:1.5.7)-] {+2.4)+}
Version: [-0.3.1-7+b1-] {+0.3.1-7+b2+}
Yes, lots of dependencies are gone.
Comparing the logs from rebuilding in buster and
bullseye brought this to my attention:
dh_shlibdeps
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libpangocairo-1.0.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libgio-2.0.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libpthread.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libatk-1.0.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libcairo.so.2 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libpangoft2-1.0.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libfontconfig.so.1 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libpango-1.0.so.0 (it uses none of the library's symbols)
-dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gkrelluim/usr/lib/gkrellm2/plugins/gkrelluim.so was not linked against
libfreetype.so.6 (it uses none of the library's symbols)
The bullseye toolchain defaults to linking with --as-needed to drop
unneeded library dependencies. But obviously gkrelluim needs them ...
Oh, link order is bullshit, the object files are coming after the libs ...
... because libraries are part of LDFLAGS ...
Please see the attached patch for a fix.
That should get the needed dependencies back ...
Andreas
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -4,5 +4,6 @@ plugindir = $(libdir)/gkrellm2/plugins/
gkrelluim_so_SOURCES = gkrelluim.c uim-helper.c gkrelluim.h
+gkrelluim_so_LDADD = $(GKRELLM_LIBS) $(UIM_LIBS)
AM_CFLAGS = -fPIC @GKRELLM_CFLAGS@ -DUIM_PIXMAPSDIR="\"$(datadir)/uim/pixmaps/\""
-AM_LDFLAGS = -shared @GKRELLM_LIBS@ @UIM_LIBS@
+AM_LDFLAGS = -shared
Processed: Re: gkrelluim: broken rebuild
Processing control commands: > tag -1 bullseye bookworm sid patch Bug #999353 [gkrelluim] gkrelluim: broken rebuild Added tag(s) bookworm, patch, bullseye, and sid. -- 999353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995879: marked as done (uninstallable due to dependency on ansible-core)
Your message dated Wed, 17 Nov 2021 11:00:09 + with message-id and subject line Bug#995879: fixed in ansible-core 2.11.6-1 has caused the Debian Bug report #995879, regarding uninstallable due to dependency on ansible-core 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.) -- 995879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ansible Version: 4.6.0-1 Severity: serious Tags: experimental Hi, ansible in experimental is currently uninstallable because of the dependency on ansible-core which is unavailable/not yet uploaded in Debian as it seems. Regards, Daniel --- End Message --- --- Begin Message --- Source: ansible-core Source-Version: 2.11.6-1 Done: Lee Garrett We believe that the bug you reported is fixed in the latest version of ansible-core, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lee Garrett (supplier of updated ansible-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 07 Nov 2021 00:40:26 +0100 Source: ansible-core Binary: ansible-core Architecture: source all Version: 2.11.6-1 Distribution: experimental Urgency: medium Maintainer: Lee Garrett Changed-By: Lee Garrett Description: ansible-core - Configuration management, deployment, and task execution system Closes: 977327 992107 995879 Changes: ansible-core (2.11.6-1) experimental; urgency=medium . * New upstream release (Closes: #977327) * Rename source/binary package to ansible-core * Upload to experimental (Closes: #995879) * Fix issues with 0005_use_py3.patch (Closes: #992107) * Fix usage of Cryptodome * Fix all unit tests * Bump Standards-Version to 4.6.0.1 (no changes needed) * Fix several lintian warnings Checksums-Sha1: aeabc486a6d8e633acf94be787bb9aeb30a648af 1631 ansible-core_2.11.6-1.dsc 8a27858b0996fd8c60afe85686a618b925548369 6999232 ansible-core_2.11.6.orig.tar.gz c8e37a07f2c7b615eba61ede24127bf87cbe86ad 20312 ansible-core_2.11.6-1.debian.tar.xz f2bd0e764b7f42c9d739396334a4bbc1ca7e0c71 1099240 ansible-core_2.11.6-1_all.deb 9e4a015a4e525b7bda601457f8fe636aec12c0c2 6110 ansible-core_2.11.6-1_amd64.buildinfo Checksums-Sha256: 250d9b6770b4e6eeaa4e1ab2ea88b9d6047e0c314222b8641df3c8c1c533e70b 1631 ansible-core_2.11.6-1.dsc 93d50283c7c5b476debf83dc089b3f679b939a8b9a7b5d628d28daafbb3d303a 6999232 ansible-core_2.11.6.orig.tar.gz ff1b5645eb981506a5b7ce1a8a4ee8d0b8e56d60a9cd1d21270c68ba31488729 20312 ansible-core_2.11.6-1.debian.tar.xz 7a3b955792c49b5dd4b3c53d7111421c3276e3f74c71de9c7b7317bc3d96f62d 1099240 ansible-core_2.11.6-1_all.deb 14d8c8e66724882235dc0d110eb3dc22112a82eaacbeb43083ed8857cf54c144 6110 ansible-core_2.11.6-1_amd64.buildinfo Files: 5e848397f9d7a4d4dae582bb65b107b3 1631 admin optional ansible-core_2.11.6-1.dsc 59ffdc26466b8f14c91502f876afd3c8 6999232 admin optional ansible-core_2.11.6.orig.tar.gz be4b5736d4888d277842404f7133160b 20312 admin optional ansible-core_2.11.6-1.debian.tar.xz b2c87b299c28c6acaf6f29c84488fc97 1099240 admin optional ansible-core_2.11.6-1_all.deb f61038fa90dfdc622c4be5f79354d19f 6110 admin optional ansible-core_2.11.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCYY55LwAKCRBitBCJKh26 HTnJAP9/mT3COem1LvThNgZ2D4+6MaspXeZuatD1B6Zk2v0dgQEA3sLYikE6j9S9 UxQ3oaPArjp4E/7qJlefLxKzwgt15wE= =HGga -END PGP SIGNATURE End Message ---
Processed: found 996353 in ruby-rack/2.1.4-3
Processing commands for cont...@bugs.debian.org: > found 996353 ruby-rack/2.1.4-3 Bug #996353 [src:ruby-rack] ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Marked as found in versions ruby-rack/2.1.4-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 996353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998679: Firefox freezes
Hello, I experience freezes on Debian testing Bookworm (with mesa 21.2.5). They happen very often when I open a link in new tab or open a new tab, enter a URL and press Enter. The proposed workaround of setting `gfx.x11-egl.force-disabled` to `true` didn't solve the issue. Michel Le Bihan
Processed (with 1 error): forcibly merging 996377 996125
Processing commands for cont...@bugs.debian.org: > forcemerge 996377 996125 Bug #996377 [ruby-activesupport] ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Unable to merge bugs because: package of #996125 is 'src:ruby-arbre' not 'ruby-activesupport' Failed to forcibly merge 996377: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 996125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996125 996377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996125: reassign to ruby-rspec-rails or rails?
The actual part reporting the error seems to be: > An error occurred while loading ./spec/rails/integration/forms_spec.rb. > Failure/Error: require 'rspec/rails' > > ArgumentError: > wrong number of arguments (given 4, expected 3) > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/rails_spec_helper.rb:7:in `' > # ./spec/rails/integration/forms_spec.rb:1:in `require' > # ./spec/rails/integration/forms_spec.rb:1:in `' which seems to be a duplicate of #996377. So it probably has to be merged with that one. signature.asc Description: signature
Bug#996122: closing 996122
close 996122 4.0.6+ds-1 thanks This bug has been closed by the upload of 4.0.6+ds-1.
Bug#996349: closing 996349
close 996349 4.0.6+ds-1 thanks This bug has been closed by the upload of 4.0.6+ds-1.
Processed: closing 996122
Processing commands for cont...@bugs.debian.org: > close 996122 4.0.6+ds-1 Bug #996122 [src:ruby-public-suffix] ruby-addressable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Ignoring request to alter fixed versions of bug #996122 to the same values previously set Bug #996122 [src:ruby-public-suffix] ruby-addressable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 996349
Processing commands for cont...@bugs.debian.org: > close 996349 4.0.6+ds-1 Bug #996349 [src:ruby-public-suffix] ruby-public-suffix: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Ignoring request to alter fixed versions of bug #996349 to the same values previously set Bug #996349 [src:ruby-public-suffix] ruby-public-suffix: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 996349 in 4.0.6+ds-1, fixed 996122 in 4.0.6+ds-1
Processing commands for cont...@bugs.debian.org: > fixed 996349 4.0.6+ds-1 Bug #996349 [src:ruby-public-suffix] ruby-public-suffix: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Marked as fixed in versions ruby-public-suffix/4.0.6+ds-1. > fixed 996122 4.0.6+ds-1 Bug #996122 [src:ruby-public-suffix] ruby-addressable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Marked as fixed in versions ruby-public-suffix/4.0.6+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 996122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996122 996349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 993247 in 0.15.3-1
Processing commands for cont...@bugs.debian.org: > fixed 993247 0.15.3-1 Bug #993247 [src:gnunet] FTBFS in sid (libunistring) Marked as fixed in versions gnunet/0.15.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 993247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999813: util-linux: Upgrade from buster to bullseye fails because of util-linux
* tomas k [27 02:33]: > Package: util-linux > Version: 2.36.1-8 Hi tomas k, > I was upgrading 'buster' to 'bullseye' using simple instructions here: > https://linuxiac.com/upgrade-debian-10-buster-to-debian-11-bullseye/ I understand your system is now broken, possibly still in the middle of the upgrade. However without further details its impossible for me to trace what happened and/or provide advice or improvements for future upgrades. Please check out the official upgrading docs here: https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html It has some hints on what to do when upgrades go wrong, and also which information to capture (best started before upgrading). Hope you'll get your system fixed. BR, Chris
Bug#996348: marked as done (ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)
Your message dated Wed, 17 Nov 2021 09:48:48 +
with message-id
and subject line Bug#996348: fixed in ruby-process-daemon 1.0.1-3
has caused the Debian Bug report #996348,
regarding ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: cannot load such file -- webrick
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.)
--
996348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-process-daemon
Version: 1.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-process-daemon was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> cannot load such file -- webrick
> # ./spec/process/daemon/daemonize_spec.rb:23:in `'
>
> Finished in 0.6 seconds (files took 0.99452 seconds to load)
> 0 examples, 0 failures, 3 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-process-daemon/ruby-process-daemon_1.0.1-2+rebuild1633391208_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-process-daemon
Source-Version: 1.0.1-3
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-process-daemon, 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.
Cédric Boutillier (supplier of updated ruby-process-daemon
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, 17 Nov 2021 10:06:49 +0100
Source: ruby-process-daemon
Architecture: source
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Cédric Boutillier
Closes: 996348
Changes:
ruby-process-daemon (1.0.1-3) unstable; urgency=medium
.
* Team upload
.
[ Utkarsh Gupta ]
* Add salsa-ci.yml
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update watch file format version to 4.
.
[ Cédric Boutillier ]
* Move debian/watch to gemwatch.debian.net
* Bump Standards-Version to 4.6.0 (no changes needed)
* Use ${ruby:Depends}
* Build-depend on ruby-webrick (Closes: #996348)
* Use gem install layout
* Rules-Requires-Root: set to no
* Bump debhelper compatibility level to 13
* Remove explicit dependency on the ruby interpreter
Checksums-Sha1:
ac43e0e2dff0e132a7f7a7dd4e1e6ecee5b7d541 1585 ruby-process-daemon_1.0.1-3.dsc
e396cc952ec6f18962c7f4556e954368aa54cb7f 11693
ruby-process-daemon_1.0.1.orig.tar.gz
9b9f563b8f1c8217932287dfc2af37874ca7d725 2780
ruby-process-daemon_1.0.1-3.debian.tar.xz
20932fece9241fbb9e5cad544380dff0a1874921 8875
ruby-process-daemon_1.0.1-3_amd64.buildinfo
Checksums-Sha256:
82beb4b9288167ee04ffc6888df248a86e9ce699dd3aa242430e5fe58cae0855 1585
ruby-process-daemon_1.0.1-3.dsc
9d11b700afe7f414df32539aec755f840a6eb899dbbb1de6b038f6d5669d78f4 11693
ruby-process-daemon_1.0.1.orig.tar.gz
0c83bbee5b3fa0b48bdad4047493cf4938c7ad15c440b42bf116fa434154d658 2780
ruby-process-daemon_1.0.1-3.debian.tar.xz
Bug#999619: marked as done (glusterfs breaks tgt autopkgtest: glfs not supported)
Your message dated Wed, 17 Nov 2021 09:35:29 + with message-id and subject line Bug#999619: fixed in glusterfs 10.0-1.2 has caused the Debian Bug report #999619, regarding glusterfs breaks tgt autopkgtest: glfs not supported 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.) -- 999619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glusterfs, tgt Control: found -1 glusterfs/10.0-1 Control: found -1 tgt/1:1.0.80-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 glusterfs the autopkgtest of tgt fails in testing on arm64 and i386 when that autopkgtest is run with the binary packages of glusterfs from unstable. It passes when run with only packages from testing. In tabular form: passfail glusterfs from testing10.0-1 tgtfrom testing1:1.0.80-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of glusterfs 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 [1] https://qa.debian.org/excuses.php?package=glusterfs https://ci.debian.net/data/autopkgtest/testing/arm64/t/tgt/16644122/log.gz ERROR - glfs not supported OK - rbd supported OK - aio supported autopkgtest [14:09:33]: test storage OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: glusterfs Source-Version: 10.0-1.2 Done: Christian Ehrhardt We believe that the bug you reported is fixed in the latest version of glusterfs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Ehrhardt (supplier of updated glusterfs 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, 17 Nov 2021 09:17:06 +0100 Source: glusterfs Architecture: source Version: 10.0-1.2 Distribution: unstable Urgency: medium Maintainer: Patrick Matthäi Changed-By: Christian Ehrhardt Closes: 999619 Launchpad-Bugs-Fixed: 1951126 Changes: glusterfs (10.0-1.2) unstable; urgency=medium . * d/rules: disable tcmalloc also on x86 avoiding issues in tgt and any other software dlopening the glusterfs libraries. LP: #1951126 Closes: #999619 Checksums-Sha1: 0eed4800d9795c2f86f5bcb33e23f8f1913feffc 2721 glusterfs_10.0-1.2.dsc 46631622a3bbcb0fa05cf78d2d0aa1c936a4ae62 21076 glusterfs_10.0-1.2.debian.tar.xz 1c6e3fee6d805c1e53b0c0d121b3070f48260102 9603 glusterfs_10.0-1.2_source.buildinfo Checksums-Sha256: 57af45367c9bb11953270696d144e61e57be5d25544a32e88c7185b83b9d 2721 glusterfs_10.0-1.2.dsc 48707671b64bac3c59e95d608e7b4090ce65491d351f0fae3a6ab4706bd92cf9 21076 glusterfs_10.0-1.2.debian.tar.xz 532214e2a8110c3d0e88cd869e7e3a5dfea2c5012a5e736435c645e90fa036a2 9603 glusterfs_10.0-1.2_source.buildinfo Files: 7479564b76de1d59b33136ee17b60e23 2721 admin optional glusterfs_10.0-1.2.dsc d6106fadcbd028672b7a1caff769cb4e 21076 admin optional glusterfs_10.0-1.2.debian.tar.xz 2a0dfd057c63548882ecd60d423d3c7c 9603 admin optional glusterfs_10.0-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEktYY9mjyL47YC+71uj4pM4KAskIFAmGUu7EACgkQuj4pM4KA skK1mQ//azz67DV5Fb7ZRBK7R0GBes8Dy9QBQJG3x3pcK5bu4EHUK8bclmYegasQ wGX/o2cqt2kQZ2q7i1TbAWblS9pDwFXJW8/vQuT165fJk0Xc2GzxN3RwHp0nsHuC 3Fk3A2llk7Nh6RU0eWgxL189VkaeUkrYE/tTPVL1CchLpGubwa9nXZTu3OWkE/+Y 0byagjQCOQmUEnHz5+KYj75Rdb47bpPk3fB0csMXaXOe68Mw5quxz2nci7xgbVEI qAvxYBD9NZyUQuirS4giDHjk12OCyHPkbmxsOahlMmHj3IaDHt4CQinoSNFO0o9g x+A5HRCpyOfpmRyPCweQQcVBI1F9t9KQPeQQ2IJBKOjpGRX1pGtRmNB+QriwLJ+a
Processed: tagging 996234, severity of 996234 is important
Processing commands for cont...@bugs.debian.org: > tags 996234 + moreinfo Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) moreinfo. > severity 996234 important Bug #996234 [src:ruby-github-markup] ruby-github-markup: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996348: marked as pending in ruby-process-daemon
Control: tag -1 pending Hello, Bug #996348 in ruby-process-daemon 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/ruby-team/ruby-process-daemon/-/commit/3137e1ceaf660f6c4b7ac8f9b444dcc065fb601d Build-depend on ruby-webrick (Closes: #996348) (this message was generated automatically) -- Greetings https://bugs.debian.org/996348
Processed: Bug#996348 marked as pending in ruby-process-daemon
Processing control commands: > tag -1 pending Bug #996348 [src:ruby-process-daemon] ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick Added tag(s) pending. -- 996348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996296: closing 996296
close 996296 thanks The upstream version 1.18.11 contains a fix for this bug, which is caused by the new major version 4 of Psych library in ruby3.0.
Processed: closing 996296
Processing commands for cont...@bugs.debian.org: > close 996296 Bug #996296 [src:ruby-i18n] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: Marked Bug as done > 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
Processed: fixed 996296 in ruby-i18n/1.18.11-1
Processing commands for cont...@bugs.debian.org: > fixed 996296 ruby-i18n/1.18.11-1 Bug #996296 [src:ruby-i18n] ruby-ice-cube: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:ArgumentError: The source ruby-i18n and version 1.18.11-1 do not appear to match any binary packages Marked as fixed in versions ruby-i18n/1.18.11-1. > 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
