Processed: block 952095 with 953537
Processing commands for cont...@bugs.debian.org:
> block 952095 with 953537
Bug #952095 {Done: Nathan Scott } [src:xfsdump] xfsdump:
FTBFS: gcc: fatal error: no input files
952095 was not blocked by any bugs.
952095 was not blocking any bugs.
Added blocking bug(s) of 952095: 953537
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 952256
Processing commands for cont...@bugs.debian.org:
> tags 952256 + fixed
Bug #952256 {Done: Michael Tautschnig } [src:cbmc] cbmc:
FTBFS: cp: cannot stat
'../../../lib/java-models-library/target/core-models.jar': No such file or
directory
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#944020: marked as pending in python-libusb1
Control: tag -1 pending Hello, Bug #944020 in python-libusb1 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/modules/python-libusb1/-/commit/cd48b3671197558b001308f3c87347eab46183ad Rename binary to python- (Closes: #944020) and new upstream release. (this message was generated automatically) -- Greetings https://bugs.debian.org/944020
Processed: Bug#944020 marked as pending in python-libusb1
Processing control commands: > tag -1 pending Bug #944020 [python3-libusb1] python3-libusb1: should be named python3-usb1, since it installs a `usb1` top-level module Added tag(s) pending. -- 944020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956543: freecad: FTBFS with new opencascade 7.4 (library transition)
Hello Gregor, On Tuesday, May 12, 2020 6:58:04 PM CDT Gregor Riepl wrote: > > Status update why this package has not yet been updated: > > If the freecad is rebuilt against pyside2, it will run > > into 945376 at runtime, namely when opening the PartDesign workbench. > > As this is a major feature in freecad and the current version in > > sid works its better to wait until pyside2 has been fixed. > > 945376 got a fix in experimental now. > > freecad is currently not co-installable with kicad, because the latter > was already transitioned to opencascade 7.4. > > Would you consider a fixed freecad upload to experimental as well? That > way, the pyside2 bugfix could be tested with an updated freecad build. > Yes, I am preparing an upload now and should have things resolved in the next day or two. > > For that, several QT dependencies pyside have to be updted: > > - qtdatavis3d-everywhere-src > > - qtscxml-everywhere-src > > - qtspeech-opensource-src > > - qtxmlpatterns-opensource-src > > > > Bugs have been filed against those package, they should block this bug. > > I didn't see any bug reports on these packages, is there still work to > be done on them? > > They are already uploaded as of about a week ago.
Bug#960415: marked as done (python3-sphinx-gallery: package empty)
Your message dated Wed, 13 May 2020 02:37:39 + with message-id and subject line Bug#960415: fixed in sphinx-gallery 0.6.2-2 has caused the Debian Bug report #960415, regarding python3-sphinx-gallery: package empty 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.) -- 960415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-sphinx-gallery Version: 0.6.2-1 Severity: grave Dear Maintainer, The version 0.6.2-1 of the package is empty and only contains: usr/share/doc/python3-sphinx-gallery/changelog.Debian.gz usr/share/doc/python3-sphinx-gallery/changelog.gz usr/share/doc/python3-sphinx-gallery/copyright And, so is completely unusable when I tried to generate a documentation which needed it. -- Regards Sudip --- End Message --- --- Begin Message --- Source: sphinx-gallery Source-Version: 0.6.2-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of sphinx-gallery, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated sphinx-gallery package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 22:18:52 -0400 Source: sphinx-gallery Architecture: source Version: 0.6.2-2 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 960415 Changes: sphinx-gallery (0.6.2-2) unstable; urgency=medium . * debian/rules - set PYBUILD_NAME, fixing installation of the module files; Closes: #960415 Checksums-Sha1: ad1fa569d6502f29d90e627e9e0f922969cdc3d0 2572 sphinx-gallery_0.6.2-2.dsc 963c1ae34fd413ed85f1208523df5f3546b9009a 4756 sphinx-gallery_0.6.2-2.debian.tar.xz 886db40496b265c97bff824f3776ab4ed3479e9e 10699 sphinx-gallery_0.6.2-2_source.buildinfo Checksums-Sha256: 6c6445f96e3e702245f1fbfe3c014faaae14fea85e0ba098f63e89e17b6aa827 2572 sphinx-gallery_0.6.2-2.dsc 50c953e1ecfde056e8c5de7180953e892e5de0f078887a668a5561e32d981ced 4756 sphinx-gallery_0.6.2-2.debian.tar.xz f743cab8f2d3c90d523698d757d3f62759427c6e97d18c24d614696cac2eae92 10699 sphinx-gallery_0.6.2-2_source.buildinfo Files: 4941cf48fd9947834ce261a2977ac19d 2572 python optional sphinx-gallery_0.6.2-2.dsc c6f91a631a31def949d875da856d1205 4756 python optional sphinx-gallery_0.6.2-2.debian.tar.xz 83f0870b8c30eb3c8ee42ed3008af86f 10699 python optional sphinx-gallery_0.6.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl67WTAACgkQh588mTgB qU96lhAAyOuKcI28oSIXdAj1dHtgE5fOUcCK41tfmr/N9ko8X6HMtlDboiO3lRXP 43JwBgF0XhvTWD/bup4qoIm6T7f8VYB1T+ry/xQn4Ztr7N7XptpiWWPEYrXjXSft lfcG9MGZflKvlayxvmiIGlGZ5NMTp2ATFr/lq7LToxCFkjUeN7My2HkUTEfO7GSD osDTC1hSnGcx1NelYSTIVvjcl9RM863b7MWZysCO/hNm/hB5xDXfw4sZ+9vjG9jR p91ydOmPd1lRUt9g89UFc0TGMA8KSyfsKJUH3yRZO6qLxVeyC6DQezbpKtcQIuag I54hp0nJ4pa9bPAL4ZRSJvkgg3izwGUqFzt3umsyafw7FbicfyYIMzWVxh8Hlzjb dNXi5jkTpecnvG/Yx5MeTsviXoMHKci+Bd1F2SuxpFmFFd4rgjYcItnu5R64XME/ 05z82kZEGpbPdAhHW1hhk6wYt1cEKsRzWlF3ne8tOXqJkLOUMIT4agYHZJxgxsdU 6DfG6JtgoInCKwfRIN0e9enzBu0Nn2RJb9j+FQSR+pSXvqXVmZhmxbYdgd/fG+Vw SggTdD+yKwzskVIPGdUCCk0ypC3pCjcZXIto91cllNvmLKMiHowUMlFcJgSO/GXa jUh+EDs0UNAtma2bzdsE/mQrHB4bwVFnotXAex1am3znFtJznGE= =FpUV -END PGP SIGNATURE End Message ---
Processed: Bug#960415 marked as pending in sphinx-gallery
Processing control commands: > tag -1 pending Bug #960415 [python3-sphinx-gallery] python3-sphinx-gallery: package empty Added tag(s) pending. -- 960415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960415: marked as pending in sphinx-gallery
Control: tag -1 pending Hello, Bug #960415 in sphinx-gallery 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/modules/sphinx-gallery/-/commit/742112ffce27d9869fb67f4426be655578ddb11c set PYBUILD_NAME, fixing installation of the module files; Closes: #960415 (this message was generated automatically) -- Greetings https://bugs.debian.org/960415
Bug#956543: freecad: FTBFS with new opencascade 7.4 (library transition)
> Status update why this package has not yet been updated: > If the freecad is rebuilt against pyside2, it will run > into 945376 at runtime, namely when opening the PartDesign workbench. > As this is a major feature in freecad and the current version in > sid works its better to wait until pyside2 has been fixed. 945376 got a fix in experimental now. freecad is currently not co-installable with kicad, because the latter was already transitioned to opencascade 7.4. Would you consider a fixed freecad upload to experimental as well? That way, the pyside2 bugfix could be tested with an updated freecad build. > For that, several QT dependencies pyside have to be updted: > - qtdatavis3d-everywhere-src > - qtscxml-everywhere-src > - qtspeech-opensource-src > - qtxmlpatterns-opensource-src > > Bugs have been filed against those package, they should block this bug. I didn't see any bug reports on these packages, is there still work to be done on them?
Bug#947568: mixxx: diff for NMU version 2.2.3~dfsg-1.1
Control: tags 947568 + patch Dear maintainer, It looks like the relevant upstream patch is https://github.com/mixxxdj/mixxx/pull/2201/commits/03fad27e1f0f18ec83c9a4bc5f03f28948cd44fb I've prepared an NMU for mixxx (versioned as 2.2.3~dfsg-1.1). The diff is attached to this message. Regards. SR diff -Nru mixxx-2.2.3~dfsg/debian/changelog mixxx-2.2.3~dfsg/debian/changelog --- mixxx-2.2.3~dfsg/debian/changelog 2020-01-10 13:33:58.0 -0800 +++ mixxx-2.2.3~dfsg/debian/changelog 2020-05-12 16:07:23.0 -0700 @@ -1,3 +1,11 @@ +mixxx (2.2.3~dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Cherry-pick an upstream patch to fix a FTBFS with Scons under Python 3. +(Closes: #947568) + + -- Stefano Rivera Tue, 12 May 2020 16:07:23 -0700 + mixxx (2.2.3~dfsg-1) unstable; urgency=medium [ Ondřej Nový ] diff -Nru mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch --- mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch 1969-12-31 16:00:00.0 -0800 +++ mixxx-2.2.3~dfsg/debian/patches/0005-scons-3.patch 2020-05-12 16:06:52.0 -0700 @@ -0,0 +1,21 @@ +Description: Build correctly under scons on Python 3 +Bug-Upstream: https://bugs.launchpad.net/mixxx/+bug/1817742 +Bug-Debian: https://bugs.debian.org/947568 +Author: Jan Holthuis +Origin: upstream, https://github.com/mixxxdj/mixxx/pull/2201/commits/03fad27e1f0f18ec83c9a4bc5f03f28948cd44fb + +--- a/build/depends.py b/build/depends.py +@@ -1285,7 +1285,11 @@ + 'preferences/dialog/dlgprefvinyldlg.ui', + 'preferences/dialog/dlgprefwaveformdlg.ui', + ] +-map(Qt.uic(build), ui_files) ++ ++# In Python 3.x, map() returns a "map object" (instead of a list), ++# which is evaluated on-demand rather than at once. To invoke uic ++# for all *.ui files at once, we need to cast it to a list here. ++list(map(Qt.uic(build), ui_files)) + + if build.platform_is_windows: + # Add Windows resource file with icons and such diff -Nru mixxx-2.2.3~dfsg/debian/patches/series mixxx-2.2.3~dfsg/debian/patches/series --- mixxx-2.2.3~dfsg/debian/patches/series 2020-01-10 13:32:29.0 -0800 +++ mixxx-2.2.3~dfsg/debian/patches/series 2020-05-12 15:56:06.0 -0700 @@ -2,3 +2,4 @@ 0002-desktop_file.patch 0003-soundtouch.patch 0004-remove_inappropriate_arm_flags.patch +0005-scons-3.patch
Processed: mixxx: diff for NMU version 2.2.3~dfsg-1.1
Processing control commands: > tags 947568 + patch Bug #947568 [src:mixxx] FTBFS with scons 3.1.2-1 Added tag(s) patch. -- 947568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952868: OpenSSL linking without license exception
Am 11.05.20 um 09:05 schrieb Rhonda D'Vine: > Without libssl-dev installed in > the building chroot this fails for me. Can you revisit this, and check > where you might have missed something? Try this new patch version. It is tested to compile without libssl-dev installed. >From 5a04599fa6d10e34df6695bb21adb352f8a1dd7d Mon Sep 17 00:00:00 2001 From: Bastian Germann Date: Sun, 1 Mar 2020 11:19:53 +0100 Subject: [PATCH] Replace OpenSSL with wolfSSL --- debian/control | 2 +- debian/control.in | 2 +- debian/patches/01wolfssl-crypto | 16 debian/patches/04omit-ssleay| 20 debian/patches/series | 2 ++ debian/rules| 2 +- 6 files changed, 41 insertions(+), 3 deletions(-) create mode 100644 debian/patches/01wolfssl-crypto create mode 100644 debian/patches/04omit-ssleay diff --git a/debian/control b/debian/control index 5e35ef9..1d650a0 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~), libsdl2-image-dev (>= 2.0.0), libboost-iostreams-dev, libboost-test-dev, libboost-regex-dev, libboost-serialization-dev, libboost-system-dev, libboost-thread-dev, libboost-program-options-dev, libboost-filesystem-dev, libboost-locale-dev, - libboost-random-dev, libpng-dev, libreadline-dev, libssl-dev, + libboost-random-dev, libpng-dev, libreadline-dev, libwolfssl-dev, libpango1.0-dev, libvorbis-dev, cmake (>= 2.6) Standards-Version: 4.1.4 Uploaders: Rhonda D'Vine , diff --git a/debian/control.in b/debian/control.in index f97ece5..b57f2df 100644 --- a/debian/control.in +++ b/debian/control.in @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~), libsdl2-image-dev (>= 2.0.0), libboost-iostreams-dev, libboost-test-dev, libboost-regex-dev, libboost-serialization-dev, libboost-system-dev, libboost-thread-dev, libboost-program-options-dev, libboost-filesystem-dev, libboost-locale-dev, - libboost-random-dev, libpng-dev, libreadline-dev, libssl-dev, + libboost-random-dev, libpng-dev, libreadline-dev, libwolfssl-dev, libpango1.0-dev, libvorbis-dev, cmake (>= 2.6) Standards-Version: 4.1.4 Uploaders: Rhonda D'Vine , diff --git a/debian/patches/01wolfssl-crypto b/debian/patches/01wolfssl-crypto new file mode 100644 index 000..4b3fa74 --- /dev/null +++ b/debian/patches/01wolfssl-crypto @@ -0,0 +1,16 @@ +Author: Bastian Germann vim:ft=diff: +Description: Link with wolfssl instead of libcrypto. + +--- a/cmake/FindCrypto.cmake b/cmake/FindCrypto.cmake +@@ -1,8 +1,8 @@ + # OpenSSL crypto library + +-find_path(CRYPTO_INCLUDE_DIR openssl/md5.h) ++find_path(CRYPTO_INCLUDE_DIR openssl/md5.h /usr/include/wolfssl) + +-find_library(CRYPTO_LIBRARY crypto) ++find_library(CRYPTO_LIBRARY wolfssl) + + # handle the QUIETLY and REQUIRED arguments and set XXX_FOUND to TRUE if all listed variables are TRUE + INCLUDE(FindPackageHandleStandardArgs) diff --git a/debian/patches/04omit-ssleay b/debian/patches/04omit-ssleay new file mode 100644 index 000..213a253 --- /dev/null +++ b/debian/patches/04omit-ssleay @@ -0,0 +1,20 @@ +Author: Bastian Germann vim:ft=diff: +Description: Omit SSLeay call which has linking problems. + +diff --git a/src/build_info.cpp b/src/build_info.cpp +index 263841e..ef61201 100644 +--- a/src/build_info.cpp b/src/build_info.cpp +@@ -239,12 +239,6 @@ version_table_manager::version_table_manager() + // OpenSSL/libcrypto + // + +-#ifndef __APPLE__ +- compiled[LIB_CRYPTO] = format_openssl_version(OPENSSL_VERSION_NUMBER); +- linked[LIB_CRYPTO] = format_openssl_version(SSLeay()); +- names[LIB_CRYPTO] = "OpenSSL/libcrypto"; +-#endif +- + // + // Cairo + // diff --git a/debian/patches/series b/debian/patches/series index 57b6465..f08ba3d 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,2 +1,4 @@ +01wolfssl-crypto 02wesnoth-nolog-desktop-file 03wesnothd-name +04omit-ssleay diff --git a/debian/rules b/debian/rules index 02ad407..cbec12c 100755 --- a/debian/rules +++ b/debian/rules @@ -23,7 +23,7 @@ ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel)) CXXFLAGSDBG = -g1 endif -export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) +export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) -I/usr/include/wolfssl -DOPENSSL_ALL export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp $(CXXFLAGSDBG) export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -- 2.26.2
Bug#960254: marked as done (ir.lv2 FTBFS with lv2-dev 1.18.0-1)
Your message dated Tue, 12 May 2020 22:03:44 +
with message-id
and subject line Bug#960254: fixed in ir.lv2 1.3.4~dfsg0-3
has caused the Debian Bug report #960254,
regarding ir.lv2 FTBFS with lv2-dev 1.18.0-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.)
--
960254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ir.lv2
Version: 1.3.4~dfsg0-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ir.lv2.html
...
ir_gui.cc:1681:14: error: invalid conversion from 'void* (*)(const
_LV2UI_Descriptor*, const char*, const char*, LV2UI_Write_Function,
LV2UI_Controller, void**, const LV2_Feature* const*)' {aka 'void* (*)(const
_LV2UI_Descriptor*, const char*, const char*, void (*)(void*, unsigned int,
unsigned int, unsigned int, const void*), void*, void**, const LV2_Feature*
const*)'} to 'void* (*)(const LV2UI_Descriptor*, const char*, const char*,
LV2UI_Write_Function, LV2UI_Controller, void**, const LV2_Feature* const*)'
{aka 'void* (*)(const LV2UI_Descriptor*, const char*, const char*, void
(*)(void*, unsigned int, unsigned int, unsigned int, const void*), void*,
void**, const LV2_Feature* const*)'} [-fpermissive]
1681 | {IR_UI_URI, instantiate, cleanup, port_event, NULL}
| ^~~
| |
| void* (*)(const _LV2UI_Descriptor*, const char*, const
char*, LV2UI_Write_Function, LV2UI_Controller, void**, const LV2_Feature*
const*) {aka void* (*)(const _LV2UI_Descriptor*, const char*, const char*, void
(*)(void*, unsigned int, unsigned int, unsigned int, const void*), void*,
void**, const LV2_Feature* const*)}
make[2]: *** [Makefile:39: ir_gui.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ir.lv2
Source-Version: 1.3.4~dfsg0-3
Done: Dennis Braun
We believe that the bug you reported is fixed in the latest version of
ir.lv2, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dennis Braun (supplier of updated ir.lv2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 May 2020 19:00:37 +0200
Source: ir.lv2
Architecture: source
Version: 1.3.4~dfsg0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Dennis Braun
Closes: 960254
Changes:
ir.lv2 (1.3.4~dfsg0-3) unstable; urgency=medium
.
* Fix LV2 types (Closes: #960254)
* Bump dh-compat to 13
* Remove obosolete linker flags
* Add archive and remove obsolete name field in d/upstream/metadata
Checksums-Sha1:
39d6aca27416c4a01aafba5b41a3781da8a4df68 2158 ir.lv2_1.3.4~dfsg0-3.dsc
726f25b53d20d7596087040b807919b204643535 5552
ir.lv2_1.3.4~dfsg0-3.debian.tar.xz
Checksums-Sha256:
4a11653b5913d159e175d3ffbe9996e38d91794f69e4e766a035806abd116aa8 2158
ir.lv2_1.3.4~dfsg0-3.dsc
fe5e954b1be59d2e4fddedfa05552de2baf5965103f518342119611b4586a1c4 5552
ir.lv2_1.3.4~dfsg0-3.debian.tar.xz
Files:
8979478d0f9c535ad76998dbd3152470 2158 sound optional ir.lv2_1.3.4~dfsg0-3.dsc
89e2fb7f39aa9c13faa52a3494c8555d 5552 sound optional
ir.lv2_1.3.4~dfsg0-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl67GOEACgkQafL8UW6n
GZN4IA/+LnfHWnzvPyK/zZNil8Gsanw+idFL8OA2NbYECJSiArbACKFe/hODt7QE
kt1jTSBXNUqbFaCQDaU2ZNXhCQAbDj8Pu5Dt8Q+XxKs8zOtTkKPv72SOklwdZpNv
dQBz3xyAWz0MGwF3RhXpdiC8x1LqqWm5u1OLvNpzQINAd+5LO8NspbMODsE/g0AH
UHvotly8+xKwXm387Zf5iVd3rDUnY8vs3cw7nGjkws9fLx2fnpkm+9xm0eBJXlzE
P1y3armFsFq4HmdfLcRt/6sUGNpT6r3x84fuXLiPIxx3h+McB43gQNKVCQmcGFcN
S1emJo+AVlOCGzJmbdgdFjaj/HRV0zlHRDpcqO7GgprXL7l10zVTXbuazs0BVOya
un88DwS7ARVnDkiAaO8BaNFK5h4cB9W0AHzl13qT75UXVeO9ob5cIhqHEH7d+xXh
uIWFyitXrS/FbtuwRtRLdu9rUEcXWslIarp3XalXXwlVxppSXangM1H8XoDmDnOt
o57OOBEGB53PlfWHF8vJWW+VSn2pYKhMP9rJ0djys3HSKFcDxp6+29xdNE29K/m9
rt5rzlSLuaaLDzaNr/0DHQk6LUTflIBZEKs6xk6aClZhVG+2sehDAWZyWCnMgFlD
j44WMXGIvYaNL9/3vzanTFK7b5FPtw/znz9W8YKXjoodXEN7mNE=
=o5HV
-END PGP SIGNATURE End Message ---
Bug#958460: marked as done (FTBFS with no network)
Your message dated Tue, 12 May 2020 22:03:34 + with message-id and subject line Bug#958460: fixed in appstream-generator 0.8.2-1 has caused the Debian Bug report #958460, regarding FTBFS with no network 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.) -- 958460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: appstream-generator Version: 0.8.1-1 Severity: serious This is a policy violation, as the build process must not rely on network accessibility. Error message: [139/147] /usr/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 -o docs/appstream-generator.1 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl ../docs/appstream-generator.1.xml I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd ../docs/appstream-generator.1.xml:12: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; ]> ^ While the message above is supposed to only be a warning, this reproducibly leads to a test timeout (30.01s). So either the timeout needs to be fixed or this specific test changed to no try to download the entity or this specific test needs to be disabled. Cheers, Sven --- End Message --- --- Begin Message --- Source: appstream-generator Source-Version: 0.8.2-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of appstream-generator, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated appstream-generator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 22:26:42 +0200 Source: appstream-generator Architecture: source Version: 0.8.2-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klumpp Changed-By: Matthias Klumpp Closes: 958460 959893 Changes: appstream-generator (0.8.2-1) unstable; urgency=medium . * New upstream version: 0.8.2 * Build-depend on docbook-xml explicitly (Closes: #958460) * Drop dependency on curl * Add build dependency on libsoup2.4-dev * Bump dependency on GLibD to >= 2.2 - This surprisingly fixes linkage of libglibd, and therefore closes: #959893 Possibly GLibD was miscompiled before in an LDC transition to trigger this issue. We will have to keep an eye on this, so the problem doesn't reappear. Checksums-Sha1: 3f9766be7ff75cdc13b5c43fd0269eaeea253d6c 2361 appstream-generator_0.8.2-1.dsc e0d37229210252fbb10febb20f12f4c573322d13 810691 appstream-generator_0.8.2.orig.tar.gz a6ba6b67ee83c305931c8b167b1d917847d05b03 4640 appstream-generator_0.8.2-1.debian.tar.xz d9e4ac553e944f67711ed29f8c64238375b27e61 16303 appstream-generator_0.8.2-1_source.buildinfo Checksums-Sha256: 68ec1d192e3bdd7b73dbdaf35260cd80b19b74c27b88b5e618400b5c6c25d7e0 2361 appstream-generator_0.8.2-1.dsc 41a6563dde303adcd60f28fbd89f14eb2a4083cec8f1021c22409c769088fdc2 810691 appstream-generator_0.8.2.orig.tar.gz d515eb75e48680b1b0af6a23c58223bbf6733862ee09d55dbecef4e387313137 4640 appstream-generator_0.8.2-1.debian.tar.xz 0ec47b3e84a8ddfcff8c0906495307d01eb14739482afd25e081e3d3eefd2dda 16303 appstream-generator_0.8.2-1_source.buildinfo Files: 5b5454567f57c7f3b4aafc1c5ebf27f4 2361 misc optional appstream-generator_0.8.2-1.dsc a7ef2948933621256be1f3603e54ec49 810691 misc optional appstream-generator_0.8.2.orig.tar.gz 25f69e7fb8e2ce005a900f5fe2eceda5 4640 misc optional appstream-generator_0.8.2-1.debian.tar.xz fd85dc8b9c6c3f30a8551bc274e8efcf 16303 misc optional appstream-generator_0.8.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl67GT8PHG1ha0BkZWJp YW4ub3JnAAoJEElMil+/Tezrrd8P/05891Vcdck4WGctYV7TXc2Z6qpmGQ0kyxmb f0/iDev9qxEOv2OlxeYFxEMP7SgvJh4I3GAgqlWWE0FdBdME3cx5aT+4LL3I6bpX K5y0lUsdqIiuIc1iyFnmcCy5UKIqygJ5aE8iekFEkyMhF//94hmLfGlIEx66CyTC
Bug#959893: marked as done (appstream-generator: Link against libglibd-2.0.so broken)
Your message dated Tue, 12 May 2020 22:03:34 + with message-id and subject line Bug#959893: fixed in appstream-generator 0.8.2-1 has caused the Debian Bug report #959893, regarding appstream-generator: Link against libglibd-2.0.so broken 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.) -- 959893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: appstream-generator Version: 0.8.1-1+b1 Severity: grave Justification: renders package unusable Hi maintainer, the package possible needs rebuilding. > appstream-generator: error while loading shared libraries: libglibd-2.0.so: > cannot open shared object file: No such file or directory libglibd-2.0 now has an explicit .0 suffix version: > $ apt-file search libglibd-2.0.so > libglibd-2.0-0: /usr/lib/x86_64-linux-gnu/libglibd-2.0.so.0 > libglibd-2.0-0: /usr/lib/x86_64-linux-gnu/libglibd-2.0.so.2.1.0 > libglibd-2.0-dev: /usr/lib/x86_64-linux-gnu/libglibd-2.0.so Adding a symlink helps, but not sure why this happened. > ln -s libglibd-2.0.so.0 /usr/lib/x86_64-linux-gnu/libglibd-2.0.so Regards Markus -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages appstream-generator depends on: ii libappstream40.12.10-2 ii libarchive13 3.4.0-2 ii libc62.30-4 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-4 ii libfreetype6 2.10.1-2 ii libgcc-s110-20200418-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4 ii libglib2.0-0 2.64.2-1 ii libjs-highlight.js 9.12.0+dfsg1-5 ii libjs-jquery-flot0.8.3+dfsg-1 ii liblmdb0 0.9.24-1 ii libpango-1.0-0 1.44.7-4 ii libphobos2-ldc-shared90 1:1.20.1-1 ii librsvg2-2 2.48.3-1 Versions of packages appstream-generator recommends: ii ffmpeg 7:4.2.2-1+b1 ii optipng 0.7.7-1+b1 appstream-generator suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: appstream-generator Source-Version: 0.8.2-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of appstream-generator, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated appstream-generator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 22:26:42 +0200 Source: appstream-generator Architecture: source Version: 0.8.2-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klumpp Changed-By: Matthias Klumpp Closes: 958460 959893 Changes: appstream-generator (0.8.2-1) unstable; urgency=medium . * New upstream version: 0.8.2 * Build-depend on docbook-xml explicitly (Closes: #958460) * Drop dependency on curl * Add build dependency on libsoup2.4-dev * Bump dependency on GLibD to >= 2.2 - This surprisingly fixes linkage of libglibd, and therefore closes: #959893 Possibly GLibD was miscompiled before in an LDC transition to trigger this issue. We will have to keep an eye on this, so the problem doesn't reappear. Checksums-Sha1: 3f9766be7ff75cdc13b5c43fd0269eaeea253d6c 2361 appstream-generator_0.8.2-1.dsc e0d37229210252fbb10febb20f12f4c573322d13 810691 appstream-generator_0.8.2.orig.tar.gz a6ba6b67ee83c305931c8b167b1d917847d05b03 4640 appstream-generator_0.8.2-1.debian.tar.xz d9e4ac553e944f67711ed29f8c64238375b27e61 16303 appstream-generator_0.8.2-1_source.buildinfo Checksums-Sha256: 68ec1d192e3bdd7b73dbdaf35260cd80b19b74c27b88b5e618400b5c6c25d7e0 2361
Bug#960250: marked as pending in guitarix
Control: tag -1 pending Hello, Bug #960250 in guitarix 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/multimedia-team/guitarix/-/commit/1eca54870db2ecbc0c2df3aee1670bd740a08d70 Fix LV2 types (Closes: #960250) (this message was generated automatically) -- Greetings https://bugs.debian.org/960250
Processed: Bug#960250 marked as pending in guitarix
Processing control commands: > tag -1 pending Bug #960250 [src:guitarix] guitarix FTBFS with lv2-dev 1.18.0-1 Added tag(s) pending. -- 960250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938108: [Pkg-xen-devel] Bug#938108: python-pyxenstore: Python2 removal in sid/bullseye
On 5/9/20 9:57 PM, Moritz Mühlenhoff wrote: > On Sat, May 09, 2020 at 02:36:24AM +0200, Thomas Goirand wrote: >> On 5/8/20 9:35 PM, Moritz Mühlenhoff wrote: >>> On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote: Package: src:python-pyxenstore Version: 0.0.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. >>> >>> Hi, >>> python-pyxenstore is dead upstream and there are no reverse deps, let's >>> remove? >>> >>> Cheers, >>> Moritz >> >> By all means, yes, remove this. >> I believe it is in Debian when I attempted to package XCP (aka: xen-api, >> aka xen-server, etc.), and that's long gone from Debian. > > Ack, I've just filed an RM bug. (seeing it happening) Also ACK from me. A while ago this confused me because I initially thought this was a binary package produced by src:xen, but it was not. At some point (I think it was our latest IRL work together day of the Debian Xen team) I realized that it really was not, and from that POV, I can confirm that it is not used by anything in there. Thanks, Hans
Bug#934031: marked as done (heimdal: FTBFS in stretch (failing tests))
Your message dated Wed, 13 May 2020 07:17:09 +1000
with message-id <87mu6c26qy@silverfish.pri>
and subject line Re: Bug#934031: heimdal: FTBFS in stretch (failing tests)
has caused the Debian Bug report #934031,
regarding heimdal: FTBFS in stretch (failing tests)
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.)
--
934031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:heimdal
Version: 7.1.0+dfsg-13+deb9u2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in stretch but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf --parallel
dh_testdir -i -O--parallel
dh_update_autotools_config -i -O--parallel
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:18: installing './compile'
configure.ac:20: installing './missing'
src/Makefile.am: installing './depcomp'
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'cf'.
libtoolize: copying file 'cf/libtool.m4'
libtoolize: copying file 'cf/ltoptions.m4'
libtoolize: copying file 'cf/ltsugar.m4'
libtoolize: copying file 'cf/ltversion.m4'
libtoolize: copying file 'cf/lt~obsolete.m4'
configure.ac:14: installing './compile'
configure.ac:10: installing './missing'
admin/Makefile.am: installing './depcomp'
patching file ./ltmain.sh
patching file ./lib/libedit/ltmain.sh
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security"
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" FCFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong" FFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong" GCJFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong"
LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" \
--libexecdir="\${prefix}/sbin" \
--enable-shared \
--prefix=/usr \
--includedir="\${prefix}/include" \
--with-openldap=/usr \
--with-sqlite3=/usr \
--with-libedit=/usr \
--enable-kcm \
--with-hdbdir=/var/lib/heimdal-kdc \
--without-openssl \
--infodir="\${prefix}/share/info" \
--datarootdir="\${prefix}/share" \
--libdir="\${prefix}/lib/x86_64-linux-gnu" \
--without-krb4
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
Bug#925411: marked as done (kernel-package: Not suitable for release)
Your message dated Tue, 12 May 2020 21:09:11 + with message-id and subject line Bug#960377: Removed package(s) from unstable has caused the Debian Bug report #925411, regarding kernel-package: Not suitable for release 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.) -- 925411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel-package Version: 13.018+nmu1 Severity: serious I discussed the state of kernel-package with Manoj and we agreed (see below) that it is not currently in a state suitable for release. Ben. --- From: Manoj Srivastava Date: Thu, 7 Mar 2019 23:15:30 -0800 Message-ID: To: Masahiro Yamada Cc: Ben Hutchings , Linux Kbuild mailing list , Liz Zhang , Lili Deng , Riku Voipio , Michal Marek , Linux Kernel Mailing List Subject: Re: [PATCH] kbuild: add workaround for Debian make-kpkg Hi, Well, if there are users, then I'll file the return bug, but I'll take a look to see how but rooted this is, and perhaps even try building personal imaged Deb packages again (I stopped doing that) If should not go into buster in it's current state. It should be killed dead of it can't be brought back to a working state. Manoj On Thu, Mar 7, 2019, 10:43 PM Masahiro Yamada wrote: > On Fri, Mar 8, 2019 at 6:56 AM Ben Hutchings wrote: > > > > On Wed, 2019-03-06 at 22:48 -0800, Manoj Srivastava wrote: > > > Hi, > > > > > > Does this have any users? > > Recently, I received a regression report. > So, yes. There are users. > > > > > I can take a stand at making it work, but I am > > > unsure of there are enough people interested in make-kpkg anymore to > make > > > it worthwhile. > > > > > > There is a man pager that might be of minor interest, but that can be > > > taken over by the kernel team if they want > > I do not want to maintain the dying package. > > > > > [...] > > > > I assume you're referring to kernel-img.conf. I would be happy to add > > that to linux-base, with some clarification of which settings are > > understood by which packages. > > > > I take it that you don't want kernel-package to be included in buster, > > so can you open an RC bug to say so? > > Also, could you make sure it won't come back to bullseye or later ? > > How about Ubuntu? Is it out of your control? > > > > > Ben. > > > > -- > > Ben Hutchings > > friends: People who know you well, but like you anyway. > > > > > > > -- > Best Regards > Masahiro Yamada > -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kernel-package depends on: ii bc 1.07.1-2+b1 ii binutils 2.31.1-15 ii build-essential 12.6 ii bzip21.0.6-9 ii dpkg-dev 1.19.5 ii file 1:5.35-4 ii gettext 0.19.8.1-9 ii kmod 26-1 ii lzma 9.22-2.1 ii po-debconf 1.0.21 ii xmlto0.0.28-2.1 ii xz-utils [lzma] 5.2.4-1 Versions of packages kernel-package recommends: ii cpio 2.12+dfsg-6 pn docbook-utils ii kernel-common 13.018+nmu1 pn uboot-mkimage Versions of packages kernel-package suggests: ii libncurses-dev 6.1+20181013-2 pn linux-source -- debconf-show failed --- End Message --- --- Begin Message --- Version: 13.018+nmu2+rm Dear submitter, as the package kernel-package has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960377 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the
Bug#959554: marked as done (oxygencursors: FTBFS: (process:24269): WARNING **: 03:13:06.033: Unable to create profile directory (Permission denied) (13))
Your message dated Tue, 12 May 2020 21:04:00 + with message-id and subject line Bug#959554: fixed in oxygencursors 0.0.2012-06-kde4.8-3 has caused the Debian Bug report #959554, regarding oxygencursors: FTBFS: (process:24269): WARNING **: 03:13:06.033: Unable to create profile directory (Permission denied) (13) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oxygencursors Version: 0.0.2012-06-kde4.8-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/builddir' > [ 0%] Generating ../oxy-black/index.theme > [ 0%] Generating ../oxy-black/config/X_cursor.in > [ 0%] Generating ../oxy-black/svg/x.svg > [ 0%] Generating ../oxy-black/png/90/x.png > > ** (process:24269): WARNING **: 03:13:06.033: Unable to create profile > directory (Permission denied) (13) > Unable to init server: Could not connect: Connection refused > Unknown option --without-gui > make[3]: *** [theme-black/CMakeFiles/package-black.dir/build.make:319: > oxy-black/png/90/x.png] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/05/01/oxygencursors_0.0.2012-06-kde4.8-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: oxygencursors Source-Version: 0.0.2012-06-kde4.8-3 Done: =?utf-8?q?Christian_G=C3=B6ttsche?= We believe that the bug you reported is fixed in the latest version of oxygencursors, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Göttsche (supplier of updated oxygencursors package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 May 2020 20:31:53 +0200 Source: oxygencursors Architecture: source Version: 0.0.2012-06-kde4.8-3 Distribution: unstable Urgency: medium Maintainer: Sune Vuorela Changed-By: Christian Göttsche Closes: 848144 959554 Changes: oxygencursors (0.0.2012-06-kde4.8-3) unstable; urgency=medium . * QA upload. * overhaul Debian packaging - switch to simple dh sequence - move install logic from custom scripts into cmake - use debhelper compat level 13 - bump to standards version 4.5.0 - update command line arguments for inkscape v1.0 (Closes: #959554) * d/patches: cherry-pick upstream commit correcting symlinks (Closes: #848144) * d/copyright: convert to machine-readable format (DEP-5) Checksums-Sha1: 93a0a72fcb578f393ea918000cb6bf105b6b3441 1958 oxygencursors_0.0.2012-06-kde4.8-3.dsc 10125b771305b11296732dbc2b1a4176043a25a6 7224 oxygencursors_0.0.2012-06-kde4.8-3.debian.tar.xz caef4c920fddbf2ca333a46e2bd65de82f00cc35 11143 oxygencursors_0.0.2012-06-kde4.8-3_source.buildinfo Checksums-Sha256: a2f73d4f8b7f5f87623fc25b44e1e0804c6c73bfc4e52f7714979d249f10c4df 1958 oxygencursors_0.0.2012-06-kde4.8-3.dsc b6bb04047d65f9836abbabef766cf8167578d280424a043cb34bb0cafb73980c 7224 oxygencursors_0.0.2012-06-kde4.8-3.debian.tar.xz 2ce9f23007f3a37f2dcf4da7b99de0b394531d9e8f8d56392375addc9e18c48a 11143 oxygencursors_0.0.2012-06-kde4.8-3_source.buildinfo Files: f3499d47149ec1f21f1adb9be29d0ca4 1958 x11 optional oxygencursors_0.0.2012-06-kde4.8-3.dsc 0d290644f84076ad86cf84ef08b6c151 7224 x11 optional oxygencursors_0.0.2012-06-kde4.8-3.debian.tar.xz aedc4e1daa1bba205df54374f654e8ee 11143 x11 optional oxygencursors_0.0.2012-06-kde4.8-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl67CkAACgkQweDZLphv
Bug#805208: marked as done (sigx: FTBFS: ./sigx/tunnel_context.h:145:18: error: using invalid field 'sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::m_bound_result')
Your message dated Tue, 12 May 2020 21:00:44 + with message-id and subject line Bug#960208: Removed package(s) from unstable has caused the Debian Bug report #805208, regarding sigx: FTBFS: ./sigx/tunnel_context.h:145:18: error: using invalid field 'sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::m_bound_result' 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.) -- 805208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sigx Version: 2.0.2-5 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, sigx fails to build from source in unstable/amd64: [..] ./sigx/tunnel_context.h: In instantiation of 'void sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::invoke() [with T_return = bool; T_unary_functor = sigc::bind_functor<-1, sigc::bind_functor<-1, sigc::hide_functor<-1, sigc::mem_functor1 >, sigx::shared_dispatchable, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, sigc::reference_wrapper >, sigc::reference_wrapper, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>]': src/connection_wrapper.cpp:277:1: required from here ./sigx/tunnel_context.h:145:18: error: using invalid field 'sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::m_bound_result' ./sigx/tunnel_context.h: In instantiation of 'void sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::invoke() [with T_return = bool; T_unary_functor = sigc::bind_functor<-1, sigc::bind_functor<-1, sigc::hide_functor<-1, sigc::const_mem_functor0 >, sigx::shared_dispatchable, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, sigc::reference_wrapper >, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>]': src/connection_wrapper.cpp:277:1: required from here ./sigx/tunnel_context.h:145:18: error: using invalid field 'sigx::tunnel_context<(sigx::sync_type)1u, T_return, T_unary_functor>::m_bound_result' scons: *** [build/release/connection_wrapper.os] Error 1 scons: building terminated because of errors. debian/rules:27: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/build/sigx-2.0.2' debian/rules:37: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/sigx_2.0.2-5.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- sigx.2.0.2-5.unstable.amd64.log.txt.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 2.0.2-5+rm Dear submitter, as the package sigx has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960208 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#796400: marked as done (golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests)
Your message dated Tue, 12 May 2020 21:01:08 + with message-id and subject line Bug#960210: Removed package(s) from unstable has caused the Debian Bug report #796400, regarding golang-github-jacobsa-ratelimit: Non-determistically FTBFS due to unreliable timing in tests 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.) -- 796400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-jacobsa-ratelimit Version: 0.0~git20150723.0.2ca5e0c-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-github-jacobsa-ratelimit's testsuite appears to use method timing/benchmarking in such a way that it will non-deterministically FTBFS: throttle_test.go: expected := smallerRateHz * (float64(perCaseDuration) / float64(time.Second)) For example: [..] go test -v github.com/jacobsa/ratelimit === RUN TestThrottle [--] Running tests from ThrottleTest [ RUN ] ThrottleTest.IntegrationTest throttle_test.go:202: Expected: greater than 135, and less than 165 Actual: 88 Test case 0. expected: 150.00 throttle_test.go:202: Expected: greater than 180, and less than 220.03 Actual: 138 Test case 1. expected: 200.00 throttle_test.go:202: Expected: greater than 180, and less than 220.03 Actual: 163 Test case 2. expected: 200.00 [ FAILED ] ThrottleTest.IntegrationTest (6.031585896s) [--] Finished with tests from ThrottleTest [--] Running tests from ThrottledReaderTest [ RUN ] ThrottledReaderTest.CallsThrottle [ OK ] ThrottledReaderTest.CallsThrottle [ RUN ] ThrottledReaderTest.ThrottleReturnsError [ OK ] ThrottledReaderTest.ThrottleReturnsError [ RUN ] ThrottledReaderTest.CallsWrapped [ OK ] ThrottledReaderTest.CallsWrapped [ RUN ] ThrottledReaderTest.WrappedReturnsError [ OK ] ThrottledReaderTest.WrappedReturnsError [ RUN ] ThrottledReaderTest.WrappedReturnsEOF [ OK ] ThrottledReaderTest.WrappedReturnsEOF [ RUN ] ThrottledReaderTest.WrappedReturnsFullRead [ OK ] ThrottledReaderTest.WrappedReturnsFullRead [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_CallsAgain [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_CallsAgain [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsError [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsError [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsEOF [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondReturnsEOF [ RUN ] ThrottledReaderTest.WrappedReturnsShortRead_SecondSucceedsInFull [ OK ] ThrottledReaderTest.WrappedReturnsShortRead_SecondSucceedsInFull [ RUN ] ThrottledReaderTest.ReadSizeIsAboveThrottleCapacity [ OK ] ThrottledReaderTest.ReadSizeIsAboveThrottleCapacity [--] Finished with tests from ThrottledReaderTest [--] Running tests from TokenBucketTest [ RUN ] TokenBucketTest.CarefulAccounting [ OK ] TokenBucketTest.CarefulAccounting [--] Finished with tests from TokenBucketTest --- FAIL: TestThrottle (6.03s) === RUN TestThrottledReader --- PASS: TestThrottledReader (0.00s) === RUN TestTokenBucket --- PASS: TestTokenBucket (0.00s) FAIL exit status 1 FAILgithub.com/jacobsa/ratelimit6.074s dh_auto_test: go test -v github.com/jacobsa/ratelimit returned exit code 1 debian/rules:6: recipe for target 'build' failed make: *** [build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/golang-github-jacobsa-ratelimit_0.0~git20150723.0.2ca5e0c-1.build2.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: samedi 22 août 2015, 06:22:59 (UTC+1400) I: pbuilder-time-stamp: 1440174179 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc
Bug#936206: marked as done (binplist: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 21:02:07 + with message-id and subject line Bug#960346: Removed package(s) from unstable has caused the Debian Bug report #936206, regarding binplist: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:binplist Version: 0.1.5-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:binplist If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.1.5-2+rm Dear submitter, as the package binplist has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960346 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#811325: marked as done (FTBFS: error: expected identifier before 'static_assert')
Your message dated Tue, 12 May 2020 21:00:44 + with message-id and subject line Bug#960208: Removed package(s) from unstable has caused the Debian Bug report #805208, regarding FTBFS: error: expected identifier before 'static_assert' 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.) -- 805208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sigx Version: 2.0.2-5 Severity: serious sigx fails to build: > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > In file included from ./sigx/signal_wrapper_base.h:27:0, > from src/connection_wrapper.cpp:30: > ./sigx/static_assert.h: At global scope: > ./sigx/static_assert.h:34:8: error: expected identifier before 'static_assert' > struct static_assert; > ^ > ./sigx/static_assert.h:34:8: error: expected unqualified-id before > 'static_assert' > ./sigx/static_assert.h:37:8: error: expected identifier before 'static_assert' > struct static_assert > ^ > ./sigx/static_assert.h:37:8: error: expected unqualified-id before > 'static_assert' > In file included from ./sigx/auto_tunneler.h:24:0, > from ./sigx/signal_wrapper_base.h:31, > from src/connection_wrapper.cpp:30: > ./sigx/internal_types.h:96:2: error: 'is_base_and_derived' is not a member of > 'sigc' > sigc::is_base_and_derived::value, > ^ > ./sigx/internal_types.h:96:45: error: expected primary-expression before ',' > token > sigc::is_base_and_derived::value, > ^ > ./sigx/internal_types.h:96:59: error: 'value' in namespace '::' does not name > a type > sigc::is_base_and_derived::value, >^ > ./sigx/internal_types.h:106:8: error: 'is_functor_tunneled' is not a class > template > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:115:50: error: wrong number of template arguments (3, > should be 1) > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:106:49: note: provided for 'template > struct sigx::internal::is_functor_tunneled' > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:125:51: error: wrong number of template arguments (3, > should be 1) > struct is_functor_tunneled >^ > ./sigx/internal_types.h:106:49: note: provided for 'template > struct sigx::internal::is_functor_tunneled' > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:136:50: error: wrong number of template arguments (3, > should be 1) > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:106:49: note: provided for 'template > struct sigx::internal::is_functor_tunneled' > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:153:73: error: wrong number of template arguments (3, > should be 1) > struct is_functor_tunneled, false, true> > ^ > ./sigx/internal_types.h:106:49: note: provided for 'template > struct sigx::internal::is_functor_tunneled' > struct is_functor_tunneled > ^ > ./sigx/internal_types.h:174:18: error: 'is_base_and_derived' is not a member > of 'sigc' > bool I_isslot = sigc::is_base_and_derived T_functor>::value, > ^ > ./sigx/internal_types.h:174:59: error: expected primary-expression before ',' > token > bool I_isslot = sigc::is_base_and_derived T_functor>::value, >^ > ./sigx/internal_types.h:174:73: error: 'value' in namespace '::' does not > name a type > bool I_isslot = sigc::is_base_and_derived T_functor>::value, > ^ > ./sigx/internal_types.h:183:8: error: 'is_or_adapts_slot' is not a class > template > struct is_or_adapts_slot > ^ > ./sigx/internal_types.h:193:49: error: wrong number of template arguments (3, > should be 1) > struct is_or_adapts_slot > ^ > ./sigx/internal_types.h:183:48: note: provided for 'template > struct sigx::internal::is_or_adapts_slot' > struct is_or_adapts_slot > ^ >
Bug#960459: memcached/1.6.5-2 FTBFS on s390x
forwarded 960459 https://github.com/memcached/memcached/issues/660 thanks Hi Lucas, > The latest version of memcached (1.6.5-2) FTBFS on s390x: Yes, I have raised it upstream last week: https://github.com/memcached/memcached/issues/660 (ETA "this week".) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#943287: marked as done (tcpwatch-httpproxy: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 20:57:43 + with message-id and subject line Bug#960135: Removed package(s) from unstable has caused the Debian Bug report #943287, regarding tcpwatch-httpproxy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcpwatch-httpproxy Version: 1.3.1-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.3.1-3+rm Dear submitter, as the package tcpwatch-httpproxy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960135 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#938108: marked as done (python-pyxenstore: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 20:58:25 + with message-id and subject line Bug#960174: Removed package(s) from unstable has caused the Debian Bug report #938108, regarding python-pyxenstore: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pyxenstore Version: 0.0.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pyxenstore If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.0.2-1+rm Dear submitter, as the package python-pyxenstore has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960174 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#804369: marked as done (netexpect: FTBFS with wireshark 2.0)
Your message dated Tue, 12 May 2020 21:00:15 + with message-id and subject line Bug#960207: Removed package(s) from unstable has caused the Debian Bug report #804369, regarding netexpect: FTBFS with wireshark 2.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.) -- 804369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netexpect Version: 0.22-2 Severity: important Hi Eloy, Wireshark will be updated to the next major upstream release (2.0.0) in unstable in a few weeks. Please make sure that netexpect builds with the new release. For helping the transition wireshark 2.0.0~rc2+g74e5b56-1 has been uploaded to experimental. The severity of this bug will be bumped to serious when 2.0.0 enters unstable. Cheers, Balint --- End Message --- --- Begin Message --- Version: 0.22-2+rm Dear submitter, as the package netexpect has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960207 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#940992: marked as done (firefoxdriver: does not work with firefox > 47 at all)
Your message dated Tue, 12 May 2020 20:56:57 + with message-id and subject line Bug#945705: Removed package(s) from unstable has caused the Debian Bug report #940992, regarding firefoxdriver: does not work with firefox > 47 at all 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.) -- 940992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefoxdriver Version: 3.14.1-1 Severity: grave Justification: unusable by everyone This is what happens when you try to use firefoxdriver in the most obvious way from python on buster: | $ dpkg -l python3-selenium | ... | ii python3-selenium 3.14.1+dfsg1-1 all Python3 bindings for Selenium | $ python3 | Python 3.7.3 (default, Apr 3 2019, 05:39:12) | [GCC 8.3.0] on linux | Type "help", "copyright", "credits" or "license" for more information. | >>> import selenium.webdriver | >>> selenium.webdriver.Firefox() | Traceback (most recent call last): | File "/usr/lib/python3/dist-packages/selenium/webdriver/common/service.py", line 76, in start | stdin=PIPE) | File "/usr/lib/python3.7/subprocess.py", line 775, in __init__ | restore_signals, start_new_session) | File "/usr/lib/python3.7/subprocess.py", line 1522, in _execute_child | raise child_exception_type(errno_num, err_msg, err_filename) | FileNotFoundError: [Errno 2] No such file or directory: 'geckodriver': 'geckodriver' | | During handling of the above exception, another exception occurred: | | Traceback (most recent call last): | File "", line 1, in | File "/usr/lib/python3/dist-packages/selenium/webdriver/firefox/webdriver.py", line 164, in __init__ | self.service.start() | File "/usr/lib/python3/dist-packages/selenium/webdriver/common/service.py", line 83, in start | os.path.basename(self.path), self.start_error_message) | selenium.common.exceptions.WebDriverException: Message: 'geckodriver' executable needs to be in PATH. | | >>> A little research reveals that this problem already has surfaced elsewhere e.g. at https://askubuntu.com/questions/1104721/sudo-apt-install-firefoxdriver-does-what. A more detailed answer at https://stackoverflow.com/questions/43272919/difference-between-webdriver-firefox-marionette-webdriver-gecko-driver/43920453 indicates that the extenstion-powered method employed by firefoxdriver only works until firefox 47. Later versions need "marionette" which usually manifestst as "geckodriver" which is missing from the firefoxdriver package. Given that even old-old-stable has firefox 52 already, I think we can safely conclude that the present firefoxdriver is broken for everyone. For unstable, I guess geckodriver needs to be packaged. For buster it may be best to simply remove the package in a point release. Also an autopkgtest would be a very good addition for this package to catch similar issues earlier. Helmut --- End Message --- --- Begin Message --- Version: 3.14.1-1+rm Dear submitter, as the package selenium-firefoxdriver has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945705 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#936526: marked as done (flask-oldsessions: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 20:58:48 + with message-id and subject line Bug#960175: Removed package(s) from unstable has caused the Debian Bug report #936526, regarding flask-oldsessions: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flask-oldsessions Version: 0.10+git20121007-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:flask-oldsessions If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.10+git20121007-2+rm Dear submitter, as the package flask-oldsessions has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960175 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937391: marked as done (pybitcointools: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 20:58:04 + with message-id and subject line Bug#960136: Removed package(s) from unstable has caused the Debian Bug report #937391, regarding pybitcointools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pybitcointools Version: 1.1.42-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pybitcointools If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.1.42-1+rm Dear submitter, as the package pybitcointools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960136 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#813340: marked as done (rhythmbox-ampache: KeyError when selecting the tab)
Your message dated Tue, 12 May 2020 20:59:51 +
with message-id
and subject line Bug#960204: Removed package(s) from unstable
has caused the Debian Bug report #813340,
regarding rhythmbox-ampache: KeyError when selecting the tab
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.)
--
813340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rhythmbox-ampache
Version: 0.11.1+svn43-1
Severity: grave
Tags: upstream
Dear maintainer,
rhythmbox-ampache crashes with this error:
Traceback (most recent call last):
File "/usr/lib/rhythmbox/plugins/ampache/AmpacheBrowser.py", line 542,
in handshake_cb
handshake['update'][0:18],
KeyError: 'update'
I added some print statement, and here is the content of “handshake”:
{'error': 'Unauthorized access attempt to API - ACL Error',
'root': 'Unauthorized access attempt to API - ACL Error\n'}
Steps to reproduce:
1. load rhythmbox-ampache from the plugins dialog
2. configure a server's URL and login
3. click the “ampache” tab of Rhythmbox
I checked my login and password, they are correct; and the server allows
stream access (I left the default config).
Server version: 3.6-rzb2752+dfsg-5 (in Jessie)
Regards,
Val
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.11.1+svn43-1+rm
Dear submitter,
as the package rhythmbox-ampache has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/960204
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937806: marked as done (python-halberd: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 20:57:21 + with message-id and subject line Bug#960134: Removed package(s) from unstable has caused the Debian Bug report #937806, regarding python-halberd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-halberd Version: 0.2.4-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-halberd If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.2.4-2+rm Dear submitter, as the package python-halberd has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/960134 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#945705: marked as done (RM: selenium-firefoxdriver -- RoQA; package non-functional; blocking py2 removal)
Your message dated Tue, 12 May 2020 20:56:50 + with message-id and subject line Bug#945705: Removed package(s) from unstable has caused the Debian Bug report #945705, regarding RM: selenium-firefoxdriver -- RoQA; package non-functional; blocking py2 removal 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.) -- 945705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: selenium-firefoxdriver Version: 3.14.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: firefoxdriver | 3.14.1-1 | amd64, i386 selenium-firefoxdriver | 3.14.1-1 | source --- Reason --- RoQA; package non-functional; blocking py2 removal -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/945705 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: Re: Bug#960459: memcached/1.6.5-2 FTBFS on s390x
Processing commands for cont...@bugs.debian.org: > forwarded 960459 https://github.com/memcached/memcached/issues/660 Bug #960459 [src:memcached] memcached/1.6.5-2 FTBFS on s390x Set Bug forwarded-to-address to 'https://github.com/memcached/memcached/issues/660'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960459: memcached/1.6.5-2 FTBFS on s390x
Source: memcached Version: 1.6.5-2 Severity: serious Dear Maintainer, The latest version of memcached (1.6.5-2) FTBFS on s390x: https://buildd.debian.org/status/fetch.php?pkg=memcached=s390x=1.6.5-2=1587246609=0 This failure is blocking its migration to testing. -- Lucas Kanashiro
Bug#960455: src:syncthing: fails to migrate to testing for too long: FTBFS on mips64el
Source: syncthing Version: 1.1.4~ds1-4 Severity: serious Control: close -1 1.1.4~ds1-5 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:syncthing in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=syncthing signature.asc Description: OpenPGP digital signature
Processed: src:syncthing: fails to migrate to testing for too long: FTBFS on mips64el
Processing control commands: > close -1 1.1.4~ds1-5 Bug #960455 [src:syncthing] src:syncthing: fails to migrate to testing for too long: FTBFS on mips64el Marked as fixed in versions syncthing/1.1.4~ds1-5. Bug #960455 [src:syncthing] src:syncthing: fails to migrate to testing for too long: FTBFS on mips64el Marked Bug as done -- 960455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938166: marked as done (python-setproctitle: Python2 removal in sid/bullseye)
Your message dated Tue, 12 May 2020 18:19:05 + with message-id and subject line Bug#938166: fixed in python-setproctitle 1.1.10-2 has caused the Debian Bug report #938166, regarding python-setproctitle: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-setproctitle Version: 1.1.10-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-setproctitle If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-setproctitle Source-Version: 1.1.10-2 Done: Gordon Ball We believe that the bug you reported is fixed in the latest version of python-setproctitle, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gordon Ball (supplier of updated python-setproctitle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 15:50:52 + Source: python-setproctitle Architecture: source Version: 1.1.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Gordon Ball Closes: 849023 938166 Changes: python-setproctitle (1.1.10-2) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/copyright: Use https protocol in Format field * d/control: Deprecating priority extra as per policy 4.0.1 * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. . [ Debian Janitor ] * Bump debhelper from old 9 to 12. * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. . [ Gordon
Processed: severity of 960438 is serious
Processing commands for cont...@bugs.debian.org: > severity 960438 serious Bug #960438 [blender] blender: OpenColorIO configuration error prevents launching Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 960438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Ticket opened on upstream's github
Processing commands for cont...@bugs.debian.org: > forwarded 960404 https://github.com/MiniZinc/libminizinc/issues/389 Bug #960404 [src:minizinc] minizinc FTBFS with bison 3.6.1 Set Bug forwarded-to-address to 'https://github.com/MiniZinc/libminizinc/issues/389'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960446: marked as done (libmount-dev: missing dependency to libselinux-dev)
Your message dated Tue, 12 May 2020 17:33:56 + with message-id and subject line Bug#960446: fixed in util-linux 2.35.1-5 has caused the Debian Bug report #960446, regarding libmount-dev: missing dependency to libselinux-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmount-dev Version: 2.35.1-4 Severity: serious Justification: breaks the build of libpam-mount Hi, libmount-dev needs a Depends libselinux-dev because of: $ grep libselinux /usr/lib/x86_64-linux-gnu/pkgconfig/mount.pc Requires.private: blkid libselinux This makes libpam-mount FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpam-mount.html Cheers Jochen -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmount-dev depends on: ii libblkid-dev 2.35.1-4 ii libc6-dev [libc-dev] 2.30-8 ii libmount1 2.35.1-4 libmount-dev recommends no packages. libmount-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: util-linux Source-Version: 2.35.1-5 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of util-linux, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 17:11:40 + Source: util-linux Architecture: source Version: 2.35.1-5 Distribution: unstable Urgency: medium Maintainer: util-linux packagers Changed-By: Chris Hofstaedtler Closes: 960446 Changes: util-linux (2.35.1-5) unstable; urgency=medium . * libmount-dev: depend on libselinux1-dev (Closes: #960446) Checksums-Sha1: dfce10e3833c600fbcc3c2b37137a801a72221bb 4232 util-linux_2.35.1-5.dsc 39d7c3d1cfbd8daa4865ee4cfe3dfa95b8be72c6 95572 util-linux_2.35.1-5.debian.tar.xz e0ff7b39131fe53bc2bbc79004365a52772519eb 6858 util-linux_2.35.1-5_source.buildinfo Checksums-Sha256: 7062bda677ed760f1ce4074f3fe4ee16e42958dbaf6b6f87ac1bfcbe55f238ad 4232 util-linux_2.35.1-5.dsc f2f7ee584c3f4b896f4faa601015c8cacc193b84781594f18f470c8ccb36ac2f 95572 util-linux_2.35.1-5.debian.tar.xz ae0291283d5ec23ec3b5ce8383a09e82f67733e1ab9d910ee516e81ccb97ea45 6858 util-linux_2.35.1-5_source.buildinfo Files: 095dc1729a1f924ec9dd0754c3a9614d 4232 base required util-linux_2.35.1-5.dsc 4db9090b6daeca50a4964305b85c1499 95572 base required util-linux_2.35.1-5.debian.tar.xz 8e1c22c7de15367e0b3272d17e195f6c 6858 base required util-linux_2.35.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl662OoACgkQXBPW25MF LgPMcQ/9GRpJTKWFx96+3m558a4xfroo+Q0Q7laFQaMreky2VPFn5YzXKIVXUbqA ife+CfK1YkxgvNMzl38RN2lhsn1BSTIb+K4MrdsXL/4mH9B1lpxo1EDuk/YEUtHn x6PQYZRy1YfSbVgiwnCez0X7Fxa1teEDLjrm9MwO6AEpzFoQCzsmshd18zhHPfo8 qOSMZ1xrSHezWW9oPb5gM02vdhLx9TdM7ypiK6JqnWCxRCazbPwTOTo70Ip2aC7L sLR+eG/V9LSAymCKcPzDOtWu0RuAundmuzRezX2pfbv5gQAQnl7mkFGn1zSkNdNe 1HaXB5z3KfHASj2SJRiIswz948483VpHXfrcSEH7f5985IlG+JGIJwnJWoTb5ElG KxkNCT3Nq2W5694jljAn2OT11mrpH5Lb+MyO4MoCdMnScClMcRThWt1g9qzDGdvo rLl97Ut7Wmaf36ZnylqHgJ834bFWfNx00/qqGYtBGIPBHJMIiF2I1pyGtBRKI9zG QeJP+058upcFnelXTrqmuOth4JhTt69Wd7GNgd1gW8kRMccWPJSit6MEP7J6PqUk hGPtyU6J01hrmRGbKOE/srYgpcaT4lVu8mlmZvhfkgo9I6BPbhddZb1hDZx1nDSf b3bUCON3HtKs4Av3Se46pErNV6PF8yjmInQSuwaTQ44q5UaIG90= =qngX -END PGP SIGNATURE End Message ---
Bug#960446: marked as pending in util-linux
Control: tag -1 pending Hello, Bug #960446 in util-linux reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/util-linux/-/commit/42a65f416afee32f3af72145581ae830fa27f08b libmount-dev: depend on libselinux1-dev Closes: #960446 (this message was generated automatically) -- Greetings https://bugs.debian.org/960446
Processed: Bug#960446 marked as pending in util-linux
Processing control commands: > tag -1 pending Bug #960446 [libmount-dev] libmount-dev: missing dependency to libselinux-dev Added tag(s) pending. -- 960446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960254: marked as pending in ir.lv2
Control: tag -1 pending Hello, Bug #960254 in ir.lv2 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/multimedia-team/ir.lv2/-/commit/f116cf2400fc690c36044cb814f2a68393b56d86 Fix LV2 types (Closes: #960254) (this message was generated automatically) -- Greetings https://bugs.debian.org/960254
Processed: Bug#960254 marked as pending in ir.lv2
Processing control commands: > tag -1 pending Bug #960254 [src:ir.lv2] ir.lv2 FTBFS with lv2-dev 1.18.0-1 Added tag(s) pending. -- 960254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960446: libmount-dev: missing dependency to libselinux-dev
Package: libmount-dev Version: 2.35.1-4 Severity: serious Justification: breaks the build of libpam-mount Hi, libmount-dev needs a Depends libselinux-dev because of: $ grep libselinux /usr/lib/x86_64-linux-gnu/pkgconfig/mount.pc Requires.private: blkid libselinux This makes libpam-mount FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpam-mount.html Cheers Jochen -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmount-dev depends on: ii libblkid-dev 2.35.1-4 ii libc6-dev [libc-dev] 2.30-8 ii libmount1 2.35.1-4 libmount-dev recommends no packages. libmount-dev suggests no packages. -- no debconf information
Bug#953832: marked as done (cannot allocate memory in static TLS block)
Your message dated Tue, 12 May 2020 16:03:27 +
with message-id
and subject line Bug#953832: fixed in drmaa 0.7.9-2
has caused the Debian Bug report #953832,
regarding cannot allocate memory in static TLS block
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.)
--
953832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drmaa
Version: 0.7.9-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainers,
With a recent upload of drmaa you added an autopkgtest, great. However,
it fails. I copied some of the output at the bottom of this report.
Currently this 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=drmaa
https://ci.debian.net/data/autopkgtest/testing/amd64/d/drmaa/4335284/log.gz
autopkgtest [03:10:24]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import drmaa; print(drmaa)" ; done
autopkgtest [03:10:24]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/drmaa/__init__.py", line 65, in
from .session import JobInfo, JobTemplate, Session
File "/usr/lib/python3/dist-packages/drmaa/session.py", line 39, in
from drmaa.helpers import (adapt_rusage, Attribute,
attribute_names_iterator,
File "/usr/lib/python3/dist-packages/drmaa/helpers.py", line 36, in
from drmaa.wrappers import (drmaa_attr_names_t, drmaa_attr_values_t,
File "/usr/lib/python3/dist-packages/drmaa/wrappers.py", line 52, in
raise RuntimeError(('Could not find drmaa library. Please specify
its ' +
RuntimeError: Could not find drmaa library. Please specify its full
path using the environment variable DRMAA_LIBRARY_PATH
autopkgtest [03:10:24]: test autodep8-python3: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: drmaa
Source-Version: 0.7.9-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
drmaa, 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 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated drmaa package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 May 2020 17:39:19 +0200
Source: drmaa
Architecture: source
Version: 0.7.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 953832
Changes:
drmaa (0.7.9-2) unstable; urgency=medium
.
* Team upload.
* Add fixed path to libdrmaa.so.1.0
Closes: #953832
* cme fix dpkg-control
* Add salsa-ci file (routine-update)
* VCS fields identical to source package name
Checksums-Sha1:
6329795a0d824467a6b9784d8e2c303982307504 2099 drmaa_0.7.9-2.dsc
1b1cac1fb9daa121358ecf13e54a923741e288a5 3524 drmaa_0.7.9-2.debian.tar.xz
39905aff7bb678239168ffd033fb79006166b878 5944 drmaa_0.7.9-2_amd64.buildinfo
Checksums-Sha256:
dfa74ed713e1a92756880ad3b684839e7e78f356c7abec18e2382299ca6b22b9 2099
drmaa_0.7.9-2.dsc
c04d1258360a6355bc7749dfb0840c6d61d68d5aee019907d26fc1b82120e2a7 3524
drmaa_0.7.9-2.debian.tar.xz
134a04b5a6e6d42fd3be8742ad7d8efef9ff7584790006d2fdd094ccb99c4070 5944
drmaa_0.7.9-2_amd64.buildinfo
Files:
e430fb1d322a421082a3d96586863af3 2099 python optional drmaa_0.7.9-2.dsc
d5167d74101294d248c025dbc305c09e 3524 python optional
drmaa_0.7.9-2.debian.tar.xz
03d6995f90ffc3d02c86bc0340937db8 5944 python optional
drmaa_0.7.9-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl66xL8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFZ0A/9ErQc67kDAw5EA/cLdB9dzvu6tfmwQ9pb
Bug#960201: Update
It is a known issue with Python 3.8.3rc1. See https://bugs.python.org/issue39562 for details.
Bug#959647: lasagne: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
I am confused. This bug is filed against 0.1+git20200419.5d3c63c+ds-1, which contains a patch for this exact problem, but the build logs indicate that the previous version, 0.1+git20181019.a61b76f-2, is being built. Steve
Bug#960439: libopenexr-dev: missing Breaks+Replaces: libilmbase-dev (<< ???)
Package: libopenexr-dev Version: 2.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopenexr-dev_2.5.0-1_amd64.deb ... Unpacking libopenexr-dev (2.5.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libopenexr-dev_2.5.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package libilmbase-dev:amd64 2.3.0-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopenexr-dev_2.5.0-1_amd64.deb There is no libilmbase-dev upload, yet, that does not ship /usr/include/OpenEXR/Iex.h Please use the version (+ suffix '~') of such an upload for the B+R. cheers, Andreas libilmbase-dev=2.3.0-6_libopenexr-dev=2.5.0-1.log.gz Description: application/gzip
Bug#933439: amule: Please rebuild against wxWidgets GTK 3 package
On Thu, 7 May 2020, Sandro Tosi wrote: Does the crash you referenced here require connecting to file sharing networks to reproduce? hard to say, as it crashed early on in the start up process (and also because i dont really remember because several months have passed). Clearly there's always a "risk" when using a file sharing software that it connects to the network. that being said, there's no _legal_ issue is you dont have anything in download/upload: even if amule connects to the enkey/kademlia networks it has nothing so share or download, so that's just an empty client with no implications for the IP address it connected to. Do you mind trying again with the latest wxwidgets3.0 release? I just uploaded a new upstream release (3.0.5.1) yesterday, so if it was possibly a wx issue, it may have been fixed. Also, there is a very similar amule bug report (crash) from someone who was still running the GTK 2 build of wx, so it would be good to check whether this is really something just seen when when running the GTK 3 build. Scott
Bug#954602: marked as done (modglue: FTBFS: socket.h:285:33: error: flexible array member ‘cmsghdr::__cmsg_data’ not at end of ‘struct modglue::pipe::send_blocking_(const char*, int)::’)
Your message dated Tue, 12 May 2020 13:53:08 +
with message-id
and subject line Bug#954602: fixed in modglue 1.17-4
has caused the Debian Bug report #954602,
regarding modglue: FTBFS: socket.h:285:33: error: flexible array member
‘cmsghdr::__cmsg_data’ not at end of ‘struct
modglue::pipe::send_blocking_(const char*, int)::’
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.)
--
954602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: modglue
Version: 1.17-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/src'
> libtool --tag=CXX --mode=compile g++ -c -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -I../include `pkg-config sigc++-2.0 --cflags`
> process.cc
> libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -I../include
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
> process.cc -fPIC -DPIC -o .libs/process.o
> libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -I../include
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
> process.cc -o process.o >/dev/null 2>&1
> libtool --tag=CXX --mode=compile g++ -c -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -I../include `pkg-config sigc++-2.0 --cflags` pipe.cc
> libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -I../include
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
> pipe.cc -fPIC -DPIC -o .libs/pipe.o
> In file included from /usr/include/x86_64-linux-gnu/sys/socket.h:33,
> from pipe.cc:27:
> /usr/include/x86_64-linux-gnu/bits/socket.h: In member function ‘int
> modglue::pipe::send_blocking_(const char*, int)’:
> /usr/include/x86_64-linux-gnu/bits/socket.h:285:33: error: flexible array
> member ‘cmsghdr::__cmsg_data’ not at end of ‘struct
> modglue::pipe::send_blocking_(const char*, int)::’
> 285 | __extension__ unsigned char __cmsg_data __flexarr; /* Ancillary
> data. */
> | ^~~
> pipe.cc:241:10: note: next member ‘int modglue::pipe::send_blocking_(const
> char*, int)fd’ declared here
> 241 | int fd;
> | ^~
> pipe.cc:239:10: note: in the definition of ‘struct
> modglue::pipe::send_blocking_(const char*, int)::’
> 239 | struct {
> | ^
> make[2]: *** [Makefile:38: pipe.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/03/21/modglue_1.17-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: modglue
Source-Version: 1.17-4
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
modglue, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated modglue package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 May 2020 15:22:02 +0200
Source: modglue
Architecture: source
Version: 1.17-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 954602
Changes:
modglue (1.17-4) unstable; urgency=medium
.
* QA upload.
* Comment out unused struct violating flexible array member constraints,
fixing
Bug#960105: marked as done (node-redis: autopkgtest regressions against Redis 6.x)
Your message dated Tue, 12 May 2020 13:53:13 + with message-id and subject line Bug#960105: fixed in node-redis 3.0.2-2 has caused the Debian Bug report #960105, regarding node-redis: autopkgtest regressions against Redis 6.x 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.) -- 960105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-redis Version: 3.0.2-1 Severity: normal Hi, According to: https://qa.debian.org/excuses.php?package=redis ... Redis 6.x is blocked from entering bullseye as node-redis's autopkgtests are failing. For example: https://ci.debian.net/data/autopkgtest/testing/arm64/n/node-redis/5383919/log.gz Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: node-redis Source-Version: 3.0.2-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-redis, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-redis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 15:22:28 +0200 Source: node-redis Architecture: source Version: 3.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 960105 Changes: node-redis (3.0.2-2) unstable; urgency=medium . * Disable error tests incompatible with redis ≥ 6 (Closes: #960105) Checksums-Sha1: a75acae5ba918127fb6866dbba0c1825e01fe373 3278 node-redis_3.0.2-2.dsc c3fb67855021aac59ce881881f042fd764a96224 16944 node-redis_3.0.2-2.debian.tar.xz Checksums-Sha256: 1525c42ec61aa2d46cef32ec3e90682bcdebc14f6caa1dee654fb1a5ed11793c 3278 node-redis_3.0.2-2.dsc b8b442f5bf069c8e505bbb68ee1fdf465fb992c69c3f495966b04f4c17c790a2 16944 node-redis_3.0.2-2.debian.tar.xz Files: 02f6c67f1f5c6882233eb529b3e5c758 3278 javascript optional node-redis_3.0.2-2.dsc 7de8285200f85d7e7779cbb71f641dbc 16944 javascript optional node-redis_3.0.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl66pGgACgkQ9tdMp8mZ 7unjdQ/47+muuaeOX1IV8ssJvoqzcmq4oaICR/dvqrerE7K+98sh2NP9Qp4H/Tcp jeb3NaOsn09cygFPhofsxUzGlOLuaA1myC5gD9sxxrhHnug6y86WgZRFVDmuOX9g cGouCJ9P57aSSz90tbzak5Geg4S47AIx9/sjnepAko+TRJoE9XQkPF3Ck+aq9tX9 uMpIDmwmsBqefBM26vUhOR3ZU2Sv+X+i11mTzOPuKVtH3XaZPg/tkU1m1hdIoeqC X6+Q54WwCXk93UElXWf6lJPJrYGBGneZeOFAW3jlaOVU0gwVaxEiER8gfhsveEZt N2SpNLKu+RVWMqPhEVX1TllFK6oqWG0VXQUAftOrNey+7xbGoGATKj4ecduh3mN7 GDDkDyHXt2ndzGo235eAgZhzQY9bpNU1vWnT68rT+6oOmHqgpDfAPmrhv4FhEAyR 19Qwd4ZumUGfFCOPbAvKvxRFY+U7C3sGYrcsEuf1dsDpxAWUvVMMcF5st/KwRgoX 8D15Tm7j32FPgEgqE6BsUpNMVhK9WzcSzxRn9rcphiRSkhe3HuARh/jJvKxqgkGd fqLsJl9q70TX9nhS8q7fdPTDVwIyhsGQHsi6thpuQEkgvj4E4hxAY+P10WnqmJzq ES9huF+3QdKEkE62Ae1p6yGTxvsS40NTp3UMhkNV6xESxL6mOQ== =AECF -END PGP SIGNATURE End Message ---
Bug#957556: marked as done (modglue: ftbfs with GCC-10)
Your message dated Tue, 12 May 2020 13:53:08 + with message-id and subject line Bug#954602: fixed in modglue 1.17-4 has caused the Debian Bug report #954602, regarding modglue: ftbfs with GCC-10 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.) -- 954602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:modglue Version: 1.17-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/modglue_1.17-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking whether ln -s works... yes checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking system type... Unix checking for gethostbyname... yes checking for socket... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking util.h usability... no checking util.h presence... no checking for util.h... no checking for openpty in -lutil... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for sigc... yes configure: creating ./config.status config.status: creating Makefile config.status: creating modglue.pc config.status: creating src/Makefile config.status: creating examples/Makefile configure: WARNING: unrecognized options: --disable-silent-rules, --disable-maintainer-mode, --disable-dependency-tracking dh_auto_build -O--no-parallel make -j1 make[1]: Entering directory '/<>' ( cd src && make ); make[2]: Entering directory '/<>/src' libtool --tag=CXX --mode=compile g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../include `pkg-config sigc++-2.0 --cflags` process.cc libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include process.cc -fPIC -DPIC -o .libs/process.o libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include process.cc -o process.o >/dev/null 2>&1 libtool --tag=CXX --mode=compile g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../include `pkg-config sigc++-2.0 --cflags` pipe.cc libtool: compile: g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I../include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include pipe.cc -fPIC -DPIC -o .libs/pipe.o In file included from
Processed: block 960193 with 959756
Processing commands for cont...@bugs.debian.org: > block 960193 with 959756 Bug #960193 [release.debian.org] transition: icu 960193 was blocked by: 960237 960374 955114 960236 960241 960239 960263 960193 was not blocking any bugs. Added blocking bug(s) of 960193: 959756 > thanks Stopping processing here. Please contact me if you need assistance. -- 960193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#960105 marked as pending in node-redis
Processing control commands: > tag -1 pending Bug #960105 [node-redis] node-redis: autopkgtest regressions against Redis 6.x Added tag(s) pending. -- 960105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960105: marked as pending in node-redis
Control: tag -1 pending Hello, Bug #960105 in node-redis 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/js-team/node-redis/-/commit/5794e45b3149139b6261cecd3b021fb365d09760 Disable error tests incompatible with redis ≥ 5.6 Closes: #960105 (this message was generated automatically) -- Greetings https://bugs.debian.org/960105
Processed: bug 960105 is forwarded to https://github.com/NodeRedis/node-redis/issues/1516
Processing commands for cont...@bugs.debian.org: > forwarded 960105 https://github.com/NodeRedis/node-redis/issues/1516 Bug #960105 [node-redis] node-redis: autopkgtest regressions against Redis 6.x Set Bug forwarded-to-address to 'https://github.com/NodeRedis/node-redis/issues/1516'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-javascript-devel] Bug#960105: node-redis: autopkgtest regressions against Redis 6.x
Processing control commands: > severity -1 serious Bug #960105 [node-redis] node-redis: autopkgtest regressions against Redis 6.x Severity set to 'serious' from 'important' > affects -1 src:redis Bug #960105 [node-redis] node-redis: autopkgtest regressions against Redis 6.x Added indication that 960105 affects src:redis -- 960105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933662: marked as done (node-matrix-js-sdk: build with webpack 4 failing)
Your message dated Tue, 12 May 2020 12:49:51 + with message-id and subject line Bug#933662: fixed in node-matrix-js-sdk 6.0.0+~cs9.8.22-1 has caused the Debian Bug report #933662, regarding node-matrix-js-sdk: build with webpack 4 failing 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.) -- 933662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-matrix-js-sdk Version: 0.9.2-1 Severity: important Control: tags -1 patch This package fail to build with webpack 4 from experimental. The attached patch makes the build pass with webpack 4. More details about webpack 4 transition here https://wiki.debian.org/Javascript/Nodejs/Webpack4 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.diff -ur node-matrix-js-sdk-0.9.2.orig/debian/control node-matrix-js-sdk-0.9.2/debian/control --- node-matrix-js-sdk-0.9.2.orig/debian/control2018-02-02 18:00:55.0 +0100 +++ node-matrix-js-sdk-0.9.2/debian/control 2019-08-01 16:13:29.831517566 +0200 @@ -26,7 +26,6 @@ #"exorcist": "^0.4.0", #"sourceify": "^0.1.0", #"source-map-support": "^0.4.11", - , node-uglify (>= 2.8.26) # (and install dependencies, to be bundled in browser package) , node-bluebird , node-browser-request diff -ur node-matrix-js-sdk-0.9.2.orig/debian/rules node-matrix-js-sdk-0.9.2/debian/rules --- node-matrix-js-sdk-0.9.2.orig/debian/rules 2017-12-29 19:17:13.0 +0100 +++ node-matrix-js-sdk-0.9.2/debian/rules 2018-02-02 18:01:17.0 +0100 @@ -18,7 +18,7 @@ dh $@ override_dh_auto_clean: - rm -rf dist lib + rm -rf dist lib node_modules/.cache override_dh_auto_build: # Node version @@ -26,8 +26,10 @@ # Browser version -- does not work yet mkdir -p dist mkdir -p node_modules - webpack --config debian/webpack.config.js browser-index.js dist/browser-matrix.js - uglifyjs -c -m -o dist/browser-matrix.min.js --source-map dist/browser-matrix.min.js.map --in-source-map dist/browser-matrix.js.map dist/browser-matrix.js + webpack --config debian/webpack.config.js \ +--entry ./browser-index.js --output ./dist/browser-matrix.js --mode development + webpack --config debian/webpack.config.js \ +--entry ./browser-index.js --output ./dist/browser-matrix.min.js --mode production # dh_make generated override targets # This is example for Cmake (See https://bugs.debian.org/641051 ) --- End Message --- --- Begin Message --- Source: node-matrix-js-sdk Source-Version: 6.0.0+~cs9.8.22-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-matrix-js-sdk, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-matrix-js-sdk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 14:26:35 +0200 Source: node-matrix-js-sdk Architecture: source Version: 6.0.0+~cs9.8.22-1 Distribution: unstable Urgency: medium Maintainer: Matrix Packaging Team Changed-By: Xavier Guimard Closes: 933662 960028 Changes: node-matrix-js-sdk (6.0.0+~cs9.8.22-1) unstable; urgency=medium . * Team upload * Bump debhelper compatibility level to 12 * Declare compliance with policy 4.5.0 * Add "Rules-Requires-Root: no" * Add debian/gbp.conf * Add upstream/metadata * Use pkg-js-tools auto install * Components added: bs58, base-x, loglevel, unhomoglyph, another-json * New upstream version 6.0.0+~cs9.8.22 really 6.0.0+~4.0.1+~3.0.8+~1.6.8+~1.0.5+0.2.0 * Build with babel7 & tsc (Closes: #960028) * Update copyright * Add build dependency to node-content * Fix webpack build (Closes: #933662) * Update VCS fields to salsa * Add hook to fix babel build Checksums-Sha1: d5337dee6dd0560c9deb5c839d31ba146f45e089 4033 node-matrix-js-sdk_6.0.0+~cs9.8.22-1.dsc 426a00a4de082efdbb6d4f50bd71011c74ed825a 6050 node-matrix-js-sdk_6.0.0+~cs9.8.22.orig-another-json.tar.gz
Processed: Re: inn2 postinst script needs libinn.so.6, but doesn't depend on it
Processing control commands: > found -1 2.6.3-3 Bug #947738 [inn2] inn2 postinst script needs libinn.so.6, but doesn't depend on it Marked as found in versions inn2/2.6.3-3. > severity -1 grave Bug #947738 [inn2] inn2 postinst script needs libinn.so.6, but doesn't depend on it Severity set to 'grave' from 'normal' -- 947738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960079: marked as done (undefined symbol: _PyNautilusInfoProvider_Type)
Your message dated Tue, 12 May 2020 12:03:45 + with message-id and subject line Bug#960079: fixed in nautilus-python 1.2.3-3 has caused the Debian Bug report #960079, regarding undefined symbol: _PyNautilusInfoProvider_Type 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.) -- 960079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-nautilus Version: 1.2.3-2 Severity: serious File: /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus-python.so Hi, today I was investigating, why nautilus-nextcloud is no longer working for me. nautilus-nextcloud is using python3-nautilus and starting nautilus from the commandline yields: ** (org.gnome.Nautilus:7160): WARNING **: 07:56:52.768: /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus-python.so: undefined symbol: _PyNautilusInfoProvider_Type I'm guessing this error is, why nautilus-nextcloud fails. Regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-nautilus depends on: ii gir1.2-nautilus-3.0 3.36.2-2 ii libc62.30-7 ii libglib2.0-0 2.64.2-1 ii libgtk-3-0 3.24.20-1 ii libnautilus-extension1a 3.36.2-2 ii libpython3.8 3.8.3~rc1-1 ii python3-gi 3.36.0-3 python3-nautilus recommends no packages. python3-nautilus suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nautilus-python Source-Version: 1.2.3-3 Done: Andreas Henriksson We believe that the bug you reported is fixed in the latest version of nautilus-python, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated nautilus-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 13:54:14 +0200 Source: nautilus-python Architecture: source Version: 1.2.3-3 Distribution: unstable Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Andreas Henriksson Closes: 960079 Changes: nautilus-python (1.2.3-3) unstable; urgency=high . * Fix up debian/patches/gcc10.patch to work properly (Closes: #960079) Checksums-Sha1: 36f97263ccc0d5e164dc48165326d7056877ab0c 2271 nautilus-python_1.2.3-3.dsc c0c83ead1760ac2510038a046181c72baf80eae0 6688 nautilus-python_1.2.3-3.debian.tar.xz 71df5018166f41d7e92a9f9fb846da1ce55877f5 14079 nautilus-python_1.2.3-3_amd64.buildinfo Checksums-Sha256: 4335e5378b2e016230387d37f0c4aa79e8c7ab083dd121b7a0c462f1786d77a7 2271 nautilus-python_1.2.3-3.dsc f124e18504f16ea5af66f9fe5bb5440076f69fbd34ef9d87dee1c85ed5b884a3 6688 nautilus-python_1.2.3-3.debian.tar.xz 7bea90b2d4d8a061a85c2e164365e958f9360e800727d739784e8dde81a8f9ea 14079 nautilus-python_1.2.3-3_amd64.buildinfo Files: ee5e4d082bd3a4058210f24fc145ece2 2271 python optional nautilus-python_1.2.3-3.dsc 63031834cfd2c99c89b22332f5c6fee3 6688 python optional nautilus-python_1.2.3-3.debian.tar.xz f28abe18b006ba4545ac704f9d7c778b 14079 python optional nautilus-python_1.2.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAl66j0cRHGFuZHJlYXNA ZmF0YWwuc2UACgkQC8R9xk0TUwY47BAAoFosNwK6rW43zFdKBqMAuqEQ6ASKYulk GPLQ5ajGX/W+Gd8gJyMSM1Ac2hXFvGpb12wWMz+pG3+iSV9/dj2yoqDAUJSwUyKP NOc/1c9jDNur3egnBBdVJwNzWRPXf6qFwNEBeTNE6s38w3+qnqGeCC6lsocKM3Z1 IObqd9MnoQo9RHe+JDLn06TjuWR4P0GMpaCFiy97ueBr8bYa96GUQ4EvkHFojk07 kIiBIaAaCYUB6Mrs0lsiUJtB0WYbTerF1RDCIuk65Dmue/TrjsJVena8v56w6Z+8 wMu6UdTMISZP/66L0+Ih95w8rjRbckK7MdLhbNd9iBGCmVV3mtDAEpXuoHf0Nm6E UR7SpjAmtw2qj4FXc8TWkAzWplDlteiLc0iP9+la4HTcPEdinlRJkAfHj9XNMOWW
Processed: Bug#960079 marked as pending in nautilus-python
Processing control commands: > tag -1 pending Bug #960079 [python3-nautilus] undefined symbol: _PyNautilusInfoProvider_Type Added tag(s) pending. -- 960079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 952949
Processing commands for cont...@bugs.debian.org: > close 952949 2.5.0-1 Bug #952949 [src:softhsm2] softhsm2: Replace PKCS11 headers provided by OASIS Marked as fixed in versions softhsm2/2.5.0-1. Bug #952949 [src:softhsm2] softhsm2: Replace PKCS11 headers provided by OASIS Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 952949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960079: marked as pending in nautilus-python
Control: tag -1 pending Hello, Bug #960079 in nautilus-python 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/gnome-team/nautilus-python/-/commit/6ba212e48b3f520fff8d80b15476ca25bac2d81d Fix up debian/patches/gcc10.patch to work properly Closes: #960079 (this message was generated automatically) -- Greetings https://bugs.debian.org/960079
Bug#960415: python3-sphinx-gallery: package empty
Package: python3-sphinx-gallery Version: 0.6.2-1 Severity: grave Dear Maintainer, The version 0.6.2-1 of the package is empty and only contains: usr/share/doc/python3-sphinx-gallery/changelog.Debian.gz usr/share/doc/python3-sphinx-gallery/changelog.gz usr/share/doc/python3-sphinx-gallery/copyright And, so is completely unusable when I tried to generate a documentation which needed it. -- Regards Sudip
Processed: reassign 958423 to src:php-defaults, fixed 958423 in 76, reassign 958424 to src:php-defaults ...
Processing commands for cont...@bugs.debian.org:
> reassign 958423 src:php-defaults 75
Bug #958423 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults, src:php-codecoverage] php-defaults breaks php-codecoverage
autopkgtest: Class 'DOMDocument' not found
Bug reassigned from package 'src:php-defaults, src:php-codecoverage' to
'src:php-defaults'.
No longer marked as found in versions php-defaults/75 and
php-codecoverage/7.0.10+dfsg-1.
No longer marked as fixed in versions php-defaults/76.
Bug #958423 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults] php-defaults breaks php-codecoverage autopkgtest: Class
'DOMDocument' not found
Marked as found in versions php-defaults/75.
> fixed 958423 76
Bug #958423 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults] php-defaults breaks php-codecoverage autopkgtest: Class
'DOMDocument' not found
Marked as fixed in versions php-defaults/76.
> reassign 958424 src:php-defaults 75
Bug #958424 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults, src:php-sabredav] php-defaults breaks php-sabredav
autopkgtest: Trying to access array offset on value of type bool
Bug reassigned from package 'src:php-defaults, src:php-sabredav' to
'src:php-defaults'.
No longer marked as found in versions php-sabredav/1.8.12-8 and php-defaults/75.
No longer marked as fixed in versions php-defaults/76.
Bug #958424 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults] php-defaults breaks php-sabredav autopkgtest: Trying to
access array offset on value of type bool
Marked as found in versions php-defaults/75.
> fixed 958424 76
Bug #958424 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= }
[src:php-defaults] php-defaults breaks php-sabredav autopkgtest: Trying to
access array offset on value of type bool
Marked as fixed in versions php-defaults/76.
> retitle 959627 openclipart: FTBFS with inkscape 1.0
Bug #959627 [src:openclipart] openclipart: FTBFS: (process:7163): WARNING **:
02:19:19.981: Unable to create profile directory (Permission denied) (13)
Changed Bug title to 'openclipart: FTBFS with inkscape 1.0' from 'openclipart:
FTBFS: (process:7163): WARNING **: 02:19:19.981: Unable to create profile
directory (Permission denied) (13)'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958423
958424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958424
959627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960410: libexplain FTBFS with bison 3.6.1
Source: libexplain
Version: 1.4.D001-9
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libexplain.html
...
y.tab.c:152:27: error: expected identifier or '(' before numeric constant
libexplain/acl_grammar.y:128:1: note: in expansion of macro 'acl_grammar_error'
128 | yyerror(const char *text)
| ^
libexplain/acl_grammar.y: In function 'acl_grammar_errorf':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:155:5: note: in expansion of macro 'acl_grammar_error'
155 | yyerror(buf);
| ^
libexplain/acl_grammar.y: In function 'acl_grammar_parse':
y.tab.c:152:27: error: called object is not a function or function pointer
libexplain/acl_grammar.y:470:13: note: in expansion of macro 'acl_grammar_error'
470 | yyerror
| ^~~
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1720:7: note: in expansion of macro 'acl_grammar_error'
y.tab.c:152:27: error: called object is not a function or function pointer
y.tab.c:1831:3: note: in expansion of macro 'acl_grammar_error'
At top level:
libexplain/acl_grammar.y:105:1: warning: 'result_append' defined but not used
[-Wunused-function]
105 | result_append(const char *text)
| ^
make[1]: *** [Makefile:4037: libexplain/acl_grammar.yacc.lo] Error 1
Bug#960411: python-pybedtools build-dependencies unsatisfiable on armel, armhf and mipsel
Source: python-pybedtools Version: 0.8.0-3 Severity: serious bedtools is no longer available in testing on armel, armhf or mipsel (or i386 but python-pybedtools never seems to have built there) which makes the build-dependencies of python-pybedtools unsatisfiable on those architectures. Either https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955403 needs to be fixed or python-pybedtools needs to be removed from the architectures in question.
Bug#958708: squid: Squid is still unusable
Package: squid Version: 4.11-4 Followup-For: Bug #958708 Same problem as described above . Squid would'nt start. I got following message on upgrade : apt-listchanges : Lecture des fichiers de modifications (« changelog »)... (Lecture de la base de données... 588149 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../squid-common_4.11-4_all.deb ... Dépaquetage de squid-common (4.11-4) sur (4.11-2) ... Préparation du dépaquetage de .../squid_4.11-4_amd64.deb ... proxy:x:13:13:proxy:/bin:/usr/sbin/nologin Dépaquetage de squid (4.11-4) sur (4.11-2) ... Paramétrage de squid-common (4.11-4) ... Paramétrage de squid (4.11-4) ... Installation de la nouvelle version du fichier de configuration /etc/apparmor.d/usr.sbin.squid ... Installation de la nouvelle version du fichier de configuration /etc/init.d/squid ... Installation de la nouvelle version du fichier de configuration /etc/logrotate.d/squid ... Installation de la nouvelle version du fichier de configuration /etc/resolvconf/update-libc.d/squid ... Installation de la nouvelle version du fichier de configuration /etc/squid/squid.conf ... Setcap worked! /usr/lib/squid/pinger is not suid! Job for squid.service failed because the control process exited with error code. See "systemctl status squid.service" and "journalctl -xe" for details. invoke-rc.d: initscript squid, action "restart" failed. ● squid.service - Squid Web Proxy Server Loaded: loaded (/lib/systemd/system/squid.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-05-12 13:08:15 CEST; 4ms ago Docs: man:squid(8) Process: 52706 ExecStartPre=/usr/sbin/squid --foreground -z (code=exited, status=255/EXCEPTION) mai 12 13:08:15 ishwara systemd[1]: Starting Squid Web Proxy Server... mai 12 13:08:15 ishwara squid[52706]: 2020/05/12 13:08:15| FATAL: failed to open /run/squid/squid.pid: (13) Permission denied mai 12 13:08:15 ishwara squid[52706]: exception location: File.cc(190) open mai 12 13:08:15 ishwara systemd[1]: squid.service: Control process exited, code=exited, status=255/EXCEPTION mai 12 13:08:15 ishwara systemd[1]: squid.service: Failed with result 'exit-code'. mai 12 13:08:15 ishwara systemd[1]: Failed to start Squid Web Proxy Server. dpkg: erreur de traitement du paquet squid (--configure) : installed squid package post-installation script subprocess returned error exit status 1 Traitement des actions différées (« triggers ») pour systemd (245.5-2) ... Traitement des actions différées (« triggers ») pour man-db (2.9.1-1) ... Traitement des actions différées (« triggers ») pour ufw (0.36-6) ... Des erreurs ont été rencontrées pendant l'exécution : squid For information : systemctl status squid.service : squid.service - Squid Web Proxy Server Loaded: loaded (/lib/systemd/system/squid.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-05-12 13:08:55 CEST; 19s ago Docs: man:squid(8) Process: 62840 ExecStartPre=/usr/sbin/squid --foreground -z (code=exited, status=255/EXCEPTION) mai 12 13:08:55 ishwara systemd[1]: Starting Squid Web Proxy Server... mai 12 13:08:55 ishwara squid[62840]: 2020/05/12 13:08:55| FATAL: failed to open /run/squid/squid.pid: (13) Permission denied mai 12 13:08:55 ishwara squid[62840]: exception location: File.cc(190) open mai 12 13:08:55 ishwara systemd[1]: ^[[0;1;39m^[[0;1;39msquid.service: Control process exited, code=exited, status=255/EXCEPTION mai 12 13:08:55 ishwara systemd[1]: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185msquid.service: Failed with result 'exit-code'. mai 12 13:08:55 ishwara systemd[1]: ^[[0;1;39mFailed to start Squid Web Proxy Server. I had to downgrade to 4.11.2 to get it working Regards -- System Information: Debian Release: bullseye/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.utf8), LANGUAGE=fr (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages squid depends on: ii adduser 3.118 ii libc62.30-8 ii libcap2 1:2.33-1 ii libcom-err2 1.45.6-1 ii libcrypt11:4.4.16-1 ii libdb5.3 5.3.28+dfsg1-0.6 ii libdbi-perl 1.643-1 ii libecap3 1.0.1-3.2+b1 ii libexpat12.2.9-1 ii libgcc-s110.1.0-1 ii libgnutls30 3.6.13-2 ii libgssapi-krb5-2 1.17-7 ii libkrb5-31.17-7 ii libldap-2.4-22.4.50+dfsg-1 ii libltdl7 2.4.6-14 ii libnetfilter-conntrack3 1.0.8-1 ii libnettle7 3.5.1+really3.5.1-2 ii libpam0g 1.3.1-5 ii libsasl2-2
Bug#960407: hexter: gtk interface segfaults
Package: hexter Version: 1.1.0-5 Severity: grave Justification: renders package unusable The package currently in unstable segfaults when it tries to run its gtk gui: hexter_gtk starting (pid 6866)... Gtk-Message: 12:49:06.836: Failed to load module "atk-bridge" Segmentation fault (core dumped) Downgrading to version 1.0.3-3+b1 in buster works. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.10-rt4 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: default Versions of packages hexter depends on: ii dssi-host-jack 1.1.1~dfsg0-4 ii libasound2 1.2.2-2.1 ii libc62.30-8 ii libcairo21.16.0-4 ii libglib2.0-0 2.64.2-1 ii libgtk2.0-0 2.24.32-4 ii liblo7 0.30-3 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 hexter recommends no packages. hexter suggests no packages. -- no debconf information
Processed: closing 960087
Processing commands for cont...@bugs.debian.org: > close 960087 Bug #960087 [wireguard] wireguard missing bc as a dependency for building kernel module Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 960087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960087: closing 960087
close 960087 thanks Howdy, This is a duplicate of bug 956869 and has been fixed in 1.0.20200429-2, then subsequently fixed when upstream moved from bc to pure bash in 1.0.20200506. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Processed: reopening 958362
Processing commands for cont...@bugs.debian.org:
> #bug in pdfrw not fixed by img2pdf
> reopen 958362
Bug #958362 {Done: Johannes 'josch' Schauer } [src:pdfrw]
pdfrw: fails with python 3.7+ -- abandoned upstream
'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 img2pdf/0.3.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960079: Acknowledgement (undefined symbol: _PyNautilusInfoProvider_Type)
Hi Andreas Am 11.05.20 um 14:59 schrieb Andreas Henriksson: > Hello again, > > Sorry for trying to be lazy. Attached new patch. Could you please > test it? v3 seems to work fine. Thanks! Michael signature.asc Description: OpenPGP digital signature
Bug#959772: marked as done (game-data-packager: FTBFS with inkscape 1.0)
Your message dated Tue, 12 May 2020 10:18:37 + with message-id and subject line Bug#959772: fixed in game-data-packager 65 has caused the Debian Bug report #959772, regarding game-data-packager: FTBFS with inkscape 1.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.) -- 959772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: game-data-packager Version: 64 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, game-data-packager started to FTBFS with inkscape 1.0: [...] inkscape --export-png=out/wolf-common.png -w96 -h96 data/wolf-common.svg inkscape --export-png=out/grimfandango.png -w96 -h96 data/grimfandango.svg inkscape --export-png=out/zork-inquisitor.png -w96 -h96 data/zork-inquisitor.svg Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused Unknown option --export-png=out/wolf-common.png Unknown option --export-png=out/zork-inquisitor.png Unknown option --export-png=out/grimfandango.png make[2]: *** [Makefile:139: out/zork-inquisitor.png] Error 1 make[2]: *** Waiting for unfinished jobs make[2]: *** [Makefile:139: out/grimfandango.png] Error 1 make[2]: *** [Makefile:139: out/wolf-common.png] Error 1 make[2]: Leaving directory '/build/game-data-packager-64' dh_auto_build: error: make -j3 returned exit code 2 Andreas game-data-packager_64.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: game-data-packager Source-Version: 65 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of game-data-packager, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated game-data-packager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 09:14:16 +0100 Source: game-data-packager Architecture: source Version: 65 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Simon McVittie Closes: 959772 Changes: game-data-packager (65) unstable; urgency=medium . * New games: - Quest for Glory 4 (!12) [Chris Cromer] * New versions: - Doom 1: Sigil v1.2 and v1.21 (!3) [fabian] - Descent 2: Vertigo Series expansion (!8) [Ryan Armstrong] - The Dig: new GOG archives (!9) [Dmitry Eremin-Solenikov] - Simon the Sorcerer 1 and 2: new GOG archives (!11) [Dmitry Eremin-Solenikov] - Zak McKracken and the Alien Mindbenders: new GOG archive (!10) [Dmitry Eremin-Solenikov] - Quest for Glory 1 to 3: new GOG archives (!15) [Chris Cromer] - King's Quest 1 to 7: new GOG archives (!17) [Chris Cromer] - Space Quest 1 to 6: new GOG archives (!13) [Chris Cromer] - Police Quest 1 to 4: new GOG archives (!14) [Chris Cromer] * Bug fixes: - Doom games: Extract icons from WAD files using omgifol and PIL (!3) [fabian] - Doom 1: Attempt to properly split up the four available Sigil PWADs (!2) [fabian] - Spear of Destiny: Remove obsolete mirrors [adetiste] * Internal changes: - Declare compliance with Debian Policy 4.5.0 [smcv] - Build with Inkscape 1.0 (Closes: #959772) [adetiste] - Trim extraneous empty line from changelog [adetiste] - adding_a_game: Document the special handling of '?' [smcv] Checksums-Sha1: c745dd512fda5cbbca62246b4606f6b935c5473b 2945 game-data-packager_65.dsc 46d63a52c1b0ee84e69ce861818d3486744cb4b9 4546732 game-data-packager_65.tar.xz 74c8fada2c69a6c63858b530f50ea83f5eef2500 10976 game-data-packager_65_source.buildinfo Checksums-Sha256: 213ce899b4a8b733c025a6c460e614fb67ad0e466fc9ac313991666876adb3dd 2945 game-data-packager_65.dsc 5c60ac8cc6e9322c35f37320b501ee9bea60908803797bc26ce53f50c8348176 4546732 game-data-packager_65.tar.xz 4940a056ccecdbad6c082283985c61fc014cb2437afba38169b0a616cc9d7995 10976 game-data-packager_65_source.buildinfo Files:
Bug#960405: mscgen: FTBFS and debci failure
Source: mscgen Version: 0.20-13 Severity: serious Tags: ftbfs https://ci.debian.net/packages/m/mscgen/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mscgen.html ... FAIL: renderercheck.sh == testinput0.msc testinput1.msc testinput10.msc testinput11.msc testinput12.msc testinput13.msc testinput14.msc testinput15.msc testinput16.msc testinput17.msc realloc(): invalid next size ../../test/renderercheck.sh: line 28: 15670 Aborted $VALGRIND $top_builddir/src/mscgen -T png -i $srcdir/$F -o $F.png FAIL renderercheck.sh (exit status: 134) Testsuite summary for mscgen 0.20 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to michael.mcternan.2...@cs.bris.ac.uk make[4]: *** [Makefile:495: test-suite.log] Error 1
Bug#960404: minizinc FTBFS with bison 3.6.1
Source: minizinc Version: 2.4.3-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minizinc.html ... /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp: In function 'int mzn_yyparse(void*)': /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:97:11: error: request for member 'filename' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 97 | Current.filename(Rhs[1].filename()); \ | ^~~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:98:11: error: request for member 'first_line' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 98 | Current.first_line(Rhs[1].first_line()); \ | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:99:11: error: request for member 'first_column' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 99 | Current.first_column(Rhs[1].first_column()); \ | ^~~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:100:11: error: request for member 'last_line' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 100 | Current.last_line(Rhs[N].last_line()); \ | ^ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:101:11: error: request for member 'last_column' in 'yylsp', which is of pointer type 'MiniZinc::ParserLocation*' (maybe you meant to use '->' ?) 101 | Current.last_column(Rhs[N].last_column()); | ^~~ /build/1st/minizinc-2.4.3/obj-x86_64-linux-gnu/parser.tab.cpp:5176:3: note: in expansion of macro 'YYLLOC_DEFAULT' 5176 | YYLLOC_DEFAULT (*yylsp, yyerror_range, 2); | ^~ make[3]: *** [CMakeFiles/minizinc_parser.dir/build.make:88: CMakeFiles/minizinc_parser.dir/parser.tab.cpp.o] Error 1
Bug#960403: libatlas-ecmwf-dev: metview searches for library in /usr/lib/lib/
Package: libatlas-ecmwf-dev Version: 0.20.2-1 Severity: serious Tags: ftbfs Control: affects -1 src:metview https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/metview.html ... -- Feature PNG enabled -- [eccodes] (2.17.0) --ECCODES_LIBRARIES : [eccodes eccodes_f90] -- [eckit] (1.10.1) --ECKIT_LIBRARIES : [eckit eckit_geometry eckit_linalg eckit_maths eckit_mpi eckit_web eckit_cmd] CMake Error at /usr/lib/x86_64-linux-gnu/cmake/atlas_ecmwf/atlas-targets.cmake:104 (message): The imported target "atlas_ecmwf" references the file "/usr/lib/lib/libatlas_ecmwf.so.0.20" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/cmake/atlas_ecmwf/atlas-targets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/atlas_ecmwf/atlas-config.cmake:92 (include) cmake/ecbuild_find_package.cmake:300 (find_package) cmake/compat/ecbuild_use_package.cmake:345 (ecbuild_find_package) mir/CMakeLists.txt:32 (ecbuild_use_package) -- Configuring incomplete, errors occurred!
Processed: libatlas-ecmwf-dev: metview searches for library in /usr/lib/lib/
Processing control commands: > affects -1 src:metview Bug #960403 [libatlas-ecmwf-dev] libatlas-ecmwf-dev: metview searches for library in /usr/lib/lib/ Added indication that 960403 affects src:metview -- 960403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960402: mwrap FTBFS with bison 3.6.1
Source: mwrap Version: 0.33-9 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mwrap.html ... dh_auto_test make -j15 test make[1]: Entering directory '/build/1st/mwrap-0.33' (cd testing; make) make[2]: Entering directory '/build/1st/mwrap-0.33/testing' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. ../mwrap -mex test_transfersmex \ -c test_transfersmex.cc \ -m test_transfers.m test_transfers.mw mkoctfile --mex test_transfersmex.cc ../mwrap -cppcomplex \ -mex test_cpp_complexmex \ -c test_cpp_complexmex.cc \ -m test_cpp_complex.m test_cpp_complex.mw mkoctfile --mex test_cpp_complexmex.cc ../mwrap -c99complex \ -mex test_c99_complexmex \ -c test_c99_complexmex.c \ -m test_c99_complex.m test_c99_complex.mw mkoctfile --mex test_c99_complexmex.c ../mwrap -cppcomplex test_syntax.mw 2> test_syntax.log make[2]: [Makefile:30: test_syntax] Error 1 (ignored) diff test_syntax.log test_syntax.ref 2c2 < Parse error (test_syntax.mw:8): syntax error, unexpected end of file, expecting ';' --- > Parse error (test_syntax.mw:8): syntax error, unexpected $end, expecting ';' make[2]: *** [Makefile:31: test_syntax] Error 1
Bug#960341: marked as done (swi-prolog-core,swi-prolog-core-packages: missing Breaks+Replaces: swi-prolog-nox (<< 8.1.30))
Your message dated Tue, 12 May 2020 09:49:47 + with message-id and subject line Bug#960341: fixed in swi-prolog 8.1.30+dfsg-2 has caused the Debian Bug report #960341, regarding swi-prolog-core,swi-prolog-core-packages: missing Breaks+Replaces: swi-prolog-nox (<< 8.1.30) 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.) -- 960341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swi-prolog-core,swi-prolog-core-packages Version: 8.1.30+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../swi-prolog-core_8.1.30+dfsg-1_amd64.deb ... Unpacking swi-prolog-core (8.1.30+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/swi-prolog-core_8.1.30+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/swi-prolog/bin/swipl.home', which is also in package swi-prolog-nox 8.1.29+dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../swi-prolog-core-packages_8.1.30+dfsg-1_amd64.deb ... Unpacking swi-prolog-core-packages (8.1.30+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/swi-prolog-core-packages_8.1.30+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/swi-prolog/bin/latex2html', which is also in package swi-prolog-nox 8.1.29+dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/swi-prolog-core_8.1.30+dfsg-1_amd64.deb /var/cache/apt/archives/swi-prolog-core-packages_8.1.30+dfsg-1_amd64.deb cheers, Andreas swi-prolog-nox=8.1.29+dfsg-2_swi-prolog-core-packages=8.1.30+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: swi-prolog Source-Version: 8.1.30+dfsg-2 Done: Lev Lamberov We believe that the bug you reported is fixed in the latest version of swi-prolog, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lev Lamberov (supplier of updated swi-prolog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 11:08:33 +0500 Source: swi-prolog Binary: swi-prolog swi-prolog-bdb swi-prolog-bdb-dbgsym swi-prolog-core swi-prolog-core-dbgsym swi-prolog-core-packages swi-prolog-core-packages-dbgsym swi-prolog-doc swi-prolog-full swi-prolog-java swi-prolog-java-dbgsym swi-prolog-nox swi-prolog-nox-dbgsym swi-prolog-odbc swi-prolog-odbc-dbgsym swi-prolog-test swi-prolog-x swi-prolog-x-dbgsym Architecture: source amd64 all Version: 8.1.30+dfsg-2 Distribution: experimental Urgency: medium Maintainer: Lev Lamberov Changed-By: Lev Lamberov Description: swi-prolog - ISO/Edinburgh-style Prolog interpreter swi-prolog-bdb - Berkeley DB interface for SWI-Prolog swi-prolog-core - ISO/Edinburgh-style Prolog interpreter - core system swi-prolog-core-packages - ISO/Edinburgh-style Prolog interpreter - core packages swi-prolog-doc - documentation and examples for SWI-Prolog swi-prolog-full - ISO/Edinburgh-style Prolog interpreter - full suit swi-prolog-java - Bidirectional interface between SWI-Prolog and Java swi-prolog-nox - ISO/Edinburgh-style Prolog interpreter - without X support swi-prolog-odbc - ODBC library for SWI-Prolog swi-prolog-test - tests and checks for SWI-Prolog swi-prolog-x - User interface library for SWI-Prolog - with X support Closes: 960341 Changes: swi-prolog (8.1.30+dfsg-2) experimental; urgency=medium . * d/control: Add Breaks and Replaces relations between swi-prolog packages (Closes: #960341) *
Processed: Re: Bug#952655: debian-ports-archive-keyring: Expired Debian Ports Archive Automatic Signing Key (2020)
Processing control commands: > found -1 2016.11.28 Bug #952655 [debian-ports-archive-keyring] debian-ports-archive-keyring: Expired Debian Ports Archive Automatic Signing Key (2020) Marked as found in versions debian-ports-archive-keyring/2016.11.28. -- 952655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952655: debian-ports-archive-keyring: Expired Debian Ports Archive Automatic Signing Key (2020)
Control: found -1 2016.11.28 The keys are also expired in oldstable. I think either the package should be kept up to date in point releases or not shipped as part of stable releases. Ansgar
Bug#960391: evdi-dkms: drmP.h removed in linux 5.5
Probably evdi 1.7.0 will help, released just 3 hours ago.
Bug#960391: evdi-dkms: drmP.h removed in linux 5.5)
The drmP.h build error can be addressed with https://gitweb.frugalware.org/frugalware-current/raw/master/source/lib-extra/evdi/kernel-5.5-test.patch from https://aur.archlinux.org/packages/evdi-git/#comment-744589 But then it hits the fatal error: linux/reservation.h: No such file or directory reported in Bug#954396. https://aur.archlinux.org/packages/evdi-git/#comment-744589 provides some clues to that problem in https://crazy.dev.frugalware.org/evdi-all-in-one-fixes.patch but it doesn't fully fix the build.
Bug#960391: evdi-dkms: drmP.h removed in linux 5.5
Package: evdi-dkms Version: 1.6.4+dfsg-1 Severity: grave Justification: renders package unusable evdi-dkms is currently unable to build the kernel module. /var/lib/dkms/evdi/1.6.4+dfsg/build/make.log reports: CC [M] /var/lib/dkms/evdi/1.6.4+dfsg/build/evdi_gem.o /var/lib/dkms/evdi/1.6.4+dfsg/build/evdi_drv.c:11:10: fatal error: drm/drmP.h: No such file or directory 11 | #include | ^~~~ compilation terminated. The problem is known upstream, https://github.com/DisplayLink/evdi/issues/185 https://github.com/DisplayLink/evdi/issues/199 Marking this bug with severity grave since it affects the standard linux kernel in unstable, linux-image-amd64 5.6.7-1 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evdi-dkms depends on: ii dkms 2.8.1-5 Versions of packages evdi-dkms recommends: ii libevdi0 1.6.4+dfsg-1 evdi-dkms suggests no packages. -- no debconf information
Bug#960374: cyrus-imapd: FTBFS on arm*, i386, mipsel, ppc64el and s390x
Le 12/05/2020 à 10:34, John Paul Adrian Glaubitz a écrit : > Hi Xavier! > > On 5/12/20 10:09 AM, Xavier wrote: The problem here is va_list. On some architectures, the calling convention doesn't seem to allow comparing va_list against NULL due to the way va_list is implemented on a particular architecture. >>> Correction: The va_list problem seems to affect ARM architectures only. >>> >>> The other architectures have testsuite failures which seem unrelated. >>> >>> Adrian >> >> Thanks a lot! I had to modify your patch: I had to declare a va_list >> "noargs" variable to fix the problem. > > Glad it works and thanks for the additional modifications and for testing > it. It was actually a shot in the dark yesterday shortly before I went > to bed :-). > > I'll have a look whether I can help with the testsuite failures as > well in the evening or tomorrow. > > Adrian Many thanks, For now, I disabled the 4 tests that fail and reported that to upstream [1] Cheers, Xavier [1]: https://github.com/cyrusimap/cyrus-imapd/issues/3040#issuecomment-627174812
Processed: fixed 958901 in 16.06.1-5
Processing commands for cont...@bugs.debian.org:
> fixed 958901 16.06.1-5
Bug #958901 {Done: Chow Loong Jin } [qreator] qreator does
not start properly
Marked as fixed in versions qreator/16.06.1-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#958538: marked as done (python3-cobra: Missing dependency on python3-sbml5)
Your message dated Tue, 12 May 2020 08:37:27 + with message-id and subject line Bug#958538: fixed in python-cobra 0.18.0-3 has caused the Debian Bug report #958538, regarding python3-cobra: Missing dependency on python3-sbml5 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.) -- 958538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-cobra Version: 0.14.2-2 Severity: serious (this issue affects both 0.14.2-2 from testing and 0.18.0-1 from unstable) python-cobra's build-dependencies are not satisfiable in testing/unstable on mipsel, it build-depends on python3-sbml5 and libsbml5 which are built by the libsbml source package. libsbml has dropped support for mipsel due to linker memory exhaustion issues. Since one of the dependencies is marked as and since there are no corresponding binary dependencies I presume that these are only needed for the testsuite. If so then I suspect the least-bad option is not to run the testsuite on mipsel. --- End Message --- --- Begin Message --- Source: python-cobra Source-Version: 0.18.0-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-cobra, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-cobra package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 08:20:18 +0200 Source: python-cobra Architecture: source Version: 0.18.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 958538 Changes: python-cobra (0.18.0-3) unstable; urgency=medium . * Team upload * Use strong Depends instead of Recommends for several dependent modules Closes: #958538 Checksums-Sha1: 0ab1fab6ee7d040e2b07ba6b1a6c0408938ea578 2693 python-cobra_0.18.0-3.dsc 248ac0e2c9079809b84ce50b4b811bd4ad58cef4 7676 python-cobra_0.18.0-3.debian.tar.xz 460cc7b60c4e7729918aa4bf73ba5f1a1a0426fd 9195 python-cobra_0.18.0-3_amd64.buildinfo Checksums-Sha256: bf1af63f24190a6673f906e76053bfce8f658a6b87721b912723473ad8b4a2f7 2693 python-cobra_0.18.0-3.dsc 02f6061642516e1dbb8173fe37364439a598273c44df4cb041fe46c6e0ff09d3 7676 python-cobra_0.18.0-3.debian.tar.xz 0bd478b2b24b1b878192640059f4cdbbbe43cba7018d06cb61fea645e1b6bff4 9195 python-cobra_0.18.0-3_amd64.buildinfo Files: 3ba154d3181991ee0957f22b37ce7203 2693 python optional python-cobra_0.18.0-3.dsc f88afd0473006835b5edfaacacd8ecd8 7676 python optional python-cobra_0.18.0-3.debian.tar.xz bb79122270ca08ae8c0300f4712268d4 9195 python optional python-cobra_0.18.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl66VfgRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtG/fQ//eahL7SqjHpfU1ZLsK3LOZq1R9mFHSkTw 7i1joJYs2/MelNt7k+rkADmmO0csN0bOi3JRoXyihmvvS+w5i74fqqpMvjrxaLKk eAcR4wYxceN7Q3Xa1UkbpfBy+fMLRlUqBjqek+6oBdQpM0tel/nlNSU00s32SNWZ x4XkrQwRQI8g+Ik8a5W0bSVS7jX5BgBTXxZywqru/P2S61PpcE3hl2VTDzQMCl0b doJiPBW3THzT0zB5je2SOE6EYZynSJpc7bugDLKdxLBz14q513f+zSYVTUTkOFTH UfUYWEjX5BxCnDQCew7JTi6XRRI1DYfNXV8V+7QoszxSW+a6/xNRmvLAdMqJOh4h krgxw6UoVrcp84/OLRVeLL0cAQPpjr9YRzhhwruIVcDXoP5HXCix0iVyhM4hOXe3 3spCOOwUc2GUWs6YDDkhWvuiLnDEvcAC3oLZ5ikTqARbsORqnWMqJnHRljE/ZERE ysRDWG6lRBmcQlvDCOrKJ/DHMaDCP1MneuDDIg12FlzdlVtHAUJbZCtQ9zd5R62A 9eLpOqxWw0M04OgoHI2qcBlu6aibf27MxsZux0/YV+DpltnXn06nlg+NEqBWYR5Q S3yfIue3a/nxQ+EBWsFoRmvLQ/yqf1R5VMFsgCk+tV9wQ2PVAWMVzAw5CRKtlXWO 4alIMU+Kdwg= =i29R -END PGP SIGNATURE End Message ---
Bug#960374: marked as done (cyrus-imapd: FTBFS: testsuite fails with all arch except x86_64)
Your message dated Tue, 12 May 2020 08:34:13 + with message-id and subject line Bug#960374: fixed in cyrus-imapd 3.2.0-2 has caused the Debian Bug report #960374, regarding cyrus-imapd: FTBFS: testsuite fails with all arch except x86_64 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.) -- 960374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cyrus-imapd Version: 3.2.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) Control: block 960193 by -1 cyrus-imapd failed to build on almost all architectures. See https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd=i386=3.2.0-1=1588581560=0 and https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd=arm64=3.2.0-1=1588581432=0 for examples. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: cyrus-imapd Source-Version: 3.2.0-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of cyrus-imapd, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated cyrus-imapd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 09:52:36 +0200 Source: cyrus-imapd Architecture: source Version: 3.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Xavier Guimard Closes: 960263 960374 Changes: cyrus-imapd (3.2.0-2) unstable; urgency=medium . * Add fix for non-x86 arch. Thanks to John Paul Adrian Glaubitz! (Closes: #960263) * Disable some test incompatible with non amd64 arch (Closes: #960374) Checksums-Sha1: b226886850ad758cf4e5738e558e9f8ee63075f5 5458 cyrus-imapd_3.2.0-2.dsc 610e16ee780a4eac61271105fd5c2617e5cc318b 93284 cyrus-imapd_3.2.0-2.debian.tar.xz Checksums-Sha256: 757f1b028bababfd6c01bff43cedae2ccf60858c3f547a2d2598a0869bf16a4c 5458 cyrus-imapd_3.2.0-2.dsc b837228c7e9610caf9868cc9ae88c9f4eb0611a3e208418999b9ad0adedf6959 93284 cyrus-imapd_3.2.0-2.debian.tar.xz Files: 1b060c8f1e23518ff5f7b48c193b9c9a 5458 mail optional cyrus-imapd_3.2.0-2.dsc c9640c894afc47876b1a598b707803dc 93284 mail optional cyrus-imapd_3.2.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl66WroACgkQ9tdMp8mZ 7unLJQ/9GYKU9sEvGfVBmBMUDcC8f6DpLntS/4WK8XufcL7XNXIM+Z4YjYwR88Rx 3B2skzIarP6QnkykDd3oqrweHReaZQ1cGYf49P1NjAJ/k+fFYwJb0Onerd/CeZTo s9gNNNxj0MVWK+WJAokNII+gmIXG7KP6u9y/VHqYu8ceI2LDb33taWBnBVEnCZob kXfnTzIH8nfzISVAGShZs8Tm38aODgiEqUGCnZrRrkmGFj8fE0+u8AkVMFbUGC/X IJ1F+NZmhJ1GVEQ9Xc6RfhBQteyOLhLQ9s6Jeg6boIY+EOZPUkLKEhG9SU8CDhPe jhacZq8OLcwqxVoUc1uCFZAKAF9YWtGRQnatPb7LW63fjAPF4RZHYlOq/u1lPZbO PV83qd9zF7bpxaFGKbGLt2clXS4b9ncX5PZIUIcDlk3ADwgVrfUUbu8YtGY5WZDC tLujs/jfrk5bMfo7mp7IyKkuP1DIniMMMItHTqkAHAGvVOar1yG85CG8vYm0UFBA H6UTsNVvPdtgqcvbChq8mc5ZgqIptYc/+h2tXqal7sWdahqGGWMutq5z5mbI1Wyi 4hnVP8HpS14Nu4YfZfxhmHOTozFc7bpPB3Iuw4j/l50Oo5GFE8oj9W9yQSMadgQM 3DWTODtBD3je0hpeqYsbrLjcs5UYxlMpWu07E/TB+7hE9v2NfC0= =wGMG -END PGP SIGNATURE End Message ---
Bug#960263: cyrus-imapd: FTBFS on arm*, i386, mipsel, ppc64el and s390x
Hi Xavier! On 5/12/20 10:09 AM, Xavier wrote: >>> The problem here is va_list. On some architectures, the calling convention >>> doesn't seem to allow comparing va_list against NULL due to the way va_list >>> is implemented on a particular architecture. >> Correction: The va_list problem seems to affect ARM architectures only. >> >> The other architectures have testsuite failures which seem unrelated. >> >> Adrian > > Thanks a lot! I had to modify your patch: I had to declare a va_list > "noargs" variable to fix the problem. Glad it works and thanks for the additional modifications and for testing it. It was actually a shot in the dark yesterday shortly before I went to bed :-). I'll have a look whether I can help with the testsuite failures as well in the evening or tomorrow. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#960263: marked as done (cyrus-imapd: FTBFS on arm*, mipsel, ppc64el and s390x)
Your message dated Tue, 12 May 2020 08:34:13 + with message-id and subject line Bug#960263: fixed in cyrus-imapd 3.2.0-2 has caused the Debian Bug report #960263, regarding cyrus-imapd: FTBFS on arm*, mipsel, ppc64el and s390x 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.) -- 960263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cyrus-imapd Version: 3.2.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) Control: block 960193 by -1 cyrus-imapd failed to build on almost all architectures. See https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd=i386=3.2.0-1=1588581560=0 and https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd=arm64=3.2.0-1=1588581432=0 for examples. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: cyrus-imapd Source-Version: 3.2.0-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of cyrus-imapd, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated cyrus-imapd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 May 2020 09:52:36 +0200 Source: cyrus-imapd Architecture: source Version: 3.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Xavier Guimard Closes: 960263 960374 Changes: cyrus-imapd (3.2.0-2) unstable; urgency=medium . * Add fix for non-x86 arch. Thanks to John Paul Adrian Glaubitz! (Closes: #960263) * Disable some test incompatible with non amd64 arch (Closes: #960374) Checksums-Sha1: b226886850ad758cf4e5738e558e9f8ee63075f5 5458 cyrus-imapd_3.2.0-2.dsc 610e16ee780a4eac61271105fd5c2617e5cc318b 93284 cyrus-imapd_3.2.0-2.debian.tar.xz Checksums-Sha256: 757f1b028bababfd6c01bff43cedae2ccf60858c3f547a2d2598a0869bf16a4c 5458 cyrus-imapd_3.2.0-2.dsc b837228c7e9610caf9868cc9ae88c9f4eb0611a3e208418999b9ad0adedf6959 93284 cyrus-imapd_3.2.0-2.debian.tar.xz Files: 1b060c8f1e23518ff5f7b48c193b9c9a 5458 mail optional cyrus-imapd_3.2.0-2.dsc c9640c894afc47876b1a598b707803dc 93284 mail optional cyrus-imapd_3.2.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl66WroACgkQ9tdMp8mZ 7unLJQ/9GYKU9sEvGfVBmBMUDcC8f6DpLntS/4WK8XufcL7XNXIM+Z4YjYwR88Rx 3B2skzIarP6QnkykDd3oqrweHReaZQ1cGYf49P1NjAJ/k+fFYwJb0Onerd/CeZTo s9gNNNxj0MVWK+WJAokNII+gmIXG7KP6u9y/VHqYu8ceI2LDb33taWBnBVEnCZob kXfnTzIH8nfzISVAGShZs8Tm38aODgiEqUGCnZrRrkmGFj8fE0+u8AkVMFbUGC/X IJ1F+NZmhJ1GVEQ9Xc6RfhBQteyOLhLQ9s6Jeg6boIY+EOZPUkLKEhG9SU8CDhPe jhacZq8OLcwqxVoUc1uCFZAKAF9YWtGRQnatPb7LW63fjAPF4RZHYlOq/u1lPZbO PV83qd9zF7bpxaFGKbGLt2clXS4b9ncX5PZIUIcDlk3ADwgVrfUUbu8YtGY5WZDC tLujs/jfrk5bMfo7mp7IyKkuP1DIniMMMItHTqkAHAGvVOar1yG85CG8vYm0UFBA H6UTsNVvPdtgqcvbChq8mc5ZgqIptYc/+h2tXqal7sWdahqGGWMutq5z5mbI1Wyi 4hnVP8HpS14Nu4YfZfxhmHOTozFc7bpPB3Iuw4j/l50Oo5GFE8oj9W9yQSMadgQM 3DWTODtBD3je0hpeqYsbrLjcs5UYxlMpWu07E/TB+7hE9v2NfC0= =wGMG -END PGP SIGNATURE End Message ---
Bug#960263: cyrus-imapd: FTBFS on arm*, i386, mipsel, ppc64el and s390x
Le 12/05/2020 à 01:04, John Paul Adrian Glaubitz a écrit :
> On 5/12/20 1:01 AM, John Paul Adrian Glaubitz wrote:
>> On 5/11/20 11:56 PM, Xavier wrote:
>>> Could someone help us here ? I forwarded this bug to upstream ([1]) but
>>> didn't receive any response for now.
>>>
>>> (Cc to RFH bug)
>>
>> The problem here is va_list. On some architectures, the calling convention
>> doesn't seem to allow comparing va_list against NULL due to the way va_list
>> is implemented on a particular architecture.
> Correction: The va_list problem seems to affect ARM architectures only.
>
> The other architectures have testsuite failures which seem unrelated.
>
> Adrian
Thanks a lot! I had to modify your patch: I had to declare a va_list
"noargs" variable to fix the problem.
Cheers,
Xavier
Description: fix for non x86 arch
The problem here is va_list. On some architectures, the calling convention
doesn't seem to allow comparing va_list against NULL due to the way va_list
is implemented on a particular architecture.
Author: John Paul Adrian Glaubitz
Bug: https://github.com/cyrusimap/cyrus-imapd/issues/3040
Bug-Debian: https://bugs.debian.org/960263
Forwarded: https://github.com/cyrusimap/cyrus-imapd/issues/3040
Reviewed-By: Xavier Guimard
Last-Update: 2020-05-12
--- a/imap/httpd.c
+++ b/imap/httpd.c
@@ -2350,7 +2350,7 @@
simple_hdr(txn, "Access-Control-Expose-Headers", hdr)
static void comma_list_body(struct buf *buf,
-const char *vals[], unsigned flags, va_list args)
+const char *vals[], unsigned flags, int has_args, va_list args)
{
const char *sep = "";
int i;
@@ -2358,11 +2358,11 @@
for (i = 0; vals[i]; i++) {
if (flags & (1 << i)) {
buf_appendcstr(buf, sep);
-if (args) buf_vprintf(buf, vals[i], args);
+if (has_args) buf_vprintf(buf, vals[i], args);
else buf_appendcstr(buf, vals[i]);
sep = ", ";
}
-else if (args) {
+else if (has_args) {
/* discard any unused args */
vsnprintf(NULL, 0, vals[i], args);
}
@@ -2377,7 +2377,7 @@
va_start(args, flags);
-comma_list_body(, vals, flags, args);
+comma_list_body(, vals, flags, 1, args);
va_end(args);
@@ -2512,6 +2512,7 @@
int i;
time_t now;
char datestr[30];
+va_list noargs;
double cmdtime, nettime;
const char **hdr, *sep;
struct auth_challenge_t *auth_chal = >auth_chal;
@@ -3077,17 +3078,17 @@
}
if (code == HTTP_SWITCH_PROT || code == HTTP_UPGRADE) {
buf_printf(logbuf, "%supgrade=", sep);
-comma_list_body(logbuf, upgrd_tokens, txn->flags.upgrade, NULL);
+comma_list_body(logbuf, upgrd_tokens, txn->flags.upgrade, 0, noargs);
sep = "; ";
}
if (txn->flags.te) {
buf_printf(logbuf, "%stx-encoding=", sep);
-comma_list_body(logbuf, te, txn->flags.te, NULL);
+comma_list_body(logbuf, te, txn->flags.te, 0, noargs);
sep = "; ";
}
if (txn->resp_body.enc.proc) {
buf_printf(logbuf, "%scnt-encoding=", sep);
-comma_list_body(logbuf, ce, txn->resp_body.enc.type, NULL);
+comma_list_body(logbuf, ce, txn->resp_body.enc.type, 0, noargs);
sep = "; ";
}
if (txn->location) {
Bug#958901: marked as done (qreator does not start properly)
Your message dated Tue, 12 May 2020 16:18:59 +0800
with message-id <20200512081859.gc6...@gmail.com>
and subject line Re: Bug#958901: qreator does not start properly
has caused the Debian Bug report #958901,
regarding qreator does not start properly
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.)
--
958901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qreator
Version: 16.06.1-3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed qreator on my system (with a KDE desktop).
I started qreator but did not see any response or window popping up:
rd@h370:~/Downloads$ qreator -w
/usr/share/qreator/qreator_lib/Builder.py:21: PyGIWarning: Gtk was imported
without specifying a version first. Use gi.require_version('Gtk', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GObject, Gtk # pylint: disable=E0611
/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py:18: PyGIWarning:
GtkChamplain was imported without specifying a version first. Use
gi.require_version('GtkChamplain', '0.12') before import to ensure that the
right version gets loaded.
from gi.repository import Gtk, GtkChamplain, Clutter, Champlain
/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py:20: PyGIWarning:
GtkClutter was imported without specifying a version first. Use
gi.require_version('GtkClutter', '1.0') before import to ensure that the right
version gets loaded.
from gi.repository import GtkClutter
/usr/share/qreator/qreator/qrcodes/QRCodeWifiGtk.py:20: PyGIWarning: NM was
imported without specifying a version first. Use gi.require_version('NM',
'1.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GLib, GdkPixbuf, NM
No handlers could be found for logger "qreator_lib"
I would have expected to see something similar to the windows shown here
https://wiki.ubuntuusers.de/Qreator/
-- System Information:
Debian Release: 10.3
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable'), (105,
'proposed-updates'), (105, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-8-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qreator depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii geoclue-2.0 2.5.2-1
ii gir1.2-champlain-0.120.12.16-3
ii gir1.2-clutter-1.0 1.26.2+dfsg-10
ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii gir1.2-geoclue-2.0 2.5.2-1
ii gir1.2-glib-2.0 1.58.3-2
ii gir1.2-gtk-3.0 3.24.5-1
ii gir1.2-gtkchamplain-0.12 0.12.16-3
ii gir1.2-gtkclutter-1.01.8.4-4
ii gir1.2-nm-1.01.14.6-2+deb10u1
ii python 2.7.16-1
ii python-cairo 1.16.2-1+b1
ii python-dbus 1.2.8-3
ii python-gi3.30.4-1
ii python-gi-cairo 3.30.4-1
ii python-pil 5.4.1-2+deb10u1
ii python-qrencode 1.2-4+b2
ii python-requests 2.21.0-1
ii python-vobject 0.9.6.1-0.1
ii python-xdg 0.25-5
qreator recommends no packages.
qreator suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed -1 16.06.1-5
kthxbye
On Mon, May 11, 2020 at 05:41:33PM +0200, Rainer Dorsch wrote:
> [...]
> But I did an apt-get source -t sid qreator and build it using dpkg-
> buildpackage.
>
> I confirm with this new package the issue is gone.
>
> If you see a chance to either fix it in a stable update or provide the new
> version through stable-backports, that would be cool.
Cool, thanks for the confirmation.
--
Kind regards,
Loong Jin
signature.asc
Description: PGP signature
--- End Message ---
Processed: retitle 960374 to cyrus-imapd: FTBFS: testsuite fails with all arch except x86_64
Processing commands for cont...@bugs.debian.org: > retitle 960374 cyrus-imapd: FTBFS: testsuite fails with all arch except x86_64 Bug #960374 [src:cyrus-imapd] cyrus-imapd: FTBFS on i386 Changed Bug title to 'cyrus-imapd: FTBFS: testsuite fails with all arch except x86_64' from 'cyrus-imapd: FTBFS on i386'. > thanks Stopping processing here. Please contact me if you need assistance. -- 960374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 959828
Processing commands for cont...@bugs.debian.org: > tags 959828 - wontfix Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide what systemd does Removed tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 959828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 946217 in 0.16.105-2
Processing commands for cont...@bugs.debian.org: > fixed 946217 0.16.105-2 Bug #946217 [libyang0.16] CVE-2019-19333 & CVE-2019-19334 in libyang Marked as fixed in versions libyang/0.16.105-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 946217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
