Processed: Re: camitk: vtk[6,7] removal

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Added tag(s) upstream.
> tags -1 help
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Added tag(s) help.
> forwarded -1 Emmanuel Promayon , 
> Celine Fouard 
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Set Bug forwarded-to-address to 'Emmanuel Promayon 
, Celine Fouard 
'.

-- 
1013153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1013153: camitk: vtk[6,7] removal

[Andreas Tille]

Control: tags -1 upstream
Control: tags -1 help
Control: forwarded -1 Emmanuel Promayon 
, Celine Fouard 


Hi Emmanuel and Celine,

Debian has dropped support for VTK 6/7 and camitk needs to be ported to VTK9.
Currently libvtk9-qt-dev is not installable to do a test build.  It would be
great if you could confirm that camitk builds with VTK9.

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1028619: rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

tags -1 patch + upstream
forwarded -1 https://github.com/Textualize/rich/pull/2751

Am 13.01.23 um 19:25 schrieb Sandro Tosi:

yeah i'm wondering why you keep updating packages you dont maintain to
new upstream releases and breaking revdeps as consequence


It's seems to me you are the only person who who disagrees on the work I do.

That rdeps are will fail on package update is quite normal not only to 
me. But it's a difference if a upstream project is doing a major version 
bump or some usual minor update.
And we are not in any freeze state yet there I agree no uncoordinated 
and unneeded version updates should happen.


So far possible I pointed in other reports I did open to the upstream 
fix that adjust the local tests for the different behavior pygments 
2.14.0 is producing.
Within rich this doesn't did happen yet by any other reporter or by 
upstream itself.


So I created a PR [1] that will fix the issues within the tests.

For your convenience I added the same patch here where I can rebuild the 
current version of rich in unstable successful again.


[1] https://github.com/Textualize/rich/pull/2751

--
Regards
CarstenFrom bea71b3ca0f7b5c22f0ed050eb125b32e8085a65 Mon Sep 17 00:00:00 2001
From: Carsten Schoenert 
Date: Sat, 14 Jan 2023 07:38:57 +0100
Subject: [PATCH] tests: Adjustments to run tests with pygments 2.14.0

The current most recent version of pygments produces some different
output which provoke failing some of the the existing tests.
---
 tests/test_syntax.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/test_syntax.py b/tests/test_syntax.py
index 5eff05ee..6b8cfd8b 100644
--- a/tests/test_syntax.py
+++ b/tests/test_syntax.py
@@ -110,7 +110,7 @@ def test_python_render_simple_indent_guides():
 )
 rendered_syntax = render(syntax)
 print(repr(rendered_syntax))
-expected = '\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: Iterable[T]) -> Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n\x1b[2m│   \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│   │   \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│   \x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│   │   \x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│   \x1b[0mfirst = \x1b[34mTrue\x1b[0m\n\x1b[2m│   \x1b[0m\x1b[34mfor\x1b[0m value \x1b[35min\x1b[0m iter_values:\n\x1b[2m│   │   \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│   │   \x1b[0mfirst = \x1b[34mFalse\x1b[0m\n\x1b[2m│   │   \x1b[0mprevious_value = value\n\x1b[2m│   \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n'
+expected = '\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: Iterable[T]) -> Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2;37m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n\x1b[2m│   \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│   │   \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│   \x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│   │   \x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│   \x1b[0mfirst = \x1b[34mTrue\x1b[0m\n\x1b[2m│   \x1b[0m\x1b[34mfor\x1b[0m value \x1b[35min\x1b[0m iter_values:\n\x1b[2m│   │   \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│   │   \x1b[0mfirst = \x1b[34mFalse\x1b[0m\n\x1b[2m│   │   \x1b[0mprevious_value = value\n\x1b[2m│   \x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n'
 assert rendered_syntax == expected
 
 
@@ -127,7 +127,7 @@ def test_python_render_line_range_indent_guides():
 )
 rendered_syntax = render(syntax)
 print(repr(rendered_syntax))
-expected = '\x1b[2m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n'
+expected = '\x1b[2;37m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n'
 assert rendered_syntax == expected
 
 
-- 
2.39.0

Bug#1028641: libquazip1-qt5-dev: Missing dependencies on "qtbase5-dev, zlib1g-dev"

[Adrian Bunk]

Package: libquazip1-qt5-dev
Version: 1.3-1
Severity: serious

/usr/lib/x86_64-linux-gnu/cmake/QuaZip-Qt5-1.3/QuaZip-Qt5_SharedTargets.cmake:
INTERFACE_LINK_LIBRARIES "Qt5::Core;ZLIB::ZLIB"


I am not sure the cmake file should add these to the linker line
for rdeps, but if it does then libquazip1-qt5-dev needs dependencies on
  qtbase5-dev, zlib1g-dev

With the missing dependencies added, users like reverse dependencies
will no longer have to manually copy such implementation details of
libquazip to their own build dependencies.

Bug#1028640: libquazip1-qt6-dev: Missing dependencies on "qt6-base-dev, libqt6core5compat6-dev, zlib1g-dev"

[Adrian Bunk]

Package: libquazip1-qt6-dev
Version: 1.3-2
Severity: serious
Control: affects -1 src:libodsstream src:minexpert2

/usr/lib/x86_64-linux-gnu/cmake/QuaZip-Qt6-1.3/QuaZip-Qt6_SharedTargets.cmake:  
INTERFACE_LINK_LIBRARIES "Qt6::Core;Qt6::Core5Compat;ZLIB::ZLIB"


I am not sure the cmake file should add these to the linker line
for rdeps, but if it does then libquazip1-qt6-dev needs dependencies on
  qt6-base-dev, libqt6core5compat6-dev, zlib1g-dev

With the missing dependencies added, users like reverse dependencies
(currently libodsstream and minexpert2) will no longer have to manually copy
such implementation details of libquazip to their own build dependencies.

Processed: libquazip1-qt6-dev: Missing dependencies on "qt6-base-dev, libqt6core5compat6-dev, zlib1g-dev"

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libodsstream src:minexpert2
Bug #1028640 [libquazip1-qt6-dev] libquazip1-qt6-dev: Missing dependencies on 
"qt6-base-dev, libqt6core5compat6-dev, zlib1g-dev"
Added indication that 1028640 affects src:libodsstream and src:minexpert2

-- 
1028640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#996799: twitterwatch - upload needed

[Emmanuel Arias]

Hi,


On Fri, Jan 13, 2023 at 09:49:15PM +0100, Malik wrote:
> Hello DPT,
> 
> I have created a patch to close #996799 in twitterwatch package [1]
> I need a mainter to upload the current version (0.1-3) to the tftp-master

As Timo mentioned in the bug report. It would be great if the Homepage can
be updated as well.

Also, the package doesn't have tests (if I'm not wrong). Could you add
autopkgtests?

Cheers,
Emmanuel
> 
> [1] https://salsa.debian.org/python-team/packages/twitterwatch
> 
> Thank you in  advance
> -- 
> Malik Mlitat




signature.asc
Description: PGP signature

Processed: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1028192 [gajim] gajim: Gajim 1.6.0-1 crashes on connect
Bug 1028192 cloned as bug 1028638
> reassign -2 libproxy1v5 0.4.18-1
Bug #1028638 [gajim] gajim: Gajim 1.6.0-1 crashes on connect
Bug reassigned from package 'gajim' to 'libproxy1v5'.
No longer marked as found in versions gajim/1.6.0-1.
Ignoring request to alter fixed versions of bug #1028638 to the same values 
previously set
Bug #1028638 [libproxy1v5] gajim: Gajim 1.6.0-1 crashes on connect
Marked as found in versions libproxy/0.4.18-1.
> retitle -2 libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Bug #1028638 [libproxy1v5] gajim: Gajim 1.6.0-1 crashes on connect
Changed Bug title to 'libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call' from 
'gajim: Gajim 1.6.0-1 crashes on connect'.

-- 
1028192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028192
1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

[Martin]

Control: clone -1 -2
Control: reassign -2 libproxy1v5 0.4.18-1
Control: retitle -2 libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

This is the backtrace with a debian.org account:

(gdb) bt
#0  read_encoded_value_with_base(unsigned char, _Unwind_Ptr, unsigned char 
const*, _Unwind_Ptr*)
(encoding=160 '\240', base=, p=0x7fffd106e799 
"\351\006\321\377\177", val=0x7fffd106ded8)
at 
/build/gcc-12-PBog5r/gcc-12-12.2.0/src/libstdc++-v3/../libgcc/unwind-pe.h:284
#1  0x734a8511 in read_encoded_value (val=0x7fffd106ded8, 
p=0x7fffd106e791 "\n\001\264\377\177", encoding=160 '\240', 
context=0x7fffd106e380)
at 
/build/gcc-12-PBog5r/gcc-12-12.2.0/src/libstdc++-v3/../libgcc/unwind-pe.h:304
#2  parse_lsda_header(_Unwind_Context*, unsigned char const*, lsda_header_info*)
(context=context@entry=0x7fffd106e380, p=0x7fffd106e791 
"\n\001\264\377\177", 
p@entry=0x7fffd106e790 "\240\n\001\264\377\177", 
info=info@entry=0x7fffd106ded0) at 
../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:60
#3  0x734a8607 in __cxxabiv1::__gxx_personality_v0(int, _Unwind_Action, 
_Unwind_Exception_Class, _Unwind_Exception*, _Unwind_Context*)
(version=, actions=2, exception_class=5138137972254386944, 
ue_header=0x7fffb4010aa0, context=0x7fffd106e380)
at ../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:454
#4  0x71313131 in _Unwind_Phase2 (context=0x7fffd106e380, 
exception_object=0x7fffb4010aa0) at unwind/unwind-internal.h:118
#5  _Unwind_Resume (exception_object=0x7fffb4010aa0) at unwind/Resume.c:37
#6  0x7fffbdaa334a in 
__gnu_cxx::new_allocator::~new_allocator() (this=, __in_chrg=)
at /usr/include/c++/11/ext/new_allocator.h:89
#7  std::allocator::~allocator() (this=, 
__in_chrg=) at /usr/include/c++/11/bits/allocator.h:174
#8  std::_Vector_base 
>::_Vector_impl::~_Vector_impl() (this=, __in_chrg=)
at /usr/include/c++/11/bits/stl_vector.h:128
#9  std::_Vector_base 
>::~_Vector_base() (this=, __in_chrg=)
at /usr/include/c++/11/bits/stl_vector.h:337
#10 std::vector >::~vector() 
(this=, __in_chrg=)
at /usr/include/c++/11/bits/stl_vector.h:683
#11 envvar_config_extension::get_config(libproxy::url const&) (this=, dst=) at ./libproxy/modules/config_envvar.cpp:60
#12 0x7fffbda99e52 in libproxy::proxy_factory::get_config(libproxy::url&, 
std::vector >&, 
std::__cxx11::basic_string, std::allocator 
>&)
(this=0x3a26320, realurl=..., config=std::vector of length 0, capacity 0, 
ignore="") at ./libproxy/proxy.cpp:265
#13 0x7fffbda9a287 in 
libproxy::proxy_factory::get_proxies(std::__cxx11::basic_string, std::allocator > const&) (this=0x3a26320, 
realurl="https://debian.org:443";) at ./libproxy/proxy.cpp:206
#14 0x7fffbda9a751 in px_proxy_factory_get_proxies(pxProxyFactory_*, char 
const*)
(self=0x3a26320, url=url@entry=0x3cb9170 "https://debian.org:443";) at 
./libproxy/proxy.cpp:465
#15 0x7fffbdace61f in get_libproxy_proxies (task=0x39e56c0 [GTask], 
source_object=0x282b580, task_data=0x3cb9170, cancellable=)
at ../proxy/libproxy/glibproxyresolver.c:153
#16 0x769c7793 in g_task_thread_pool_thread (thread_data=0x39e56c0, 
pool_data=) at ../../../gio/gtask.c:1454
#17 0x76ca46da in g_thread_pool_thread_proxy (data=) at 
../../../glib/gthreadpool.c:352
#18 0x76ca3d0d in g_thread_proxy (data=0x2f96a40) at 
../../../glib/gthread.c:831
#19 0x77d25fd4 in start_thread (arg=) at 
./nptl/pthread_create.c:442
#20 0x77da666c in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) 

Bug#1028636: pocl: FTBFS on arm64: ***** The testsuite has failed! *****

[Sebastian Ramacher]

Source: pocl
Version: 3.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=arm64&ver=3.1-1&stamp=1673537413&raw=0

dpkg-gensymbols: warning: debian/libpocl2/DEBIAN/symbols doesn't match 
completely debian/libpocl2.symbols
--- debian/libpocl2.symbols (libpocl2_3.1-1_arm64)
+++ dpkg-gensymbolsR76HBy   2023-01-12 15:29:59.848720577 +
@@ -23,28 +23,28 @@
  
_ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb0EEclEcE5__nul@Base
 3.0
  
_ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 3.0
  _ZN4pocl23eraseFunctionAndCallersEPN4llvm8FunctionE@Base 1.8-3~visibility
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 0.11
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 0.11
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst)_ZNSt6vectorIPKcSaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 0.13-9~llvm3.8+gcc7
+#MISSING: 3.1-1# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
 #MISSING: 1.8# 
(optional=templinst|arch=mipsel)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 1.1-6~llvm6.0+gcc8
-#MISSING: 1.8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4swapERS4_@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKc{size_t}@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst|subst)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_mutateE{size_t}{size_t}PKc{size_t}@Base
 1.6-2~hardening
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE24_M_get_insert_unique_posERKS5_@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERKS5_@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 1.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 1.1-2~llvm5.0
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIvESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 1.7-3~llvm10
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 0.11
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 0.11
-#MISSING: 1.8# 
(optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_jESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 1.0
-#MISSING: 1.8# 
(optional=te

Bug#1028635: dnf FTBFS: ERROR: test_do_transaction (tests.api.test_dnf_base.DnfBaseApiTest.test_do_transaction)

[Adrian Bunk]

Source: dnf
Version: 4.14.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dnf&arch=all&ver=4.14.0-2&stamp=1673468063&raw=0

==
ERROR: test_do_transaction 
(tests.api.test_dnf_base.DnfBaseApiTest.test_do_transaction)
--
Traceback (most recent call last):
  File "/<>/tests/api/test_dnf_base.py", line 160, in 
test_do_transaction
self.base.do_transaction(display=None)
  File "/<>/dnf/base.py", line 951, in do_transaction
self._moduleContainer.save()
  File "/usr/lib/python3/dist-packages/libdnf/module.py", line 1241, in save
return _module.ModulePackageContainer_save(self)
   ^
libdnf._error.Error: Failed to create directory "/etc/dnf": 13 - Permission 
denied

--
Ran 796 tests in 7.199s

FAILED (errors=1, skipped=1)


0% tests passed, 1 tests failed out of 1

Total Test time (real) =   7.96 sec

The following tests FAILED:
  1 - test (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8

Processed: libexplain: FTBFS in bullseye

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 997222
Bug #997222 {Done: Håvard Flaget Aasen } 
[src:libexplain] libexplain: FTBFS: libexplain/iocontrol/siocadddlci.c:51:12: 
error: invalid application of ‘sizeof’ to incomplete type ‘struct dlci_add’
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libexplain/1.4.D001-12.
> found 997222 1.4.D001-11
Bug #997222 [src:libexplain] libexplain: FTBFS: 
libexplain/iocontrol/siocadddlci.c:51:12: error: invalid application of 
‘sizeof’ to incomplete type ‘struct dlci_add’
Ignoring request to alter found versions of bug #997222 to the same values 
previously set
> fixed 997222 1.4.D001-12
Bug #997222 [src:libexplain] libexplain: FTBFS: 
libexplain/iocontrol/siocadddlci.c:51:12: error: invalid application of 
‘sizeof’ to incomplete type ‘struct dlci_add’
Marked as fixed in versions libexplain/1.4.D001-12.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
997222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#997222: libexplain: FTBFS in bullseye

[Santiago Vila]

reopen 997222
found 997222 1.4.D001-11
fixed 997222 1.4.D001-12
thanks

Note: There is a fix proposal for bullseye in Bug #1025703.

Bug#1027619: gh: FTBFS: tests fail

[Andreas Henriksson]

Hello Lucas Nussbaum,

Could you please provide some additional input? See below.

On Sun, Jan 01, 2023 at 03:33:44PM +0100, Lucas Nussbaum wrote:
> Source: gh
> Version: 2.18.1+dfsg1-1
> Severity: serious
> Justification: FTBFS
[...]
> > === RUN   TestStartJupyterServerFailure
> > client_test.go:70: error connecting to internal server: failed to share 
> > remote port 16634: dial tcp 127.0.0.1:50051: connect: connection refused
> > --- FAIL: TestStartJupyterServerFailure (0.00s)
> > FAIL
> > FAILgithub.com/cli/cli/v2/internal/codespaces/grpc  0.039s
> > ?   github.com/cli/cli/v2/internal/codespaces/grpc/jupyter  [no 
> > test files]
> > ?   github.com/cli/cli/v2/internal/codespaces/grpc/test [no 
> > test files]
> > ?   github.com/cli/cli/v2/internal/config   [no test files]
[...]

Port 16634 is hardcoded at:
./internal/codespaces/grpc/client.go:   codespacesInternalPort=
16634

If this port is not available I presume things will just fail.

I've rebuilt the package locally and it succeeds for me. It also
succeded on the official buildds.

If you are able to reproduce the problem it would be great if you could
check what is using the port to identify if it's some external program
using this port and thus making the test fail or if it possibly is the
test-suite racing against itself somehow.

As far as I can tell right now, this issue doesn't seem release-critical to me
so consider if maybe the severity should be downgraded.

Regards,
Andreas Henriksson

Processed: unarchive for bullseye

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 997222
Bug #997222 {Done: Håvard Flaget Aasen } 
[src:libexplain] libexplain: FTBFS: libexplain/iocontrol/siocadddlci.c:51:12: 
error: invalid application of ‘sizeof’ to incomplete type ‘struct dlci_add’
Unarchived Bug 997222
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
997222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1025183: silx: (autopkgtest) needs update for python3.11: Segmentation fault

[Adrian Bunk]

On Sat, Dec 03, 2022 at 10:06:21PM +1100, Stuart Prescott wrote:
> It appears that src:silx FTBFS at present too. The failure is during
> building the docs with python3.10, meaning that this failure predates
> python3.11.
> 
> The failing line is:
> 
> # build the documentation
> pybuild --build -s custom -p 3.10 --build-args="cd doc && env
> PYTHONPATH={build_dir} http_proxy='127.0.0.1:9' xvfb-run -a
> --server-args=\"-screen 0 1024x768x24\" {interpreter} -m sphinx -N -bhtml
> source build/html"
> I: pybuild base:240: cd doc && env 
> PYTHONPATH=/build/silx-pvssnu/silx-1.1.0+dfsg/.pybuild/cpython3_3.10_silx/build
> http_proxy='127.0.0.1:9' xvfb-run -a --server-args="-screen 0 1024x768x24"
> python3.10 -m sphinx -N -bhtml source build/html
> Running Sphinx v4.5.0
> [...snip...]
> reading sources... [ 92%] modules/sx
> qt.qpa.xcb: could not connect to display :109
> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though
> it was found.
> This application failed to start because no Qt platform plugin could be
> initialized. Reinstalling the application may fix this problem.
> 
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen, vnc, xcb.
> 
> Aborted (core dumped)

This doesn't happen for me or in the reproducible CI,
it might be (or was) a bug that only triggers in some setups?

cu
Adrian

Bug#1019790: eviacam: diff for NMU version 2.1.4-2.1

[Bastian Germann]

On Thu, 5 Jan 2023 09:43:48 +1300 Olly Betts  wrote:

I can't test the patch I attached earlier due to the other bug.  If
that bug is specific to some webcams/systems I could NMU the patch
without testing if you think that's useful (let me know).  I'm hesitant
to try applying the PR too as I'm not at all familiar with this package,
- it seems better for the maintainer to do that.


I have just tested the patch and uploaded it as-is as NMU to DELAYED/10.

Bug#1028633: mlpack: FTBFS: mkdir: cannot create directory ‘/usr/lib/python3.11/site-packages/’: Permission denied

[Sebastian Ramacher]

Source: mlpack
Version: 4.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=mlpack&arch=amd64&ver=4.0.1-1&stamp=1673622675&raw=0

-- Installing: 
/<>/debian/tmp/usr/include/mlpack/methods/CMakeLists.txt
mkdir: cannot create directory ‘/usr/lib/python3.11/site-packages/’: Permission 
denied
/usr/bin/python3: No module named pip
CMake Error at 
/<>/src/mlpack/bindings/python/PythonInstall.cmake:23 (message):
  Error installing Python bindings!
Call Stack (most recent call first):
  src/mlpack/bindings/python/cmake_install.cmake:66 (include)
  src/mlpack/bindings/cmake_install.cmake:50 (include)
  src/mlpack/cmake_install.cmake:68 (include)
  cmake_install.cmake:55 (include)


make[1]: *** [Makefile:113: install] Error 1


Cheers
-- 
Sebastian Ramacher

Bug#1028634: tiledarray: FTBFS: Could not find a package configuration file provided by "blaspp"

[Sebastian Ramacher]

Source: tiledarray
Version: 1.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=tiledarray&arch=amd64&ver=1.0.0-1&stamp=1673359717&raw=0


-- Performing Test EIGEN3_COMPILES - Success
CMake Error at /usr/share/cmake-3.25/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
  Could not find a package configuration file provided by "blaspp" with any
  of the following names:

blasppConfig.cmake
blaspp-config.cmake

  Add the installation prefix of "blaspp" to CMAKE_PREFIX_PATH or set
  "blaspp_DIR" to a directory containing one of the above files.  If "blaspp"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/lib/cmake/BTAS/btas-config.cmake:104 (find_dependency)
  cmake/modules/FindOrFetchBTAS.cmake:1 (find_package)
  CMakeLists.txt:279 (include)

Cheers
-- 
Sebastian Ramacher

Bug#1027803: src:fakeroot: fails to migrate to testing for too long: ftbfs on mipsel

[Andreas Henriksson]

Hello,

So the mipsel FTBFS is because of a failing test-case that was added in
the 1.30-1 version of fakeroot.

For more information on this issue see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023286#48

Regards,
Andreas Henriksson

Bug#1023686: marked as done (readline: Inaccurate copyright file)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 22:38:15 +
with message-id 
and subject line Bug#1023686: fixed in readline 8.2-1.3
has caused the Debian Bug report #1023686,
regarding readline: Inaccurate copyright file
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.)


-- 
1023686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: readline
Version: 8.2-1.1
Severity: serious
Tags: patch

The debian/copyright file is missing some information (copyright statements and 
at least one license).
I have put together and attached machine-readable versions of the two copyright 
files with added info.

You should repack to get rid of the embedded rlwrap copy and the non-source doc 
files (#1023683),
which would simplify maintaining the copyright files.

The licenses of the embedded fonts are not included in the attached copyright 
file.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment:
This is Debian GNU/Linux's prepackaged version of the FSF's GNU
Readline library.
 .
This package was put together by Matthias Klose ,
derived from the bash package by Guy Maor .
Upstream-Name: Readline
Upstream-Contact: 
Chet Ramey 
Jeff Solomon  (examples/excallback.c)
Harold Levy  (examples/rl-fgets.c)
Source: http://ftp.gnu.org/gnu/readline/

Files: *
Copyright:
Copyright (C) 1987-2022 Free Software Foundation, Inc.
License: GPL-3+
Readline is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
 .
This package is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
 .
You should have received a copy of the GNU General Public License
along with Readline.  If not, see .
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 3 can be found in `/usr/share/common-licenses/GPL-3'.

Files: examples/readlinebuf.h
   examples/rl-fgets.c
   examples/rlfe/*
   examples/rlwrap-*.tar.gz
Copyright:
Copyright (C) 1987-2022 Free Software Foundation, Inc.
Copyright (c) 2001 by Dimitris Vyzovitis [v...@media.mit.edu]
Copyright (C) 1999 Jeff Solomon (examples/excallback.c)
Copyright (C) 2003-2004 Harold Levy (examples/rl-fgets.c)
Copyright (c) 1993-2002 Juergen Weigert 
(jnwei...@immd4.informatik.uni-erlangen.de)
Copyright (c) 1993-2002 Michael Schroeder 
(mlsch...@immd4.informatik.uni-erlangen.de)
Copyright (C) 1987 Oliver Laumann (examples/rlfe)
Copyright (C) 2004, 1999 Per Bothner
Copyright (C) 2000-2007 Hans Lub
Copyright (C) 1999-2001 Geoff Wing
Copyright (C) Damian Ivereigh 2000
License: GPL-2+
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2, or (at your option)
any later version.
 .
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
 .
You should have received a copy of the GNU General Public License
along with this program (see the file COPYING); if not, write to the
Free Software Foundation, Inc.,
59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
Comment:
 On Debian systems, the complete text of the GNU General Public License
 version 2 can be found in `/usr/share/common-licenses/GPL-2'.
 .
 The rlwrap example is also available in its own Debian package.
 The code copyrighted by Damian Ivereigh is licensed under LGPL-2.1+.

Files: doc/*.texi doc/*.info doc/*.html doc/*.[03] doc/*.dvi doc/*.pdf doc/*.ps
Copyright:
Copyright (C) 1988-2015 Free Software Foundation, Inc.
License: GFDL-NIV-1.3+
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, no Front-Cover Texts, and
no Back-Cover Texts.  A copy of the license is included in the
section entitled "GNU

Bug#1028278: dh-cmake FTBFS with Python 3.11 as default version

[Andreas Henriksson]

On Mon, Jan 09, 2023 at 08:02:05AM +0200, Adrian Bunk wrote:
> Source: dh-cmake
> Version: 0.6.1
> Severity: serious
> Tags: ftbfs bookworm sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dh-cmake.html
[...]
> 
>   File "/build/1st/dh-cmake-0.6.1/dhcmake/tests/source_check.py", line 25, in 
> 
> self.foreach_py(lambda a, r, c: self.assertEqual(autopep8.fix_code(c), c,
> ^
> AssertionError: '# Th[204 chars]\n\n# from unittest import skip\n\nimport 
> os\n[9838 chars]e)\n' != '# Th[204 chars]\n\n#from unittest import 
> skip\n\nimport os\nf[9837 chars]e)\n'
> Diff is 10430 characters long. Set self.maxDiff to None to see it. : File 
> dhcmake/tests/common.py is incorrectly formatted
[...]

So same as above, but in my own words:
It seems autopep8.fix_code() has changed it's opinion on formatting and
now thinks dhcmake/tests/common.py line 5 should have a space after
the hash (#) character (before `from unittest import skip`).

The new style looks better IMHO and this might be a bugfix in
autopep8.fix_code(), but at the same time changes like these might cause
alot of breakage (atleast if used in tests like in this case).

Regards,
Andreas Henriksson

Bug#1028632: tomcat10: Catalina fails to load due to missing MbeansDescriptorsIntrospectionSource

[Jorge Moraleda]

Package: tomcat10
Version: 10.0.0~M7-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jorge.moral...@gmail.com

Dear Maintainer,

I just tested the tomcat 10 version packaged in the "debian/experimental".
(10.0.0~M7-1) on top of a recent debian 12 (bookworm) installation.

It failed with "java.lang.ClassNotFoundException:
org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource".

I don't think detailed logs are necessary because:

(1) This bug is the same as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=964908 (that one is against tomcat9).

(2) From the above it seems that it has to do with the format of "bnd" and from
this package changelogs, I believe the maintainers are already familiar with
this issue. (https://metadata.ftp-
master.debian.org/changelogs//main/t/tomcat10/tomcat10_10.0.0~M7-1_changelog)

Thank you


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (800, 'testing'), (50, 'experimental'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tomcat10 depends on:
ii  lsb-base   11.5
ii  systemd252.4-1
ii  sysvinit-utils [lsb-base]  3.06-2
ii  tomcat10-common10.0.0~M7-1
ii  ucf3.0043

Versions of packages tomcat10 recommends:
ii  libtcnative-1  1.2.32-1+b1

Versions of packages tomcat10 suggests:
pn  tomcat10-admin 
pn  tomcat10-docs  
pn  tomcat10-examples  
pn  tomcat10-user  

-- Configuration Files:
/etc/tomcat10/policy.d/01system.policy [Errno 13] Permission denied: 
'/etc/tomcat10/policy.d/01system.policy'
/etc/tomcat10/policy.d/02debian.policy [Errno 13] Permission denied: 
'/etc/tomcat10/policy.d/02debian.policy'
/etc/tomcat10/policy.d/03catalina.policy [Errno 13] Permission denied: 
'/etc/tomcat10/policy.d/03catalina.policy'
/etc/tomcat10/policy.d/04webapps.policy [Errno 13] Permission denied: 
'/etc/tomcat10/policy.d/04webapps.policy'
/etc/tomcat10/policy.d/50local.policy [Errno 13] Permission denied: 
'/etc/tomcat10/policy.d/50local.policy'

-- no debconf information

Bug#1025884: src:ddnet: fails to migrate to testing for too long: FTBFS on s390x

[Andreas Henriksson]

Hello,

The upstream PR fixing big endian builds that Adrian Bunk previously
set in the forwarded control message is now merged upstream.
It would be great if this commit could be cherry-picked as a patch
into the ddnet package to fix build os s390x (big endian):

https://github.com/ddnet/ddnet/commit/abb1979d20d9a3290442d5d0ed304ce24c0a710e

Regards,
Andreas Henriksson

Processed: Re: collectd FTBFS with Python 3.11 as default version

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #1028146 [src:collectd] collectd FTBFS with Python 3.11 as default version
Added tag(s) fixed-upstream.
> forwarded -1 https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/11
Bug #1028146 [src:collectd] collectd FTBFS with Python 3.11 as default version
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/11'.

-- 
1028146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028146: collectd FTBFS with Python 3.11 as default version

[Andreas Henriksson]

Control: tags -1 + fixed-upstream
Control: forwarded -1 
https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/11

Hello,

The python 3.11 issue is fixed upstream in this commit:
https://github.com/collectd/collectd/commit/623e95394e0e62e7f9ced2104b786d21e9c0bf53

A merge-request against the debian collectd packaging git repo has been
opened, albeit with a different patch than upstreams:
https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/11

Regards,
Andreas Henriksson

Bug#909750: marked as done (applications tries to write to /usr/* directories via libfontconfig1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 22:19:50 +0100
with message-id <20230113211950.sj74o6xejk322...@fatal.se>
and subject line fontconfig 2.14.1-3 uploaded to unstable
has caused the Debian Bug report #909750,
regarding applications tries to write to /usr/* directories via libfontconfig1
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.)


-- 
909750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 62.0.2-1
Severity: normal
Tags: upstream

Dear Maintainer,

I am using Firefox confined with "unofficial" AppArmor profile, and
noticed that this produces a lot of strange denials, as Firefox for
unknown reason tries to write to the /usr/* directories, something to do
with fonts:

```
type=AVC msg=audit(1538065109.144:473): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/local/share/fonts/.uuid.TMP-iXM9tT" pid=6835 
comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:474): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/cMap/.uuid.TMP-ilSIWs" pid=6835 
comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:475): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/X11/util/.uuid.TMP-WTbop2" pid=6835 
comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:476): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-CNS1/.uuid.TMP-Sab4RB" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:477): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-GB1/.uuid.TMP-CxBKkb" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:478): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-Japan1/.uuid.TMP-udurNK" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:479): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-Japan2/.uuid.TMP-E6K8fk" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:480): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-Korea1/.uuid.TMP-oMrQIT" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:481): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/eot/font-awesome/.uuid.TMP-O2xybt" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:482): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/svg/font-awesome/.uuid.TMP-vOWiE2" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:483): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/truetype/wine/.uuid.TMP-zKha7B" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.144:484): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/X11/encodings/large/.uuid.TMP-mxX2zb" 
pid=6835 comm="firefox" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.476:485): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/local/share/fonts/.uuid.TMP-O01YyL" pid=6896 
comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c" fsuid=1000 
ouid=1000
type=AVC msg=audit(1538065109.476:486): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/cMap/.uuid.TMP-SNXVVl" pid=6896 
comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c" fsuid=1000 
ouid=1000
type=AVC msg=audit(1538065109.480:487): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/fonts/X11/util/.uuid.TMP-qg04iW" pid=6896 
comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c" fsuid=1000 
ouid=1000
type=AVC msg=audit(1538065109.480:488): apparmor="DENIED" operation="mknod" 
profile="firefox" name="/usr/share/poppler/cMap/Adobe-CNS1/.uuid.TMP-yTTeGw" 
pid=6896 comm=57656220436F6E74656E74 requested_mask="c" denied_mask="c" 
fsuid=1000 ouid=1000
type=AVC msg=audit(1538065109.480:489): apparmor="DENIED" o

Processed: tagging 1028187, fixed 1012478 in 0.2.0~alpha6-2, tagging 1028592, tagging 1028607

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1028187 + sid bookworm
Bug #1028187 {Done: Sun Min } [libcommons-validator-java] 
libcommons-validator-java: Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:aggregate (default-cli)
Added tag(s) bookworm and sid.
> fixed 1012478 0.2.0~alpha6-2
Bug #1012478 {Done: Louis-Philippe Véronneau } 
[src:data-xml-clojure] data-xml-clojure: FTBFS with libnrepl-clojure 0.9.0-1
Marked as fixed in versions data-xml-clojure/0.2.0~alpha6-2.
> tags 1028592 + sid bookworm
Bug #1028592 [tagcoll2] tagcoll2 2.0.14-2 fails to build on sid
Added tag(s) bookworm and sid.
> tags 1028607 + sid bookworm
Bug #1028607 [src:emacs] FTBFS: FAILED test-correct-notice and test-end-chop in 
copyright-tests.log due to new year 2023
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1012478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012478
1028187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028187
1028592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028592
1028607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028628: rust-lsd: ftbfs, build-depends on librust-lscolors-0.12+default-dev

[Jeremy Bicha]

Source: rust-lsd
Version: 0.23.1-1
Severity: serious
Tags: ftbfs

rust-lsd fails to build from source because it Build-Depends on
librust-lscolors-0.12+default-dev but the current version of
rust-lscolors in Debian is 0.13

Thank you,
Jeremy Bicha

Bug#1026213: marked as done (login: $HOME created as 0755 by default)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 22:04:15 +0100
with message-id <20230113210415.mfdcle5dyjaqm...@fatal.se>
and subject line Re: login: $HOME created as 0755 by default
has caused the Debian Bug report #1026213,
regarding login: $HOME created as 0755 by default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1026213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: login
Version: 1:4.13+dfsg1-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: r...@localhost.lan, Debian Security Team 


Dear Maintainer,

please uncomment the line in /etc/login.defs that currently says:

#HOME_MODE  0700

to say:

HOME_MODE  0700

The current settings makes user $HOME directories be created with
permissions where other users can read the contents by default.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages login depends on:
ii  libaudit1   1:3.0.7-1.1+b2
ii  libc6   2.36-6
ii  libcrypt1   1:4.4.33-1
ii  libpam-modules  1.5.2-5
ii  libpam-runtime  1.5.2-5
ii  libpam0g1.5.2-5

login recommends no packages.

login suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,

Given there already seems to be common consensus that this is not a bug
I've sent a request to tag this bug report with the 'wontfix' tag
and I'm now closing the bug (to get it of the release-critical bugs
tracker).

My personal opinion on this matter if anyone cares is that the
login.defs setting the reporter talks about is not a universal fix.
Tools like adduser doesn't care about it. The adduser tool is also the
one to use instead of useradd, et.al. from src:shadow if you want
"sane defaults" (according to debian policy etc).
If you insist on using other tools, then getting the right settings is
left up to you to control.

Regards,
Andreas Henriksson--- End Message ---

Processed: wontfix 1026...@bugs.debian.org

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1026213 + wontfix
Bug #1026213 [login] login: $HOME created as 0755 by default
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1026213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#996799: twitterwatch - upload needed

[Malik]

Hello DPT,

I have created a patch to close #996799 in twitterwatch package [1]
I need a mainter to upload the current version (0.1-3) to the tftp-master

[1] https://salsa.debian.org/python-team/packages/twitterwatch

Thank you in  advance
-- 
Malik Mlitat

Bug#965006:

[Markus Koschany]

Am Freitag, dem 13.01.2023 um 12:47 -0600 schrieb Jorge Moraleda:
> I think getting tomcat 10 into unstable so it is in a path to eventually
> making into testing and then stable has become a higher priority now that
> tomcat 10 is required when using webapps developed using the latest Spring
> framework version
> (https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x
> )

[...]

Tomcat 10 coming to unstable this weekend. Stay tuned!

Markus


signature.asc
Description: This is a digitally signed message part

Processed: severity of 1028608 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1028608 serious
Bug #1028608 [evdi-dkms] evdi-dkms: EVDI module does not build with 
linux-headers-6.0.0-6-amd64
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1028608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028625: src:x-loader: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: x-loader
Version: 1.5.1+git20110715+fca7cd2-2
Severity: serious
Control: close -1 1.5.1+git20110715+fca7cd2-3
X-Debbugs-CC: Marcos Talau 
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1026364

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:x-loader has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The package failed to build from 
source, which was reported in bug 1026364.


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=x-loader



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:x-loader: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.1+git20110715+fca7cd2-3
Bug #1028625 [src:x-loader] src:x-loader: fails to migrate to testing for too 
long: FTBFS
The source 'x-loader' and version '1.5.1+git20110715+fca7cd2-3' do not appear 
to match any binary packages
Marked as fixed in versions x-loader/1.5.1+git20110715+fca7cd2-3.
Bug #1028625 [src:x-loader] src:x-loader: fails to migrate to testing for too 
long: FTBFS
Marked Bug as done
> block -1 by 1026364
Bug #1028625 {Done: Paul Gevers } [src:x-loader] 
src:x-loader: fails to migrate to testing for too long: FTBFS
1028625 was not blocked by any bugs.
1028625 was not blocking any bugs.
Added blocking bug(s) of 1028625: 1026364

-- 
1028625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1028442 https://github.com/SirVer/ultisnips/issues/1514
Bug #1028442 [src:vim-ultisnips] vim-ultisnips: autopkgtest fails if Vim has 
non-contiguous patch ranges applied
Set Bug forwarded-to-address to 
'https://github.com/SirVer/ultisnips/issues/1514'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1028442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#965006:

[Jorge Moraleda]

I think getting tomcat 10 into unstable so it is in a path to eventually
making into testing and then stable has become a higher priority now that
tomcat 10 is required when using webapps developed using the latest Spring
framework version (
https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x
)

Thus IMHO we should resolve this issue by adding the Breaks+Replaces to
libtomcat10-java and give up co-instalability. Of course we should
immediately open a feature request to get co-instalability back, but that
would not stop the package from going into unstable and, after bookworm is
released, testing.

Bug#1028622: sphinx-prompt: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: sphinx-prompt
Version: 1.5.0-2
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

Some of the failing parts are:

autopkgtest [03:25:03]: test unittests: [---
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.k5oqcgm7/downtmp/build.h5g/src
collected 12 items

../build.h5g/src/tests/test_sphinx_prompt.py .FF...F.[100%]

=== FAILURES ===
_ test[arguments1-options1-content1-\nspan.prompt1:before {\n  content: "$ ";\n}\none line\n] _

arguments = ['bash'], options = {'language': 'bash'}, content = ['one line']
expected = '\nspan.prompt1:before {\n  
content: "$ ";\n}\none 
line\n'

@pytest.mark.parametrize("arguments, options, content, expected", testdata)
def test(arguments, options, content, expected):
sphinx_prompt._cache.next_index = 1
sphinx_prompt._cache.prompts.clear()
stream = StringIO()
reporter = docutils.utils.Reporter("test data", 2, 4, stream, 1)
statemachine = docutils.statemachine.StateMachine([], None)
setattr(statemachine, "reporter", reporter)
directive = sphinx_prompt.PromptDirective(
"prompt", arguments, options, content, 0, 0, "", None, statemachine
)
result = directive.run()
>   assert result[0].astext() == expected
E   assert ''
E Skipping 159 identical leading characters in diff, use -v to show
E - ompt1">one line
E + ompt1">one line
E   

../build.h5g/src/tests/test_sphinx_prompt.py:165: AssertionError
_ test[arguments2-options2-content2-\nspan.prompt1:before {\n  content: "$ ";\n}\none line\n] _

arguments = [], options = {'language': 'bash'}, content = ['one line']
expected = '\nspan.prompt1:before {\n  
content: "$ ";\n}\none 
line\n'

@pytest.mark.parametrize("arguments, options, content, expected", testdata)
def test(arguments, options, content, expected):
sphinx_prompt._cache.next_index = 1
sphinx_prompt._cache.prompts.clear()
stream = StringIO()
reporter = docutils.utils.Reporter("test data", 2, 4, stream, 1)
statemachine = docutils.statemachine.StateMachine([], None)
setattr(statemachine, "reporter", reporter)
directive = sphinx_prompt.PromptDirective(
"prompt", arguments, options, content, 0, 0, "", None, statemachine
)
result = directive.run()
>   assert result[0].astext() == expected
E   assert ''
E Skipping 159 identical leading characters in diff, use -v to show
E - ompt1">one line
E + ompt1">one line
E   
...

It might be enough to pick

https://github.com/sbrunner/sphinx-prompt/commit/f996f7ab96ec63b08e27f96559b759143ccff214

from the upstream git tree to fix the issues.

Regards
Carsten

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1013935: [Pkg-freeipa-devel] Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x

[Timo Aaltonen]

Timo Aaltonen kirjoitti 12.1.2023 klo 20.57:

Paul Gevers kirjoitti 27.6.2022 klo 21.31:

Source: dogtag-pki
Version: 11.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it 
was showing up on our "slow" page [1]. I noticed that there were 
several runs that took 2:47 (our timeout time), while successful runs 
more in the order of minutes.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put dogtag-pki on our reject_list for amd64, 
armhf, and s390x.


Don't hesitate to reach out if you need help and some more information
from our infrastructure. E.g. I note that the runs on amd64 that I 
happen to check are run on ci-worker13 that, together with our armhf 
worker is running on a host with lots of CPUs (64 and 160) and RAM 
(256GB and 511GB) and also our s390x has 10 CPUs and 32 GB.


Paul

[1] https://ci.debian.net/status/slow/


Hi,

I've finally updated dogtag-pki to fix some grave bugs, but this still 
remains. I don't know if the update fixes these racy tests (which they 
are, something goes wrong and it gets stuck), but is there a way for me 
to manually trigger them on ci.debian.net? They do pass on salsa-ci, but 
it's not the same thing..


Looks like the tests are still being run, which at least shows that they 
seem to be just as racy still :/ I need to reproduce the failure 
locally, which has been impossible so far.


--
t

Bug#1028621: sphinx: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: sphinx
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

As the output of the failing parts are noisy it's not useful to paste
them here.
The full log of the autopkgtest on amd64 run can be found here:

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sphinx/30313691/log.gz

Regards
Carsten

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1028620: ruby-pygments: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: ruby-pygments
Version: 2.3.0+ds-2.1
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

The failed part in detail is:

RUBYLIB=. GEM_PATH= ruby3.1 -S rake -f debian/ruby-tests.rake
mv lib ./.gem2deb.lib
/usr/bin/ruby3.1 -w -I"test" 
/usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/test_pygments.rb"  -v
Loaded suite /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader
Started
PygmentsConfigTest:
  test_filters: .: (0.064462)
  test_formatters:  .: (0.006962)
  test_lexers:  .: (0.021366)
  test_styles:  .: (0.000854)
PygmentsCssTest:
  test_css: .: (0.001624)
  test_css_colorful:.: (0.001286)
  test_css_default: .: (0.000903)
  test_css_options: .: (0.000823)
  test_css_prefix:  .: (0.000833)
  test_css_prefix_and_options:  .: (0.000772)
PygmentsHighlightTest:
  test_full_html_highlight: F
===
Failure: test_full_html_highlight(PygmentsHighlightTest)
/tmp/autopkgtest-lxc.wcymigwk/downtmp/build.qG9/src/test/test_pygments.rb:31:in 
`test_full_html_highlight'
 28:   def test_full_html_highlight
 29: code = P.highlight(RUBY_CODE)
 30: assert_match '#!/usr/bin/ruby', code
  => 31: assert_equal %(#!/usr/bin/ruby
 32: puts 'foo'
 33: ), code
 34:   end
<"#!/usr/bin/ruby\n" +
"puts 'foo'\n" +
""> expected but was
<"#!/usr/bin/ruby\n" +
"puts 'foo'\n" +
"">

diff:
  #!/usr/bin/ruby
? puts  'foo'
  
===
: (0.154840)
  test_highlight_defaults_to_html:  .: (0.002140)
  test_highlight_formatter_bbcode:  .: (0.001620)
  test_highlight_formatter_terminal:.: (0.001277)
  test_highlight_on_multi_threads:  O
===
Omission: We do not actually support multithreading 
[test_highlight_on_multi_threads(PygmentsHighlightTest)]
/tmp/autopkgtest-lxc.wcymigwk/downtmp/build.qG9/src/test/test_pygments.rb:114:in
 `test_highlight_on_multi_threads'
===
: (0.000826)
  test_highlight_options:   .: (0.001922)
  test_highlight_still_works_with_invalid_code: .: (0.046896)
  test_highlight_works_on_utf8: .: (0.000949)
  test_highlight_works_on_utf8_all_chars_automatically: .: (0.000811)
  test_highlight_works_on_utf8_automatically:   .: (0.000834)
  test_highlight_works_with_larger_files:   .: (0.033287)
  test_highlight_works_with_multiple_newlines:  .: (0.001873)
  test_highlight_works_with_multiple_utf8:  .: (0.000864)
  test_highlight_works_with_multiple_utf8_and_trailing_newline: .: (0.000906)
  test_highlight_works_with_null_bytes: .: (0.000902)
  test_highlight_works_with_trailing_cr:.: (0.001775)
  test_highlight_works_with_trailing_newline:   .: (0.001717)
  test_version: .: (0.000343)
PygmentsLexerClassTest:
  test_find:.: (0.000268)
  test_find_by_alias:   .: (0.000152)
  test_find_by_name:.: (0.000124)
  test_find_lexer_by_extname:   .: (0.000178)
  test_find_lexer_by_mimetype:  .: (0.000122)
PygmentsLexerTest:
  test_lexer_by_content:.: (0.001258)
  test_lexer_by_filename:   .: (0.420205)
  test_lexer_by_filename_and_content:   .: (0.084091)
  test_lexer_by_mimetype:   .: (0.000676)
  test_lexer_by_name:   .: (0.014858)
  test_lexer_by_nothing:.: (0.002577)

Finished in 0.881532932 seconds.
---
39 tests, 60 assertions, 1 failures, 0 errors, 0 pendings, 1 omissions, 0 
notifications
97.3684% passed
---
44.24 tests/s, 68.06 assertions/s

Updating to 2.3.1 and adding this commit might solve this issue.

https://github.com/pygments/pygments.rb/commit/fe03c274a4b01fc9657a90dba5f16b3e9401082a

Regards
Carsten


-- System Information:
Debian Release: bookworm/

Bug#1028619: rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Sandro Tosi]

On Fri, Jan 13, 2023 at 1:24 PM Carsten Schoenert
 wrote:
>
> Source: rich
> Version: 13.0.0-1
> Severity: serious
>
> Dear Maintainer,
>
> after the upload of pygments 2.14.0+dfsg-1 your package is failung while
> running the autopkgtest.

yeah i'm wondering why you keep updating packages you dont maintain to
new upstream releases and breaking revdeps as consequence



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1028619: rich: autopkgtest is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: rich
Version: 13.0.0-1
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

The failed part in detail is:

=== FAILURES ===
___ test_python_render_simple_indent_guides 

def test_python_render_simple_indent_guides():
syntax = Syntax(
CODE,
lexer="python",
line_numbers=False,
theme="ansi_light",
code_width=60,
word_wrap=False,
indent_guides=True,
)
rendered_syntax = render(syntax)
print(repr(rendered_syntax))
expected = '\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: 
Iterable[T]) -> Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2m│   
\x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for first 
an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = 
\x1b[36miter\x1b[0m(values)\n\x1b[2m│   \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│   
│   \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│   
\x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│   │   
\x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│   \x1b[0mfirst = 
\x1b[34mTrue\x1b[0m\n\x1b[2m│   \x1b[0m\x1b[34mfor\x1b[0m value 
\x1b[35min\x1b[0m iter_values:\n\x1b[2m│   │   \x1b[0m\x1b[34myield\x1b[0m 
first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│   │   \x1b[0mfirst = 
\x1b[34mFalse\x1b[0m\n\x1b[2m│   │   \x1b[0mprevious_value = value\n\x1b[2m│   
\x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n'
>   assert rendered_syntax == expected
E   assert '\x1b[34mdef\...vious_value\n' == '\x1b[34mdef\...vious_value\n'
E Skipping 81 identical leading characters in diff, use -v to show
E   mb␛[0m
E - ␛[2m│   ␛[0m␛[33m"""Iterate and generate a tuple with a flag for 
first an␛[0m
E + ␛[2;37m│   ␛[0m␛[33m"""Iterate and generate a tuple with a flag for 
first an␛[0m
E ?+++
E   ␛[2m│   ␛[0miter_values = ␛[36miter␛[0m(values)
E   ␛[2m│   ␛[0m␛[34mtry␛[0m:...
E 
E ...Full output truncated (10 lines hidden), use '-vv' to show

tests/test_syntax.py:114: AssertionError
- Captured stdout call -
'\x1b[34mdef\x1b[0m \x1b[32mloop_first_last\x1b[0m(values: Iterable[T]) -> 
Iterable[Tuple[\x1b[36mb\x1b[0m\n\x1b[2;37m│   \x1b[0m\x1b[33m"""Iterate and 
generate a tuple with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values 
= \x1b[36miter\x1b[0m(values)\n\x1b[2m│   \x1b[0m\x1b[34mtry\x1b[0m:\n\x1b[2m│  
 │   \x1b[0mprevious_value = \x1b[36mnext\x1b[0m(iter_values)\n\x1b[2m│   
\x1b[0m\x1b[34mexcept\x1b[0m \x1b[36mStopIteration\x1b[0m:\n\x1b[2m│   │   
\x1b[0m\x1b[34mreturn\x1b[0m\n\x1b[2m│   \x1b[0mfirst = 
\x1b[34mTrue\x1b[0m\n\x1b[2m│   \x1b[0m\x1b[34mfor\x1b[0m value 
\x1b[35min\x1b[0m iter_values:\n\x1b[2m│   │   \x1b[0m\x1b[34myield\x1b[0m 
first, \x1b[34mFalse\x1b[0m, previous_value\n\x1b[2m│   │   \x1b[0mfirst = 
\x1b[34mFalse\x1b[0m\n\x1b[2m│   │   \x1b[0mprevious_value = value\n\x1b[2m│   
\x1b[0m\x1b[34myield\x1b[0m first, \x1b[34mTrue\x1b[0m, previous_value\n'
_ test_python_render_line_range_indent_guides __

def test_python_render_line_range_indent_guides():
syntax = Syntax(
CODE,
lexer="python",
line_numbers=False,
theme="ansi_light",
code_width=60,
word_wrap=False,
line_range=(2, 3),
indent_guides=True,
)
rendered_syntax = render(syntax)
print(repr(rendered_syntax))
expected = '\x1b[2m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple 
with a flag for first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = 
\x1b[36miter\x1b[0m(values)\n'
>   assert rendered_syntax == expected
E   assert '\x1b[2;37m│ ...[0m(values)\n' == '\x1b[2m│   \...[0m(values)\n'
E - ␛[2m│   ␛[0m␛[33m"""Iterate and generate a tuple with a flag for 
first an␛[0m
E + ␛[2;37m│   ␛[0m␛[33m"""Iterate and generate a tuple with a flag for 
first an␛[0m
E ?+++
E   ␛[2m│   ␛[0miter_values = ␛[36miter␛[0m(values)

tests/test_syntax.py:131: AssertionError
- Captured stdout call -
'\x1b[2;37m│   \x1b[0m\x1b[33m"""Iterate and generate a tuple with a flag for 
first an\x1b[0m\n\x1b[2m│   \x1b[0miter_values = \x1b[36miter\x1b[0m(values)\n'
=== short test summary info 
FAILED tests/test_syntax.py::test_python_render_simple_indent_guides - assert...
FAILED tests/test_syntax.py::test_python_render_line_range_indent_guides - as...
== 2 failed, 765 passed, 23 skipped in 5.86s ===
E: pybuild pybuild:388: test: plugin pyproject failed with: exit code=1: cd 
/tmp/autopkgtest

Bug#1028618: retext: autopkgtest on s390x is failng after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: retext
Version: 8.0.0-1
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest on s390x with python 3.10.

The failed part in detail is:

==
FAIL: test_autoSave (test_window.TestWindow)
--
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
  File 
"/tmp/autopkgtest-lxc.ay0gd1cu/downtmp/autopkgtest_tmp/tests/test_window.py", 
line 382, in test_autoSave
self.assertEqual(tempFile.read(), 'second content')
AssertionError: 'first content' != 'second content'
- first content
+ second content


--

Regards
Carsten

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1028617: ipython: autopkgtest is faling after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: ipython
Version: 8.5.0-3
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

The failed part in detail is:

=== FAILURES ===
_ TestLexers.testIPythonLexer __

self = 

def testIPythonLexer(self):
fragment = '!echo $HOME\n'
tokens = [
(Token.Operator, '!'),
]
tokens.extend(self.bash_lexer.get_tokens(fragment[1:]))
>   self.assertEqual(tokens, list(self.lexer.get_tokens(fragment)))
E   AssertionError: Lists differ: [(Tok[78 chars] (Token.Name.Variable, 
'$HOME'), (Token.Text.Whitespace, '\n')] != [(Tok[78 chars] 
(Token.Name.Variable, '$HOME'), (Token.Text, '\n')]
E
E   First differing element 4:
E   (Token.Text.Whitespace, '\n')
E   (Token.Text, '\n')
E
E [(Token.Operator, '!'),
E  (Token.Name.Builtin, 'echo'),
E  (Token.Text.Whitespace, ' '),
E  (Token.Name.Variable, '$HOME'),
E   -  (Token.Text.Whitespace, '\n')]
E   ? ---
E
E   +  (Token.Text, '\n')]

IPython/lib/tests/test_lexers.py:25: AssertionError

Updating the package to version 8.8.0 should fix the issue, it's
containing the commit

https://github.com/ipython/ipython/commit/ed7f35f8b721d4b4dcafea173ce724bee25704c7

which addresses the changes done by recent pygments.

Regards
Carsten

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1028616: hovercraft: autopkgtest is faling after updating pygments to 2.14.0+dfsg-1

[Carsten Schoenert]

Source: hovercraft
Version: 2.7-4
Severity: serious

Dear Maintainer,

after the upload of pygments 2.14.0+dfsg-1 your package is failung while
running the autopkgtest.

The failed part in detail is:

autopkgtest [03:24:50]: test hovercraft: [---
[*] testing python3.11:
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack -- 
/usr/bin/python3.11
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.74de8cqg/downtmp/build.58j/src
collecting ... collected 35 items

tests/test_generator.py::GeneratorTests::test_big FAILED [  2%]

=== FAILURES ===
___ GeneratorTests.test_big 

self = 

def test_big(self):
template = Template(os.path.join(TEST_DATA, "maximal"))
html, deps = rst2html(os.path.join(TEST_DATA, "advanced.rst"), template)
>   self.assertEqual(html, HTML_OUTPUTS["advanced"])
E   AssertionError: b'\n
' != b'\n# 
Comment\n[1236 chars]tml>'

tests/test_generator.py:24: AssertionError
=== short test summary info 
FAILED tests/test_generator.py::GeneratorTests::test_big - AssertionError: b'...
!! stopping after 1 failures !!!
== 1 failed in 0.25s ===


Regards
Carsten

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1026645: marked as done (trapperkeeper-webserver-jetty9-clojure: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 17:41:49 +
with message-id 
and subject line Bug#1026645: fixed in trapperkeeper-webserver-jetty9-clojure 
4.4.1-2
has caused the Debian Bug report #1026645,
regarding trapperkeeper-webserver-jetty9-clojure: FTBFS: make[1]: *** 
[debian/rules:17: override_dh_auto_build] Error 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.)


-- 
1026645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trapperkeeper-webserver-jetty9-clojure
Version: 4.4.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> lein pom debian/pom.xml
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> java.lang.Exception: Error loading /<>/project.clj
>  at leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1046)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.Compiler$CompilerException: Syntax error compiling at 
> (/<>/project.clj:3:1).
> #:clojure.error{:phase :compile-syntax-check, :line 3, :column 1, :source 
> "/<>/project.clj"}
>  at clojure.lang.Compiler.load (Compiler.java:7652)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.ExceptionInfo: Unsupported major Java version. 
> Expects 8 or 11.
> {:major "17", :minor "0"}
>  at leiningen.core.project$eval657.invokeStatic (project.clj:101)
> leiningen.core.project$eval657.invoke (project.clj:3)
> clojure.lang.Compiler.eval (Compiler.java:7181)
> clojure.lang.Compiler.load (Compiler.java:7640)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.

Bug#1026687: marked as done (puppetlabs-http-client-clojure: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 17:12:34 +
with message-id 
and subject line Bug#1026687: fixed in puppetlabs-http-client-clojure 2.1.0-3
has caused the Debian Bug report #1026687,
regarding puppetlabs-http-client-clojure: FTBFS: make[1]: *** [debian/rules:17: 
override_dh_auto_build] Error 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.)


-- 
1026687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetlabs-http-client-clojure
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> lein pom debian/pom.xml
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> java.lang.Exception: Error loading /<>/project.clj
>  at leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1046)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.Compiler$CompilerException: Syntax error compiling at 
> (/<>/project.clj:1:1).
> #:clojure.error{:phase :compile-syntax-check, :line 1, :column 1, :source 
> "/<>/project.clj"}
>  at clojure.lang.Compiler.load (Compiler.java:7652)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.main$_main$fn__7024.invoke (main.clj:447)
> leiningen.core.main$_main.invokeStatic (main.clj:442)
> leiningen.core.main$_main.doInvoke (main.clj:439)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.core$apply.invokeStatic (core.clj:667)
> clojure.main$main_opt.invokeStatic (main.clj:514)
> clojure.main$main_opt.invoke (main.clj:510)
> clojure.main$main.invokeStatic (main.clj:664)
> clojure.main$main.doInvoke (main.clj:616)
> clojure.lang.RestFn.applyTo (RestFn.java:137)
> clojure.lang.Var.applyTo (Var.java:705)
> clojure.main.main (main.java:40)
> Caused by: clojure.lang.ExceptionInfo: Unsupported major Java version. 
> Expects 8 or 11.
> {:major "17", :minor "0"}
>  at leiningen.core.project$eval657.invokeStatic (project.clj:60)
> leiningen.core.project$eval657.invoke (project.clj:1)
> clojure.lang.Compiler.eval (Compiler.java:7181)
> clojure.lang.Compiler.load (Compiler.java:7640)
> clojure.lang.Compiler.loadFile (Compiler.java:7578)
> clojure.lang.RT$3.invoke (RT.java:327)
> leiningen.core.project$read_raw$fn__7638.invoke (project.clj:1044)
> leiningen.core.project$read_raw.invokeStatic (project.clj:1040)
> leiningen.core.project$read_raw.invoke (project.clj:1036)
> leiningen.core.project$read.invokeStatic (project.clj:1057)
> leiningen.core.project$read.invoke (project.clj:1054)
> leiningen.core.project$read.invokeStatic (project.clj:1058)
> leiningen.core.project$read.invoke (project.clj:1054)

Bug#985840: marked as done (gitlab-shell: should not ship /usr/bin/check)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 17:08:55 +
with message-id 
and subject line Bug#985840: fixed in gitlab-shell 14.13.0+ds1-1
has caused the Debian Bug report #985840,
regarding gitlab-shell: should not ship /usr/bin/check
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.)


-- 
985840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab-shell
Version: 13.13.0+debian-1+b1
Severity: serious

/usr/bin/check seems like an awfully generic program name to be shipped
in something like gitlab-shell.  Please don't.

Thanks,
Julien

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'testing-debug'), (500, 'testing'), (101, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab-shell depends on:
ii  libc6  2.31-9

gitlab-shell recommends no packages.

gitlab-shell suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gitlab-shell
Source-Version: 14.13.0+ds1-1
Done: Mohammed Bilal 

We believe that the bug you reported is fixed in the latest version of
gitlab-shell, 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 985...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mohammed Bilal  (supplier of updated gitlab-shell 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, 13 Jan 2023 17:42:29 +0530
Source: gitlab-shell
Binary: gitlab-shell golang-gitlab-gitlab-org-gitlab-shell-v14-dev
Architecture: source amd64 all
Version: 14.13.0+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Mohammed Bilal 
Description:
 gitlab-shell - handles git commands for GitLab
 golang-gitlab-gitlab-org-gitlab-shell-v14-dev - gitlab-shell golang module
Closes: 985840
Changes:
 gitlab-shell (14.13.0+ds1-1) experimental; urgency=medium
 .
   * Team upload.
 .
   [ Abhijith PA ]
   * Change /usr/bin/check to usr/bin/gitlab-shell-check
 (Closes: #985840)
 .
   [ Mohammed Bilal ]
   * New upstream version 14.13.0+ds1
Checksums-Sha1:
 0e9efe193952a80502f614be0c427213e701a6c8 3455 gitlab-shell_14.13.0+ds1-1.dsc
 bf03e8b1660422ad74d63a327070fe67a9eade84 16314672 
gitlab-shell_14.13.0+ds1.orig-vendor.tar.xz
 d64fe7a26cf47ad7ab1158d0f53a1e1771160cad 137500 
gitlab-shell_14.13.0+ds1.orig.tar.xz
 647f96999c852d38ccf242f590eaed1d5a556610 7520 
gitlab-shell_14.13.0+ds1-1.debian.tar.xz
 b4d9fa43f2598ead37dae90b199f19af00277933 8322 
gitlab-shell_14.13.0+ds1-1_amd64.buildinfo
 7ac0d5d592fad59bc1557dab2ccce8dfebbdb12e 18199240 
gitlab-shell_14.13.0+ds1-1_amd64.deb
 ebde72156d0422594fbd282de3f04168f2b2e9b4 16188484 
golang-gitlab-gitlab-org-gitlab-shell-v14-dev_14.13.0+ds1-1_all.deb
Checksums-Sha256:
 f640b467105791b51ca7287c30891f26994436d0d6602d8cecf170cdba3f0cdf 3455 
gitlab-shell_14.13.0+ds1-1.dsc
 300cdd0489d8be2e7689c62dfa59f4c521b8b840b9b488cca10a39cff85cfe9a 16314672 
gitlab-shell_14.13.0+ds1.orig-vendor.tar.xz
 d14351bac0a25d22d74cc08abd18170035269a3d2f473008dfa01a7cb13d3074 137500 
gitlab-shell_14.13.0+ds1.orig.tar.xz
 ef1f27ea84a68771349dd77fe991bad806e6b43a1f71b046093d82b311715f3a 7520 
gitlab-shell_14.13.0+ds1-1.debian.tar.xz
 abb0801a69f6704a9cb7b39a833a1dd1d2cc98056962e83f8e37e67f84bb26d1 8322 
gitlab-shell_14.13.0+ds1-1_amd64.buildinfo
 c4df61a50452c4532203168f573d117463faf3e23bb0259bd585e71db9b5ea4f 18199240 
gitlab-shell_14.13.0+ds1-1_amd64.deb
 ff3f99da875edb42d8f0ad97a1a576128d8386833ce22699ed596ec4ea5e7fe3 16188484 
golang-gitlab-gitlab-org-gitlab-shell-v14-dev_14.13.0+ds1-1_all.deb
Files:
 e67e2b0760c6ace107f3369b90f9a353 3455 net optional 
gitlab-shell_14.13.0+ds1-1.dsc
 a18962c3a4a68e420a968d1dbf13ec1b 16314672 net optional 
gitlab-shell_14.13.0+ds1.orig-ve

Bug#1012478: marked as done (data-xml-clojure: FTBFS with libnrepl-clojure 0.9.0-1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 12:09:52 -0500
with message-id 
and subject line close data-xml-clojure: FTBFS with libnrepl-clojure 0.9.0-1 bug
has caused the Debian Bug report #1012478,
regarding data-xml-clojure: FTBFS with libnrepl-clojure 0.9.0-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.)


-- 
1012478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: data-xml-clojure
Version: 0.2.0~alpha6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

data-xml-clojure/experimental recently started to FTBFS, probably after
libnrepl-clojure was upgraded (it built fine with 0.6.0-2).

[...]
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/data-xml-clojure-0.2.0~alpha6'
lein test
Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the 
artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
This could be due to a typo in :dependencies, file system permissions, or 
network issues.
If you are behind a proxy, try setting the 'http_proxy' environment variable.
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/data-xml-clojure-0.2.0~alpha6'
make: *** [debian/rules:11: binary] Error 2


Andreas


data-xml-clojure_0.2.0~alpha6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

This bug has been fixed and 0.2.0~alpha6-2 was uploaded.

Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#1028609: deepin-terminal: FTBFS -- Build dependency uninstallable

[Arun Kumar Pariyar]

Hi Nilesh,

On 13/01/2023 21:17, Nilesh Patra wrote:

Dear Maintainer,

deepin-terminal FTBFS because of not being able to install its
B-Ds. Some B-D (transitively?) depends on qtbase-abi-5-15-7 which
is not installable due to being a virtual package. But I leave that
onto you to check further.

| Install main build dependencies (apt-based resolver)
| 
|
| Installing build dependencies
| Reading package lists...
| Building dependency tree...
| Reading state information...
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libdtkgui5 : Depends: qtbase-abi-5-15-7 but it is not installable
| libdtkwidget5 : Depends: qtbase-abi-5-15-7 but it is not installable
| libqt5designer5 : Depends: qtbase-abi-5-15-7 but it is not installable
| qttools5-dev-tools : Depends: qt5-assistant (= 5.15.7-2) but it is not going 
to be installed
|  Depends: libqt5quick5 (>= 5.15.7+dfsg~) but it is not 
going to be installed or
|   libqt5quick5-gles (>= 5.15.7+dfsg~) but it is 
not going to be installed
|  Depends: libqt5quickwidgets5 (>= 5.15.7+dfsg~) but it is 
not going to be installed
|  Depends: libqt5webkit5 (>= 5.212.0~alpha4-8~) but it is 
not going to be installed
|  Depends: qtbase-abi-5-15-7 but it is not installable
|  Depends: qtdeclarative-abi-5-15-7
| E: Unable to correct problems, you have held broken packages.


Thanks for your bug report, the reason for uninstallable B-D is because 
qtbase-abi-5-15-8 is under transition [1]. It should take around 1-2 
days for the transition to complete with a binNMU of deepin-terminal 
with the new dependency, which should fix the issue.


[1] https://release.debian.org/transitions/html/qtbase-abi-5-15-8.html

Regards,
~ Arun Kumar Pariyar


OpenPGP_0x4B542AF704F74516.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 1028598 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1028598 serious
Bug #1028598 [pathological] pathological: Unplayable game
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1028598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1027391: marked as done (puppetlabs-ring-middleware-clojure: autopkgtest needs update for new version of clojure: warning on stderr)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 16:37:21 +
with message-id 
and subject line Bug#1027391: fixed in puppetlabs-ring-middleware-clojure 
1.3.1-2
has caused the Debian Bug report #1027391,
regarding puppetlabs-ring-middleware-clojure: autopkgtest needs update for new 
version of clojure: warning on stderr
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.)


-- 
1027391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: puppetlabs-ring-middleware-clojure
Version: 1.3.1-1
Severity: serious
X-Debbugs-CC: cloj...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:clojure

Dear maintainer(s),

With a recent upload of clojure the autopkgtest of 
puppetlabs-ring-middleware-clojure fails in testing when that 
autopkgtest is run with the binary packages of clojure from unstable. It 
passes when run with only packages from testing. In tabular form:


   passfail
clojurefrom testing1.11.1-2
puppetlabs-ring-middleware-clojure from testing1.3.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. There's a 
warning on stderr which is interpreted as failure by autopkgtest. If you 
can't work around the warning, you can make autopkgtest ignore it by 
adding the allow-stderr restriction.


Currently this regression is blocking the migration of clojure to 
testing [1]. Of course, clojure shouldn't just break your autopkgtest 
(or even worse, your package), but it seems to me that the change in 
clojure was intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from clojure should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=clojure

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppetlabs-ring-middleware-clojure/29779591/log.gz

#'user/all-tests
WARNING: abs already refers to: #'clojure.core/abs in namespace: 
medley.core, being replaced by: #'medley.core/abs
2022-12-29 18:13:02,909 INFO  [o.e.j.u.log] Logging initialized @4853ms 
to org.eclipse.jetty.util.log.Slf4jLog
2022-12-29 18:13:03,109 INFO  [p.t.s.w.jetty9-core] Removing buggy 
security provider SunPKCS11 version 17
WARNING: update-vals already refers to: #'clojure.core/update-vals in 
namespace: clojure.tools.analyzer.utils, being replaced by: 
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in 
namespace: clojure.tools.analyzer.utils, being replaced by: 
#'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in 
namespace: clojure.tools.analyzer, being replaced by: 
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in 
namespace: clojure.tools.analyzer, being replaced by: 
#'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in 
namespace: clojure.tools.analyzer.passes, being replaced by: 
#'clojure.tools.analyzer.utils/update-vals
WARNING: update-vals already refers to: #'clojure.core/update-vals in 
namespace: clojure.tools.analyzer.passes.uniquify, being replaced by: 
#'clojure.tools.analyzer.utils/update-vals

(nil nil nil)

Testing puppetlabs.ring-middleware.core-test
2022-12-29 18:13:07,045 INFO  [p.t.s.w.jetty9-service] Initializing web 
server(s).
2022-12-29 18:13:07,052 INFO  [p.t.s.w.jetty9-service] Starting web 
server(s).

2022-12-29 18:13:07,173 INFO  [p.t.s.w.jetty9-core] Starting web server.
2022-12-29 18:13:07,175 INFO  [o.e.j.s.Server] jetty-9.4.50.v20221107; 
built: unknown; git: unknown; jvm 17.0.5+8-Debian-2
2022-12-29 18:13:07,257 INFO  [o.e.j.s.AbstractConnector] Started 
ServerConnector@142a0473{HTTP/1.1, (http/1.1)}{0.0.0.0:9000}

2022-12-29 18:13:07,258 INFO  [o.e.j.s.Server] Started @9202ms
2022-12-29 18:13:07,268 INFO  [o.e.j.s.h.ContextHandler] Started 
o.e.j.s.h.ContextHandler@44c5830b{/hello,null,AVAILABLE}
2022-12-29

Bug#1026591: marked as done (cinder: FTBFS: make[1]: pyversions: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 16:19:43 +
with message-id 
and subject line Bug#1026591: fixed in cinder 2:21.0.0-2
has caused the Debian Bug report #1026591,
regarding cinder: FTBFS: make[1]: pyversions: No such file or directory
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.)


-- 
1026591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cinder
Version: 2:21.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> ==
> FAIL: 
> cinder.tests.unit.volume.drivers.ceph.test_rbd_iscsi.RBDISCSITestCase.test_unsupported_version
> cinder.tests.unit.volume.drivers.ceph.test_rbd_iscsi.RBDISCSITestCase.test_unsupported_version
> --
> testtools.testresult.real._StringException: pythonlogging:'': {{{
> 2022-12-20 09:56:59,544 INFO [keystonemiddleware.auth_token] Starting 
> Keystone auth_token middleware
> 2022-12-20 09:56:59,545 WARNING [keystonemiddleware._common.config] The 
> option "auth_url" is not known to keystonemiddleware
> 2022-12-20 09:56:59,545 WARNING [keystonemiddleware.auth_token] AuthToken 
> middleware is set with keystone_authtoken.service_token_roles_required set to 
> False. This is backwards compatible but deprecated behaviour. Please set this 
> to True.
> 2022-12-20 09:56:59,547 WARNING [keystonemiddleware.auth_token] Configuring 
> www_authenticate_uri to point to the public identity endpoint is required; 
> clients may not be able to authenticate against an admin endpoint
> }}}
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3.11/unittest/mock.py", line 1369, in patched
> return func(*newargs, **newkeywargs)
>^
>   File 
> "/<>/cinder/tests/unit/volume/drivers/ceph/test_rbd_iscsi.py", 
> line 167, in test_unsupported_version
> self.setup_mock_client()
>   File "/usr/lib/python3.11/unittest/mock.py", line 1366, in patched
> with self.decoration_helper(patched,
>   File "/usr/lib/python3.11/contextlib.py", line 137, in __enter__
> return next(self.gen)
>^^
>   File "/usr/lib/python3.11/unittest/mock.py", line 1348, in decoration_helper
> arg = exit_stack.enter_context(patching)
>   ^^
>   File "/usr/lib/python3.11/contextlib.py", line 502, in enter_context
> result = _enter(cm)
>  ^^
>   File "/usr/lib/python3.11/unittest/mock.py", line 1491, in __enter__
> new = Klass(**_kwargs)
>   
>   File "/usr/lib/python3.11/unittest/mock.py", line 2100, in __init__
> _safe_super(MagicMixin, self).__init__(*args, **kw)
>   File "/usr/lib/python3.11/unittest/mock.py", line 1100, in __init__
> _safe_super(CallableMixin, self).__init__(
>   File "/usr/lib/python3.11/unittest/mock.py", line 451, in __init__
> self._mock_add_spec(spec, spec_set, _spec_as_instance, _eat_self)
>   File "/usr/lib/python3.11/unittest/mock.py", line 502, in _mock_add_spec
> raise InvalidSpecError(f'Cannot spec a Mock object. [object={spec!r}]')
> unittest.mock.InvalidSpecError: Cannot spec a Mock object. [object= name='mock.client.RBDISCSIClient' id='139944652671568'>]
> 
> 
> --
> Ran 16561 tests in 297.642s

The full build log is available from:
http://qa-logs.debian.net/2022/12/20/cinder_21.0.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cinde

Bug#1026005: marked as done (cumin FTBFS: Tries to use $HOME)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 16:19:55 +
with message-id 
and subject line Bug#1026005: fixed in cumin 4.2.0-1
has caused the Debian Bug report #1026005,
regarding cumin FTBFS: Tries to use $HOME
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.)


-- 
1026005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cumin
Version: 4.1.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cumin&ver=4.1.1-2

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
SETUPTOOLS_SCM_PRETEND_VERSION="4.1.1-2" python3 setup.py develop --user
/usr/lib/python3/dist-packages/setuptools/dist.py:530: UserWarning: Normalizing 
'4.1.1-2' to '4.1.1.post2'
  warnings.warn(tmpl.format(**locals()))
running develop
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
and pip and other standards-based tools.
  warnings.warn(
error: [Errno 13] Permission denied: '/sbuild-nonexistent'
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1


This can be reproduced with
  HOME=/sbuild-nonexistent dpkg-buildpackage
--- End Message ---
--- Begin Message ---
Source: cumin
Source-Version: 4.2.0-1
Done: Riccardo Coccioli 

We believe that the bug you reported is fixed in the latest version of
cumin, 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 1026...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Riccardo Coccioli  (supplier of updated cumin 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, 12 Jan 2023 18:06:38 -
Source: cumin
Architecture: source
Version: 4.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Riccardo Coccioli 
Changed-By: Riccardo Coccioli 
Closes: 1026005
Changes:
 cumin (4.2.0-1) unstable; urgency=medium
 .
   * v4.2.0 upstream release. (Closes: #1026005)
Checksums-Sha1:
 4b4cbe3ad2c46ad003eed1014206490cf630a61c 2161 cumin_4.2.0-1.dsc
 c9154daf071addf9fbadbecd7a3d3261afc219e0 142756 cumin_4.2.0.orig.tar.gz
 4eae36c7bb0fa804f2a63cbd017b7340b6ff9e9b 833 cumin_4.2.0.orig.tar.gz.asc
 ea0ee756f8a2c7d9f69f6a43da7c281079538378 8724 cumin_4.2.0-1.debian.tar.xz
 7653bd078cc8dcbd3f596acbf901149270beeaca 10006 cumin_4.2.0-1_amd64.buildinfo
Checksums-Sha256:
 eb85f63fe407f1ca8c8d7864633738d787e4b610965fad84b270524cad787ca8 2161 
cumin_4.2.0-1.dsc
 0bf291d5451a5e3a24ad279920af3008a6b3b4f969746a9dc523881dacfa197a 142756 
cumin_4.2.0.orig.tar.gz
 9099aa3dfd789827b5ae6b076b4559c85a06f199b40046a1f4b214378361 833 
cumin_4.2.0.orig.tar.gz.asc
 2e5ec893897235f81ac3946311367fde2c7264ed8603a58373d83d77453f2b7b 8724 
cumin_4.2.0-1.debian.tar.xz
 8ad5b449af71b10f37d44399c9c80b34423deab33efd824bca05ba1bd05a8b6b 10006 
cumin_4.2.0-1_amd64.buildinfo
Files:
 8d4ce459d8883707e1114080d1bca5ce 2161 utils optional cumin_4.2.0-1.dsc
 c148f9c66f66d15566086be3506d0d81 142756 utils optional cumin_4.2.0.orig.tar.gz
 ef4757b7edcbe657ea770debb1a6e487 833 utils optional cumin_4.2.0.orig.tar.gz.asc
 3ba5a18ce884cc73b240ec425ee9fb30 8724 utils optional 
cumin_4.2.0-1.debian.tar.xz
 4f81b35cd276dc322b2da8d7319d7a42 10006 utils optional 
cumin_4.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAmPBf+0ACgkQPqHd3bJh
2XtoPAf/QcUw1qprms2PrP0EvaiZiu8iobDmDwC4GOuHFIBEVmf1X5z2qPSbn48C
xXVLBJsLHxAmRdo5Qy+jPd4ucgr/YHMZdtgB5aNWUYiWbCmDbpfr/qmg1VEo/Mwd
rAZBFECEDy6r3zXEOn/EOahQRPOv2GnKiWt1hLEW+vxW81NOpKdR9I3m0P6NugtZ
edQXDTq5hqJDDH74rFuOXwjaL0g5pVCP0mcNTOXcSERe4Iqmcgk//JoeWOscv1VI
yXdIBEJkGHDq41EWnZj6U35jCtjzcYKJqF08mlCOAuTecOjlbR4GfDY9IKDb9lBy
5F9LuxEqtO7BXjoA5UBVBJ3B2K6rQg==
=oaIG
-END PGP SIGNATURE End Message ---

Bug#1024820: Test suite error with pandas 1.5 (Issue #810)

[Yoshiki Vázquez Baeza]

Yes, I’ll take a stab at this in the coming days. Thanks for reporting.

On Jan 12, 2023, at 11:16 PM, Andreas Tille ***@***.***> wrote:



Is there any chance to tackle this issue?

—
Reply to this email directly, view it on 
GitHub, 
or 
unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: 
***@***.***>



-- 
Reply to this email directly or view it on GitHub:
https://github.com/biocore/emperor/issues/810#issuecomment-1382031195
You are receiving this because you authored the thread.

Message ID: 

Processed: Bug#1026591 marked as pending in cinder

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026591 [src:cinder] cinder: FTBFS: make[1]: pyversions: No such file or 
directory
Added tag(s) pending.

-- 
1026591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026591: marked as pending in cinder

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1026591 in cinder 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/services/cinder/-/commit/da4b69a6ea681bab4f4dc2570f7c62171725b292


* Address broken tests in Python 3.11 (Closes: #1026591):
- Add py3.11-test_rbd_iscsi_Make_tests_compatible_with_python.patch.
- Blacklist all of BackupCephTestCase and test_hpe3par.py
Note that this really is broken tests (mocking), and not a broken Cinder.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026591

Bug#1028609: deepin-terminal: FTBFS -- Build dependency uninstallable

[Nilesh Patra]

Package: deepin-terminal
Version: 5.2.11-1+b4
Severity: serious
X-Debbugs-Cc: a...@debian.org, by...@debian.org

Dear Maintainer,

deepin-terminal FTBFS because of not being able to install its
B-Ds. Some B-D (transitively?) depends on qtbase-abi-5-15-7 which
is not installable due to being a virtual package. But I leave that
onto you to check further.

| Install main build dependencies (apt-based resolver)
| 
|
| Installing build dependencies
| Reading package lists...
| Building dependency tree...
| Reading state information...
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libdtkgui5 : Depends: qtbase-abi-5-15-7 but it is not installable
| libdtkwidget5 : Depends: qtbase-abi-5-15-7 but it is not installable
| libqt5designer5 : Depends: qtbase-abi-5-15-7 but it is not installable
| qttools5-dev-tools : Depends: qt5-assistant (= 5.15.7-2) but it is not going 
to be installed
|  Depends: libqt5quick5 (>= 5.15.7+dfsg~) but it is not 
going to be installed or
|   libqt5quick5-gles (>= 5.15.7+dfsg~) but it is 
not going to be installed
|  Depends: libqt5quickwidgets5 (>= 5.15.7+dfsg~) but it is 
not going to be installed
|  Depends: libqt5webkit5 (>= 5.212.0~alpha4-8~) but it is 
not going to be installed
|  Depends: qtbase-abi-5-15-7 but it is not installable
|  Depends: qtdeclarative-abi-5-15-7
| E: Unable to correct problems, you have held broken packages.

Thanks.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages deepin-terminal depends on:
ii  expect5.45.4-2+b1
ii  libatspi2.0-0 2.46.0-4
ii  libc6 2.36-7
ii  libdframeworkdbus25.5.22-1
ii  libdtkcore5   5.5.33-1+b2
ii  libdtkgui55.5.25-1+b2
ii  libdtkwidget5 5.5.48-1+b2
ii  libgcc-s1 12.2.0-13
ii  libglib2.0-0  2.74.4-1
ii  libqt5core5a [qtbase-abi-5-15-7]  5.15.7+dfsg-2
ii  libqt5dbus5   5.15.7+dfsg-2
ii  libqt5gui55.15.7+dfsg-2
ii  libqt5widgets55.15.7+dfsg-2
ii  libstdc++612.2.0-13
ii  zssh  1.5c.debian.1-8

deepin-terminal recommends no packages.

deepin-terminal suggests no packages.

-- no debconf information

Bug#1027212: marked as done (python-dtcwt: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 15:28:17 +
with message-id 
and subject line Bug#1027212: fixed in python-dtcwt 0.12.0-5
has caused the Debian Bug report #1027212,
regarding python-dtcwt: autopkgtest fail with numpy/1.24.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.)


-- 
1027212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dtcwt
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: python-dtcwt
Source-Version: 0.12.0-5
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
python-dtcwt, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated python-dtcwt 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: Fri, 13 Jan 2023 20:23:14 +0530
Source: python-dtcwt
Architecture: source
Version: 0.12.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Bas Couwenberg 
Closes: 1027212
Changes:
 python-dtcwt (0.12.0-5) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix test failure with Numpy 1.24.
 (closes: #1027212)
Checksums-Sha1:
 94b3c47c3ebacfb6c4a110e15bc666f47c64591b 1808 python-dtcwt_0.12.0-5.dsc
 3af9a3a4b2e4978c77eb6f20b3e682cf0beeaad6 5788 
python-dtcwt_0.12.0-5.debian.tar.xz
 0836bb544c51faa430398746f71bf6d05bd3acb7 10254 
python-dtcwt_0.12.0-5_amd64.buildinfo
Checksums-Sha256:
 3e4ac839e7c1bbf932c12160b2a0ca91cc8a9e75708e53579e2a366f9fe1d8bf 1808 
python-dtcwt_0.12.0-5.dsc
 995694abfd1489d97b203fae46d31aa9a9ab8d030340cf5842d93c10a02df18e 5788 
python-dtcwt_0.12.0-5.debian.tar.xz
 0c9aac20a31a2b44f1d66003a4aea30413a141d91003081b96fb3f002b79ec25 10254 
python-dtcwt_0.12.0-5_amd64.buildinfo
Files:
 e395233482e367dcf690d7aa12fed33c 1808 science optional 
python-dtcwt_0.12.0-5.dsc
 c618962dbfc1ab45b4778d6606824202 5788 science optional 
python-dtcwt_0.12.0-5.debian.tar.xz
 caa99fbbf7450dcd5c5e80c331fe8bae 10254 science optional 
python-dtcwt_0.12.0-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY8FxzgAKCRAqJ5BL1yQ+
2puBAQCVxBDOlzZ4jZHkSKrAAX19U2HNX5U1qy7m96qWlsSdhgEAiJF+wA6XtK12
M8BO/uzPGUpIvfmWu9PdDINkRWwUswE=
=te8/
-END PGP SIGNATURE End Message ---

Bug#1028138: marked as done (arandr: no longer starts: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 15:19:29 +
with message-id 
and subject line Bug#1028138: fixed in arandr 0.1.11-1
has caused the Debian Bug report #1028138,
regarding arandr: no longer starts: module 'inspect' has no attribute 
'getargspec'
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.)


-- 
1028138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arandr
Version: 0.1.10-1.1
Severity: serious

Dear maintainer,

since I updated some Python packages recently, arandr is no longer starting:

> $ arandr
> Traceback (most recent call last):
>   File "/usr/bin/arandr", line 41, in 
> from screenlayout.gui import main
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 76, in 
> 
> class Application:
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 185, in 
> Application
> @actioncallback
>  ^^
>   File "/usr/lib/python3/dist-packages/screenlayout/gui.py", line 48, in 
> actioncallback
> argnames = inspect.getargspec(function)[0]
>^^
> AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
> 'getargs'?

Kind regards,
  Reiner
--- End Message ---
--- Begin Message ---
Source: arandr
Source-Version: 0.1.11-1
Done: Christian M. Amsüss 

We believe that the bug you reported is fixed in the latest version of
arandr, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian M. Amsüss  (supplier of updated arandr 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, 13 Jan 2023 09:24:48 +0100
Source: arandr
Architecture: source
Version: 0.1.11-1
Distribution: unstable
Urgency: medium
Maintainer: Christian M. Amsüss 
Changed-By: Christian M. Amsüss 
Closes: 1021216 1028138 1028406
Changes:
 arandr (0.1.11-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1028138, #1028406)
 - Fix Python 3.11 compatibility by replacing getargspec with
   getfullargspec
 .
   [ Ryan Kavanagh ]
   * Move python3-docutils from Build-Depends-Indep to Build-Depends
 (Closes: #1021216)
Checksums-Sha1:
 ea886a7c37b01cde540aa562cbb2a25fd5578d4b 1889 arandr_0.1.11-1.dsc
 b39c4e9a882a40d4a5185315f5d4de42afe3ed63 100603 arandr_0.1.11.orig.tar.gz
 25c7ed7204d313a620a8ec7c4b2451bb033a2ae5 4684 arandr_0.1.11-1.debian.tar.xz
 3e18dc8031ca17f0fda57a065fa8812360d1398e 6801 arandr_0.1.11-1_amd64.buildinfo
Checksums-Sha256:
 00dfeb783b54bebbbd5c9b32b6413c8f78f94ceeb6f4f4297fc4543ab54e2cb9 1889 
arandr_0.1.11-1.dsc
 e4cbbe3698bb812b395770870174be0094bbaeb391105a811f95f42eb182ae02 100603 
arandr_0.1.11.orig.tar.gz
 f502da51a2cdcd7a7a9d15b50e084aa9f706f18f01bdf897a6130fe77ae8c7ce 4684 
arandr_0.1.11-1.debian.tar.xz
 bd2e297b60d2870743201c680b92ec81e207f9f81b68de5930fca375738cd820 6801 
arandr_0.1.11-1_amd64.buildinfo
Files:
 e37421c360be90920c6108daa691ecd7 1889 x11 optional arandr_0.1.11-1.dsc
 f3535bc91118b66cc040ec9ccece4fce 100603 x11 optional arandr_0.1.11.orig.tar.gz
 fbf6d5c3c321ecdc888e1b2cab441482 4684 x11 optional 
arandr_0.1.11-1.debian.tar.xz
 155b5d39848b5ed9d465d71fb2d5eb49 6801 x11 optional 
arandr_0.1.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEP7FHOW9as2zJ9q6CWXuniu1D+jAFAmPBcWUACgkQWXuniu1D
+jBlgw//flWARP9lOTeaH1Jj8Z4I9F/MyOLSSaHq9gLsgyBrqJuvbp4+wGTUL9lm
jc9phRwjAL9VSd14EoigXyY1hvBEGfNFGX1UFcgfWshjiynam+xEr/42MEpaEaGU
4oqXM2mDqGbGPm27a2LqXZHLsc2FypKCgxhZG6+a0AFpjWjhvguPgaPqCXtSlTwD
M7cYVDXw4juVLQkizlonPGK19WoDX/ilp4hHj0Cm5fBpOBsyN9y34I1y63Lu4Iak
u3YIvwmcWZlBGXjpWjWsF9/1VOzzN6dJMuLMZTcSsXGLOTC6MYOLVtq9c8b8m18D
GHqZinUcyE+UwnV52ahjmtW/HEevj072XSC57nz22nG+eWqBesDPR0lV3c/nmJGD
ayioMGWCQjKHe01DicoLUCVlCWuGFPUGZsr3edBYckRNfJBfluIFeKI15oUBM9kt
vd6RibTvRgZrelt6BlGi7SmCPM2EE7fipnlrxTYqBFrt/6bkjCoD89jVViEgwqfI
g9DZzBK4IJ/opVeIs9LT4b6lfoM8kCjkZK2D2HOEYqIoTnAb3i/gSnKjZ4Rprk+b
DDAoEfJ5Eu2Uu9nKSiofNQkhwZMntczr50wOrZsTYH6HuvICZ6A2zJx0JZ6VCueS
AE6fYdPaTj/CsFw3CKQ9yrPkyIp3NSonFxT1++rXECuZovb+AKs=
=LmYm
-END PGP SIGNATURE End Message ---

Processed: Re: FTBFS: FAILED test-correct-notice and test-end-chop in copyright-tests.log due to new year 2023

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream fixed-upstream patch
Bug #1028607 [src:emacs] FTBFS: FAILED test-correct-notice and test-end-chop in 
copyright-tests.log due to new year 2023
Added tag(s) upstream, patch, and fixed-upstream.

-- 
1028607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028607: FTBFS: FAILED test-correct-notice and test-end-chop in copyright-tests.log due to new year 2023

[Vincent Lefevre]

Control: tags -1 upstream fixed-upstream patch

On 2023-01-13 16:07:09 +0100, Vincent Lefevre wrote:
> The cause may be that we are now in 2023 and the above tests
> are expecting 2022. Instead of expecting 2022, shouldn't they
> expect the current year?

This is what upstream did in

commit da77d70deeb2798693ec4f28a291befeb8e43989
Author: Mattias Engdegård 
Date:   2023-01-01 13:18:50 +0100

; * test/lisp/emacs-lisp/copyright-tests.el: Fix and future-safe.

I'm attaching this commit.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
commit da77d70deeb2798693ec4f28a291befeb8e43989
Author: Mattias Engdegård 
Date:   2023-01-01 13:18:50 +0100

; * test/lisp/emacs-lisp/copyright-tests.el: Fix and future-safe.

diff --git a/test/lisp/emacs-lisp/copyright-tests.el b/test/lisp/emacs-lisp/copyright-tests.el
index ef531174617..5f8b5c67896 100644
--- a/test/lisp/emacs-lisp/copyright-tests.el
+++ b/test/lisp/emacs-lisp/copyright-tests.el
@@ -59,7 +59,8 @@ test-end-chop
 "\nCopyright 2006, 2007, 2008 Foo Bar\n\n")
 (copyright-update)
 (buffer-substring (- (point-max) 42) (point-max
-"Copyright 2006, 2007, 2008, 2022 Foo Bar\n\n")))
+(format "Copyright 2006, 2007, 2008, %s Foo Bar\n\n"
+(format-time-string "%Y")
 
 (ert-deftest test-correct-notice ()
   (should (equal
@@ -70,7 +71,8 @@ test-correct-notice
(copyright-query nil))
(copyright-update))
  (buffer-string))
-   "Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n")))
+   (format "Copyright 2021 FSF\nCopyright 2021, %s FSF\n"
+   (format-time-string "%Y")
 
 (defmacro with-copyright-fix-years-test (orig result)
   `(let ((copyright-year-ranges t))

Bug#1028607: FTBFS: FAILED test-correct-notice and test-end-chop in copyright-tests.log due to new year 2023

[Vincent Lefevre]

Source: emacs
Version: 28.2+1-9
Severity: serious
Tags: ftbfs
Justification: ftbfs

When trying to rebuild emacs:

SUMMARY OF TEST RESULTS
---
Files examined: 375
Ran 5623 tests, 5545 results as expected, 2 unexpected, 76 skipped
1 files contained unexpected results:
  lisp/emacs-lisp/copyright-tests.log

and in this log file:

[...]
Test test-correct-notice condition:
(ert-test-failed
 ((should
   (equal
(with-temp-buffer ... ... ...)
"Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n"))
  :form
  (equal "Copyright 2021 FSF\nCopyright 2021, 2023 FSF\n" "Copyright 2021 
FSF\nCopyright 2021, 2022 FSF\n")
  :value nil :explanation
  (array-elt 38
 (different-atoms
  (51 "#x33" "?3")
  (50 "#x32" "?2")
   FAILED  2/3  test-correct-notice (0.000103 sec)
[...]
Test test-end-chop condition:
(ert-test-failed
 ((should
   (equal
(with-temp-buffer ...)
"Copyright 2006, 2007, 2008, 2022 Foo Bar\n\n"))
  :form
  (equal "Copyright 2006, 2007, 2008, 2023 Foo Bar\n\n" "Copyright 2006, 
2007, 2008, 2022 Foo Bar\n\n")
  :value nil :explanation
  (array-elt 31
 (different-atoms
  (51 "#x33" "?3")
  (50 "#x32" "?2")
   FAILED  3/3  test-end-chop (0.000154 sec)
[...]
2 unexpected results:
   FAILED  test-correct-notice
   FAILED  test-end-chop

This comes from test/lisp/emacs-lisp/copyright-tests.el, which has

(ert-deftest test-end-chop ()
  (should
   (equal
(with-temp-buffer
  (let ((copyright-query nil))
(insert (make-string (- copyright-limit 14) ?x) "\n"
"\nCopyright 2006, 2007, 2008 Foo Bar\n\n")
(copyright-update)
(buffer-substring (- (point-max) 42) (point-max
"Copyright 2006, 2007, 2008, 2022 Foo Bar\n\n")))

(ert-deftest test-correct-notice ()
  (should (equal
   (with-temp-buffer
 (dotimes (_ 2)
   (insert "Copyright 2021 FSF\n"))
 (let ((copyright-at-end-flag t)
   (copyright-query nil))
   (copyright-update))
 (buffer-string))
   "Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n")))

The cause may be that we are now in 2023 and the above tests
are expecting 2022. Instead of expecting 2022, shouldn't they
expect the current year?

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Running 3 tests (2023-01-13 15:46:41+0100, selector ‘(not (or (tag 
:expensive-test) (tag :unstable)))’)
   passed  1/3  test-copyright-update (0.372676 sec)
Test test-correct-notice backtrace:
  signal(ert-test-failed (((should (equal (with-temp-buffer (dotimes (
  ert-fail(((should (equal (with-temp-buffer (dotimes (_ 2) (insert "C
  #f(compiled-function () #)()
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name test-correct-notice :documentation ni
  ert-run-or-rerun-test(#s(ert--stats :selector (not (or (tag :expensi
  ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
  ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
  ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
  command-line-1(("-L" ":/home/vinc17/tmp/emacs-28.2+1/debian/build-sr
  command-line()
  normal-top-level()
Test test-correct-notice condition:
(ert-test-failed
 ((should
   (equal
(with-temp-buffer ... ... ...)
"Copyright 2021 FSF\nCopyright 2021, 2022 FSF\n"))
  :form
  (equal "Copyright 2021 FSF\nCopyright 2021, 2023 FSF\n" "Copyright 2021 
FSF\nCopyright 2021, 2022 FSF\n")
  :value nil :explanation
  (array-elt 38
 (different-atoms
  (51 "#x33" "?3")
  (50 "#x32" "?2")
   FAILED  2/3  test-correct-notice (0.000103 sec)
Test test-end-chop backtrace:
  signal(ert-test-failed (((should (equal (with-temp-buffer (let (...)
  ert-fail(((should (equal (with-temp-buffer (let ((copyright-query ni
  #f(compiled-function () #)()
  ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
  ert-run-test(#s(ert-test :name test-end-chop :documentation nil :bod
  ert-run-or-rer

Bug#1003007: marked as done (libvirt-php FTBFS with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 15:03:37 +
with message-id 
and subject line Bug#1003007: fixed in libvirt-php 0.5.6-5
has caused the Debian Bug report #1003007,
regarding libvirt-php FTBFS with PHP 8.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.)


-- 
1003007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt-php
Version: 0.5.5-3
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/fetch.php?pkg=libvirt-php&arch=amd64&ver=0.5.5-3%2Bb1&stamp=1641147267&raw=0

...
In file included from ../../src/libvirt-php.c:19:
../../src/libvirt-php.h:161:26: error: expected ‘;’, ‘,’ or ‘)’ before 
‘TSRMLS_DC’
  161 | void set_error(char *msg TSRMLS_DC);
  |  ^
../../src/libvirt-php.h:162:35: error: expected ‘;’, ‘,’ or ‘)’ before 
‘TSRMLS_DC’
  162 | void set_error_if_unset(char *msg TSRMLS_DC);
  |   ^
../../src/libvirt-php.h:163:1: warning: parameter names (without types) in 
function declaration
  163 | void reset_error(TSRMLS_D);
  | ^~~~
...
--- End Message ---
--- Begin Message ---
Source: libvirt-php
Source-Version: 0.5.6-5
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
libvirt-php, 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 1003...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libvirt-php 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, 13 Jan 2023 09:47:05 +0100
Source: libvirt-php
Binary: php-libvirt-php php-libvirt-php-all-dev php8.2-libvirt-php 
php8.2-libvirt-php-dbgsym
Architecture: source all amd64
Version: 0.5.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-libvirt-php - libvirt bindings for PHP
 php-libvirt-php-all-dev - libvirt bindings for PHP
 php8.2-libvirt-php - libvirt bindings for PHP
Closes: 1003007
Changes:
 libvirt-php (0.5.6-5) unstable; urgency=medium
 .
   * Fix FTBFS with PHP 8.x (Closes: #1003007)
   * Override source-is-missing lintian error
Checksums-Sha1:
 da37d33227af18ccaab25aa215f7d1720046ef69 2363 libvirt-php_0.5.6-5.dsc
 e37b949ccb38e38508deea70787496db63af7c63 386372 libvirt-php_0.5.6.orig.tar.xz
 90e4c9edbac3f0597ead8d6fb7db16ef0fc69532 5216 libvirt-php_0.5.6-5.debian.tar.xz
 406d5de7b1ffef1f63ac9aaeaa8c1bd4b4c5fd6e 10226 
libvirt-php_0.5.6-5_amd64.buildinfo
 8444b17b47b6168aa6d337c7e16e8343bec07b94 4112 
php-libvirt-php-all-dev_0.5.6-5_all.deb
 59dcfd73c0ddda89992ff64d626ebb17aca2f0ba 5020 php-libvirt-php_0.5.6-5_amd64.deb
 edb30c08b44ab781c111df18e6803a0c74cdfb7f 270736 
php8.2-libvirt-php-dbgsym_0.5.6-5_amd64.deb
 e1c89286c201a4399dd1e9fb81bc4c1e731bcc7d 69760 
php8.2-libvirt-php_0.5.6-5_amd64.deb
Checksums-Sha256:
 d8edca2258fe6450069acef9156d434b0ac78cb6dd717313ac0f66507fd42606 2363 
libvirt-php_0.5.6-5.dsc
 7916bd0bcd08befacaeba9c5c93ff98a10d41fe580e6b7db5e0bc649193d279f 386372 
libvirt-php_0.5.6.orig.tar.xz
 5b525be23a77880d2e59faeccc5c5f837cd45578567b104831d565c8bb81d420 5216 
libvirt-php_0.5.6-5.debian.tar.xz
 a36599c13bd6fefc4f5c3b3e0ca595ac365c52a2206ea27781df7cc1cbb8ef94 10226 
libvirt-php_0.5.6-5_amd64.buildinfo
 57e07616fdf4a8d8603965301c1ac4b53331c8479a6d04a29b66cb7b3d6df702 4112 
php-libvirt-php-all-dev_0.5.6-5_all.deb
 8b69949c429e961fca8cbac68571d1aec9598eb37c0c80a6d55976cb51a9fda4 5020 
php-libvirt-php_0.5.6-5_amd64.deb
 ed41ec9336eef6a0a4a81105aa122fb37626ac4feed8aaab104bd75b16b557f9 270736 
php8.2-libvirt-php-dbgsym_0.5.6-5_amd64.deb
 b9bbfe0a1c6458fa7d0160dd5943f0cff3ea993c8507d49cd54ddd67eb6b1ec8 69760 
php8.2-libvirt-php_0.5.6-5_amd64.deb
Files:
 261751bea2f6307bbb0e8389c57fe6bf 2363 php optional libvirt-php_0.5.6-5.dsc
 13f4614f7bdafc39b0cbf8dcb4b845b6 386372 php optional 
libvirt-php_0.5.6.orig.tar.xz
 895533b78e63fbbd0dd3609d4a89721f 5216 php optional 
libvirt-php_0.5.6-5.debian.tar.xz
 c3fb1b7f4ad87fc2a53d05ad73f7cd93 10226 php optional 
libvirt-php_0.5.6-5_amd64.buildinfo
 58cfb776be7ca184a

Bug#1022096: marked as done (e2fsprogs: Inaccurate copyright file)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 14:42:07 +
with message-id 
and subject line Bug#1022096: fixed in e2fsprogs 1.46.6~rc1-1.1
has caused the Debian Bug report #1022096,
regarding e2fsprogs: Inaccurate copyright file
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.)


-- 
1022096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: e2fsprogs
Severity: serious
Tags: patch
Version: 1.46.6~rc1-1

Hi Theodore,

There are several distribution licenses and copyright information not
mentioned, which are required by Debian Policy §12.5. I have attached
a patch fixing this, which also has the conversion of the copyright
files that are still in use to the machine-readable format.

Also attached is a patch for the upstream source (as you are also the
upstream maintainer) that applies a license requirement that I found
not to be present.

Thanks for your consideration,
BastianFrom 59c43fc9e933238789d4f6863adcf67c79679979 Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Mon, 17 Oct 2022 18:50:35 +0200
Subject: [PATCH] dict: Add modifification note required by license

The Kazlib license says:

"Permission is also granted to adapt this software to produce
derivative works, as long as the modified versions carry this copyright
notice and additional notices stating that the work has been modified."

Add the missing notice stating that the work has been modified.

Signed-off-by: Bastian Germann 
---
 lib/support/dict.c | 1 +
 lib/support/dict.h | 1 +
 2 files changed, 2 insertions(+)

diff --git a/lib/support/dict.c b/lib/support/dict.c
index ee0bf29b..93fdd0b2 100644
--- a/lib/support/dict.c
+++ b/lib/support/dict.c
@@ -16,6 +16,7 @@
  *
  * $Id: dict.c,v 1.40.2.7 2000/11/13 01:36:44 kaz Exp $
  * $Name: kazlib_1_20 $
+ * The work has been modified.
  */
 
 #define DICT_NODEBUG
diff --git a/lib/support/dict.h b/lib/support/dict.h
index f1382e1d..2d87cc00 100644
--- a/lib/support/dict.h
+++ b/lib/support/dict.h
@@ -16,6 +16,7 @@
  *
  * $Id: dict.h,v 1.22.2.6 2000/11/13 01:36:44 kaz Exp $
  * $Name: kazlib_1_20 $
+ * The work has been modified.
  */
 
 #ifndef DICT_H
-- 
2.30.2

From 040c3b9f3376c30bf0e711d4c729bc76556bc3d3 Mon Sep 17 00:00:00 2001
From: Viraj Shah 
Date: Mon, 17 Oct 2022 12:57:40 +0200
Subject: [PATCH] debian: make the copyright file machine readable
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Debian introduced a machine-readable copyright file a while ago.
Convert the general copyright file and the package-specific ones,
splitting the info that belongs to the package-specific ones.
Drop debian/e2fsck-static.copyright because that does not have a
file set that is very distinct from the general source; it would
just replicate parts of it.

This change adds some missing licenses that have to be documented
according to Debian Policy §12.5 as well as the copyright info for
many files.

Signed-off-by: Viraj Shah 
Signed-off-by: Bastian Germann 
---
 debian/copyright| 476 +++-
 debian/e2fsck-static.copyright  |  26 --
 debian/e2fsprogs-l10n.copyright |  52 ++--
 debian/libcom-err2.copyright| 143 --
 debian/libss2.copyright |  61 ++--
 5 files changed, 592 insertions(+), 166 deletions(-)
 delete mode 100644 debian/e2fsck-static.copyright

diff --git a/debian/copyright b/debian/copyright
index e6f46761..f18058eb 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,73 +1,403 @@
-This is the Debian GNU/Linux prepackaged version of the EXT2 file
-system utilities (e2fsck, mke2fs, etc.).  The EXT2 utilities were
-written by Theodore Ts'o  and Remy Card .
-
-Sources were obtained from http://sourceforge.net/projects/e2fsprogs
-
-Packaging is Copyright (c) 2003-2007 Theodore Ts'o 
- Copyright (c) 1997-2003 Yann Dirson 
-	 Copyright (c) 2001 Alcove 
-	 Copyright (c) 1997 Klee Dienes
-	 Copyright (c) 1995-1996 Michael Nonweiler 
-
-Upstream Author: Theodore Ts'o 
-
-Copyright notice:
-
-This package, the EXT2 filesystem utilities, are made available under
-the GNU General Public License version 2, with the exception of the
-lib/ext2fs and lib/e2p libraries, which are made available under the
-GNU Library General Public License Version 2, the lib/uuid library
-which is made available under a BSD-style license and the lib/et and
-lib/ss libraries which are made available under an MIT-style license.
-
-	Copyright (c) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 
-	2001, 2002

Bug#1027467: marked as done (dyssol: FTBFS without network access)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 14:41:43 +
with message-id 
and subject line Bug#1027467: fixed in dyssol 1.1.0+ds1-2
has caused the Debian Bug report #1027467,
regarding dyssol: FTBFS without network access
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.)


-- 
1027467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dyssol
Version: 1.1.0+ds1-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen on reproducible builds [1], dyssol 1.1.0+ds1-1 FTBFS
without network access.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/dyssol.html


(models_development: line 1596) broken
http://de.mathworks.com/help/matlab/cc-mx-matrix-library.html -
HTTPConnectionPool(host='de.mathworks.com', port=80): Max retries
exceeded with url: /help/matlab/cc-mx-matrix-library.html (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(  simulation: line  100) broken
https://computing.llnl.gov/projects/sundials/ida -
HTTPSConnectionPool(host='computing.llnl.gov', port=443): Max retries
exceeded with url: /projects/sundials/ida (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(  simulation: line   93) broken
https://computing.llnl.gov/projects/sundials -
HTTPSConnectionPool(host='computing.llnl.gov', port=443): Max retries
exceeded with url: /projects/sundials (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   units: line 1578) broken
https://doi.org/10.1007/978-3-662-52989-8_91 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.1007/978-3-662-52989-8_91 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   index: line   89) broken
https://doi.org/10.1007/978-3-030-45168-4_17 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.1007/978-3-030-45168-4_17 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   index: line   86) broken
https://doi.org/10.1016/j.apt.2018.12.007 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.1016/j.apt.2018.12.007 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   index: line   85) broken
https://doi.org/10.1016/j.powtec.2017.01.061 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.1016/j.powtec.2017.01.061 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   index: line   88) broken
https://doi.org/10.1016/j.softx.2020.100572 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.1016/j.softx.2020.100572 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(   index: line   87) broken
https://doi.org/10.3390/pr7080535 -
HTTPSConnectionPool(host='doi.org', port=443): Max retries exceeded
with url: /10.3390/pr7080535 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(000_get_started/get_started: line   20) broken
https://github.com/FlowsheetSimulation/Dyssol-open/releases -
HTTPSConnectionPool(host='github.com', port=443): Max retries exceeded
with url: /FlowsheetSimulation/Dyssol-open/releases (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(models_development: line9) broken
https://go.microsoft.com/fwlink/?LinkId=615448&clcid=0x409 -
HTTPSConnectionPool(host='go.microsoft.com', port=443): Max retries
exceeded with url: /fwlink/?LinkId=615448&clcid=0x409 (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(data: line   26) broken
https://www.hdfgroup.org/solutions/hdf5/ -
HTTPSConnectionPool(host='www.hdfgroup.org', port=443): Max retries
exceeded with url: /solutions/hdf5/ (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3]
Temporary failure in name resolution'))
(  simulation: li

Processed: Re: gnote: FTBFS: ../src/test/unit/datetimeutests.cpp:97:1: error: Failure in pretty_print_date: Expected Yesterday but was Dec 31 2022

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #1027529 [src:gnote] gnote: FTBFS: 
../src/test/unit/datetimeutests.cpp:97:1: error: Failure in pretty_print_date: 
Expected Yesterday but was Dec 31 2022
Severity set to 'minor' from 'serious'
> forwarded -1 https://gitlab.gnome.org/GNOME/gnote/-/issues/145
Bug #1027529 [src:gnote] gnote: FTBFS: 
../src/test/unit/datetimeutests.cpp:97:1: error: Failure in pretty_print_date: 
Expected Yesterday but was Dec 31 2022
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnote/-/issues/145'.

-- 
1027529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1027529: gnote: FTBFS: ../src/test/unit/datetimeutests.cpp:97:1: error: Failure in pretty_print_date: Expected Yesterday but was Dec 31 2022

[Jeremy Bicha]

Control: severity -1 minor
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnote/-/issues/145

I'm downgrading the severity since the package builds fine today;
might build fine every day except January 1.

Thank you,
Jeremy Bicha

Bug#1028438: otpclient: OTP values are all 000000

[eng . stk]

Hi!

The problem is not otpclient 3.1.1, but with libcotp12 1.2.7 which is  
broken (upstream released 1.2.8 with bugfix).


Meanwhile upstream released otpclient 3.1.2 and libcotp12 2.0.0, those  
should be merged instead.


Also libbaseencode1 has been deprecated.

Thanks.

Bug#1028438: otpclient: OTP values are all 000000

[eng . stk]

Hi!

The problem is not otpclient 3.1.1, but with libcotp12 1.2.7 which is  
broken (upstream released 1.2.8 with bugfix).


Meanwhile upstream released otpclient 3.1.2 and libcotp12 2.0.0, those  
shold be merged.


Also libbaseencode1 has been deprecated.

Thanks.

On Thu, 12 Jan 2023 13:26:12 + Francisco Vilmar Cardoso Ruviaro  
 wrote:


 > Hi Buster Keaton,

 > I just upgraded otpclient from 2.6.3-2 to 3.1.1-1 and everything went fine,

 > this error you reported did not occur*.

 >

 > Here is part of my /var/log/apt/history.log:

 > Commandline: apt install otpclient

 > Upgrade: otpclient-cli:amd64 (2.6.3-2, 3.1.1-1), otpclient:amd64  
(2.6.3-2, 3.1.1-1)


 >

 >

 > The fact that you have deleted otpclient config (~/.config/otpclient.cfg)

 > would not solve the problem, what we need to preserve would be the

 > ~/otpclient.enc file, if you have the backup file of ~/otpclient.enc you

 > can try to restore and test if the OTP Values are valid.

 >

 >

 > * I close the bug after checking what has been reported,

 >   so far I have not encountered any problems.

 >

 > Thanks!

 > --

 > Francisco Vilmar Cardoso Ruviaro 

 > 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00

Bug#1027652: mir-eval: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code 13

[Bastian Germann]

Now with the new numpy version, the build log also has additional stack traces 
ending in:

  File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 284, in 
__getattr__
raise AttributeError("module {!r} has no attribute "
AttributeError: module 'numpy' has no attribute 'float'

Bug#1026069: marked as done (Cannot find symbols during build)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 14:02:44 +0100
with message-id 
and subject line Re: scrcpy: Bug#1026069: Cannot find symbols during build
has caused the Debian Bug report #1026069,
regarding Cannot find symbols during build
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.)


-- 
1026069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scrcpy
Version: 1.24-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Running `apt build-dep scrcpy` and `fakeroot debian/rules binary` 
results in plenty of unresolvable symbols.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages scrcpy depends on:
ii  libavcodec59   7:5.1.2-1
ii  libavdevice59  7:5.1.2-1
ii  libavformat59  7:5.1.2-1
ii  libavutil577:5.1.2-1
ii  libc6  2.36-6
ii  libsdl2-2.0-0  2.26.0+dfsg-1
ii  libusb-1.0-0   2:1.0.26-1
ii  scrcpy-server  1.24-1

Versions of packages scrcpy recommends:
ii  adb  1:29.0.6-21

scrcpy suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
--- End Message ---
--- Begin Message ---

Regarding the following, written by "Bernhard Übelacker" on 2023-01-13 at 11:51 
Uhr +0100:

Can you still reproduce it?


Also no, thanks for following up. I guess my computer had a bad day 
back then…


--
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
it is better to have loft and lost

than to never have loft at all.
 -- groucho marx
--- End Message ---

Bug#1025498: marked as done (Links to old libavdevice58)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 14:01:30 +0100
with message-id 
and subject line Re: scrcpy: Bug#1025498: Links to old libavdevice58
has caused the Debian Bug report #1025498,
regarding Links to old libavdevice58
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.)


-- 
1025498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scrcpy
Version: 1.24-1
Severity: grave

The package depends on libavdevice59, but it's apparently built 
against libavdevice58:

lotus:~% ldd =scrcpy | grep libavdevice
  libavdevice.so.58 => not found

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-rc7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages scrcpy depends on:
ii  libavcodec59   7:5.1.2-1
ii  libavdevice59  7:5.1.2-1
ii  libavformat59  7:5.1.2-1
ii  libavutil577:5.1.2-1
ii  libc6  2.36-6
ii  libsdl2-2.0-0  2.26.0+dfsg-1
ii  libusb-1.0-0   2:1.0.26-1
ii  scrcpy-server  1.24-1

Versions of packages scrcpy recommends:
ii  adb  1:29.0.6-21

scrcpy suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
--- End Message ---
--- Begin Message ---

Regarding the following, written by "Bernhard Übelacker" on 2023-01-13 at 11:33 
Uhr +0100:

can you still reproduce this issue?


No, I am glad you asked. I have no idea what happened, but it works 
now.


Btw, `=scrcpy` is a zsh-specific way to do `$(command -v scrcpy)`.

Thanks for following up. Closing…

--
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"it is the mark of an educated mind

 to be able to entertain a thought
 without accepting it."
  -- aristoteles
--- End Message ---

Bug#1025816: libde265: several CVE's, proposed possibly patch

[Tobias Frost]

Control: tags -1 patch

Hi,

A while ago I've debugged into this issue and proposed a patch upstream. 
Unfortunatly there is no feedback from upstream,
but I'm confident that my patch will at least improve things; The very least 
they stop the upstream provided pocs to stop
working for those CVEs:

The PRs are those:
- https://github.com/strukturag/libde265/pull/365
- https://github.com/strukturag/libde265/pull/366
- https://github.com/strukturag/libde265/pull/372 (this patch is not strictly a
  fix for the CVEs, but should mitigate situations where a legitimate stream
  would be rejected to be decoded due to the CVE mitigations, namely if the
  stream just re-sends the "sequence parameter set", which is allowed by the
  standard.)

My analysis of the issue can be found here:
- https://github.com/strukturag/libde265/issues/345#issuecomment-1346406079

With the patch attached, all the pocs mentioned in the respective upstream 
issues cease to work.
Additionally I've tested the patched decoder on several videos to ensure that 
there is nothing broken there,
so I'm confident that my patch improves the situation.

This is the list of the CVEs this patch addresses:

CVE-2022-43235
CVE-2022-43236
CVE-2022-43237
CVE-2022-43238
CVE-2022-43239
CVE-2022-43240
CVE-2022-43241
CVE-2022-43242
CVE-2022-43243
CVE-2022-43244
CVE-2022-43245
CVE-2022-43248
CVE-2022-43249
CVE-2022-43250
CVE-2022-43252
CVE-2022-43253

crashes this fixes too, without CVE (or where I could not match them):
https://github.com/strukturag/libde265/issues/350
https://github.com/strukturag/libde265/issues/351
https://github.com/strukturag/libde265/issues/353

Note that there are older CVEs as well; I did not check if the patch would also 
fix those due to ENOTIME.
Of course, I will do so, when this patch results in /me preparing an upload 
either for sid*, stable-security**, LTS*** or ELTS***.
(I'm hoping for feedback from upstream, but if that times out, I will use my 
patches for said uploads.)

In the meantime, there has been additional CVES reported. I've did not check 
those either yet. (e.g CVE-2022-47655 and two further crashes without 
mentioning of a CVE)

* as NMU, if required, of if the maintainer is not objecting
** if ok with the security  team
*** as LTS/ELTS contributor for Freexian.

-- 
tobi

Processed: libde265: several CVE's, proposed possibly patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1025816 [src:libde265] libde265: CVE-2022-43243 CVE-2022-43248 
CVE-2022-43253
Added tag(s) patch.

-- 
1025816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1019648: ruby-premailer-rails: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:

[Santiago Vila]

Hi. I've just build ruby-premailer-rails version 1.10.3-3 successfully in 
unstable today.

I believe some build-dependency might have changed behaviour between the date 
this
was reported and now. Could you please double-check?

Thanks.

Processed: Reassigning to gnustep-gui

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1028185 libgnustep-gui-dev 0.30.0-1
Bug #1028185 [src:agenda.app] src:agenda.app: FTBFS with gnustep-gui/0.30.0
Bug reassigned from package 'src:agenda.app' to 'libgnustep-gui-dev'.
No longer marked as found in versions agenda.app/0.46-2.
Ignoring request to alter fixed versions of bug #1028185 to the same values 
previously set
Bug #1028185 [libgnustep-gui-dev] src:agenda.app: FTBFS with gnustep-gui/0.30.0
Marked as found in versions gnustep-gui/0.30.0-1.
> retitle 1028185 NSSound.h unusable as single #import
Bug #1028185 [libgnustep-gui-dev] src:agenda.app: FTBFS with gnustep-gui/0.30.0
Changed Bug title to 'NSSound.h unusable as single #import' from 
'src:agenda.app: FTBFS with gnustep-gui/0.30.0'.
> tags 1028185 = pending
Bug #1028185 [libgnustep-gui-dev] NSSound.h unusable as single #import
Added tag(s) pending; removed tag(s) sid, ftbfs, and bookworm.
> affects 1028185 src:agenda.app
Bug #1028185 [libgnustep-gui-dev] NSSound.h unusable as single #import
Added indication that 1028185 affects src:agenda.app
> severity 1028185 serious
Bug #1028185 [libgnustep-gui-dev] NSSound.h unusable as single #import
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1028185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1028592: tagcoll2 2.0.14-2 fails to build on sid

[Holger Levsen]

Package: tagcoll2
Version: 2.0.14-2
Severity: serious
Justification: FTBFS

tagcoll2 migrated to bookworm today but fails to build from source in current 
sid:

I: Building the package
I: Running cd /build/tagcoll2-2.0.14/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us 
-uc  && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" 
dpkg-genchanges -S  > ../tagcoll2_2.0.14-2_source.changes
dpkg-buildpackage: info: source package tagcoll2
dpkg-buildpackage: info: source version 2.0.14-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andrey Rahmatullin 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_clean
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in 
use)
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building tagcoll2 using existing 
./tagcoll2_2.0.14.orig.tar.gz
dpkg-source: info: building tagcoll2 in tagcoll2_2.0.14-2.debian.tar.xz
dpkg-source: info: building tagcoll2 in tagcoll2_2.0.14-2.dsc
 debian/rules build
dh build
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/tagcoll2-2.0.14'
dh_auto_configure -- --disable-shared --with-pic --disable-docs
dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
(level 9 in use)
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --disable-shared --with-pic --disable-docs
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make sets $(MAKE)... (cached) yes
checking for style of include used by make... GNU
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking for library containing strerror... none required
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) none
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... none
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... none needed
checking whether yytext is a pointer... no
checking for bison... bison -y
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranl

Bug#997329: marked as done (dnsviz: FTBFS: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 11:36:55 +
with message-id 
and subject line Bug#997329: fixed in dnsviz 0.9.4-1
has caused the Debian Bug report #997329,
regarding dnsviz: FTBFS: _gtk_style_provider_private_get_settings: assertion 
'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
997329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnsviz
Version: 0.9.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> inkscape --batch-process --export-width=25 
> --export-filename=images/warning.png src/warning.svg
> 
> ** (process:18603): WARNING **: 07:37:50.591: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> Emergency save activated!
> Emergency save completed. Inkscape will close now.
> If you can reproduce this crash, please file a bug at 
> https://inkscape.org/report
> with a detailed description of the steps leading to the crash, so we can fix 
> it.
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> 
> (inkscape:18603): Gtk-CRITICAL **: 07:37:50.598: 
> _gtk_style_provider_private_get_settings: assertion 
> 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
> make[2]: *** [Makefile:23: images/warning.png] Segmentation fault
> make[2]: Leaving directory '/<>/doc'
> make[1]: *** [debian/rules:6: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/dnsviz_0.9.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dnsviz
Source-Version: 0.9.4-1
Done: Ondřej Surý 

We believe that the bug you reported is fixed in the latest version of
dnsviz, 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.
Ondřej Surý  (supplier of updated dnsviz 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, 13 Jan 2023 12:01:44 +0100
Source: dnsviz
Architecture: source
Version: 0.9.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team 
Changed-By: Ondřej Surý 
Closes: 997329
Changes:
 dnsviz (0.9.4-1) unstable; urgency=medium
 .
   * New upstream version 0.9.4
   * Fix inscape invocation (Closes: #997329)
- Remove deprecated -z/--without-gui
- Replace -e with --export-type=png
- Set HOME to /var/tmp, so .config can be created
Checksums-Sha1:
 9ab41602fc1908dbbb5320648c118d9f24ca0ac0 2151 dnsviz_0.9.4-1.dsc
 06ae5f1214f359692f3e1022042ebd75922ce776 388809 dnsviz_0.9.4.orig.tar.gz
 4ffb62ab86365cbdd68d3950114fa17b07952334 7077 dnsviz_0.9.4-1.debian.tar.gz
 758d1670a6135ee9dbfcee08b80dc7cd53796d6e 12833 dnsviz_0.9.4-1_am

Bug#1026069: scrcpy: Bug#1026069: Cannot find symbols during build

[Bernhard Übelacker]

On Wed, 14 Dec 2022 10:07:27 +0100 martin f krafft  
wrote:

Package: scrcpy
Version: 1.24-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Running `apt build-dep scrcpy` and `fakeroot debian/rules binary` 
results in plenty of unresolvable symbols.



Hello Martin,
I could not reproduce an issue inside a minimal unstable VM.

The package builds with "fakeroot debian/rules binary" and
"dpkg-buildpackage" without showing an error.

Can you still reproduce it?

Kind regards,
Bernhard

Bug#1028090: marked as done (odoo: contains non-free fonts)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 10:40:55 +
with message-id 
and subject line Bug#1028090: fixed in odoo 14.0.0+dfsg.4-1
has caused the Debian Bug report #1028090,
regarding odoo: contains non-free fonts
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.)


-- 
1028090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: odoo
Severity: serious
Version: 14.0.0+dfsg.3-1.1

odoo contains at least 2 non-free fonts: mnmliconsv21 and Rhesmanisa.
See the upstream bugs
https://github.com/odoo/odoo/issues/6382
https://github.com/odoo/odoo/issues/109361

Please repack to get rid of these fonts.
--- End Message ---
--- Begin Message ---
Source: odoo
Source-Version: 14.0.0+dfsg.4-1
Done: Sebastien Delafond 

We believe that the bug you reported is fixed in the latest version of
odoo, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated odoo 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, 13 Jan 2023 10:34:53 +0100
Source: odoo
Architecture: source
Version: 14.0.0+dfsg.4-1
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Sebastien Delafond 
Closes: 1028090
Changes:
 odoo (14.0.0+dfsg.4-1) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * Remove non-free fonts (Closes: #1028090)
Checksums-Sha1:
 da32d04e15622c2953db099e69b9551eda6b66dc 1621 odoo_14.0.0+dfsg.4-1.dsc
 5afd821a2a6e684115cb3249b8446330a3c9a73f 71700708 
odoo_14.0.0+dfsg.4.orig.tar.xz
 8e5355a1f2ec2992cbdd4042dba49fd9637f57b2 28216 
odoo_14.0.0+dfsg.4-1.debian.tar.xz
 32f42147842f3ad0bde9e2ab3c1e79bf569be45d 6760 
odoo_14.0.0+dfsg.4-1_amd64.buildinfo
Checksums-Sha256:
 d816ab720043add9726f838e930bfdb297587838092b56175dbeb4a34a0ccda3 1621 
odoo_14.0.0+dfsg.4-1.dsc
 a47a6199176f8be93619d291cd4a1ce3154e07090f8b88435cbf5bab7b8f7e5b 71700708 
odoo_14.0.0+dfsg.4.orig.tar.xz
 8e18dc622b64ddf3d99ba75605eb7b4c871da990e7db3f60fedc5e2a5e51197f 28216 
odoo_14.0.0+dfsg.4-1.debian.tar.xz
 07fd7ddfaa28de31aea8fc265714a8fc611c0d3655368094711320ca38cf7520 6760 
odoo_14.0.0+dfsg.4-1_amd64.buildinfo
Files:
 8b5a4e713043a891dcbaba705b97daf6 1621 net optional odoo_14.0.0+dfsg.4-1.dsc
 a89928d70b3af40593b4f106f9c1880c 71700708 net optional 
odoo_14.0.0+dfsg.4.orig.tar.xz
 822b2718fb87167f6608bd83eeaebd20 28216 net optional 
odoo_14.0.0+dfsg.4-1.debian.tar.xz
 4a39b27ddb7fc1bdb4b71ed5aaf99342 6760 net optional 
odoo_14.0.0+dfsg.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAmPBK18ACgkQEL6Jg/PV
nWSDSwf/d49RW0NNJt+emnqseJ/H3UgpJ738uZBO5IjBPIx4UxAyNdMPySrl3DY6
UAOADcjnhiWLZBBtvIE1Ea6cx7dIsB1SomqvL6vWjG1RrQTXMtkR3de9lfkEEziB
UPtIG4HgWVqajftZw6inbWOtxtEU23mLgSYVL5gKFv5Gx+E7LXwUh1S2ClHo2jm7
ZMzllBYrWWXSB0XUDoOdNOrdpfqR1L1nefJlrdvC7F+7hAMFPrONAkB0zobnwSAw
P9Alf9zDJq9ByyYylL9ieZfgR6aoCK1gswyXxAX6PatOpB9EpoN5//M0/ImaG2IY
50/8h5h586vOwHnAXo7tnOELQQDjwQ==
=ELu2
-END PGP SIGNATURE End Message ---

Bug#1025498: scrcpy: Bug#1025498: Links to old libavdevice58

[Bernhard Übelacker]

On Mon, 5 Dec 2022 21:33:03 +0100 martin f krafft  wrote:

Package: scrcpy
Version: 1.24-1
Severity: grave

The package depends on libavdevice59, but it's apparently built 
against libavdevice58:


lotus:~% ldd =scrcpy | grep libavdevice
  libavdevice.so.58 => not found



Hello Martin,
can you still reproduce this issue?

I have installed scrcpy inside a minimal unstable VM,
and receive the output below [1].

Also the build log [2] seems to show that libavdevice59
was installed during package build.

Your ldd shows "=scrcpy" instead of an absolute path,
does it really point to the binary from the package?

Kind regards,
Bernhard


[1]
benutzer@debian:~$ ldd /usr/bin/scrcpy | grep libavdevice
libavdevice.so.59 => /lib/x86_64-linux-gnu/libavdevice.so.59 
(0x7fa06f9cd000)
benutzer@debian:~$ dpkg -l | grep scrcpy
ii  scrcpy1.24-1 amd64  
  Display and control your Android device
ii  scrcpy-server 1.24-1 all
  Display and control your Android device - server binary


[2] 
https://buildd.debian.org/status/fetch.php?pkg=scrcpy&arch=amd64&ver=1.24-1&stamp=1658088686&raw=0
Unpacking libavdevice59:amd64 (7:5.0.1-3+b1) ...
Unpacking libavdevice-dev:amd64 (7:5.0.1-3+b1) ...

Processed: Bug#1027229 marked as pending in mlpy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1027229 [src:mlpy] mlpy: autopkgtest fail with numpy/1.24.1
Added tag(s) pending.

-- 
1027229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1027229: marked as pending in mlpy

[Bas Couwenberg]

Control: tag -1 pending

Hello,

Bug #1027229 in mlpy 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/science-team/mlpy/-/commit/fc8df840c199ab13ff8a804020c4181449d83c81


Add patch to fix test failure with Numpy 1.24. (closes: #1027229)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1027229

Bug#1028533: marked as done (symfony: FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 09:44:15 +
with message-id 
and subject line Bug#1028533: fixed in symfony 5.4.18+dfsg-3
has caused the Debian Bug report #1028533,
regarding symfony: FTBFS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symfony
Version: 5.4.18+dfsg-2
Severity: serious
Tags: ftbfs
Justification: ftbfs

Dear maintianer(s),

Your most recent upload of symfony FTBFS. The test suite fails.

Paul

https://buildd.debian.org/status/fetch.php?pkg=symfony&arch=all&ver=5.4.18%2Bdfsg-2&stamp=1673508040&raw=0
--- End Message ---
--- Begin Message ---
Source: symfony
Source-Version: 5.4.18+dfsg-3
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
symfony, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated symfony 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: Fri, 13 Jan 2023 08:47:36 +0100
Source: symfony
Architecture: source
Version: 5.4.18+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1028533
Changes:
 symfony (5.4.18+dfsg-3) unstable; urgency=medium
 .
   * Drop (data) tests failing with PHP 8.2 (Closes: #1028533)
Checksums-Sha1:
 c24573726a4f9fc2043d3f4f60727008e16c16f1 13201 symfony_5.4.18+dfsg-3.dsc
 17b3c6f0ace2dc5a6898db53a5e96911bc8d36db 58556 
symfony_5.4.18+dfsg-3.debian.tar.xz
 fe952363a96bf020b19a1dcbe0ab92f92ce4fc8b 53656 
symfony_5.4.18+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 5db5c23c9782a4305ea5cc83441791bcc62003b970498a34343cacbfc2be544e 13201 
symfony_5.4.18+dfsg-3.dsc
 7ad7ded1eacd248b1a51f11390cf216bf969fb501414bbe2725ec7c8d0e6d15f 58556 
symfony_5.4.18+dfsg-3.debian.tar.xz
 4afd759455ac5d28f4f65ad79b00291f41447c35650815979565f72724d4b239 53656 
symfony_5.4.18+dfsg-3_amd64.buildinfo
Files:
 50f2654f9885117d8dfc0baff0cee9ec 13201 php optional symfony_5.4.18+dfsg-3.dsc
 357efc2305a4772bdb1f96ae16d1ea21 58556 php optional 
symfony_5.4.18+dfsg-3.debian.tar.xz
 2815ab10b1317bd02d4a3260e8b0ad3c 53656 php optional 
symfony_5.4.18+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmPBEKUSHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08/RAIALJ+arf0EFJJElNP9LxDzbTqd11IL1ax
zgxycTpsWrXZC1bfH33R65iR4ht8i5vAdjCi1APnsiG9vdCtYc++zaV9eLpyRN4m
IpHLQlW+2LzHI7hKuE2YYdQZZ/kFMWWclDJQmoIK7xXwJ3mUDEnl3qLxSRUX4esr
r22jMWVyEz8IYY7fIRBLAanZ3vSQ4wLHxECx4QSeJdZkVcf2Kb3/FAZIHu+JeOSG
CMwln5SVwSdFZ43Yo0YGPUo68LHY9pjWIMUGQLLIqtdpWWsms0twIw2hfWTV563N
xtr1l+NIw/5E1SYjvX38CGUSA9NRhoJ6iW/+qoRbHJUGlIVOeUdfh8I=
=M4Ar
-END PGP SIGNATURE End Message ---

Bug#948075: marked as done (possible licensing issues)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 09:54:04 +0100
with message-id <02b09b68-ca37-40c1-9748-513672548...@isc.org>
and subject line Resolved by relicensing to BSD-2
has caused the Debian Bug report #948075,
regarding possible licensing issues
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.)


-- 
948075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-smbclient
Severity: serious
Usertags: license-violation

php-smbclient links against both libsmbclient (which is GPLv3) and php
(licensed under the PHP3.01 license).

According to both the FSF
(https://www.gnu.org/licenses/license-list.en.html#PHP-3.01) and the
guidance from the ftp-masters (https://ftp-master.debian.org/php-license.html)
these licenses are incompatible.
--- End Message ---
--- Begin Message ---
Version: 1.0.6-8

Hi,

the smbclient extension has been relicenced under BSD-2,
so this issue has been resolved.

Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org

My working hours and your working hours may be different. Please do not feel 
obligated to reply outside your normal working hours.--- End Message ---

Bug#1027261: marked as done (src:cl-sql: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2023 08:35:16 +
with message-id 
and subject line Bug#1027261: fixed in cl-sql 6.7.2-1.1
has caused the Debian Bug report #1027261,
regarding src:cl-sql: fails to migrate to testing for too long: uploader built 
arch:all binaries
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.)


-- 
1027261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: cl-sql
Version: 6.7.1-3
Severity: serious
Control: close -1 6.7.2-1
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:cl-sql 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.


Your package is only 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.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=cl-sql



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cl-sql
Source-Version: 6.7.2-1.1
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
cl-sql, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated cl-sql 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, 29 Dec 2022 08:07:41 +0100
Source: cl-sql
Architecture: source
Version: 6.7.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Kevin M. Rosenberg 
Changed-By: Paul Gevers 
Closes: 1027261
Changes:
 cl-sql (6.7.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1027261)
Checksums-Sha1:
 41e51f62c19c288275023c1fbd3a4480b67002cd 2134 cl-sql_6.7.2-1.1.dsc
 047c070201430f9abc14ebe3f9787048b8e1666f 10428 cl-sql_6.7.2-1.1.debian.tar.xz
Checksums-Sha256:
 969094530c1242f723008db6d2768429f0e56be1e2bb7bd532fb9782b6ffa301 2134 
cl-sql_6.7.2-1.1.dsc
 ff3ae07f53957231903d4d74105e66d909ffe72777f7a0f510cd857dddccb75d 10428 
cl-sql_6.7.2-1.1.debian.tar.xz
Files:
 16efd66c8ebc736a4eac9a5cb1b492c0 2134 lisp optional cl-sql_6.7.2-1.1.dsc
 153af8e83515f0db0f9a68ba93c2efe4 10428 lisp optional 
cl-sql_6.7.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmOtPNIACgkQnFyZ6wW9
dQrEoAf6AiFi65zEL7fg8uKhYKSaA5kfx1EocR4PMVLmZL8V+Ksm0xm0VmhHcKpR
f7Hc7cqSkfpWMHJXNLHMiLU8Sg3p4oDP8cS8cQYlylKATMlrdOWzZFuAPtbXPb52
C7iyqu/69zjyGZmwWmJfoWI/5UUhnTy/Mgqnfw5jcDuqy4sCV6orrwIRLrFvw+OD
XOJK+bbBFXTxJVGrXrVJ8uvAJLBf6jJA4/gzGGrl7oudh06Bq7/Tlizj302dI5RC
DF+YjBxsamSySXoRNeEFrwNPSwJj/g67+Pd6OFxWQZV9KWBYsJtZZwANUyxg+RlG
oN4LzJDrct6+j9PDowUp5GimygP6AQ==
=fLIV
-END PGP SIGNATURE End Message ---