Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception
Control: found -1 5.2.0-3 Contrl: tags -1 bullseye bookworm unstable On Wed, Oct 20, 2021 at 09:14:31AM +0200, Francois Lesueur wrote: > Version: 5.2.0-4 You filed this with the version in bookworm, but your test was done in bullseye (and I also verified this affects bullseye), so marking the bug as such. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: Re: Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception
Processing control commands: > found -1 5.2.0-3 Bug #996878 [python3-prelude] python3-prelude: python3 import prelude throws an ImportError exception Marked as found in versions libprelude/5.2.0-3. -- 996878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#996878: python3-prelude: python3 import prelude throws an ImportError exception
Processing control commands: > found -1 5.2.0-3 Bug #996878 [python3-prelude] python3-prelude: python3 import prelude throws an ImportError exception Ignoring request to alter found versions of bug #996878 to the same values previously set -- 996878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999360: resolved in 0.8.4-4
Control: close -1 Control: fixed -1 0.8.4-4 I erroneously closed the wrong bug with upload of 0.8.4-4 (see [1]). So, closing this one manually now. The 0.8.4-4 changelog entry has been fixed in Git and will be correct with the upcoming upload of libayatana-indicator. Thanks to Adrian for reopening the other bug. Mike [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993960#30 -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpUV8Jo4YQTx.pgp Description: Digitale PGP-Signatur
Processed: resolved in 0.8.4-4
Processing control commands:
> close -1
Bug #999360 [src:libayatana-indicator]
libayatana-indicator_0.8.4-3_all-buildd.changes REJECTED
Marked Bug as done
> fixed -1 0.8.4-4
Bug #999360 {Done: Mike Gabriel }
[src:libayatana-indicator] libayatana-indicator_0.8.4-3_all-buildd.changes
REJECTED
Marked as fixed in versions libayatana-indicator/0.8.4-4.
--
999360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#974606: [Pkg-rust-maintainers] Bug#974606: should rust-tokio-process be removed?
On November 12, 2021 6:47 am, peter green wrote: > In addition to the (build-)dependency on an old version of > rust-crossbeam-queue, > rust-tokio-process (build-)depends on version 0.1 of rust-futures. Upstream > seems to > have abandoned the crate, there was an alpha release supporting futures 0.2, > but > the code appears to have been removed from the tokio git repository. it was moved from a separate crate to a 'process' feature in the main tokio crate. there are a few more like this[1], and they can all be RMed once we upload tokio 1.x (plus the remaining related/supporting crates tokio-util, tokio-macros, tokio-stream, bytes, mio, tracing, ..). > > There are no reverse dependencies in testing or unstable > > If there are no objections in a few weeks, I intend to file a removal request. 1: see https://tokio.rs/blog/2019-11-tokio-0-2 and the diff between 0.1 and 0.2, AFAICT the following were dropped altogether as standalone crates: tokio-async-await tokio-buf tokio-codec tokio-core tokio-current-thread tokio-executor tokio-fs tokio-io tokio-process tokio-reactor tokio-signal tokio-sync tokio-tcp tokio-threadpool tokio-timer tokio-udp tokio-uds
Bug#997137: ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage
Control: tags -1 + patch fixed-upstream
On Sat, 23 Oct 2021 at 20:53:39 +0200, Lucas Nussbaum wrote:
> > /usr/include/c++/11/type_traits:44:3: error: template with C linkage
> >44 | template
> > | ^~~~
> > run-passwd.cpp:10:1: note: ‘extern "C"’ linkage started here
> >10 | extern "C" {
> > | ^~
This appears to be fixed by the attached patch from upstream. (Compiled
successfully on amd64, not otherwise tested.)
To avoid this sort of thing happening whenever a new GLib version has
a behaviour change, it would also be a good idea to choose a target version
of GLib and define the GLIB_VERSION_MIN_REQUIRED and GLIB_VERSION_MAX_ALLOWED
macros, similar to .
I do not use UKUI myself and I do not intend to NMU this.
smcv
From: Z-bin <1134636...@qq.com>
Date: Sat, 6 Mar 2021 16:06:13 +0800
Subject: fix: Not include glib's headers in an 'extern "C"' context
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Description: Not include glib's headers in an 'extern "C"' context
Log: 去除extern "C"
Origin: upstream, commit:291c510087cc2443fb4f49cdb61d0de5e66417ca
Bug-Debian: https://bugs.debian.org/997137
---
checkUserPwd/main.cpp| 5 -
plugins/account/userinfo/changefacedialog.h | 2 --
plugins/account/userinfo/changepwddialog.cpp | 3 ---
plugins/account/userinfo/qtdbus/userdispatcher.h | 2 --
plugins/account/userinfo/run-passwd.cpp | 3 ---
plugins/account/userinfo/userinfo.cpp| 2 --
plugins/devices/audio/ukmedia_main_widget.h | 3 ++-
plugins/devices/keyboard/kbdlayoutmanager.cpp| 2 --
plugins/devices/mouse/mousecontrol.cpp | 2 --
plugins/devices/shortcut/realizeshortcutwheel.h | 2 --
plugins/devices/shortcut/shortcut.cpp| 3 ---
plugins/devices/touchpad/touchpad.cpp| 2 --
plugins/messages-task/notice/notice.h| 2 --
plugins/messages-task/notice/realizenotice.h | 2 --
plugins/network/proxy/proxy.h| 2 --
plugins/personalized/desktop/realizedesktop.h| 2 --
plugins/personalized/fonts/fonts.h | 2 --
plugins/personalized/screensaver/screensaver.h | 2 --
plugins/personalized/wallpaper/wallpaper.h | 2 --
plugins/security-updates/backup/backup.cpp | 2 --
plugins/system/autoboot/addautoboot.h| 2 --
plugins/system/autoboot/autoboot.cpp | 2 --
plugins/system/defaultapp/addappdialog.h | 2 --
plugins/system/defaultapp/defaultapp.h | 2 --
plugins/time-language/area/area.h| 2 --
plugins/time-language/datetime/changtime.h | 2 --
plugins/time-language/datetime/datetime.h| 2 --
shell/mainwindow.cpp | 2 --
28 files changed, 2 insertions(+), 61 deletions(-)
diff --git a/checkUserPwd/main.cpp b/checkUserPwd/main.cpp
index a352f07..1ed17b0 100644
--- a/checkUserPwd/main.cpp
+++ b/checkUserPwd/main.cpp
@@ -18,16 +18,11 @@
*
*/
-extern "C" {
-
#include
#include
#include
-
#include
-}
-
#define SHADOW_FILE "/etc/shadow"
#define BUFF_SIZE 256
#define SIZE 256
diff --git a/plugins/account/userinfo/changefacedialog.h b/plugins/account/userinfo/changefacedialog.h
index 4686165..609e6a7 100644
--- a/plugins/account/userinfo/changefacedialog.h
+++ b/plugins/account/userinfo/changefacedialog.h
@@ -35,10 +35,8 @@
#undef signals
#endif
-extern "C" {
#include
#include
-}
namespace Ui {
class ChangeFaceDialog;
diff --git a/plugins/account/userinfo/changepwddialog.cpp b/plugins/account/userinfo/changepwddialog.cpp
index 9156b79..630ab7c 100644
--- a/plugins/account/userinfo/changepwddialog.cpp
+++ b/plugins/account/userinfo/changepwddialog.cpp
@@ -36,12 +36,9 @@
#undef signals
#endif
-extern "C" {
#include
#include
-}
-
#include "run-passwd.h"
#define PWD_LOW_LENGTH 6
diff --git a/plugins/account/userinfo/qtdbus/userdispatcher.h b/plugins/account/userinfo/qtdbus/userdispatcher.h
index 401d45c..b7e243a 100644
--- a/plugins/account/userinfo/qtdbus/userdispatcher.h
+++ b/plugins/account/userinfo/qtdbus/userdispatcher.h
@@ -34,11 +34,9 @@
#undef signals
#endif
-extern "C" {
#include
#include
#include
-}
class UserInfo;
diff --git a/plugins/account/userinfo/run-passwd.cpp b/plugins/account/userinfo/run-passwd.cpp
index 6407929..d95490d 100644
--- a/plugins/account/userinfo/run-passwd.cpp
+++ b/plugins/account/userinfo/run-passwd.cpp
@@ -7,7 +7,6 @@
#undef signals
#endif
-extern "C" {
#include
#include
@@ -16,8 +15,6 @@ extern "C" {
#include
#include
-}
-
#include "run-passwd.h"
/* Buffer size for backend output */
diff --git a/plugins/account/userinfo/userinfo.cpp b/plugins/account/userinfo/userinfo.cpp
index 8488fef..29d5af6 100644
--- a/plugins/account/userinfo/userinfo.cpp
+++ b/plugins/account/userinfo/userinfo.cpp
@@ -43,10 +43,8 @@
#undef sig
Processed: Re: Bug#997137: ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage
Processing control commands: > tags -1 + patch fixed-upstream Bug #997137 [src:ukui-control-center] ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage Added tag(s) patch and fixed-upstream. -- 997137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999507: [Pkg-rust-maintainers] Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.
On November 12, 2021 6:38 am, Peter Green wrote: > Package: rust-tokio-signal > Version: 0.2.7-2 > Severity: serious > > rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream > seems to > have abandoned the project, there was an alpha release supporting futures > 0.2, but > the code appears to have been removed from the tokio git repository. So I > presume > it is abandoned upstream. > > There are no reverse dependencies in testing, there is a single reverse > dependency > in unstable which is rc buggy and also appears to be abandoned upstream. > > If there are no objections in a few weeks, I intend to file a removal request. same here, tokio-signal is now tokio+signal ;) accordingly, it can be RMed with the rest of the legacy tokio 0.1 crates once tokio 1.0 has been uploaded
Processed: Bug#997141 marked as pending in ayatana-indicator-sound
Processing control commands: > tag -1 pending Bug #997141 [src:ayatana-indicator-sound] ayatana-indicator-sound: FTBFS: indicator-sound-service.h:826:1: error: unknown type name ‘VALA_EXTERN’; did you mean ‘G_LOCK_EXTERN’? Added tag(s) pending. -- 997141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997141: marked as pending in ayatana-indicator-sound
Control: tag -1 pending Hello, Bug #997141 in ayatana-indicator-sound 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-ayatana-team/ayatana-indicator-sound/-/commit/aafbaac07f5e7dd19f34551114fec2359983dbd0 debian/patches: Add 0001_Fix-undefined-VALA_EXTERN.patch. Resolve FTBFS againt latest Vala compiler. (Closes: #997141). (this message was generated automatically) -- Greetings https://bugs.debian.org/997141
Bug#997350: marked as pending in python-pecan
Control: tag -1 pending Hello, Bug #997350 in python-pecan reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pecan/-/commit/65057f8f620e66fd220a338c88b15f9b996713b8 Add Support_SQLAlchemy_1.4.x.patch (Closes: #997350). (this message was generated automatically) -- Greetings https://bugs.debian.org/997350
Processed: Bug#997350 marked as pending in python-pecan
Processing control commands: > tag -1 pending Bug #997350 [src:python-pecan] python-pecan: FTBFS: KeyError: 'greenlet' Added tag(s) pending. -- 997350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997468: marked as done (sadisplay: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Fri, 12 Nov 2021 09:48:54 +
with message-id
and subject line Bug#997468: fixed in sadisplay 0.4.9-2
has caused the Debian Bug report #997468,
regarding sadisplay: 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.)
--
997468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sadisplay
Version: 0.4.9-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=pybuild --with
> python3
> dh: error: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose
> from: binary binary-arch binary-indep build build-arch build-indep clean
> install install-arch install-indep)
> dh build --buildsystem=pybuild --with python3
>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
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sadisplay/build/sadisplay
> copying sadisplay/__init__.py ->
> /<>/.pybuild/cpython3_3.9_sadisplay/build/sadisplay
> copying sadisplay/describe.py ->
> /<>/.pybuild/cpython3_3.9_sadisplay/build/sadisplay
> copying sadisplay/reflect.py ->
> /<>/.pybuild/cpython3_3.9_sadisplay/build/sadisplay
> copying sadisplay/render.py ->
> /<>/.pybuild/cpython3_3.9_sadisplay/build/sadisplay
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:285: cp -r /<>/tests
> /<>/.pybuild/cpython3_3.9_sadisplay/build/
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_sadisplay/build; python3.9 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 7 items
>
> tests/test_describe.py F.F
> [100%]
>
> === FAILURES
> ===
> __ test_single_mapper
> __
>
> def test_single_mapper():
>
> objects, relations, inherits = sadisplay.describe([model.User])
>
> assert len(objects) == 1
> assert relations == []
> assert inherits == []
> > assert objects[0] == {
> 'name':
> model.User.__name__,
> 'cols': [
> ('INTEGER', 'id', 'pk'),
> ('VARCHAR(50)', 'name', None),
> ],
> 'indexes': [{
> 'cols': ['name', 'department'],
> 'name': 'ix_username_department',
> }],
> 'props': [
> 'address',
> 'books',
> ],
> 'methods': [
> 'login',
> ],
> }
> E AssertionError: assert {'cols': [('I...: 'User', ...} == {'cols':
> [('I...: 'User', ...}
> E Omitting 4 identical items, use -vv to show
> E Differing items:
> E {'props': ['address']} != {'props': ['address', 'books']}
> E Use -v to get the full diff
>
> tests/test_describe.py:17: AssertionError
> test_inherits
> _
>
> def test_inherits():
>
> objects, relations, inherits = sadisplay \
> .describe([model.User, model.Admin, model.Manager])
>
> assert len(relations) == 0
> assert len(objects) == 3
> assert len(inherits) == 2
> > assert objects[1] == {
> 'name':
> model.Admin.__name__,
> 'cols': [
> ('INTEGER', 'id', 'pk'),
> ('VARCHAR(50)', 'name', None),
> ('VARCHAR(50)', 'phone', None),
> ],
> 'indexes': [{
> 'cols': ['name', 'department'],
> 'name': 'ix_username_department',
> }],
> 'props': [
> 'address',
> 'books',
> ],
> 'methods': [
>
Bug#997350: marked as done (python-pecan: FTBFS: KeyError: 'greenlet')
Your message dated Fri, 12 Nov 2021 10:03:48 + with message-id and subject line Bug#997350: fixed in python-pecan 1.3.3-4 has caused the Debian Bug report #997350, regarding python-pecan: FTBFS: KeyError: 'greenlet' 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.) -- 997350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pecan Version: 1.3.3-3 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): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > set -e && for pyvers in 3.9 ; do \ > python$pyvers setup.py test -v ; \ > done > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > WARNING: The directory '/sbuild-nonexistent/.cache/pip' or its parent > directory is not owned or is not writable by the current user. The cache has > been disabled. Check the permissions and owner of that directory. If > executing pip with sudo, you may want sudo's -H flag. > ERROR: Exception: > Traceback (most recent call last): > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/resolvers.py", > line 171, in _merge_into_criterion > crit = self.state.criteria[name] > KeyError: 'greenlet' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/share/python-wheels/requests-2.25.1-py2.py3-none-any.whl/requests/adapters.py", > line 412, in send > conn = self.get_connection(request.url, proxies) > File > "/usr/share/python-wheels/requests-2.25.1-py2.py3-none-any.whl/requests/adapters.py", > line 309, in get_connection > proxy_manager = self.proxy_manager_for(proxy) > File > "/usr/share/python-wheels/requests-2.25.1-py2.py3-none-any.whl/requests/adapters.py", > line 193, in proxy_manager_for > manager = self.proxy_manager[proxy] = proxy_from_url( > File > "/usr/share/python-wheels/urllib3-1.26.5-py2.py3-none-any.whl/urllib3/poolmanager.py", > line 536, in proxy_from_url > return ProxyManager(proxy_url=url, **kw) > File > "/usr/share/python-wheels/urllib3-1.26.5-py2.py3-none-any.whl/urllib3/poolmanager.py", > line 480, in __init__ > raise ProxySchemeUnknown(proxy.scheme) > urllib3.exceptions.ProxySchemeUnknown: Proxy URL had no scheme, should start > with http:// or https:// > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", > line 223, in _main > status = self.run(options, args) > File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", > line 180, in wrapper > return func(self, options, args) > File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line > 162, in run > requirement_set = resolver.resolve( > File > "/usr/lib/python3/dist-packages/pip/_internal/resolution/resolvelib/resolver.py", > line 122, in resolve > self._result = resolver.resolve( > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/resolvers.py", > line 453, in resolve > state = resolution.resolve(requirements, max_rounds=max_rounds) > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/resolvers.py", > line 318, in resolve > name, crit = self._merge_into_criterion(r, parent=None) > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/resolvers.py", > line 173, in _merge_into_criterion > crit = Criterion.from_requirement(self._p, requirement, parent) > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/resolvers.py", > line 82, in from_requirement > if not cands: > File > "/usr/share/python-wheels/resolvelib-0.5.4-py2.py3-none-any.whl/resolvelib/structs.py", > line 124, in __bool__ > return bool(self._sequence) > File > "/usr/lib/python3/dist-packages/pip/_internal/resolution/resolvelib/found_candidates.py", > line 99, in __bool__ > return any(self) > File > "/usr/lib/python3/dist-packages/pip/_internal/resolution/resolvelib/factory.py", > line 220, in iter_ind
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forwarded 997289 https://github.com/ericniebler/range-v3/issues/1672
Bug #997289 [src:range-v3] range-v3: FTBFS: concepts.hpp:455:5: error:
satisfaction of atomic constraint ‘requires(T& t, T& u)
{(conceptsswap)(t, u);} [with T = S]’ depends on itself
Set Bug forwarded-to-address to
'https://github.com/ericniebler/range-v3/issues/1672'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
997289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984224: marked as done (lomiri-app-launch: ftbfs with GCC-11)
Your message dated Fri, 12 Nov 2021 10:49:49 +
with message-id
and subject line Bug#984224: fixed in lomiri-app-launch 0.0.90-9
has caused the Debian Bug report #984224,
regarding lomiri-app-launch: 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.)
--
984224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lomiri-app-launch
Version: 0.0.90-7
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/lomiri-app-launch_0.0.90-7_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.
[...]
from
/<>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.h:12,
from
/<>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:13:
/<>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:
In function ‘proxy_socket_demangler_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of
‘__atomic_load’ discards ‘volatile’ qualifier
[-Werror=incompatible-pointer-types]
112 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
__ATOMIC_SEQ_CST); \
| ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
‘g_atomic_pointer_get’
260 | (!g_atomic_pointer_get (location) && \
| ^~~~
/usr/include/glib-2.0/gobject/gtype.h:2042:7: note: in expansion of macro
‘g_once_init_enter’
2042 | if (g_once_init_enter (&g_define_type_id__volatile)) \
| ^
/usr/include/glib-2.0/gobject/gtype.h:1803:61: note: in expansion of macro
‘_G_DEFINE_INTERFACE_EXTENDED_BEGIN’
1803 | #define G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, _C_)
_G_DEFINE_INTERFACE_EXTENDED_BEGIN(TN, t_n, T_P) {_C_;}
_G_DEFINE_INTERFACE_EXTENDED_END()
|
^~
/usr/include/glib-2.0/gobject/gtype.h:1784:61: note: in expansion of macro
‘G_DEFINE_INTERFACE_WITH_CODE’
1784 | #define G_DEFINE_INTERFACE(TN, t_n, T_P)
G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, ;)
|
^~~~
/<>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:265:1:
note: in expansion of macro ‘G_DEFINE_INTERFACE’
265 | G_DEFINE_INTERFACE (proxySocketDemangler, proxy_socket_demangler,
G_TYPE_OBJECT)
| ^~
/<>/obj-x86_64-linux-gnu/liblomiri-app-launch/proxy-socket-demangler.c:
In function ‘proxy_socket_demangler_proxy_get_type’:
/usr/include/glib-2.0/glib/gatomic.h:112:5: error: argument 2 of
‘__atomic_load’ discards ‘volatile’ qualifier
[-Werror=incompatible-pointer-types]
112 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
__ATOMIC_SEQ_CST); \
| ^
/usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
‘g_atomic_pointer_get’
260 | (!g_atomic_pointer_get (location) && \
| ^~~~
/usr/include/glib-2.0/gobject/gt
Processed: Re: Bug#997118: kmplayer: FTBFS: type_traits:44:3: error: template with C linkage
Processing control commands: > tags -1 + patch upstream Bug #997118 [src:kmplayer] kmplayer: FTBFS: type_traits:44:3: error: template with C linkage Added tag(s) patch and upstream. -- 997118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997118: kmplayer: FTBFS: type_traits:44:3: error: template with C linkage
Control: tags -1 + patch upstream
On Sat, 23 Oct 2021 at 20:38:16 +0200, Lucas Nussbaum wrote:
> > /usr/include/c++/11/type_traits:44:3: error: template with C linkage
> >44 | template
> > | ^~~~
> > /<>/src/npplayer.cpp:24:1: note: ‘extern "C"’ linkage started
> > here
> >24 | extern "C" {
> > | ^~
This is caused by a behaviour change in GLib 2.68, which now uses inline
C++ in some headers when they are compiled as C++, for better type-safety
for C++ callers.
Since knpplayer seems to be a standalone host for NPAPI browser plugins
(which are an obsolete technology) and depends on the obsolete libraries
GTK 2 and dbus-glib, I would personally suggest disabling/removing the
knpplayer part of this package instead of fixing it: see #999459 for
details and a patch (builds successfully, otherwise untested).
Or, if that's not considered acceptable, there are two strategies that
kmplayer could use to solve this: it can either ask GLib to behave more
like the older GLib versions for which this module was developed, or
move the header inclusion out from under the extern "C" guards. See the
attached patches for more information.
Either one of the attached patches is sufficient to make this package
build (again, compiled successfully but otherwise untested), but it would
be most robust to do both.
smcv
From: Simon McVittie
Date: Fri, 12 Nov 2021 09:33:59 +
Subject: npplayer: Don't wrap third-party headers in extern "C"
These libraries all include extern "C" guards in their headers when
compiled as C++ (in some cases via a macro such as GLib's G_BEGIN_DECLS),
so it is unnecessary to wrap them in another layer of extern "C".
Some C library headers make use of C++ in inline functions when compiled
as C++: in particular, GLib 2.68+ does this for better type-safety.
This will not work inside an extern "C" block.
Bug-Debian: https://bugs.debian.org/997118
---
src/npplayer.cpp | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/npplayer.cpp b/src/npplayer.cpp
index 6881abe..a38f898 100644
--- a/src/npplayer.cpp
+++ b/src/npplayer.cpp
@@ -21,7 +21,6 @@
http://devedge-temp.mozilla.org/library/manuals/2002/plugin/1.0/
http://dbus.freedesktop.org/doc/dbus/libdbus-tutorial.html
*/
-extern "C" {
#include
#include
#include
@@ -50,6 +49,8 @@ extern "C" {
#define INITIAL_WINDOW_WIDTH 1920
+extern "C" {
+
typedef const char* (* NP_LOADDS NP_GetMIMEDescriptionUPP)();
typedef NPError (* NP_GetValueUPP)(void *inst, NPPVariable var, void *value);
typedef NPError (* NP_InitializeUPP)(NPNetscapeFuncs*, NPPluginFuncs*);
From: Simon McVittie
Date: Fri, 12 Nov 2021 09:49:41 +
Subject: npplayer: Target a specific GLib API version
Since GLib 2.32 (2012), setting GLIB_VERSION_MIN_REQUIRED selects the
minimum required version of GLib for this project. Code that was
deprecated after that version will not cause deprecation warnings, and
where header files have changed their compile-time behaviour over time,
the behaviour that was seen in the selected version will be used where
possible.
In particular, this disables new C++ behaviour introduced in GLib 2.68,
which caused this project to fail to build.
Similarly, setting GLIB_VERSION_MAX_ALLOWED causes GLib to emit warnings
if a function introduced after the selected version is used, even inside
a GLIB_CHECK_VERSION guard.
There is no particular significance to 2.50, except that it's the
version in Debian 9 (2017), which is the oldest build environment that
I have conveniently available.
Bug-Debian: https://bugs.debian.org/997118
---
src/CMakeLists.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index 7a05382..4fd436c 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -135,7 +135,7 @@ if (KMPLAYER_WITH_NPP)
add_executable(knpplayer ${knpplayer_SRCS})
SET_TARGET_PROPERTIES(knpplayer PROPERTIES COMPILE_FLAGS
-"${GLibDBusCflags} ${GTKCflags} ${GThreadCflags} ${GModuleCflags}"
+"-DGLIB_VERSION_MAX_ALLOWED=\"G_ENCODE_VERSION(2,50)\" -DGLIB_VERSION_MIN_REQUIRED=\"G_ENCODE_VERSION(2,50)\" ${GLibDBusCflags} ${GTKCflags} ${GThreadCflags} ${GModuleCflags}"
)
target_link_libraries(knpplayer ${GLibDBusLinkFlags} ${GTKLinkFlags} ${GThreadLinkFlags} ${GModuleLinkFlags}
Bug#999554: mbdyn: FTBFS: ISO C++17 does not allow dynamic exception specifications
Source: mbdyn Version: 1.7.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source | In file included from wraptest.cc:61: | naivewrap.h:59:27: error: ISO C++17 does not allow dynamic exception | specifications |59 | void Factor(void) throw(LinearSolver::ErrFactor); | | ^ | make[3]: *** [Makefile:670: wraptest.o] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=mbdyn&arch=amd64&ver=1.7.3-1%2Bb3&stamp=1636533608&raw=0 Cheers -- Sebastian Ramacher
Bug#998634: marked as done (sssd: Please switch libsemanage1-dev BD to libsemanage-dev)
Your message dated Fri, 12 Nov 2021 11:49:08 + with message-id and subject line Bug#998634: fixed in sssd 2.5.2-5 has caused the Debian Bug report #998634, regarding sssd: Please switch libsemanage1-dev BD to libsemanage-dev 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.) -- 998634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sssd Version: 2.4.1-2 Severity: important Hello, I'm planning in the following days to upload a new version of libsemange to unstable. This new version has bumped the soname, I used this occasion to rename the -dev package from libsemanage1-dev to libsemanage-dev so it matches the .pc file and library name. I tried to rebuild the package and it's building fine with the new version. You'll have to adjust the BD at that moment I upload the new version. Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: sssd Source-Version: 2.5.2-5 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of sssd, 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 sssd 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: Mon, 08 Nov 2021 21:17:29 +0200 Source: sssd Built-For-Profiles: noudeb Architecture: source Version: 2.5.2-5 Distribution: unstable Urgency: medium Maintainer: Debian SSSD Team Changed-By: Timo Aaltonen Closes: 998634 Changes: sssd (2.5.2-5) unstable; urgency=medium . * control: Fix libsemanage-dev build-dep. (Closes: #998634) Checksums-Sha1: 9546f337573e5ef08421dd97c3eb6d65626a9afe 4956 sssd_2.5.2-5.dsc 50d27c0c88e86b7a67bb697f08fcf57c5f521dd8 38096 sssd_2.5.2-5.debian.tar.xz 5755f7fea4fa0aeae319c357b07aab4c3ca2ade4 9764 sssd_2.5.2-5_source.buildinfo Checksums-Sha256: 4935edb13dfba5dfc1a76c6313b1eb554eff30434a2d7f636145ea6581b8ce29 4956 sssd_2.5.2-5.dsc 7d9946a82a9c57e43e53d52d076bd3a1a4ef01fa638aae78cfa2dfc7fdc25501 38096 sssd_2.5.2-5.debian.tar.xz 9cb69530cff13a0ace952e8639ba991e80099cee52fde4ff11d1f63f9f8117e4 9764 sssd_2.5.2-5_source.buildinfo Files: 8408e0d6e3db4aa3acc2fab3e247e95a 4956 utils optional sssd_2.5.2-5.dsc 125ccc1e350cfb0722dd119de96313e6 38096 utils optional sssd_2.5.2-5.debian.tar.xz cda44f644485cf498aa1cea49d7c2cea 9764 utils optional sssd_2.5.2-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmGJd9sACgkQy3AxZaiJ hNyXWxAAjQqHuXBAZOhAxunJAx0n7mBkq1OBNwSUG8d9m8ssio+g+6f2mpQpZbj5 g4ZNg0AapRqlQSRRaE2Cpk+XqBnfh66paD33SJ1QQJS1mR1gYmKYmVeCdBZeQJSM AAjMbRtB/9YbN0Dg9l41pzIU/+PDPJ4OJeu+e6+hy+olaZIo5oDghYSxUubJe3z2 Yl5qfKP7umulL/2i20mj0+kJ1c4X5IKXL2Cdo94qPIDkeEXS114XQ4bd19mMMa3/ qXLhfZ5b6oL9zWmDfs5KOD0b0DD7/gH19PNA3VCAbBy2Vol7mgvkkATuJIy65TwQ n3k5jH55QcXlBdE4xtsv6jraFaGaWBvO1leuOWwwzBNsEBUs9h1XghSY4mmrHfIB BzOU+xKaHDx7R6BlR3+FEeOE1VrSsB/s8Ran2opFRk6s9OEv3Um4o0gXr/flIc+y rb33aPiD86YOozIQF0qw3yrl+m/3TFXM7MFGh+rJBlmQDZLRYBsUqRru/0T7p0bO wRKSsNs9tyAp/8wlWlFMu7jAsl0hZJTTjViXfBrmlmAkoDgvxyk3B7x39sXwo5Ob ieqgYQO4TrKsMiXUV7zwetrKT/QzNaWdTKrC1pQcR8mUH+BkDIbXBcMiUCdC/L6B NxC05YpCUm+N+xu/sZqbuQ9Xr/mZXukOINQWK6GR9DWfoV0u4ug= =B5td -END PGP SIGNATURE End Message ---
Bug#999507: [Pkg-rust-maintainers] Bug#999507: Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.
Le ven 12 nov 2021 à 10:18, Fabian Grünbichler a écrit : On November 12, 2021 6:38 am, Peter Green wrote: Package: rust-tokio-signal Version: 0.2.7-2 Severity: serious rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream seems to have abandoned the project, there was an alpha release supporting futures 0.2, but the code appears to have been removed from the tokio git repository. So I presume it is abandoned upstream. There are no reverse dependencies in testing, there is a single reverse dependency in unstable which is rc buggy and also appears to be abandoned upstream. If there are no objections in a few weeks, I intend to file a removal request. same here, tokio-signal is now tokio+signal ;) accordingly, it can be RMed with the rest of the legacy tokio 0.1 crates once tokio 1.0 has been uploaded I would not even wait for tokio 1.0 upload and request removal of tokio-signal could be done right away. As it stands, it is broken due to unsastifiable build dependencies and it has no reverse dependencies, as Peter explained. Fabian, I see no point in keeping tokio-signal in the archive in its current state and the package is going away anyway as you mentionned it being superseeded by tokio+signal. Do you see any reasons to keep it until tokio 1.0 upload? Regards, Henry-Nicolas
Processed: Reassign #997550 to src:jetty9
Processing commands for cont...@bugs.debian.org: > reassign 997550 src:jetty9 Bug #997550 [src:libfreemarker-java] libfreemarker-java: FTBFS: [ivy:retrieve] :: org.eclipse.jetty#jetty-util;7.6.16.v20140903: not found Bug reassigned from package 'src:libfreemarker-java' to 'src:jetty9'. No longer marked as found in versions libfreemarker-java/2.3.23-11. Ignoring request to alter fixed versions of bug #997550 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 997550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998575: [Pkg-freeipa-devel] Bug#998575: Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
On 9.11.2021 10.53, Ondřej Surý wrote: Hi Timo, On 5. 11. 2021, at 8:09, Timo Aaltonen wrote: On 5.11.2021 1.37, peter green wrote: bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be installed It looks like bind8 no longer builds the bind9-dev package. It's still present in unstable as a cruft package but is uninstallable due to version constraints, it's completely gone from testing. I don't know what's going on here, but at least the current bind9 packaging is not available on salsa, debian/main is on 9.16.22-1 and according to d/changelog it was uploaded to unstable on the same day as 9.17.19-1... (which has now migrated to testing already) The 9.17 packaging is available from the isc/9.17 branch which should be up to date. The new bind9 doesn't mention dropping bind9-dev on d/changelog. Ondrej, why was it dropped? We need to figure out what to do with bind-dyndb-ldap in the future. The BIND 9 libraries are not meant for public consumption since 9.14.0. The upstream (which is incidentally also me) has declare the libraries private and the symbols could change even between patch releases. There’s absolutely no guarantee about symbol stability even on stable branch. Unfortunately, bind-dyndb-ldap is licensed under GPL-2.0 which makes it impossible to include it directly in the src:bind9 package. I see no easy way from this. I will reintroduce the bind9-dev package, but this will make the bind-dyndb-ldap package to regularly FTBFS anyway and it needs to be fixed before the next stable release. Thanks for adding the -dev, but it's missing the .so's? bind-dyndb-ldap fails to pass configure with the current version. Looks like dns/version.h is gone as well, and there are several checks for the version in the code. -- t
Processed: Reassign 997546 src:jetty9
Processing commands for cont...@bugs.debian.org:
> reassign 997546 src:jetty9
Bug #997546 [src:lucene4.10] lucene4.10: FTBFS: [ivy:retrieve] ::
org.eclipse.jetty#jetty-http;${/org.eclipse.jetty/jetty-http}: not found
Bug reassigned from package 'src:lucene4.10' to 'src:jetty9'.
No longer marked as found in versions lucene4.10/4.10.4+dfsg-6.
Ignoring request to alter fixed versions of bug #997546 to the same values
previously set
> forcemerge 997546 997550
Bug #997546 [src:jetty9] lucene4.10: FTBFS: [ivy:retrieve] ::
org.eclipse.jetty#jetty-http;${/org.eclipse.jetty/jetty-http}: not found
Bug #997550 [src:jetty9] libfreemarker-java: FTBFS: [ivy:retrieve]
:: org.eclipse.jetty#jetty-util;7.6.16.v20140903: not found
Merged 997546 997550
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997546
997550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997545: marked as pending in python-proliantutils
Control: tag -1 pending Hello, Bug #997545 in python-proliantutils reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-proliantutils/-/commit/a4a38e5c310c212c608d22516355cb7378488f2b Add Fix_the_test_cases_for_latest_sushy.patch (Closes: #997545). (this message was generated automatically) -- Greetings https://bugs.debian.org/997545
Processed: Bug#997545 marked as pending in python-proliantutils
Processing control commands: > tag -1 pending Bug #997545 [src:python-proliantutils] python-proliantutils: FTBFS: tests failed Added tag(s) pending. -- 997545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Reassign 998556 to src:commons-io
Processing commands for cont...@bugs.debian.org: > reassign 998556 src:commons-io Bug #998556 [src:gkl] gkl: FTBFS: Could not resolve commons-io:commons-io:2.4. Bug reassigned from package 'src:gkl' to 'src:commons-io'. No longer marked as found in versions gkl/0.8.7+dfsg-1. Ignoring request to alter fixed versions of bug #998556 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 998556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997550: marked as done (libfreemarker-java: FTBFS: [ivy:retrieve] :: org.eclipse.jetty#jetty-util;7.6.16.v20140903: not found)
Your message dated Fri, 12 Nov 2021 14:17:33 +0100 with message-id <5ace59c91d873b705fa8ecd757ec0635b7d769ef.ca...@debian.org> and subject line Re: lucene4.10: FTBFS: [ivy:retrieve] has caused the Debian Bug report #997546, regarding libfreemarker-java: FTBFS: [ivy:retrieve] :: org.eclipse.jetty#jetty-util;7.6.16.v20140903: 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.) -- 997546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfreemarker-java Version: 2.3.23-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- -Divy.default.ivy.user.dir=/<>/.ivy > -Dtitlebar.found=true \ > -DTODAY= -DDSTAMP= -DTSTAMP= -DtimestampNice= > -DtimestampInVersion= \ > javacc jar javadoc > ant -Divy.settings.file=/usr/share/ivy-debian-helper/ivysettings.xml > -Divy.default.ivy.user.dir=/<>/.ivy2 > -Divy.default.ivy.user.dir=/<>/.ivy -Dtitlebar.found=true > -DTODAY= -DDSTAMP= -DTSTAMP= -DtimestampNice= -DtimestampInVersion= javacc > jar javadoc > Buildfile: /<>/build.xml >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1612743144 > [mkdir] Created dir: /<>/build > [copy] Copying 1 file to /<>/build >[delete] Deleting: /<>/build/version.properties.tmp > > _autoget-deps: >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1612743144 > [copy] Copying 1 file to /<>/build >[delete] Deleting: /<>/build/version.properties.tmp > > update-deps: > [echo] Getting dependencies... > [echo] --- > [ivy:retrieve] :: Apache Ivy non official version - :: > https://ant.apache.org/ivy/ :: > [ivy:retrieve] :: loading settings :: file = > /usr/share/ivy-debian-helper/ivysettings.xml > [ivy:retrieve] [ivy-debian-helper] Loading the Maven rules... > [ivy:retrieve] :: resolving dependencies :: > org.freemarker#freemarker;working@ip-172-31-1-94 > [ivy:retrieve]confs: [default, runtime, build.base, build.j2se1.5, > build.jsp1.2, build.jsp2.0, build.jsp2.1, build.jython2.0, build.jython2.2, > build.jython2.5, test, build.test, run.test, IDE, retrotranslate, parser, > manual, bnd, example.servlet, example.webapp1, example.webapp2, > example.struts-webapp, example.ant] > [ivy:retrieve] [ivy-debian-helper] Replacing jaxen:jaxen:jar:1.0-FCS -> > jaxen:jaxen:jar:debian > [ivy:retrieve]found jaxen#jaxen;debian in debian > [ivy:retrieve][debian] jaxen#jaxen;1.0-FCS (forced) > [ivy:retrieve] [ivy-debian-helper] Ignoring saxpath:saxpath:jar:1.0-FCS > [ivy:retrieve]found org.debian.ivy#ivy-debian-helper;1.0 in debian > [ivy:retrieve][1.0] saxpath#saxpath;1.0-FCS (forced) > [ivy:retrieve] [ivy-debian-helper] Passing through > org.debian.maven:maven-repo-helper:jar:debian > [ivy:retrieve]found org.debian.maven#maven-repo-helper;debian in > debian > [ivy:retrieve] [ivy-debian-helper] Replacing xalan:xalan:jar:2.7.0 -> > xalan:xalan:jar:debian > [ivy:retrieve]found xalan#xalan;debian in debian > [ivy:retrieve][debian] xalan#xalan;2.7.0 (forced) > [ivy:retrieve] [ivy-debian-helper] Passing through xalan:serializer:jar:debian > [ivy:retrieve]found xalan#serializer;debian in debian > [ivy:retrieve] [ivy-debian-helper] Replacing dom4j:dom4j:jar:1.3 -> > dom4j:dom4j:jar:debian > [ivy:retrieve] dom4j#dom4j;debian is relocated to org.dom4j#dom4j;debian. > Please update your dependencies. > [ivy:retrieve]found dom4j#dom4j;debian in debian > [ivy:retrieve][debian] dom4j#dom4j;1.3 (forced) > [ivy:retrieve] [ivy-debian-helper] Passing through org.dom4j:dom4j:jar:debian > [ivy:retrieve]found org.dom4j#dom4j;debian in debian > [ivy:retrieve] [ivy-debian-helper] Replacing org.jdom:jdom:jar:1.0-beta8-dev > -> org.jdom:jdom:jar:debian > [ivy:retrieve]found org.jdom#jdom;debian in debian > [ivy:retrieve][debian] org.jdom#jdom;1.0-beta8-dev (forced) > [ivy:retrieve] [ivy-debian-helper] Replacing ant:ant:jar:1.6.5 -> > org.apache.ant:ant:jar:debian > [ivy:retrieve] [ivy-debian-helper] Passing through > org.apache.ant:ant-parent:jar:debian > [ivy:retrieve]found org.apache.ant#ant;debian in deb
Bug#998556: marked as done (gkl: FTBFS: Could not resolve commons-io:commons-io:2.4.)
Your message dated Fri, 12 Nov 2021 14:21:09 +0100 with message-id <5542e1173a0ed169f2b4bfb590d2fd98c4fd8f95.ca...@debian.org> and subject line Re: gkl: FTBFS: Could not resolve commons-io:commons-io:2.4. has caused the Debian Bug report #998556, regarding gkl: FTBFS: Could not resolve commons-io:commons-io:2.4. 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.) -- 998556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gkl Version: 0.8.7+dfsg-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): > make[1]: Entering directory '/<>' > dh_auto_build -- jar > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=gkl -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Settings evaluated using settings file '/<>/settings.gradle'. > Settings file not found (/<>/settings.gradle) > Root project name not defined in settings.gradle, defaulting to 'gkl' > instead of the name of the root directory 'gkl-0.8.7+dfsg' > Projects loaded. Root project using build file > '/<>/build.gradle'. > Included projects: [root project 'gkl'] > Keep-alive timer started > Adding Debian repository to project 'gkl' > Parallel execution is an incubating feature. > Evaluating root project 'gkl' using build file > '/<>/build.gradle'. > Compiling build file '/<>/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/build.gradle' using > BuildScriptTransformer. > Starting process 'command 'dpkg-parsechangelog''. Working directory: > /<> Command: dpkg-parsechangelog -S Version > Successfully started process 'command 'dpkg-parsechangelog'' > Adding Maven pom generation to project 'gkl' > Linking the generated javadoc to the system JDK API documentation > All projects evaluated. > Selected primary task 'jar' from project : > Creating new cache for annotation-processors, path > /<>/.gradle/4.4.1/fileContent/annotation-processors.bin, access > org.gradle.cache.internal.DefaultCacheAccess@7a34505a > Tasks to be executed: [task ':compileJava', task ':cmakeConfig', task > ':cmakeBuild', task ':copyNativeLib', task ':buildOnMac', task > ':processResources', task ':classes', task ':debianMavenPom', task ':jar'] > Creating new cache for resourceHashesCache, path > /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > Creating new cache for taskHistory, path > /<>/.gradle/4.4.1/taskHistory/taskHistory.bin, access > org.gradle.cache.internal.DefaultCacheAccess@49f1184e > Creating new cache for outputFiles, path > /<>/.gradle/buildOutputCleanup/outp
Bug#998575: [Pkg-freeipa-devel] Bug#998575: Bug#998575: Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
On 12.11.2021 15.14, Timo Aaltonen wrote: Thanks for adding the -dev, but it's missing the .so's? bind-dyndb-ldap fails to pass configure with the current version. Looks like dns/version.h is gone as well, and there are several checks for the version in the code. I see that lib/bind/api was removed in 9.17.10, bind-dyndb-ldap has not even looked at 9.17 yet.. -- t
Bug#998575: [Pkg-freeipa-devel] Bug#998575: Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
> On 12. 11. 2021, at 14:14, Timo Aaltonen wrote: > > Thanks for adding the -dev, but it's missing the .so's? bind-dyndb-ldap fails > to pass configure with the current version. Ah, I didn’t noticed that I listed them in the exclude files list, -3 coming up... > Looks like dns/version.h is gone as well, and there are several checks for > the version in the code. Yes, the file is gone upstream - the whole build system got rewritten to automake instead of the home-baked stuff. Cheers, Ondrej
Bug#999440: marked as done (golang-github-containerd-stargz-snapshotter: Build access network)
Your message dated Fri, 12 Nov 2021 14:35:52 + with message-id and subject line Bug#999440: fixed in golang-github-containerd-stargz-snapshotter 0.8.0-5 has caused the Debian Bug report #999440, regarding golang-github-containerd-stargz-snapshotter: Build access network 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.) -- 999440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-containerd-stargz-snapshotter Version: 0.8.0-3 Severity: serious X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/fetch.php?pkg=golang-github-containerd-stargz-snapshotter&arch=all&ver=0.8.0-4&stamp=1636327998&raw=0 === RUN TestLayerConvertFunc estargz_test.go:37: Get "https://github.com/AkihiroSuda/test-oci-archives/releases/download/v20210101/hello-world.tar.gz": dial tcp 140.82.121.3:443: connect: network is unreachable --- FAIL: TestLayerConvertFunc (0.13s) FAIL FAILgithub.com/containerd/stargz-snapshotter/nativeconverter/estargz 0.170s === RUN TestLayerConvertFunc zstdchunked_test.go:40: Get "https://github.com/AkihiroSuda/test-oci-archives/releases/download/v20210101/hello-world.tar.gz": dial tcp 140.82.121.3:443: connect: network is unreachable --- FAIL: TestLayerConvertFunc (0.00s) FAIL --- End Message --- --- Begin Message --- Source: golang-github-containerd-stargz-snapshotter Source-Version: 0.8.0-5 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of golang-github-containerd-stargz-snapshotter, 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. Reinhard Tartler (supplier of updated golang-github-containerd-stargz-snapshotter 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: Fri, 12 Nov 2021 07:57:26 -0500 Source: golang-github-containerd-stargz-snapshotter Architecture: source Version: 0.8.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Reinhard Tartler Closes: 999440 Changes: golang-github-containerd-stargz-snapshotter (0.8.0-5) unstable; urgency=medium . * exclude tests that reach out to internet (Closes: #999440) Checksums-Sha1: 14c4882efeb4c1a9936e03dd5182406ddd57defc 3593 golang-github-containerd-stargz-snapshotter_0.8.0-5.dsc e61a9b498b632a2ff6731626136f824bd71a47ee 4008 golang-github-containerd-stargz-snapshotter_0.8.0-5.debian.tar.xz Checksums-Sha256: ac76d40f92b75d1324e3ae8c89240cb8d593f7a7e0cf2098de1a94fefd868929 3593 golang-github-containerd-stargz-snapshotter_0.8.0-5.dsc 4cbbf335b576f7bad7949c72e76b45f968dbc15b742b835e0280edf194ca071e 4008 golang-github-containerd-stargz-snapshotter_0.8.0-5.debian.tar.xz Files: e44b1a8a55244b1210ff2db63faf4863 3593 golang optional golang-github-containerd-stargz-snapshotter_0.8.0-5.dsc 8d273ce8838b31360f4d19e5571a88a6 4008 golang optional golang-github-containerd-stargz-snapshotter_0.8.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmGOdXEUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJsulNQ//QSDGRRogLr2W7fnoRSwyDplmbykO Umt+h/4lTomuZRLUb99hL08s30uPnizu9WfdcJpdslfR3OrdDLDBHbNFNbodWSlJ 6npGlG0b2xdLbcIcSie8Cpnz6BelvLZdm+J1bw85kYWDQRCw0ugdRUxFTG1HIRP1 9vrpQWYotEEJFMNwhRaKQ7DqVdXIwVTjWNsDCV74Pjh77kSR1L/COkRjVbUsGiYW xhGHQq4dcIN7VtVWI4UY1gXbNQvAegMdXSaY+TF97fTitbX33toUUveEUfmStnNP bL7NTal/ofEKifrrbd1wndyrwD5Bp7biiojeMC1vSAiRmqkwivu8lT8l5hogwvmV hjIc6VSvLB34LX/JHRjObrmPuUQoKC3dG5+JCYHqtQKspZjFn215wyq5HbeiiqWQ BhG4oaBzkyljJNhtTqXwDSS0fb7BsGx91YVR75Gxm4OFC1wCeBClApJjz2omQDh0 1UAECAijw81rCu5ZrD7Cr9jclF91pEowrGpwcwj7N03YKDMzxZ8MDdI/GqJlFBLR FEwQNx7F4IykT0w3u6ATAoHX3I0OVoMgZGXEJqLAPBMm3eIlYtwwDwEBy2kcEUjP Yte5o6PgZNZdSImVT1xqL6ENnt/TElEmXdU5WGZjBtK5Exf/UY/23E/SRDmkWZ48 DQ1y+YTAsZ9ccLQ= =xnMG -END PGP SIGNATURE End Message ---
Bug#984019: marked as done (cmtk: ftbfs with GCC-11)
Your message dated Fri, 12 Nov 2021 14:35:47 + with message-id and subject line Bug#984019: fixed in cmtk 3.3.1p2+dfsg-1 has caused the Debian Bug report #984019, regarding cmtk: 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.) -- 984019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cmtk Version: 3.3.1p1+dfsg-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/cmtk_3.3.1p1+dfsg-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. [...] [ 10%] Building C object Utilities/NrrdIO/CMakeFiles/NrrdIO.dir/biffbiff.o cd /<>/obj-x86_64-linux-gnu/Utilities/NrrdIO && /usr/bin/cc -DCMTK_USE_DCMTK_JPEG -DHAVE_CONFIG_H -DNrrdIO_EXPORTS -DTEEM_BUILD=1 -DTEEM_DIO=0 -DTEEM_QNANHIBIT=1 -DTEEM_ZLIB -DTEEM_ZLIB=1 -I/<>/Utilities/mxml -I/<>/obj-x86_64-linux-gnu/Utilities/NrrdIO -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/NrrdIO.dir/biffbiff.o -c /<>/Utilities/NrrdIO/biffbiff.c [ 10%] Building C object Utilities/NrrdIO/CMakeFiles/NrrdIO.dir/biffmsg.o cd /<>/obj-x86_64-linux-gnu/Utilities/NrrdIO && /usr/bin/cc -DCMTK_USE_DCMTK_JPEG -DHAVE_CONFIG_H -DNrrdIO_EXPORTS -DTEEM_BUILD=1 -DTEEM_DIO=0 -DTEEM_QNANHIBIT=1 -DTEEM_ZLIB -DTEEM_ZLIB=1 -I/<>/Utilities/mxml -I/<>/obj-x86_64-linux-gnu/Utilities/NrrdIO -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/NrrdIO.dir/biffmsg.o -c /<>/Utilities/NrrdIO/biffmsg.c [ 10%] Building C object Utilities/NrrdIO/CMakeFiles/NrrdIO.dir/endianNrrd.o cd /<>/obj-x86_64-linux-gnu/Utilities/NrrdIO && /usr/bin/cc -DCMTK_USE_DCMTK_JPEG -DHAVE_CONFIG_H -DNrrdIO_EXPORTS -DTEEM_BUILD=1 -DTEEM_DIO=0 -DTEEM_QNANHIBIT=1 -DTEEM_ZLIB -DTEEM_ZLIB=1 -I/<>/Utilities/mxml -I/<>/obj-x86_64-linux-gnu/Utilities/NrrdIO -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/NrrdIO.dir/endianNrrd.o -c /<>/Utilities/NrrdIO/endianNrrd.c [ 11%] Building C object Utilities/NrrdIO/CMakeFiles/NrrdIO.dir/methodsNrrd.o cd /<>/obj-x86_64-linux-gnu/Utilities/NrrdIO && /usr/bin/cc -DCMTK_USE_DCMTK_JPEG -DHAVE_CONFIG_H -DNrrdIO_EXPORTS -DTEEM_BUILD=1 -DTEEM_DIO=0 -DTEEM_QNANHIBIT=1 -DTEEM_ZLIB -DTEEM_ZLIB=1 -I/<>/Utilities/mxml -I/<>/obj-x86_64-linux-gnu/Utilities/NrrdIO -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o CMakeFiles/NrrdIO.dir/methodsNrrd.o -c /<>/Utilities/NrrdIO/methodsNrrd.c [ 11%] Building C object Utilities/NrrdIO/CMakeFiles/NrrdIO.dir/sane.o cd /<>/obj-x86_64-linux-gnu/Utilities/NrrdIO && /usr/bin/cc -DCMTK_USE_DCMTK_JPEG -DHAVE_CONFIG_H -DNrrdIO_EXPORTS -DTEEM_BUILD=1 -DTEEM_DIO=0 -DTEEM_QNANHIBIT=1 -DTEEM_ZLIB -DTEEM_ZLIB=1 -I/<>/Utilities/mxml -I/<>/obj-x86_64-linux-gnu/Utilities/NrrdIO -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOUR
Bug#998912: marked as done (python3-hbmqtt: MQTTClient fails connecting to any broker: TypeError: 'Lock' object is not iterable)
Your message dated Fri, 12 Nov 2021 14:36:17 +
with message-id
and subject line Bug#998912: fixed in python-hbmqtt 0.9.6-1.2
has caused the Debian Bug report #998912,
regarding python3-hbmqtt: MQTTClient fails connecting to any broker: TypeError:
'Lock' object is not iterable
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.)
--
998912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hbmqtt
Version: 0.9.6-1.1
Severity: grave
Justification: hbmqtt.client.MQTTClient.connect never works
Tags: patch upstream
The MQTTClient is not useable at all at present. Trying to connect to
any broker results in the following:
| Unhandled exception: 'Lock' object is not iterable
| Connection failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Maximum number of connection attempts reached. Reconnection aborted
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 149, in connect
| return (yield from self._do_connect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 234, in
_do_connect
| return_code = yield from self._connect_coro()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 423, in
_connect_coro
| return_code = yield from self._handler.mqtt_connect()
| File
"/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/client_handler.py", line
83, in mqtt_connect
| yield from self._send_packet(connect_packet)
| File "/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/handler.py", line
445, in _send_packet
| with (yield from self._write_lock):
| TypeError: 'Lock' object is not iterable
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 220, in
reconnect
| return (yield from self._do_connect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 234, in
_do_connect
| return_code = yield from self._connect_coro()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 423, in
_connect_coro
| return_code = yield from self._handler.mqtt_connect()
| File
"/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/client_handler.py", line
83, in mqtt_connect
| yield from self._send_packet(connect_packet)
| File "/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/handler.py", line
445, in _send_packet
| with (yield from self._write_lock):
| TypeError: 'Lock' object is not iterable
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "", line 1, in
| File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in
run_until_complete
| return future.result()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 156, in connect
| return (yield from self.reconnect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 225, in
reconnect
| raise ConnectException("Too many connection attempts failed")
| hbmqtt.client.ConnectException: Too many connection attempts failed
The cause for this is a change in how asyncio Locks work. Their support
for the pre-async API based on iterators has ceased, but hbmqtt attempts
to do so. Avoiding the context manager does the trick here. Please find
a minimal patch fixing the problem attached.
In any case, hbmqtt looks quite dead upstream. Maybe replacing it with
https://github.com/sbtinstruments/asyncio-mqtt would be better.
Helmut
--- a/hbmqtt/mqtt/protocol/handler.py
+++ b/hbmqtt/mqtt/protocol/handler.py
@@ -442,8 +442,11 @@ class ProtocolHandler:
@asyncio.coroutine
def _send_packet(self, packet):
try:
-with (yield from self._write_lock):
+yield from self._write_lock.acquire()
+try:
yield from packet.to_stream(self.writer)
+finally:
+self._write_lock.release()
if self._keepalive_task:
self._keepalive_task.cancel()
self._keepalive_task = self._loop.call_later(self.keepalive_timeout, self.handle_write_timeo
Bug#984119: marked as done (fbpager: ftbfs with GCC-11)
Your message dated Fri, 12 Nov 2021 15:19:24 + with message-id and subject line Bug#984119: fixed in fbpager 0.1.5~git20090221.1.8e0927e6-3 has caused the Debian Bug report #984119, regarding fbpager: 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.) -- 984119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fbpager Version: 0.1.5~git20090221.1.8e0927e6-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/fbpager_0.1.5~git20090221.1.8e0927e6-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. [...] In file included from FbPager.cc:38: Resources.hh: In member function ‘std::string FbTk::Resource::getString() [with T = FbPager::FbPager::Alignment]’: Resources.hh:72:1: warning: control reaches end of non-void function [-Wreturn-type] 72 | } | ^ mv -f .deps/fbpager-FbPager.Tpo .deps/fbpager-FbPager.Po x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..-IFbTk -g -O2 -MT fbpager-Workspace.o -MD -MP -MF .deps/fbpager-Workspace.Tpo -c -o fbpager-Workspace.o `test -f 'Workspace.cc' || echo './'`Workspace.cc In file included from Workspace.hh:27, from Workspace.cc:24: FbTk/FbWindow.hh:208:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 208 | std::auto_ptr m_transparent; | ^~~~ In file included from /usr/include/c++/11/memory:76, from FbTk/FbWindow.hh:30, from Workspace.hh:27, from Workspace.cc:24: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ mv -f .deps/fbpager-Workspace.Tpo .deps/fbpager-Workspace.Po x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..-IFbTk -g -O2 -MT fbpager-Ewmh.o -MD -MP -MF .deps/fbpager-Ewmh.Tpo -c -o fbpager-Ewmh.o `test -f 'Ewmh.cc' || echo './'`Ewmh.cc In file included from Ewmh.cc:22: Ewmh.hh:52:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 52 | std::auto_ptr m_data; | ^~~~ In file included from /usr/include/c++/11/memory:76, from Ewmh.hh:26, from Ewmh.cc:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from Ewmh.cc:28: FbTk/FbWindow.hh:208:10: warning: ‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr' instead [-Wdeprecated-declarations] 208 | std::auto_ptr m_transparent; | ^~~~ In file included from /usr/include/c++/11/memory:76, from Ewmh.hh:26, from Ewmh.cc:22: /usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ In file included from Ewmh.cc:30: PropertyTools.hh:33:52: error: ISO C++17 does not allow dynamic exception specifications 33 | unsigned int getIntProperty(Window win,
Processed (with 1 error): transmission: ftbfs with autoconf 2.70
Processing commands for cont...@bugs.debian.org: > tags 978911 patch Bug #978911 [src:transmission] transmission: ftbfs with autoconf 2.70 Added tag(s) patch. > userubuntu-de...@lists.ubuntu.com Unknown command or malformed arguments to command. > usertags 978911 origin-ubuntu impish ubuntu-patch User is seb...@ubuntu.com There were no usertags set. Usertags are now: ubuntu-patch impish origin-ubuntu. > thank you Stopping processing here. Please contact me if you need assistance. -- 978911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978911: transmission: ftbfs with autoconf 2.70
tags 978911 patch
userubuntu-de...@lists.ubuntu.com
usertags 978911 origin-ubuntu impish ubuntu-patch
thank you
The attached patch should fix the issue
Index: transmission-3.00/configure.ac
===
--- transmission-3.00.orig/configure.ac
+++ transmission-3.00/configure.ac
@@ -555,9 +555,7 @@ dnl it should be safe to re-edit 0.40 ba
use_nls=no
if test "x$enable_nls" = "xyes" ; then
use_nls=yes
-m4_ifdef([IT_PROG_INTLTOOL],
- [IT_PROG_INTLTOOL([0.35.0],[no-xml])],
- [AC_MSG_ERROR("--enable-nls requires intltool to be installed.")])
+IT_PROG_INTLTOOL([0.35.0],[no-xml])
AC_CHECK_HEADERS([libintl.h])
GETTEXT_PACKAGE=transmission-gtk
AC_SUBST(GETTEXT_PACKAGE)
Bug#998571: marked as done (image-factory: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2)
Your message dated Fri, 12 Nov 2021 16:18:33 +
with message-id
and subject line Bug#998571: fixed in image-factory 1.0.2-1
has caused the Debian Bug report #998571,
regarding image-factory: FTBFS: dh_auto_test: error: make -j4 check returned
exit code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
998571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: image-factory
Version: 1.0.1-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):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_empty_config (tests.test_cli.TestCLI)
> Test empty configuration file. ... ok
> test_example_config (tests.test_cli.TestCLI)
> Test exapmle image-factory.conf file. ... ok
> test_override_cache_dir (tests.test_cli.TestCLI)
> Test overriding the cache directory. ... ok
> test_flake8 (tests.test_flake8.Flake8TestCase)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3 -m flake8 --max-line-length=99 image-factory tests
> ok
> test_invalid (tests.test_helper.TestParseBytes)
> Test parse_bytes("invalid") ... ok
> test_parse_1_g (tests.test_helper.TestParseBytes)
> Test parse_bytes("1G") ... ok
> test_parse_2_tb (tests.test_helper.TestParseBytes)
> Test parse_bytes("2 TB") ... ok
> test_parse_512_mib (tests.test_helper.TestParseBytes)
> Test parse_bytes("512 MiB") ... ok
> test_pylint (tests.test_pylint.PylintTestCase)
> Test: Run pylint on Python source code. ... Running following command:
> /usr/bin/python3 -m pylint --rcfile=/<>/tests/pylint.conf --
> image-factory tests
> FAIL
> test_chmod_dnf_log (tests.test_sudo_helper.TestSudoHelper)
> Test read access for dnf log file. ... ok
> test_chmod_log_file (tests.test_sudo_helper.TestSudoHelper)
> Test read access for mounted /var/log/... ... ok
> test_chmod_recursive (tests.test_sudo_helper.TestSudoHelper)
> Test chmod recursively ... ok
> test_chmod_remove_root (tests.test_sudo_helper.TestSudoHelper)
> Test chmod remove mounted /root permission ... ok
> test_chmod_root (tests.test_sudo_helper.TestSudoHelper)
> Test chmod mounted /root ... ok
> test_chmod_var_log (tests.test_sudo_helper.TestSudoHelper)
> Test write access for mounted /var/log/... ... ok
> test_mount (tests.test_sudo_helper.TestSudoHelper)
> Test mounting. ... ok
> test_reject_escaping (tests.test_sudo_helper.TestSudoHelper)
> Test rejecting ../../etc/shadow. ... ok
> test_umount (tests.test_sudo_helper.TestSudoHelper)
> Test unmounting. ... ok
>
> ==
> FAIL: test_pylint (tests.test_pylint.PylintTestCase)
> Test: Run pylint on Python source code.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_pylint.py", line 76, in test_pylint
> self.fail("\n".join(msgs))
> AssertionError: pylint found issues:
> * Module image-factory
> image-factory:139:24: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:133:22: R1732: Consider using 'with' for resource-allocating
> operations (consider-using-with)
> image-factory:168:24: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:162:22: R1732: Consider using 'with' for resource-allocating
> operations (consider-using-with)
> image-factory:180:18: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:199:12: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:234:19: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:239:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:242:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:243:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:246:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:255:19: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:257:24: C0209: Formatting a
Processed: sword-comm-tdavid: Source available
Processing control commands: > forwarded -1 https://gitlab.com/crosswire-bible-society/tdavid Bug #984608 [sword-comm-tdavid] sword-comm-tdavid: Missing source Changed Bug forwarded-to-address to 'https://gitlab.com/crosswire-bible-society/tdavid' from 'https://tracker.crosswire.org/browse/MOD-404'. -- 984608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984608: sword-comm-tdavid: Source available
Control: forwarded -1 https://gitlab.com/crosswire-bible-society/tdavid
Bug#998544: marked as done (golang-github-go-playground-validator-v10: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 [...] returned exit code 1)
Your message dated Sat, 13 Nov 2021 00:36:26 +0800 with message-id and subject line Re: Bug#998544: golang-github-go-playground-validator-v10: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 [...] returned exit code 1 has caused the Debian Bug report #998544, regarding golang-github-go-playground-validator-v10: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 [...] returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-go-playground-validator-v10 Version: 10.4.1-2 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 binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 4 > github.com/go-playground/validator/v10 > github.com/go-playground/validator/v10/non-standard/validators > github.com/go-playground/validator/v10/translations/en > github.com/go-playground/validator/v10/translations/es > github.com/go-playground/validator/v10/translations/fr > github.com/go-playground/validator/v10/translations/id > github.com/go-playground/validator/v10/translations/ja > github.com/go-playground/validator/v10/translations/nl > github.com/go-playground/validator/v10/translations/pt > github.com/go-playground/validator/v10/translations/pt_BR > github.com/go-playground/validator/v10/translations/ru > github.com/go-playground/validator/v10/translations/tr > github.com/go-playground/validator/v10/translations/zh > github.com/go-playground/validator/v10/translations/zh_tw > internal/goexperiment > internal/unsafeheader > internal/cpu > runtime/internal/atomic > internal/abi > runtime/internal/sys > runtime/internal/math > internal/race > sync/atomic > unicode > unicode/utf8 > internal/bytealg > internal/itoa > math/bits > encoding > unicode/utf16 > math > github.com/go-playground/locales/currency > internal/nettrace > runtime > internal/reflectlite > sync > internal/testlog > internal/singleflight > runtime/cgo > errors > sort > io > internal/oserror > syscall > strconv > bytes > hash > reflect > crypto > path > strings > time > internal/syscall/unix > internal/syscall/execenv > vendor/golang.org/x/net/dns/dnsmessage > context > internal/poll > io/fs > github.com/go-playground/locales > regexp/syntax > os > internal/fmtsort > encoding/binary > encoding/base64 > crypto/sha256 > golang.org/x/crypto/sha3 > regexp > fmt > io/ioutil > path/filepath > net > encoding/hex > net/url > encoding/json > log > github.com/go-playground/universal-translator > github.com/leodido/go-urn > github.com/go-playground/validator/v10 > github.com/go-playground/validator/v10/non-standard/validators > github.com/go-playground/validator/v10/translations/en > github.com/go-playground/validator/v10/translations/fr > github.com/go-playground/validator/v10/translations/es > github.com/go-playground/validator/v10/translations/id > github.com/go-playground/validator/v10/translations/ja > github.com/go-playground/validator/v10/translations/nl > github.com/go-playground/validator/v10/translations/pt > github.com/go-playground/validator/v10/translations/pt_BR > github.com/go-playground/validator/v10/translations/ru > github.com/go-playground/validator/v10/translations/tr > github.com/go-playground/validator/v10/translations/zh > github.com/go-playground/validator/v10/translations/zh_tw >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 4 > github.com/go-playground/validator/v10 > github.com/go-playground/validator/v10/non-standard/validators > github.com/go-playground/validator/v10/translations/en > github.com/go-playground/validator/v10/translations/es > github.com/go-playground/validator/v10/translations/fr > github.com/go-playground/validator/v10/translations/id > github.com/go-playground/validator/v10/translations/ja > github.com/go-playground/validator/v10/translations/nl > github.com/go-playground/validator/v10/tr
Bug#998240: texlive: causes lgrind to FTBFS
Am 01.11.2021 um 14:32 teilte Andreas Beckmann mit:
Hi,
The offending line + some context:
537 % The meta-symbols and their meanings are:
538 % \begin{description}
539 % \item[\$] The end of a line
540 % \item[\^] The beginning of a line
541 % \item[$\backslash$d] A delimiter (space, tab, newline, start of line)
542 % \item[$\backslash$a] Matches any string of symbols (like `.*' in lex)
543 % \item[$\backslash$p] Matches any identifier. In a procedure definition
Replacing the "\item[\^]" by "\item[\^{}]" solved the issue for me. I
guess I don't need to create a patch / pull request for this. ;-)
Hilmar
--
sigfault
OpenPGP_signature
Description: OpenPGP digital signature
Bug#988462: Thank you
Ah, thank you, that's very helpful - I will try nspawn or docker. I look forward to 1.6 in Debian 12! Chris
Processed: tagging 996483
Processing commands for cont...@bugs.debian.org: > tags 996483 + pending Bug #996483 [src:mp3blaster] mp3blaster FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999575: elan: error: failed to select a version for the requirement `itertools = "^0.9.0"`
Source: elan
Version: 1.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j4',
'--target', 'x86_64-unknown-linux-gnu'],) {}
| error: failed to select a version for the requirement `itertools = "^0.9.0"`
| candidate versions found which didn't match: 0.10.1
| location searched: directory source `/<>/debian/cargo_registry`
(which is replacing registry `crates-io`)
| required by package `elan v1.0.6 (/<>)`
| perhaps a crate was updated and forgotten to be re-vendored?
| dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
| make: *** [debian/rules:19: binary-arch] Error 25
https://buildd.debian.org/status/fetch.php?pkg=elan&arch=amd64&ver=1.0.6-1%2Bb1&stamp=1636717403&raw=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#998903: src:libidn: fails to migrate to testing for too long
Hi Simon, On 11-11-2021 22:52, Simon Josefsson wrote: James, let us drop building jxmpp-stringprep-libidn for now and drop dependency on libidn11-java. Sounds great, please upload to unstable -- let me know if eventually there is demand for libidn11-java, otherwise let's hope it can finally be removed as cruft. Pending the removal, I'll ensure again that libidn migrates if all else remains OK the moment I tend to it (which should be real soon). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#996483: marked as done (mp3blaster FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Fri, 12 Nov 2021 19:19:25 + with message-id and subject line Bug#996483: fixed in mp3blaster 1:3.2.6-3 has caused the Debian Bug report #996483, regarding mp3blaster FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp3blaster Version: 1:3.2.6-2 Severity: serious Tags: ftbfs mp3blaster fails to build from source in unstable due to ncurses having gained format string annotations. A non-parallel build now ends as follows: | g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/ncurses -I. -I/usr/include -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++98 -c -o nullmixer.o nullmixer.cc | nmixer.cc: In member function ‘void NMixer::DrawScrollbar(short int, int)’: | nmixer.cc:219:26: error: format not a string literal and no format arguments [-Werror=format-security] | 219 | mvwprintw(mixwin, my_y - 1, my_x, (char*)source); | | ~^~~ | cc1plus: some warnings being treated as errors | make[3]: *** [Makefile:445: nmixer.o] Error 1 | make[3]: Leaving directory '/<>/nmixer' | make[2]: *** [Makefile:457: all-recursive] Error 1 | make[2]: Leaving directory '/<>' | make[1]: *** [Makefile:355: all] Error 2 | make[1]: Leaving directory '/<>' | dh_auto_build: error: make -j8 returned exit code 2 | make: *** [debian/rules:9: binary] Error 25 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: mp3blaster Source-Version: 1:3.2.6-3 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of mp3blaster, 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. Adrian Bunk (supplier of updated mp3blaster 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: Fri, 12 Nov 2021 20:21:45 +0200 Source: mp3blaster Architecture: source Version: 1:3.2.6-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 996483 Changes: mp3blaster (1:3.2.6-3) unstable; urgency=medium . * QA upload. * Fix FTBFS with new ncurses. (Closes: #996483) Checksums-Sha1: cce05ffec5456498eaa5bda713fe6bbc9beb5228 1955 mp3blaster_3.2.6-3.dsc d40399e35ea472026ea18066d8c5938cbd43ff06 6948 mp3blaster_3.2.6-3.debian.tar.xz Checksums-Sha256: c66287457424d0914d4850dd9fbb362b8cb774320e669b612b6c08cdd00c7a5e 1955 mp3blaster_3.2.6-3.dsc b8b4259b521fd40e8845df69b42f04614422c2a256de6b86be1994378f32b2f1 6948 mp3blaster_3.2.6-3.debian.tar.xz Files: cecf5f264567e8f358919563e544ef93 1955 sound optional mp3blaster_3.2.6-3.dsc 750d2f306ae162be2814804ca1d5ce5b 6948 sound optional mp3blaster_3.2.6-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGOuOsACgkQiNJCh6LY mLFPQBAAjbpD88ZykLksQ7ZUPivXp03Mq8YxOdVeKiFolj5uKDiPhSN+wRvGIKEJ JBr+vAOn8/K5azWm7rL0jNhqh2QrlQncGNO5CTt8nyxf/27dO7KHAs+s3/4J9TV+ xK0yolFiPOCjTpVOT2QBGdYIBALmryN8aLuijzCVw/WXQ4htrbpSp8x9oGwCU3sm +csqWoy7DzdJH5XryjMUN9Yn2ED0qayk9IS8piKwTOUxO8+JHh2bJeo5f5XzWeom anEG2nEzxuPGAN8yLMglYuBt7hgkmNZUKK3GnBzN+rLutOs9GMdtFeTl2ttNxyL6 VNZ1KIFzG+8MCmfAOCDkgrKTkI75gg5JJluSJsFMxtVHb+F1h8Xkc7S9GtI2vGOi eB+iG8+EYRDM5704no4k9ySvwXSavQdkQvAgjMQZLjPh4L3+w3fCnw3FYfvzSUJY tFYrgPwkMerzSxoDwn5XydQIrexJyXi/Pns01N/nboMolCbOQuOpSsfHfkOiVoa4 IF1Vyjo0L+QLZ0Ieg7qWm2K4rMgJ6Xri0OcZCgfIx0b9snQGlgNNFBHP+zUtjgZK kMsb5e7LqNarEdq+Zu8dvlutvPaZDXzF+8BorZdLEFa0yQYYRmFQN8aP3KeaBy7W DbIx0KJoIXQBnVpG+hYe86g7aWo9hPjg4NOoK0p3yWWe+1j+LZY= =n1Lw -END PGP SIGNATURE End Message ---
Bug#999481: marked as done (symbols files need updates for various architectures)
Your message dated Fri, 12 Nov 2021 19:49:12 + with message-id and subject line Bug#999481: fixed in mrgingham 1.20-2 has caused the Debian Bug report #999481, regarding symbols files need updates for various architectures 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.) -- 999481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrgingham Version: 1.20-1 Severity: serious Tags: sid bookworm See https://buildd.debian.org/status/package.php?p=mrgingham the symbols file is not ready for the release architectures. --- End Message --- --- Begin Message --- Source: mrgingham Source-Version: 1.20-2 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of mrgingham, 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. Dima Kogan (supplier of updated mrgingham 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: Fri, 12 Nov 2021 11:24:35 -0800 Source: mrgingham Architecture: source Version: 1.20-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Closes: 999481 Changes: mrgingham (1.20-2) unstable; urgency=medium . * Removed the symbols file. Bug fix: "symbols files need updates for various architectures", thanks to Matthias Klose (Closes: #999481). Checksums-Sha1: 5db3f38c69561e65029286e82782df78da816d01 2271 mrgingham_1.20-2.dsc 1b7c87a02e4a4b0fc744b9c7b53fa1686761219a 2928 mrgingham_1.20-2.debian.tar.xz 23af1523ecc5df403780a538a84f4f2a0a58037e 19268 mrgingham_1.20-2_amd64.buildinfo Checksums-Sha256: c775e424f512dabdd164f2c6f12ebbcff4648c0ea39fb64358a0cdcce337d35e 2271 mrgingham_1.20-2.dsc 05cf5edaff00ca3f67c588a8e30174250870768398ebb89f26e88944204e0d03 2928 mrgingham_1.20-2.debian.tar.xz fdb08d1565b51f26f49bbd0d68ff932260a4ae241ba4ad5104e3bccd71305c1f 19268 mrgingham_1.20-2_amd64.buildinfo Files: 987ae9e6cf91a7d676b7f76168540502 2271 devel optional mrgingham_1.20-2.dsc 25ca72a60ba1317fbbdc0f7193a5df49 2928 devel optional mrgingham_1.20-2.debian.tar.xz 3e9faa3c7f9a3cf303ec3a4617c1b704 19268 devel optional mrgingham_1.20-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmGOwVIACgkQrMfCzzCU EYhqUhAAhcvwtnYxeS6hn5NvRotgKFPE13MgouycrL5lzJM+99gFbLLf0jdVHMBi Vg7CPsfhIwk6/8UUk3Jqz9Y3rKQ8vN7rnjMN08V41UPL6o7ucG6ZA5/Cwh1D9xax ruKqXbWZdfOP7ZK3nO6XJtsTRfmJ4S+F1Zmn4DsszvT8dhPxKwaBt7cCQuYK/kOi njcnAVNtChduQpjsPslH5EZZdQqeXjnsiJkQeXTtaiht0lF0RVOHziwAtNg2XtMR 2MIOocBzr3XstSmGOBY/c0yku7qlMGfI6sAsDZt4XlU+Ety0YKtA2TkarbB/hgJD uW+sxqPJb7jjZRELauviaV+rSfWn1LmSmZoTMdZYULapuFzLDN4bAqGRyJoIVSt/ 0uw1oVinW0G727ZSbVwg1mXW4qVjOohC5fZyZs+WF2fqJglOYLHkiUXlonzosqvn +ELyx/+ip9FonilYBUVaDLNkt/C8PF34u6PusW2Cwf+uK+kwnd1j71ml6qqoqjXu xgdtp0vYpVDnSxUOjQc/qoLS7m1g265jYP2XWdHn7oOy5ES0n3pmCzcLNEeHi7+a eRWph33JbmXOjfGYlKEBi3m5nM05UFxLuYKtYTZsWkDIIZvGjPZsRdGtjEmuK/8v b3d9m/KaoZrPrvhJ13T55dRxdonnRsDm04+X5FpnN5YtPIw9WuM= =nPI+ -END PGP SIGNATURE End Message ---
Processed: src:libcache-memcached-fast-perl: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.27-3
Bug #999580 [src:libcache-memcached-fast-perl]
src:libcache-memcached-fast-perl: fails to migrate to testing for too long:
autopkgtest regression
Marked as fixed in versions libcache-memcached-fast-perl/0.27-3.
Bug #999580 [src:libcache-memcached-fast-perl]
src:libcache-memcached-fast-perl: fails to migrate to testing for too long:
autopkgtest regression
Marked Bug as done
> block -1 by 996712
Bug #999580 {Done: Paul Gevers }
[src:libcache-memcached-fast-perl] src:libcache-memcached-fast-perl: fails to
migrate to testing for too long: autopkgtest regression
999580 was not blocked by any bugs.
999580 was not blocking any bugs.
Added blocking bug(s) of 999580: 996712
--
999580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999581: src:dbab: fails to migrate to testing for too long: unresolved RC bug
Source: dbab Version: 1.5.01-1 Severity: serious Control: close -1 1.5.7-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 995769 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:dbab has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=dbab OpenPGP_signature Description: OpenPGP digital signature
Processed: src:dbab: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 1.5.7-1
Bug #999581 [src:dbab] src:dbab: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions dbab/1.5.7-1.
Bug #999581 [src:dbab] src:dbab: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 995769
Bug #999581 {Done: Paul Gevers } [src:dbab] src:dbab: fails
to migrate to testing for too long: unresolved RC bug
999581 was not blocked by any bugs.
999581 was not blocking any bugs.
Added blocking bug(s) of 999581: 995769
--
999581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999580: src:libcache-memcached-fast-perl: fails to migrate to testing for too long: autopkgtest regression
Source: libcache-memcached-fast-perl Version: 0.25-1 Severity: serious Control: close -1 0.27-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 996712 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:libcache-memcached-fast-perl has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=libcache-memcached-fast-perl OpenPGP_signature Description: OpenPGP digital signature
Processed: block 984371 with 998836
Processing commands for cont...@bugs.debian.org:
> block 984371 with 998836
Bug #984371 {Done: Adrian Bunk } [src:trafficserver]
trafficserver: ftbfs with GCC-11
984371 was not blocked by any bugs.
984371 was not blocking any bugs.
Added blocking bug(s) of 984371: 998836
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#997743 marked as pending in spatial4j
Processing control commands: > tag -1 pending Bug #997743 [src:spatial4j] spatial4j: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: Compilation failure: Added tag(s) pending. -- 997743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997743: marked as pending in spatial4j
Control: tag -1 pending Hello, Bug #997743 in spatial4j reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/spatial4j/-/commit/552ffe1d052e8df20bd098bdb5bd6e215a565a80 Fix incompatibilitiy with latest version of libjts-java. Closes: #997743 (this message was generated automatically) -- Greetings https://bugs.debian.org/997743
Bug#997743: marked as done (spatial4j: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: C
Your message dated Fri, 12 Nov 2021 21:33:54 + with message-id and subject line Bug#997743: fixed in spatial4j 0.8-1 has caused the Debian Bug report #997743, regarding spatial4j: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: Compilation failure: 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.) -- 997743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spatial4j Version: 0.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package spatial4j > dpkg-buildpackage: info: source version 0.7-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by tony mancill > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean > bash -c "for dir in \$(find . -name target -type d); do if [ -f \$(echo > \$dir | sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done" > mh_unpatchpoms -plibspatial4j-java >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building spatial4j using existing > ./spatial4j_0.7.orig.tar.gz > dpkg-source: info: building spatial4j in spatial4j_0.7-1.debian.tar.xz > dpkg-source: info: building spatial4j in spatial4j_0.7-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibspatial4j-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /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 > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project org.locationtech.spatial4j:spatial4j:bundle:0.7 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] < org.locationtech.spatial4j:spatial4j > > > [INFO] Building Spatial4J 0.7 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- replacer:1.5.3:replace (process-packageVersion) @ spatial4j --- > [INFO] Replacement run on 1 file. > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > spatial4j --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ spatial4j > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 72 source files to /<>/target/classes > [INFO] > /<>/src/main/java/org/locationtech/spatial4j/context/SpatialContextFactory.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/org/locationtech/spatial4j/context/SpatialContextFactory.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] bootstrap class path not set in conjunction with -source 7 > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/shape/jts/JtsShapeFactory.java:[23,38] > org.locationtech.jts.algorithm.CGAlgorithms in > org.locationtech.jts.algorithm has been deprecated > [WARNING] > /<>/src/main/java/org/locationtech/spatial4j/io/jts/JtsGeoJSONWriter.java:[17,37] > org.locationtech.spatial4j.io.LegacyShapeWriter in > org.locationtech.spatial4j.io has
Processed: Bug#997782 marked as pending in spatial4j-0.4
Processing control commands: > tag -1 pending Bug #997782 [src:spatial4j-0.4] spatial4j-0.4: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: Compilation failure: Added tag(s) pending. -- 997782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997782: marked as pending in spatial4j-0.4
Control: tag -1 pending Hello, Bug #997782 in spatial4j-0.4 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/spatial4j-0.4/-/commit/835ef28a62010c04dba7ff7765a7dc255f9bf901 Fix FTBFS with jts 18.1. Closes: #997782 (this message was generated automatically) -- Greetings https://bugs.debian.org/997782
Bug#995655: marked as done (dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143)
Your message dated Fri, 12 Nov 2021 21:48:34 + with message-id and subject line Bug#995655: fixed in dnsmasq 2.86-1.1 has caused the Debian Bug report #995655, regarding dnsmasq breaks systemd autopkgtest: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143 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.) -- 995655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dnsmasq, systemd Control: found -1 dnsmasq/2.86-1 Control: found -1 systemd/247.9-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of dnsmasq the autopkgtest of systemd fails in testing when that autopkgtest is run with the binary packages of dnsmasq from unstable. It passes when run with only packages from testing. In tabular form: passfail dnsmasqfrom testing2.86-1 systemdfrom testing247.9-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 dnsmasq to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from dnsmasq/2.86-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=dnsmasq https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemd/15711756/log.gz == FAIL: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.re_u3b37/downtmp/build.aCg/src/test/networkd-test.py", line 660, in test_resolved_domain_restricted_dns self.assertIn(b'megasearch.net: 192.168.42.1', out) AssertionError: b'megasearch.net: 192.168.42.1' not found in b'megasearch.net: 207.148.248.143 -- link: eth0\n\n-- Information acquired via protocol DNS in 123.2ms.\n-- Data is authenticated: no\n' -- OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: dnsmasq Source-Version: 2.86-1.1 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of dnsmasq, 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. Michael Biebl (supplier of updated dnsmasq package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Nov 2021 22:05:45 +0100 Source: dnsmasq Architecture: source Version: 2.86-1.1 Distribution: unstable Urgency: medium Maintainer: Simon Kelley Changed-By: Michael Biebl Closes: 995655 Changes: dnsmasq (2.86-1.1) unstable; urgency=medium . * Non-maintainer upload. * Fix --address=/#/.. which was lost in 2.86. (closes: #995655) Checksums-Sha1: 1dd8bb749e3358aca290784467bff909e8f7268a 2200 dnsmasq_2.86-1.1.dsc 5558227b28f578effd7adeacc6de6ede418c650a 27173 dnsmasq_2.86-1.1.diff.gz c190d60ce8fd3e0b9e2e583808fcdae6e022f05c 5902 dnsmasq_2.86-1.1_source.buildinfo Checksums-Sha256: 0e29e86b6d481c7b560cf1343e392763f2f98a9eeacaaf24dde40f7b606deb3d 2200 dnsmasq_2.86-1.1.dsc c0b7f21629c103820ab0e498ba40ab93372fbbc2dcf7ac1551187176b7a703f5 27173 dnsmasq_2.86-1.1.diff.gz e4627d44db69ee0cc8df86e4870937fc3bde090182a6d6136292ffd844
Bug#998032: marked as done (src:breezy-debian: fails to migrate to testing for too long: uploader built arch:all binaries (and blocked by breezy))
Your message dated Fri, 12 Nov 2021 21:48:28 + with message-id and subject line Bug#998032: fixed in breezy-debian 2.8.63+nmu1 has caused the Debian Bug report #998032, regarding src:breezy-debian: fails to migrate to testing for too long: uploader built arch:all binaries (and blocked by breezy) 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.) -- 998032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breezy-debian Version: 2.8.51 Severity: serious Control: close -1 2.8.63 Tags: sid bookworm pending 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:breezy-debian has been trying to migrate for 237 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. I just filed an RC bug against breezy, which also needs to be fixed for breezy-debian to migrate. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=breezy-debian OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: breezy-debian Source-Version: 2.8.63+nmu1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of breezy-debian, 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. Paul Gevers (supplier of updated breezy-debian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 28 Oct 2021 22:46:07 +0200 Source: breezy-debian Architecture: source Version: 2.8.63+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Bazaar Maintainers Changed-By: Paul Gevers Closes: 998032 Changes: breezy-debian (2.8.63+nmu1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #998032) Checksums-Sha1: f97069be51981783c5ad16e45a5fa0faa1156245 1979 breezy-debian_2.8.63+nmu1.dsc 8307548979e5ec8c452103ff87ed02baa78363c3 166864 breezy-debian_2.8.63+nmu1.tar.xz Checksums-Sha256: 49ef063c77b321b6b490bb7ae4114b138d917a18babeb153528c8906c72ba73c 1979 breezy-debian_2.8.63+nmu1.dsc c60edf7576df3425311b481f20a993ac5aed03f5863b7b5475f21a6a3b93187b 166864 breezy-debian_2.8.63+nmu1.tar.xz Files: b7e2c35b4acb03d812e263f3066a264e 1979 vcs optional breezy-debian_2.8.63+nmu1.dsc edd823c88d2412e77146e3b3e55d5d32 166864 vcs optional breezy-debian_2.8.63+nmu1.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmF7DC0ACgkQnFyZ6wW9 dQrNSggAsn9aMiE2IIhgMRGxXr2uftv3jpcRNVYuEUhfm9YMxphanVV3F2oa7nBo 1Prz8ha/06E6Rqh080kuALkh8kaeNJeb/tsuOlNsirESnO3kYXWjOcTT0t5GI53D qut0+F6jGUVr1OZnAr6BlmOMCDHb8eGJDplYHPOWhIVGQyf7N9xmCgBQ4bl5Rt8o PasOP
Bug#984608: marked as done (sword-comm-tdavid: Missing source)
Your message dated Fri, 12 Nov 2021 22:06:53 + with message-id and subject line Bug#984608: fixed in sword-comm-tdavid 2.0-1 has caused the Debian Bug report #984608, regarding sword-comm-tdavid: Missing source 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.) -- 984608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sword-comm-tdavid Severity: serious Control: forwarded https://tracker.crosswire.org/browse/MOD-404 sword-comm-tdavid is missing source. The suggested decompression commands in debian/copyright will not give the original source because the translation process is lossy. I suggest to move the package to non-free or to remove it. --- End Message --- --- Begin Message --- Source: sword-comm-tdavid Source-Version: 2.0-1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of sword-comm-tdavid, 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 984...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated sword-comm-tdavid 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: Fri, 12 Nov 2021 22:40:54 +0100 Source: sword-comm-tdavid Architecture: source Version: 2.0-1 Distribution: unstable Urgency: low Maintainer: CrossWire Packaging Team Changed-By: Bastian Germann Closes: 984608 Changes: sword-comm-tdavid (2.0-1) unstable; urgency=low . * Team upload. * New upstream version 2.0. * Build from source (Closes: #984608) * d/copyright: Convert to Format 1.0 * Address silent-on-rules-requiring-root * Remove debian/source/options . [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from deprecated 9 to 13. * Set debhelper-compat version in Build-Depends. * Use secure URI in Homepage field. Checksums-Sha1: 38e692e62a359ec69304ec41eda35386747f730e 1976 sword-comm-tdavid_2.0-1.dsc a039cca4c145779efca30f9dc265fdfba5071d56 4120161 sword-comm-tdavid_2.0.orig.tar.gz b65f84ada2f99cf93aec6731d36b169685117e70 2540 sword-comm-tdavid_2.0-1.debian.tar.xz c1d354550ead8cf30f5924dee59c670d00e3e48a 5857 sword-comm-tdavid_2.0-1_source.buildinfo Checksums-Sha256: 33137dce17f30d644e9ae6b44fe0e397a286e9d7bccc77723ce07cee79b00503 1976 sword-comm-tdavid_2.0-1.dsc a34abffe28112374f4bd46532b13c196e27229e8978110e82155ffe195d29d94 4120161 sword-comm-tdavid_2.0.orig.tar.gz ca5cd75d227c86aafec39117ddbca2e03057f7ba453eba43ec989754c4f71ca7 2540 sword-comm-tdavid_2.0-1.debian.tar.xz 3c061bec30f51f4ff5ce340ce20ee4f221cdedb08215af67b423d8af6074ae46 5857 sword-comm-tdavid_2.0-1_source.buildinfo Files: e1bf08f20c771a2c78a121d365da6860 1976 text optional sword-comm-tdavid_2.0-1.dsc 4beff1a2702c5ab56f963edc620978fd 4120161 text optional sword-comm-tdavid_2.0.orig.tar.gz 7ceaae657c8e2570a0c71a22e9498082 2540 text optional sword-comm-tdavid_2.0-1.debian.tar.xz abfc490aa7461431722f8c6620dfa34d 5857 text optional sword-comm-tdavid_2.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmGO4AMACgkQH1x6i0VW QxQeaQv/STjDDHXHYFBOuZ75E1ohN18zxJ8zv+IeoPNMMkfR/2dvMQSmBlyYhWaJ /O8erhg7bp2btXoqD1YdZz0ymdTJ+lSh2tgd0/48lWHDz5uaCDYqLAcCWyHfhnN9 BN5WSKwM3TTOncsz0K8BaoE7PaCyOffbnds5kMg+0MtX73FFQtcXJgsbtEL4j7dX kIb6CsLMFFU0W3THjh3VrHaZo0IvJsALYVQqQMatr2ux6//lwRlbupByEQyxWKfq 56gsCW45dUNjxXcwYYTbxbo8nivKO2wVNd5HgDjcLrra2212Iys5paiNkvDTvNCw jwI5a/udztBseg8xSQ/EkP3im3KpuTIRMZpXatf46GQ0rPZzRA8qHqCXp/v8xR0E 2d9QMtgff66sexCQgqsBWo6EURy1kgIv/PqYnpquDXJ5DCgkyaQSppN746T7SiXO oTG7oAcOTk9/L0Y7pty14s3hIlxx5ttbWgcCFkJg7l+WkYwxBJAeKRWirMixeqIa F56rz+XP =Xn2A -END PGP SIGNATURE End Message ---
Bug#997782: marked as done (spatial4j-0.4: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failur
Your message dated Fri, 12 Nov 2021 22:06:46 + with message-id and subject line Bug#997782: fixed in spatial4j-0.4 0.4.1-7 has caused the Debian Bug report #997782, regarding spatial4j-0.4: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project spatial4j: Compilation failure: Compilation failure: 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.) -- 997782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spatial4j-0.4 Version: 0.4.1-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > 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 -plibspatial4j-0.4-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 > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project com.spatial4j:spatial4j:bundle:0.4.1 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] --< com.spatial4j:spatial4j > >--- > [INFO] Building Spatial4J 0.4.1 > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > spatial4j --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /<>/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ spatial4j > --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 39 source files to /<>/target/classes > Use of target 1.6 is no longer supported, switching to 7 > Use of source 1.6 is no longer supported, switching to 7 > [INFO] > /<>/src/main/java/com/spatial4j/core/io/WktShapeParser.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/com/spatial4j/core/io/WktShapeParser.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [WARNING] COMPILATION WARNING : > [INFO] - > [WARNING] bootstrap class path not set in conjunction with -source 7 > [WARNING] > /<>/src/main/java/com/spatial4j/core/io/jts/JtsWktShapeParser.java:[27,38] > org.locationtech.jts.algorithm.CGAlgorithms in > org.locationtech.jts.algorithm has been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/context/SpatialContextFactory.java:[96,45] > newInstance() in java.lang.Class has been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/context/SpatialContextFactory.java:[184,34] > readShape(java.lang.String) in com.spatial4j.core.context.SpatialContext has > been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/context/jts/JtsSpatialContext.java:[92,17] > toString(com.spatial4j.core.shape.Shape) in > com.spatial4j.core.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/context/jts/JtsSpatialContext.java:[99,17] > toString(com.spatial4j.core.shape.Shape) in > com.spatial4j.core.context.SpatialContext has been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/io/jts/JtsWktShapeParser.java:[143,29] > org.locationtech.jts.algorithm.CGAlgorithms in > org.locationtech.jts.algorithm has been deprecated > [WARNING] > /<>/src/main/java/com/spatial4j/core/io/jts/JtsWktShapeParser.java:[143,41] > isCCW(org.locationtech.jts.
Bug#996322: marked as pending in ruby-mmap2
Control: tag -1 pending Hello, Bug #996322 in ruby-mmap2 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-mmap2/-/commit/ded5a06ae7e6a1b63dac2434f111e9592ad35550 Add patch to fix FTBFS with Ruby 3.0 * d/patches/996322-fix-ruby3-compat.patch: Add patch. - Drop rb_secure() and rb_safe_level() in Ruby 3 (Closes: #996322). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996322
Processed: Bug#996322 marked as pending in ruby-mmap2
Processing control commands: > tag -1 pending Bug #996322 [src:ruby-mmap2] ruby-mmap2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file -- mmap (LoadError) Added tag(s) pending. -- 996322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996322: marked as done (ruby-mmap2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such fil
Your message dated Fri, 12 Nov 2021 23:04:29 +
with message-id
and subject line Bug#996322: fixed in ruby-mmap2 2.2.7-2
has caused the Debian Bug report #996322,
regarding ruby-mmap2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
:85:in
`require': cannot load such file -- mmap (LoadError)
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.)
--
996322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mmap2
Version: 2.2.7-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-mmap2 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):
> :85:in
> `require': cannot load such file -- mmap (LoadError)
> from
> :85:in
> `require'
> from /<>/test/test_mmap.rb:1:in `'
> from
> :85:in
> `require'
> from
> :85:in
> `require'
> from
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in
> `block in '
> from
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in
> `select'
> from
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in
> `'
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
> "test/test_mmap.rb" -v]
>
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mmap2/ruby-mmap2_2.2.7-1+rebuild1633387115_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-mmap2
Source-Version: 2.2.7-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-mmap2, 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-mmap2 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: Fri, 12 Nov 2021 23:36:47 +0100
Source: ruby-mmap2
Architecture: source
Version: 2.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996322
Changes:
ruby-mmap2 (2.2.7-2) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Use secure copyright file specification URI.
* debian/copyright: use spaces rather than tabs to start continuation
lines.
* Use secure URI in debian/watch.
* Bump debhelper from old 10 to 13.
* Set debhelper-compat version in Build-Depends.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Apply multi-arch hints.
+ ruby-mmap2: Add Multi-Arch: same.
* Update watch file format version to 4.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Homepage): Update URL.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Source): Update URL.
* d/ruby-tests.rake: Only run tests outside autopkgtest.
* d/watch: Use gemwatch URL.
* d/patches/996322-fix-ruby3-compat.patch: Add patch.
- Drop rb_secure() and rb_safe_level() in Ruby 3 (Closes: #996322).
* d/patches/series: Enable new patch.
Checksums-Sha1:
da4077e5c6f3ca56590b28009c553f5134712ed8 1997 ruby-mmap2_2.2.7-2.dsc
30ceafe2d14096fdab0bf6f14f33a16724fece12 4120 ruby-mmap2_2.2.7-2.debian.tar.xz
011245bd9c82ad1951495a78f63817e48a037599 9383
ruby-mmap2_2.2.7-2_amd64.buildinfo
Checksums-Sha256:
e1af12df6627d47ce34d5150edb6536c065fc108b02263f5cae8810637d2d74e 1997
ruby-mmap2_2.2.7-2.dsc
9a4801842769f139b1675106978e59b03febfae32e9785ae9abb6096fa369307 4120
ruby-mmap2_2.2.7-2.debian.t
Bug#995742: ddnet: diff for NMU version 15.5.4-1.1
Control: tags 995742 + patch Control: tags 995742 + pending Dear maintainer, I've prepared an NMU for ddnet (versioned as 15.5.4-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru ddnet-15.5.4/debian/changelog ddnet-15.5.4/debian/changelog --- ddnet-15.5.4/debian/changelog 2021-09-30 06:45:10.0 +0300 +++ ddnet-15.5.4/debian/changelog 2021-11-12 21:45:34.0 +0200 @@ -1,3 +1,11 @@ +ddnet (15.5.4-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Allow stderr in autopkgtest for gcc warnings on some architectures. +(Closes: #995742) + + -- Adrian Bunk Fri, 12 Nov 2021 21:45:34 +0200 + ddnet (15.5.4-1) unstable; urgency=medium * New upstream release diff -Nru ddnet-15.5.4/debian/tests/control ddnet-15.5.4/debian/tests/control --- ddnet-15.5.4/debian/tests/control 2021-09-30 06:45:10.0 +0300 +++ ddnet-15.5.4/debian/tests/control 2021-11-12 21:45:31.0 +0200 @@ -1,2 +1,3 @@ Tests: unittest.sh Depends: @builddeps@ +Restrictions: allow-stderr
Processed: ddnet: diff for NMU version 15.5.4-1.1
Processing control commands: > tags 995742 + patch Bug #995742 [src:ddnet] ddnet armhf autopkgtest regression due to compiler warning Bug #997802 [src:ddnet] ddnet: autopkgtest regression on armhf: output to stderr Added tag(s) patch. Added tag(s) patch. > tags 995742 + pending Bug #995742 [src:ddnet] ddnet armhf autopkgtest regression due to compiler warning Bug #997802 [src:ddnet] ddnet: autopkgtest regression on armhf: output to stderr Added tag(s) pending. Added tag(s) pending. -- 995742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995742 997802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999594: libyaml-cpp-dev: empty YAML_CPP_LIBRARIES in yaml-cpp-config.cmake
Package: libyaml-cpp-dev Version: 0.7.0+dfsg-7.1 Severity: serious X-Debbugs-Cc: sramac...@debian.org Control: affects -1 src:dcm2niix src:ros-rviz Based on what I can tell from 0.6.3-10, /usr/lib/*/cmake/yaml-cpp/yaml-cpp-config.cmake should have YAML_CPP_LIBRARIES set to yaml-cpp. With the current version this is no longer the case. I think this issue causes at least ros-rviz and dcm2niix fail to build Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: libyaml-cpp-dev: empty YAML_CPP_LIBRARIES in yaml-cpp-config.cmake
Processing control commands: > affects -1 src:dcm2niix src:ros-rviz Bug #999594 [libyaml-cpp-dev] libyaml-cpp-dev: empty YAML_CPP_LIBRARIES in yaml-cpp-config.cmake Added indication that 999594 affects src:dcm2niix and src:ros-rviz -- 999594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 999594
Processing commands for cont...@bugs.debian.org: > affects 999594 src:opensurgsim Bug #999594 [libyaml-cpp-dev] libyaml-cpp-dev: empty YAML_CPP_LIBRARIES in yaml-cpp-config.cmake Added indication that 999594 affects src:opensurgsim > thanks Stopping processing here. Please contact me if you need assistance. -- 999594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 998343, block 998572 with 998343
Processing commands for cont...@bugs.debian.org: > affects 998343 + src:pytools Bug #998343 [python3-sphinx-copybutton] python3-sphinx-copybutton: clipboard.min.js is missing - causes new black upstream release to fail to build Added indication that 998343 affects src:pytools > block 998572 with 998343 Bug #998572 [src:pytools] pytools: FTBFS: dh_sphinxdoc: error: debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboard.min.js is missing 998572 was not blocked by any bugs. 998572 was not blocking any bugs. Added blocking bug(s) of 998572: 998343 > thanks Stopping processing here. Please contact me if you need assistance. -- 998343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998343 998572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997465: marked as done (python-marshmallow-sqlalchemy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sat, 13 Nov 2021 07:18:45 +
with message-id
and subject line Bug#997465: fixed in python-marshmallow-sqlalchemy 0.26.1-1
has caused the Debian Bug report #997465,
regarding python-marshmallow-sqlalchemy: 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.)
--
997465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-marshmallow-sqlalchemy
Version: 0.19.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-marshmallow-sqlalchemy
> dpkg-buildpackage: info: source version 0.19.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Utkarsh Gupta
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem=pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-marshmallow-sqlalchemy using existing
> ./python-marshmallow-sqlalchemy_0.19.0.orig.tar.gz
> dpkg-source: info: building python-marshmallow-sqlalchemy in
> python-marshmallow-sqlalchemy_0.19.0-1.debian.tar.xz
> dpkg-source: info: building python-marshmallow-sqlalchemy in
> python-marshmallow-sqlalchemy_0.19.0-1.dsc
> debian/rules binary
> dh binary --buildsystem=pybuild --with python3
>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
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> copying src/marshmallow_sqlalchemy/convert.py ->
> /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> copying src/marshmallow_sqlalchemy/fields.py ->
> /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> copying src/marshmallow_sqlalchemy/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> copying src/marshmallow_sqlalchemy/schema.py ->
> /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> copying src/marshmallow_sqlalchemy/exceptions.py ->
> /<>/.pybuild/cpython3_3.9/build/marshmallow_sqlalchemy
> running egg_info
> creating src/marshmallow_sqlalchemy.egg-info
> writing src/marshmallow_sqlalchemy.egg-info/PKG-INFO
> writing dependency_links to
> src/marshmallow_sqlalchemy.egg-info/dependency_links.txt
> writing requirements to src/marshmallow_sqlalchemy.egg-info/requires.txt
> writing top-level names to src/marshmallow_sqlalchemy.egg-info/top_level.txt
> writing manifest file 'src/marshmallow_sqlalchemy.egg-info/SOURCES.txt'
> reading manifest file 'src/marshmallow_sqlalchemy.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory
> 'docs'
> warning: no previously-included files matching '*.pyo' found under directory
> 'docs'
> warning: no previously-included files matching '*.pyc' found under directory
> 'tests'
> warning: no previously-included files matching '*.pyo' found under directory
> 'tests'
> no previously-included directories found matching 'docs/_build'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'src/marshmallow_sqlalchemy.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile:
Bug#995783: marked as done (python-marshmallow-sqlalchemy autopkgtest fails with SQLAlchemy 1.4.23+ds1-2)
Your message dated Sat, 13 Nov 2021 07:18:45 + with message-id and subject line Bug#997465: fixed in python-marshmallow-sqlalchemy 0.26.1-1 has caused the Debian Bug report #997465, regarding python-marshmallow-sqlalchemy autopkgtest fails with SQLAlchemy 1.4.23+ds1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-marshmallow-sqlalchemy Version: 0.19.0-1 Severity: serious Hi, As per this log: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-marshmallow-sqlalchemy/15788075/log.gz Please fix this ASAP. Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Source: python-marshmallow-sqlalchemy Source-Version: 0.26.1-1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of python-marshmallow-sqlalchemy, 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. Emmanuel Arias (supplier of updated python-marshmallow-sqlalchemy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Nov 2021 06:46:16 + Source: python-marshmallow-sqlalchemy Architecture: source Version: 0.26.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 989270 997465 Changes: python-marshmallow-sqlalchemy (0.26.1-1) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Remove obsolete field Name from debian/upstream/metadata (already present in machine-readable debian/copyright). . [ Emmanuel Arias ] * d/tests: uses pyversions -s instead of -i parameter to test supported Python versions. * d/control: add python3-pytest-lazy-fixture dependency. * wrap-and-sort * New upstream version 0.26.1 (Closes: #989270) which includes: - Fix call deprecated attribute 'Binary' of sqlalchemy (Closes: #997465). * d/control: Bump debhelper-compat to 13. * d/control: Bump Standards-Version to 4.6.0.1. * d/gbp.conf: set debian/master as default branch according to DEP-14. * d/docs: Add AUTHORS.rst and CONTRIBUTING.rst. * d/control: add nocheck profile to b-deps used in tests. * d/copyright: update upstream copyright. Checksums-Sha1: 2b2636b8d1016fcc7ae0169c9ee0e561e3df6a27 2498 python-marshmallow-sqlalchemy_0.26.1-1.dsc 3a335020b138ce83a094532de2af392911c9afeb 48035 python-marshmallow-sqlalchemy_0.26.1.orig.tar.gz f1ab73489b2702ef0c462146f34ce0340623fd67 2788 python-marshmallow-sqlalchemy_0.26.1-1.debian.tar.xz a6e13cb7c37d89e1f4bd7af51fe97723f8017ee1 8050 python-marshmallow-sqlalchemy_0.26.1-1_source.buildinfo Checksums-Sha256: 6a3d34b58c8cb1e804a8d8d6424cd5c0b44f3e23cc926a2004423ae7197c15dd 2498 python-marshmallow-sqlalchemy_0.26.1-1.dsc ac3de0308cf08483b8e72de7481cd92fa20444a5ac587a2c4c4267115ee2c35c 48035 python-marshmallow-sqlalchemy_0.26.1.orig.tar.gz e5a843c2c5ecbd270c94240494f76ae90dc56fb1314a39ea02a794767937ddcc 2788 python-marshmallow-sqlalchemy_0.26.1-1.debian.tar.xz cd4b531022db5e508c1401d20f7b3f27ae053bcf45203db11fc9b06b639cb1b2 8050 python-marshmallow-sqlalchemy_0.26.1-1_source.buildinfo Files: e3331e04545b3beeca6fd8a9c8e2fe7c 2498 python optional python-marshmallow-sqlalchemy_0.26.1-1.dsc 21c033fb586887a29c81a97aa6ec7809 48035 python optional python-marshmallow-sqlalchemy_0.26.1.orig.tar.gz eaf62862ddd41cc654a68ed9dc4ad098 2788 python optional python-marshmallow-sqlalchemy_0.26.1-1.debian.tar.xz 506090c301e35817b434aa3d98083002 8050 python optional python-marshmallow-sqlalchemy_0.26.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmGPYEMACgkQQoMEoXSN zHrHlA//Rpvc9vcwf0o8KDKkmeQt0pBuwWvxEN1YBRM9eYzrquB81dLJWy1no2pm tscU6xXfWBzquNrB3aPhQ5T0auXi2GkXuXiFUM/UmRXyYFnd5CGsrg9RFMm1yyO7 HJrs86pyofjbxFhtE3s0MGQfnr4x
Processed: breezy also FTBFS in bookworm since somewhere in September 2021
Processing commands for cont...@bugs.debian.org: > found 995410 3.1.0-8 Bug #995410 [src:breezy] breezy: FTBFS: Marked as found in versions breezy/3.1.0-8. > thanks Stopping processing here. Please contact me if you need assistance. -- 995410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
