Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp
On 8/7/22 11:04 AM, Yadd wrote:
On 06/08/2022 14:59, Nilesh Patra wrote:
Yadd,
Since you added in coffeescript patch for this package, I'd highly appreciate if
you could consider taking a look.
Hi,
is there a test somewhere to see this error ?
I'm not aware of any specific test that could trigger this code unfortunately,
but I can reproduce
it on running shiny-server.
(Sorry for the long procedure)
| # apt install shiny-server
| # cd /srv
| # mkdir -p shiny-server
| # cd shiny-server
| # mkdir covid
| # cd covid
| # wget
https://raw.githubusercontent.com/eebrown/covidprobability_shiny/main/app.R
| # R -e 'install.packages(c("covidprobability", "shinyjs"))'
| # # Start shiny server
| # shiny-server
|
| ===> This will start on localhost:3838. Migrate to localhost:3838/covid,
click on any of the bars and you will see this on terminal
|
| [2022-08-06T23:03:16.777] [INFO] shiny-server - Shiny Server v1.5.19.0
(Node.js v18.6.0)
| [2022-08-06T23:03:16.779] [INFO] shiny-server - Using config file
"/etc/shiny-server/shiny-server.conf"
| [2022-08-06T23:03:16.830] [WARN] shiny-server - Running as root unnecessarily
is a security risk! You could be running more securely as non-root.
| [2022-08-06T23:03:16.836] [INFO] shiny-server - Starting listener on
http://[::]:3838
| [2022-08-06T23:03:33.825] [ERROR] shiny-server - Uncaught exception:
TypeError: Cannot read properties of undefined (reading 'addEventListener')
| [2022-08-06T23:03:33.829] [ERROR] shiny-server - TypeError: Cannot read
properties of undefined (reading 'addEventListener')
| at WebSocketReceiver.setUp
(/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24)
| at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12)
| at new WebSocketReceiver
(/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9)
| at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55)
| at WebSocket.dispatchEvent
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30)
| at WebSocket._open
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10)
| at Hybi.
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49)
| at Hybi.emit (node:events:513:28)
| at Hybi._open
(/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10)
| at Hybi.start
(/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34)
| [2022-08-06T23:03:33.839] [INFO] shiny-server - Stopping listener on
http://[::]:3838
| [2022-08-06T23:03:33.839] [INFO] shiny-server - Shutting down worker
processes (with notification)
| /usr/lib/shiny-server/lib/main.js:391
| throw err;
| ^
|
| TypeError: Cannot read properties of undefined (reading 'addEventListener')
| at WebSocketReceiver.setUp
(/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24)
| at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12)
| at new WebSocketReceiver
(/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9)
| at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55)
| at WebSocket.dispatchEvent
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30)
| at WebSocket._open
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10)
| at Hybi.
(/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49)
| at Hybi.emit (node:events:513:28)
| at Hybi._open
(/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10)
| at Hybi.start
(/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34)
|
| Node.js v18.6.0
--
Best,
Nilesh
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1016282: marked as done (qcoro: FTBFS: qcorosignal.h:225:14: error: ‘((Data**)((char*)&result + offsetof(std::optional >,std::optional >::
Your message dated Sun, 07 Aug 2022 06:03:55 +
with message-id
and subject line Bug#1016282: fixed in qcoro 0.6.0-4
has caused the Debian Bug report #1016282,
regarding qcoro: FTBFS: qcorosignal.h:225:14: error: ‘((Data**)((char*)&result
+ offsetof(std::optional
>,std::optional
>::.std::_Optional_base, false,
false>::_M_payload.std::_Optional_payload, false,
false, false>::.std::_Optional_payload,
true, false,
false>::.std::_Optional_payload_base
>::_M_payload)))[1]’ may be used uninitialized [-Werror=maybe-uninitialized]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qcoro
Version: 0.6.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/build-Qt6/tests/testlibs && /usr/bin/c++ -DQT_CORE_LIB
> -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII
> -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS
> -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_URL_CAST_FROM_STRING
> -DQT_STRICT_ITERATORS
> -DQT_TESTCASE_BUILDDIR=\"/<>/build-Qt6/tests/testlibs\"
> -DQT_TESTCASE_SOURCEDIR=\"/<>/tests/testlibs\" -DQT_TESTLIB_LIB
> -DQT_USE_STRINGBUILDER
> -I/<>/build-Qt6/tests/testlibs/qcoro_test_autogen/include
> -I/<>/tests/testlibs -I/<> -I/<>/qcoro
> -I/<>/qcoro/core -I/<>/build-Qt6/qcoro/core
> -I/<>/build-Qt6/qcoro -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtCore -isystem
> /usr/include/x86_64-linux-gnu/qt6 -isystem
> /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtTest -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror
> -pedantic -fcoroutines -fPIC -pthread -std=gnu++20 -MD -MT
> tests/testlibs/CMakeFiles/qcoro_test.dir/testloop.cpp.o -MF
> CMakeFiles/qcoro_test.dir/testloop.cpp.o.d -o
> CMakeFiles/qcoro_test.dir/testloop.cpp.o -c
> /<>/tests/testlibs/testloop.cpp
> In file included from /<>/qcoro/websockets/qcorowebsocket.cpp:7:
> /<>/qcoro/core/qcorosignal.h: In function ‘void
> qCoroSignalListener<{anonymous}::WebSocketSignalWatcher, void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)>({anonymous}::WebSocketSignalWatcher*, void
> ({anonymous}::WebSocketSignalWatcher::*&&)(std::optional bool> >),
> std::chrono::milliseconds):: void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)>,
> std::default_delete void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)> >
> >)>::operator()(qCoroSignalListener<{anonymous}::WebSocketSignalWatcher, void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)>({anonymous}::WebSocketSignalWatcher*, void
> ({anonymous}::WebSocketSignalWatcher::*&&)(std::optional bool> >),
> std::chrono::milliseconds):: void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)>,
> std::default_delete void
> ({anonymous}::WebSocketSignalWatcher::*)(std::optional bool> >)> >
> >)>::_ZZ19qCoroSignalListenerIN12_GLOBAL__N_122WebSocketSignalWatcherEMS1_FvSt8optionalISt5tupleIJ10QByteArraybEN5QCoro14AsyncGeneratorINS9_6detail16QCoroSignalQueueIT_T0_E11result_type10value_typeEEEPSD_OSE_NSt6chrono8durationIlSt5ratioILl1ELl1000ENKUlSt10unique_ptrINSC_IS1_S8_EESt14default_deleteISR_EEE_clESU_.Frame*)’:
> /<>/qcoro/core/qcorosignal.h:225:14: error:
> ‘((Data**)((char*)&result + offsetof(std::optional bool> >,std::optional
> >::.std::_Optional_base, false,
> false>::_M_payload.std::_Optional_payload,
> false, false, false>::.std::_Optional_payload bool>, true, false,
> false>::.std::_Optional_payload_base
> >::_M_payload)))[1]’ may be used uninitialized [-Werror=maybe-uninitialized]
> 225 | auto result = std::move(mQueue.front());
> | ^~
> /<>/qcoro/core/qcorosignal.h:225:14: error:
> ‘((char**)((char*)&result + offsetof(std::optional bool> >,std::optional
> >::.std::_Optional_base, false,
> false>::_M_payload.std::_Optional_payload,
> false, false, false>::.std::_Optional_payload bool>, true, false,
> false>::.std::_Optional_payload_base
> >::_M_payload)))[2]’ may be used uninitialized [-Werror=maybe-uninitialized]
> [ 34%] Linking CXX shared library libQCoro6Network.so
> cd /<>/build-Qt6/qcoro/network && /usr/bin/cmake -E
>
Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp
On 06/08/2022 14:59, Nilesh Patra wrote: Yadd, Since you added in coffeescript patch for this package, I'd highly appreciate if you could consider taking a look. Hi, is there a test somewhere to see this error ?
Processed: tagging 1016282
Processing commands for cont...@bugs.debian.org: > tags 1016282 + pending Bug #1016282 [src:qcoro] qcoro: FTBFS: qcorosignal.h:225:14: error: ‘((Data**)((char*)&result + offsetof(std::optional >,std::optional >::.std::_Optional_base, false, false>::_M_payload.std::_Optional_payload, false, false, false>::.std::_Optional_payload, true, false, false>::.std::_Optional_payload_base >::_M_payload)))[1]’ may be used uninitialized [-Werror=maybe-uninitialized] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen for bullseye
Processing commands for cont...@bugs.debian.org:
> reopen 1010355
Bug #1010355 {Done: Santiago Vila } [unzip] unzip:
CVE-2022-0529 CVE-2022-0530
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions unzip/6.0-27.
> found 1010355 6.0-21+deb9u2
Bug #1010355 [unzip] unzip: CVE-2022-0529 CVE-2022-0530
Ignoring request to alter found versions of bug #1010355 to the same values
previously set
> fixed 1010355 6.0-27
Bug #1010355 [unzip] unzip: CVE-2022-0529 CVE-2022-0530
Marked as fixed in versions unzip/6.0-27.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016618: marked as done (nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)
Your message dated Sat, 06 Aug 2022 22:50:05 + with message-id and subject line Bug#1016618: fixed in nvidia-graphics-drivers-tesla-450 450.203.03-1 has caused the Debian Bug report #1016618, regarding nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5383 CVE-2022-31607 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer (nvidia.ko), where a local user with basic capabilities can cause improper input validation, which may lead to denial of service, escalation of privileges, data tampering, and limited information disclosure. CVE-2022-31608 NVIDIA GPU Display Driver for Linux contains a vulnerability in an optional D-Bus configuration file, where a local user with basic capabilities can impact protected D-Bus endpoints, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. CVE-2022-31615 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer, where a local user with basic capabilities can cause a null-pointer dereference, which may lead to denial of service. Linux Driver Branch CVE IDs Addressed R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615 Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-450 Source-Version: 450.203.03-1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-450, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-450 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 07 Aug 2022 00:14:36 +0200 Source: nvidia-graphics-drivers-tesla-450 Architecture: source Version: 450.203.03-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1016618 Changes: nvidia-graphics-drivers-tesla-450 (450.203.03-1) unstable; urgency=medium . * New upstream Tesla release 450.203.03 (2022-08-02). * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615. (
Bug#1016748: marked as done (mathcomp-analysis: FTBFS: test failure: Error: apply-w-params)
Your message dated Sat, 06 Aug 2022 21:53:42 + with message-id and subject line Bug#1016748: fixed in mathcomp-analysis 0.5.2-2 has caused the Debian Bug report #1016748, regarding mathcomp-analysis: FTBFS: test failure: Error: apply-w-params to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mathcomp-analysis Version: 0.5.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Rebuilds of mathcomp-analysis failed: COQC theories/realfun.v COQC theories/exp.v COQC theories/lebesgue_measure.v File "./theories/lebesgue_measure.v", line 133, characters 0-76: Warning: Casts are ignored in patterns [cast-in-pattern,automation] File "./theories/lebesgue_measure.v", line 133, characters 0-76: Warning: Casts are ignored in patterns [cast-in-pattern,automation] COQC theories/lebesgue_integral.v COQC theories/trigo.v File "./theories/lebesgue_integral.v", line 201, characters 0-51: Error: apply-w-params make[3]: *** [Makefile.coq:764: theories/lebesgue_integral.vo] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [Makefile.coq:387: all] Error 2 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: mathcomp-analysis Source-Version: 0.5.2-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of mathcomp-analysis, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated mathcomp-analysis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Aug 2022 23:25:50 +0200 Source: mathcomp-analysis Architecture: source Version: 0.5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 1016259 1016748 Changes: mathcomp-analysis (0.5.2-2) unstable; urgency=medium . * Add patch to support more recent elpi versions (Closes: #1016748). * Upload will trigger rebuild (Closes: #1016259). Checksums-Sha1: bd88b3bb31e1d4d7a2bd0af2d005fe14d6c4ce3c 2366 mathcomp-analysis_0.5.2-2.dsc ca301eb5d2f5365f7e35251a18c023884c9a52f9 9008 mathcomp-analysis_0.5.2-2.debian.tar.xz 5b72aa5cd499f6eef5bd71a9f4801ecb8b0de6d5 7901 mathcomp-analysis_0.5.2-2_source.buildinfo Checksums-Sha256: 8ae93b458e65574dde936d7d041ef5bf1250f08bd0b3ad6d978d8b06d4af2c30 2366 mathcomp-analysis_0.5.2-2.dsc 5a784bba5d1e8b9fb17a6b54f5f02de56a1b03eea77832a351778727f67c7c30 9008 mathcomp-analysis_0.5.2-2.debian.tar.xz f91fe02b36918407847a83b6e010a52af7756954506fd41ec0f21d03c9fa9a1b 7901 mathcomp-analysis_0.5.2-2_source.buildinfo Files: 583d557ed9c92fabe2911039282f42a9 2366 ocaml optional mathcomp-analysis_0.5.2-2.dsc 070a708d7c3f897cd803cdc2e9186b57 9008 ocaml optional mathcomp-analysis_0.5.2-2.debian.tar.xz f3f4445625a0f9c9211db52238496375 7901 ocaml optional mathcomp-analysis_0.5.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmLu3LYSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRDtkP/1sid6VGeZfxdIUP7Cqu7neb60zXqMec fIa+w1aXYBTQHd7KizDqmr/iifZ2ZC+Zdxs7F0InZ6IaRi7kymeZ0rMojRKWPE8z dGU0MQbV+r9CDS8+jrvkq6qcA3bTGwoSJy20wXYKdsmfOJsxrpq0qAyhoQNbLaY3 9hqg9RLbwEyoTHSuE89cT8fxi6ninspQE1P6tW/NLofBu68/O38XqAhj3aW5aoab o3Zr4L7X9YCYlXBRZsd81rsIfVKyQwLnaSn0cizUsQ59bc2+oGXqzHyUSgveEa6B +QuNTmyeW5sg0lPMfScVMLAGI1D4QTAgxY+1anxLxI4hmmwxJlaJGk1kd1neGA7j 8+dvOcSgx96U13nInhvhMI4aZKaN3eb4Wyp59aeJK0I1OkfNaDiJ56em6QLmNXKc j/IKleqt1k/L5vNHIF+E5IdeFc+qTbKpsTng3UcbzvsnLfaoO93te+dFh9g0oCpF eE9rwWs9Cw1Yv3vxe9Me9aqzj9IKma7OZJtyKA3IaVVnbHF3WkzeQBPhhpX6DH3p QF6OkKSjlMFO7tkJUXw0RElmi9VE6j6Ifj83b2rvZLoSdsDG2pHn9sa15yJGiDqO tySobPCBRDaT+CYGNGuAN1ARZzeWneddRALan8o74qk25o63TMIzCZMcUBMuXwXB 4rzGvkFPfr7F =jsU7 -END PGP SIGNATURE End Message ---
Bug#1016259: marked as done (mathcomp-analysis: FTBFS: build-dependency not installable: libcoq-elpi-b71f8)
Your message dated Sat, 06 Aug 2022 21:53:42 + with message-id and subject line Bug#1016259: fixed in mathcomp-analysis 0.5.2-2 has caused the Debian Bug report #1016259, regarding mathcomp-analysis: FTBFS: build-dependency not installable: libcoq-elpi-b71f8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mathcomp-analysis Version: 0.5.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: coq, debhelper-compat (= 13), dh-coq, dh-ocaml, > libcoq-elpi, libcoq-elpi-ocaml-dev, libcoq-hierarchy-builder, > libcoq-mathcomp-algebra, libcoq-mathcomp-field, libcoq-mathcomp-fingroup, > libcoq-mathcomp-solvable, libcoq-mathcomp-ssreflect, > libcoq-mathcomp-bigenough, libcoq-mathcomp-finmap, ocaml-dune, > build-essential, fakeroot > Filtered Build-Depends: coq, debhelper-compat (= 13), dh-coq, dh-ocaml, > libcoq-elpi, libcoq-elpi-ocaml-dev, libcoq-hierarchy-builder, > libcoq-mathcomp-algebra, libcoq-mathcomp-field, libcoq-mathcomp-fingroup, > libcoq-mathcomp-solvable, libcoq-mathcomp-ssreflect, > libcoq-mathcomp-bigenough, libcoq-mathcomp-finmap, ocaml-dune, > 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 [464 B] > Get:5 copy:/<>/apt_archive ./ Packages [549 B] > Fetched 1970 B in 0s (80.5 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libcoq-hierarchy-builder : Depends: libcoq-elpi-b71f8 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/2022/07/28/mathcomp-analysis_0.5.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: mathcomp-analysis Source-Version: 0.5.2-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of mathcomp-analysis, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated mathcomp-analysis package) (This message was generated automatically at their request; if you believe that there i
Bug#1014903: marked as done (xorg-server: CVE-2022-2319 CVE-2022-2320)
Your message dated Sat, 06 Aug 2022 21:02:13 + with message-id and subject line Bug#1014903: fixed in xorg-server 2:1.20.11-1+deb11u2 has caused the Debian Bug report #1014903, regarding xorg-server: CVE-2022-2319 CVE-2022-2320 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xorg-server Version: 2:21.1.3-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for xorg-server. CVE-2022-2319[0]: | ZDI-CAN-16062: X.Org Server ProcXkbSetGeometry Out-Of-Bounds Access CVE-2022-2320[1]: | ZDI-CAN-16070: X.Org Server ProcXkbSetDeviceInfo Out-Of-Bounds Access If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-2319 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2319 [1] https://security-tracker.debian.org/tracker/CVE-2022-2320 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2320 [2] https://www.openwall.com/lists/oss-security/2022/07/12/1 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: xorg-server Source-Version: 2:1.20.11-1+deb11u2 Done: Emilio Pozuelo Monfort We believe that the bug you reported is fixed in the latest version of xorg-server, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated xorg-server package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Aug 2022 10:00:36 +0200 Source: xorg-server Architecture: source Version: 2:1.20.11-1+deb11u2 Distribution: bullseye-security Urgency: medium Maintainer: Debian X Strike Force Changed-By: Emilio Pozuelo Monfort Closes: 1014903 Changes: xorg-server (2:1.20.11-1+deb11u2) bullseye-security; urgency=medium . * xkb: add request length validation for XkbSetGeometry (CVE-2022-2319) * xkb: swap XkbSetDeviceInfo and XkbSetDeviceInfoCheck (CVE-2022-2320) * Closes: #1014903. Checksums-Sha1: 5e456e9f0d99de9e4cdb176dd08ca12a93525ba5 4236 xorg-server_1.20.11-1+deb11u2.dsc 470731401c0c828f603b6ac5b92799483bd12eff 9414572 xorg-server_1.20.11.orig.tar.gz 57f5de5088bb7d69872e40126ec43d25ee585a09 165358 xorg-server_1.20.11-1+deb11u2.diff.gz 8125621690dbe010b493c261e8b7360d2dcf8ad4 6933 xorg-server_1.20.11-1+deb11u2_source.buildinfo Checksums-Sha256: f50b59fa629d6e1a0a343361f368817ba228c7418ecd19b7399be49ba4ed7039 4236 xorg-server_1.20.11-1+deb11u2.dsc 4e9341c96f5ed0f6b9491ed732c501303479d3fe21da280c768a1822d7e5d352 9414572 xorg-server_1.20.11.orig.tar.gz 3ea840e7d486a6532c5be47a20bbf6f29d0ff56afe64b9282663904cf353f3ec 165358 xorg-server_1.20.11-1+deb11u2.diff.gz e6626ce9152eeba4d1c69cd8a508333ae3a3821d3330030b3a877787c968a11b 6933 xorg-server_1.20.11-1+deb11u2_source.buildinfo Files: f038696fab61ef7b9d04893c59f8521f 4236 x11 optional xorg-server_1.20.11-1+deb11u2.dsc 86ef76882fabf07028a95a29a3edf032 9414572 x11 optional xorg-server_1.20.11.orig.tar.gz 608aa3f44fd0eef9b1a33a3936fa3ebe 165358 x11 optional xorg-server_1.20.11-1+deb11u2.diff.gz 9fbfc15053edc566421d4d00c7cfd266 6933 x11 optional xorg-server_1.20.11-1+deb11u2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAmLuM04ACgkQnUbEiOQ2 gwISkg//UoqUYDZ04MuOxxDOKbi9qG1J4J2vRV83ATdz5OOOd6huGD86hVdDkzgB X7RtSdbzIoglBVGDt/qq91F4QG3/xKZJEg9EuzWJzbNMECuO+WScJr2MuxbSixbO Iu7hM7bIJyJ5kqkYfJvqapHDnl4TLE4MIfeHCsh82uUc4+WP8hfiRac2NAYeeO3x KC//cAVqMBM9ltSIkBOdUhqey13sU+DMQj5Z8zAqY/Yri3TsLk5wFK4qB3x/qrDK QoWDUrnPEyd33wCZn4sH+726eBlC1bfOoYKDJWJHguwCTIpIzsBXXMsnWPVIbh03 x5ovW8oWWcwmydLYqJ6FD0jMtJrF2mrg7ZaNXYjoCLK24RldqYhVqCpGN6gSwg14 WjeCI2qHc5H+Tt2++z0Y4cAk98K4AsWCeTVe+Z9JdqhS37uMsHpQtKi/3dhahjQq BDN5OGk6qSQJU5nhLcsocpSZ4
Bug#1016342: marked as done (pyscanfcs: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_build] Error 1)
Your message dated Sat, 06 Aug 2022 20:38:24 + with message-id and subject line Bug#1016342: fixed in pyscanfcs 0.3.6+ds-4 has caused the Debian Bug report #1016342, regarding pyscanfcs: FTBFS: make[1]: *** [debian/rules:37: override_dh_auto_build] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyscanfcs Version: 0.3.6+ds-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd doc && \ > faketime -f "2022-07-21 20:00:35+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex \ > faketime -f "2022-07-21 20:00:35+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex && \ > bibtex PyScanFCS_doc.aux && \ > faketime -f "2022-07-21 20:00:35+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex && \ > faketime -f "2022-07-21 20:00:35+00:00" pdflatex -synctex=1 > -interaction=nonstopmode PyScanFCS_doc.tex > This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./PyScanFCS_doc.tex > LaTeX2e <2022-06-01> patch level 5 > L3 programming layer <2022-07-15> > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls > Document Class: scrartcl 2022/07/04 v3.37 KOMA-Script document class (article) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlogo.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize12pt.clo) > (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def)) > (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty > (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def)) > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def) > (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf)) > (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex) > (/usr/share/texlive/texmf-dist/tex/latex/sistyle/sistyle.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty > (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifvtex.sty > (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty > For additional information on amsmath, use the `?' option. > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty) > (/usr/share/texlive/texmf-dist/tex/latex/cite/cite.sty) > (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty) > (/usr/share/texlive/texmf-dist/tex/latex/subfig/subfig.sty > (/usr/share/texlive/texmf-dist/tex/latex/caption/caption.sty > (/usr/share/texlive/texmf-dist/tex/latex/caption/caption3.sty > (/usr/share/texlive/texmf-dist/tex/latex/caption/caption-koma.sto > (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty) > (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx) > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/svgnam.def)) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/
Processed: Re: Bug#1016369: IO::Handle ->error does not work, always saying "fine"
Processing control commands: > severity -1 normal Bug #1016369 [perl] IO::Handle ->error does not work, always saying "fine" Severity set to 'normal' from 'grave' -- 1016369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016369: IO::Handle ->error does not work, always saying "fine"
Control: severity -1 normal Hi, thanks Ian for the report and Damyan for looking into the issues. On Sun, Jul 31, 2022 at 11:37:09AM +0300, Damyan Ivanov wrote: > -=| Ian Jackson, 30.07.2022 13:42:05 +0100 |=- > > Package: perl > > Version: 5.34.0-4 > > Severity: grave > > > > To reproduce > > > > perl -MIO::Handle -e 'open X, "<", "." or die $!; $_ = ; printf "%s > > %s %s\n", X->error(), $!;' > > perl -MIO::Handle -e 'open X, ">", "/dev/full" or die $!; print X 1; > > flush X; printf "%s %s %s\n", X->error(), $!; close X' > > > > Expected output > > > > -1 Bad file descriptor > > -1 No space left on device > > > > Actual output > > > > 0 Bad file descriptor > > 0 No space left on device FWIW I get 0 Is a directory 1 No space left on device on sid (perl_5.34.0-5). I'm not sure why you'd expect -1. The documentation for IO::Handle::error() only mentions it reporting a true value. The first issue (reading a directory as a plain file) seems to be about the error flag getting cleared when reading past EOF or something like that. According to my meager debugger skills, the clearing happens around https://sources.debian.org/src/perl/5.34.0-5/pp_hot.c/#L3278 As Damyan notes, you can detect this by checking for EOF before reading, although perl -MIO::Handle -e 'open X, "<", "." or die $!; $_ = if !X->eof(); printf "%s %s\n", X->error(), $!;' 1 Inappropriate ioctl for device is not quite what I'd expect either. Anyway, the data loss argument seems misplaced given we've read all the data there is when we are at EOF? I can see there is probably a bug around here, but it would be good to have an example test case that doesn't involve treating a directory as a plain file (which can have very varying results between different platforms) before taking this upstream. Particularly so if you want to argue it's as serious as claimed here. See also https://github.com/Perl/perl5/issues/12782 which has not received attention in almost ten years. The second issue (writing to /dev/full) is indeed fixed in sid / Perl 5.34. It was https://github.com/Perl/perl5/issues/6799 and reportedly only affects things like character devices (including /dev/full) and sockets. I've verified that trying to write to a normal file on a full filesystem does set the error() flag on stable / Perl 5.32. I think that makes the issue less severe, and I'm not very inclined to fix it in stable. But in case we end up doing that anyway, these would be the commits needed: https://github.com/Perl/perl5/commit/89341f87f9fc65c4d7133e497bb04586e86b8052 https://github.com/Perl/perl5/commit/8a2562bec7cd9f8eff6812f340f99028bb33 Downgrading the severity, but let me know what you think based on the above. -- Niko
Processed: closing 1016356
Processing commands for cont...@bugs.debian.org: > close 1016356 Bug #1016356 [unpaper] FTBFS: unpaper fails to build against ffmpeg 5.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1016356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1016356 in 7.0.0-0.1
Processing commands for cont...@bugs.debian.org: > fixed 1016356 7.0.0-0.1 Bug #1016356 [unpaper] FTBFS: unpaper fails to build against ffmpeg 5.0 Marked as fixed in versions unpaper/7.0.0-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1004640 to src:unpaper, forcibly merging 1016356 1004640
Processing commands for cont...@bugs.debian.org:
> reassign 1004640 src:unpaper
Bug #1004640 {Done: Nicholas Guriev } [src:unpaper] unpaper:
FTBFS with ffmpeg 5.0
Ignoring request to reassign bug #1004640 to the same package
> forcemerge 1016356 1004640
Bug #1016356 [unpaper] FTBFS: unpaper fails to build against ffmpeg 5.0
Unable to merge bugs because:
package of #1004640 is 'src:unpaper' not 'unpaper'
Failed to forcibly merge 1016356: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004640
1016356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016670: marked as done (libconfig-model-dpkg-perl: autopkgtest failures)
Your message dated Sat, 06 Aug 2022 17:05:18 + with message-id and subject line Bug#1016670: fixed in libconfig-model-dpkg-perl 2.163 has caused the Debian Bug report #1016670, regarding libconfig-model-dpkg-perl: autopkgtest failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libconfig-model-dpkg-perl Version: 2.162 Severity: serious Justification: autopkgtest failures are serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libconfig-model-dpkg-perl fails its autopkgtests both on ci.d.n and locally. (But not the tests during build.) https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libconfig-model-dpkg-perl/24124550/log.gz and copied from a local test: … ok 106 - test debhelper migration In config class 'Dpkg::Control::Source', (location: control source Vcs-Browser) element 'Vcs-Browser' (level normal) has a configuration model error: Compute argument 'pkgname', error with '- Source': Configuration item 'control source Source' has a wrong value: Undefined mandatory value. value is computed from 'use Cwd; my $res = getcwd =~ m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef; ' # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 106. Dubious, test returned 255 (wstat 65280, 0xff00) All 106 subtests passed 2022/08/04 22:40:52 write backend Dpkg Config::Model::Backend::Dpkg::write failed: In config class 'Dpkg', (location: changelog) element 'changelog' (level normal) has a configuration model error: Compute argument 'pkg_name', error with '! control source Source': Configuration item 'control source Source' has a wrong value: Undefined mandatory value. value is computed from 'use Cwd; my $res = getcwd =~ m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef; ' … 2022/08/04 22:40:53 write backend Dpkg::Control Config::Model::Backend::Dpkg::Control::write failed: Configuration item 'control source Source' has a wrong value: Undefined mandatory value. value is computed from 'use Cwd; my $res = getcwd =~ m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef; ' Configuration item 'control source Source' has a wrong value: Undefined mandatory value. value is computed from 'use Cwd; my $res = getcwd =~ m!/([a-z0-9][a-z0-9+.-]+)$! ? $1 : undef; ' # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 1. Dubious, test returned 255 (wstat 65280, 0xff00) All 1 subtests passed … Test Summary Report - --- t/dependency-check.t(Wstat: 65280 Tests: 106 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/dpkg.t(Wstat: 65280 Tests: 1 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output Cheers, gregor - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLsTPZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZYGxAAinz/gSzn2nE8VI2sFIySHIp+S56WyiRKV23chG2dOQ3osq8WDQ9U5Oq1 inJd5xcOmKKmBcZ7weoC8IeLhCrIKPDzvp5/YzDPUkXSMehANBqzJi9baXbZjkUG QTnRmoF4Os7+0PqU9Ji8bQtcWSAeW01SFYRGNWi2dmGAorPAewMSoQ2NF9G+a/4U XtHjdQt2dJd0TFwdK1s/KeKHvE5sGqhLDBzoxb6R9nV7e5zMjDsNTxzG8vuv6qVz qb0mviF+hKEZtKYloiotKY19sxh5ecqhx0GGuADl5jkTXB5Wv9nxSlU3f30oDqN+ Ynjyu78gLTnpWDPSpl58ShXCJRszUPhH3hc04yu3c/moxKn6L3oXkjZoKY/CBi2S dDpFr/x+eXLDYhSFHsLROAm6mZ5CffnAfQYSKE8hQup5f4+9pnB4gxQbDewxsb+l yjfewjTK6mZ3H9CMIX33d+Ai6LLrInr7vZNTIu8mf7YFaZC98mt8S/w/0g95s1/r Ozl5vylt40oEEG4ZftwqW8+Wt1MJG5r2hS3klLzXD85DWiHKDfsT7EE+nEo7P8s7 6ChLhRv0nzYqG9NKwqpYnBxa1/q+ul0MNu5GXTHHUiB4FyxXbZ8jDQZtKwYrVpXp AGoSG1+iChjCNSsPoR9KUxEN0VLH6udgKryRq5Nq+pVbyfEJn4Y= =jaGK -END PGP SIGNATURE- --- End Message
Bug#1016670: marked as pending in libconfig-model-dpkg-perl
Control: tag -1 pending Hello, Bug #1016670 in libconfig-model-dpkg-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libconfig-model-dpkg-perl/-/commit/522848cbf14008062b10b98a7d0a4f5e947465be Test: set Source value when needed Closes: #1016670 Thanks: gregoa for the bug report This bug is related to 1015913 This commit fixes autopkgtest failures. Looks like autopkgtest runs in a directory that cannot be used as default Source value. So Source value remains undef. This is a problem because Source value is mandatory and is used to compute the default value of Vcs-Browser. So when Computation of Vcs-Browser tries to Source, the mandatory check kicks in and exit on error. Here the solution is to set a dummy value before Vcs-Browser is read (which triggers the computation of its default value). (this message was generated automatically) -- Greetings https://bugs.debian.org/1016670
Processed: Bug#1016670 marked as pending in libconfig-model-dpkg-perl
Processing control commands: > tag -1 pending Bug #1016670 [src:libconfig-model-dpkg-perl] libconfig-model-dpkg-perl: autopkgtest failures Added tag(s) pending. -- 1016670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1016401, found 1016401 in ncview/2.1.8+ds-4
Processing commands for cont...@bugs.debian.org:
> tags 1016401 + bookworm sid
Bug #1016401 {Done: Bas Couwenberg } [src:ncview] switch
build depends on libnetpbm10-dev to libnetpbm-dev
Added tag(s) bookworm and sid.
> found 1016401 ncview/2.1.8+ds-4
Bug #1016401 {Done: Bas Couwenberg } [src:ncview] switch
build depends on libnetpbm10-dev to libnetpbm-dev
Marked as found in versions ncview/2.1.8+ds-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1014104: marked as done (mothur: autopkgtest regression: did not complete cluster.)
Your message dated Sat, 06 Aug 2022 16:05:11 + with message-id and subject line Bug#1014104: fixed in mothur 1.48.0-2 has caused the Debian Bug report #1014104, regarding mothur: autopkgtest regression: did not complete cluster. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1014104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mothur Version: 1.48.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of mothur the autopkgtest of mothur fails in testing when that autopkgtest is run with the binary packages of mothur from unstable. It passes when run with only packages from testing. In tabular form: passfail mothur from testing1.48.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=mothur https://ci.debian.net/data/autopkgtest/testing/amd64/m/mothur/23197987/log.gz Linux version Using ReadLine mothur v.1.48.0 Last updated: 5/20/22 by Patrick D. Schloss Department of Microbiology & Immunology University of Michigan http://www.mothur.org When using, please cite: Schloss, P.D., et al., Introducing mothur: Open-source, platform-independent, community-supported software for describing and comparing microbial communities. Appl Environ Microbiol, 2009. 75(23):7537-41. Distributed under the GNU General Public License Type 'help()' for information on the commands that are available For questions and analysis support, please visit our forum at https://forum.mothur.org Type 'quit()' to exit program [NOTE]: Setting random seed to 19760620. Batch Mode mothur > unique.seqs(fasta=HA.fasta) 599 259 Output File Names: HA.unique.fasta HA.count_table mothur > dist.seqs(fasta=HA.unique.fasta, countends=F, cutoff=0.01) Using 2 processors. SequenceTimeNum_Dists_Below_Cutoff 0 0 0 200 0 3443 100 0 5025 258 0 15965 182 0 16617 It took 0 secs to find distances for 259 sequences. 32582 distances below cutoff 0.01. Output File Names: HA.unique.dist mothur > cluster(method=furthest, column=HA.unique.dist, name=HA.names, cutoff=0.01, precision=1000) Unable to open HA.names. Trying mothur's executable directory HA.names. Unable to open HA.names. Unable to open HA.names Using 2 processors. [ERROR]: did not complete cluster. mothur > summary.single(list=HA.unique.fn.list, calc=nseqs-sobs-chao, label=unique-0.001-0.003-0.005-0.008) Unable to open HA.unique.fn.list. Trying mothur's executable directory HA.unique.fn.list. Unable to open HA.unique.fn.list. Unable to open HA.unique.fn.list No valid current files. You must provide a list, sabund, rabund or shared file before you can use the collect.single command. [ERROR]: did not complete summary.single. mothur > heatmap.bin(scale=linear, label=unique-0.001-0.003) No valid current files. You must provide a list, sabund, rabund, relabund or shared file. [ERROR]: did not complete heatmap.bin. mothur > rarefaction.single(calc=sobs-chao, label=unique-0.001-0.003, freq=10) No valid current files. You must provide a list, sabund, rabund or shared file before you can use the collect.single command. Using 2 processors. [ERROR]: did not complete rarefaction.single. mothur > quit() It took 0 seconds to run 7 commands from test.batch batch file. Logfile : mothur.1656579650.logfile Detected 4 [ERROR] messages, please review. autopkgtest [09:00:51]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: mothur Source-Version: 1.48.0-2 Done: Mohammed Bilal We believe that the bug you reported is fixed in the latest version of mothur, which is due to
Bug#1016236: marked as done (uhd: FTBFS: awaitable.hpp:68:19: error: ‘exchange’ is not a member of ‘std’; did you mean ‘std::__atomic_impl::exchange’?)
Your message dated Sat, 06 Aug 2022 15:24:22 + with message-id and subject line Bug#1016236: fixed in uhd 4.2.0.1+ds1-1 has caused the Debian Bug report #1016236, regarding uhd: FTBFS: awaitable.hpp:68:19: error: ‘exchange’ is not a member of ‘std’; did you mean ‘std::__atomic_impl::exchange’? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhd Version: 4.2.0.0+ds1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DBOOST_ASIO_DISABLE_STD_EXPERIMENTAL_STRING_VIEW > -DBOOST_ASIO_HAS_STD_STRING_VIEW -DBOOST_ERROR_CODE_HEADER_ONLY > -DHAVE_CONFIG_H -DHAVE_DPDK -DUHD_LOG_CONSOLE_COLOR -DUHD_LOG_CONSOLE_LEVEL=2 > -DUHD_LOG_FILE_LEVEL=2 -DUHD_LOG_MIN_LEVEL=1 > -I/<>/obj-x86_64-linux-gnu/include > -I/<>/host/include -I/<>/host/lib/include > -I/<>/obj-x86_64-linux-gnu/lib/include > -I/<>/host/lib/deps/flatbuffers/include > -I/<>/obj-x86_64-linux-gnu/lib/ic_reg_maps > -I/<>/host/lib/convert > -I/<>/obj-x86_64-linux-gnu/lib/convert > -I/<>/host/lib/usrp > -I/<>/host/lib/usrp/common/ad9361_driver > -I/<>/host/lib/usrp/common -I/usr/include/dpdk > -I/usr/include/libnl3 -I/usr/include/dpdk/../x86_64-linux-gnu/dpdk > -I/usr/include/x86_64-linux-gnu/dpdk > -I/<>/obj-x86_64-linux-gnu/lib/transport/nirio/lvbitx > -I/usr/include/libusb-1.0 -I/<>/host/lib/transport/uhd-dpdk > -I/<>/host/lib/deps/rpclib/include > -I/<>/host/lib/deps/rpclib/include/rpc -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden > -fvisibility-inlines-hidden -fPIC -Wall -Wextra -Wsign-compare -std=gnu++20 > -MD -MT > lib/deps/rpclib/CMakeFiles/uhd_rpclib.dir/lib/rpc/detail/server_session.cc.o > -MF > lib/deps/rpclib/CMakeFiles/uhd_rpclib.dir/lib/rpc/detail/server_session.cc.o.d > -o > lib/deps/rpclib/CMakeFiles/uhd_rpclib.dir/lib/rpc/detail/server_session.cc.o > -c /<>/host/lib/deps/rpclib/lib/rpc/detail/server_session.cc > In file included from /usr/include/boost/asio.hpp:23, > from > /<>/host/lib/deps/rpclib/include/rpc/detail/server_session.h:6, > from > /<>/host/lib/deps/rpclib/lib/rpc/detail/server_session.cc:1: > /usr/include/boost/asio/awaitable.hpp: In constructor > ‘boost::asio::awaitable::awaitable(boost::asio::awaitable Executor>&&)’: > /usr/include/boost/asio/awaitable.hpp:68:19: error: ‘exchange’ is not a > member of ‘std’; did you mean ‘std::__atomic_impl::exchange’? >68 | : frame_(std::exchange(other.frame_, nullptr)) > | ^~~~ > In file included from /usr/include/c++/12/bits/shared_ptr_atomic.h:33, > from /usr/include/c++/12/memory:78, > from /usr/include/boost/asio/associated_allocator.hpp:19, > from /usr/include/boost/asio.hpp:20: > /usr/include/c++/12/bits/atomic_base.h:976:7: note: > ‘std::__atomic_impl::exchange’ declared here > 976 | exchange(_Tp* __ptr, _Val<_Tp> __desired, memory_order __m) > noexcept > | ^~~~ The full build log is available from: http://qa-logs.debian.net/2022/07/28/uhd_4.2.0.0+ds1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: uhd Source-Version: 4.2.0.1+ds1-1 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of uhd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one i
Bug#1016454: marked as done (megadepth: autopkgtest failure on s390x: segmentation fault)
Your message dated Sat, 06 Aug 2022 15:21:15 + with message-id and subject line Bug#1016454: fixed in megadepth 1.2.0-4 has caused the Debian Bug report #1016454, regarding megadepth: autopkgtest failure on s390x: segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: megadepth Version: 1.2.0-3 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package megadepth, great. However, it fails on s390x. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=megadepth https://ci.debian.net/data/autopkgtest/testing/s390x/m/megadepth/23583699/log.gz [93m[1mRunning Tests[0m [93m[1mTest 1[0m building whole annotation region map done 2 chromosomes for annotated regions read 0 chromosomes for annotated regions read, collapsed total number of annotations in collapsed: 0 Processing BAM: "tests/test_noprefix.bam" /tmp/autopkgtest-lxc.gmfzuwos/downtmp/build.jJn/src/debian/tests/run-unit-test: line 33: 1590 Segmentation fault megadepth tests/test_noprefix.bam --prefix test.bam --threads 4 --bigwig --auc --min-unique-qual 10 --annotation tests/test_exons.bed --frag-dist --alts --include-softclip --only-polya --read-ends --test-polya --no-annotation-stdout --no-auc-stdout --filter-out 260 --add-chr-prefix human autopkgtest [04:42:40]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: megadepth Source-Version: 1.2.0-4 Done: Mohammed Bilal We believe that the bug you reported is fixed in the latest version of megadepth, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mohammed Bilal (supplier of updated megadepth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Aug 2022 18:13:55 +0530 Source: megadepth Architecture: source Version: 1.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Mohammed Bilal Closes: 1016454 Changes: megadepth (1.2.0-4) unstable; urgency=medium . * Team upload. * d/t/control : disable tests on s390 (Closes: #1016454) Checksums-Sha1: 72d1441ac3bb2c2a0d27ef4186ac1b207037e254 2035 megadepth_1.2.0-4.dsc 3a0ce65d432442402716816345bdee247112f5e5 8764 megadepth_1.2.0-4.debian.tar.xz 8ca44be420b2fd7a4459e16e0bcacadd0eb071d1 7359 megadepth_1.2.0-4_amd64.buildinfo Checksums-Sha256: f20f96fcb58c9be9d2c4195fc6e26aa912b3d5ee09ac3c6de26207c232d57ea4 2035 megadepth_1.2.0-4.dsc 4270c1f25640387cc3ce3bd529708a0bcfaa06f6ee6f36d8a6fae984b26b765a 8764 megadepth_1.2.0-4.debian.tar.xz 1e206a0b1789037295d18c7b730b08d3eb93f010e34a74a55e4ee65705928aa5 7359 megadepth_1.2.0-4_amd64.buildinfo Files: fdba54b0f05700d9950570a9b275f1cd 2035 science optional megadepth_1.2.0-4.dsc 19adaaa0c00642f0cba2ed0bd4e122ed 8764 science optional megadepth_1.2.0-4.debian.tar.xz 354b08d1d10ff52cf8d1355154ba0b25 7359 science optional megadepth_1.2.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmLuhDoRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHeMg//bShbMEFbkRMD24V0r8F+qtUXAwBR/Rit SEkClfd16oySln4rPt+gMziYJIeIYOIw3eE8DsCG4Tq0/sI2uTLtzPEQ84VdpJ99 QzJAJzUWMxYYaXvEFQrbEc4CrKT/50sinu8YqlGQtjgRh9FYamw2BBJ7HqMQpBN9 vDH5ZzmkBpoXfhML6AljTlIvUbwe0t+SSDWGVsscVclOpMH4YQZeqPT9juLgprIs D5xhdpOg/z1IyX0YYv1U75q2lBzgQc9YQw7PXkAhiRoNHjioqEgk7Cuz5UHogKXN TTJ4qsYJXMFmrd82cY5LqdtSjSOB/lY8T++XQ5txhHlhbVioI9TBgRQWpxQlHBqL Dp5X42wdXjk9+j6YB8zHTCgXN5d06NKRW0gsKwwy3Co5R2QWQ5fetnUT0liDJVcA W9FDFrZfMITHbcr+20xZhzbxWSds6IusWh6x6fPVT7BDC3V4SNx8OS7E
Bug#1011165: org.h2.jdbc.JdbcSQLSyntaxErrorException: schema "MEDIATHEKVIEW" not found
Hello Markus,
On Tue, May 17, 2022 at 10:09:08PM +0200, Markus Koschany wrote:
> Control: severity -1 serious
>
> Am Dienstag, dem 17.05.2022 um 21:59 +0200 schrieb mt...@nurfuerspam.de:
> > Package: mediathekview
> > Version: 13.2.1-4
> > Severity: important
> >
> > Dear Maintainer,
> >
> > after libh2-java was updated from version 2.1.210+really1.4.197-1 to
> > 2.1.212-
> > 1
> > there is an enormous occurrence of the following error exceptions when
> > starting mediathekview:
>
> Hello and thanks for the report. Currently this cannot be avoided because we
> had to move forward with the h2 database in Debian. The latest version of
> mediathekview should not require h2 anymore. I don't have the time to package
> a
> new upstream release right now but if someone wants to beat me to it, please
> go
> ahead and mark yourself as the owner of this bug report.
I hope that you'll have some time so that mediathekview is shipped in
Testing/Futures stables again.
I tried to have a look at it (though I've really no clue about java
and building java progs) and unfortunately the situation is worse than
I thought.
To save others time, that's what I tried:
1) Using the existing debian directory with or without applying
patches no longer works (this is what I expected).
2) A direct ("upstream") build also fails (and the documentation on
building is very terse) and on a quick search I could not find a
workaround.
Direct build:
./mvnw compile
…
Downloaded from central:
https://repo.maven.apache.org/maven2/org/openjfx/javafx-graphics/19-ea+7/javafx-graphics-19-ea+7-linux.jar
(4.8 MB at 1.3 MB/s)
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 10.034 s
[INFO] Finished at: 2022-07-20T14:49:04+02:00
[INFO]
[ERROR] Failed to execute goal on project MediathekView: Could not resolve
dependencies for project de.mediathekview:MediathekView:jar:13.9.1: Could not
find artifact airsquared:JMacNotification:jar:1.1 in local-maven-repository
(file:tmp/mtvb2/MediathekView-13.9.1/maven-repository) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
and indeed,
/tmp/mtvb2/MediathekView-13.9.1/maven-repository/airsquared/JMacNotification/1.1/JMacNotification-1.1.jar
does not exists, and even worse (explaining the failure):
https://repo.maven.apache.org/maven2/airsquared/JMacNotification/1.1/JMacNotification-1.1.jar
is 404 (does not exist)
I could find maybe a read only copy here:
https://github.com/mediathekview/MediathekViewArchiv/blob/master/maven-repository/airsquared/JMacNotification/1.1/JMacNotification-1.1.jar
So this would require verification and then somehow to be included
into the build.
Maybe this helps getting the ball rolling …
Greetings
Helge
P.S. Besides the errors the current version still seems to work
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
Bug#1016750: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.
Source: sbcl, cl-ironclad
Control: found -1 sbcl/2:2.2.6-2
Control: found -1 cl-ironclad/0.57-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of sbcl the autopkgtest of cl-ironclad fails in
testing when that autopkgtest is run with the binary packages of sbcl
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
sbcl from testing2:2.2.6-2
cl-ironcladfrom testing0.57-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of sbcl to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=sbcl
https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-ironclad/24381695/log.gz
; wrote
/tmp/autopkgtest-lxc.d2c27h4h/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/ironclad/src/ciphers/tea-tmp93OFNPHA.fasl
; compilation finished in 0:00:00.160
; compiling file
"/usr/share/common-lisp/source/ironclad/src/ciphers/threefish.lisp"
(written 18 FEB 2022 01:39:10 PM):
Heap exhausted during garbage collection: 16 bytes available, 48 requested.
Immobile Object Counts
Gen GF type fdefn symbol code Boxed ConsRaw Code SmMix
Mixed LgRaw LgCode LgMix Waste% AllocTrig Dirty GCs
Mem-age
1 00 0 0 0 7121939 9668 5273
827 0 0 17 19.96186748032499253 18850 1
1.1503
2 00 0 0 0 19865 2766 12586 84836
1681 10 34127 11.7 137430448 5368709 23089 0
0.9496
3 00 0 0 0 45116 7190 7447604 3552
16732394673311.0 270091288 2007806 0
0.4559
4 00 0 0 0 0 0 0 0 0
0 0 0 00.0 0 200 0 0
0.
5 00 0 0 0 0 0 0 0 0
0 0 0 00.0 0 200 0 0
0.
6 00 0 0 0 1370471 1242 3507314
402551342811.930584464 200 251 0
0.
Tot 00 0 0 0 73472 11366 30943 4200 4975
42215046357566.9 499973680 [93.1% of 536870912 max]
GC control variables:
*GC-INHIBIT* = true
*GC-PENDING* = true
fatal error encountered in SBCL pid 1357:
Heap exhausted, game over.
0: 0xf746478c pc=0x98 {0x4f0380b8+b0fc7fe0} {code_serialno=3901}
1: 0xf7464730 pc=0x4f005760 {0x4f005000+0760} (FLET
"WITHOUT-GCING-BODY-5" :IN SB-KERNEL::SUB-GC)
2: 0xf74646d4 pc=0x4f0053f8 {0x4f005000+03f8} (FLET
"WITHOUT-INTERRUPTS-BODY-1" :IN SB-KERNEL::SUB-GC)
3: 0xf7464678 pc=0x4f005108 {0x4f005000+0108} SB-KERNEL::SUB-GC
4: 0xf746466c pc=(nil) LRA=0x3e2e75: [I]0xf7464654
pc=0x3e4d8 {0x4fb3f240+b04ff298} {code_serialno=f5f}
6: 0xf7464634 pc=0x5028c858 {0x5028c4b0+03a8} SB-C::MAKE-WIRED-TN
7: 0xf7464604 pc=0x4fd9a348 {0x4fd9a030+0318}
SB-C::IR2-CONVERT-FULL-CALL-ARGS
8: 0xf74645c4 pc=0x4f8506f8 {0x4f8505c8+0130}
SB-C::IR2-CONVERT-FIXED-FULL-CALL
9: 0xf74645b4 pc=0x4f3d8b18 {0x4f3d8990+0188}
SB-C::IR2-CONVERT-FULL-CALL
10: 0xf7464598 pc=0x4f6fe720 {0x4f6fda90+0c90}
SB-C::IR2-CONVERT-BLOCK
11: 0xf7464584 pc=0x4f2c8f58 {0x4f2c8dc8+0190} SB-C::IR2-CONVERT
12: 0xf7464550 pc=0x504637a8 {0x50463198+0610}
SB-C::%COMPILE-COMPONENT
13: 0xf7464538 pc=0x5041c820 {0x5041c258+05c8}
SB-C::COMPILE-COMPONENT
14: 0xf7464514 pc=0x5037ca10 {0x5037c7b8+0258} SB-C::COMPILE-TOPLEVEL
15: 0xf7464500 pc=0x503f0eb8 {0x503f0c28+0290}
SB-C::CONVERT-AND-MAYBE-COMPILE
16: 0xf74644b4 pc=0x50393270 {0x50392a10+0860}
SB-C::PROCESS-TOPLEVEL-FORM
17: 0xf746449c pc=0x50457490 {0x504573a0+00f0}
SB-C::PROCESS-TOPLEVEL-PROGN
18: 0xf7464450 pc=0x50393188 {0x50392a10+0778}
SB-C::PROCESS-TOPLEVEL-FORM
19: 0xf7464404 pc=0x50393408 {0x50392a10+09f8}
SB-C::PROCESS-TOPLEVEL-FORM
20: 0xf74643b8 pc=0x50393408 {0x50392a10+09f8}
SB-C::PROCESS-TOPLEVEL-FORM
21: 0xf7464334 pc=0x502f60e0 {0x502f3b20+25c0} (LAMBDA
(SB-KERNEL::FORM &KEY :CURRENT-INDEX &ALLOW-OTHER-KEYS) :IN
SB-C::SUB-COMPILE-FILE)
22: 0xf74642c0 pc=0x4f0c5038 {0x4f0c49a8+0690}
SB-C::%DO-FORMS-FROM-INFO
23: 0xf7464244 pc=0x502f3ea0 {0x502f3b20+0380} (FLET "LAMBDA0"
:IN "SYS:SRC;COMPILER;MAIN.L
Bug#1016749: pytango: autopkgtest failure on armel
Source: pytango
Version: 9.3.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package pytango, great.
However, it fails on armel. Currently this failure is blocking the
migration to testing [1]. Can you please investigate the situation and
fix it?
I copied some of the output at the bottom of this report.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pytango
https://ci.debian.net/data/autopkgtest/testing/armel/p/pytango/23495376/log.gz
=== FAILURES
===
___ test_subscribe_change_event[Synchronous]
___
event_device = EventDevice(test/nodb/eventdevice)
def test_subscribe_change_event(event_device):
results = []
def callback(evt):
results.append(evt.attr_value.value)
# Subscribe
eid = event_device.subscribe_event(
"attr", EventType.CHANGE_EVENT, callback, wait=True)
assert eid == 1
# Trigger an event
event_device.command_inout("send_event", wait=True)
# Wait for tango event
retries = 20
for _ in range(retries):
event_device.read_attribute("state", wait=True)
if len(results) > 1:
break
time.sleep(0.05)
# Test the event values
assert results == [0., 1.]
E assert [0.0] == [0.0, 1.0]
E Right contains one more item: 1.0
E Full diff:
E - [0.0, 1.0]
E + [0.0]
tests/test_event.py:115: AssertionError
Captured stdout setup
-
Ready to accept request
Captured stderr setup
-
Can't create notifd event supplier. Notifd event not available
_ test_push_event_with_timestamp[Synchronous]
__
event_device = EventDevice(test/nodb/eventdevice)
def test_push_event_with_timestamp(event_device):
string = StringIO()
ec = EventCallback(fd=string)
# Subscribe
eid = event_device.subscribe_event(
"attr", EventType.CHANGE_EVENT, ec, wait=True)
assert eid == 1
# Trigger an event
event_device.command_inout("send_event_with_timestamp", wait=True)
# Wait for tango event
retries = 20
for _ in range(retries):
event_device.read_attribute("state", wait=True)
if len(ec.get_events()) > 1:
break
time.sleep(0.05)
# Test the event values and timestamp
results = [evt.attr_value.value for evt in ec.get_events()]
assert results == [0., 2.]
E assert [0.0] == [0.0, 2.0]
E Right contains one more item: 2.0
E Full diff:
E - [0.0, 2.0]
E + [0.0]
tests/test_event.py:191: AssertionError
Captured stdout setup
-
Ready to accept request
Captured stderr setup
-
Can't create notifd event supplier. Notifd event not available
=== warnings summary
===
tests/test_client.py:19
/tmp/autopkgtest-lxc.q395dj8v/downtmp/autopkgtest_tmp/tests/test_client.py:19:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
from distutils.spawn import find_executable
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
FAILED tests/test_event.py::test_subscribe_change_event[Synchronous]
FAILED tests/test_event.py::test_push_event_with_timestamp[Synchronous]
== 2 failed, 1033 passed, 26 xfailed, 1 warning in 263.04s (0:04:23)
===
autopkgtest [07:52:48]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
Processed: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.
Processing control commands: > found -1 sbcl/2:2.2.6-2 Bug #1016750 [src:sbcl, src:cl-ironclad] sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over. Marked as found in versions sbcl/2:2.2.6-2. > found -1 cl-ironclad/0.57-1 Bug #1016750 [src:sbcl, src:cl-ironclad] sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over. Marked as found in versions cl-ironclad/0.57-1. -- 1016750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 1016356 1004640
Processing commands for cont...@bugs.debian.org: > forcemerge 1016356 1004640 Bug #1016356 [unpaper] FTBFS: unpaper fails to build against ffmpeg 5.0 Unable to merge bugs because: package of #1004640 is 'src:unpaper' not 'unpaper' Failed to forcibly merge 1016356: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004640 1016356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016748: mathcomp-analysis: FTBFS: test failure: Error: apply-w-params
Source: mathcomp-analysis Version: 0.5.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Rebuilds of mathcomp-analysis failed: COQC theories/realfun.v COQC theories/exp.v COQC theories/lebesgue_measure.v File "./theories/lebesgue_measure.v", line 133, characters 0-76: Warning: Casts are ignored in patterns [cast-in-pattern,automation] File "./theories/lebesgue_measure.v", line 133, characters 0-76: Warning: Casts are ignored in patterns [cast-in-pattern,automation] COQC theories/lebesgue_integral.v COQC theories/trigo.v File "./theories/lebesgue_integral.v", line 201, characters 0-51: Error: apply-w-params make[3]: *** [Makefile.coq:764: theories/lebesgue_integral.vo] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [Makefile.coq:387: all] Error 2 Cheers -- Sebastian Ramacher
Processed: Reassign to sshuttle from setuptools-scm
Processing commands for cont...@bugs.debian.org: > reassign 1015044 sshutle 1.0.1-1 Bug #1015044 [python3-setuptools-scm] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Bug reassigned from package 'python3-setuptools-scm' to 'sshutle'. Warning: Unknown package 'sshutle' Warning: Unknown package 'sshutle' No longer marked as found in versions setuptools-scm/7.0.5-1. Warning: Unknown package 'sshutle' Warning: Unknown package 'sshutle' Ignoring request to alter fixed versions of bug #1015044 to the same values previously set Warning: Unknown package 'sshutle' Bug #1015044 [sshutle] sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Warning: Unknown package 'sshutle' There is no source info for the package 'sshutle' at version '1.0.1-1' with architecture '' Unable to make a source version for version '1.0.1-1' Marked as found in versions 1.0.1-1. Warning: Unknown package 'sshutle' > thanks Stopping processing here. Please contact me if you need assistance. -- 1015044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016746: sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No such file or directory
Source: sbcl, cffi Control: found -1 sbcl/2:2.2.6-2 Control: found -1 cffi/1:0.24.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of sbcl the autopkgtest of cffi fails in testing when that autopkgtest is run with the binary packages of sbcl from unstable. It passes when run with only packages from testing. In tabular form: passfail sbcl from testing2:2.2.6-2 cffi from testing1:0.24.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of sbcl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=sbcl https://ci.debian.net/data/autopkgtest/testing/amd64/c/cffi/24381426/log.gz ; wrote /tmp/autopkgtest-lxc.qpgu5j9b/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/cl-cffi/tests/grovel-tmpFNKDE5XP.fasl ; compilation finished in 0:00:00.015 ;;; running tests (uncompiled) Doing 332 pending tests of 332 tests total. LOAD-CORE-FOUNDATION FUNCALL.CHAR FUNCALL.INT.1 FUNCALL.INT.2 FUNCALL.LONG FUNCALL.LONG-LONG FUNCALL.UNSIGNED-LONG-LONG FUNCALL.FLOAT FUNCALL.DOUBLE FUNCALL.STRING.1 FUNCALL.STRING.2 FUNCALL.STRING.3 FUNCALL.VARARGS.NOSTDLIB FUNCALL.VARARGS.CHAR FUNCALL.VARARGS.INT FUNCALL.VARARGS.LONG FUNCALL.VARARGS.DOUBLE FUNCALL.VARARGS.STRING FUNCALL.DOUBLE26 FUNCALL.FLOAT26 FUNCALL.F-S-P.1 FUNCALL.NIL-SKIP FUNCALL.POINTER-NOT-NIL DEFCFUN.PARSE-NAME-AND-OPTIONS.1 DEFCFUN.PARSE-NAME-AND-OPTIONS.2 DEFCFUN.PARSE-NAME-AND-OPTIONS.3 DEFCFUN.PARSE-NAME-AND-OPTIONS.4 DEFCFUN.PARSE-NAME-AND-OPTIONS.5 DEFCFUN.PARSE-NAME-AND-OPTIONS.6 DEFCFUN.PARSE-NAME-AND-OPTIONS.7 DEFCFUN.PARSE-NAME-AND-OPTIONS.8 TRANSLATE-UNDERSCORE-SEPARATED-NAME.TO-SYMBOL TRANSLATE-UNDERSCORE-SEPARATED-NAME.TO-STRING TRANSLATE-CAMELCASE-NAME.TO-SYMBOL TRANSLATE-CAMELCASE-NAME.TO-STRING TRANSLATE-CAMELCASE-NAME.TO-STRING-UPPER TRANSLATE-CAMELCASE-NAME.TO-SYMBOL-SPECIAL TRANSLATE-CAMELCASE-NAME.TO-STRING-SPECIAL TRANSLATE-NAME-FROM-FOREIGN.FUNCTION TRANSLATE-NAME-FROM-FOREIGN.VAR TRANSLATE-NAME-TO-FOREIGN.FUNCTION TRANSLATE-NAME-TO-FOREIGN.VAR DEFCFUN.CHAR DEFCFUN.DOCSTRING DEFCFUN.INT DEFCFUN.LONG DEFCFUN.LONG-LONG DEFCFUN.UNSIGNED-LONG-LONG DEFCFUN.FLOAT DEFCFUN.DOUBLE DEFCFUN.STRING.1 DEFCFUN.STRING.2 DEFCFUN.STRING.3 DEFCFUN.NOARGS DEFCFUN.NOOP DEFCFUN.VARARGS.NOSTDLIB DEFCFUN.VARARGS.DOCSTRINGS DEFCFUN.VARARGS.CHAR DEFCFUN.VARARGS.SHORT DEFCFUN.VARARGS.INT DEFCFUN.VARARGS.LONG DEFCFUN.VARARGS.FLOAT DEFCFUN.VARARGS.DOUBLE DEFCFUN.VARARGS.STRING DEFCFUN.BFF.1 DEFCFUN.BFF.2 DEFCFUN.UNDEFINED DEFCFUN.DOUBLE26 DEFCFUN.FLOAT26 CALLBACKS.CHAR CALLBACKS.UNSIGNED-CHAR CALLBACKS.SHORT CALLBACKS.UNSIGNED-SHORT CALLBACKS.INT CALLBACKS.UNSIGNED-INT CALLBACKS.LONG CALLBACKS.UNSIGNED-LONG CALLBACKS.LONG-LONG CALLBACKS.UNSIGNED-LONG-LONG CALLBACKS.FLOAT CALLBACKS.DOUBLE CALLBACKS.POINTER CALLBACKS.STRING CALLBACKS.STRING-NOT-DOCSTRING CALLBACKS.NIL-FOR-NULL CALLBACKS.QSORT CALLBACKS.VOID CALLBACKS.FUNCALL.1 CALLBACKS.FUNCALL.2 CALLBACKS.BFF.1 CALLBACKS.BFF.2 CALLBACKS.NON-EXISTANT CALLBACKS.DOUBLE26 CALLBACKS.DOUBLE26.FUNCALL CALLBACKS.FLOAT26 CALLBACKS.FLOAT26.FUNCALL CALLBACKS.UNINTERNED FOREIGN-GLOBALS.REF.CHAR FOREIGN-GLOBALS.REF.UNSIGNED-CHAR FOREIGN-GLOBALS.REF.SHORT FOREIGN-GLOBALS.REF.UNSIGNED-SHORT FOREIGN-GLOBALS.REF.INT FOREIGN-GLOBALS.REF.UNSIGNED-INT FOREIGN-GLOBALS.REF.LONG FOREIGN-GLOBALS.REF.UNSIGNED-LONG FOREIGN-GLOBALS.REF.FLOAT FOREIGN-GLOBALS.REF.DOUBLE FOREIGN-GLOBALS.REF.POINTER FOREIGN-GLOBALS.REF.STRING FOREIGN-GLOBALS.REF.LONG-LONG FOREIGN-GLOBALS.REF.UNSIGNED-LONG-LONG FOREIGN-GLOBALS.SET.INT FOREIGN-GLOBALS.SET.STRING FOREIGN-GLOBALS.SET.LONG-LONG FOREIGN-GLOBALS.GET-VAR-POINTER.1 FOREIGN-GLOBALS.GET-VAR-POINTER.2 FOREIGN-GLOBALS.REF.UPPERCASEINT1 FOREIGN-GLOBALS.REF.UPPER-CASE-INT1 FOREIGN-GLOBALS.REF.MIXEDCASEINT1 FOREIGN-GLOBALS.REF.MIXED-CASE-INT1 FOREIGN-GLOBALS.REF.UPPERCASEINT2 FOREIGN-GLOBALS.REF.UPPER-CASE-INT2 FOREIGN-GLOBALS.REF.MIXEDCASEINT2 FOREIGN-GLOBALS.REF.MIXED-CASE-INT2 FOREIGN-GLOBALS.REF.UPPERCASEINT3 FOREIGN-GLOBALS.REF.UPPER-CASE-INT3 FOREIGN-GLOBALS.REF.MIXEDCASEINT3 FOREIGN-GLOBALS.REF.MIXED-CASE-INT3 FOREIGN-GLOBALS.SYMBOL-NAME FOREIGN-GLOBALS.READ-ONLY.1 DEFCVAR.DOCSTRING FOREIGN-GLOBALS.UNDEFINED.1 FOREIGN-GLOBALS.ERROR.1 DEREF.CHAR DEREF.UNSIGNED-CHAR DEREF.SHORT DEREF.UNSIGNED-SHORT DEREF.INT DEREF.UNSIGNED-INT DEREF.LONG DEREF.UNSIGNED-LONG DEREF.LONG-LONG DEREF.UNSIGNED-LONG-LONG DEREF.FLOAT.1 DEREF.FLOAT.2 DEREF
Processed: sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No such file or directory
Processing control commands: > found -1 sbcl/2:2.2.6-2 Bug #1016746 [src:sbcl, src:cffi] sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No such file or directory Marked as found in versions sbcl/2:2.2.6-2. > found -1 cffi/1:0.24.1-2 Bug #1016746 [src:sbcl, src:cffi] sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No such file or directory Marked as found in versions cffi/1:0.24.1-2. -- 1016746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016744: vim-ultisnips: autopkgtest failure on arm64, i386 and ppc64el
Source: vim-ultisnips Version: 3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package vim-ultisnips, great. However, it fails on arm64, i386 and ppc64el. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=vim-ultisnips https://ci.debian.net/data/autopkgtest/testing/arm64/v/vim-ultisnips/23984911/log.gz == FAIL: runTest (test_ParseSnippets.ParseSnippets_ExtendsWithoutFiletype) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.p149hn5f/downtmp/build.kSM/src/test/vim_test_case.py", line 53, in runTest self.assertRegexpMatches(self.output, self.expected_error) AssertionError: Regex didn't match: "'extends' without file types in \\S+:2" not found in 'An error occured. This is either a bug in UltiSnips or a bug in a\nsnippet definition. If you think this is a bug, please report it to\nhttps://github.com/SirVer/ultisnips/issues/new\nPlease read and follow:\nhttps://github.com/SirVer/ultisnips/blob/master/CONTRIBUTING.md#reproducing-bugs\n\nFollowing is the full stack trace:\nTraceback (most recent call last):\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/err_to_scratch_buffer.py", line 18, in wrapper\nreturn func(self, *args, **kwds)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 905, in _track_change\n self._try_expand(autotrigger_only=True)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 749, in _try_expand\nsnippets = self._snips(before, False, autotrigger_only)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet_manager.py", line 629, in _snips\nsource.ensure(filetypes)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 31, in ensure\nself._load_snippets_for(ft)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 53, in _load_snippets_for\nself._parse_snippets(ft, fn)\n File "/usr/share/nvim/site/pack/dist-bundle/opt/ultisnips/pythonx/UltiSnips/snippet/source/file/base.py", line 69, in _parse_snippets\nraise SnippetSyntaxError(filename, line_index, msg)\nUltiSnips.snippet.source.file.base.SnippetSyntaxError: \'extends\' without file types in /tmp/p\tautopkgtest-lxc.p149hn5f/downtmp/autopkgtest_tmp/UltiSnipsTest_Casenir0duuw/us/all.snippets:2' -- Ran 560 tests in 1259.152s FAILED (failures=1, skipped=4) autopkgtest [05:49:55]: test with-neovim OpenPGP_signature Description: OpenPGP digital signature
Bug#1016743: zalign: autopkgtest failure on 32 bit architectures: Segmentation fault
Source: zalign Version: 0.9.1-6 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package zalign, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=zalign https://ci.debian.net/data/autopkgtest/testing/armhf/z/zalign/23914703/log.gz [93m[1mRunning Tests[0m [93m[1mTest 1[0m Stage 1: Distribute data to all nodes - # File parameters S sequence: 104 characters Filename: dd T sequence: 104 characters Filename: rt # Performance parameters Number of 'split' submatrices: 1 Available nodes:1 Horizontal block divisions:10 Vertical block divisions: 10 # Scoring parameters Match: 1 Mismatch: -3 Gap Opening: -5 Gap Extension: -2 Stage 2: Find best scores - Showing progress information for root node (rank 0): split 1/1: || 0%* | 1%* | 2%** | 3%** | 4%** | 5%*** | 6%*** | 7% | 8% | 9% | 10%* | 11%* | 12%** | 13%** | 14%** | 15%*** | 16%*** | 17% | 18% | 19% | 20%* | 21%* | 22%** | 23%** | 24%** | 25%*** | 26%*** | 27% | 28% | 29% | 30%* | 31%* | 32%** | 33%** | 34%** | 35%*** | 36%*** | 37% | 38%*
Bug#1016099: marked as done (python3-pudb: Missing urwid_readline package)
Your message dated Sat, 06 Aug 2022 13:45:13 +
with message-id
and subject line Bug#1016099: fixed in pudb 2022.1.2-2
has caused the Debian Bug report #1016099,
regarding python3-pudb: Missing urwid_readline package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pudb
Version: 2022.1.2-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
version 2022.1.2 introduced a new dependency on urwid_readline[0] which has not
been packaged for Debian:
Traceback (most recent call last):
File "/usr/bin/pudb3", line 33, in
sys.exit(load_entry_point('pudb==2022.1.2', 'console_scripts',
'pudb3')())
File "/usr/lib/python3/dist-packages/pudb/run.py", line 65, in main
runscript(mainpyfile, **options_kwargs)
File "/usr/lib/python3/dist-packages/pudb/__init__.py", line 109, in
runscript
dbg = _get_debugger(steal_output=steal_output)
File "/usr/lib/python3/dist-packages/pudb/__init__.py", line 85, in
_get_debugger
dbg = Debugger(**kwargs)
File "/usr/lib/python3/dist-packages/pudb/debugger.py", line 194, in
__init__
self.ui = DebuggerUI(self, stdin=stdin, stdout=stdout,
term_size=term_size)
File "/usr/lib/python3/dist-packages/pudb/debugger.py", line 830, in
__init__
import urwid_readline
ModuleNotFoundError: No module named 'urwid_readline'
Regards,
Michael
- -- 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.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.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 python3-pudb depends on:
ii dpkg 1.21.9
ii python33.10.5-3
ii python3-pkg-resources 59.6.0-1.2
ii python3-pygments 2.12.0+dfsg-2
ii python3-urwid 2.1.2-2+b2
python3-pudb recommends no packages.
Versions of packages python3-pudb suggests:
ii ipython3 7.31.1-1
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmLg/KwRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WrVLwf9HvFBN0+LUFo/Zlj4GhiqZwyaDCZh2ABo
A6eEvQcteWJl+XiJ+UI8YB6H93CppaGx87Y10q3RxnjYOvycwXtYn7AYkHA6oMwW
egINJPrs8yqd4tqZpwPLsb3w3AuI4BIGH8Pu/XQdTYMeP0R79Qvwgn6FyosbPMQz
VcYwwYaDj1WdXF0JsRLWjR9NS1pNFt6em1Ss68H8xIfTPSU8rygey7P1Vuzt8ble
o0zrRV8JpyKOjun99/6UJhtMILItB31k06llcJY7i57ZSWY3ePpuqykwekLKDPRA
XE1IFobKnRT9jlMyCzDMpXrKwaU9zjLBCogtiQrqxZKnc1QSKQRkuQ==
=kCV9
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: pudb
Source-Version: 2022.1.2-2
Done: Josue Ortega
We believe that the bug you reported is fixed in the latest version of
pudb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Josue Ortega (supplier of updated pudb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 06 Aug 2022 06:35:53 -0600
Source: pudb
Architecture: source
Version: 2022.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto
Changed-By: Josue Ortega
Closes: 1016099
Changes:
pudb (2022.1.2-2) unstable; urgency=medium
.
* debian/control: Add python3-urwid-readline as build dependency
(Closes: #1016099)
Checksums-Sha1:
7c7d870713bb9b15c7888c452896335af83dcd1f 2071 pudb_2022.1.2-2.dsc
f5a31345be43c25bd503302f653b1ba0d7961709 4548 pudb_2022.1.2-2.debian.tar.xz
5ababf5477ab5d0a45c42490e8ad064ccf6d334d 6951 pudb_2022.1.2-2_source.buildinfo
Checksums-Sha256:
2d0e1145874c25edb7ba4fa29e22c44ea31eb14028b367568d708114b184d628 2071
pudb_2022.1.2-2.dsc
08cb67a2f17c446983a20191745792d674c8759e6e8886213aea8485b160493a 4548
pudb_2022.1.2-2.d
Bug#1016742: libcereal: autopkgtest regression: add_subdirectory given source "sandbox" which is not an existing directory
Source: libcereal Version: 1.3.2+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libcereal the autopkgtest of libcereal fails in testing when that autopkgtest is run with the binary packages of libcereal from unstable. It passes when run with only packages from testing. In tabular form: passfail libcereal from testing1.3.2+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libcereal https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcereal/24396353/log.gz -- The CXX compiler identification is GNU 11.3.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found version "1.74.0") found components: serialization -- boost_variant.cpp CMake Error at CMakeLists.txt:123 (add_subdirectory): add_subdirectory given source "sandbox" which is not an existing directory. -- Configuring incomplete, errors occurred! See also "/tmp/autopkgtest-lxc.q81fqk9c/downtmp/autopkgtest_tmp/CMakeFiles/CMakeOutput.log". make: *** No targets specified and no makefile found. Stop. autopkgtest [03:11:34]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1016740: golang-github-cli-go-gh: autopkgtest regression: TestGQLClientDoWithContext/http_fail_request_timed_out
Source: golang-github-cli-go-gh Version: 0.0.3+git20220623.91ca4ef-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of golang-github-cli-go-gh the autopkgtest of golang-github-cli-go-gh fails in testing when that autopkgtest is run with the binary packages of golang-github-cli-go-gh from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-cli-go-gh from testing0.0.3+git20220623.91ca4ef-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-cli-go-gh https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-cli-go-gh/24389592/log.gz === RUN TestGQLClientDoWithContext/http_fail_request_canceled gql_client_test.go:170: Error Trace:gql_client_test.go:170 Error: An error is expected but got nil. Test: TestGQLClientDoWithContext/http_fail_request_canceled === RUN TestGQLClientDoWithContext/http_fail_request_timed_out gql_client_test.go:170: Error Trace:gql_client_test.go:170 Error: An error is expected but got nil. Test: TestGQLClientDoWithContext/http_fail_request_timed_out --- FAIL: TestGQLClientDoWithContext (0.00s) --- FAIL: TestGQLClientDoWithContext/http_fail_request_canceled (0.00s) --- FAIL: TestGQLClientDoWithContext/http_fail_request_timed_out (0.00s) === RUN TestRESTClientDoWithContext/http_fail_request_canceled rest_client_test.go:341:Error Trace:rest_client_test.go:341 Error: An error is expected but got nil. Test: TestRESTClientDoWithContext/http_fail_request_canceled === RUN TestRESTClientDoWithContext/http_fail_request_timed_out rest_client_test.go:341:Error Trace:rest_client_test.go:341 Error: An error is expected but got nil. Test: TestRESTClientDoWithContext/http_fail_request_timed_out --- FAIL: TestRESTClientDoWithContext (0.00s) --- FAIL: TestRESTClientDoWithContext/http_fail_request_canceled (0.00s) --- FAIL: TestRESTClientDoWithContext/http_fail_request_timed_out (0.00s) === RUN TestRESTClientRequestWithContext === RUN TestRESTClientRequestWithContext/http_fail_request_canceled rest_client_test.go:394:Error Trace:rest_client_test.go:394 Error: An error is expected but got nil. Test: TestRESTClientRequestWithContext/http_fail_request_canceled === RUN TestRESTClientRequestWithContext/http_fail_request_timed_out rest_client_test.go:394:Error Trace:rest_client_test.go:394 Error: An error is expected but got nil. Test: TestRESTClientRequestWithContext/http_fail_request_timed_out --- FAIL: TestRESTClientRequestWithContext (0.00s) --- FAIL: TestRESTClientRequestWithContext/http_fail_request_canceled (0.00s) --- FAIL: TestRESTClientRequestWithContext/http_fail_request_timed_out (0.00s) === RUN TestRestPrefix === RUN TestRestPrefix/github === RUN TestRestPrefix/localhost === RUN TestRestPrefix/enterprise --- PASS: TestRestPrefix (0.00s) --- PASS: TestRestPrefix/github (0.00s) --- PASS: TestRestPrefix/localhost (0.00s) --- PASS: TestRestPrefix/enterprise (0.00s) FAIL FAILgithub.com/cli/go-gh/internal/api 0.007s OpenPGP_signature Description: OpenPGP digital signature
Bug#1016738: dt-schema: autopkgtest failure: No module named 'libfdt'
Source: dt-schema Version: 2022.07-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package dt-schema, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems you are missing a dependency. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dt-schema https://ci.debian.net/data/autopkgtest/testing/amd64/d/dt-schema/24372986/log.gz === python3.10 === Traceback (most recent call last): File "/tmp/autopkgtest-lxc.ard1nynt/downtmp/autopkgtest_tmp/test/test-dt-validate.py", line 20, in import dtschema File "/usr/lib/python3/dist-packages/dtschema/__init__.py", line 1, in from dtschema.lib import ( File "/usr/lib/python3/dist-packages/dtschema/lib.py", line 18, in import dtschema.dtb File "/usr/lib/python3/dist-packages/dtschema/dtb.py", line 9, in import libfdt ModuleNotFoundError: No module named 'libfdt' autopkgtest [08:11:46]: test unittests OpenPGP_signature Description: OpenPGP digital signature
Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp
Yadd, Since you added in coffeescript patch for this package, I'd highly appreciate if you could consider taking a look. On Sat, 06 Aug 2022 17:54:13 +0530 Nilesh Patra wrote: > Package: node-sockjs > Version: 0.3.24+~0.3.33-1 > Severity: serious > X-Debbugs-Cc: e...@ericebrown.com > > Hi, > > On running shiny-server with 0.3.24+~0.3.33-1 it chokes with: > > | [2022-08-06T04:59:03.613] [ERROR] shiny-server - Uncaught exception: > TypeError: Cannot read properties of undefined (reading 'addEventListener') > | [2022-08-06T04:59:03.614] [ERROR] shiny-server - TypeError: Cannot read > properties of undefined (reading 'addEventListener') > |at WebSocketReceiver.setUp > (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) > |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) > |at new WebSocketReceiver > (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) > |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) > |at WebSocket.dispatchEvent > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) > |at WebSocket._open > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) > |at Hybi. > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) > |at Hybi.emit (node:events:513:28) > |at Hybi._open > (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) > |at Hybi.start > (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) > | [2022-08-06T04:59:03.615] [INFO] shiny-server - Stopping listener on > http://[::]:3838 > | [2022-08-06T04:59:03.615] [INFO] shiny-server - Shutting down worker > processes (with notification) > | /usr/lib/shiny-server/lib/main.js:391 > | throw err; > | ^ > | > | TypeError: Cannot read properties of undefined (reading 'addEventListener') > |at WebSocketReceiver.setUp > (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) > |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) > |at new WebSocketReceiver > (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) > |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) > |at WebSocket.dispatchEvent > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) > |at WebSocket._open > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) > |at Hybi. > (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) > |at Hybi.emit (node:events:513:28) > |at Hybi._open > (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) > |at Hybi.start > (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) > | > | Node.js v18.6.0 > > > While it is running perfectly ok _with 0.3.24-2_. Since this is > not a new release, there is a regression with the new changelog revision. > > In particular, it seems that something is off with the coffeescript > generated files. > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > -- Best, Nilesh signature.asc Description: PGP signature
Bug#1016681: marked as done (python-mitogen: Build-Depends on python2 which Debian tries to remove)
Your message dated Sat, 06 Aug 2022 12:22:05 + with message-id and subject line Bug#1016681: fixed in python-mitogen 0.3.3-2 has caused the Debian Bug report #1016681, regarding python-mitogen: Build-Depends on python2 which Debian tries to remove to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1016681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-mitogen Version: 0.3.3-1 Severity: serious Hi all, We're trying to remove python2 from bookworm, but your package still Build-Depends on it. That looks like an oversight, but I might be wrong. Please update your package. Paul --- End Message --- --- Begin Message --- Source: python-mitogen Source-Version: 0.3.3-2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-mitogen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-mitogen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Aug 2022 13:56:33 +0200 Source: python-mitogen Architecture: source Version: 0.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1016681 Changes: python-mitogen (0.3.3-2) unstable; urgency=medium . * Drop Build-Depends on python2. (Closes: #1016681) - Patch: Stop the (trivial) testing against python2.7. Checksums-Sha1: 741dce70280ef6011b5ae527b34b0a8e7d2ed6a8 1769 python-mitogen_0.3.3-2.dsc 3fff9d4b75c9373037a1c483463180cf78448050 9652 python-mitogen_0.3.3-2.debian.tar.xz c2a94e03757cbba21fdebb0e8a6a2fb278520efc 5926 python-mitogen_0.3.3-2_source.buildinfo Checksums-Sha256: 893145410a670640fadffe34124b8c29734209d1bd67a5eaa236751f59e45373 1769 python-mitogen_0.3.3-2.dsc 8da7eda442de16e7ec38a541582e97db31273c4f5468ce2d5e241a38b4c7ab1a 9652 python-mitogen_0.3.3-2.debian.tar.xz bd4a32342246fd8473cb3e42547ee2318950005305e4226007c05ab2fedce5ed 5926 python-mitogen_0.3.3-2_source.buildinfo Files: 12a9cb722f37de11771291f125f10e28 1769 python optional python-mitogen_0.3.3-2.dsc b8ed71714de6fb52a0887751cb809a1e 9652 python optional python-mitogen_0.3.3-2.debian.tar.xz b81fc344f5baba51f915b90054785b8f 5926 python optional python-mitogen_0.3.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYu5XJhQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2HNwAP9eY/iLsYrUFAAXuq0I0HmFzXUbNFjG 2mUBtJV/eK7GdgD/SxNqDfMAa612TaEiN/khXxZ3+h4IqN5g3VqPyDNxSwE= =nSZK -END PGP SIGNATURE End Message ---
Bug#1016732: node-sockjs throws: TypeError: Cannot read properties of undefined (reading 'addEventListener') at WebSocketReceiver.setUp
Package: node-sockjs Version: 0.3.24+~0.3.33-1 Severity: serious X-Debbugs-Cc: e...@ericebrown.com Hi, On running shiny-server with 0.3.24+~0.3.33-1 it chokes with: | [2022-08-06T04:59:03.613] [ERROR] shiny-server - Uncaught exception: TypeError: Cannot read properties of undefined (reading 'addEventListener') | [2022-08-06T04:59:03.614] [ERROR] shiny-server - TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | [2022-08-06T04:59:03.615] [INFO] shiny-server - Stopping listener on http://[::]:3838 | [2022-08-06T04:59:03.615] [INFO] shiny-server - Shutting down worker processes (with notification) | /usr/lib/shiny-server/lib/main.js:391 | throw err; | ^ | | TypeError: Cannot read properties of undefined (reading 'addEventListener') |at WebSocketReceiver.setUp (/usr/share/nodejs/sockjs/lib/trans-websocket.js:76:24) |at new GenericReceiver (/usr/share/nodejs/sockjs/lib/transport.js:313:12) |at new WebSocketReceiver (/usr/share/nodejs/sockjs/lib/trans-websocket.js:63:9) |at ws.onopen (/usr/share/nodejs/sockjs/lib/trans-websocket.js:31:55) |at WebSocket.dispatchEvent (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api/event_target.js:24:30) |at WebSocket._open (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:144:10) |at Hybi. (/usr/share/nodejs/faye-websocket/lib/faye/websocket/api.js:35:49) |at Hybi.emit (node:events:513:28) |at Hybi._open (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:148:10) |at Hybi.start (/usr/share/nodejs/websocket-driver/lib/websocket/driver/base.js:105:34) | | Node.js v18.6.0 While it is running perfectly ok _with 0.3.24-2_. Since this is not a new release, there is a regression with the new changelog revision. In particular, it seems that something is off with the coffeescript generated files. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-sockjs depends on: pn node-faye-websocket ii node-uuid 8.3.2+~8.3.3-2 pn node-websocket-driver node-sockjs recommends no packages. node-sockjs suggests no packages.
Bug#1009281: [Debichem-devel] Bug#1009281: Bug#1009281: Bug#1009281: Should cinfony be removed?
Hi,
On 2022-07-24 21:18, Moritz Mühlenhoff wrote:
> Did you get any reply? Otherwise let's go ahead with the removal.
I have checked upstream's master branch and it indeed seems to contain
at least some porting to Python 3. I have opened a branch on Salsa
('python3') to attempt to package it. However, the port does not seem to
be complete, as I get syntax errors due to Python 2 syntax.
Best,
Andrius
Processed: Bug#1016681 marked as pending in python-mitogen
Processing control commands: > tag -1 pending Bug #1016681 [src:python-mitogen] python-mitogen: Build-Depends on python2 which Debian tries to remove Added tag(s) pending. -- 1016681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016681: marked as pending in python-mitogen
Control: tag -1 pending Hello, Bug #1016681 in python-mitogen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-mitogen/-/commit/824e449a48cefb81ed3becdc392c51f66e27f9bd Drop Build-Depends on python2. (Closes: #1016681) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016681
Processed: not found....
Processing commands for cont...@bugs.debian.org:
> # oops
> notfixed 1013531 1013531
Bug #1013531 {Done: Paul Gevers } [src:maim] maim: FTBFS:
unsatisfiable build-dependencies: libslopy7.6, libslopy-dev
The source 'maim' and version '1013531' do not appear to match any binary
packages
No longer marked as fixed in versions maim/1013531.
> notfound 1013531 5.7.4-2
Bug #1013531 {Done: Paul Gevers } [src:maim] maim: FTBFS:
unsatisfiable build-dependencies: libslopy7.6, libslopy-dev
No longer marked as found in versions maim/5.7.4-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012895: marked as done (aptitude: ftbfs with GCC-12)
Your message dated Sat, 06 Aug 2022 11:48:53 + with message-id and subject line Bug#1012895: fixed in aptitude 0.8.13-5 has caused the Debian Bug report #1012895, regarding aptitude: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1012895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aptitude Version: 0.8.13-4 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/aptitude_0.8.13-4_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /usr/include/cppunit/tools/StringHelper.h:25:9: note: mismatched types ‘const _CharT*’ and ‘std::vector >’ 25 | ost << x; | ^~~~ /usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_Ch, _Tr>& std::operator<<(basic_ostream<_Ch, _Tr>&, const char*)’ 302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s) | ^~~~ /usr/include/c++/12/bits/ostream.tcc:302:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:615:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const char*)’ 615 | operator<<(basic_ostream& __out, const char* __s) | ^~~~ /usr/include/c++/12/ostream:615:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:628:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’ 628 | operator<<(basic_ostream& __out, const signed char* __s) | ^~~~ /usr/include/c++/12/ostream:628:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const signed char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:633:5: note: candidate: ‘template std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’ 633 | operator<<(basic_ostream& __out, const unsigned char* __s) | ^~~~ /usr/include/c++/12/ostream:633:5: note: template argument deduction/substitution failed: /usr/include/cppunit/tools/StringHelper.h:25:9: note: cannot convert ‘x’ (type ‘const std::vector >’) to type ‘const unsigned char*’ 25 | ost << x; | ^~~~ /usr/include/c++/12/ostream:754:5: note: candidate: ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&)’ 754 | operator<<(_Ostream&& __os, const _Tp& __x) | ^~~~ /usr/include/c++/12/ostream:754:5: note: template argument deduction/substitution failed: /usr/include/c++/12/ostream: In substitution of ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&) [with _Ostream = std::__cxx11::basic_ostringstream&; _Tp = std::vector >]’: /usr/include/cppunit/tools/String
Bug#1006245: marked as done (libwebsockets: FTBFS with OpenSSL 3.0)
Your message dated Sat, 06 Aug 2022 11:50:00 + with message-id and subject line Bug#1006245: fixed in libwebsockets 4.1.6-2 has caused the Debian Bug report #1006245, regarding libwebsockets: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1006245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libwebsockets Version: 4.0.20-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: | [ 31%] Building C object CMakeFiles/websockets.dir/lib/tls/openssl/openssl-server.c.o | /usr/bin/cc -I/<>/include -I/<>/plugins -I/<>/lib/core -I/<>/lib/core-net -I/<>/lib/event-libs -I/<>/include/abstract -I/<>/lib/tls -I/<>/lib/roles -I/<>/lib/event-libs/libuv -I/<>/lib/event-libs/poll -I/<>/lib/event-libs/libevent -I/<>/lib/event-libs/glib -I/<>/lib/event-libs/libev -I/<>/lib/jose/jwe -I/<>/lib/jose/jws -I/<>/lib/jose -I/<>/lib/misc -I/<>/lib/roles/http -I/<>/lib/roles/http/compression -I/<>/lib/roles/h1 -I/<>/lib/roles/h2 -I/<>/lib/roles/ws -I/<>/lib/roles/cgi -I/<>/lib/roles/dbus -I/<>/lib/roles/raw-proxy -I/<>/lib/abstract -I/<>/lib/system/async-dns -I/<>/lib/roles/mqtt -I/<>/lib/plat/unix -I/<>/obj-x86_64-linux-gnu -I/<>/lib -Wall -Wsign-compare -Wstrict-aliasing -Wuninitialized -Werror -fvisibility=hidden -Wundef -Wtype-limits -Wignored-qualifiers -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -Wno-error=format-truncation -Wno-error=format-overflow -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -MD -MT CMakeFiles/websockets.dir/lib/tls/openssl/openssl-server.c.o -MF CMakeFiles/websockets.dir/lib/tls/openssl/openssl-server.c.o.d -o CMakeFiles/websockets.dir/lib/tls/openssl/openssl-server.c.o -c /<>/lib/tls/openssl/openssl-server.c | /<>/lib/tls/openssl/openssl-server.c: In function ‘lws_tls_server_certs_load’: | /<>/lib/tls/openssl/openssl-server.c:403:9: error: ‘EC_KEY_new_by_curve_name’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 403 | ecdh = EC_KEY_new_by_curve_name(ecdh_nid); | | ^~~~ | In file included from /usr/include/openssl/x509.h:33, | from /usr/include/openssl/ssl.h:31, | from /<>/include/libwebsockets.h:250, | from /<>/lib/core/private-lib-core.h:135, | from /<>/lib/tls/openssl/openssl-server.c:25: | /usr/include/openssl/ec.h:996:31: note: declared here | 996 | OSSL_DEPRECATEDIN_3_0 EC_KEY *EC_KEY_new_by_curve_name(int nid); | | ^~~~ | /<>/lib/tls/openssl/openssl-server.c:409:9: error: ‘EC_KEY_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 409 | EC_KEY_free(ecdh); | | ^~~ | In file included from /usr/include/openssl/x509.h:33, | from /usr/include/openssl/ssl.h:31, | from /<>/include/libwebsockets.h:250, | from /<>/lib/core/private-lib-core.h:135, | from /<>/lib/tls/openssl/openssl-server.c:25: | /usr/include/openssl/ec.h:1001:28: note: declared here | 1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key); | |^~~ | /<>/lib/tls/openssl/openssl-server.c:451:9: error: ‘EVP_PKEY_get1_EC_KEY’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 451 | EC_key = EVP_PKEY_get1_EC_KEY(pkey); | | ^~ | In file included from /usr/include/openssl/x509.h:29, | from /usr/include/openssl/ssl.h:31, | from /<>/include/libwebsockets.h:250, | from /<>/lib/core/private-lib-core.h:135, | from /<>/lib/tls/openssl/openssl-server.c:25: | /usr/include/openssl/evp.h:1374:19: note: declared here | 1374 | struct ec_key_st *EVP_PKEY_get1_EC_KEY(EVP_PKEY *pkey); | | ^~~~ | /<>/lib/tls/openssl/openssl-server.c:459:9: error: ‘EC_KEY_free’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 459 | EC_KEY_free(EC_key); | | ^~~ | In file included from /usr/include/openssl/x509.h:33, | from /usr/include/openssl/ssl.h:31, | from /<>/include/libwebsockets.h:250, | from /<>/lib/core/private-lib-core.h:135,
Processed: tagging 1012895
Processing commands for cont...@bugs.debian.org: > tags 1012895 + pending Bug #1012895 [src:aptitude] aptitude: ftbfs with GCC-12 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nfft breaks pynfft autopkgtest on i386: Segmentation fault
Processing commands for cont...@bugs.debian.org:
> reassign 1013940 src:nfft 3.3.2-2.1
Bug #1013940 {Done: Andreas Tille } [src:nfft, src:pynfft]
nfft breaks pynfft autopkgtest on i386: Segmentation fault
Bug reassigned from package 'src:nfft, src:pynfft' to 'src:nfft'.
No longer marked as found in versions pynfft/1.3.2-5 and nfft/3.3.2-2.1.
Ignoring request to alter fixed versions of bug #1013940 to the same values
previously set
Bug #1013940 {Done: Andreas Tille } [src:nfft] nfft breaks
pynfft autopkgtest on i386: Segmentation fault
Marked as found in versions nfft/3.3.2-2.1.
> fixed 1013940 3.5.3-1
Bug #1013940 {Done: Andreas Tille } [src:nfft] nfft breaks
pynfft autopkgtest on i386: Segmentation fault
Marked as fixed in versions nfft/3.5.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016454: megadepth: autopkgtest failure on s390x: segmentation fault
Hi Bilal, You added in autopkgtests for this one -- could you please take a look? On Sun, 31 Jul 2022 22:06:50 +0200 Paul Gevers wrote: > Source: megadepth > Version: 1.2.0-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainer(s), > > You recently added an autopkgtest to your package megadepth, great. > However, it fails on s390x. Currently this failure is blocking the > migration to testing [1]. Can you please investigate the situation and > fix it? > > I copied some of the output at the bottom of this report. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=megadepth > > https://ci.debian.net/data/autopkgtest/testing/s390x/m/megadepth/23583699/log.gz > > [93m[1mRunning Tests[0m > [93m[1mTest 1[0m > building whole annotation region map done > 2 chromosomes for annotated regions read > 0 chromosomes for annotated regions read, collapsed > total number of annotations in collapsed: 0 > Processing BAM: "tests/test_noprefix.bam" > /tmp/autopkgtest-lxc.gmfzuwos/downtmp/build.jJn/src/debian/tests/run-unit-test: > > line 33: 1590 Segmentation fault megadepth tests/test_noprefix.bam > --prefix test.bam --threads 4 --bigwig --auc --min-unique-qual 10 > --annotation tests/test_exons.bed --frag-dist --alts --include-softclip > --only-polya --read-ends --test-polya --no-annotation-stdout > --no-auc-stdout --filter-out 260 --add-chr-prefix human > autopkgtest [04:42:40]: test run-unit-test > -- Best, Nilesh signature.asc Description: PGP signature
Processed: Re: maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev
Processing control commands: > notfound -1 1013531 Bug #1013531 [src:maim] maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev The source 'maim' and version '1013531' do not appear to match any binary packages Ignoring request to alter found versions of bug #1013531 to the same values previously set > close -1 1013531 Bug #1013531 [src:maim] maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev The source 'maim' and version '1013531' do not appear to match any binary packages Marked as fixed in versions maim/1013531. Bug #1013531 [src:maim] maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev Marked Bug as done -- 1013531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013531: maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev
Control: notfound -1 1013531
Control: close -1 1013531
Dear Antoine, all,
You marked this bug as fixed with the same version as it was reported
against. This "confuses" the BTS in the sense that it doesn't consider
the bug to be fixed. Hence, I removed the "found" version to improve the
situation.
Your last upload included the amd64 binary. I have triggered a binNMU to
get it build on a buildd because otherwise the package wasn't migrating
(already for 60 days).
Assuming that with the fixes above, the package can finally migrate.
One thing I spotted while investigating the situation. maim now
hard-codes the Build-Depends and Depends on libslopy7.6 which means that
during slop transitions maim needs a source full upload. libslop-dev
should always depend on the correct named library already, so it
shouldn't be needed as a Build-Depends and unless this are implemented
wrong, ${shlibs:Depends} should also generate the right Depends. If you
drop both, the package only needs a no-change rebuild (binNMU) during
transitions, making the transition much easier to manage from the
Release Team side.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
