Bug#1016621: marked as done (nvidia-graphics-drivers-tesla-510: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 05:50:37 +
with message-id 
and subject line Bug#1016621: fixed in nvidia-graphics-drivers-tesla-510 
510.85.02-1
has caused the Debian Bug report #1016621,
regarding nvidia-graphics-drivers-tesla-510: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5383

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-510
Source-Version: 510.85.02-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-510 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Aug 2022 07:24:37 +0200
Source: nvidia-graphics-drivers-tesla-510
Architecture: source
Version: 510.85.02-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016621
Changes:
 nvidia-graphics-drivers-tesla-510 (510.85.02-1) unstable; urgency=medium
 .
   * New upstream Tesla release 510.85.02 (2022-08-02).
 * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615. 

Bug#1016935: assaultcube: FTBFS with GCC 12: dwz fails

[Andreas Beckmann]

Source: assaultcube
Version: 1.2.0.2.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

Hi,

assaultcube recently started to FTBFS, this could be related to GCC 12
becoming the default compiler.

   dh_dwz -O--sourcedirectory=source/src
dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown debugging 
section .debug_addr
dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown debugging 
section .debug_addr
dwz: Too few files for multifile optimization
dh_dwz: error: dwz 
-mdebian/assaultcube/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/assaultcube.debug -- 
debian/assaultcube/usr/lib/games/assaultcube/ac_client 
debian/assaultcube/usr/lib/games/assaultcube/ac_server returned exit code 1
dh_dwz: error: Aborting due to earlier error
make: *** [debian/rules:9: binary] Error 25


Andreas


assaultcube_1.2.0.2.1-2.log.gz
Description: application/gzip

Processed: src:python-xarray: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2022.06.0-1
Bug #1016934 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions python-xarray/2022.06.0-1.
Bug #1016934 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1013939
Bug #1016934 {Done: Paul Gevers } [src:python-xarray] 
src:python-xarray: fails to migrate to testing for too long: autopkgtest 
regression
1016934 was not blocked by any bugs.
1016934 was not blocking any bugs.
Added blocking bug(s) of 1016934: 1013939

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

Bug#1016934: src:python-xarray: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: python-xarray
Version: 2022.03.0-2
Severity: serious
Control: close -1 2022.06.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1013939

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:python-xarray has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. It's blocked by an 
autopkgtest regression which I reported earlier in bug #1013939.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016933: src:ghc: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: ghc
Version: 8.8.4-3
Severity: serious
Control: close -1 9.0.2-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1015733

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:ghc has been trying to migrate for 61 days 
[2]. Hence, I am filing this bug. You have an unresolved RC bug that 
blocks migration. You also seem to have not finished the haskell 
transition that you started.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:ghc: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 9.0.2-3
Bug #1016933 [src:ghc] src:ghc: fails to migrate to testing for too long: 
unresolved RC bug
Marked as fixed in versions ghc/9.0.2-3.
Bug #1016933 [src:ghc] src:ghc: fails to migrate to testing for too long: 
unresolved RC bug
Marked Bug as done
> block -1 by 1015733
Bug #1016933 {Done: Paul Gevers } [src:ghc] src:ghc: fails 
to migrate to testing for too long: unresolved RC bug
1016933 was not blocked by any bugs.
1016933 was not blocking any bugs.
Added blocking bug(s) of 1016933: 1015733

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

Bug#1016750: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.

[Paul Gevers]

Hi Sean,

On 09-08-2022 18:17, Sean Whitton wrote:

I first looked at  and
the failure doesn't show up there -- do you know what that would be?


Yes, it's the difficulty of making good UI. In the past we reported the 
last overall result, but for testing that includes all tests with 
${random} package from unstable so that could be changing all the time, 
so we changed that to only report "pure" runs. It's on our wishlist to 
change it again and report both flavors on the same page, but we need a 
reasonable design to do that without causing too much confusion.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016927: [Debian-on-mobile-maintainers] Bug#1016927: gnome-console: Shortcuts being executed without shift being hold

[Evangelos Ribeiro Tzaras]

control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/5095

Hi,

On Tue, 2022-08-09 at 21:00 -0300, Thiago Bellini Ribeiro wrote:
> Hey Jeremy,
> 
> I not only closed and reopened the app but I also restarted my pc after my
> last update to Debian Sid.
> 
> Also, as I mentioned in the upstream bug, this issue affected both my office
> pc and my personal one the same way, both which I restarted after updating all
> pacakges (they both run Debian Sid).
> 
> On Tue, Aug 9, 2022 at 8:58 PM Jeremy Bicha 
> wrote:
> > On Tue, Aug 9, 2022 at 7:45 PM Thiago Bellini Ribeiro
> >  wrote:
> > > After upgrading to the current gnome-console version in Debian Sid
> > > (43~beta-1),
> > > all shortcuts are being executed even without pressing shift.
> > > 
> > > For example, ctrl+c is executing a copy (together with a SIGINT) just as
> > > if I
> > > pressed ctrl+shift+c
> > > ctrl+v is pasting without requiring shift being hold
> > > ctrl+w is closing the current tab
> > 
> > I'm not able to reproduce that bug either with Ubuntu 22.10 which is
> > running a similar version of gnome-console.

According to the devs it appears to be a X11 specific gtk bug.

Apparently it should be reproducible with
`$ GDK_BACKEND=x11 kgx`
which wasn't the case for me.

PS: Two Ribeiro's in this bug \o/

-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19


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

Processed: Re: [Debian-on-mobile-maintainers] Bug#1016927: gnome-console: Shortcuts being executed without shift being hold

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/gtk/-/issues/5095
Bug #1016927 [gnome-console] gnome-console: Shortcuts being executed without 
shift being hold
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gtk/-/issues/5095'.

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

Bug#1016925: kodi.log attached

[Vasyl Gello]

Control: severity -1 important

Hi Mark,

Sorry for the inconvenience!

I had to upload v20 with experimental ffmpeg5 support because otherwise we had 
no Kodi at all.
This case is the second video not playing that I am aware of. I am 
investigating the
"unsupported stream" error message and will send you a test build this week.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Processed: Re: Bug#1016925: kodi.log attached

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1016925 [kodi] kodi: Video playback not working in latest version of kodi
Severity set to 'important' from 'grave'

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

Bug#1016750: [Sbcl-bugs] Heap exhaustion problem with SBCL 2.2.6 on armel, armhf

[Sean Whitton]

Hello,

On Tue 09 Aug 2022 at 02:53PM -04, Douglas Katzman wrote:

> https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-ironclad/24441370/log.gz
> shows a GC invariant failure, not a heap exhaustion.

Hmm okay, sounds like it's a bug in sbcl rather than cl-ironclad, then.

> How do I identify the exact git revision of SBCL you're using? I can only 
> guess
> at what line# failed an assertion in my current tree.

We currently use the release tarballs from URIs matching:



plus these patches:



a couple of which are backported from git.

(If I continue to be the only person working on sbcl packaging in
Debian, I'll probably switch to packaging git revisions not tarballs,
and patches in git not in a directory like this, which'll mean that you
can work with our git repo directly.)

Thanks.

-- 
Sean Whitton

Bug#1009425: marked as done (prewikka: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable')

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2022 01:50:27 +
with message-id 
and subject line Bug#1009425: fixed in python-lesscpy 0.15.0+ds-0.1
has caused the Debian Bug report #1009425,
regarding prewikka: FTBFS: AttributeError: module 'collections' has no 
attribute 'Iterable'
to be marked as done.

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

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


-- 
1009425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prewikka
Version: 5.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 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
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running compile_catalog
> compiling catalog prewikka/locale/it/LC_MESSAGES/prewikka.po to 
> prewikka/locale/it/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/en/LC_MESSAGES/prewikka.po to 
> prewikka/locale/en/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:168: unknown named 
> placeholder 'version'
> error: prewikka/locale/ru/LC_MESSAGES/prewikka.po:2793: placeholders are 
> incompatible
> compiling catalog prewikka/locale/ru/LC_MESSAGES/prewikka.po to 
> prewikka/locale/ru/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2397: placeholders are 
> incompatible
> error: prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po:2810: placeholders are 
> incompatible
> compiling catalog prewikka/locale/pt_BR/LC_MESSAGES/prewikka.po to 
> prewikka/locale/pt_BR/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2162: placeholders are 
> incompatible
> error: prewikka/locale/pl/LC_MESSAGES/prewikka.po:2854: placeholders are 
> incompatible
> compiling catalog prewikka/locale/pl/LC_MESSAGES/prewikka.po to 
> prewikka/locale/pl/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2393: placeholders are 
> incompatible
> error: prewikka/locale/es/LC_MESSAGES/prewikka.po:2807: placeholders are 
> incompatible
> compiling catalog prewikka/locale/es/LC_MESSAGES/prewikka.po to 
> prewikka/locale/es/LC_MESSAGES/prewikka.mo
> compiling catalog prewikka/locale/fr/LC_MESSAGES/prewikka.po to 
> prewikka/locale/fr/LC_MESSAGES/prewikka.mo
> error: prewikka/locale/de/LC_MESSAGES/prewikka.po:2804: placeholders are 
> incompatible
> compiling catalog prewikka/locale/de/LC_MESSAGES/prewikka.po to 
> prewikka/locale/de/LC_MESSAGES/prewikka.mo
> 9 errors encountered.
> running build_custom
> Traceback (most recent call last):
>   File "/usr/bin/lesscpy", line 11, in 
> load_entry_point('lesscpy==0.13.0', 'console_scripts', 'lesscpy')()
>   File "/usr/lib/python3/dist-packages/lesscpy/scripts/compiler.py", line 
> 154, in run
> p.parse(filename=u, debuglevel=args.debug)
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 156, in 
> parse
> self.post_parse()
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 171, in 
> post_parse
> self.result = list(utility.flatten(out))
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/utility.py", line 28, in 
> flatten
> if isinstance(elm, collections.Iterable) and not isinstance(elm, 
> string_types):
> AttributeError: module 'collections' has no attribute 'Iterable'
> creating prewikka/htdocs/css/themes
> compiling ['themes/dark.less', 'prewikka/htdocs/css/style.less'] -> 
> prewikka/htdocs/css/themes/dark.css
> Traceback (most recent call last):
>   File "/<>/setup.py", line 218, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
> cmd_obj.run()
>   File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
> self.run_command(cmd_name)
>   File 

Bug#1009425: python-lesscpy: diff for NMU version 0.15.0+ds-0.1

[Boyuan Yang]

Control: tags 1009425 + patch
Control: tags 1009425 + pending

Dear maintainer,

I've prepared an NMU for python-lesscpy (versioned as 0.15.0+ds-0.1) and
uploaded it to DELAYED/0. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru python-lesscpy-0.13.0+ds/AUTHORS python-lesscpy-0.15.0+ds/AUTHORS
--- python-lesscpy-0.13.0+ds/AUTHORS1969-12-31 19:00:00.0 -0500
+++ python-lesscpy-0.15.0+ds/AUTHORS2019-10-08 14:40:38.0 -0400
@@ -0,0 +1,5 @@
+James Page 
+Patrick 
+Sascha Peilicke 
+Simon de Haan 
+Jóhann T Maríusson 
diff -Nru python-lesscpy-0.13.0+ds/debian/changelog python-lesscpy-
0.15.0+ds/debian/changelog
--- python-lesscpy-0.13.0+ds/debian/changelog   2019-11-12 05:07:24.0
-0500
+++ python-lesscpy-0.15.0+ds/debian/changelog   2022-08-09 21:29:18.0
-0400
@@ -1,3 +1,12 @@
+python-lesscpy (0.15.0+ds-0.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * New upstream release.
++ Fix FTBFS due to collections module. (Closes: #1009425)
+  * debian/control: Bump Standards-Version to 4.6.1.
+
+ -- Boyuan Yang   Tue, 09 Aug 2022 21:29:18 -0400
+
 python-lesscpy (0.13.0+ds-2) unstable; urgency=medium
 
   * Unnecessary postinst and prerm and add preinst for upgrade
diff -Nru python-lesscpy-0.13.0+ds/debian/control python-lesscpy-
0.15.0+ds/debian/control
--- python-lesscpy-0.13.0+ds/debian/control 2019-11-12 05:07:24.0
-0500
+++ python-lesscpy-0.15.0+ds/debian/control 2022-08-09 21:28:00.0
-0400
@@ -8,7 +8,7 @@
python3-all,
python3-ply,
python3-setuptools,
-Standards-Version: 4.4.1
+Standards-Version: 4.6.1
 Vcs-Browser: https://salsa.debian.org/totol-guest/python-lesscpy
 Vcs-Git: https://salsa.debian.org/totol-guest/python-lesscpy.git
 Homepage: https://pypi.python.org/pypi/lesscpy
diff -Nru python-lesscpy-0.13.0+ds/lesscpy/__init__.py python-lesscpy-
0.15.0+ds/lesscpy/__init__.py
--- python-lesscpy-0.13.0+ds/lesscpy/__init__.py2018-02-05
09:46:27.0 -0500
+++ python-lesscpy-0.15.0+ds/lesscpy/__init__.py2021-07-15
02:45:16.0 -0400
@@ -1,4 +1,4 @@
-__version_info__ = ('0', '13', '0')
+__version_info__ = ('0', '15', '0')
 __version__ = '.'.join(__version_info__)
 
 
@@ -18,4 +18,3 @@
 p.parse(file=file)
 f = formatter.Formatter(opt)
 return f.format(p)
-
diff -Nru python-lesscpy-0.13.0+ds/lesscpy/lessc/color.py python-lesscpy-
0.15.0+ds/lesscpy/lessc/color.py
--- python-lesscpy-0.13.0+ds/lesscpy/lessc/color.py 2017-12-28
10:17:44.0 -0500
+++ python-lesscpy-0.15.0+ds/lesscpy/lessc/color.py 2020-01-24
09:00:33.0 -0500
@@ -12,13 +12,12 @@
 
 import colorsys
 import re
-import six
+from six import string_types
 from . import utility
 from lesscpy.lib import colors
 
 
-class Color():
-
+class Color:
 def process(self, expression):
 """ Process color expression
 args:
@@ -70,10 +69,9 @@
 return self._rgbatohex(list(map(int, args)))
 except ValueError:
 if all((a for a in args
-if a[-1] == '%'
-and 100 >= int(a[:-1]) >= 0)):
-return self._rgbatohex([int(a[:-1]) * 255 / 100.0
-for a in args])
+if a[-1] == '%' and 100 >= int(a[:-1]) >= 0)):
+return self._rgbatohex(
+[int(a[:-1]) * 255 / 100.0 for a in args])
 raise ValueError('Illegal color values')
 
 def rgba(self, *args):
@@ -94,15 +92,14 @@
 return self._rgbatohex(list(map(int, args)))
 except ValueError:
 if all((a for a in args
-if a[-1] == '%'
-and 100 >= int(a[:-1]) >= 0)):
+if a[-1] == '%' and 100 >= int(a[:-1]) >= 0)):
 alpha = list(args)[3]
 if alpha[-1] == '%' and float(alpha[:-1]) == 0:
-values = self._rgbatohex_raw([int(a[:-1]) * 255 /
100.0
- for a in args])
+values = self._rgbatohex_raw(
+[int(a[:-1]) * 255 / 100.0 for a in args])
 return "rgba(%s)" % ','.join([str(a) for a in
values])
-return self._rgbatohex([int(a[:-1]) * 255 / 100.0
-for a in args])
+return self._rgbatohex(
+[int(a[:-1]) * 255 / 100.0 for a in args])
 raise ValueError('Illegal color values')
 
 def argb(self, *args):
@@ -135,16 +132,17 @@
 if fval > 1:
 rgb = [255] + rgb[1:]  # Clip invalid integer/float
values
 elif 1 >= fval >= 0:
-rgb = [fval * 256] + rgb[1:]  # Convert 0-1 to 0-255
range for _rgbatohex
+rgb 

Processed: python-lesscpy: diff for NMU version 0.15.0+ds-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1009425 + patch
Bug #1009425 [python3-lesscpy] prewikka: FTBFS: AttributeError: module 
'collections' has no attribute 'Iterable'
Added tag(s) patch.
> tags 1009425 + pending
Bug #1009425 [python3-lesscpy] prewikka: FTBFS: AttributeError: module 
'collections' has no attribute 'Iterable'
Added tag(s) pending.

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

Bug#1016848: marked as done (librecast: unknown section 'unknown')

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 18:09:37 -0700
with message-id <87wnbgzyy6.fsf@contorta>
and subject line Re: Bug#1016848: librecast: unknown section 'unknown'
has caused the Debian Bug report #1016848,
regarding librecast: unknown section 'unknown'
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.)


-- 
1016848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librecast
Version: 0.5.1-2
Severity: serious

Hi Maintainer

debian/control contains:

Section: unknown

Regards
Graham
--- End Message ---
--- Begin Message ---
Version: 0.5.1-3

On 2022-08-08, Vagrant Cascadian wrote:
> Control: tags 1016848 pending
>
> On 2022-08-08, Graham Inggs wrote:
>> debian/control contains:
>>
>> Section: unknown
>
> This was fixed in git a couple days ago:
>
>   
> https://salsa.debian.org/vagrant/librecast/-/commit/3d1f704693c1bdefc8bc440ee360de5a10932fcf

And uploaded:

librecast (0.5.1-3) unstable; urgency=medium

  * debian/control: Set default Section to "libs".

 -- Vagrant Cascadian   Tue, 09 Aug 2022 17:09:40 -0700


live well,
  vagrant


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

Processed: Re: Bug#1016927: gnome-console: Shortcuts being executed without shift being hold

[Debian Bug Tracking System]

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

> severity 1016927 serious
Bug #1016927 [gnome-console] gnome-console: Shortcuts being executed without 
shift being hold
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#919697: arcanist: file conflict with arc

[Guillem Jover]

Hi!

[ The bug has been (correctly) bumped back to serious. Sorry that I
  have not engaged about this bug in the past, but the reply to simply
  ignore policy looked rather off-putting, I just noticed the reply
  below, which seemed encouraging! :) ]

On Sat, 2019-01-26 at 11:20:13 +0100, Sylvestre Ledru wrote:
> As we shipped the previous release with this bug, we are close to
> the freeze and there is not easy fix,
> I propose that we fix this issue for the next stable release.

Could you please rename the archanist /usr/bin/arc into
/usr/bin/arcanist? Or if that's not feasible, then stop installing the
symlink in PATH, and document that users might want to add the /usr/share
/arcanist/bin/ into their own PATH? Or do both?

Renaming the binary from the arc package, which matches the package
name itself, seems unfair, as it has existed upstream and has been in
the Debian archive for way way longer, and in addition the idea of
potentially having a binary package arc with a non-arc program, and
arcanist providing an arc program seems rather confusing and just
wrong. :)

Otherwise, all these package will get removed in the coming days. So I'd
also appreciate if you could reassign these bugs to arcanist.

Thanks,
Guillem

Bug#1016614: marked as done (nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 22:04:41 +
with message-id 
and subject line Bug#1016614: fixed in nvidia-graphics-drivers 510.85.02-1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5383

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 510.85.02-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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, 09 Aug 2022 23:44:14 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 510.85.02-1
Distribution: experimental
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1012713 1016614
Changes:
 nvidia-graphics-drivers (510.85.02-1) experimental; urgency=medium
 .
   * New upstream production branch release 510.85.02 (2022-08-02).
 (Closes: #1012713, #1016614)
 * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615.
   

Bug#1012713: marked as done (nvidia-graphics-drivers: Fails to build from source: 510.73.08 missing upstream)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 22:04:41 +
with message-id 
and subject line Bug#1012713: fixed in nvidia-graphics-drivers 510.85.02-1
has caused the Debian Bug report #1012713,
regarding nvidia-graphics-drivers: Fails to build from source: 510.73.08 
missing upstream
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I am trying to build the associated flathub packages for 510.73.08 and they 
seem to be completely absent upstream
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried to build the git 510 branch from source.

   * What was the outcome of this action?
The get-orig-source command failed.

   * What outcome did you expect instead?
The upstream source should exist?

curl  
https://download.nvidia.com/XFree86/Linux-x86_64/510.73.08/NVIDIA-Linux-x86_64-510.73.08.run
 results in 404

http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;>
http://www.w3.org/1999/xhtml; xml:lang="en" lang="en">

404 - Not Found


404 - Not Found





It seems that the version 510.73.08 is completely absent upstream. The archive 
page only lists 510.73.05 from this
series. I'm not sure where this version came from, there seems to be little 
reference to it outside of debian's
ecosystem. Perhaps this was a prelude to the opensourcing somehow??

It's frustrating that this is completely unbuildable now. I'm guessing the 
adoption of the 515 branch is going to
be held up in debian-legal for some time, because of obvious reasons.

Is it perhaps that this is secretly 510.73.05 and got the wrong number somehow?

Christian

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

Kernel: Linux 5.18.1-tkg-pds (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 510.85.02-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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, 09 Aug 2022 23:44:14 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 510.85.02-1
Distribution: experimental
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1012713 1016614
Changes:
 nvidia-graphics-drivers (510.85.02-1) experimental; urgency=medium
 .
   * New upstream production branch release 510.85.02 (2022-08-02).
 (Closes: #1012713, #1016614)
 * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615.
   https://nvidia.custhelp.com/app/answers/detail/a_id/5383
 * Improved compatibility with recent Linux kernels.
 .
   [ Andreas Beckmann ]
   * Merge changes from 470.141.03-1.
   * Refresh patches.
   * Update nv-readme.ids.
   * Restrict watch file to releases from the 510.xx production branch.
Checksums-Sha1:
 d844f8d247aa351447fecb9ef2e8a13b09ebca8a 6942 
nvidia-graphics-drivers_510.85.02-1.dsc
 d86d3e3660424532af040c0028fc490b3a562748 329820599 

Bug#1016905: marked as done (freecad: fails to install when installing together with kicad)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 23:22:43 +0200
with message-id <05fed2cb57b89073fbb98e572746143f1bff7d0d.ca...@debian.org>
and subject line Re: freecad: fails to install when installing together with 
kicad
has caused the Debian Bug report #1016905,
regarding freecad: fails to install when installing together with kicad
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.)


-- 
1016905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.20+dfsg1-2
Severity: serious
X-Debbugs-Cc: jo...@debian.org

Hi,

when installing freecad together with kicad, one gets the following
error:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libfreecad-python3-0.20 : Depends: libocct-data-exchange-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
   Depends: libocct-foundation-7.5 (>= 7.5.2+dfsg1) but 
it is not installable
   Depends: libocct-modeling-algorithms-7.5 (>= 
7.5.2+dfsg1) but it is not installable
   Depends: libocct-modeling-data-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
   Depends: libocct-ocaf-7.5 (>= 7.5.2+dfsg1) but it is 
not installable
   Depends: libocct-visualization-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
E: Unable to correct problems, you have held broken packages.


The reason is a conflict between libocct-modeling-algorithms-7.6 (as
pulled in by kicad) and libocct-modeling-algorithms-7.5 (as pulled in by
freecad):

report:
 -
  coinst: freecad:amd64 (= 0.20+dfsg1-2) , kicad:amd64 (= 6.0.7+dfsg-1+b1)
  status: broken

 reasons:
  -
   conflict:
pkg1:
 package: libocct-modeling-algorithms-7.6
 version: 7.6.3+dfsg1-2
 architecture: amd64
 unsat-conflict: libocct-modeling-algorithms-7.5:amd64
pkg2:
 package: libocct-modeling-algorithms-7.5
 version: 7.5.2+dfsg1-2
 architecture: amd64
depchain2:
 -
  depchain:
   -
package: freecad
version: 0.20+dfsg1-2
architecture: all
depends: freecad-python3:amd64 (>= 0.20+dfsg1-2)
   -
package: freecad-python3
version: 0.20+dfsg1-2
architecture: amd64
depends: libfreecad-python3-0.20:amd64 (= 0.20+dfsg1-2)
   -
package: libfreecad-python3-0.20
version: 0.20+dfsg1-2
architecture: amd64
depends: libocct-modeling-algorithms-7.5:amd64 (>= 7.5.2+dfsg1)
--- End Message ---
--- Begin Message ---

This is due to the opencascade transition, which is happening now.

As differnet opencascade versions are not co-installable (#958905), packages 
using different versions of opencascade cannot be installed at the same time.
Kicad has already been recompiled against opencascadr 7.6.3, while freecad not.

Actually, the upload from today (freecad 0.20+dfsg1-4) should recompile against 
opencascade 7.6.3 as well, so
kicad and opencascade should be co-installable after next dinstall.

Closing this bug…

--
tobi 



On Tue, 09 Aug 2022 15:49:11 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> Package: freecad
> Version: 0.20+dfsg1-2
> Severity: serious
> X-Debbugs-Cc: jo...@debian.org
> 
> Hi,
> 
> when installing freecad together with kicad, one gets the following
> error:
> 
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libfreecad-python3-0.20 : Depends: libocct-data-exchange-7.5 (>= 
>7.5.2+dfsg1) but it is not installable
>    Depends: libocct-foundation-7.5 (>= 7.5.2+dfsg1) 
>but it is not installable
>    Depends: libocct-modeling-algorithms-7.5 (>= 
>7.5.2+dfsg1) but it is not installable
>    Depends: libocct-modeling-data-7.5 (>= 
>7.5.2+dfsg1) but it is not installable
>    Depends: libocct-ocaf-7.5 (>= 7.5.2+dfsg1) but it 
>is not installable
>    Depends: libocct-visualization-7.5 

Bug#1013598: marked as done (binutils-arm-none-eabi: FTBFS: dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.38.50.20220622)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 21:03:49 +
with message-id 
and subject line Bug#1013598: fixed in binutils-arm-none-eabi 16
has caused the Debian Bug report #1013598,
regarding binutils-arm-none-eabi: FTBFS: dh_auto_configure: error: invalid or 
non-existing path to the source directory: binutils-2.38.50.20220622
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.)


-- 
1013598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-arm-none-eabi
Version: 15
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 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 -Dbinutils-2.38.50.20220622 -Bbuild
>dh_update_autotools_config -O-Dbinutils-2.38.50.20220622 -O-Bbuild
>dh_autoreconf -O-Dbinutils-2.38.50.20220622 -O-Bbuild
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> tar xf /usr/src/binutils/binutils-*.tar.*
> mkdir -p debian/stamp
> cp /usr/share/doc/binutils-source/copyright debian/copyright
> touch debian/stamp/tar
> dh_auto_configure -Dbinutils-2.38.50.20220622 -Bbuild -- 
> --target=arm-none-eabi --prefix=/usr/lib --bindir=/usr/bin 
> --libdir=/usr/lib/arm-none-eabi 
> --infodir=/usr/share/doc/binutils-arm-none-eabi/info 
> --htmldir=/usr/share/doc/binutils-arm-none-eabi/html 
> --pdfdir=/usr/share/doc/binutils-arm-none-eabi/pdf --mandir=/usr/share/man 
> --disable-nls --disable-werror --enable-plugins --enable-interwork 
> --with-system-zlib "--with-pkgversion=2.38.50.20220622-1+15" 
> --enable-deterministic-archives ASFLAGS="" CFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
> CXXFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security" DFLAGS="-frelease" 
> FCFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong" FFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong" GCJFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong" 
> LDFLAGS="-Wl,-z,relro -Wl,-z,now" OBJCFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" OBJCXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" 
> dh_auto_configure: error: invalid or non-existing path to the source 
> directory: binutils-2.38.50.20220622
> make[1]: *** [debian/rules:53: override_dh_auto_configure] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/binutils-arm-none-eabi_15_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please 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: binutils-arm-none-eabi
Source-Version: 16
Done: Keith Packard 

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

Debian distribution maintenance software
pp.
Keith Packard  (supplier of updated binutils-arm-none-eabi 
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, 09 Aug 2022 12:57:54 -0700
Source: binutils-arm-none-eabi
Architecture: source
Version: 16
Distribution: unstable
Urgency: medium
Maintainer: Joaquin de Andres 

Bug#1013495: marked as done (asio: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 9 Aug 2022 21:35:48 +0200
with message-id 
and subject line Re: Bug#1013495: asio: FTBFS: dh_auto_test: error: make -j8 
check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
has caused the Debian Bug report #1013495,
regarding asio: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 
--verbose" VERBOSE=1 returned exit code 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[7]: Entering directory '/<>/src/tests'
> PASS: unit/associated_executor
> PASS: unit/associated_allocator
> PASS: unit/basic_datagram_socket
> PASS: unit/async_result
> PASS: unit/associated_cancellation_slot
> PASS: unit/awaitable
> PASS: unit/associator
> PASS: unit/basic_deadline_timer
> PASS: unit/basic_file
> PASS: unit/basic_raw_socket
> PASS: unit/basic_seq_packet_socket
> PASS: unit/basic_random_access_file
> PASS: unit/basic_readable_pipe
> PASS: unit/basic_signal_set
> PASS: unit/basic_serial_port
> PASS: unit/basic_socket
> PASS: unit/basic_socket_acceptor
> PASS: unit/basic_stream_file
> PASS: unit/basic_stream_socket
> PASS: unit/basic_waitable_timer
> PASS: unit/basic_streambuf
> PASS: unit/basic_writable_pipe
> PASS: unit/bind_cancellation_slot
> PASS: unit/buffered_read_stream
> PASS: unit/buffer
> PASS: unit/buffer_registration
> PASS: unit/buffered_write_stream
> PASS: unit/buffers_iterator
> PASS: unit/buffered_stream
> PASS: unit/cancellation_state
> PASS: unit/cancellation_signal
> PASS: unit/co_spawn
> PASS: unit/cancellation_type
> PASS: unit/completion_condition
> PASS: unit/connect_pipe
> PASS: unit/deadline_timer
> PASS: unit/defer
> PASS: unit/connect
> PASS: unit/detached
> PASS: unit/dispatch
> PASS: unit/error
> PASS: unit/execution/any_executor
> PASS: unit/execution/bulk_execute
> PASS: unit/execution/blocking_adaptation
> PASS: unit/execution/blocking
> PASS: unit/execution/connect
> PASS: unit/execution/bulk_guarantee
> PASS: unit/execution/context_as
> PASS: unit/execution/executor
> PASS: unit/execution/execute
> PASS: unit/execution/operation_state
> PASS: unit/execution/mapping
> PASS: unit/execution/outstanding_work
> PASS: unit/execution/receiver
> PASS: unit/execution/prefer_only
> PASS: unit/execution/invocable_archetype
> PASS: unit/execution/sender
> PASS: unit/execution/set_done
> PASS: unit/execution/schedule
> PASS: unit/execution/relationship
> PASS: unit/execution/scheduler
> PASS: unit/execution/set_error
> PASS: unit/execution/set_value
> PASS: unit/execution/start
> PASS: unit/execution/submit
> PASS: unit/executor
> PASS: unit/executor_work_guard
> PASS: unit/execution_context
> PASS: unit/high_resolution_timer
> PASS: unit/file_base
> PASS: unit/ip/address
> PASS: unit/ip/address_v4_iterator
> PASS: unit/ip/address_v4_range
> PASS: unit/ip/address_v4
> PASS: unit/ip/address_v6
> PASS: unit/ip/address_v6_range
> PASS: unit/ip/basic_endpoint
> PASS: unit/ip/basic_resolver
> PASS: unit/ip/address_v6_iterator
> PASS: unit/ip/basic_resolver_entry
> PASS: unit/ip/basic_resolver_iterator
> PASS: unit/ip/basic_resolver_query
> PASS: unit/ip/icmp
> PASS: unit/ip/host_name
> PASS: unit/ip/network_v6
> PASS: unit/ip/multicast
> PASS: unit/ip/network_v4
> PASS: unit/ip/resolver_query_base
> PASS: unit/ip/unicast
> PASS: unit/ip/udp
> PASS: unit/ip/tcp
> PASS: unit/ip/v6_only
> PASS: unit/is_read_buffered
> PASS: unit/is_write_buffered
> PASS: unit/local/connect_pair
> PASS: unit/local/basic_endpoint
> PASS: unit/local/datagram_protocol
> PASS: unit/local/stream_protocol
> PASS: unit/packaged_task
> PASS: unit/placeholders
> PASS: unit/posix/basic_stream_descriptor
> PASS: unit/posix/basic_descriptor
> PASS: unit/posix/descriptor_base
> PASS: unit/posix/descriptor
> PASS: unit/posix/stream_descriptor
> PASS: unit/post
> PASS: unit/random_access_file
> PASS: unit/read
> PASS: unit/read_at
> PASS: unit/read_until
> PASS: unit/recycling_allocator
> PASS: unit/redirect_error
> PASS: unit/readable_pipe
> PASS: unit/registered_buffer
> PASS: unit/serial_port
> PASS: unit/serial_port_base
> PASS: unit/signal_set
> PASS: unit/socket_base
> PASS: unit/static_thread_pool
> PASS: unit/stream_file
> PASS: unit/steady_timer
> PASS: unit/streambuf
> 

Processed: bug 1012943 is forwarded to https://github.com/herbstluftwm/herbstluftwm/issues/1512

[Debian Bug Tracking System]

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

> forwarded 1012943 https://github.com/herbstluftwm/herbstluftwm/issues/1512
Bug #1012943 [src:herbstluftwm] herbstluftwm: ftbfs with GCC-12
Set Bug forwarded-to-address to 
'https://github.com/herbstluftwm/herbstluftwm/issues/1512'.
> thanks
Stopping processing here.

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

Bug#1000946: marked as done (gcc-riscv64-unknown-elf: reproducible builds: embeds path to various binaries)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 12:22:11 -0700
with message-id <87edxpdxy4@keithp.com>
and subject line Typo'd the version number in changelog
has caused the Debian Bug report #1000946,
regarding gcc-riscv64-unknown-elf: reproducible builds: embeds path to various 
binaries
to be marked as done.

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

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


-- 
1000946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-riscv64-unknown-elf
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge shell
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org, kei...@keithp.com

The paths to various binaries are embedded which differs on a usrmerge
vs. non-usrmerge system.

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/gcc-riscv64-unknown-elf.html

  /usr/lib/gcc/riscv64-unknown-elf/8.3.0/install-tools/fixincl

  /bin/sed
  vs.
  /usr/bin/sed

  /usr/lib/gcc/riscv64-unknown-elf/8.3.0/install-tools/mkheaders

  mkinstalldirs="/bin/bash·${itoolsdir}/mkinstalldirs"
  vs.
  mkinstalldirs="/bin/sh·${itoolsdir}/mkinstalldirs"

Patch attached which passes variables to configure to use the
non-usrmerge locations, as usrmerge installations typically have
compatibility symlinks, but not vice-versa. The patch also sets
variables to ensure consistent values for bash, which can be triggered
when /bin/sh points to bash.

This patch alone does not fix all reproducibility issues (e.g. build
paths, which are only tested on unstable and experimental), but should
build reproducibly in bookworm/testing once binutils-riscv64-unknown-elf
is built with deterministic archives enabled.


Thanks for maintaining gcc-riscv64-unknown-elf!


live well,
  vagrant

p.s. more deja-vu?
From 6e8817705e2734392483bc332f1ba1df0212 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Wed, 1 Dec 2021 03:13:30 +
Subject: [PATCH] debian/rules: Pass variables to configure to make the package
 build reproducibly regardless of usrmerge.

The variables SED, SHELL, BASH and CONFIG_SHELL should all point to
their non-usrmerge locations.

https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index 86fbda13298..c54382b8e4b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -57,6 +57,10 @@ configure_flags = \
 	--with-gnu-ld \
 	--with-as=$(target_bin)as \
 	--with-ld=$(target_bin)ld \
+SED=/bin/sed \
+SHELL=/bin/sh \
+BASH=/bin/bash \
+CONFIG_SHELL=/bin/bash \
 	$(target_tools) \
 	$(build_flags) \
 	CFLAGS_FOR_TARGET='-Os -mcmodel=medany' CXXFLAGS_FOR_TARGET='-Os -mcmodel=medany'
-- 
2.30.2



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

Version: 11

I accidentally put 1000964 instead of 1000946 in changelog. 1000964 has
already been re-opened. (sorry!)

-- 
-keith


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

Bug#1013536: marked as done (python-django-extensions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" --system=custom "--test-args={interpreter} -m pytest --

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 19:20:25 +
with message-id 
and subject line Bug#1013536: fixed in python-django-extensions 3.2.0-1
has caused the Debian Bug report #1013536,
regarding python-django-extensions: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.10" --system=custom 
"--test-args={interpreter} -m pytest --cov=django_extensions 
--ds=tests.testapp.settings 
--ignore=tests/management/commands/test_create_template_tags.py 
--ignore=tests/management/commands/test_pipchecker.py 
--ignore=tests/templatetags/test_highlighting.py 
--ignore=tests/management/commands/shell_plus_tests/test_shell_plus.py tests" 
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.)


-- 
1013536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-extensions
Version: 3.1.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 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 '/<>'
> PYTHONPATH=. \
> dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest 
> --cov=django_extensions --ds=tests.testapp.settings  
> --ignore=tests/management/commands/test_create_template_tags.py 
> --ignore=tests/management/commands/test_pipchecker.py 
> --ignore=tests/templatetags/test_highlighting.py  
> --ignore=tests/management/commands/shell_plus_tests/test_shell_plus.py tests"
> I: pybuild base:239: python3.9 -m pytest --cov=django_extensions 
> --ds=tests.testapp.settings  
> --ignore=tests/management/commands/test_create_template_tags.py 
> --ignore=tests/management/commands/test_pipchecker.py 
> --ignore=tests/templatetags/test_highlighting.py  
> --ignore=tests/management/commands/shell_plus_tests/test_shell_plus.py tests
> = test session starts 
> ==
> platform linux -- Python 3.9.13, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
> Django settings: tests.testapp.settings (from command line option)
> rootdir: /<>, configfile: setup.cfg
> plugins: django-3.5.1, cov-3.0.0
> collected 459 items / 1 error / 3 skipped / 455 selected
> 
>  ERRORS 
> 
> _ ERROR collecting tests/management/commands/test_show_urls.py 
> _
> ImportError while importing test module 
> '/<>/tests/management/commands/test_show_urls.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/management/commands/test_show_urls.py:4: in 
> from django.conf.urls import url
> E   ImportError: cannot import name 'url' from 'django.conf.urls' 
> (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
> === warnings summary 
> ===
> ../../../usr/lib/python3/dist-packages/django/conf/__init__.py:206
>   /usr/lib/python3/dist-packages/django/conf/__init__.py:206: 
> RemovedInDjango50Warning: The default value of USE_TZ will change from False 
> to True in Django 5.0. Set USE_TZ to False in your project settings if you 
> want to keep the current default behavior.
> warnings.warn(
> 
> django_extensions/management/jobs.py:4
>   /<>/django_extensions/management/jobs.py:4: 
> DeprecationWarning: the imp module is deprecated in favour of importlib; see 
> the module's documentation for alternative uses
> from imp import find_module
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> 
> -- coverage: platform linux, python 3.9.13-final-0 ---
> Name  Stmts   
> Miss  Cover
> -
> django_extensions/__init__.py17   
>665%
> django_extensions/admin/__init__.py  89   
>   6131%
> django_extensions/admin/filter.py27   
>   1544%
> django_extensions/admin/widgets.py   46   
>   2937%
> django_extensions/apps.py 4   
>0   100%
> django_extensions/auth/__init__.py 

Bug#1016311: marked as done (raft: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 17:38:01 +
with message-id 
and subject line Bug#1016311: fixed in raft 0.14.0-2
has caused the Debian Bug report #1016311,
regarding raft: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 
--verbose" VERBOSE=1 returned exit code 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> PASS: test/integration/core
> PASS: test/fuzzy/core
> PASS: test/unit/uv
> FAIL: test/integration/uv
> PASS: test/unit/core
> ===
>raft 0.14.0: ./test-suite.log
> ===
> 
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test/integration/uv
> =
> 
> Running test suite with seed 0x0c818c79...
> init/dirTooLong [ OK] [ 
> 0.0876 / 0.0838 CPU ]
> init/oom
>   heap-fault-delay=1, heap-fault-repeat=1   [ OK] [ 
> 0.00513923 / 0.00012712 CPU ]
> init/dirDoesNotExist[ OK] [ 
> 0.2371 / 0.2346 CPU ]
> init/dirNotAccessible   [ OK] [ 
> 0.2515 / 0.2500 CPU ]
> init/noSpace
>   dir-fs=tmpfs  [ SKIP  ]
> init/metadataOneTooShort[ OK] [ 
> 0.05285602 / 0.00041775 CPU ]
> init/metadataOneBadFormat   [ OK] [ 
> 0.06739239 / 0.00038578 CPU ]
> init/metadataOneBadVersion  [ OK] [ 
> 0.05536759 / 0.00035030 CPU ]
> init/metadataOneAndTwoSameVersion   [ OK] [ 
> 0.05529730 / 0.00042951 CPU ]
> append/first[ OK] [ 
> 0.12416089 / 0.00199877 CPU ]
> append/prepareSegments  [ OK] [ 
> 0.00502013 / 0.00110471 CPU ]
> append/finalizeSegment  [ OK] [ 
> 0.04916033 / 0.00159129 CPU ]
> append/firstBig [ OK] [ 
> 0.11269950 / 0.00194452 CPU ]
> append/secondBig[ OK] [ 
> 0.04403969 / 0.00140343 CPU ]
> append/severalBig   [ OK] [ 
> 0.15714019 / 0.00377408 CPU ]
> append/fitBlock [ OK] [ 
> 0.09603802 / 0.00163026 CPU ]
> append/matchBlock   [ OK] [ 
> 0.13236936 / 0.00165099 CPU ]
> append/exceedBlock  [ OK] [ 
> 0.20842068 / 0.00181559 CPU ]
> append/batch[ OK] [ 
> 0.00427482 / 0.00098080 CPU ]
> append/wait [ OK] [ 
> 0.00515443 / 0.00102270 CPU ]
> append/resizeArena  [ OK] [ 
> 0.08037526 / 0.00165256 CPU ]
> append/truncate [ SKIP  ]
> append/truncateClosing  [ OK] [ 
> 0.10790485 / 0.00173663 CPU ]
> append/prepareClosing   [ OK] [ 
> 0.04796955 / 0.00131057 CPU ]
> append/counter  [ OK] [ 
> 0.12402830 / 0.00369946 CPU ]
> append/cancel   [ OK] [ 
> 0.00153553 / 0.00075515 CPU ]
> append/noSpaceUponPrepareCurrent
>   dir-fs=tmpfs  [ SKIP  ]
> append/noSpaceUponPrepareSpare  
>   dir-fs=tmpfs  [ SKIP  ]
> append/noSpaceUponWrite 
>   dir-fs=tmpfs  [ SKIP  ]
> append/noSpaceResolved  
>   dir-fs=tmpfs   

Bug#1014875: marked as done (freecad: FTBFS on armel and armhf: error: ‘GL_PROJECTION’ was not declared in this scope;)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 17:06:21 +
with message-id 
and subject line Bug#1014875: fixed in freecad 0.20+dfsg1-4
has caused the Debian Bug report #1014875,
regarding freecad: FTBFS on armel and armhf: error: ‘GL_PROJECTION’ was not 
declared in this scope;
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.)


-- 
1014875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.20+dfsg1-2
Severity: serious
Tags: ftbfs
Justification: FTBFS

Freecad FTBFS on the buildds,
see https://buildd.debian.org/status/package.php?p=freecad

build logs indicate this error:

cd /<>/debian/build-py3/src/Mod/Fem/App && /usr/bin/c++ 
-DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK 
-DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK 
-DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK 
-DFC_USE_VTK -DFem_EXPORTS -DH5_BUILT_AS_DYNAMIC_LIB -DHAVE_CONFIG_H 
-DHAVE_LIMITS_H -DMPICH_SKIP_MPICXX -DMPI_NO_CPPBIND -DOMPI_SKIP_MPICXX 
-DQT_CORE_LIB -DQT_NO_DEBUG -DQT_XML_LIB -D_FILE_OFFSET_BITS=64 -D_MPICC_H 
-Dkiss_fft_scalar=double 
-I/<>/debian/build-py3/src/Mod/Fem/App/Fem_autogen/include 
-I/<>/debian/build-py3 -I/<>/debian/build-py3/src 
-I/<>/src -I/<>/debian/build-py3/src/Mod/Fem/App 
-I/usr/include/opencascade -I/<>/src/3rdParty/salomesmesh/inc 
-isystem /usr/include/arm-linux-gnueabihf/qt5 -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem 
/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtXml -isystem /usr/include/vtk-9.1 
-isystem /usr/include/jsoncpp -isystem 
/usr/lib/arm-linux-gnueabihf/openmpi/include -isystem 
/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -isystem 
/usr/include/hdf5/serial -isystem /usr/include/freetype2 -Wall -Wextra 
-Wno-write-strings -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -fpermissive -I/usr/include/python3.10 -flto 
-Wno-overloaded-virtual -O2 -g -DNDEBUG -fPIC -pthread 
-I/usr/include/hdf5/openmpi -I/usr/lib/arm-linux-gnueabihf/openmpi/include 
-I/usr/lib/arm-linux-gnueabihf/openmpi/include/openmpi -Wno-pedantic -fPIC 
-fopenmp -std=gnu++17 -MD -MT 
src/Mod/Fem/App/CMakeFiles/Fem.dir/FemSetElementsObject.cpp.o -MF 
CMakeFiles/Fem.dir/FemSetElementsObject.cpp.o.d -o 
CMakeFiles/Fem.dir/FemSetElementsObject.cpp.o -c 
/<>/src/Mod/Fem/App/FemSetElementsObject.cpp
/<>/src/Gui/Quarter/QuarterWidget.cpp: In member function ‘virtual 
void SIM::Coin3D::Quarter::QuarterWidget::paintEvent(QPaintEvent*)’:
/<>/src/Gui/Quarter/QuarterWidget.cpp:869:18: error: 
‘GL_PROJECTION’ was not declared in this scope; did you mean ‘GL_LOCATION’?
  869 | glMatrixMode(GL_PROJECTION);
  |  ^
  |  GL_LOCATION
/<>/src/Gui/Quarter/QuarterWidget.cpp:869:5: error: ‘glMatrixMode’ 
was not declared in this scope
  869 | glMatrixMode(GL_PROJECTION);
  | ^~~~
/<>/src/Gui/Quarter/QuarterWidget.cpp:910:5: error: ‘glPushAttrib’ 
was not declared in this scope
  910 | glPushAttrib(GL_MULTISAMPLE_BIT_EXT);
  | ^~~~
/<>/src/Gui/Quarter/QuarterWidget.cpp:912:5: error: ‘glPopAttrib’ 
was not declared in this scope
  912 | glPopAttrib();
  | ^~~

-- 
tobi


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (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 freecad depends on:
ii  freecad-python3  0.20+dfsg1-2

Versions of packages freecad recommends:
ii  calculix-ccx  2.19-1
ii  graphviz  2.42.2-7

Versions of packages freecad suggests:
pn  povray  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: freecad
Source-Version: 0.20+dfsg1-4
Done: Tobias Frost 

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

Bug#1016750: Heap exhaustion problem with SBCL 2.2.6 on armel, armhf

[Sean Whitton]

Hello,

When I updated SBCL in Debian from 2.2.3 to 2.2.6, our ci infrastructure
detected that the test suite for the cl-ironclad package consistently
runs out of memory on armhf and armel.  This didn't happen before.

https://ci.debian.net/packages/c/cl-ironclad/testing/armhf/
https://ci.debian.net/packages/c/cl-ironclad/testing/armel/

Based on your understanding of the changes between SBCL 2.2.3 and 2.2.6,
does it seem likely that this is an SBCL bug, or rather that changes in
SBCL have uncovered a bug or limitation in the ironclad test suite,
e.g. that it tries to use more memory than a 32-bit address space can
accommodate?

Also asked about here: .

Would be grateful for any input.  Thanks.

-- 
Sean Whitton

Processed: bug 1016750 is forwarded to https://github.com/sharplispers/ironclad/issues/53

[Debian Bug Tracking System]

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

> forwarded 1016750 https://github.com/sharplispers/ironclad/issues/53
Bug #1016750 [src:sbcl, src:cl-ironclad] sbcl breaks cl-ironclad autopkgtest on 
armhf: Heap exhausted, game over.
Set Bug forwarded-to-address to 
'https://github.com/sharplispers/ironclad/issues/53'.
> thanks
Stopping processing here.

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

Processed: tagging 1014875

[Debian Bug Tracking System]

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

> tags 1014875 + pending
Bug #1014875 [freecad] freecad: FTBFS on armel and armhf: error: 
‘GL_PROJECTION’ was not declared in this scope;
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1016750: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.

[Sean Whitton]

Hello,

On Tue 09 Aug 2022 at 07:46AM +02, Paul Gevers wrote:

> Hi Sean,
>
> On 09-08-2022 05:08, Sean Whitton wrote:
>> It looks like Lisp just ran out of memory.
>
> Yes, but it does so systematically.
>
>> Indeed, I can't see this
>> failure on debci.debian.org at present,
>
> Huh? Did you check https://ci.debian.net/packages/c/cl-ironclad/testing/armhf/
> or https://ci.debian.net/packages/c/cl-ironclad/testing/armel/ You'll see
> there that cl-ironclad was retried with sbcl about 11 + 10 times and every
> time it failed (and never succeeded).
>
>> which makes sense if it's a
>> random OOM problem on weaker architectures like armhf -- so, not the
>> fault of the new sbcl upload.
>
> This isn't random. And, our armhf box has 255 GB of RAM (and armel VM has 26
> GB), so running out of memory isn't likely. What can happen is that threads
> use too much resources for the address space, but that's something under
> control of the packages in question if I'm correct (but please correct me if I
> misunderstand). I'm not saying it's (easily) fixable, just that it
> systematically runs out of reachable memory during the particular test.

Right, it's not random.  I was looking at the page for unstable.

I first looked at  and
the failure doesn't show up there -- do you know what that would be?
Then I clicked on unstable but not testing, it would seem.

I'll write to upstream about this.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1016499: marked as done (cctbx: autopkgtest failure: Please run this program in an empty directory.)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 16:04:19 +
with message-id 
and subject line Bug#1016499: fixed in cctbx 2021.12+ds1-8
has caused the Debian Bug report #1016499,
regarding cctbx: autopkgtest failure: Please run this program in an empty 
directory.
to be marked as done.

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

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


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

Source: cctbx
Version: 2021.12+ds1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package cctbx, 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=cctbx

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cctbx/23732580/log.gz

Testing with python3.10:
Sorry: Please run this program in an empty directory.
autopkgtest [21:14:13]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cctbx
Source-Version: 2021.12+ds1-8
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated cctbx 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, 09 Aug 2022 17:44:07 +0200
Source: cctbx
Architecture: source
Version: 2021.12+ds1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1016324 1016499
Changes:
 cctbx (2021.12+ds1-8) unstable; urgency=medium
 .
   * More modules activated
 - annlib_adaptbx
 - ccp4io
 - ccp4io_adaptbx
 - fable
 - mmtbx
   * Added missing Python extensions
 - iotbx_cif_ext
 - iotbx_mtz_ext
   * d/t/control: start autopkgtest from an empty directory
   * d/rules: activated --enable_cxx11
   * d/rules: install libtbx_env under /usr/lib/cctbx/pythonX.Y
   * Bug fix: "FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess
 returned exit status 2", thanks to Lucas Nussbaum (Closes: #1016324).
   * Bug fix: "autopkgtest failure: Please run this program in an empty
 directory.", thanks to Paul Gevers (Closes: #1016499).
Checksums-Sha1:
 334b9270565fa71cf1ac0aa5f6061d50119725c3 3038 cctbx_2021.12+ds1-8.dsc
 ce7f4e65ab94289db5b879ebaf46defc96bd244c 269488 
cctbx_2021.12+ds1-8.debian.tar.xz
Checksums-Sha256:
 13f2f5b52efd34c086ae3b3fd76a24951d3c26044e63fdaffca622fcad59c15c 3038 
cctbx_2021.12+ds1-8.dsc
 bdae4cb2674776d7593e21add4942254d372c9bdb30425b5f7ad22b81ebbc767 269488 
cctbx_2021.12+ds1-8.debian.tar.xz
Files:
 b87f3c7cfe5409974b8a502784dbe6bf 3038 science optional cctbx_2021.12+ds1-8.dsc
 95595dd1520b15afc07139eb8b241b6f 269488 science optional 
cctbx_2021.12+ds1-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmLygd8RHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALv8Ow/+Imp4NHwO5iBg8WH0SA8OR42kqh62+hyn
QtxUurGiTJBVR7QRCrN/z4jyWTK3piPlGl2OSFyz2y9tP8MgAxkbJ2z6WOWwVO8g
kvSFVyRdXlrY6pN5mt5T8eDAjwzSxDqFSw3aovmETWxhW3l9VZ5eO7iYvE20VvYI
+1Y6m8z/oEjsRmsTZkHrSHLl+3y+8QAkhwQtMWDTuBDv9NI625WoQYAGbbkVn57o
ewxdc+jjvLwbVEVcGUbTYqpDY0qQHPIC2Y/VljYzkaxKkf5HA10+8sns5WX04b5C
kFEjFGh10y+vq472McQNWGo1tlqxs5bqw8D44tiQiqOV0+xwigIIAp6rl5rkWaTm
e3+oP0X7qnEE9Lm58VrJROlMwd39ELOB/aVlWlYOsLjmjzW++ZVNYU80Kc7z8D9u
gzmAoIpgX3enfZhw9ovftZrTSNzyCzekeYeX5lzuj52YlDh+IQuBIpRiioDy11XH
apmr48A+Abj/BUwXb3GctxYSFaVmqhxHrWCyM1pbaIepmJxoux4zrcP+tJjQkCYU
H2X9SQyrCw3/6SSQuECfpNzy0mbzl+1N1Ly9xJxaaQgT1DWm5LGYQT2bhX3sxR0w
01q+m6+TWdPFXX5s/7J2Smoe8y078dvbpOad/C09SoZ/0CYTONXtp8TE0vUjE+YA
7izkia/DOnA=
=x88V
-END PGP SIGNATURE End Message ---

Bug#1016324: marked as done (cctbx: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 16:04:19 +
with message-id 
and subject line Bug#1016324: fixed in cctbx 2021.12+ds1-8
has caused the Debian Bug report #1016324,
regarding cctbx: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

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

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


-- 
1016324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cctbx
Version: 2021.12+ds1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 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 '/<>'
> cp -f debian/setup.py setup.py
> dh_auto_clean
>   install -d 
> /<>/cctbx-2021.12\+ds1/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.10
> I: pybuild base:239: python3.10 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.10/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
>   rm -rf .pybuild/
>   find . -name \*.pyc -exec rm {} \;
> find . -name __pycache__ -type d -exec rm -rf {} \;
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>   rm -f debian/debhelper-build-stamp
>   rm -rf debian/.debhelper/
>   rm -f -- debian/libcctbx0.substvars debian/libcctbx-dev.substvars 
> debian/python3-cctbx.substvars debian/files
>   rm -fr -- debian/libcctbx0/ debian/tmp/ debian/libcctbx-dev/ 
> debian/python3-cctbx/
>   find .  \( \( \
>   \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
> .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
> -type f -a \
>   \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
>-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
>-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
>-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
>   \) -exec rm -f {} + \) -o \
>   \( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
> \)
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building cctbx using existing 
> ./cctbx_2021.12+ds1.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file dox/Doxyfile.orig, use 
> --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  cctbx-2021.12+ds1/setup.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/cctbx_2021.12+ds1-7.diff.gtdz0R
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2022-07-29T09:09:11Z


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/cctbx_2021.12+ds1-7_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results

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

If you reassign this bug to another package, please 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: cctbx
Source-Version: 2021.12+ds1-8
Done: Picca Frédéric-Emmanuel 

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

Bug#938351: marked as done (renpy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 16:00:19 +
with message-id 
and subject line Bug#938351: fixed in renpy 8.0.1+dfsg-1
has caused the Debian Bug report #938351,
regarding renpy: Python2 removal in sid/bullseye
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.)


-- 
938351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:renpy
Version: 7.3.2+dfsg-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:renpy

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: renpy
Source-Version: 8.0.1+dfsg-1
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated renpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 08 Aug 2022 13:48:45 +0200
Source: renpy
Binary: python3-renpy python3-renpy-dbgsym renpy renpy-demo renpy-doc 
renpy-thequestion
Architecture: source amd64 all
Version: 8.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 python3-renpy - framework for developing visual-novel type games - Python 
module
 renpy  - framework for developing visual-novel type games
 renpy-demo - framework for developing visual-novel type games - demo
 renpy-doc  - framework for developing visual-novel type games - doc
 renpy-thequestion - simple and complete Ren'Py game
Closes: 938351 1006540
Changes:
 renpy (8.0.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 8.0.1+dfsg.
 * Renpy supports Python 3 now. (Closes: #1006540, #938351)
   * Remove get-orig-source target.
   * Rename python-renpy binary package to python3-renpy and also remove
 

Bug#1006540: marked as done (renpy: Move package to experimental while porting is still in progress)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 16:00:20 +
with message-id 
and subject line Bug#1006540: fixed in renpy 8.0.1+dfsg-1
has caused the Debian Bug report #1006540,
regarding renpy: Move package to experimental while porting is still in progress
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.)


-- 
1006540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: renpy
Version: 7.3.5+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: onit...@gmail.com

Dear Maintainer,

Please consider moving the Debian Ren'Py package from sid to experimental.

It is currently in an unusable state, because the Python 3 porting process is
still ongoing.
It doesn't make any sense to have it in testing right now, and unstable is
probably not ideal either.

FWIW, the package currently doesn't install properly:

--- snip ---

Setting up renpy (7.3.5+dfsg-2) ...
  File "/usr/share/games/renpy/launcher/game/gui7/code.py", line 283
l = re.sub(ur'_\((\".*?\")\)', replace, l)
 ^
SyntaxError: invalid syntax

  File "/usr/share/games/renpy/launcher/game/pefile.py", line 88
IMAGE_ORDINAL_FLAG  = 0x8000L
^
SyntaxError: invalid syntax

--- snip, similar errors follow ---

According to [1], there are preliminary Ren'Py 8 releases with Python 3
support. It would be great to have packages built from the upstream nightlies
[2], so people can start testing them in Debian.

Thank you!

[1] https://github.com/renpy/renpy/issues/2003#issuecomment-1016741906
[2] https://nightly.renpy.org/current-8/index.html


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

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

Versions of packages renpy depends on:
ii  fonts-dejavu-core 2.37-2
ii  fonts-motoya-l-cedar  1.01-5
ii  fonts-nanum   20200506-1
ii  fonts-roboto-hinted   2:0~20170802-3
ii  python-renpy  7.3.5+dfsg-2
ii  python3   3.9.8-1
ii  python3-pygame-sdl2   7.4.10-1+b1

Versions of packages renpy recommends:
ii  python-tk2.7.18-1
ii  python2 [python-ctypes]  2.7.18-3
ii  zenity   3.41.0-2

renpy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: renpy
Source-Version: 8.0.1+dfsg-1
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated renpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 08 Aug 2022 13:48:45 +0200
Source: renpy
Binary: python3-renpy python3-renpy-dbgsym renpy renpy-demo renpy-doc 
renpy-thequestion
Architecture: source amd64 all
Version: 8.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 python3-renpy - framework for developing visual-novel type games - Python 
module
 renpy  - framework for developing visual-novel type games
 renpy-demo - framework for developing visual-novel type games - demo
 renpy-doc  - framework for developing visual-novel type games - doc
 renpy-thequestion - simple and complete Ren'Py game
Closes: 938351 1006540
Changes:
 renpy (8.0.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 8.0.1+dfsg.
 * Renpy supports Python 3 now. (Closes: #1006540, #938351)
   * Remove get-orig-source target.
   * Rename python-renpy binary package to python3-renpy and also remove
 python-ctypes 

Bug#1015912: marked as done (mpi4py FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 14:49:40 +
with message-id 
and subject line Bug#1015912: fixed in mpi4py 3.1.3-3
has caused the Debian Bug report #1015912,
regarding mpi4py FTBFS on IPV6-only buildds
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=mpi4py=amd64=3.1.3-2%2Bb1=1658589239=0

...
==
ERROR: testJoin (test_dynproc.TestDPM)
--
Traceback (most recent call last):
  File "/<>/test/test_dynproc.py", line 175, in testJoin
server.bind((host, 0))
socket.gaierror: [Errno -5] No address associated with hostname

--
Ran 547 tests in 17.493s

FAILED (errors=1, skipped=10)
--
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--
make[1]: *** [debian/rules:91: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: mpi4py
Source-Version: 3.1.3-3
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mpi4py 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, 09 Aug 2022 15:18:47 +0200
Source: mpi4py
Architecture: source
Version: 3.1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1015912
Changes:
 mpi4py (3.1.3-3) unstable; urgency=medium
 .
   * Team upload.
   * debian patch test_ipv6.patch tests available internet sockets in
 order to use IPv4 or IPv6 in test_dynproc.TestDPM.testJoin.
 Select IPv4 if available, else IPv6, UNIX or the first available
 (undocumented) socket family. Closes: #1015912.
   * Standards-Version: 4.6.1
Checksums-Sha1:
 fc879db8bedc7c2273768345e0a06c14c752e08e 2411 mpi4py_3.1.3-3.dsc
 0b392ee58ec0ecb1793e742af3b7c958399b8443 12668 mpi4py_3.1.3-3.debian.tar.xz
Checksums-Sha256:
 430406610a3a656b394cd3fef9e8986abdf593f399d0646600e848284f7ed7fc 2411 
mpi4py_3.1.3-3.dsc
 2403e1c1491b286e2db25a2107ce4b78b9aabfa0e461c529c418c85e6bb2a10f 12668 
mpi4py_3.1.3-3.debian.tar.xz
Files:
 040549ca9d65ec15d8f16340588ccbee 2411 python optional mpi4py_3.1.3-3.dsc
 1fa10218e0f6aaac47cec36bb626eb62 12668 python optional 
mpi4py_3.1.3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmLyZyAACgkQVz7x5L1a
AfpbqA/+I9C8lr2LRC1HFPyGRCN6a1HmG7gjmqWN4g7js3Lge41i5/B9IUIrGfjl
HJOeQOvq+yJPHoK+NaJD39W7l0yOFn1yfskVgMO52JCOYqXJ1qnAfwINNgz8TGd9
rRtGgQ5Rs6jMwZu1wm80eA7YabO6vCxaRoopPb8xc3LU9goO8e/lfV8QjrsD5e4v
kPfrtfO0UZdUT76QEGViQG1kJaxIQF9jDhYr+dz2K210TusE8hKvLf+5AMCWJoz3
QAP8s37dwrCKrS7a2v1CNap/lwz3P8dOi6118WCYfHmuOsRmUHcfUTqY3CeL9wqc
hBLb96rN2e7kdLGOgClfyStUF19nuPA5+afZpQVPNqN/B90X1tmBFsYOnoFS8BKm
V4wJE4xyeyo/yZFIHiQQd77O5MaPgXQ3rL6NJ39TUM2f8qVxj/NEXWMaeU8GDY//
FFK36IIQgrXD1vyskdE0ZRFgu0qZfz6U7tI5iHBZcaAC0ZqqrMlcWjCDJoZb+VAh
o0ZmZIkFxPt+u0VOSJ0ziv/eKWxwbv36KAH4Pvt8IEzRfE1TzPE1PNjltakwVhJW
OyghfZ2PmaVuIxDrNy0IbuhkoG2fINkJhUWkIhewvS9yXH5nzr3o5V6GQqvqYlCT
isS3s6wbIyPxxCLqpqK6TeqAulSVAz4gF7CdyYbQ4Qqya5V/wXM=
=8Oh/
-END PGP SIGNATURE End Message ---

Bug#1015912: marked as pending in mpi4py

[Drew Parsons]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/science-team/mpi4py/-/commit/81ce3cc8199dc2ed2d5f193d7111915993b5e170


add debian patch test_ipv6.patch

tests available internet sockets in order to use IPv4 or IPv6 in
test_dynproc.TestDPM.testJoin, whichever is available first.

Closes: #1015912.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1015912

Processed: Bug#1015912 marked as pending in mpi4py

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1015912 [src:mpi4py] mpi4py FTBFS on IPV6-only buildds
Added tag(s) pending.

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

Bug#1014964:

[Andreas Hasenack]

Hi,

we hit this bug in Ubuntu as well, and I created a salsa PR for it:

https://salsa.debian.org/science-team/netgen/-/merge_requests/12

Bug#1008420: marked as done (editorconfig-core: FTBFS: error: Could not create output directory /<>/build/doc/man)

[Debian Bug Tracking System]

Your message dated Tue, 9 Aug 2022 09:58:26 -0400
with message-id 

and subject line Re: editorconfig-core: FTBFS: error: Could not create output 
directory /<>/build/doc/man
has caused the Debian Bug report #1008420,
regarding editorconfig-core: FTBFS: error: Could not create output directory 
/<>/build/doc/man
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.)


-- 
1008420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: editorconfig-core
Version: 0.12.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/build'
> [  5%] Building C object 
> src/lib/CMakeFiles/editorconfig_shared.dir/ec_glob.c.o
> [ 11%] Building C object 
> src/lib/CMakeFiles/editorconfig_shared.dir/editorconfig.c.o
> [ 17%] Building C object 
> src/lib/CMakeFiles/editorconfig_shared.dir/editorconfig_handle.c.o
> [ 29%] Building C object src/lib/CMakeFiles/editorconfig_shared.dir/ini.c.o
> [ 29%] Generating html/index.html
> [ 35%] Building C object 
> src/lib/CMakeFiles/editorconfig_static.dir/ec_glob.c.o
> [ 41%] Building C object 
> src/lib/CMakeFiles/editorconfig_static.dir/editorconfig.c.o
> [ 47%] Generating man/man1/editorconfig.1
> cd /<>/build/src/lib && /usr/bin/cc 
> -Deditorconfig_shared_EXPORTS -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_shared.dir/ec_glob.c.o -MF 
> CMakeFiles/editorconfig_shared.dir/ec_glob.c.o.d -o 
> CMakeFiles/editorconfig_shared.dir/ec_glob.c.o -c 
> /<>/src/lib/ec_glob.c
> cd /<>/build/src/lib && /usr/bin/cc 
> -Deditorconfig_shared_EXPORTS -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_shared.dir/editorconfig.c.o -MF 
> CMakeFiles/editorconfig_shared.dir/editorconfig.c.o.d -o 
> CMakeFiles/editorconfig_shared.dir/editorconfig.c.o -c 
> /<>/src/lib/editorconfig.c
> cd /<>/doc && /usr/bin/doxygen 
> /<>/build/doc/Doxyfile
> cd /<>/build/src/lib && /usr/bin/cc 
> -Deditorconfig_shared_EXPORTS -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_shared.dir/editorconfig_handle.c.o -MF 
> CMakeFiles/editorconfig_shared.dir/editorconfig_handle.c.o.d -o 
> CMakeFiles/editorconfig_shared.dir/editorconfig_handle.c.o -c 
> /<>/src/lib/editorconfig_handle.c
> cd /<>/build/src/lib && /usr/bin/cc  -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_static.dir/ec_glob.c.o -MF 
> CMakeFiles/editorconfig_static.dir/ec_glob.c.o.d -o 
> CMakeFiles/editorconfig_static.dir/ec_glob.c.o -c 
> /<>/src/lib/ec_glob.c
> cd /<>/build/src/lib && /usr/bin/cc 
> -Deditorconfig_shared_EXPORTS -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_shared.dir/ini.c.o -MF 
> CMakeFiles/editorconfig_shared.dir/ini.c.o.d -o 
> CMakeFiles/editorconfig_shared.dir/ini.c.o -c /<>/src/lib/ini.c
> cd /<>/doc && /usr/bin/doxygen 
> /<>/build/doc/Doxyfile-1
> cd /<>/build/src/lib && /usr/bin/cc  -I/<>/include 
> -I/<>/build/src/auto -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -funsigned-char -MD -MT 
> src/lib/CMakeFiles/editorconfig_static.dir/editorconfig.c.o -MF 
> CMakeFiles/editorconfig_static.dir/editorconfig.c.o.d -o 
> CMakeFiles/editorconfig_static.dir/editorconfig.c.o -c 
> /<>/src/lib/editorconfig.c
> warning: Tag 'TCL_SUBST' at line 237 of file 
> '/<>/build/doc/Doxyfile-1' has become obsolete.
>  To avoid this warning please remove this line from your 
> configuration file or upgrade it using "doxygen -u"
> warning: Tag 'TCL_SUBST' at line 237 of file 

Bug#1016905: freecad: fails to install when installing together with kicad

[Johannes Schauer Marin Rodrigues]

Package: freecad
Version: 0.20+dfsg1-2
Severity: serious
X-Debbugs-Cc: jo...@debian.org

Hi,

when installing freecad together with kicad, one gets the following
error:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libfreecad-python3-0.20 : Depends: libocct-data-exchange-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
   Depends: libocct-foundation-7.5 (>= 7.5.2+dfsg1) but 
it is not installable
   Depends: libocct-modeling-algorithms-7.5 (>= 
7.5.2+dfsg1) but it is not installable
   Depends: libocct-modeling-data-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
   Depends: libocct-ocaf-7.5 (>= 7.5.2+dfsg1) but it is 
not installable
   Depends: libocct-visualization-7.5 (>= 7.5.2+dfsg1) 
but it is not installable
E: Unable to correct problems, you have held broken packages.


The reason is a conflict between libocct-modeling-algorithms-7.6 (as
pulled in by kicad) and libocct-modeling-algorithms-7.5 (as pulled in by
freecad):

report:
 -
  coinst: freecad:amd64 (= 0.20+dfsg1-2) , kicad:amd64 (= 6.0.7+dfsg-1+b1)
  status: broken

 reasons:
  -
   conflict:
pkg1:
 package: libocct-modeling-algorithms-7.6
 version: 7.6.3+dfsg1-2
 architecture: amd64
 unsat-conflict: libocct-modeling-algorithms-7.5:amd64
pkg2:
 package: libocct-modeling-algorithms-7.5
 version: 7.5.2+dfsg1-2
 architecture: amd64
depchain2:
 -
  depchain:
   -
package: freecad
version: 0.20+dfsg1-2
architecture: all
depends: freecad-python3:amd64 (>= 0.20+dfsg1-2)
   -
package: freecad-python3
version: 0.20+dfsg1-2
architecture: amd64
depends: libfreecad-python3-0.20:amd64 (= 0.20+dfsg1-2)
   -
package: libfreecad-python3-0.20
version: 0.20+dfsg1-2
architecture: amd64
depends: libocct-modeling-algorithms-7.5:amd64 (>= 7.5.2+dfsg1)

Processed: Re: Bug#1016821: libspf2: FTBFS with glibc 2.34

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1016821 [src:libspf2] libspf2: FTBFS with glibc 2.34
Added tag(s) patch.

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

Bug#1016821: libspf2: FTBFS with glibc 2.34

[Aurelien Jarno]

control: tag -1 + patch

Hi,

On 2022-08-08 01:34, Sebastian Ramacher wrote:
> Source: libspf2
> Version: 1.2.10-7.1
> Severity: serious
> Tags: ftbfs sid bookworm
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=libspf2=arm64=1.2.10-7.1%2Bb2=1659915050=0
> 
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall  -Wl,-z,relro 
> -Wl,--version-script=/<>/debian/libspf2.ver -o spfquery 
> spfquery.o ../../src/libspf2/libspf2.la -lpthread -lnsl -lresolv 
> libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
> -Wl,relro -Wl,--version-script=/<>/debian/libspf2.ver -o 
> .libs/spfquery spfquery.o  ../../src/libspf2/.libs/libspf2.so -lpthread -lnsl 
> -lresolv
> /usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
> `__dn_expand'
> /usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
> `__dn_skipname'

It appears that these two symbols have been renamed in glibc 2.34 when
moved from libresolv to libc. Quoting the glibc NEWS file:

| * Various symbols previously defined in libresolv have been moved to libc
|   in order to prepare for libresolv moving entirely into libc (see earlier
|   entry for merging libraries into libc).  The symbols __dn_comp,
|   __dn_expand, __dn_skipname, __res_dnok, __res_hnok, __res_mailok,
|   __res_mkquery, __res_nmkquery, __res_nquery, __res_nquerydomain,
|   __res_nsearch, __res_nsend, __res_ownok, __res_query, __res_querydomain,
|   __res_search, __res_send formerly in libresolv have been renamed and no
|   longer have a __ prefix.  They are now available in libc.

libspf2 is using libreplace internally to provide "replacements in case
the OS does not have native libraries that contain (working) copies.".
In that case it takes care to rename dn_expand into __dn_expand and
dn_skipname into __dn_skipname. It appears that with the changes done in
glibc 2.34, libspf2 does not need to use libreplace anymore. Therefore
the following patch from Ubuntu fixes the issue:

https://patches.ubuntu.com/libs/libspf2/libspf2_1.2.10-7.1ubuntu1.patch

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1011165: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found

[Markus Koschany]

Hello,

I have pushed a new branch which includes version 13.9.1.

https://salsa.debian.org/debian/mediathekview/-/tree/experimental

As you can see I have started from scratch because this is basically a new
package now. In order to complete this upgrade we need at least 

an upgrade of okhttp to version 4.x

https://tracker.debian.org/pkg/libokhttp-java

an upgrade of okio to 3.x

https://tracker.debian.org/pkg/okio

tilesfx

a new package eu.hansolo tilesfx

https://github.com/HanSolo/tilesfx

a new package glazedlists

https://github.com/glazedlists/glazedlists

We could omit flatlaf because that seems to be only relevant for Windows


Those are the major issues we have to fix in order to package a new upstream
release of mediathekview. And we also need to fix kotlin in unstable. If
someone wants to help, that's our todo list.

Regards,

Markus 


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

Bug#1014488: marked as pending in scapy

[Neil Williams]

Control: tag -1 pending

Hello,

Bug #1014488 in scapy 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/pkg-security-team/scapy/-/commit/59a4c0e2ed8c24cf5a3d4412cecdd5086a5b0395


Add can-utils package to autopkgtest dependencies. (Closes: #1014488)

Add basic Python autopkgtest.
Upstream development tests may need to be removed as being too intrusive
for autopkgtest - retain in Salsa CI.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014488

Processed: Bug#1014488 marked as pending in scapy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014488 [src:scapy] scapy: flaky autopkgtest: No such file or directory: 
'isotpsend'
Added tag(s) pending.

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

Bug#1016898: dolfin needs a rebuild against glibc 2.34

[Aurelien Jarno]

On 2022-08-09 13:21, Aurelien Jarno wrote:
> Source: dolfin
> Version: 2019.2.0~git20220407.d29e24d-5
> Severity: serious

FYI, I filled this bug with severity serious as it currently makes this
package uninstallable in sid, given breaks have been added to libc6-dev
against the affected version of libdolfin-dev-common.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1016898: dolfin needs a rebuild against glibc 2.34

[Aurelien Jarno]

Source: dolfin
Version: 2019.2.0~git20220407.d29e24d-5
Severity: serious

Dear maintainer,

glibc 2.34 has merged a few libraries (libpthread, libdl, libutil,
libanl) into libc. While this is handled transparently at runtime, there
are a few corner cases at build time. In the case of dolfin, the file
usr/share/dolfin/cmake/DOLFINTargets.cmake files embed the path to
libdl.so which doesn't exist anymore.

dolfin has been binNMUed as part of the transition [1], however we later
realised that the above file is actually in the libdolfin-dev-common
package which is binary all. Therefore a source upload is necessary.

Could you please schedule one? There should be no change needed besides
adding a build-depends on libc-dev (>= 2.34) to ensure it is built
against glibc 2.34 (not all chroots have been upgraded yet).

Thanks,
Aurelien

[1] https://buildd.debian.org/status/package.php?p=dolfin

Processed: Bug#1016574 marked as pending in adduser

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016574 [adduser] adduser: dpkg conffile prompt for adduser.conf even 
though unmodified
Added tag(s) pending.

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

Bug#1016574: marked as pending in adduser

[Marc Haber]

Control: tag -1 pending

Hello,

Bug #1016574 in adduser 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/adduser/-/commit/0b1ccd809ba5c585ca94028b38f27daec37c4b37


more clear conffile handling in debian/preinst

Thanks: Simon McVittie
Closes: #1016574


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016574

Processed: bug 1016343 is forwarded to https://github.com/dimitri/pgloader/issues/1407

[Debian Bug Tracking System]

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

> forwarded 1016343 https://github.com/dimitri/pgloader/issues/1407
Bug #1016343 [src:pgloader] pgloader: FTBFS: make[2]: *** [Makefile:125: 
regress/out/csv-districts.out] Error 1
Set Bug forwarded-to-address to 
'https://github.com/dimitri/pgloader/issues/1407'.
> thanks
Stopping processing here.

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

Bug#1016363: Bug#1016516: notion: Notion fails on startup (in sid)

[Göran Weinholt]

Jurij Smakov  writes:

> On Mon, Aug 8, 2022 at 9:50 AM Göran Weinholt  wrote:
>
>  @Jurij: What happens if you update your libc6, could you give it a try?
>  It would be good to get confirmation that the bug was in libc6.
>
> I can confirm that upgrading libc6 (in my case, to Debian's 2.34-3 package) 
> fixes the problem.

Thank you very much. There is the possibility that libc6 2.34 just hides
the problem. Adam Jackson wrote:

| glibc 2.34 merged several libraries into libc.so.6, including
| libpthread, which would probably explain that.



I have a suggested fix for libX11 here, which adds -pthread to the
compilation and linking commands:



It seems harmless, but I've tested it very little.

The discussion is complicated a bit by the fact that there are clients
with genuine bugs (calls to libX11 during event processing), and other
clients that break just because they themselves don't build with
-pthread.

Either way, notion (and glxgears, etc) stopped working because Debian sid
for a short while had glibc 2.33 and a libx11 that called XInitThreads()
without using -pthread, resulting in pthread mutexes being used when
uninitialized.

Regards,

-- 
Göran Weinholt   | https://weinholt.se/
Debian Developer | 73 de SA6CJK

Processed: mpi4py

[Debian Bug Tracking System]

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

> forwarded 1015912 https://github.com/mpi4py/mpi4py/issues/240
Bug #1015912 [src:mpi4py] mpi4py FTBFS on IPV6-only buildds
Set Bug forwarded-to-address to 'https://github.com/mpi4py/mpi4py/issues/240'.
> thanks
Stopping processing here.

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

Bug#1016876: marked as done (netkit-telnetd: missing Conflicts: telnetd-ssl)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 07:34:12 +
with message-id 
and subject line Bug#1016876: fixed in netkit-telnet 0.17-47
has caused the Debian Bug report #1016876,
regarding netkit-telnetd: missing Conflicts: telnetd-ssl
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.)


-- 
1016876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netkit-telnetd
Version: 0.17-46
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../netkit-telnetd_0.17-46_amd64.deb ...
  Unpacking netkit-telnetd (0.17-46) ...
  dpkg: error processing archive 
/var/cache/apt/archives/netkit-telnetd_0.17-46_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/telnetlogin', which is also in package 
telnetd-ssl 0.17.41+0.2-3.3+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/netkit-telnetd_0.17-46_amd64.deb

These files are in conflict:
usr/lib/telnetlogin
usr/sbin/in.telnetd
usr/share/man/man5/issue.net.5.gz
usr/share/man/man8/in.telnetd.8.gz
usr/share/man/man8/telnetlogin.8.gz

telnetd-ssl has a 'Conflicts: telnetd', but that is no longer effective
after the rename to netkit-telnetd.


cheers,

Andreas


telnetd-ssl=0.17.41+0.2-3.3+b1_netkit-telnetd=0.17-46.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: netkit-telnet
Source-Version: 0.17-47
Done: Simon Josefsson 

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

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

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

Debian distribution maintenance software
pp.
Simon Josefsson  (supplier of updated netkit-telnet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Aug 2022 09:16:11 +0200
Source: netkit-telnet
Architecture: source
Version: 0.17-47
Distribution: experimental
Urgency: medium
Maintainer: Simon Josefsson 
Changed-By: Simon Josefsson 
Closes: 1016876
Changes:
 netkit-telnet (0.17-47) experimental; urgency=medium
 .
   * Add Conflicts: telnetd-ssl to netkit-telnetd.  Closes: #1016876.
Checksums-Sha1:
 cf2c37dbdd0e174637d073893d22e579bb5cc5ba 1667 netkit-telnet_0.17-47.dsc
 734289d6f70b07f5e5376dc8ed292834ccc0ed50 36900 
netkit-telnet_0.17-47.debian.tar.xz
 c51e836701b2f3e7f66e4ad77888cb031fde28bd 7352 
netkit-telnet_0.17-47_amd64.buildinfo
Checksums-Sha256:
 386cee79fb8d20d3a731f2788cc1a0a733b46e3fa861acb0e7f4b9549a2d1f61 1667 
netkit-telnet_0.17-47.dsc
 55ece96ffe05bc416254e1b913beb384da51721abed89a1d3c0c32cb0c69d9df 36900 
netkit-telnet_0.17-47.debian.tar.xz
 f2c497eb9aa7cc1b5d3427a89db1fac168f014d1796f2d336c905951ca329947 7352 
netkit-telnet_0.17-47_amd64.buildinfo
Files:
 eb3fd4bdd7547cbb7f2d4b6ecc16baed 1667 net optional netkit-telnet_0.17-47.dsc
 99d09235cb703418f72bac6c484e409a 36900 net optional 
netkit-telnet_0.17-47.debian.tar.xz
 6205b537c060e8fff57c12cf501076fb 7352 net optional 
netkit-telnet_0.17-47_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFIBAEBCgAyFiEEmUFc4ZBdDlWp+IAmhgt/uzL4EZ0FAmLyChkUHHNpbW9uQGpv
c2Vmc3Nvbi5vcmcACgkQhgt/uzL4EZ0lbQf9F5bTbemekSt4DlhQhySgE89EdBDC
61ARQyj4QEb3sLLUGtOET2Y/WjRGGo8FkxlAy+b4eALpj0TP9EMIH5eNqLjcI59W
34IGA4kFjX/n31+7ZnFcC4I8Uc+i6H76iJ6TH0BphOekGNDcy0C1YxzJe3SHaHDl
eg/QaJKLUxZMRy0K6GwvR5Sos5Jqga/GOB6BevYKc5dtipZm3V4ip74fnXx9oOEe
ifkKxYBo3xSg7r9VCFUmPFPxw7zmx+j4lhgCkuZFk5hJItC4fkShrwYpcDDedDsV
NcpntLq3eB2xBaMgdahORdvmzVJc74cC8XmXYGy/Mj0yIa72HRalDKEcvQ==
=eIvQ
-END PGP SIGNATURE End Message ---

Processed: tagging 1016556

[Debian Bug Tracking System]

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

> tags 1016556 + ftbfs
Bug #1016556 [src:fpc] fpc: glibc 2.34 breaks fpc autopkgtest on arm64: 
undefined reference to `__libc_csu_init'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 1016884

[Debian Bug Tracking System]

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

> tags 1016884 + ftbfs
Bug #1016884 [src:heimdal] heimdal: FTBFS with glibc >= 2.34
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Bug#1016560: glibc 2.34 breaks scalpel autopkgtest on amd64: bash: line 1: 1961 Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> severity 1016560 serious
Bug #1016560 [src:scalpel] glibc 2.34 breaks scalpel autopkgtest on amd64: 
bash: line 1:  1961 Segmentation fault
Severity set to 'serious' from 'important'

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

Processed: Bug#1016540: wmanager: FTBFS / autopkgtest regression with glibc 2.34

[Debian Bug Tracking System]

Processing control commands:

> severity 1016540 serious
Bug #1016540 [src:wmanager] wmanager: FTBFS / autopkgtest regression with glibc 
2.34
Severity set to 'serious' from 'important'

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