date:20211209

Processed: Re: [debian-mysql] Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok

2021-12-09 Thread Debian Bug Tracking System

Processing control commands:

> severity -1 wishlist
Bug #1001385 [mariadb-client-10.5] mariadb-client-10.5: authentification fails 
while the credentials are ok
Severity set to 'wishlist' from 'grave'

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

Bug#1001311: [Pkg-freeipa-devel] Bug#1001311: certmonger: FTBFS with openssl 3

2021-12-09 Thread Timo Aaltonen


On 8.12.2021 9.09, Steve Langasek wrote:

Source: certmonger
Version: 0.79.14+git20211010-2
Severity: serious
Tags: experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy

Hi Timo,

certmonger FTBFS against openssl 3 with an undefined symbol error:

[...]
gcc   -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem 
/usr/include/mit-krb5   -I/usr/include/uuid -g -O2 
-ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra  
-I/usr/include/libxml2 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/x86_64-linux-gnu -g -O2 
-ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -fPIC  -fPIC 
-pie -Wl,-z,relro,-z,now -o scep-submit scep_submit-scep.o scep_submit-submit-h.o scep_submit-util-m.o 
scep_submit-util-o.o scep_submit-submit-u.o scep_submit-util.o scep_submit-log.o scep_submit-pkcs7.o 
scep_submit-store-gen.o scep_submit-tm.o scep_submit-prefs.o scep_submit-prefs-o.o scep_submit-scep-o.o 
scep_submit-env-system.o -lcurl -lxml2 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 
-lcrypto -ltalloc  -luuid  -lpopt
../../src/submit-h.c: In function ‘cm_submit_h_run’:
../../src/submit-h.c:257:17: warning: call to 
‘_curl_easy_setopt_err_write_callback’ declared with attribute warning: 
curl_easy_setopt expects a curl_write_callback argument for this option 
[-Wattribute-warning]
   257 | curl_easy_setopt(ctx->curl, CURLOPT_WRITEFUNCTION,
   | ^
/usr/bin/ld: /tmp/ccPXkLF2.ltrans0.ltrans.o: in function `main':
./build/src/../../src/util-o.c:54: undefined reference to `OPENSSL_init_ssl'
collect2: error: ld returned 1 exit status
[...]

   
(https://launchpad.net/ubuntu/+source/certmonger/0.79.14+git20211010-2/+build/22293176)

openssl 3 is currently in experimental, and is expected to ship with the
next version of Debian.  It is also the version of openssl to be used for
the upcoming Ubuntu 22.04 LTS release.


Hi,

Yeah looks like upstream was lazy and never pushed a bunch of fixes from 
the Fedora package to upstream git, but I've poked them about this and 
should get a new release soon.



--
t

Bug#1001385: [debian-mysql] Bug#1001385: mariadb-client-10.5: authentification fails while the credentials are ok

2021-12-09 Thread Otto Kekäläinen

Control: severity -1 wishlist

On Thu, Dec 9, 2021 at 5:00 AM Anthony Bourguignon
 wrote:
...
> I’m having an issue with the mariadb-client in bullseye. I can’t connect
> to a local server using the mariadb client.
>
> To reproduce the bug :
>   - Install bullseye
>   - Install mariadb-server and mariadb-client
>   - connect as root and create a database and a user :
> create database testbug;
> grant all privileges on testbug.* to 'testbug'@'127.0.0.1'
> identified by 's3cr3t';
>   - exit the client
>   - try to connect with those credentials :
> mariadb -h 127.0.0.1 -u testbug -p testbug
>
> You can’t connect and get an error :
>   ERROR 1045 (28000): Access denied for user 'testbug'@'localhost' (using 
> password: YES)

You granted permissions to 'testbug'@'127.0.0.1' but you are
connecting from 'testbug'@'localhost'. Grant permissions to the
hostname (not IP) and try again. Also report back here if that solved
it for you, so we can close the bug report.

Thanks!

Processed: tagging 984189

2021-12-09 Thread Debian Bug Tracking System

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

> tags 984189 + fixed-upstream
Bug #984189 [src:libodb] libodb-boost: ftbfs with GCC-11
Bug #984191 [src:libodb] libodb: ftbfs with GCC-11
Bug #984192 [src:libodb] libodb-qt: ftbfs with GCC-11
Bug #984193 [src:libodb] libodb-mysql: ftbfs with GCC-11
Bug #984194 [src:libodb] libodb-pgsql: ftbfs with GCC-11
Bug #984197 [src:libodb] libodb-sqlite: ftbfs with GCC-11
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1000573: marked as done (Bytecode architectures blocking bug)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Fri, 10 Dec 2021 07:57:09 +0100
with message-id 
and subject line Upstream uninterested
has caused the Debian Bug report #1000573,
regarding Bytecode architectures blocking bug
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.)


-- 
1000573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coq
Version: 8.14.0+dfsg-6
Severity: grave
X-Debbugs-CC: debian-ocaml-ma...@lists.debian.org

Don't migrate to testing until the bytecode architectures' situation is
cleared.

Cheers,

J. Puydt
--- End Message ---
--- Begin Message ---
Hi,

after some discussion with upstream, they're not ready to support those
architectures, so we can just drop them.

Closing this report so that doesn't hamper migration to testing.

Cheers,

J.Puydt--- End Message ---

Bug#998827: Processed: Re: openorienteering-mapper: FTBFS with GDAL 3.4.0

2021-12-09 Thread Sebastiaan Couwenberg


On 12/10/21 06:56, Kai Pastor, DG0YT wrote:

Am 08.12.21 um 13:48 schrieb Debian Bug Tracking System:

Processing control commands:


severity -1 serious
Bug #998827 [src:openorienteering-mapper] openorienteering-mapper: 
FTBFS with GDAL 3.4.0

Severity set to 'serious' from 'important'

The build failure is in running the tests for georeferencing properties. 
Please verify if this can be resolved by installing proj-data and/or 
gdal-data as build dependencies.


gdal-data is installed as it is a dependency of libgdal,
proj-data is likewise installed as a dependency of libproj.

The proj-data package does not include the geotiff grids part of the 
upstream proj-data project, these are not packaged in Debian due to 
license issues:



https://alioth-lists.debian.net/pipermail/pkg-grass-devel/2020-April/084074.html

Setting PROJ_NETWORK=ON to get the grids from the CDN is not an option 
as there is no network in the buildds where the package is built.


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: your mail

2021-12-09 Thread Debian Bug Tracking System

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

> fixed 995014 zfs-linux/2.1.1-3
Bug #995014 {Done: Aron Xu } [src:zfs-linux] 
linux/linux-signe-* break zfs-linux autopkgtest: None of the expected 
"capability" interfaces were detected
Marked as fixed in versions zfs-linux/2.1.1-3.
> fixed 999663 zfs-linux/2.1.1-3
Bug #999663 {Done: Aron Xu } [src:zfs-linux] zfs-linux: FTBFS 
with libabigail 2.0
Marked as fixed in versions zfs-linux/2.1.1-3.
>
End of message, stopping processing here.

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

Bug#995653: marked as done (hyperkitty FTBFS with django-mailman3 1.3.7)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Thu, 09 Dec 2021 23:57:14 +
with message-id 
and subject line Bug#995653: fixed in hyperkitty 1.3.5-1
has caused the Debian Bug report #995653,
regarding hyperkitty FTBFS with django-mailman3 1.3.7
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.)


-- 
995653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-mailman3, hyperkitty
Control: found -1 django-mailman3/1.3.7-1
Control: found -1 hyperkitty/1.3.4-4
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
django-mailman3from testing1.3.7-1
hyperkitty from testing1.3.4-4
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 django-mailman3
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/h/hyperkitty/15711755/log.gz

==
ERROR: test_basic_reply (hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 69, in test_basic_reply
self.user.save()
  File
"/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
66, in save
super().save(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
743, in save
self.save_base(using=using, force_insert=force_insert,
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
791, in save_base
post_save.send(
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 173, in send
return [
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 174, in 
(receiver, receiver(signal=self, sender=sender, **named))
  File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line
101, in create_profile
address.display_name = new_display_name
AttributeError: 'str' object has no attribute 'display_name'

==
ERROR: test_reply_different_sender
(hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 102, in test_reply_different_sender
self.user.save()
  File
"/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
66, in save
super().save(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
743, in save
self.save_base(using=using, force_insert=force_insert,
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line
791, in save_base
post_save.send(
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 173, in send
return [
  File "/usr/lib/python3/dist-packages/django/dispatch/dispatcher.py",
line 174, in 
(receiver, receiver(signal=self, sender=sender, **named))
  File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line
101, in create_profile
address.display_name = new_display_name
AttributeError: 'str' object has no attribute 'display_name'

==
ERROR: test_smtp_error_raises_postingfailed
(hyperkitty.tests.lib.test_posting.PostingTestCase)
--
Traceback (most recent call last):
  File
"/usr/lib/python3/dist-packages/hyperkitty/tests/lib/test_posting.py",
line 89, in test_smtp_error_raises_postingfailed
self.user.save(

Bug#997361: marked as done (python3-testresources does not work with Python 3.10)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Thu, 09 Dec 2021 23:25:13 +
with message-id 
and subject line Bug#997361: fixed in testresources 2.0.1-3
has caused the Debian Bug report #997361,
regarding python3-testresources does not work with Python 3.10
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_IN_TMP=no
> + PKGOS_USE_PY2=no
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=rally
> + echo rally
> + sed s/python-//
> + PY_MODULE_NAME=rally
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.9
> + [ no = yes ]
> + [ yes = yes ]
> + [ no = yes ]
> + TARGET_DIR=python3-rally
> + pwd
> + python3.9 setup.py install --install-layout=deb --root 
> /<>/debian/python3-rally
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/rally
> creating build/lib/rally/plugins
> creating build/lib/rally/plugins/common
> creating build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/__init__.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/serial.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/constant.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/rps.py -> 
> build/lib/rally/plugins/common/runners
> creating build/lib/rally/plugins/task
> creating build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/__init__.py -> 
> build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/periodic.py -> 
> build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/event.py -> 
> build/lib/rally/plugins/task/hook_triggers
> creating build/lib/rally/ui
> copying rally/ui/__init__.py -> build/lib/rally/ui
> copying rally/ui/utils.py -> build/lib/rally/ui
> creating build/lib/rally/plugins/common/exporters
> creating build/lib/rally/plugins/common/exporters/elastic
> copying rally/plugins/common/exporters/elastic/__init__.py -> 
> build/lib/rally/plugins/common/exporters/elastic
> copying

Processed: Bug#995653 marked as pending in hyperkitty

2021-12-09 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #995653 [src:hyperkitty] hyperkitty FTBFS with django-mailman3 1.3.7
Added tag(s) pending.

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

Bug#995653: marked as pending in hyperkitty

2021-12-09 Thread Pierre-Elliott Bécue

Control: tag -1 pending

Hello,

Bug #995653 in hyperkitty 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/mailman-team/hyperkitty/-/commit/9685efaba3748e74af0d92aaa6ea6a08133b1aef


Mark bugs to be closed

Closes: #995653


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/995653

Bug#997361: marked as done (python3-testresources does not work with Python 3.10)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Thu, 09 Dec 2021 22:19:08 +
with message-id 
and subject line Bug#997361: fixed in testresources 2.0.1-2.1
has caused the Debian Bug report #997361,
regarding python3-testresources does not work with Python 3.10
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_USE_PY2=yes
> + PKGOS_USE_PY3=yes
> + PKGOS_IN_TMP=no
> + PKGOS_USE_PY2=no
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=rally
> + echo rally
> + sed s/python-//
> + PY_MODULE_NAME=rally
> + [ no = yes ]
> + [ yes = yes ]
> + py3versions -vr
> + PYTHON3S=3.9
> + [ no = yes ]
> + [ yes = yes ]
> + [ no = yes ]
> + TARGET_DIR=python3-rally
> + pwd
> + python3.9 setup.py install --install-layout=deb --root 
> /<>/debian/python3-rally
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/rally
> creating build/lib/rally/plugins
> creating build/lib/rally/plugins/common
> creating build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/__init__.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/serial.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/constant.py -> 
> build/lib/rally/plugins/common/runners
> copying rally/plugins/common/runners/rps.py -> 
> build/lib/rally/plugins/common/runners
> creating build/lib/rally/plugins/task
> creating build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/__init__.py -> 
> build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/periodic.py -> 
> build/lib/rally/plugins/task/hook_triggers
> copying rally/plugins/task/hook_triggers/event.py -> 
> build/lib/rally/plugins/task/hook_triggers
> creating build/lib/rally/ui
> copying rally/ui/__init__.py -> build/lib/rally/ui
> copying rally/ui/utils.py -> build/lib/rally/ui
> creating build/lib/rally/plugins/common/exporters
> creating build/lib/rally/plugins/common/exporters/elastic
> copying rally/plugins/common/exporters/elastic/__init__.py -> 
> build/lib/rally/plugins/common/exporters/elastic
> copyin

Bug#1001410: marked as done (python-csb: (autopkgtest) needs update for python3.10: TypeError: multiple bases have instance lay-out conflict)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Thu, 09 Dec 2021 22:18:55 +
with message-id 
and subject line Bug#1001410: fixed in python-csb 1.2.5+dfsg-7
has caused the Debian Bug report #1001410,
regarding python-csb: (autopkgtest) needs update for python3.10: TypeError: 
multiple bases have instance lay-out conflict
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.)


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

Source: python-csb
Version: 1.2.5+dfsg-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-csb fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-csb from testing1.2.5+dfsg-6
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 python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-csb/17420646/log.gz

/usr/lib/python3/dist-packages/csb/test/__init__.py:162: 
DeprecationWarning: the imp module is deprecated in favour of importlib 
and slated for removal in Python 3.12; see the module's documentation 
for alternative uses

  import imp
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.4e8yo8la/downtmp/autopkgtest_tmp/test/app.py", 
line 5, in 

from csb.test import Console
  File "/usr/lib/python3/dist-packages/csb/test/__init__.py", line 446, 
in 

class InvalidNamespaceError(NameError, ImportError):
TypeError: multiple bases have instance lay-out conflict
autopkgtest [13:26:23]: test build



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-csb
Source-Version: 1.2.5+dfsg-7
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated python-csb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 10 Dec 2021 03:37:52 +0530
Source: python-csb
Architecture: source
Version: 1.2.5+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 1001410
Changes:
 python-csb (1.2.5+dfsg-7) unstable; urgency=medium
 .
   * Team Upload.
   * Add patch to fix python 3.10 autopkgtest failure (Closes: #1001410)
   * d/t/build: Use -s with py3versions instead of -i
Checksums-Sha1:
 4850a4b0faa97294fcf4ea070b9a6c85c827c47a 2253 python-csb_1.2.5+dfsg-7.dsc
 12c223cf1fb35ffb9c8acb4f49fe77a3ba13d4a7 10556 
python-csb_1.2.5+dfsg-7.debian.tar.xz
 aa7e00a46778e04fedd21b465db912ec12b62ba3 8705 
python-csb_1.2.5+dfsg-7_amd64.buildinfo
Checksums-Sha256:
 226ef1e3ace5aa1281c4ed2ab3185ce3f21dfb28ea0eb2ee86a63505d4a354f6 2253 
python-csb_1.2.5+dfsg-7.dsc
 b24720fe29dc4d927c89ec62aef32856b426a2043835ad7e1e332a4f9cf49256 10556 
python-csb_1.2.5+dfsg-7.debian.tar.xz
 1d96cc7907e88143c7d715a53d3debda2219810c5c44de1f3892969202a87752 8705 
python-csb_1.2.5+dfsg-7_amd64.buildinfo
Files:
 cc1cb70d2401e7ac4eb0f766f990f899 2253 science optional 
python-csb_1.2.5+dfsg-7.ds

Bug#1001410: marked as pending in python-csb

2021-12-09 Thread Nilesh Patra

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/python-csb/-/commit/5f050a4f584824ac68e93fae75edb4c8c84acc10


Add patch to fix python 3.10 autopkgtest failure (Closes: #1001410)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001410

Processed: Bug#1001410 marked as pending in python-csb

2021-12-09 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1001410 [src:python-csb] python-csb: (autopkgtest) needs update for 
python3.10: TypeError: multiple bases have instance lay-out conflict
Added tag(s) pending.

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

Bug#997361: testresources: diff for NMU version 2.0.1-2.1

2021-12-09 Thread Stefano Rivera

Control: tags 997361 + patch

Dear maintainer,

I've prepared an NMU for testresources (versioned as 2.0.1-2.1). The diff
is attached to this message.

Regards.

SR
diff -Nru testresources-2.0.1/debian/changelog testresources-2.0.1/debian/changelog
--- testresources-2.0.1/debian/changelog	2020-05-08 06:08:01.0 -0400
+++ testresources-2.0.1/debian/changelog	2021-12-09 17:52:35.0 -0400
@@ -1,3 +1,10 @@
+testresources (2.0.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Python 3.10 support.  Closes: #997361
+
+ -- Stefano Rivera   Thu, 09 Dec 2021 17:52:35 -0400
+
 testresources (2.0.1-2) unstable; urgency=medium
 
   * Uploading to unstable.
diff -Nru testresources-2.0.1/debian/patches/python3.10.patch testresources-2.0.1/debian/patches/python3.10.patch
--- testresources-2.0.1/debian/patches/python3.10.patch	1969-12-31 20:00:00.0 -0400
+++ testresources-2.0.1/debian/patches/python3.10.patch	2021-12-09 17:52:35.0 -0400
@@ -0,0 +1,39 @@
+From: Athos Ribeiro 
+Date: Thu, 9 Dec 2021 17:45:47 -0400
+Subject: Use MutableSet collections.abc if available
+
+Python 3.10 removed the aliases to collections.abc from the collections
+module. See [1] for reference.
+
+[1] https://docs.python.org/3/whatsnew/3.10.html#removed
+
+Signed-off-by: Athos Ribeiro 
+---
+ testresources/__init__.py | 7 +--
+ 1 file changed, 5 insertions(+), 2 deletions(-)
+
+diff --git a/testresources/__init__.py b/testresources/__init__.py
+index 26363dd..c1a2ad0 100644
+--- a/testresources/__init__.py
 b/testresources/__init__.py
+@@ -20,7 +20,10 @@
+ import heapq
+ import inspect
+ import unittest
+-import collections
++try:
++from collections.abc import MutableSet
++except ImportError:
++from collections import MutableSet
+ try:
+ import unittest2
+ except ImportError:
+@@ -192,7 +195,7 @@ def _strongly_connected_components(graph, no_resources):
+ return partitions
+ 
+ 
+-class _OrderedSet(collections.MutableSet):
++class _OrderedSet(MutableSet):
+ """This is taken from the OrderedSet recipe link in the Python 2 docs.
+ 
+ See:
diff -Nru testresources-2.0.1/debian/patches/series testresources-2.0.1/debian/patches/series
--- testresources-2.0.1/debian/patches/series	2020-05-08 06:08:01.0 -0400
+++ testresources-2.0.1/debian/patches/series	2021-12-09 17:52:35.0 -0400
@@ -1 +1,2 @@
 remove-non-deterministic-ftbfs-testBasicSortTests.patch
+python3.10.patch

Processed: testresources: diff for NMU version 2.0.1-2.1

2021-12-09 Thread Debian Bug Tracking System

Processing control commands:

> tags 997361 + patch
Bug #997361 [python3-testresources] python3-testresources does not work with 
Python 3.10
Added tag(s) patch.

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

Bug#1001234: (no subject)

2021-12-09 Thread piorunz


By the way this is quick solution for people who want to painlessly
upgrade unsupported Firefox ESR in Bullseye, folks on Debian User
mailing list came up with this, I updated it a bit:


How to download & maintain new Firefox ESR from Mozilla, point always to
latest Firefox-ESR:

wget -O firefox.tar.bz2
"https://download.mozilla.org/?product=firefox-esr-latest&os=linux64&lang=en-GB";

tar vxf firefox.tar.bz2

Binary is in ~/firefox/firefox. You can replace Firefox shortcut you
use, or add a new one. Remember to backup ~/.mozilla first, as upgrading
Firefox will most likely make using profile again under Firefox ESR 78
impossible. Once Firefox ESR is updated in Stable, you can stop using it
and continue with normal Debian package.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1001234: src:firefox-esr: fails to migrate to testing for too long: FTBFS on mipsel and unresolved RC bug

2021-12-09 Thread piorunz

On Thu, 9 Dec 2021 19:35:47 +0100 Paul Gevers wrote:

Hi Piotr, Martin-Éric,

Please stop bashing Mike. He's doing a great job.

Hi Paul,

I am not bashing anyone. My post was simply a copy of my e-mail I sent
to Debian user group yesterday:
https://lists.debian.org/debian-user/2021/12/msg00242.html

My post also is here to raise awareness to this problem. I am worried. I
don't (didn't until now) know who is a maintainer of firefox-esr. From
what I gather here, it's Mike. I support him all the way, and I hope
firefox-esr can be updated quickly. I honestly think that Debian should
throw more resources at this problem, if it don't want to become a
laughing stock in the community:
https://www.phoronix.com/scan.php?page=news_item&px=Web-Browser-Packages-Debian
100+ posts and counting, all bashing on entire Debian project because of
this.

This bug was merely a procedure to raise awareness in case it was
missing and is part of the Release Team way of working. The required
action happened: the removal of the mipsel binary. All is good for the
migration at this moment.

That's good to hear. But didn't Mike just mentioned, that Firefox will
not migrate to Stable, due to Rust compiler problems?

There is work ongoing too for stable. Please remember we're all
volunteers and supporting a browser in Debian Stable is just not easy.

Of course, I support Debian volunteers and maintainers all the way!

I'd like to point out the notes about security support for browsers in
the Release Notes [1].

Link you posted, says, quote:
"The package debian-security-support helps to track the security support
status of installed packages. "

I installed this package, and run it:
check-support-status | grep firefox
(zero results)
Nowhere it says, that firefox-esr installed in my system is EOL and
vulnerable to several CVEs. This should be updated. I am happy to fill
bug against debian-security-support, do you want me to do that?

Also, same chapter of Release Notes you linked, goes on to say, that:
"For general web browser use we recommend Firefox or Chromium. They will
be kept up-to-date by rebuilding the current ESR releases for stable.
The same strategy will be applied for Thunderbird. "

Debian has failed to deliver on that. "Recommended" browser in Debian
Stable is EOL and vulnerable. And people are not aware of this as
Release Notes and debian-security-support is not showing the problem.

Release Notes should have been updated in November 2021, when
firefox-esr went EOL, to reflect this. Do Release Notes for Bullseye
receive "errata" updates? Shouldn't this be done right now?
Debian should throw more resources at flagship browser problem! I
sincerely hope this can be resolved quickly. We don't want people
blaming Debian for virus infections due to unpatched Firefox being
shipped in Stable.

Paul

[1]
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#limited-security-support

I don't know development process in Stable, but shouldn't firefox-esr
78.15.0esr-1~deb11u1 be removed from bullseye servers? It's vulnerable
and unusable in current state? Can it be removed at all? So people don't
fall for this false sense of security?

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1000791: marked as done (uhd: FTBFS on mipsel:)

2021-12-09 Thread Debian Bug Tracking System

Your message dated Thu, 09 Dec 2021 16:15:10 -0500
with message-id <83k0gdcwf5@scm.rf.org>
and subject line uhd: FTBFS on mipsel:
has caused the Debian Bug report #1000791,
regarding uhd: FTBFS on mipsel:
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.)


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

uhd fails to build on mipsel:
| FAILED: python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o 
| /usr/bin/c++ -DBOOST_ALL_NO_LIB 
-DBOOST_ASIO_DISABLE_STD_EXPERIMENTAL_STRING_VIEW 
-DBOOST_ASIO_DISABLE_STD_STRING_VIEW -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
-DBOOST_ERROR_CODE_HEADER_ONLY -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK 
-DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
-DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DHAVE_CONFIG_H -DUHD_LOG_CONSOLE_COLOR 
-DUHD_LOG_CONSOLE_LEVEL=2 -DUHD_LOG_FILE_LEVEL=2 -DUHD_LOG_MIN_LEVEL=1 
-Dpyuhd_EXPORTS -I/<>/obj-mipsel-linux-gnu/include 
-I/<>/host/include -I/usr/include/python3.9 
-I/<>/host/lib/deps/pybind11/include 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/<>/host/lib 
-I/<>/obj-mipsel-linux-gnu/_cmrc/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-fvisibility-inlines-hidden -O2 -g -DNDEBUG -fPIC   -Wall -Wextra 
-Wsign-compare -std=gnu++14 -MD -MT python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o -MF 
python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o.d -o 
python/CMakeFiles/pyuhd.dir/pyuhd.cpp.o -c 
/<>/host/python/pyuhd.cpp
|
| cc1plus: out of memory allocating 2217812 bytes after a total of 59752448 
bytes
| ninja: build stopped: subcommand failed.

See
https://buildd.debian.org/status/fetch.php?pkg=uhd&arch=mipsel&ver=4.1.0.4-2&stamp=1638083831&raw=0

If you start an uncoordinated transition, please ensure at least that
the package builds everywhere.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---

Package: src:uhd
Source: uhd
Version: 4.1.0.4-7

As of this version uhd now builds on mipsel.
This required:
 Explicitly set -DENABLE_PYTHON_API=OFF in debian/rules for mipsel
 move usrp_update_fs to python3-uhd

Note that the binary package python3-uhd is not built on mipsel.

-Maitland--- End Message ---

Bug#1001433: scitokens-cpp: FTBFS with openssl 3

2021-12-09 Thread Steve Langasek

Package: scitokens-cpp
Version: 0.6.2-1
Severity: serious
Tags: patch experimental
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Mattias,

In Ubuntu, scitokens-cpp is failing to build from source because we have
updated to update to openssl 3, and scitokens-cpp uses some functions which
are now deprecated:

[...]
/usr/bin/c++ -DSciTokens_EXPORTS -I/<> 
-I/<>/vendor/jwt-cpp/include -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror -std=c++11 -fPIC -MD -MT 
CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o -MF 
CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o.d -o 
CMakeFiles/SciTokens.dir/src/scitokens_cache.cpp.o -c 
/<>/src/scitokens_cache.cpp
In file included from /<>/src/scitokens_internal.h:6,
 from /<>/src/scitokens_cache.cpp:17:
/<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h: In constructor 
‘jwt::algorithm::ecdsa::ecdsa(const string&, const string&, const string&, 
const string&, const EVP_MD* (*)(), const string&, size_t)’:
/<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h:360:74: error: ‘EC_KEY* 
PEM_read_bio_EC_PUBKEY(BIO*, EC_KEY**, int (*)(char*, int, int, void*), void*)’ 
is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
  360 | 
pkey.reset(PEM_read_bio_EC_PUBKEY(pubkey_bio.get(), nullptr, nullptr, 
(void*)public_key_password.c_str()), EC_KEY_free);
  |
~~^~~~
In file included from /<>/vendor/jwt-cpp/include/jwt-cpp/jwt.h:11,
 from /<>/src/scitokens_internal.h:6,
 from /<>/src/scitokens_cache.cpp:17:
/usr/include/openssl/pem.h:463:1: note: declared here
  463 | DECLARE_PEM_rw_attr(OSSL_DEPRECATEDIN_3_0, EC_PUBKEY, EC_KEY)
  | ^~~
[...]

  
(https://launchpad.net/ubuntu/+source/scitokens-cpp/0.6.2-1build1/+build/22604628)

OpenSSL 3 is currently only in experimental in Debian, but is expected to be
the version shipped in the next release of Debian.

In Ubuntu, I've applied the following patch to let scitokens-cpp build by
ignoring the deprecation warnings.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru scitokens-cpp-0.6.2/debian/rules scitokens-cpp-0.6.2/debian/rules
--- scitokens-cpp-0.6.2/debian/rules2021-08-25 01:36:24.0 -0700
+++ scitokens-cpp-0.6.2/debian/rules2021-12-09 13:11:57.0 -0800
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations
+
 %:
dh $@

Processed: affects 1001421, block 1001421 with 997361

2021-12-09 Thread Debian Bug Tracking System

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

> affects 1001421 python-testresources
Bug #1001421 [src:python-launchpadlib] python-launchpadlib: (autopkgtest) needs 
update for python3.10: module 'collections' has no attribute 'MutableSet'
Added indication that 1001421 affects python-testresources
> block 1001421 with 997361
Bug #1001421 [src:python-launchpadlib] python-launchpadlib: (autopkgtest) needs 
update for python3.10: module 'collections' has no attribute 'MutableSet'
1001421 was not blocked by any bugs.
1001421 was not blocking any bugs.
Added blocking bug(s) of 1001421: 997361
> thanks
Stopping processing here.

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

Processed: re: pfstools: FTBFS: stl_algobase.h:278:56: error: macro "min" passed 3 arguments, but takes just 2

2021-12-09 Thread Debian Bug Tracking System

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

> Tags 998498 +patch
Bug #998498 [src:pfstools] pfstools: FTBFS: stl_algobase.h:278:56: error: macro 
"min" passed 3 arguments, but takes just 2
Added tag(s) patch.
> Thanks
Stopping processing here.

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

Bug#998498: pfstools: FTBFS: stl_algobase.h:278:56: error: macro "min" passed 3 arguments, but takes just 2

2021-12-09 Thread peter green


Tags 998498 +patch
Thanks


This looks like a problem with libnetpbm10-dev, it should not #define
generic max/min macros in a public header.


This can be worked around by changing the order in which headers are
included, so the C++ standard library headers are included before
the netpbm headers and hence unaffected by the macro.

Debdiff is attatched and has been uploaded to raspbian, no intent to
NMU in Debian.
diff -Nru pfstools-2.2.0/debian/changelog pfstools-2.2.0/debian/changelog
--- pfstools-2.2.0/debian/changelog 2021-08-29 16:19:07.0 +
+++ pfstools-2.2.0/debian/changelog 2021-12-09 19:43:19.0 +
@@ -1,3 +1,10 @@
+pfstools (2.2.0-1+rpi1) bookworm-staging; urgency=medium
+
+  * Reorder includes to stop macro in pm.h causing breakage in
+c++ system headers (Closes: 998498)
+
+ -- Peter Michael Green   Thu, 09 Dec 2021 19:43:19 
+
+
 pfstools (2.2.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru pfstools-2.2.0/debian/patches/43_reorder-includes-netpbm.patch 
pfstools-2.2.0/debian/patches/43_reorder-includes-netpbm.patch
--- pfstools-2.2.0/debian/patches/43_reorder-includes-netpbm.patch  
1970-01-01 00:00:00.0 +
+++ pfstools-2.2.0/debian/patches/43_reorder-includes-netpbm.patch  
2021-12-09 19:43:19.0 +
@@ -0,0 +1,23 @@
+Description:  Reorder includes to stop macro in pm.h causing breakage in c++ 
system headers
+Author: Peter Michael Green 
+Bug-Debian: https://bugs.debian.org/998498
+
+--- pfstools-2.2.0.orig/src/fileformat/ppmio.cpp
 pfstools-2.2.0/src/fileformat/ppmio.cpp
+@@ -27,13 +27,13 @@
+ 
+ #include "ppmio.h"
+ 
++#include 
++#include 
++
+ extern "C" {
+  #include 
+ }
+ 
+-#include 
+-#include 
+-
+ struct PPMData
+ {
+ pixval maxPV;
diff -Nru pfstools-2.2.0/debian/patches/series 
pfstools-2.2.0/debian/patches/series
--- pfstools-2.2.0/debian/patches/series2021-08-29 16:11:20.0 
+
+++ pfstools-2.2.0/debian/patches/series2021-12-09 19:43:19.0 
+
@@ -4,3 +4,4 @@
 25_Multiple-typo-fixes-suggested-by-lintian.patch
 30_parallel_build.diff
 42_reorder-includes-imagemagick.patch
+43_reorder-includes-netpbm.patch

Bug#1001430: unbound: FTBFS with OpenSSL 3

2021-12-09 Thread Steve Langasek

Package: unbound
Version: 1.13.1-1
Severity: serious
Tags: patch experimental
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Robert,

In Ubuntu, unbound is failing to build from source because it uses the
ERR_GET_FUNC() macro, which has been obsoleted in OpenSSL 3.

The attached patch addresses this by removing the call to the macro,
allowing unbound to build.

Please consider applying this patch in Debian.

OpenSSL 3 is currently in experimental, and expected to be the version of
OpenSSL shipped in the next release of Debian.

Thanks for considering,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru unbound-1.13.1/debian/patches/openssl3.patch 
unbound-1.13.1/debian/patches/openssl3.patch
--- unbound-1.13.1/debian/patches/openssl3.patch1969-12-31 
16:00:00.0 -0800
+++ unbound-1.13.1/debian/patches/openssl3.patch2021-12-09 
12:51:25.0 -0800
@@ -0,0 +1,20 @@
+Description: compatibility with OpenSSL 3
+Author: Steve Langasek 
+Last-Update: 2021-12-09
+Forwarded: no
+
+Index: unbound-1.13.1/smallapp/unbound-control.c
+===
+--- unbound-1.13.1.orig/smallapp/unbound-control.c
 unbound-1.13.1/smallapp/unbound-control.c
+@@ -492,9 +492,7 @@
+ {
+   unsigned long err;
+   err = ERR_peek_error();
+-  if (ERR_GET_LIB(err) == ERR_LIB_SYS &&
+-  (ERR_GET_FUNC(err) == SYS_F_FOPEN ||
+-   ERR_GET_FUNC(err) == SYS_F_FREAD) ) {
++  if (ERR_GET_LIB(err) == ERR_LIB_SYS) {
+   fprintf(stderr, "error: %s\n%s: %s\n",
+   s, path, ERR_reason_error_string(err));
+   exit(1);
diff -Nru unbound-1.13.1/debian/patches/series 
unbound-1.13.1/debian/patches/series
--- unbound-1.13.1/debian/patches/series2021-07-01 07:16:26.0 
-0700
+++ unbound-1.13.1/debian/patches/series2021-12-09 12:50:04.0 
-0800
@@ -1 +1,2 @@
 0001-Enable-remote-control-by-default.patch
+openssl3.patch

Processed: python-qtpy: (autopkgtest) needs update for python3.10: deprecation warning on stderr

2021-12-09 Thread Debian Bug Tracking System

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001429 [src:python-qtpy] python-qtpy: (autopkgtest) needs update for 
python3.10: deprecation warning on stderr
Added indication that 1001429 affects src:python3-defaults

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

1 2 >

1 - 100 of 128 matches

Mail list logo