Bug#1028705: xraylarch: FTBFS: build-dependency not installable: python-numpy-doc

[Andrius Merkys]

Control: tags -1 + pending

On Sat, 14 Jan 2023 13:54:02 +0100 Lucas Nussbaum  
wrote:> > The following packages have unmet dependencies:

>  sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not 
installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


xraylarch builds successfully without python-numpy-doc. I have removed 
it and pushed to salsa.


Andrius

Processed: Re: xraylarch: FTBFS: build-dependency not installable: python-numpy-doc

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1028705 [src:xraylarch] xraylarch: FTBFS: build-dependency not 
installable: python-numpy-doc
Added tag(s) pending.

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

Bug#1028993: marked as done (libsbml: (autopkgtest) needs update for Python 3.11)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 07:50:49 +
with message-id 
and subject line Bug#1028993: fixed in libsbml 5.19.7+dfsg-2
has caused the Debian Bug report #1028993,
regarding libsbml: (autopkgtest) needs update for Python 3.11
to be marked as done.

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

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


-- 
1028993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsbml
Version: 5.19.7+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Hi Maintainer

The autopkgtests of libsbml fail with Python 3.11 as the default
version (and Python 3.10 still supported).  I've copied what I hope is
the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/libs/libsbml/testing/amd64/


autopkgtest [21:36:52]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo
"Testing with $py:" ; $py -c "import libsbml; print(libsbml)" ; done
autopkgtest [21:36:52]: test autodep8-python3: [---
Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/libsbml/libsbml.py", line 27, in 
import _libsbml
ModuleNotFoundError: No module named '_libsbml'
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.19.7+dfsg-2
Done: Étienne Mollier 

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

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

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated libsbml 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, 16 Jan 2023 21:48:17 +0100
Source: libsbml
Architecture: source
Version: 5.19.7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1028993
Changes:
 libsbml (5.19.7+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * d/control: bump preferred python3 version to 3.11. (Closes: #1028993)
   * d/control: declare compliance to standards version 4.6.2.
Checksums-Sha1:
 7ab39d265641822372da94995e59f56a2e9601f4 3860 libsbml_5.19.7+dfsg-2.dsc
 2741298e1b35f1fa51bbc97e90a890492a55dbac 31268 
libsbml_5.19.7+dfsg-2.debian.tar.xz
Checksums-Sha256:
 19c30a0d7a49d3b197c945fec775a88b27a2694cabfe3dc29a7b713631ab1a1c 3860 
libsbml_5.19.7+dfsg-2.dsc
 0c76c501a13aa0eccb1061b4fd12491fa124e989b3854532e13f06487a23a9e6 31268 
libsbml_5.19.7+dfsg-2.debian.tar.xz
Files:
 a8bc2c285d0b880e2cc6e0e90fb0dcd6 3860 science optional 
libsbml_5.19.7+dfsg-2.dsc
 9c8a927a0ee91b43b82c2be5d507436e 31268 science optional 
libsbml_5.19.7+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmPGSrAUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqeNQ//S6fUqUBfhZyPtxkOZoYElQBnzRNz
YZPIalIRuwNPLtmjInTJo0SLRkWZe8mHEDL+ynAfDTa0iXABGzDjjdfpp8g/K8rr
5yHg+27QlrxiUxBJ9vxy2ixsB3RT/0C3u6RjbIItKlHX5Nw1MSZX80UJDiLRerQu
+bSiofQB76rToKhxhutLmQM9Fh5vmmlcsVphg+01uKrgLEXekkAjP/Wcrcb2g2LQ
SWB0yyoxdchIbss+iU9fzGfqkLtvLyDxS0uTYCwivN1TZTgKB7AKwR//40ynm1+b
SjVdfLuZbABT40F0GG8ZzooBWFNpNrxkezg4UlEFUMha/4cs+Lj0Yj8AIsZREZK2
smo+G0VMuo2iuQK04iPYQef6cgI7J5pIwTTicwou9JT+EGG3+JEQt0fX91IGpwtW
0ebClety7NWQSrQq5XxiwPGbwaG1+FJSlgY3IohB9L6dWocbuvL9MLZZ5WQlyNYH
tMQ/3i1id431iPB5zzdEEF9cfRx8uXOGXcfmjtOOjlB+4uFR6P/W0OUhzEg/Y+v/
YUrD1NFtaWOsUj5RCe27I04sHAGCqKml+3+0MDzdEFRh04WicuTX663yPVQLQ8hB
/IC4Ev6U2xDffKP+zW3gg+/3OzsfnUozV4r0/xVgAmgWTYA9mNUsATMd8VP/XF2b
K1XWaoTXkYkdTvI=
=2QFf
-END PGP SIGNATURE End Message ---

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

[Emmanuel Promayon]

Dear Andreas,

Thank you for your commit on salsa.
The VTK API is generally stable enough and some little things might have 
to be modified in the source code. However, my experience with 
transition to a new VTK version is that it may cause some problem in the 
way 3D rendering is handled, which is harder to tackle.


I have not tested CamiTK with VTK9 yet, but I will try to do so in the 
next few days and will get back to you ASAP.


Kind regards and thanks again for the time and attention
Emmanuel

On 14/01/2023 08:42, Andreas Tille wrote:

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

Hi Emmanuel and Celine,

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

Kind regards
 Andreas.



--
Emmanuel Promayon
Professeur Univ. Grenoble Alpes - Polytech Grenoble
Laboratoire TIMC - équipe GMCAO

Bug#1025868: marked as done (lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 07:00:30 +
with message-id 
and subject line Bug#1025868: fixed in lintian 2.116.0
has caused the Debian Bug report #1025868,
regarding lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected 
build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t
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.)


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

Source: lintian
Version: 2.111.0
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails currently 
everywhere except on amd64. Can you please investigate the situation and 
fix it? I copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing as are regressions on all release 
architectures.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/l/lintian/28970519/log.gz

# Hints do not match
#
# --- 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.specified.calibrated
# +++ 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.actual.parsed
# -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/x86_64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/GoodExtras-42.typelib]
# -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/x86_64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/Good-42.typelib]
# +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/aarch64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/GoodExtras-42.typelib]
# +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory 
usr/lib/aarch64-linux-gnu/girepository-1.0 
[usr/lib/girepository-1.0/Good-42.typelib]

#
#   Failed test 'Lintian passes for gir'
#   at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t 
...



and

# Hints do not match
#
# --- 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/hints.specified.calibrated
# +++ 
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/hints.actual.parsed
# +bin-sbin-confusion-in-elf (binary): bin-sbin-mismatch sbin/our-script 
-> usr/bin/our-script [usr/bin/calls-sbin]
# +bin-sbin-confusion-in-elf (binary): bin-sbin-mismatch bin/our-script 
-> usr/bin/our-script [usr/bin/calls-sbin]

#
#   Failed test 'Lintian passes for bin-sbin-confusion-in-elf'
#   at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343.
# Looks like you failed 1 test of 1.
../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/generic.t 



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.116.0
Done: Axel Beckert 

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated lintian 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, 17 Jan 2023 01:37:56 +0100
Source: lintian
Architecture: source
Version: 2.116.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Axel Beckert 
Closes: 932634 1002053 1006631 1013314 1014175 1014956 1016147 

Bug#1021628: marked as done (android-platform-tools: FTBFS: error: no template named 'function' in namespace 'std')

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 22:37:14 -0800
with message-id 

and subject line Re: android-platform-tools: FTBFS: error: no template named 
'function' in namespace 'std'
has caused the Debian Bug report #1021628,
regarding android-platform-tools: FTBFS: error: no template named 'function' in 
namespace 'std'
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.)


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

Hi,

android-platform-tools/experimental recently started to FTBFS.
The version in sid is not affected.

...
clang++ -c -o packages/modules/adb/client/auth.o 
packages/modules/adb/client/auth.cpp -g -O2 
-ffile-prefix-map=/build/android-platform-tools-33.0.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -std=gnu++2a 
-Wexit-time-destructors -Wno-non-virtual-dto
r -Wno-unused-parameter -Wno-missing-field-initializers -Wvla  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -fmessage-length=0 -fno-exceptions 
-fno-strict-aliasing -no-canonical-prefixes  -Wno-c99-designator 
-Wno-gnu-designator -Wno-gnu-folding-constant  -DPLATFORM_T
OOLS_VERSION='"33.0.1"' -DADB_HOST=1 -DADB_VERSION='"33.0.1-1~exp9"' 
-DANDROID_BASE_UNIQUE_FD_DISABLE_IMPLICIT_CONVERSION=1 -Ipackages/modules/adb 
-Ipackages/modules/adb/crypto/include 
-Ipackages/modules/adb/pairing_auth/include 
-Ipackages/modules/adb/pairing_connection/
include -Ipackages/modules/adb/proto -Ipackages/modules/adb/tls/include 
-Isystem/core/diagnose_usb/include -Isystem/core/include 
-Isystem/core/libcrypto_utils/include -Isystem/core/libcutils/include 
-Isystem/libbase/include -I/usr/include/android
...
In file included from packages/modules/adb/client/auth.cpp:35:
packages/modules/adb/tls/include/adb/tls/tls_connection.h:51:31: error: no 
template named 'function' in namespace 'std'
using CertVerifyCb = std::function;
 ~^
packages/modules/adb/tls/include/adb/tls/tls_connection.h:52:28: error: no 
template named 'function' in namespace 'std'
using SetCertCb = std::function;
  ~^
packages/modules/adb/tls/include/adb/tls/tls_connection.h:67:40: error: unknown 
type name 'CertVerifyCb'
virtual void SetCertVerifyCallback(CertVerifyCb cb) = 0;
   ^
packages/modules/adb/tls/include/adb/tls/tls_connection.h:76:41: error: unknown 
type name 'SetCertCb'
virtual void SetCertificateCallback(SetCertCb cb) = 0;
^
...
4 errors generated.
make[2]: *** [debian/system/libadb.mk:120: packages/modules/adb/client/auth.o] 
Error 1


Looks like a missing #include that is no longer included transitively.


Andreas


android-platform-tools_33.0.1-1~exp9.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 33.0.3-1~exp1--- End Message ---

Bug#1028451: 2nd DisplayPort doesn't get video

[Salvatore Bonaccorso]

Hi,

Thanks all who have contributed to the descussion! Much appreciated.

On Mon, Jan 16, 2023 at 03:08:22PM -0700, Sam Hartman wrote:
> > "Moritz" == Moritz Mühlenhoff  writes:
> Moritz> Not moving to 6.1.x (which is most likely the next Linux
> Moritz> kernel LTS) is by far a worse regression since it applies to
> Moritz> every single Debian system.
> 
> Moritz> As a community distro without paid, full time kernel
> Moritz> maintainers we can't just randomly stick to an older kernel
> Moritz> tree and decide to assess/backport hundreds of patches sent
> Moritz> to stable@ every week.
> 
> I think we're all agreed on that point.
> What we can do is delay the release if we have a serious enough bug that
> is not fixed yet.
> I think what people are saying on this bug is that this issue is serious
> enough it should be considered as a release blocker---something that
> could actually delay the release.

I do agree, this is defintively an issue we would not would want to
have in a stable release, so the assessment of marking it RC is
defintively right.

While 6.0.y is now EOL, and 6.1 was aimed to be the LTS release, and
the reason we would like to pick that for bookworm, there was not yet
an official announce for it, in part because of reported regressions,
cf. https://lore.kernel.org/all/y53bputyk+3dj...@kroah.com/ and
https://lore.kernel.org/all/20230114084719.ga6...@1wt.eu/ for some
context.

> From where I sit, thinking about what I've deployed in the last five
> years, I agree with that analysis: this *might* be serious enough to
> delay the release until there is a fix.
> Given that  we can't stick on 6.0, I think we should try to get this
> into testing as soon as possible so we can see how big of an impact it
> is in practice.
> I don't like to see testing broken, but I like to see stable broken in
> serious ways even less.
> And so I'd recommend we see  how badly this is going to hurt us.

I will bite the bullet (taking full responsibility for it if
necessary, don't blame the other kernel team members) and ask here now
the release team: Can we let linux 6.1.4-1 despite the RC bug
reported, migrate to testing, so we can move on to 6.1.y? Let's keep
the bug as RC severity. I'm currently working on uploading as well
6.1.6 or 6.1.7 (depending on the timing) further after that to
unstable.  Unfortuantely there is still not a solution to address
#1028451 but will contain other important fixes (including security
ones).

Thank you for considering it,

Odyx, I feel sorry, this will knowingly impact your and others!

Regards,
Salvatore

Processed: Re: python3-opengl: GLUT import error on Wayland

[Debian Bug Tracking System]

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

> forwarded 1029011 https://github.com/mcfletch/pyopengl/issues/89
Bug #1029011 [python3-opengl] python3-opengl: GLUT import error on Wayland
Set Bug forwarded-to-address to 
'https://github.com/mcfletch/pyopengl/issues/89'.
> thanks
Stopping processing here.

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

Bug#1028099: marked as done ([libtepl-6-2] package upgrade error)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 04:20:11 +
with message-id 
and subject line Bug#1024388: fixed in tepl 6.4.0-6
has caused the Debian Bug report #1024388,
regarding [libtepl-6-2] package upgrade error
to be marked as done.

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

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


-- 
1024388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtepl-6-2
Version: 6.4.0-3
Severity: serious

Ran into an upgrade issue on Sid today. Seems libtepl-6-1 did not get
removed before trying to install libtepl-6-2, causing the libtepl-6-2
install to fail, and consequently cascading failures from there.

Output of first aptitude upgrade command:

```
$ sudo aptitude upgrade
Resolving dependencies...
The following NEW packages will be installed:
  libtepl-6-2{a} 
The following packages will be REMOVED:
  libtepl-6-1{u} 
The following packages will be upgraded:
  gedit gedit-plugin-bookmarks gedit-plugin-bracket-completion 
gedit-plugin-character-map 
  gedit-plugin-code-comment gedit-plugin-color-picker 
gedit-plugin-color-schemer 
  gedit-plugin-draw-spaces gedit-plugin-git gedit-plugin-join-lines 
gedit-plugin-multi-edit 
  gedit-plugin-session-saver gedit-plugin-smart-spaces gedit-plugin-synctex 
  gedit-plugin-terminal gedit-plugin-text-size gedit-plugin-word-completion 
  gedit-plugins-common gnustep-base-common gnustep-base-runtime imagemagick 
  imagemagick-6-common imagemagick-6.q16 libapache-pom-java libbcmail-java 
libbcpkix-java 
  libbcprov-java libbcutil-java libgnustep-base1.28 libmagick++-6.q16-8 
libmagickcore-6.q16-6 
  libmagickwand-6.q16-6 
The following packages are RECOMMENDED but will NOT be installed:
  libmagickcore-6.q16-6-extra 
32 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 16.3 MB of archives. After unpacking 1,024 B will be freed.
Do you want to continue? [Y/n/?] y
Get: 1 https://deb.debian.org/debian sid/main amd64 libtepl-6-2 amd64 6.4.0-3 
[122 kB]
Get: 2 https://deb.debian.org/debian sid/main amd64 gedit amd64 43.2-2+b1 [364 
kB]
Get: 3 https://deb.debian.org/debian sid/main amd64 gedit-plugins-common amd64 
43.1-1+b1 [293 kB]
Get: 4 https://deb.debian.org/debian sid/main amd64 gedit-plugin-draw-spaces 
amd64 43.1-1+b1 [19.9 kB]
Get: 5 https://deb.debian.org/debian sid/main amd64 imagemagick-6-common all 
8:6.9.11.60+dfsg-1.4 [165 kB]
Get: 6 https://deb.debian.org/debian sid/main amd64 libmagickcore-6.q16-6 amd64 
8:6.9.11.60+dfsg-1.4 [1,780 kB]
Get: 7 https://deb.debian.org/debian sid/main amd64 libmagickwand-6.q16-6 amd64 
8:6.9.11.60+dfsg-1.4 [407 kB]
Get: 8 https://deb.debian.org/debian sid/main amd64 gedit-plugin-bookmarks 
amd64 43.1-1+b1 [30.6 kB]
Get: 9 https://deb.debian.org/debian sid/main amd64 
gedit-plugin-bracket-completion amd64 43.1-1+b1 [17.9 kB]
Get: 10 https://deb.debian.org/debian sid/main amd64 gedit-plugin-character-map 
amd64 43.1-1+b1 [21.1 kB]
Get: 11 https://deb.debian.org/debian sid/main amd64 gedit-plugin-code-comment 
amd64 43.1-1+b1 [22.0 kB]
Get: 12 https://deb.debian.org/debian sid/main amd64 gedit-plugin-color-picker 
amd64 43.1-1+b1 [22.4 kB]
Get: 13 https://deb.debian.org/debian sid/main amd64 gedit-plugin-color-schemer 
amd64 43.1-1+b1 [18.9 kB]
Get: 14 https://deb.debian.org/debian sid/main amd64 gedit-plugin-git amd64 
43.1-1+b1 [24.4 kB]
Get: 15 https://deb.debian.org/debian sid/main amd64 gedit-plugin-join-lines 
amd64 43.1-1+b1 [22.1 kB]
Get: 16 https://deb.debian.org/debian sid/main amd64 gedit-plugin-multi-edit 
amd64 43.1-1+b1 [28.4 kB]
Get: 17 https://deb.debian.org/debian sid/main amd64 gedit-plugin-session-saver 
amd64 43.1-1+b1 [20.4 kB]
Get: 18 https://deb.debian.org/debian sid/main amd64 gedit-plugin-smart-spaces 
amd64 43.1-1+b1 [10.7 kB]
Get: 19 https://deb.debian.org/debian sid/main amd64 gedit-plugin-synctex amd64 
43.1-1+b1 [20.0 kB]
Get: 20 https://deb.debian.org/debian sid/main amd64 gedit-plugin-terminal 
amd64 43.1-1+b1 [20.6 kB]
Get: 21 https://deb.debian.org/debian sid/main amd64 gedit-plugin-text-size 
amd64 43.1-1+b1 [19.0 kB]
Get: 22 https://deb.debian.org/debian sid/main amd64 
gedit-plugin-word-completion amd64 43.1-1+b1 [24.6 kB]
Get: 23 https://deb.debian.org/debian sid/main amd64 libgnustep-base1.28 amd64 
1.28.1-2 [1,595 kB]
Get: 24 https://deb.debian.org/debian sid/main amd64 gnustep-base-runtime amd64 
1.28.1-2 [445 kB]
Get: 25 https://deb.debian.org/debian sid/main amd64 gnustep-base-common all 
1.28.1-2 [296 kB]
Get: 26 https://deb.debian.org/debian sid/main amd64 imagemagick-6.q16 amd64 

Bug#1024388: marked as done (libtepl-6-2: missing (unversioned) Breaks+Replaces: libtepl-6-0, libtepl-6-1)

[Debian Bug Tracking System]

Your message dated Tue, 17 Jan 2023 04:20:11 +
with message-id 
and subject line Bug#1024388: fixed in tepl 6.4.0-6
has caused the Debian Bug report #1024388,
regarding libtepl-6-2: missing (unversioned) Breaks+Replaces: libtepl-6-0, 
libtepl-6-1
to be marked as done.

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

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


-- 
1024388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtepl-6-1
Version: 6.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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 .../libtepl-6-1_6.2.0-2_amd64.deb ...
  Unpacking libtepl-6-1:amd64 (6.2.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/tepl-6.mo', which is 
also in package libtepl-6-0:amd64 6.1.2-1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb


The *.mo files have the same name in both packages.


cheers,

Andreas


libtepl-6-0=6.1.2-1+b2_libtepl-6-1=6.2.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tepl
Source-Version: 6.4.0-6
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated tepl 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, 16 Jan 2023 22:55:24 -0500
Source: tepl
Built-For-Profiles: noudeb
Architecture: source
Version: 6.4.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1024388
Changes:
 tepl (6.4.0-6) unstable; urgency=medium
 .
   * Release to unstable
 .
 tepl (6.4.0-5) experimental; urgency=medium
 .
   * Add libtepl-common package for smoother library transitions in the future
 (Closes: #1024388)
Checksums-Sha1:
 5847055c1f0a773d36119eda2969f9d433d47c6a 2562 tepl_6.4.0-6.dsc
 f9f6a75bedee4973ca25130aeeeab8ddf8ea4cad 6352 tepl_6.4.0-6.debian.tar.xz
 7dc45f02dcf73da398dd68c82ec9538011a500b4 18356 tepl_6.4.0-6_source.buildinfo
Checksums-Sha256:
 9426fa9917682634b07730c715dc1f858b43b248f23d0b7c697072910ff2c3a5 2562 
tepl_6.4.0-6.dsc
 680e26933151218acd4ec1deae4087f179c3e690b5919b20e83f8d85eae807ae 6352 
tepl_6.4.0-6.debian.tar.xz
 841759751af5f3553ec5160c0fdd8b1bafd1161aa6e49a6667a8eb56c6e84c9a 18356 
tepl_6.4.0-6_source.buildinfo
Files:
 2e5c50bc0bb7b141f6484455825fc9e5 2562 libs optional tepl_6.4.0-6.dsc
 0d59dc72cde8223979e1b582f5ac19a9 6352 libs optional tepl_6.4.0-6.debian.tar.xz
 dec819b6e4abcd891dcfd3700c9f8c60 18356 libs optional 
tepl_6.4.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmPGHFIACgkQ5mx3Wuv+
bH3b6g/3YBg+0X8g32b0v6PDhkFvSeNf1oM2D4SvCR0sPGKJahSU2zODGxnp46bV
U8H7VDFIwz+xBMIZ41OzwShx1LS+Vagky3EsA3eZjNXrrJvwCxbZGb0gaTd7VvfF
NMpoaFztZnunTMKiCeIVPgBhyynhagLPhBQOokFI3IwgJFLPUdbJnxf80jG8IqiK
7KzQDcV36pQieEh2uuHwz5cROUdVMq5CFHtV7XzFDZ+8tB7n+KQrFB2X2rKF3/PI
9RJkUcY5XR3vMYUPEefr0KVFu91b/RCx1922mQLLQThTDB4MRlR0vZ/mI7IWzPB0
P0hSysFRB7PryMX129SC9cVIxGvEO+r8fjM7HNr1a0Wc9TgM3KfD9ZvcGeG6XVa8
39UidTyueaWtOE15KFFvuOzBjbBDhFdZeB9u5i+N+F17ZDDKyJNQMd9CQfKRd6i9
7WL7fn2dud8lKIwo+BqGjbPTvHS5ZFY6N5bIvFOEX6uTMiyTwsQsBoXuWKFnRv2E
uk3qrQnPwXbTlWB0ciF7IHgi+ZVKWrkxaGjAuZ0QWqrL31zyuIXp8hIUMkxXExVl
F+Ola1LzujpncSklwQGDSBHuKIWcEIwGeoo4S9k/Z1zbqzrbNaGpHGJ5om5ACrrX
6PpNK2PRHu3+rfHFXHTeHJbqj7aY2KhSNjfJhhNqDrbzTlTycw==
=gsZT
-END PGP SIGNATURE End Message ---

Processed: tagging 1026343

[Debian Bug Tracking System]

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

> tags 1026343 + ftbfs
Bug #1026343 [src:bcolz] bcolz: autopkgtest needs update for new version of 
numpy: 'NoneType' object has no attribute 'base'
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1003694: marked as done ("gosa: completly broken in bookworm, breaking debian-edu")

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 22:36:13 +
with message-id 
and subject line Bug#1003694: fixed in gosa 2.8~git20230116.d119cff+dfsg-1
has caused the Debian Bug report #1003694,
regarding "gosa: completly broken in bookworm, breaking debian-edu"
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.)


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

Package: src:gosa
Severity: important
Version: 2.7.4+reloaded3-16

There are some PHP deprecations warnings appearing on screen when  
using GOsa on Debian bullseye against PHP 7.4. Probably much worse  
with upcoming PHP 8.x:


```

Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 156


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1013


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1035


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1039


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1045


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1047


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1062


Deprecated: Array and string offset access syntax with curly braces is  
deprecated in  
/usr/share/gosa/include/utils/excel/class.writeexcel_formula.inc.php  
on line 1194


Warning: "continue" targeting switch is equivalent to "break". Did you  
mean to use "continue 2"? in  
/usr/share/gosa/plugins/admin/systems/services/shares/class_servNfs.inc on  
line 130


Warning: "continue" targeting switch is equivalent to "break". Did you  
mean to use "continue 2"? in  
/usr/share/gosa/plugins/admin/systems/services/shares/class_goShareServer.inc  
on line 383


```

I will collect more of these an propose a fix for them...

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpQOyd7mxWMc.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: gosa
Source-Version: 2.8~git20230116.d119cff+dfsg-1
Done: Mike Gabriel 

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

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

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated gosa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Jan 2023 15:51:01 +0100
Source: gosa
Architecture: source
Version: 2.8~git20230116.d119cff+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Closes: 991542 1003694
Changes:
 gosa (2.8~git20230116.d119cff+dfsg-1) experimental; urgency=medium
 .
   * Upload to experimental.
 .
   * Upstream pre-release of GOsa² 2.8.x. (Closes: #1003694, #991542
 #800679).
   * debian/patches:
 + Drop nearly all patches except from the Debian-specific ones. Next major
   GoSA² version has them all (or should, but that's an upstream matter from
   here).
 + Trivial rebase of 2002 and 2003.
 + Rebase 2004_fix-locale-location.patch.
 + Add 0001_fix-setup-license-txt.patch. Amend license mismatch between
 

Bug#1028305: marked as done (libcotp12: Update libotp to fix grave bug)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 22:09:56 +
with message-id 
and subject line Bug#1028305: fixed in libcotp 1.2.8-1
has caused the Debian Bug report #1028305,
regarding libcotp12: Update libotp to fix grave bug
to be marked as done.

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

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


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

Package: libcotp12
Version: 1.2.6-2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

libotp, and hence otpclient and possibly other applications using this 
library, has a grave bug preventing it to be used.  Please update to 
1.2.8, released yesterday (a few days after previous buggy version 1.2.7).


More information: 
https://github.com/paolostivanin/libcotp/releases/tag/v1.2.8 ("This 
release fixes a regression brought with v1.2.7. Users must either update 
to this release or rollback to v1.2.6.")


Thanks,
Eugen
--- End Message ---
--- Begin Message ---
Source: libcotp
Source-Version: 1.2.8-1
Done: Francisco Vilmar Cardoso Ruviaro 

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

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

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

Debian distribution maintenance software
pp.
Francisco Vilmar Cardoso Ruviaro  (supplier of updated 
libcotp 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, 16 Jan 2023 21:01:00 +
Source: libcotp
Architecture: source
Version: 1.2.8-1
Distribution: unstable
Urgency: medium
Maintainer: Francisco Vilmar Cardoso Ruviaro 
Changed-By: Francisco Vilmar Cardoso Ruviaro 
Closes: 1028305
Changes:
 libcotp (1.2.8-1) unstable; urgency=medium
 .
   * New upstream version 1.2.8. (Closes: #1028305)
Checksums-Sha1:
 a955b439cd1c776067196859556e6459d03a6e82 2217 libcotp_1.2.8-1.dsc
 aaf5ccad4db2724e5fc2d36de7c32caf456b9f5b 13647 libcotp_1.2.8.orig.tar.gz
 0cfde46ac1d1e9fda51bb964ddaf16eef837beff 833 libcotp_1.2.8.orig.tar.gz.asc
 792bc80e71c7f281dbaa21f383f85ca5d47fd25e 5516 libcotp_1.2.8-1.debian.tar.xz
 c5eb83e971fbaf14bf509844cfd63c9ed1c8c8c7 7515 libcotp_1.2.8-1_amd64.buildinfo
Checksums-Sha256:
 4cb2cf0f7cdd19826ac0c25d15a71a6c2bebe2d1d80d74639d00c16786ffb4f7 2217 
libcotp_1.2.8-1.dsc
 78dab6a2ee08e73f1d052dcb7c1ad069cc37fdf600f3f660d8e6299e11218f0b 13647 
libcotp_1.2.8.orig.tar.gz
 8fb3deddf9cf22814059fa0eef4fd85576b1d6a4ec6345f9f35f1a9f6198afed 833 
libcotp_1.2.8.orig.tar.gz.asc
 44822c0160cdae10a53fa8bb4505eddd09156c0591b6005ac9a5bc7b9d424429 5516 
libcotp_1.2.8-1.debian.tar.xz
 9f49c490e172a308987316d9a25811f0cf7a0b35bbb0b8eb9db84c7bc31dcc39 7515 
libcotp_1.2.8-1_amd64.buildinfo
Files:
 b499f23c43a57a627c77c936ef0f1a7b 2217 libs optional libcotp_1.2.8-1.dsc
 9c1ffc06009e67d16071dedaccb2deec 13647 libs optional libcotp_1.2.8.orig.tar.gz
 59c024a1ca81eb02d798c00a53a344f8 833 libs optional 
libcotp_1.2.8.orig.tar.gz.asc
 bea0d82c14fca0b3d0d6e0b84a62247f 5516 libs optional 
libcotp_1.2.8-1.debian.tar.xz
 f2b66d2bbb8273ef6713ac50f5c34ea4 7515 libs optional 
libcotp_1.2.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEG4z2Vu87hEcvSPDngvv3BgsvfQAFAmPFvmYSHHZpbG1hckBk
ZWJpYW4ub3JnAAoJEIL79wYLL30Al70QAINcOv+E6p0gyIi2+1ok8gJllOhSuiWO
2lIsfJw57VZ5oEfRVs43gGSuHnue4V2XbCqjdI0AYENuPw0vfpE607yaLJ8U4D3L
FlRANW1IbrqyoN5yLDsEg/am4eQq/3+9QZ5uFEauH2vl+NR/zKAwH8R6tvl5Uqp/
LnVfEH9X0G5GA6sezwqkVxEvvPrwaylqXQNDOMUPXtLITFFsxcboS8rGEIQgeSwm
qNePxSDB58JWLK1T2bMpT8P3eK+5et0uGAtXWumU7wqlF2LKvP1tQ8pzmjtsy02F
iEfMvkAsretjscmvY9SdBmxHZHt6OmwI6kCQSo4e71/q0VbrPELUzIQ+LFFn+GRB
TOkuiK/h60gwOi7ES9YtLg3WpO2Hh/E3vv2PpGo81HT5D82aO0AELRrCXXWXYs99
WbG2pJHzncLZF5y3blP8LL/QzPa85Bjw58kGfgIE1ENuFiMhergoieXnj9EDmWoq
IQRTJlthYVrz+wwwTe7dXSAC0ML2OZKneiA8U0RpTP9DPfYyZSQKjqGSkUq4wouh
FaOlDdOoeHpYhXMyxXQmWDos5OrhaeCODdcOROvHG/87mJkRGY9AtwUXxnQIftY3
AWkzHgTVELoXZ5yh1k/RpPbOWJ9ZVz47DRQqKbFMBjqW1MhDV8Kq283Y3lio5fYn
BZLG8oQyQLl9
=/XIg
-END PGP SIGNATURE End Message ---

Bug#1028451: 2nd DisplayPort doesn't get video

[Sam Hartman]

> "Moritz" == Moritz Mühlenhoff  writes:
Moritz> Not moving to 6.1.x (which is most likely the next Linux
Moritz> kernel LTS) is by far a worse regression since it applies to
Moritz> every single Debian system.

Moritz> As a community distro without paid, full time kernel
Moritz> maintainers we can't just randomly stick to an older kernel
Moritz> tree and decide to assess/backport hundreds of patches sent
Moritz> to stable@ every week.

I think we're all agreed on that point.
What we can do is delay the release if we have a serious enough bug that
is not fixed yet.
I think what people are saying on this bug is that this issue is serious
enough it should be considered as a release blocker---something that
could actually delay the release.

From where I sit, thinking about what I've deployed in the last five
years, I agree with that analysis: this *might* be serious enough to
delay the release until there is a fix.
Given that  we can't stick on 6.0, I think we should try to get this
into testing as soon as possible so we can see how big of an impact it
is in practice.
I don't like to see testing broken, but I like to see stable broken in
serious ways even less.
And so I'd recommend we see  how badly this is going to hurt us.


signature.asc
Description: PGP signature

Bug#1028872: marked as done (elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 22:05:38 +
with message-id 
and subject line Bug#1028872: fixed in elan 1.4.2-4
has caused the Debian Bug report #1028872,
regarding elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build 
returned exit code 101
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.)


-- 
1028872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elan
Version: 1.4.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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 '/<>'
> touch debian/cargo-checksum.json
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `zstd = "^0.11.2"`
> candidate versions found which didn't match: 0.12.1+zstd.1.5.2
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `elan-dist v1.11.0 (/<>/src/elan-dist)`
> ... which satisfies path dependency `elan-dist` of package `elan v1.4.2 
> (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/elan_1.4.2-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

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

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

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated elan 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, 16 Jan 2023 21:17:12 +
Source: elan
Architecture: source
Version: 1.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin 
Changed-By: Christopher Hoskin 
Closes: 1028653 1028872
Changes:
 elan (1.4.2-4) unstable; urgency=medium
 .
   [ Peter Michael Green ]
   * Build-depend explicitly on clap 2.x (Closes: #1028653)
   * Update cargo dependency for zstd 0.11 and update Debian dependency
 to match. (Closes: #1028872)
 .
   [ Christopher Hoskin ]
   * Update copyright
Checksums-Sha1:
 3b2eee285db70dc9ff5320f9371faf7fff55afd1 2742 elan_1.4.2-4.dsc
 eacbf82ac90d3fdcd7bbae5f9337e0eb968a4e51 6404 elan_1.4.2-4.debian.tar.xz
 a52f115385bb4a43ca63d7aed2941e95954b18a9 18222 elan_1.4.2-4_amd64.buildinfo
Checksums-Sha256:
 

Bug#1023284: libevent: FTBFS with glibc 2.36

[Nicolas Mora]

Hello,

I opened an issue upstream [1] to ask for feedbacks. Azat suggest to 
change the function signature from


void evutil_secure_rng_add_bytes(const char *buf, size_t n);

to:
int evutil_secure_rng_add_bytes(const char *buf, size_t n)

and make evutil_secure_rng_add_bytes to return -1, to make it more 
explicit that the function is no-oped.


I understand and I tend to agree with this suggestion, but I'm wondering 
if this solution is correct for this bug?


The symbol would still be the same, but would the signature change 
introduce problems in the libevent package dependencies and build-deps?


Any thoughts?

/Nicolas

[1] https://github.com/libevent/libevent/issues/1393

Bug#1028451: 2nd DisplayPort doesn't get video

[Moritz Mühlenhoff]

Am Mon, Jan 16, 2023 at 12:46:37PM + schrieb Didier 'OdyX' Raboud:
> > I understand that would be annoying for you, but I don't think that it would
> > affect the majority of our users.
> 
> Hrm. More and more laptops come with usb-c only, and dongles/docks become more
> and more common.
> 
> It's clearly a serious regression, as such setups "just worked" with 6.0.

Not moving to 6.1.x (which is most likely the next Linux kernel LTS) is by far
a worse regression since it applies to every single Debian system.

As a community distro without paid, full time kernel maintainers we can't
just randomly stick to an older kernel tree and decide to assess/backport
hundreds of patches sent to stable@ every week.

Cheers,
Moritz

Bug#1029047: software-properties-qt: software-property-qt should depends on lazr

[Vincent-Xavier JUMEL]

Package: software-properties-qt
Version: 0.99.30-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When launching software-properties-qt, I get the following message :

❯ /usr/bin/software-properties-qt
Traceback (most recent call last):
  File "/usr/bin/software-properties-qt", line 36, in 
from softwareproperties.qt.SoftwarePropertiesQt import SoftwarePropertiesQt
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 45, in 
from softwareproperties.SoftwareProperties import SoftwareProperties
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
62, in 
from softwareproperties.shortcuts import shortcut_handler
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
from softwareproperties.ppa import PPAShortcutHandler
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, in 

from lazr.restfulclient.errors import (NotFound, BadRequest, Unauthorized)
ModuleNotFoundError: No module named 'lazr'

The package should include a runtime depends on python3-lazr.uri.

Thanks,

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

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

Versions of packages software-properties-qt depends on:
ii  debconf-kde-helper   1.1.0-1
ii  python3  3.11.1-1
ii  python3-pyqt55.15.7+dfsg-3+b3
ii  python3-software-properties  0.99.30-3
ii  software-properties-common   0.99.30-3

software-properties-qt recommends no packages.

Versions of packages software-properties-qt suggests:
ii  plasma-discover  5.26.5-2

-- no debconf information

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1028442: marked as done (vim-ultisnips: autopkgtest fails if Vim has non-contiguous patch ranges applied)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 21:27:58 +
with message-id 
and subject line Bug#1028442: fixed in vim-ultisnips 3.2-2
has caused the Debian Bug report #1028442,
regarding vim-ultisnips: autopkgtest fails if Vim has non-contiguous patch 
ranges applied
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.)


-- 
1028442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vim-ultisnips
Version: 3.2-1
Severity: serious
Tags: upstream
Justification: RT

Bookworm's Vim now has a non-contiguous set of patches applied:

% vim --version | grep Included
Included patches: 1-1000, 1087, 1117-1118, 1129

This is causing the "with-vim" autopkgtests to fail to parse the Vim
version.  For example:

==
ERROR: runTest 
(test_Autotrigger.Autotrigger_WillProduceNoExceptionWithVimLowerThan214.runTest)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/vim_test_case.py", 
line 99, in setUp
reason_for_skipping = self.skip_if()
  ^^
  File 
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/test_Autotrigger.py", 
line 56, in 
if not check_required_vim_version(self)
   
  File 
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/test_Autotrigger.py", 
line 8, in check_required_vim_version
if not test.vim.has_version(7, 4, 214):
   ^^^
  File 
"/tmp/autopkgtest-lxc.8wvyi1gs/downtmp/build.Ujt/src/test/vim_interface.py", 
line 102, in has_version
_patch = int(line.split(":")[-1].strip().split("-")[-1])
 ^^^
ValueError: invalid literal for int() with base 10: '1118, 1129'

See the full log for more failures:
https://ci.debian.net/data/autopkgtest/unstable/i386/v/vim-ultisnips/30238961/log.gz

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: vim-ultisnips
Source-Version: 3.2-2
Done: Nicholas Guriev 

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

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

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

Debian distribution maintenance software
pp.
Nicholas Guriev  (supplier of updated vim-ultisnips 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: Sat, 14 Jan 2023 20:11:35 +0300
Source: vim-ultisnips
Architecture: source
Version: 3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev 
Changed-By: Nicholas Guriev 
Closes: 1028442
Changes:
 vim-ultisnips (3.2-2) unstable; urgency=medium
 .
   * test/vim_interface.py: Check Vim version through call to Vim's has()
 function. (Closes: #1028442)
   * test/vim_test_case.py: Respect the retries option in tests with the
 expected_error parameter.
   * debian/watch: Update to changed HTML on GitHub page.
Checksums-Sha1:
 79dd85158c5573a3f7d07907df3f373166a3f958 1449 vim-ultisnips_3.2-2.dsc
 75b7750bba5b0959dc793278eaeef07fb54d4b8a 8012 vim-ultisnips_3.2-2.debian.tar.xz
Checksums-Sha256:
 c0701867020e7e21adc45e16bac24477c4ee4342f3aea48be0f10d572472e657 1449 
vim-ultisnips_3.2-2.dsc
 964c3031c1b15b47e8647bfd385395d52afdea80a5e1c44059b28faec0b10b1b 8012 
vim-ultisnips_3.2-2.debian.tar.xz
Files:
 2c21caef2ce5d499fad338140739a40e 1449 editors optional vim-ultisnips_3.2-2.dsc
 ff0f67ceb2ec1a578d8b2012f1d5747c 8012 editors optional 

Bug#1027622: marked as done (mccs: FTBFS: stl_tree.h:770:15: error: static assertion failed: comparison object must be invocable as const)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 21:25:04 +
with message-id 
and subject line Bug#984229: fixed in mccs 1:1.1-10
has caused the Debian Bug report #984229,
regarding mccs: FTBFS: stl_tree.h:770:15: error: static assertion failed: 
comparison object must be invocable as const
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.)


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

Hi,

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


Relevant part (hopefully):
> g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs -fPIC 
> objs/cudf.tab.c -o objs/cudf.tab.o
> In file included from /usr/include/c++/12/set:60,
>  from libsrcs/cudf.h:18,
>  from libsrcs/cudf.y:14:
> /usr/include/c++/12/bits/stl_tree.h: In instantiation of ‘static const _Key& 
> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
> _Alloc>::_S_key(_Const_Link_type) [with _Key = CUDFVersionedPackage*; _Val = 
> CUDFVersionedPackage*; _KeyOfValue = std::_Identity; 
> _Compare = CUDFPackage_comparator; _Alloc = 
> std::allocator; _Const_Link_type = const 
> std::_Rb_tree_node*]’:
> /usr/include/c++/12/bits/stl_tree.h:1951:36:   required from 
> ‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator 
> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
> _Alloc>::_M_lower_bound(_Link_type, _Base_ptr, const _Key&) [with _Key = 
> CUDFVersionedPackage*; _Val = CUDFVersionedPackage*; _KeyOfValue = 
> std::_Identity; _Compare = CUDFPackage_comparator; 
> _Alloc = std::allocator; iterator = 
> std::_Rb_tree std::_Identity, CUDFPackage_comparator, 
> std::allocator >::iterator; _Link_type = 
> std::_Rb_tree_node*; _Base_ptr = 
> std::_Rb_tree_node_base*]’
> /usr/include/c++/12/bits/stl_tree.h:2531:36:   required from 
> ‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator 
> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::find(const _Key&) 
> [with _Key = CUDFVersionedPackage*; _Val = CUDFVersionedPackage*; _KeyOfValue 
> = std::_Identity; _Compare = CUDFPackage_comparator; 
> _Alloc = std::allocator; iterator = 
> std::_Rb_tree std::_Identity, CUDFPackage_comparator, 
> std::allocator >::iterator]’
> /usr/include/c++/12/bits/stl_set.h:795:25:   required from ‘std::set<_Key, 
> _Compare, _Alloc>::iterator std::set<_Key, _Compare, _Alloc>::find(const 
> key_type&) [with _Key = CUDFVersionedPackage*; _Compare = 
> CUDFPackage_comparator; _Alloc = std::allocator; 
> iterator = std::_Rb_tree std::_Identity, CUDFPackage_comparator, 
> std::allocator >::const_iterator; key_type = 
> CUDFVersionedPackage*]’
> libsrcs/cudf.y:117:36:   required from here
> /usr/include/c++/12/bits/stl_tree.h:770:15: error: static assertion failed: 
> comparison object must be invocable as const
>   770 |   is_invocable_v _Key&>,
>   |   
> ^
> /usr/include/c++/12/bits/stl_tree.h:770:15: note: ‘std::is_invocable_v CUDFPackage_comparator&, CUDFVersionedPackage* const&, CUDFVersionedPackage* 
> const&>’ evaluates to false
> make[1]: *** [makefile:179: objs/cudf.tab.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/01/mccs_1.1-9_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further 

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

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 21:25:04 +
with message-id 
and subject line Bug#984229: fixed in mccs 1:1.1-10
has caused the Debian Bug report #984229,
regarding mccs: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
  |^~
sources/pblib_solver.c:99:16: note: ‘sprintf’ output 31 or more bytes (assuming 
1051) into a destination of size 1024
   99 | sprintf(command, "cat %s >> %s; %s -f %s > %s 2> /dev/null",
  | ~~~^
  100 | ctpbfilename, pbfilename, pb_solver, pbfilename, 
pboutfilename);
  | 
~~~
g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs 
sources/removed_criteria.c -o objs/removed_criteria.o
sources/removed_criteria.c: In member function ‘virtual CUDFcoefficient 
removed_criteria::upper_bound()’:
sources/removed_criteria.c:98:70: warning: ‘*’ in boolean context, suggest ‘&&’ 
instead [-Wint-in-bool-context]
   98 | CUDFcoefficient removed_criteria::upper_bound() { return lambda_crit * 
(lambda_crit >= 0)?ub:lb; }
  |  
^~~~
sources/removed_criteria.c: In member function ‘virtual CUDFcoefficient 
removed_criteria::lower_bound()’:
sources/removed_criteria.c:101:70: warning: ‘*’ in boolean context, suggest 
‘&&’ instead [-Wint-in-bool-context]
  101 | CUDFcoefficient removed_criteria::lower_bound() { return lambda_crit * 
(lambda_crit >= 0)?lb:ub; }
  |  
^~~~
g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs 
sources/changed_criteria.c -o objs/changed_criteria.o
g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs 
sources/new_criteria.c -o objs/new_criteria.o
g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs 
sources/notuptodate_criteria.c -o objs/notuptodate_criteria.o
g++ -Wall -O6 -Wl,-z,relro -DUSELPSOLVE -c -Iobjs -Isources -Ilibsrcs 
sources/nunsat_criteria.c -o objs/nunsat_criteria.o
sources/nunsat_criteria.c: In member function ‘virtual void 
nunsat_criteria::initialize(CUDFproblem*, abstract_solver*)’:
sources/nunsat_criteria.c:86:29: warning: suggest explicit braces to avoid 
ambiguous ‘else’ [-Wdangling-else]
   86 | else if (comp(jpkg->first, (*disjunct)->version))
  | ^
sources/nunsat_criteria.c:81:20: warning: suggest explicit braces to avoid 
ambiguous ‘else’ [-Wdangling-else]
   81 | if (! self_depend)
  |^
sources/nunsat_criteria.c: In member function ‘virtual int 

Bug#1027273: marked as done (openvswitch: CVE-2022-4337 CVE-2022-4338)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 21:17:08 +
with message-id 
and subject line Bug#1027273: fixed in openvswitch 2.15.0+ds1-2+deb11u2
has caused the Debian Bug report #1027273,
regarding openvswitch: CVE-2022-4337 CVE-2022-4338
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.)


-- 
1027273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openvswitch
Version: 3.1.0~git20221212.739bcf2-3
Severity: grave
Tags: security upstream
Forwarded: https://github.com/openvswitch/ovs/pull/405
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for openvswitch.

Filling as RC to make sure the fix can reach bookworm release.

CVE-2022-4337[0]:
| Out-of-Bounds Read in Organization Specific TLV

CVE-2022-4338[1]:
| Integer Underflow in Organization Specific TLV

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-4337
https://www.cve.org/CVERecord?id=CVE-2022-4337
[1] https://security-tracker.debian.org/tracker/CVE-2022-4338
https://www.cve.org/CVERecord?id=CVE-2022-4338
[2] https://github.com/openvswitch/ovs/pull/405
[3] https://mail.openvswitch.org/pipermail/ovs-dev/2022-December/400596.html
[4] https://www.openwall.com/lists/oss-security/2022/12/20/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.15.0+ds1-2+deb11u2
Done: Thomas Goirand 

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 03 Oct 2022 12:59:27 +0200
Source: openvswitch
Architecture: source
Version: 2.15.0+ds1-2+deb11u2
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1027273
Changes:
 openvswitch (2.15.0+ds1-2+deb11u2) bullseye-security; urgency=medium
 .
   * Fix ovs-dpctl-top by removing 3 wrong hunks in py3-compat.patch.
   * CVE-2022-4337 & CVE-2022-4338: Out-of-Bounds Read and Integer Underflow in
 Organization Specific TLV. Added upstream patches (Closes: #1027273).
Checksums-Sha1:
 a3027ea346e4cdbc1b771d3323b7802d89bfbd72 3180 
openvswitch_2.15.0+ds1-2+deb11u2.dsc
 23e1e6493c66a7af4b454c473c34f1ed5de4b9cf 3721240 
openvswitch_2.15.0+ds1.orig.tar.xz
 e8514245add5f997f81832cb9bd321e3b492bf70 54040 
openvswitch_2.15.0+ds1-2+deb11u2.debian.tar.xz
 ed95acd0db0935ad1b5fc381752265ff642e47fc 21970 
openvswitch_2.15.0+ds1-2+deb11u2_amd64.buildinfo
Checksums-Sha256:
 6b9af72d052ed38cc35e309bca041e896d8859022b8f4b599d03b103e6114e1d 3180 
openvswitch_2.15.0+ds1-2+deb11u2.dsc
 801aeb7e4135f20ebb965df47527ce1118da25ac143a975113f4f0d2c7be62ab 3721240 
openvswitch_2.15.0+ds1.orig.tar.xz
 fb5580da1365fd9bbb1de0d1b17d6b0027b5659daa64eae8adebb908f423757d 54040 
openvswitch_2.15.0+ds1-2+deb11u2.debian.tar.xz
 4e5e33bac7f768e0601fb43da81a332d5a10a368c3f46b3e07e1db3a6502138b 21970 
openvswitch_2.15.0+ds1-2+deb11u2_amd64.buildinfo
Files:
 4322b65be1e8c2db43401253240cea24 3180 net optional 
openvswitch_2.15.0+ds1-2+deb11u2.dsc
 534a718be0dac829f71f02bc4e89fe1f 3721240 net optional 
openvswitch_2.15.0+ds1.orig.tar.xz
 024a68141a69d72c59aa854a4c681af6 54040 net optional 
openvswitch_2.15.0+ds1-2+deb11u2.debian.tar.xz
 d940001372210fbb4926a4d8aa5e7a03 21970 net optional 
openvswitch_2.15.0+ds1-2+deb11u2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmPBEIwACgkQ1BatFaxr
Q/4NHRAAj6txhSM5hwkldU/hMT/wNuPKSqndZy2FC4TrDXfzYGDUfROZk6x5ClKr
ozIZ/nsMBViJVTXPybhrNJnFhALW/CY3nLNuLbqqxkFfHZAqrHLdJf9qclBTvChd
i6RO/xnNzip9KmrfNA+8WSpgfK7Vuq46qIxKxKrix7VSq/V5297oYzS7kkFCzEBg

Processed: tagging 1026525

[Debian Bug Tracking System]

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

> tags 1026525 - ftbfs
Bug #1026525 [mitmproxy] AttributeError: module 'OpenSSL.SSL' has no attribute 
'SSLv2_METHOD'
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1025868: lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t

[Paul Gevers]

Hi Axel,

On 15-01-2023 23:07, Axel Beckert wrote:

TL;DR:


[...]

You're awesome. And indeed, what a shame of your time.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#1028993 marked as pending in libsbml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1028993 [src:libsbml] libsbml: (autopkgtest) needs update for Python 3.11
Added tag(s) pending.

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

Bug#1028993: marked as pending in libsbml

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/libsbml/-/commit/c14457053326c1564998373de81c4a3f32f5ccaf


d/control: bump preferred python3 version to 3.11.

Closes: #1028993


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1028993

Bug#1028683: marked as done (pytools: FTBFS: build-dependency not installable: python-numpy-doc)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 20:47:31 +
with message-id 
and subject line Bug#1028683: fixed in pytools 2022.1.14-2
has caused the Debian Bug report #1028683,
regarding pytools: FTBFS: build-dependency not installable: python-numpy-doc
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-python3, 
> dh-sequence-numpy3, dh-sequence-sphinxdoc, dh-python, python3-all, 
> python3-setuptools, python3-numpy, python3-decorator (>= 3.2.0), python3-six, 
> furo, python3-pytest, python3-typing-extensions, build-essential, fakeroot, 
> python3-doc, python-numpy-doc, python3-sphinx (>= 1.0.7+dfsg), 
> python3-sphinx-copybutton
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-python3, 
> dh-sequence-numpy3, dh-sequence-sphinxdoc, dh-python, python3-all, 
> python3-setuptools, python3-numpy, python3-decorator (>= 3.2.0), python3-six, 
> furo, python3-pytest, python3-typing-extensions, build-essential, fakeroot, 
> python3-doc, python-numpy-doc, python3-sphinx (>= 1.0.7+dfsg), 
> python3-sphinx-copybutton
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [960 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [521 B]
> Get:5 copy:/<>/apt_archive ./ Packages [581 B]
> Fetched 2062 B in 0s (154 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/pytools_2022.1.14-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

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

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

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

Debian distribution maintenance software
pp.
Tomasz Rybak  (supplier of updated pytools 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 

Bug#984229: mccs: diff for NMU version 1:1.1-9.1

[Ralf Treinen]

Hi Adrien,

On Mon, Jan 16, 2023 at 07:34:53PM +0200, Adrian Bunk wrote:

> I've prepared an NMU for mccs (versioned as 1:1.1-9.1) and uploaded
> it to DELAYED/14. Please feel free to tell me if I should cancel it.

thanks a lot, I just uploaded version 1.1-10, which includes your patch,
to unstable.

Cheers -Ralf.

Processed: reassign 1026525 to mitmproxy

[Debian Bug Tracking System]

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

> reassign 1026525 mitmproxy 6.0.2-1
Bug #1026525 [src:python-scrapy] python-scrapy: FTBFS: AttributeError: module 
'OpenSSL.SSL' has no attribute 'SSLv2_METHOD'. Did you mean: 'SSLv23_METHOD'?
Bug reassigned from package 'src:python-scrapy' to 'mitmproxy'.
No longer marked as found in versions python-scrapy/2.7.1-1.
Ignoring request to alter fixed versions of bug #1026525 to the same values 
previously set
Bug #1026525 [mitmproxy] python-scrapy: FTBFS: AttributeError: module 
'OpenSSL.SSL' has no attribute 'SSLv2_METHOD'. Did you mean: 'SSLv23_METHOD'?
Marked as found in versions mitmproxy/6.0.2-1.
> thanks
Stopping processing here.

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

Processed: retitle 1026525 to AttributeError: module 'OpenSSL.SSL' has no attribute 'SSLv2_METHOD'

[Debian Bug Tracking System]

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

> retitle 1026525 AttributeError: module 'OpenSSL.SSL' has no attribute 
> 'SSLv2_METHOD'
Bug #1026525 [mitmproxy] python-scrapy: FTBFS: AttributeError: module 
'OpenSSL.SSL' has no attribute 'SSLv2_METHOD'. Did you mean: 'SSLv23_METHOD'?
Changed Bug title to 'AttributeError: module 'OpenSSL.SSL' has no attribute 
'SSLv2_METHOD'' from 'python-scrapy: FTBFS: AttributeError: module 
'OpenSSL.SSL' has no attribute 'SSLv2_METHOD'. Did you mean: 'SSLv23_METHOD'?'.
> thanks
Stopping processing here.

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

Bug#1029044: gcc-12-cross-mipsen: source and binary version go out of sync

[Paul Gevers]

Source: gcc-12-cross-mipsen
Version: 1+c2
Severity: serious

Dear maintainer,

The current version in unstable is stuck, because the mips64el build
is kept in Uploaded state. Asking around on #d-buildd, I got the
following discussion:

[20:09:34]  mips64el 3days in uploaded state feels like an issue, 
right? https://buildd.debian.org/status/package.php?p=gcc-12-cross-mipsen
[20:18:32]  probably means dak rejected it
[20:18:45]  Your upload included the binary package 
cpp-12-mips-linux-gnu, version 12.2.0-13cross1, for mips64el,
[20:18:48]  however unstable already has version 12.2.0-14cross2.
[20:19:09]  
coccia:/srv/ftp-master.debian.org/queue/reject/gcc-12-cross-mipsen_3+c1_mips64el-buildd.changes.reason
[20:29:57]  the higher version is
[20:29:57]  Source: gcc-12-cross-mipsen (2+c1)
[20:30:23]  so the generated version numbers are broken
[20:32:07]  not for the first time afair
[[21:04:30]  adsb: thanks for looking; but the source is 3+c1, no? or 
did the older one generate a newer binary?

You may want to check your logic.

Paul

Processed: unarchiving 1023361, found 1023361 in 4.7.1-1

[Debian Bug Tracking System]

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

> unarchive 1023361
Bug #1023361 {Done: Gordon Ball } [src:jupyter-core] 
jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in 
JupyterApp
Unarchived Bug 1023361
> found 1023361 4.7.1-1
Bug #1023361 {Done: Gordon Ball } [src:jupyter-core] 
jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in 
JupyterApp
Marked as found in versions jupyter-core/4.7.1-1.
> thanks
Stopping processing here.

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

Bug#1029042: jenkins-job-builder: flaky autopkgtest (host dependent)

[Paul Gevers]

Source: jenkins-job-builder
Version: 3.11.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on amd64. The failures seem related on the host 
that runs the test. ci-worker13 is a beefy machine [1], while the other 
amd64 workers are much more moderate [2].


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://metal.equinix.com/product/servers/m3-large/
[2] https://aws.amazon.com/ec2/instance-types/m5/


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027902: marked as done (ns3 FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 19:00:23 +
with message-id 
and subject line Bug#1027902: fixed in ns3 3.37-1
has caused the Debian Bug report #1027902,
regarding ns3 FTBFS with Python 3.11 as default version
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.)


-- 
1027902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ns3
Version: 3.36.1+dfsg-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ns3=amd64=3.36.1%2Bdfsg-5%2Bb2=1672815346=0

...
In file included from /usr/include/python3.11/Python.h:44,
 from 
/<>/ns-3.36.1/build/src/core/bindings/ns3module.h:3,
 from 
/<>/ns-3.36.1/build/src/core/bindings/ns3module.cc:1:
/<>/ns-3.36.1/build/src/core/bindings/ns3module.cc: 
In function ‘PyObject* PyInit__core()’:
/usr/include/python3.11/object.h:136:30: error: 
lvalue required as left operand of assignment
  136 | #  define Py_TYPE(ob) Py_TYPE(_PyObject_CAST(ob))
  |   ~~~^~~~
/<>/ns-3.36.1/build/src/core/bindings/ns3module.cc:51869:5:
 note: in expansion of macro ‘Py_TYPE’
51869 | Py_TYPE(_Type) = _Type;
  | ^~~
/usr/include/python3.11/object.h:136:30: error: 
lvalue required as left operand of assignment
  136 | #  define Py_TYPE(ob) Py_TYPE(_PyObject_CAST(ob))
  |   ~~~^~~~
/<>/ns-3.36.1/build/src/core/bindings/ns3module.cc:52056:5:
 note: in expansion of macro ‘Py_TYPE’
52056 | Py_TYPE(_t_Type) = 
_tMeta_Type;
  | ^~~
/usr/include/python3.11/object.h:136:30: error: 
lvalue required as left operand of assignment
  136 | #  define Py_TYPE(ob) Py_TYPE(_PyObject_CAST(ob))
  |   ~~~^~~~
/<>/ns-3.36.1/build/src/core/bindings/ns3module.cc:52478:5:
 note: in expansion of macro ‘Py_TYPE’
52478 | Py_TYPE(_Type) = 
_Type;
  | ^~~
[ 46%] Building CXX object 
src/lte/CMakeFiles/liblte-obj.dir/model/lte-fr-soft-algorithm.cc.o
...
--- End Message ---
--- Begin Message ---
Source: ns3
Source-Version: 3.37-1
Done: Martin Quinson 

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

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

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated ns3 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: Sat, 14 Jan 2023 10:18:14 +0100
Source: ns3
Binary: libns3-dev libns3.37 libns3.37-dbgsym ns3 ns3-dbgsym ns3-doc
Architecture: source amd64 all
Version: 3.37-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 libns3-dev - Static and header files of ns-3
 libns3.37  - shared libraries of ns-3
 ns3- discrete-event network simulator for Internet systems
 ns3-doc- documentation for ns3
Closes: 1027902
Changes:
 ns3 (3.37-1) unstable; urgency=medium
 .
   * New upstream release.
 * Waf files are gone upstream, so we don't need to repack the tarfiles.
 * Re-enable the ns3 package, which content is now properly installed
   upstream.
 * Python bindings now depend on ccppy, which is not packaged in
   Debian, so this package does not provide these bindings anymore.
   Closes: #1027902 (even if not in a pleasant way).
   * d/control: bump Standards-Version to 4.6.2 (no change needed).
Checksums-Sha1:
 3195203f147042c7d3bd02e34569836ff022f8e3 2521 ns3_3.37-1.dsc
 2242b5a90ba9d85914c4b305d1853bfab9592160 39515477 ns3_3.37.orig.tar.bz2
 

Bug#1027118: marked as done (zabbix: FTBFS: error: invalid use of void expression)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 19:01:16 +
with message-id 

and subject line zabbix: FTBFS: error: invalid use of void expression
has caused the Debian Bug report #1027118,
regarding zabbix: FTBFS: error: invalid use of void expression
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=zabbix=amd64=1%3A6.0.10%2Bdfsg-1%2Bb1=1672133685=0

simple.c: In function ‘check_https’:
simple.c:180:65: error: invalid use of void expression
  180 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_USERAGENT, "Zabbix " ZABBIX_VERSION)) ||
  | ^
simple.c:181:69: error: invalid use of void expression
  181 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_URL, https_host)) ||
  | ^
simple.c:182:69: error: invalid use of void expression
  182 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_PORT, (long)port)) ||
  | ^
simple.c:183:69: error: invalid use of void expression
  183 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_NOBODY, 1L)) ||
  | ^
simple.c:184:69: error: invalid use of void expression
  184 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_SSL_VERIFYPEER, 0L)) ||
  | ^
simple.c:185:69: error: invalid use of void expression
  185 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_SSL_VERIFYHOST, 0L)) ||
  | ^
simple.c:186:69: error: invalid use of void expression
  186 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_TIMEOUT, (long)timeout)) ||
  | ^
simple.c:187:69: error: invalid use of void expression
  187 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
ZBX_CURLOPT_ACCEPT_ENCODING, "")))
  | ^
simple.c:196:73: error: invalid use of void expression
  196 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt 
= CURLOPT_INTERFACE, CONFIG_SOURCE_IP)))
  | 
^
make[6]: *** [Makefile:500: libsimplesysinfo_a-simple.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Fixed by curl 7.87.0-2.

I can't giveback on the failed builds on buildd.d.o, but I think it
auto-retries once the bug is resolved, right?!

Thank you,

-- 
Samuel Henrique --- End Message ---

Bug#1028099: marked as done ([libtepl-6-2] package upgrade error)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 19:00:33 +
with message-id 
and subject line Bug#1024388: fixed in tepl 6.4.0-5
has caused the Debian Bug report #1024388,
regarding [libtepl-6-2] package upgrade error
to be marked as done.

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

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


-- 
1024388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtepl-6-2
Version: 6.4.0-3
Severity: serious

Ran into an upgrade issue on Sid today. Seems libtepl-6-1 did not get
removed before trying to install libtepl-6-2, causing the libtepl-6-2
install to fail, and consequently cascading failures from there.

Output of first aptitude upgrade command:

```
$ sudo aptitude upgrade
Resolving dependencies...
The following NEW packages will be installed:
  libtepl-6-2{a} 
The following packages will be REMOVED:
  libtepl-6-1{u} 
The following packages will be upgraded:
  gedit gedit-plugin-bookmarks gedit-plugin-bracket-completion 
gedit-plugin-character-map 
  gedit-plugin-code-comment gedit-plugin-color-picker 
gedit-plugin-color-schemer 
  gedit-plugin-draw-spaces gedit-plugin-git gedit-plugin-join-lines 
gedit-plugin-multi-edit 
  gedit-plugin-session-saver gedit-plugin-smart-spaces gedit-plugin-synctex 
  gedit-plugin-terminal gedit-plugin-text-size gedit-plugin-word-completion 
  gedit-plugins-common gnustep-base-common gnustep-base-runtime imagemagick 
  imagemagick-6-common imagemagick-6.q16 libapache-pom-java libbcmail-java 
libbcpkix-java 
  libbcprov-java libbcutil-java libgnustep-base1.28 libmagick++-6.q16-8 
libmagickcore-6.q16-6 
  libmagickwand-6.q16-6 
The following packages are RECOMMENDED but will NOT be installed:
  libmagickcore-6.q16-6-extra 
32 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 16.3 MB of archives. After unpacking 1,024 B will be freed.
Do you want to continue? [Y/n/?] y
Get: 1 https://deb.debian.org/debian sid/main amd64 libtepl-6-2 amd64 6.4.0-3 
[122 kB]
Get: 2 https://deb.debian.org/debian sid/main amd64 gedit amd64 43.2-2+b1 [364 
kB]
Get: 3 https://deb.debian.org/debian sid/main amd64 gedit-plugins-common amd64 
43.1-1+b1 [293 kB]
Get: 4 https://deb.debian.org/debian sid/main amd64 gedit-plugin-draw-spaces 
amd64 43.1-1+b1 [19.9 kB]
Get: 5 https://deb.debian.org/debian sid/main amd64 imagemagick-6-common all 
8:6.9.11.60+dfsg-1.4 [165 kB]
Get: 6 https://deb.debian.org/debian sid/main amd64 libmagickcore-6.q16-6 amd64 
8:6.9.11.60+dfsg-1.4 [1,780 kB]
Get: 7 https://deb.debian.org/debian sid/main amd64 libmagickwand-6.q16-6 amd64 
8:6.9.11.60+dfsg-1.4 [407 kB]
Get: 8 https://deb.debian.org/debian sid/main amd64 gedit-plugin-bookmarks 
amd64 43.1-1+b1 [30.6 kB]
Get: 9 https://deb.debian.org/debian sid/main amd64 
gedit-plugin-bracket-completion amd64 43.1-1+b1 [17.9 kB]
Get: 10 https://deb.debian.org/debian sid/main amd64 gedit-plugin-character-map 
amd64 43.1-1+b1 [21.1 kB]
Get: 11 https://deb.debian.org/debian sid/main amd64 gedit-plugin-code-comment 
amd64 43.1-1+b1 [22.0 kB]
Get: 12 https://deb.debian.org/debian sid/main amd64 gedit-plugin-color-picker 
amd64 43.1-1+b1 [22.4 kB]
Get: 13 https://deb.debian.org/debian sid/main amd64 gedit-plugin-color-schemer 
amd64 43.1-1+b1 [18.9 kB]
Get: 14 https://deb.debian.org/debian sid/main amd64 gedit-plugin-git amd64 
43.1-1+b1 [24.4 kB]
Get: 15 https://deb.debian.org/debian sid/main amd64 gedit-plugin-join-lines 
amd64 43.1-1+b1 [22.1 kB]
Get: 16 https://deb.debian.org/debian sid/main amd64 gedit-plugin-multi-edit 
amd64 43.1-1+b1 [28.4 kB]
Get: 17 https://deb.debian.org/debian sid/main amd64 gedit-plugin-session-saver 
amd64 43.1-1+b1 [20.4 kB]
Get: 18 https://deb.debian.org/debian sid/main amd64 gedit-plugin-smart-spaces 
amd64 43.1-1+b1 [10.7 kB]
Get: 19 https://deb.debian.org/debian sid/main amd64 gedit-plugin-synctex amd64 
43.1-1+b1 [20.0 kB]
Get: 20 https://deb.debian.org/debian sid/main amd64 gedit-plugin-terminal 
amd64 43.1-1+b1 [20.6 kB]
Get: 21 https://deb.debian.org/debian sid/main amd64 gedit-plugin-text-size 
amd64 43.1-1+b1 [19.0 kB]
Get: 22 https://deb.debian.org/debian sid/main amd64 
gedit-plugin-word-completion amd64 43.1-1+b1 [24.6 kB]
Get: 23 https://deb.debian.org/debian sid/main amd64 libgnustep-base1.28 amd64 
1.28.1-2 [1,595 kB]
Get: 24 https://deb.debian.org/debian sid/main amd64 gnustep-base-runtime amd64 
1.28.1-2 [445 kB]
Get: 25 https://deb.debian.org/debian sid/main amd64 gnustep-base-common all 
1.28.1-2 [296 kB]
Get: 26 https://deb.debian.org/debian sid/main amd64 imagemagick-6.q16 amd64 

Bug#1024388: marked as done (libtepl-6-2: missing (unversioned) Breaks+Replaces: libtepl-6-0, libtepl-6-1)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 19:00:33 +
with message-id 
and subject line Bug#1024388: fixed in tepl 6.4.0-5
has caused the Debian Bug report #1024388,
regarding libtepl-6-2: missing (unversioned) Breaks+Replaces: libtepl-6-0, 
libtepl-6-1
to be marked as done.

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

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


-- 
1024388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtepl-6-1
Version: 6.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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 .../libtepl-6-1_6.2.0-2_amd64.deb ...
  Unpacking libtepl-6-1:amd64 (6.2.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/tepl-6.mo', which is 
also in package libtepl-6-0:amd64 6.1.2-1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libtepl-6-1_6.2.0-2_amd64.deb


The *.mo files have the same name in both packages.


cheers,

Andreas


libtepl-6-0=6.1.2-1+b2_libtepl-6-1=6.2.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tepl
Source-Version: 6.4.0-5
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated tepl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 13 Jan 2023 15:40:24 -0500
Source: tepl
Binary: libtepl-common
Architecture: source all
Version: 6.4.0-5
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libtepl-common - Text editor library for GTK (common files)
Closes: 1024388
Changes:
 tepl (6.4.0-5) experimental; urgency=medium
 .
   * Add libtepl-common package for smoother library transitions in the future
 (Closes: #1024388)
Checksums-Sha1:
 daee31265a01fcf24a14ab10f6698cb757f0704a 2562 tepl_6.4.0-5.dsc
 182841bc68e7559174f320dfa790e925333b451d 6352 tepl_6.4.0-5.debian.tar.xz
 54a22c041ef28bcac9d4a011483d9a9d1277eab5 35284 libtepl-common_6.4.0-5_all.deb
 cf6878f3a13d210c2edf9032782be53296235567 15483 tepl_6.4.0-5_all.buildinfo
Checksums-Sha256:
 6ba2d533caa3239f215d41b5e489ccb0ffc9e71e21660ea0ddac9313cc66461d 2562 
tepl_6.4.0-5.dsc
 67b39e43ef18d8485e2fa5f5b13b78f903419bf98787be9d7c219f94f9231525 6352 
tepl_6.4.0-5.debian.tar.xz
 e9988146cc18ead2cd0b7bc2c58df2576fe7b3ce275da631f3928d25e5f151cc 35284 
libtepl-common_6.4.0-5_all.deb
 1ceab310bf3d1ef51e70e8b73dec414d243fe5592432a176ddcf9489011619f0 15483 
tepl_6.4.0-5_all.buildinfo
Files:
 fd5b2e9d7c8aaff9fec8e4fa4178f4ea 2562 libs optional tepl_6.4.0-5.dsc
 d8b681c6e4c0b7e342a44ec92814e27b 6352 libs optional tepl_6.4.0-5.debian.tar.xz
 cd6eb94864cfae462877adfed0344291 35284 libs optional 
libtepl-common_6.4.0-5_all.deb
 4d0a9007e82b9f7e6a0985f202fc32df 15483 libs optional tepl_6.4.0-5_all.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmPB0BoACgkQ5mx3Wuv+
bH2NeQ/8DqHWvenzdKT1UWpKXcCqPVNF/kkIfUQZn2gzqmgbALqPAY4QRe9pxJJh
+9HGdU2ytakdh21kUs8+dyYTcubXcMw6SEQF0zzsi3lebn2UJSf9QDcQrnSJT6Y3
PAMoKeuBxVd4MkDzedCnJhP1fqG8dqYDcnTYbjJwVwxtu6UzTSpxusOE8vMMk0JN
5TX6LOFdv9P0bQMbGzG92TI6gdKI5T2ITxFp0tn36kWu7Thw0yIloF2XUI+3YfVW
C1wNycYyu7f7mhMALxfKqbqvMXCN4+3+7retnGiQQirdprt49s0ti7r/gzPv2fjU
6Or3LaVNT6d2RBNID/DqSS+utUPK9y6CrAR8/cBbchJp4hy1hco07Wsr6LKfOhWU
l7emefSAFoAYLtQ4eff6VZk4ROZqs1GeyzDcEEuSNEzSeDUkCHigKzNcJNt4IHWM
4IIC0h+5swbdd0SVuvnNptLtRFbeq6AxINb3u0ZeKmAQxHp9ppy84VtiDOAb2VG/

Bug#1029036: inventor: includes non-free source

[Bastian Germann]

Source: inventor
Version: 2.1.5-10-25
Severity: serious

Your package cointains stdmacro with the comment:

.\"Copyright (c) 1984 AT
.\"  All Rights Reserved
.\" THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT
.\"   The copyright notice above does not evidence any actual
.\"   or intended publication of such source code.

This file is non-free, so please repack to get rid of it.

Bug#1029035: ncl: includes non-free source

[Bastian Germann]

Source: ncl
Version: 6.6.2-12
Severity: serious

Your source package includes lex.yy_linux.c which has:

/*  Copyright (c) 1989 AT */
/*All Rights Reserved   */

/*  THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT */
/*  The copyright notice above does not evidence any*/
/*  actual or intended publication of such source code. */

Please repack getting rid of that file.

Bug#1028776: marked as done (python-googleapi: FTBFS: ValueError: invalid mode: 'rU')

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 18:35:48 +
with message-id 
and subject line Bug#1028776: fixed in python-googleapi 1.7.12-1
has caused the Debian Bug report #1028776,
regarding python-googleapi: FTBFS: ValueError: invalid mode: 'rU'
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.)


-- 
1028776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-googleapi
Version: 1.7.11-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 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 '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> nosetests3
> .E...S.E...SS
> ==
> ERROR: test_usage (tests.test__helpers.PositionalTests.test_usage)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test__helpers.py", line 54, in test_usage
> @_helpers.positional
>  ^^^
>   File "/<>/googleapiclient/_helpers.py", line 136, in positional
> args, _, _, defaults = inspect.getargspec(max_positional_args)
>^^
> AttributeError: module 'inspect' has no attribute 'getargspec'
> 
> ==
> ERROR: test_pickle_with_credentials (tests.test_discovery.Discovery)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_discovery.py", line 1407, in 
> test_pickle_with_credentials
> http = self._dummy_zoo_request()
>^
>   File "/<>/tests/test_discovery.py", line 1375, in 
> _dummy_zoo_request
> with open(os.path.join(DATA_DIR, 'zoo.json'), 'rU') as fh:
>  ^^
> ValueError: invalid mode: 'rU'
> 
> --
> Ran 229 tests in 0.481s
> 
> FAILED (SKIP=3, errors=2)
> make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/python-googleapi_1.7.11-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-googleapi
Source-Version: 1.7.12-1
Done: Laszlo Boszormenyi (GCS) 

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated 
python-googleapi 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, 16 Jan 2023 18:33:07 +0100
Source: python-googleapi
Architecture: source
Version: 1.7.12-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1018504 1028776
Changes:
 python-googleapi (1.7.12-1) unstable; urgency=medium
 .
  

Bug#1029034: snack: includes non-free source

[Bastian Germann]

Source: snack
Version: 2.2.10.20090623-dfsg-10
Severity: serious

jkFormant.c contains the following license info:

/* formant.c */
/*
 * This software has been licensed to the Centre of Speech Technology, KTH
 * by AT Corp. and Microsoft Corp. with the terms in the accompanying
 * file BSD.txt, which is a BSD style license.
 *
 *"Copyright (c) 1987-1990  AT, Inc.
 *"Copyright (c) 1986-1990  Entropic Speech, Inc.
 *"Copyright (c) 1990-1994  Entropic Research Laboratory, Inc.
 *   All rights reserved"
 *
 * Written by:  David Talkin
 * Revised by: John Shore
 *
 */

[...]

/*  Copyright (c) 1987, 1988, 1989 AT */
/*All Rights Reserved   */

/*  THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT */
/*  The copyright notice above does not evidence any*/
/*  actual or intended publication of such source code. */

/* downsample.c */


While the file part that is copied from formant.c is okay to be included in 
Debian, the part from downsample.c is not.
Please repack the source package getting rid of the file.

Bug#1029031: dcap: includes non-free source

[Bastian Germann]

There are more affected files in plugins/gssapi. I guess you have to get rid of 
dcap-tunnel-gsi.
As you are the maintainer for the only reverse dependency gfal2-plugin-dcap you 
can coordinate the uploads.

Bug#1029031: dcap: includes non-free source

[Bastian Germann]

Source: dcap
Severity: serious
Version: 2.47.12-4

plugins/gssapi/gssIoTunnel.c has the following comment:

 *   Copyright (c) 2000,2001,2002 DESY Hamburg DMG-Division
 *   All rights reserved.
 *
 *   THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF
 * DESY Hamburg DMG-Division
 *
 * Copyright (c) 1997 - 2002 Kungliga Tekniska H�gskolan (Royal Institute of
 * Technology, Stockholm, Sweden). All rights reserved.

Please repack the source package to get rid of the file.

Bug#1021079: NMU w/o ppc64el?

[Adam Borowski]

On Mon, Jan 16, 2023 at 08:26:37AM +0200, Konstantinos Margaritis wrote:
> On 15/1/23 03:33, Adam Borowski wrote:
> > Hi!
> > As you're apparently too busy to either fix ppc or suggest a different plan,
> > I'd make a NMU dropping ppc64el for now so the package can be released with
> > Bookworm.
> > 
> > Please say if I shouldn't.

> It is true that I am busy during this period, which may explain the lack of
> communication. Now regarding vectorscan w/o ppc64le, I have 2 serious bugs I
> want to fix before a new version upload (5.4.9), one is on Arm (a regression
> compared to x86) and the other is the failure on ppc64le. How long do I have
> to make an upload and ensure bookworm release? If that is too soon, then I
> will make an upload asap myself disabling ppc64le until I fix this locally.

Feb 12 is the cut-off; the package must be in testing at that time.  Then if
you have autopkgtests (vectorscan does), there's two more months before hard
freeze.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄

Bug#1027383: xen-tools: FTBFS in bullseye (missing build-depends on mount)

[Santiago Vila]

Hi.

The relevant paragraph in Policy is this one:

If build-time dependencies are specified, it must be possible to build the 
package and produce working binaries on a system  with only essential and 
build-essential packages installed and also those required to satisfy the 
build-time relationships (including any implied relationships).

Note that this is a MUST requirement in policy.

Moreover, this policy 4.2 item is a release goal:

Packages must list any packages they require to build beyond those
that are "build-essential" in the appropriate Build-Depends: fields.
Ref: 4.2

Source: https://release.debian.org/testing/rc_policy.txt

So if you want to downgrade the bug, go ahead, but as explained,
it would be wrong.

Thanks.

Bug#1026103: aflplusplus: FTBFS on s390x

[Adrian Bunk]

On Sun, Jan 15, 2023 at 12:12:39AM +0100, Bastian Germann wrote:
>...
> So the issue is
> [!] LTO llvm_mode failed
> [!] llvm_mode LTO instrumentlist feature compilation failed
> [!] llvm_mode LTO persistent mode feature compilation failed

The Ubuntu diff contains a change that was likely done to workaround 
this issue:

aflplusplus (4.04c-2ubuntu2) lunar; urgency=medium

  * Disable lld support on s390x for now, making the build fail.

 -- Gianfranco Costamagna   Wed, 21 Dec 2022 10:40:50 
+0100

cu
Adrian

Bug#1028732: marked as done (pyopencl: FTBFS: build-dependency not installable: python-numpy-doc)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 17:34:47 +
with message-id 
and subject line Bug#1028732: fixed in pyopencl 2022.3.1-2
has caused the Debian Bug report #1028732,
regarding pyopencl: FTBFS: build-dependency not installable: python-numpy-doc
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-sequence-numpy3, 
> dh-sequence-python3, mesa-common-dev, ocl-icd-opencl-dev | opencl-dev, 
> opencl-c-headers, pybuild-plugin-pyproject, python3-all-dev, python3-pybind11 
> (>= 2.5.0), python3-setuptools, pocl-opencl-icd | mesa-opencl-icd, 
> python3-mako, python3-pytest (>= 7), python3-pytools (>= 2021.2.7), 
> build-essential, fakeroot, dh-sequence-sphinxdoc, jdupes, python-mako-doc, 
> python-numpy-doc, python3-doc, python3-sphinx, python3-sphinx-copybutton
> Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-numpy3, 
> dh-sequence-python3, mesa-common-dev, ocl-icd-opencl-dev, opencl-c-headers, 
> pybuild-plugin-pyproject, python3-all-dev, python3-pybind11 (>= 2.5.0), 
> python3-setuptools, pocl-opencl-icd, python3-mako, python3-pytest (>= 7), 
> python3-pytools (>= 2021.2.7), build-essential, fakeroot, 
> dh-sequence-sphinxdoc, jdupes, python-mako-doc, python-numpy-doc, 
> python3-doc, python3-sphinx, python3-sphinx-copybutton
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [609 B]
> Get:5 copy:/<>/apt_archive ./ Packages [626 B]
> Fetched 2198 B in 0s (176 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/pyopencl_2022.3.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

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

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

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

Debian distribution maintenance software
pp.
Andreas 

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 997282 libmediainfo0v5
Bug #997282 [src:qnapi] qnapi: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libmediainfo.so: 
undefined reference to `tfsxml_value'
Bug reassigned from package 'src:qnapi' to 'libmediainfo0v5'.
No longer marked as found in versions qnapi/0.2.3-2.
Ignoring request to alter fixed versions of bug #997282 to the same values 
previously set
> unarchive 995863
Bug #995863 {Done: Chow Loong Jin } [libmediainfo0v5] 
libmediainfo-dev: Missing tfsxml_* symbols
Unarchived Bug 995863
> forcemerge 995863 997282
Bug #995863 {Done: Chow Loong Jin } [libmediainfo0v5] 
libmediainfo-dev: Missing tfsxml_* symbols
Bug #997282 [libmediainfo0v5] qnapi: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libmediainfo.so: 
undefined reference to `tfsxml_value'
Set Bug forwarded-to-address to 
'https://github.com/MediaArea/MediaInfoLib/pull/1434'.
Marked Bug as done
Added tag(s) fixed-upstream.
Bug #995863 {Done: Chow Loong Jin } [libmediainfo0v5] 
libmediainfo-dev: Missing tfsxml_* symbols
Added tag(s) bookworm, sid, and ftbfs.
Merged 995863 997282
> affects 995863 src:qnapi
Bug #995863 {Done: Chow Loong Jin } [libmediainfo0v5] 
libmediainfo-dev: Missing tfsxml_* symbols
Bug #997282 {Done: Chow Loong Jin } [libmediainfo0v5] 
qnapi: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libmediainfo.so: 
undefined reference to `tfsxml_value'
Added indication that 995863 affects src:qnapi
Added indication that 997282 affects src:qnapi
> thanks
Stopping processing here.

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

Processed: mccs: diff for NMU version 1:1.1-9.1

[Debian Bug Tracking System]

Processing control commands:

> tags 984229 + patch
Bug #984229 [src:mccs] mccs: ftbfs with GCC-11
Bug #1027622 [src:mccs] mccs: FTBFS: stl_tree.h:770:15: error: static assertion 
failed: comparison object must be invocable as const
Added tag(s) patch.
Added tag(s) patch.
> tags 984229 + pending
Bug #984229 [src:mccs] mccs: ftbfs with GCC-11
Bug #1027622 [src:mccs] mccs: FTBFS: stl_tree.h:770:15: error: static assertion 
failed: comparison object must be invocable as const
Added tag(s) pending.
Added tag(s) pending.

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

Bug#984229: mccs: diff for NMU version 1:1.1-9.1

[Adrian Bunk]

Control: tags 984229 + patch
Control: tags 984229 + pending

Dear maintainer,

I've prepared an NMU for mccs (versioned as 1:1.1-9.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru mccs-1.1/debian/changelog mccs-1.1/debian/changelog
--- mccs-1.1/debian/changelog	2020-05-28 12:52:06.0 +0300
+++ mccs-1.1/debian/changelog	2023-01-16 19:28:52.0 +0200
@@ -1,3 +1,12 @@
+mccs (1:1.1-9.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with -std=gnu++14 to workaround FTBFS with gcc >= 11.
+(Closes: #984229)
+  * Build with -g to add debug symbols to mccs-dbgsym.
+
+ -- Adrian Bunk   Mon, 16 Jan 2023 19:28:52 +0200
+
 mccs (1:1.1-9) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru mccs-1.1/debian/rules mccs-1.1/debian/rules
--- mccs-1.1/debian/rules	2020-05-28 12:52:06.0 +0300
+++ mccs-1.1/debian/rules	2023-01-16 19:28:52.0 +0200
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+export DEB_LDFLAGS_MAINT_APPEND += -std=gnu++14 -g
+
 %:
 	dh $@ --no-parallel
 

Bug#1029021: mutt-wizard: /usr/bin/mailsync is already shipped by the mailsync package

[Andreas Beckmann]

Package: mutt-wizard
Version: 3.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../mutt-wizard_3.3.1-1_all.deb ...
  Unpacking mutt-wizard (3.3.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/mutt-wizard_3.3.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/mailsync', which is also in package mailsync 
5.2.7-3.1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/mutt-wizard_3.3.1-1_all.deb

These files are in conflict:

  /usr/bin/mailsync
  /usr/share/man/man1/mailsync.1.gz


cheers,

Andreas


mailsync=5.2.7-3.1+b1_mutt-wizard=3.3.1-1.log.gz
Description: application/gzip

Bug#1028146: marked as done (collectd FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 17:05:46 +
with message-id 
and subject line Bug#1028146: fixed in collectd 5.12.0-12
has caused the Debian Bug report #1028146,
regarding collectd FTBFS with Python 3.11 as default version
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.)


-- 
1028146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.12.0-11
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/collectd.html

...
In file included from src/python.c:36:
src/cpython.h:29:10: fatal error: longintrepr.h: No such file or directory
   29 | #include 
  |  ^~~
compilation terminated.
make[2]: *** [Makefile:8457: src/python_la-python.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: collectd
Source-Version: 5.12.0-12
Done: Bernd Zeimetz 

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

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

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated collectd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Jan 2023 16:54:46 +0100
Source: collectd
Architecture: source
Version: 5.12.0-12
Distribution: unstable
Urgency: medium
Maintainer: Collectd Packaging Team 
Changed-By: Bernd Zeimetz 
Closes: 1028146
Changes:
 collectd (5.12.0-12) unstable; urgency=medium
 .
   * [d077f5d] Add lintian override for the java plugin.
   * [6ebe59a] Remove removed debconf questions from translations
   * [0c5f9dc] collectd-core: debconfig is used in postrm only.
 Override lintian errors.
   * [6be4222] Add package name to lintian overrides
   * [bda81fa] Migrate to dh / debhelper compat 13
   * [074299d] Fix building with python 3.11 (Closes: #1028146)
   * [69e6716] Move dh_install to the appropriate place
   * [45ea76f] Use debian/tmp for header/lib updates
Checksums-Sha1:
 746f7850594bd454d8207fe70800c50efd0d 4150 collectd_5.12.0-12.dsc
 61dcadddc9f25a63944e0fbe4f60250b2961ddfb 80692 collectd_5.12.0-12.debian.tar.xz
 81a8e0fbc6f9bfb37d1f3d5bc7857e599b3ec193 28451 
collectd_5.12.0-12_source.buildinfo
Checksums-Sha256:
 c522bc8380de298fe20add52d989fe5531cc1ac8cb88372f9d5af8bdea71867b 4150 
collectd_5.12.0-12.dsc
 821b2542b0efcf1eda5e7b43d5c4272f9327703dce9dcd6c9594a05d938197d4 80692 
collectd_5.12.0-12.debian.tar.xz
 4783c73fb0a0829c544de2c320c35d71bef27df35c0608dea9785dfbdd00a2d8 28451 
collectd_5.12.0-12_source.buildinfo
Files:
 20a985c16fb8f2becb50ee1efd8b733d 4150 utils optional collectd_5.12.0-12.dsc
 8445812c376083ceb6ef23b149a9e376 80692 utils optional 
collectd_5.12.0-12.debian.tar.xz
 99fad74bf261cae87a3a13b25d1e37c4 28451 utils optional 
collectd_5.12.0-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAmPFf4gACgkQ6zYXGm/5
Q19vYxAApVZlQiw4+eAzUDVXVw5+nu9ZHsU0SVeqrXSTnGeFaGYeyTC4iVozXSad
lAgrXnNfHRQNRNXKpxmz3+OYs+WY/y9SBNozsKHi7SrzM/FEGIs+6gXMB2JFKtFr
EIVmbXN6Xyv5C43Jc2Sv45UfSADITl3XNwBa8volsXODgbeOCIo71UPHxhVisBwc
nd+EDnmEVUFAu3nytZ2KZxJ8R5wEv4/kzRYmnIw/MmB4futwo+kP68iTnutdIlVj
Y6NDq5Z46YUcmDcJtTV1wQoJpRvG2sNTJGgJer4HrdFLKQIvv1kkW/vLt12JdhlW
D8Dw3XA76WZG/5zn7epbH0/gLZXOGQ44DjOgFnYObjgA2Fk0ybV/vopzG0wA4Ksr
9hBtUYfW2HhLLivthLbrj1hU5pOuXlP+uJY6gQF0minpvGuYllY52dUEYvXbDrIN
010JlGCaU5EOeFcQzwMkw0O2bC/IG0UScjYgV1Tmdrqeonyrbo9hAH6UPPTeiMIJ
HbCyZerr+wdWqRKqy8Ms0HHqkmi58EpTb9Ruu+p75TNd9zkfA7XkX5+1ZL8TVisT
k7bDrkvdRZBeBoUdGwPZnR24ytb4w/sOAaFtKfGAmKfS9/H4oSmEoxpTuNGdf5Y0
GF/uTne44z6+LC0SC4dWqCQzcfzCRkCdDN6o1wZUx0Yks9OEV0o=
=vjgy
-END PGP SIGNATURE End Message ---

Bug#1027383: xen-tools: FTBFS in bullseye (missing build-depends on mount)

[Andreas Henriksson]

Hello Santiago Vila,

While I do consider this a valid (wishlist) bug report,
...

On Fri, Dec 30, 2022 at 07:04:32PM +0100, Santiago Vila wrote:
> Package: src:xen-tools
> Version: 4.9-1
> Severity: serious
> Tags: ftbfs patch
[...]
> CPUs, using a reduced chroot with only build-essential packages (plus
> debhelper).
[...]

This IMHO means you're using an *unsupported* system setup!

None of the debootstrap variants lacks `Priority: required` packages and
I don't think this warrants a release-critical severity. (You might
argue about the exact wording of policy, but I think you should better
do that in a policy bug report or their mailing list. This is not a
practical problem until you use an unsupported setup, which means you
get to keep all the pieces. The name of the priority level should be
pretty self-explanatory - *required*, not recommended.)

As already mentioned, I think wishlist is the proper severity.
(And as said, I don't mind this being considered a bug or fixing it
which is simple... however with a relevant severity.)

Regards,
Andreas Henriksson

Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andreas Tille]

Hi Thiago,

Am Mon, Jan 16, 2023 at 11:08:35AM -0300 schrieb Thiago Franco Moraes:
> Done! I removed both python3-theano and python3-keras.

Thanks for the quick response.  Autopkgtest currently fails due to

  Bug #1027851  pytorch FTBFS with Python 3.11 as default version

I think, I'll wait a bit until this is clarified.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1029015: qtmir-tests: Depends on NBS package python3-mir-perf-framework

[Scott Kitterman]

Package: qtmir-tests
Version: 0.8.0~git20230115.30c2337-1
Severity: serious
Justification: Policy 3.5

qtmir-tests depends on python3-mir-perf-framework which is no longer
built by the mir package.  Once it's decrufted, the package will not be
installable.  Please either drop the dependency or coordinate with the
mir maintainers to get python3-mir-perf-framework restored.

Scott K

Processed: tagging 1028451, bug 1028451 is forwarded to https://gitlab.freedesktop.org/drm/amd/-/issues/2171

[Debian Bug Tracking System]

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

> tags 1028451 + upstream
Bug #1028451 [src:linux] 2nd DisplayPort doesn't get video
Added tag(s) upstream.
> forwarded 1028451 https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Bug #1028451 [src:linux] 2nd DisplayPort doesn't get video
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/amd/-/issues/2171'.
> thanks
Stopping processing here.

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

Bug#1029011: python3-opengl: GLUT import error on Wayland

[Sebastian Kuzminsky]

Package: python3-opengl
Version: 3.1.6+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: s...@highlab.com


GLUT fails to import on Wayland (using EGL), but it works if you force
it to GLX:

  $ echo $XDG_SESSION_TYPE
  wayland

  $ python3 -c 'from OpenGL.GLUT import *'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/OpenGL/GLUT/__init__.py", line 5, in 

  from OpenGL.GLUT.fonts import *
File "/usr/lib/python3/dist-packages/OpenGL/GLUT/fonts.py", line 20, in 

  p = platform.getGLUTFontPointer( name )
File "/usr/lib/python3/dist-packages/OpenGL/platform/baseplatform.py", line 
350, in getGLUTFontPointer
  raise NotImplementedError(
  NotImplementedError: Platform does not define a GLUT font retrieval function

  $ PYOPENGL_PLATFORM=x11 python3 -c 'from OpenGL.GLUT import *; print("no 
problem")'
  no problem


Looking at OpenGL.platform.egl[0] there is indeed no
`getGLUTFontPointer()` function, unlike in OpenGL.platform.glx[1] where
the function *does* exist.

0: ,
1: 

The problem is not present in 3.1.5 (e.g. in Bullseye), because the
older platform detection code there does not try to detect Wayland and
so chooses GLX (which works) instead of EGL (which fails):

3.1.5:
* 

* 


3.1.6:
* 

* 


Reported to upstream here: 


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

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

Versions of packages python3-opengl depends on:
ii  libgl1  1.5.0-1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  python3 3.10.6-3+b1

python3-opengl recommends no packages.

Versions of packages python3-opengl suggests:
pn  libgle3
ii  python3-numpy  1:1.23.5-2
ii  python3-tk 3.10.8-1

-- no debconf information

Bug#1028904: pillow: Lost tiff support after binNMU with tiff 4.5.0

[Bastian Germann]

I am uploading a NMU with the attached debdiff to DELAYED/10 to fix this.diff -Nru pillow-9.4.0/debian/changelog pillow-9.4.0/debian/changelog
--- pillow-9.4.0/debian/changelog   2023-01-03 10:06:46.0 +0100
+++ pillow-9.4.0/debian/changelog   2023-01-16 16:29:25.0 +0100
@@ -1,3 +1,10 @@
+pillow (9.4.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Handle more than one directory returned by pkg-config (Closes: #1028904).
+
+ -- Bastian Germann   Mon, 16 Jan 2023 16:29:25 +0100
+
 pillow (9.4.0-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru pillow-9.4.0/debian/patches/pkg-config-multiarch.diff 
pillow-9.4.0/debian/patches/pkg-config-multiarch.diff
--- pillow-9.4.0/debian/patches/pkg-config-multiarch.diff   1970-01-01 
01:00:00.0 +0100
+++ pillow-9.4.0/debian/patches/pkg-config-multiarch.diff   2023-01-16 
16:20:19.0 +0100
@@ -0,0 +1,63 @@
+From 04cf5e2cfc5dc1676efd9f5c8d605ddfccb0f9ee Mon Sep 17 00:00:00 2001
+From: Bas Couwenberg 
+Date: Sat, 14 Jan 2023 19:09:43 +0100
+Subject: Handle more than one directory returned by pkg-config.
+
+tiff (4.5.0-1) in Debian results in two include directories being returned:
+```
+-I/usr/include/x86_64-linux-gnu -I/usr/include
+```
+---
+ setup.py | 24 +++-
+ 1 file changed, 15 insertions(+), 9 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 243365681..b4ebbb9c2 100755
+--- a/setup.py
 b/setup.py
+@@ -263,18 +263,20 @@ def _pkg_config(name):
+ if not DEBUG:
+ command_libs.append("--silence-errors")
+ command_cflags.append("--silence-errors")
+-libs = (
++libs = re.split(
++r"\s*-L",
+ subprocess.check_output(command_libs, stderr=stderr)
+ .decode("utf8")
+-.strip()
+-.replace("-L", "")
++.strip(),
+ )
+-cflags = (
+-subprocess.check_output(command_cflags)
++libs.remove("")
++cflags = re.split(
++r"\s*-I",
++subprocess.check_output(command_cflags, stderr=stderr)
+ .decode("utf8")
+-.strip()
+-.replace("-I", "")
++.strip(),
+ )
++cflags.remove("")
+ return libs, cflags
+ except Exception:
+ pass
+@@ -473,8 +475,12 @@ class pil_build_ext(build_ext):
+ else:
+ lib_root = include_root = root
+ 
+-_add_directory(library_dirs, lib_root)
+-_add_directory(include_dirs, include_root)
++if lib_root is not None:
++for lib_dir in lib_root:
++_add_directory(library_dirs, lib_dir)
++if include_root is not None:
++for include_dir in include_root:
++_add_directory(include_dirs, include_dir)
+ 
+ # respect CFLAGS/CPPFLAGS/LDFLAGS
+ for k in ("CFLAGS", "CPPFLAGS", "LDFLAGS"):
+-- 
+2.30.2
+
diff -Nru pillow-9.4.0/debian/patches/series pillow-9.4.0/debian/patches/series
--- pillow-9.4.0/debian/patches/series  2022-10-21 17:53:14.0 +0200
+++ pillow-9.4.0/debian/patches/series  2023-01-16 16:27:58.0 +0100
@@ -4,3 +4,4 @@
 no-sphinx-removed-in.diff
 no-sphinx-opengraph.diff
 no-sphinx-furo.diff
+pkg-config-multiarch.diff

Bug#1029010: llvm-toolchain-15: autopkgtest regression

[Adrian Bunk]

Source: llvm-toolchain-15
Version: 1:15.0.7-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-15/30436521/log.gz

...
In file included from cout.cpp:1:
In file included from /usr/include/wasm32-wasi/c++/v1/iostream:41:
In file included from /usr/include/wasm32-wasi/c++/v1/ios:221:
In file included from /usr/include/wasm32-wasi/c++/v1/__locale:18:
In file included from /usr/include/wasm32-wasi/c++/v1/memory:841:
In file included from /usr/include/wasm32-wasi/c++/v1/__algorithm/copy.h:12:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__algorithm/unwrap_iter.h:13:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/iterator_traits.h:14:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/incrementable_traits.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/concepts:133:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__concepts/arithmetic.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/type_traits:421:
In file included from /usr/include/wasm32-wasi/c++/v1/__functional/invoke.h:17:
In file included from /usr/include/wasm32-wasi/c++/v1/__type_traits/decay.h:16:
/usr/include/wasm32-wasi/c++/v1/__type_traits/is_array.h:40:22: error: 
reference to unresolved using declaration
template  struct _LIBCPP_TEMPLATE_VIS is_array<_Tp[_Np]>
 ^
/usr/include/wasm32-wasi/c++/v1/cstddef:52:1: note: using declaration annotated 
with 'using_if_exists' here
using ::size_t _LIBCPP_USING_IF_EXISTS;
^
In file included from cout.cpp:1:
In file included from /usr/include/wasm32-wasi/c++/v1/iostream:41:
In file included from /usr/include/wasm32-wasi/c++/v1/ios:221:
In file included from /usr/include/wasm32-wasi/c++/v1/__locale:18:
In file included from /usr/include/wasm32-wasi/c++/v1/memory:841:
In file included from /usr/include/wasm32-wasi/c++/v1/__algorithm/copy.h:12:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__algorithm/unwrap_iter.h:13:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/iterator_traits.h:14:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__iterator/incrementable_traits.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/concepts:133:
In file included from 
/usr/include/wasm32-wasi/c++/v1/__concepts/arithmetic.h:15:
In file included from /usr/include/wasm32-wasi/c++/v1/type_traits:421:
In file included from /usr/include/wasm32-wasi/c++/v1/__functional/invoke.h:17:
In file included from /usr/include/wasm32-wasi/c++/v1/__type_traits/decay.h:20:
/usr/include/wasm32-wasi/c++/v1/__type_traits/remove_extent.h:25:22: error: 
reference to unresolved using declaration
template  struct _LIBCPP_TEMPLATE_VIS 
remove_extent<_Tp[_Np]>
 ^
/usr/include/wasm32-wasi/c++/v1/cstddef:52:1: note: using declaration annotated 
with 'using_if_exists' here
using ::size_t _LIBCPP_USING_IF_EXISTS;
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
autopkgtest [04:43:27]: test command1: ---]
autopkgtest [04:43:27]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
...
autopkgtest [04:47:28]:  summary
command1 FAIL non-zero exit status 1
integration-test-suite-test PASS
cmake-test   PASS
command2 PASS
command3 PASS

Bug#1028368: marked as done (dahdi-dkms fails to install after arrival of 6.1.0-1 kernel)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 15:04:40 +
with message-id 
and subject line Bug#1028368: fixed in dahdi-linux 1:2.11.1.0.20170917~dfsg-8.1
has caused the Debian Bug report #1028368,
regarding dahdi-dkms fails to install after arrival of 6.1.0-1 kernel
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.)


-- 
1028368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dahdi-dkms
Version: 1:2.11.1.0.20170917~dfsg-8
Severity: normal

Dear Maintainer,

as title says

thanks,
cs

mc36@noti:~$ sudo apt install dahdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libecj-java libtonezone2.0 linux-headers-6.0.0-5-common
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  dahdi-linux
The following NEW packages will be installed:
  dahdi-dkms dahdi-linux
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/859 kB of archives.
After this operation, 6,213 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package dahdi-dkms.
(Reading database ... 801204 files and directories currently installed.)
Preparing to unpack .../dahdi-dkms_1%3a2.11.1.0.20170917~dfsg-8_all.deb ...
Unpacking dahdi-dkms (1:2.11.1.0.20170917~dfsg-8) ...
Selecting previously unselected package dahdi-linux.
Preparing to unpack .../dahdi-linux_1%3a2.11.1.0.20170917~dfsg-8_all.deb ...
Unpacking dahdi-linux (1:2.11.1.0.20170917~dfsg-8) ...
Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-8) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-8 DKMS files...
Building for 6.1.0-1-amd64
Building initial module for 6.1.0-1-amd64
Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64)
Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/make.log for more
information.
dpkg: error processing package dahdi-dkms (--configure):
 installed dahdi-dkms package post-installation script subprocess returned
error exit status 10
dpkg: dependency problems prevent configuration of dahdi-linux:
 dahdi-linux depends on dahdi-dkms | dahdi-source; however:
  Package dahdi-dkms is not configured yet.
  Package dahdi-source is not installed.

dpkg: error processing package dahdi-linux (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 dahdi-dkms
 dahdi-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)
mc36@noti:~$ cat /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/make.log
DKMS make.log for dahdi-2.11.1.0.20170917~dfsg-8 for kernel 6.1.0-1-amd64
(x86_64)
Tue Jan 10 04:47:05 AM CET 2023
make -C /lib/modules/6.1.0-1-amd64/build
KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi
DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/include
DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes
modules DAHDI_BUILD_ALL=m
make[1]: Entering directory '/usr/src/linux-headers-6.1.0-1-amd64'
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o
  CC [M]
/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o
  CC [M]

Bug#1028978: marked as done (libomxil-bellagio FTBFS on mipsel: error: ‘__builtin_strncpy’ destination unchanged after copying no bytes [-Werror=stringop-truncation])

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 15:05:35 +
with message-id 
and subject line Bug#1028978: fixed in libomxil-bellagio 0.9.3-8
has caused the Debian Bug report #1028978,
regarding libomxil-bellagio FTBFS on mipsel: error: ‘__builtin_strncpy’ 
destination unchanged after copying no bytes [-Werror=stringop-truncation]
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.)


-- 
1028978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libomxil-bellagio
Version: 0.9.3-7
Severity: serious
Tags: ftbfs

Hi,

libomxil-bellagio fails to build form source when built on mipsel. A
build ends as follows:

| gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
-DOMXILCOMPONENTSPATH=\"/usr/lib/mipsel-linux-gnu/libomxil-bellagio0/\" 
-I../include -g -O2 -ffile-prefix-map=/root/libomxil-bellagio-0.9.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror 
-DCONFIG_DEBUG_LEVEL=0 -c -o omxregister_bellagio-omxregister.o `test -f 
'omxregister.c' || echo './'`omxregister.c
| In file included from /usr/include/string.h:535,
|  from omxregister.c:42:
| In function ‘strncpy’,
| inlined from ‘showComponentsList’ at omxregister.c:110:3,
| inlined from ‘main’ at omxregister.c:454:9:
| /usr/include/mipsel-linux-gnu/bits/string_fortified.h:95:10: error: 
‘__builtin_strncpy’ destination unchanged after copying no bytes 
[-Werror=stringop-truncation]
|95 |   return __builtin___strncpy_chk (__dest, __src, __len,
|   |  ^~
|96 |   __glibc_objsize (__dest));
|   |   ~
| cc1: all warnings being treated as errors
| make[4]: *** [Makefile:719: omxregister_bellagio-omxregister.o] Error 1
| make[4]: Leaving directory '/root/libomxil-bellagio-0.9.3/src'
| make[3]: *** [Makefile:776: all-recursive] Error 1
| make[3]: Leaving directory '/root/libomxil-bellagio-0.9.3/src'
| make[2]: *** [Makefile:495: all-recursive] Error 1
| make[2]: Leaving directory '/root/libomxil-bellagio-0.9.3'
| make[1]: *** [Makefile:381: all] Error 2
| make[1]: Leaving directory '/root/libomxil-bellagio-0.9.3'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:9: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

If you look at https://crossqa.debian.net/src/libomxil-bellagio, you can
guess that this is not entirely mipsel-specific, but probably also a
FTBFS on ppc64el and s390x. That said, I have only reproduced it on
mipsel and thus am filing it on mipsel.

A native build on amd64 succeeds.

I also briefly looked into it and couldn' really make sense of why gcc
thinks that the len parameter would become 0 here. Maybe someone else
figures?

Helmut
--- End Message ---
--- Begin Message ---
Source: libomxil-bellagio
Source-Version: 0.9.3-8
Done: Ying-Chun Liu (PaulLiu) 

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

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

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated 
libomxil-bellagio 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, 16 Jan 2023 22:35:07 +0800
Source: libomxil-bellagio
Architecture: source
Version: 0.9.3-8
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Closes: 1028978
Changes:
 libomxil-bellagio (0.9.3-8) unstable; urgency=low
 .
   * Fix FTBFS on mipsel. (Closes: #1028978)
 - add debian/patches/0017_patch_for_strncpy.patch
Checksums-Sha1:
 078661075be3a13005e60818a09d558d40ee6950 2288 libomxil-bellagio_0.9.3-8.dsc
 c632cead2e71002564e5acb25faf36d5e2fc7ef2 13320 
libomxil-bellagio_0.9.3-8.debian.tar.xz
 e35d85684a79f76b79a4169537ca504b3069eb56 7478 
libomxil-bellagio_0.9.3-8_source.buildinfo
Checksums-Sha256:
 302cd72ac819142b5c589c63cbaaa197f1b1cc5576ff0df3ba6ed13ab2beee2b 2288 

Bug#1026207: marked as done (python-ase: autopkgtest regression because test functions return values)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 15:07:54 +
with message-id 
and subject line Bug#1026207: fixed in python-ase 3.22.1-3
has caused the Debian Bug report #1026207,
regarding python-ase: autopkgtest regression because test functions return 
values
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.)


-- 
1026207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ase
Version: 3.22.1-2
Severity: serious
Control: affects -1 src:pytest

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainers,

the autopkgtest of your package started failing because some of the
tests return values. This has always been incorrect (tests are expected
to assert, not return anything), but recently, pytest 7.2 started
issuing warnings to stderr [1].

As a simple workaround, you could set "Restrictions: allow-stderr" until
upstream has fixed their tests properly.


Cheers
Timo

[1] 
https://docs.pytest.org/en/7.2.x/deprecations.html#returning-non-none-value-in-test-functions


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmOcQ5cACgkQ+C8H+466
LVmxrAwA3nN7Lbpp5XoVNWAR8NKy3fENAty3CFTnc17myzhoYc4TVoj8e9Vzg+Ci
NuHgY3gl7AKTYK4mPtgicw5VXOdt+hojwJDgsMjRIYli/zssLFhfsN+I3/YoETsN
tw5V+HJMJpahcMuHKgqcMfR3mVTy52u1eNrsf7jsyFyUacs2PO2/5tNaKCzAfinF
Y5HB7oii4+drxSdHGTJqADDrBmAQvkXqzLsJLyG7kJpGBw7qLBN7IQdPMvoQMgcw
iP4r9Y5lA7n3ae2Q/Nukt4/lF1snEn6KUcN1gkVeDbY2twRvlORNwnu5o8r7tJmU
W5vHvB5eP0aakylfQQqhbUdq9jsvoWLbZHCY9dlrrLFwa1TA88olKXNoEcdup/rc
Obj3rrkhrVHEs1Ax626PCuFOg5Y1+sVv9m/LJo4dEyh0/35S1gw6BZA697hrWnO9
pcElGT4lL4CXkb7LcS//y4YjOf8gLx9xi/6LwC62JsYkweCocqzqZXbyIErATBXx
4rjUs7u0
=Ysj+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-ase
Source-Version: 3.22.1-3
Done: Andrius Merkys 

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

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

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated python-ase 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, 16 Jan 2023 09:43:57 -0500
Source: python-ase
Architecture: source
Version: 3.22.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Closes: 1023972 1026207
Changes:
 python-ase (3.22.1-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Replace use of deprecated $ADTTMP with $AUTOPKGTEST_TMP.
   * Remove constraints unnecessary since buster
 .
   [ Andrius Merkys ]
   * Add a patch to fix compatibility with Python 3.11 (Closes: #1023972).
 Thanks Simon McVittie.
   * Restore compatibility of tests (Closes: #1026207)
   * Describe patches.
   * Bump copyright years.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.2, no changes needed.
   * Adjust dependencies and environment needed to build documentation.
Checksums-Sha1:
 1049836e2cb4d55f4539bad006ed0cc134b61c27 2611 python-ase_3.22.1-3.dsc
 f5d0d73bd72e7d77f72999ed11eec0cb9dcd2f5d 14080 
python-ase_3.22.1-3.debian.tar.xz
 e4740c0521fa8fae08f9c8642aac5c7df7ddfda5 13550 
python-ase_3.22.1-3_source.buildinfo
Checksums-Sha256:
 1a17dc6d7fd3476e370a3ed700eca7b2fe2baef2d2d7a249abbab42d9451df08 2611 
python-ase_3.22.1-3.dsc
 5d13db2f328d68e221c7d83ced5f41ab3183e2f5c21c6a933b9fa3371c4127fb 14080 
python-ase_3.22.1-3.debian.tar.xz
 80b376062f7d707bf9568565943cdec7b05d491a81715d0c244d73a62f8777a9 13550 
python-ase_3.22.1-3_source.buildinfo
Files:
 5aead62ec63a5d63bdc2ca2ca32d3439 2611 science optional python-ase_3.22.1-3.dsc
 c7463759c4d6901c39154fc7d55b5dc9 14080 science optional 
python-ase_3.22.1-3.debian.tar.xz
 0cf275b68d7770e7a706dada21a0572a 13550 science optional 
python-ase_3.22.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmPFYxgSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKH9vkP/A7wNbrtb6PfCcr45cWWxB+elvh/PBxC
ixephI08l9r+zhzJjWxcim6EB6h+/7ucpK5Ul5S4qRq4kLPjVj2Gv9LqpRLj1d+F

Bug#1023972: marked as done (python-ase: FTBFS with Python 3.11 due to pathlib.Path.__enter__() deprecation)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 15:07:54 +
with message-id 
and subject line Bug#1023972: fixed in python-ase 3.22.1-3
has caused the Debian Bug report #1023972,
regarding python-ase: FTBFS with Python 3.11 due to pathlib.Path.__enter__() 
deprecation
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.)


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

Source: python-ase
Version: 3.22.1
Severity: important
Forwarded: https://gitlab.com/ase/ase/-/issues/1163

Hello,

python-ase/3.22.1 FTBFS with the following after Python 3.11 support has 
been added:


DeprecationWarning: pathlib.Path.__enter__() is deprecated and scheduled 
for removal in Python 3.13; Path objects as a context manager is a no-op


I have forwarded this upstream.

Andrius
--- End Message ---
--- Begin Message ---
Source: python-ase
Source-Version: 3.22.1-3
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated python-ase 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, 16 Jan 2023 09:43:57 -0500
Source: python-ase
Architecture: source
Version: 3.22.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Closes: 1023972 1026207
Changes:
 python-ase (3.22.1-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Replace use of deprecated $ADTTMP with $AUTOPKGTEST_TMP.
   * Remove constraints unnecessary since buster
 .
   [ Andrius Merkys ]
   * Add a patch to fix compatibility with Python 3.11 (Closes: #1023972).
 Thanks Simon McVittie.
   * Restore compatibility of tests (Closes: #1026207)
   * Describe patches.
   * Bump copyright years.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.2, no changes needed.
   * Adjust dependencies and environment needed to build documentation.
Checksums-Sha1:
 1049836e2cb4d55f4539bad006ed0cc134b61c27 2611 python-ase_3.22.1-3.dsc
 f5d0d73bd72e7d77f72999ed11eec0cb9dcd2f5d 14080 
python-ase_3.22.1-3.debian.tar.xz
 e4740c0521fa8fae08f9c8642aac5c7df7ddfda5 13550 
python-ase_3.22.1-3_source.buildinfo
Checksums-Sha256:
 1a17dc6d7fd3476e370a3ed700eca7b2fe2baef2d2d7a249abbab42d9451df08 2611 
python-ase_3.22.1-3.dsc
 5d13db2f328d68e221c7d83ced5f41ab3183e2f5c21c6a933b9fa3371c4127fb 14080 
python-ase_3.22.1-3.debian.tar.xz
 80b376062f7d707bf9568565943cdec7b05d491a81715d0c244d73a62f8777a9 13550 
python-ase_3.22.1-3_source.buildinfo
Files:
 5aead62ec63a5d63bdc2ca2ca32d3439 2611 science optional python-ase_3.22.1-3.dsc
 c7463759c4d6901c39154fc7d55b5dc9 14080 science optional 
python-ase_3.22.1-3.debian.tar.xz
 0cf275b68d7770e7a706dada21a0572a 13550 science optional 
python-ase_3.22.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmPFYxgSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKH9vkP/A7wNbrtb6PfCcr45cWWxB+elvh/PBxC
ixephI08l9r+zhzJjWxcim6EB6h+/7ucpK5Ul5S4qRq4kLPjVj2Gv9LqpRLj1d+F
H0ClriSlgA3yMcS+K5JxCqvFZfsWOqOHkdM5anQ9S59OKX9OB3PD3RJgqRrbLqlP
aquiNLFWhpdmCVw1dtuZn7253vglAsJmBMsjw6zZTNFCwQq2b0o55XYYqQVqdkT1
YrcQobKLN/76B1BAsLQoWk8v22v61mGRREJJLwnKkGay1BUnX8tzU0u6YibV412/
0VWw4YCzdXlB3CTAm0/tUQAVwvtt5BVInivrx8WscutA+4ODE8fFsTILIfgoGU2+
2k80f46Z5uDa61MvN6Tzi5O7UlRgJJgrUT1E3O1yUF1oc5UijPNgTdHKYmeozVsi
v0KqmQ1X2+vpz/4wGKLcmXkd+/infotjvGPrVeTWIbwyzsvs1VlAcsYaBh30PqcX
OJZkpyPajfTWKCDBdXMYsRbpqURHT1pQSs9ZZ5xoYsyEYdMNXFS8OUzsqZOTeaRy
3CNOD9nSCH612CwQL4T/m2eHGg11cVW/0gpi99hOcnR9cZcJXitNTMJ2PMekVkAV
PT8M/RwfdNL+mdUUkKgT1LCyAvySyqzLnL/MNiFgLXLCdCl4hU0udMCAtVRMhcOr
t4uFQLQARr7J
=zTUI
-END PGP SIGNATURE End Message ---

Bug#1029006: bpy: couldn't find 'scripts/modules', blender probably won't start

[Steve Cotton]

Package: blender-data
Version: 3.4.1+dfsg-1
Severity: grave
Justification: renders package unusable

Blender has no menus, and the only reaction to mouse-movement or keypresses is
an "WM_keymap_poll: empty keymap" error to stdout/stderr. The logs to
stdout/stderr start with:

$ blender
bpy: couldn't find 'scripts/modules', blender probably won't start.
Freestyle: couldn't find 'scripts/freestyle/modules', Freestyle won't work 
properly.
ModuleNotFoundError: No module named 'bpy_types'
ModuleNotFoundError: No module named 'bpy_types'

It seems a lot of directories that 3.3.1 put in /u/s/b/scripts have
ended up down a level in /u/s/b/scripts/scripts instead:

/usr/share/blender/scripts:
drwxr-xr-x 3 root root 4096 Jan 16 15:05 addons
drwxr-xr-x 9 root root 4096 Jan 16 15:05 scripts

/usr/share/blender/scripts/scripts:
drwxr-xr-x 64 root root 4096 Jan 16 15:05 addons
drwxr-xr-x  4 root root 4096 Jan 16 15:05 freestyle
drwxr-xr-x 12 root root 4096 Jan 16 15:05 modules
drwxr-xr-x 19 root root 4096 Jan 16 15:05 presets
drwxr-xr-x  5 root root 4096 Jan 16 15:05 startup
drwxr-xr-x  2 root root 4096 Jan 16 15:05 templates_osl
drwxr-xr-x  2 root root 4096 Jan 16 15:05 templates_py

Symlinking the directories up a level didn't fix everything (I didn't resolve
the two "addons" directories), but was enough to show the menus and react to
input.

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

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

Versions of packages blender-data depends on:
ii  python3  3.11.1-1

blender-data recommends no packages.

blender-data suggests no packages.

-- no debconf information

Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Thiago Franco Moraes]

Hi Andreas,

Done! I removed both python3-theano and python3-keras.

Best regards.

Em seg., 16 de jan. de 2023 às 09:54, Andreas Tille 
escreveu:

> Hi Thiago,
>
> Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes:
> > Hi Rebecca,
> >
> > InVesalius can work without Theano (and Keras). It will use Pytorch.
>
> Would you mind updating the packaging without Theano?  Currently its in
> its Build-Depends.  Would it be sufficient to drop this Build-Depends?
> If yes, I would upload a fixed package.
>
> Kind regards
>Andreas.
>
> --
> http://fam-tille.de
>

Bug#1028060: marked as done (open-infrastructure-service-tools: missing Breaks+Replaces: open-infrastructure-apache-tools (<< 20221122))

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 13:50:15 +
with message-id 
and subject line Bug#1028060: fixed in open-infrastructure-service-tools 
20221122-2
has caused the Debian Bug report #1028060,
regarding open-infrastructure-service-tools: missing Breaks+Replaces: 
open-infrastructure-apache-tools (<< 20221122)
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.)


-- 
1028060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-infrastructure-service-tools
Version: 20221122-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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 .../open-infrastructure-service-tools_20221122-1_all.deb 
...
  Unpacking open-infrastructure-service-tools (20221122-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/open-infrastructure-service-tools_20221122-1_all.deb 
(--unpack):
   trying to overwrite '/etc/apache2/conf-available/000-apache-icons.conf', 
which is also in package open-infrastructure-apache-tools 20190301-lts1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/open-infrastructure-service-tools_20221122-1_all.deb


cheers,

Andreas


open-infrastructure-apache-tools=20190301-lts1-2_open-infrastructure-service-tools=20221122-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: open-infrastructure-service-tools
Source-Version: 20221122-2
Done: Daniel Baumann 

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

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

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
open-infrastructure-service-tools 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, 16 Jan 2023 14:30:31 +0100
Source: open-infrastructure-service-tools
Architecture: source
Version: 20221122-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Closes: 1028060
Changes:
 open-infrastructure-service-tools (20221122-2) unstable; urgency=medium
 .
   * Uploading to unstable.
   * Updating to standards version 4.6.2.
   * Downgrading apache2-data depends to suggests.
   * Adding missing breaks and replaces for apache-tools package renaming
 (Closes: #1028060).
Checksums-Sha1:
 c6b89b035f820f9a47fe2bb68c0aa613b068c71b 2378 
open-infrastructure-service-tools_20221122-2.dsc
 83971dad9f18ee4d95e3c74e50a62cb7bdd9dce9 12576 
open-infrastructure-service-tools_20221122-2.debian.tar.xz
 fe523e47cce6f1fe94c3d84499ee7bbccb5d309b 9758 
open-infrastructure-service-tools_20221122-2_amd64.buildinfo
Checksums-Sha256:
 f6334191b415cffc46a08a4ab480f611ca024235920b347a06697c5f36d227e9 2378 
open-infrastructure-service-tools_20221122-2.dsc
 f8761a8c4d89146d4bcc99a4af6653cdb830c68a79b9d4e24cd99c1b64f414b2 12576 
open-infrastructure-service-tools_20221122-2.debian.tar.xz
 4ab7964117931f37fd67b81619b782368bd0fa67b321ed1b5fd6373f4db8ee75 9758 
open-infrastructure-service-tools_20221122-2_amd64.buildinfo
Files:
 deeb732df117b3993137dbce22b5c21a 2378 admin optional 
open-infrastructure-service-tools_20221122-2.dsc
 a9c57afc3934e98014367cbd0f375339 12576 admin optional 
open-infrastructure-service-tools_20221122-2.debian.tar.xz
 37412dc3255d423d444dea8130e8a418 9758 admin optional 
open-infrastructure-service-tools_20221122-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmPFUj0ACgkQVc8b+Yar
ucffAQ//cwFW215KzAOnmhQ8oHBxEc+Q1+s1QaM24wedhz68d/peufvPu1j6adA+
S1cT/CqTpjg0LaC7s/5+oX6GHlKzdDO6PtU7oP3qoMSRhi+ipA+UOvcJQdvQehv1

Bug#1026207: marked as pending in python-ase

[Andrius Merkys]

Control: tag -1 pending

Hello,

Bug #1026207 in python-ase 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/debichem-team/python-ase/-/commit/107cd838b53315dd7a0e9536e219ab72b68ca21b


Restore compatibility of tests (Closes: #1026207)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026207

Processed: Bug#1026207 marked as pending in python-ase

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026207 [src:python-ase] python-ase: autopkgtest regression because test 
functions return values
Added tag(s) pending.

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

Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andreas Tille]

Hi Thiago,

Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes:
> Hi Rebecca,
> 
> InVesalius can work without Theano (and Keras). It will use Pytorch.

Would you mind updating the packaging without Theano?  Currently its in
its Build-Depends.  Would it be sufficient to drop this Build-Depends?
If yes, I would upload a fixed package.

Kind regards
   Andreas.

-- 
http://fam-tille.de

Bug#1028451: 2nd DisplayPort doesn't get video

[Didier 'OdyX' Raboud]

Hello there,

I finally managed to test

https://github.com/archlinux/linux/commit/7c4fed4d2afd27d7acb8835f8e79f49c99c03cdf.patch

(which is a revert of 4d07b0bc403403438d9cf88450506240c5faf92f)

… on top of 6.1.4-1.

I can confirm (without looking into any code-related details), that the two
of my DisplayPort-connected screens light up and work correctly.

(The "first" external screen is connected with a DisplayPort-DVI converter; that
one always worked; the "second" is connected directly via DisplayPort, which 
didn't
work on unpatched 6.1.4)


14 janvier 2023 17:52 "Diederik de Haas"  a écrit:
> On Saturday, 14 January 2023 16:30:05 CET Salvatore Bonaccorso wrote:
>> On Thu, Jan 12, 2023 at 02:51:05PM +0100, Diederik de Haas wrote:
>> On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
>>> Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
>>> 
>>> upstream here:
>>> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
>> 
>> Thanks! About an hour ago the suggested fix was to revert commit
>> 4d07b0bc403403438d9cf88450506240c5faf92f part of v6.1-rc1
>> 
>> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#
>> s4.2.2 describes a procedure to build a kernel with the proposed patch
>> (attached).
>> 
>> OdyX: Can you try to see whether that resolves the issue?
>> 
>> Should we keep 6.1.y based kernel out of testing until this is clear?
>> As we aim though to have 6.1.y into bookworm I would see it as more
>> preferable to get 6.1.4 in for testing, we will need to followup as
>> well soonish with another interation for e.g. for fixing
>> CVE-2023-0266.
> 
> As CVE-2023-0266 is fixed in 6.1.6, I'd suggest to upload that now, which I
> believe is ready to be uploaded already.
> That should keep 6.1.y out of testing for a few more days.
> 
>> Now if it turns out that this is the same issue as the referenced
>> upstream, reverting I think we only should really revert the commit if
>> that's queued up for 6.1. There is currently some furhter discussion
>> on
>> https://lore.kernel.org/stable/dcf0612f-7d40-d607-e9aa-94599594e...@amd.com
>> /T/#m38bdafb9c6c64b167ec94ac1bd131f1d2db66e40
>> 
>> Given the size of the revert, there is as well a chance to re-break
>> other parts. So preferring to closely follow upstream here, whatever
>> the decision will be.
> 
> Agreed.
> 
> I asked 'OdyX' to test the revert to make sure it would indeed fix *this*
> issue, IOW what I consider standard bug triaging.
> 
> But even Daniel Vetter has SERIOUS 'issues' with the revert, next to the other
> people who weren't happy about it. So *I* wouldn't suggest applying it to
> Debian (although I don't think my opinion should have much weight).
> 
> As for letting this bug _continue_ to prevent a migration, ie keep the RC
> status, I'm against it and for downgrading it to 'important'.
> You could opt to add a NEWS item to warn people about this potential issue.
> 
> But the original report is about the *2nd* DisplayPort being 'broken'.
> 
> On zaterdag 14 januari 2023 17:04:52 CET you wrote:
> 
>> Basically this issue breaks all usage of Displayport MST on amdgpu systems.
>> Which roughly translates to breaking external monitors for everyone using
>> an USB-C docks with multiple display outputs (which is pretty common these
>> days) on AMD laptops. As well as those like myself who daisy-chain display
>> port monitors with an amdgpu using graphics card.
> 
> I understand that would be annoying for you, but I don't think that it would
> affect the majority of our users.

Hrm. More and more laptops come with usb-c only, and dongles/docks become more
and more common.

It's clearly a serious regression, as such setups "just worked" with 6.0.

Best,

OdyX

Bug#1028803: marked as done (jni-inchi: FTBFS: [ERROR] Failed to execute goal on project jni-inchi: Could not resolve dependencies for project net.sf.jni-inchi:jni-inchi:jar:0.8: Cannot access central

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 10:34:19 +
with message-id 
and subject line Bug#1028803: fixed in jni-inchi 0.8+dfsg-7
has caused the Debian Bug report #1028803,
regarding jni-inchi: FTBFS: [ERROR] Failed to execute goal on project 
jni-inchi: Could not resolve dependencies for project 
net.sf.jni-inchi:jni-inchi:jar:0.8: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
log4j:log4j:jar:debian has not been downloaded from it before. -> [Help 1]
to be marked as done.

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

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


-- 
1028803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jni-inchi
Version: 0.8+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibjni-inchi-java --debian-build --keep-pom-version 
> --maven-repo=/<>/jni-inchi-0.8\+dfsg/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/jni-inchi-0.8\+dfsg 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/jni-inchi-0.8\+dfsg/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/jni-inchi-0.8\+dfsg/debian 
> -Dmaven.repo.local=/<>/jni-inchi-0.8\+dfsg/debian/maven-repo 
> --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< net.sf.jni-inchi:jni-inchi 
> >-
> [INFO] Building JNI-InChI 0.8
> [INFO] [ jar 
> ]-
> [WARNING] The artifact 
> org.apache.maven.plugins:maven-resources-plugin:jar:2.6 has been relocated to 
> org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0
> [WARNING] The artifact org.apache.maven.plugins:maven-jar-plugin:jar:2.4 has 
> been relocated to org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0
> [WARNING] The POM for log4j:log4j:jar:debian is missing, no dependency 
> information available
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  0.183 s
> [INFO] Finished at: 2023-01-13T20:27:41Z
> [INFO] 
> 
> [ERROR] Failed to execute goal on project jni-inchi: Could not resolve 
> dependencies for project net.sf.jni-inchi:jni-inchi:jar:0.8: Cannot access 
> central (https://repo.maven.apache.org/maven2) in offline mode and the 
> artifact log4j:log4j:jar:debian has not been downloaded from it before. -> 
> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify 
> -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/jni-inchi-0.8\+dfsg 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/jni-inchi-0.8\+dfsg/debian/maven.properties
>  org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/jni-inchi-0.8\+dfsg/debian 
> -Dmaven.repo.local=/<>/jni-inchi-0.8\+dfsg/debian/maven-repo 
> --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
> exit code 1
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:

Bug#1027215: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

[Andrius Merkys]

Hello,

On 2023-01-14 13:12, Rebecca N. Palmer wrote:
theano has been mostly abandoned upstream since 2018.  (The Aesara fork 
is not abandoned, but includes interface changes including the import 
name, so would break reverse dependencies not specifically altered for it.)


Its reverse dependencies are keras, deepnano and invesalius.

It is currently broken, probably by numpy 1.24 (#1027215), and the 
immediately obvious fixes weren't enough 
(https://salsa.debian.org/science-team/theano/-/pipelines).


Is this worth spending more effort on fixing, or should we just remove it?


keras is needed to train evaluation models for qmean [1] which I intend 
[2] to package eventually. qmean is a quite popular protein model 
evaluation tool, personally I use it a lot and I believe it would be 
useful to have it in Debian.


That said, it is OK to omit keras in bookworm if need be, but I would 
like to see it back for trixie.


[1] 
https://git.scicore.unibas.ch/search?search=keras_source=navbar_id=69_id=25_code=true_ref=master

[2] https://bugs.debian.org/976981

Best,
Andrius

Bug#1028667: marked as done (dask: B-D on python-numpy-doc which no longer exists)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 10:04:36 +
with message-id 
and subject line Bug#1028667: fixed in dask 2022.12.1+dfsg-1
has caused the Debian Bug report #1028667,
regarding dask: B-D on python-numpy-doc which no longer exists
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-python, dpkg-dev (>= 
> 1.17.14), node-js-yaml, python-asyncssh-doc, python-numpy-doc, 
> python-pandas-doc, python3-all, python3-cloudpickle, 
> python3-dask-sphinx-theme, python3-distributed, python3-fsspec, 
> python3-ipython, python3-numpydoc, python3-pandas (>= 1.3), python3-partd, 
> python3-scipy, python3-setuptools, python3-sphinx, python3-sphinx-click, 
> python3-sphinx-remove-toctrees, python3-sphinx-tabs, python3-toolz, 
> sphinx-common, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-python, dpkg-dev (>= 
> 1.17.14), node-js-yaml, python-asyncssh-doc, python-numpy-doc, 
> python-pandas-doc, python3-all, python3-cloudpickle, 
> python3-dask-sphinx-theme, python3-distributed, python3-fsspec, 
> python3-ipython, python3-numpydoc, python3-pandas (>= 1.3), python3-partd, 
> python3-scipy, python3-setuptools, python3-sphinx, python3-sphinx-click, 
> python3-sphinx-remove-toctrees, python3-sphinx-tabs, python3-toolz, 
> sphinx-common, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [551 B]
> Get:5 copy:/<>/apt_archive ./ Packages [622 B]
> Fetched 2136 B in 0s (132 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  sbuild-build-depends-main-dummy : Depends: python-numpy-doc but it is not 
> installable
>Depends: python3-pandas (>= 1.3) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/dask_2022.02.0+dfsg-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2022.12.1+dfsg-1
Done: Andreas Tille 

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

Bug#1027254: marked as done (dask: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 10:04:36 +
with message-id 
and subject line Bug#1027254: fixed in dask 2022.12.1+dfsg-1
has caused the Debian Bug report #1027254,
regarding dask: autopkgtest fail with numpy/1.24.1
to be marked as done.

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

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


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

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

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

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

Several of the errors are in the form of:

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

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

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

some deprecations introduced in 1.20.0

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

(released almost 2 years ago).

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

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

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

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2022.12.1+dfsg-1
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dask 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, 16 Jan 2023 10:22:16 +0100
Source: dask
Architecture: source
Version: 2022.12.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1025393 1027254 1028667
Changes:
 dask (2022.12.1+dfsg-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * New upstream version
 Closes: #1025393, #1027254
   * Simplify watch file
   * Standards-Version: 4.6.2 (routine-update)
   * Add salsa-ci file (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Ignore some sphinx packages that are not packaged yet
   * yaml.min.js should be properly excluded from upstream source.  Just
 in case it is needed it can be taken from debian/missing-sources.
 .
   [ Rebecca N. Palmer ]
   * Docs: continue to use our js-yaml.
   * Temporarily remove python3-distributed B-D to break cycle.
 Closes: #1028667
   * Docs: ignore build errors.
   * Tests: be compatible with our CI setup.
   * Remove newline from error message, to not break python3-intake.
Checksums-Sha1:
 85c60b2a54b4e5248e3f29017c766e0da0476f2d 3012 dask_2022.12.1+dfsg-1.dsc
 487c400a5fa78bb6b0a7441758ab19580fe2b1e3 7548508 
dask_2022.12.1+dfsg.orig.tar.xz
 18e12f3e4c3053a06762fbac50eeaaec31661d02 46932 
dask_2022.12.1+dfsg-1.debian.tar.xz
 73736890abf4254d281e434e0403571615f9d952 20883 
dask_2022.12.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 e474074e3a70579aed837f71dd0fc99bdd2b268cf18299a42f1f49c1081fc051 3012 
dask_2022.12.1+dfsg-1.dsc
 bc9331d6f47f37f21b3025baccbaa7f1a1b85dafc47d024e41bb3a44c3a41fd0 7548508 
dask_2022.12.1+dfsg.orig.tar.xz
 fe39feec3da12e624878d42e65d1393ab8c0678605c60f932b6947358101f188 46932 
dask_2022.12.1+dfsg-1.debian.tar.xz
 82bcf23d5d15a337acc83fa3247f76f0d6d7a08ed47af541064d96136c6d7e48 20883 
dask_2022.12.1+dfsg-1_source.buildinfo
Files:
 9b4bb256f19eba63b0ddbbc47d72c6de 3012 python optional dask_2022.12.1+dfsg-1.dsc
 c07e24e5135ecfa7ff3c8f1481519c89 7548508 python 

Bug#1025393: marked as done (dask: autopkgtest fail with pandas 1.5)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 10:04:36 +
with message-id 
and subject line Bug#1025393: fixed in dask 2022.12.1+dfsg-1
has caused the Debian Bug report #1025393,
regarding dask: autopkgtest fail with pandas 1.5
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.)


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

Package: python3-dask
Version: 2022.02.0+dfsg-2
Tags: fixed-upstream
Control: block 1022571 by -1

With pandas 1.5 (currently in experimental), the dask autopkgtest fails:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dask/28842796/log.gz

This appears to be fixed upstream, but I haven't tested this:
https://github.com/dask/dask/pull/8961
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2022.12.1+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dask 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, 16 Jan 2023 10:22:16 +0100
Source: dask
Architecture: source
Version: 2022.12.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andreas Tille 
Closes: 1025393 1027254 1028667
Changes:
 dask (2022.12.1+dfsg-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * New upstream version
 Closes: #1025393, #1027254
   * Simplify watch file
   * Standards-Version: 4.6.2 (routine-update)
   * Add salsa-ci file (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Ignore some sphinx packages that are not packaged yet
   * yaml.min.js should be properly excluded from upstream source.  Just
 in case it is needed it can be taken from debian/missing-sources.
 .
   [ Rebecca N. Palmer ]
   * Docs: continue to use our js-yaml.
   * Temporarily remove python3-distributed B-D to break cycle.
 Closes: #1028667
   * Docs: ignore build errors.
   * Tests: be compatible with our CI setup.
   * Remove newline from error message, to not break python3-intake.
Checksums-Sha1:
 85c60b2a54b4e5248e3f29017c766e0da0476f2d 3012 dask_2022.12.1+dfsg-1.dsc
 487c400a5fa78bb6b0a7441758ab19580fe2b1e3 7548508 
dask_2022.12.1+dfsg.orig.tar.xz
 18e12f3e4c3053a06762fbac50eeaaec31661d02 46932 
dask_2022.12.1+dfsg-1.debian.tar.xz
 73736890abf4254d281e434e0403571615f9d952 20883 
dask_2022.12.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 e474074e3a70579aed837f71dd0fc99bdd2b268cf18299a42f1f49c1081fc051 3012 
dask_2022.12.1+dfsg-1.dsc
 bc9331d6f47f37f21b3025baccbaa7f1a1b85dafc47d024e41bb3a44c3a41fd0 7548508 
dask_2022.12.1+dfsg.orig.tar.xz
 fe39feec3da12e624878d42e65d1393ab8c0678605c60f932b6947358101f188 46932 
dask_2022.12.1+dfsg-1.debian.tar.xz
 82bcf23d5d15a337acc83fa3247f76f0d6d7a08ed47af541064d96136c6d7e48 20883 
dask_2022.12.1+dfsg-1_source.buildinfo
Files:
 9b4bb256f19eba63b0ddbbc47d72c6de 3012 python optional dask_2022.12.1+dfsg-1.dsc
 c07e24e5135ecfa7ff3c8f1481519c89 7548508 python optional 
dask_2022.12.1+dfsg.orig.tar.xz
 9487cffb5faa8fb78c6e6c5659d880f6 46932 python optional 
dask_2022.12.1+dfsg-1.debian.tar.xz
 daf6bea9886ae153b5024ae97b8f545b 20883 python optional 
dask_2022.12.1+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmPFHbgOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFDIhAAnDGtxFJN0ZwNho4gobG9UUy6eQcg0hdWOayk
2DRd4VVmHOyK3S4/32VIZfOVhA7pxPRFJ8TFbw37uPP8mzZ0QWfttxBSSFfTLHOY
UI/5nZxeXNtpn34A1LiVl98/MeZuW0/6A5K5vjdBCzHZ2lhjFLIJg3ZG+cRtRtsG
hwYvNl753zen9zYtXoogVEjtXS3EyUpS/4BfuTG80kUMk/zMcSNW91wKm2rjuBlS
R1SKzEWBwWwzAz8sNjT90vpuBFtcmRhX9Do4UDU04FVP7mI0JfWSA8nYSYTDXXuz
fr25MDym4UXFiUAheFaZSpbTNOWedUxLsp1phn0F/U5H7y3aitzMEGLk80sdeIvl
N8GdfShwp1LKRtOLets91Dd5++SLRwNTZK1+hJJ+Z2KYqcX4a7DuKJ/+9FkEKKJ8
jTYk7aexn/9J+OnXyYt8nbfkfapq7o6BUHjtx1cFoyFtrRwk+zoEXQGifkxPbR51
dmdGbZ6PN+0rMzBevsqmVpe9Mu6u2KQXOX2tyamFZ3nbI49uTI8NmDiDokxyrq3L

Bug#1028667: dask BD-Uninstallable

[Andreas Tille]

Am Sun, Jan 15, 2023 at 06:16:31PM + schrieb Rebecca N. Palmer:
> Probably fixed - see my merge request on Salsa.

I've uploaded after some slight changes (for instance fixing lintian
issue about yaml.min.js by repackaging source tarball).

Thanks a lot for your work
   Andreas. 

-- 
http://fam-tille.de

Bug#1028828: marked as done (python-django-ical: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 10:50:10 +0100
with message-id <2a57ee6b8f8052ab51841631f91f2993cb7d5721.ca...@gmail.com>
and subject line Unreproducible
has caused the Debian Bug report #1028828,
regarding python-django-ical: FTBFS: distutils.errors.DistutilsError: Command 
'['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', 
'--no-deps', '-w', '/tmp/tmpvy3hf3w4', '--quiet', 'tomli>=1.0.0']' returned 
non-zero exit status 1.
to be marked as done.

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

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


-- 
1028828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-ical
Version: 1.8.3-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
> SetuptoolsDeprecationWarning: setuptools.installer is deprecated. 
> Requirements should be satisfied by a PEP 517 installer.
>   warnings.warn(
> WARNING: The wheel package is not available.
> /usr/bin/python3.10: No module named pip
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 82, in 
> fetch_build_egg
> subprocess.check_call(cmd)
>   File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3.10', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpvy3hf3w4', '--quiet', 'tomli>=1.0.0']' returned non-zero exit status 
> 1.
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 5, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 86, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 80, in 
> _install_setup_requires
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 874, in 
> fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 789, 
> in resolve
> dist = best[req.key] = env.best_match(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1075, 
> in best_match
> return self.obtain(req, installer)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1087, 
> in obtain
> return installer(requirement)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 944, in 
> fetch_build_egg
> return fetch_build_egg(self, req)
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 84, in 
> fetch_build_egg
> raise DistutilsError(str(e)) from e
> distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 
> 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpvy3hf3w4', '--quiet', 'tomli>=1.0.0']' returned non-zero exit status 
> 1.
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.10 3.11" 
> returned exit code 13
> make: *** [debian/rules:9: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/01/13/python-django-ical_1.8.3-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230113=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

I just rebuilt the package in an unstable chroot and everything went

Bug#1028405: marked as done (ansible-core: autopkgtest regresses with new python3-defaults (python 3.11))

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:49:49 +
with message-id 
and subject line Bug#1028405: fixed in ansible-core 2.14.1-2
has caused the Debian Bug report #1028405,
regarding ansible-core: autopkgtest regresses with new python3-defaults (python 
3.11)
to be marked as done.

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

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


-- 
1028405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible-core
Version: 2.14.1-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Hi Lee,

The ansible-core autopkgtests fail now that /usr/bin/python3 is python 3.11:

[...]
autopkgtest [08:17:06]: test unit: [---
FATAL: Running under Python version 3.11 instead of 3.10.
FATAL: Command "/usr/bin/env 
ANSIBLE_TEST_CONTENT_ROOT=/tmp/autopkgtest-lxc.8ik95lf6/downtmp/build.jHa/src 
PYTHONPATH=/tmp/ansible-test-iin32i73 /usr/bin/python3 /usr/bin/ansible-test 
units --containers '{}' --truncate 0 --color no --host-path 
test/results/.tmp/host-n2w5rzai --metadata 
test/results/.tmp/metadata-_yj0am3d.json" returned exit status 1.
autopkgtest [08:17:07]: test unit: ---]
[...]

  
(https://ci.debian.net/data/autopkgtest/unstable/amd64/a/ansible-core/29976247/log.gz)

This comes down to a hard-coded "--python 3.11" option in the autopkgtest
which seems superfluous.

I have uploaded the attached patch to Ubuntu to unblock the python3-defaults
transition there.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ansible-core-2.14.1/debian/tests/unit 
ansible-core-2.14.1/debian/tests/unit
--- ansible-core-2.14.1/debian/tests/unit   2022-11-27 23:43:42.0 
-0800
+++ ansible-core-2.14.1/debian/tests/unit   2023-01-09 21:15:02.0 
-0800
@@ -2,5 +2,4 @@
 
 /usr/bin/ansible-test units \
   --python-interpreter /usr/bin/python3 \
-  --python 3.10 \
   --local
--- End Message ---
--- Begin Message ---
Source: ansible-core
Source-Version: 2.14.1-2
Done: Jochen Sprickerhof 

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

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

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ansible-core 
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, 16 Jan 2023 10:14:20 +0100
Source: ansible-core
Architecture: source
Version: 2.14.1-2
Distribution: unstable
Urgency: medium
Maintainer: Lee Garrett 
Changed-By: Jochen Sprickerhof 
Closes: 1028405
Changes:
 ansible-core (2.14.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Steve Langasek ]
   * Drop superfluous --python 3.10 in autopkgtest (Closes: #1028405)
Checksums-Sha1:
 56ca0629185bab8a0001b036906476fd636a6a48 2690 ansible-core_2.14.1-2.dsc
 1ce40c4a301ca0e3d4ee2b7efe138176cd7af45b 25608 
ansible-core_2.14.1-2.debian.tar.xz
 4263aeecfd35bdeb9d15be85088b3fd7ccedf4d3 6904 
ansible-core_2.14.1-2_source.buildinfo
Checksums-Sha256:
 64b7ab5d688769082809e832afc40e75892dfe58692fbcfeef84a8dae0efbafb 2690 
ansible-core_2.14.1-2.dsc
 708b9989c57d623f116e12f21319a7e5bbadd52909a950b37f48be5bd5f8156d 25608 
ansible-core_2.14.1-2.debian.tar.xz
 0a991fd3c1c1f358aef28897a2e92ff91274155654e4e1eb7fbd89ff4826596c 6904 
ansible-core_2.14.1-2_source.buildinfo
Files:
 89979d2cae6e65f8577d43b5191dc787 2690 admin optional ansible-core_2.14.1-2.dsc
 514bb80838c876b993c906b9c431f670 25608 admin optional 
ansible-core_2.14.1-2.debian.tar.xz
 197c09c2d39ed1a69ad6de855ec75802 6904 admin optional 
ansible-core_2.14.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmPFFbQACgkQW//cwljm
lDPD2w/+LbioWIHNx2hH3csksEaa0EzWTSGhKI5M6Tjyq7ar0Ws94R8KyIOmtjzy

Bug#1028899: marked as done (gocr: Build-depends on NBS -dev package libnetpbm11-dev)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:26:20 +
with message-id 
and subject line Bug#1028899: fixed in gocr 0.52-6
has caused the Debian Bug report #1028899,
regarding gocr: Build-depends on NBS -dev package libnetpbm11-dev
to be marked as done.

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

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


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

The libnetpbm11-dev package is no longer built by the netpdm-free
package.  Once it is decrufted gocr will FTBFS.

Scott K
--- End Message ---
--- Begin Message ---
Source: gocr
Source-Version: 0.52-6
Done: Andrius Merkys 

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

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

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated gocr 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, 16 Jan 2023 03:54:18 -0500
Source: gocr
Architecture: source
Version: 0.52-6
Distribution: unstable
Urgency: medium
Maintainer: Andrius Merkys 
Changed-By: Andrius Merkys 
Closes: 1028899
Changes:
 gocr (0.52-6) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Fix day-of-week for changelog entries 0.48-1, 0.3.4-4, 0.2.7-2.
   * Apply multi-arch hints. + libpgm2asc0.52: Add Multi-Arch: same.
 .
   [ Andrius Merkys ]
   * Build depend on libnetpbm-dev instead of libnetpbm11-dev (Closes: #1028899)
   * Bump copyright years.
Checksums-Sha1:
 9741a0086c4aba8ee80563d377c6a641704e7f3c 2135 gocr_0.52-6.dsc
 4b901da5849d45804b9378569bda900480237ed1 7264 gocr_0.52-6.debian.tar.xz
 24a41e3793f9a17e617e27d51394ecb720968026 7103 gocr_0.52-6_source.buildinfo
Checksums-Sha256:
 14ff1c0c22eda2bc61fbab755ce8b9e467fd58f5a39b883b96e511145ee1d69b 2135 
gocr_0.52-6.dsc
 c74754aabf6efd52cbd8c059e5b1b8e93091ac3f4f02a7370daff418f39025fd 7264 
gocr_0.52-6.debian.tar.xz
 3094a2f9a4e333a2f794d84fdf4253a3075cc96d0933a8dbc7807b9d567c098f 7103 
gocr_0.52-6_source.buildinfo
Files:
 6ceb15a3b388277ed6cba82a89218769 2135 graphics optional gocr_0.52-6.dsc
 74ed0187e1656e77b4e988621bd4268b 7264 graphics optional 
gocr_0.52-6.debian.tar.xz
 6dee08531b21792d797870ad0c991109 7103 graphics optional 
gocr_0.52-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmPFEtESHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHoo0P/3IRocGlbFVU9V1P7FM8gHfC8dm+N4az
p6vjxLiYJJNeVV6JLTiAHMAaCM8MTFIrLIE3FzlXTO5r46HhCMxHT4x+gA4Ai1uz
m52KJxPsxtFY6CUzJoJgMiYM8DpqnqD+lqB2iltqp0GedgfObFwVD027puu11W6G
+otPcyU6k49PYKFfdmAfEBSYSVpAspitXEGGY14ZPrKOMdMCTxGb461nsq4zxem1
eDBZvAzuJUpnNdFWsgDuJCLzYfpZpPb0GiwAbEXqvrNpWU69C4BjxEVNTS7hxwtV
iHJFaDnQZZbeX1UA1Pyj51RLqlXWnUzrIhq7QXb1jEo0qm8e12FEQvzbdsCA5KK3
12xWLkez5jcIrPBxcGMsFHUt1jVhpEcjx0wsYViJtgLAVhiIu63BV+TkH+TXWwrw
DC1jy7zfsoIqXBuG/xzlyAktpGMrGcJCbXruab06KOp9gSPqReEgx+9+LumgKEBC
IZ1+K3tFIZYul5sgL8gghT0WAEtZ3j4gTrgc5GK5HTtaqMMTLG9xiTk4miAcl9/9
y+WKZuglKGmCOVAAn/fYs9g3No13Qb3DM507cf8ivnJyCp3SnsCgTUpb99KRTvQu
g9fE7o24qgFMiIKC0c3v/+sEnMZt2WeqqAh4QrTwbGhxf/WwXEv0KmivCpz9akMX
1h2KbpCFN9kq
=VOtD
-END PGP SIGNATURE End Message ---

Bug#1028316: marked as done (libfplll8-data: missing Breaks+Replaces: libfplll7-data (>= 5.4.3))

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:04:57 +
with message-id 
and subject line Bug#1028292: fixed in fplll 5.4.4-3
has caused the Debian Bug report #1028292,
regarding libfplll8-data: missing Breaks+Replaces: libfplll7-data (>= 5.4.3)
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.)


-- 
1028292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfplll8-data
Version: 5.4.4-1
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 .../libfplll8-data_5.4.4-1_all.deb ...
  Unpacking libfplll8-data (5.4.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libfplll8-data_5.4.4-1_all.deb (--unpack):
   trying to overwrite '/usr/share/libfplll8/strategies/default.json', which is 
also in package libfplll7-data 5.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libfplll8-data_5.4.4-1_all.deb

The (>= 5.4.3) is unusual but correct in this case since libfplll7-data
5.4.3-1 moved a file to a libfplll8 path without renaming the package.
Thus libfplll8-data should be co-installable with older (non-buggy)
versions of libfplll7-data.

cheers,

Andreas


libfplll7-data=5.4.3-2_libfplll8-data=5.4.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fplll
Source-Version: 5.4.4-3
Done: Julien Puydt 

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated fplll 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, 16 Jan 2023 09:31:36 +0100
Source: fplll
Architecture: source
Version: 5.4.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Julien Puydt 
Closes: 1028292
Changes:
 fplll (5.4.4-3) unstable; urgency=medium
 .
   * Add breaks+replace for libfplll7-data 5.4.3-2 (Closes: #1028292).
Checksums-Sha1:
 78f1931def70a8b425265cbe95e99d2792da5ad5 2149 fplll_5.4.4-3.dsc
 f81c17f22cac19fac44fe14e3e9accba8ebe47cd 8920 fplll_5.4.4-3.debian.tar.xz
 97a66103875aa76e786745576539475a644d481c 6580 fplll_5.4.4-3_source.buildinfo
Checksums-Sha256:
 425090dd89772e79d8f5e0dfef8b9e55022ef0aa3ea82d14e1e125e200f7d32b 2149 
fplll_5.4.4-3.dsc
 2614dcec71a608827d4ce1e151fe70d0509aa9501ca469309825af2eeffbdbae 8920 
fplll_5.4.4-3.debian.tar.xz
 dc4a1b3dbe4256c8a96ec15bac1eaec5aaab7840efdb5fb1d6be7b935504c31a 6580 
fplll_5.4.4-3_source.buildinfo
Files:
 a664cecb2a4ff5a3891ec56a95130f76 2149 math optional fplll_5.4.4-3.dsc
 674e2e988f28e0e3a116102dd8b089ef 8920 math optional fplll_5.4.4-3.debian.tar.xz
 f3a487c17c163440a2dcca259552805e 6580 math optional 
fplll_5.4.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmPFC5ISHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRd3kP/RShLoSlG1YqRFfD5/FWofbz3jKBxRaF
bcJQp23NB/LPnHBepDxIytH6sn8sHBx1e2BlC1AWxBYrCzXbz5Iv1XcuF20DHTKk
ptcC1jaB8sPghW2xNZMgenC11QKx8yoPuc5SdqiQDugqT4C9QJ/zyp5G+KQ/g7Kz
146/FV6QQ/aY+1lCk7ArzMvIZVmUfyO0rlXgJdOYSMVyb8q1zEPTk1Ml+BiBqzvu
vY4SKt9RxDwqYG6TIJ7OYSdFYO9A6RvS6lf+wXt3Xq0oEgeigBowDcZHMzWQJdiV
TG6iXLpq/DKE7JwF42oeiL317DKXIM5OsA4dy7uFtl991SDSjohon2Ndy4lkz6Xe
3X4pAzWlTGbh1AeWWQou8EsMfI05bGSwSpT7dqBBUxumqTchuAYTbyLVx+p3/B6r
uKKYFfaaKCacF+IZc90fwElP+TzgCTGbyJWceSWXSIq15Is+iu/q6gWXZgW/ADt1
khQeWmgpecbqvw6nB0vaAD2FngfkxqdI4rzGbDrrGqDdasEZqdHli9vqkJMQXvRE

Bug#1026551: marked as done (aioftp: FTBFS: TypeError: Passing coroutines is forbidden, use tasks explicitly.)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:04:29 +
with message-id 
and subject line Bug#1026551: fixed in aioftp 0.21.4-1
has caused the Debian Bug report #1026551,
regarding aioftp: FTBFS: TypeError: Passing coroutines is forbidden, use tasks 
explicitly.
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_aioftp/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pytest.ini
> plugins: cov-4.0.0, asyncio-0.20.3
> asyncio: mode=Mode.STRICT
> collected 771 items
> 
> tests/test_abort.py F
> 
> === FAILURES 
> ===
> __ test_abort_stor[127.0.0.1] 
> __
> 
> pair_factory = .Factory'>
> 
> @pytest.mark.asyncio
> async def test_abort_stor(pair_factory):
> >   async with pair_factory() as pair:
> 
> tests/test_abort.py:12: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> tests/conftest.py:125: in __aenter__
> await self.client.connect(self.server.server_host,
> aioftp/client.py:605: in connect
> code, info = await self.command(None, "220", "120")
> aioftp/client.py:254: in command
> code, info = await self.parse_response()
> aioftp/client.py:180: in parse_response
> code, rest = await self.parse_line()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> 
> async def parse_line(self):
> """
> :py:func:`asyncio.coroutine`
> 
> Parsing server response line.
> 
> :return: (code, line)
> :rtype: (:py:class:`aioftp.Code`, :py:class:`str`)
> 
> :raises ConnectionResetError: if received data is empty (this
> means, that connection is closed)
> :raises asyncio.TimeoutError: if there where no data for `timeout`
> period
> """
> line = await self.stream.readline()
> if not line:
> self.stream.close()
> >   raise ConnectionResetError
> E   ConnectionResetError
> 
> aioftp/client.py:163: ConnectionResetError
> -- Captured log setup 
> --
> 09:47:47.108 asyncio  DEBUGselector_events.py 54   Using 
> selector: EpollSelector
> 09:47:47.108 asyncio  DEBUGselector_events.py 54   Using 
> selector: EpollSelector
> -- Captured log call 
> ---
> 09:47:47.110 aioftp.serverINFO server.py   741  serving on 
> 127.0.0.1:41135
> 09:47:47.111 aioftp.serverINFO server.py   888  new 
> connection from 127.0.0.1:33270
> 09:47:47.112 aioftp.serverERRORserver.py   960  dispatcher 
> caught exception
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.11_aioftp/build/aioftp/server.py", line 
> 929, in dispatcher
> done, pending = await asyncio.wait(
> ^^^
>   File "/usr/lib/python3.11/asyncio/tasks.py", line 415, in wait
> raise TypeError("Passing coroutines is forbidden, use tasks explicitly.")
> TypeError: Passing coroutines is forbidden, use tasks explicitly.
> 09:47:47.113 aioftp.serverINFO server.py   962  closing 
> connection from 127.0.0.1:33270
>  Captured log teardown 
> -
> 09:47:47.200 asyncio  DEBUGselector_events.py 54   Using 
> selector: EpollSelector
> === warnings summary 
> ===
> ../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294
>   /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1294: 
> PytestConfigWarning: Unknown config option: color
>   
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
> 
> 

Bug#1028292: marked as done (libfplll8-data: tries to overwrite /usr/share/libfplll8/strategies/default.json, already in libfplll7-data)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:04:57 +
with message-id 
and subject line Bug#1028292: fixed in fplll 5.4.4-3
has caused the Debian Bug report #1028292,
regarding libfplll8-data: tries to overwrite 
/usr/share/libfplll8/strategies/default.json, already in libfplll7-data
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.)


-- 
1028292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfplll8-data
Version: 5.4.4-2
Severity: serious

When upgrading, I got the following error:

Preparing to unpack .../libfplll8-data_5.4.4-2_all.deb ...
Unpacking libfplll8-data (5.4.4-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/libfplll8-data_5.4.4-2_all.deb (--unpack):
 trying to overwrite '/usr/share/libfplll8/strategies/default.json', which is 
also in package libfplll7-data 5.4.3-2

Perhaps something like a missing Breaks/Replaces to ensure that
libfplll7-data will be removed first.

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

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: fplll
Source-Version: 5.4.4-3
Done: Julien Puydt 

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

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

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated fplll 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, 16 Jan 2023 09:31:36 +0100
Source: fplll
Architecture: source
Version: 5.4.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Julien Puydt 
Closes: 1028292
Changes:
 fplll (5.4.4-3) unstable; urgency=medium
 .
   * Add breaks+replace for libfplll7-data 5.4.3-2 (Closes: #1028292).
Checksums-Sha1:
 78f1931def70a8b425265cbe95e99d2792da5ad5 2149 fplll_5.4.4-3.dsc
 f81c17f22cac19fac44fe14e3e9accba8ebe47cd 8920 fplll_5.4.4-3.debian.tar.xz
 97a66103875aa76e786745576539475a644d481c 6580 fplll_5.4.4-3_source.buildinfo
Checksums-Sha256:
 425090dd89772e79d8f5e0dfef8b9e55022ef0aa3ea82d14e1e125e200f7d32b 2149 
fplll_5.4.4-3.dsc
 2614dcec71a608827d4ce1e151fe70d0509aa9501ca469309825af2eeffbdbae 8920 
fplll_5.4.4-3.debian.tar.xz
 dc4a1b3dbe4256c8a96ec15bac1eaec5aaab7840efdb5fb1d6be7b935504c31a 6580 
fplll_5.4.4-3_source.buildinfo
Files:
 a664cecb2a4ff5a3891ec56a95130f76 2149 math optional fplll_5.4.4-3.dsc
 674e2e988f28e0e3a116102dd8b089ef 8920 math optional fplll_5.4.4-3.debian.tar.xz
 f3a487c17c163440a2dcca259552805e 6580 math optional 
fplll_5.4.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmPFC5ISHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRd3kP/RShLoSlG1YqRFfD5/FWofbz3jKBxRaF
bcJQp23NB/LPnHBepDxIytH6sn8sHBx1e2BlC1AWxBYrCzXbz5Iv1XcuF20DHTKk
ptcC1jaB8sPghW2xNZMgenC11QKx8yoPuc5SdqiQDugqT4C9QJ/zyp5G+KQ/g7Kz
146/FV6QQ/aY+1lCk7ArzMvIZVmUfyO0rlXgJdOYSMVyb8q1zEPTk1Ml+BiBqzvu
vY4SKt9RxDwqYG6TIJ7OYSdFYO9A6RvS6lf+wXt3Xq0oEgeigBowDcZHMzWQJdiV
TG6iXLpq/DKE7JwF42oeiL317DKXIM5OsA4dy7uFtl991SDSjohon2Ndy4lkz6Xe
3X4pAzWlTGbh1AeWWQou8EsMfI05bGSwSpT7dqBBUxumqTchuAYTbyLVx+p3/B6r
uKKYFfaaKCacF+IZc90fwElP+TzgCTGbyJWceSWXSIq15Is+iu/q6gWXZgW/ADt1
khQeWmgpecbqvw6nB0vaAD2FngfkxqdI4rzGbDrrGqDdasEZqdHli9vqkJMQXvRE
NiZrbGzxkouzC5DvdQN+NTsBcdtkl4jT9KpVY7gxNyVW1rbDwt6LG9xslXd8BStx
2RYo8y2VR1BlQNPSoEsQ4k122kngwD5KZeFzqb+vWSnxfXcNXtLLhQJeRwSw6k3S

Bug#1027222: marked as done (gammapy: autopkgtest fail with numpy/1.24.1)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jan 2023 09:05:08 +
with message-id 
and subject line Bug#1027222: fixed in gammapy 1.0-2
has caused the Debian Bug report #1027222,
regarding gammapy: autopkgtest fail with numpy/1.24.1
to be marked as done.

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

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


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

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

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

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

Several of the errors are in the form of:

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

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

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

some deprecations introduced in 1.20.0

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

(released almost 2 years ago).

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

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

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

Regards,
Sandro
--- End Message ---
--- Begin Message ---
Source: gammapy
Source-Version: 1.0-2
Done: Ole Streicher 

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated gammapy 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, 16 Jan 2023 08:59:35 +0100
Source: gammapy
Architecture: source
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1027222
Changes:
 gammapy (1.0-2) unstable; urgency=medium
 .
   * Replace deprecated numpy type aliases (Closes: #1027222)
   * Push Standards-Version to 4.6.2, no changes needed
   * Fix inhomogeneous array shape deprecation
Checksums-Sha1:
 66b09dbfa3f88f7555653e2b67104041674f325a 2512 gammapy_1.0-2.dsc
 4a652f6f9cd497f6cd84135eba4d035c853c5e08 8940 gammapy_1.0-2.debian.tar.xz
Checksums-Sha256:
 1d44cfdd42b217d937516579a7e63d0144fead577df3665242d00f5c9aefe8d2 2512 
gammapy_1.0-2.dsc
 e3e59d1399a2935e41cffcf94b777bf581dc1491901bca75375b2a2c5eb34fef 8940 
gammapy_1.0-2.debian.tar.xz
Files:
 1c019f5e2e684313a44c4e872ff3a380 2512 python optional gammapy_1.0-2.dsc
 ae05256d7fd6115b4486ef52962005b0 8940 python optional 
gammapy_1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmPFC2wACgkQcRWv0HcQ
3PfxOxAAzeJtb6hPFW6DdWK4iqVKI47tt2VuWSy1JQl4EpBUx5VmZsMud9k6pT9L
+1Zd+bjrYiSU2Zzz41UMnGetxszjxqJuWzXaec7+Jmcn8zCV1Yizkm0n71tLQXn4
r6fSt8O93Jfjx3wcKzvoqPC4chS6xZ+IHUJqsg4HtOs4grBLSmRthk8+uDX3/FvI
HK3brCVLkAgwvpPA6UEvKGb1w7YfE7UxzbRVmaEdHISnNe5rVKCgqnFR+bwYd7Vj
HBue53CYQBPPlARYlclvCgVyDg9l+ZtLXJzjhfvPi/PXIQtcyCmpYLCkZH40+vXv
II2n3yvmCNYmhe2tJKTcwxI52QjL1yxo2+Gl4iIogaUNo5ejfo4oagbg/DQE85YY
8pK2Kbe9/W9Eod925hVbb3ylm0Ivlbi5EhtogEosv8uWHNK/QcJFB3heLXxUjugL
VcCSdG1rGXC7/mkvCnS+1Ra7gXYpt1oxiOz8Eh3+lc1mSin+D8aen6095UBocZ9F
ljHrluZxIFl5UYfrU21NKblVc6GHLsAVBftg7A5PKbr5W2/jgfQpwK2n/nnQIsZo
hcE+0DbvhcCmWJzqUEGVI//25/0xDqODsjSR5SxKZYqcArKfASZr+y+jpxaL6qPE
J0q4ebFFP1arE/Nx3EIvnE5LyNVzix19wRMscWljZM5MKpLUZg8=
=NI/D
-END PGP SIGNATURE End Message ---

Processed: Re: vedo: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027210 [src:vedo] vedo: autopkgtest fail with numpy/1.24.1
Added tag(s) patch.

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

Processed: forcibly merging 1027210 1028698

[Debian Bug Tracking System]

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

> forcemerge 1027210 1028698
Bug #1027210 [src:vedo] vedo: autopkgtest fail with numpy/1.24.1
Bug #1028698 [src:vedo] vedo: FTBFS: AttributeError: module 'numpy' has no 
attribute 'warnings'
Added tag(s) patch.
Bug #1027210 [src:vedo] vedo: autopkgtest fail with numpy/1.24.1
Added tag(s) bookworm, sid, and ftbfs.
Merged 1027210 1028698
> thanks
Stopping processing here.

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

Bug#1027210: vedo: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/science-team/vedo/-/commit/38552518c68ac46d03de940c6b4ed88aa987962a

Kind Regards,

Bas

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

Processed: Re: tpot: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027205 [src:tpot] tpot: autopkgtest fail with numpy/1.24.1
Added tag(s) patch.

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

Bug#1027205: tpot: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/science-team/tpot/-/commit/b7989129ccecae0b9cff9a3fa5b863a0d551815e

Kind Regards,

Bas

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

Processed: forcibly merging 1027228 1028755

[Debian Bug Tracking System]

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

> forcemerge 1027228 1028755
Bug #1027228 [src:quintuple] quintuple: autopkgtest fail with numpy/1.24.1
Bug #1028755 [src:quintuple] quintuple: FTBFS: AttributeError: module 'numpy' 
has no attribute 'complex'. Did you mean: 'complex_'?
Added tag(s) patch.
Bug #1027228 [src:quintuple] quintuple: autopkgtest fail with numpy/1.24.1
Added tag(s) ftbfs.
Merged 1027228 1028755
> thanks
Stopping processing here.

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

Bug#1029000: yoyo: (autopkgtest) needs update for Python 3.11

[Graham Inggs]

Source: yoyo
Version: 7.3.2+dfsg1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Hi Maintainer

The autopkgtests of yoyo fail with Python 3.11 as the default version
(and Python 3.10 still supported) [1].  I've copied what I hope is the
relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/y/yoyo/testing/amd64/


Creating new PostgreSQL cluster 15/regress ...
Warning: connection to the database failed, disabling startup checks:
psql: error: connection to server on socket "/tmp/.s.PGSQL.5433"
failed: FATAL:  role "debci" does not exist

+ export 
PYTHONPATH=/tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src/debian/tests
+ PYTHONPATH=/tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src/debian/tests
+ psql -Upostgres -c 'create database yoyo_test;'
CREATE DATABASE
+ pytest-3 yoyo/tests
= test session starts ==
platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
rootdir: /tmp/autopkgtest-lxc.z8fl1tkb/downtmp/build.X7w/src
collected 152 items

yoyo/tests/test_backends.py ..ss..s.s..  [ 15%]
yoyo/tests/test_cli_script.py ..s.s. [ 42%]
.[ 43%]
yoyo/tests/test_config.py ...[ 53%]
yoyo/tests/test_connections.py   [ 58%]
yoyo/tests/test_internalmigrations.py    [ 63%]
yoyo/tests/test_migrations.py .. [ 91%]
..FF [ 96%]
yoyo/tests/test_utils.py .   [100%]

=== FAILURES ===
__ TestPostApplyHooks.test_it_runs_multiple_post_apply_hooks ___

self = 
backend_sqlite3 = 

def test_it_runs_multiple_post_apply_hooks(self, backend_sqlite3):
with migrations_dir(
**{
"a": "step('create table postapply (i int)')",
"post-apply": "step('insert into postapply values (1)')",
"post-apply2": "step('insert into postapply values (2)')",
}
) as tmpdir:
>   backend_sqlite3.apply_migrations(
backend_sqlite3.to_apply(read_migrations(tmpdir))
)

yoyo/tests/test_migrations.py:611:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
yoyo/backends.py:449: in apply_migrations
self.apply_migrations_only(migrations, force=force)
yoyo/backends.py:461: in apply_migrations_only
self.apply_one(m, force=force)
yoyo/backends.py:507: in apply_one
migration.process_steps(migration_backend, "apply", force=force)
yoyo/migrations.py:272: in process_steps
raise exc_info[1].with_traceback(exc_info[2])
yoyo/migrations.py:257: in process_steps
getattr(step, direction)(backend, force)
yoyo/migrations.py:315: in apply
getattr(self.step, direction)(backend, force)
yoyo/migrations.py:411: in apply
self._execute(cursor, self._apply)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = , cursor = 
stmt = 'create table postapply (i int)'
out = <_io.TextIOWrapper name="<_io.FileIO name=6 mode='rb+'
closefd=True>" mode='r+' encoding='utf-8'>

def _execute(self, cursor, stmt, out=None):
"""
Execute the given statement. If rows are returned, output these in a
tabulated format.
"""
if out is None:
out = sys.stdout
if isinstance(stmt, str):
logger.debug(" - executing %r", stmt.encode("ascii", "replace"))
else:
logger.debug(" - executing %r", stmt)
>   cursor.execute(stmt)
E   sqlite3.OperationalError: table postapply already exists

yoyo/migrations.py:381: OperationalError
___ TestPostApplyHooks.test_apply_migrations_only_does_not_run_hooks ___

self = 
backend_sqlite3 = 

def test_apply_migrations_only_does_not_run_hooks(self, backend_sqlite3):
with migrations_dir(
**{
"a": "step('create table postapply (i int)')",
"post-apply": "step('insert into postapply values (1)')",
}
) as tmpdir:
>   backend_sqlite3.apply_migrations_only(
backend_sqlite3.to_apply(read_migrations(tmpdir))
)

yoyo/tests/test_migrations.py:625:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
yoyo/backends.py:461: in apply_migrations_only
self.apply_one(m, force=force)
yoyo/backends.py:507: in apply_one
migration.process_steps(migration_backend, "apply", force=force)
yoyo/migrations.py:272: in process_steps
raise 

Processed: Re: astroplan: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027189 [src:astroplan] astroplan: autopkgtest fail with numpy/1.24.1
Added tag(s) patch.

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

Bug#1027189: astroplan: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/debian-astro-team/astroplan/-/commit/43fe7901581c7572200bd5aefabc17e00d08544f

Kind Regards,

Bas

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

Processed: yoyo: (autopkgtest) needs update for Python 3.11

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1029000 [src:yoyo] yoyo: (autopkgtest) needs update for Python 3.11
Added indication that 1029000 affects src:python3-defaults

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

Processed: Re: pymca: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027240 [src:pymca] pymca: autopkgtest fail with numpy/1.24.1
Added tag(s) patch.

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

Bug#1027240: pymca: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/science-team/pymca/-/commit/7bb6e5ac06650d3433dcd23f3005aa349bebecc7

Kind Regards,

Bas

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

Processed: Re: python-bayespy: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027220 [src:python-bayespy] python-bayespy: autopkgtest fail with 
numpy/1.24.1
Added tag(s) patch.

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

Bug#1027220: python-bayespy: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/science-team/python-bayespy/-/commit/7ea04cff193c5124d56f99eba2dfd4daa48feed4

Kind Regards,

Bas

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

Processed: python-stem: (autopkgtest) needs update for Python 3.11

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1028998 [src:python-stem] python-stem: (autopkgtest) needs update for 
Python 3.11
Added indication that 1028998 affects src:python3-defaults

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

Processed: Re: python-pymbar: autopkgtest fail with numpy/1.24.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1027217 [src:python-pymbar] python-pymbar: autopkgtest fail with 
numpy/1.24.1
Added tag(s) patch.

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

Bug#1027217: python-pymbar: autopkgtest fail with numpy/1.24.1

[Sebastiaan Couwenberg]

Control: tags -1 patch

A patch has been committed in git:


https://salsa.debian.org/science-team/python-pymbar/-/commit/731962ad419521a78c753ef6010ef3bed9980663

Kind Regards,

Bas

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