Bug#1000220: marked as done (dicomscope: error: cannot bind non-const lvalue reference of type ‘std::__cxx11::list >::const_iterator&’ to an rvalue of type ‘std::__cxx11::list

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 07:48:33 +
with message-id 
and subject line Bug#1000220: fixed in dcmtk 3.6.6-3
has caused the Debian Bug report #1000220,
regarding dicomscope: error: cannot bind non-const lvalue reference of type 
‘std::__cxx11::list >::const_iterator&’ to an rvalue 
of type ‘std::__cxx11::list >::const_iterator’
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.)


-- 
1000220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dicomscope
Version: 3.6.0-22
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| cd /<>/obj-x86_64-linux-gnu/interface/libsrc && /usr/bin/c++ 
-DHAVE_CONFIG_H -DHAVE_STRSTREAM_H -DNDEBUG -DjInterface_EXPORTS 
-I/<>/interface/include -I/usr/lib/jvm/default-java/include 
-I/usr/lib/jvm/default-java/include/linux -I/usr/include/dcmtk/dcmpstat 
-I/usr/include/dcmtk/dcmsr -I/usr/include/dcmtk/dcmjpeg -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT 
interface/libsrc/CMakeFiles/jInterface.dir/DSRImageValue.cpp.o -MF 
CMakeFiles/jInterface.dir/DSRImageValue.cpp.o.d -o 
CMakeFiles/jInterface.dir/DSRImageValue.cpp.o -c 
/<>/interface/libsrc/DSRImageValue.cpp
| In file included from /usr/include/dcmtk/dcmsr/dsrscogr.h:30,
|  from /usr/include/dcmtk/dcmsr/dsrscovl.h:30,
|  from /usr/include/dcmtk/dcmsr/dsrcitem.h:33,
|  from /usr/include/dcmtk/dcmsr/dsrdocst.h:33,
|  from /usr/include/dcmtk/dcmsr/dsrdoctr.h:29,
|  from /usr/include/dcmtk/dcmsr/dsrdoc.h:29,
|  from /<>/interface/include/jInterface.h:49,
|  from /<>/interface/libsrc/DSRImageValue.cpp:39:
| /usr/include/dcmtk/dcmsr/dsrtlist.h: In instantiation of ‘OFCondition 
DSRListOfItems::removeItem(size_t) [with T = int; size_t = long unsigned 
int]’:
| /<>/interface/libsrc/DSRImageValue.cpp:313:49:   required from 
here
| /usr/include/dcmtk/dcmsr/dsrtlist.h:303:30: error: cannot bind non-const 
lvalue reference of type ‘std::__cxx11::list 
>::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’
|   303 | if (gotoItemPos(idx, iterator))
|   |  ^~~~
| In file included from /usr/include/c++/11/list:63,
|  from /usr/include/dcmtk/ofstd/oflist.h:56,
|  from /usr/include/dcmtk/ofstd/ofstd.h:28,
|  from /usr/include/dcmtk/ofstd/offile.h:30,
|  from /usr/include/dcmtk/dcmdata/dcistrma.h:28,
|  from /usr/include/dcmtk/dcmdata/dctk.h:30,
|  from /usr/include/dcmtk/dcmpstat/dcmpstat.h:27,
|  from /usr/include/dcmtk/dcmpstat/dvpstat.h:27,
|  from /usr/include/dcmtk/dcmpstat/dviface.h:32,
|  from /<>/interface/include/jInterface.h:42,
|  from /<>/interface/libsrc/DSRImageValue.cpp:39:
| /usr/include/c++/11/bits/stl_list.h:286:7: note:   after user-defined 
conversion: ‘std::_List_const_iterator<  
>::_List_const_iterator(const iterator&) [with _Tp = int; 
std::_List_const_iterator<  >::iterator = 
std::_List_const_iterator::iterator]’
|   286 |   _List_const_iterator(const iterator& __x) _GLIBCXX_NOEXCEPT
|   |   ^~~~
| In file included from /usr/include/dcmtk/dcmsr/dsrscogr.h:30,
|  from /usr/include/dcmtk/dcmsr/dsrscovl.h:30,
|  from /usr/include/dcmtk/dcmsr/dsrcitem.h:33,
|  from /usr/include/dcmtk/dcmsr/dsrdocst.h:33,
|  from /usr/include/dcmtk/dcmsr/dsrdoctr.h:29,
|  from /usr/include/dcmtk/dcmsr/dsrdoc.h:29,
|  from /<>/interface/include/jInterface.h:49,
|  from /<>/interface/libsrc/DSRImageValue.cpp:39:
| /usr/include/dcmtk/dcmsr/dsrtlist.h:320:64: note:   initializing argument 2 
of ‘OFBool DSRListOfItems::gotoItemPos(size_t, typename 
std::__cxx11::list::const_iterator&) const [with T = int; OFBool = bool; 
size_t = long unsigned int; typename std::__cxx11::list::const_iterator = 
std::__cxx11::list >::const_iterator]’
|   320 |OFLIST_TYPENAME OFListConstIterator(T) 
) const
|   |^
| make[3]: *** [interface/libsrc/CMakeFiles/jInterface.dir/build.make:135: 

Processed: Bug#1000220 marked as pending in dcmtk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1000220 [src:dcmtk] dicomscope: error: cannot bind non-const lvalue 
reference of type ‘std::__cxx11::list 
>::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’
Ignoring request to alter tags of bug #1000220 to the same tags previously set

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

Bug#1000220: marked as pending in dcmtk

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

Bug #1000220 in dcmtk 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/med-team/dcmtk/-/commit/48c24b0f258b9503053b0583ce4c7cf84427c72c


d/patches: Fix compilation of dicomscope. Closes: #1000220


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000220

Bug#1000435: Matplotlib crashes on mips64el in lines.py

[Ole Streicher]

Source: matplotlib
Severity: serious
Version: 3.5.0-1
Control: affects -1 yt
Control: affects -1 astropy

With the new matplotlib version, I now have crashes with a segmentation fault
in at least two of my packages on mips64el, which cause a FTBFS: yt and
astropy. On both packages, the crash happens here:

--8<
  File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in draw
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in draw
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in draw
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in 
_draw_list_compositing_images
  File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 in 
draw
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in 
_draw_list_compositing_images
  File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in draw
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in 
draw_wrapper
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", 
line 436 in draw
--8<

Build log on Astropy: 
https://buildd.debian.org/status/fetch.php?pkg=astropy=mips64el=5.0-1=1637626067=0

Build log on yt: 
https://buildd.debian.org/status/fetch.php?pkg=yt=mips64el=4.0.1-3=1637588650=0

This happens on both Python 3.9 and 3.10. The I will try to create a stacktrace 
for it.

Processed: Matplotlib crashes on mips64el in lines.py

[Debian Bug Tracking System]

Processing control commands:

> affects -1 yt
Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py
Added indication that 1000435 affects yt
> affects -1 astropy
Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py
Added indication that 1000435 affects astropy

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

Bug#999519: xrayutilities: diff for NMU version 1.7.1-2.1

[Dominik Kriegner]

Dear Debian team,

I think the patch can be used like this. I'll also release a new upstream
version with this patch hopefully today.

kind regards
Dominik

On Tue, Nov 23, 2021 at 2:48 AM Stefano Rivera  wrote:

> Control: tags 999519 + patch
> Control: tags 999519 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for xrayutilities (versioned as 1.7.1-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Also filed as:
> https://salsa.debian.org/science-team/python-xrayutilities/-/merge_requests/1
>
> Regards,
>
> SR
>

Bug#1000412: marked as done (poetry-core: autopkgtest regression: No such file or directory: 'git')

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 06:18:39 +
with message-id 
and subject line Bug#1000412: fixed in poetry-core 1.0.7-2
has caused the Debian Bug report #1000412,
regarding poetry-core: autopkgtest regression: No such file or directory: 'git'
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.)


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

Source: poetry-core
Version: 1.0.7-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
poetry-corefrom testing1.0.7-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=poetry-core

https://ci.debian.net/data/autopkgtest/testing/amd64/p/poetry-core/16881615/log.gz


=== FAILURES 
===
__ test_git_clone_raises_error_on_invalid_repository 
___


def test_git_clone_raises_error_on_invalid_repository():
with pytest.raises(GitError):

  Git().clone("-u./payload", Path("foo"))


tests/vcs/test_vcs.py:273: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/poetry/core/vcs/git.py:228: in __init__

self._config = GitConfig(requires_git_presence=True)
/usr/lib/python3/dist-packages/poetry/core/vcs/git.py:206: in __init__
subprocess.check_output(
/usr/lib/python3.9/subprocess.py:424: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
/usr/lib/python3.9/subprocess.py:505: in run
with Popen(*popenargs, **kwargs) as process:
/usr/lib/python3.9/subprocess.py:951: in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
args = ['git', 'config', '-l'], executable = b'git', preexec_fn = None
close_fds = True, pass_fds = (), cwd = None, env = None, startupinfo = None
creationflags = 0, shell = False, p2cread = -1, p2cwrite = -1, c2pread = 11
c2pwrite = 12, errread = -1, errwrite = 12, restore_signals = True, gid 
= None

gids = None, uid = None, umask = -1, start_new_session = False

def _execute_child(self, args, executable, preexec_fn, close_fds,
   pass_fds, cwd, env,
   startupinfo, creationflags, shell,
   p2cread, p2cwrite,
   c2pread, c2pwrite,
   errread, errwrite,
   restore_signals,
   gid, gids, uid, umask,
   start_new_session):
"""Execute program (POSIX version)"""
if isinstance(args, (str, bytes)):
args = [args]
elif isinstance(args, os.PathLike):
if shell:
raise TypeError('path-like args is not allowed when '
'shell is true')
args = [args]
else:
args = list(args)
if shell:
# On Android the default shell is at '/system/bin/sh'.
unix_shell = ('/system/bin/sh' if
  hasattr(sys, 'getandroidapilevel') else '/bin/sh')
args = [unix_shell, "-c"] + args
if executable:
args[0] = executable
if executable is None:
executable = args[0]
sys.audit("subprocess.Popen", executable, args, cwd, env)
if (_USE_POSIX_SPAWN
and os.path.dirname(executable)
and preexec_fn is None
and not close_fds
and not pass_fds
and cwd is None
and (p2cread == -1 or p2cread > 2)
and (c2pwrite == -1 or c2pwrite > 2)
and (errwrite == -1 or errwrite > 2)
and not 

Bug#1000425: marked as done (node-cheerio: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 05:48:28 +
with message-id 
and subject line Bug#1000425: fixed in node-cheerio 1.0.0~rc~10+~cs13.5.2-5
has caused the Debian Bug report #1000425,
regarding node-cheerio: FTBFS in sid
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.)


-- 
1000425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-cheerio
Version: 1.0.0~rc~10+~cs13.5.2-4
Severity: serious

Hello, some changes in sid made the package FTBFS

 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
mkdir node_modules
ln -s /usr/share/nodejs/css-what ./node_modules/
ln -s /usr/share/nodejs/domelementtype ./node_modules/
ln -s /usr/share/nodejs/jest-diff ./node_modules/
ln -s /usr/share/nodejs/pretty-format ./node_modules/
ln -s /usr/share/nodejs/ts-jest ./node_modules/
ln -s /usr/share/nodejs/tslib ./node_modules/
mkdir -p ./node_modules/\@types
ln -s /usr/share/nodejs/\@types/node ./node_modules/\@types/
ln -s /usr/share/nodejs/\@types/parse5 ./node_modules/\@types/
cp -rL /usr/share/nodejs/css-select ./node_modules/
cp -rL /usr/share/nodejs/domhandler ./node_modules/
cp -rL /usr/share/nodejs/dom-serializer ./node_modules/
cp -rL /usr/share/nodejs/domutils ./node_modules/
cp -rL /usr/share/nodejs/htmlparser2 ./node_modules/
mkdir -p ./node_modules/\@types
cp -rL /usr/share/nodejs/\@types/jest ./node_modules/\@types
ln -s ../cheerio-select node_modules/cheerio-select
ln -s ../parse5-htmlparser2-tree-adapter 
node_modules/parse5-htmlparser2-tree-adapter
ln -s ../../types-parse5-htmlparser2-tree-adapter 
node_modules/\@types/parse5-htmlparser2-tree-adapter
   debian/rules override_dh_auto_build
make[1]: Entering directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/cheerio-select/build
cd ./cheerio-select && sh -ex ../debian/nodejs/cheerio-select/build
+ tsc
No build command found, searching known files
No build command found, searching known files
tsc
src/cheerio.ts:83:9 - error TS2322: Type 'Node' is not assignable to type 'T'.
  'T' could be instantiated with an arbitrary type which could be unrelated to 
'Node'.

83 this[idx] = elem;
   ~


Found 1 error.

make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'


Can you please have a look? thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: node-cheerio
Source-Version: 1.0.0~rc~10+~cs13.5.2-5
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-cheerio 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: Tue, 23 Nov 2021 06:27:56 +0100
Source: node-cheerio
Architecture: source
Version: 1.0.0~rc~10+~cs13.5.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1000425
Changes:
 node-cheerio (1.0.0~rc~10+~cs13.5.2-5) unstable; urgency=medium
 .
   [ Yadd ]
   * Fix debian/watch
 .
   [ Gianfranco Costamagna ]
   * Update typescript patch (Closes: #1000425)
Checksums-Sha1: 
 e5077925b7cae1eee46ec7ac70888ccc5909c1c2 3766 
node-cheerio_1.0.0~rc~10+~cs13.5.2-5.dsc
 9f1221acf3f7cec901db139b8d75e2abdf01a3c6 8628 
node-cheerio_1.0.0~rc~10+~cs13.5.2-5.debian.tar.xz
Checksums-Sha256: 
 46adaaad77b48b28d9c1fd90af87c9377312e3555fc4ea1547bfe065238ca18b 3766 
node-cheerio_1.0.0~rc~10+~cs13.5.2-5.dsc
 c7f8b4c4e319b4e3aeebb34a9b34a96881fc5b992bd2d1af27fbcf51b42a0d01 8628 
node-cheerio_1.0.0~rc~10+~cs13.5.2-5.debian.tar.xz
Files: 
 1d1770a4c77b0fd71502abcdc1f5acbe 3766 javascript optional 
node-cheerio_1.0.0~rc~10+~cs13.5.2-5.dsc
 71671ec9684cbacd00ef5e9011a4dd3a 8628 javascript 

Bug#997364: marked as done (ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `opacity=' for 320x64 DirectClass 16-bit:Magick::Image)

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 05:48:45 +
with message-id 
and subject line Bug#997364: fixed in ruby-sprite-factory 1.7.1-4
has caused the Debian Bug report #997364,
regarding ruby-sprite-factory: FTBFS: ERROR: Test "ruby2.7" failed: 
NoMethodError: undefined method `opacity=' for   320x64 DirectClass 
16-bit:Magick::Image
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.)


-- 
997364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sprite-factory
Version: 1.7.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> NoMethodError: undefined method `opacity=' for   320x64 DirectClass 
> 16-bit:Magick::Image
> 
> /<>/debian/ruby-sprite-factory/usr/lib/ruby/vendor_ruby/sprite_factory/library/rmagick.rb:23:in
>  `create'
> /<>/test/library_test.rb:36:in `block (3 levels) in 
> '
> /<>/test/test_case.rb:67:in `with_clean_output'
> /<>/test/library_test.rb:26:in `block (2 levels) in 
> '
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
> 
> 50 runs, 246 assertions, 0 failures, 28 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w 
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
>  "test/integration_test.rb" "test/library_test.rb" "test/runner_test.rb" 
> "test/style_test.rb" -v]
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in ` (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed: 


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ruby-sprite-factory_1.7.1-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-sprite-factory
Source-Version: 1.7.1-4
Done: Daniel Leidert 

We believe that the bug you reported is fixed in the latest version of
ruby-sprite-factory, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-sprite-factory 
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: Tue, 23 Nov 2021 06:35:53 +0100
Source: ruby-sprite-factory

Processed: tagging 1000412

[Debian Bug Tracking System]

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

> tags 1000412 + pending
Bug #1000412 [src:poetry-core] poetry-core: autopkgtest regression: No such 
file or directory: 'git'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#997364: marked as pending in ruby-sprite-factory

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #997364 in ruby-sprite-factory reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby-sprite-factory/-/commit/392beac8f4ca4b947fb8102b61017da27f0f4d6a


Add patch to replace deprecated method

  * d/patches/replace-deprecated-method-opacity.patch: Add patch.
- Replace deprecated method (closes: #997364).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997364

Processed: Bug#997364 marked as pending in ruby-sprite-factory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997364 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS: ERROR: Test 
"ruby2.7" failed: NoMethodError: undefined method `opacity=' for   320x64 
DirectClass 16-bit:Magick::Image
Added tag(s) pending.

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

Processed: tagging 997364

[Debian Bug Tracking System]

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

> # 
> https://github.com/jakesgordon/sprite-factory/pull/55/files#diff-8c5e632b364c4744c063806d71492877069319e4bca52c2723c3423a2095dd9c
> tags 997364 + patch
Bug #997364 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS: ERROR: Test 
"ruby2.7" failed: NoMethodError: undefined method `opacity=' for   320x64 
DirectClass 16-bit:Magick::Image
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#996212: marked as done (ruby-dalli: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2))

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 05:03:48 +
with message-id 
and subject line Bug#996212: fixed in ruby-dalli 3.0.3-1
has caused the Debian Bug report #996212,
regarding ruby-dalli: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
ArgumentError: wrong number of arguments (given 3, expected 2)
to be marked as done.

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

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


-- 
996212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-dalli
Version: 2.7.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-dalli was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> ArgumentError: wrong number of arguments (given 3, expected 2)
> 
> 
> rails test <>/test/test_active_support.rb:42
> 
> Dalli::key validation#test_0002_allow namespace to be a symbol = 0.00 s = .
> Dalli::key validation#test_0001_not allow blanks = 0.00 s = .
> Encoding::using a live server#test_0001_support i18n content = 0.00 s = .
> Encoding::using a live server#test_0002_support content expiry = 1.21 s = .
> 
> Finished in 38.006598s, 5.0781 runs/s, 206.5168 assertions/s.
> 193 runs, 7849 assertions, 0 failures, 63 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w -I"test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/benchmark_test.rb" "test/test_active_support.rb" 
> "test/test_cas_client.rb" "test/test_compressor.rb" "test/test_dalli.rb" 
> "test/test_encoding.rb" "test/test_failover.rb" "test/test_network.rb" 
> "test/test_rack_session.rb" "test/test_ring.rb" "test/test_sasl.rb" 
> "test/test_serializer.rb" "test/test_server.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-dalli/ruby-dalli_2.7.11-1+rebuild1633377472_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-dalli
Source-Version: 3.0.3-1
Done: Daniel Leidert 

We believe that the bug you reported is fixed in the latest version of
ruby-dalli, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-dalli 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: Tue, 23 Nov 2021 02:40:43 +0100
Source: ruby-dalli
Architecture: source
Version: 3.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Daniel Leidert 
Closes: 996212
Changes:
 ruby-dalli (3.0.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 - Provides compatibility with Ruby 3 and Rails 6.1 (closes: #996212).
   * d/control (Standards-Version): Bump to 4.6.0.
 (Build-Depends): Add ruby-prof.
   * d/copyright (Copyright): Update.
   * d/ruby-dalli.docs: Add 3.0-Upgrade.md.
   * d/watch: Update file.
   * d/patches/0004-Fix-minitest-spec-tests.patch: Remove patch.
 - File has been removed by upstream.
   * d/patches/0005-Skip-SSL-test.patch: Add patch.
 - Skip failing SSL test.
   * d/patches/series: Remove patch.
   * d/upstream/metadata: Update some URLs.
Checksums-Sha1:
 3b48159ef45a8f7d91301c8657691148ef6cbff0 2109 ruby-dalli_3.0.3-1.dsc
 714d9d98fdcdf356fb3cf4652cf46499414e0735 47633 ruby-dalli_3.0.3.orig.tar.gz
 80695ef1e5006cdd98f6a871665cb57829c88aef 4504 ruby-dalli_3.0.3-1.debian.tar.xz
 d8c0233f8c70d35561ede4636d3913bfe9b55e2d 11129 
ruby-dalli_3.0.3-1_amd64.buildinfo
Checksums-Sha256:
 ac378b3319e2943d714a533e7ff0bbfd40b9640eff34812cd00922cd5c6b0162 2109 
ruby-dalli_3.0.3-1.dsc
 17f50d81a283144318b9b97dd01c25d37494f1bb9da3bb36f87b792525e7689d 47633 
ruby-dalli_3.0.3.orig.tar.gz
 

Bug#996217: marked as done (ruby-dry-logic: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 04:33:57 +
with message-id 
and subject line Bug#996217: fixed in ruby-dry-logic 1.2.0-1
has caused the Debian Bug report #996217,
regarding ruby-dry-logic: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
 ArgumentError:
to be marked as done.

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

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


-- 
996217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-dry-logic
Version: 1.0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-dry-logic was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>  ArgumentError:
>wrong number of arguments (0 for -2)
>  # ./lib/dry/logic/rule/interface.rb:16:in `initialize'
>  # ./lib/dry/logic/rule.rb:39:in `new'
>  # ./lib/dry/logic/rule.rb:39:in `block in specialize'
>  # ./lib/dry/logic/rule.rb:38:in `specialize'
>  # ./lib/dry/logic/rule.rb:47:in `build'
>  # ./lib/dry/logic/rule.rb:16:in `Rule'
>  # ./spec/integration/rule_spec.rb:31:in `block (2 levels) in  (required)>'
> 
> Finished in 0.11951 seconds (files took 0.28615 seconds to load)
> 219 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/integration/rule_spec.rb:39 # Rules defining an exclusive 
> disjunction
> rspec ./spec/integration/rule_spec.rb:13 # Rules defining a conjunction
> rspec ./spec/integration/rule_spec.rb:30 # Rules defining an implication
> 
> Randomized with seed 21613
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-dry-logic/ruby-dry-logic_1.0.5-2+rebuild1633378530_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-dry-logic
Source-Version: 1.2.0-1
Done: Daniel Leidert 

We believe that the bug you reported is fixed in the latest version of
ruby-dry-logic, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-dry-logic 
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: Tue, 23 Nov 2021 05:01:34 +0100
Source: ruby-dry-logic
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Team 

Changed-By: Daniel Leidert 
Closes: 996217
Changes:
 ruby-dry-logic (1.2.0-1) unstable; urgency=low
 .
   * Team upload.
   * New upstream release.
 - Fixes ArgumentError with Ruby 3 (closes: #996217).
 .
   [ Debian Janitor ]
   * Set field Upstream-Contact in debian/copyright.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
   * Remove constraints unnecessary since buster:
 + Build-Depends: Drop versioned constraint on ruby-concurrent.
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Daniel Leidert ]
   * d/control (Standards-Version): Bump to 4.6.0.
 (Build-Depends): Add ruby-warning, remove ruby-dry-equalizer, and
 raise ruby-dry-core.
   * d/copyright (Copyright): Update team copyright.
   * d/ruby-dry-logic.examples: Install example.
   * d/rules: Install upstream changelog.
   * d/watch: Use github sources to keep the tests.
   * d/patches/Fix-NameError-by-requiring-open-uri.patch: Add patch.
 - Fix a NameError thrown without requiring open-uri.
   * d/patches/series: Enable patch.
   * d/upstream/metadata (Bug-Submit, Changelog): Update URLs.

Bug#996157: marked as done (ruby-clean-test: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_any_symbol_works(TestAny): ArgumentError: wrong number of arguments (given 2, expected 0..1))

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 03:39:56 +0100
with message-id 
and subject line Fixed in ruby-faker
has caused the Debian Bug report #996157,
regarding ruby-clean-test: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
Error: test_any_symbol_works(TestAny): ArgumentError: wrong number of arguments 
(given 2, expected 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.)


-- 
996157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-clean-test
Version: 1.0.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-clean-test was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> Error: test_any_symbol_works(TestAny): ArgumentError: wrong number of 
> arguments (given 2, expected 0..1)
> /usr/share/rubygems-integration/all/gems/i18n-1.8.10/lib/i18n.rb:196:in 
> `translate'
> /usr/share/rubygems-integration/all/gems/faker-1.9.1/lib/faker.rb:153:in 
> `translate'
> /usr/share/rubygems-integration/all/gems/faker-1.9.1/lib/faker/lorem.rb:14:in 
> `words'
> /<>/debian/ruby-clean-test/usr/lib/ruby/vendor_ruby/clean_test/any.rb:110:in
>  `any_string'
> /<>/debian/ruby-clean-test/usr/lib/ruby/vendor_ruby/clean_test/any.rb:122:in
>  `any_symbol'
> /<>/test/test_any.rb:111:in `block (2 levels) in '
> /<>/debian/ruby-clean-test/usr/lib/ruby/vendor_ruby/clean_test/given_when_then.rb:96:in
>  `Given'
> /<>/test/test_any.rb:110:in `block in '
> ===
> : (0.000564)
> test_both_min_and_max_must_be_positive_(-10,1):   .: (0.000335)
> test_both_min_and_max_must_be_positive_(0,-10):   .: (0.000115)
> test_both_min_and_max_must_be_positive_(0,0): .: (0.000104)
> test_both_min_and_max_must_be_positive_(0,1): .: (0.000101)
> test_min_and_max_must_agree:  .: (0.000107)
>   TestCircle: 
> 
> test_anonymous_test_at_/<>/test/test_circle.rb,_line_12_passes:  
> .: (0.006066)
>   TestGivenWhenThen: 
> test_basics:  .: (0.000210)
> test_can_pass_params_to_symbols:  .: (0.000106)
> test_can_reuse_blocks:.: (0.000124)
> test_can_use_symbols_for_methods: .: (0.82)
> test_cannot_use_locals:   .: (0.87)
> test_invert_for_block_based_asserts:  .: (0.000136)
> test_methods_that_return_blocks:  .: (0.79)
> test_mock_support:.: (0.87)
>   TestSimpleGiven: 
> 
> test_anonymous_test_at_/<>/test/test_test_that.rb,_line_19_passes:
>.: (0.000171)
> test_that_test_that_barfs_with_no_block:  .: (0.000110)
> test_when_assigning_@x_to_4,_it_is_4: .: (0.76)
> 
> Finished in 0.022210569 seconds.
> ---
> 30 tests, 29 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 
> notifications
> 76.6667% passed
> ---
> 1350.71 tests/s, 1305.68 assertions/s
> rake aborted!
> Command failed with status (1): [ruby -w -I"test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/test_any.rb" "test/test_circle.rb" "test/test_given_when_then.rb" 
> "test/test_test_that.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-clean-test/ruby-clean-test_1.0.0-1.1+rebuild1633376642_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-faker
Source-Version: 1.9.1-3
Done: Daniel Leidert 

This problem has been solved with the upload of ruby-faker/1.9.1-3.
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000421: dpkg-shlibdeps: Wrong minimum version requirement on libc6

[Guillem Jover]

Hi!

On Mon, 2021-11-22 at 22:49:43 +0100, Joachim Reichel wrote:
> Package: dpkg-dev
> Version: 1.20.9
> Severity: serious
> Control: affects -1 cppcheck

> dpkg-shlibdeps calculates too low minimum version requirements for cppcheck 
> on libc6 (see bug 1000146).
> 
> To reproduce, build cppcheck 2.6-1 in unstable chroot without cleaning up, 
> e.g., "dpkg-buildpackage -rfakeroot -us -uc".
> 
> $ grep Depends debian/cppcheck/DEBIAN/control
> Depends: libc6 (>= 2.29), [...]
> 
> But running the binary with libc6 2.31 fails with
> 
> cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by cppcheck)
> cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6)
> cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
> /lib/x86_64-linux-gnu/libpthread.so.0)
> 
> I believe that is the case because a certain symbol in the .bss section is 
> ignored (this is the only symbol with 2.32 suffix):
> 
> $ objdump -w -T ./debian/cppcheck/usr/bin/cppcheck | grep 
> __libc_single_threaded
> 004670e0 gDO .bss   0001  GLIBC_2.32  
> __libc_single_threaded
> 
> $ nm -D ./debian/cppcheck/usr/bin/cppcheck | grep __libc_single_threaded
> 004670e0 B __libc_single_threaded@@GLIBC_2.32
> 
> $ dpkg-shlibdeps ./debian/cppcheck/usr/bin/cppcheck; cat debian/substvars
> shlibs:Depends=libc6 (>= 2.29), [...]
> 
> After hacking /usr/share/perl5/Dpkg/Shlibs/Objdump.pm:462 to read
> "defined => ($sect ne '*UND*') && ($sect ne '.bss')"
> (maybe not the right solution, just for demonstration):

Thanks for the investigation! But, I'm afraid that would mean
dpkg-gensymbols missing symbols on the generated .symbols file. Also
marking all such symbols from «.bss» would start emitting tons of
warnings for non-imported symbols, more so in cppcheck case as it is
built with -rdynamic (which exports those).

After some further checking, it seems newer binutils have started
qualifying symbols in copy relocation with the version string, which
the code was not matching (but i386 was not affected f.ex. as it does
not use copy relocations for those). The attached patch seems to work
on amd64, but I'll check tomorrow whether the same applies to other
arches and if they use the same symbol format. But at least it should
improve things and not cause regressions as it will try both formats.

Thanks,
Guillem
From a9c4f1806f1927a2da42712658f4cfdd37f73e50 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Tue, 23 Nov 2021 02:26:50 +0100
Subject: [PATCH] Dpkg::Shlibs::Objdump: Fix apply_relocations to work with
 versioned symbols
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Since at least binutils 2.28 copy relocations for versioned symbols have
the version appended after «@@». We were not taking this into account
which meant these did not match and did not get marked as undefined.

Try both the version qualified symbol and the bare symbol name to cope
with old and new formats.

Closes: #1000421
---
 scripts/Dpkg/Shlibs/Objdump.pm | 15 +--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/scripts/Dpkg/Shlibs/Objdump.pm b/scripts/Dpkg/Shlibs/Objdump.pm
index 93319d1eb..43d786edd 100644
--- a/scripts/Dpkg/Shlibs/Objdump.pm
+++ b/scripts/Dpkg/Shlibs/Objdump.pm
@@ -488,9 +488,20 @@ sub apply_relocations {
 	# We want to mark as undefined symbols those which are currently
 	# defined but that depend on a copy relocation
 	next if not $sym->{defined};
-	next if not exists $self->{dynrelocs}{$sym->{name}};
-	if ($self->{dynrelocs}{$sym->{name}} =~ /^R_.*_COPY$/) {
+
+my @relocs;
+push @relocs, $sym->{name} . '@@' . $sym->{version} if $sym->{version};
+
+# Symbols that are not versioned, or versioned but linked with old
+# binutils do not have a version appended.
+push @relocs, $sym->{name};
+
+foreach my $reloc (@relocs) {
+next if not exists $self->{dynrelocs}{$reloc};
+next if not $self->{dynrelocs}{$reloc} =~ /^R_.*_COPY$/;
+
 	$sym->{defined} = 0;
+last;
 	}
 }
 }
-- 
2.34.0

Bug#1000204: pyfai: diff for NMU version 0.20.0+dfsg1-4.1

[Stefano Rivera]

Control: tags 1000204 + pending

Dear maintainer,

I've prepared an NMU for pyfai (versioned as 0.20.0+dfsg1-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Also filed as https://salsa.debian.org/science-team/pyfai/-/merge_requests/4

Regards,

SR
diff -Nru pyfai-0.20.0+dfsg1/debian/changelog pyfai-0.20.0+dfsg1/debian/changelog
--- pyfai-0.20.0+dfsg1/debian/changelog	2021-09-19 07:57:57.0 -0400
+++ pyfai-0.20.0+dfsg1/debian/changelog	2021-11-22 21:29:59.0 -0400
@@ -1,3 +1,10 @@
+pyfai (0.20.0+dfsg1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.10 support, thanks Lukas Märdian. (Closes: #1000204)
+
+ -- Stefano Rivera   Mon, 22 Nov 2021 21:29:59 -0400
+
 pyfai (0.20.0+dfsg1-4) unstable; urgency=medium
 
   * Bug fix: "Removal of the python3-*-dbg packages in sid/bookworm",
diff -Nru pyfai-0.20.0+dfsg1/debian/patches/0009-Fix-collections.MutableSets-compat-with-python3.10.patch pyfai-0.20.0+dfsg1/debian/patches/0009-Fix-collections.MutableSets-compat-with-python3.10.patch
--- pyfai-0.20.0+dfsg1/debian/patches/0009-Fix-collections.MutableSets-compat-with-python3.10.patch	1969-12-31 20:00:00.0 -0400
+++ pyfai-0.20.0+dfsg1/debian/patches/0009-Fix-collections.MutableSets-compat-with-python3.10.patch	2021-11-22 21:29:59.0 -0400
@@ -0,0 +1,45 @@
+From: Lukas Märdian 
+Date: Mon, 22 Nov 2021 21:30:44 -0400
+Subject: Fix collections.MutableSets compat with python3.10
+
+collections.MutableSet was deprecated a long time ago and removed with python3.10.
+https://docs.python.org/3/whatsnew/3.10.html#removed
+https://bugs.python.org/issue37324
+
+Using the old class name leads to test failures such as this one:
+==
+ERROR: test_import_all_modules (pyFAI.test.test_bug_regression.TestBugRegression)
+Try to import every single module in the package
+--
+Traceback (most recent call last):
+  File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 286, in test_import_all_modules
+raise err
+  File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 271, in test_import_all_modules
+load_source(fqn, path)
+  File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 78, in load_source
+spec.loader.exec_module(module)
+  File "", line 883, in exec_module
+  File "", line 241, in _call_with_frames_removed
+  File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/utils/orderedset.py", line 30, in 
+class OrderedSet(collections.MutableSet):
+AttributeError: module 'collections' has no attribute 'MutableSet'
+
+Origin: vendor, Ubuntu
+Forwarded: https://github.com/silx-kit/pyFAI/pull/1588
+---
+ pyFAI/utils/orderedset.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/pyFAI/utils/orderedset.py b/pyFAI/utils/orderedset.py
+index de097cf..417490f 100644
+--- a/pyFAI/utils/orderedset.py
 b/pyFAI/utils/orderedset.py
+@@ -27,7 +27,7 @@
+ import collections
+ 
+ 
+-class OrderedSet(collections.MutableSet):
++class OrderedSet(collections.abc.MutableSet):
+ 
+ def __init__(self, iterable=None):
+ self.end = end = []
diff -Nru pyfai-0.20.0+dfsg1/debian/patches/series pyfai-0.20.0+dfsg1/debian/patches/series
--- pyfai-0.20.0+dfsg1/debian/patches/series	2021-09-19 07:57:57.0 -0400
+++ pyfai-0.20.0+dfsg1/debian/patches/series	2021-11-22 21:29:59.0 -0400
@@ -6,3 +6,4 @@
 0006-fix-a-couple-of-test-failing-with-i386.patch
 0007-cleaner-test.patch
 0008-tunning.patch
+0009-Fix-collections.MutableSets-compat-with-python3.10.patch

Processed: pyfai: diff for NMU version 0.20.0+dfsg1-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1000204 + pending
Bug #1000204 [pyfai] pyfai: FTBFS if built using python3.10 
(collections.MutableSets deprecated)
Added tag(s) pending.

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

Bug#999519: xrayutilities: diff for NMU version 1.7.1-2.1

[Stefano Rivera]

Control: tags 999519 + patch
Control: tags 999519 + pending

Dear maintainer,

I've prepared an NMU for xrayutilities (versioned as 1.7.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Also filed as: 
https://salsa.debian.org/science-team/python-xrayutilities/-/merge_requests/1

Regards,

SR
diff -Nru xrayutilities-1.7.1/debian/changelog xrayutilities-1.7.1/debian/changelog
--- xrayutilities-1.7.1/debian/changelog	2021-09-19 08:54:46.0 -0400
+++ xrayutilities-1.7.1/debian/changelog	2021-11-22 21:22:36.0 -0400
@@ -1,3 +1,10 @@
+xrayutilities (1.7.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: matplotlib 3.5 support (Closes: #999519)
+
+ -- Stefano Rivera   Mon, 22 Nov 2021 21:22:36 -0400
+
 xrayutilities (1.7.1-2) unstable; urgency=medium
 
   * Corrected Profile nodocs -> nodoc
diff -Nru xrayutilities-1.7.1/debian/patches/0005-Fix-matplotlib-3.5-issue.patch xrayutilities-1.7.1/debian/patches/0005-Fix-matplotlib-3.5-issue.patch
--- xrayutilities-1.7.1/debian/patches/0005-Fix-matplotlib-3.5-issue.patch	1969-12-31 20:00:00.0 -0400
+++ xrayutilities-1.7.1/debian/patches/0005-Fix-matplotlib-3.5-issue.patch	2021-11-22 21:22:36.0 -0400
@@ -0,0 +1,35 @@
+From: Dominik Kriegner 
+Date: Fri, 12 Nov 2021 12:30:16 +0100
+Subject: Fix matplotlib-3.5 issue.
+
+reported by Debian. The best solution seems to be to avoid the
+problematic keyword argument since we anyhow specified the default
+value.
+
+Bug-Debian: https://bugs.debian.org/999519
+---
+ lib/xrayutilities/simpack/fit.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/lib/xrayutilities/simpack/fit.py b/lib/xrayutilities/simpack/fit.py
+index 8e71783..5d49dcf 100644
+--- a/lib/xrayutilities/simpack/fit.py
 b/lib/xrayutilities/simpack/fit.py
+@@ -13,7 +13,7 @@
+ # You should have received a copy of the GNU General Public License
+ # along with this program; if not, see .
+ #
+-# Copyright (C) 2016-2020 Dominik Kriegner 
++# Copyright (C) 2016-2021 Dominik Kriegner 
+ 
+ import warnings
+ 
+@@ -208,7 +208,7 @@ class FitModel(object):
+ else:
+ self.zord = 1
+ if self.logscale:
+-self.ax.set_yscale("log", nonposy='clip')
++self.ax.set_yscale("log")
+ self.fline = None
+ 
+ def showplot(self, xlab=self.lmodel.xlabelstr,
diff -Nru xrayutilities-1.7.1/debian/patches/series xrayutilities-1.7.1/debian/patches/series
--- xrayutilities-1.7.1/debian/patches/series	2021-09-19 08:54:46.0 -0400
+++ xrayutilities-1.7.1/debian/patches/series	2021-11-22 21:22:36.0 -0400
@@ -2,3 +2,4 @@
 0002-Desactivated-pdf-generation-for-the-doc.patch
 0003-Do-not-change-PYTHONPATH-during-the-build.patch
 0004-Used-the-system-Mathjax.patch
+0005-Fix-matplotlib-3.5-issue.patch

Processed: xrayutilities: diff for NMU version 1.7.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999519 + patch
Bug #999519 [src:xrayutilities] xrayutilities: FTBFS with matplotlib 3.5 (in 
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 -s 
custom "--test-args={interpreter} {dir}/setup.py egg_info -e {build_dir}; cd 
{build_dir}; {interpreter} -m unittest2 discover -v;" returned exit code 13
Added tag(s) patch.
> tags 999519 + pending
Bug #999519 [src:xrayutilities] xrayutilities: FTBFS with matplotlib 3.5 (in 
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9 -s 
custom "--test-args={interpreter} {dir}/setup.py egg_info -e {build_dir}; cd 
{build_dir}; {interpreter} -m unittest2 discover -v;" returned exit code 13
Added tag(s) pending.

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

Bug#1000428: gammapy: FTBFS with matplotlib 3.5

[Stefano Rivera]

Source: gammapy
Version: 0.18.2-1
Severity: serious
Justification: FTBFS

Matplotlib 3.5 seems to have caused some test failures:
=== short test summary info 
FAILED gammapy/datasets/tests/test_map.py::test_plot_residual_onoff - ValueEr...
FAILED gammapy/datasets/tests/test_spectrum.py::test_peek - TypeError: Unsupp...
FAILED gammapy/datasets/tests/test_spectrum.py::TestSpectrumOnOff::test_peek
FAILED gammapy/datasets/tests/test_spectrum.py::TestSpectrumOnOff::test_plot_fit
FAILED 
gammapy/irf/tests/test_edisp_map.py::test_edispkernel_from_diagonal_response
FAILED gammapy/irf/tests/test_edisp_map.py::test_edispkernel_from_1D - KeyErr...
FAILED gammapy/makers/background/tests/test_reflected.py::test_bad_on_region
FAILED gammapy/maps/tests/test_region.py::test_width - AssertionError: 
FAILED gammapy/maps/tests/test_regionnd.py::test_region_nd_map_plot - TypeErr...
FAILED gammapy/modeling/models/tests/test_spectral.py::test_model_plot - Type...
= 10 failed, 1157 passed, 479 skipped, 2 xfailed, 3 xpassed in 82.49s (0:01:22) 
=

With both Python 3.9 and 3.10.

See: 
https://buildd.debian.org/status/fetch.php?pkg=gammapy=amd64=0.18.2-1%2Bb1=1637623734=0

SR

Bug#1000427: pyregion: FTBFS with setuptools >= 58

[Stefano Rivera]

Source: pyregion
Version: 2.1.1-1
Severity: serious
Tags: upstream
Justification: FTBFS

pyregion fails to build with setuptools >= 58, which dropped use_2to3
support.:

/usr/lib/python3/dist-packages/setuptools/dist.py:294: DistDeprecationWarning: 
use_2to3 is ignored.
  warnings.warn(f"{attr} is ignored.", DistDeprecationWarning)

See the full log:
https://buildd.debian.org/status/fetch.php?pkg=pyregion=amd64=2.1.1-1%2Bb1=1637589214=0

SR

Processed: block 1000423 with 1000422

[Debian Bug Tracking System]

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

> block 1000423 with 1000422
Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python 
3.10 - Test failures
1000423 was not blocked by any bugs.
1000423 was not blocking any bugs.
Added blocking bug(s) of 1000423: 1000422
> thanks
Stopping processing here.

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

Processed (with 1 error): reassign 997882 to src:licensecheck, forcibly merging 994150 997882

[Debian Bug Tracking System]

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

> reassign 997882 src:licensecheck
Bug #997882 {Done: Jonas Smedegaard } [src:licensecheck] 
licensecheck: autopkgtest regression: lots of failures
Ignoring request to reassign bug #997882 to the same package
> forcemerge 994150 997882
Failed to forcibly merge 994150: Not altering archived bugs; see unarchive.

> thanks
Stopping processing here.

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

Bug#999484: marked as done (freedombox: Missing dependencies for essential modules)

[Debian Bug Tracking System]

Your message dated Tue, 23 Nov 2021 00:48:35 +
with message-id 
and subject line Bug#999484: fixed in freedombox 21.14
has caused the Debian Bug report #999484,
regarding freedombox: Missing dependencies for essential modules
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.)


-- 
999484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freedombox
Version: 21.13
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jvalle...@mailbox.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

freedombox 21.13 is missing many dependencies for essential modules,
such as apache2, avahi-daemon, certbot, etc.

It is likely related to this issue about the --list-dependencies
command:

https://salsa.debian.org/freedombox-team/freedombox/-/issues/2149

When building the freedombox package, it also uses --list-dependencies
to collect dependencies for essential modules.

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmGNY+MWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICFVoD/9ZNERDDm8KXYlh/Ij5hW3X4350
TKVVaX2104j95qBGHRM2fQF1rJJjtzPeiCVesJdaUOQAZ1eoPXXP2LUpgpkci5vH
FLsZOMIOZsvt4n13HoYKonVO+jUic0tpNdVEv/qc8okMyS/a/iJb+Nt90uSVl450
FSBpOB21Tz1uqeAcIyUZBfFhqYt3+9beDjt+MBx2CJ2GSG1vYTMciYmEta8WOA1k
NlHno7TM7rkFW2k52vNo7qonU/JBVKFX0PSdbY8FZdtGPshuWFSbSlHzSkmRlnKa
6i0/90nzUbjK6sUVdMqjl7rJvh/Yf7wKLlQvYo3ChRIIqHzFo0geFfz/TOAskxXO
DnWq++0PeKWTWSlS9HmYuFLmc3mu7w3nFEMI1P42MzQd00jLXTjGvEeqr1zFD/MB
vVbqSGJ+tXVgK5YuSg5Kl554F3inWvwqynANOEuMj02hjE8WJlmQqYekUZy/TT/8
2Y9ar9PD5/ocWMV3fJv/iPLT0ywX72GY6UVuvCHsE4IExhr7AfAkorNfOhp1l1/t
PkvBbcrf0Ii3XW8FjNWMMQXj7zjxm7owrMELQCv9M6EjBONyVhS04HdUs5zf+COn
ZFmnvtmOiiUQalySpXXOrQSnovyxci6MoHfbTYpcYP7J+qnQCOcR3Z3OEKoOyqBi
yTe6btoJvsJrkCwsuw==
=vYHx
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: freedombox
Source-Version: 21.14
Done: James Valleroy 

We believe that the bug you reported is fixed in the latest version of
freedombox, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated freedombox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 18:45:33 -0500
Source: freedombox
Architecture: source
Version: 21.14
Distribution: unstable
Urgency: high
Maintainer: FreedomBox packaging team 

Changed-By: James Valleroy 
Closes: 999484
Changes:
 freedombox (21.14) unstable; urgency=high
 .
   [ Burak Yavuz ]
   * Translated using Weblate (Turkish)
 .
   [ Michael Breidenbach ]
   * Translated using Weblate (Swedish)
 .
   [ Sunil Mohan Adapa ]
   * app: Introduce separate method for post initialization operations
   * module_loader: Split app initialization into separate steps
   * avahi: Split app initialization
   * backups: Split app initialization
   * cockpit: Split app initialization
   * diagnostics: Split app initialization
   * dynamicdns: Split app initialization
   * email_server: Don't get domain name during initialization
   * config: Split app configuration
   * letencrypt: Split app initialization
   * names: Split app initialization
   * pagekite: Split app initialization
   * storage: Split app initialization
   * tor: Split app initialziation
   * upgrades: Split app initialziation
   * ejabberd: Split app initialziation
   * gitweb: Split app initialization
   * frontpage: Avoid URL reverse during Shortcut component construction
   * menu: Avoid reversing URL during Menu component construction
   * main: Drop initializing Django when listing dependencies (Closes: #999484)
 .
   [ Andrij Mizyk ]
   * Translated using Weblate (Ukrainian)
 .
   [ Joseph Nuthalapati ]
   * names: Create a generic TLS domain selection form
   * tt-rss: Allow selection of a domain name
 .
   [ James Valleroy ]
   * debian: Fail build if no module dependencies found
   * datetime: Avoid error when systemctl is not available
   * locale: Update translation strings
   * doc: Fetch latest manual
Checksums-Sha1:
 daec7278f9872c61735120ca3ced71eeb0c24f67 

Processed: pidgin-sipe: diff for NMU version 1.25.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 997278 + patch
Bug #997278 [src:pidgin-sipe] pidgin-sipe: FTBFS: sipe-tls-tester.c:158:17: 
error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead 
[-Werror=deprecated-declarations]
Added tag(s) patch.
> tags 997278 + pending
Bug #997278 [src:pidgin-sipe] pidgin-sipe: FTBFS: sipe-tls-tester.c:158:17: 
error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead 
[-Werror=deprecated-declarations]
Added tag(s) pending.

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

Bug#997278: pidgin-sipe: diff for NMU version 1.25.0-2.1

[Adrian Bunk]

Control: tags 997278 + patch
Control: tags 997278 + pending

Dear maintainer,

I've prepared an NMU for pidgin-sipe (versioned as 1.25.0-2.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru pidgin-sipe-1.25.0/debian/changelog pidgin-sipe-1.25.0/debian/changelog
--- pidgin-sipe-1.25.0/debian/changelog	2020-01-23 19:13:12.0 +0200
+++ pidgin-sipe-1.25.0/debian/changelog	2021-11-23 01:46:05.0 +0200
@@ -1,3 +1,11 @@
+pidgin-sipe (1.25.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with --disable-quality-check to fix building with
+recent glib. (Closes: #997278)
+
+ -- Adrian Bunk   Tue, 23 Nov 2021 01:46:05 +0200
+
 pidgin-sipe (1.25.0-2) unstable; urgency=medium
 
   * Add upstream patch 0001-Fix-359-Incorrect-build-due-to-false-negative-config
diff -Nru pidgin-sipe-1.25.0/debian/rules pidgin-sipe-1.25.0/debian/rules
--- pidgin-sipe-1.25.0/debian/rules	2020-01-23 19:13:12.0 +0200
+++ pidgin-sipe-1.25.0/debian/rules	2021-11-23 01:46:05.0 +0200
@@ -2,7 +2,7 @@
 
 include /usr/share/dpkg/pkg-info.mk
 
-DEB_CONFIGURE_EXTRA_FLAGS := --libdir=/usr/lib --enable-purple --disable-telepathy --enable-openssl=no
+DEB_CONFIGURE_EXTRA_FLAGS := --libdir=/usr/lib --enable-purple --disable-telepathy --enable-openssl=no --disable-quality-check
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 

Bug#1000414: textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1

[Julian Gilbey]

On Mon, Nov 22, 2021 at 10:14:03PM +0100, Paul Gevers wrote:
> Source: textdistance
> Version: 4.2.2-1
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Dear maintainer(s),
> 
> With a recent upload of textdistance the autopkgtest of textdistance fails
> in testing when that autopkgtest is run with the binary packages of
> textdistance from unstable on arm64. It passes when run with only packages
> from testing. In tabular form:

Hi Paul,

Thanks for this report.  I've just been fighting with abydos (part of
the same chain of dependencies of spyder), and fixed that.  I'm
working through the list, and textdistance is high on it...

I'm not quite sure what the cause is, but we'll see...

Best wishes,

   Julian

Bug#1000378: marked as done (telnetd: post-installation error)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 23:21:14 +
with message-id 
and subject line Bug#1000378: fixed in netkit-telnet 0.17-44
has caused the Debian Bug report #1000378,
regarding telnetd: post-installation error
to be marked as done.

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

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


-- 
1000378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telnetd
Version: 0.17-43
Severity: grave
Justification: renders package unusable

Dear Maintainer,

package does report error on install:


aptitude install telnetd
Die folgenden NEUEN Pakete werden zusätzlich installiert:
  telnetd
0 Pakete aktualisiert, 1 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
0 B/46,0 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 116 kB zusätzlich belegt sein.
Vormals nicht ausgewähltes Paket telnetd wird gewählt.
(Lese Datenbank ... 743851 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../telnetd_0.17-43_amd64.deb ...
Entpacken von telnetd (0.17-43) ...
telnetd (0.17-43) wird eingerichtet ...
Benutzer telnetd wird zur Gruppe utmp hinzugefügt.
chown: Zugriff auf '/usr/lib/telnetlogin' nicht möglich: Datei oder Verzeichnis
nicht gefunden
dpkg: Fehler beim Bearbeiten des Paketes telnetd (--configure):
 »installiertes telnetd-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 1 zurück
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 telnetd
E: Sub-process /usr/bin/dpkg returned an error code (1)
telnetd (0.17-43) wird eingerichtet ...
chown: Zugriff auf '/usr/lib/telnetlogin' nicht möglich: Datei oder Verzeichnis
nicht gefunden
dpkg: Fehler beim Bearbeiten des Paketes telnetd (--configure):
 »installiertes telnetd-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 telnetd



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

Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telnetd depends on:
ii  adduser   3.118
ii  libc6 2.32-4
ii  openbsd-inetd [inet-superserver]  0.20160825-5
ii  passwd1:4.8.1-2

telnetd recommends no packages.

telnetd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: netkit-telnet
Source-Version: 0.17-44
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated netkit-telnet package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 23:40:00 +0100
Source: netkit-telnet
Architecture: source
Version: 0.17-44
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1000378
Changes:
 netkit-telnet (0.17-44) unstable; urgency=medium
 .
   * QA upload
   * telnetd: Revert changes from last revision (Closes: #1000378)
Checksums-Sha1:
 af1eda3c06d89a5d47ad79d53d0d2b639c4f3cea 1667 netkit-telnet_0.17-44.dsc
 d7a2c219fbae06801e67d70616b0ffa5d4580dad 36604 
netkit-telnet_0.17-44.debian.tar.xz
 61bc58221a3ff34e279298f5e561c379cda83240 6094 
netkit-telnet_0.17-44_source.buildinfo
Checksums-Sha256:
 ca51be255cc8de2ccdbfd5712b65df7771845eb22076cc5baeb00f98330f0aca 1667 
netkit-telnet_0.17-44.dsc
 958893ff75c88e6d6c5b925664b143008bf4d11472e480576a65035071e0b195 36604 
netkit-telnet_0.17-44.debian.tar.xz
 09b3edc8460bf56a542f7890ea8e4b9e938388cdfad461a16499ce497c9ce9a2 6094 

Processed: bug 996406 is forwarded to https://github.com/Pylons/pyramid_chameleon/pull/34

[Debian Bug Tracking System]

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

> forwarded 996406 https://github.com/Pylons/pyramid_chameleon/pull/34
Bug #996406 [src:python-pyramid, src:python-pyramid-chameleon] python-pyramid 
breaks python-pyramid-chameleon autopkgtest: No module named 'pyramid.compat'
Set Bug forwarded-to-address to 
'https://github.com/Pylons/pyramid_chameleon/pull/34'.
> thanks
Stopping processing here.

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

Bug#1000425: node-cheerio: FTBFS in sid

[Gianfranco Costamagna]

control: tags -1 patch

Hello, I just discovered that the following patch, extracted from a big 
upstream refactor fixed the build/test

Description: Fix build failure with part of upstream patch
Origin: 
https://github.com/cheeriojs/cheerio/commit/b64cb31bb0d40d9d912a4e3a24a5ad22a5cdfced
Bug-Debian: https://bugs.debian.org/1000425
Last-Update: 2021-11-22

--- node-cheerio-1.0.0~rc~10+~cs13.5.2.orig/src/cheerio.ts
+++ node-cheerio-1.0.0~rc~10+~cs13.5.2/src/cheerio.ts
@@ -79,9 +79,9 @@ export class Cheerio implements Array
 : null;

 if (elements) {
-  elements.forEach((elem, idx) => {
-this[idx] = elem;
-  });
+  for (let idx = 0; idx < elements.length; idx++) {
+this[idx] = elements[idx];
+  }
   this.length = elements.length;
   return this;
 }

G.

On Mon, 22 Nov 2021 23:39:21 +0100 Gianfranco Costamagna 
 wrote:
> Source: node-cheerio
> Version: 1.0.0~rc~10+~cs13.5.2-4
> Severity: serious
> 
> Hello, some changes in sid made the package FTBFS
> 
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>   mkdir node_modules
>   ln -s /usr/share/nodejs/css-what ./node_modules/
>   ln -s /usr/share/nodejs/domelementtype ./node_modules/
>   ln -s /usr/share/nodejs/jest-diff ./node_modules/
>   ln -s /usr/share/nodejs/pretty-format ./node_modules/
>   ln -s /usr/share/nodejs/ts-jest ./node_modules/
>   ln -s /usr/share/nodejs/tslib ./node_modules/
>   mkdir -p ./node_modules/\@types
>   ln -s /usr/share/nodejs/\@types/node ./node_modules/\@types/
>   ln -s /usr/share/nodejs/\@types/parse5 ./node_modules/\@types/
>   cp -rL /usr/share/nodejs/css-select ./node_modules/
>   cp -rL /usr/share/nodejs/domhandler ./node_modules/
>   cp -rL /usr/share/nodejs/dom-serializer ./node_modules/
>   cp -rL /usr/share/nodejs/domutils ./node_modules/
>   cp -rL /usr/share/nodejs/htmlparser2 ./node_modules/
>   mkdir -p ./node_modules/\@types
>   cp -rL /usr/share/nodejs/\@types/jest ./node_modules/\@types
>   ln -s ../cheerio-select node_modules/cheerio-select
>   ln -s ../parse5-htmlparser2-tree-adapter 
> node_modules/parse5-htmlparser2-tree-adapter
>   ln -s ../../types-parse5-htmlparser2-tree-adapter 
> node_modules/\@types/parse5-htmlparser2-tree-adapter
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/cheerio-select/build
>   cd ./cheerio-select && sh -ex ../debian/nodejs/cheerio-select/build
> + tsc
> No build command found, searching known files
> No build command found, searching known files
> tsc
> src/cheerio.ts:83:9 - error TS2322: Type 'Node' is not assignable to type 'T'.
>   'T' could be instantiated with an arbitrary type which could be unrelated 
> to 'Node'.
> 
> 83 this[idx] = elem;
>~
> 
> 
> Found 1 error.
> 
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
> make[1]: Leaving directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'
> 
> 
> Can you please have a look? thanks
> 
> Gianfranco
> 
> 

Processed: Re: node-cheerio: FTBFS in sid

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1000425 [src:node-cheerio] node-cheerio: FTBFS in sid
Added tag(s) patch.

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

Bug#998507: marked as done (rails: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2))

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 22:42:36 +
with message-id 
and subject line Bug#998507: fixed in rails 2:6.1.4.1+dfsg-5
has caused the Debian Bug report #998507,
regarding rails: FTBFS: ERROR: Test "ruby3.0" failed: ArgumentError: wrong 
number of arguments (given 3, expected 2)
to be marked as done.

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

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


-- 
998507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rails
Version: 2:6.0.3.7+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> ArgumentError: wrong number of arguments (given 3, expected 2)
> /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in 
> `set'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:397:in
>  `block (2 levels) in write_entry'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:25:in
>  `with'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:397:in
>  `block in write_entry'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:478:in
>  `failsafe'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:391:in
>  `write_entry'
> 
> /<>/activesupport/lib/active_support/cache/strategy/local_cache.rb:150:in
>  `write_entry'
> 
> /<>/activesupport/lib/active_support/cache/redis_cache_store.rb:83:in
>  `write_entry'
> /<>/activesupport/lib/active_support/cache.rb:465:in `block 
> in write'
> /<>/activesupport/lib/active_support/cache.rb:686:in `block 
> in instrument'
> /<>/activesupport/lib/active_support/notifications.rb:180:in 
> `block in instrument'
> 
> /<>/activesupport/lib/active_support/notifications/instrumenter.rb:24:in
>  `instrument'
> /<>/activesupport/lib/active_support/notifications.rb:180:in 
> `instrument'
> /<>/activesupport/lib/active_support/cache.rb:686:in 
> `instrument'
> /<>/activesupport/lib/active_support/cache.rb:463:in `write'
> 
> /<>/activesupport/test/cache/stores/redis_cache_store_test.rb:275:in
>  `block in '
> 
> rails test 
> <>/activesupport/test/cache/stores/redis_cache_store_test.rb:274
> 
> .
> 
> Finished in 8.270014s, 30.2297 runs/s, 91.1728 assertions/s.
> 250 runs, 754 assertions, 0 failures, 113 errors, 1 skips
> 
> You have skipped tests. Run with --verbose for details.
> rake aborted!
> Command failed with status (1): [ruby -w -I"lib:test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/cache/stores/redis_cache_store_test.rb" --seed=0]
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `block 
> (3 levels) in define'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils.rb:57:in `sh'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils.rb:104:in `ruby'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:117:in `block 
> (2 levels) in define'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/file_utils_ext.rb:58:in 
> `verbose'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:111:in `block 
> in define'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in 
> execute'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in 
> invoke_with_call_chain'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `synchronize'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
> /<>/activesupport/Rakefile:18:in `block in '
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in 
> execute'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in 
> invoke_with_call_chain'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `synchronize'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in 
> `invoke_with_call_chain'
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
> 

Bug#997883: marked as done (rails: autopkgtest needs update for new version of puma: Could not find gem 'puma (~> 4.1)')

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 22:42:36 +
with message-id 
and subject line Bug#997883: fixed in rails 2:6.1.4.1+dfsg-5
has caused the Debian Bug report #997883,
regarding rails: autopkgtest needs update for new version of puma: Could not 
find gem 'puma (~> 4.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.)


-- 
997883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rails
Version: 2:6.0.3.7+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, p...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:puma

Dear maintainer(s),

With a recent upload of puma the autopkgtest of rails fails in testing
when that autopkgtest is run with the binary packages of puma from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
puma   from testing5.3.2-3
rails  from testing2:6.0.3.7+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of puma to testing
[1]. Of course, puma shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in puma 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 puma 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=puma

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rails/16207757/log.gz

 run  bundle install --local
Could not find gem 'puma (~> 4.1)' in cached gems from rubygems repository
https://rubygems.org/ or installed locally.
The source contains the following versions of 'puma': 5.3.2
 run  bundle binstubs bundler
Could not find gem 'puma (~> 4.1)' in locally installed gems.
The source contains the following versions of 'puma': 5.3.2
 run  bundle exec spring binstub --all
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:278:in
`block in verify_gemfile_dependencies_are_found!': Could not find gem
'puma (~> 4.1)' in locally installed gems. (Bundler::GemNotFound)
The source contains the following versions of 'puma': 5.3.2
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`each'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:253:in
`verify_gemfile_dependencies_are_found!'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:50:in
`start'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/resolver.rb:23:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:262:in
`resolve'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:483:in
`materialize'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:234:in
`specs_for'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/runtime.rb:18:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in
`setup'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
`block in '
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:136:in
`with_level'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:88:in
`silence'
from
/usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
`'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
`require'
from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
`require'
+ cd foo
+ rails runner puts "Empty Rails %s app booted correctly" % Rails.version

Bug#996377: marked as done (ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 22:42:36 +
with message-id 
and subject line Bug#996377: fixed in rails 2:6.1.4.1+dfsg-5
has caused the Debian Bug report #996377,
regarding ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
ArgumentError:
to be marked as done.

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

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


-- 
996377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-rails
Version: 4.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-rspec-rails was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> ArgumentError:
>   wrong number of arguments (given 4, expected 3)
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `block in require'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in
>  `load_dependency'
> # 
> /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in
>  `require'
> # ./spec/spec_helper.rb:18:in `'
> No examples found.
> No examples found.
> 
> 
> Finished in 0.00825 seconds (files took 6.98 seconds to load)
> 0 examples, 0 failures, 1 error occurred outside of examples
> 
> Finished in 0.00825 seconds (files took 6.98 seconds to load)
> 0 examples, 0 failures, 1 error occurred outside of examples
> 
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> ./spec/rspec/rails/active_model_spec.rb 
> ./spec/rspec/rails/active_record_spec.rb 
> ./spec/rspec/rails/assertion_adapter_spec.rb 
> ./spec/rspec/rails/assertion_delegator_spec.rb 
> ./spec/rspec/rails/configuration_spec.rb 
> ./spec/rspec/rails/example/channel_example_group_spec.rb 
> ./spec/rspec/rails/example/controller_example_group_spec.rb 
> ./spec/rspec/rails/example/feature_example_group_spec.rb 
> ./spec/rspec/rails/example/helper_example_group_spec.rb 
> ./spec/rspec/rails/example/job_example_group_spec.rb 
> ./spec/rspec/rails/example/mailbox_example_group_spec.rb 
> ./spec/rspec/rails/example/model_example_group_spec.rb 
> 

Bug#1000425: node-cheerio: FTBFS in sid

[Gianfranco Costamagna]

Source: node-cheerio
Version: 1.0.0~rc~10+~cs13.5.2-4
Severity: serious

Hello, some changes in sid made the package FTBFS

 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
mkdir node_modules
ln -s /usr/share/nodejs/css-what ./node_modules/
ln -s /usr/share/nodejs/domelementtype ./node_modules/
ln -s /usr/share/nodejs/jest-diff ./node_modules/
ln -s /usr/share/nodejs/pretty-format ./node_modules/
ln -s /usr/share/nodejs/ts-jest ./node_modules/
ln -s /usr/share/nodejs/tslib ./node_modules/
mkdir -p ./node_modules/\@types
ln -s /usr/share/nodejs/\@types/node ./node_modules/\@types/
ln -s /usr/share/nodejs/\@types/parse5 ./node_modules/\@types/
cp -rL /usr/share/nodejs/css-select ./node_modules/
cp -rL /usr/share/nodejs/domhandler ./node_modules/
cp -rL /usr/share/nodejs/dom-serializer ./node_modules/
cp -rL /usr/share/nodejs/domutils ./node_modules/
cp -rL /usr/share/nodejs/htmlparser2 ./node_modules/
mkdir -p ./node_modules/\@types
cp -rL /usr/share/nodejs/\@types/jest ./node_modules/\@types
ln -s ../cheerio-select node_modules/cheerio-select
ln -s ../parse5-htmlparser2-tree-adapter 
node_modules/parse5-htmlparser2-tree-adapter
ln -s ../../types-parse5-htmlparser2-tree-adapter 
node_modules/\@types/parse5-htmlparser2-tree-adapter
   debian/rules override_dh_auto_build
make[1]: Entering directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/cheerio-select/build
cd ./cheerio-select && sh -ex ../debian/nodejs/cheerio-select/build
+ tsc
No build command found, searching known files
No build command found, searching known files
tsc
src/cheerio.ts:83:9 - error TS2322: Type 'Node' is not assignable to type 'T'.
  'T' could be instantiated with an arbitrary type which could be unrelated to 
'Node'.

83 this[idx] = elem;
   ~


Found 1 error.

make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/node-cheerio-1.0.0~rc~10+~cs13.5.2'


Can you please have a look? thanks

Gianfranco

Processed: bug 997203 is forwarded to https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000=3999=4000

[Debian Bug Tracking System]

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

> forwarded 997203 
> https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000=3999=4000
Bug #997203 [src:gigedit] gigedit: FTBFS: ../compat.h:194:21: error: ‘const 
Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity
Changed Bug forwarded-to-address to 
'https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000=3999=4000'
 from 
'https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000'.
> thanks
Stopping processing here.

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

Processed: bug 997203 is forwarded to https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000

[Debian Bug Tracking System]

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

> forwarded 997203 
> https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000
Bug #997203 [src:gigedit] gigedit: FTBFS: ../compat.h:194:21: error: ‘const 
Pango::Alignment Pango::ALIGN_LEFT’ redeclared as different kind of entity
Set Bug forwarded-to-address to 
'https://svn.linuxsampler.org/cgi-bin/viewvc.cgi/gigedit/trunk/src/gigedit/compat.h?r1=4000'.
> thanks
Stopping processing here.

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

Bug#1000423: python-biom-format: FTBFS with Python 3.10 - Test failures

[Stefano Rivera]

Source: python-biom-format
Version: 2.1.10-2
Severity: serious
Tags: upstream
Justification: FTBFS
Block -1 with 1000422

python-biom-format FTBFS with Python 3.10:
=== short test summary info 
ERROR biom/tests/test_err.py
ERROR biom/tests/test_parse.py
ERROR biom/tests/test_table.py
ERROR biom/tests/test_util.py
ERROR biom/tests/test_cli/test_add_metadata.py
ERROR biom/tests/test_cli/test_show_install_info.py
ERROR biom/tests/test_cli/test_subset_table.py
ERROR biom/tests/test_cli/test_summarize_table.py
ERROR biom/tests/test_cli/test_table_converter.py
ERROR biom/tests/test_cli/test_table_normalizer.py
ERROR biom/tests/test_cli/test_uc_processor.py
ERROR biom/tests/test_cli/test_validate_table.py
!!! Interrupted: 12 errors during collection !!!
== 12 errors in 2.27s ==
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.10_biom-format/build; python3.10 -m pytest

See: 
https://buildd.debian.org/status/fetch.php?pkg=python-biom-format=amd64=2.1.10-2%2Bb1=1637570066=0

I adapted an upstream patch, in 
https://salsa.debian.org/med-team/python-biom-format/-/merge_requests/1

But it still doesn't build because we need pandas, first.

SR

Bug#1000422: pandas: FTBFS with Python 3.10 - Test failures

[Stefano Rivera]

Source: pandas
Version: 1.1.5+dfsg-2
Severity: serious
Justification: FTBFS

Pandas fails to build with Python 3.10.
See: 
https://buildd.debian.org/status/fetch.php?pkg=pandas=amd64=1.1.5%2Bdfsg-2%2Bb1=1637461771=0

=== FAILURES ===
 TestDatetime64SeriesComparison.test_comparison_invalid[None-DataFrame] 

left =0  1  2  3  4
0  0  1  2  3  4
right =0  1  2  3  4
0 2001-01-01 2001-01-02 2001-01-03 2001-01-04 2001-01-05
box = 

def assert_invalid_comparison(left, right, box):
"""
Assert that comparison operations with mismatched types behave 
correctly.

Parameters
--
left : np.ndarray, ExtensionArray, Index, or Series
right : object
box : {pd.DataFrame, pd.Series, pd.Index, tm.to_array}
"""
# Not for tznaive-tzaware comparison

# Note: not quite the same as how we do this for tm.box_expected
xbox = box if box is not Index else np.array

result = left == right
expected = xbox(np.zeros(result.shape, dtype=np.bool_))

tm.assert_equal(result, expected)

result = right == left
tm.assert_equal(result, expected)

result = left != right
tm.assert_equal(result, ~expected)

result = right != left
tm.assert_equal(result, ~expected)

msg = "|".join(
[
"Invalid comparison between",
"Cannot compare type",
"not supported between",
"invalid type promotion",
(
# GH#36706 npdev 1.20.0 2020-09-28
r"The DTypes  and "
r" do not have a common 
DType. "
"For example they cannot be stored in a single array unless 
the "
"dtype is `object`."
),
]
)
with pytest.raises(TypeError, match=msg):
>   left < right

pandas/tests/arithmetic/common.py:89:

Looks like upstream has got there, but a quick search didn't find the
relevant patches, yet:
https://github.com/pandas-dev/pandas/commit/e7efd02c71c48c7968b2f8fdb845a0b0bf61a3fa

SR

Processed: dpkg-shlibdeps: Wrong minimum version requirement on libc6

[Debian Bug Tracking System]

Processing control commands:

> affects -1 cppcheck
Bug #1000421 [dpkg-dev] dpkg-shlibdeps: Wrong minimum version requirement on 
libc6
Added indication that 1000421 affects cppcheck

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

Bug#1000421: dpkg-shlibdeps: Wrong minimum version requirement on libc6

[Joachim Reichel]

Package: dpkg-dev
Version: 1.20.9
Severity: serious
Control: affects -1 cppcheck

Hi,

dpkg-shlibdeps calculates too low minimum version requirements for cppcheck on 
libc6 (see bug 1000146).

To reproduce, build cppcheck 2.6-1 in unstable chroot without cleaning up, 
e.g., "dpkg-buildpackage -rfakeroot -us -uc".

$ grep Depends debian/cppcheck/DEBIAN/control
Depends: libc6 (>= 2.29), [...]

But running the binary with libc6 2.31 fails with

cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by cppcheck)
cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
/lib/x86_64-linux-gnu/libpthread.so.0)

I believe that is the case because a certain symbol in the .bss section is 
ignored (this is the only symbol with 2.32 suffix):

$ objdump -w -T ./debian/cppcheck/usr/bin/cppcheck | grep __libc_single_threaded
004670e0 gDO .bss   0001  GLIBC_2.32  
__libc_single_threaded

$ nm -D ./debian/cppcheck/usr/bin/cppcheck | grep __libc_single_threaded
004670e0 B __libc_single_threaded@@GLIBC_2.32

$ dpkg-shlibdeps ./debian/cppcheck/usr/bin/cppcheck; cat debian/substvars
shlibs:Depends=libc6 (>= 2.29), [...]

After hacking /usr/share/perl5/Dpkg/Shlibs/Objdump.pm:462 to read
"defined => ($sect ne '*UND*') && ($sect ne '.bss')"
(maybe not the right solution, just for demonstration):

$ dpkg-shlibdeps ./debian/cppcheck/usr/bin/cppcheck; cat debian/substvars
shlibs:Depends=libc6 (>= 2.32), [...]

(Not really sure about the severity. I believe the resulting bugs in packagage 
using dpkg-shlipdeps are "serious".)

Best regards,
  Joachim

-- Package-specific info:
System tainted due to merged-usr-via-aliased-dirs.

-- System Information:
Debian Release: 11.1
  APT prefers stable-debug
  APT policy: (800, 'stable-debug'), (800, 'stable'), (500, 'stable-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-9-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 dpkg-dev depends on:
ii  binutils  2.35.2-2
ii  bzip2 1.0.8-4
ii  libdpkg-perl  1.20.9
ii  make  4.3-4.1
ii  patch 2.7.6-7
ii  perl  5.32.1-4+deb11u2
ii  tar   1.34+dfsg-1
ii  xz-utils  5.2.5-2

Versions of packages dpkg-dev recommends:
ii  build-essential  12.9
ii  clang-11 [c-compiler]1:11.0.1-2
ii  fakeroot 1.25.3-1.1
ii  gcc [c-compiler] 4:10.2.1-1
ii  gcc-10 [c-compiler]  10.2.1-6
ii  gnupg2.2.27-2
ii  gpgv 2.2.27-2
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2021.07.26

-- no debconf information

Bug#996380: Explanation

[Daniel Leidert]

It seems here is an explanation of the problem:
https://github.com/paolobrasolin/jekyll-antex/issues/16

I cannot find any patches so far.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000419: pymatgen: FTBFS - Test failure: BSPlotterProjectedTest.test_methods

[Stefano Rivera]

Source: pymatgen
Version: 2022.0.14+dfsg1-1
Severity: serious
Justification: FTBFS

Presumably due to a new matplotlib, but I'm just guessing...

.pybuild/test_python3.9/pymatgen/electronic_structure/tests/test_plotter.py . [ 
55%]
.F

=== FAILURES ===
_ BSPlotterProjectedTest.test_methods __

self = 

def test_methods(self):
self.plotter.get_elt_projected_plots().close()
self.plotter.get_elt_projected_plots_color().close()
self.plotter.get_projected_plots_dots({"Cu": ["d", "s"], "O": 
["p"]}).close()
>   self.plotter.get_projected_plots_dots_patom_pmorb(
{"Cu": ["dxy", "s", "px"], "O": ["px", "py", "pz"]},
{"Cu": [3, 5], "O": [1]},
).close()

.pybuild/test_python3.9/pymatgen/electronic_structure/tests/test_plotter.py:220:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
.pybuild/test_python3.9/pymatgen/electronic_structure/plotter.py:1651: in 
get_projected_plots_dots_patom_pmorb
plt.subplot(row + 1, 2, count)
/usr/lib/python3/dist-packages/matplotlib/pyplot.py:1268: in subplot
key = SubplotSpec._from_subplot_args(fig, args)
/usr/lib/python3/dist-packages/matplotlib/gridspec.py:595: in _from_subplot_args
gs = GridSpec._check_gridspec_exists(figure, rows, cols)
/usr/lib/python3/dist-packages/matplotlib/gridspec.py:223: in 
_check_gridspec_exists
return GridSpec(nrows, ncols, figure=figure)
/usr/lib/python3/dist-packages/matplotlib/gridspec.py:383: in __init__
super().__init__(nrows, ncols,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <[AttributeError("'GridSpec' object has no attribute 
'_row_height_ratios'") raised in repr()] GridSpec object at 0x7f507628bf40>
nrows = 5.5, ncols = 2, height_ratios = None, width_ratios = None

def __init__(self, nrows, ncols, height_ratios=None, width_ratios=None):
"""
Parameters
--
nrows, ncols : int
The number of rows and columns of the grid.
width_ratios : array-like of length *ncols*, optional
Defines the relative widths of the columns. Each column gets a
relative width of ``width_ratios[i] / sum(width_ratios)``.
If not given, all columns will have the same width.
height_ratios : array-like of length *nrows*, optional
Defines the relative heights of the rows. Each column gets a
relative height of ``height_ratios[i] / sum(height_ratios)``.
If not given, all rows will have the same height.
"""
if not isinstance(nrows, Integral) or nrows <= 0:
>   raise ValueError(
f"Number of rows must be a positive integer, not {nrows!r}")
E   ValueError: Number of rows must be a positive integer, not 5.5

/usr/lib/python3/dist-packages/matplotlib/gridspec.py:47: ValueError
- Captured stdout call -
You do not want to sum projection over orbitals.
You do not want to sum projection over atoms.
Number of subfigures: 9
{'start_index': 0, 'end_index': 15, 'name': '\\Gamma-X'}
{'start_index': 16, 'end_index': 31, 'name': 'X-M'}
{'start_index': 32, 'end_index': 47, 'name': 'M-\\Gamma'}
{'start_index': 48, 'end_index': 63, 'name': '\\Gamma-R'}
{'start_index': 64, 'end_index': 79, 'name': 'R-X'}
{'start_index': 80, 'end_index': 95, 'name': 'M-R'}
dictio_d: {'Cu': ['dxy', 's', 'px'], 'O': ['px', 'py', 'pz']}
dictpa_d: {'Cu': ['3', '5'], 'O': ['1']}
=== warnings summary ===


See: 
https://buildd.debian.org/status/fetch.php?pkg=pymatgen=amd64=2022.0.14%2Bdfsg1-1%2Bb1=1637567905=0

SR

Bug#998532: marked as done (dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "per_library_versions")

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 21:19:37 +
with message-id 
and subject line Bug#998532: fixed in dpdk 20.11.3-2
has caused the Debian Bug report #998532,
regarding dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: 
"per_library_versions"
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure --  \
>   --includedir=include/dpdk \
>   --default-library=shared \
>   -Dper_library_versions=false \
>   -Dinclude_subdir_arch=../x86_64-linux-gnu/dpdk \
>   -Dmachine="default"
>   install -d obj-x86_64-linux-gnu
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --includedir=include/dpdk 
> --default-library=shared -Dper_library_versions=false 
> -Dinclude_subdir_arch=../x86_64-linux-gnu/dpdk -Dmachine=default
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Program cat found: YES (/bin/cat)
> 
> ../meson.build:4:0: ERROR: Unknown options: "per_library_versions"
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2021-11-04T08:54:47.258619
> Main binary: /usr/bin/python3
> Build Options: -Dper_library_versions=false 
> -Dinclude_subdir_arch=../x86_64-linux-gnu/dpdk -Dmachine=default 
> -Dprefix=/usr -Dincludedir=include/dpdk -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Ddefault_library=shared -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Program cat found: YES (/bin/cat)
> Running command: /bin/cat /<>/VERSION
> --- stdout ---
> 20.11.3
> 
> --- stderr ---
> 
> 
> 
> ../meson.build:4:0: ERROR: Unknown options: "per_library_versions"
> dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --includedir=include/dpdk 
> --default-library=shared -Dper_library_versions=false 
> -Dinclude_subdir_arch=../x86_64-linux-gnu/dpdk -Dmachine=default returned 
> exit code 1
> make[1]: *** [debian/rules:85: override_dh_auto_configure] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/dpdk_20.11.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: dpdk
Source-Version: 20.11.3-2
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
dpdk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated dpdk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 20:18:15 +
Source: dpdk
Architecture: source
Version: 20.11.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian DPDK Maintainers 
Changed-By: Luca Boccassi 
Closes: 998532

Bug#1000417: devscripts: autopkgtest regression: zstd: not found

[Paul Gevers]

Source: devscripts
Version: 2.21.5
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
devscripts from testing2.21.5
all others from testingfrom testing

I copied some of the output at the bottom of this report. Seems like 
you're missing a (test) dependency.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/devscripts/16896916/log.gz

testSymlink
testSymlinkWithConvertedSig
testSymlinkWithArmoredSig
testCopy
testRename
testSymlinkExplicit
testCopyExplicit
testRenameExplicit
testSymlinkExplicitSubdir
testRepackGZ2GZ
testForceRepackGZ2XZ
testRepackGZ2XZ
testRepackXZ2GZ
testRepackZST2XZRepackOpt
/bin/sh: 1: zstd: not found
tar: /tmp/shunit.58aiKV/tmp/test_mk-origtargz.zy3M/foo-0.1.tar.zst: 
Cannot write: Broken pipe

tar: Child returned status 127
tar: Error is not recoverable: exiting now
ASSERT:standard output of mk-origtargz --package foo --version 0.1 
--copy foo-0.1.tar.zst --repack\n expected:foo-0.1.tar.zst as foo_0.1.orig.tar.xz.> but was:<>
ASSERT:error output of mk-origtargz --package foo --version 0.1 --copy 
foo-0.1.tar.zst --repack\n expected:<> but was:Unknown compression used in foo-0.1.tar.zst>

ASSERT:result does not exist
ASSERT:filetype for foo_0.1.orig.tar.xz expected: but 
was:`/tmp/shunit.58aiKV/tmp/test_mk-origtargz.zy3M/foo_0.1.orig.tar.xz' (No 
such file or directory)>

testRepackZST2XZNoRepackOpt
/bin/sh: 1: zstd: not found
tar: /tmp/shunit.58aiKV/tmp/test_mk-origtargz.gH3Z/foo-0.1.tar.zst: 
Cannot write: Broken pipe

tar: Child returned status 127
tar: Error is not recoverable: exiting now
ASSERT:standard output of mk-origtargz --package foo --version 0.1 
--copy foo-0.1.tar.zst\n expected:as foo_0.1.orig.tar.xz.> but was:<>
ASSERT:error output of mk-origtargz --package foo --version 0.1 --copy 
foo-0.1.tar.zst\n expected:<> but was:compression used in foo-0.1.tar.zst>

ASSERT:result does not exist
ASSERT:filetype for foo_0.1.orig.tar.xz expected: but 
was:`/tmp/shunit.58aiKV/tmp/test_mk-origtargz.gH3Z/foo_0.1.orig.tar.xz' (No 
such file or directory)>

testRepackZST2ZSTFail
/bin/sh: 1: zstd: not found
tar: /tmp/shunit.58aiKV/tmp/test_mk-origtargz.EdLV/foo-0.1.tar.zst: 
Cannot write: Broken pipe

tar: Child returned status 127
tar: Error is not recoverable: exiting now
testRepackZip2GZ
testRepackJar2GZ
testRepackZip2GZRename
testRepackZip2XZ
testRepackXpi2XZ
testRepackTAR2XZ
testOldFormat
testExclude
testGoVendorIncludeIgnore
testExcludeXZ
testExcludeZip
testSuffix
testSuffixXZ
testSuffixZip
testSuffixNoExclusions
testSameNameSymlink
testSameNameCopy
testSameNameRename
testSameNameExclude
testSameNameExcludeSymlink
testCopyrightFormatWarning
testBrokenTarWarning
testUnmatchedExclusion
testDuplicatePattern

Ran 40 tests.

FAILED (failures=8)
make[1]: *** [Makefile:43: test_mk-origtargz.test_installed] Error 1
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.7_8glf45/downtmp/build.uPh/src/test'

make: *** [Makefile:47: test-installed] Error 2
autopkgtest [11:12:56]: test shunit2




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1000414: textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1

[Paul Gevers]

Source: textdistance
Version: 4.2.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of textdistance the autopkgtest of textdistance 
fails in testing when that autopkgtest is run with the binary packages 
of textdistance from unstable on arm64. It passes when run with only 
packages from testing. In tabular form:


   passfail
textdistance   from testing4.2.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/arm64/t/textdistance/16584010/log.gz

=== FAILURES 
===
___ test_normalization_range[alg23] 



alg = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K', 
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G', 
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})


@pytest.mark.parametrize('alg', ALGS)

  @hypothesis.given(

left=hypothesis.strategies.text(),
right=hypothesis.strategies.text(),
)

tests/test_common.py:50: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

left = '0', right = 'ῢ'
alg = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K', 
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G', 
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})


@pytest.mark.parametrize('alg', ALGS)
@hypothesis.given(
left=hypothesis.strategies.text(),
right=hypothesis.strategies.text(),
)
def test_normalization_range(left, right, alg):

  assert 0 <= alg.normalized_distance(left, right) <= 1

E   AssertionError: assert 3.0 <= 1
E+  where 3.0 = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local': 
False... 'B', 'K', 'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 
'E', 'N', 'J', 'G', 'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})>('0', 'ῢ')
E+where Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local': 
False... 'B', 'K', 'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 
'E', 'N', 'J', 'G', 'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})> = 
Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local': 
False, 'external': True, 'grouped': frozenset({'U', 'B', 'K', 'F', 'D', 
'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G', 'V', 'L', 
'I', 'R', 'O', 'A', 'Y'})}).normalized_distance


tests/test_common.py:55: AssertionError
-- Hypothesis 
--

Falsifying example: test_normalization_range(
left='0',
right='ῢ',
alg=Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K', 
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G', 
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})}),

)
=== warnings summary 
===

tests/test_external.py:16

/tmp/autopkgtest-lxc.iu33ychk/downtmp/autopkgtest_tmp/tests/test_external.py:16: 
PytestUnknownMarkWarning: Unknown pytest.mark.external - is this a typo? 
 You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.external

tests/test_external.py:39

/tmp/autopkgtest-lxc.iu33ychk/downtmp/autopkgtest_tmp/tests/test_external.py:39: 
PytestUnknownMarkWarning: Unknown pytest.mark.external - is this a typo? 
 You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.external

tests/test_external.py:67

/tmp/autopkgtest-lxc.iu33ychk/downtmp/autopkgtest_tmp/tests/test_external.py:67: 
PytestUnknownMarkWarning: Unknown pytest.mark.external - is this a typo? 
 You can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html

@pytest.mark.external

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 

FAILED tests/test_common.py::test_normalization_range[alg23] - 
AssertionError...
== 1 failed, 397 passed, 3 warnings in 54.22s 
==

autopkgtest [23:19:58]: test pytest




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1000413: discosnp: autopkgtest regression: Segmentation fault

[Paul Gevers]

Source: discosnp
Version: 1:2.5.4-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
discosnp   from testing1:2.5.4-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. As the test 
passes in unstable and because of bug #998143 I wonder if the update of 
gatb-core wasn't an ABI breakage and should have seen a SONAME bump and 
a proper transition. As this package and gatb-core are handled in the 
same team, I'll leave you to figure it out. I think you'd want to block 
gatb-core from migrating.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
discosnp/1:2.5.4-1. I.e. due to versioned dependencies or breaks/conflicts.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/d/discosnp/16901493/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/d/discosnp/16901493/log.gz

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified


 Running discoSnp++ 2.3.X, in directory /usr with following parameters:
 read_sets=fof.txt
 prefix=discoRes_k_31_c_3
 c=3
 C=2147483647
 k=31
 b=0
 d=1
 D=100
 s=
 P=3
 p=discoRes
 G=
 e=
 starting date=Mon Nov 22 15:13:02 UTC 2021


 
  GRAPH CREATION  ###
 
/usr/bin/dbgh5 -in 
fof.txt_discoRes_k_31_c_3_D_100_P_3_b_0_removemeplease -out 
discoRes_k_31_c_3 -kmer-size 31 -abundance-min 3 -abundance-max 
2147483647 -solidity-kind one -verbose 1 -skip-bcalm -skip-bglue -no-mphf


[DSK: counting kmers ]  0%   elapsed:   0 min 0 
 sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  25,   25, 
57] MB [DSK: Pass 1/1, Step 1: partitioning ]  0%   elapsed:   0 
min 0  sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  53, 
53,   57] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  26.4 % 
elapsed:   0 min 1  sec   remaining:   0 min 3  sec   cpu: 102.7 % 
mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: counting kmers   ] 
26.4 %   elapsed:   0 min 1  sec   remaining:   0 min 3  sec   cpu: 
102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: counting 
kmers   ]  26.4 %   elapsed:   0 min 1  sec   remaining:   0 min 3  sec 
  cpu: 102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: 
counting kmers   ]  26.4 %   elapsed:   0 min 1  sec   remaining:   0 
min 3  sec   cpu: 102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, 
Step 2: counting kmers   ]  26.4 %   elapsed:   0 min 1  sec 
remaining:   0 min 3  sec   cpu: 102.7 %   mem: [  86,   86,  847] MB 
[DSK: Pass 1/1, Step 2: counting kmers   ]  26.4 %   elapsed:   0 min 1 
 sec   remaining:   0 min 3  sec   cpu: 102.7 %   mem: [  86,   86, 
847] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  26.4 %   elapsed: 
0 min 1  sec   remaining:   0 min 3  sec   cpu: 102.7 %   mem: [  86, 
86,  847] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  26.4 % 
elapsed:   0 min 1  sec   remaining:   0 min 3  sec   cpu: 102.7 % 
mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: counting kmers   ] 
26.4 %   elapsed:   0 min 1  sec   remaining:   0 min 3  sec   cpu: 
102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: counting 
kmers   ]  26.4 %   elapsed:   0 min 1  sec   remaining:   0 min 3  sec 
  cpu: 102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, Step 2: 
counting kmers   ]  26.4 %   elapsed:   0 min 1  sec   remaining:   0 
min 3  sec   cpu: 102.7 %   mem: [  86,   86,  847] MB [DSK: Pass 1/1, 
Step 2: counting kmers   ]  26.4 %   elapsed:   0 min 1  sec 
remaining:   0 min 3  sec   cpu: 102.7 %   mem: [  86,   86,  847] MB 
[DSK: Pass 1/1, Step 2: counting kmers   ]  26.4 %   elapsed:   0 min 1 
 sec   remaining:   0 min 3  sec   cpu: 102.7 %   mem: [  86,   86, 
847] MB [DSK: 

Bug#997882: marked as done (licensecheck: autopkgtest regression: lots of failures)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 21:04:04 +
with message-id 
and subject line Bug#997882: fixed in licensecheck 3.2.14-1
has caused the Debian Bug report #997882,
regarding licensecheck: autopkgtest regression: lots of failures
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.)


-- 
997882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: licensecheck
Version: 3.2.13-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
licensecheck   from testing3.2.13-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/l/licensecheck/16222812/log.gz

t/OSI.t .. # Seeded srand with seed '20211026' from
local date.
1..26
ok 1 - Corpus file t/OSI/MPL-1.0
ok 2 - Corpus file t/OSI/EPL-1.0
ok 3 - Corpus file t/OSI/RPSL-1.0
ok 4 - Corpus file t/OSI/Artistic-2.0
ok 5 - Corpus file t/OSI/Python-2.0
ok 6 - Corpus file t/OSI/Zlib
ok 7 - Corpus file t/OSI/AFL-3.0
ok 8 - Corpus file t/OSI/GPL-2.0
ok 9 - Corpus file t/OSI/BSL-1.0
ok 10 - Corpus file t/OSI/LGPL-2.0
ok 11 - Corpus file t/OSI/MPL-1.1
ok 12 - Corpus file t/OSI/CECILL-2.1
ok 13 - Corpus file t/OSI/Apache-2.0
ok 14 - Corpus file t/OSI/AGPL-3.0
ok 15 - Corpus file t/OSI/NTP
ok 16 - Corpus file t/OSI/Artistic-1.0-Perl
ok 17 - Corpus file t/OSI/PostgreSQL
ok 18 - Corpus file t/OSI/MPL-2.0
ok 19 - Corpus file t/OSI/OFL-1.1
ok 20 - Corpus file t/OSI/CDDL-1.0
ok 21 - Corpus file t/OSI/BSD-3-Clause
ok 22 - Corpus file t/OSI/MIT
ok 23 - Corpus file t/OSI/BSD-2-Clause-Views
ok 24 - Corpus file t/OSI/QPL-1.0
ok 25 - Corpus file t/OSI/LGPL-2.1
ok 26 - Corpus file t/OSI/ISC
ok
t/SPDX.t . # Seeded srand with seed '20211026' from
local date.
1..88
ok 1 - Corpus file t/SPDX/CC-BY-2.5.txt
ok 2 - Corpus file t/SPDX/CC-BY-SA-4.0.txt
ok 3 - Corpus file t/SPDX/CC-BY-NC-ND-4.0.txt
ok 4 - Corpus file t/SPDX/CC-BY-NC-SA-3.0.txt
ok 5 - Corpus file t/SPDX/BSD-3-Clause.txt
ok 6 - Corpus file t/SPDX/CC-BY-SA-2.0.txt
ok 7 - Corpus file t/SPDX/AFL-2.0.txt
ok 8 - Corpus file t/SPDX/LGPL-2.0.txt
ok 9 - Corpus file t/SPDX/zlib-acknowledgement.txt
ok 10 - Corpus file t/SPDX/MS-RL.txt
ok 11 - Corpus file t/SPDX/Apache-2.0.txt
ok 12 - Corpus file t/SPDX/OFL-1.0.txt
ok 13 - Corpus file t/SPDX/Zlib.txt
ok 14 - Corpus file t/SPDX/Eurosym.txt
ok 15 - Corpus file t/SPDX/ISC.txt
ok 16 - Corpus file t/SPDX/MIT-feh.txt
ok 17 - Corpus file t/SPDX/CC-BY-SA-3.0.txt
ok 18 - Corpus file t/SPDX/MIT-CMU.txt
ok 19 - Corpus file t/SPDX/Artistic-1.0.txt
ok 20 - Corpus file t/SPDX/WTFPL.txt
ok 21 - Corpus file t/SPDX/EPL-1.0.txt
ok 22 - Corpus file t/SPDX/CC-BY-NC-2.5.txt
ok 23 - Corpus file t/SPDX/CDDL-1.0.txt
ok 24 - Corpus file t/SPDX/CC0-1.0.txt
ok 25 - Corpus file t/SPDX/MIT.txt
ok 26 - Corpus file t/SPDX/CC-BY-1.0.txt
ok 27 - Corpus file t/SPDX/AGPL-1.0.txt
ok 28 - Corpus file t/SPDX/AFL-3.0.txt
ok 29 - Corpus file t/SPDX/CC-BY-SA-2.5.txt
ok 30 - Corpus file t/SPDX/ICU.txt
ok 31 - Corpus file t/SPDX/AFL-2.1.txt
ok 32 - Corpus file t/SPDX/CC-BY-NC-3.0.txt
ok 33 - Corpus file t/SPDX/SGI-B-1.1.txt
ok 34 - Corpus file t/SPDX/CC-BY-ND-3.0.txt
ok 35 - Corpus file t/SPDX/Python-2.0.txt
ok 36 - Corpus file t/SPDX/CC-BY-NC-SA-1.0.txt
ok 37 - Corpus file t/SPDX/CC-BY-NC-4.0.txt
ok 38 - Corpus file t/SPDX/CECILL-1.0.txt
ok 39 - Corpus file t/SPDX/MS-PL.txt
ok 40 - Corpus file t/SPDX/MPL-1.0.txt
ok 41 - Corpus file t/SPDX/CC-BY-NC-SA-2.5.txt
ok 42 - Corpus file t/SPDX/MPL-2.0.txt
ok 43 - Corpus file t/SPDX/Libpng.txt
ok 44 - Corpus file t/SPDX/OFL-1.1.txt
ok 45 - Corpus file t/SPDX/Cube.txt
ok 46 - Corpus file t/SPDX/CC-BY-3.0.txt
ok 47 - Corpus file t/SPDX/CC-BY-ND-1.0.txt
ok 48 - Corpus file t/SPDX/CC-BY-NC-ND-1.0.txt
ok 49 - Corpus file t/SPDX/CC-BY-SA-1.0.txt
ok 50 - Corpus file 

Bug#997882: marked as pending in licensecheck

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #997882 in licensecheck 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/perl-team/modules/packages/licensecheck/-/commit/f346257c1685ba35c4235a769ec7aa828598768d


fix tests to use executable set in environment variable LICENSECHECK; closes: 
bug#997882, thanks to Paul Gevers


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997882

Bug#997882: marked as pending in licensecheck

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #997882 in licensecheck 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/perl-team/modules/packages/licensecheck/-/commit/f346257c1685ba35c4235a769ec7aa828598768d


fix tests to use executable set in environment variable LICENSECHECK; closes: 
bug#997882, thanks to Paul Gevers


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997882

Processed: Bug#997882 marked as pending in licensecheck

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997882 [src:licensecheck] licensecheck: autopkgtest regression: lots of 
failures
Added tag(s) pending.

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

Processed: Bug#997882 marked as pending in licensecheck

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997882 [src:licensecheck] licensecheck: autopkgtest regression: lots of 
failures
Ignoring request to alter tags of bug #997882 to the same tags previously set

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

Bug#997718: glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch' in '/<>/webapp-src/node_modules/i18next-http-backend/cjs'

[Nicolas Mora]

Hello,

The package node-cross-fetch is in the NEW queue [1].
When it will be accepted in unstable, a quick change in the package 
i18next-http-backend will fix glewlwyd's ftbfs.


/Nicolas

[1] https://ftp-master.debian.org/new/node-cross-fetch_3.1.4%2Bds.1-1.html

Bug#1000412: poetry-core: autopkgtest regression: No such file or directory: 'git'

[Paul Gevers]

Source: poetry-core
Version: 1.0.7-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
poetry-corefrom testing1.0.7-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=poetry-core

https://ci.debian.net/data/autopkgtest/testing/amd64/p/poetry-core/16881615/log.gz


=== FAILURES 
===
__ test_git_clone_raises_error_on_invalid_repository 
___


def test_git_clone_raises_error_on_invalid_repository():
with pytest.raises(GitError):

  Git().clone("-u./payload", Path("foo"))


tests/vcs/test_vcs.py:273: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/poetry/core/vcs/git.py:228: in __init__

self._config = GitConfig(requires_git_presence=True)
/usr/lib/python3/dist-packages/poetry/core/vcs/git.py:206: in __init__
subprocess.check_output(
/usr/lib/python3.9/subprocess.py:424: in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
/usr/lib/python3.9/subprocess.py:505: in run
with Popen(*popenargs, **kwargs) as process:
/usr/lib/python3.9/subprocess.py:951: in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
args = ['git', 'config', '-l'], executable = b'git', preexec_fn = None
close_fds = True, pass_fds = (), cwd = None, env = None, startupinfo = None
creationflags = 0, shell = False, p2cread = -1, p2cwrite = -1, c2pread = 11
c2pwrite = 12, errread = -1, errwrite = 12, restore_signals = True, gid 
= None

gids = None, uid = None, umask = -1, start_new_session = False

def _execute_child(self, args, executable, preexec_fn, close_fds,
   pass_fds, cwd, env,
   startupinfo, creationflags, shell,
   p2cread, p2cwrite,
   c2pread, c2pwrite,
   errread, errwrite,
   restore_signals,
   gid, gids, uid, umask,
   start_new_session):
"""Execute program (POSIX version)"""
if isinstance(args, (str, bytes)):
args = [args]
elif isinstance(args, os.PathLike):
if shell:
raise TypeError('path-like args is not allowed when '
'shell is true')
args = [args]
else:
args = list(args)
if shell:
# On Android the default shell is at '/system/bin/sh'.
unix_shell = ('/system/bin/sh' if
  hasattr(sys, 'getandroidapilevel') else '/bin/sh')
args = [unix_shell, "-c"] + args
if executable:
args[0] = executable
if executable is None:
executable = args[0]
sys.audit("subprocess.Popen", executable, args, cwd, env)
if (_USE_POSIX_SPAWN
and os.path.dirname(executable)
and preexec_fn is None
and not close_fds
and not pass_fds
and cwd is None
and (p2cread == -1 or p2cread > 2)
and (c2pwrite == -1 or c2pwrite > 2)
and (errwrite == -1 or errwrite > 2)
and not start_new_session
and gid is None
and gids is None
and uid is None
and umask < 0):
self._posix_spawn(args, executable, env, restore_signals,
  p2cread, p2cwrite,
  c2pread, c2pwrite,
  errread, errwrite)
return
orig_executable = executable
# For transferring possible exec failure from child to parent.
# Data format: "exception name:hex errno:description"
# Pickle is not used; it is complex and involves memory allocation.
errpipe_read, errpipe_write = os.pipe()
# errpipe_write must not be in the standard io 0, 1, or 2 fd range.
low_fds_to_close = []
while errpipe_write < 3:

Bug#998353: src:win32-loader: fails to migrate to testing for too long

[Paul Gevers]

Dear Debian-boot,

On Tue, 2 Nov 2021 20:55:11 +0100 Paul Gevers  wrote:

Can somebody please judge if win32-loader should
migrate in the current state and take appropriate actions if so: contact
ftp to process the package on their side and update bug 982838 (I
wouldn't close it, but reuse it after migration) with the right meta
info such that the bug doesn't block migration? If help is needed,
please reach out to the Release Team.


I didn't see any follow-up on this request. I had a look at the 
changelog, it seems trivial. Is it worth doing the ftp-master dance?


 win32-loader (0.10.5) unstable; urgency=medium
 .
   [ Valentin Vidic ]
   * Update Croatian translation
 .
   [ Didier Raboud ]
   * Run wrap-and-sort -baskt
   * Remove myself from Uploaders

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#998532 marked as pending in dpdk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #998532 [src:dpdk] dpdk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: 
"per_library_versions"
Added tag(s) pending.

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

Bug#998532: marked as pending in dpdk

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #998532 in dpdk reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/dpdk/-/commit/afd4179197d106a51df8406995422df6fdd0b423


d/rules: drop per_library_versions removed since 19.11 (Closes: #998532)

Signed-off-by: Christian Ehrhardt 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998532

Bug#997172: marked as done (sngrep: FTBFS: curses/ui_manager.c:668:5: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 18:50:32 +
with message-id 
and subject line Bug#997172: fixed in sngrep 1.4.10-1
has caused the Debian Bug report #997172,
regarding sngrep: FTBFS: curses/ui_manager.c:668:5: error: format not a string 
literal and no format arguments [-Werror=format-security]
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/p11-kit-1   -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> curses/sngrep-ui_call_list.o `test -f 'curses/ui_call_list.c' || echo 
> './'`curses/ui_call_list.c
> curses/ui_manager.c: In function ‘dialog_confirm’:
> curses/ui_manager.c:668:5: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   668 | mvwprintw(dialog_win, 1, (width - strlen(title)) / 2, title);
>   | ^
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/p11-kit-1   -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> curses/sngrep-ui_call_flow.o `test -f 'curses/ui_call_flow.c' || echo 
> './'`curses/ui_call_flow.c
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/p11-kit-1   -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> curses/sngrep-ui_call_raw.o `test -f 'curses/ui_call_raw.c' || echo 
> './'`curses/ui_call_raw.c
> curses/ui_call_flow.c: In function ‘call_flow_draw_message’:
> curses/ui_call_flow.c:574:62: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>   574 | mvwprintw(flow_win, cline + 1, startpos + 5, 
> mediastr);
>   |  ^~~~
> curses/ui_call_flow.c:576:100: error: format not a string literal and no 
> format arguments [-Werror=format-security]
>   576 | mvwprintw(flow_win, cline + 1, startpos + distance / 
> 2 - strlen(mediastr) / 2 + 2, mediastr);
>   |   
>  ^~~~
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/p11-kit-1   -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> curses/sngrep-ui_stats.o `test -f 'curses/ui_stats.c' || echo 
> './'`curses/ui_stats.c
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:877: curses/sngrep-ui_manager.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sngrep_1.4.9-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: sngrep
Source-Version: 1.4.10-1
Done: Victor Seva 

We believe that the bug you reported is fixed in the latest version of
sngrep, 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.
Victor Seva  (supplier of updated sngrep package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 19:28:18 +0100
Source: sngrep
Architecture: source
Version: 1.4.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Victor Seva 
Closes: 997172
Changes:
 sngrep 

Bug#997248: marked as done (mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive])

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 18:33:44 +
with message-id 
and subject line Bug#997248: fixed in mysql++ 3.2.5-2.1
has caused the Debian Bug report #997248,
regarding mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address 
of rvalue [-fpermissive]
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.)


-- 
997248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql++
Version: 3.2.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> g++ -c -o resetdb_resetdb.o -Ilib -I/usr/include/mysql  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> ./examples/resetdb.cpp
> ./examples/load_jpeg.cpp: In function ‘bool load_jpeg_file(const 
> mysqlpp::examples::CommandLine&, images&, std::string&)’:
> ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]
>90 | &(stringstream() << 
> img_file.rdbuf()))->str();
>   |  ^~~~
> g++ -c -o simple1_simple1.o -Ilib -I/usr/include/mysql  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> ./examples/simple1.cpp
> make[1]: *** [Makefile:794: load_jpeg_load_jpeg.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/mysql++_3.2.5-2_unstable.log

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

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

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

We believe that the bug you reported is fixed in the latest version of
mysql++, 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.
Sascha Steinbiss  (supplier of updated mysql++ 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: Mon, 22 Nov 2021 13:01:43 +0100
Source: mysql++
Architecture: source
Version: 3.2.5-2.1
Distribution: unstable
Urgency: medium
Maintainer: Athena Capital Research 
Changed-By: Sascha Steinbiss 
Closes: 997248
Changes:
 mysql++ (3.2.5-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Incorporate patch from upstream to fix build on newer GCC versions.
 (Closes: #997248)
Checksums-Sha1:
 f7c85bdf920498b35a09a00898d248d261b1bced 1967 mysql++_3.2.5-2.1.dsc
 f40d90544fc055eef20101f35ab10eb368b05710 9600 mysql++_3.2.5-2.1.debian.tar.xz
Checksums-Sha256:
 e81e72b2e90eb36299e64c8724d45ab9bacf1775bffc7f7c98633b999e12d5e2 1967 
mysql++_3.2.5-2.1.dsc
 cf3b44d46b3609ab872583361e7476f08f75d4cca71e6f6880bcbc1d8db4a379 9600 
mysql++_3.2.5-2.1.debian.tar.xz
Files:
 2a82af471ebb11d9e6550c463bf8c3df 1967 libs optional mysql++_3.2.5-2.1.dsc
 09859a612717789bb51ee53bcebf4d8d 9600 libs optional 
mysql++_3.2.5-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAmGbw24ACgkQ6NN64vCf
SHJA9g/+IHj+V0cbofQ5hL5PFRXCZtrk17MQzdP5CH5k4zUJ3SXOH3ivoYAsLGOL
quVZw14ygH37pEe4bxcXVFz/deGqjYnIYxw30faSL5GiuhOV9Aaq6X7Aa5tQKhYO
51/xdRYfvd1j39jPEbP5Lj3j/qgAAhXmxw/ilwaNh7Eyo4LdUWBai99Q00uvJ7kJ
SUIQngGl47w0TfNsNaL3HKnXUcNCy8RnJscOBjCrcOjmdrQLLaHrTmnGEThQqZG5
1432TNkZgPX+DGpluKQk6pW7Ut5J8ZxtXjhdsHbfWz6avxv96qBOaXRQmWpr4jlP
bI41OoMK9eZU03LpoXh7ii3BfINDPcleBlXrW+CxBXf5k8VwJk6zjfjj+EMdNOxQ
/JwfvbXp7CaTneHQUq+NwvKywAg6qLUHMfsGxCpyHduDQi2nAQrKr1kHzNLNS6bt
uF7c1TszV0CRaQ+ctg5Zf31Tm+ri1RflC/iOgrNxgHSypSghp6f1sNktBqYt3UDk

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1000220 pending patch
Bug #1000220 [src:dcmtk] dicomscope: error: cannot bind non-const lvalue 
reference of type ‘std::__cxx11::list 
>::const_iterator&’ to an rvalue of type ‘std::__cxx11::list >::const_iterator’
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1000357: marked as done (ddcci-dkms: install and module build failure with Linux 5.15: error: initialization of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct device *)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 17:49:40 +
with message-id 
and subject line Bug#1000357: fixed in ddcci-driver-linux 0.4.1-2
has caused the Debian Bug report #1000357,
regarding ddcci-dkms: install and module build failure with Linux 5.15: error: 
initialization of 'void (*)(struct device *)' from incompatible pointer type 
'int (*)(struct device *)' [-Werror=incompatible-pointer-types]
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.)


-- 
1000357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ddcci-dkms
Version: 0.4.1-1
Severity: serious

When I try to install ddcci-dkms with linux-headers-amd64 5.15.3-1
installed, the installation fails because the build of the ddcci module
fails because of an incompatible pointer type in the source code:

   $ sudo apt install linux-headers-amd64
   ...
   
   $ sudo apt install ddcci-dkms
   ...
   Setting up ddcci-dkms (0.4.1-1) ...
   Loading new ddcci-0.4.1 DKMS files...
   Building for 5.15.0-1-amd64
   Building initial module for 5.15.0-1-amd64
   Error! Bad return status for module build on kernel: 5.15.0-1-amd64 (x86_64)
   Consult /var/lib/dkms/ddcci/0.4.1/build/make.log for more information.
   dpkg: error processing package ddcci-dkms (--configure):
installed ddcci-dkms package post-installation script subprocess returned 
error exit status 10
   Processing triggers for libc-bin (2.32-4) ...
   Errors were encountered while processing:
ddcci-dkms
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   
   $ cat /var/lib/dkms/ddcci/0.4.1/build/make.log
   DKMS make.log for ddcci-0.4.1 for kernel 5.15.0-1-amd64 (x86_64)
   Mon Nov 22 01:53:32 UTC 2021
   make: Entering directory '/var/lib/dkms/ddcci/0.4.1/build'
   make -C "ddcci"
   make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci'
   make -C "/lib/modules/5.15.0-1-amd64/build" 
M="/var/lib/dkms/ddcci/0.4.1/build/ddcci" modules
   make[2]: Entering directory '/usr/src/linux-headers-5.15.0-1-amd64'
 CC [M]  /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o
   /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization 
of 'void (*)(struct device *)' from incompatible pointer type 'int (*)(struct 
device *)' [-Werror=incompatible-pointer-types]
1295 | .remove = ddcci_device_remove
 |   ^~~
   /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: note: (near 
initialization for 'ddcci_bus_type.remove')
   cc1: some warnings being treated as errors
   make[3]: *** 
[/usr/src/linux-headers-5.15.0-1-common/scripts/Makefile.build:282: 
/var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o] Error 1
   make[2]: *** [/usr/src/linux-headers-5.15.0-1-common/Makefile:1892: 
/var/lib/dkms/ddcci/0.4.1/build/ddcci] Error 2
   make[2]: Leaving directory '/usr/src/linux-headers-5.15.0-1-amd64'
   make[1]: *** [Makefile:38: ddcci.ko] Error 2
   make[1]: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build/ddcci'
   make: *** [Makefile:28: ddcci] Error 2
   make: Leaving directory '/var/lib/dkms/ddcci/0.4.1/build'

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates-debug'), (860, 'testing-proposed-updates'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ddcci-dkms depends on:
ii  dkms  2.8.7-2

ddcci-dkms recommends no packages.

ddcci-dkms suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: ddcci-driver-linux
Source-Version: 0.4.1-2
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
ddcci-driver-linux, 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 1000...@bugs.debian.org,

Processed: [bts-link] source package src:mod-wsgi

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:mod-wsgi
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #999857 (http://bugs.debian.org/999857)
> # Bug title: mod-wsgi FTBFS with python 3.10 as supported version
> #  * https://github.com/GrahamDumpleton/mod_wsgi/pull/688
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 999857 + fixed-upstream
Bug #999857 [src:mod-wsgi] mod-wsgi FTBFS with python 3.10 as supported version
Added tag(s) fixed-upstream.
> usertags 999857 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#998867: debootstrap: --no-merged-usr became a no-op

[Julien Cristau]

On Mon, Nov 15, 2021 at 01:54:36PM +, Dimitri John Ledkov wrote:
> > Also, build chroots must still be created without merged-usr for 
> > sid/bookworm, until something's been done to migrate user systems.
> 
> But Julien, you said that buildds run stable, meaning they are
> unaffected by this debootstrap change in sid/bookworm.
> 
This isn't just about buildds, it's about everything that builds Debian
packages.  (And even if it was just about buildds, we should still do
things in the right order.)

Cheers,
Julien

Processed: Re: maxima-emacs: fails to install with xemacs21

[Debian Bug Tracking System]

Processing control commands:

> found -1 5.45.1-5
Bug #999626 {Done: Camm Maguire } [maxima-emacs] maxima-emacs: 
fails to install with xemacs21
Marked as found in versions maxima/5.45.1-5; no longer marked as fixed in 
versions maxima/5.45.1-5 and reopened.

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

Bug#999626: maxima-emacs: fails to install with xemacs21

[Andreas Beckmann]

Followup-For: Bug #999626
Control: found -1 5.45.1-5

Hi,

the bug is still present, but with a slightly different error message:

  Setting up maxima-emacs (5.45.1-5) ...
  Install emacsen-common for xemacs21
  emacsen-common: Handling install of emacsen flavor xemacs21
  Loading /usr/share/emacsen-common/debian-startup...
  Loading 00debian...
  Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
  Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
  Done
  Install maxima-emacs for xemacs21
  install/maxima: Handling install for emacsen flavor xemacs21
  Compiling /usr/share/xemacs21/site-lisp/maxima/bookmode.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/bookmode.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/emaxima.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/emaxima.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/imath.el...
  While compiling toplevel forms in file 
/usr/share/xemacs21/site-lisp/maxima/imath.el:
!! Symbol's value as variable is void ((image-map))
  >>Error occurred processing imath.el: 
  Symbol's value as variable is void: image-map
  
  
  Compiling 
/usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/imaxima.el...
  While compiling toplevel forms in file 
/usr/share/xemacs21/site-lisp/maxima/imaxima.el:
** misplaced interactive spec: (interactive)
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
  Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/maxima.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/maxima.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/smart-complete.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/smart-complete.elc
  Compiling /usr/share/xemacs21/site-lisp/maxima/sshell.el...
  Wrote /usr/share/xemacs21/site-lisp/maxima/sshell.elc
  Done
  ERROR: install script from maxima-emacs package failed
  dpkg: error processing package maxima-emacs (--configure):
   installed maxima-emacs package post-installation script subprocess returned 
error exit status 1


Andreas

Bug#984261: marked as done (ocaml-mccs: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 16:48:57 +
with message-id 
and subject line Bug#984261: fixed in ocaml-mccs 1.1+13-1
has caused the Debian Bug report #984261,
regarding ocaml-mccs: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-mccs
Version: 1.1+11-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/ocaml-mccs_1.1+11-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
dpkg-source: info: unpacking ocaml-mccs_1.1+11.orig.tar.xz
dpkg-source: info: unpacking ocaml-mccs_1.1+11-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-lp_solver.cpp-Fix-typos.patch

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-cfdb0ec1-7d7b-40f0-9974-60d078ad5bdf
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package ocaml-mccs
dpkg-buildpackage: info: source version 1.1+11-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Nicolas Braud-Santoni 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
dh clean --with ocaml
   dh_ocamlclean
   dh_clean
 debian/rules binary
dh binary --with ocaml
   dh_update_autotools_config
   dh_autoreconf
   dh_ocamlinit
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mv src/glpk/dune-shared src/glpk/dune
dune build -p mccs
x86_64-linux-gnu-gcc src/mccs_stubs.o (exit 1)
(cd _build/default/src && /usr/bin/x86_64-linux-gnu-gcc -O2 
-fno-strict-aliasing -fwrapv -fPIC -I . -DUSEGLPK -g -I /usr/lib/ocaml -I 
/usr/lib/ocaml/bytes -I /usr/lib/ocaml/cudf -I /usr/lib/ocaml/extlib -I glpk -o 
mccs_stubs.o -c mccs_stubs.cpp)
In file included from /usr/include/c++/11/map:60,
 from mccs_stubs.cpp:14:
/usr/include/c++/11/bits/stl_tree.h: In instantiation of ‘static const _Key& 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Const_Link_type) [with _Key = CUDFVersionedPackage*; _Val = 
CUDFVersionedPackage*; _KeyOfValue = std::_Identity; 
_Compare = CUDFPackage_comparator; _Alloc = 
std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, 
_Compare, _Alloc>::_Const_Link_type = const 
std::_Rb_tree_node*]’:
/usr/include/c++/11/bits/stl_tree.h:2069:47:   required from 
‘std::pair 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_M_get_insert_unique_pos(const key_type&) [with _Key = 
CUDFVersionedPackage*; _Val = 

Bug#1000370: marked as done (FTBFS (static assertion failed))

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 16:48:57 +
with message-id 
and subject line Bug#984261: fixed in ocaml-mccs 1.1+13-1
has caused the Debian Bug report #984261,
regarding FTBFS (static assertion 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.)


-- 
984261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-mccs
Version: 1.1+11-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

ocaml-mccs FTBFS on all architectures:
> [...]
> (cd _build/default/src && /usr/bin/x86_64-linux-gnu-gcc -O2 
> -fno-strict-aliasing -fwrapv -fPIC -I . -DUSEGLPK -g -I /usr/lib/ocaml -I 
> /usr/lib/ocaml/bytes -I /usr/lib/ocaml/cudf -I /usr/lib/ocaml/extlib -I glpk 
> -o mccs_stubs.o -c mccs_stubs.cpp)
> In file included from /usr/include/c++/11/map:60,
>  from mccs_stubs.cpp:14:
> /usr/include/c++/11/bits/stl_tree.h: In instantiation of ‘static const _Key& 
> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
> _Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
> _Alloc>::_Const_Link_type) [with _Key = CUDFVersionedPackage*; _Val = 
> CUDFVersionedPackage*; _KeyOfValue = std::_Identity; 
> _Compare = CUDFPackage_comparator; _Alloc = 
> std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, 
> _Compare, _Alloc>::_Const_Link_type = const 
> std::_Rb_tree_node*]’:
> /usr/include/c++/11/bits/stl_tree.h:2069:47:   required from 
> ‘std::pair 
> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
> _Alloc>::_M_get_insert_unique_pos(const key_type&) [with _Key = 
> CUDFVersionedPackage*; _Val = CUDFVersionedPackage*; _KeyOfValue = 
> std::_Identity; _Compare = CUDFPackage_comparator; 
> _Alloc = std::allocator; std::_Rb_tree<_Key, _Val, 
> _KeyOfValue, _Compare, _Alloc>::key_type = CUDFVersionedPackage*]’
> /usr/include/c++/11/bits/stl_tree.h:2122:4:   required from 
> ‘std::pair, bool> std::_Rb_tree<_Key, _Val, 
> _KeyOfValue, _Compare, _Alloc>::_M_insert_unique(_Arg&&) [with _Arg = 
> CUDFVersionedPackage* const&; _Key = CUDFVersionedPackage*; _Val = 
> CUDFVersionedPackage*; _KeyOfValue = std::_Identity; 
> _Compare = CUDFPackage_comparator; _Alloc = 
> std::allocator]’
> /usr/include/c++/11/bits/stl_set.h:512:25:   required from 
> ‘std::pair, _Compare, 
> typename 
> __gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key>::other>::const_iterator, 
> bool> std::set<_Key, _Compare, _Alloc>::insert(const value_type&) [with _Key 
> = CUDFVersionedPackage*; _Compare = CUDFPackage_comparator; _Alloc = 
> std::allocator; typename std::_Rb_tree<_Key, _Key, 
> std::_Identity<_Tp>, _Compare, typename 
> __gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key>::other>::const_iterator = 
> std::_Rb_tree std::_Identity, CUDFPackage_comparator, 
> std::allocator >::const_iterator; typename 
> __gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key>::other = 
> std::allocator; typename 
> __gnu_cxx::__alloc_traits<_Allocator>::rebind<_Key> = 
> __gnu_cxx::__alloc_traits, 
> CUDFVersionedPackage*>::rebind; typename 
> _Allocator::value_type = CUDFVersionedPackage*; std::set<_Key, _Compare, 
> _Alloc>::value_type = CUDFVersionedPackage*]’
> mccs_stubs.cpp:316:39:   required from here
> /usr/include/c++/11/bits/stl_tree.h:770:15: error: static assertion failed: 
> comparison object must be invocable as const
>   770 |   is_invocable_v _Key&>,
>   |   
> ^
> /usr/include/c++/11/bits/stl_tree.h:770:15: note: ‘std::is_invocable_v CUDFPackage_comparator&, CUDFVersionedPackage* const&, CUDFVersionedPackage* 
> const&>’ evaluates to false
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:9: binary-arch] Error 2


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
--- End Message ---
--- Begin Message ---
Source: ocaml-mccs
Source-Version: 1.1+13-1
Done: Stéphane Glondu 

We believe that the bug you reported is fixed in the latest version of
ocaml-mccs, 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.

Bug#998679: firefox-esr freezes shortly after start

[Daniel Blaschke]

Package: firefox-esr
Followup-For: Bug #998679
X-Debbugs-Cc: blasc...@hep.itp.tuwien.ac.at

Dear Maintainer,

for the past two days I've been testing firefox-esr 91.3.0 downloaded directly
from mozilla.org on debian 11 (bullseye) without any problems: no crashes
whatsoever.
gfx.x11-egl.force-disabled is set to its default "false" and mesa version on my
system is 20.3.5.

I'm running on an intel broadwell gpu (HD Graphics 5500) using the older
xserver-xorg-video-intel driver and gnome-shell on xorg (not wayland).
In fact, wayland crashes randomly after standby on my system (unrelated to
firefox).

Perhaps, the firefox crashes experienced by others is a bug in either newer
mesa 21.2 or the wayland display server of debian testing and firefox is merely
triggering that bug?
Do people affected by this bug experience it on both xorg and wayland or just
wayland?

On Debian stable we're now 3 weeks overdue for a security update of firefox,
which too me seems rather important to address; I cannot reproduce the bug
reported here on bullseye.

Cheers,
Daniel


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
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 firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u2
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.61-1
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.9.0-1
ii  libx11-6 2:1.7.2-1
ii  libx11-xcb1  2:1.7.2-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxrender1  1:0.9.10-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.3.3-0+deb11u1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-6.1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.18.3-6+deb11u1
ii  libgtk2.0-02.24.33-2
ii  pulseaudio 14.2-2

-- no debconf information

Bug#998913: [biod/BioD] Fails to build with ldc 1.28.0 (Issue #55)

[Andreas Tille]

Hi Pjotr,

Am Mon, Nov 22, 2021 at 08:17:26AM -0800 schrieb Pjotr Prins:
> Thanks @tillea. I wonder if anyone is using BioD. Sambamba imported a subset 
> of BioD, but no longer does that. 

The motivation to package BioD was only to get Sambamba packaged.  I have no 
idea whether there is any user of plain BioD (we simply can not know).  If you 
want to tell me that there is no sense to keep BioD in Debian I wonder whether 
it might be the best idea to simply orphan the project upstream.
Kind regards, Andreas.

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

[Sascha Steinbiss]

Hi Roberto,

thanks for the quick response!

> I cannot attend to this at the moment, so I give you my blessing to
> proceed with the NMU.

Thanks, will do that and upload soon.

Cheers
Sascha

Bug#993196: Germany Business List

[Elena Williams]

Hi,

Interested in Industry contacts professional list..

Please let me know which target criteria you would like to 
acquire!..

Target Industry: -__? (Any Industry)
Target Country: - _? (Denmark , USA , UK, Germany and many more..)
Target Job Title: - _? (CEO, President, VP's, Managing Director, 
Director, Manager and many more..)

With complete contact information for pre-show marketing campaign, appointment 
sitting, networking and various other post-show Marketing initiatives.

Data fields: Company names, Contact name, email address, phone number and etc.

If interested let me know so that we can send you count, cost and more info of 
deliver of data GD-PR etc...

Hope we get a positive reply

Have a Great Day!

Best Regards,
Elena Williams

Bug#1000182: marked as done (python-jira: network access during the build)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 16:04:27 +
with message-id 
and subject line Bug#1000182: fixed in python-jira 3.1.1-1
has caused the Debian Bug report #1000182,
regarding python-jira: network access during the 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.)


-- 
1000182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jira
Version: 3.0-1
Severity: serious

Dear maintainer,

It has been brought to our attention[1] that python-jira is doing
network access during its build.

On a build with network enabled:

|PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs/ 
build/html # HTML generator
|Running Sphinx v4.2.0
|making output directory... done
|loading intersphinx inventory from https://docs.python.org/3.7/objects.inv...
|loading intersphinx inventory from 
https://requests.kennethreitz.org/en/master/objects.inv...
|loading intersphinx inventory from 
https://requests-oauthlib.readthedocs.io/en/latest/objects.inv...
|loading intersphinx inventory from 
https://ipython.readthedocs.io/en/stable/objects.inv...
|loading intersphinx inventory from 
https://pip.readthedocs.io/en/stable/objects.inv...
|intersphinx inventory has moved: 
https://pip.readthedocs.io/en/stable/objects.inv -> 
https://pip.pypa.io/en/stable/objects.inv

On a build with a skewed clock:

|PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs/ 
build/html # HTML generator
|Running Sphinx v4.2.0
|making output directory... done
|loading intersphinx inventory from https://docs.python.org/3.7/objects.inv...
|loading intersphinx inventory from 
https://requests.kennethreitz.org/en/master/objects.inv...
|loading intersphinx inventory from 
https://requests-oauthlib.readthedocs.io/en/latest/objects.inv...
|loading intersphinx inventory from 
https://ipython.readthedocs.io/en/stable/objects.inv...
|loading intersphinx inventory from 
https://pip.readthedocs.io/en/stable/objects.inv...
|WARNING: failed to reach any of the inventories with the following issues:
|intersphinx inventory 
'https://requests.kennethreitz.org/en/master/objects.inv' not fetchable due to 
: 
HTTPSConnectionPool(host='requests.kennethreitz.org', port=443): Max retries 
exceeded with url: /en/master/objects.inv (Caused by 
SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed: certificate has expired (_ssl.c:1129)')))
|WARNING: failed to reach any of the inventories with the following issues:
|intersphinx inventory 'https://ipython.readthedocs.io/en/stable/objects.inv' 
not fetchable due to : 
HTTPSConnectionPool(host='ipython.readthedocs.io', port=443): Max retries 
exceeded with url: /en/stable/objects.inv (Caused by 
SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed: certificate has expired (_ssl.c:1129)')))
|WARNING: failed to reach any of the inventories with the following issues:
|intersphinx inventory 
'https://requests-oauthlib.readthedocs.io/en/latest/objects.inv' not fetchable 
due to : 
HTTPSConnectionPool(host='requests-oauthlib.readthedocs.io', port=443): Max 
retries exceeded with url: /en/latest/objects.inv (Caused by 
SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed: certificate has expired (_ssl.c:1129)')))
|WARNING: failed to reach any of the inventories with the following issues:
|intersphinx inventory 'https://pip.readthedocs.io/en/stable/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='pip.readthedocs.io', port=443): Max retries exceeded 
with url: /en/stable/objects.inv (Caused by 
SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed: certificate has expired (_ssl.c:1129)')))
|WARNING: failed to reach any of the inventories with the following issues:
|intersphinx inventory 'https://docs.python.org/3.7/objects.inv' not fetchable 
due to : 
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
with url: /3.7/objects.inv (Caused by SSLError(SSLCertVerificationError(1, 
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has 
expired (_ssl.c:1129)')))

On a build with network blocked:

|PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs/ 
build/html # HTML generator
|Running Sphinx v4.2.0
|making output directory... done
|loading intersphinx inventory from https://docs.python.org/3.7/objects.inv...
|loading intersphinx inventory from 

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

[Roberto C . Sánchez]

On Mon, Nov 22, 2021 at 01:16:06PM +0100, Sascha Steinbiss wrote:
> Hi everyone,
> 
> looks like upstream fixed this already [0]. The fix is easily imported
> into packaging, see attached debdiff.
> 
> I would be happy to NMU this within a week or so if there is no action
> by the maintainer to avoid mysql++ to be removed from testing. Please
> let me know if this is not wanted. Also addressing this mail to the
> previous uploader of the package.
> 
> mysql++ is a dependency of my augustus package, which I would prefer not
> to be removed from testing.
> 
Hi Sascha,

I cannot attend to this at the moment, so I give you my blessing to
proceed with the NMU.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 1000222
Bug #1000222 {Done: Mathieu Malaterre } [src:orthanc] 
orthanc: DCMTK was configured to use C++14 features, but your compiler does not 
or was not configured to provide them.
'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 orthanc/1.9.7+dfsg-2.
>
End of message, stopping processing here.

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

Bug#1000222: marked as done (orthanc: DCMTK was configured to use C++14 features, but your compiler does not or was not configured to provide them.)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 14:39:08 +
with message-id 
and subject line Bug#1000222: fixed in orthanc 1.9.7+dfsg-2
has caused the Debian Bug report #1000222,
regarding orthanc: DCMTK was configured to use C++14 features, but your 
compiler does not or was not configured to provide them.
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.)


-- 
1000222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc
Version: 1.9.7+dfsg-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_FILESYSTEM_VERSION=3 -DBOOST_HAS_FILESYSTEM_V3=1 
-DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOCALE_DYN_LINK -DBOOST_REGEX_DYN_LINK 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DCIVETWEB_API="" 
-DCIVETWEB_HAS_DISABLE_KEEP_ALIVE=1 -DCIVETWEB_HAS_WEBDAV_WRITING=1 
-DCIVETWEB_KEEP_ALIVE_TIMEOUT_SECONDS=1 
-DDCMTK_DICTIONARY_DIR=\"/usr/share/libdcmtk16\" 
-DDCMTK_USE_EMBEDDED_DICTIONARIES=0 -DDCMTK_VERSION_NUMBER=366 
-DHAVE_CONFIG_H=1 -DJSONCPP_DEPRECATED_STACK_LIMIT=5000 
-DORTHANC_API_VERSION=15 -DORTHANC_BUILDING_FRAMEWORK_LIBRARY=1 
-DORTHANC_DATABASE_VERSION=6 -DORTHANC_DEFAULT_DICOM_ENCODING=Encoding_Latin1 
-DORTHANC_ENABLE_BASE64=1 -DORTHANC_ENABLE_CIVETWEB=1 -DORTHANC_ENABLE_CURL=1 
-DORTHANC_ENABLE_DCMTK=1 -DORTHANC_ENABLE_DCMTK_JPEG=1 
-DORTHANC_ENABLE_DCMTK_JPEG_LOSSLESS=1 -DORTHANC_ENABLE_DCMTK_NETWORKING=1 
-DORTHANC_ENABLE_DCMTK_TRANSCODING=1 -DORTHANC_ENABLE_JPEG=1 
-DORTHANC_ENABLE_LOCALE=1 -DORTHANC_ENABLE_LOGGING=1 
-DORTHANC_ENABLE_LOGGING_STDIO=0 -DORTHANC_ENABLE_LUA=1 -DORTHANC_ENABLE_MD5=1 
-DORTHANC_ENABLE_MONGOOSE=0 -DORTHANC_ENABLE_PKCS11=0 -DORTHANC_ENABLE_PNG=1 
-DORTHANC_ENABLE_PUGIXML=1 -DORTHANC_ENABLE_SQLITE=1 -DORTHANC_ENABLE_SSL=1 
-DORTHANC_ENABLE_ZLIB=1 -DORTHANC_MAXIMUM_TAG_LENGTH=256 -DORTHANC_SANDBOXED=0 
-DORTHANC_SQLITE_VERSION=3036000 -DORTHANC_STATIC_ICU=0 
-DORTHANC_VERSION=\"1.9.7\" -DORTHANC_VERSION_MAJOR=1 -DORTHANC_VERSION_MINOR=9 
-DORTHANC_VERSION_REVISION=7 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 
-I/<>/BuildStaticFramework/AUTOGENERATED -I/usr/include/lua5.3 
-I/usr/src/gtest -I/usr/include/jsoncpp -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wno-long-long -Wno-variadic-macros -std=gnu++11 -fPIC -MD -MT 
CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o
 -MF 
CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o.d
 -o 
CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp.o
 -c /<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp
| In file included from /usr/include/dcmtk/dcmdata/dcdatset.h:26,
|  from 
/<>/OrthancFramework/Sources/DicomFormat/../DicomParsing/FromDcmtkBridge.h:30,
|  from 
/<>/OrthancFramework/Sources/DicomFormat/DicomPath.cpp:32:
| /usr/include/dcmtk/config/osconfig.h:1136:2: error: invalid preprocessing 
directive #errorDCMTK
|  1136 | #error\
|   |  ^~
|  1137 | DCMTK was configured to use C++14 features, but your compiler does 
not or was not configured to provide them.
|   | ~

See 
https://buildd.debian.org/status/fetch.php?pkg=orthanc=amd64=1.9.7%2Bdfsg-1%2Bb1=1637357465=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: orthanc
Source-Version: 1.9.7+dfsg-2
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated orthanc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 15:26:02 +0100
Source: orthanc

Bug#980016: marked as done (argus FTBFS due to missing link and includes for tirpc library)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 14:36:44 +
with message-id 
and subject line Bug#980016: fixed in argus 2:3.0.8.2-2.1
has caused the Debian Bug report #980016,
regarding argus FTBFS due to missing link and includes for tirpc library
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.)


-- 
980016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: argus
Version: 2:3.0.8.2-2
Severity: important

Dear Maintainer,

This package failed to rebuild in Ubuntu with "fatal error: rpc/type.h".
Sun RPC used to be included in glibc and now it must be added from
TI-RPC library (libtirpc-dev).

To fix it 3 changes were required:

configure.ac:
+AC_CHECK_LIB([tirpc],[rpc_call],,
+ [AC_MSG_ERROR([no tirpc library, exiting...!])])
 AC_CHECK_FUNCS(xdrmem_create)

reordering library inclusion in argus/Makefile.in:
-LIB = @LIBS@ @V_THREADS@ $(WRAPLIBS) $(SASLLIBS) $(COMPATLIB) 
../lib/argus_common.a -lm
+LIB = ../lib/argus_common.a -lm @LIBS@ @V_THREADS@ $(WRAPLIBS) $(SASLLIBS) 
$(COMPATLIB)

and finally the header include in debian/rules
+export DEB_CFLAGS_MAINT_APPEND  = -I/usr/include/tirpc

I tried the header inclusion through V_INCLS but it was being overriden
by the wrap macro, and this quick workaround was fine.

The full debdiff is available at:
https://launchpad.net/ubuntu/+archive/primary/+files/argus_2%3A3.0.8.2-2_2%3A3.0.8.2-2ubuntu1.diff.gz

Best regards,
Tiago

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-36-generic (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: argus
Source-Version: 2:3.0.8.2-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated argus 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: Sun, 07 Nov 2021 18:45:39 +0200
Source: argus
Architecture: source
Version: 2:3.0.8.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Stone 
Changed-By: Adrian Bunk 
Closes: 974760 980016
Changes:
 argus (2:3.0.8.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Tiago Stürmer Daitx to use libtirpc.
 (Closes: #980016)
   * Homepage: https://openargus.org (Closes: #974760)
Checksums-Sha1:
 7409c39fe3cde25680502f2b0a76bb433317c22f 1770 argus_3.0.8.2-2.1.dsc
 ad1c1ae4df748e2d6c550b2ac127caa514f497e1 9172 argus_3.0.8.2-2.1.debian.tar.xz
Checksums-Sha256:
 c0deb115a72741e58246433b2ab96abdbeafa8ccbdff7e7a7c2acee9b75cddf6 1770 
argus_3.0.8.2-2.1.dsc
 4f0e130b07cc7289a4cd792b93cc01d49807bf783c00a99a10e4a682ce3d4fff 9172 
argus_3.0.8.2-2.1.debian.tar.xz
Files:
 1f1af6814acea167bd397c772ee398ca 1770 net optional argus_3.0.8.2-2.1.dsc
 b97632a34f53e65325f45098ece40aeb 9172 net optional 
argus_3.0.8.2-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmGIBzoACgkQiNJCh6LY
mLGA2A/8DXkUV34FgStImVKLLp0WHveUfa78CN2y58JSYYMxU+QRDOpJqVMJmZEN
cALxVTQDX1uKDK2ZH1g19TerYsRvdeKEXI/bXJyZEfjbw8pHCOmiYfeqkeh+dt3V
SbU5hWGXEpraJkmWVBOA/WL4xvconn4dHd8wX164ZI/8d8vnzSRenzC6KGmog3VH
q/yLox+qw3yRsJmG1GLDALNhk9GDzV05EMvHankVvJolpm/7m/nvtGQaA5L2Wcx9
X0V89KQUDsDwu/XgrH2NIpsYvhRGXJysg05kSsGBozJgfGhcgZ1UPFxgfQ/j6VV/
e3Of1u+4SEYZWve9rlJw8ODX7m8ASwVChofl2vyhjD1WhKVi1WtQWNbUD1cV606C
m5gBJmS2hs54+mu6IQqnq5jIA6UHL5+eTaCLRv8SmdOSnlNbIO6c4KVSU2NTEwkK
ucRUHsUEgrBk4CA+6SiMdxcuMBWqa+IurPJQPe9ZW768aO0n/0R8EXu1r66GEmCD
kmPMsery0WIcEyJ7C2y8gxEO/uabqF4/L5/iO1DSel3AfbZBbmlljmrWUtjdNo0C

Bug#1000222: marked as pending in orthanc

[Mathieu Malaterre]

Control: tag -1 pending

Hello,

Bug #1000222 in orthanc 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/med-team/orthanc/-/commit/fa9b65bf0c3cc68105d115483d904034933ac3cc


d/patches: Remove c++11 hardcoded value. Closes: #1000222


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000222

Processed: Bug#1000222 marked as pending in orthanc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, 
but your compiler does not or was not configured to provide them.
Added tag(s) pending.

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

Bug#997137: marked as done (ukui-control-center: FTBFS: type_traits:44:3: error: template with C linkage)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 13:34:53 +
with message-id 
and subject line Bug#997137: fixed in ukui-control-center 3.0.4-1
has caused the Debian Bug report #997137,
regarding ukui-control-center: FTBFS: type_traits:44:3: error: template with C 
linkage
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.)


-- 
997137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-control-center
Version: 3.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -pthread -pthread -Wall -Wextra -D_REENTRANT -fPIC 
> -DQT_NO_DEBUG -DQT_PLUGIN -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I../../../commonComponent 
> -I../../../../ukui-control-center-3.0.2 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
> -I/usr/include/x86_64-linux-gnu/qt5/QGSettings 
> -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o run-passwd.o 
> run-passwd.cpp
> In file included from /usr/include/glib-2.0/glib/glib-typeof.h:39,
>  from /usr/include/glib-2.0/glib/gatomic.h:28,
>  from /usr/include/glib-2.0/glib/gthread.h:32,
>  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
>  from /usr/include/glib-2.0/glib.h:32,
>  from run-passwd.cpp:11:
> /usr/include/c++/11/type_traits:44:3: error: template with C linkage
>44 |   template
>   |   ^~~~
> run-passwd.cpp:10:1: note: ‘extern "C"’ linkage started here
>10 | extern "C" {
>   | ^~
> make[3]: *** [Makefile:839: run-passwd.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ukui-control-center_3.0.2-2_unstable.log

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

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

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

We believe that the bug you reported is fixed in the latest version of
ukui-control-center, 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.
handsome_feng  (supplier of updated 
ukui-control-center 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, 18 Nov 2021 11:42:34 +0800
Source: ukui-control-center
Architecture: source
Version: 3.0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 997137
Changes:
 ukui-control-center (3.0.4-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #997137)
Checksums-Sha1:
 d506d47deacc21cb575d65a9b1bb65938255311f 2689 ukui-control-center_3.0.4-1.dsc
 41f3b038a00534aab37406ce42ee763d1244ed8d 17602147 
ukui-control-center_3.0.4.orig.tar.gz
 4e3a47befe6bce19a6f515de8b16819363ec5088 5288 
ukui-control-center_3.0.4-1.debian.tar.xz
 d397a9435ba61ffa1b520407bf06821bace9062f 27439 
ukui-control-center_3.0.4-1_source.buildinfo
Checksums-Sha256:
 50b78d4c6346dff824150847e7a9e1469e2c4229e0565c6c3342ec5c6cffabe1 2689 
ukui-control-center_3.0.4-1.dsc
 

Bug#1000380: marked as done (node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 13:34:11 +
with message-id 
and subject line Bug#1000380: fixed in node-superagent 6.1.0+repack-1
has caused the Debian Bug report #1000380,
regarding node-superagent,node-fast-safe-stringify: both ship 
/usr/share/nodejs/fast-safe-stringify/*
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.)


-- 
1000380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-superagent,node-fast-safe-stringify
Severity: serious
Tags: sid bookworm .
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.1.0+~2.1.1-1
Control: found -1 2.0.7-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../node-fast-safe-stringify_2.0.7-2_all.deb ...
  Unpacking node-fast-safe-stringify (2.0.7-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/fast-safe-stringify/index.d.ts', 
which is also in package node-superagent 6.1.0+~2.1.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/share/nodejs/fast-safe-stringify/index.d.ts
  usr/share/nodejs/fast-safe-stringify/index.js
  usr/share/nodejs/fast-safe-stringify/package.json
  usr/share/nodejs/fast-safe-stringify/test-stable.js

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


node-superagent=6.1.0+~2.1.1-1_node-fast-safe-stringify=2.0.7-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-superagent
Source-Version: 6.1.0+repack-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-superagent package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 14:14:08 +0100
Source: node-superagent
Architecture: source
Version: 6.1.0+repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1000380
Changes:
 node-superagent (6.1.0+repack-1) unstable; urgency=medium
 .
   * Replace component by dependency to node-fast-safe-stringify and repack
 (Closes: #1000380)
Checksums-Sha1: 
 767af0633d23542deee4b628a962e1ada54e0581 2446 
node-superagent_6.1.0+repack-1.dsc
 ca9def3227f7e76afd397436507b6388a4fbc008 330014 
node-superagent_6.1.0+repack.orig.tar.gz
 f173a40b6a0c311a7103bac2eb1ec86147d65a05 137756 
node-superagent_6.1.0+repack-1.debian.tar.xz
Checksums-Sha256: 
 682c1fe8d250fce3fdd23679e217f389df3b123be56abff14c7fc659e80cc4c3 2446 
node-superagent_6.1.0+repack-1.dsc
 

Bug#1000380: marked as done (node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 13:34:05 +
with message-id 
and subject line Bug#1000380: fixed in node-fast-safe-stringify 2.1.1-1
has caused the Debian Bug report #1000380,
regarding node-superagent,node-fast-safe-stringify: both ship 
/usr/share/nodejs/fast-safe-stringify/*
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.)


-- 
1000380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-superagent,node-fast-safe-stringify
Severity: serious
Tags: sid bookworm .
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.1.0+~2.1.1-1
Control: found -1 2.0.7-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../node-fast-safe-stringify_2.0.7-2_all.deb ...
  Unpacking node-fast-safe-stringify (2.0.7-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/fast-safe-stringify/index.d.ts', 
which is also in package node-superagent 6.1.0+~2.1.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/share/nodejs/fast-safe-stringify/index.d.ts
  usr/share/nodejs/fast-safe-stringify/index.js
  usr/share/nodejs/fast-safe-stringify/package.json
  usr/share/nodejs/fast-safe-stringify/test-stable.js

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


node-superagent=6.1.0+~2.1.1-1_node-fast-safe-stringify=2.0.7-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-fast-safe-stringify
Source-Version: 2.1.1-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-fast-safe-stringify package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 14:19:33 +0100
Source: node-fast-safe-stringify
Architecture: source
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1000380
Changes:
 node-fast-safe-stringify (2.1.1-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ lintian-brush ]
   * Trim trailing whitespace.
   * Bump debhelper from old 11 to 13
   * Set upstream metadata fields: Bug-Submit
   * Remove obsolete fields Contact, Name from debian/upstream/metadata
 (already present in machine-readable debian/copyright)
   * Update standards version to 4.6.0, no changes needed
 .
   [ Yadd ]
   * Add "Rules-Requires-Root: no"
   * Use dh-sequence-nodejs instead of pkg-js-tools
   * Drop dependency to nodejs
   * Mark test dependencies with 
   * 

Bug#1000380: marked as pending in node-superagent

[Yadd]

Control: tag -1 pending

Hello,

Bug #1000380 in node-superagent reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-superagent/-/commit/74c4fda7230a22dc31f9a73fd398560fa4bf22e2


Replace component by dependency to node-fast-safe-stringify and repack

Closes: #1000380


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000380

Processed: Bug#1000380 marked as pending in node-superagent

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1000380 [node-superagent,node-fast-safe-stringify] 
node-superagent,node-fast-safe-stringify: both ship 
/usr/share/nodejs/fast-safe-stringify/*
Added tag(s) pending.

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

Bug#998867: bumping severity

[Adam Borowski]

Control: severity -1 critical

The current severity, "grave", is a serious understatement.

As all buildd chroots that are created with buggy debootstrap are tainted,
any packages built recently may assume merged usr, and thus needs to be
rebuilt.

Do we have a patch?  If not, let's revert, today or tomorrow at the latest.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A white dwarf seeks a red giant for a binary relationship.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Processed: bumping severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op
Severity set to 'critical' from 'grave'

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

Bug#999525: [help] New error in test cases of bmtk

[Andreas Tille]

Hi,

I think I've found a patch[1] to solve the original issue which just
seems to be a floating point precision issue.  However, meanwhile there
is another less simple issue:

 ERRORS 
_ ERROR collecting 
.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py _
ImportError while importing test module 
'/build/bmtk-0.0.9+ds/.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connection_map.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/pandas/__init__.py:30: in 
from pandas._libs import hashtable as _hashtable, lib as _lib, tslib as 
_tslib
/usr/lib/python3/dist-packages/pandas/_libs/__init__.py:13: in 
from pandas._libs.interval import Interval
E   ModuleNotFoundError: No module named 'pandas._libs.interval'

The above exception was the direct cause of the following exception:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
bmtk/tests/builder/test_connection_map.py:4: in 
from bmtk.builder.connection_map import ConnectionMap
bmtk/builder/__init__.py:23: in 
from .networks import DenseNetwork, NetworkBuilder
bmtk/builder/networks/__init__.py:23: in 
from .dm_network import DenseNetwork
bmtk/builder/networks/dm_network.py:32: in 
from bmtk.utils import sonata
bmtk/utils/sonata/__init__.py:24: in 
from .file import File
bmtk/utils/sonata/file.py:23: in 
from . import utils
bmtk/utils/sonata/utils.py:27: in 
import pandas as pd
/usr/lib/python3/dist-packages/pandas/__init__.py:34: in 
raise ImportError(
E   ImportError: C extension: No module named 'pandas._libs.interval' not 
built. If you want to import pandas from the source directory, you may need to 
run 'python setup.py build_ext --
_ ERROR collecting 
.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connector.py _
ImportError while importing test module 
'/build/bmtk-0.0.9+ds/.pybuild/cpython3_3.10/build/bmtk/tests/builder/test_connector.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/pandas/__init__.py:30: in 
from pandas._libs import hashtable as _hashtable, lib as _lib, tslib as 
_tslib
/usr/lib/python3/dist-packages/pandas/_libs/__init__.py:13: in 
from pandas._libs.interval import Interval
E   ModuleNotFoundError: No module named 'pandas._libs.interval'

The above exception was the direct cause of the following exception:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
bmtk/tests/builder/test_connector.py:1: in 
from bmtk.builder import connector
bmtk/builder/__init__.py:23: in 
from .networks import DenseNetwork, NetworkBuilder
bmtk/builder/networks/__init__.py:23: in 
from .dm_network import DenseNetwork
bmtk/builder/networks/dm_network.py:32: in 
from bmtk.utils import sonata
bmtk/utils/sonata/__init__.py:2= test session 
starts ==


I updated the upstream version in Git (but the issue is the same for the version
in unstable) and you can see a full build log in Salsa CI[2].

Any idea how to fix this?

Kind regards

  Andreas.


[1] 
https://salsa.debian.org/med-team/bmtk/-/blob/master/debian/patches/precision_in_test.patch
[2] https://salsa.debian.org/med-team/bmtk/-/jobs/2206233#L2178

-- 
http://fam-tille.de

Bug#997248: mysql++: FTBFS: ./examples/load_jpeg.cpp:90:50: error: taking address of rvalue [-fpermissive]

[Sascha Steinbiss]

Hi everyone,

looks like upstream fixed this already [0]. The fix is easily imported
into packaging, see attached debdiff.

I would be happy to NMU this within a week or so if there is no action
by the maintainer to avoid mysql++ to be removed from testing. Please
let me know if this is not wanted. Also addressing this mail to the
previous uploader of the package.

mysql++ is a dependency of my augustus package, which I would prefer not
to be removed from testing.


Thanks
Sascha

[0]
https://github.com/tangentsoft/mysqlpp/commit/df890798c8017dee79d5e4ee0867e2dae44ca5b5
diff -Nru mysql++-3.2.5/debian/changelog mysql++-3.2.5/debian/changelog
--- mysql++-3.2.5/debian/changelog	2020-04-23 03:37:47.0 +0200
+++ mysql++-3.2.5/debian/changelog	2021-11-22 13:01:43.0 +0100
@@ -1,3 +1,11 @@
+mysql++ (3.2.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Incorporate patch from upstream to fix build on newer GCC versions.
+(Closes: #997248)
+
+ -- Sascha Steinbiss   Mon, 22 Nov 2021 13:01:43 +0100
+
 mysql++ (3.2.5-2) unstable; urgency=medium
 
   * Update to Standards-Version 4.5.0 (no changes)
diff -Nru mysql++-3.2.5/debian/patches/rvalue_fix_example.patch mysql++-3.2.5/debian/patches/rvalue_fix_example.patch
--- mysql++-3.2.5/debian/patches/rvalue_fix_example.patch	1970-01-01 01:00:00.0 +0100
+++ mysql++-3.2.5/debian/patches/rvalue_fix_example.patch	2021-11-22 12:55:30.0 +0100
@@ -0,0 +1,57 @@
+From df890798c8017dee79d5e4ee0867e2dae44ca5b5 Mon Sep 17 00:00:00 2001
+From: tangent 
+Date: Sat, 19 Sep 2020 17:24:45 +
+Subject: [PATCH] Exchanged the "file slurp" idiom used in
+ examples/load_jpeg.cpp for one that also works in C++11, which complains of
+ "address to rvalue" with the original formulation.
+
+FossilOrigin-Name: b062e656cc2ed9356c6f757837580a2145251c5294e382f8e2c1ad3e74a91cdd
+---
+ examples/load_jpeg.cpp | 18 ++
+ 1 file changed, 10 insertions(+), 8 deletions(-)
+
+--- a/examples/load_jpeg.cpp
 b/examples/load_jpeg.cpp
+@@ -2,9 +2,9 @@
+  load_jpeg.cpp - Example showing how to insert BLOB data into the
+ 	database from a file.
+ 
+- Copyright (c) 1998 by Kevin Atkinson, (c) 1999-2001 by MySQL AB, and
+- (c) 2004-2009 by Educational Technology Resources, Inc.  Others may
+- also hold copyrights on code in this file.  See the CREDITS.txt file
++ Copyright © 1998 by Kevin Atkinson, © 1999-2001 by MySQL AB, and
++ © 2004-2009 by Educational Technology Resources, Inc.  Others may
++ also hold copyrights on code in this file.  See the CREDITS.md file
+  in the top directory of the distribution for details.
+ 
+  This file is part of MySQL++.
+@@ -80,14 +80,16 @@
+ 	img_name = cmdline.extra_args()[0];
+ 	ifstream img_file(img_name.c_str(), ios::binary);
+ 	if (img_file) {
+-		// Slurp file contents into RAM with minimum copying.  (Idiom
+-		// explained here: http://stackoverflow.com/questions/116038/)
++		// Slurp file contents into RAM with only a single copy, per
++		// https://stackoverflow.com/a/116220  It also explains why
++// there is no concise zero-copy option here.
+ 		//
+ 		// By loading the file into a C++ string (stringstream::str())
+ 		// and assigning that directly to a mysqlpp::sql_blob, we avoid
+ 		// truncating the binary data at the first null character.
+-		img.data.data = static_cast(
+-&(stringstream() << img_file.rdbuf()))->str();
++stringstream ss;
++ss << img_file.rdbuf();
++		img.data.data = ss.str();
+ 
+ 		// Check JPEG data for sanity.
+ 		const char* error;
+@@ -130,7 +132,7 @@
+ 			// as C strings, thus causing null-truncation.  The fact
+ 			// that we're using SSQLS here is a side issue, simply
+ 			// demonstrating that mysqlpp::Null is
+-			// now legal in SSQLS, as of MySQL++ 3.0.7.
++// now legal in SSQLS, as of MySQL++ 3.0.7.
+ 			Query query = con.query();
+ 			query.insert(img);
+ 			SimpleResult res = query.execute();
diff -Nru mysql++-3.2.5/debian/patches/series mysql++-3.2.5/debian/patches/series
--- mysql++-3.2.5/debian/patches/series	2020-04-23 03:37:47.0 +0200
+++ mysql++-3.2.5/debian/patches/series	2021-11-22 12:54:57.0 +0100
@@ -1,2 +1,3 @@
 do_not_link_against_libmysqlclient_r.patch
 discover_localtime_r_with_AC_TRY_COMPILE.patch
+rvalue_fix_example.patch

Bug#1000308: marked as done (pycuda: FTBFS with Python 3.10)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 11:04:03 +
with message-id 
and subject line Bug#1000308: fixed in pycuda 2021.1~dfsg-2
has caused the Debian Bug report #1000308,
regarding pycuda: FTBFS with Python 3.10
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.)


-- 
1000308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycuda
Version: 2021.1~dfsg-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

I tried to do a manual binNMU of pycuda to add Python 3.10 as a
supported version (#996584), but it failed.  I've copied what I hope
is the relevant part of the log below.

I believe that should be '-lboost_python310'.

Regards
Graham


x86_64-linux-gnu-g++ -pthread -shared -Wl,-Bsymbolic-functions -g
-fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2
-ffile-prefix-map=/<>=. -fstack-p
rotector-strong -Wformat -Werror=format-security -Wall -pedantic
-Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-x86_64-3.10/src/cpp/bitlog.o build/temp.l
inux-x86_64-3.10/src/cpp/cuda.o
build/temp.linux-x86_64-3.10/src/wrapper/mempool.o
build/temp.linux-x86_64-3.10/src/wrapper/wrap_cudadrv.o
build/temp.linux
-x86_64-3.10/src/wrapper/wrap_cudagl.o
build/temp.linux-x86_64-3.10/src/wrapper/wrap_curand.o
-L/usr/lib/stubs -L/usr/lib64/stubs -L/usr/lib/stubs -L/usr/l
ib64/stubs -lboost_python31 -lboost_thread -lcuda -lcurand -o
/<>/.pybuild/cpython3_3.10/build/pycuda/_driver.cpython-310-x86_64-linux-gnu.so
/usr/bin/ld: cannot find -lboost_python31
collect2: error: ld returned 1 exit status
error: command '/usr/bin/x86_64-linux-gnu-g++' failed with exit code 1
--- End Message ---
--- Begin Message ---
Source: pycuda
Source-Version: 2021.1~dfsg-2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pycuda 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: Mon, 22 Nov 2021 11:37:39 +0100
Source: pycuda
Binary: python-pycuda-doc python3-pycuda python3-pycuda-dbgsym
Architecture: source all amd64
Version: 2021.1~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 python-pycuda-doc - module to access Nvidia‘s CUDA computation API 
(documentation)
 python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation 
API
Closes: 1000308
Changes:
 pycuda (2021.1~dfsg-2) unstable; urgency=medium
 .
   * Fix boost python library name generation.  (Closes: #1000308)
Checksums-Sha1:
 d3b2535cfd298de71cf0cd4a43731d443f30f144 2560 pycuda_2021.1~dfsg-2.dsc
 9455f3d2aca29acb23758df1b02e4dca5d23ddd5 31860 
pycuda_2021.1~dfsg-2.debian.tar.xz
 8072f5e49610167ca0c30c67eaf33bdc85e22d35 12942 
pycuda_2021.1~dfsg-2_amd64.buildinfo
 dee81aaa5f3a2bd8525c8abc017cf1969bfbfdbd 173892 
python-pycuda-doc_2021.1~dfsg-2_all.deb
 8cdb5662cf6f5a59da3792617510036dd151f1d4 6193476 
python3-pycuda-dbgsym_2021.1~dfsg-2_amd64.deb
 8938fda922799f7ba27d764e23da9996492e9024 357428 
python3-pycuda_2021.1~dfsg-2_amd64.deb
Checksums-Sha256:
 305e1a12e6be420d167f594511e969a01ca4fdde40249be96ee254dd7413d446 2560 
pycuda_2021.1~dfsg-2.dsc
 2b6bb586e2f0b67f18d6c6eae1b3297f2eef4bd57a4fbac250955a981bff5185 31860 
pycuda_2021.1~dfsg-2.debian.tar.xz
 cc138803e12c8dd47075b91495912b79f259e23f8f2e67aa6f765c24b82f665b 12942 
pycuda_2021.1~dfsg-2_amd64.buildinfo
 df9f9bf0cc18e396ccab8c89e35c348468d098957f25f4587e9ccdf70a2efa0a 173892 
python-pycuda-doc_2021.1~dfsg-2_all.deb
 22b740896a0980c75af20e2d1e48d0da8cfd5c209e84dee0e44b7d5a61195fcb 6193476 
python3-pycuda-dbgsym_2021.1~dfsg-2_amd64.deb
 6d4be14434a9a8caf577d0687714d73f62ab0815fe90f2708e8b9f92da2196e2 357428 
python3-pycuda_2021.1~dfsg-2_amd64.deb
Files:
 a088f6e7e361d17df64c368790467a8c 2560 contrib/python optional 
pycuda_2021.1~dfsg-2.dsc
 8b175c95c6faed31eefc4a01fe4dbe96 31860 contrib/python optional 
pycuda_2021.1~dfsg-2.debian.tar.xz
 

Bug#1000380: node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*

[Andreas Beckmann]

Package: node-superagent,node-fast-safe-stringify
Severity: serious
Tags: sid bookworm .
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.1.0+~2.1.1-1
Control: found -1 2.0.7-2

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../node-fast-safe-stringify_2.0.7-2_all.deb ...
  Unpacking node-fast-safe-stringify (2.0.7-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/fast-safe-stringify/index.d.ts', 
which is also in package node-superagent 6.1.0+~2.1.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/node-fast-safe-stringify_2.0.7-2_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/share/nodejs/fast-safe-stringify/index.d.ts
  usr/share/nodejs/fast-safe-stringify/index.js
  usr/share/nodejs/fast-safe-stringify/package.json
  usr/share/nodejs/fast-safe-stringify/test-stable.js

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


node-superagent=6.1.0+~2.1.1-1_node-fast-safe-stringify=2.0.7-2.log.gz
Description: application/gzip

Processed: node-superagent,node-fast-safe-stringify: both ship /usr/share/nodejs/fast-safe-stringify/*

[Debian Bug Tracking System]

Processing control commands:

> found -1 6.1.0+~2.1.1-1
Bug #1000380 [node-superagent,node-fast-safe-stringify] 
node-superagent,node-fast-safe-stringify: both ship 
/usr/share/nodejs/fast-safe-stringify/*
There is no source info for the package 'node-fast-safe-stringify' at version 
'6.1.0+~2.1.1-1' with architecture ''
Marked as found in versions node-superagent/6.1.0+~2.1.1-1.
> found -1 2.0.7-2
Bug #1000380 [node-superagent,node-fast-safe-stringify] 
node-superagent,node-fast-safe-stringify: both ship 
/usr/share/nodejs/fast-safe-stringify/*
There is no source info for the package 'node-superagent' at version '2.0.7-2' 
with architecture ''
Marked as found in versions node-fast-safe-stringify/2.0.7-2.

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

Processed: Re: Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1000293 [jackd2] Problems starting jackd: Method RequestRelease is not 
implemented on interface org.freedesktop.ReserveDevice1
Added tag(s) moreinfo.

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

Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1

[Sebastian Ramacher]

Control: tags -1 moreinfo

On 2021-11-21 00:55:50, Arnaldo Pirrone wrote:
> Package: jackd2
> Version: 1.9.19~dfsg-2
> Severity: grave
> X-Debbugs-Cc: it9...@gmail.com
> 
> Apparently there is something wrong with Jack and dbus.
> Also reported here:
> https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/
> Find below the jack server logs.
> 
> 00:41:32.228 Resetta le statistiche.
> 00:41:32.269 Connessioni di ALSA cambiate.
> 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka jackdbus).
> Cannot connect to server socket err = File o directory non esistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA.
> 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace
> Sun Nov 21 00:41:47 2021: Starting jack server...
> Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with priority
> 10
> Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self connect
> requests"
> Cannot connect to server socket err = File o directory non esistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> Sun Nov 21 00:41:47 2021: Device reservation request with priority 2147483647
> denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method
> RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1)
> Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 error 
> :
> Method RequestRelease is not implemented on interface
> org.freedesktop.ReserveDevice1
> Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be acquired...
> Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver
> Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1
> Sun Nov 21 00:41:47 2021: ERROR: Failed to open server
> Sun Nov 21 00:41:48 2021: Saving settings to
> "/home/it9exm/.config/jack/conf.xml" ...
> 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione
> fallita. - Impossibile connettersi al server JACK. Controlla la finestra dei
> messaggi per maggiori informazioni.
> Cannot connect to server socket err = File o directory non esistente
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
> unlock

Unfortunately I'm not able to reprodue this issue. Are you running
pipewire by any chance?

Best
Sebastian

> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 jackd2 depends on:
> ii  debconf [debconf-2.0]  1.5.79
> ii  libasound2 1.2.5.1-1
> ii  libc6  2.32-4
> ii  libdbus-1-31.12.20-3
> ii  libexpat1  2.4.1-3
> ii  libgcc-s1  11.2.0-10
> ii  libjack-jackd2-0   1.9.19~dfsg-2
> ii  libreadline8   8.1-2
> ii  libsamplerate0 0.2.2-1
> ii  libsndfile11.0.31-2
> ii  libstdc++6 11.2.0-10
> ii  libsystemd0249.6-2
> ii  libzita-alsa-pcmi0 0.3.2-2
> ii  libzita-resampler1 1.8.0-2
> ii  python33.9.8-1
> ii  python3-dbus   1.2.18-3
> 
> Versions of packages jackd2 recommends:
> ii  jackd2-firewire  1.9.19~dfsg-2
> ii  libpam-modules   1.4.0-10
> ii  qjackctl 0.9.5-1
> 
> Versions of packages jackd2 suggests:
> pn  jack-tools   
> pn  meterbridge  
> 
> -- debconf information:
> * jackd/tweak_rt_limits: true

-- 
Sebastian Ramacher

Bug#996320: marked as done (ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 22 Nov 2021 10:49:58 +
with message-id 
and subject line Bug#996320: fixed in ruby-minitest-excludes 2.0.1-2
has caused the Debian Bug report #996320,
regarding ruby-minitest-excludes: FTBFS with ruby3.0: ERROR: Test "ruby3.0" 
failed.
to be marked as done.

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

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


-- 
996320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-minitest-excludes
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-minitest-excludes was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-minitest-excludes/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"minitest-excludes\"
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-minitest-excludes/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> Run options: --seed 1794
> 
> # Running:
> 
> F
> 
> Finished in 0.001705s, 586.6517 runs/s, 586.6517 assertions/s.
> 
>   1) Failure:
> TestMinitestExcludes#test_cls_excludes 
> [/<>/test/test_minitest_excludes.rb:44]:
> Expected: ["test_test3", "test_test1"]
>   Actual: ["test_test1", "test_test3"]
> 
> 1 runs, 1 assertions, 1 failures, 0 errors, 0 skips
> ERROR: Test "ruby3.0" failed.


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-minitest-excludes/ruby-minitest-excludes_2.0.1-1+rebuild1633386834_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-minitest-excludes
Source-Version: 2.0.1-2
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-minitest-excludes, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated 
ruby-minitest-excludes package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Nov 2021 11:25:12 +0100
Source: ruby-minitest-excludes
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 996320
Changes:
 ruby-minitest-excludes (2.0.1-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Cédric Boutillier ]
   * Update team name
   * Add upstream patch to sort runnable_methods in tests to account for FS
 glob order differences (Closes: #996320)
   * Bump Standards-Version to 4.6.0 (no changes needed)
Checksums-Sha1:
 

Bug#1000222: [Debian-med-packaging] Bug#1000222: orthanc force gnuc++11 reason

[Sébastien Jodogne]

Dear Mathieu,

I confirm that this is an acceptable patch, except that it could be 
applied only to "JsonCppConfiguration.cmake" (the 
"DownloadOrthancFramework.cmake" is part of the skeleton that is copied 
in each Orthanc official plugin).


It was on my plan to do this patch by myself, once I had time in my 
academic schedule.


The reason for forcing "--std=gnu++11" upstream is to support older 
versions of gcc, especially the one shipped with Linux Standard Base SDK 
(if I remember correctly) that is used to build the cross-distro 
binaries of Orthanc.


I guess that the same patch will need to be applied to the other Orthanc 
plugin that links against DCMTK, i.e. "orthanc-wsi".


Thanks for your contribution,
Sébastien-


On 22/11/21 11:14, Mathieu Malaterre wrote:

Control: tags -1 patch

Could someone confirm; this is an acceptable patch ?

thanks

Bug#1000378: telnetd: post-installation error

[Elmar Haneke]

Package: telnetd
Version: 0.17-43
Severity: grave
Justification: renders package unusable

Dear Maintainer,

package does report error on install:


aptitude install telnetd
Die folgenden NEUEN Pakete werden zusätzlich installiert:
  telnetd
0 Pakete aktualisiert, 1 zusätzlich installiert, 0 werden entfernt und 0 nicht
aktualisiert.
0 B/46,0 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 116 kB zusätzlich belegt sein.
Vormals nicht ausgewähltes Paket telnetd wird gewählt.
(Lese Datenbank ... 743851 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../telnetd_0.17-43_amd64.deb ...
Entpacken von telnetd (0.17-43) ...
telnetd (0.17-43) wird eingerichtet ...
Benutzer telnetd wird zur Gruppe utmp hinzugefügt.
chown: Zugriff auf '/usr/lib/telnetlogin' nicht möglich: Datei oder Verzeichnis
nicht gefunden
dpkg: Fehler beim Bearbeiten des Paketes telnetd (--configure):
 »installiertes telnetd-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 1 zurück
Trigger für man-db (2.9.4-2) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 telnetd
E: Sub-process /usr/bin/dpkg returned an error code (1)
telnetd (0.17-43) wird eingerichtet ...
chown: Zugriff auf '/usr/lib/telnetlogin' nicht möglich: Datei oder Verzeichnis
nicht gefunden
dpkg: Fehler beim Bearbeiten des Paketes telnetd (--configure):
 »installiertes telnetd-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 telnetd



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

Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telnetd depends on:
ii  adduser   3.118
ii  libc6 2.32-4
ii  openbsd-inetd [inet-superserver]  0.20160825-5
ii  passwd1:4.8.1-2

telnetd recommends no packages.

telnetd suggests no packages.

-- no debconf information

Processed: Re: orthanc force gnuc++11 reason

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, 
but your compiler does not or was not configured to provide them.
Added tag(s) patch.

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

Bug#1000222: orthanc force gnuc++11 reason

[Mathieu Malaterre]

Control: tags -1 patch

Could someone confirm; this is an acceptable patch ?

thanks


donotforcec++11.patch
Description: Binary data

Processed: orthanc force gnuc++11 reason

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream confirmed
Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, 
but your compiler does not or was not configured to provide them.
Added tag(s) upstream and confirmed.
> affects -1 dcmtk/3.6.6-2
Bug #1000222 [src:orthanc] orthanc: DCMTK was configured to use C++14 features, 
but your compiler does not or was not configured to provide them.
Added indication that 1000222 affects dcmtk/3.6.6-2

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