Bug#997672: ITP: sphinx-book-theme -- clean book theme for scientific explanations and documentation with Sphinx

[Sandro Tosi]

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 
X-Debbugs-Cc: debian-de...@lists.debian.org, mo...@debian.org

* Package name: sphinx-book-theme
  Version : 0.1.6
  Upstream Author : Chris Holdgraf
* URL : https://sphinx-book-theme.readthedocs.io/en/latest/
* License : BSD-3
  Programming Lang: Python
  Description : clean book theme for scientific explanations and 
documentation with Sphinx

This is a new dependency of sphinx-copybutton

Note to self: when this package is accepted from NEW we can revert
https://salsa.debian.org/python-team/packages/sphinx-copybutton/-/commit/22efbdfdfee66c121191e33e74ff21d6aae27fd3

Bug#884575: ITP: syncthingtray -- a tray applet, plasmoid, and Dolphin integration for Syncthing

[Nicholas D Steeves]

Hi Hannah,

Hannah Rittich  writes:

> Hi,
>
> I have created a patch set which allows to specify a prefix for the
> files and directories that are installed into system directories. These
> patches have also been accepted by the upstream author. Thus, the
> packages cpputilities and qtutilities can be installed using a more
> specific naming.
>

Wow!  I'm sorry for holding you back, this is excellent work.

> I have updated the Debian packages for cpp-utilities, qtutilities, and
> Syncthing Tray to include the patches and renamed the source packages.
> The sources are on Salsa.
>
> How do we proceed now?
>

Have you read any of the New Maintainer Docs, and Debian Policy?  Are
you familiar with Lintian?  Expectations for all uploads are that
they're Policy-compliant, DFSG-free, and Lintian-clean.  It's also worth
reading the ftpmaster "Reject FAQ for Debian's NEW-Queue".

First, file ITP (Intent to Package) bug reports for the two dependencies
using their prefixed source package names.  You will close these bugs in
each package's first changelog entry.  This is required.  Yes, I was
lazy and didn't file ITPs for cpp-utilities, qtutilities--even though I
was working on them.  Yes, I should have filed them.

There is no need to file an RFS (Request for Sponsorship) for these
three packages, because I've committed to reviewing and sponsoring them.

You'll also need to do a formal copyright review which is (infamously)
not fun for most people.  I've already done the reviews on my copies, so
if you'd like to skip this for these three packages, I'm completely ok
with it and can just merge my work.  Formal copyright reviews are also
part of the basic skill-set for Debian packaging work.  Part of this
also requires identifying binary blobs, embedded copies, and assets of
questionable origin.

  https://www.debian.org/social_contract
  https://wiki.debian.org/DebianFreeSoftwareGuidelines
  https://wiki.debian.org/DFSGLicenses

Let me know if you prefer to do a copyright review on these packages, or
save it for another time.

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#993680: transition: proj

[Sebastiaan Couwenberg]

On 10/23/21 08:27, Sebastiaan Couwenberg wrote:

On 10/22/21 6:17 PM, Sebastiaan Couwenberg wrote:

On 10/22/21 5:51 PM, Sebastiaan Couwenberg wrote:

On 10/22/21 1:49 PM, Sebastiaan Couwenberg wrote:

On 10/22/21 11:19 AM, Sebastiaan Couwenberg wrote:

On 10/21/21 11:17 PM, Sebastian Ramacher wrote:

On 2021-09-04 19:49:39 +0200, Bas Couwenberg wrote:

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org
Control: forwarded -1 https://release.debian.org/transitions/html/auto-proj.html
Control: block -1 by 983222 983224 983229 983230 983253 983254 983299 983345

For the Debian GIS team I'd like to transition to PROJ 8.


Please go ahead. Please also raise  the remaining FTBFS bugs to serious.


proj (8.1.1-1) and python-cartopy (0.20.1+dfsg-1) have been uploaded to
unstable. And the severity of the bugreports has been raised to serious.

Thanks for already scheduling the dependency level 2 NMUs, these are
almost done except for mips64el where they had to wait for proj to be
installed which it is now.


libgeotiff & spatialite are built & installed on all release
architectures, dependency level 3 can be NMUed now.


magics++ is built and installed on all release architectures, cdo can be
NMUed now.


gdal is now also built & installed on all release architectures, the
rest of dependency level 4 can be NMUed now too.


grass and r-cran-sf are built & installed on all release architectures,
qgis and r-cran-lwgeom can be NMUed.

The rest of dependency level 5 is waiting for vtk9 which will take a bit
more time.


vtk9 is now also built & installed on all release architectures, the 
rest of dependency level 5 can also be NMUed now.


Kind Regards,

Bas

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

Bug#997664: sundials: apparent ABI bumps in sundials5 library packages

[Anton Gladky]

Hi Drew,

Thanks for the catch!

yes,  library splitting is somehow strange in this package. We should
probably split it in much more sublibs to escape such situations in the
future.

Regards

Anton

Drew Parsons  schrieb am So., 24. Okt. 2021, 02:18:

> Source: sundials
> Version: 5.7.0+dfsg-1
> Severity: normal
>
> Unless I misunderstood the package naming system for sundials, looks
> like there was an ABI bump in sublibraries when sundials upgraded from
> v4 to v5.
>
> It can be seen in 5.7.0+dfsg-1, so it's not a side-effect of the the new
> 5.8.0 build (hence no need to block 5.8.0 with severity Serious).
>
> The apparently upgraded libraries are
>
> arkode3  ->  arkode4  (libsundials_arkode.so.4)
> cvode[s]4  ->  cvodes5  (libsundials_cvode[s].so.5 )
> ida[s]4  ->  ida5  (libsundials_ida[s].so.5)
> kinsol4  ->  kinsol5  (libsundials_kinsol.so.5)
> nvecserial4 ->  nvecserial5  (libsundials_nvecserial.so.5)
> sunmatrix2  ->  sunmatrix3   (libsundials_sunmatrixband.so.3 etc)
> sunlinsol2  ->  sunlinsol3   (libsundials_fsunlinsolband.so.3 etc, and
> other anomalies)
>
> nvecparallel-XX4  ->  nvecparallel-XX5 (libsundials_nvecXX.so.5)
> (XX = pthread, petsc, openmp, mpi, hypre)
>
> --
> debian-science-maintainers mailing list
> debian-science-maintain...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
>

Bug#973313: The locales package not installed in salsa lintian Docker image

[Felix Lechner]

Hi 肖盛文

On Sat, Oct 23, 2021 at 8:51 PM xiao sheng wen  wrote:
>
> Is this  the root case of this bug?

Possibly. I thought I had looked into the locales question with Iñaki
Malerba from the Salsa CI Team about a year ago. If you found it, I am
going to have a party!

The messages have never been reported in any other setting. Just this
morning, I was again unable to reproduce the messages on my local
system with

docker run --rm -it --privileged
registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable bash

and concluded that Salsa's host system was probably to blame. The
shared runner operates in 'privileged' mode. [1]

I also contemplated other methods making the C.UTF-8 locale available
via the Docker file. [2]

I'll look into the Salsa runner package list again, unless you beat me to it.
Thanks!

Kind regards
吴大菲 (Felix Lechner)

[1] https://www.educba.com/docker-privileged/
[2] https://leimao.github.io/blog/Docker-Locale/

Bug#884575: ITP: syncthingtray -- a tray applet, plasmoid, and Dolphin integration for Syncthing

[Nicholas D Steeves]

Hi Alexandre and Hannah,

So sorry for the unreasonably long delay, reply follows inline:

Alexandre Viau  writes:

> Hello Nicholas, Hannah,
>
>> Oh, and Alexandre was my first Debian contact.
>
> Aww. This is giving me Debconf nostalgia <3.
>

That's wonderful to hear <3  I look forward to meeting up again when
the covid situation allows for it :-)

>> I'm CCing you to ask if you'd appreciate help packaging deps for
>> Syncthing 1.18.2,
>
> Help for packaging new dependencies of syncthing is always welcome!
>

Sweet :-)  Distribution of labour FTW ;-)

> I have the habit of keeping a TODO list in the changelog:
> - 
> https://salsa.debian.org/go-team/packages/syncthing/-/blob/b356f757a44765ff2bb1e2a53df6d64b08dbdd25/debian/changelog
>

Nice, that's a great habit which I'm now considering adopting, and thank
you for the link!

> I am not very territorial with my TODO list. Feel free to steal as
> many tasks as you like. If it ever runs out, I am sure we can add even
> more things to it ;).
>

Haha, oh my!  I will have to wait to respond until a window when I have
more time/energy ;-)  Regrettably, both have been in short supply this
last month.

> At the time of writing this email, there are three things that need to be 
> done:
> - Bump the version of github.com/shirou/gopsutil/v3/disk in Debian
> - Package github.com/AudriusButkevicius/recli
> - Package github.com/flynn-archive/go-shlex
>

Hannah, so these are fair game if you're interested in Golang.  As
dependencies for Syncthing, I think it would be best if these go under
Debian Go Packaging Team maintenance if you decide to work on them.  Oh,
and to indirectly answer your question about team maintenance...  There
is a rule in Debian: No one can force you work on anything.  Also, we
have a social contract and a CoC, so if someone tries to guilt/shame you
into doing work, that's wrong too!

  https://wiki.debian.org/SponsoredMaintainer
  https://go-team.pages.debian.net/

If your eventual objective is "Debian Maintainer" or "Debian Developer"
status, then it may be useful to cultivate a rapport with another DD,
because you'll need two advocates for the application.  It's totally
optional, of course!


Humble regards,
Nicholas


signature.asc
Description: PGP signature

Bug#973313: The locales package not installed in salsa lintian Docker image

[肖盛文]

Hi,

    The Docker images provided by Salsa CI:

registry.salsa.debian.org/salsa-ci-team/pipeline/lintian:unstable

It has not install the locales package.

The locales.postinst of locales package can set the LC_ALL, LANG and 
generate some files,etc.


Is this  the root case of this bug?


--
肖盛文 xiao sheng wen Faris Xiao
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_0x00186602339240CB.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#884575: ITP: syncthingtray -- a tray applet, plasmoid, and Dolphin integration for Syncthing

[Nicholas D Steeves]

Hi Hannah,

I'm sorry for the unreasonably long delay. (this was a draft from
late Sept) Reply follows inline:

Hannah Rittich  writes:
>
> I think a prefix would be nicer, and I think it should not be too hard
> to add configuration name prefix switch. I would like to check if this
> is a feasible option. In case it is not too much work and the upstream
> author is willing to merge those changes, we could get a proper prefix
> to the package name. Otherwise, I would suggest to stick with a suffix
> for ease of maintenance.
>

Agreed, and I just noticed that I missed your Oct 5th email which
addresses this directly.  Once again, sorry, you deserve more timely
replies.

>> Wow!  Yes, I will definitely sponsor your work :-)  How do you feel
>> about comaintaining these packages in the "debian" group (used to be
>> called collab-maint)?
>
> I am happy to share the responsibility with a team. Would that mean any
> additional obligations for me?
>

For the "debian" group, no additional obligations, and no interference
from evolving team policies which you may or may not appreciate.  The
undocumented (as far as I know) conventions of this group are as
follows:

  1. All DDs have commit access (as a rule rather than convention)
  2. If necessary, most DDs will usually file patches on the BTS, or
  might submit an MR if they're enabled
  3. Even though all DDs have commit access, uploads for NMUs follow the
  usual conventions.  So only NMUs for RC bugs in the case of
  unresponsive maintainers.  It's a fair expectation that in time you'll
  be granted permissions to upload, should you wish to pursue the
  "Debian Maintainer" role.
  https://wiki.debian.org/DebianMaintainer

>> Syncthing for Debian tends to lag behind upstream, and we'll need to 
>> ignore or remove the embedded copy of libsyncthing in Syncthing
>> Tray. In terms of long-term maintenance it looks like Syncthing Tray
>> updates will need to block for Syncthing (and its new deps) uploads.
>> I forget if I uploaded the packages or not, but at some point I
>> worked on packaging new Golang deps for Syncthing, and it wasn't as
>> difficult as I had expected.  I'll wait for Alexandre's ACK before
>> asking you if you're also interested in Golang packaging ;-)
>
> I am a bit confused here. I though libsyncthing is a part of Syncthing
> Tray. I could not find the sources anywhere else. Are they actually part
> of some other package? Where do I find the sources?
>

I think these links will be enough for you to figure it out:
  
https://martchus.no-ip.biz/gitea/Martchus/syncthingtray/commit/6ab7662a649bb10edb1a15e8da542aca87317fa1
  https://github.com/Martchus/syncthingtray/tree/master/libsyncthing
  
https://github.com/Martchus/syncthing/tree/0b016895447adea3e8537f27cff045cabf5c128a
  https://github.com/syncthing/syncthing

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#997671: ITP: sphinx-panels -- sphinx extension for creating panels in a grid layout

[Sandro Tosi]

Package: wnpp
Severity: wishlist
Owner: Sandro Tosi 
X-Debbugs-Cc: debian-de...@lists.debian.org, mo...@debian.org

* Package name: sphinx-panels
  Version : 0.6.0
  Upstream Author : Executable Books
* URL : https://sphinx-panels.readthedocs.io/en/latest/
* License : MIT
  Programming Lang: Python
  Description : sphinx extension for creating panels in a grid layout

this is a new dependency for matplotlib doc

note to self: when this is accepted from NEW, we can revert
https://salsa.debian.org/python-team/packages/matplotlib/-/commit/be2cec2dcb2ed8d6f0b9a9a2ecb08249e1e2ee48

Bug#997670: bookworm: crashes with glibc heap consistency checking turned on

[Paul Wise]

Package: bookworm
Version: 1.1.2+git20210715-2
Severity: normal
Usertags: crash
File: /usr/bin/com.github.babluboy.bookworm

When I turn on glibc heap consistency checking, bookworm crashes at
startup. From the gdb trace it looks like it is trying to g_strdup a
pointer that has not been initialised. Also valgrind indicates an
invalid memory read, which is probably cause of the crash.

https://www.gnu.org/software/libc/manual/html_node/Heap-Consistency-Checking.html
https://udrepper.livejournal.com/11429.html

$ export MALLOC_CHECK_=2
$ export MALLOC_PERTURB_=$((0xF0))

$ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' --args 
com.github.babluboy.bookworm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory.
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x7718eab4 in g_strdup (str=0x7f0f0f0f0f0f0d1 ) at ../../../glib/gstrfuncs.c:363
#2  0x77389a67 in add_packed_option (entry=0x7fffd290, 
application=0x5580c120 [BookwormAppBookworm]) at 
../../../gio/gapplication.c:648
#3  g_application_add_main_option_entries 
(application=application@entry=0x5580c120 [BookwormAppBookworm], 
entries=) at ../../../gio/gapplication.c:740
#4  0x55567a8d in bookworm_app_bookworm_constructor (type=, n_construct_properties=, 
construct_properties=0x557b1bf0) at ../src/bookworm.vala:116
#5  0x77268ab8 in g_object_new_with_custom_constructor (n_params=2, 
params=0x7fffd470, class=0x55801200) at ../../../gobject/gobject.c:1863
#6  g_object_new_internal (class=class@entry=0x55801200, 
params=params@entry=0x7fffd470, n_params=n_params@entry=2) at 
../../../gobject/gobject.c:1943
#7  0x7726a508 in g_object_new_valist (object_type=0x557fb220 
[BookwormAppBookworm/GraniteApplication/GtkApplication/GApplication], 
first_property_name=first_property_name@entry=0x555ad74b "application-id", 
var_args=var_args@entry=0x7fffd740) at ../../../gobject/gobject.c:2288
#8  0x7726aa39 in g_object_new (object_type=, 
first_property_name=first_property_name@entry=0x555ad74b "application-id") 
at ../../../gobject/gobject.c:1788
#9  0x555676c5 in bookworm_app_bookworm_construct 
(object_type=) at ../src/bookworm.vala:120
#10 bookworm_app_bookworm_new () at ../src/bookworm.vala:119
#11 bookworm_app_bookworm_getAppInstance () at ../src/bookworm.vala:136
#12 0x555633fb in _vala_main (args_length1=, 
args=) at ../src/main.vala:23
#13 main (argc=, argv=) at ../src/main.vala:20
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120
#1  0x7718eab4 in g_strdup (str=0x7f0f0f0f0f0f0d1 ) at ../../../glib/gstrfuncs.c:363
new_str = 
length = 
#2  0x77389a67 in add_packed_option (entry=0x7fffd290, 
application=0x5580c120 [BookwormAppBookworm]) at 
../../../gio/gapplication.c:648
__func__ = "add_packed_option"
my_entries = {{long_name = 0x7f0f0f0f0f0f0d1 , short_name = -127 '\201', flags = 0, arg 
= G_OPTION_ARG_NONE, arg_data = 0x557b2e30, description = 0x0, 
arg_description = 0x1 }, {long_name 
= 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 
0x0, description = 0x0, arg_description = 0x0}}
i = 0
__func__ = "g_application_add_main_option_entries"
#3  g_application_add_main_option_entries 
(application=application@entry=0x5580c120 [BookwormAppBookworm], 
entries=) at ../../../gio/gapplication.c:740
my_entries = {{long_name = 0x7f0f0f0f0f0f0d1 , short_name = -127 '\201', flags = 0, arg 
= G_OPTION_ARG_NONE, arg_data = 0x557b2e30, description = 0x0, 
arg_description = 0x1 }, {long_name 
= 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 
0x0, description = 0x0, arg_description = 0x0}}
i = 0
__func__ = "g_application_add_main_option_entries"
#4  0x55567a8d in bookworm_app_bookworm_constructor (type=, n_construct_properties=, 
construct_properties=0x557b1bf0) at ../src/bookworm.vala:116
obj = 0x5580c120 [BookwormAppBookworm]
parent_class = 
self = 0x5580c120 [BookwormAppBookworm]
_tmp0_ = 
_tmp1_ = 
_tmp2_ = 
_tmp3_ = 
_tmp4_ = 
_tmp5_ = 
_tmp6_ = 
_tmp7_ = {long_name = 0x555ad1c6 "version", short_name = 0 '\000', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x557933d4 
, description = , arg_description = }
_tmp8_ = 
_tmp9_ = {long_name = 0x555ad1d0 "debug", short_name = 0 '\000', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x557933d0 
, description = , arg_description = }
_tmp10_ = 
_tmp11_ = {long_name = 0x555ad1d8 "info", 

Bug#997669: RFS: dedalus/2.2006-1 [ITP] -- Dedalus is a framework for solving partial differential equation

[Mac Lee]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dedalus":

* Package name : dedalus
Version : 2.2006-1
Upstream Author : Keaton J. Burns 
* URL : https://dedalus-project.org/
* License : GPL-3
* Vcs : g...@github.com:macthecadillac/dedalus.git
Section : python

It builds those binary packages:

python3-dedalus - Dedalus is a framework for solving partial differential 
equation

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/dedalus/

Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/d/dedalus/dedalus_2.2006-1.dsc

Changes for the initial release:

dedalus (2.2006-1) UNRELEASED; urgency=low
.
* Initial release.

Regards,

Mac Lee

Bug#997488: [Debian-med-packaging] Bug#997488: q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Étienne Mollier]

Control: tags -1 + confirmed

Aloha,

From looking up ci.debian.net [1], this q2cli issue seems
related to a recent upgrade of python-click 8.0.2.

[1]: https://ci.debian.net/packages/q/q2cli/testing/amd64/

The multiple failures are probably all related to the following
issue, which can be simply triggered with the --version flag:

$ qiime --version
Traceback (most recent call last):
  File "/usr/bin/qiime", line 33, in 
sys.exit(load_entry_point('q2cli==2021.8.0', 'console_scripts', 
'qiime')())
  File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in 
__call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1050, in 
main
with self.make_context(prog_name, args, **extra) as ctx:
  File "/usr/lib/python3/dist-packages/click/core.py", line 912, in 
make_context
self.parse_args(ctx, args)
  File "/usr/lib/python3/dist-packages/q2cli/click/command.py", line 
43, in parse_args
return super().parse_args(ctx, args)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1613, in 
parse_args
rest = super().parse_args(ctx, args)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1364, in 
parse_args
parser = self.make_parser(ctx)
  File "/usr/lib/python3/dist-packages/q2cli/click/command.py", line 
33, in make_parser
param.add_to_parser(parser, ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 2639, in 
add_to_parser
parser.add_option(
  File "/usr/lib/python3/dist-packages/q2cli/click/parser.py", line 
126, in add_option
option = Q2Option(opts, dest, action=action, nargs=nargs,
TypeError: __init__() got multiple values for argument 'obj'

Have a good night,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from my alarm clock


signature.asc
Description: PGP signature

Bug#997031: nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup

[Andreas Beckmann]

Control: found -1 11.2.152~11.2.2-3
Control: found -1 11.3.109~11.3.1-4
Control: retitle -1 nvidia-cuda-gdb: cuda-gdb 'Segmentation fault' at startup 
if libpython2.7 is installed

On 22/10/2021 19.11, Tim Trant wrote:

"gdb /usr/bin/cuda-gdb" and "strings /usr/bin/cuda-gdb" suggest that there's a 
hidden
use of libpython2.7.so.1 which is failing.


cuda-gdb is (after some patching) built against python3, but nvidia has
made changes that attempt to dlopen the libpythonX.Y.so.1, but only for 2.Y.
So if libpython2.7 is installed, it will crash, since 2.7 and 3.x do not
seem to be binary compatible. If it is not installed, python support
will simply not work.

In experimental (based on gdb 10.1) it does at least not segfault, but
python seems to work neither.

At least for stable (and propagating to oldstable-backports) I'll just
build without python support ...


Andreas

Bug#982298: dh-python: deprecated test command 'python3.9 setup.py test'

[Stefano Rivera]

Hi Piotr (2021.10.22_11:06:02_-0700)
> I'm doing some testing to see what effect this will have. There are
> about 500 affected packages, as far as I can tell.

So, about 50 of them fail to build with this change (and a couple go
from FTBFS to building successfully):

--- setuppy-test-failed 2021-10-24 01:50:12.702126456 +
+++ unittest-failed 2021-10-24 01:50:21.006070451 +
@@ -1,29 +1,75 @@
+autopep8_1.5.7-1_arm64.build:Status: attempted
+black_21.4b2-3_arm64.build:Status: attempted
 blessings_1.6-3_arm64.build:Status: attempted
-blist_1.3.6-7_arm64.build:Status: attempted
+debmutate_0.45_arm64.build:Status: attempted
+django-classy-tags_2.0.0-1_arm64.build:Status: attempted
+django-guardian_2.4.0-1_arm64.build:Status: attempted
+django-prometheus_2.1.0-1_arm64.build:Status: attempted
+django-recurrence_1.10.3-1_arm64.build:Status: attempted
 django-restricted-resource_2016.8-3_arm64.build:Status: attempted
+django-sekizai_2.0.0-4_arm64.build:Status: attempted
 doxypypy_0.8.8.6-4_arm64.build:Status: attempted
+elasticsearch-curator_5.8.1-1_arm64.build:Status: attempted
+factory-boy_2.11.1-3_arm64.build:Status: attempted
 fail2ban_0.11.2-2_arm64.build:Status: attempted
+flask-autoindex_0.6.6-2_arm64.build:Status: attempted
 flask-migrate_2.6.0-1_arm64.build:Status: attempted
+flask-testing_0.8.1-1_arm64.build:Status: attempted
 frozen-flask_0.11-3.1_arm64.build:Status: attempted
 glue_0.13-5_arm64.build:Status: attempted
 hydroffice.bag_0.2.15-3_arm64.build:Status: attempted
 khard_0.17.0-2_arm64.build:Status: attempted
+lazr.uri_1.0.6-1_arm64.build:Status: attempted
+lesana_0.8.1-1_arm64.build:Status: attempted
+lttnganalyses_0.6.1-2_arm64.build:Status: attempted
+magic-wormhole_0.12.0-1_arm64.build:Status: attempted
+manuel_1.10.1-2_arm64.build:Status: attempted
+mmllib_0.3.0.post1-2_arm64.build:Status: attempted
+multiprocess_0.70.12.2-1_arm64.build:Status: attempted
 nose_1.3.7-7_arm64.build:Status: attempted
 objgraph_3.5.0-3_arm64.build:Status: attempted
 pelican_4.0.1+dfsg-1.1_arm64.build:Status: attempted
+pocketsphinx-python_0.1.15-2_arm64.build:Status: attempted
+ponyorm_0.7.14-1_arm64.build:Status: attempted
+powerline_2.8.2-1_arm64.build:Status: attempted
 pygithub_1.43.7-1_arm64.build:Status: attempted
 pyliblo_0.10.0-4_arm64.build:Status: attempted
+pyramid-jinja2_2.7+dfsg-1.2_arm64.build:Status: attempted
 pyro4_4.80-1_arm64.build:Status: attempted
+pytables_3.6.1-5_arm64.build:Status: attempted
+python-applicationinsights_0.11.10-1_arm64.build:Status: attempted
+python-argcomplete_1.12.3-0.1_arm64.build:Status: attempted
+python-bitcoinlib_0.11.0-1_arm64.build:Status: attempted
+python-chameleon_3.8.1-1_arm64.build:Status: attempted
+python-ciso8601_2.2.0-1_arm64.build:Status: attempted
+python-configargparse_1.2.3-1_arm64.build:Status: attempted
+python-django-bootstrap-form_3.4-5_arm64.build:Status: attempted
+python-django-colorfield_0.4.5+ds1-1_arm64.build:Status: attempted
+python-django-ical_1.8.0-1_arm64.build:Status: attempted
 python-django-imagekit_4.0.2-3_arm64.build:Status: attempted
 python-django-registration_2.2-5_arm64.build:Status: attempted
+python-django-swapper_1.1.2-2_arm64.build:Status: attempted
+python-funcsigs_1.0.2-5_arm64.build:Status: attempted
 python-jsmin_2.2.2-2_arm64.build:Status: attempted
+python-launchpadlib_1.10.14-1_arm64.build:Status: attempted
+python-libais_0.17+git.20190917.master.e464cf8-2_arm64.build:Status: attempted
 python-libusb1_1.9.1-1_arm64.build:Status: attempted
+python-mpv_0.5.2-1_arm64.build:Status: attempted
+python-ofxhome_0.3.3-3_arm64.build:Status: attempted
+python-phabricator_0.7.0-1.1_arm64.build:Status: attempted
 python-pkginfo_1.4.2-3_arm64.build:Status: attempted
+python-pulp_2.5.1+dfsg-2_arm64.build:Status: attempted
+python-pylibdmtx_0.1.9-3_arm64.build:Status: attempted
 python-pyramid-multiauth_0.8.0-1.1_arm64.build:Status: attempted
 python-pyramid-zcml_1.0.0-1.2_arm64.build:Status: attempted
 python-slimmer_0.1.30-8_arm64.build:Status: attempted
-pytrainer_2.0.2-2_arm64.build:Status: attempted
+python-wadllib_1.3.6-1_arm64.build:Status: attempted
+python-zstd_1.4.5.1-3_arm64.build:Status: attempted
 pyvirtualdisplay_0.2.1-3_arm64.build:Status: attempted
-retweet_0.10-1.1_arm64.build:Status: attempted
+pyzbar_0.1.8-3_arm64.build:Status: attempted
+quark-sphinx-theme_0.5.1-2_arm64.build:Status: attempted
+silver-platter_0.4.3-1_arm64.build:Status: attempted
 simpleeval_0.9.10-1_arm64.build:Status: attempted
 supervisor_4.2.2-2_arm64.build:Status: attempted
+supysonic_0.6.2+ds-3_arm64.build:Status: attempted
+toro_1.0.1-4_arm64.build:Status: attempted

That's enough that I'm not about to just upload this to unstable, unless
someone persuades me that it's a good idea to.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#996104: dkms: Fail to remove modules

[Vincent Lefevre]

Control: tags -1 patch fixed-upstream

On 2021-10-22 18:35:55 +0700, Damir Islamov wrote:
> Tags 996104 patch fixed-upstream

Really tagging...

>  https://github.com/dell/dkms/commit/
> 64a882a32fdf126ef20e6b6403b5cb158dad21f4[1]

Without the line break:

https://github.com/dell/dkms/commit/64a882a32fdf126ef20e6b6403b5cb158dad21f4

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

Bug#997325: [Debian-med-packaging] Bug#997325: python-sqlsoup: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13

[Étienne Mollier]

Control: tag -1 confirmed

Greetings,

Lucas Nussbaum, on 2021-10-23:
> > Failure: ImportError (cannot import name 'MapperExtension' from 
> > 'sqlalchemy.orm.interfaces' 
> > (/usr/lib/python3/dist-packages/sqlalchemy/orm/interfaces.py)) ... ERROR

This one has the same symptom as the autopkgtest failure
documented in #995781, although not at the same stage.  I'm
tempted to merge both, as once the issue is fixed on one end,
the other one will be fixed as well.

The most likely outcome is that the package drops from Testing
though, given that a fix seems non-trivial, and the package is
not maintained upstream any more.

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#783550: mrtg: install didn't create /var/www/mrtg nor /etc/cron.d/mrtg

[Eriberto Mota]

Control: tags 783550 pending


Hi everyone,

About this bug:

> 1 No /var/www/mrtg directory was created

Fixed. I will send a new revision to Debian soon.

> 2 No mrtg.cfg file was created ANYWHERE

Fixed in a previous release.

> 3 No cronjob was added, i.e. no /etc/cron.d/mrtg file

Fixed in a previous release. However, in the next release the cronjob
will be dropped in favor of init.d and systemd scripts.

Thanks for your report.

Regards,

Eriberto

Bug#993324: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

[Dirk Eddelbuettel]

I have now 'patched' the upstream setting of GSL_AGE, this results (as kindly
analysed by Sebastian) in new sonames '26' so I prepared a new version which
just went out to unstable.

Unless I am mistaken, I need to get the release team on board for a proper
transition.  Correct?

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#997668: xen-tools: Incorrect security repo url for Jessie

[Diederik de Haas]

Hi Axel,

On Sunday, 24 October 2021 02:08:46 CEST Axel Beckert wrote:
> Diederik de Haas wrote:
> > enabled the security repo lines in /etc/apt/sources.list. But when doing
> > 'aptitude update', it reported that it couldn't find the repo.
> > Turns out that it uses 'jessie-security', what the section has become
> > since Bullseye, but it should be 'jessie/updates'. 
> > 
> > 'Strangely' enough, in my recently created Stretch VM, it did have
> > 'stretch/updates' in /e/a/sources.list, which is correct.
> 
> Yep, indeed. This is a bug introduced when I rewrote the
> differentiation between pre-bullseye and bullseye + later
> 
> There's a missing "|" in a regexp in hooks/debian/20-setup-apt. Small
> mistake, big effect.
> 
> It affects Wheezy as well btw. as the regexp uselessly matches
> "wheezyjessie" instead of "wheezy|jessie".
> 
> Fix committed locally. Will prepare a upstream minor bugfix release as
> well as a Debian upload to unstable at least.

That is quick, thanks!
I was pleasantly surprised how easy it was to create VMs for (to me) such old 
releases, so thanks for your tool :-)

Cheers,
  Diederik

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

Bug#997668: xen-tools: Incorrect security repo url for Jessie

[Axel Beckert]

Control: severity -1 important
Control: tag -1 + confirmed pending

Hi Diederik,

Diederik de Haas wrote:
> I have recently created a Jessie VM and noticed that there was (quite) a
> difference between the kernel I expected and the one that I had.
> I just learned that those are uploaded to security.debian.org, so I
> enabled the security repo lines in /etc/apt/sources.list. But when doing
> 'aptitude update', it reported that it couldn't find the repo.
> Turns out that it uses 'jessie-security', what the section has become
> since Bullseye, but it should be 'jessie/updates'. After changing that,
> it could find the repo and I had quite some updates.
> 
> 'Strangely' enough, in my recently created Stretch VM, it did have
> 'stretch/updates' in /e/a/sources.list, which is correct.

Yep, indeed. This is a bug introduced in commit
eab2940bf6d56538159808acb174bbda6271d343 when I rewrote the
differentiation between pre-bullseye and bullseye + later
because my first solution wasn't backward compatible:

There's a missing "|" in a regexp in hooks/debian/20-setup-apt. Small
mistake, big effect.

It affects Wheezy as well btw. as the regexp uselessly matches
"wheezyjessie" instead of "wheezy|jessie".

Fix committed locally. Will prepare a upstream minor bugfix release as
well as a Debian upload to unstable at least.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#996595:

[Jeremy Hendricks]

This might be related to the bug I submitted: 996026

I found that its pulling in a few nvidia-460 packages:

Inst nvidia-legacy-check (460.91.03-1 Debian:11.0/stable [amd64])
Inst nvidia-alternative (460.91.03-1 Debian:11.0/stable [amd64])
Inst nvidia-egl-common (460.91.03-1 Debian:11.0/stable [amd64])
Inst nvidia-modprobe (460.32.03-1 Debian:11.0/stable [amd64])
Inst libnvidia-cfg1 (460.91.03-1 Debian:11.0/stable [amd64])
Inst nvidia-persistenced (460.32.03-1 Debian:11.0/stable [amd64])
Inst nvidia-vulkan-common (460.91.03-1 Debian:11.0/stable [amd64])

Bug#997668: xen-tools: Incorrect security repo url for Jessie

[Diederik de Haas]

Package: xen-tools
Version: 4.9-1
Severity: normal

I have recently created a Jessie VM and noticed that there was (quite) a
difference between the kernel I expected and the one that I had.
I just learned that those are uploaded to security.debian.org, so I
enabled the security repo lines in /etc/apt/sources.list. But when doing
'aptitude update', it reported that it couldn't find the repo.
Turns out that it uses 'jessie-security', what the section has become
since Bullseye, but it should be 'jessie/updates'. After changing that,
it could find the repo and I had quite some updates.

'Strangely' enough, in my recently created Stretch VM, it did have
'stretch/updates' in /e/a/sources.list, which is correct.

Cheers,
  Diederik

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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages xen-tools depends on:
ii  debootstrap   1.0.123
ii  libconfig-inifiles-perl   3.03-1
ii  libdata-validate-domain-perl  0.10-1.1
ii  libdata-validate-ip-perl  0.30-1
ii  libdata-validate-uri-perl 0.07-1
ii  libfile-slurp-perl.32-1
ii  libfile-which-perl1.23-1
ii  libsort-versions-perl 1.62-1
ii  libterm-ui-perl   0.50-1
ii  libtext-template-perl 1.60-1
ii  openssh-client1:8.4p1-6
ii  perl  5.32.1-6

Versions of packages xen-tools recommends:
ii  debian-archive-keyring  2021.1.1
ii  debootstrap 1.0.123
ii  e2fsprogs   1.46.4-1
ii  libexpect-perl  1.21-1.1
ii  lvm22.03.11-2.1
ii  rinse   3.6
pn  ubuntu-keyring | ubuntu-archive-keyring 
ii  xen-hypervisor-4.14-amd64 [xen-hypervisor]  4.14.3-1
ii  xen-utils-4.14 [xen-utils]  4.14.3-1

Versions of packages xen-tools suggests:
ii  btrfs-progs5.14.1-1
pn  cfengine2  
ii  grub-xen-host  2.04-20
pn  reiserfsprogs  
pn  xfsprogs   

-- Configuration Files:
/etc/xen-tools/xen-tools.conf changed [not included]

-- no debconf information

Bug#997667: fprintd: max_tries argument should instead be max-tries

[John Colvin]

Package: fprintd
Version: 1.90.9-1build1
Severity: normal
X-Debbugs-Cc: john.loughran.col...@gmail.com

Dear Maintainer,

Sorry if I do something wrong here, I've never submitted a bug to debian
before. I am acutally running kubuntu but I'm pretty sure the bug is
deeper down the stack. It may even be deeper than debian!

pam-auth-updates, when asked to enable fingerprint auth, sets an
argument max_tries=1 to the fprintd module. This is the wrong name for
the option (perhaps a misunderstanding from old release notes, see 
https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/164),
the correct form would be max-tries=1

I couldn't find any matching strings in pam-auth-updates, but I was able
to find
https://salsa.debian.org/debian/fprintd/-/blob/0b7353bcd7ebd8d307dad44e73276e67271f67ec/debian/pam-configs/fprintd
which seems to have the same mistake. Maybe that is where the bug truly
is?

That was added in
https://salsa.debian.org/debian/fprintd/-/commit/d90232eaf6ce050ed494d9fb9cd8464ba595468f
which appears to be from a debian patch to fprintd adding max_tries
(note the underscore) as an option. Then in
https://salsa.debian.org/debian/fprintd/-/commit/b8b886550e3f4e3392d50ca03fb5a94244ebcbc6
when the upstream implementation was adopted - which used max-tries as
the option name - the change wasn't reflected in pam_configs/fprintd.

As I mentioned on the upstream MR I made, this might seem relatively
innocuous, but it does mean a lot of systems out there might be using
the default (3 for now) instead of the 1 expected.

I suppose I should submit a patch, but I don't really understand the
process here yet. Can I just make an MR on salsa.debian.org?


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

Kernel: Linux 5.13.0-20-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fprintd depends on:
ii  dbus   1.12.20-2ubuntu2
ii  libc6  2.34-0ubuntu3
ii  libfprint-2-2  1:1.90.7+git20210222+tod1-0ubuntu3
ii  libglib2.0-0   2.68.4-1ubuntu1
ii  libpolkit-gobject-1-0  0.105-31
ii  policykit-10.105-31

fprintd recommends no packages.

fprintd suggests no packages.

-- no debconf information

Bug#997666: flufl.bounce: please update to 4.0

[David Bremner]

Source: flufl.bounce
Version: 3.0.1-1
Severity: wishlist
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

flufl.bounce is an important part of the operation of
mailman3. Mailmain3 upstream informs me that the bounces currently
bugging me are detected properly with version 4.0 of the library. It
would be nice to be able to fix this mailman3 problem within Debian.

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmF0mk0ACgkQA0U5G1Wq
FSH4ZQ//aeF6Yj6KXvnDPmkMkUsCEIa/gA6HGyo4F4nl+PkASAQ4m64w3vyLCH2w
KcVY/blF08+00ieDiZAEC0VLXmgYiI4WTXFsMdQ6537KqMvFp+v02CcqJ4VngE6A
ZKRx0eQIoMSRW+OdzJuVGou2vgEOPZJYQvETRV8BKB7qBEhplzM0/XUZQes7vLN/
wxaTj8ZhCwtM3c65YjQU0WvnlyyNgCX+jtWkFhjwfMxl3sIJB3J0NU9nwdSomS3k
YZlzvJYBZdPaN3AEQL8kEYFXCHc8xFeEbZhgkw73UrN1fF0WeSSZdvuPcnUVkhTo
XOAj7nNcOnQmq/igHe933wP0OIYpzn+nbgSRT9KR6kFt6BDQOTK3lfsGDer74Cup
AWSyzd74mUPkQ5hAvYaPZOnjf+z4PZZmwyElfwhqvMQjZJTy6pjKZzw8kwCWUf9A
Y5Lj7u+CUEHbg5czteNEYrUV3KQfTqaD5O1RY5dyVyFL//XkQH6h6m43A801z0Th
4bZR0dZI4RiM7vr+dsbYVa9TliFJQqpgNXnB43xcK3gAnL1P15EuoZFLR/35nL7Z
ipRIE24tg08XxPiy9Viq/oSorKtPVY+sAHj3aRwj2+MB2xgt/u15iXChlCBcK89P
WIYbAVqPt3iylCUQJuZT96f2Z6ZT7iWWkmC1GwNineFjz21rgH8=
=5Xmy
-END PGP SIGNATURE-

Bug#997665: projectm-pulseaudio should depend on projectm-data

[Timothy Allen]

Package: projectm-pulseaudio
Version: 3.1.12-1
Severity: normal

Dear Maintainer,

Today I heard about ProjectM for the first time, so I looked at the list of
packages and decided projectm-pulseaudio would be the most useful variant for
me. I installed it:

$ sudo apt install projectm-pulseaudio
The following NEW packages will be installed:
  projectm-pulseaudio
0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
Need to get 428 kB of archives.
After this operation, 1,349 kB of additional disk space will be used.

...but when I tried to run it, it failed:

$ projectM-pulseaudio
Default config: /usr/share/projectM/config.inp
trying to create /home/st/.projectM/config.inp
Cannot find projectM default config, using implementation defaults
Aborted

`apt-file` tells me that `/usr/share/projectM/config.inp` comes from the
package projectm-data, and sure enough if I install that, projectM-pulseaudio
starts correctly.


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

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

Versions of packages projectm-pulseaudio depends on:
ii  libc6   2.32-4
ii  libgcc-s1   11.2.0-9
ii  libgl1  1.3.4-2+b1
ii  libpulse0   15.0+dfsg1-2
ii  libqt5core5a5.15.2+dfsg-12
ii  libqt5gui5  5.15.2+dfsg-12
ii  libqt5opengl5   5.15.2+dfsg-12
ii  libqt5widgets5  5.15.2+dfsg-12
ii  libstdc++6  11.2.0-9
ii  pulseaudio  15.0+dfsg1-2

projectm-pulseaudio recommends no packages.

projectm-pulseaudio suggests no packages.

-- no debconf information

Bug#997664: sundials: apparent ABI bumps in sundials5 library packages

[Drew Parsons]

Source: sundials
Version: 5.7.0+dfsg-1
Severity: normal

Unless I misunderstood the package naming system for sundials, looks
like there was an ABI bump in sublibraries when sundials upgraded from
v4 to v5.

It can be seen in 5.7.0+dfsg-1, so it's not a side-effect of the the new
5.8.0 build (hence no need to block 5.8.0 with severity Serious).

The apparently upgraded libraries are

arkode3  ->  arkode4  (libsundials_arkode.so.4)
cvode[s]4  ->  cvodes5  (libsundials_cvode[s].so.5 )
ida[s]4  ->  ida5  (libsundials_ida[s].so.5)
kinsol4  ->  kinsol5  (libsundials_kinsol.so.5)
nvecserial4 ->  nvecserial5  (libsundials_nvecserial.so.5)
sunmatrix2  ->  sunmatrix3   (libsundials_sunmatrixband.so.3 etc)
sunlinsol2  ->  sunlinsol3   (libsundials_fsunlinsolband.so.3 etc, and other 
anomalies)

nvecparallel-XX4  ->  nvecparallel-XX5 (libsundials_nvecXX.so.5)
(XX = pthread, petsc, openmp, mpi, hypre)

Bug#997238: lordsawar: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’ type

[Simon McVittie]

On Sat, 23 Oct 2021 at 21:53:34 +0100, Simon McVittie wrote:
> I suspect that applying the change from
> https://gitlab.gnome.org/GNOME/gstreamermm/-/merge_requests/4 in
> gstreamermm-1.0 would allow lordsawar to be built successfully against it
> (test-builds in progress).

Yes, confirmed via a test-build of lordsawar. Please consider the attached
patch.

smcv
>From 699d47eb51831b207a749e4351e3ebc7285a749b Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sat, 23 Oct 2021 21:51:27 +0100
Subject: [PATCH] Add patch from upstream to fix FTBFS of dependent packages

This misuse of 'volatile' caused build failures triggered by gcc 11
and/or GLib 2.68.

Closes: #997238
---
 .../patches/Fix-build-against-glib-2.68.patch | 41 +++
 debian/patches/series |  1 +
 2 files changed, 42 insertions(+)
 create mode 100644 debian/patches/Fix-build-against-glib-2.68.patch

diff --git a/debian/patches/Fix-build-against-glib-2.68.patch b/debian/patches/Fix-build-against-glib-2.68.patch
new file mode 100644
index 000..2048840
--- /dev/null
+++ b/debian/patches/Fix-build-against-glib-2.68.patch
@@ -0,0 +1,41 @@
+From: Dominique Leuenberger 
+Date: Tue, 13 Jul 2021 10:32:30 +
+Subject: Fix build against glib 2.68
+
+volatile has been misused in the past
+
+Bug: https://gitlab.gnome.org/GNOME/gstreamermm/-/issues/11
+Bug-Debian: https://bugs.debian.org/997238
+Reference: https://gitlab.gnome.org/GNOME/glib/-/issues/600
+Reference: http://c.isvolatileusefulwiththreads.com/
+---
+ gstreamer/gstreamermm/register.h| 2 +-
+ tests/integration/test-integration-seekonstartup.cc | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/gstreamer/gstreamermm/register.h b/gstreamer/gstreamermm/register.h
+index db66d17..a7ab3a6 100644
+--- a/gstreamer/gstreamermm/register.h
 b/gstreamer/gstreamermm/register.h
+@@ -110,7 +110,7 @@ register_mm_type(const gchar * type_name)
+ /* The typedef for GType may be gulong or gsize, depending on the
+  * system and whether the compiler is c++ or not. The g_once_init_*
+  * functions always take a gsize * though ... */
+-static volatile gsize gonce_data = 0;
++static gsize gonce_data = 0;
+ if (g_once_init_enter (_data)) {
+ GTypeInfo info;
+ 
+diff --git a/tests/integration/test-integration-seekonstartup.cc b/tests/integration/test-integration-seekonstartup.cc
+index 247ac49..cd43a12 100644
+--- a/tests/integration/test-integration-seekonstartup.cc
 b/tests/integration/test-integration-seekonstartup.cc
+@@ -18,7 +18,7 @@ RefPtr mainloop;
+ RefPtr bus;
+ RefPtr pipeline;
+ RefPtr sink_pad;
+-static volatile gint counter;
++static gint counter;
+ bool prerolled = false;
+ gboolean was_check = 0;
+ 
diff --git a/debian/patches/series b/debian/patches/series
index 9a0a29d..3c80c41 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 01-disable-tests.patch
 02-do-not-compile-examples.patch
+Fix-build-against-glib-2.68.patch
-- 
2.33.0

Bug#997663: general: bullseye, system freezes completely when firefox freezes

[Jacob Kochems]

Package: general
Severity: important
X-Debbugs-Cc: jacobkochems+bugtrack...@gmail.com

Dear Maintainer,

* What led up to the situation?
When using Firefox (FF) with many open tabs it sometimes freezes and takes the
whole system with it. At this point all mouse and keyboard input is ignored. In
every case so far there was at least one tab with a YouTube video open. I
suspect using a lot of memory is the trigger here.

* What exactly did you do (or not do) that was effective (or ineffective)?
I tried to switch to a different tty via Ctrl+Alt+F: no effect.
I tried the magic SysRq key sequence: REISUB: no effect.
I tried SysRq + f to call oom_kill: no effect.
Only a hard reset (power cycle) was effective so far.

* What was the outcome of this action?
The system freezes ignoring all user input.
If a video was playing at that time a short audio sequence of that video keeps
repeating in an infinite loop.

* What outcome did you expect instead?
I expect to be able to kill the offending applications.
I expect the system (be it gnome-shell, the kernel itself or other critical
components) to be able to handle failing user space programs without freezing
themselves. That is why I consider this *not* to be a bug of FF, although a bug
in FF seems to trigger it. No user space program should be able to tank the
system by hogging up resources.


Since I was unable to recover the system from this state I cannot provide any
error messages.
Is there a log file I can inspect after the fact?
If so, what should I look for?
Do I have to activate additional logging for this?

Some system information:
$ uname -v -r -m
5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64

CPU: Intel Core i7, 4 Cores
RAM: 8GB

Please let me know if you need additional system information.
I would appreciate any insight into how to diagnose this.

Thank you for your time.

Best regards,
Jacob

Bug#997240: lives: FTBFS: htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory

[salsaman]

The line causing the error message can safely be removed as it is
redundant. The correction appears in the most recent stable release, 3.2.0

On Sat, 23 Oct 2021, 16:24 Lucas Nussbaum,  wrote:

> Source: lives
> Version: 3.0.2-1.1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > gcc -DPACKAGE_NAME=\"LiVES\" -DPACKAGE_TARNAME=\"lives\"
> -DPACKAGE_VERSION=\"3.0.2\" -DPACKAGE_STRING=\"LiVES\ 3.0.2\"
> -DPACKAGE_BUGREPORT=\"https://github.com/salsaman/LiVES/issues\;
> -DPACKAGE_URL=\"http://lives-video.com\; -DPACKAGE=\"lives\"
> -DVERSION=\"3.0.2\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1
> -DHAVE_SYS_PARAM_H=1 -DSTDC_HEADERS=1 -D_ALL_SOURCE=1 -D_DARWIN_C_SOURCE=1
> -D_GNU_SOURCE=1 -D_HPUX_ALT_XOPEN_SOCKET_API=1 -D_NETBSD_SOURCE=1
> -D_OPENBSD_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1
> -D__STDC_WANT_IEC_60559_ATTRIBS_EXT__=1 -D__STDC_WANT_IEC_60559_BFP_EXT__=1
> -D__STDC_WANT_IEC_60559_DFP_EXT__=1 -D__STDC_WANT_IEC_60559_FUNCS_EXT__=1
> -D__STDC_WANT_IEC_60559_TYPES_EXT__=1 -D__STDC_WANT_LIB_EXT2__=1
> -D__STDC_WANT_MATH_SPEC_FUNCS__=1 -D_TANDEM_SOURCE=1 -D__EXTENSIONS__=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PTHREAD_PRIO_INHERIT=1
> -DHAVE_PTHREAD=1 -DGETTEXT_PACKAGE=\"lives\"
> -DLOCALEDIR=\"\$\{datarootdir\}/locale\" -DPREFIX=\"/usr\"
> -DLiVES_VERSION=\"3.0.2\" -DHAVE_VISIBILITY=1
> -DHAVE_STDINT_H_WITH_UINTMAX=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1
> -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DINTDIV0_RAISES_SIGFPE=1
> -DHAVE_INTTYPES_H_WITH_UINTMAX=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1
> -DHAVE_UINTMAX_T=1 -DHAVE_INTTYPES_H=1 -DUSE_POSIX_THREADS=1
> -DUSE_POSIX_THREADS_WEAK=1 -DHAVE_PTHREAD_RWLOCK=1
> -DHAVE_PTHREAD_MUTEX_RECURSIVE=1 -DHAVE_BUILTIN_EXPECT=1 -DHAVE_ARGZ_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1
> -DHAVE_SYS_PARAM_H=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1
> -DHAVE_GETGID=1 -DHAVE_GETUID=1 -DHAVE_MEMPCPY=1 -DHAVE_MUNMAP=1
> -DHAVE_STPCPY=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRTOUL=1
> -DHAVE_TSEARCH=1 -DHAVE_ARGZ_COUNT=1 -DHAVE_ARGZ_STRINGIFY=1
> -DHAVE_ARGZ_NEXT=1 -DHAVE___FSETLOCKING=1 -DHAVE_DECL_FEOF_UNLOCKED=1
> -DHAVE_DECL_FGETS_UNLOCKED=1 -DHAVE_ICONV=1 -DICONV_CONST=
> -DHAVE_NL_LOCALE_NAME=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_WCHAR_T=1
> -DHAVE_WINT_T=1 -DHAVE_INTMAX_T=1 -DHAVE_POSIX_PRINTF=1 -DHAVE_STDINT_H=1
> -DHAVE_STDINT_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_ASPRINTF=1 -DHAVE_FWPRINTF=1 -DHAVE_PUTENV=1 -DHAVE_SETENV=1
> -DHAVE_SETLOCALE=1 -DHAVE_SNPRINTF=1 -DHAVE_WCSLEN=1
> -DHAVE_DECL__SNPRINTF=0 -DHAVE_DECL__SNWPRINTF=0
> -DHAVE_DECL_GETC_UNLOCKED=1 -DHAVE_LANGINFO_CODESET=1 -DHAVE_LC_MESSAGES=1
> -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DHAVE_LIBDL=1
> -DHAVE_POSIX_MEMALIGN=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_FALLOCATE=1
> -DHAVE_SYS_PRCTL_H=1 -DHAVE_LINUX_JOYSTICK_H=1 -DHAVE_JACK_JACK_H=1
> -DHAVE_JACK_TRANSPORT_H=1 -DHAVE_LINUX_VIDEODEV2_H=1 -DHAVE_FREI0R_H=1
> -DHAVE_LIBRAW1394_RAW1394_H=1 -DHAVE_LIBAVC1394_AVC1394_H=1
> -DHAVE_LIBAVC1394_ROM1394_H=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I..
>  -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -fcommon -Wall -c -o sendOSC-sendOSC.o
> `test -f 'sendOSC.c' || echo './'`sendOSC.c
> > htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory
> >41 | #include 
> >   |  ^~~
> > compilation terminated.
> > make[3]: *** [Makefile:605: sendOSC-htmsocket.o] Error 1
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2021/10/23/lives_3.0.2-1.1_unstable.log
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please marking it as
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
>
>

Bug#997060: [Pkg-mailman-hackers] Bug#997060: Bring back mailing list support to Debian

[Pierre-Elliott Bécue]

Hi,

Alain Knaff  wrote on 23/10/2021 at 14:21:32+0200:

> Package: mailman3-web
> Version: 0+20200530-2
>
> Hi,
>
> After I recently upgraded my server to Debian 11, I was rather appalled
> that mailman was dropped without a clear migration path.
>
> I figured out that this is now replaced by mailman3-full, but apparently
> that package is still pretty much work in progress.
>
> /usr/share/doc/mailman3-web/README.Debian.gz says to run
> dpkg-reconfigure mailman3-web after installing it, and this does indeed
> prompt me to set up a superuser account, and installs its configuration
> in the webserver
>
> However, when navigating to https://myserver/mailman3/ , I encounter
> several issues:
>
> 1. Proxy permissions are not set up.
>
> So I added the following:
>
> 
> Require all granted
> 
>
>
> 2. After the above, I see a message "Page not found This page either
> doesn't exist, or it moved somewhere else."
>
> Links in the top menu bar are broken, they snip off the last letter of
> "mailman3", so it becomes "mailman". After setting up a ProxyPass for
> the path "mailman" as well, I see that another letter is snipped in the
> top links, so it becomes "mailma", then "mailm", ...
>
> What is going on here?
>
>
> 3. So, I tried clicking on login, and manually added back the missing 3
> to the URL and went to
> https://myserver/mailman3/accounts/login/?next=/mailman3/accounts/login/
>
> => Still the same page with "Page not found. This page either doesn't
> exist, or it moved somewhere else."
>
>
> So, what gives?
>
> I can understand that it takes some time for a full rewrite of a major
> software to become production-ready. However, in that case, please don't
> drop the working previous version (mailman 2.1) until the new one is
> actually usable.

mailman removal is the decision of the mailman maintainer, Thijs, due to
the fact it relies on python2 which got removed from Debian.

Regarding mailman3, I did the nginx integration, Jonas the Apache2 one,
from upstream recommendations. Looking from the config, I'd try the URL
without the trailing slash: https://myserver/mailman3

I don't know if the proxy permissions are really required.

Apart from that, mailman3 is in Debian since Buster, so more than three
years, and while it indeed carried out its lot of bugs, it's quite
usable.

Regards,
--
Pierre-Elliott Bécue


signature.asc
Description: PGP signature

Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests

[Diederik de Haas]

Control: Forwarded -1 
https://lore.kernel.org/linux-block/cabvffennj8jkp7etuutqi+vkjdbfu37w1uxe4q3cb7-ixxh...@mail.gmail.com/

On Saturday, 23 October 2021 23:29:21 CEST Daniel Black wrote:
> https://marc.info/?l=linux-block=163489378723217=2

Looked up your upstream message on lore.k.o and set 'Forwarded' to that.

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

Bug#997082: qemu: FTBFS: usb.c:200:23: error: array subscript ‘device_descriptor_t[0]’ is partly outside array bounds of ‘u8[8]’ {aka ‘unsigned char[8]’} [-Werror=array-bounds]

[Michael Tokarev]

23.10.2021 19:33, Lucas Nussbaum wrote:

Source: qemu
Version: 1:6.1+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bullseye

Hi,

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


Relevant part (hopefully):

powerpc64-linux-gnu-gcc $EXTRACFLAGS -m32 -mcpu=604 -msoft-float -fno-builtin-bcopy -fno-builtin-log2 -Os -g 
-DNATIVE_BITWIDTH_EQUALS_HOST_BITWIDTH -USWAP_ENDIANNESS -Wall -Wredundant-decls -Wshadow -Wpointer-arith 
-Wstrict-prototypes -Wmissing-declarations -Wundef -Wendif-labels -Wstrict-aliasing -Wwrite-strings 
-Wmissing-prototypes -Wnested-externs -Werror -MMD -MP -MT target/drivers/usbohci_rh.o -MF 
'target/drivers/usbohci_rh.d' -I/<>/roms/openbios/include 
-I/<>/roms/openbios/kernel/include -I./target/include -c -o target/drivers/usbohci_rh.o 
/<>/roms/openbios/drivers/usbohci_rh.c
/<>/roms/openbios/drivers/usb.c: In function ‘get_descriptor’:
/<>/roms/openbios/drivers/usb.c:200:23: error: array subscript 
‘device_descriptor_t[0]’ is partly outside array bounds of ‘u8[8]’ {aka ‘unsigned char[8]’} 
[-Werror=array-bounds]
   200 | if (dd->bMaxPacketSize0 != 0)
   |   ^~
/<>/roms/openbios/drivers/usb.c:181:12: note: while referencing 
‘buf’
   181 | u8 buf[8];
   |^~~


This is interesting. And I'm not really sure what to do with this.
The code is right, and gcc is too picky there. The thing is,
while the buffer is indeed smaller than the size of the structure
to which it is casted there, but the actual code does not access
past the buffer, bMaxPacketSize0 is byte #7 (counting from 0) there
which is exactly the last byte of buf[] array.

I haven't seen this warning before, it must be some new gcc
addition, and gcc is being too smart there :)

I agree the code is cloudy there, it can have been written
more clearly. So I can't say this is really a bug in gcc,
it is like classic "variable can be used uninitialized" while
it actually is not, for example because all relevant switch(){}
statements leads to return but gcc can not figure it out.

Thanks,

/mjt

Bug#997059: [Debian-med-packaging] Bug#997059: intake FTBFS on IPV6-only buildds

[Étienne Mollier]

Oh, hold on!  I'm not sure I have the same definition of "ipv6
only" as the buildd.  Mine involves not having ipv4 loopback at
all, which does not raise the issue documented in the bug
report, but tornado errors on binding to 127.0.0.1 instead.

If my ipv6 only host gets back an ipv4 loopback, then I
reproduce the initial problem, independently of the changes in
python3-tornado, which is unsurprising since the initial
traceback does not involve the tornado module at all.

I'm not sure how to proceed from there…  :(
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/6, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#997662: lintian: Incorrect tag: package-contains-python-dot-directory for .egg-info directories

[Stefano Rivera]

Package: lintian
Version: 2.110.0
Severity: normal

Hi, I see lintian 2.110 is now emitting a
package-contains-python-dot-directory tag for .egg-info directories in
binary packages.

We do not want to encourage package maintainers to remove .egg-info
directories from their Python binary packages. Tools inspect these to
know which Python modules are available on the system, as well as many
other things.

I would consider all of these tags to be incorrect:
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/PKG-INFO
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/dependency_links.txt
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/requires.txt
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/top_level.txt

Thanks,

SR

Bug#997628: imake: uses an argument to ar(1) which recent binutils changed in an incompatible way, causing packages using imake to FTBFS (was Re: Bug#997628: mgp: FTBFS: ar: libdeps specified more tha

[Thorsten Glaser]

# imake
reassign 997628 xutils-dev
found 997628 1:7.7+5
retitle 997628 imake: uses “ar clq” by default, which recent binutils broke in 
an incompatible way
# causes an FTBFS, cannot be workarounded in mgp
affects 997628 src:mgp
# root bug is in binutils
block 997628 by 981072
# at least, if not more
severity 981072 important
thanks

Lucas Nussbaum dixit:

>> ar clq libmgpimage.a  imagetypes.o send.o zio.o zoom.o new.o compress.o 
>> reduce.o value.o misc.o rotate.o rle.o rlelib.o smooth.o halftone.o 
>> clip.o   dither.o path.o bright.o window.o imlib_loader.o
>> ar: libdeps specified more than once

WTF, what does that even mean? *researches*

This is #981072, an incompatible(!) change in binutils, which I’d
consider of a rather serious severity but is tagged wontfix.

Basically, ar(1) in bullseye documents the ‘l’ modifier as…

   l   This modifier is accepted but not used.

… and ar(1) in sid reuses it in an incompatible way, with no
deprecation/warning period, instead of doing the sensible thing
and using a different, not currently used, flag.


Robert Luberda dixit:

>Quick search on sources of packages showed that there are about 30
>other packages that also call "ar clq", see [2] - that's why I'm writing

No, it’s far more than your search shows.


I’m tempted to reassign to binutils, but this would probably
be ignored. But I’ve got to reassign it anyway since the clq
is injected by imake(1). Which version(s) of binutils contain
this breaking change? (That is, does imake need a change in a
stable release?)

Doko, I urge you to request the upstream developers to change
this and use a currently-unused flag for their new feature. I
know getting them to do that, therefore admitting a mistake,
is going to be hard, but considering this is embedded in *so*
many build systems, they’re not going to make any friends by
breaking this.

bye,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r

Bug#996019: debootstrap: bootstrap of ubuntu impish is failing

[Sylvestre Ledru]

Le 23/10/2021 à 22:02, Dimitri John Ledkov a écrit :
>
>
> On Sat, 23 Oct 2021, 19:49 Sylvestre Ledru,  wrote:
>
> Hello
>
> Le 20/10/2021 à 18:05, Dimitri John Ledkov a écrit :
>> Hi,
>>
>> I've tried to reproduce this more 
> Thanks, I appreciate it!
>> and I have a few questions:
>>
>> 1) what is the version of debootstrap ?
> 1.0.123 (bullseye & sid)
>
>
>
> Impish support is only available in experimental at the moment in the
> 1.0.124. can you please try that?

oh, thanks :)

It fixed the issue indeed!

Thanks again
S

Bug#993161: pam: some remaining changes for DPKG_ROOT

[Sam Hartman]

> "Johannes" == Johannes Schauer Marin Rodrigues  writes:

Johannes> Control: user debian-d...@lists.debian.org Control:
Johannes> usertag -1 + dpkg-root-support

Johannes> Hi Sam,

Johannes> Quoting Helmut Grohne (2021-09-24 18:14:28)
>> So if you continue refusing our patches, can you propose any
>> other way to move forward?

Johannes> it has been a month since your last mail, so I wanted to
Johannes> send a friendly ping to ask, whether there is anything
Johannes> else we can do to help you with this bug.

No.
I'm waiting for Steve to chime in.
I do owe you and Helmut an explanation of why I'm uncomfortable, but I
think that belongs outside of this bug.
If this were my package entirely, I'd accept the patch, but my rationale
for doing so would be because I respect all the work Helmut has done and
I'm uncomfortable standing in the way of that.
In a case where I'm not really the maintainer, simply someone helping
out, that's not a good enough rationale.

Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests

[Daniel Black]

https://marc.info/?l=linux-block=163489378723217=2

Bug#997659: earlyoom: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules'

[Lucas Nussbaum]

Source: earlyoom
Version: 1.6.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> cc -Wl,-z,relro -Wl,-z,now  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wall -Wextra -Wformat-security 
> -Wconversion -DVERSION=\"v1.6.2\" -g -fstack-protector-all -std=gnu99 -o 
> earlyoom globals.c kill.c main.c meminfo.c msg.c
> pandoc MANPAGE.md -s -t man > earlyoom.1
> sed "s|:TARGET:|/usr/bin|g;s|:SYSCONFDIR:|/etc|g" earlyoom.service.in > 
> earlyoom.service
> make[1]: Leaving directory '/<>'
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> go version | grep -qF gcc || HOME=$PWD go test -v
> go: go.mod file not found in current directory or any parent directory; see 
> 'go help modules'
> make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/earlyoom_1.6.2-1_unstable.log

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

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

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

Bug#997661: binutils-mingw-w64: FTBFS: patching fails

[Lucas Nussbaum]

Source: binutils-mingw-w64
Version: 8.11
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> tar xf /usr/src/binutils/binutils-2.37.tar.*
> rm -rf /<>/upstream
> mv binutils-* /<>/upstream
> patch -d /<>/upstream -R -p1 < 
> /usr/src/binutils/patches/001_ld_makefile_patch.patch
> patching file ld/Makefile.am
> patching file ld/Makefile.in
> Hunk #1 succeeded at 564 (offset 2 lines).
> QUILT_SERIES=debian/patches/series QUILT_PATCHES=debian/patches quilt push -a
> Applying patch debian/patches/testsuite-timeout.patch
> patching file upstream/gas/testsuite/lib/gas-defs.exp
> 
> Applying patch debian/patches/specify-timestamp.patch
> patching file upstream/bfd/peXXigen.c
> Hunk #1 succeeded at 73 with fuzz 2 (offset -4 lines).
> Hunk #2 succeeded at 854 (offset -25 lines).
> patching file upstream/ld/pe-dll.c
> Hunk #2 succeeded at 1221 (offset 1 line).
> patching file upstream/ld/emultempl/pe.em
> Hunk #1 succeeded at 318 (offset 14 lines).
> patching file upstream/ld/emultempl/pep.em
> Hunk #1 succeeded at 337 (offset 14 lines).
> 
> Applying patch debian/patches/dont-run-objcopy.patch
> patching file upstream/binutils/testsuite/binutils-all/objcopy.exp
> Hunk #1 succeeded at 668 (offset 13 lines).
> 
> Applying patch debian/patches/disable-flags.patch
> patching file upstream/ld/emultempl/pe.em
> Hunk #1 succeeded at 262 (offset 3 lines).
> Hunk #2 FAILED at 273.
> Hunk #3 FAILED at 344.
> Hunk #4 FAILED at 353.
> Hunk #5 FAILED at 487.
> Hunk #6 FAILED at 864.
> 5 out of 6 hunks FAILED -- rejects in file upstream/ld/emultempl/pe.em
> patching file upstream/ld/emultempl/pep.em
> Hunk #1 succeeded at 241 (offset 4 lines).
> Hunk #2 FAILED at 251.
> Hunk #3 succeeded at 332 (offset 14 lines).
> Hunk #4 FAILED at 333.
> Hunk #5 FAILED at 454.
> Hunk #6 FAILED at 815.
> 4 out of 6 hunks FAILED -- rejects in file upstream/ld/emultempl/pep.em
> Patch debian/patches/disable-flags.patch does not apply (enforce with -f)
> make[1]: *** [debian/rules:50: unpack-stamp] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/binutils-mingw-w64_8.11_unstable.log

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

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

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

Bug#997660: calibre: FTBFS: -c: Unable to find file "QtWidgets/QtWidgetsmod.sip"

[Lucas Nussbaum]

Source: calibre
Version: 5.29.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> blhc: ignore-line-regexp: \tCompiling form /.+\.ui
> blhc: ignore-line-regexp: .+ -dM -E -o moc_predefs\.h 
> /usr/lib/[^/]+/qt5/mkspecs/features/data/dummy\.cpp
> [ -d build ] || python3.9 setup.py build
> 
> *
> * Running build
> *
> 
> Building 24 extensions
> Compiling 35 files...
> g++ -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -std=c++11 
> -DCALIBRE_MODINIT_FUNC=extern "C" __attribute__ ((visibility ("default"))) 
> PyObject* -I/usr/include/hunspell -c 
> /<>/src/calibre/utils/spell/hunspell_wrapper.cpp -o 
> /<>/build/objects/hunspell/hunspell_wrapper.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -std=c99 -DCALIBRE_MODINIT_FUNC= 
> __attribute__ ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/utils/hyphenation/hyphen.c -o 
> /<>/build/objects/hyphen/hyphen.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -std=c99 -DCALIBRE_MODINIT_FUNC= 
> __attribute__ ((visibility ("default"))) PyObject* -c 
> /<>/src/unicode_names/unicode_names.c -o 
> /<>/build/objects/unicode_names/unicode_names.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/utils/speedup.c -o 
> /<>/build/objects/speedup/speedup.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/gui2/tweak_book/editor/syntax/html.c -o 
> /<>/build/objects/html_syntax_highlighter/html.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/tinycss/tokenizer.c -o 
> /<>/build/objects/tokenizer/tokenizer.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/gui2/tweak_book/diff/_patiencediff_c.c -o 
> /<>/build/objects/_patiencediff_c/_patiencediff_c.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/utils/icu.c -o 
> /<>/build/objects/icu/icu.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
> -pthread -I/usr/include/python3.9 -O3 -DCALIBRE_MODINIT_FUNC= __attribute__ 
> ((visibility ("default"))) PyObject* -c 
> /<>/src/calibre/utils/matcher.c -o 
> /<>/build/objects/matcher/matcher.o
> 
> gcc -Wall -DNDEBUG -fno-strict-aliasing -pipe -fPIC -g 

Bug#997658: botan: FTBFS: tests failed

[Lucas Nussbaum]

Source: botan
Version: 2.18.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> LD_LIBRARY_PATH=. /<>/botan-test
> Testing Botan 2.18.1 (unreleased, revision unknown, distribution Debian)
> CPU flags: sse2 ssse3 sse41 sse42 avx2 avx512f avx512dq avx512bw rdtsc bmi1 
> bmi2 adx aes_ni clmul rdrand rdseed
> Starting tests drbg_seed:16B097975A637739
> block:
> AES-128 ran 34470 tests in 53.80 msec all ok
> AES-192 ran 40500 tests in 63.88 msec all ok
> AES-256 ran 46260 tests in 74.17 msec all ok
> ARIA-128 ran 30 tests in 0.06 msec all ok
> ARIA-192 ran 30 tests in 0.06 msec all ok
> ARIA-256 ran 30 tests in 0.06 msec all ok
> Blowfish ran 1860 tests in 21.24 msec all ok
> CAST-128 ran 1440 tests in 2.10 msec all ok
> CAST-256 ran 195 tests in 0.34 msec all ok
> Camellia-128 ran 180 tests in 0.27 msec all ok
> Camellia-192 ran 90 tests in 0.13 msec all ok
> Camellia-256 ran 150 tests in 0.23 msec all ok
> Cascade(Serpent,AES-256) ran 30 tests in 0.08 msec all ok
> Cascade(Serpent,CAST-128) ran 15 tests in 0.04 msec all ok
> Cascade(Serpent,Twofish) ran 45 tests in 0.17 msec all ok
> DES ran 9630 tests in 13.49 msec all ok
> DESX ran 135 tests in 0.20 msec all ok
> GOST-28147-89(R3411_94_TestParam) ran 270 tests in 0.52 msec all ok
> GOST-28147-89(R3411_CryptoPro) ran 150 tests in 0.28 msec all ok
> IDEA ran 16260 tests in 33.14 msec all ok
> KASUMI ran 45 tests in 0.07 msec all ok
> Lion(SHA-160,RC4,64) ran 15 tests in 0.10 msec all ok
> MISTY1 ran 465 tests in 0.65 msec all ok
> Noekeon ran 15450 tests in 21.44 msec all ok
> SEED ran 120 tests in 0.19 msec all ok
> SHACAL2 ran 46035 tests in 79.69 msec all ok
> SM4 ran 45 tests in 0.09 msec all ok
> Serpent ran 47070 tests in 76.78 msec all ok
> Threefish-512 ran 150 tests in 0.29 msec all ok
> TripleDES ran 1680 tests in 2.70 msec all ok
> Twofish ran 16545 tests in 31.26 msec all ok
> XTEA ran 1020 tests in 1.67 msec all ok
> stream:
> CTR-BE(AES-128) ran 648 tests in 1.91 msec all ok
> CTR-BE(AES-128,4) ran 12 tests in 0.05 msec all ok
> CTR-BE(AES-128,5) ran 12 tests in 0.03 msec all ok
> CTR-BE(AES-128,6) ran 12 tests in 0.03 msec all ok
> CTR-BE(AES-128,8) ran 12 tests in 0.04 msec all ok
> CTR-BE(AES-192) ran 768 tests in 1.90 msec all ok
> CTR-BE(AES-256) ran 804 tests in 2.00 msec all ok
> CTR-BE(Blowfish) ran 12 tests in 0.17 msec all ok
> CTR-BE(DES) ran 588 tests in 1.57 msec all ok
> CTR-BE(Noekeon) ran 2304 tests in 6.18 msec all ok
> CTR-BE(Serpent) ran 2100 tests in 5.73 msec all ok
> CTR-BE(TripleDES) ran 2556 tests in 11.61 msec all ok
> CTR-BE(XTEA) ran 1452 tests in 3.72 msec all ok
> ChaCha(12) ran 72 tests in 0.17 msec all ok
> ChaCha(20) ran 3096 tests in 8.30 msec all ok
> ChaCha(8) ran 717 tests in 1.90 msec all ok
> MARK-4 ran 120 tests in 0.25 msec all ok
> OFB(AES-128) ran 132 tests in 0.34 msec all ok
> OFB(AES-192) ran 12 tests in 0.03 msec all ok
> OFB(AES-256) ran 12 tests in 0.03 msec all ok
> OFB(DES) ran 48 tests in 0.14 msec all ok
> RC4 ran 1656 tests in 4.55 msec all ok
> RC4(3) ran 24 tests in 0.05 msec all ok
> SHAKE-128 ran 13740 tests in 25.10 msec all ok
> Salsa20 ran 143 tests in 0.34 msec all ok
> hash:
> Adler32 ran 266 tests in 0.19 msec all ok
> BLAKE2b(224) ran 2547 tests in 2.44 msec all ok
> BLAKE2b(256) ran 2547 tests in 2.42 msec all ok
> BLAKE2b(384) ran 2547 tests in 2.56 msec all ok
> BLAKE2b(512) ran 2675 tests in 3.25 msec all ok
> CRC24 ran 284 tests in 0.14 msec all ok
> CRC32 ran 266 tests in 0.14 msec all ok
> Comb4P(MD4,MD5) ran 10 tests in 0.05 msec all ok
> Comb4P(SHA-160,RIPEMD-160) ran 10 tests in 0.03 msec all ok
> GOST-R-34.11-94 ran 95 tests in 0.55 msec all ok
> Keccak-1600(224) ran 2667 tests in 3.88 msec all ok
> Keccak-1600(256) ran 2667 tests in 3.95 msec all ok
> Keccak-1600(384) ran 2667 tests in 4.38 msec all ok
> Keccak-1600(512) ran 2667 tests in 5.00 msec all ok
> MD4 ran 1500 tests in 0.74 msec all ok
> MD5 ran 1520 tests in 0.85 msec all ok
> Parallel(MD5,SHA-160) ran 13 tests in 0.03 msec all ok
> Parallel(SHA-256,SHA-512) ran 15 tests in 0.04 msec all ok
> RIPEMD-160 ran 1486 tests in 0.98 msec all ok
> SHA-160 ran 3060 tests in 2.44 msec all ok
> SHA-224 ran 100 tests in 0.08 msec all ok
> SHA-256 ran 15572 tests in 11.60 msec all ok
> SHA-3(224) ran 1994 tests in 3.32 msec all ok
> SHA-3(256) ran 1994 tests in 3.28 msec all ok
> SHA-3(384) ran 1994 tests in 3.23 msec all ok
> SHA-3(512) ran 1994 tests in 6.49 msec all ok
> SHA-384 ran 252 tests in 0

Bug#997657: cgreen: FTBFS: Icon font not found for set: fas

[Lucas Nussbaum]

Source: cgreen
Version: 1.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/build'
> [  1%] asciidoctor-pdf cgreen-guide-en
> cd /<>/build/doc && /usr/bin/asciidoctor-pdf -a toc -a 
> VERSION=1.3.0 -a docinfo -o cgreen-guide-en.pdf 
> /<>/doc/cgreen-guide-en.asciidoc
> Icon font not found for set: fas
>   Use --trace for backtrace
> make[4]: *** [doc/CMakeFiles/cgreen-guide-en-pdf.dir/build.make:77: 
> doc/cgreen-guide-en.pdf-pdf] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/cgreen_1.3.0-2_unstable.log

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

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

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

Bug#997656: xfsprogs: FTBFS: mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied

[Lucas Nussbaum]

Source: xfsprogs
Version: 5.13.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> Installing libfrog-install
> Installing libxfs-install
> ../install-sh -o root -g root -m 755 -d /usr/include/xfs
> mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied
> mkdir: cannot create directory ‘/usr/include/xfs’: Permission denied
> gmake[2]: *** [Makefile:124: install] Error 1
> make[1]: *** [Makefile:148: libxfs-install] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/xfsprogs_5.13.0-1_unstable.log

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

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

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

Bug#997655: diodon: FTBFS: autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?

[Lucas Nussbaum]

Source: diodon
Version: 1.11.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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=meson --with gir
>dh_update_autotools_config -O--buildsystem=meson
>dh_autoreconf -O--buildsystem=meson
> autoreconf: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> autoreconf: error: configure.in: AC_INIT not found; not an autoconf script?
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:8: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/diodon_1.11.1-1_unstable.log

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

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

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

Bug#997653: caribou: FTBFS: Caribou-1.0.gir:In NullAdapter: error: Can't resolve type '_Caribou.DisplayAdapter' for field Caribou.NullAdapter.parent_instance

[Lucas Nussbaum]

Source: caribou
Version: 0.4.21-7.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/libcaribou'
> Makefile:883: warning: overriding recipe for target 'caribou-1.0.vapi'
> Makefile:868: warning: ignoring old recipe for target 'caribou-1.0.vapi'
> rm -f libcaribou_la_vala.stamp && echo stamp > libcaribou_la_vala.stamp-t
> /usr/bin/valac -H caribou.h --vapi caribou-1.0.vapi -h caribou-internals.h 
> --vapidir=../vapi --pkg xtst --pkg gee-0.8 --pkg gdk-x11-3.0 --pkg libxml-2.0 
> --pkg libxklavier --pkg external-libs --internal-vapi 
> caribou-internals-1.0.vapi --library caribou-1.0 --gir _Caribou-1.0.gir 
> --symbols libcaribou.symbols   -C display-adapter.vala xadapter.vala 
> keyboard-model.vala keyboard-service.vala group-model.vala level-model.vala 
> row-model.vala key-model.vala column-model.vala scanner.vala 
> iscannable-item.vala iscannable-group.vala scannable-group.vala 
> ikeyboard-object.vala xml-deserializer.vala
> xadapter.vala:170.37-170.68: warning: `Gdk.x11_get_default_root_xwindow' has 
> been deprecated since vala-0.24. Use Gdk.X11.get_default_root_xwindow
> xadapter.vala:174.35-174.66: warning: `Gdk.x11_get_default_root_xwindow' has 
> been deprecated since vala-0.24. Use Gdk.X11.get_default_root_xwindow
> xadapter.vala:218.30-218.51: warning: `Gdk.Keymap.get_default' has been 
> deprecated since 3.22
> xadapter.vala:32.29-32.42: warning: `Gdk.X11Display' has been deprecated 
> since vala-0.24. Use Gdk.X11.Display
> xadapter.vala:33.19-33.31: warning: `Gdk.X11Window' has been deprecated since 
> vala-0.24. Use Gdk.X11.Window
> scannable-group.vala:62.21-62.62: warning: Access to possible `null'. Perform 
> a check or use an unsafe cast.
> (item as ScannableGroup).get_scan_children();
> ^^
> keyboard-service.vala:7.9-7.48: warning: DBus methods are recommended to 
> throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
> public abstract void set_cursor_location(int x, int y, int w, int h);
> 
> keyboard-service.vala:8.9-8.47: warning: DBus methods are recommended to 
> throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
> public abstract void set_entry_location(int x, int y, int w, int h);
> ^^^
> keyboard-service.vala:9.9-9.33: warning: DBus methods are recommended to 
> throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
> public abstract void show(uint32 timestamp);
> ^
> keyboard-service.vala:10.9-10.33: warning: DBus methods are recommended to 
> throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
> public abstract void hide(uint32 timestamp);
> ^
> Compilation succeeded - 10 warning(s)
> mv -f libcaribou_la_vala.stamp-t libcaribou_la_vala.stamp
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc 
> -DPACKAGE_NAME=\"caribou\" -DPACKAGE_TARNAME=\"caribou\" 
> -DPACKAGE_VERSION=\"0.4.21\" -DPACKAGE_STRING=\"caribou\ 0.4.21\" 
> -DPACKAGE_BUGREPORT=\"https://bugzilla.gnome.org/enter_bug.cgi\?product=caribou\;
>  -DPACKAGE_URL=\"\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -DPACKAGE=\"caribou\" -DVERSION=\"0.4.21\" 
> -DGETTEXT_PACKAGE=\"caribou\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 
> -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 
> -DENABLE_NLS=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
> -DG_LOG_DOMAIN=\"caribou\" -I.. -pthread -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
> -I/usr/include/harfbuzz -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/libxml2 -I/usr/include/gee-0.8 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o libcaribou_la-display-ad

Bug#997654: billiard: FTBFS: Configuration error: There is a syntax error in your configuration file: invalid syntax (conf.py, line 173)

[Lucas Nussbaum]

Source: billiard
Version: 3.6.4.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHONPATH=. python3 -m sphinx -b html -N Doc 
> /<>/debian/python-billiard-doc/usr/share/doc/python-billiard-doc/html
> Running Sphinx v4.2.0
> 
> Configuration error:
> There is a syntax error in your configuration file: invalid syntax (conf.py, 
> line 173)
> 
> make[1]: *** [debian/rules:17: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/billiard_3.6.4.0-1_unstable.log

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

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

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

Bug#997652: sparql-wrapper-python: FTBFS: error in SPARQLWrapper setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: sparql-wrapper-python
Version: 1.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package sparql-wrapper-python
> dpkg-buildpackage: info: source version 1.8.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sandro Tosi 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'use_2to3_fixers'
>   warnings.warn(msg)
> error in SPARQLWrapper setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:15: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sparql-wrapper-python_1.8.5-1_unstable.log

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

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

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

Bug#997651: python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not callable

[Lucas Nussbaum]

Source: python-ara
Version: 1.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> PYTHON=python3 python3 -m sphinx -b html doc/source 
> debian/python-ara-doc/usr/share/doc/python-ara-doc/html
> Running Sphinx v4.2.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 18 source files that are out of date
> updating environment: [new config] 18 added, 0 changed, 0 removed
> reading sources... [  5%] ansible-configuration
> reading sources... [ 11%] ansible-role-ara-api
> reading sources... [ 16%] ansible-role-ara-web
> reading sources... [ 22%] api-configuration
> reading sources... [ 27%] api-documentation
> reading sources... [ 33%] api-security
> reading sources... [ 38%] api-usage
> reading sources... [ 44%] ara-api-lookup
> reading sources... [ 50%] ara-manage
> reading sources... [ 55%] ara-plugin-configuration
> reading sources... [ 61%] ara-record
> reading sources... [ 66%] container-images
> reading sources... [ 72%] contributing
> reading sources... [ 77%] distributed-sqlite-backend
> reading sources... [ 83%] faq
> reading sources... [ 88%] index
> reading sources... [ 94%] installation
> reading sources... [100%] playbook-names-and-labels
> 
> /<>/doc/source/ara-manage.rst:25: WARNING: Command 'ara-manage 
> --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:32: WARNING: Command 'ara-manage 
> prune --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:41: WARNING: Command 'ara-manage 
> changepassword --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:48: WARNING: Command 'ara-manage 
> createsuperuser --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:55: WARNING: Command 'ara-manage 
> makemigrations --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:64: WARNING: Command 'ara-manage 
> migrate --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:76: WARNING: Command 'ara-manage 
> runserver --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:86: WARNING: Command 'ara-manage 
> generate --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  5%] ansible-configuration
> writing output... [ 11%] ansible-role-ara-api
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 127, in 
> get_lexer
> lexer = lexer_classes[lang](**opts)
> TypeError: 'AnsibleYamlJinjaLexer' object is not callable
> The full traceback has been saved in /tmp/sphinx-err-9sp7oh5b.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> make[1]: *** [debian/rules:19: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-ara_1.4.3-1_unstable.log

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

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

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

Bug#997650: xtel: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: xtel
Version: 3.3.0-24
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/Videotex'
> gcc -g -O2  -DUSE_MOTIF -DUSE_SYSLOG-DDONT_USE_POPUP  -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO -Wdate-time -D_FORTIFY_SOURCE=2  
> -c -o Videotex.o Videotex.c
> In file included from /usr/include/malloc.h:22,
>  from Videotex.c:25:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> Videotex.c: In function ‘alloc_DRCS’:
> Videotex.c:545:9: warning: implicit declaration of function ‘exit’ 
> [-Wimplicit-function-declaration]
>   545 | exit (1);
>   | ^~~~
> Videotex.c:31:1: note: include ‘’ or provide a declaration of ‘exit’
>30 | #include "VideotexP.h"
>   +++ |+#include 
>31 | 
> Videotex.c:545:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   545 | exit (1);
>   | ^~~~
> Videotex.c:545:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c:551:13: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   551 | exit (1);
>   | ^~~~
> Videotex.c:551:13: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c:555:13: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   555 | exit (1);
>   | ^~~~
> Videotex.c:555:13: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c: In function ‘atoni’:
> Videotex.c:3868:13: warning: implicit declaration of function ‘atoi’; did you 
> mean ‘atoni’? [-Wimplicit-function-declaration]
>  3868 | return (atoi(buf));
>   | ^~~~
>   | atoni
> Videotex.c: In function ‘Initialize’:
> Videotex.c:4203:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>  4203 | exit(1);
>   | ^~~~
> Videotex.c:4203:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c:4207:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>  4207 | exit(1);
>   | ^~~~
> Videotex.c:4207:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c:4211:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>  4211 | exit(1);
>   | ^~~~
> Videotex.c:4211:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c:4219:9: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>  4219 | exit(1);
>   | ^~~~
> Videotex.c:4219:9: note: include ‘’ or provide a declaration of 
> ‘exit’
> Videotex.c: In function ‘reconnaissance_commande’:
> Videotex.c:1057:21: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1057 | write(pv->fd_connexion, "\023", 1);
>   | ^~
> Videotex.c:1058:21: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1058 | write(pv->fd_connexion, 
> commandes_minitel[i].code, 1);
>   | 
> ^
> Videotex.c:1077:13: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1077 | write(pv->fd_connexion, chaine, strlen(chaine));
>   | ^~~
> Videotex.c:1097:17: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1097 | write(pv->fd_connexion,

Bug#997649: feedparser: FTBFS: error in feedparser setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: feedparser
Version: 5.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean 
> error in feedparser setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:11: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/feedparser_5.2.1-3_unstable.log

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

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

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

Bug#997648: pyvirtualdisplay: FTBFS: error in PyVirtualDisplay setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pyvirtualdisplay
Version: 0.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'use_2to3_exclude_fixers'
>   warnings.warn(msg)
> error in PyVirtualDisplay setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyvirtualdisplay_0.2.1-3_unstable.log

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

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

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

Bug#997647: pystache: FTBFS: error in pystache setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pystache
Version: 0.5.4-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 8 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> pystache: using: version '58.2.0' of  '/usr/lib/python3/dist-packages/setuptools/__init__.py'>
> Warning: 'classifiers' should be a list, got type 'tuple'
> error in pystache setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:9: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pystache_0.5.4-6.1_unstable.log

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

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

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

Bug#997646: ssvnc: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: ssvnc
Version: 1.0.29-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/vnc_unixsrc/libvncauth'
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security-I. -I../include -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o vncauth.o vncauth.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from vncauth.c:24:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security-I. -I../include -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o d3des.o d3des.c
> rm -f libvncauth.a
> ar clq libvncauth.a vncauth.o d3des.o
> ar: libdeps specified more than once
> make[2]: *** [Makefile:1053: libvncauth.a] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ssvnc_1.0.29-5_unstable.log

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

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

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

Bug#997645: python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-slimmer
Version: 0.1.30-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in slimmer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-slimmer_0.1.30-8_unstable.log

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

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

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

Bug#997644: rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: rnc2rng
Version: 2.6.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in rnc2rng setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rnc2rng_2.6.4-1_unstable.log

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

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

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

Bug#997643: ctwm: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: ctwm
Version: 3.7-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO-DUSEM4 -DGNOME  -DXPM -DJPEG -DX11R6 -DSOUNDS  -DI18N  
> -DUSE_GNU_REGEX  `dpkg-buildflags --get CPPFLAGS`  -c -o libctwm.o libctwm.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from libctwm.c:26:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f libctwm.a
> ar clq libctwm.a  libctwm.o
> ar: libdeps specified more than once
> make[1]: *** [Makefile:1245: libctwm.a] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ctwm_3.7-5_unstable.log

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

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

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

Bug#997642: jquery-tablesorter: FTBFS: DefaultsError: `ie8` is not a supported option

[Lucas Nussbaum]

Source: jquery-tablesorter
Version: 1:2.31.3+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_build
> grunt --verbose
> Initializing
> Command-line options: --verbose, --gruntfile=/<>/Gruntfile.js
> 
> Reading "Gruntfile.js" Gruntfile...OK
> 
> Registering Gruntfile tasks.
> Reading package.json...OK
> Parsing package.json...OK
> Initializing config...OK
> 
> Registering "grunt-contrib-clean" local Npm module tasks.
> Reading /usr/share/nodejs/grunt-contrib-clean/package.json...OK
> Parsing /usr/share/nodejs/grunt-contrib-clean/package.json...OK
> Loading "clean.js" tasks...OK
> + clean
> 
> Registering "grunt-contrib-jshint" local Npm module tasks.
> >> Local Npm module "grunt-contrib-jshint" not found. Is it installed?
> 
> Registering "grunt-htmlhint" local Npm module tasks.
> >> Local Npm module "grunt-htmlhint" not found. Is it installed?
> 
> Registering "grunt-contrib-qunit" local Npm module tasks.
> >> Local Npm module "grunt-contrib-qunit" not found. Is it installed?
> 
> Registering "grunt-contrib-concat" local Npm module tasks.
> Reading /usr/share/nodejs/grunt-contrib-concat/package.json...OK
> Parsing /usr/share/nodejs/grunt-contrib-concat/package.json...OK
> Loading "concat.js" tasks...OK
> + concat
> 
> Registering "grunt-contrib-uglify" local Npm module tasks.
> Reading /usr/share/nodejs/grunt-contrib-uglify/package.json...OK
> Parsing /usr/share/nodejs/grunt-contrib-uglify/package.json...OK
> Loading "uglify.js" tasks...OK
> + uglify
> 
> Registering "grunt-contrib-copy" local Npm module tasks.
> Reading /usr/share/nodejs/grunt-contrib-copy/package.json...OK
> Parsing /usr/share/nodejs/grunt-contrib-copy/package.json...OK
> Loading "copy.js" tasks...OK
> + copy
> 
> Registering "grunt-contrib-watch" local Npm module tasks.
> >> Local Npm module "grunt-contrib-watch" not found. Is it installed?
> 
> Registering "grunt-contrib-cssmin" local Npm module tasks.
> >> Local Npm module "grunt-contrib-cssmin" not found. Is it installed?
> 
> Registering "grunt-jscs" local Npm module tasks.
> >> Local Npm module "grunt-jscs" not found. Is it installed?
> Loading "Gruntfile.js" tasks...OK
> + custom, default, quick, test, updateManifest
> 
> No tasks specified, running default tasks.
> Running tasks: default
> 
> Running "default" task
> Creating a widgets file with: storage, uitheme, columns, filter, 
> stickyHeaders, resizable, saveSort
> !js/parsers/*.js
> 
> Running "clean:build" (clean) task
> Verifying property clean.build exists in config...OK
> Files: [no src]
> Options: force=false, no-write=false
> >> 0 paths cleaned.
> 
> Running "copy" task
> 
> Running "copy:css" (copy) task
> Verifying property copy.css exists in config...OK
> Files: css/dragtable.mod.css -> dist/css/dragtable.mod.css
> Files: css/filter.formatter.css -> dist/css/filter.formatter.css
> Files: css/highlights.css -> dist/css/highlights.css
> Files: css/theme.black-ice.css -> dist/css/theme.blackice.css
> Files: css/theme.blue.css -> dist/css/theme.blue.css
> Files: css/theme.bootstrap_2.css -> dist/css/theme.bootstrap_2.css
> Files: css/theme.bootstrap_3.css -> dist/css/theme.bootstrap_3.css
> Files: css/theme.bootstrap_4.css -> dist/css/theme.bootstrap_4.css
> Files: css/theme.bootstrap.css -> dist/css/theme.bootstrap.css
> Files: css/theme.dark.css -> dist/css/theme.dark.css
> Files: css/theme.default.css -> dist/css/theme.default.css
> Files: css/theme.dropbox.css -> dist/css/theme.dropbox.css
> Files: css/theme.green.css -> dist/css/theme.green.css
> Files: css/theme.grey.css -> dist/css/theme.grey.css
> Files: css/theme.ice.css -> dist/css/theme.ice.css
> Files: css/theme.jui.css -> dist/css/theme.jui.css
> Files: css/theme.materialize.css -> dist/css/theme.materialize.css
> Files: css/theme.metro-dark.css -> dist/css/theme.metro-dark.css
> Files: css/widget.grouping.css -> dist/css/widget.grouping.css
> Files: addons/pager/jquery.tablesorter.pager.css -> 
> dist/css/jquery.tablesorter.pager.css
> Options: encoding="utf8", processContent=false, processContentExclude=[], 
> timestamp=false, mode=false

Bug#997641: knews: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: knews
Version: 1.0b.1-33
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/Widgets'
> gcc -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L 
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>   -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o ArtText.o ArtText.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from ArtText.c:5:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> ArtText.c: In function ‘get_sel_len’:
> ArtText.c:885:8: warning: suggest explicit braces to avoid ambiguous ‘else’ 
> [-Wdangling-else]
>   885 | if (start == stop)
>   |^
> ArtText.c: In function ‘get_sel’:
> ArtText.c:940:8: warning: suggest explicit braces to avoid ambiguous ‘else’ 
> [-Wdangling-else]
>   940 | if (start == stop)
>   |^
> ArtText.c:969:8: warning: suggest explicit braces to avoid ambiguous ‘else’ 
> [-Wdangling-else]
>   969 | if (stop->gen.type == LineTypeString)
>   |^
> ArtText.c: In function ‘click’:
> ArtText.c:1151:31: warning: variable ‘button’ set but not used 
> [-Wunused-but-set-variable]
>  1151 | int x, y, button;
>   |   ^~
> gcc -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L 
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>   -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o ArtTree.o ArtTree.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from ArtTree.c:5:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> ArtTree.c: In function ‘ArtTreeNodeSetDashed’:
> ArtTree.c:1284:8: warning: suggest explicit braces to avoid ambiguous ‘else’ 
> [-Wdangling-else]
>  1284 | if (dashed)
>   |^
> gcc -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L 
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>   -Wdate-time -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o CloseSh.o CloseSh.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from CloseSh.c:5:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> gcc -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L 
> -D_POSIX_SOURCE -D_XOPEN_SOURCE  

Bug#997640: pybluez: FTBFS: error in PyBluez setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pybluez
Version: 0.23-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf PyBluez.egg*
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in PyBluez setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make[1]: *** [debian/rules:23: override_dh_auto_clean] Error 25


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

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

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

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

Bug#997638: nas: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: nas
Version: 1.9.4-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/server/dia'
> rm -f dispatch.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   -DNASCONFSEARCHPATH=\"/etc/nas/\"   
> dispatch.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/string.h:26,
>  from ../include/os.h:124,
>  from ../include/misc.h:57,
>  from dispatch.c:52:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f dixutils.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   -DNASCONFSEARCHPATH=\"/etc/nas/\"   
> dixutils.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/string.h:26,
>  from ../include/os.h:124,
>  from ../include/misc.h:57,
>  from dixutils.c:52:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f events.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   -DNASCONFSEARCHPATH=\"/etc/nas/\"   
> events.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/string.h:26,
>  from ../include/os.h:124,
>  from ../include/misc.h:57,
>  from events.c:52:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f globals.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon   -I. 
> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO   -DNASCONFSEARCHPATH=\"/etc/nas/\"   
> globals.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>   

Bug#997639: python-keepalive: FTBFS: error in keepalive setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-keepalive
Version: 0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in keepalive setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:9: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-keepalive_0.5-2_unstable.log

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

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

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

Bug#997637: python-oauth: FTBFS: error in oauth setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-oauth
Version: 1.0.1-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> error in oauth setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:5: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-oauth_1.0.1-6_unstable.log

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

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

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

Bug#997636: koules: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: koules
Version: 1.4-27
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: warning: -j4 forced in submake: resetting jobserver mode.
> gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM 
> -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6  -ffast-math  -I.   
> -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\"
> -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o init.o init.c
> gcc  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mem.o mem.S
> gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM 
> -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6  -ffast-math  -I.   
> -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\"
> -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o interface.o interface.c
> gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM 
> -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6  -ffast-math  -I.   
> -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\"
> -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\"  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o shmbitmap.o shmbitmap.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from init.c:18:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdint.h:26,
>  from /usr/lib/gcc/x86_64-linux-gnu/11/include/stdint.h:9,
>  from interface.c:17:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdlib.h:25,
>  from shmbitmap.c:24:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> gcc -g -O2 -fno-strict-aliasing-Ixlib -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -DONLYANSI -DSOUND -DJOYSTICK -DNETSUPPORT -DMITSHM 
> -DHAVEUSLEEP -Wall -fomit-frame-pointer -O6  -ffast-math  -I.   
> -DASSEMBLY -DSOUNDSERVER=\"/usr/games/koules.sndsrv.linux\"
> -DSOUNDDIR=\"/usr/lib/games/koules\"-DSOUNDDEV=\"/dev/dsp\"  -Wdate-time

Bug#997635: flask-openid: FTBFS: error in Flask-OpenID setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: flask-openid
Version: 1.2.5+dfsg-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with=python3,sphinxdoc --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in Flask-OpenID setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/flask-openid_1.2.5+dfsg-5_unstable.log

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

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

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

Bug#997634: python-rdflib-jsonld: FTBFS: error in rdflib-jsonld setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-rdflib-jsonld
Version: 0.5.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in rdflib-jsonld setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:11: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-rdflib-jsonld_0.5.0-1_unstable.log

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

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

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

Bug#997633: python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-tempita
Version: 0.5.2-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in Tempita setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-tempita_0.5.2-6_unstable.log

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

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

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

Bug#997632: behave: FTBFS: error in behave setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: behave
Version: 1.2.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'upload-dir' will not be supported in future versions. Please 
> use the underscore name 'upload_dir' instead
>   warnings.warn(
> error in behave setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:5: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/behave_1.2.6-3_unstable.log

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

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

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

Bug#997631: pycallgraph: FTBFS: error in pycallgraph2 setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pycallgraph
Version: 1.1.3-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> error in pycallgraph2 setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pycallgraph_1.1.3-1.2_unstable.log

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

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

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

Bug#997628: mgp: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: mgp
Version: 1.13a+upstream20090219-12
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/image'
> rm -f imagetypes.o
> gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable 
> -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function 
> -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>-D_POSIX_SOURCE -D_XOPEN_SOURCE
>  -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time 
> -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" 
> -D_DEFAULT_SOURCE-D_GNU_SOURCE   -DPACKAGE_NAME=\"\" 
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
> -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_FILE_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_STDARG_H=1 
> -DHAVE_TERMIOS_H=1 -DHAVE_LOCALE_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void 
> -DHAVE_POLL=1 -DHAVE_STRSTR=1 -DHAVE_USLEEP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 
> -DHAVE_MKSTEMP=1 -DHAVE_SNPRINTF=1 -DHAVE_MEMCMP=1 -DUSE_PNG=1 -DUSE_XFT2=1 
> -DHAVE_ICONV=1 -DHAVE_FONTCONFIG_FONTCONFIG_H=1 -DUSE_GIF=1 -DUSE_IMLIB=1 
> imagetypes.c
> rm -f send.o
> gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable 
> -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function 
> -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>-D_POSIX_SOURCE -D_XOPEN_SOURCE
>  -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time 
> -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" 
> -D_DEFAULT_SOURCE-D_GNU_SOURCE   -DPACKAGE_NAME=\"\" 
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
> -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_FILE_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_STDARG_H=1 
> -DHAVE_TERMIOS_H=1 -DHAVE_LOCALE_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void 
> -DHAVE_POLL=1 -DHAVE_STRSTR=1 -DHAVE_USLEEP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 
> -DHAVE_MKSTEMP=1 -DHAVE_SNPRINTF=1 -DHAVE_MEMCMP=1 -DUSE_PNG=1 -DUSE_XFT2=1 
> -DHAVE_ICONV=1 -DHAVE_FONTCONFIG_FONTCONFIG_H=1 -DUSE_GIF=1 -DUSE_IMLIB=1 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16  
> -DUUDECODE=\"/usr/bin/uudecode\" -DGUNZIP=\"/bin/gunzip\" -DUSE_SETLOCALE 
> -I/usr/include/libpng16 -I/usr/include   send.c
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable 
> -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function 
> -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
>   -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO-Wdate-time 
> -D_FORTIFY_SOURCE=2 -DFREETYPEFONTDIR="/usr/share/fonts/truetype" 
> -D_DEFAULT_SOURCE-D_GNU_SOURCE -c -o zio.o zio.c
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -Wformat -Wno-unused-variable 
> -Wno-unused-but-set-variable -Wno-pointer-sign -Wno-unused-function 
> -Wno-unused-result -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=19

Bug#997630: pygithub: FTBFS: error in PyGithub setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pygithub
Version: 1.43.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf *.egg-info
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in PyGithub setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pygithub_1.43.7-1_unstable.log

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

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

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

Bug#997629: pyraf: FTBFS: error in setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pyraf
Version: 2.1.15-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'requires-python' will not be supported in future versions. 
> Please use the underscore name 'requires_python' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'pre-hook.glob-data-files' will not be supported in future 
> versions. Please use the underscore name 'pre_hook.glob_data_files' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'pre-hook.pyraf-buildext-hook' will not be supported in future 
> versions. Please use the underscore name 'pre_hook.pyraf_buildext_hook' 
> instead
>   warnings.warn(
> error in setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyraf_2.1.15-2_unstable.log

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

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

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

Bug#997627: pixmap: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: pixmap
Version: 2.6pl4-20
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/SelFile'
> rm -f SelFile.o
> gcc -c -g -O2 -fno-strict-aliasing  -I. -I.. -I/usr/include/X11 
> -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA 
> -DAPPDEFDIR=\"/etc/X11/app-defaults\"   
> -DRGBF=\"/etc/X11/rgb.txt\"   SelFile.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from SelFile.c:46:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> SelFile.c: In function ‘SFexposeList’:
> SelFile.c:153:9: warning: implicit declaration of function ‘SFdrawList’ 
> [-Wimplicit-function-declaration]
>   153 | SFdrawList(n, SF_DO_NOT_SCROLL);
>   | ^~
> SelFile.c: In function ‘SFcreateWidgets’:
> SelFile.c:275:9: warning: implicit declaration of function ‘SFinitFont’ 
> [-Wimplicit-function-declaration]
>   275 | SFinitFont();
>   | ^~
> SelFile.c:481:9: warning: implicit declaration of function ‘SFcreateGC’; did 
> you mean ‘XCreateGC’? [-Wimplicit-function-declaration]
>   481 | SFcreateGC();
>   | ^~
>   | XCreateGC
> SelFile.c: In function ‘SFopenFile’:
> SelFile.c:568:5: warning: implicit declaration of function ‘SFchdir’; did you 
> mean ‘fchdir’? [-Wimplicit-function-declaration]
>   568 | SFchdir(SFstartDir);
>   | ^~~
>   | fchdir
> SelFile.c: At top level:
> SelFile.c:594:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   594 | SFtextChanged()
>   | ^
> SelFile.c: In function ‘SFtextChanged’:
> SelFile.c:613:9: warning: implicit declaration of function ‘SFupdatePath’ 
> [-Wimplicit-function-declaration]
>   613 | SFupdatePath();
>   | ^~~~
> SelFile.c: At top level:
> SelFile.c:624:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   624 | SFprepareToReturn()
>   | ^
> SelFile.c: In function ‘XsraSelFile’:
> SelFile.c:710:33: warning: implicit declaration of function ‘SFsetText’; did 
> you mean ‘SFgetText’? [-Wimplicit-function-declaration]
>   710 | SFsetText(SFcurrentPath);
>   | ^
>   | SFgetText
> rm -f Path.o
> gcc -c -g -O2 -fno-strict-aliasing  -I. -I.. -I/usr/include/X11 
> -I/usr/include/-Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L  
> -D_POSIX_SOURCE -D_XOPEN_SOURCE 
> -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO -DUSE_ATHENA 
> -DAPPDEFDIR=\"/etc/X11/app-defaults\"   
> -DRGBF=\"/etc/X11/rgb.txt\"   Path.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from Path.c:27:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> Path.c:86:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>86 | SFfree(i)
>   | ^~
> Path.c:109:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   109 | SFunreadableDir(dir)
>   | ^~~
> Path.c:169:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   169 | SFreplaceText(dir, str)
>   | ^
> Path.c: In function ‘SFreplaceText’:
> Path.c:183:17: warning: implicit declaration of function ‘SFsetText’ 
> [-Wimplicit-function-declaration]
>   183 | SFsetText(

Bug#997626: django-restricted-resource: FTBFS: TypeError: Abstract models cannot be instantiated.

[Lucas Nussbaum]

Source: django-restricted-resource
Version: 2016.8-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> # Run the bundled tests (in-memory database) when building the package
> LC_ALL=C python3 ./django_restricted_resource/test_project/manage.py test
> Creating test database for alias 'default'...
> System check identified some issues:
> 
> WARNINGS:
> django_restricted_resource.ExampleRestrictedResource: (models.W042) 
> Auto-created primary key used when not defining a primary key type, by 
> default 'django.db.models.AutoField'.
>   HINT: Configure the DEFAULT_AUTO_FIELD setting or the 
> AppConfig.default_auto_field attribute to point to a subclass of AutoField, 
> e.g. 'django.db.models.BigAutoField'.
> 
> System check identified 1 issue (0 silenced).
> ....
> ==
> ERROR: test_clean_is_okay_when_just_group_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_group_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 64, in test_clean_is_okay_when_just_group_set
> resource = RestrictedResource(group=group)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_is_okay_when_just_user_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_user_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 59, in test_clean_is_okay_when_just_user_set
> resource = RestrictedResource(user=user)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_raises_exception_when_both_user_and_group_is_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_both_user_and_group_is_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 54, in test_clean_raises_exception_when_both_user_and_group_is_set
> resource = RestrictedResource(user=user, group=group)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_raises_exception_when_owner_is_not_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_owner_is_not_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 48, in test_clean_raises_exception_when_owner_is_not_set
> resource = RestrictedResource()
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract

Bug#997624: python-defer: FTBFS: error in defer setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-defer
Version: 1.0.6-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_requires'
>   warnings.warn(msg)
> error in defer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:7: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-defer_1.0.6-2.1_unstable.log

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

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

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

Bug#997625: node-jquery: FTBFS: DefaultsError: `ie8` is not a supported option

[Lucas Nussbaum]

Source: node-jquery
Version: 3.5.1+dfsg+~3.5.5-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> mkdir -p external
> mkdir -p external/sizzle/dist
> ln -s /usr/share/javascript/sizzle/sizzle.js external/sizzle/dist
> grunt qunit_fixture
> Loading "babel.js" tasks...ERROR
> >> Error: Cannot find module '@babel/core'
> >> Require stack:
> >> - /usr/share/nodejs/grunt-babel/tasks/babel.js
> >> - /usr/share/nodejs/grunt/lib/grunt/task.js
> >> - /usr/share/nodejs/grunt/lib/grunt.js
> >> - /usr/share/nodejs/grunt-cli/bin/grunt
> >>  grunt-babel@8 requires Babel 7.x (the package '@babel/core'). If you'd 
> >> like to use Babel 6.x ('babel-core'), you should install 'grunt-babel@7'.
> 
> Running "qunit_fixture" task
> >> Updated ./test/data/qunit-fixture.js.
> 
> Done.
> grunt build:*:* uglify remove_map_comment dist:*
> Loading "babel.js" tasks...ERROR
> >> Error: Cannot find module '@babel/core'
> >> Require stack:
> >> - /usr/share/nodejs/grunt-babel/tasks/babel.js
> >> - /usr/share/nodejs/grunt/lib/grunt/task.js
> >> - /usr/share/nodejs/grunt/lib/grunt.js
> >> - /usr/share/nodejs/grunt-cli/bin/grunt
> >>  grunt-babel@8 requires Babel 7.x (the package '@babel/core'). If you'd 
> >> like to use Babel 6.x ('babel-core'), you should install 'grunt-babel@7'.
> 
> Running "build:all:*" (build) task
> >> File 'dist/jquery.js' created.
> 
> Running "uglify:all" (uglify) task
> DefaultsError: `ie8` is not a supported option
> at DefaultsError.get (:69:23)
> at formatError (internal/util/inspect.js:1164:38)
> at formatRaw (internal/util/inspect.js:937:14)
> at formatValue (internal/util/inspect.js:791:10)
> at inspect (internal/util/inspect.js:328:10)
> at formatWithOptions (internal/util/inspect.js:1989:40)
> at console.value (internal/console/constructor.js:308:14)
> at console.log (internal/console/constructor.js:343:61)
> at /usr/share/nodejs/grunt-contrib-uglify/tasks/uglify.js:156:17
> at Array.forEach (:null:null)
> at Object. 
> (/usr/share/nodejs/grunt-contrib-uglify/tasks/uglify.js:90:16)
> at Object. (/usr/share/nodejs/grunt/lib/grunt/task.js:253:15)
> at Object.thisTask.fn (/usr/share/nodejs/grunt/lib/grunt/task.js:71:16)
> at Object. (/usr/share/nodejs/grunt/lib/util/task.js:294:30)
> at Task.runTaskFn (/usr/share/nodejs/grunt/lib/util/task.js:244:24)
> at Task. (/usr/share/nodejs/grunt/lib/util/task.js:293:12)
> at /usr/share/nodejs/grunt/lib/util/task.js:220:11
> at processTicksAndRejections (internal/process/task_queues.js:79:11)
>  {
>   defs: {
> annotations: false,
> ascii_only: false,
> beautify: false,
> braces: false,
> comments: false,
> galio: false,
> ie: false,
> indent_level: 4,
> indent_start: 0,
> inline_script: true,
> keep_quoted_props: false,
> max_line_len: false,
> preamble: null,
> preserve_line: false,
> quote_keys: false,
> quote_style: 0,
> semicolons: true,
> shebang: true,
> source_map: null,
> v8: false,
> webkit: false,
> width: 80,
> wrap_iife: false
>   }
> }
> >> Uglifying source dist/jquery.js failed.
> Warning: Uglification failed.
> `ie8` is not a supported option. 
>  Use --force to continue.
> 
> Aborted due to warnings.
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 6


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-jquery_3.5.1+dfsg+~3.5.5-7_unstable.log

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

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

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

Bug#997622: kinput2: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: kinput2
Version: 3.1-13
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/lib'
> rm -f AdoptedShe.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -I../include 
> -Iimlib  -I/usr/include   -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO
> AdoptedShe.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from AdoptedShe.c:21:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f AuxPanel.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -I../include 
> -Iimlib  -I/usr/include   -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTOAuxPanel.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from AuxPanel.c:51:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f CandPanel.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -I../include 
> -Iimlib  -I/usr/include   -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTOCandPanel.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from CandPanel.c:21:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> CandPanel.c: In function ‘Notify’:
> CandPanel.c:472:24: warning: cast to pointer from integer of different size 
> [-Wint-to-pointer-cast]
>   472 |(XtPointer)cpw->cpanel.current);
>   |^
> rm -f Canvas.o
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -I../include 
> -Iimlib  -I/usr/include   -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L   
> -D_POSIX_SOURCE -D_XOPEN_SOURCE   
>   -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTOCanvas.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrins

Bug#997623: funcparserlib: FTBFS: error in funcparserlib setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: funcparserlib
Version: 0.3.6+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in funcparserlib setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:8: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/funcparserlib_0.3.6+dfsg1-1_unstable.log

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

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

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

Bug#997621: fvwm1: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: fvwm1
Version: 1.24r-57
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/libs'
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -c -o CatString3.o CatString3.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from CatString3.c:1:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -c -o SendInfo.o SendInfo.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from SendInfo.c:1:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> SendInfo.c: In function ‘SendInfo’:
> SendInfo.c:17:7: warning: implicit declaration of function ‘write’; did you 
> mean ‘fwrite’? [-Wimplicit-function-declaration]
>17 |   write(fd[0],, sizeof(unsigned long));
>   |   ^
>   |   fwrite
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -c -o SendText.o SendText.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from SendText.c:1:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> SendText.c: In function ‘SendText’:
> SendText.c:15:7: warning: implicit declaration of function ‘write’; did you 
> mean ‘fwrite’? [-Wimplicit-function-declaration]
>15 |   write(fd[0],, sizeof(unsigned long));
>   |   ^
>   |   fwrite
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>   -DFUNCPROTO=15 
> -DNARROWPROTO   -c -o wild.o wild.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from wild.c:1:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> wild.c: In function ‘matchWildcards’:
> wild.c:23:15: warning: implicit declaration of function ‘strcmp’ 
> [-Wimplicit-function-declaration]
>23 |   else if(strcmp(pattern,"*")==0)
>   |   ^~
> wild.c:2:1: note: include ‘’ or provide a declaration of ‘strcmp’
> 1 | #include 
>   +++ |+#include 
> 2 | 
> gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=1993

Bug#997620: python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-dexml
Version: 0.5.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in dexml setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-dexml_0.5.1-3_unstable.log

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

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

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

Bug#997619: python-mailer: FTBFS: error in mailer setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-mailer
Version: 0.8.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh  clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in mailer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-mailer_0.8.1-4_unstable.log

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

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

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

Bug#997618: python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-jsmin
Version: 2.2.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3 --verbose
>dh_auto_clean -O--buildsystem=pybuild -O--verbose
>   pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean 
> error in jsmin setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-jsmin_2.2.2-2_unstable.log

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

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

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

Bug#997617: twofish: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: twofish
Version: 0.3-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_testdir
> #
> gcc -c -o twofish.o -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wextra -O0 twofish.c
> twofish.c: In function ‘test_platform’:
> twofish.c:498:58: warning: comparison of unsigned expression in ‘< 0’ is 
> always false [-Wtype-limits]
>   498 | if( ((UInt32) ((UInt32)1 << 31) == 0) || ((UInt32)-1 < 0) )
>   |  ^
> ar clq libtwofish.a twofish.o
> ar: libdeps specified more than once
> make: *** [debian/rules:30: build-arch-stamp] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/twofish_0.3-5_unstable.log

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

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

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

Bug#997616: python-anyjson: FTBFS: error in anyjson setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-anyjson
Version: 0.3.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> error in anyjson setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-anyjson_0.3.3-2_unstable.log

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

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

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

Bug#997615: troffcvt: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: troffcvt
Version: 1.04-25
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/portlib-1.01'
> rm -f ato.o
> gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I /<>/lib -I. -I/usr/local/include 
> -Dlinux -D_POSIX_SOURCE  -D_BSD_SOURCE -D_GNU_SOURCE 
> -DX_LOCALE  -DHAS_SYSCONF=0 -DHAS_FLOCK=1   -DHAS_FCNTL=0   
> -DHAS_SYS_DIR_H=1   -DHAS_DIRENT_H=0-DHAS_BCOPY=1 ato.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from ato.c:13:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f dir.o
> gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I /<>/lib -I. -I/usr/local/include 
> -Dlinux -D_POSIX_SOURCE  -D_BSD_SOURCE -D_GNU_SOURCE 
> -DX_LOCALE  -DHAS_SYSCONF=0 -DHAS_FLOCK=1   -DHAS_FCNTL=0   
> -DHAS_SYS_DIR_H=1   -DHAS_DIRENT_H=0-DHAS_BCOPY=1 dir.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from dir.c:14:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f fd.o
> gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I /<>/lib -I. -I/usr/local/include 
> -Dlinux -D_POSIX_SOURCE  -D_BSD_SOURCE -D_GNU_SOURCE 
> -DX_LOCALE  -DHAS_SYSCONF=0 -DHAS_FLOCK=1   -DHAS_FCNTL=0   
> -DHAS_SYS_DIR_H=1   -DHAS_DIRENT_H=0-DHAS_BCOPY=1 fd.c
> fd.c: In function ‘MaxFileDesc’:
> fd.c:24:17: warning: implicit declaration of function ‘getdtablesize’ 
> [-Wimplicit-function-declaration]
>24 | return (getdtablesize ());
>   | ^
> rm -f lock.o
> gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I /<>/lib -I. -I/usr/local/include 
> -Dlinux -D_POSIX_SOURCE  -D_BSD_SOURCE -D_GNU_SOURCE 
> -DX_LOCALE  -DHAS_SYSCONF=0 -DHAS_FLOCK=1   -DHAS_FCNTL=0   
> -DHAS_SYS_DIR_H=1   -DHAS_DIRENT_H=0-DHAS_BCOPY=1 lock.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from lock.c:14:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f mem.o
> gcc -c -O -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -I /<>/lib -I. -I/usr/local/include 
> -Dlinux -D_POSIX_SOURCE  -D_BSD_SOURCE -D_GNU_SOURCE 
> -DX_LOCALE  -DHAS_SYSCONF=0 -DHAS_FLOCK=1   -DHAS_FCNTL=0   
> -DHAS_SYS_DIR_H=1   -DHAS_DIRENT_H=0-DHAS_BCOPY=1 mem.c
> In file included from /usr/include/strings.h:21,
>  from mem.c:13:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> rm -f libport.a
> ar clq libport.a ato.o dir.o fd.o lock.o mem.o 
> ar: libdeps specified more than once
> make[3]: *** [Makefile:325: libport.a] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/troffcvt_1.04-25_unstable.log

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

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

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

Bug#997614: python-parse-type: FTBFS: error in parse_type setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-parse-type
Version: 0.3.4-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'upload-dir' will not be supported in future versions. Please 
> use the underscore name 'upload_dir' instead
>   warnings.warn(
> error in parse_type setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-parse-type_0.3.4-3_unstable.log

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

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

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

Bug#997613: blessings: FTBFS: error in blessings setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: blessings
Version: 1.6-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 7 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> error in blessings setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/blessings_1.6-3_unstable.log

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

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

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

Bug#997612: vatnumber: FTBFS: error in vatnumber setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: vatnumber
Version: 1:1.2-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package vatnumber
> dpkg-buildpackage: info: source version 1:1.2-10
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Mathias Behrle 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> error in vatnumber setup command: use_2to3 is invalid.
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in vatnumber setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:9: clean] Error 25


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

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

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

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

Bug#997611: wnn6-sdk: FTBFS: ar: libdeps specified more than once

[Lucas Nussbaum]

Source: wnn6-sdk
Version: 1.0.0-18
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/contrib/im/Xsi/Wnn/jlib'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/msg.o'
> Makefile:1414: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/msg.o'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/yincoding.o'
> Makefile:1417: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/yincoding.o'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/py_table.o'
> Makefile:1420: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/py_table.o'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/zy_table.o'
> Makefile:1423: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/zy_table.o'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/strings.o'
> Makefile:1426: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/strings.o'
> Makefile:1435: warning: overriding recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/serverdefs.o'
> Makefile:1429: warning: ignoring old recipe for target 
> '/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/etc/serverdefs.o'
> rm -f js.o unshared/js.o
> gcc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  
> -I/<>/contrib/im/Xsi/../../../contrib/../contrib/im/Xsi/Wnn/include
>  -I/<>/contrib/im/Xsi/../../../contrib -Dlinux -D__amd64__ 
> -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE 
> -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE  
>-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
>  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DFUNCPROTO=15 -DNARROWPROTO   
> -DLIBDIR=\"/usr/local/lib/wnn6\" -DJAPANESE -DCHINESE -DKOREAN -DLATIN 
> -DWRITE_CHECK-g -O2 -fno-strict-aliasing -g  js.c -o unshared/js.o
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from js.c:167:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> In file included from js.c:207:
> ../etc/pwd.c: In function ‘new_pwd’:
> ../etc/pwd.c:163:9: warning: implicit declaration of function ‘time’ 
> [-Wimplicit-function-declaration]
>   163 | x = time(NULL);
>   | ^~~~
> js.c: In function ‘cd_open_in’:
> js.c:506:14: warning: implicit declaration of function ‘inet_addr’ 
> [-Wimplicit-function-declaration]
>   506 | ia = inet_addr(pserver);
>   |  ^
> js.c: In function ‘_get_server_name’:
> js.c:534:30: warning: implicit declaration of function ‘atoi’ 
> [-Wimplicit-function-declaration]
>   534 | if (*(p+1)) offset = atoi(p+1);
>   |  ^~~~
> js.c: In function ‘js_set_henkan_hinsi’:
> js.c:1453:17: warning: implicit declaration of function ‘abs’ 
> [-Wimplicit-function-declaration]
>  1453 |  for(x = 0; x < abs(nhinsi); x++) put4com(hlist[x], env->js_id);
>   | ^~~
> js.c:208:1: note: include ‘’ or provide a declaration of ‘abs’
>   207 | #include "../etc/pwd.c"
>   +++ |+#include 
>   208 | 
> js.c: In function ‘js_access_get_info’:
> js.c:5099:9: warning: implicit declaration of function ‘free’ 
> [-Wimplicit-function-declaration]
>  5099 | free((char *)save);
>   | ^~~~
> js.c:5099:9: note: include ‘’ or provide a declaration of ‘free’
> js.c:5099:9: warning: incompatible implicit declaration of built-in function 
> ‘free’ [-Wbuiltin-declaration-mismatch]
> js.c:5099:9: not

Bug#997610: suds: FTBFS: error in suds-community setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: suds
Version: 0.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in suds-community setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/suds_0.8.5-1_unstable.log

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

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

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

Bug#997609: deap: FTBFS: error in deap setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: deap
Version: 1.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in deap setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:32: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/deap_1.3.1-2_unstable.log

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

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

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

Bug#997608: easyprocess: FTBFS: error in EasyProcess setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: easyprocess
Version: 0.2.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in EasyProcess setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:5: clean] Error 25


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

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

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

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

Bug#997606: simpleeval: FTBFS: error in simpleeval setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: simpleeval
Version: 0.9.10-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf .egg-info
> rm -rf PKG-INFO
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in simpleeval setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make[1]: *** [debian/rules:16: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/simpleeval_0.9.10-1_unstable.log

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

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

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

Bug#997607: python-fudge: FTBFS: error in fudge setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: python-fudge
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean 
> error in fudge setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-fudge_1.1.0-2_unstable.log

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

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

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

Bug#997605: pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: pprofile
Version: 2.0.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pprofile
> dpkg-buildpackage: info: source version 2.0.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Josue Ortega 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from pprofile-2.0.5/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in pprofile setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:8: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pprofile_2.0.5-1_unstable.log

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

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

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

Bug#997604: x2gobroker: FTBFS: error in x2gobroker setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: x2gobroker
Version: 0.0.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
> -Wl,-z,relro -Wl,-z,now -pie 
> -DTRUSTED_BINARY=\"/usr/lib/x2go/x2gobroker-agent.pl\" -o 
> lib/x2gobroker-agent src/x2gobroker-agent.c
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
> -Wl,-z,relro -Wl,-z,now -pie -DTRUSTED_BINARY=\"/usr/bin/x2gobroker\" -o 
> bin/x2gobroker-ssh src/x2gobroker-ssh.c
> python3 setup.py build
> error in x2gobroker setup command: use_2to3 is invalid.
> make[1]: *** [Makefile:68: build_pymodule] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/x2gobroker_0.0.4.3-1_unstable.log

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

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

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

Bug#997603: glue: FTBFS: error in glue setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: glue
Version: 0.13-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>'
> rm -rf build/sphinx
> make[1]: Leaving directory '/<>'
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in glue setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/glue_0.13-5_unstable.log

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

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

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

Bug#997602: iptables-converter: FTBFS: error in iptables-converter setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: iptables-converter
Version: 0.9.8-1.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf build
> rm -rf *.egg-info
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> error in iptables-converter setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make[1]: *** [debian/rules:27: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/iptables-converter_0.9.8-1.2_unstable.log

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

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

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

Bug#997598: toro: FTBFS: error in toro setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: toro
Version: 1.0.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> Warning: 'classifiers' should be a list, got type 'filter'
> error in toro setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/toro_1.0.1-4_unstable.log

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

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

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

Bug#997601: fail2ban: FTBFS: error in fail2ban setup command: use_2to3 is invalid.

[Lucas Nussbaum]

Source: fail2ban
Version: 0.11.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean 
> error in fail2ban setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:15: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/fail2ban_0.11.2-2_unstable.log

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

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

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