Bug#998401: [Debichem-devel] Bug#998401: nwchem: remove csh requirement
Hi Edoardo, On 2021-11-05 08:07, Apra, Edoardo wrote: > I am not able to reproduce your failure. Sorry, I was too impatient - I tried building once more, and the build was successful. Best, Andrius
Bug#980107: python-rioxarray
Dear Alastair and Magnus, yesterday I have pushed on the salsa repository an updated version of the rioxarray package including the latest upstream version 0.8.0. Please consider it for your review and upload. kind regards antonio Il 02/10/21 17:08, Antonio Valentino ha scritto: Thank Magnus, all branches and tags have been pushed now. Now the package is ready for a review. kind regards antonio Il 02/10/21 16:34, Magnus HAGDORN ha scritto: Hi Antionio, Excellent. I am very happy for you to push directly to the repo. magnus On Sat, 2021-10-02 at 09:48 +0200, Antonio Valentino wrote: This email was sent to you by someone outside the University. You should only click on links or attachments if you are certain that the email is genuine and the content is safe. Dear Alastair and Magnus, I have update the package on my fork [1]. I have temporary removed the -doc package because it not buildable at the moment due to #995299 [2]. We can re-add the -doc package in a future version if necessary. I have also updated the package to the latest upstream version 0.7.1. @Magnus please let me know if you prefer me to push directly on the debian-science repository or to submit a merge request. [1] https://salsa.debian.org/antonio.valentino/python-rioxarray [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995299 kind regards Antonio Il 27/09/21 11:59, Alastair McKinstry ha scritto: Hi Magnus I downloaded and reviewed the package. As it currently stands it needs some work to deal with privacy issues (The lintian tests). Basically sphinxdocs is adding links to cloudflare etc that leak user information. You can look at "python-xarray" to see some solutions - some can be fixed with a patch to the sphinxdocs configuration, some needs editing of the html files in debian/rules to use javascript helpers that you depend-on with the package. Best regards Alastair On 23/08/2021 10:47, Magnus HAGDORN wrote: Hi Alastair and Antonio, Antonio has prodded me to sort out the python-rioxarray. He's updated it to the latest version and enabled the test-suite. I have rebuild the package and uploaded it to mentors: https://mentors.debian.net/package/python-rioxarray/ You offred to sponsor this package before hence my direct request. Antionio has offred to be a co-maintainer - thanks for this and for updating the package. Regards magnus The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336. -- Antonio Valentino -- Antonio Valentino
Bug#998618: bind9.17.19: crashes with INSIST assertion fail resp->disp->active.tail or .head == or != resp
Michael, do you have full coredump available? Ondřej > On 5. 11. 2021, at 3:09, Michael Alan Dorman wrote: > > Package: bind9 > Version: 1:9.17.19-1 > Severity: important > > Dear Maintainer, > > Named began crashing several times a day after updating from bind 9.16.21-1 > to 9.17.19-1 on Oct 30. > > Wanted to report this before dropping back to 9.16.21. > > Some examples of the logs during a crash: > > 2021-11-03T17:40:27.402030-05:00 william named[11429]: dispatch.c:1524: > INSIST((resp->disp->active).tail == (resp)) failed, back trace > 2021-11-03T17:40:27.402343-05:00 william named[11429]: > /usr/sbin/named(+0x1a8eb) [0x44c8eb] > 2021-11-03T17:40:27.402354-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc_assertion_failed+0x25) > [0xb7c49775] > 2021-11-03T17:40:27.402362-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(dns_dispatch_cancel+0x2cc) > [0xb79ec93c] > 2021-11-03T17:40:27.402373-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x110d98) [0xb7ab7d98] > 2021-11-03T17:40:27.402381-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x1170a3) [0xb7abe0a3] > 2021-11-03T17:40:27.402389-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x45d15) [0xb79ecd15] > 2021-11-03T17:40:27.402397-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__nm_async_connectcb+0xa2) > [0xb7c36722] > 2021-11-03T17:40:27.402404-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1cb96) [0xb7c37b96] > 2021-11-03T17:40:27.402411-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d2cc) [0xb7c382cc] > 2021-11-03T17:40:27.402420-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1db28) [0xb7c38b28] > 2021-11-03T17:40:27.402427-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libuv.so.1(+0xd0aa) [0xb75cc0aa] > 2021-11-03T17:40:27.402435-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libuv.so.1(+0x2239e) [0xb75e139e] > 2021-11-03T17:40:27.402443-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libuv.so.1(uv_run+0x10e) [0xb75cca6e] > 2021-11-03T17:40:27.402451-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d353) [0xb7c38353] > 2021-11-03T17:40:27.402458-05:00 william named[11429]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__trampoline_run+0x22) > [0xb7c7db22] > 2021-11-03T17:40:27.402466-05:00 william named[11429]: > /lib/i386-linux-gnu/libpthread.so.0(+0x80af) [0xb73730af] > 2021-11-03T17:40:27.402473-05:00 william named[11429]: > /lib/i386-linux-gnu/libc.so.6(clone+0x66) [0xb72828f6] > 2021-11-03T17:40:27.402481-05:00 william named[11429]: exiting (due to > assertion failure) > > 2021-10-30T12:30:36.648373-05:00 william named[16425]: dispatch.c:1524: > INSIST((resp->disp->active).head == (resp)) failed, back trace > 2021-10-30T12:30:36.648815-05:00 william named[16425]: > /usr/sbin/named(+0x1a8eb) [0x4da8eb] > 2021-10-30T12:30:36.648897-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc_assertion_failed+0x25) > [0xb7c66775] > 2021-10-30T12:30:36.648963-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(dns_dispatch_cancel+0x2cc) > [0xb7a0993c] > 2021-10-30T12:30:36.649025-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x110d98) [0xb7ad4d98] > 2021-10-30T12:30:36.649094-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x1170a3) [0xb7adb0a3] > 2021-10-30T12:30:36.649157-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x45d15) [0xb7a09d15] > 2021-10-30T12:30:36.649234-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__nm_async_connectcb+0xa2) > [0xb7c53722] > 2021-10-30T12:30:36.649298-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1cb96) [0xb7c54b96] > 2021-10-30T12:30:36.649371-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d2cc) [0xb7c552cc] > 2021-10-30T12:30:36.649410-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1db28) [0xb7c55b28] > 2021-10-30T12:30:36.649444-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libuv.so.1(+0xd0aa) [0xb75e90aa] > 2021-10-30T12:30:36.649477-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libuv.so.1(+0x2239e) [0xb75fe39e] > 2021-10-30T12:30:36.649507-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libuv.so.1(uv_run+0x10e) [0xb75e9a6e] > 2021-10-30T12:30:36.649515-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d353) [0xb7c55353] > 2021-10-30T12:30:36.649523-05:00 william named[16425]: > /usr/lib/i386-linux-gnu/libisc-9.17.19-
Bug#998450: libfilezilla: please make the library packages coinstallable
On Thu, 2021-11-04 at 13:07 +0100, Mattia Rizzolo wrote: > Source: libfilezilla > > Dear maintainer, > > I see that you keep regularly uploading new versions of this library and > each has a different SONAME, so that you keep renaming the binary > package. > > Now, that package contains both the library and some supporting files > (for i18n) that share a common path between different versions of the > library, forcing you to add Conflicts against the older version. > > That is kind of annoying to me, who is used to run `apt upgrade` which > doesn't remove packages. I've come in the past years to rely on just > that for most of my system upgrade needs, as dist-upgrade became less > and less needed, opposed to what used to be years ago. > > I see several ways so that libfilezilla could also allow for smooth > transitions between its versions*, so could you please consider one of > them? :) > Besides, I don't think it's a problem for this specific library since it > only has one user and you control it, but it would make the testing > migration potentially easier as well. > > > Thanks for considering! > > > * not limited to: > + move the i18n files into some soname-named path > + move the i18n files into a -common binary that is then used by > multiple versions of the library > + embed the data into the library itself > Hi Mattia, Thanks for filing this and I agree. I will create a -common for architecture independent files in the next release. Regards Phil -- *** Playing the game for the games own sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Bug#998622: glibc: CVE-2021-43396: Conversion from ISO-2022-JP-3 with iconv may emit spurious NUL character on state reset
Source: glibc Version: 2.31-10 Severity: important Tags: security upstream Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=28524 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for glibc. CVE-2021-43396[0]: | In iconvdata/iso-2022-jp-3.c in the GNU C Library (aka glibc) 2.34, | remote attackers can force iconv() to emit a spurious '\0' character | via crafted ISO-2022-JP-3 data that is accompanied by an internal | state reset. This may affect data integrity in certain iconv() use | cases. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-43396 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43396 [1] https://sourceware.org/bugzilla/show_bug.cgi?id=28524 Regards, Salvatore
Bug#997126: [Debian-med-packaging] Bug#997126: nipype test issue reported upstream
Hi Étienne On Fri, 5 Nov 2021 at 00:03, Étienne Mollier wrote: > From Andreas Tille's discussion with upstream, this might be > caused by numpy or scipy, possibly Debian specific. This sounds a lot like #994457 which was due to a change in lapack 3.10. Regards Graham
Bug#995450: buster->bullseye: octave segfaulting during configure (seems unrelated to #992405)
Il 04/11/2021 12:27, Sébastien Villemot ha scritto: I happen to have access to a machine with exactly the same CPU (and Debian Bullseye). I fail to replicate your problem there. I can start octave with libopenblas0-pthread and there is no segfault. So there must be another factor at play.Uhm... I use pam-limits and cgroups to limit the memory available to users. I just did another test and it seems to confirm this hypothesis: -8<-- root@str957-cluster:/var/log# ulimit -a real-time non-blocking time (microseconds, -R) unlimited core file size (blocks, -c) unlimited data seg size (kbytes, -d) 1024000 scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63754 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 63754 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited root@str957-cluster:/var/log# ulimit -d unlimited root@str957-cluster:/var/log# ulimit -a real-time non-blocking time (microseconds, -R) unlimited core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63754 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 63754 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited root@str957-cluster:/var/log# apt install libopenblas0^Cthread root@str957-cluster:/var/log# export LANG=C root@str957-cluster:/var/log# octave-cli X11 connection rejected because of wrong authentication. GNU Octave, version 6.2.0 Copyright (C) 2021 The Octave Project Developers. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. For details, type 'warranty'. Octave was configured for "x86_64-pc-linux-gnu". Additional information about Octave is available at https://www.octave.org. Please contribute if you find this software useful. For more information, visit https://www.octave.org/get-involved.html Read https://www.octave.org/bugs.html to learn how to submit bug reports. For information about changes from previous versions, type 'news'. octave:1> version -blas ans = OpenBLAS (config: OpenBLAS 0.3.13 NO_LAPACKE DYNAMIC_ARCH NO_AFFINITY Sandybridge SINGLE_THREADED) octave:2> root@str957-cluster:/var/log# apt install libopenblas0-pthread Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libopenblas0-pthread 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6034 kB of archives. After this operation, 43.8 MB of additional disk space will be used. Selecting previously unselected package libopenblas0-pthread:amd64. (Reading database ... 295123 files and directories currently installed.) Preparing to unpack .../libopenblas0-pthread_0.3.13+ds-3_amd64.deb ... Unpacking libopenblas0-pthread:amd64 (0.3.13+ds-3) ... Setting up libopenblas0-pthread:amd64 (0.3.13+ds-3) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/openblas-pthread/libblas.so.3 to provide /usr/lib/x86_64-linux-gnu/libblas.so.3 (libblas.so.3-x86_64-linux-gnu) in auto mode update-alternatives: using /usr/lib/x86_64-linux-gnu/openblas-pthread/liblapack.so.3 to provide /usr/lib/x86_64-linux-gnu/liblapack.so.3 (liblapack.so.3-x86_64-linux-gnu) in auto mode update-alternatives: using /usr/lib/x86_64-linux-gnu/openblas-pthread/libopenblas.so.0 to provide /usr/lib/x86_64-linux-gnu/libopenblas.so.0 (libopenblas.so.0-x86_64-linux-gnu) in auto mode Processing triggers for libc-bin (2.31-13+deb11u2) ... root@str957-cluster:/var/log# octave-cli X11 connection rejected because of wrong authentication. GNU Octave, version 6.2.0 Copyright (C) 2021 The Octave Project Developers. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. For details, type 'warranty'. Octave was configured for "x86_64-pc-linux-gnu".
Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
On 2021/11/05 05:55, Florian Schlichting wrote: > However, Max: behind this hides another problem, which is why I asked > Ryan to delete the pid_file configuration: as part of 0.23.3 you added > the "RuntimeDirectory=mpd" directive to both mpd.service units. In the > absence of User and Group directives, this causes /run/mpd to change > ownership from mpd:audio (as created by our > /usr/lib/tmpfiles.d/mpd.conf) to root:root, which means that mpd would > have to be run as root in order to be able to create a socket or a > pidfile (yes, legacy) there. I think that's broken from an upstream > perspective as well, and only works when running mpd as user. True, and the real fix would be to finally cease launching MPD as root, which is an anachronism. > I suppose the best way forward is to specify User=mpd and Group=audio > in the system unit, however this immediately hits a snag when mpd tries > to open its log file /var/log/mpd/mpd.log, which up to now is created as > root. This we could probably work around in Debian, and defaulting to > log to syslog/journal also feels sensible, but I'm not sure if there may > be other things that mpd might want to be root for when starting up as a > system service? The right way to have a writable /var/log/mpd is "LogsDirectory=mpd", but I don't want to do that. Per-daemon log files are an anachronism, too. Just like starting daemons as root, PID files, per-daemon daemonization code and so on ... all the good stuff that systemd can do for us, stuff which in ancient times every daemon had unnecessary duplicate code for. Another thing that MPD could fail if we don't launch MPD as root is binding to "privileged ports" (another anachronism). For example, a httpd streaming output could be bound to a low port. People who do that could add a drop-in with "AmbientCapabilities=CAP_NET_BIND_SERVICE" to give MPD permission for that.
Bug#998109: python3-numpy: numpy.typing is missing
On Wed, Nov 3, 2021 at 7:16 PM Drew Parsons wrote: > > On 2021-11-02 17:40, Sandro Tosi wrote: > > > > sorry but that's not how RC severity works, that's for policy > > violations, which in this case there are none. > > > > I understand you may want to see this fixed sooner rather than later, > > so maybe you can submit an MR against the numpy salsa repo to fix > > this? i'll then review, merge and upload as needed. > > > It's a trivial patch, isn't it? > Just add >usr/lib/python3*/*-packages/numpy/typing/ > to debian/python3-numpy.install. i've uploaded this to experimental > The bigger question here is why are the subdirs listed separately? > Is it in order to handle the dbg libraries (python3-numpy-dbg.install) ? > Since python3-dbg is now deprecated (Bug#994316), do we want to simplify > the package by replacing all the subdirs in python3-numpy.install with > just >usr/lib/python3*/*-packages/numpy/ > > That would keep this bug from happening again with other new features in > the future. that's a fair point, and i cant recall why it's setup that way. I'll keep a note to review when we're ready to drop the -dbg package (there are still a handful of rdeps) Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#887834: [Pkg-mpd-maintainers] Bug#887834: Bug#887834: mpd installation fails, cannot open /var/lib/mpd/tag_cache, /run/mpd/pid
Hi Ryan (and Max please see below):
> and have the following minimal mpd.conf:
>
> --
> music_directory "/var/lib/mpd/music"
> db_file "/var/lib/mpd/tag_cache"
> pid_file "/run/mpd/pid"
> state_file"/var/lib/mpd/state"
> log_level "verbose"
>
> user "mpd"
> bind_to_address "127.0.0.1"
>
> audio_output {
> type "null"
> name "null"
> }
> --
please, for now, delete or comment out the pid_file line
> Attempting to start mpd results in:
>
> --
> rak@zeta:~$ sudo service mpd start
> Job for mpd.service failed because a fatal signal was delivered to the
> control process.
> See "systemctl status mpd.service" and "journalctl -xeu mpd.service" for
> details.
> rak@zeta:~$ sudo systemctl status mpd.service
> × mpd.service - Music Player Daemon
> Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled; vendor
> preset: enabled)
> Active: failed (Result: signal) since Thu 2021-11-04 13:49:36 EDT; 2s ago
> TriggeredBy: × mpd.socket
>Docs: man:mpd(1)
> man:mpd.conf(5)
> file:///usr/share/doc/mpd/html/user.html
> Process: 474546 ExecStart=/usr/bin/mpd --no-daemon $MPDCONF (code=killed,
> signal=ABRT)
>Main PID: 474546 (code=killed, signal=ABRT)
> CPU: 175ms
>
> Nov 04 13:49:36 zeta mpd[474546]: sndfile: libsndfile-1.0.31
> Nov 04 13:49:36 zeta mpd[474546]: hybrid_dsd: The Hybrid DSD decoder is
> disabled because it was not explicitly enabled
> Nov 04 13:49:36 zeta mpd[474546]: adplug: adplug 2.3.3
> Nov 04 13:49:36 zeta mpd[474546]: exception: Failed to open
> '/var/lib/mpd/tag_cache': No such file or directory
> Nov 04 13:49:36 zeta mpd[474546]: curl: version 7.74.0
> Nov 04 13:49:36 zeta mpd[474546]: curl: with GnuTLS/3.7.2
> Nov 04 13:49:36 zeta mpd[474546]: mpd: ../src/event/Loop.cxx:60:
> EventLoop::~EventLoop(): Assertion `sockets.empty()' failed.
> Nov 04 13:49:36 zeta systemd[1]: mpd.service: Main process exited,
> code=killed, status=6/ABRT
> Nov 04 13:49:36 zeta systemd[1]: mpd.service: Failed with result 'signal'.
> Nov 04 13:49:36 zeta systemd[1]: Failed to start Music Player Daemon.
The tag_cache exception is non-fatal. The problem here is the Assertion
failure, which is #998310 and fixed in mpd 0.23.3-2
However, Max: behind this hides another problem, which is why I asked
Ryan to delete the pid_file configuration: as part of 0.23.3 you added
the "RuntimeDirectory=mpd" directive to both mpd.service units. In the
absence of User and Group directives, this causes /run/mpd to change
ownership from mpd:audio (as created by our
/usr/lib/tmpfiles.d/mpd.conf) to root:root, which means that mpd would
have to be run as root in order to be able to create a socket or a
pidfile (yes, legacy) there. I think that's broken from an upstream
perspective as well, and only works when running mpd as user.
I suppose the best way forward is to specify User=mpd and Group=audio
in the system unit, however this immediately hits a snag when mpd tries
to open its log file /var/log/mpd/mpd.log, which up to now is created as
root. This we could probably work around in Debian, and defaulting to
log to syslog/journal also feels sensible, but I'm not sure if there may
be other things that mpd might want to be root for when starting up as a
system service?
Florian
Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones
Hello, Igor Kovalenko solution work for me only if libspa-0.2-bluetooth package is installed. The solution is described in https://wiki.debian.org/PipeWire#Bluetooth 1) Only pulseaudio-module-bluetooth is installed; it is impossible to pair. 2) Both pulseaudio-module-bluetooth and libspa-0.2-bluetooth are installed; pairing is flaky but not impossible. (Few failed attempts before success.) 3) Only libspa-0.2-bluetooth is installed, pairing is reliable. (It failed the first time after pulseaudio-module-bluetooth was removed.) Failure always end in src/service.c:btd_service_connect() a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX: Protocol not available message. Best regards, Sincerely, Viktor Malyarchuk
Bug#954159: pavucontrol: allow multiple instances
Package: pavucontrol Version: 4.0-2 Followup-For: Bug #954159 Upstream bug here: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/issues/75 Attracting the usual level of developer interest for a freedesktop project. This seems to be the patch that introduced the broken behaviour: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/commit/f6ce4fb8db51489f6ab1210593695f465ccb83a0 Behaviour looks pretty entrenched - don't know how hard it would be to put it all under a commandline switch. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (5, 'testing'), (2, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 pavucontrol depends on: ii libatkmm-1.6-1v5 2.28.0-3 ii libc62.31-13+deb11u2 ii libcanberra-gtk3-0 0.30-7 ii libcanberra0 0.30-7 ii libgcc-s110.2.1-6 ii libglib2.0-0 2.66.8-1 ii libglibmm-2.4-1v52.64.2-2 ii libgtk-3-0 3.24.24-4 ii libgtkmm-3.0-1v5 3.24.2-2 ii libpulse-mainloop-glib0 14.2-2 ii libpulse014.2-2 ii libsigc++-2.0-0v52.10.4-2 ii libstdc++6 10.2.1-6 Versions of packages pavucontrol recommends: ii pulseaudio 14.2-2 pavucontrol suggests no packages. -- no debconf information
Bug#998621: RM: python-dexml -- RoQA; Orphaned; RC-Buggy; Dead upstream; Useless
Package: ftp.debian.org Severity: normal Hi, I request to remove package python-dexml (as shown on https://tracker.debian.org/pkg/python-dexml ) from Sid. This package * Shows no upstream activity since 2012, and upstream abandoned the project in 2018 (see https://github.com/rfk/dexml ) * Orphaned * No reverse dependencies * No reverse build-dependencies * RC Buggy ( https://bugs.debian.org/997620 , no easy fix) * Very low popcon (7) I believe these factors make the package eligible for removal. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#998090: libvirt-daemon-system: Please defer starting libvirtd.socket until libvirtd.service dependencies can be met
Hi Guido, On Wed, Nov 03, 2021 at 07:15:37PM +0100, Guido Günther wrote: > Hi Ron, > > Sorry for the broken boot. That's always annoying. Thanks for looking at the details. I filed these bugs because even though I can step around the problem in the permutation that involves something I maintain - if we don't fill in *all* of the contributing potholes, then I can't prevent some other combination which I have no control over making a reboot after some future upgrade crash on the same sharp corner case. So it really would be nice if we can make this as naturally robust as possible. That we have "three corner" accidents like this, where the problem would not have occurred if any one of the contributors did not have some window for trouble, and that nobody detected and reported this through the stable release cycle, says to me that we ought to close every window for this that we see when we see it ... > On Sat, Oct 30, 2021 at 05:39:45PM +1030, Ron wrote: > > The race occurs because the .socket unit creates the libvirt control > > socket very early in the boot, before even the network-pre target is > > reached, and so long before the libvirtd.service dependencies are > > satisfied and the daemon itself can be started to handle requests. > > > > The deadlock in my case occurs when a udev rule for a device already > > attached at boot tries to assign that device to a VM. > > > > Prior to Bullseye, what would occur is: > > > > The udev rule calls a small script on device hot/cold plug which > > checks a config file, and if the device is allocated to a VM, then > > calls virsh to attach it to that VM. > > Is that a sync call to virsh from udev via RUN ? It's a call to virsh attach-device - which unless I'm missing something has no option except to be a "sync" call? But also unless I'm really missing something, there really is no reason that particular operation should ever block or be "long running" when called for a local domain. Either it fails out immediately because the local libvird is not running (prior to socket activation), it fails out immediately because the requested domain is not running, or it succeeds or fails "almost immediately" because the device could (not) be attached to it. I agree there are cases where virsh *could* be "long running" (I wouldn't try to spin up a new VM from udev RUN :), and pathological cases where *any* process, even the most trivial, could become "long running" - but neither of those are involved in the failure mode I'm currently looking at avoiding. > > This 'immediately' either succeeds, fails because the desired VM > > is not actually running (yet), or fails because libvirtd is not > > running and virsh did not find its socket present. > > > > If either of the failure cases occur, the calling script fails > > gracefully, and a QEMU hook will later handle attaching the device > > if/when libvirtd and the desired VM is actually started. > > > > But in Bullseye there's a three-way race, and if the zombie socket is > > created before the udev rule runs, then virsh connects to it, but hangs > > indefinitely waiting for libvirtd.service to be able to start and > > respond to the request. > > So far sounds like expected behaviour for socket activation. Yes, I think that's the crux here. I understand the wishful thinking in the design of socket activation, where you just fire the starting gun early and let everything race for the finish line with no explicit ordering, hoping that it will just shake out as an emergent property ... But that only works if none of the dependency relationships are cyclic, as soon as there's a cycle (which is what we have here), the emergent property is you can't predict what it will break ... and the only tie-breaker is to time-out and kill something. In the case I got to analyse here, the problem doesn't depend on the bit-babbler package, or even anything being called by udev RUN. Any early-start service, with an ordering dependency that requires it first started before any of libvirtd.service's After list, which calls virsh for any reason would also fall into the same trap. So the problem in libvirt's circle of influence isn't "a long running service" spawned by udev, it's that it's now not safe for *anything* to call virsh without an explicit dependency somehow declaring it must not be required to complete before libvirtd.service is successfully started ... Otherwise libvirtd will never start, and virsh will never return. Which might seem like a trivial problem to avoid, but as we see here, it's quite easy to create it accidentally in the tangle of multiple independent requirements created by multiple independent authors. And I assume this would be true for even the most seemingly benign uses of virsh (like version --daemon or sysinfo et al.) - there's certainly many things being called by RUN rules which I'd expect as more probable to become "long running" than virsh version ... I'm not clinging tight to
Bug#998485: gjiten: FTBFS: configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times
Hi, maybe it's a good chance to change to the new updated version of gjiten at https://github.com/DarkTrick/gjiten The new version might also encounter packaging problems, but it uses more recent technology and updates; It's probably more worthful to spend time there than in the 10 year old package* Regards Chris - DarkTrick * Yes, I'm trying to promote my updates here :) On 2021/11/05 2:38, Lucas Nussbaum wrote: Source: gjiten Version: 2.6-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 dh_update_autotools_config dh_autoreconf autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in' aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:8: error: AM_INIT_AUTOMAKE expanded multiple times /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.in:7: the top level /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.in:8: the top level autom4te: error: /usr/bin/m4 failed with exit status: 1 aclocal: error: /usr/bin/autom4te failed with exit status: 1 autoreconf: error: aclocal failed with exit status: 1 dh_autoreconf: error: autoreconf -f -i returned exit code 1 make: *** [debian/rules:4: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gjiten_2.6-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#997482: sublime-music: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Upstream version 0.11.14 seems to fix this issue, but the patch seems to create a new bug: https://gitlab.com/sublime-music/sublime-music/-/issues/325 Currently waiting for feedback from upstream. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#998618: bind9.17.19: crashes with INSIST assertion fail resp->disp->active.tail or .head == or != resp
Package: bind9 Version: 1:9.17.19-1 Severity: important Dear Maintainer, Named began crashing several times a day after updating from bind 9.16.21-1 to 9.17.19-1 on Oct 30. Wanted to report this before dropping back to 9.16.21. Some examples of the logs during a crash: 2021-11-03T17:40:27.402030-05:00 william named[11429]: dispatch.c:1524: INSIST((resp->disp->active).tail == (resp)) failed, back trace 2021-11-03T17:40:27.402343-05:00 william named[11429]: /usr/sbin/named(+0x1a8eb) [0x44c8eb] 2021-11-03T17:40:27.402354-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc_assertion_failed+0x25) [0xb7c49775] 2021-11-03T17:40:27.402362-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(dns_dispatch_cancel+0x2cc) [0xb79ec93c] 2021-11-03T17:40:27.402373-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x110d98) [0xb7ab7d98] 2021-11-03T17:40:27.402381-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x1170a3) [0xb7abe0a3] 2021-11-03T17:40:27.402389-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x45d15) [0xb79ecd15] 2021-11-03T17:40:27.402397-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__nm_async_connectcb+0xa2) [0xb7c36722] 2021-11-03T17:40:27.402404-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1cb96) [0xb7c37b96] 2021-11-03T17:40:27.402411-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d2cc) [0xb7c382cc] 2021-11-03T17:40:27.402420-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1db28) [0xb7c38b28] 2021-11-03T17:40:27.402427-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libuv.so.1(+0xd0aa) [0xb75cc0aa] 2021-11-03T17:40:27.402435-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libuv.so.1(+0x2239e) [0xb75e139e] 2021-11-03T17:40:27.402443-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libuv.so.1(uv_run+0x10e) [0xb75cca6e] 2021-11-03T17:40:27.402451-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d353) [0xb7c38353] 2021-11-03T17:40:27.402458-05:00 william named[11429]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__trampoline_run+0x22) [0xb7c7db22] 2021-11-03T17:40:27.402466-05:00 william named[11429]: /lib/i386-linux-gnu/libpthread.so.0(+0x80af) [0xb73730af] 2021-11-03T17:40:27.402473-05:00 william named[11429]: /lib/i386-linux-gnu/libc.so.6(clone+0x66) [0xb72828f6] 2021-11-03T17:40:27.402481-05:00 william named[11429]: exiting (due to assertion failure) 2021-10-30T12:30:36.648373-05:00 william named[16425]: dispatch.c:1524: INSIST((resp->disp->active).head == (resp)) failed, back trace 2021-10-30T12:30:36.648815-05:00 william named[16425]: /usr/sbin/named(+0x1a8eb) [0x4da8eb] 2021-10-30T12:30:36.648897-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc_assertion_failed+0x25) [0xb7c66775] 2021-10-30T12:30:36.648963-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(dns_dispatch_cancel+0x2cc) [0xb7a0993c] 2021-10-30T12:30:36.649025-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x110d98) [0xb7ad4d98] 2021-10-30T12:30:36.649094-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x1170a3) [0xb7adb0a3] 2021-10-30T12:30:36.649157-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libdns-9.17.19-1-Debian.so(+0x45d15) [0xb7a09d15] 2021-10-30T12:30:36.649234-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__nm_async_connectcb+0xa2) [0xb7c53722] 2021-10-30T12:30:36.649298-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1cb96) [0xb7c54b96] 2021-10-30T12:30:36.649371-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d2cc) [0xb7c552cc] 2021-10-30T12:30:36.649410-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1db28) [0xb7c55b28] 2021-10-30T12:30:36.649444-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libuv.so.1(+0xd0aa) [0xb75e90aa] 2021-10-30T12:30:36.649477-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libuv.so.1(+0x2239e) [0xb75fe39e] 2021-10-30T12:30:36.649507-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libuv.so.1(uv_run+0x10e) [0xb75e9a6e] 2021-10-30T12:30:36.649515-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(+0x1d353) [0xb7c55353] 2021-10-30T12:30:36.649523-05:00 william named[16425]: /usr/lib/i386-linux-gnu/libisc-9.17.19-1-Debian.so(isc__trampoline_run+0x22) [0xb7c9ab22] 2021-10-30T12:30:36.649531-05:00 william named[16425]: /lib/i386-linux-gnu/libpthread.so.0(+0x80af) [0xb73900af] 2021-10-30T12:30:36.649538-05:00 william named[16425]: /lib/i386-linux-gnu/libc.so.6(clone+0x66) [0xb729f8f6] 2021-10-30T12:30:36.6
Bug#996726: Some other questions
> After 2 weeks, the bug has finally been fixed. But I wonder why the bug > wasn't tested out in the unstable branch and was pushed into the testing Because on unstable everything worked. The bug happens only due to different transition times from unstable to testing. This cannot be tested in unstable before. Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#996726: Some other questions
After 2 weeks, the bug has finally been fixed. But I wonder why the bug wasn't tested out in the unstable branch and was pushed into the testing branch.
Bug#998456: duplicity: b-d on python3-all-dev, but not built for all supported Python3 versions
On Thu, 04 Nov 2021 16:39:09 +0200, Graham Inggs writes: >Please either replace the b-d python3-all-dev with python3-dev, python policy 7.1: "The python3-all-dev should be used when building extensions for any or all Python 3 versions" >or build for all supported Python3 versions. what undocumented magic do you expect me to bake for doing this? the package already uses dh $@ --with python3 --buildsystem=pybuild what more do you want? -- Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/ My name is sendmail.cf. You killed my process. Prepare to vi. signature.asc Description: Digital Signature
Bug#998581: git-imerge: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
On Thu, 2021-11-04 at 20:45 +0100, Lucas Nussbaum wrote: > Source: git-imerge ... > > ERROR: Could not install packages due to an EnvironmentError: > > [Errno 13] Permission denied: '/usr/lib/python3.9/dist-packages' This is apparently caused by a change in dh-python that will be reverted. For now please don't file any more bugs about this. https://salsa.debian.org/python-team/tools/dh-python/-/commit/169bc6ba400d27cfc143dc7f9f6f4b5db471def1 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#885433: wiki.debian.org: Access to wiki.debian.org is blocked with 403 Forbidden
Hi there, our IP is also blocked by the wiki. Can you add an exception for us? 50.251.200.225 Please and thank you! Jack
Bug#966400: sublime-music: fails to create new server
Hi, Thanks for reporting this bug and adding more info. It seems this was reproduced in bug #997482 and I can reproduce it locally when running the testsuite. I still have to upload the latest upstream version of sublime-music. I'm hoping it will fix the problem? Otherwise, I'll try to debug this further. No promises on an ETA though, I'm quite busy :( -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#998040: RFS: makedeb-makepkg/8.11.0 [ITP] -- Arch Linux build utility, modified for use with makedeb
Control: tags -1 moreinfo makedeb-makepkg's version has to have a Debian revision -1. Please keep only the latest packaged version in the changelog with a line closing the ITP. When you are done and have uploaded a version with fixed changelog please untag moreinfo.
debian-bugs-dist@lists.debian.org
Control: tags -1 moreinfo Please untag moreinfo when you have provided a fixed upload.
Bug#990821: aptly fails to run if both gnupg2 and gnupg1 are installed
Package: aptly Version: 1.4.0+ds1-6 Followup-For: Bug #990821 Hi all, conflicting with gpgv1 is *not* the correct solution. The correct solution is to fix aptly, not conflicting with other programs that are reasonably important. gpg v1 is still necessary for the creation of old style keyrings when creating distributions of verification keys. I use both aptly and gpgv1 and this is very painful to see. I suggest reopening this bug and working on a proper bug fix. Thanks Norbert -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.16+futex+ntfs3+zstd+intel+ (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptly depends on: ii bzip2 1.0.8-4 ii gnupg 2.2.27-2 ii gpgv 2.2.27-2 ii libc6 2.32-4 ii xz-utils 5.2.5-2 aptly recommends no packages. Versions of packages aptly suggests: ii graphviz 2.42.2-5+b1 -- no debconf information
Bug#998617: lebiniou: missing d/copyright info
Source: lebiniou Version: 3.62.1-3 Severity: important The d/copyright files misses some copyright info, e.g.: Copyright 2019-2021 Laurent Marsac Copyright 2021 Jérémie Astor Copyright 2014-2021 Frantz Balinski Copyright 2019-2021 Tavasti Copyright (C) 2001-2002 FUKUCHI Kentaro Copyright (C) Free Software Foundation, Inc. Also, plugins/main/swarm/swarm.c has an MIT-like license that is missing with: Copyright (c) 1996 by Tim Auckland Incorporating some code from Stephen Davies Copyright (c) 2000 ... 18-Jul-1996: Adapted from swarm.c Copyright (c) 1991 by Patrick J. Naughton. The license that is named MIT seems to be Expat (MIT is not very specific).
Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
> bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be installed It looks like bind8 no longer builds the bind9-dev package. It's still present in unstable as a cruft package but is uninstallable due to version constraints, it's completely gone from testing. Bind maintainers: was this a deliberate change? (I can't seem to find any mention of it in the changelog) and if so what should reverse-dependencies do?
Bug#998616: epson2: "setting focus failed" error on 1640SU after libsane1 upgrade
Package: libsane1 Version: 1.0.32-4 Severity: grave Justification: renders package unusable Dear Maintainer, I've upgraded libsane1 package from 1.0.31-4.1 to 1.0.32-4 and my Epson Perfection 164SU stopped working. I tried to debug the issue with: ~$ SANE_DEBUG_EPSON2=255 scanimage --device=epson2:libusb:006:011 --format=jpeg --output-file=./test.jpg and I discoverd this error: ... [00:15:42.111491] [epson2] setting focus failed scanimage: sane_start: Operation not supported ... I think that this error is related to this changelog of "SANE Backends 1.0.32": epson2: adds autofocus support for devices that support it (!531) Info: https://gitlab.com/sane-project/backends/-/merge_requests/531 https://gitlab.com/sane-project/backends/-/merge_requests/531/diffs Downgrading to libsane1 1.0.31-4.1 solve the issue. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (850, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsane1 depends on: ii acl2.3.1-1 ii adduser3.118 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libc6 2.32-4 ii libcairo2 1.16.0-5 ii libcurl3-gnutls7.74.0-1.3+b1 ii libgcc-s1 11.2.0-10 ii libglib2.0-0 2.70.0-3 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port12 2.5.27-1 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.0.6-4 ii libpng16-161.6.37-3 ii libpoppler-glib8 20.09.0-3.1 ii libsane-common 1.0.32-4 ii libsnmp40 5.9.1+dfsg-1 ii libstdc++6 11.2.0-10 ii libtiff5 4.3.0-2 ii libusb-1.0-0 2:1.0.24-3 ii libxml22.9.12+dfsg-5 ii udev 249.5-1 Versions of packages libsane1 recommends: ii ipp-usb 0.9.19-2 ii sane-utils 1.0.32-4 Versions of packages libsane1 suggests: ii avahi-daemon 0.8-5 pn hplip -- no debconf information
Bug#985047:
Hi, maybe do you know a way to make a chainload from shim.efi ? Best Regards, Juri Grabowski
Bug#986108: RFS: f3d/1.1.0-1 [ITP] -- fast and minimalist 3D viewer
Control: tags -1 moreinfo On 04.11.21 22:21, François Mazen wrote: Hello Bastian, Please consider relicensing debian/* or at least debian/patches/* I've relicensed to BSD-3, in order to match upstream license. Ken Martin, Will Schroeder, Bill Lorensen's copyright is missing. I guess you are referencing classic VTK's copyright. F3D's copyright is "Kitware, SAS" according to source code and official website, without any link to VTK's copyright. It is fine for them not to include it because these people obviously have the say over Kitware. Still, there are three source files that have their copyright and are BSD licensed. The license mandates including the copyright in any distribution, which is why Debian mandates it to be in the d/copyright file for the binary package to be compliant. I have added them to the git. src/cxxopts.hpp: Expat license is missing. Added to the copyright file, and I've opened an upstream bug: https://gitlab.kitware.com/f3d/f3d/-/issues/253 That is very kind of you. For the binaries that Kitware provides they are actually in breach of that license (given the file is actually compiled). Have you checked the files in the data directory? At least data/BoxAnimated0.bin is not a source file and some others might not be. Non-source files (defined as preferred format for modification) have to be excluded. Also, does the files' metadata say anythinng about copyright or license? d/f3d.1 === Please describe the options in the man page. Man page updated. You should prefer using the not-installed file for this use case. The not-installed file seems to avoid trigger dh_missing error, which is not what I need here. I haven't figured out how exclude files during the CMake install target (--exclude has no effect), so I've added an "rm" command in the rules file. If there is a better way, please suggest. I see you have already found another way... I suggest to have the package in Salsa's debian namespace so that others can contribute easily. If you agree I can create that and grant you maintainer rights for it. Yes! Please create the debian repository and grant me right to maintain it. Done. The CI test suite won't run because of the .lfsconfig file which is why I have disabled it.
Bug#998515: arpwatch generates malformed emails.
Control: tags -1 + moreinfo Hi Yanko, thanks for your report! Please help me to understand what's happening by providing the following information: * How exactly is arpwatch invoked? Please provide the output of `ps -U arpwatch -F` or (in case that doesn't show any processes) `ps -eF | grep arpwatch`. * The output of `dpkg -S /usr/lib/sendmail` so I know which Debian package is providing the /usr/lib/sendmail binary installed in your system. Thanks Lukas
Bug#989705: Suspend to RAM hangs computer with nouveau driver
Same problem. Also there was often freezing in Xfce, mostly when switching between windows, SysRc+r help unfreeze. Setting init_on_alloc=0 help with this (suspend and freezing). But now, if second monitor connected (VGA or HDMI), after login Xfce freeze. Maybe it's different issue, something about xfce or randr. uname -a Linux hp-deb 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux inxi -G Graphics: Device-1: NVIDIA G86M [GeForce 8400M GS] driver: nouveau v: kernel Device-2: Chicony VGA 30fps UVC Webcam type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1: 1280x800~60Hz 2: 1280x1024~60Hz OpenGL: renderer: NV86 v: 3.3 Mesa 20.3.5
Bug#998108: Tracking this bug down
Maybe I am wrong, but, for me, the simplest method to track this bug down is to check the changes between the two versions, 93.0 and 93.0-1+b1. Firefox code has not changed, only one or some libraries it depends on. I thought that the only change is in libvpx version, but, surprisingly, a previous comment mentions that rebuilding firefox with old vpx (libvpx6) still exhibits the bug. I think that libc6 is out of question, because the last package is 19 Sep, too old wrt this bug; the same for gcc-11, the last package being on 21 Oct. Doesn't this (checking the changes) sound like a good approach to find the cause of the problem?
Bug#986108: RFS: f3d/1.1.0-1 [ITP] -- fast and minimalist 3D viewer
Hello Bastian, > Please consider relicensing debian/* or at least debian/patches/* I've relicensed to BSD-3, in order to match upstream license. > Ken Martin, Will Schroeder, Bill Lorensen's copyright is missing. I guess you are referencing classic VTK's copyright. F3D's copyright is "Kitware, SAS" according to source code and official website, without any link to VTK's copyright. > src/cxxopts.hpp: Expat license is missing. Added to the copyright file, and I've opened an upstream bug: https://gitlab.kitware.com/f3d/f3d/-/issues/253 > d/f3d.1 > === > Please describe the options in the man page. Man page updated. > You should prefer using the not-installed file for this use case. The not-installed file seems to avoid trigger dh_missing error, which is not what I need here. I haven't figured out how exclude files during the CMake install target (--exclude has no effect), so I've added an "rm" command in the rules file. If there is a better way, please suggest. > I suggest to have the package in Salsa's debian namespace so that > others > can contribute easily. If you agree I can create that and grant you > maintainer rights for it. Yes! Please create the debian repository and grant me right to maintain it. Thanks a lot for this review, the new package is available on mentors. Best, François signature.asc Description: This is a digitally signed message part
Bug#998108: Additional information: tab freezes first, then browser
Maybe i missed a comment but can someone give a try with the upstream binary? To see if it happens for you too there? Merci Sylvestre Le jeu. 4 nov. 2021 à 23:15, Josh Triplett a écrit : > Some additional information that might help track this down: several > times, I've observed one tab freezing, but the browser itself is still > responsive for a *short* time. I can open a new tab, and close it again, > and the previous tab then renders as a busy symbol. > > I'm wondering if one of the tab processes or helper processes dies, and > then that grinds the browser to a halt but not instantly. > >
Bug#996204: Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
I have fixed gmsh. It will appear in NEW soon. Regards Anton
Bug#998108: Additional information: tab freezes first, then browser
Some additional information that might help track this down: several times, I've observed one tab freezing, but the browser itself is still responsive for a *short* time. I can open a new tab, and close it again, and the previous tab then renders as a busy symbol. I'm wondering if one of the tab processes or helper processes dies, and then that grinds the browser to a halt but not instantly.
Bug#934297: RFS: bibtexconv
Control: tags -1 moreinfo On Thu, 02 Jan 2020 12:18:40 +0100 Tobias Frost wrote: - Can you please merge the d/changelog entries for (in Debian) unreleased versions? - The Debian changelog seems incomplete, I see (packaing) changes which are not documented. Please also try to expand a bit on the changes, e.g did the SV update require you add changes? (documenting "why has this changed" is important as additional information to the "what") These were fixed. - You do not need to specify the standards versions 4th digit, this digit is for editorial changes only. So it is sufficient to declare compatiblitliy with e.g 4.4.1 (which has been released since you put this package to mentors) - d/test/control is a empty file. I don't think that is right. nitpicks: d/compat can be obsoleted. ( https://nthykier.wordpress.com/2019/01/04/debhelper-compat-12-is-now-released/ ) Please correct these. - Where do you get the OpenSSL exception from? I know you are the upstream but this exception should be present in the source as well or should be removed from d/copyright. Debian does not require it any longer. - Please change the version and the origtarxz to actually match the released version/file. No ~test0 - Add "(Closes: #975076)" to d/changelog's "New upstream release." line. With these changes I am going to sponsor the package. Please untag moreinfo when you are done.
Bug#998615: RFS: fonts-jetbrains-mono/2.242+ds-2 -- free and open-source typeface for developers
Package: sponsorship-requests Severity: normal X-Debbugs-Cc:debian-fo...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "fonts-jetbrains-mono": * Package name: fonts-jetbrains-mono Version : 2.242+ds-2 Upstream Author : Phillip Nurullin * URL :https://www.jetbrains.com/lp/mono/ * License : Apache-2 * Vcs :https://salsa.debian.org/fonts-team/fonts-jetbrains-mono Section : fonts It builds those binary packages: fonts-jetbrains-mono - free and open-source typeface for developers To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fonts-jetbrains-mono/ Alternatively, one can download the package with dget using this command: dget -xhttps://mentors.debian.net/debian/pool/main/f/fonts-jetbrains-mono/fonts-jetbrains-mono_2.242+ds-2.dsc Changes since the last upload: fonts-jetbrains-mono (2.242+ds-2) unstable; urgency=medium . * d/control: update Standards version to 4.6.0.1 (no changes needed) * Use upstream build script instead of custom Makefile Regards, -- Romain Porte
Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
On 2021-11-04 21:41, Sebastian Ramacher wrote: On 2021-11-03 22:33:01 +0100, Drew Parsons wrote: ... The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to solve is that hypre is ABI-ignorant (https://github.com/hypre-space/hypre/issues/56), so each point patch release would have to be a new binary package, and the upstream release rate is faster than the average NEW queue processing rate (the new package for the current transition would be libhypre2.22.1, and already libhypre2.23.0 is released upstream). (So why is this packaged as shared library?) A reasonable question to ask. For my part, it was already being packaged as a shared library when I started working on it, so I just continued it so. I could imagine a clash of hypre symbols if a client programs links against both petsc and sundials (which both use hypre), and uses hypre directly. I guess the symbol table must guard against clashes like that. ... Is it best to revert back to strict Policy 8.1 compliance, which will slow down hypre patch release updates? Yes. Having to wait for binNEW to being processed is not an excuse to violate a must section of the policy. Processing of packages in NEW can take some time. I'm also waiting on some of them for months. The solution to that is however not to abondon well established practices for shared libraries. The problems that are caused by that can be seen with libhypre and its reverse dependencies. Fair enough. I'll make the change, either to libhypre2.22.2 or to libhypre-static. Drew
Bug#998067: transition: libsepol and libsemanage
Control: tags -1 moreinfo On 2021-10-29 13:44:16 +0200, Laurent Bigonville wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hello, > > libsepol and libsemanage have both bumped their soname from 1 to 2, the > packages already went through the NEW queue and are in experimental. > > The transition trackers are already created: > > https://release.debian.org/transitions/html/auto-libsepol.html > https://release.debian.org/transitions/html/auto-libsemanage.html > > Most of the packages are from the same upstream. > > For libsemanage, sssd and shadow will have to adjust their build-dependencies Have bugs been filed for that? Cheers > > For libsepol, dmraid must remove the build-dependency, this is useless, > see #929484. Note that dmraid already has a RC bug, for other reasons. > > Kind regards, > Laurent Bigonville > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#998605: krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error
Hi, On Thu, Nov 04, 2021 at 08:49:47PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: > > syntax error It looks like a result of recent pyqt5 update — it broke compatibility with SIP 4. This issue was discussed on PyQt mailing list yesterday [1], but the upstream developer said he is not going to rush to fix this. I don't know what this means, but if there is a fix at least in upstream Vcs or snapshots, I will cherry-pick it. [1]: https://www.riverbankcomputing.com/pipermail/pyqt/2021-November/044346.html -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#998101: recent upgrade
apt policy gnome-shell gnome-core thunderbird-l10n-fr firefox gnome-shell: Installé : 41.0-2 Candidat : 41.0-2 Table de version : *** 41.0-2 500 100 https://deb.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 3.38.6-1~deb11u1 100 100 http://deb.debian.org/debian stable/main amd64 Packages gnome-core: Installé : 1:40+1 Candidat : 1:40+1 Table de version : *** 1:40+1 500 100 https://deb.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38+3 100 100 http://deb.debian.org/debian stable/main amd64 Packages thunderbird-l10n-fr: Installé : 1:91.3.0-1 Candidat : 1:91.3.0-1 Table de version : *** 1:91.3.0-1 500 500 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 1:91.2.1-1 500 500 https://deb.debian.org/debian unstable/main i386 Packages 1:78.14.0-1 100 100 https://deb.debian.org/debian testing/main amd64 Packages 100 https://deb.debian.org/debian testing/main i386 Packages 1:78.14.0-1~deb11u1 100 100 http://deb.debian.org/debian stable/main amd64 Packages 100 http://deb.debian.org/debian stable/main i386 Packages firefox: Installé : 94.0-1 Candidat : 94.0-1 Table de version : *** 94.0-1 500 500 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 92.0-2+b1 1 1 https://deb.debian.org/debian experimental/main amd64 Packages gnome does not seem to have been updated. on the other hand, thunderbird and firefox have been updated. I'm looking at it. Is it better?
Bug#998529: rust-cargo: FTBFS: unsatisfiable build-dependencies: librust-cargo-util-0.1+default-dev (>= 0.1.1-~~), librust-im-rc-15+default-dev
The packages that will fix this (rust-cargo-util and rust-im-rc) are in NEW.
Bug#998408: debian-installer: "good password" advise
On 11/3/21 21:12, Alejandro Colomar (man-pages) wrote: On 11/3/21 20:30, Alejandro Colomar wrote: So my advise would be instead: "A good password will not need rare characters, but rather be as long as possible. Having a memorable random password can help it be longer, and therefore stronger." Hmm, I'd reword this a bit, since that wording of mine makes it look like long memorable passwords are better than completely random ones, while they aren't. "A good password will not need rare characters, but rather be as long as possible. If you can use a password manager, a completely random alphanumeric password is the best. However, if you need to memorize it, it should be easy to memorize, relatively random, and very long." Maybe too long of an advise; maybe it could be made shorter... "A good password will not need special characters, but rather be as long as possible." Much better and simpler, IMO. 26^8 = 2.08 e+11 62^8 = 2.18 e+14 94^8 = 6.10 e+15 26^16 = 4.36 e+22 62^16 = 4.77 e+28 94^16 = 3.71 e+31 26^32 = 1.90 e+45 62^32 = 2.27 e+57 94^32 = 1.38 e+63 26^64 = 3.62 e+90 62^64 = 5.16 e+114 94^64 = 1.91 e+126 -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
Bug#998382: The patch has been accepted by upstream
Here is the (now closed) upstream ticket: https://github.com/jirka-h/haveged/issues/66 Here is the commit where the patch has been applied: https://github.com/jirka-h/haveged/commit/a4b69d65a8dfc5a9f52ff8505c7f58dcf8b9234f
Bug#998520: rust-bstr: FTBFS: unsatisfiable build-dependencies (purely virtual?): librust-memchr-2+std-dev (>= 2.4.0-~~), librust-memchr-2-dev (>= 2.4.0-~~)
The new version of rust-memchr which will fix this is in NEW.
Bug#804857: linux: New feature: enable CONFIG_NO_HZ_FULL and CONFIG_RCU_NOCB_CPU/CONFIG_RCU_NOCB_CPU_NONE
Am Sat, 30 Oct 2021 16:04:35 +0200
schrieb Salvatore Bonaccorso :
> Control: tags -1 + moreinfo
>
> On Wed, Oct 27, 2021 at 10:16:56AM +0200, Georg Müller wrote:
> > > But for other configurations it is worse:
> > >
> > > config NO_HZ_FULL
> > > bool "Full dynticks system (tickless)"
> > > ...
> > > This is implemented at the expense of some overhead in
> > > user <-> kernel transitions: syscalls, exceptions and interrupts.
> > > Even when it's dynamically off.
> > >
> > > Say N.
> > >
> >
> >
> > Upstream commit 176b8906 changed the description regarding
> > NO_HZ_FULL:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=176b8906c399a170886ea4bad5b24763c6713d61
> >
> >
> > > By default, without passing the nohz_full parameter, this behaves
> > > just like NO_HZ_IDLE.
> > >
> > > If you're a distro say Y.
>
> While this is changed, and distros encouraged to select it, selecting
> this would enable both CONFIG_VIRT_CPU_ACCOUNTING_GEN and
> CONFIG_RCU_NOCB_CPU.
>
> For CONFIG_VIRT_CPU_ACCOUNTING_GEN
>
> Select this option to enable task and CPU time accounting
> on full dynticks systems. This accounting is implemented by watching
> every kernel-user boundaries using the context tracking subsystem.
> The accounting is thus performed at the expense of some
> significant overhead.
>
> For now this is only useful if you are working on the full
> dynticks subsystem development.
>
> If unsure, say N.
>
> which indicates some significant overhead.
I can not answer that from the back of my head. Would have to dig as
well. Might get back in about two weeks if nobody else finds an answer.
But i took the liberty to include Frederic into Cc, the author of the
"distro reassure" patch.
Not sure such a change would be allowed for bullseye (5.10) and if the
answer for 5.10 would be another than for i.e. 5.15
Reading what it is, maybe it can in fact be decoupled from NO_HZ_FULL.
Which would mean an upstream patch and backporting (if preempt would do
that, but could be considered a "performance bug" i guess)
> And for CONFIG_RCU_NOCB_CPU
>
> Use this option to reduce OS jitter for aggressive HPC or
> real-time workloads. It can also be used to offload RCU
> callback invocation to energy-efficient CPUs in
> battery-powered asymmetric multiprocessors. The price of this
> reduced jitter is that the overhead of call_rcu() increases and that
> some workloads will incur significant increases in context-switch
> rates.
>
> This option offloads callback invocation from the set of
> CPUs specified at boot time by the rcu_nocbs parameter. For each
> such CPU, a kthread ("rcuox/N") will be created to invoke
> callbacks, where the "N" is the CPU being offloaded, and
> where the "x" is "p" for RCU-preempt (PREEMPTION kernels) and "s" for
> RCU-sched (!PREEMPTION kernels). Nothing prevents this
> kthread from running on the specified CPUs, but (1) the kthreads may
> be preempted between each callback, and (2) affinity or cgroups can
> be used to force the kthreads to run on whatever set of
> CPUs is desired.
>
> Say Y here if you need reduced OS jitter, despite added
> overhead. Say N here if you are unsure.
>
> Adding as well overhead.
>
> Is this still to be considered true?
probably but only for people that actively choose to use it and only
for the CPUs they choose. "rcu_nocbs" cmdline param, if not set
everything will be as it was.
I already indicated that in the commit message of my MR:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/385
regards,
Henning
>
> Regards,
> Salvatore
>
Bug#998536: osmosis: FTBFS: Could not resolve commons-io:commons-io:2.6.
reassign 998536 src:commons-io found 998536 commons-io/2.11.0-1 affects 998536 src:osmosis retitle 998536 Missing dependency on junit5 for junit-bom thanks On 11/4/21 20:56, Lucas Nussbaum wrote: Putting task artifact state for task ':osmosis-pbf2:compileJava' into context took 0.0 secs. Replacing com.google.guava:guava:jar:26.0-jre -> com.google.guava:guava:jar:debian Passing through com.google.guava:guava-parent:jar:debian Replacing commons-io:commons-io:jar:2.6 -> commons-io:commons-io:jar:debian Passing through org.junit:junit-bom:jar:debian Passing through org.jsr-305:jsr305:jar:0.x :osmosis-pbf2:compileJava FAILED :osmosis-pbf2:compileJava (Thread[main,5,main]) completed. Took 0.078 secs. Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. :osmosis-apidb:compileJava (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 1.031 secs. :osmosis-osm-binary:javadoc (Thread[Task worker for ':' Thread 3,5,main]) completed. Took 8.04 secs. :osmosis-core:javadoc (Thread[Task worker for ':',5,main]) completed. Took 8.998 secs. FAILURE: Build failed with an exception. * What went wrong: Could not resolve all files for configuration ':osmosis-pbf2:compileClasspath'. Could not resolve commons-io:commons-io:2.6. Required by: project :osmosis-pbf2 > Could not resolve commons-io:commons-io:2.6. > Could not parse POM /usr/share/maven-repo/commons-io/commons-io/debian/commons-io-debian.pom > Could not resolve org.junit:junit-bom:debian. > No cached version of org.junit:junit-bom:debian available for offline mode. > No cached version of commons-io:commons-io:2.6 available for offline mode. org.junit:junit-bom:debian is provided by junit5, but commons-io build depends on junit4, and libcommons-io-java depends on neither. commons-io-debian.pom may need to be patched, or the package dependencies fixed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#998606: gradle: FTBFS: Could not resolve commons-io:commons-io:debian.
Am Donnerstag, dem 04.11.2021 um 20:54 +0100 schrieb Lucas Nussbaum: > Source: gradle > Version: 4.4.1-13 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211104 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. This looks like the same issue as with syncany. I guess I just remove the (superfluous?) dependency on junit-bom in commons-io and we are done with it. signature.asc Description: This is a digitally signed message part
Bug#998411: Bug#996204: transition: numerical library stack: hypre SONAME (Policy 8.1)
On 2021-11-03 22:33:01 +0100, Drew Parsons wrote: > On 2021-11-03 20:57, Sebastian Ramacher wrote: > > Source: hypre > > Severity: serious > ... > > The real blocker is hypre, specifically: > > > > hypre (2.18.1-1) experimental; urgency=medium > > . > >* Team upload. > >* New upstream release. > >* Standards-Version: 4.4.1 > >* Provide library binary package as libhypre without the soname > > version embedded in the package name. Enforce version dependency > > through strict shlibs dependency. This is to workaround lack of > > ABI backwards compatibility and keep minor version updates being > > delayed in the NEW queue. See README.Debian. > > > > > > As a consequence, hypre breaks co-installability of all its reverse > > dependencies, therefore breaking smooth updates of the packages involved > > in the transition. And yes, in the end, deal.ii currently keeps the > > whole stack from migrating as it renders deal.ii's binaries > > uninstallable in testing. > > > The problem that hypre 2.18.1-1 (un-versioned libhypre) intended to solve is > that hypre is ABI-ignorant (https://github.com/hypre-space/hypre/issues/56), > so each point patch release would have to be a new binary package, and the > upstream release rate is faster than the average NEW queue processing rate > (the new package for the current transition would be libhypre2.22.1, and > already libhypre2.23.0 is released upstream). (So why is this packaged as shared library?) > hypre has only 2 direct reverse dependencies, petsc and sundials, which we > can keep up-to-date easily. The current problem is that deal.ii depends on > the old petsc3.14, so it can't be installed with the new petsc3.15. That's why the second sentence of 8.1 reads: "This allows several versions of the shared library to be installed at the same time, allowing installation of the new version of the shared library without immediately breaking binaries that depend on the old version." The problem is not deal.ii. > It > wouldn't be a problem in practice, if deal.ii hadn't started FTBFS > (Bug#996277) preventing it rebuilding against petsc 3.15. We could say it > was tactical error running the hypre and petsc ABI updates at the same time > (I wasn't anticipating deal.ii Bug#996277) deal.ii doesn't FTBFS. deal.ii cannot currently be rebuilt in unsable because of another broken shared library (#995424 in gmsh). Once deal.ii is rebuilt (in testing), #996277 will disappear. > If we revert back to version-named hypre library packages then the cost is > that we won't be able to provide timely patch updates for hypre (each one > will be a new library package needing to pass NEW, since hypre does not > provide ABI compatibility). > > The alternative for this transition is to remove deal.ii from testing, which > is happening anyway due to Bug#996277 It won't be removed. > So the use of un-versioned libhypre was intended as a specific exception to > Policy 8.1, for the purpose of facilitating faster hypre patch updates. The > irregularity is due to a lack of ABI-awareness in hypre itself. > > Is it best to revert back to strict Policy 8.1 compliance, which will slow > down hypre patch release updates? Yes. Having to wait for binNEW to being processed is not an excuse to violate a must section of the policy. Processing of packages in NEW can take some time. I'm also waiting on some of them for months. The solution to that is however not to abondon well established practices for shared libraries. The problems that are caused by that can be seen with libhypre and its reverse dependencies. Cheers -- Sebastian Ramacher
Bug#998614: RFP: python-crccheck -- implementation of 170+ CRC algorithms in Python
Package: wnpp Severity: wishlist Tags: patch X-Debbugs-Cc: debian-pyt...@lists.debian.org * Package name: python-crccheck Version : 1.0 Upstream Author : Martin Scharrer * URL : https://sourceforge.net/projects/crccheck/ * License : GPL-3 Programming Lang: Python Description : implementation of 170+ CRC algorithms in Python crccheck is a Python module that implements more than 170 CRC algorithms used in various applications. A few examples include: CRC-5/USB, CRC-14/GSM, CRC-16/MODBUS, CRC-24/OPENPGP, PKZIP, CRC-32 A catalogue can be found at http://reveng.sourceforge.net/crc-catalogue/. Packaging crccheck is a prerequisite for other Python modules notably chepy and zigpy. I've already packaged it and am attaching my work. Helmut python-crccheck_1.0-1.debian.tar.xz Description: application/xz
Bug#998282: Please make Section a required field for the source paragraph in d/control
Hi David, On Thu, Nov 4, 2021 at 7:14 AM David Bremner wrote: > > I think Debian would be better off if > we eliminated sections Without sections my request would go away, but that's as much of a side as I will take. > do you have some numbers Thank you for that idea! I added a Lintian classification tag for it [1] and will answer that question shortly. Kind regards Felix Lechner P.S. I would be happy to add additional tags for statistics if they are helpful to your cause. [1] https://salsa.debian.org/lintian/lintian/-/commit/bc48c6e2114c1cf9ca143db3ad9b6068ddca791d
Bug#996153: pipetty doesn't set window size
* Adam Borowski , 2021-10-12, 22:09:
Some programs are very confused about the terminal width when run
under pipetty, e.g.:
[...]
Apparently this is because pipetty never sets windows size, so the
size is reported as 0:
$ strace -f -o '|grep -w TIOCGWINSZ >&2' pipetty gallery-dl --help >/dev/null
9222 ioctl(1, TIOCGWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
9222 ioctl(1, TIOCGWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
Yeah, that's because in the usual use case there is no outside
terminal. Passing the size of the terminal if there's one would be
probably be a bad idea as it'd change the behaviour during testing vs
real use.
One option would be providing a bogus size (such as 80x24 as getty on
serial does). I'm not sure, though, if it'd do more or less harm than
not providing a size at all.
On the other hand, lesstty in any non-erroneous case will be invoked
from a terminal -- I've thus just changed it to pass the size.
What would be your advice about what data to provide for pipetty?
I'm not sure either.
I needed this for my own lesstty-like program. But in the mean time, I
figured out I can easily set the terminal size myself:
https://github.com/jwilk/pagerboy/commit/375bbbcdc3550483
Feel free to close the bug.
--
Jakub Wilk
debian-bugs-dist@lists.debian.org
On Thu, Nov 04, 2021 at 04:29:18PM +0100, Marco M. F. De Santis wrote: > * Package name: hoteldruid >Version : 3.0.3-1 > hoteldruid (3.0.3-1) unstable; urgency=low > . >* New upstream release > - Fixes multiple sql injection and XSS vulnerabilities. >(Ref: CVE-2021-32832, CVE-2021-38733, CVE-2021-38559) >(Closes: #991910) >* debian/control: updated Standards-Version >* debian/watch: updated debian watch file standard >* Added lintian override for index.html that is not documentation >* Updated appdata file with categories and content_rating >* debian/postinst: replaced tempfile with mktemp (Closes: #992458) >* Added autopkg tests: install-sqlite and lint >* debian/config: don't set administrator-username as blank when > called twice Hi! I'm afraid the "install-sqlite" autopkgtest silently fails; full log: autopkgtest [19:54:05]: test install-sqlite: preparing testbed autopkgtest [19:54:06]: testbed dpkg architecture: amd64 Get:1 file:/tmp/autopkgtest.tZYvNW/binaries InRelease Ign:1 file:/tmp/autopkgtest.tZYvNW/binaries InRelease Get:2 file:/tmp/autopkgtest.tZYvNW/binaries Release [816 B] Get:2 file:/tmp/autopkgtest.tZYvNW/binaries Release [816 B] Get:3 file:/tmp/autopkgtest.tZYvNW/binaries Release.gpg Ign:3 file:/tmp/autopkgtest.tZYvNW/binaries Release.gpg Get:4 file:/tmp/autopkgtest.tZYvNW/binaries Packages [1438 B] Reading package lists... Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following additional packages will be installed: apache2 apache2-bin apache2-data apache2-utils curl hoteldruid libapache2-mod-php libapache2-mod-php7.4 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libargon2-1 libbrotli1 libbsd0 libcurl4 libedit2 libexpat1 libicu67 libjansson4 libldap-2.4-2 liblua5.3-0 libmagic-mgc libmagic1 libmd0 libncurses6 libncursesw6 libnghttp2-14 libprocps8 libpsl5 librtmp1 libsasl2-2 libsasl2-modules-db libsodium23 libsqlite3-0 libssh2-1 libxml2 libxslt1.1 mailcap media-types mime-support php-common php-sqlite3 php-xml php7.4-cli php7.4-common php7.4-json php7.4-opcache php7.4-readline php7.4-sqlite3 php7.4-xml procps psmisc sensible-utils ucf Suggested packages: apache2-doc apache2-suexec-pristine | apache2-suexec-custom www-browser firefox | www-browser php-mysql | php-pgsql php-pear file Recommended packages: ssl-cert php-imap ca-certificates libldap-common libgpm2 publicsuffix libsasl2-modules file The following NEW packages will be installed: apache2 apache2-bin apache2-data apache2-utils curl hoteldruid libapache2-mod-php libapache2-mod-php7.4 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libargon2-1 libbrotli1 libbsd0 libcurl4 libedit2 libexpat1 libicu67 libjansson4 libldap-2.4-2 liblua5.3-0 libmagic-mgc libmagic1 libmd0 libncurses6 libncursesw6 libnghttp2-14 libprocps8 libpsl5 librtmp1 libsasl2-2 libsasl2-modules-db libsodium23 libsqlite3-0 libssh2-1 libxml2 libxslt1.1 mailcap media-types mime-support php-common php-sqlite3 php-xml php7.4-cli php7.4-common php7.4-json php7.4-opcache php7.4-readline php7.4-sqlite3 php7.4-xml procps psmisc sensible-utils ucf 0 upgraded, 55 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 20.8 MB/22.2 MB of archives. After this operation, 91.9 MB of additional disk space will be used. Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 sensible-utils all 0.0.17 [21.5 kB] Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 ucf all 3.0043 [74.0 kB] Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libapr1 amd64 1.7.0-8 [106 kB] Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libexpat1 amd64 2.4.1-3 [104 kB] Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libaprutil1 amd64 1.6.1-5 [92.1 kB] Get:6 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libsqlite3-0 amd64 3.36.0-2 [815 kB] Get:7 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libaprutil1-dbd-sqlite3 amd64 1.6.1-5 [18.8 kB] Get:8 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libsasl2-modules-db amd64 2.1.27+dfsg-2.2 [69.1 kB] Get:9 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libsasl2-2 amd64 2.1.27+dfsg-2.2 [106 kB] Get:10 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libldap-2.4-2 amd64 2.4.59+dfsg-1 [232 kB] Get:11 file:/tmp/autopkgtest.tZYvNW/binaries hoteldruid 3.0.3-1 [1346 kB] Get:12 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libaprutil1-ldap amd64 1.6.1-5 [17.0 kB] Get:13 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libbrotli1 amd64 1.0.9-
Bug#997919: pipewire: Automatich profile selection for bluetooth headsets fails since 0.3.39
On 27.10.21 21:24, Dylan Aïssi wrote: Could you check if you have both wireplumber and libspa-0.2-bluetooth installed on your system? (Sorry for the late reply, I just learned by accident, that the BTS silently ate my two previous mails.) Hy Dylan, yes. In fact, I had to manually install libspa-0.2-bluetooth otherwise I could pair with the headphone, but not connect due to "protocol not available". Wireplumber is installed too, as I said it replaced the pipewire-media-session last week and I suspect that may be the reason why this bug appears. Meanwhile, I've created an upstream issue here: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/640#note_1122799 Which caused an issue in wireplumber: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/90 The bottom line is, that wireplumber does not support profile switching. pipewire-session-manager did. Cheers, Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
Bug#998613: retro-gtk: FTBFS: ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments "export_packages", "namespace"
Source: retro-gtk Version: 1.0.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- -Ddemos=false > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Ddemos=false > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: retro-gtk > Project version: 1.0.2 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency epoxy found: YES 1.5.9 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency glib-2.0 found: YES 2.70.0 > Run-time dependency gmodule-2.0 found: YES 2.70.0 > Run-time dependency gobject-2.0 found: YES 2.70.0 > Run-time dependency gtk+-3.0 found: YES 3.24.30 > Run-time dependency libpulse-simple found: YES 15.0 > Library m found: YES > Run-time dependency samplerate found: YES 0.2.2 > Configuring retro-gtk-config.h using configuration > Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program make-ipc-runner-private.sh found: YES > (/<>/shared/make-ipc-runner-private.sh) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Configuring retro-gtk-version.h using configuration > Run-time dependency gobject-introspection-1.0 found: YES 1.70.0 > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program vapigen found: YES (/usr/bin/vapigen) > > ../retro-gtk/meson.build:188:4: ERROR: Got unknown keyword arguments > "export_packages", "namespace" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:50:41.618732 > Main binary: /usr/bin/python3 > Build Options: -Ddemos=false -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: retro-gtk > Project version: 1.0.2 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the build machine: cc ld.bfd 2.37 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 >
Bug#998612: libisocodes: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: libisocodes
Version: 1.2.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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 '/<>/po'
> make[3]: Nothing to be done for 'check'.
> make[3]: Leaving directory '/<>/po'
> make[3]: Verzeichnis „/<>“ wird betreten
> make check-local
> make[4]: Verzeichnis „/<>“ wird betreten
> /usr/bin/valac --pkg libxml-2.0 --pkg gee-0.8 --vapidir=./vapi --pkg config
> -X -I. -X -DGETTEXT_PACKAGE=\"libisocodes\" -X
> -DLOCALEDIR=\"/usr/share/locale\" -X -DTESTDIR=\"./tests/data\"
> --output=codetest tests/codetest.vala tests/test_iso_3166.vala
> tests/test_iso_3166_2.vala tests/test_iso_639.vala tests/test_iso_639_3.vala
> tests/test_iso_639_5.vala tests/test_iso_4217.vala tests/test_iso_15924.vala
> src/isocodes.vala src/iso_3166.vala src/iso_3166_item.vala
> src/iso_3166_2.vala src/iso_3166_2_item.vala src/iso_639.vala
> src/iso_639_item.vala src/iso_639_3.vala src/iso_639_3_item.vala
> src/iso_639_5.vala src/iso_639_5_item.vala src/iso_4217.vala
> src/iso_4217_item.vala src/iso_15924.vala src/iso_15924_item.vala
> src/exceptions.vala
> config.vapi:19.2-19.6: warning: Argument `prefix' never used
> [CCode (prefix = "", lower_case_cprefix = "", cheader_filename = "config.h")]
> ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_3166.vala.c:22:
> /<>/tests/test_iso_3166.vala.c: In function
> ‘libisocodes_test_iso_3166_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
> ‘g_atomic_pointer_get’
> 260 | (!g_atomic_pointer_get (location) && \
> | ^~~~
> /<>/tests/test_iso_3166.vala.c:1913:13: note: in expansion of
> macro ‘g_once_init_enter’
> 1913 | if (g_once_init_enter
> (&libisocodes_test_iso_3166_type_id__volatile)) {
> | ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_3166_2.vala.c:22:
> /<>/tests/test_iso_3166_2.vala.c: In function
> ‘libisocodes_test_iso_3166_2_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
> ‘g_atomic_pointer_get’
> 260 | (!g_atomic_pointer_get (location) && \
> | ^~~~
> /<>/tests/test_iso_3166_2.vala.c:1191:13: note: in expansion of
> macro ‘g_once_init_enter’
> 1191 | if (g_once_init_enter
> (&libisocodes_test_iso_3166_2_type_id__volatile)) {
> | ^
> In file included from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /usr/include/glib-2.0/gobject/gbinding.h:28,
> from /usr/include/glib-2.0/glib-object.h:22,
> from /<>/tests/test_iso_639.vala.c:22:
> /<>/tests/test_iso_639.vala.c: In function
> ‘libisocodes_test_iso_639_get_type’:
> /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
> ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
> 113 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
> __ATOMIC_SEQ_CST); \
> | ^
> /usr/include/glib-
Bug#998611: rust-tokio-executor: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~)
Source: rust-tokio-executor Version: 0.1.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-crossbeam-utils-0.7+default-dev, > librust-futures-0.1+default-dev (>= 0.1.19-~~), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-crossbeam-utils-0.7+default-dev, > librust-futures-0.1+default-dev (>= 0.1.19-~~), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [449 B] > Get:5 copy:/<>/apt_archive ./ Packages [521 B] > Fetched 1927 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-futures-0.1+default-dev > (>= 0.1.19-~~) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/rust-tokio-executor_0.1.8-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#998608: canl-java: FTBFS: [ERROR] /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17]
Source: canl-java Version: 2.7.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=maven >dh_update_autotools_config -O--buildsystem=maven >dh_autoreconf -O--buildsystem=maven >dh_auto_configure -O--buildsystem=maven > mh_patchpoms -plibcanl-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build -O--buildsystem=maven > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The project eu.eu-emi.security:canl:jar:2.7.0 uses prerequisites > which is only intended for maven-plugin projects but not for non maven-plugin > projects. For such purposes you should use the maven-enforcer-plugin. See > https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html > [INFO] > [INFO] --< eu.eu-emi.security:canl > >--- > [INFO] Building canl 2.7.0 > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ canl > --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ canl --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 167 source files to /<>/target/classes > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Some input files use or override a deprecated API. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/RFC3280CertPathUtilitiesCanl.java: > Recompile with -Xlint:deprecation for details. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Some input files use unchecked or unsafe operations. > [INFO] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/PKIXPolicyNode.java: > Recompile with -Xlint:unchecked for details. > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] > eu.emi.security.authn.x509.helpers.trust.OpensslTruststoreHelper$1> is not > abstract and does not override abstract method > accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in > org.apache.commons.io.file.PathFilter > [INFO] 1 error > [INFO] - > [INFO] > [INFO] > > [INFO] Skipping canl > [INFO] This project has been banned from the build due to previous failures. > [INFO] > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.558 s > [INFO] Finished at: 2021-11-04T09:29:19Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > (default-compile) on project canl: Compilation failure > [ERROR] > /<>/src/main/java/eu/emi/security/authn/x509/helpers/trust/OpensslTruststoreHelper.java:[80,17] > eu.emi.security.authn.x509.helpers.trust.OpensslTruststoreHelper$1> is not > abstract and does not override abstract method > accept(java.nio.file.Path,java.nio.file.attribute.BasicFileAttributes) in > org.apache.commons.io.file.PathFilter > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERRO
Bug#998609: appstream-glib: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "firmware, ostree"
Source: appstream-glib Version: 0.7.18-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- -Dbuilder=false -Drpm=false -Dostree=false -Ddep11=true > -Dfirmware=true -Dgtk-doc=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dbuilder=false > -Drpm=false -Dostree=false -Ddep11=true -Dfirmware=true -Dgtk-doc=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "firmware, ostree" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:48:43.587741 > Main binary: /usr/bin/python3 > Build Options: -Dbuilder=false -Drpm=false -Dostree=false -Ddep11=true > -Dfirmware=true -Dgtk-doc=true -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "firmware, ostree" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dbuilder=false > -Drpm=false -Dostree=false -Ddep11=true -Dfirmware=true -Dgtk-doc=true > returned exit code 1 > make[1]: *** [debian/rules:23: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/appstream-glib_0.7.18-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#998610: node-cli-truncate: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Source: node-cli-truncate Version: 2.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/cli-truncate > /bin/sh -ex debian/tests/pkg-js/test > + tape test.js > TAP version 13 > # main > /<>/index.js:102 > return sliceAnsi(text, 0, columns - ellipsisWidth) + ellipsis; > ^ > > TypeError: sliceAnsi is not a function > at module.exports (/<>/index.js:102:10) > at Test. (/<>/test.js:5:7) > at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.run (/usr/share/nodejs/tape/lib/test.js:114:31) > at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:96:32) > at Immediate.next (/usr/share/nodejs/tape/lib/results.js:88:19) > at processImmediate (internal/timers.js:461:21) > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/node-cli-truncate_2.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#998607: gnome-logs: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "tests"
Source: gnome-logs Version: 3.36.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- -Dman=true -Dtests=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dman=true -Dtests=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "tests" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:33:47.509593 > Main binary: /usr/bin/python3 > Build Options: -Dman=true -Dtests=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "tests" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dman=true -Dtests=true > returned exit code 1 > make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gnome-logs_3.36.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#998606: gradle: FTBFS: Could not resolve commons-io:commons-io:debian.
Source: gradle Version: 4.4.1-13 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > sed '/@GENERATED@/,$d' debian/gradle.pod.in > debian/gradle.pod > # process items: `-?`, `-h`, `--help`:: → =item `-?`, `-h`, `--help` > # process bold: `-?` → B<-?> > # remove empty line markers > # drop text from links: https://gradle.com/build-scans[...] > # drop underscores from documentation links > # replace documentation links by UPPERCASE LABELS > # ... but not those where the link is in a middle of a sentence > # ... since otherwise it breaks the sentence structure > # ... so just make it *bold* instead > # move parethesed option "(comments)" outside of the bold parts > # cut off everything after and including the [[daemon_cli]] section > # cut off the introduction > sed \ > -e 's/\(.*\):: *$/\n=item \1\n/' \ > -e 's/`\([^`]*\)`/B<\1>/g' \ > -e 's/^+$//g' \ > -e 's/\(https:[^[]*\)[[][^]]*\]/L<\1>/g' \ > -e '/<]*>>/y/_/ /' \ > -e 's/\([Tt]he\) <]*\)>>/\1 documentation section > B<\U\2\E>/g' \ > -e 's/<]*\)>>/the documentation section B<\U\1\E>/g' \ > -e '/<<[^>]*>>/y/_/ /' \ > -e 's/<<.[^,]*,\([^>]*\)>>/B<\1>/g' \ > -e 's/\([Tt]he\) <<\([^>]*\)>>/\1 documentation section B<\U\2\E>/g' \ > -e 's/<<\([^>]*\)>>/the documentation section B<\U\1\E>/g' \ > -e 's/ (\([^)]*\))>/> (\1)/g' \ > -e '/^\[\[.*]]$/d' \ > -e 's/GRADLE OPTS/GRADLE_OPTS/g' \ > -e 's/^=== \(.*\)$/=back\n\n=head1 \U\1\n\n/g' \ > -e '0,/The command-line options available/d' \ > subprojects/docs/src/docs/userguide/commandLine.adoc >> > debian/gradle.pod > sed '0,/@GENERATED@/d' debian/gradle.pod.in >> debian/gradle.pod > touch -d@1613028759 debian/gradle.pod > pod2man --errors=stderr --utf8 -r "Gradle 4.4.1" -c "Gradle Command Line > Manual" debian/gradle.pod > debian/gradle.1 > debian/gradle.pod around line 196: '=item' outside of any '=over' > debian/gradle.pod around line 229: '=item' outside of any '=over' > debian/gradle.pod around line 244: '=item' outside of any '=over' > Wide character in printf at /usr/share/perl/5.32/Pod/Simple.pm line 573. > debian/gradle.pod around line 250: Non-ASCII character seen before =encoding > in '“B”'. Assuming UTF-8 > rm -f gradle.properties # Some properties here breaks the latest JVM > mkdir --parents buildSrc/src/main/java/tmp # Symlinks are for building Gradle > 4 using Gradle 3 > ln --symbolic --force --target-directory=buildSrc/src/main/java/tmp/ > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/Directory.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/DirectoryProperty.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/FileSystemLocation.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFile.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/file/RegularFileProperty.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/NonNullApi.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Property.java > > ../../../../../subprojects/core-api/src/main/java/org/gradle/api/provider/Provider.java > > ../../../../../subprojects/core/src/main/java/org/gradle/api/internal/file/TaskFileVarFactory.java > gradle assemble startScripts --project-prop finalRelease=true --offline > --stacktrace --gradle-user-home debian/.gradlehome --no-daemon > -Dgradle-debian-helper.hook.enabled=false -x :distributions:assemble -x > :internalTesting:assemble -x :internalIntegTesting:assemble -x > :internalPerformanceTesting:assemble -x :integTest:assemble -x > :performance:assemble -x :smokeTest:assemble -x :soak:assemble --parallel > --max-workers=4 > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider
Bug#998602: matplotlib: FTBFS: dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js is missing
Source: matplotlib Version: 3.3.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > py3versions: no X-Python3-Version in control file, using supported versions > dh_testdir -i > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dh_testroot -i > dh_prep > dh_install -p python-matplotlib-data > dh_install: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/Vera*.ttf > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/*.TXT > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/local.conf > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/pdfcorefonts/readme.txt > chmod 644 > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/images/*.svg > dh_testdir -i > dh_testroot -i > dh_installchangelogs > dh_installchangelogs: warning: Compatibility levels before 10 are deprecated > (level 7 in use) > dh_installdocs -ppython-matplotlib-doc -i doc/build/html/ tutorials/ > dh_installdocs: warning: Compatibility levels before 10 are deprecated (level > 7 in use) > # remove pyc file from doc > dh_installexamples -ppython-matplotlib-doc -i examples/* > dh_installexamples: warning: Compatibility levels before 10 are deprecated > (level 7 in use) > dh_compress -i -Xexamples -Xexamples/data -Xpdf -X.js -X.py -Xobjects.inv > -X.html > dh_compress: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > dh_compress: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > dh_link -i > dh_sphinxdoc > dh_sphinxdoc: error: > debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js > is missing > make: *** [debian/rules:163: binary-indep] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/matplotlib_3.3.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#998604: wala: FTBFS: Could not resolve commons-io:commons-io:2.4.
Source: wala Version: 1.5.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=wala -Dfile.encoding=UTF-8 --parallel > --max-workers=4 jar > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@4bf3798b > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Generating JAR file: > /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar > Generating JAR file 'gradle-api-4.4.1.jar' > Keep-alive timer started > Adding Debian repository to project 'buildSrc' > Parallel execution is an incubating feature. > Evaluating project ':buildSrc' using build file > '/<>/buildSrc/build.gradle'. > Adding Maven pom generation to project 'buildSrc' > Linking the generated javadoc to the system JDK API documentation > Selected primary task 'clean' from project : > Selected primary task 'build' from project : > Creating new cache for annotation-processors, path > /<>/buildSrc/.gradle/4.4.1/fileContent/annotation-processors.bin, > access org.gradle.cache.internal.DefaultCacheAccess@2047adea > Creating new cache for resourceHashesCache, path > /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > Creating new cache for taskHistory, path > /<>/buildSrc/.gradle/4.4.1/taskHistory/taskHistory.bin, access > org.gradle.cache.internal.DefaultCacheAccess@300aa927 > Creating new cache for outputFiles, path > /<>/buildSrc/.gradle/buildOutputCleanup/outputFiles.bin, access > org.gradle.cache.internal.DefaultCacheAccess@6774f264 > Build cache is an incubating feature. > Using local directory build cache for build ':buildSrc' (location = > /<>/.gradle/caches/build-cache-1, targetSize = 5 GB). > :clean (Thread[main,5,main]) started. > :buildSrc:clean > Putting task artifact state for task ':buildSrc:clean' into context took > 0.001 secs. > Caching disabled for task ':buildSrc:clean': Caching has not been enabled for > the task > Up-to-date check for task ':buildSrc:clean' took 0.0 secs. It is not > up-to-date because: > Task has not declared any outputs. > :buildSrc:clean UP-TO-DATE > :clean (Thread[main,5,main]) completed. Took 0.022 secs. > :compileJava (Thread[main,5,main]) started. > :buildSrc:compileJava > Putting task artifact state for task ':buildSrc:compileJava' into context > took 0.004 secs. > file or directory '/<>/buildSrc/src/main/java', not found > Skipping task ':buildSrc:compileJava' as it has no source files and no > previous output files. > :buildSrc:compileJava NO-SOURCE > :compileJava (Thread[main,5,main])
Bug#998605: krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error
Source: krita Version: 1:4.4.8+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>/obj-x86_64-linux-gnu' > [ 90%] Generating krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E echo > > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E touch > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/sip -t ALL -t WS_X11 -t Qt_5_15_0 -g -o -x PyKDE_QVector -n > PyQt5.sip -j 1 -c > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita > -I /usr/share/sip -I /usr/lib/python3/dist-packages/PyQt5/bindings -I > /<>/plugins/extensions/pykrita/sip/krita > /<>/plugins/extensions/pykrita/sip/krita/kritamod.sip > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: > syntax error > make[3]: *** > [plugins/extensions/pykrita/sip/CMakeFiles/python_module_PyKrita_krita.dir/build.make:113: > plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/krita_4.4.8+dfsg-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#998603: weston: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "simple-dmabuf-drm"
Source: weston Version: 9.0.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- -Dscreenshare=true \ > -Dsystemd=true -Dsimple-dmabuf-drm=auto > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu -Dscreenshare=true -Dsystemd=true > -Dsimple-dmabuf-drm=auto > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "simple-dmabuf-drm" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:48:16.842009 > Main binary: /usr/bin/python3 > Build Options: -Dscreenshare=true -Dsystemd=true -Dsimple-dmabuf-drm=auto > -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu -Dlibexecdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "simple-dmabuf-drm" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu -Dscreenshare=true -Dsystemd=true > -Dsimple-dmabuf-drm=auto returned exit code 1 > make[1]: *** [debian/rules:4: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/weston_9.0.0-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#998601: libconfig-model-itself-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 2
Source: libconfig-model-itself-perl Version: 2.022-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > xvfb-run -a dh_auto_test > /usr/bin/perl Build test --verbose 1 > Configuration item has a configuration model declaration error: > load error: couldn't do > /<>/<>/wr_root/application/lib/wr_model1/models/MasterModel.pl: > No such file or directory > # Tests were run but no plan was declared and done_testing() was not seen. > # Looks like your test exited with 2 just after 4. > t/application.t > ok 1 - compiled > # Running tests in wr_root/application > ok 2 - loaded Master model > ok 3 - Read Itself::Model and created instance > ok 4 - Created model reader/writer > Dubious, test returned 2 (wstat 512, 0x200) > All 4 subtests passed > t/author-critic.t .. skipped: these tests are for testing by the > author > t/backend_detect.t . > ok 1 - compiled > ok 2 - test class created > ok 3 - IniFile plugin backend was found > ok 4 - Found IniFile doc in pod > ok 5 - cds_file help was kept > ok 6 - memory cycle > 1..6 > ok > Prototype mismatch: sub CORE::GLOBAL::exit: none vs (;$) at > /usr/lib/x86_64-linux-gnu/perl5/5.32/Tk.pm line 415. > > # Failed test 'edit is in test mode' > # at t/cme-meta-edit.t line 34. > # 'Reading model from /usr/share/perl5/Config/Model > # ' > # doesn't match '(?^:Test mode: quit)' > # Looks like you failed 1 test of 3. > t/cme-meta-edit.t .. > ok 1 - compiled > ok 2 - edit and quit > not ok 3 - edit is in test mode > 1..3 > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/3 subtests > Prototype mismatch: sub CORE::GLOBAL::exit: none vs (;$) at > /usr/lib/x86_64-linux-gnu/perl5/5.32/Tk.pm line 415. > > # Failed test 'threw no exceptions' > # at t/cme-meta-plugin.t line 52. > # got: 'Configuration item has a configuration model declaration > error: > # load error: couldn't do > /<>/usr/share/perl5/Config/Model/models/Fstab.pl: No such file > or directory > # ' > # expected: undef > > # Failed test 'edit plugin is in test mode' > # at t/cme-meta-plugin.t line 57. > # 'Preparing plugin my-plugin for model Fstab found in > /usr/share/perl5/Config/Model > # Use -dev option to create a plugin for a local model (i.e. in > wr_test/plugin-ui) > # ' > # doesn't match '(?^:Test mode: save and quit)' > > # Failed test 'check content of > wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl' > # at t/cme-meta-plugin.t line 59. > # Could not open file > wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl: No such > file or directory > # Looks like you failed 3 tests of 5. > t/cme-meta-plugin.t > ok 1 - compiled > not ok 2 - threw no exceptions > ok 3 - edit plugin and quit > not ok 4 - edit plugin is in test mode > not ok 5 - check content of > wr_test/plugin-ui/models/Fstab.d/my-plugin/Fstab/CommonOptions.pl > 1..5 > Dubious, test returned 3 (wstat 768, 0x300) > Failed 3/5 subtests > Prototype mismatch: sub CORE::GLOBAL::exit: none vs (;$) at > /usr/lib/x86_64-linux-gnu/perl5/5.32/Tk.pm line 415. > > # Failed test 'meta check fstab' > # at t/cme-meta.t line 32. > # 'loading model > # Reading model from /usr/share/perl5/Config/Model > # ' > # doesn't match '(?^:checking data)' > > # Failed test 'dump fstab model in wr_root/cme-meta/fstab.cds' > # at t/cme-meta.t line 40. > # 'Reading model from /usr/share/perl5/Config/Model > # ' > # doesn't match '(?^:Dumping Fstab)' > > # Failed test 'check content of wr_root/cme-meta/fstab.cds' > # at t/cme-meta.t line 41. > # Could not open file wr_root/cme-meta/fstab.cds: No such file or > directory > > # Failed test 'dump fstab model in wr_root/cme-meta/fstab.yml' > # at t/cme-meta.t line 47. > # 'Reading model from /usr/share/perl5/Config/Model > # ' > # doesn't match '(?^:Dumping Fstab)' > > # Failed test 'check content of wr_root/cme-meta/fstab.yml' > # at t/cme-meta.t line 48. > # Could not open file wr_root/cme-meta/fstab.yml: No such fi
Bug#998599: jengelman-shadow: FTBFS: Could not resolve commons-io:commons-io:2.5.
Source: jengelman-shadow Version: 4.0.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 -- jar -x test > mkdir -p .gradle/init.d > cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ > gradle --info --console plain --offline --stacktrace --no-daemon > --refresh-dependencies --gradle-user-home .gradle -Duser.home=. > -Duser.name=debian -Ddebian.package=jengelman-shadow -Dfile.encoding=UTF-8 > --parallel --max-workers=4 jar -x test > Initialized native services in: /<>/.gradle/native > Using 4 worker leases. > Creating new cache for fileHashes, path > /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@162be91c > Creating new cache for resourceHashesCache, path > /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, > access org.gradle.cache.internal.DefaultCacheAccess@162be91c > Creating new cache for fileHashes, path > /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access > org.gradle.cache.internal.DefaultCacheAccess@2cd2c8fe > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access using Lookup on > org.gradle.internal.reflect.JavaMethod > (file:/usr/share/gradle/lib/gradle-base-services-4.4.1.jar) to class > java.lang.ClassLoader > WARNING: Please consider reporting this to the maintainers of > org.gradle.internal.reflect.JavaMethod > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > Starting Build > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using SubsetScriptTransformer. > Creating new cache for metadata-1.1/results, path > /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access > org.gradle.cache.internal.DefaultCacheAccess@221a2068 > Compiling initialization script '/<>/.gradle/init.d/init.gradle' > using BuildScriptTransformer. > Generating JAR file: > /<>/.gradle/caches/4.4.1/generated-gradle-jars/gradle-api-4.4.1.jar > Generating JAR file 'gradle-api-4.4.1.jar' > Keep-alive timer started > Adding Debian repository to project 'buildSrc' > Parallel execution is an incubating feature. > Evaluating project ':buildSrc' using build file > '/<>/buildSrc/build.gradle'. > Compiling build file '/<>/buildSrc/build.gradle' using > SubsetScriptTransformer. > Compiling build file '/<>/buildSrc/build.gradle' using > BuildScriptTransformer. > Adding Maven pom generation to project 'buildSrc' > Linking the generated javadoc to the system JDK API documentation > Creating new cache for metadata-2.36/module-metadata, path > /<>/.gradle/caches/modules-2/metadata-2.36/module-metadata.bin, > access org.gradle.cache.internal.DefaultCacheAccess@57515944 > Loading the Maven rules... > Replacing org.codehaus.groovy:groovy-backports-compat23:jar:2.4.15 -> > org.codehaus.groovy:groovy:jar:debian > Replacing org.jdom:jdom2:jar:2.0.6 -> org.jdom:jdom2:jar:debian > Replacing org.ow2.asm:asm:jar:7.0-beta -> > org.ow2.asm:asm-all:jar:debian > Ignoring org.ow2.asm:asm-commons:jar:7.0-beta > Replacing commons-io:commons-io:jar:2.5 -> > commons-io:commons-io:jar:debian > Passing through org.apache.commons:commons-parent:jar:debian > Passing through org.apache:apache:jar:debian > Passing through org.junit:junit-bom:jar:debian > Replacing org.apache.ant:ant:jar:1.9.7 -> > org.apache.ant:ant:jar:debian > Passing through org.apache.ant:ant-parent:jar:debian > Replacing org.codehaus.plexus:plexus-utils:jar:3.0.24 -> > org.codehaus.plexus:plexus-utils:jar:debian > Replacing org.apache.logging.log4j:log4j-core:jar:2.11.0 -> > org.apache.logging.log4j:log4j-core:jar:debian > Passing through org.apache.logging.log4j:log4j:jar:debian > Replacing org.vafer:jdependency:jar:2.1.1 -> > org.vafer:jdependency:jar:debian > Passing through org.apache.ant:ant-launcher:jar:debian > Passing through org.apache.logging.log4j:log4j-api:jar:debian > > FAILURE: Build failed with an exception. > > * What went wrong: > Could not resolve all files for configuration ':buildSrc:runtimeClasspath'. &g
Bug#998600: mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
Source: mdevctl
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> install -d /<>/debian/.debhelper/generated/_source/home
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
> cp debian/cargo-checksum.json .cargo-checksum.json
> rm -f Cargo.lock
> /usr/share/cargo/bin/cargo prepare-debian debian/cargo_registry
> --link-from-system
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
>dh_auto_test -O--buildsystem=cargo
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
> /usr/share/cargo/bin/cargo build
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `env_logger = "^0.7.1"`
> candidate versions found which didn't match: 0.9.0
> location searched: directory source `/<>/debian/cargo_registry`
> (which is replacing registry `crates-io`)
> required by package `mdevctl v1.0.0 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> rm -fr -- /tmp/dh-xdg-rundir-5hMmEe4U
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/mdevctl_1.0.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#998598: distro-info: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2
Source: distro-info Version: 1.0 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > testDevel > testOldstable > py3versions: no X-Python3-Version in control file, using supported versions > cd python && python3.9 setup.py test > testStable > 1..35 > testSupported > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > testLTS > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testELTS > testUnsupported > testTesting > testFullname > testRelease > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > testSeries > running build_ext > testCombinedShortform > testReleaseDate > test_pylint (distro_info_test.test_pylint.PylintTestCase) > Test: Run pylint on Python source code ... Running following command: > /usr/bin/python3.9 -m pylint > --rcfile=/<>/python/distro_info_test/pylint.conf -- > debian-distro-info ubuntu-distro-info distro_info.py setup.py > testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentAlias > testMissingArgumentDate > testMissingArgumentSeries > testInvalidAlias > testInvalidDate > testInvalidSeries > testMultipleAlias > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 30 tests. > > OK > ./test-ubuntu-distro-info > testAll > testDevel > testLatest > testLTS > testStable > testSupported > testUnsupported > testFullname > testRelease > testSeries > testCombinedShortform > testReleaseDate > testHelp > testExactlyOne > testUnrecognizedOption > testUnrecognizedArguments > testMissingArgumentDate > testMissingArgumentSeries > testDistributionDataOutdated > testInvalidDate > testInvalidSeries > testMultipleDates > testMultipleSeries > testUnknownSeries > testDays > > Ran 25 tests. > > OK > FAIL > test_all (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: List all known Debian distributions. ... ok > test_codename (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Codename decoding ... ok > test_codename_result > (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Check result set to codename. ... ok > test_devel (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Get latest development Debian distribution. ... ok > test_elts_supported > (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: List all ELTS supported Debian distribution. ... ok > test_fullname (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Check result set to fullname. ... ok > test_lts_supported > (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: List all LTS supported Debian distribution. ... ok > test_old (distro_info_test.test_distro_info.DebianDistroInfoTestCase) > Test: Get old (stable) Debian distribution. ... ok > test_release (distro_info_tes
Bug#998596: python-pyproj: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Source: python-pyproj Version: 3.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test > I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_pyproj/build; > python3.9 -m pytest -v -m "not network and not cli and not grid" > = test session starts > == > platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- > /usr/bin/python3.9 > cachedir: .pytest_cache > rootdir: /<>, configfile: pytest.ini > plugins: cov-3.0.0 > collecting ... collected 816 items / 59 deselected / 757 selected > > test/test_aoi.py::test_backwards_compatible_import_paths PASSED [ > 0%] > test/test_aoi.py::test_contains PASSED [ > 0%] > test/test_aoi.py::test_not_contains PASSED [ > 0%] > test/test_aoi.py::test_intersects PASSED [ > 0%] > test/test_aoi.py::test_not_intersects PASSED [ > 0%] > test/test_aoi.py::test_null_input[input0-AreaOfInterest] PASSED [ > 0%] > test/test_aoi.py::test_null_input[input0-BBox] PASSED[ > 0%] > test/test_aoi.py::test_null_input[input1-AreaOfInterest] PASSED [ > 1%] > test/test_aoi.py::test_null_input[input1-BBox] PASSED[ > 1%] > test/test_aoi.py::test_null_input[input2-AreaOfInterest] PASSED [ > 1%] > test/test_aoi.py::test_null_input[input2-BBox] PASSED[ > 1%] > test/test_aoi.py::test_null_input[input3-AreaOfInterest] PASSED [ > 1%] > test/test_aoi.py::test_null_input[input3-BBox] PASSED[ > 1%] > test/test_aoi.py::test_null_input[input4-AreaOfInterest] PASSED [ > 1%] > test/test_aoi.py::test_null_input[input4-BBox] PASSED[ > 1%] > test/test_aoi.py::test_null_input[input5-AreaOfInterest] PASSED [ > 2%] > test/test_aoi.py::test_null_input[input5-BBox] PASSED[ > 2%] > test/test_aoi.py::test_null_input[input6-AreaOfInterest] PASSED [ > 2%] > test/test_aoi.py::test_null_input[input6-BBox] PASSED[ > 2%] > test/test_aoi.py::test_null_input[input7-AreaOfInterest] PASSED [ > 2%] > test/test_aoi.py::test_null_input[input7-BBox] PASSED[ > 2%] > test/test_aoi.py::test_null_input[input8-AreaOfInterest] PASSED [ > 2%] > test/test_aoi.py::test_null_input[input8-BBox] PASSED[ > 3%] > test/test_aoi.py::test_null_input[input9-AreaOfInterest] PASSED [ > 3%] > test/test_aoi.py::test_null_input[input9-BBox] PASSED[ > 3%] > test/test_awips221.py::test_awips221 PASSED [ > 3%] > test/test_database.py::test_backwards_compatible_import_paths PASSED [ > 3%] > test/test_database.py::test_units_map__default PASSED[ > 3%] > test/test_database.py::test_units_map__category[linear] PASSED [ > 3%] > test/test_database.py::test_units_map__category[linear_per_time] PASSED [ > 3%] > test/test_database.py::test_units_map__category[angular] PASSED [ > 4%] > test/test_database.py::test_units_map__category[angular_per_time] PASSED [ > 4%] > test/test_database.py::test_units_map__category[scale] PASSED[ > 4%] > test/test_database.py::test_units_map__category[scale_per_time] PASSED [ > 4%] > test/test_database.py::test_units_map__category[time] PASSED [ > 4%] > test/test_database.py::test_units_map__auth_name[EPSG] PASSED[ > 4%] > test/test_database.py::test_units_map__auth_name[PROJ] PASSED[ > 4%] > test/test_database.py::test_units_map__deprecated[zzz] PASSED[ > 5%] > test/test_database.py::test_units_map__deprecated[True0] PASSED [ > 5%] > test/test_database.py::test_units_map__deprecated[True1] PASSED [ > 5%] > test/test_database.py::test_units_map__invalid[None-1] PASSED[ > 5%] > test/test_database.py::test_units_map__invalid[1-None] PASSED[ > 5%] > test/test_database.py::test_get_authorities PASSED [ > 5%] > test/test_database.py::test_get_codes[IGNF-PJType.ELLIPSOID-False] PASSED [ > 5%] > test/test_database.py::test_get_codes[EPSG-PJType.CRS-False] PASSED [ > 5%] > test/test_da
Bug#998597: sysprof: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "sysprofd"
Source: sysprof Version: 3.40.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > -Denable_examples=true \ > -Denable_tests=true \ > -Denable_tools=true \ > -Dsysprofd=bundled \ > -Dsystemdunitdir=/lib/systemd/system > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Denable_examples=true > -Denable_tests=true -Denable_tools=true -Dsysprofd=bundled > -Dsystemdunitdir=/lib/systemd/system > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "sysprofd" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:49:15.125639 > Main binary: /usr/bin/python3 > Build Options: -Denable_examples=true -Denable_tests=true -Denable_tools=true > -Dsysprofd=bundled -Dsystemdunitdir=/lib/systemd/system -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "sysprofd" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Denable_examples=true > -Denable_tests=true -Denable_tools=true -Dsysprofd=bundled > -Dsystemdunitdir=/lib/systemd/system returned exit code 1 > make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/sysprof_3.40.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#998595: pyqwt3d: FTBFS: SIP failed to generate the C++ code.
Source: pyqwt3d
Version: 0.1.8-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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
> export QTDIR=/usr/share/qt5
> set -e ;\
> for py in 3.9 ; do \
> mkdir -p build/py$py-qt5; \
> cp -Rl `ls . |grep -v build|grep -v debian` build/py$py-qt5; \
> (cd build/py$py-qt5/configure;\
> python$py configure-qt5.py -5 -I /usr/include/qwtplot3d
> --extra-libs=qwtplot3d-qt5 \
>
> --sip-include-dirs=/usr/lib/python3/dist-packages/PyQt5/bindings/ \
> -D GL2PS_HAVE_ZLIB); \
> done
> sip: Deprecation warning: ../sip/OpenGL_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: Deprecation warning: ../sip/Qwt3D_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: /usr/lib/python3/dist-packages/PyQt5/bindings//QtCore/QtCoremod.sip:23:
> syntax error
> Command line options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': [],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '',
> 'modules': [],
> 'qt': 5,
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip',
> '-I /usr/lib/python3/dist-packages/PyQt5/bindings/'],
> 'subdirs': [],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> Found SIP-4.19.25.
>
> Found 'posix' operating system:
> 3.9.7 (default, Sep 24 2021, 09:43:00)
> [GCC 10.3.0]
>
> Found NumPy-1.19.5.
>
> Setup the OpenGL package build.
> -n PyQt5.sip -t Qt_5_15_0 -t WS_X11
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -b
> '
> 'tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -c tmp-OpenGL_Qt5 '
> '../sip/OpenGL_Qt5_Module.sip')
> Copy tmp-OpenGL_Qt5/sipOpenGLcmodule.cpp -> OpenGL_Qt5/sipOpenGLcmodule.cpp.
> Copy tmp-OpenGL_Qt5/sipAPIOpenGL.h -> OpenGL_Qt5/sipAPIOpenGL.h.
> Copy tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -> OpenGL_Qt5/OpenGL_Qt5.sbf.
> 3 file(s) lazily copied.
> Setup the Qwt3D package build.
> Extended options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': ['-x HAS_QT3 -x HAS_QT4'],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB', 'HAS_NUMPY'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d',
> '/usr/include/python3.9',
> '/usr/lib/python3/dist-packages/numpy/core/include',
> '/usr/include/x86_64-linux-gnu/qt5/Qt',
> '/usr/include/x86_64-linux-gnu/qt5/QtCore',
> '/usr/include/x86_64-linux-gnu/qt5/QtGui',
> '/usr/include/x86_64-linux-gnu/qt5/QtWidgets',
> '/usr/include/x86_64-linux-gnu/qt5/QtOpenGL',
> '/usr/include/x86_64-linux-gnu/qt5'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '/usr/lib/python3.9/dist-packages/PyQt5/Qwt3D',
> 'modules': [],
> 'opengl': 'OpenGL_Qt5',
> 'qt': 5,
> 'qwt3d': 'Qwt3D_Qt5',
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip',
> '-I /usr/lib/python3/dist-packages/PyQt5/bindings/'],
> 'subdirs': ['Qwt3D_Qt5', 'OpenGL_Qt5'],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -b
> '
> 'tmp-Qwt3D_Qt5/qwt3d.sbf -c tmp-Qwt3D_Qt5 -I ../sip -I '
> '/usr/lib/python3/dist-packages/PyQt5/bindings/ -x HAS_QT3 -x HAS_QT4 '
> '../sip/Qwt3D_Qt5_Module.sip')
>
> SIP failed to generate the C++ code.
> make: *** [debian/rules:25: configure-stamp] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/pyqwt3d_0.1.8-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#998594: php-raphf: FTBFS: dh_prep: error: debian/control has a duplicate entry for php-raphf-all-dev
Source: php-raphf Version: 2.0.1+1.1.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > if [ ! -f debian/control-prep ]; then cp debian/control debian/control-prep; > fi > awk '/^Package: php-raphf/,/^$/' debian/control-prep | sed -e > 's/^Architecture: all/Architecture: any/' -e 's/^Package: > php-raphf\(.*\)/Package: php7.4-raphf/' >> debian/control-prep-extra > echo >> debian/control-prep-extra > touch dh_prep-7.4-stamp > echo >> debian/control > awk '/^Package: php-raphf/,/^$/' debian/control-prep | sed -e > 's/^Architecture: any/Architecture: all/' -e 's/^Package: > php-raphf\(.*\)/Package: php-raphf-all-dev/' >> debian/control > echo >> debian/control > cat debian/control-prep-extra >> debian/control > dh_prep > dh_prep: error: debian/control has a duplicate entry for php-raphf-all-dev > make[1]: *** [/usr/share/dh-php/pkg-pecl.mk:77: override_dh_prep] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/php-raphf_2.0.1+1.1.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#998591: bdebstrap: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Source: bdebstrap
Version: 0.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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 bdebstrap
> dpkg-buildpackage: info: source version 0.2.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Benjamin Drung
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: warning: cannot import key in
> bdebstrap-0.2.0/debian/upstream/signing-key.asc since GnuPG is not installed
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building bdebstrap using existing
> ./bdebstrap_0.2.0.orig.tar.xz
> dpkg-source: info: building bdebstrap using existing
> ./bdebstrap_0.2.0.orig.tar.xz.asc
> gpgv: Signature made Tue Jun 8 13:30:13 2021 UTC
> gpgv:using RSA key E7FAB70B3950275E6DA30975DD8CD5A5DE8C7E7A
> gpgv: Can't check signature: No public key
> dpkg-source: warning: failed to verify signature on
> ./bdebstrap_0.2.0.orig.tar.xz.asc
> dpkg-source: info: building bdebstrap in bdebstrap_0.2.0-1.debian.tar.xz
> dpkg-source: info: building bdebstrap in bdebstrap_0.2.0-1.dsc
> debian/rules binary
> dh binary --buildsystem pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running doc
> running command: pandoc -s -t man bdebstrap.1.md -o bdebstrap.1
> running build_scripts
> creating build
> creating build/scripts-3.9
> copying and adjusting bdebstrap -> build/scripts-3.9
> changing mode of build/scripts-3.9/bdebstrap from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m unittest discover -v -s /<>
> test_black (tests.test_black.BlackTestCase)
> Test: Run black code formatter on Python source code. ... Running following
> command:
> black --check --diff -l 99 /<>/bdebstrap tests
> /<>/setup.py
> ok
> test_debug (tests.test_config.TestArguments)
> Test --debug argument parsing. ... ok
> test_empty_args (tests.test_config.TestArguments)
> Test setting arguments to empty strings. ...
> /usr/lib/python3.9/unittest/case.py:1132: DeprecationWarning:
> assertDictContainsSubset is deprecated
> warnings.warn('assertDictContainsSubset is deprecated',
> ok
> test_malformed_env (tests.test_config.TestArguments)
> Test malformed --env parameter (missing equal sign). ... usage: python3.9 -m
> unittest [-h] [-c CONFIG] [-n NAME] [-e ENV] [-s]
> [-b OUTPUT_BASE_DIR] [-o OUTPUT] [-q] [-v]
> [--debug] [-f] [-t TMPDIR]
> [--variant
> {extract,custom,essential,apt,required,minbase,buildd,important,debootstrap,-,standard}]
> [--mode
> {auto,sudo,root,unshare,fakeroot,fakechroot,proot,chrootless}]
> [--aptopt APTOPT] [--keyring KEYRING]
> [--dpkgopt DPKGOPT] [--hostname HOSTNAME]
> [--install-recommends] [--packages PACKAGES]
> [--components COMPONENTS]
> [--architectures ARCHITECTURES]
> [--setup-hook COMMAND] [--essential-hook COMMAND]
> [--customize-hook COMMAND]
> [--cleanup-hook COMMAND] [--suite SUITE]
> [--target TARGET] [--mirrors MIRRORS]
> [suite] [target] [mirrors ...]
> python3.9 -m unittest: error: Failed to parse --env 'invalid'. It needs to be
> in
Bug#998592: glade: FTBFS: dpkg-gensymbols: error: some libraries disappeared in the symbols file: libgladegtk.so libgladegjs.so libgladewebkit2gtk.so libgladepython.so
Source: glade Version: 3.38.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_missing -X/usr/share/gettext/ > make[1]: Leaving directory '/<>' >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: error: some libraries disappeared in the symbols file: > libgladegtk.so libgladegjs.so libgladewebkit2gtk.so libgladepython.so > dpkg-gensymbols: warning: debian/libgladeui-2-13/DEBIAN/symbols doesn't match > completely debian/libgladeui-2-13.symbols > --- debian/libgladeui-2-13.symbols (libgladeui-2-13_3.38.2-5_amd64) > +++ dpkg-gensymbolsXoDJl2 2021-11-04 09:33:07.308208929 + > @@ -1,625 +1,3 @@ > -libgladegjs.so libgladeui-2-13 #MINVER# > - glade_gjs_init@Base 3.38.1 > -libgladegtk.so libgladeui-2-13 #MINVER# > - _glade_gtk_get_resource@Base 3.16.1 > - accel_cleared@Base 3.14.0 > - accel_edited@Base 3.14.0 > - empty@Base 3.14.0 > - glade_about_dialog_editor_get_type@Base 3.16.1 > - glade_about_dialog_editor_new@Base 3.16.1 > - glade_accel_glist_get_type@Base 3.14.0 > - glade_accel_list_copy@Base 3.14.0 > - glade_accel_list_free@Base 3.14.0 > - glade_accel_read@Base 3.14.0 > - glade_accel_write@Base 3.14.0 > - glade_accels_make_string@Base 3.14.0 > - glade_action_bar_editor_get_type@Base 3.20.0 > - glade_action_bar_editor_new@Base 3.20.0 > - glade_action_editor_get_type@Base 3.16.1 > - glade_action_editor_new@Base 3.16.1 > - glade_action_editor_post_create@Base 3.16.1 > - glade_activatable_editor_get_type@Base 3.14.0 > - glade_activatable_editor_new@Base 3.14.0 > - glade_app_chooser_button_editor_get_type@Base 3.16.1 > - glade_app_chooser_button_editor_new@Base 3.16.1 > - glade_app_chooser_widget_editor_get_type@Base 3.16.1 > - glade_app_chooser_widget_editor_new@Base 3.16.1 > - glade_arrow_editor_get_type@Base 3.16.1 > - glade_arrow_editor_new@Base 3.16.1 > - glade_attr_glist_get_type@Base 3.14.0 > - glade_attr_list_free@Base 3.14.0 > - glade_box_editor_get_type@Base 3.16.1 > - glade_box_editor_new@Base 3.16.1 > - glade_button_editor_get_type@Base 3.14.0 > - glade_button_editor_new@Base 3.14.0 > - glade_button_editor_post_create@Base 3.16.1 > - glade_cell_renderer_editor_get_type@Base 3.14.0 > - glade_cell_renderer_editor_new@Base 3.14.0 > - glade_cell_renderer_get_model@Base 3.14.0 > - glade_column_list_copy@Base 3.14.0 > - glade_column_list_find_column@Base 3.14.0 > - glade_column_list_free@Base 3.14.0 > - glade_column_type_free@Base 3.14.0 > - glade_column_type_list_get_type@Base 3.14.0 > - glade_column_type_new@Base 3.14.0 > - glade_combo_box_editor_get_type@Base 3.16.1 > - glade_combo_box_editor_new@Base 3.16.1 > - glade_combo_box_text_editor_get_type@Base 3.16.1 > - glade_combo_box_text_editor_new@Base 3.16.1 > - glade_entry_editor_get_type@Base 3.14.0 > - glade_entry_editor_new@Base 3.14.0 > - glade_entry_editor_post_create@Base 3.16.1 > - glade_eprop_accel_get_type@Base 3.14.0 > - glade_eprop_attrs_get_type@Base 3.14.0 > - glade_eprop_cell_attribute_get_type@Base 3.14.0 > - glade_eprop_column_types_get_type@Base 3.14.0 > - glade_eprop_enum_int_get_type@Base 3.22.0 > - glade_eprop_enum_int_new@Base 3.22.0 > - glade_eprop_icon_sources_get_type@Base 3.14.0 > - glade_eprop_model_data_get_type@Base 3.14.0 > - glade_eprop_string_list_get_type@Base 3.14.0 > - glade_eprop_string_list_new@Base 3.14.0 > - glade_file_chooser_button_editor_get_type@Base 3.16.1 > - glade_file_chooser_button_editor_new@Base 3.16.1 > - glade_file_chooser_dialog_editor_get_type@Base 3.16.1 > - glade_file_chooser_dialog_editor_new@Base 3.16.1 > - glade_file_chooser_editor_get_type@Base 3.16.1 > - glade_file_chooser_editor_new@Base 3.16.1 > - glade_file_chooser_widget_editor_get_type@Base 3.16.1 > - glade_file_chooser_widget_editor_new@Base 3.16.1 > - glade_fixed_get_type@Base 3.14.0 > - glade_font_button_editor_get_type@Base 3.16.1 > - glade_font_button_editor_new@Base 3.16.1 > - glade_font_chooser_dialog_editor_get_type@Base 3.16.1 > - glade_font_chooser_dialog_editor_new@Base 3.16.1 > - glade_font_chooser_editor_get_type@Base 3.16.1 > - glade_font_chooser_editor_new@Base 3.16.1 > - glade_font_chooser_widget_editor_get_type@Base 3.16.1 > - glade_font_chooser_widget_editor_new@Base 3.16.1 > - glade_grid_editor_get_type@Base 3.16.1 > - glade_grid_editor_new@Base 3.16.1 > - glade_gtk_about_dialog_read_widget@Base 3.16.1 > - glade_gtk_about_dialog_set_property@Base 3.16.1 > - glade_gtk_action_action_activate@Base 3.14.0 > - glade_gtk_action_
Bug#998593: arch-test: FTBFS: win64.o:fake:(.text+0x27): relocation truncated to fit: R_X86_64_32S against `.data'
Source: arch-test Version: 0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > x86_64-linux-gnu-as --64 amd64.s -o amd64.o > x86_64-linux-gnu-as --x32 x32.s -o x32.o > x86_64-linux-gnu-as --32 i386.s -o i386.o > i686-w64-mingw32-as win32.s -o win32.o > x86_64-linux-gnu-ld -melf_x86_64 -s amd64.o -o arch-test-amd64 > x86_64-linux-gnu-ld -melf32_x86_64 -s x32.o -o arch-test-x32 > x86_64-linux-gnu-ld -melf_i386 -s i386.o -o arch-test-i386 > i686-w64-mingw32-ld -s win32.o -lkernel32 -o arch-test-win32 > x86_64-w64-mingw32-as win64.s -o win64.o > mips64el-linux-gnuabi64-as -32 -EB mips.s -o mips.o > mips64el-linux-gnuabi64-as -32 -EL mips.s -o mipsel.o > x86_64-w64-mingw32-ld -s win64.o -lkernel32 -o arch-test-win64 > mips64el-linux-gnuabi64-as -n32 -EB mipsn32.s -o mipsn32.o > mips64el-linux-gnuabi64-ld -melf32btsmip -s mips.o -o arch-test-mips > mips64el-linux-gnuabi64-ld -melf32ltsmip -s mipsel.o -o arch-test-mipsel > win64.o:fake:(.text+0x27): relocation truncated to fit: R_X86_64_32S against > `.data' > make[1]: *** [Makefile:65: arch-test-win64] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/arch-test_0.17-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#998590: frogr: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "warnlevel"
Source: frogr Version: 1.6-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "warnlevel" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:50:21.622250 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlibexecdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "warnlevel" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu returned exit code 1 > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/frogr_1.6-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#998588: pyopencl: FTBFS: dh_sphinxdoc: error: debian/python-pyopencl-doc/usr/share/doc/python-pyopencl-doc/html/_static/clipboard.min.js is missing
Source: pyopencl
Version: 2021.2.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- -s custom --test-args="PYTHONPATH={build_dir} cp -r
> {dir}/test {build_dir} && cd {build_dir}/test && {interpreter} -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf {build_dir}/test"
> pybuild --test --test-pytest -i python{version} -p 3.9 -s custom
> "--test-args=PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test"
> D: pybuild pybuild:569: version: 5.20211022.1
> D: pybuild pybuild:570: ['/usr/bin/pybuild', '--test', '--test-pytest', '-i',
> 'python{version}', '-p', '3.9', '-s', 'custom',
> "--test-args=PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test"]
> D: pybuild pybuild:36: cfg: Namespace(verbose=True, quiet=False,
> really_quiet=False, detect_only=False, clean_only=False,
> configure_only=False, build_only=False, install_only=False, test_only=True,
> list_systems=False, print_args=None, before_clean=None, clean_args=None,
> after_clean=None, before_configure=None, configure_args=None,
> after_configure=None, before_build=None, build_args=None, after_build=None,
> before_install=None, install_args=None, after_install=None, before_test=None,
> test_args="PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test", after_test=None,
> test_nose=False, test_nose2=False, test_pytest=True, test_tox=False,
> dir='/<>', destdir='debian/tmp', ext_destdir=None,
> ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None,
> install_dir=None, name=None, system='custom', versions=['3.9'],
> interpreter=['python{version}'], disable=None, custom_tests=True)
> D: pybuild __init__:36: cannot initialize 'cmake' plugin
> Traceback (most recent call last):
> File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in
> module.BuildSystem.is_usable()
> File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
> raise Exception("missing command: %s" % command)
> Exception: missing command: cmake
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild pybuild:132: detected build system: custom (certainty: 99%)
> I: pybuild base:232: PYTHONPATH=/<>/.pybuild/cpython3_3.9/build
> cp -r /<>/test /<>/.pybuild/cpython3_3.9/build &&
> cd /<>/.pybuild/cpython3_3.9/build/test && python3.9 -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf
> /<>/.pybuild/cpython3_3.9/build/test
> D: pybuild tools:232: invoking:
> PYTHONPATH=/<>/.pybuild/cpython3_3.9/build cp -r
> /<>/test /<>/.pybuild/cpython3_3.9/build && cd
> /<>/.pybuild/cpython3_3.9/build/test && python3.9 -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf
> /<>/.pybuild/cpython3_3.9/build/test
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> collecting ... collected 258 items / 1 deselected / 257 selected
>
> test_algorithm.py::test_elwise_kernel[ 'pthread-Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz' on 'Portable
> Computing Language'>>] PASSED [ 0%]
> test_algorithm.py::test_elwise_kernel_with_options[ 'Portable Computing Language'>>] PASSED [ 0%]
> test_algorithm.py::test_ranged_elwise_kernel[ 'Portable Computing Language'>>] PASSED [ 1%]
> test_algorithm.py::test_take[ 'pthread-Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz' on 'Portable
> Computing Language'>>] PASSED [ 1%]
> test_algorithm.py::test_arange[ 'pth
Bug#998587: isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: isoquery Version: 3.2.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 /<>/debian/tmpdir/locale > localedef -i de_DE -f UTF-8 /<>/debian/tmpdir/locale/de_DE.UTF-8 > LOCPATH=/<>/debian/tmpdir/locale LANG=de LC_ALL=de_DE.UTF-8 > dh_auto_test > make -j4 check VERBOSE=1 > make[2]: Verzeichnis „/<>“ wird betreten > Making check in po > make[3]: Verzeichnis „/<>/po“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/po“ wird verlassen > Making check in src > make[3]: Verzeichnis „/<>/src“ wird betreten > make[3]: Für das Ziel „check“ ist nichts zu tun. > make[3]: Verzeichnis „/<>/src“ wird verlassen > Making check in tests > make[3]: Verzeichnis „/<>/tests“ wird betreten > make check-am > make[4]: Verzeichnis „/<>/tests“ wird betreten > make options integration\ > > make[5]: Verzeichnis „/<>/tests“ wird betreten > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.5\" -DPACKAGE_STRING=\"isoquery\ 3.2.5\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.5\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -I../src -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -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 > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o options.o > options.c > gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" > -DPACKAGE_VERSION=\"3.2.5\" -DPACKAGE_STRING=\"isoquery\ 3.2.5\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" > -DVERSION=\"3.2.5\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 > -DGETTEXT_PACKAGE=\"isoquery\" -I. -DTESTDIR=\".\" -I../src > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread > -I/usr/include/json-glib-1.0 -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 > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > integration-integration.o `test -f 'integration.c' || echo './'`integration.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o integration > integration-integration.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 > -lglib-2.0 ../src/options.o > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o options > options.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 > ../src/options.o > make[5]: Verzeichnis „/<>/tests“ wird verlassen > make check-TESTS > make[5]: Verzeichnis „/<>/tests“ wird betreten > make[6]: Verzeichnis „/<>/tests“ wird betreten > PASS: options 1 /options/standard_default > PASS: options 2 /options/standard_provided > PASS: options 3 /options/standard_deprecated_639 > PASS: options 4 /options/standard_deprecated_3166 > PASS: options 5 /options/standard_invalid > PASS: options 6 /options/pathname_default > PASS: options 7 /options/pathname_provided > PASS: options 8 /options/pathname_provided_with_dir_separator > PASS: options 9 /options/pathname_from_standard > PASS: options 10 /options/name_default > PASS: options 11 /options/name_name > PASS: options 12 /options/name_official_name > PASS: options 13 /options/name_common_name > PASS: options 14 /options/null_separator > PASS: options 15 /options/invalid_option > PASS: integration 1 /integration/iso_639-2/all_localized > PASS: integration 2 /integration/iso_639-2/all_null_separator > PASS: integration 3 /integration/iso_639-2/all > PASS: integration 4 /integration/iso_639-2/multiple_codes > PASS: integration 5 /integration/iso_639-3/all_localized > PASS: integration 6 /integration/iso_639-3/all_null_separator > PASS: integration 7 /integration/iso_639-3/all > PASS: integration 8 /integratio
Bug#998589: gnome-shell: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "bash_completion"
Source: gnome-shell Version: 41.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > --libdir=/usr/lib \ > -Dbash_completion=true \ > -Dnetworkmanager=true -Dsoup2=true -Dsystemd=true -Dtests=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu --libdir=/usr/lib > -Dbash_completion=true -Dnetworkmanager=true -Dsoup2=true -Dsystemd=true > -Dtests=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "bash_completion" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:42:32.646170 > Main binary: /usr/bin/python3 > Build Options: -Dbash_completion=true -Dnetworkmanager=true -Dsoup2=true > -Dsystemd=true -Dtests=true -Dprefix=/usr -Dlibdir=/usr/lib > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "bash_completion" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu --libdir=/usr/lib > -Dbash_completion=true -Dnetworkmanager=true -Dsoup2=true -Dsystemd=true > -Dtests=true returned exit code 1 > make[1]: *** [debian/rules:25: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gnome-shell_41.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#998586: libgxps: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg"
Source: libgxps Version: 0.3.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > -Denable-gtk-doc=true \ > -Denable-man=true \ > -Dwith-liblcms2=true \ > -Dwith-libgjpeg=true \ > -Dwith-libtiff=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu -Denable-gtk-doc=true -Denable-man=true > -Dwith-liblcms2=true -Dwith-libgjpeg=true -Dwith-libtiff=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:50:11.272690 > Main binary: /usr/bin/python3 > Build Options: -Denable-gtk-doc=true -Denable-man=true -Dwith-liblcms2=true > -Dwith-libgjpeg=true -Dwith-libtiff=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlibexecdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "with-libgjpeg" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > --libexecdir=lib/x86_64-linux-gnu -Denable-gtk-doc=true -Denable-man=true > -Dwith-liblcms2=true -Dwith-libgjpeg=true -Dwith-libtiff=true returned exit > code 1 > make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/libgxps_0.3.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#998585: pillow: FTBFS: /<>/docs/deprecations.rst:105: WARNING: Unknown directive type "versionremoved".
Source: pillow Version: 8.3.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>/docs' > sphinx-build -b html -W --keep-going -d _build/doctrees . _build/html > Running Sphinx v4.2.0 > making output directory... done > loading intersphinx inventory from https://docs.python.org/3/objects.inv... > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 93 source files that are out of date > updating environment: [new config] 93 added, 0 changed, 0 removed > reading sources... [ 1%] PIL > reading sources... [ 2%] about > reading sources... [ 3%] deprecations > reading sources... [ 4%] handbook/appendices > reading sources... [ 5%] handbook/concepts > reading sources... [ 6%] handbook/image-file-formats > reading sources... [ 7%] handbook/index > reading sources... [ 8%] handbook/overview > reading sources... [ 9%] handbook/text-anchors > reading sources... [ 10%] handbook/tutorial > reading sources... [ 11%] handbook/writing-your-own-file-decoder > reading sources... [ 12%] index > reading sources... [ 13%] installation > reading sources... [ 15%] porting > reading sources... [ 16%] reference/ExifTags > reading sources... [ 17%] reference/Image > reading sources... [ 18%] reference/ImageChops > reading sources... [ 19%] reference/ImageCms > reading sources... [ 20%] reference/ImageColor > reading sources... [ 21%] reference/ImageDraw > reading sources... [ 22%] reference/ImageEnhance > reading sources... [ 23%] reference/ImageFile > reading sources... [ 24%] reference/ImageFilter > reading sources... [ 25%] reference/ImageFont > reading sources... [ 26%] reference/ImageGrab > reading sources... [ 27%] reference/ImageMath > reading sources... [ 29%] reference/ImageMorph > reading sources... [ 30%] reference/ImageOps > reading sources... [ 31%] reference/ImagePalette > reading sources... [ 32%] reference/ImagePath > reading sources... [ 33%] reference/ImageQt > reading sources... [ 34%] reference/ImageSequence > reading sources... [ 35%] reference/ImageShow > reading sources... [ 36%] reference/ImageStat > reading sources... [ 37%] reference/ImageTk > reading sources... [ 38%] reference/ImageWin > reading sources... [ 39%] reference/JpegPresets > reading sources... [ 40%] reference/PSDraw > reading sources... [ 41%] reference/PixelAccess > reading sources... [ 43%] reference/PyAccess > reading sources... [ 44%] reference/TiffTags > reading sources... [ 45%] reference/block_allocator > reading sources... [ 46%] reference/c_extension_debugging > reading sources... [ 47%] reference/features > reading sources... [ 48%] reference/index > reading sources... [ 49%] reference/internal_design > reading sources... [ 50%] reference/internal_modules > reading sources... [ 51%] reference/limits > reading sources... [ 52%] reference/open_files > reading sources... [ 53%] reference/plugins > reading sources... [ 54%] releasenotes/2.7.0 > reading sources... [ 55%] releasenotes/2.8.0 > reading sources... [ 56%] releasenotes/3.0.0 > reading sources... [ 58%] releasenotes/3.1.0 > reading sources... [ 59%] releasenotes/3.1.1 > reading sources... [ 60%] releasenotes/3.1.2 > reading sources... [ 61%] releasenotes/3.2.0 > reading sources... [ 62%] releasenotes/3.3.0 > reading sources... [ 63%] releasenotes/3.3.2 > reading sources... [ 64%] releasenotes/3.4.0 > reading sources... [ 65%] releasenotes/4.0.0 > reading sources... [ 66%] releasenotes/4.1.0 > reading sources... [ 67%] releasenotes/4.1.1 > reading sources... [ 68%] releasenotes/4.2.0 > reading sources... [ 69%] releasenotes/4.2.1 > reading sources... [ 70%] releasenotes/4.3.0 > reading sources... [ 72%] releasenotes/5.0.0 > reading sources... [ 73%] releasenotes/5.1.0 > reading sources... [ 74%] releasenotes/5.2.0 > reading sources... [ 75%] releasenotes/5.3.0 > reading sources... [ 76%] releasenotes/5.4.0 > reading sources... [ 77%] releasenotes/5.4.1 > reading sources... [ 78%] releasenotes/6.0.0 > reading sources... [ 79%] releasenotes/6.1.0 > reading sources... [ 80%] releasenotes/6.2.0 > reading sources... [ 81%] releasenotes/6.2.1 > reading sources... [ 82%] releasenotes/6.2.2 > reading sources... [ 83%] releasenotes/7.0.0 > reading sources... [ 84%] releasenotes/7.1.0 > reading sources... [ 86%] releasenotes/7.1.1 > reading sources... [ 87%] releasenotes/7.1.2 > reading sources... [ 88%] releasenotes/7.2.0 > reading sources... [ 89%] releasenotes/8.0.0 > reading sources... [ 90%] releasenotes/8.0.1 > re
Bug#998583: orc: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "disable_gtkdoc, disable_tests"
Source: orc Version: 1:0.4.32-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > if test -r /proc/cpuinfo; then \ > cat /proc/cpuinfo; \ > fi > processor : 0 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003005 > cpu MHz : 3102.019 > cache size: 36608 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid: 0 > initial apicid: 0 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp: yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm > constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf > tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe > popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm > 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms > invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd > avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke > bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > swapgs itlb_multihit > bogomips : 4999.98 > clflush size : 64 > cache_alignment : 64 > address sizes : 46 bits physical, 48 bits virtual > power management: > > processor : 1 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003005 > cpu MHz : 3106.629 > cache size: 36608 KB > physical id : 0 > siblings : 4 > core id : 1 > cpu cores : 2 > apicid: 2 > initial apicid: 2 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp: yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm > constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf > tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe > popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm > 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms > invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd > avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke > bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > swapgs itlb_multihit > bogomips : 4999.98 > clflush size : 64 > cache_alignment : 64 > address sizes : 46 bits physical, 48 bits virtual > power management: > > processor : 2 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 > microcode : 0x5003005 > cpu MHz : 3102.941 > cache size: 36608 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 2 > apicid: 1 > initial apicid: 1 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp: yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm > constant_tsc rep_good nopl xtopology nonstop_tsc cpuid aperfmperf > tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe > popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm > 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms > invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd > avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke > bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds > swapgs itlb_multihit > bogomips : 4999.98 > clflush size : 64 > cache_alignment : 64 > address sizes : 46 bits physical, 48 bits virtual > power management: > > processor : 3 > vendor_id : GenuineIntel > cpu family: 6 > model : 85 > model name: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz > stepping : 7 >
Bug#998584: gnome-desktop3: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "desktop-docs"
Source: gnome-desktop3 Version: 41.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- \ > -Dgnome_distributor=Debian \ > -Ddate_in_gnome_version=false \ > -Dgtk_doc=true \ > -Dinstalled_tests=true \ > -Ddesktop-docs=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgnome_distributor=Debian > -Ddate_in_gnome_version=false -Dgtk_doc=true -Dinstalled_tests=true > -Ddesktop-docs=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "desktop-docs" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:44:09.290155 > Main binary: /usr/bin/python3 > Build Options: -Dgnome_distributor=Debian -Ddate_in_gnome_version=false > -Dgtk_doc=true -Dinstalled_tests=true -Ddesktop-docs=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "desktop-docs" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgnome_distributor=Debian > -Ddate_in_gnome_version=false -Dgtk_doc=true -Dinstalled_tests=true > -Ddesktop-docs=true returned exit code 1 > make[1]: *** [debian/rules:20: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/gnome-desktop3_41.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#998582: liquidsoap: FTBFS: build-dependency not installable: libocamlnet-ocaml-dev-2d6s9
Source: liquidsoap Version: 1.4.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: chrpath, debhelper (>= 11), debhelper-compat (= 13), > dh-elpa, dh-ocaml (>= 1.0.1), festival, fonts-liberation, pandoc, > libalsa-ocaml-dev (>= 0.2.1), libao-ocaml-dev (>= 0.2.0), libbjack-ocaml-dev > (>= 0.1.3), libcamlimages-ocaml-dev (>= 4.0.1-6), libcamomile-ocaml-dev (>= > 1.0.0), libcry-ocaml-dev (>= 0.6.0), libdtools-ocaml-dev (>= 0.4.1), > libduppy-ocaml-dev (>= 0.8.0), libfaad-ocaml-dev (>= 0.4.0), > libffmpeg-ocaml-dev (>= 0.2.), libflac-ocaml-dev (>= 0.1.5), > libfrei0r-ocaml-dev (>= 0.1.0), libgavl-ocaml-dev (>= 0.1.4), libgd-ocaml-dev > | libgd-gd2-noxpm-ocaml-dev, libssl-ocaml-dev (>= 0.5.2), > libgstreamer-ocaml-dev (>= 0.3.0), libinotify-ocaml-dev (>= 1.0), > libladspa-ocaml-dev (>= 0.1.4), liblastfm-ocaml-dev (>= 0.3.0), > liblo-ocaml-dev (>= 0.1.2), libmad-ocaml-dev (>= 0.1.4), libmagic-ocaml-dev > (>= 0.6), libmenhir-ocaml-dev, libmm-ocaml-dev (>= 0.5.0), > libmp3lame-ocaml-dev (>= 0.3.2), libogg-ocaml-dev (>= 0.5.0), > libopus-ocaml-dev (>= 0.1.3), libpcre-ocaml-dev, libportaudio-ocaml-dev (>= > 0.2.0), libpulse-ocaml-dev (>= 0.1.2), libsamplerate-ocaml-dev (>= 0.1.1), > libsdl-ocaml-dev, libsedlex-ocaml-dev (>= 2.0), libshine-ocaml-dev (>= > 0.2.0), libsoundtouch-ocaml-dev (>= 0.1.7), libspeex-ocaml-dev (>= 0.2.1), > libtaglib-ocaml-dev (>= 0.3.0), libtheora-ocaml-dev (>= 0.3.1), > libvoaacenc-ocaml-dev, libvorbis-ocaml-dev (>= 0.7.0), libxml-dom-perl, > libxmlplaylist-ocaml-dev (>= 0.1.3), libyojson-ocaml-dev, menhir, > ocaml-findlib, ocaml-nox (>= 4.08), sox, build-essential, fakeroot > Filtered Build-Depends: chrpath, debhelper (>= 11), debhelper-compat (= 13), > dh-elpa, dh-ocaml (>= 1.0.1), festival, fonts-liberation, pandoc, > libalsa-ocaml-dev (>= 0.2.1), libao-ocaml-dev (>= 0.2.0), libbjack-ocaml-dev > (>= 0.1.3), libcamlimages-ocaml-dev (>= 4.0.1-6), libcamomile-ocaml-dev (>= > 1.0.0), libcry-ocaml-dev (>= 0.6.0), libdtools-ocaml-dev (>= 0.4.1), > libduppy-ocaml-dev (>= 0.8.0), libfaad-ocaml-dev (>= 0.4.0), > libffmpeg-ocaml-dev (>= 0.2.), libflac-ocaml-dev (>= 0.1.5), > libfrei0r-ocaml-dev (>= 0.1.0), libgavl-ocaml-dev (>= 0.1.4), > libgd-ocaml-dev, libssl-ocaml-dev (>= 0.5.2), libgstreamer-ocaml-dev (>= > 0.3.0), libinotify-ocaml-dev (>= 1.0), libladspa-ocaml-dev (>= 0.1.4), > liblastfm-ocaml-dev (>= 0.3.0), liblo-ocaml-dev (>= 0.1.2), libmad-ocaml-dev > (>= 0.1.4), libmagic-ocaml-dev (>= 0.6), libmenhir-ocaml-dev, libmm-ocaml-dev > (>= 0.5.0), libmp3lame-ocaml-dev (>= 0.3.2), libogg-ocaml-dev (>= 0.5.0), > libopus-ocaml-dev (>= 0.1.3), libpcre-ocaml-dev, libportaudio-ocaml-dev (>= > 0.2.0), libpulse-ocaml-dev (>= 0.1.2), libsamplerate-ocaml-dev (>= 0.1.1), > libsdl-ocaml-dev, libsedlex-ocaml-dev (>= 2.0), libshine-ocaml-dev (>= > 0.2.0), libsoundtouch-ocaml-dev (>= 0.1.7), libspeex-ocaml-dev (>= 0.2.1), > libtaglib-ocaml-dev (>= 0.3.0), libtheora-ocaml-dev (>= 0.3.1), > libvoaacenc-ocaml-dev, libvorbis-ocaml-dev (>= 0.7.0), libxml-dom-perl, > libxmlplaylist-ocaml-dev (>= 0.1.3), libyojson-ocaml-dev, menhir, > ocaml-findlib, ocaml-nox (>= 4.08), sox, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [805 B] > Get:5 copy:/<>/apt_archive ./ Packages [865 B] > Fetched 2633 B in 0s (258 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situ
Bug#998581: git-imerge: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Source: git-imerge
Version: 1.2.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying gitimerge.py -> /<>/.pybuild/cpython3_3.9/build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; tox -c
> /<>/tox.ini -e py39
> GLOB sdist-make: /<>/setup.py
> py39 create: /<>/.tox/py39
> py39 inst: /<>/.tox/.tmp/package/1/git-imerge-1.2.0.zip
> WARNING: Discarding $PYTHONPATH from environment, to override specify
> PYTHONPATH in 'passenv' in your configuration.
> ERROR: invocation failed (exit code 1), logfile:
> /<>/.tox/py39/log/py39-1.log
> == log start
> ===
> Processing ./.tox/.tmp/package/1/git-imerge-1.2.0.zip
> Building wheels for collected packages: git-imerge
> Building wheel for git-imerge (setup.py): started
> Building wheel for git-imerge (setup.py): finished with status 'done'
> Created wheel for git-imerge: filename=git_imerge-1.2.0-py3-none-any.whl
> size=46148
> sha256=7580367737395e578c734b21b743c98ede824eb5fdd701a0b6cdbfd688654e7f
> Stored in directory:
> /<>/.pybuild/cpython3_3.9/.cache/pip/wheels/0e/d9/2d/d731ccabd2ae79f6f1169113cdb0165308d006796409d4bc3b
> Successfully built git-imerge
> Installing collected packages: git-imerge
> ERROR: Could not install packages due to an EnvironmentError: [Errno 13]
> Permission denied: '/usr/lib/python3.9/dist-packages'
> Consider using the `--user` option or check the permissions.
>
>
> === log end
>
> ___ summary
>
> ERROR: py39: InvocationError for command
> /<>/.tox/py39/bin/python -m pip install --exists-action w
> .tox/.tmp/package/1/git-imerge-1.2.0.zip (exited with code 1)
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.9/build; tox -c /<>/tox.ini
> -e py39
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/git-imerge_1.2.0-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#998579: gnome-connections: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 1
Source: gnome-connections
Version: 41.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-connections
> Project version: 41.1
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10)
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.37
> Vala compiler for the host machine: valac (valac 0.54.2)
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Configuring config.h.in using configuration
> Program /usr/bin/meson found: YES (/usr/bin/meson)
> Configuring org.gnome.Connections.desktop.in using configuration
> Program desktop-file-validate found: YES (/usr/bin/desktop-file-validate)
> Program appstream-util found: YES (/usr/bin/appstream-util)
> Configuring org.gnome.Connections.service using configuration
> Program glib-compile-schemas found: YES (/usr/bin/glib-compile-schemas)
> Library config found: YES
> Library m found: YES
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.0
> Run-time dependency gtk+-3.0 found: YES 3.24.30
> Run-time dependency gtk-vnc-2.0 found: YES 1.0.0
> Run-time dependency libhandy-1 found: YES 1.4.0
> Run-time dependency libxml-2.0 found: YES 2.9.12
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency gtk-frdp-0.1 found: NO (tried pkgconfig and cmake)
>
> Executing subproject gtk-frdp
>
> gtk-frdp| Project name: gtk-frdp
> gtk-frdp| Project version: 0.1.0
> gtk-frdp| C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian
> 11.2.0-10) 11.2.0")
> gtk-frdp| C linker for the host machine: cc ld.bfd 2.37
> gtk-frdp| Vala compiler for the host machine: valac (valac 0.54.2)
> gtk-frdp| Configuring gtk-frdp-config.h using configuration
> gtk-frdp| WARNING: Project targeting '>= 0.40.0' but tried to use feature
> introduced in '0.50.0': install arg in configure_file.
> gtk-frdp| Configuring gtk-frdp-version.h using configuration
> gtk-frdp| Run-time dependency winpr2 found: YES 2.3.0
> gtk-frdp| Run-time dependency freerdp2 found: YES 2.3.0
> gtk-frdp| Dependency gio-2.0 found: YES 2.70.0 (cached)
> gtk-frdp| Dependency gtk+-3.0 found: YES 3.24.30 (cached)
> gtk-frdp| Library m found: YES
> gtk-frdp| Run-time dependency gobject-introspection-1.0 found: YES 1.70.0
> gtk-frdp| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> gtk-frdp| Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> gtk-frdp| Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached)
> gtk-frdp| Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> gtk-frdp| Program vapigen found: YES (/usr/bin/vapigen)
> gtk-frdp| Build targets in project: 9
> gtk-frdp| WARNING: Project specifies a minimum meson_version '>= 0.40.0' but
> uses features which were added in newer versions:
> gtk-frdp| * 0.50.0: {'install arg in configure_file'}
> gtk-frdp| Subproject gtk-frdp finished.
>
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Program build-aux/meson/postinstall.py found: YES
> (/<>/build-aux/meson/postinstall.py)
> Build targets in project: 56
>
> gnome-connections 41.1
>
> Subprojects
> gtk-frdp : YES 2 warnings
>
> User defined options
> buildtype: plain
> libdir : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix : /usr
> sysconfdir : /etc
> wrap_mode: nodownload
>
> Found ninja-1.10.1 at /usr/bin/ninja
>dh_auto_build
> cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
> [1/76] /usr/bin/meson --internal vcstagger config.h.in config.h ''
> /<> @VCS_TAG@ '(.*)' /<>/git rev-parse --short HEAD
> [2/76] /usr/bin/meson --internal msgfmthelper
> data/org.gnome.Connections.desktop.in data/org.gnome.Connections.desktop
> desktop ../data/../po
> [3/76] /usr/bin/meson --internal msgfmthelper
> ../data/org.gnome.Connections.appdata.xml.in
> data/org.gnome.Connections.appdata.xml x
Bug#998580: mako-notifier: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "apparmor"
Source: mako-notifier Version: 1.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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_configure -- -Dzsh-completions=true -Dapparmor=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dzsh-completions=true > -Dapparmor=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "apparmor" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:57:41.714983 > Main binary: /usr/bin/python3 > Build Options: -Dzsh-completions=true -Dapparmor=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "apparmor" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dzsh-completions=true > -Dapparmor=true returned exit code 1 > make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/mako-notifier_1.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#998578: packagekit: FTBFS: ../lib/packagekit-glib2/meson.build:49:0: ERROR: Got unknown keyword arguments "install_header"
Source: packagekit Version: 1.2.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cp -dpr /<>/docs/api /<>/docs/api.orig > dh_auto_configure -- -Dpackaging_backend=aptcc -Dsystemd=true > -Doffline_update=true -Dgobject_introspection=true -Dman_pages=true > -Dgtk_doc=true -Dbash_completion=true -Dbash_command_not_found=true > -Dgstreamer_plugin=true -Dgtk_module=true -Dcron=false -Dpython_backend=false > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpackaging_backend=aptcc > -Dsystemd=true -Doffline_update=true -Dgobject_introspection=true > -Dman_pages=true -Dgtk_doc=true -Dbash_completion=true > -Dbash_command_not_found=true -Dgstreamer_plugin=true -Dgtk_module=true > -Dcron=false -Dpython_backend=false > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: PackageKit > Project version: 1.2.2 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency glib-2.0 found: YES 2.70.0 > Run-time dependency gobject-2.0 found: YES 2.70.0 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency gmodule-2.0 found: YES 2.70.0 > Run-time dependency sqlite3 found: YES 3.36.0 > Run-time dependency polkit-gobject-1 found: YES 0.105 > Run-time dependency libsystemd found: YES 249 > Run-time dependency systemd found: YES 249 > Run-time dependency ply-boot-client found: YES 0.9.5 > Checking for function "setpriority" : YES > Checking for function "clearenv" : YES > Has header "unistd.h" : YES > Configuring config.h using configuration > ../meson.build:131: WARNING: Consider using the built-in warning_level option > instead of using "-Wall". > Program /<>/contrib/fix_translations.py found: YES > (/<>/contrib/fix_translations.py) > Configuring org.freedesktop.PackageKit.conf using configuration > Configuring org.freedesktop.PackageKit.service using configuration > Configuring packagekit.service using configuration > Configuring packagekit-offline-update.service using configuration > > ../lib/packagekit-glib2/meson.build:49:0: ERROR: Got unknown keyword > arguments "install_header" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:45:22.492495 > Main binary: /usr/bin/python3 > Build Options: -Dpackaging_backend=aptcc -Dsystemd=true -Doffline_update=true > -Dgobject_introspection=true -Dman_pages=true -Dgtk_doc=true > -Dbash_completion=true -Dbash_command_not_found=true -Dgstreamer_plugin=true > -Dgtk_module=true -Dcron=false -Dpython_backend=false -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: PackageKit > Project version: 1.2.2 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,--as-needed > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFF
Bug#998577: python-dmsh: FTBFS: build-dependency not installable: python3-meshio (< 5)
Source: python-dmsh Version: 0.2.11-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-all, > python3-importlib-metadata, python3-matplotlib, python3-meshplex (>= 0.15.8), > python3-meshplex (<< 0.16), python3-numpy, python3-scipy, python3-setuptools, > python3-wheel, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, > python3-importlib-metadata, python3-matplotlib, python3-meshplex (>= 0.15.8), > python3-meshplex (<< 0.16), python3-numpy, python3-scipy, python3-setuptools, > python3-wheel, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [450 B] > Get:5 copy:/<>/apt_archive ./ Packages [534 B] > Fetched 1941 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-meshplex : Depends: python3-meshio (< 5) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/python-dmsh_0.2.11-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#998576: squeekboard: FTBFS: msgfmt: ../data/../po/LINGUAS does not exist
Source: squeekboard Version: 1.14.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 Cargo.lock > dh build-arch --builddirectory=_build --buildsystem=meson >dh_update_autotools_config -a -O--builddirectory=_build > -O--buildsystem=meson >dh_auto_configure -a -O--builddirectory=_build -O--buildsystem=meson > cd _build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload > --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/_build > Build type: native build > Project name: squeekboard > Project version: 1.14.0 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Rust compiler for the host machine: rustc -C linker=cc (rustc 1.56.0) > Rust linker for the host machine: rustc -C linker=cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > ../meson.build:50: WARNING: Consider using the built-in werror option instead > of using "-Werror". > Message: > -- > squeekboard 1.14.0 > > -- > > Configuring Cargo.toml.base using configuration > Program cat found: YES (/bin/cat) > Program cargo found: YES (/usr/bin/cargo) > Program cargo.sh found: YES (/<>/cargo.sh) > Program cargo_build.py found: YES (/usr/bin/python3 > /<>/cargo_build.py) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Configuring sm.puri.Squeekboard.desktop.in using configuration > DEPRECATION: i18n.merge_file does not take any positional arguments. This > will become a hard error in the next Meson release. > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency wayland-protocols found: YES 1.23 > Program wayland-scanner found: YES (/usr/bin/wayland-scanner) > Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen) > Configuring config.h using configuration > ../src/meson.build:7: WARNING: Got an empty configuration_data() object and > found no substitutions in the input file 'config.h.in'. If you want to copy a > file to the build dir, use the 'copy:' keyword argument added in 0.47.0 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency gnome-desktop-3.0 found: YES 41.0 > Run-time dependency gtk+-3.0 found: YES 3.24.30 > Run-time dependency libfeedback-0.0 found: YES 0.0.0 > Run-time dependency wayland-client found: YES 1.19.0 > Run-time dependency xkbcommon found: YES 1.3.1 > Library m found: YES > Library rt found: YES > Library dl found: YES > Library pthread found: YES > Build targets in project: 11 > > squeekboard 1.14.0 > > User defined options > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > > Found ninja-1.10.1 at /usr/bin/ninja >dh_auto_build -a -O--builddirectory=_build -O--buildsystem=meson > cd _build && LC_ALL=C.UTF-8 ninja -j4 -v > [1/58] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml > --sourcedir ../data --c-name squeekboard --internal --generate --target > data/squeekboard-resources.h > xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint > is not in PATH > [2/58] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml > --sourcedir ../data --c-name squeekboard --internal --generate --target > data/squeekboard-resources.c --dependency-file data/squeekboard-resources.c.d > xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint > is not in PATH > [3/58] /usr/bin/gdbus-codegen --c-generate-autocleanup all --body --output > src/sm.puri.OSK0.c /<>/data/dbus/sm.puri.OSK0.xml > [4/58] /usr/bin/gdbus-codegen --c-generate-autocleanup all --header --output > src/sm.puri.OSK0.h /<>/data/dbus/sm.puri.OSK0.xml > [5/58] /usr/bin/wayland-scanner client-header > //usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml > src/liblibsqueekboard.a.p/xdg-shell-client-protocol.h > [6/58] /usr/bin/wayland-scanner private-code > //usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml > src/liblibsqueekboard.a.p/xdg-shell-protocol.c > [7/58] /usr/b
Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
Source: bind-dyndb-ldap Version: 11.9-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), bind9-dev, libkrb5-dev, > libldap2-dev, libsasl2-dev, uuid-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), bind9-dev, libkrb5-dev, > libldap2-dev, libsasl2-dev, uuid-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [397 B] > Get:5 copy:/<>/apt_archive ./ Packages [481 B] > Fetched 1835 B in 0s (179 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/bind-dyndb-ldap_11.9-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#998574: ionit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Source: ionit
Version: 0.3.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> copying ionit_plugin.py -> /<>/.pybuild/cpython3_3.9/build
> running build_scripts
> creating build
> creating build/scripts-3.9
> copying and adjusting ionit -> build/scripts-3.9
> changing mode of build/scripts-3.9/ionit from 644 to 755
> pandoc -s -t man ionit.1.md -o ionit.1
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m unittest discover -v -s /<>
> test_black (tests.test_black.BlackTestCase)
> Test: Run black code formatter on Python source code. ... Running following
> command:
> black --check --diff -l 99 /<>/ionit tests ionit_plugin.py
> /<>/setup.py
> ok
> test_flake8 (tests.test_flake8.Flake8TestCase)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3.9 -m flake8 --max-line-length=99 /<>/ionit
> tests ionit_plugin.py /<>/setup.py
> ok
> test_collect_function (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/function"]) ... ok
> test_collect_static_context (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/static"]) ... ok
> test_configuration_file (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/static/second.yaml"]) ... ok
> test_context_stacking (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/stacking"]) ... ok
> test_empty_context (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/empty-context"]) ... ok
> test_empty_python_file (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/empty"]) ... ok
> test_ignoring_additional_files (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/additional-file"]) ... ok
> test_invalid_json (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-json"]) ... ok
> test_invalid_python (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-python"]) ... ok
> test_invalid_yaml (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/invalid-yaml"]) ... ok
> test_missing_directory (tests.test_ionit.TestCollectContext)
> Test: Non-existing context directory ... ok
> test_non_dict_context (tests.test_ionit.TestCollectContext)
> Test failure for collect_context(["tests/config/non-dict"]) ... ok
> test_python_module (tests.test_ionit.TestCollectContext)
> Test: Run collect_context(["tests/config/python"]) ... ok
> test_raise_exception (tests.test_ionit.TestCollectContext)
> Test failure for collect_context(["tests/config/exception"]) ... ok
> test_main_default_config (tests.test_ionit.TestMain)
> Test main() with default config ... 2021-11-04 09:54:54,731 ionit INFO:
> Loading Python module 'function' from
> '/<>/tests/config/function/function.py'...
> 2021-11-04 09:54:54,734 ionit INFO: Rendered
> '/<>/tests/template/function/Document.jinja' to
> '/<>/tests/template/function/Document'.
> ok
> test_main_static (tests.test_ionit.TestMain)
> Test main() with static context ... 2021-11-04 09:54:54,735 ionit INFO:
> Reading configuration file
> '/<>/tests/config/static/first.json'...
> 2021-11-04 09:54:54,735 ionit INFO: Reading configuration file
> '/<>/tests/config/static/second.yaml'...
> 2021-11-04 09:54:54,736 ionit INFO: Rendered
> '/<>/tests/template/static/counting.jinja' to
> '/<>/tests/template/static/counting'.
> ok
> test_attribution_error (tests.test_ionit.TestRendering)
> Test: Run render_templates("tests/template/attribution-error") ... ok
> test_missing_context (tests.test_ionit.TestRendering)
> Test: Missing context for render_templates("tests/template/static") ... ok
> test_render_function (tests.test_ionit.TestRendering)
> Test: Run render_templates("tests/template/function") ... 2021-11-04
> 09:54:54,744 ionit INFO: Rendered
> '/<>/tests/template/function/Document.jinja' to
Bug#998573: git-buildpackage: FTBFS: AssertionError: 1 != 0
Source: git-buildpackage Version: 0.9.24 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 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 '/<>' > flake8 > flake8 examples/gbp-add-patch examples/zeitgeist-git.py > export GIT_AUTHOR_NAME="Gbp Tests"; \ > export GIT_AUTHOR_EMAIL=te...@example.com;\ > export GIT_COMMITTER_NAME=$GIT_AUTHOR_NAME; \ > export GIT_COMMITTER_EMAIL=$GIT_AUTHOR_EMAIL; \ > PYTHONPATH=. \ > LC_ALL=C.UTF-8 python3 setup.py nosetests --with-xcoverage > running nosetests > running egg_info > creating gbp.egg-info > writing gbp.egg-info/PKG-INFO > writing dependency_links to gbp.egg-info/dependency_links.txt > writing entry points to gbp.egg-info/entry_points.txt > writing requirements to gbp.egg-info/requires.txt > writing top-level names to gbp.egg-info/top_level.txt > writing manifest file 'gbp.egg-info/SOURCES.txt' > reading manifest file 'gbp.egg-info/SOURCES.txt' > adding license file 'COPYING' > writing manifest file 'gbp.egg-info/SOURCES.txt' > Coverage.py warning: --include is ignored because --source is set > (include-ignored) > Doctest: gbp.command_wrappers.Command.__call__ ... ok > Doctest: gbp.command_wrappers.Command._f ... ok > Doctest: gbp.command_wrappers.Command.call ... ok > Doctest: gbp.config.GbpOptionParser._listify ... ok > Doctest: gbp.config.GbpOptionParser._name_to_filename ... ok > Doctest: gbp.config.GbpOptionParser.get_config_files ... ok > Doctest: gbp.deb.format.DebianSourceFormat ... ok > Doctest: gbp.deb.format.DebianSourceFormat.parse_file ... ok > Doctest: gbp.deb.git.DebianGitRepository._build_legacy_tag ... ok > Doctest: gbp.deb.git.DebianGitRepository._mangle_version ... ok > Doctest: gbp.deb.git.DebianGitRepository._sanitize_version ... ok > Doctest: gbp.deb.git.DebianGitRepository._unsanitize_version ... ok > Doctest: gbp.deb.git.DebianGitRepository.tag_to_version ... ok > Doctest: gbp.deb.git.DebianGitRepository.version_to_tag ... ok > Doctest: gbp.deb.policy.DebianPkgPolicy ... ok > Doctest: gbp.deb.policy.DebianPkgPolicy.build_tarball_name ... ok > Doctest: gbp.deb.uscan.Uscan._parse ... ok > Doctest: gbp.deb.uscan.Uscan._parse_uptodate ... ok > Doctest: gbp.deb.uscan.Uscan._raise_error ... ok > Doctest: gbp.format.format_b ... ok > Doctest: gbp.format.format_str ... ok > Doctest: gbp.git.args.GitArgs ... ok > Doctest: gbp.git.commit.GitCommit.is_sha1 ... ok > Doctest: gbp.git.modifier.GitModifier.get_author_env ... ok > Doctest: gbp.git.modifier.GitModifier.get_committer_env ... ok > Doctest: gbp.git.repository.GitRepository.strip_sha1 ... ok > Doctest: gbp.git.rfc822_date_to_git ... ok > Doctest: gbp.patch_series.Patch._get_subject_from_filename ... ok > Doctest: gbp.patch_series.PatchSeries._get_topic ... ok > Doctest: gbp.patch_series.PatchSeries._parse_line ... ok > Doctest: gbp.patch_series.PatchSeries._read_series ... ok > Doctest: gbp.patch_series.PatchSeries._split_strip ... ok > Doctest: gbp.patch_series.PatchSeries._strip_comment ... ok > Doctest: gbp.pkg.archive.Archive.parse_filename ... ok > Doctest: gbp.pkg.compressor.Compressor.__repr__ ... ok > Doctest: gbp.pkg.compressor.Compressor.cmdline ... ok > Doctest: gbp.pkg.git.PkgGitRepository.sanitize_prefix ... ok > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.guess_upstream_src_version ... ok > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_packagename ... ok > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.is_valid_upstreamversion ... ok > Doctest: gbp.pkg.pkgpolicy.PkgPolicy.version_subst ... ok > Doctest: gbp.rpm.git.RpmGitRepository._sanitize_tag ... ok > Doctest: gbp.rpm.git.RpmGitRepository.version_to_tag ... ok > Doctest: gbp.rpm.linkedlist.LinkedList.append ... ok > Doctest: gbp.rpm.linkedlist.LinkedList.delete ... ok > Doctest: gbp.rpm.linkedlist.LinkedList.insert_after ... ok > Doctest: gbp.rpm.linkedlist.LinkedList.insert_before ... ok > Doctest: gbp.rpm.linkedlist.LinkedList.prepend ... ok > Doctest: gbp.rpm.linkedlist.LinkedListNode.set_data ... ok > Doctest: gbp.rpm.policy.RpmPkgPolicy.is_valid_orig_archive ... ok > Doctest: gbp.rpm.compose_version_str ... ok > Doctest: gbp.rpm.filter_version ... ok > Doctest: gbp.rpm.split_version_str ... ok > Doctest: gbp.rpm.string_to_int ... ok > Doctest: gbp.scripts.buildpackage.changes_file_suffix ... ok > Doctest: gbp.scripts.clone.repo_to_url ... ok > Doctest: gbp.scripts.common.pq.is_pq_branch ... ok > Doctest: gbp.scripts.common.pq.pq_branch_base ... ok > Doctest: gbp.scripts.common.pq.pq_branch_name ... ok > Docte
Bug#998572: pytools: FTBFS: dh_sphinxdoc: error: debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboard.min.js is missing
Source: pytools
Version: 2021.2.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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 '/<>/doc'
> Running Sphinx v4.2.0
> making output directory... done
> loading intersphinx inventory from
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-numpy-doc/html/objects.inv...
> loading intersphinx inventory from
> https://documen.tician.de/pymbolic/objects.inv...
> loading intersphinx inventory from
> https://documen.tician.de/loopy/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://documen.tician.de/pymbolic/objects.inv' not
> fetchable due to :
> HTTPSConnectionPool(host='documen.tician.de', port=443): Max retries exceeded
> with url: /pymbolic/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7fbdd7f0ca30>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://documen.tician.de/loopy/objects.inv' not
> fetchable due to :
> HTTPSConnectionPool(host='documen.tician.de', port=443): Max retries exceeded
> with url: /loopy/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7fbdd7f0cd90>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 8 source files that are out of date
> updating environment: [new config] 8 added, 0 changed, 0 removed
> reading sources... [ 12%] codegen
> reading sources... [ 25%] graph
> reading sources... [ 37%] index
> reading sources... [ 50%] misc
> reading sources... [ 62%] obj_array
> reading sources... [ 75%] persistent_dict
> reading sources... [ 87%] reference
> reading sources... [100%] tag
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 12%] codegen
> writing output... [ 25%] graph
> writing output... [ 37%] index
> writing output... [ 50%] misc
> writing output... [ 62%] obj_array
> writing output... [ 75%] persistent_dict
> writing output... [ 87%] reference
> writing output... [100%] tag
>
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 2 warnings.
>
> The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/doc'
> dh_installdocs
> install -d debian/python3-pytools/usr/share/doc/python3-pytools
> install -d debian/.debhelper/generated/python3-pytools
> cp --reflink=auto -a ./README.rst
> debian/python3-pytools/usr/share/doc/python3-pytools
> chmod -R u\+rw,go=rX debian/python3-pytools/usr/share/doc
> dh_installdocs: warning: Cannot auto-detect main package for
> python-pytools-doc. If the default is wrong, please use --doc-main-package
> install -p -m0644 debian/README.Debian
> debian/python3-pytools/usr/share/doc/python3-pytools/README.Debian
> install -p -m0644 debian/copyright
> debian/python3-pytools/usr/share/doc/python3-pytools/copyright
> install -d debian/python-pytools-doc/usr/share/doc/python-pytools-doc
> install -d debian/.debhelper/generated/python-pytools-doc
> cd './doc/_build/html/..' && find 'html' \( -type f -or -type l \) -and
> ! -empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto
> --parents -dp {}
> /<>/debian/python-pytools-doc/usr/share/doc/python-pytools-doc
> chmod -R u\+rw,go=rX debian/python-pytools-doc/usr/share/doc
> install -p -m0644 debian/copyright
> debian/python-pytools-doc/usr/share/doc/python-pytools-doc/copyright
> install -d debian/python-pytools-doc/usr/share/doc-base/
> install -p -m0644 debian/python-pytools-doc.doc-base
> debian/python-pytools-doc/usr/share/doc-base/python-pytools-doc.python-pytools-doc
> make[1]: Leaving directory '/<>'
>dh_sphinxdoc -O--buildsystem=pybuild
> dh_sphinxdoc: error:
> debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboar
Bug#998571: image-factory: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2
Source: image-factory
Version: 1.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover -v
> test_empty_config (tests.test_cli.TestCLI)
> Test empty configuration file. ... ok
> test_example_config (tests.test_cli.TestCLI)
> Test exapmle image-factory.conf file. ... ok
> test_override_cache_dir (tests.test_cli.TestCLI)
> Test overriding the cache directory. ... ok
> test_flake8 (tests.test_flake8.Flake8TestCase)
> Test: Run flake8 on Python source code. ... Running following command:
> /usr/bin/python3 -m flake8 --max-line-length=99 image-factory tests
> ok
> test_invalid (tests.test_helper.TestParseBytes)
> Test parse_bytes("invalid") ... ok
> test_parse_1_g (tests.test_helper.TestParseBytes)
> Test parse_bytes("1G") ... ok
> test_parse_2_tb (tests.test_helper.TestParseBytes)
> Test parse_bytes("2 TB") ... ok
> test_parse_512_mib (tests.test_helper.TestParseBytes)
> Test parse_bytes("512 MiB") ... ok
> test_pylint (tests.test_pylint.PylintTestCase)
> Test: Run pylint on Python source code. ... Running following command:
> /usr/bin/python3 -m pylint --rcfile=/<>/tests/pylint.conf --
> image-factory tests
> FAIL
> test_chmod_dnf_log (tests.test_sudo_helper.TestSudoHelper)
> Test read access for dnf log file. ... ok
> test_chmod_log_file (tests.test_sudo_helper.TestSudoHelper)
> Test read access for mounted /var/log/... ... ok
> test_chmod_recursive (tests.test_sudo_helper.TestSudoHelper)
> Test chmod recursively ... ok
> test_chmod_remove_root (tests.test_sudo_helper.TestSudoHelper)
> Test chmod remove mounted /root permission ... ok
> test_chmod_root (tests.test_sudo_helper.TestSudoHelper)
> Test chmod mounted /root ... ok
> test_chmod_var_log (tests.test_sudo_helper.TestSudoHelper)
> Test write access for mounted /var/log/... ... ok
> test_mount (tests.test_sudo_helper.TestSudoHelper)
> Test mounting. ... ok
> test_reject_escaping (tests.test_sudo_helper.TestSudoHelper)
> Test rejecting ../../etc/shadow. ... ok
> test_umount (tests.test_sudo_helper.TestSudoHelper)
> Test unmounting. ... ok
>
> ==
> FAIL: test_pylint (tests.test_pylint.PylintTestCase)
> Test: Run pylint on Python source code.
> --
> Traceback (most recent call last):
> File "/<>/tests/test_pylint.py", line 76, in test_pylint
> self.fail("\n".join(msgs))
> AssertionError: pylint found issues:
> * Module image-factory
> image-factory:139:24: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:133:22: R1732: Consider using 'with' for resource-allocating
> operations (consider-using-with)
> image-factory:168:24: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:162:22: R1732: Consider using 'with' for resource-allocating
> operations (consider-using-with)
> image-factory:180:18: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:199:12: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:234:19: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:239:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:242:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:243:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:246:17: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:255:19: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:257:24: C0209: Formatting a regular string which could be a
> f-string (consider-using-f-string)
> image-factory:301:21: W1514: Using open without explicitly specifying an
> encoding (unspecified-encoding)
> image-factory:305:25: W1514: Using open without explicitly specifying an
> encoding (unspecified-encoding)
> image-factory:305:25: R1732: Consider using 'with' for resource-allocating
> operations (consider-using-with)
> image-factory:401:18: R1732: Consider using 'with' for
