Bug#1002316: python-schedule should be probably moved to Debian Python Team

[Andreas Tille]

Hi,

I've just fixed #1002316 by upgrading to latest upstream version.  When
looking at the package it might make sense to move it to Debian Python
team instead of private maintainership.  I'd volunteer to move the package
over if all involved people agree.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#1002316: marked as done (schedule: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jan 2022 07:03:45 +
with message-id 
and subject line Bug#1002316: fixed in schedule 1.1.0-0.1
has caused the Debian Bug report #1002316,
regarding schedule: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --configure -i python{version} -p "3.10 3.9"
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.10 3.9"
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_schedule/build/schedule
> copying schedule/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_schedule/build/schedule
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_schedule/build/schedule
> copying schedule/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_schedule/build/schedule
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test -i python{version} -p "3.10 3.9"
> I: pybuild pybuild:286: cp -r /<>/test_* 
> /<>/.pybuild/cpython3_3.10_schedule/build
> I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_schedule/build; python3.10 -m 
> unittest discover -v 
> test_at_time (test_schedule.SchedulerTests) ... ok
> test_at_time_hour (test_schedule.SchedulerTests) ... ok
> test_at_time_minute (test_schedule.SchedulerTests) ... ok
> test_cancel_job (test_schedule.SchedulerTests) ... ok
> test_cancel_jobs (test_schedule.SchedulerTests) ... ok
> test_clear_by_tag (test_schedule.SchedulerTests) ... ERROR
> test_job_func_args_are_passed_on (test_schedule.SchedulerTests) ... ok
> test_misconfigured_job_wont_break_scheduler (test_schedule.SchedulerTests)
> Ensure an interrupted job definition chain won't break ... ok
> test_next_run_property (test_schedule.SchedulerTests) ... ok
> test_next_run_time (test_schedule.SchedulerTests) ... ok
> test_run_all (test_schedule.SchedulerTests) ... ok
> test_run_every_n_days_at_specific_time (test_schedule.SchedulerTests) ... ok
> test_run_every_weekday_at_specific_time_past_today 
> (test_schedule.SchedulerTests) ... ok
> test_run_every_weekday_at_specific_time_today (test_schedule.SchedulerTests) 
> ... ok
> test_run_pending (test_schedule.SchedulerTests)
> Check that run_pending() runs pending jobs. ... ok
> test_singular_time_units_match_plural_units (test_schedule.SchedulerTests) 
> ... ok
> test_tag_type_enforcement (test_schedule.SchedulerTests) ... ERROR
> test_time_range (test_schedule.SchedulerTests) ... ok
> test_time_range_repr (test_schedule.SchedulerTests) ... ok
> test_time_units (test_schedule.SchedulerTests) ... ok
> test_to_string (test_schedule.SchedulerTests) ... ok
> test_to_string_functools_partial_job_func (test_schedule.SchedulerTests) ... 
> ok
> test_to_string_lambda_job_func (test_schedule.SchedulerTests) ... ok
> 
> ==
> ERROR: test_clear_by_tag (test_schedule.SchedulerTests)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.10_schedule/build/test_schedule.py", 
> line 438, in test_clear_by_tag
> every().second.do(make_mock_job(name='job1')).tag('tag1')
>   File 
> "/<>/.pybuild/cpython3_3.10_schedule/build/schedule/__init__.py",
>  line 357, in tag
> if not all(isinstance(tag, collections.Hashable) for tag in tags):
>   File 
> "/<>/.pybuild/cpython3_3.10_schedule/build/schedule/__init__.py",
>  line 357, in 
> if not all(isinstance(tag, collections.Hashable) for tag in tags):
> AttributeError: module 'collections' has no attribute 'Hashable'
> 
> ===

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Sebastian Rasmussen]

> I'm slightly worried by this comment though:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77

I have now tried to temporarily upgrade to the wicd-curses,
wicd-cli, wicd-daemon and python3-wicd versions present in
Debian/experimental. Unfortunately I can only see a fraction
of the Wi-Fi SSIDs compared to the version that used to be
in Debian/testing. I'm happy to do more testing for that issue
(help me find the bug, I can't find it), since that appears to
block the resolution of this bug #885140.

 / Sebastian

Processed: your mail

[Debian Bug Tracking System]

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

> reopen 1003003
Bug #1003003 {Done: James Lu } [src:libqalculate] 
libqalculate FTBFS on architectures where char is unsigned
'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 libqalculate/3.22.0-2.
> thanks
Stopping processing here.

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

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Sebastian Rasmussen]

> If nobody steps up to finish the porting, there is (not so nice) plan B: 
> disable
> wicd-gtk and leave wicd-curses (more buggy than it should be, but
> usable) and wicd-cli.

Sadly it appears no one has stepped up to do the porting in the four years
since 2017. As a user of wicd-curses, can I humbly suggest that Debian
disables wicd-gtk for the time being so that Debian/testing mapped to
bookworm can continue using wicd?

I'm slightly worried by this comment though:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77

If wicd-curses is kicked out of Debian entirely, what is the suggested
alternative for scanning, connecting to and disconnecting from Wi-Fi
in a terminal?

 / Sebastian

Bug#1003628: marked as done (imdbpy: autopkgtest failure on arm64: AssertionError: assert '' == 'Mandariinid')

[Debian Bug Tracking System]

Your message dated Wed, 19 Jan 2022 04:18:44 +
with message-id 
and subject line Bug#1003628: fixed in imdbpy 2021.04.18-3
has caused the Debian Bug report #1003628,
regarding imdbpy: autopkgtest failure on arm64: AssertionError: assert '' == 
'Mandariinid'
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.)


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

Source: imdbpy
Version: 2021.04.18-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package imdbpy, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


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

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=imdbpy

https://ci.debian.net/data/autopkgtest/testing/arm64/i/imdbpy/18081764/log.gz

=== FAILURES 
===
___ test_movie_original_title[http] 



ia = 

def test_movie_original_title(ia):
movie = ia.get_movie('2991224', info=['main'])
title = movie.get('original title', '')

  assert title == 'Mandariinid'

E   AssertionError: assert '' == 'Mandariinid'
E - Mandariinid

tests/test_http_movie_titles.py:13: AssertionError
=== short test summary info 

FAILED tests/test_http_movie_titles.py::test_movie_original_title[http] 
- Ass...
 1 failed, 342 passed, 19 skipped in 308.55s (0:05:08) 
=

autopkgtest [11:35:41]: test unittests



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: imdbpy
Source-Version: 2021.04.18-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated imdbpy 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: Tue, 18 Jan 2022 22:51:33 -0500
Source: imdbpy
Architecture: source
Version: 2021.04.18-3
Distribution: unstable
Urgency: medium
Maintainer: Ana Beatriz Guerrero Lopez 
Changed-By: Sandro Tosi 
Closes: 1003628
Changes:
 imdbpy (2021.04.18-3) unstable; urgency=medium
 .
   * debian/tests/unittests
 - skip test_movie_original_title and
   test_selected_ended_tv_series_should_have_correct_series_years in
   autopkgtest; Closes: #1003628
Checksums-Sha1:
 d93ee7eeb682b7268c8704dc0f635f3e7be437cc 1990 imdbpy_2021.04.18-3.dsc
 48a6a819b8134337c4c2fbca038228ff9abe5b9d 8468 imdbpy_2021.04.18-3.debian.tar.xz
 6ac623f080e5b418805864a00f52a4632ef768c6 7441 
imdbpy_2021.04.18-3_source.buildinfo
Checksums-Sha256:
 6b0f72f21d5079115a4892d582cd722c850c43770335fef7316d671226d84eb6 1990 
imdbpy_2021.04.18-3.dsc
 77638fc4892b5c7b252e36f6ce2f7078624ec4931759c527809d43d7b656c929 8468 
imdbpy_2021.04.18-3.debian.tar.xz
 83b24621460e87b3e34487ec9893f3ec9c965c20d3c37a8af7b5b1ab0597f3c1 7441 
imdbpy_2021.04.18-3_source.buildinfo
Files:
 630c18f9659626a63eeece178409d157 1990 python optional imdbpy_2021.04.18-3.dsc
 e94d4ed6ba0ea8e73c56ef6c3a435ccb 8468 python optional 
imdbpy_2021.04.18-3.debian.tar.xz
 ea3ba5d542c10b297af3b1c81d2d574d 7441 python optional 
imdbpy_2021.04.18-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmHnitYACgkQh588mTgB
qU8ahRAAj9rzP7QYgbv+QI7EZbKcTAP3Rl7pFIdfx6ol+YCoTZmSXUx48gfcpV2b
9G77+6TtmtXfVvwcLO/6r625yJW03gHM80wQIBSrvfnMpDf9YamFvyet25jmR9YF
tgyXzJsAdcsdiYTUKB+nj3t4AtnSl8lX/RttMvuEeTxSzxq8jxlk2j3n1Fw19VRg
29d5YUEy7YQRPLn6e9BG5hYelCgWw+S0WLAMdmqqFy7GzmIBnVvHSNg1O3ZQcv7U
Ba8NWYiRfH8/85Wdnl3wGTF60XXUl0bRdCINq55Sp1UdYyePXC

Bug#1003003: marked as done (libqalculate FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jan 2022 04:18:51 +
with message-id 
and subject line Bug#1003003: fixed in libqalculate 3.22.0-2
has caused the Debian Bug report #1003003,
regarding libqalculate FTBFS on architectures where char is unsigned
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.)


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

https://buildd.debian.org/status/package.php?p=libqalculate

...
FAIL: unittest
==


./tests/variables.batch - 11 tests passed


./tests/units.batch - 13 tests passed


Mismatch detected at line 42
char(0xD8)
expected ''Ø''
received '"Ø"'

Running all unit tests

Running unit tests from 'variables.batch'
Running unit tests from 'units.batch'
Running unit tests from 'strings.batch'
FAIL unittest (exit status: 1)


Testsuite summary for libqalculate 3.22.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/test-suite.log

make[4]: *** [Makefile:835: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: libqalculate
Source-Version: 3.22.0-2
Done: James Lu 

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

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

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

Debian distribution maintenance software
pp.
James Lu  (supplier of updated libqalculate 
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: SHA384

Format: 1.8
Date: Fri, 14 Jan 2022 18:32:42 -0800
Source: libqalculate
Architecture: source
Version: 3.22.0-2
Distribution: unstable
Urgency: medium
Maintainer: Qalculate Team 
Changed-By: James Lu 
Closes: 1003003
Changes:
 libqalculate (3.22.0-2) unstable; urgency=medium
 .
   * Build with -fsigned-char to fix builds on architectures where char is
 unsigned (Closes: #1003003)
 .
   [ Norbert Preining ]
   * Drop myself from uploaders.
Checksums-Sha1:
 739f4330343c2e1a73205bd46ea76eab26b3ab5e 2498 libqalculate_3.22.0-2.dsc
 fb37e92eb82f4b99078f6589873506c74d4bb4ce 1661965 
libqalculate_3.22.0.orig.tar.gz
 ce34245b1ca1be01da4de79955a86eb6fe3c9122 8604 
libqalculate_3.22.0-2.debian.tar.xz
 1f46f59bad4d8742b1b51b4d16d7adbd2c5c2bd2 11757 
libqalculate_3.22.0-2_amd64.buildinfo
Checksums-Sha256:
 55f54c884b8efed067f5c0bc2182aa9b88cd8cfe91f30759a5ac690bd8ba6df9 2498 
libqalculate_3.22.0-2.dsc
 2128645c52a65bc77567669e0c01c0c409318bb2efc3a5e287450df5125aa263 1661965 
libqalculate_3.22.0.orig.tar.gz
 14de6bee5aac5142326cbc0a1d9d6f2849f2db9d5d7f4269be3b6bd14398153e 8604 
libqalculate_3.22.0-2.debian.tar.xz
 87257cf9151042bef07cf0246814d8f934b5e38e66f420dea3f26aadc251f420 11757 
libqalculate_3.22.0-2_amd64.buildinfo
Files:
 99d3b920765acf60a8743dda52ac70c6 2498 math optional libqalculate_3.22.0-2.dsc
 752c1c2db53c0e9c9fdda7b2108d00b3 1661965 math optional 
libqalculate_3.22.0.orig.tar.gz
 4b0b4dcc504dd857b9026f7e0ce75a5c 8604 math optional 
libqalculate_3.22.0-2.debian.tar.xz
 fac24cc621ecb338cea6ff99fbd6847b 11757 math optional 
libqalculate_3.22.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmHnizUACgkQUAHhsJqj
dEvquQ/+M8BesDYYLZ+93xIjQpgwD+jH9pI9UfYHYj841WGOjb9x/YbJGvgENsU/
/phTceYuXNcLZCoHC7oEQMQ1TTxPhpCxXv+nNZXXSvBUtGw/5sOg2bkDG5KfrgNm
XUZGCLBpYACuKKsNyoP462kSePUs9vj7LTUywRAvlN+OIOsTja8E5JO28W/FO68w
V5AoLKxr5wTIkkzqpWNTAzlDUpafnokB4PErbiYqoT9V0zI+DGDH89eQgGEcb2p4
Hx+1jVtaOZWrWQkc7ogIJri+E8gVGK7RK4XGr83Z/hbAeYxtTyBYs+0q5lCgU7I6
tLjsgZE/y60fxj7rMSwuu4iWTU7Tw+SSIPNkEzma1lQPtIM05hCmjSTa5nhfI27P
kXcwhqcjONhZcCsT1YfuAPsiHUu/ZBCLziJ8Vy750Ay0ZPoLjhIXtv+vBqVHHRld
iVlbAMQq8IimaaQ4QDC9hHAczicbgqwpwBylTXumi0eOgcHb2uhKUP6V78TFXdiL
uv+Ym17QxZtyZCJ3w47E8M+XnlxPm6wqdUjANtzkYF1xb0bmo9LnkgNC2GicGT

Bug#1003989: marked as done (gr-satellites FTBFS with gnuradio 3.10.0)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jan 2022 04:04:04 +
with message-id 
and subject line Bug#1003989: fixed in gr-satellites 4.4.0-2
has caused the Debian Bug report #1003989,
regarding gr-satellites FTBFS with gnuradio 3.10.0
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.)


-- 
1003989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-satellites
Version: 4.4.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=gr-satellites&suite=sid

...
   dh_auto_test -a
cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process --verbose -j4
UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
Test project /<>/obj-x86_64-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
  Start  1: qa_fixedlen_tagger

1: Test command: /bin/sh "qa_fixedlen_tagger_test.sh"
1: Test timeout computed to be: 1000
test 2
  Start  2: qa_hdlc

2: Test command: /bin/sh "qa_hdlc_test.sh"
2: Test timeout computed to be: 1000
test 3
  Start  3: qa_kiss

3: Test command: /bin/sh "qa_kiss_test.sh"
3: Test timeout computed to be: 1000
test 4
  Start  4: qa_nrzi

4: Test command: /bin/sh "qa_nrzi_test.sh"
4: Test timeout computed to be: 1000
4: vmcircbuf_prefs::get :error: 
/<>/debian/.debhelper/generated/_source/home/.gnuradio/prefs/vmcircbuf_default_factory:
 No such file or directory
4: gr::vmcircbuf :error: vmcircbuf_createfilemapping: createfilemapping is not 
available
4: ...
4: --
4: Ran 3 tests in 0.038s
4: 
4: OK
2: E
2: ==
2: ERROR: test_framer_deframer (__main__.qa_hdlc)
2: Connects an HDLC framer to a deframer and sends PDUs through
2: --
2: Traceback (most recent call last):
2:   File "/<>/python/qa_hdlc.py", line 38, in test_framer_deframer
2: pdu2tag = blocks.pdu_to_tagged_stream(blocks.byte_t)
2: AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'
2: 
2: --
2: Ran 1 test in 0.001s
2: 
2: FAILED (errors=1)
 1/14 Test  #4: qa_nrzi ..   Passed0.40 sec
test 5
  Start  5: qa_pdu_add_meta

5: Test command: /bin/sh "qa_pdu_add_meta_test.sh"
5: Test timeout computed to be: 1000
1: E
1: ==
1: ERROR: test_tagger (__main__.qa_fixedlen_tagger)
1: Runs some test data through the tagger and checks resulting PDUs
1: --
1: Traceback (most recent call last):
1:   File "/<>/python/qa_fixedlen_tagger.py", line 38, in setUp
1: self.tag2pdu = blocks.tagged_stream_to_pdu(blocks.byte_t,
1: AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'
1: 
1: --
1: Ran 1 test in 0.001s
1: 
1: FAILED (errors=1)
 2/14 Test  #2: qa_hdlc ..***Failed0.44 sec
E
==
ERROR: test_framer_deframer (__main__.qa_hdlc)
Connects an HDLC framer to a deframer and sends PDUs through
--
Traceback (most recent call last):
  File "/<>/python/qa_hdlc.py", line 38, in test_framer_deframer
pdu2tag = blocks.pdu_to_tagged_stream(blocks.byte_t)
AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'

--
Ran 1 test in 0.001s

FAILED (errors=1)

test 6
  Start  6: qa_pdu_head_tail

6: Test command: /bin/sh "qa_pdu_head_tail_test.sh"
6: Test timeout computed to be: 1000
 3/14 Test  #1: qa_fixedlen_tagger ...***Failed0.51 sec
E
==
ERROR: test_tagger (__main__.qa_fixedlen_tagger)
Runs some test data through the tagger and checks resulting PDUs
-

Bug#1003990: marked as done (gr-funcube FTBFS with gnuradio 3.10.0)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jan 2022 03:33:36 +
with message-id 
and subject line Bug#1003990: fixed in gr-funcube 1.0.0-3
has caused the Debian Bug report #1003990,
regarding gr-funcube FTBFS with gnuradio 3.10.0
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.)


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

https://buildd.debian.org/status/package.php?p=gr-funcube&suite=sid

...
[ 29%] Building CXX object 
lib/CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -DBOOST_ALL_NO_LIB 
-DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DFMT_LOCALE -DFMT_SHARED 
-DGR_CTRLPORT -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DSPDLOG_COMPILED_LIB 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -Dgnuradio_funcube_EXPORTS 
-I/usr/include/hidapi -I/<>/lib/../include -isystem 
/usr/include/python3.9 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC   -fvisibility=hidden -std=gnu++11 -MD 
-MT lib/CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o -MF 
CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o.d -o 
CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o -c 
/<>/lib/fcdpp_control_impl.cc
/<>/lib/fcd_impl.cc: In constructor 
‘gr::funcube::fcd_impl::fcd_impl(std::string)’:
/<>/lib/fcd_impl.cc:43:5: error: ‘GR_CONFIG_LOGGER’ was not 
declared in this scope
   43 | GR_CONFIG_LOGGER(config_file);
  | ^~~~
/<>/lib/fcd_impl.cc:45:22: error: ‘LOG’ was not declared in this 
scope
   45 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  |  ^~~
/<>/lib/fcd_impl.cc:45:5: error: ‘GR_LOG_GETLOGGER’ was not 
declared in this scope; did you mean ‘GR_LOG_ERROR’?
   45 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  | ^~~~
  | GR_LOG_ERROR
/<>/lib/fcd_impl.cc:46:5: error: ‘GR_LOG_SET_LEVEL’ was not 
declared in this scope
   46 | GR_LOG_SET_LEVEL(LOG, log_level);
  | ^~~~
/<>/lib/fcd_impl.cc:49:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   49 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cout", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcd_impl.cc:51:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   51 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cerr", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcd_impl.cc:53:13: error: ‘GR_LOG_SET_FILE_APPENDER’ was 
not declared in this scope
   53 | GR_LOG_SET_FILE_APPENDER(LOG, log_file, true, "%r :%p: 
%c{1} - %m%n");
  | ^~~~
make[3]: *** [lib/CMakeFiles/gnuradio-funcube.dir/build.make:79: 
lib/CMakeFiles/gnuradio-funcube.dir/fcd_impl.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/lib/fcdpp_impl.cc: In constructor 
‘gr::funcube::fcdpp_impl::fcdpp_impl(std::string, int)’:
/<>/lib/fcdpp_impl.cc:41:5: error: ‘GR_CONFIG_LOGGER’ was not 
declared in this scope
   41 | GR_CONFIG_LOGGER(config_file);
  | ^~~~
/<>/lib/fcdpp_impl.cc:43:22: error: ‘LOG’ was not declared in this 
scope
   43 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  |  ^~~
/<>/lib/fcdpp_impl.cc:43:5: error: ‘GR_LOG_GETLOGGER’ was not 
declared in this scope; did you mean ‘GR_LOG_ERROR’?
   43 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  | ^~~~
  | GR_LOG_ERROR
/<>/lib/fcdpp_impl.cc:44:5: error: ‘GR_LOG_SET_LEVEL’ was not 
declared in this scope
   44 | GR_LOG_SET_LEVEL(LOG, log_level);
  | ^~~~
/<>/lib/fcdpp_impl.cc:47:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   47 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cout", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcdpp_impl.cc:49:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   49 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cerr", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcdpp_impl.cc:51:13: error: ‘GR_LOG_SET_FILE_APPENDER’ was 
not declared in this scope
   51 | GR_LOG_SET_FILE_APPENDER(LOG, log_file, true, "%r :%p: 
%c{

Bug#1003990: gr-funcube FTBFS with gnuradio 3.10.0

[Adrian Bunk]

Source: gr-funcube
Version: 1.0.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=gr-funcube&suite=sid

...
[ 29%] Building CXX object 
lib/CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++ -DBOOST_ALL_NO_LIB 
-DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_REGEX_DYN_LINK 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DFMT_LOCALE -DFMT_SHARED 
-DGR_CTRLPORT -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DSPDLOG_COMPILED_LIB 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -Dgnuradio_funcube_EXPORTS 
-I/usr/include/hidapi -I/<>/lib/../include -isystem 
/usr/include/python3.9 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC   -fvisibility=hidden -std=gnu++11 -MD 
-MT lib/CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o -MF 
CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o.d -o 
CMakeFiles/gnuradio-funcube.dir/fcdpp_control_impl.cc.o -c 
/<>/lib/fcdpp_control_impl.cc
/<>/lib/fcd_impl.cc: In constructor 
‘gr::funcube::fcd_impl::fcd_impl(std::string)’:
/<>/lib/fcd_impl.cc:43:5: error: ‘GR_CONFIG_LOGGER’ was not 
declared in this scope
   43 | GR_CONFIG_LOGGER(config_file);
  | ^~~~
/<>/lib/fcd_impl.cc:45:22: error: ‘LOG’ was not declared in this 
scope
   45 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  |  ^~~
/<>/lib/fcd_impl.cc:45:5: error: ‘GR_LOG_GETLOGGER’ was not 
declared in this scope; did you mean ‘GR_LOG_ERROR’?
   45 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  | ^~~~
  | GR_LOG_ERROR
/<>/lib/fcd_impl.cc:46:5: error: ‘GR_LOG_SET_LEVEL’ was not 
declared in this scope
   46 | GR_LOG_SET_LEVEL(LOG, log_level);
  | ^~~~
/<>/lib/fcd_impl.cc:49:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   49 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cout", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcd_impl.cc:51:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   51 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cerr", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcd_impl.cc:53:13: error: ‘GR_LOG_SET_FILE_APPENDER’ was 
not declared in this scope
   53 | GR_LOG_SET_FILE_APPENDER(LOG, log_file, true, "%r :%p: 
%c{1} - %m%n");
  | ^~~~
make[3]: *** [lib/CMakeFiles/gnuradio-funcube.dir/build.make:79: 
lib/CMakeFiles/gnuradio-funcube.dir/fcd_impl.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/lib/fcdpp_impl.cc: In constructor 
‘gr::funcube::fcdpp_impl::fcdpp_impl(std::string, int)’:
/<>/lib/fcdpp_impl.cc:41:5: error: ‘GR_CONFIG_LOGGER’ was not 
declared in this scope
   41 | GR_CONFIG_LOGGER(config_file);
  | ^~~~
/<>/lib/fcdpp_impl.cc:43:22: error: ‘LOG’ was not declared in this 
scope
   43 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  |  ^~~
/<>/lib/fcdpp_impl.cc:43:5: error: ‘GR_LOG_GETLOGGER’ was not 
declared in this scope; did you mean ‘GR_LOG_ERROR’?
   43 | GR_LOG_GETLOGGER(LOG, "gr_log." + alias());
  | ^~~~
  | GR_LOG_ERROR
/<>/lib/fcdpp_impl.cc:44:5: error: ‘GR_LOG_SET_LEVEL’ was not 
declared in this scope
   44 | GR_LOG_SET_LEVEL(LOG, log_level);
  | ^~~~
/<>/lib/fcdpp_impl.cc:47:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   47 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cout", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcdpp_impl.cc:49:13: error: ‘GR_LOG_SET_CONSOLE_APPENDER’ 
was not declared in this scope
   49 | GR_LOG_SET_CONSOLE_APPENDER(LOG, "cerr", "gr::log :%p: 
%c{1} - %m%n");
  | ^~~
/<>/lib/fcdpp_impl.cc:51:13: error: ‘GR_LOG_SET_FILE_APPENDER’ was 
not declared in this scope
   51 | GR_LOG_SET_FILE_APPENDER(LOG, log_file, true, "%r :%p: 
%c{1} - %m%n");
  | ^~~~
make[3]: *** [lib/CMakeFiles/gnuradio-funcube.dir/build.make:107: 
lib/CMakeFiles/gnuradio-funcube.dir/fcdpp_impl.cc.o] Error 1

Bug#1003989: gr-satellites FTBFS with gnuradio 3.10.0

[Adrian Bunk]

Source: gr-satellites
Version: 4.4.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=gr-satellites&suite=sid

...
   dh_auto_test -a
cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process --verbose -j4
UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
Test project /<>/obj-x86_64-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
  Start  1: qa_fixedlen_tagger

1: Test command: /bin/sh "qa_fixedlen_tagger_test.sh"
1: Test timeout computed to be: 1000
test 2
  Start  2: qa_hdlc

2: Test command: /bin/sh "qa_hdlc_test.sh"
2: Test timeout computed to be: 1000
test 3
  Start  3: qa_kiss

3: Test command: /bin/sh "qa_kiss_test.sh"
3: Test timeout computed to be: 1000
test 4
  Start  4: qa_nrzi

4: Test command: /bin/sh "qa_nrzi_test.sh"
4: Test timeout computed to be: 1000
4: vmcircbuf_prefs::get :error: 
/<>/debian/.debhelper/generated/_source/home/.gnuradio/prefs/vmcircbuf_default_factory:
 No such file or directory
4: gr::vmcircbuf :error: vmcircbuf_createfilemapping: createfilemapping is not 
available
4: ...
4: --
4: Ran 3 tests in 0.038s
4: 
4: OK
2: E
2: ==
2: ERROR: test_framer_deframer (__main__.qa_hdlc)
2: Connects an HDLC framer to a deframer and sends PDUs through
2: --
2: Traceback (most recent call last):
2:   File "/<>/python/qa_hdlc.py", line 38, in test_framer_deframer
2: pdu2tag = blocks.pdu_to_tagged_stream(blocks.byte_t)
2: AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'
2: 
2: --
2: Ran 1 test in 0.001s
2: 
2: FAILED (errors=1)
 1/14 Test  #4: qa_nrzi ..   Passed0.40 sec
test 5
  Start  5: qa_pdu_add_meta

5: Test command: /bin/sh "qa_pdu_add_meta_test.sh"
5: Test timeout computed to be: 1000
1: E
1: ==
1: ERROR: test_tagger (__main__.qa_fixedlen_tagger)
1: Runs some test data through the tagger and checks resulting PDUs
1: --
1: Traceback (most recent call last):
1:   File "/<>/python/qa_fixedlen_tagger.py", line 38, in setUp
1: self.tag2pdu = blocks.tagged_stream_to_pdu(blocks.byte_t,
1: AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'
1: 
1: --
1: Ran 1 test in 0.001s
1: 
1: FAILED (errors=1)
 2/14 Test  #2: qa_hdlc ..***Failed0.44 sec
E
==
ERROR: test_framer_deframer (__main__.qa_hdlc)
Connects an HDLC framer to a deframer and sends PDUs through
--
Traceback (most recent call last):
  File "/<>/python/qa_hdlc.py", line 38, in test_framer_deframer
pdu2tag = blocks.pdu_to_tagged_stream(blocks.byte_t)
AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'

--
Ran 1 test in 0.001s

FAILED (errors=1)

test 6
  Start  6: qa_pdu_head_tail

6: Test command: /bin/sh "qa_pdu_head_tail_test.sh"
6: Test timeout computed to be: 1000
 3/14 Test  #1: qa_fixedlen_tagger ...***Failed0.51 sec
E
==
ERROR: test_tagger (__main__.qa_fixedlen_tagger)
Runs some test data through the tagger and checks resulting PDUs
--
Traceback (most recent call last):
  File "/<>/python/qa_fixedlen_tagger.py", line 38, in setUp
self.tag2pdu = blocks.tagged_stream_to_pdu(blocks.byte_t,
AttributeError: module 'gnuradio.blocks' has no attribute 'byte_t'

--
Ran 1 test in 0.001s

FAILED (errors=1)

test 7
  Start  7: qa_pdu_length_filter

7: Test command: /bin/sh "qa_pdu_length_filter_test.sh"
7: Test timeout computed to be: 1000
3: E
3: ==
3: ERROR: test_encoder_decoder (__main__.qa_kiss)
3: Connects a PDU to KISS and KISS to PDU and  sends PDUs through
3: --
3: Traceback (most recent call last):
3:

Bug#1003984: [Pkg-electronics-devel] Bug#1003984: fpga-icestorm: binary-all FTBFS

[Daniel Gröber]

Hi Adrian,

Thanks for the report.

On Wed, Jan 19, 2022 at 01:04:27AM +0200, Adrian Bunk wrote:
> https://buildd.debian.org/status/logs.php?pkg=fpga-icestorm&arch=all
> 
> ...
>debian/rules override_dh_install
> make[1]: Entering directory '/<>'
> dh_install
> cd debian/fpga-icestorm/usr/share/fpga-icestorm/python/ && \
>   find . -type f -print0 | xargs -0 -n1 -I{} rm ../../../bin/{}
> /bin/sh: 1: cd: can't cd to 
> debian/fpga-icestorm/usr/share/fpga-icestorm/python/
> make[1]: *** [debian/rules:25: override_dh_install] Error 2

Fixed on salsa in[1], I'm just waiting for a sponsored upload.

[1]: 
https://salsa.debian.org/electronics-team/fpga-icestorm/-/commit/bd60e6882085d2713e46c0d822ad974852a64266

--Daniel


signature.asc
Description: PGP signature

Bug#1003975: marked as done (gnuradio-dev: Missing dependency on libspdlog-dev)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 18:23:44 -0500
with message-id <20220118182344.597fe...@216-moncure.alexandria.va.us>
and subject line gnuradio-dev: Missing dependency on libspdlog-dev
has caused the Debian Bug report #1003975,
regarding gnuradio-dev: Missing dependency on libspdlog-dev
to be marked as done.

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

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


-- 
1003975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuradio-dev
Version: 3.10.0.0-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:gr-fosphor src:gr-funcube src:gr-hpsdr src:gr-iqbal 
src:gr-rds src:gr-satellites

https://buildd.debian.org/status/fetch.php?pkg=gr-fosphor&arch=amd64&ver=3.9%7E0.974ab2f-1%2Bb2&stamp=1642532351&raw=0

...
CMake Error at /usr/share/cmake-3.22/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
  By not providing "Findspdlog.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "spdlog", but
  CMake did not find one.

  Could not find a package configuration file provided by "spdlog" with any
  of the following names:

spdlogConfig.cmake
spdlog-config.cmake

  Add the installation prefix of "spdlog" to CMAKE_PREFIX_PATH or set
  "spdlog_DIR" to a directory containing one of the above files.  If "spdlog"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:13 
(find_dependency)
  CMakeLists.txt:34 (find_package)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Package: gnuradio
Version: 3.10.0.0-4

Use source package name to close.
-Maitland--- End Message ---

Bug#1003975: marked as done (gnuradio-dev: Missing dependency on libspdlog-dev)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 18:05:32 -0500
with message-id <20220118180532.08367...@216-moncure.alexandria.va.us>
and subject line gnuradio-dev: Missing dependency on libspdlog-dev
has caused the Debian Bug report #1003975,
regarding gnuradio-dev: Missing dependency on libspdlog-dev
to be marked as done.

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

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


-- 
1003975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuradio-dev
Version: 3.10.0.0-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:gr-fosphor src:gr-funcube src:gr-hpsdr src:gr-iqbal 
src:gr-rds src:gr-satellites

https://buildd.debian.org/status/fetch.php?pkg=gr-fosphor&arch=amd64&ver=3.9%7E0.974ab2f-1%2Bb2&stamp=1642532351&raw=0

...
CMake Error at /usr/share/cmake-3.22/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
  By not providing "Findspdlog.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "spdlog", but
  CMake did not find one.

  Could not find a package configuration file provided by "spdlog" with any
  of the following names:

spdlogConfig.cmake
spdlog-config.cmake

  Add the installation prefix of "spdlog" to CMAKE_PREFIX_PATH or set
  "spdlog_DIR" to a directory containing one of the above files.  If "spdlog"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:13 
(find_dependency)
  CMakeLists.txt:34 (find_package)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Package: gnuradio-dev
Version: 3.10.0.0-4

Forgot to close this via debian/changelog.
-Maitland--- End Message ---

Bug#1003984: fpga-icestorm: binary-all FTBFS

[Adrian Bunk]

Source: fpga-icestorm
Version: 0~20220102git3b7b199-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=fpga-icestorm&arch=all

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
cd debian/fpga-icestorm/usr/share/fpga-icestorm/python/ && \
find . -type f -print0 | xargs -0 -n1 -I{} rm ../../../bin/{}
/bin/sh: 1: cd: can't cd to debian/fpga-icestorm/usr/share/fpga-icestorm/python/
make[1]: *** [debian/rules:25: override_dh_install] Error 2

Bug#995830: marked as done (openlp: License incompatible with PyQt5)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 22:34:33 +
with message-id 
and subject line Bug#995830: fixed in openlp 2.9.4-0.1
has caused the Debian Bug report #995830,
regarding openlp: License incompatible with PyQt5
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.)


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

Package: openlp
Severity: serious
Version: 2.4.6-1

OpenLP v2.4.6 is licensed under GPL-2-only. This is incompatible with PyQt5's GPL-3+ 
license, which it depends on. Upstream has released OpenLP beta versions licensed under 
GPL-3+. A package for those versions is currently available at

https://gitlab.com/openlp/debian-package

Please upload a GPL-3+ version of OpenLP to the archive.
--- End Message ---
--- Begin Message ---
Source: openlp
Source-Version: 2.9.4-0.1
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated openlp 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, 18 Jan 2022 19:51:00 +0100
Source: openlp
Architecture: source
Version: 2.9.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Raoul Snyman 
Changed-By: Bastian Germann 
Closes: 995830
Changes:
 openlp (2.9.4-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * d/watch: Scan for case sensitive tarball
   * d/rules: Deselect display-dependent test
   * New upstream version 2.9.4. Closes: #995830
 .
   [ Jelmer Vernooij ]
   * Use secure URI in Vcs control header.
 .
   [ Debian Janitor ]
   * Remove unnecessary X-Python{,3}-Version field in debian/control.
   * Bump debhelper from old 9 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Re-export upstream signing key without extra signatures.
   * Fix day-of-week for changelog entry 2.2-1.
 .
   [ Raoul Snyman ]
   * Migrate from old patches format to patches unapplied format
Checksums-Sha1:
 86f887ad22f129111a9da67fee79da74813d8e95 2432 openlp_2.9.4-0.1.dsc
 150a7a3ec33dae02c2bd3e2a1e15d457273a0a62 24072809 openlp_2.9.4.orig.tar.gz
 511b457939600981f47ca8ed9f49e8f7db0bdffa 5292 openlp_2.9.4-0.1.debian.tar.xz
 909e955d9378fa262077f99f0520c7ef7d4736cd 7088 openlp_2.9.4-0.1_source.buildinfo
Checksums-Sha256:
 840197d6e18830ce53f2388150ffca38a34527fd9e26fe9a39083cda46e5c86f 2432 
openlp_2.9.4-0.1.dsc
 24dcd14841b5a6a03e0ac12202628429f467264ac8605268c63b6634121dd73a 24072809 
openlp_2.9.4.orig.tar.gz
 969a93a0286bd3646fdf97aa836e7548b1f5c656a2ed8a5f0d876e47864db7c8 5292 
openlp_2.9.4-0.1.debian.tar.xz
 10fadcb261b3ce5057c64527813f44f2c678ce4c8700aa3e43431282627ee3a9 7088 
openlp_2.9.4-0.1_source.buildinfo
Files:
 592937589cb0cd5fa6cdf9301548ccae 2432 x11 optional openlp_2.9.4-0.1.dsc
 cbee92a7de43610af651abd08cf0e7de 24072809 x11 optional openlp_2.9.4.orig.tar.gz
 4c45ad0e8d80c8b66484e8573216f2b9 5292 x11 optional 
openlp_2.9.4-0.1.debian.tar.xz
 2631af99d5442e1eff0c5b18155ce4e6 7088 x11 optional 
openlp_2.9.4-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmHnM5UQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFL7aDACDfZjJlrDQBof89RvuVSuksYN4cSvp8aic
eV5N2W9tml9yB+QxpPfLLrLi01dLEdMtBJNYRIFSlMvBqsP9yeBMzD0jv9NB2rLa
IWT7xoJowXDIiRDWEZdMbJgalA3OspcdulCuKJuCcjREGMtSM0krhPc2yCuNWE+B
flmDUHac1/m1Zcfu4sVTy6tLTDk8/bfNf2fbSW1HoPcE9dl0EOCvtuVLiey5aa+N
uQwvjnZyMl0LDXQGPwvRrNb5gFZDE7iUyKaNI/e9bqvQ7SFYCRwaJPgZqEzN8mgF
T4HHr3pF4rcdJw4n46JlQPRZYMIUnjGKZbbYDQtcgcuf5dYv/981StxY7S/j8uR3
lCBx93TBImY2od9fWrpjqOYkanfEHu9mzUuzqr15NaXKIbRp7YCg30gEle97hw2C
b280Nt2Sa9QO33oM/Gh+fpuFxtyQCJhu+Z2U4opfMcLV7PGaLaX5NuqnU0lBBi0M
IOT683DTToVVOUB6NCtUc7kgyV60xJc=
=82k0
-END PGP SIGNATURE End Message ---

Processed (with 4 errors): gnuradio-dev: Missing dependency on libspdlog-dev

[Debian Bug Tracking System]

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

> package gnuradio-dev
Limiting to bugs with field 'package' containing at least one of 'gnuradio-dev'
Limit currently set to 'package':'gnuradio-dev'

> tags 1003975 pending
Bug #1003975 [gnuradio-dev] gnuradio-dev: Missing dependency on libspdlog-dev
Added tag(s) pending.
> OK. Yes, everything building using gnuradio-dev needs to have
Unknown command or malformed arguments to command.
> libspdlog-dev available. Best to add this dependency. RSN.
Unknown command or malformed arguments to command.
> Thanks!
Unknown command or malformed arguments to command.
> -Maitland
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1003981: nextpnr build-depends on removed package

[peter green]

Package: nextpnr
Version: 0.0~git20210102.9b96280-1
Tags: bookworm, sid
Severity: serious

nextpnr build-depends on fpga-icestorm-chipdb which is no longer built by
the fpga-icestorm source package, it is still present in unstable as a cruft
package, but is completely gone from testing.

Bug#995830: openlp: License incompatible with PyQt5

[Bastian Germann]

On Wed, 6 Oct 2021 17:26:59 +0200 Bastian Germann  wrote:

Package: openlp
Severity: serious
Version: 2.4.6-1

OpenLP v2.4.6 is licensed under GPL-2-only. This is incompatible with PyQt5's GPL-3+ 
license, which it depends on. Upstream has released OpenLP beta versions licensed under 
GPL-3+. A package for those versions is currently available at

https://gitlab.com/openlp/debian-package

Please upload a GPL-3+ version of OpenLP to the archive.


As there was no reaction up to now and the first RC was released, I am going to 
NMU this with
https://gitlab.com/openlp/debian-package/-/merge_requests/3

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[Jonas Smedegaard]

Quoting John MacFarlane (2022-01-18 22:02:02)
> A note from upstream, in case it's helpful: we haven't depended on 
> cmark-gfm since pandoc 2.10.1 (released a year and a half ago).  If 
> you could move to a more recent version of pandoc, this would avoid 
> the problem entirely.  I'm aware that issues of policy and packaging 
> may make this difficult, though.

Thanks, always appreciate your remarks from upstream POV.

I recently had a look at your Haskell-based CommonMark library/tool and 
consider packaging it for Debian.  That alone (if even possible to do 
with current libraries in Debian) is however not enough to upgrade 
pandoc, as you know.  I am unable to do such general Haskell upgrade 
myself, and am looking forward to the Debian Haskell team hopefully 
gaining strength to do a round of library updates, so pandoc can be 
upgraded as well...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1003979: arachne-pnr build-depends on removed package

[peter green]

Package: arachne-pnr
Version: 0.1+20190728gitc40fb22-2
Tags: bookworm, sid
Severity: serious

arachne-pnr build-depends on fpga-icestorm-chipdb which is no longer built by
the fpga-icestorm source package, it is still present in unstable as a cruft
package, but is completely gone from testing.

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[John MacFarlane]

A note from upstream, in case it's helpful:  we haven't depended
on cmark-gfm since pandoc 2.10.1 (released a year and a half
ago).  If you could move to a more recent version of pandoc, this
would avoid the problem entirely.  I'm aware that issues of
policy and packaging may make this difficult, though.

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

[Diederik de Haas]

On Sunday, 19 September 2021 17:53:26 CET Diederik de Haas wrote:
> According to 'buildd' version 1.5.7-4+b1 has been built 28 days ago,
> but because this issue is still present, fwupd can't be updated.
> I'm fine with waiting a couple of days as that happens with other
> packages from time to time as well. When it last for more then a week,
> I tend to investigate why. It's now almost a month.
> And it's consistently recurring.

Thus bug is supposed to be fixed, but the above described problem still exists 
on my system, although it's not a month (yet?).

root@bagend:~# aptitude full-upgrade -s
The following NEW packages will be installed:
  fwupd-unsigned{a} libfwupdplugin5{a} 
The following packages will be REMOVED:
  libfwupdplugin1{u} 
The following packages will be upgraded:
  fwupd 
1 packages upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 2,769 kB of archives. After unpacking 1,660 kB will be used.
The following packages have unmet dependencies:
 fwupd-amd64-signed : Depends: fwupd (< 1.5.7-6) but 1.7.4-1 is to be 
installed
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) fwupd [1.5.7-5 (now, testing)] 
2) fwupd-unsigned [Not Installed] 
3) libfwupdplugin1 [1.5.7-5 (now, testing)]   



Accept this solution? [Y/n/q/?] q

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

Bug#1003907: fails to successfully associate

[Andrej Shadura]

Hi Michael,

On Tue, 18 Jan 2022, at 21:52, Michael Biebl wrote:
> Am 18.01.22 um 21:47 schrieb Masashi Honma:
>> The log indicates that the Wi-Fi access point rejected the association
>> request from the Wi-Fi station with status
>> code=WLAN_STATUS_INVALID_IE.
>> 
>> We can't read from this log why the Wi-Fi access point rejected the
>> assocication request.
>> If I have that Wi-Fi access point on hand, I can bisect this issue.
>> What is the Wi-Fi access point you are using?
>> 
>
> It's a FRITZ!Box 7490 (a very common Wi-Fi Router in Germany) running 
> Firmware version 07.39.
> WPA-Mode is set to WPA2+WPA3

Just a random thought: could you please try those two versions formerly from 
experimental:
 * 2:2.9.0+git20200517+dd2daf0-1
 * 2:2.9.0+git20210909+a75fdcd-1

I have re-enabled some options (WNM, MBO, FILS and mesh networking) in the 
latter, I wonder if that could have some effect.

-- 
Cheers,
  Andrej

Bug#1003907: fails to successfully associate

[Michael Biebl]

Am 18.01.22 um 21:47 schrieb Masashi Honma:

The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
code=WLAN_STATUS_INVALID_IE.

We can't read from this log why the Wi-Fi access point rejected the
assocication request.
If I have that Wi-Fi access point on hand, I can bisect this issue.
What is the Wi-Fi access point you are using?



It's a FRITZ!Box 7490 (a very common Wi-Fi Router in Germany) running 
Firmware version 07.39.

WPA-Mode is set to WPA2+WPA3


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003907: fails to successfully associate

[Masashi Honma]

The log indicates that the Wi-Fi access point rejected the association
request from the Wi-Fi station with status
code=WLAN_STATUS_INVALID_IE.

We can't read from this log why the Wi-Fi access point rejected the
assocication request.
If I have that Wi-Fi access point on hand, I can bisect this issue.
What is the Wi-Fi access point you are using?

2022年1月19日(水) 3:55 Andrej Shadura :
>
> Hi,
>
> As far as I remember, I think you don’t need to be subscribed.
>
> On Tue, 18 Jan 2022, at 11:50, Michael Biebl wrote:
> > I only saw this reply by accident, as I wasn't CCed.
> > But I assume this was directed at me.
> >
> > CCing the upstream mailing list will probably not work, since I'm not
> > subscribed.
> >
> > Anyway, here is the requested output.
> > I hope the results are properly anonymized as I didn't check the logs
> > and I don't want to change my WiFi password :-)
> >
> > The package upgrade starts at 11:35
> >
> > I let wpasupplicant/NM try for another 3 mins before I stopped them.
> >
> > Regards,
> > Michael
> >
> > On Tue, 18 Jan 2022 09:09:14 +0100 "Andrej Shadura" 
> > wrote:
> >> Adding the Debian bug to the loop.
> >>
> >> On Tue, 18 Jan 2022, at 03:59, Masashi Honma wrote:
> >> > To investigate more, could you enable wpa_supplicant debug option and
> >> > provide the log ?
> >> >
> >> > Procedure is like this.
> >> >
> >> > 1) Edit 
> >> > /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service to
> >> > add -dd option like this.
> >> >
> >> > ExecStart=/sbin/wpa_supplicant -u -s -dd -O /run/wpa_supplicant
> >> >
> >> > 2) Reboot wpa_supplicant.
> >> > $ sudo systemctl daemon-reload
> >> >
> >> > 3) Enable NetworkManager logging
> >> > $ sudo nmcli general logging level DEBUG domains ALL
> >> >
> >> > 4) Get logs
> >> > $ journalctl -u NetworkManager -b
> >> >
> >> > If possible, could you provide Wi-Fi capture ?
> >> >
> >> > Regards,
> >> > Masashi Honma.
> >>
> >> --
> >> Cheers,
> >>   Andrej
> >>
> >>
> >
> > Attachments:
> > * wpasupplicant.txt
> > * NetworkManager.txt
> > * OpenPGP_signature
>
> --
> Cheers,
>   Andrej___
> Hostap mailing list
> hos...@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/hostap

Bug#1003847: marked as done (binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others))

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 20:35:00 +
with message-id 
and subject line Bug#1003847: fixed in glibc 2.33-3
has caused the Debian Bug report #1003847,
regarding binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: 
`vspltisb' (and others)
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.)


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

Source: binutils, glibc
Control: found -1 binutils/2.37.50.20220106-2
Control: found -1 glibc/2.33-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: affects -1 gcc-10 gcc-11

Dear maintainer(s),

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


   passfail
binutils   from testing2.37.50.20220106-2
glibc  from testing2.33-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 binutils, gcc-10 
and gcc-11 to testing [1]. Due to the nature of this issue, I filed this 
bug report against the binutils and glibc source packages. Can you 
please investigate the situation and reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/ppc64el/g/glibc/18280958/log.gz

powerpc64le-linux-gnu-gcc-10 
../sysdeps/ieee754/ldbl-128ibm/tst-strtold-ldbl-128ibm.c -c -std=gnu11 
-fgnu89-inline  -pipe -O2 -g 
-fdebug-prefix-map=/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src=. 
-mcpu=power8 -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants 
-frounding-math -fstack-protector-strong -Wstrict-prototypes 
-Wold-style-definition -fmath-errno -mabi=ieeelongdouble -Wno-psabi 
-mno-gnu-attribute  -mlong-double-128   -mabi=ibmlongdouble 
-isystem 
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/debian/include 
-I../include 
-I/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/stdlib 

-I/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc 
 -I../sysdeps/unix/sysv/linux/powerpc/powerpc64/le/fpu 
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64/fpu 
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64/le 
-I../sysdeps/unix/sysv/linux/powerpc/powerpc64 
-I../sysdeps/unix/sysv/linux/wordsize-64 
-I../sysdeps/unix/sysv/linux/powerpc  -I../sysdeps/powerpc/nptl 
-I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux 
-I../sysdeps/nptl  -I../sysdeps/pthread  -I../sysdeps/gnu 
-I../sysdeps/unix/inet  -I../sysdeps/unix/sysv 
-I../sysdeps/unix/powerpc  -I../sysdeps/unix  -I../sysdeps/posix 
-I../sysdeps/powerpc/powerpc64/le/power8/fpu/multiarch 
-I../sysdeps/powerpc/powerpc64/le/power7/fpu/multiarch 
-I../sysdeps/powerpc/powerpc64/le/fpu/multiarch 
-I../sysdeps/powerpc/powerpc64/le/power8/fpu 
-I../sysdeps/powerpc/powerpc64/le/power7/fpu 
-I../sysdeps/powerpc/powerpc64/le/fpu 
-I../sysdeps/powerpc/powerpc64/fpu 
-I../sysdeps/powerpc/powerpc64/le/power8/multiarch 
-I../sysdeps/powerpc/powerpc64/le/power7/multiarch 
-I../sysdeps/powerpc/powerpc64/le/multiarch 
-I../sysdeps/powerpc/powerpc64/multiarch 
-I../sysdeps/powerpc/powerpc64/le/power8 
-I../sysdeps/powerpc/powerpc64/power8 
-I../sysdeps/powerpc/powerpc64/le/power7 
-I../sysdeps/powerpc/powerpc64/power7 
-I../sysdeps/powerpc/powerpc64/power6 
-I../sysdeps/powerpc/powerpc64/power4  -I../sysdeps/powerpc/power4 
-I../sysdeps/powerpc/powerpc64/le  -I../sysdeps/powerpc/powerpc64 
-I../sysdeps/wordsize-64  -I../sysdeps/powerpc/fpu  -I../sysdeps/powerpc 
 -I../sysdeps/ieee754/ldbl-128ibm-compat 
-I../sysdeps/ieee754/ldbl-128ibm/include 
-I../sysdeps/ieee754/ldbl-128ibm  -I../sysdeps/ieee754/ldbl-opt 
-I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32 
-I../sysdeps/ieee754/float128  -I../sysdeps/ieee754 
-I../sysdeps/generic  -I.. -I../libio -I. -nostdinc -isystem 
/usr/lib/gcc/powerpc64le-linux-gnu/10/include -isystem 
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/debian/include 
-D_LIBC_REENTRANT -include 
/tmp/autopkgtest-lxc.448kjxt6/downtmp/build.UW5/src/build-tree/ppc64el-libc/

Bug#1003574: marked as done (segfault in libc-2.33.so during i386 boot ofde QEMU VM)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 20:35:00 +
with message-id 
and subject line Bug#1003610: fixed in glibc 2.33-3
has caused the Debian Bug report #1003610,
regarding segfault in libc-2.33.so during i386 boot ofde QEMU VM
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.)


-- 
1003610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.33-2
Severity: normal

When booting an i386 VM built for autopkgtests, I see the following
segfault during boot:

> [1.374128] Freeing unused kernel image (initmem) memory: 940K
> [1.384002] Write protecting kernel text and read-only data: 11292k
> [1.384526] Run /init as init process
> Loading, please wait...
> Starting version 250.2-1
> [1.406157] udevadm[106]: segfault at bc ip b7d9f638 sp bf989cb8 error 
> 6 in libc-2.33.so[b7c6e000
> [1.407017] Code: 1c 8b 01 ca ff e3 29 d9 8d b4 26 00 00 00 00 8d 76 00 0f 
> 18 8a c0 03 00 00 0f 18 8a
> Segmentation fault

Boot continues briefly after that, but then drops to an emergency shell.

I've tried the other popular architectures, but I only saw this on i386.


To reproduce, this requires qemu-system-x86 and autopkgtest >= 5.17.

# Build image
$ sudo autopkgtest-build-qemu \
--mirror http://deb.debian.org/debian
--arch i386 \
unstable i386.img

# Boot image. -enable-kvm assumes that this is being tested on amd64
# Optionally use -nographic for terminal output instead of GUI
$ qemu-system-i386 \
-machine q35 \
-enable-kvm \
-device virtio-serial \
-nic user,model=virtio \
-m 1024 -smp 1 \
i386.img

Filing as severity "normal" as it can't be ruled out that this is a QEMU
issue, though I would be surprised. Unfortunately, I no longer have i386
hardware on which I could test this.
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.33-3
Done: Aurelien Jarno 

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

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 18 Jan 2022 19:06:44 +0100
Source: glibc
Architecture: source
Version: 2.33-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1003574 1003610 1003847
Changes:
 glibc (2.33-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-ttydefaults.diff: New patch to fix default
 character for termio cc[VSTATE].
   * debian/patches/hurd-i386/git-const.diff: Constify RPCs server-side.
 - debian/control: Bump mig build-dep accordingly.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix FTBFS on ppc64el with recent binutils snapshots.  Closes: #1003847.
 - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
   be determined.  Closes: #1003574, #1003610.
 - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
 - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).
 .
   [ Gunnar Hjalmarsson ]
   * debian/local/usr_sbin/update-locale: tweak validation of args to
 update-locale().
Checksums-Sha1:
 6e9f094f445a8f6a883080d566a4bb39cd080e66 9631 glibc_2.33-3.dsc
 c6cb74fc11a6b7b84b15134b1073d5db25fc9133 815404 glibc_2.33-3.debian.tar.xz
 6ed674db63e1bb32ceade0950b1dcd25f28256cd 8897 glibc_2.33-3_source.buildinfo
Checksums-Sha256:
 5f2f07b974f79975369ea77a7dd5dddb5d85b6fec5e390da5c295529932c16c5 9631 
glibc_2.33-3.dsc
 4b184b55337cec4786c15c162314d05421a5b734089ad5dd54a34d49e37a81ff 815404 
glibc_2.33-3.debian.tar.xz
 a32cc1bdfe0529c3d4a20a0ac54c96a7ff2bd5f2a344c8f3da8d17403883d389 8897 
glibc_2.33-3_source.buildinfo
Files:
 71926b8274d2646ee90b80e388be7100 9631 libs required glibc_2.33-3.dsc
 8d4c5c4050441e874ef7f41387151755 815404 libs required 
glibc_2.33-3.debian.tar.xz
 f608aefd47f4024c7e386c8

Bug#1003610: marked as done (libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 20:35:00 +
with message-id 
and subject line Bug#1003610: fixed in glibc 2.33-3
has caused the Debian Bug report #1003610,
regarding libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33
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.)


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

Package: libc6
Version: 2.33-2
Severity: important

After upgrading from libc6 2.32 to 2.33 all machines with a VIA C7 or 
VIA Eden show segfaults in libc (i.e. hostname fails to work, or 
rebooting fails). Machines with VIA Nehemiah work fine.


I tested again starting with an older version of sid, upgrading all 
packages but libc6 (pinned to 2.32) (some other packaages could not been 
updated because they already depend on 2.33). This works fine.



Regards,
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.33-3
Done: Aurelien Jarno 

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

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 18 Jan 2022 19:06:44 +0100
Source: glibc
Architecture: source
Version: 2.33-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1003574 1003610 1003847
Changes:
 glibc (2.33-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-ttydefaults.diff: New patch to fix default
 character for termio cc[VSTATE].
   * debian/patches/hurd-i386/git-const.diff: Constify RPCs server-side.
 - debian/control: Bump mig build-dep accordingly.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix FTBFS on ppc64el with recent binutils snapshots.  Closes: #1003847.
 - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
   be determined.  Closes: #1003574, #1003610.
 - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
 - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).
 .
   [ Gunnar Hjalmarsson ]
   * debian/local/usr_sbin/update-locale: tweak validation of args to
 update-locale().
Checksums-Sha1:
 6e9f094f445a8f6a883080d566a4bb39cd080e66 9631 glibc_2.33-3.dsc
 c6cb74fc11a6b7b84b15134b1073d5db25fc9133 815404 glibc_2.33-3.debian.tar.xz
 6ed674db63e1bb32ceade0950b1dcd25f28256cd 8897 glibc_2.33-3_source.buildinfo
Checksums-Sha256:
 5f2f07b974f79975369ea77a7dd5dddb5d85b6fec5e390da5c295529932c16c5 9631 
glibc_2.33-3.dsc
 4b184b55337cec4786c15c162314d05421a5b734089ad5dd54a34d49e37a81ff 815404 
glibc_2.33-3.debian.tar.xz
 a32cc1bdfe0529c3d4a20a0ac54c96a7ff2bd5f2a344c8f3da8d17403883d389 8897 
glibc_2.33-3_source.buildinfo
Files:
 71926b8274d2646ee90b80e388be7100 9631 libs required glibc_2.33-3.dsc
 8d4c5c4050441e874ef7f41387151755 815404 libs required 
glibc_2.33-3.debian.tar.xz
 f608aefd47f4024c7e386c85ac32c7e0 8897 libs required 
glibc_2.33-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmHnIusACgkQE4jA+Jno
M2vkug/+KbopxKz/29IpY3H5aJ79IHH9wmhwSHalgSpqv+JC90Rhaea2zEFOMa4E
uFh4SQC6qhZ8cxTSSb8AFX0ZPiPTIOrCT+J2+1gWbZ+mkClzaqfIaHeCusp/HvdI
zWBT7aPLKaSxXRT5/HdUw56H2xbfFWngmnq3yTvCueZH6x0gjaP/ug94dG7ElFLC
DtvZowQLvmnBHC7Dsx/5UfV10XWUrgYeVjqnmmvxqfyKzKIF96X2GoFeEu+PwVXi
Rnbnwha0zbES0VpGrIaJuBR8DoJoPE7UrSS9z9SPf67rNbfurDQITAuR4CvojXx8
DbUHTLO6kWaAO2oQ3p0v/VJVrmpk3S4x2nNsB+fkF73KMSWvx6op4kB/ObvbqaQA
pPnqO6YXXAQnB0gG1AE+PJfFPaj+2AYIzM6SAGqXbO2ikxS7n7ufyW35Teo4CN5h
0oLWq2jshNbqytk/4fraL6whMvZORtkG8qFgfxvyWMK4SsEBMi+v9omiJESufTNS
RkIB0v3xa3AEmxFx0b9OsKL/s3mF3ioZ4hQAf18C4nnZvW9gYhJbNglfK07HGC3p
uqjqgHv87pkCCqiPu0U9lwfB/ViAk6svgf0XHjAemAsy3Z4RyaGL0BEh9/s6hRG4
G63dBt0CwW3gxt8QSCUTxlWNZX4qUmOZqQNXCWhDGLa0+QpCwdA=
=C9SG
-END PGP SIGNATURE End Message ---

Bug#1003610: marked as done (libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 20:35:00 +
with message-id 
and subject line Bug#1003574: fixed in glibc 2.33-3
has caused the Debian Bug report #1003574,
regarding libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33
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.)


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

Package: libc6
Version: 2.33-2
Severity: important

After upgrading from libc6 2.32 to 2.33 all machines with a VIA C7 or 
VIA Eden show segfaults in libc (i.e. hostname fails to work, or 
rebooting fails). Machines with VIA Nehemiah work fine.


I tested again starting with an older version of sid, upgrading all 
packages but libc6 (pinned to 2.32) (some other packaages could not been 
updated because they already depend on 2.33). This works fine.



Regards,
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.33-3
Done: Aurelien Jarno 

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

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 18 Jan 2022 19:06:44 +0100
Source: glibc
Architecture: source
Version: 2.33-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1003574 1003610 1003847
Changes:
 glibc (2.33-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-ttydefaults.diff: New patch to fix default
 character for termio cc[VSTATE].
   * debian/patches/hurd-i386/git-const.diff: Constify RPCs server-side.
 - debian/control: Bump mig build-dep accordingly.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix FTBFS on ppc64el with recent binutils snapshots.  Closes: #1003847.
 - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
   be determined.  Closes: #1003574, #1003610.
 - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
 - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).
 .
   [ Gunnar Hjalmarsson ]
   * debian/local/usr_sbin/update-locale: tweak validation of args to
 update-locale().
Checksums-Sha1:
 6e9f094f445a8f6a883080d566a4bb39cd080e66 9631 glibc_2.33-3.dsc
 c6cb74fc11a6b7b84b15134b1073d5db25fc9133 815404 glibc_2.33-3.debian.tar.xz
 6ed674db63e1bb32ceade0950b1dcd25f28256cd 8897 glibc_2.33-3_source.buildinfo
Checksums-Sha256:
 5f2f07b974f79975369ea77a7dd5dddb5d85b6fec5e390da5c295529932c16c5 9631 
glibc_2.33-3.dsc
 4b184b55337cec4786c15c162314d05421a5b734089ad5dd54a34d49e37a81ff 815404 
glibc_2.33-3.debian.tar.xz
 a32cc1bdfe0529c3d4a20a0ac54c96a7ff2bd5f2a344c8f3da8d17403883d389 8897 
glibc_2.33-3_source.buildinfo
Files:
 71926b8274d2646ee90b80e388be7100 9631 libs required glibc_2.33-3.dsc
 8d4c5c4050441e874ef7f41387151755 815404 libs required 
glibc_2.33-3.debian.tar.xz
 f608aefd47f4024c7e386c85ac32c7e0 8897 libs required 
glibc_2.33-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmHnIusACgkQE4jA+Jno
M2vkug/+KbopxKz/29IpY3H5aJ79IHH9wmhwSHalgSpqv+JC90Rhaea2zEFOMa4E
uFh4SQC6qhZ8cxTSSb8AFX0ZPiPTIOrCT+J2+1gWbZ+mkClzaqfIaHeCusp/HvdI
zWBT7aPLKaSxXRT5/HdUw56H2xbfFWngmnq3yTvCueZH6x0gjaP/ug94dG7ElFLC
DtvZowQLvmnBHC7Dsx/5UfV10XWUrgYeVjqnmmvxqfyKzKIF96X2GoFeEu+PwVXi
Rnbnwha0zbES0VpGrIaJuBR8DoJoPE7UrSS9z9SPf67rNbfurDQITAuR4CvojXx8
DbUHTLO6kWaAO2oQ3p0v/VJVrmpk3S4x2nNsB+fkF73KMSWvx6op4kB/ObvbqaQA
pPnqO6YXXAQnB0gG1AE+PJfFPaj+2AYIzM6SAGqXbO2ikxS7n7ufyW35Teo4CN5h
0oLWq2jshNbqytk/4fraL6whMvZORtkG8qFgfxvyWMK4SsEBMi+v9omiJESufTNS
RkIB0v3xa3AEmxFx0b9OsKL/s3mF3ioZ4hQAf18C4nnZvW9gYhJbNglfK07HGC3p
uqjqgHv87pkCCqiPu0U9lwfB/ViAk6svgf0XHjAemAsy3Z4RyaGL0BEh9/s6hRG4
G63dBt0CwW3gxt8QSCUTxlWNZX4qUmOZqQNXCWhDGLa0+QpCwdA=
=C9SG
-END PGP SIGNATURE End Message ---

Bug#1003574: marked as done (segfault in libc-2.33.so during i386 boot ofde QEMU VM)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 20:35:00 +
with message-id 
and subject line Bug#1003574: fixed in glibc 2.33-3
has caused the Debian Bug report #1003574,
regarding segfault in libc-2.33.so during i386 boot ofde QEMU VM
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.)


-- 
1003574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.33-2
Severity: normal

When booting an i386 VM built for autopkgtests, I see the following
segfault during boot:

> [1.374128] Freeing unused kernel image (initmem) memory: 940K
> [1.384002] Write protecting kernel text and read-only data: 11292k
> [1.384526] Run /init as init process
> Loading, please wait...
> Starting version 250.2-1
> [1.406157] udevadm[106]: segfault at bc ip b7d9f638 sp bf989cb8 error 
> 6 in libc-2.33.so[b7c6e000
> [1.407017] Code: 1c 8b 01 ca ff e3 29 d9 8d b4 26 00 00 00 00 8d 76 00 0f 
> 18 8a c0 03 00 00 0f 18 8a
> Segmentation fault

Boot continues briefly after that, but then drops to an emergency shell.

I've tried the other popular architectures, but I only saw this on i386.


To reproduce, this requires qemu-system-x86 and autopkgtest >= 5.17.

# Build image
$ sudo autopkgtest-build-qemu \
--mirror http://deb.debian.org/debian
--arch i386 \
unstable i386.img

# Boot image. -enable-kvm assumes that this is being tested on amd64
# Optionally use -nographic for terminal output instead of GUI
$ qemu-system-i386 \
-machine q35 \
-enable-kvm \
-device virtio-serial \
-nic user,model=virtio \
-m 1024 -smp 1 \
i386.img

Filing as severity "normal" as it can't be ruled out that this is a QEMU
issue, though I would be surprised. Unfortunately, I no longer have i386
hardware on which I could test this.
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.33-3
Done: Aurelien Jarno 

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

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 18 Jan 2022 19:06:44 +0100
Source: glibc
Architecture: source
Version: 2.33-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1003574 1003610 1003847
Changes:
 glibc (2.33-3) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-ttydefaults.diff: New patch to fix default
 character for termio cc[VSTATE].
   * debian/patches/hurd-i386/git-const.diff: Constify RPCs server-side.
 - debian/control: Bump mig build-dep accordingly.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix FTBFS on ppc64el with recent binutils snapshots.  Closes: #1003847.
 - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
   be determined.  Closes: #1003574, #1003610.
 - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
 - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).
 .
   [ Gunnar Hjalmarsson ]
   * debian/local/usr_sbin/update-locale: tweak validation of args to
 update-locale().
Checksums-Sha1:
 6e9f094f445a8f6a883080d566a4bb39cd080e66 9631 glibc_2.33-3.dsc
 c6cb74fc11a6b7b84b15134b1073d5db25fc9133 815404 glibc_2.33-3.debian.tar.xz
 6ed674db63e1bb32ceade0950b1dcd25f28256cd 8897 glibc_2.33-3_source.buildinfo
Checksums-Sha256:
 5f2f07b974f79975369ea77a7dd5dddb5d85b6fec5e390da5c295529932c16c5 9631 
glibc_2.33-3.dsc
 4b184b55337cec4786c15c162314d05421a5b734089ad5dd54a34d49e37a81ff 815404 
glibc_2.33-3.debian.tar.xz
 a32cc1bdfe0529c3d4a20a0ac54c96a7ff2bd5f2a344c8f3da8d17403883d389 8897 
glibc_2.33-3_source.buildinfo
Files:
 71926b8274d2646ee90b80e388be7100 9631 libs required glibc_2.33-3.dsc
 8d4c5c4050441e874ef7f41387151755 815404 libs required 
glibc_2.33-3.debian.tar.xz
 f608aefd47f4024c7e386c8

Bug#1003610: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1003610 in glibc 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/glibc-team/glibc/-/commit/41086a4c85e828a019b1ab3adbf20f0d6d791df6


debian/patches/git-updates.diff: update from upstream stable branch:

  - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
be determined.  Closes: #1003574, #1003610.
  - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
  - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003610

Processed: Bug#1003574 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003574 [libc6] segfault in libc-2.33.so during i386 boot ofde QEMU VM
Bug #1003610 [libc6] libc6 crashes with VIA C7 and VIA Eden processors starting 
with 2.33
Ignoring request to alter tags of bug #1003574 to the same tags previously set
Ignoring request to alter tags of bug #1003610 to the same tags previously set

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

Bug#1003574: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1003574 in glibc 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/glibc-team/glibc/-/commit/41086a4c85e828a019b1ab3adbf20f0d6d791df6


debian/patches/git-updates.diff: update from upstream stable branch:

  - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
be determined.  Closes: #1003574, #1003610.
  - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
  - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003574

Processed: Bug#1003610 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003610 [libc6] libc6 crashes with VIA C7 and VIA Eden processors starting 
with 2.33
Bug #1003574 [libc6] segfault in libc-2.33.so during i386 boot ofde QEMU VM
Ignoring request to alter tags of bug #1003610 to the same tags previously set
Ignoring request to alter tags of bug #1003574 to the same tags previously set

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

Bug#1003975: gnuradio-dev: Missing dependency on libspdlog-dev

[Adrian Bunk]

Package: gnuradio-dev
Version: 3.10.0.0-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:gr-fosphor src:gr-funcube src:gr-hpsdr src:gr-iqbal 
src:gr-rds src:gr-satellites

https://buildd.debian.org/status/fetch.php?pkg=gr-fosphor&arch=amd64&ver=3.9%7E0.974ab2f-1%2Bb2&stamp=1642532351&raw=0

...
CMake Error at /usr/share/cmake-3.22/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
  By not providing "Findspdlog.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "spdlog", but
  CMake did not find one.

  Could not find a package configuration file provided by "spdlog" with any
  of the following names:

spdlogConfig.cmake
spdlog-config.cmake

  Add the installation prefix of "spdlog" to CMAKE_PREFIX_PATH or set
  "spdlog_DIR" to a directory containing one of the above files.  If "spdlog"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GnuradioConfig.cmake:13 
(find_dependency)
  CMakeLists.txt:34 (find_package)


-- Configuring incomplete, errors occurred!

Processed: gnuradio-dev: Missing dependency on libspdlog-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:gr-fosphor src:gr-funcube src:gr-hpsdr src:gr-iqbal src:gr-rds 
> src:gr-satellites
Bug #1003975 [gnuradio-dev] gnuradio-dev: Missing dependency on libspdlog-dev
Added indication that 1003975 affects src:gr-fosphor, src:gr-funcube, 
src:gr-hpsdr, src:gr-iqbal, src:gr-rds, and src:gr-satellites

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

Bug#1002121: marked as done (gr-limesdr: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 19:50:30 +
with message-id 
and subject line Bug#1002121: fixed in gr-limesdr 3.0.1-3
has caused the Debian Bug report #1002121,
regarding gr-limesdr: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
`pthread_create'
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.)


-- 
1002121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-limesdr
Version: 3.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_ae954.dir/src.c.o: in function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
> `pthread_create'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined 
> reference to `pthread_detach'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: undefined 
> reference to `pthread_cancel'
> /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14: undefined 
> reference to `pthread_join'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/gr-limesdr_3.0.1-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: gr-limesdr
Source-Version: 3.0.1-3
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated gr-limesdr 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: Tue, 18 Jan 2022 20:23:05 +0100
Source: gr-limesdr
Architecture: source
Version: 3.0.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 1002121
Changes:
 gr-limesdr (3.0.1-3) unstable; urgency=low
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Christoph Berg ]
   * B-D on libspdlog-dev.
   * Disable detection of git at build time.
   * Add patch by Chris Gorman, NZSmartie, and Daniel Estévez to support
 GNUradio 3.9. (Closes: #1002121)
   * B-D on python3-numpy and call dh_numpy3.
Checksums-Sha1:
 63c2cbc4b8239ed7f1eb6c7b17a91bb41084539f 2307 gr-limesdr_3.0.1-3.dsc
 1d5d39cb1b84fedb8979b28a71735c2f47ff5301 63852 gr-limesdr_3.0.1-3.debian.tar.xz
Checksums-Sha256:
 c97846782f4e7e5c9d80648e6f5a898d076bebb879b2332adc477507b26c1e01 2307 
gr-limesdr_3.0.1-3.dsc
 8693898fc6015c594cd9a8afd6e76da77f30569da468206e02a4de9a10eafab9 63852 
gr-limesdr_3.0.1-3.debian.tar.xz
Files:
 63fea581a30b2dd6e989285d31b791f1 2307 hamradio optional gr-limesdr_3.0.1-3.dsc
 2c9dbe914e4b56b9420244cfff7835ae 63852 hamradio optional 
gr-limesdr_3.0.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmHnGNgACgkQTFprqxLS
p66eIQ/9EUK/HEQMR8/Jy1aOxjutN/cNJAHhEf/rgGzLew+/1REhe7QFOCAH1gsG
hGa7YpT7KB8hGx6riRrM3sBsZOU5iuCv7t4tsM0bLbXRwiS8njYy8yyHrg0lkcmQ
IJ6roY/vUhCQpKHdE6AW7nbYwlRAahv4LMBZNQpixEBcIN3K6qfwFZqevcvNtr1j
04rhlzNOJi3c/HwKzxrC5EsxJi5TK9GpRreEd4zAOqjVMmzOBgC0tuToKGuvJ+fo
vyT3wt5Ihb556mhnel2oqwcNIzrjk0TzfKRDWFOmnfg7FHBrk+tGo5+irbKXDpYz
hSToABT4AnjLErpX8FjxtrnotmqgX5nfDVmopmL1QsOrB6kkQJgJ9FGvlNvo3ECB
tacez

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2022-01-18 19:30:39)
> Control: reassign -1 src:cmark-gfm 0.29.0.gfm.2-1
> Control: retitle -1 cmark-gfm: shlibs too relaxed for unstable ABI
> Control: affects -1 pandoc blogliterately gitit pandoc-citeproc patat

[...]

> Hmm - thinking on it, it seems to me that the change really should be 
> in the libcmark-gfm package - something like this (untested):
> 
> override_dh_makeshlibs:
> dh_makeshlibs --version-info="libcmark-gfm0 (>= ${DEB_VERSION}), 
> libcmark-gfm0 (<< ${DEB_VERSION}+)"

For cmark the above essentially worked - here is the complete changes: 
https://salsa.debian.org/debian/cmark/-/commit/8be8eba

When applied, reverse dependencies need a binNMU...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: bug 1003964 is forwarded to https://github.com/commonmark/cmark/issues/252 ...

[Debian Bug Tracking System]

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

> forwarded 1003964 https://github.com/commonmark/cmark/issues/252
Bug #1003964 [src:cmark-gfm] cmark-gfm: shlibs too relaxed for unstable ABI
Set Bug forwarded-to-address to 
'https://github.com/commonmark/cmark/issues/252'.
> forwarded 1003970 https://github.com/commonmark/cmark/issues/252
Bug #1003970 [src:cmark] cmark: shlibs too relaxed for unstable ABI
Set Bug forwarded-to-address to 
'https://github.com/commonmark/cmark/issues/252'.
> thanks
Stopping processing here.

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

Bug#1003955: marked as done (systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 19:06:52 +
with message-id 
and subject line Bug#1003955: fixed in systemd 250.3-1
has caused the Debian Bug report #1003955,
regarding systemd: systemd-networkd: wireguard AllowedIPs is inserted into 
routing table
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.)


-- 
1003955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 250.2-3
Severity: critical
Justification: completely breaks network connectivity in certain setups
X-Debbugs-Cc: none, Tollef Fog Heen 

(Feel free to downgrade, but this completely broke network on my testing
system, which weren't it my laptop and sat in front of me, it'd be
really hard to debug.)

It seems like systemd-networkd between 249.7-1 and 250.2-3 started
adding IPs specified in AllowedIPs in WireGuardPeer stanzas in netdev
units to the routing table.

The documentation in systemd.netdev states:

   Note that this only affects routing inside the network interface 
itself, i.e. the
   packets that pass through the tunnel itself. To cause packets to be 
sent via the
   tunnel in the first place, an appropriate route needs to be added as 
well — either in
   the "[Routes]" section on the ".network" matching the wireguard 
interface, or
   externally to systemd-networkd.

This is the historic behaviour, and this behaviour can be had by using
RouteTable=off in the WireGuardPeer section.

The reason it broke is I have a multi-peer wireguard setup where I
direct traffic to the different peers a machine can talk to using BGP
and bird, and therefore has AllowedIPs=0.0.0.0/0 for the netdevs. After
the upgrade, systemd-networkd proceeded to make my default route point
at the tunnels (which are not suitable as default routes) in addition to
my regular default route, causing most of the traffic to end up on the
floor.

It might be possible to detect this in a postinst, but it's probably
brittle, so I'd consider changing the default RouteTable setting to off.

-- System Information:
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.3.1-1
ii  libapparmor1 3.0.3-6
ii  libaudit11:3.0.6-1+b1
ii  libblkid12.37.2-6
ii  libc62.33-2
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.27-1
ii  libcryptsetup12  2:2.4.3-1
ii  libfdisk12.37.2-6
ii  libgcrypt20  1.9.4-5
ii  libgnutls30  3.7.2-5
ii  libgpg-error01.43-1
ii  libip4tc21.8.7-1
ii  libkmod2 29-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.37.2-6
ii  libpam0g 1.4.0-11
ii  libseccomp2  2.5.3-2
ii  libselinux1  3.3-1+b1
ii  libsystemd0  250.2-3
ii  libzstd1 1.4.8+dfsg-3
ii  mount2.37.2-6
ii  util-linux   2.37.2-6

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]  1.12.20-3
ii  ntp [time-daemon]   1:4.2.8p15+dfsg-1

Versions of packages systemd suggests:
ii  libfido2-11.9.0-1
ii  libtss2-esys-3.0.2-0  3.1.0-3
ii  libtss2-mu0   3.1.0-3
ii  libtss2-rc0   3.1.0-3
ii  policykit-1   0.105-31
ii  systemd-container 250.2-3

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   250.2-3
ii  libpam-systemd   250.2-3
ii  udev 250.2-3

-- no debconf information

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 250.3-1
Done: Michael Biebl 

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Tue, 18 Jan 2022 18:52:45 +0100
Source: systemd
Architecture: source
Version: 250.3-1
Distri

Bug#1003865: marked as done (GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 18:53:06 +
with message-id 
<582900164cd11084efccf10192631e502d140cfb.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1003865: GPG error: http://deb.debian.org/debian sid 
InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 
Debian Archive Automatic Signing Key (10/buster) 
has caused the Debian Bug report #1003865,
regarding GPG error: http://deb.debian.org/debian sid InRelease: The following 
signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic 
Signing Key (10/buster) 
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.)


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

Package: debian-archive-keyring
Version: 2021.1.1
Severity: grave
Justification: this breaks updating any package

On Debian sid, apt update is broken for some days now

$ sudo apt update
Get:1 http://deb.debian.org/debian sid InRelease [165 kB]
Err:1 http://deb.debian.org/debian sid InRelease
 The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian 
Archive Automatic Signing Key (10/buster) 

Get:2 http://deb.debian.org/debian experimental InRelease [75.4 kB]
Err:2 http://deb.debian.org/debian experimental InRelease
 The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian 
Archive Automatic Signing Key (10/buster) 

Hit:3 https://packages.riot.im/debian sid InRelease
Hit:4 https://people.debian.org/~praveen/nheko unstable InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1369 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository 
is not updated and the previous index files will be used. GPG error: 
http://deb.debian.org/debian sid InRelease: The following signatures 
were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing 
Key (10/buster) 
W: An error occurred during the signature verification. The repository 
is not updated and the previous index files will be used. GPG error: 
http://deb.debian.org/debian experimental InRelease: The following 
signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive 
Automatic Signing Key (10/buster) 
W: Failed to fetch http://deb.debian.org/debian/dists/sid/InRelease The 
following signatures were invalid: BADSIG 648ACFD622F3D138 Debian 
Archive Automatic Signing Key (10/buster) 
W: Failed to fetch 
http://deb.debian.org/debian/dists/experimental/InRelease The following 
signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive 
Automatic Signing Key (10/buster) 
W: Some index files failed to download. They have been ignored, or old 
ones used instead.
--- End Message ---
--- Begin Message ---
Control: tags -1 + moreinfo unreproducible

On Mon, 2022-01-17 at 13:34 +0530, Pirate Praveen wrote:
> Package: debian-archive-keyring
> Version: 2021.1.1
> Severity: grave
> Justification: this breaks updating any package
> 
> On Debian sid, apt update is broken for some days now
> 
> $ sudo apt update
> Get:1 http://deb.debian.org/debian sid InRelease [165 kB]
> Err:1 http://deb.debian.org/debian sid InRelease
>   The following signatures were invalid: BADSIG 648ACFD622F3D138
> Debian 
> Archive Automatic Signing Key (10/buster) 
> Get:2 http://deb.debian.org/debian experimental InRelease [75.4 kB]
> Err:2 http://deb.debian.org/debian experimental InRelease
>   The following signatures were invalid: BADSIG 648ACFD622F3D138
> Debian 
> Archive Automatic Signing Key (10/buster) 

Based on the fact that autobuilding of unstable is still continuing and
there haven't been any reports of this issue on either #d-devel or 
debian-devel@lists, it seems unlikely that there's a general issue
here, rather than something more local to your environment.

In any case, if there were an issue, it would either be with the
archive itself (which is ftp.d.o territory) or with deb.d.o (which is
mirror team / DSA territory), not with either debian-archive-keyring
(which simply ships the public keys) or APT.

Regards,

Adam--- End Message ---

Processed: Re: Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1003964 [pandoc] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Bug 1003964 cloned as bug 1003970
> reassign -1 src:cmark-gfm 0.29.0.gfm.2-1
Bug #1003964 [pandoc] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Bug reassigned from package 'pandoc' to 'src:cmark-gfm'.
No longer marked as found in versions pandoc/2.9.2.1-2.
Ignoring request to alter fixed versions of bug #1003964 to the same values 
previously set
Bug #1003964 [src:cmark-gfm] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Marked as found in versions cmark-gfm/0.29.0.gfm.2-1.
> retitle -1 cmark-gfm: shlibs too relaxed for unstable ABI
Bug #1003964 [src:cmark-gfm] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Changed Bug title to 'cmark-gfm: shlibs too relaxed for unstable ABI' from 
'pandoc doesn't start: error while loading shared libraries: 
libcmark-gfm.so.0.29.0.gfm.0'.
> affects -1 pandoc blogliterately gitit pandoc-citeproc patat
Bug #1003964 [src:cmark-gfm] cmark-gfm: shlibs too relaxed for unstable ABI
Added indication that 1003964 affects pandoc, blogliterately, gitit, 
pandoc-citeproc, and patat
> reassign -2 src:cmark 0.30.2-3
Bug #1003970 [pandoc] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Bug reassigned from package 'pandoc' to 'src:cmark'.
No longer marked as found in versions pandoc/2.9.2.1-2.
Ignoring request to alter fixed versions of bug #1003970 to the same values 
previously set
Bug #1003970 [src:cmark] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Marked as found in versions cmark/0.30.2-3.
> severity -2 important
Bug #1003970 [src:cmark] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Severity set to 'important' from 'grave'
> retitle -2 cmark: shlibs too relaxed for unstable ABI
Bug #1003970 [src:cmark] pandoc doesn't start: error while loading shared 
libraries: libcmark-gfm.so.0.29.0.gfm.0
Changed Bug title to 'cmark: shlibs too relaxed for unstable ABI' from 'pandoc 
doesn't start: error while loading shared libraries: 
libcmark-gfm.so.0.29.0.gfm.0'.

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

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[Jonas Smedegaard]

Control: clone -1 -2
Control: reassign -1 src:cmark-gfm 0.29.0.gfm.2-1
Control: retitle -1 cmark-gfm: shlibs too relaxed for unstable ABI
Control: affects -1 pandoc blogliterately gitit pandoc-citeproc patat
Control: reassign -2 src:cmark 0.30.2-3
Control: severity -2 important
Control: retitle -2 cmark: shlibs too relaxed for unstable ABI

Quoting Jonas Smedegaard (2022-01-18 18:40:33)
> Quoting gregor herrmann (2022-01-18 18:08:02)
> > While looking at some test issues in libpod-pandoc-perl, I noticed
> > that pandoc looks quite broken in current amd64/sid:
> > 
> > % pandoc --version
> > pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0: 
> > cannot open shared object file: No such file or directory
> [...]
> > So it looks like pandoc wants libcmark-gfm.so.0.29.0.gfm.0 but 
> > libcmark-gfm0 ships libcmark-gfm.so.0.29.0.gfm.2. Maybe this is an 
> > issue in libcmark-gfm0 … Not sure where to fix this.
> 
> libcmark-gfm offers an unstable API, so I guess pandoc packaging is to 
> blame for having too loose dependency on that inherently untameable 
> library package.
> 
> Thanks for reporting, Gregor - might be enough to request a binNMU but 
> I'd better tighten that dependency, so will do a regular upload.

Hmm - thinking on it, it seems to me that the change really should be in 
the libcmark-gfm package - something like this (untested):

override_dh_makeshlibs:
dh_makeshlibs --version-info="libcmark-gfm0 (>= ${DEB_VERSION}), 
libcmark-gfm0 (<< ${DEB_VERSION}+)"

Similar is required for the package cmark.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1003955: Acknowledgement (systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table)

[Tollef Fog Heen]

]] Michael Biebl 

> sorry for the inconvenience

No worries.

> Am 18.01.22 um 17:03 schrieb Tollef Fog Heen:
> > It seems like this is
> > https://github.com/systemd/systemd/issues/21964.
> > 
> 
> I'm working on an update as we speak. 250.3-1 should hit the archive
> later today.

Thanks a lot for the quick reaction on this and that you're maintaining
systemd.  Much appreciated!

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Processed: Bug#1003574 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003574 [libc6] segfault in libc-2.33.so during i386 boot ofde QEMU VM
Bug #1003610 [libc6] libc6 crashes with VIA C7 and VIA Eden processors starting 
with 2.33
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1003610: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1003610 in glibc 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/glibc-team/glibc/-/commit/41086a4c85e828a019b1ab3adbf20f0d6d791df6


debian/patches/git-updates.diff: update from upstream stable branch:

  - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
be determined.  Closes: #1003574, #1003610.
  - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
  - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003610

Processed: Bug#1003610 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003610 [libc6] libc6 crashes with VIA C7 and VIA Eden processors starting 
with 2.33
Bug #1003574 [libc6] segfault in libc-2.33.so during i386 boot ofde QEMU VM
Ignoring request to alter tags of bug #1003610 to the same tags previously set
Ignoring request to alter tags of bug #1003574 to the same tags previously set

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

Bug#1003574: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1003574 in glibc 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/glibc-team/glibc/-/commit/41086a4c85e828a019b1ab3adbf20f0d6d791df6


debian/patches/git-updates.diff: update from upstream stable branch:

  - Fix crashes in bzero/memset on i386 with SSE2 when the cache size cannot
be determined.  Closes: #1003574, #1003610.
  - Fix a buffer overflow in sunrpc svcunix_create (CVE-2022-23218).
  - Fix a buffer overflow in sunrpc clnt_create (CVE-2022-23219).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003574

Bug#984121: marked as done (fbreader: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 17:48:47 +
with message-id 
and subject line Bug#984121: fixed in fbreader 0.12.10dfsg2-6
has caused the Debian Bug report #984121,
regarding fbreader: 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.)


-- 
984121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fbreader
Version: 0.12.10dfsg2-4
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/fbreader_0.12.10dfsg2-4_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.

[...]
gcc -MMD -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W 
-DLIBICONV_PLUG -DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib\" -DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W -DLIBICONV_PLUG 
-DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" -DLIBDIR=\"/usr/lib\" 
-DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I /<>/fbreader/../zlibrary/core/include 
-I /<>/fbreader/../zlibrary/text/include  HtmlDCTagsReader.cpp
gcc -MMD -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W 
-DLIBICONV_PLUG -DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib\" -DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W -DLIBICONV_PLUG 
-DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" -DLIBDIR=\"/usr/lib\" 
-DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I /<>/fbreader/../zlibrary/core/include 
-I /<>/fbreader/../zlibrary/text/include  Migration.cpp
gcc -MMD -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W 
-DLIBICONV_PLUG -DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib\" -DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-pipe -fno-exceptions -Wall -Wno-ctor-dtor-privacy -W -DLIBICONV_PLUG 
-DINSTALLDIR=\"/usr\" -DBASEDIR=\"/usr/share\" -DLIBDIR=\"/usr/lib\" 
-DIMAGEDIR=\"/usr/share/pixmaps\" 
-DAPPIMAGEDIR=\"/usr/share/pixmaps/%APPLICATION_NAME%\" -DVERSION=\"0.12.10\" 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I /<>/fbreader/../zlibrary/core/include 
-I /<>/fbreader/../zlibrary/text/include  Migration_0_10_4.cpp
gcc -MMD -c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-pref

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[gregor herrmann]

On Tue, 18 Jan 2022 18:40:33 +0100, Jonas Smedegaard wrote:

> Thanks for reporting, Gregor - might be enough to request a binNMU but 
> I'd better tighten that dependency, so will do a regular upload.

Great, thanks in advance!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[Jonas Smedegaard]

Quoting gregor herrmann (2022-01-18 18:08:02)
> While looking at some test issues in libpod-pandoc-perl, I noticed
> that pandoc looks quite broken in current amd64/sid:
> 
> % pandoc --version
> pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0: 
> cannot open shared object file: No such file or directory
[...]
> So it looks like pandoc wants libcmark-gfm.so.0.29.0.gfm.0 but 
> libcmark-gfm0 ships libcmark-gfm.so.0.29.0.gfm.2. Maybe this is an 
> issue in libcmark-gfm0 … Not sure where to fix this.

libcmark-gfm offers an unstable API, so I guess pandoc packaging is to 
blame for having too loose dependency on that inherently untameable 
library package.

Thanks for reporting, Gregor - might be enough to request a binNMU but 
I'd better tighten that dependency, so will do a regular upload.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1003955: Acknowledgement (systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table)

[Michael Biebl]

Control: severity -1 grave
Control: forwarded -1 https://github.com/systemd/systemd/issues/21964
Control: tags -1 + fixed-upstream patch

Hi Tollef,

sorry for the inconvenience

Am 18.01.22 um 17:03 schrieb Tollef Fog Heen:


It seems like this is https://github.com/systemd/systemd/issues/21964.



I'm working on an update as we speak. 250.3-1 should hit the archive 
later today.


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1003955: Acknowledgement (systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1003955 [systemd] systemd: systemd-networkd: wireguard AllowedIPs is 
inserted into routing table
Severity set to 'grave' from 'critical'
> forwarded -1 https://github.com/systemd/systemd/issues/21964
Bug #1003955 [systemd] systemd: systemd-networkd: wireguard AllowedIPs is 
inserted into routing table
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/21964'.
> tags -1 + fixed-upstream patch
Bug #1003955 [systemd] systemd: systemd-networkd: wireguard AllowedIPs is 
inserted into routing table
Added tag(s) fixed-upstream and patch.

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

Processed: affects 1003962

[Debian Bug Tracking System]

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

> affects 1003962 pynest2d
Bug #1003962 [dh-python] Fails with --buildsystem=cmake if builddirectory 
contains package version with ~ tilde
Added indication that 1003962 affects pynest2d
> thanks
Stopping processing here.

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

Bug#1003964: pandoc doesn't start: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0

[gregor herrmann]

Package: pandoc
Version: 2.9.2.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While looking at some test issues in libpod-pandoc-perl, I noticed
that pandoc looks quite broken in current amd64/sid:

% pandoc --version
pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0: 
cannot open shared object file: No such file or directory
% echo $?
127
% apt-file search libcmark-gfm.so.0.29.0.gfm.0
libcmark-gfm0: /usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0
% dpkg -l libcmark-gfm0
…
ii  libcmark-gfm0:amd64 0.29.0.gfm.2-1 amd64CommonMark GitHub flavor 
gfm library
% dpkg -L libcmark-gfm0 
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2
/usr/share
/usr/share/doc
/usr/share/doc/libcmark-gfm0
/usr/share/doc/libcmark-gfm0/changelog.Debian.gz
/usr/share/doc/libcmark-gfm0/changelog.gz
/usr/share/doc/libcmark-gfm0/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libcmark-gfm0
% ls -la /usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2 
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0
ls: cannot access '/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.0': No 
such file or directory
- -rw-r--r-- 1 root root 317688 Jan 18 01:43 
/usr/lib/x86_64-linux-gnu/libcmark-gfm.so.0.29.0.gfm.2

So it looks like pandoc wants libcmark-gfm.so.0.29.0.gfm.0 but libcmark-gfm0
ships libcmark-gfm.so.0.29.0.gfm.2. Maybe this is an issue in libcmark-gfm0
… Not sure where to fix this.

cmark-gfm (0.29.0.gfm.2-1) unstable; urgency=medium

  * New upstream version.
  * Fix for CVE-2020-5238. (Closes: #965984)
  * Switch man page --safe to --unsafe. (Closes: #1003745)

 -- Keith Packard   Mon, 17 Jan 2022 16:43:27 -0800

cmark-gfm (0.29.0.gfm.0-6) unstable; urgency=medium

  * Use  directly instead of "config.h". (Closes: #969212)

 -- Keith Packard   Wed, 02 Sep 2020 10:25:33 -0700




Cheers,
gregor


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages pandoc depends on:
ii  libc6 2.33-2
ii  libcmark-gfm-extensions0  0.29.0.gfm.2-1
ii  libcmark-gfm0 0.29.0.gfm.2-1
ii  libffi8   3.4.2-4
ii  libgmp10  2:6.2.1+dfsg-3
ii  libpcre3  2:8.39-13
ii  pandoc-data   2.9.2.1-2
ii  zlib1g1:1.2.11.dfsg-2

pandoc recommends no packages.

Versions of packages pandoc suggests:
pn  citation-style-language-styles  
ii  context 2020.03.10.20200331-1
pn  ghc 
ii  groff   1.22.4-8
pn  libjs-katex 
ii  libjs-mathjax   2.7.9+dfsg-1
ii  librsvg2-bin2.50.7+dfsg-2
pn  nodejs  
pn  pandoc-citeproc 
ii  perl5.32.1-6
pn  php 
pn  python  
pn  r-base-core 
ii  ruby1:2.7.6
ii  texlive-latex-extra 2021.20211217-1
ii  texlive-latex-recommended   2021.20211217-1
ii  texlive-luatex  2021.20211217-1
ii  texlive-xetex   2021.20211217-1
pn  wkhtmltopdf 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmHm8/JfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaeqg//SynSrZ9ifms45FsFTw/25leWnr1rbeGLz3Xt+aRzfCqcS9gH21uEkXZZ
x1V0zUQlUMh0EtisO2cmQBqZGCzscCL4oHj7hRR3e1yzG4ONcptk0kzJBZK0UesD
0N+l0Q11fE2pVia7TG7kD3BF+FC9/JYobdiDYtIwrwxGBuVzch8xp1v6Vep+vow2
Zc3LUXF+cRyaVejMivVx4Gc1rfpkuZBwmkV5NbAUJ3NSLYsQEVoblBor9DS6BTTF
LyTPijwyWM808k3hVdoC/xFKNtpyMQuzkj4hTzqe7nVbLUEHYLPCzkywu0+5kTvU
cWCq+Z/XjPz0+lWoGrqaiKZ6PV54U+5iVB322ISUaWQA2isfIg/umOa9tBUA/mbd
KaS236uRP+rDwCP3AN0+sKBqhFzTZp7Hcr1BuUV+8cMK3FQB6lbU2u7w/wvFYqCG
eGdZ1FwYJ9HLwdGf3NdvVzwYR8QjMGwGW2L8NVjZsoL/0AQ8xMJsF004oinveVBy
WZIv4g29gvUfC7ac5GW3rPomaQygDJC0pqsqO3gCsD5HRwvoLAAkeWpRPRAimv4d
0MRKPWz7QvHtTZIUH+gxpjiICVEVJEdyYxGUq9qtFPil41rgBT+uFer4dUyt7bKr
yIsYn1SnB/PyhxkCJBPhRIpBQpCvbClpil9hKL3ODsEFjhCncXE=
=2b+J
-END PGP SIGNATURE-

Bug#1003962: Fails with --buildsystem=cmake if builddirectory contains package version with ~ tilde

[Christoph Berg]

Package: dh-python
Version: 5.20220101
Severity: serious
Affects: pynest2s

pynest2s 4.13~beta-1 ftbfses on all architectures:
https://buildd.debian.org/status/package.php?p=pynest2d

The reason is that pybuild "'double quotes'" the --builddirectory
argument, making it a relative path since it doesn't start with /.
Note how PKGBUILDDIR is duplicated:

dh build-arch --buildsystem=pybuild --with python3 --with sip3
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_configure --buildsystem=cmake 
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" -- [...]
...
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_build --buildsystem=cmake 
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" --
cd '/<>/pynest2d-4.13\~beta/.pybuild/cpython3_3.10/build' && 
make -j4 "INSTALL=install --strip-program=true" VERBOSE=1
make[1]: Entering directory 
'/<>/'/<>/.pybuild/cpython3_3.10/build''
(For whatever reason make is still happy with the borked path at that point...)
...
/usr/bin/cmake -E touch 
/<>/'/<>/.pybuild/cpython3_3.10/build'/src/sippynest2dpart0.cpp
 [...]
cmake -E touch: failed to update 
"/<>//<>/.pybuild/cpython3_3.10/build/src/sippynest2dpart0.cpp".


I suspect the error is in /usr/share/dh-python/dhpython/build/plugin_cmake.py:

return ('dh_auto_build --buildsystem=cmake'
' --builddirectory="{build_dir}"'

If I replace "{build_dir}" by {build_dir} in that file, the build
succeeds.

Christoph

Bug#1003955: Acknowledgement (systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table)

[Tollef Fog Heen]

It seems like this is https://github.com/systemd/systemd/issues/21964.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#1003955: systemd: systemd-networkd: wireguard AllowedIPs is inserted into routing table

[Tollef Fog Heen]

Package: systemd
Version: 250.2-3
Severity: critical
Justification: completely breaks network connectivity in certain setups
X-Debbugs-Cc: none, Tollef Fog Heen 

(Feel free to downgrade, but this completely broke network on my testing
system, which weren't it my laptop and sat in front of me, it'd be
really hard to debug.)

It seems like systemd-networkd between 249.7-1 and 250.2-3 started
adding IPs specified in AllowedIPs in WireGuardPeer stanzas in netdev
units to the routing table.

The documentation in systemd.netdev states:

   Note that this only affects routing inside the network interface 
itself, i.e. the
   packets that pass through the tunnel itself. To cause packets to be 
sent via the
   tunnel in the first place, an appropriate route needs to be added as 
well — either in
   the "[Routes]" section on the ".network" matching the wireguard 
interface, or
   externally to systemd-networkd.

This is the historic behaviour, and this behaviour can be had by using
RouteTable=off in the WireGuardPeer section.

The reason it broke is I have a multi-peer wireguard setup where I
direct traffic to the different peers a machine can talk to using BGP
and bird, and therefore has AllowedIPs=0.0.0.0/0 for the netdevs. After
the upgrade, systemd-networkd proceeded to make my default route point
at the tunnels (which are not suitable as default routes) in addition to
my regular default route, causing most of the traffic to end up on the
floor.

It might be possible to detect this in a postinst, but it's probably
brittle, so I'd consider changing the default RouteTable setting to off.

-- System Information:
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.3.1-1
ii  libapparmor1 3.0.3-6
ii  libaudit11:3.0.6-1+b1
ii  libblkid12.37.2-6
ii  libc62.33-2
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.27-1
ii  libcryptsetup12  2:2.4.3-1
ii  libfdisk12.37.2-6
ii  libgcrypt20  1.9.4-5
ii  libgnutls30  3.7.2-5
ii  libgpg-error01.43-1
ii  libip4tc21.8.7-1
ii  libkmod2 29-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.37.2-6
ii  libpam0g 1.4.0-11
ii  libseccomp2  2.5.3-2
ii  libselinux1  3.3-1+b1
ii  libsystemd0  250.2-3
ii  libzstd1 1.4.8+dfsg-3
ii  mount2.37.2-6
ii  util-linux   2.37.2-6

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]  1.12.20-3
ii  ntp [time-daemon]   1:4.2.8p15+dfsg-1

Versions of packages systemd suggests:
ii  libfido2-11.9.0-1
ii  libtss2-esys-3.0.2-0  3.1.0-3
ii  libtss2-mu0   3.1.0-3
ii  libtss2-rc0   3.1.0-3
ii  policykit-1   0.105-31
ii  systemd-container 250.2-3

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   250.2-3
ii  libpam-systemd   250.2-3
ii  udev 250.2-3

-- no debconf information

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#987689: tbb already in new queue of debian

[M. Zhou]

To anyone who is concerned with the package status in debian,
since there is a significant change in packaging, we have to
go through new queue again.

https://ftp-master.debian.org/new/onetbb_2021.4.0-1~exp1.html
This depends on our ftp team.

The latest package git repository is here:
https://salsa.debian.org/science-team/tbb

Bug#1003797: marked as done (libssreflect-coq: Depends: coq-8.14.0+4.11.1 but it is not installable)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 15:49:59 +
with message-id 
and subject line Bug#1003797: fixed in ssreflect 1.13.0-2
has caused the Debian Bug report #1003797,
regarding libssreflect-coq: Depends: coq-8.14.0+4.11.1 but it is not installable
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.)


-- 
1003797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssreflect-coq
Version: 1.13.0-1
Severity: serious

The following packages have unmet dependencies:
 libssreflect-coq : Depends: coq-8.14.0+4.11.1 but it is not installable

libssreflect-coq is binary-all, therefore requires a source upload.
--- End Message ---
--- Begin Message ---
Source: ssreflect
Source-Version: 1.13.0-2
Done: Julien Puydt 

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated ssreflect 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, 17 Jan 2022 08:57:04 +0100
Source: ssreflect
Architecture: source
Version: 1.13.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1003797
Changes:
 ssreflect (1.13.0-2) unstable; urgency=medium
 .
   * Source-only upload to trigger rebuild. (Closes: #1003797)
Checksums-Sha1:
 13c900fae08ef15fe45e66e4ed145f6af21dfc27 2111 ssreflect_1.13.0-2.dsc
 1cfdf8f9f0e8359140c14a612630bcf6739914f1 12140 ssreflect_1.13.0-2.debian.tar.xz
 1daf0d96591a2da0ef36e214b0ef26762ed2d700 7377 
ssreflect_1.13.0-2_source.buildinfo
Checksums-Sha256:
 4b2e56a046ced98c9db735c0f477b8f73b3a6f52213bad949542e0c8482ef5af 2111 
ssreflect_1.13.0-2.dsc
 ffc2d39af00b107a5877c5a1174f310a9ad9bdb658d2f635449eee8db96de5ef 12140 
ssreflect_1.13.0-2.debian.tar.xz
 935ff24718d330d79b5b53f2ce821f03ab917e83d610edc56d01dff1e78b6c07 7377 
ssreflect_1.13.0-2_source.buildinfo
Files:
 25369e72c0cda917a9027174ca8af2fb 2111 math optional ssreflect_1.13.0-2.dsc
 74c18c61db19ca08e51d86a77f104f6e 12140 math optional 
ssreflect_1.13.0-2.debian.tar.xz
 08476ec206fbd520630f8370a41950dd 7377 math optional 
ssreflect_1.13.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmHm298SHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRQ24P/12glSLHkxaIxShzmnQOKVZIUa3xse6z
2rCzyUHrxFc41ENGj3cVe6idIBh37dJu0IEksxfV+B8KmOdTiwk/AbSfPidoYKKY
6jTCMTUhUs860eleT1ZU85IhmmfQnwInT9Sx8yET8gpD2nZpck507BV99Dn8JTEb
1KGF3l2BvADyn0jePQruc5i/gIuM0r4KXoNHkc6pBmbrWfaj7OkZ2UafLiw4gFJ2
ffbpIj5+pqLW3aH/ZlcN2R3HWlAVny8kzUkJSAcIGBZkKFmbGmobztU8ZKV+Jxyl
S8XEDWUuG2cEK/koNB4tiG6DUIhlagONkDZmwh5qY0PRDHesCjf4xt3dWddSOmz2
kJT9hUkXpVZ3SHpfpIbEP5LsiOuODX2ygRjnq67TakGHDmbxewsYMavMUxQ+aEc6
pZKjXJCRy8oT2V6LCFhZc213GCBuHfAKMkGGMS3+2TtSxghy/4EGG+Jd4eDzeBvU
CS/Go/ALedov9ye8jtQmk0+etwSibu3eIDL/xCfFX58I8aydyePk00coefP6iEM+
qNI+n7UJUsAJDOQorvqILS7pNTK8g4VceTyFjC4MnYIJ0OQ4rqImMZBqaQnKPzLu
3jel8Sdgji0n3v/PzUnm21WQLMLDif9qsStUgwhVDVrGmCjKxCd/p3TdMSP/D98Z
iR278M2Tbi2M
=OLjF
-END PGP SIGNATURE End Message ---

Bug#1003907: fails to successfully associate

[Andrej Shadura]

I tried forwarding the logs to the hostapd list, but apparently the file is too 
large to be allowed by default.

The original message with the attachments can be found here: 
https://bugs.debian.org/1003907#20

On Tue, 18 Jan 2022, at 11:50, Michael Biebl wrote:
> I only saw this reply by accident, as I wasn't CCed.
> But I assume this was directed at me.
>
> CCing the upstream mailing list will probably not work, since I'm not 
> subscribed.
>
> Anyway, here is the requested output.
> I hope the results are properly anonymized as I didn't check the logs 
> and I don't want to change my WiFi password :-)
>
> The package upgrade starts at 11:35
>
> I let wpasupplicant/NM try for another 3 mins before I stopped them.
>
> Regards,
> Michael
>
> On Tue, 18 Jan 2022 09:09:14 +0100 "Andrej Shadura"  
> wrote:
>> Adding the Debian bug to the loop.
>> 
>> On Tue, 18 Jan 2022, at 03:59, Masashi Honma wrote:
>> > To investigate more, could you enable wpa_supplicant debug option and
>> > provide the log ?
>> >
>> > Procedure is like this.
>> >
>> > 1) Edit /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service 
>> > to
>> > add -dd option like this.
>> >
>> > ExecStart=/sbin/wpa_supplicant -u -s -dd -O /run/wpa_supplicant
>> >
>> > 2) Reboot wpa_supplicant.
>> > $ sudo systemctl daemon-reload
>> >
>> > 3) Enable NetworkManager logging
>> > $ sudo nmcli general logging level DEBUG domains ALL
>> >
>> > 4) Get logs
>> > $ journalctl -u NetworkManager -b
>> >
>> > If possible, could you provide Wi-Fi capture ?
>> >
>> > Regards,
>> > Masashi Honma.
>> 
>> -- 
>> Cheers,
>>   Andrej
>> 
>> 
>
> Attachments:
> * wpasupplicant.txt
> * NetworkManager.txt
> * OpenPGP_signature

-- 
Cheers,
  Andrej

Bug#1002772: marked as done (nfs-ganesha: FTBFS: internal.h:50:2: error: #error rados/rgw_file.h version unsupported (require >= 1.1.1))

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 15:27:32 +0100
with message-id 
and subject line Fwd: ntirpc_3.5-2_source.changes ACCEPTED into unstable
has caused the Debian Bug report #1002772,
regarding nfs-ganesha: FTBFS: internal.h:50:2: error: #error rados/rgw_file.h 
version unsupported (require >= 1.1.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.)


-- 
1002772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-ganesha
Version: 3.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211228 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/src/obj-x86_64-linux-gnu/FSAL/FSAL_RGW && /usr/bin/cc 
> -DHAS_DOFF -D_FILE_OFFSET_BITS=64 -Dfsalrgw_EXPORTS -I/usr/include/uuid 
> -I/<>/src/obj-x86_64-linux-gnu/include 
> -I/<>/src/include -I/<>/src/include/os/linux 
> -I/include -I/usr/include/ntirpc -I/usr -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE 
> -D_FILE_OFFSET_BITS=64 -fno-strict-aliasing -O2 -g -DNDEBUG -fPIC -MD -MT 
> FSAL/FSAL_RGW/CMakeFiles/fsalrgw.dir/up.c.o -MF 
> CMakeFiles/fsalrgw.dir/up.c.o.d -o CMakeFiles/fsalrgw.dir/up.c.o -c 
> /<>/src/FSAL/FSAL_RGW/up.c
> In file included from /<>/src/FSAL/FSAL_RGW/up.c:40:
> /<>/src/FSAL/FSAL_RGW/internal.h:50:2: error: #error 
> rados/rgw_file.h version unsupported (require >= 1.1.1)
>50 | #error rados/rgw_file.h version unsupported (require >= 1.1.1)
>   |  ^
> [ 83%] Linking C shared module libganesha_rados_recov.so
> cd /<>/src/obj-x86_64-linux-gnu/SAL && /usr/bin/cmake -E 
> cmake_link_script CMakeFiles/ganesha_rados_recov.dir/link.txt --verbose=1
> make[4]: *** [FSAL/FSAL_RGW/CMakeFiles/fsalrgw.dir/build.make:79: 
> FSAL/FSAL_RGW/CMakeFiles/fsalrgw.dir/up.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/28/nfs-ganesha_3.4-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 ---

FTBFS Error was fixed with Version 3.5
--- Begin Message ---


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Jan 2022 10:54:54 +0100
Source: ntirpc
Architecture: source
Version: 3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Christoph Martin 
Changes:
 ntirpc (3.5-2) unstable; urgency=medium
 .
   * include Debian Janitor fixes
Checksums-Sha1:
 6f382fa62777c38ec67a4def63106d458568234e 1952 ntirpc_3.5-2.dsc
 bf126810d2707947985d361a353b0187bb001629 385446 ntirpc_3.5.orig.tar.gz
 33ae5f672732ef188c619c99de01794de7e77d4e 7944 ntirpc_3.5-2.debian.tar.xz
 34ebbf9238241cdf75a2e47b7436fb4fa024ded5 8315 ntirpc_3.5-2_amd64.buildinfo
Checksums-Sha256:
 eca814ee7c498c225e94aedb8cfe8f084ad4161ef2482b490b16dcae661e97c6 1952 
ntirpc_3.5-2.dsc
 4487ad79d9573e5381348d16543ee983d9b27140703867ac65a8a3335d9e2ea4 385446 
ntirpc_3.5.orig.tar.gz
 995c6d5bf48fc6cbb2133359c68881d44cff78a51edc21187a522fb11b778339 7944 
ntirpc_3.5-2.debian.tar.xz
 fa0110524dc67849271378f54d2d10be03fc6239d79e60b5725ab9b9edcda1eb 8315 
ntirpc_3.5-2_amd64.buildinfo
Files:
 504a0b29deab0e9cff20e4e425e8a978 1952 net optional ntirpc_3.5-2.dsc
 cfce3c0523d8ef395f05554d2704e5ef 385446 net optional ntirpc_3.5.orig.tar.gz
 4066c77c9a51d180c0b08dd5ef146b7b 7944 net optional ntirpc_3.5-2.debian.tar.xz
 6fc65d2f3a64b6d815461ac218db5d39 8315 net optional ntirpc_3.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEienqSdlSvBRoCebg9oBraugTkrAFAmHcTPMACgkQ9oBraugT
krDMWw/9Gd8BZwcnw3t5bSvfgXEcmwzqmQd2DJ6fJxejzTpYbTHNsNXF14zT+AqA
XSBOp9BZzxfld9r7n/cpuKlyh6G0r/lic7jOogDnB2qQFLUsXMxl2hCqLXrONIMd
iohyau0FfmkjIEfzU2GDZvHBlMxOPbiPIYe0C4FJwCnJ/g0bNFnhSdPG6lDQMlwK
NDnWP+mg7VunClflEgPxgGcEUnUobgWHP+0z/ZLkRRWE2c5DaW3iZo0AF1XtAQDc
pQ+WUyF5WJwoePphOrCe0yAFbod8xeLUgP7VjUcYeFdUFz84apxTJfwAGuvD3PXI
KN83nv8ZGZTyCitJwVp2oAR3wLC1rX0QWBl21mdTNU9n/Fqg1dkGlxt/lPgzkvvo
rh6inkZPY1enohcZHcW5oUkPxhzLgp883vHhBGZ909wCqXEUWDnRUSJJUBQdAQif
R3S7CeEPo1OGesXvnklI

Bug#1002418: marked as done (mat2: FTBFS: AssertionError: 'TransparentColor' not found in {})

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 13:18:43 +
with message-id 
and subject line Bug#1002418: fixed in mat2 0.12.2-1.1
has caused the Debian Bug report #1002418,
regarding mat2: FTBFS: AssertionError: 'TransparentColor' not found in {}
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_jpg (tests.test_climat2.TestCleanFolder) ... ok
> test_jpg (tests.test_climat2.TestCleanMeta) ... ok
> test_jpg_nosandbox (tests.test_climat2.TestCleanMeta) ... ok
> test_different (tests.test_climat2.TestCommandLineParallel) ... WARNING: The 
> format of "./tests/data/parallel/dirty.mp4" (video/mp4) has some mandatory 
> metadata fields; mat2 filled them with standard data.
> WARNING: The format of "./tests/data/parallel/dirty.wmv" (video/x-ms-wmv) has 
> some mandatory metadata fields; mat2 filled them with standard data.
> ok
> test_faulty (tests.test_climat2.TestCommandLineParallel) ... ok
> test_same (tests.test_climat2.TestCommandLineParallel) ... ok
> test_jpg (tests.test_climat2.TestControlCharInjection) ... ok
> test_jpg_777 (tests.test_climat2.TestCopyPermissions) ... ok
> test_dependencies (tests.test_climat2.TestDependencies) ... ok
> test_docx (tests.test_climat2.TestGetMeta) ... ok
> test_flac (tests.test_climat2.TestGetMeta) ... ok
> test_jpg (tests.test_climat2.TestGetMeta) ... ok
> test_mp3 (tests.test_climat2.TestGetMeta) ... ok
> test_odt (tests.test_climat2.TestGetMeta) ... ok
> test_ogg (tests.test_climat2.TestGetMeta) ... ok
> test_pdf (tests.test_climat2.TestGetMeta) ... ok
> test_png (tests.test_climat2.TestGetMeta) ... ok
> test_help (tests.test_climat2.TestHelp) ... ok
> test_no_arg (tests.test_climat2.TestHelp) ... ok
> test_cleaning (tests.test_climat2.TestInplaceCleaning) ... ok
> test_cleaning_multiple_one_fails (tests.test_climat2.TestInplaceCleaning) ... 
> ok
> test_pdf (tests.test_climat2.TestIsSupported) ... ok
> test_nonzero (tests.test_climat2.TestReturnValue) ... ok
> test_zero (tests.test_climat2.TestReturnValue) ... ok
> test_version (tests.test_climat2.TestVersion) ... ok
> test_docx (tests.test_corrupted_files.TestCorruptedEmbedded) ... ok
> test_odt (tests.test_corrupted_files.TestCorruptedEmbedded) ... ok
> test_avi (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_avi_injection (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_bmp (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_docx (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_epub (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_flac (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_html (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_jpg (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_mp3 (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_odg (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_pdf (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_png (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_png2 (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_png_lightweight (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_tar (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_torrent (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_wrong_tif (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_zip (tests.test_corrupted_files.TestCorruptedFiles) ... ok
> test_pdf (tests.test_corrupted_files.TestExplicitelyUnsupportedFiles) ... ok
> test_brokensymlink (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_chardevice (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_folder (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_inexistingfile (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_notaccessible (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_ro (tests.test_corrupted_files.TestInexistentFiles) ... ok
> test_tar_absolute_path 
> (tests.test_corrupted_files.TestPathTraversalArchiveMembers) ... ok
> test_tar_device_file 
> (tests.test_corrupted_files.TestPathTraversalArchiveMembers) ... ok

Bug#1003933: w3c-sgml-lib: catalogs for MathML 2.0 are incomplete

[Vincent Lefevre]

Package: w3c-sgml-lib
Version: 1.3-2
Severity: grave
Justification: renders package unusable

The switch from w3-dtd-mathml to w3c-sgml-lib breaks the handling
of XML files using MathML 2.0 entities.

Consider the following test.xml file:


http://www.w3.org/TR/MathML2/dtd/isonum.ent";>
%ent-isonum;
http://www.w3.org/TR/MathML2/dtd/mmlalias.ent";>
%ent-mmlalias;
]>


$ xmllint --nonet --loaddtd test.xml
I/O error : Attempt to load network entity 
http://www.w3.org/TR/MathML2/dtd/isonum.ent
test.xml:6: warning: failed to load external entity 
"http://www.w3.org/TR/MathML2/dtd/isonum.ent";
%ent-isonum;
^
I/O error : Attempt to load network entity 
http://www.w3.org/TR/MathML2/dtd/mmlalias.ent
test.xml:10: warning: failed to load external entity 
"http://www.w3.org/TR/MathML2/dtd/mmlalias.ent";
%ent-mmlalias;
  ^

http://www.w3.org/TR/MathML2/dtd/isonum.ent";>
http://www.w3.org/TR/MathML2/dtd/mmlalias.ent";>
]>


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

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

Versions of packages w3c-sgml-lib depends on:
ii  xml-core  0.18+nmu1

w3c-sgml-lib recommends no packages.

w3c-sgml-lib suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence"

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #910813 [src:doc-linux-fr] doc-linux-fr: FTBFS, latex error "Package 
inputenc Error: Invalid UTF-8 byte sequence"
Added tag(s) patch.

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

Bug#910813: doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence"

[Lukas Märdian]

Package: doc-linux-fr
Version: 2013.01-3
Followup-For: Bug #910813
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to fix the build failure due to an
invalid UTF-8 byte sequence. Setting the output encoding of the xslt processor
to UTF-8 fixes the issue.


  * Fix FTBFS by using UTF-8 to produce the TeX (Closes: #910813)


Thanks for considering the patch.


-- System Information:
Debian Release: 11.0
  APT prefers impish-updates
  APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 
'impish'), (100, 'impish-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.0-23-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru doc-linux-fr-2013.01/debian/patches/fix_ftbfs_utf8.patch 
doc-linux-fr-2013.01/debian/patches/fix_ftbfs_utf8.patch
--- doc-linux-fr-2013.01/debian/patches/fix_ftbfs_utf8.patch1970-01-01 
01:00:00.0 +0100
+++ doc-linux-fr-2013.01/debian/patches/fix_ftbfs_utf8.patch2022-01-18 
10:05:56.0 +0100
@@ -0,0 +1,26 @@
+Description: Fix FTBFS with invalid UTF-8 sequence
+Author: Lukas Märdian 
+Origin: vendor, Ubuntu
+Forwarded: no
+Last-Update: 2022-01-18
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- doc-linux-fr-2013.01.orig/fcol-faq/to_tex.xsl
 doc-linux-fr-2013.01/fcol-faq/to_tex.xsl
+@@ -17,7 +17,7 @@ See the file COPYING for copying conditi
+  xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
+  xmlns="http://www.tug.org";>
+ 
+- 
++ 
+ 
+  
+ 
diff -Nru doc-linux-fr-2013.01/debian/patches/series 
doc-linux-fr-2013.01/debian/patches/series
--- doc-linux-fr-2013.01/debian/patches/series  2016-02-11 00:09:32.0 
+0100
+++ doc-linux-fr-2013.01/debian/patches/series  2022-01-18 10:04:54.0 
+0100
@@ -6,3 +6,4 @@
 0006-Use-local-resolver-thus-avoiding-network-access.patch
 0007-Use-proper-www.oasis-open.org-URL.patch
 0008-Workaround-incorrect-detection-of-ISO-8859-files.patch
+fix_ftbfs_utf8.patch

Bug#880786: doc-linux-fr build depends on removed transitional package lynx-cur

[Lukas Märdian]

Package: doc-linux-fr
Version: 2013.01-3
Followup-For: Bug #880786
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied for quite a while to not depend on
the transitional lynx-cur package anymore:

  * debian/control: build-depend on lynx instead of the deprecated lynx-cur
transitional package. (Closes: #880786)

Thanks for considering the patch.

Cheers,
  Lukas


-- System Information:
Debian Release: 11.0
  APT prefers impish-updates
  APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 
'impish'), (100, 'impish-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.0-23-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru doc-linux-fr-2013.01/debian/control 
doc-linux-fr-2013.01/debian/control
--- doc-linux-fr-2013.01/debian/control 2016-02-11 00:09:32.0 +0100
+++ doc-linux-fr-2013.01/debian/control 2022-01-18 10:16:07.0 +0100
@@ -20,7 +20,7 @@
  libxml2-utils,
  linuxdoc-tools,
  locales-all,
- lynx-cur,
+ lynx,
  texlive-binaries,
  texlive-lang-french,
  texlive-latex-base,

Processed: Re: doc-linux-fr build depends on removed transitional package lynx-cur

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #880786 [src:doc-linux-fr] doc-linux-fr build depends on removed 
transitional package lynx-cur
Ignoring request to alter tags of bug #880786 to the same tags previously set

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

Bug#1003344: marked as done (restfuldb: FTBFS with SQLite3 3.37.0+)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 09:04:17 +
with message-id 
and subject line Bug#1003307: fixed in restfuldb 0.15.2+dfsg-3
has caused the Debian Bug report #1003307,
regarding restfuldb: FTBFS with SQLite3 3.37.0+
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.)


-- 
1003307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: restfuldb
Version: 0.15.2+dfsg-2
Severity: serious
Tags: patch

Hi,

SQLite3 3.37.0 and onwards changed its inner working. Now table column
data types are stored as a value and always returned as uppercase
text. This breaks your package as it relies on the old behavior, when
this was stored as text and returned in a case it was defined.
As I broke it, I've created a fix for you, patch is attached. Couldn't
make it work with older SQLite3 versions thus you will need to build
depend on SQLite3 3.37.0 and newer.

Sorry for the inconvenience,
Laszlo/GCS
Description: SQLite3 3.37.0+ use uppercase column tupe names
 Starting with SQLite3 3.37.0 it stores column type names as a value and
 always displayed in uppercase letters.
 Previously it stored type names as text with the same case as it was given. 
 This breaks testing where the column type is defined in lowercase and
 expects it to be given back as-is.
 Fix this with using type names in uppercase.
Author: Laszlo Boszormenyi (GCS) 
Forwarded: no
Last-Update: 2022-01-08

---

--- restfuldb-0.15.2+dfsg.orig/tests/cases/Database.pm_007.sh
+++ restfuldb-0.15.2+dfsg/tests/cases/Database.pm_007.sh
@@ -31,8 +31,8 @@ trap "exit 1" HUP INT QUIT TERM
 
 TMP_DB_MAIN="${TMP_DIR}/test.db"
 
-sqlite3 ${TMP_DB_MAIN} "create table parent(id int, name text)"
-sqlite3 ${TMP_DB_MAIN} "create table child(id int, parent_id int, FOREIGN KEY(parent_id) REFERENCES parent(id))"
+sqlite3 ${TMP_DB_MAIN} "create table parent(id INT, name TEXT)"
+sqlite3 ${TMP_DB_MAIN} "create table child(id INT, parent_id INT, FOREIGN KEY(parent_id) REFERENCES parent(id))"
 sqlite3 ${TMP_DB_MAIN} "insert into parent values (1, 'first entry')"
 sqlite3 ${TMP_DB_MAIN} "insert into parent values (2, 'second entry')"
 sqlite3 ${TMP_DB_MAIN} "insert into child values (1, 1)"
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_001.out
+++ restfuldb-0.15.2+dfsg/tests/outputs/Database.pm_001.out
@@ -1,11 +1,11 @@
 $VAR1 = {
-  'image' => 'blob'
+  'image' => 'BLOB'
 };
 $VAR1 = {
-  'caption' => 'text',
-  'description' => 'text',
-  'id' => 'integer',
-  'image' => 'blob'
+  'caption' => 'TEXT',
+  'description' => 'TEXT',
+  'id' => 'INTEGER',
+  'image' => 'BLOB'
 };
 -
 $VAR1 = {
@@ -13,10 +13,10 @@ $VAR1 = {
   'authors' => 'varchar',
   'cdate' => 'date',
   'ctime' => 'time',
-  'id' => 'integer',
-  'revision_id' => 'integer',
-  'title' => 'text',
-  'year' => 'integer'
+  'id' => 'INTEGER',
+  'revision_id' => 'INTEGER',
+  'title' => 'TEXT',
+  'year' => 'INTEGER'
 };
 $VAR1 = {
   'PublicID' => '12',
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_007.out
+++ restfuldb-0.15.2+dfsg/tests/outputs/Database.pm_007.out
@@ -5,7 +5,7 @@ $VAR1 = [
 'coltype' => 'id',
 'length' => undef,
 'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
 'value' => 1
   },
   'parent_id' => {
@@ -29,14 +29,14 @@ $VAR1 = [
   'coltype' => 'id',
   'length' => undef,
   'resolver' => undef,
-  'sqltype' => 'int',
+  'sqltype' => 'INT',
   'value' => 1
 },
 'name' => {
   'coltype' => undef,
   'length' => undef,
   'resolver' => undef,
-  'sqltype' => 'text',
+  'sqltype' => 'TEXT',
   'value' => 'first entry'
 }
   },
@@ -66,7 +66,7 @@ $VAR1 = [
 },
 'length' => undef,
 'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
 'value' => 1
   }
 },
@@ -89,7 +89,7 @@ $VAR1 = [
 'coltype' => 'id',
 'length' => undef,
 'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
 'value' => 1
   },
   'parent_id' => {
@@ -109,7 +109,7 @@ $VAR1 = [
 }, 'Database::ForeignKey' ),
 'length' => undef,
 'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
 'value' => 2
   }
 },
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_012.out
+++ restfuldb-0.15.2+

Bug#1003307: marked as done (restfuldb: FTBFS against sqlite3 3.37 or newer)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jan 2022 09:04:17 +
with message-id 
and subject line Bug#1003307: fixed in restfuldb 0.15.2+dfsg-3
has caused the Debian Bug report #1003307,
regarding restfuldb: FTBFS against sqlite3 3.37 or newer
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.)


-- 
1003307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: restfuldb
Version: 0.15.2+dfsg-2
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy

Dear Maintainer,

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/1956798

When built against sqlite 3.37 or newer, the build will fail in test.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/r/restfuldb/20220107_080256_a18a5@/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/restfuldb/17950775/log.gz

tests/cases/Database.pm_001.sh:FAILED:
2c2
<   'image' => 'blob'
---
>   'image' => 'BLOB'

+many more of a similar nature.

As of sqlite 3.37.0, with FossilOrigin-Name:
d2da62a9df63036b02dadca3798de9e623c2680b3ef0c37d2b18bb88693afd7f,
type names for 5 common types BLOB, INT, INTEGER, REAL, and TEXT will be
treated as if they were created in all uppercase.

My proposed workaround is the following.  Due to the nature of the tests, any
sort of fixes to the test would in my opinion be best done upstream.

--- restfuldb-0.15.2+dfsg.orig/Makefile
+++ restfuldb-0.15.2+dfsg/Makefile
@@ -103,7 +103,7 @@ define can_run_test
 endef

 define diff_outputs
-diff -I 'Expires:\|Date:' ${OUTP_DIR}/$*.out -
+diff -i -I 'Expires:\|Date:' ${OUTP_DIR}/$*.out -
 endef

 define report_differences

-Dan
--- End Message ---
--- Begin Message ---
Source: restfuldb
Source-Version: 0.15.2+dfsg-3
Done: Andrius Merkys 

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

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

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated restfuldb 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, 18 Jan 2022 03:40:53 -0500
Source: restfuldb
Architecture: source
Version: 0.15.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Andrius Merkys 
Changed-By: Andrius Merkys 
Closes: 1003307
Changes:
 restfuldb (0.15.2+dfsg-3) unstable; urgency=medium
 .
   * Simplifying debian/watch.
   * Restoring compatibility with SQLite3 3.37.0 (Closes: #1003307).
   * Removing unused lintian override, false-positive in lintian << 2.105.0.
   * Marking all patches 'Forwarded: not-needed'.
   * Adjusting lintian override for web-application-works-only-with-apache.
   * Bumping copyright years.
Checksums-Sha1:
 4b9e13e191ed990c91805d41edd4b5739741e73d 3072 restfuldb_0.15.2+dfsg-3.dsc
 7f9222c880bf817610db8fb713bcc6935607bba5 25140 
restfuldb_0.15.2+dfsg-3.debian.tar.xz
 108466938080c73df45648b695b45154aed7a2da 11709 
restfuldb_0.15.2+dfsg-3_source.buildinfo
Checksums-Sha256:
 3a8ac842f8bd38f708934becdae4972b7d4ddd2e46a9ec1e642d583009f597eb 3072 
restfuldb_0.15.2+dfsg-3.dsc
 2ff0bf069adcf0d630cbbc0243309a8f239f514b548e6d497d3a08a3b3e02f9c 25140 
restfuldb_0.15.2+dfsg-3.debian.tar.xz
 39dc7a9a6c8be735997cd8c0b00b4763229a8a6d5606992f62efff410ba5a17a 11709 
restfuldb_0.15.2+dfsg-3_source.buildinfo
Files:
 cc604c6303118755cbc9357e4a53a705 3072 web optional restfuldb_0.15.2+dfsg-3.dsc
 d517fe3bfeb4a9498b960de609c1ab37 25140 web optional 
restfuldb_0.15.2+dfsg-3.debian.tar.xz
 439415baff99dd0507afdd81960ac977 11709 web optional 
restfuldb_0.15.2+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmHmfn8SHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHL90P/ik+rIqZKFgDEc/LnF9jYcuQM24f8XUu
4VdSXpc1/l2iBrKSDmcSmw+p6BA5z4qR4Jp567y2+SRUmyNp9iuH10vAUD3XD9Rj
KQUhZzBBQJqVcCmM15jmAzEyuX497SkoqEtG4d2fYrVgFpW2UFriJ1hnVXO/NNAx
UXARdCAhw8R93oXt0x7Ntlo36WwajaL8pSWx29U5LZ8CrPfcy6coooKwwgiXLaIG
qVkoy97Jbh5jxrBg4PlXyAIFI7ntq+q0+iTjo8qf65mJCzcepB4qFOkEcu81vArh
xcvuea+IBJa6btmdO2Qh+RYn3C7ZZVY27nvN4eKEbHDb

Processed: Bug#1002121 marked as pending in gr-limesdr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002121 [src:gr-limesdr] gr-limesdr: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to 
`pthread_create'
Added tag(s) pending.

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

Bug#1002121: marked as pending in gr-limesdr

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1002121 in gr-limesdr 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-hamradio-team/gr-limesdr/-/commit/6786822db8977e432157a2e270c76eb547e4599c


Add patch by Chris Gorman, NZSmartie, and Daniel Estévez to support GNUradio 
3.9. (Closes: #1002121)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002121

Bug#1003907: fails to successfully associate

[Andrej Shadura]

Adding the Debian bug to the loop.

On Tue, 18 Jan 2022, at 03:59, Masashi Honma wrote:
> To investigate more, could you enable wpa_supplicant debug option and
> provide the log ?
>
> Procedure is like this.
>
> 1) Edit /etc/systemd/system/multi-user.target.wants/wpa_supplicant.service to
> add -dd option like this.
>
> ExecStart=/sbin/wpa_supplicant -u -s -dd -O /run/wpa_supplicant
>
> 2) Reboot wpa_supplicant.
> $ sudo systemctl daemon-reload
>
> 3) Enable NetworkManager logging
> $ sudo nmcli general logging level DEBUG domains ALL
>
> 4) Get logs
> $ journalctl -u NetworkManager -b
>
> If possible, could you provide Wi-Fi capture ?
>
> Regards,
> Masashi Honma.

-- 
Cheers,
  Andrej