Bug#907228: marked as done (kaffeine: FTBFS with Qt 5.11)
Your message dated Mon, 03 Sep 2018 05:33:57 + with message-id and subject line Bug#907228: fixed in kaffeine 2.0.15-2 has caused the Debian Bug report #907228, regarding kaffeine: FTBFS with Qt 5.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kaffeine Version: 2.0.15-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --with kf5 dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure --buildsystem=kf5 -a cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done [... snipped ...] [ 36%] Building CXX object src/CMakeFiles/kaffeine.dir/iso-codes.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/<>/obj-x86_64-linux-gnu/src/kaffeine_autogen/include -I/<>/include -I/<>/obj-x86_64-linux-gnu -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem / usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/Solid -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KBookmarks -isystem /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KDBusAddons -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall -Wextra - Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o CMakeFiles/kaffeine.dir/iso-codes.cpp.o -c /<>/src/iso-codes.cpp [ 38%] Building CXX object src/CMakeFiles/kaffeine.dir/dvb/dvbcam_linux.cpp.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/<>/obj-x86_64-linux-gnu/src/kaffeine_autogen/include -I/<>/include -I/<>/obj-x86_64-linux-gnu -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
Processed: tagging 907763
Processing commands for cont...@bugs.debian.org: > tags 907763 + confirmed Bug #907763 [src:ant-contrib] ant-contrib: FTBFS in buster/sid (failing tests) Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 907763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906624: marked as done (kexi: FTBFS in buster/sid (invalid use of incomplete type 'class QAction'))
Your message dated Mon, 03 Sep 2018 05:18:59 + with message-id and subject line Bug#906624: fixed in kexi 1:3.1.0-3 has caused the Debian Bug report #906624, regarding kexi: FTBFS in buster/sid (invalid use of incomplete type 'class QAction') 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.) -- 906624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kexi Version: 1:3.1.0-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with kf5 dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -Skf5 -- -DBUILD_TESTING=OFF -DKEXI_QTGUI_RUNTIME_AVAILABLE=OFF cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_TESTING=OFF -DKEXI_QTGUI_RUNTIME_AVAILABLE=OFF .. -- Kexi version "3.1.0" (3.1.0), distribution version "3.1" -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info [... snipped ...] /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 'template static typename std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) && (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]': /<>/src/main/startup/KexiNewProjectAssistant.cpp:499:63: required from here /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 'type' in 'struct std::enable_if' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 'template static typename std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, Func2)' connect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, Func2 slot) ^~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: template argument deduction/substitution failed: /<>/src/main/startup/KexiNewProjectAssistant.cpp:499:63: note: candidate expects 3 arguments, 4 provided this, SLOT(overwriteActionTriggered())); ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:64, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer.h:48, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtCore/QPointer:1, from /usr/include/KDb3/KDbMessageHandler.h:26, from /usr/include/KDb3/KDbMessageHandler:1, from /<>/src/main/startup/KexiAssistantMessageHandler.h:23, from /<>/src/main/startup/KexiNewProjectAssistant.h:25, from /<>/src/main/startup/KexiNewProjectAssistant.cpp:22: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 'template static typename std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, Qt::ConnectionType)' connect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, const QObject *context, Func2 slot, ^~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: template argument deduction/substitution failed: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 'template static typename std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), QMetaObject::Connection>::type
Processed: bug 907228 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 907228 Bug #907228 [src:kaffeine] kaffeine: FTBFS with Qt 5.11 Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 907228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907819: jellyfish: Does not build on paths containing "-L"
On Mon, Sep 03, 2018 at 01:00:15AM +0300, Adrian Bunk wrote: > jellyfish doesn't do anything here that strikes me as wrong, > my first suspects for the root cause would be libtool or automake. Well, I see this kind of thing in examples/jf_count_dump/Makefile LDFLAGS = -Wl,--rpath=$(shell pkg-config --libs-only-L jellyfish-2.0 | sed -e 's/-L//g') That might work if the output of pkg-config is somewhere in /usr/[...] but I guess this is being used with the installed version at WHATEVER/debian/tmp/[...]. Then there is the python script swig/python/setup.py which does stuff regarding libraries and paths, this is partially patched by debian/patches/drop-rpath. Thanks.
Processed: Re: Bug#907819: jellyfish: Does not build on paths containing "-L"
Processing commands for cont...@bugs.debian.org: > severity 907819 serious Bug #907819 [src:jellyfish] jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 907819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905107: gnome-shell-pomodoro: patch in the repo
Control: tags -1 + pending Patched version available in the repo. I'm in the process of becoming a DD. If my usual sponsor don't have the time to review and upload it before I finish the process, I'll take care of it (hopefully in about 2 weeks). Thanks, Joseph
Processed: gnome-shell-pomodoro: patch in the repo
Processing control commands: > tags -1 + pending Bug #905107 [gnome-shell-pomodoro] gnome-shell-extension-pomodoro: global.screen is not available in GNOME Shell 3.29 Added tag(s) pending. -- 905107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#890307: Package update for version 4.7
Hello: Based on the Philippe work I've update the packaging for tortoisehg 4.7. You can find the source (and binary) packages here: https://trismegisto.no-ip.org/~rasasi/thg/tortoisehg_4.7-1.dsc There are still some lintian warnings (and errors) that I have not dealt with yet. Feel free to improve or comment it. Hope this helps. Regards. -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#907819: jellyfish: Does not build on paths containing "-L"
Processing control commands: > severity -1 important Bug #907819 [src:jellyfish] jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild Severity set to 'important' from 'serious' -- 907819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907819: jellyfish: Does not build on paths containing "-L"
Control: severity -1 important On Sun, Sep 02, 2018 at 10:36:28PM +0200, Santiago Vila wrote: >... > On Sun, Sep 02, 2018 at 09:43:28PM +0300, Adrian Bunk wrote: >... > > https://people.debian.org/~sanvila/build-logs/jellyfish/jellyfish_2.2.8-3_amd64-20180902T150417Z > > > > ... > > I: NOTICE: Log filtering will replace > > 'build/jellyfish-La3pVw/jellyfish-2.2.8' with '<>' > > ... > > x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > > -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -g -O2 > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > > build/temp.linux-amd64-3.7/jellyfish_wrap.o > > -L/build/jellyfisha3pVw/jellyfish-2.2.8/debian/tmp//usr/lib/x86_64-linux-gnu > > > > -Wl,--enable-new-dtags,-R/<>/debian/tmp/usr/lib/x86_64-linux-gnu > > -ljellyfish-2.0 -lpthread -o > > /<>/.pybuild/cpython3_3.7_dna-jellyfish/build/_dna_jellyfish.cpython-37m-x86_64-linux-gnu.so > > /usr/bin/ld: cannot find -ljellyfish-2.0 > > > > > > Something (libtool?) removes the "-L" from the "jellyfish-La3pVw", > > Good catch! Yes, that's what it seems to happen! > > > However, this can happen in any official buildd the same way it happened to > me. > > In every build log there are three different messages about log filtering, > like this: > > I: NOTICE: Log filtering will replace > 'var/run/schroot/mount/sid-53306582-5e1d-46e9-87b2-1e8840f72cfe' with > '<>' > > [...] > > I: NOTICE: Log filtering will replace > 'build/jellyfish-La3pVw/jellyfish-2.2.8' with '<>' > I: NOTICE: Log filtering will replace 'build/jellyfish-La3pVw' with > '<>' > > > The first one is a UUID (alphanumeric) and by design it's clear that > it will never contain "-L". > > But the last two are chosen by sbuild randomly, using "mktemp -d" and > the algorithm followed by sbuild to construct this random path does not > seem to be different from buildd to the packaged version of sbuild I'm > using. > > So not only there may be a "-L" in a path in the official buildds, > but it mathematically will (provided you try enough times). > > So yes, this package FTBFS randomly in the official buildds too. No, it cannot. The buildds use a UUID, which cannot contain L. I was lucky that you provided build logs this time, bugs without any logs are basically "minor moreinfo" since there is nothing that can be done about such bugs. Please double-check whether in other bugs you reported the buildpath contained strings like -l or -L or -I or similar that cannot happen on the buildds, and that might have caused such build failures noone can reproduce. And in any case, please ensure that all your bugs have a full build log attached or linked (reproducible is fine). > We could of course change the algorithm used by sbuild to construct > this random path, but really, packages are supposed to be buildable > in any path, and definitely on paths containing "-L". jellyfish doesn't do anything here that strikes me as wrong, my first suspects for the root cause would be libtool or automake. > Thanks. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#906308: marked as done (CVE-2018-14348)
Your message dated Sun, 02 Sep 2018 20:47:11 + with message-id and subject line Bug#906308: fixed in libcgroup 0.41-8+deb9u1 has caused the Debian Bug report #906308, regarding CVE-2018-14348 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.) -- 906308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcgroup Severity: grave Tags: security This was assigned CVE-2018-14348: https://bugzilla.suse.com/show_bug.cgi?id=1100365 (cgred seems to be cgrulesengd in Debian) Patch: https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590/ Cheers, Moritz --- End Message --- --- Begin Message --- Source: libcgroup Source-Version: 0.41-8+deb9u1 We believe that the bug you reported is fixed in the latest version of libcgroup, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated libcgroup 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: Sun, 19 Aug 2018 23:10:45 +0200 Source: libcgroup Binary: cgroup-tools libcgroup1 libcgroup-dev libpam-cgroup cgroup-bin Architecture: source all amd64 Version: 0.41-8+deb9u1 Distribution: stretch Urgency: high Maintainer: Christian Kastner Changed-By: Markus Koschany Description: cgroup-bin - control and monitor control groups (transitional package) cgroup-tools - control and monitor control groups (tools) libcgroup-dev - control and monitor control groups (development) libcgroup1 - control and monitor control groups (library) libpam-cgroup - control and monitor control groups (PAM) Closes: 906308 Changes: libcgroup (0.41-8+deb9u1) stretch; urgency=high . * Non-maintainer upload. * Fix CVE-2018-14348: The cgrulesengd daemon in libcgroup creates log files with world readable and writable permissions due to a reset of the file mode creation mask (umask(0)). (Closes: #906308) Checksums-Sha1: 14b2867b089e4fce9d3b6daaf87b238101ba15cd 2327 libcgroup_0.41-8+deb9u1.dsc 20161d5e0c4b83dbf0e9768f67f8be4395ed47dd 16672 libcgroup_0.41-8+deb9u1.debian.tar.xz 97574b51adfa64545033f9d5ea07d3c1d9ed36ec 6838 cgroup-bin_0.41-8+deb9u1_all.deb 83f4eece8c32b018f5f706d9ae91495a80247107 150892 cgroup-tools-dbgsym_0.41-8+deb9u1_amd64.deb 52ee10bb4daf36c698b3feae014a7764ca0fe1a5 68916 cgroup-tools_0.41-8+deb9u1_amd64.deb aaafd1c522d7fd463b20899adc3a71bf000457e1 20186 libcgroup-dev_0.41-8+deb9u1_amd64.deb e40ef9754cce7b4b6e27be7bd0543ecd8129ca6e 91470 libcgroup1-dbgsym_0.41-8+deb9u1_amd64.deb 5bdd25ab9bf2d53389a9925a2e6cf28089807ec1 44784 libcgroup1_0.41-8+deb9u1_amd64.deb 39758bb1ba12995a955a9983c7c3849c8e684ae2 8034 libcgroup_0.41-8+deb9u1_amd64.buildinfo 5e969153c33edf83723338838d933184ee82280e 4936 libpam-cgroup-dbgsym_0.41-8+deb9u1_amd64.deb 28237c56292c47042512b88b908cba90b571d6ce 9150 libpam-cgroup_0.41-8+deb9u1_amd64.deb Checksums-Sha256: b4796e907c4fa5b4b64f700cc6ad1875bd600227ec95f37cfb8c55d69ee17377 2327 libcgroup_0.41-8+deb9u1.dsc c426122003b2e492e30a2f4dd6df6f81aa718f326b4a0866de9af272fc2822b1 16672 libcgroup_0.41-8+deb9u1.debian.tar.xz 2c1a4fea0563e20d532ffa0c73bfb42e0924c5feb01616b7da59a5ab8f97da92 6838 cgroup-bin_0.41-8+deb9u1_all.deb 4a4d92c1d0f48b3d3ec2094fb3a3ba1709c9aa379bf9f40bda8cdae5fffad74c 150892 cgroup-tools-dbgsym_0.41-8+deb9u1_amd64.deb 3ec68d335d5dea2044ef063478cac6f588f1b4bfe9ce760b696245d621d41748 68916 cgroup-tools_0.41-8+deb9u1_amd64.deb 98129fc899974999c3d64b1a1cee2e7b0206f68cd372611b4c2c8be34102e710 20186 libcgroup-dev_0.41-8+deb9u1_amd64.deb 0388031b60dbd2333bc2ef6c0acad1b1977211ef53877a3ed9b24f70b8474ac5 91470 libcgroup1-dbgsym_0.41-8+deb9u1_amd64.deb 9ebf7a353a27f3f865f8baf2eafc27c2ceb7dd704f9cfa59e202a57f168362b8 44784 libcgroup1_0.41-8+deb9u1_amd64.deb adf6ebfa1e156143e6b77f9e5651924cc3c3bf1c83d5c78997f281bd65fb91cb 8034 libcgroup_0.41-8+deb9u1_amd64.buildinfo 807690bcf816e79d0e83126ecba51d93ede33eb0fbb4af5ce5b42065e714f88c 4936 libpam-cgroup-dbgsym_0.41-8+deb9u1_amd64.deb
Bug#904763: marked as done (vmtk: /usr/bin/vmtk fails to run: ImportError: No module named vtk)
Your message dated Sun, 02 Sep 2018 20:47:14 + with message-id and subject line Bug#904763: fixed in vmtk 1.3+dfsg-2.1+deb9u1 has caused the Debian Bug report #904763, regarding vmtk: /usr/bin/vmtk fails to run: ImportError: No module named vtk 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.) -- 904763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vmtk Version: 1.3+dfsg-2.1 Severity: serious $ vmtk Traceback (most recent call last): File "/usr/bin/vmtk", line 26, in import vtk ImportError: No module named vtk Andreas --- End Message --- --- Begin Message --- Source: vmtk Source-Version: 1.3+dfsg-2.1+deb9u1 We believe that the bug you reported is fixed in the latest version of vmtk, 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 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated vmtk 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, 14 Aug 2018 23:17:15 +0300 Source: vmtk Binary: libvmtk1.3 python-vmtk libvmtk-dev vmtk Architecture: source Version: 1.3+dfsg-2.1+deb9u1 Distribution: stretch Urgency: medium Maintainer: Debian Science Team Changed-By: Adrian Bunk Description: libvmtk-dev - shared links and header files for vmtk libvmtk1.3 - runtime libraries for vmtk python-vmtk - Python interface for vmtk vmtk - the Vascular Modeling Toolkit Closes: 904763 Changes: vmtk (1.3+dfsg-2.1+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * python-vmtk: Add the missing dependency on python-vtk6. (Closes: #904763) Checksums-Sha1: 320116323654309fd32f124b268fc6d82a41dc1e 2445 vmtk_1.3+dfsg-2.1+deb9u1.dsc 6f4f20700ad7cce18cbdab0d5061f48c123a1711 15436 vmtk_1.3+dfsg-2.1+deb9u1.debian.tar.xz Checksums-Sha256: 7b9821bbdc390566a9d7225e0ba6780ff11de9caee8f8b70c73fe0a83814b2b3 2445 vmtk_1.3+dfsg-2.1+deb9u1.dsc 14cb4d4abf73d51ce2b4ecab009ebd5d7fa42ada2f6c16228376c3e393cf42fa 15436 vmtk_1.3+dfsg-2.1+deb9u1.debian.tar.xz Files: 8e57c7e6cc7ccd4ebfee09e2994832e6 2445 non-free/science optional vmtk_1.3+dfsg-2.1+deb9u1.dsc 705d6f90424eda63f8011a31c659a28c 15436 non-free/science optional vmtk_1.3+dfsg-2.1+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltzQKUACgkQiNJCh6LY mLExMg//Y7U2TuqJqXx/SkPUfl4ArgeaxS4Uny2y7c+kIJ9MwkGfCFZcu1not0jn KbYAXszKSJIoqSw32Cb45LQPTacbTJa+RXAzRpPViJI/CbFoF0Gy68Z9VHKOC7CH aASa4USke+9/JIuaFJiCiakU93MFTTA1OjLfvMEZXQ7U/jg9ACgITbY1KuOhZSLs rdw5++S9XGl8e1Q+JjNaH5Eq3BZ1gDrQN/6a4993s4OANDjLicGcTO9d7fIiQDR6 JM5HasoqjZzKUgnDScEGIzKq/DjStjmembgUZn57PcHg1V75w8NvqOlJ2eLOBy/+ kY6dzjwlZFL+ttpYvwSHZzZop5HuRJvfWxdi+GkawRw48gEiZEQF2jEDPoy07WKd kjBKMacsSiKRPKzxOT3OyBTVOd8ETVXdtjnEFCwGJ5ZfmiEjHaIy6YoYUDicC4fw pmFpHeO3qVi1mLxYtYVaREjy9BbiOq/lhP6zU5zEgdA5S1lo0ETMsfMGPGfZe6er OUBATodF6wLVikVUfNewVqAoGrj4B9MEqsUVTVgEeyzFQvTeUKIRk6g4kGOq9zTC jeV2ai6Rc6pjJR+qK/3TcOyTPeI2UXghJBU2lG4KJVAZkzYklvT1jHcmX6kU5IrJ HupRW859V9g2dg5w/oLE9+xlIRzQHUhLdHqtlgoGIpOsaVQEueo= =d7hY -END PGP SIGNATURE End Message ---
Bug#875637: marked as done (iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf)
Your message dated Sun, 02 Sep 2018 20:47:10 + with message-id and subject line Bug#875637: fixed in iipimage 1.0-1+deb9u1 has caused the Debian Bug report #875637, regarding iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf 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.) -- 875637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: iipimage-server Version: 1.0-1+b1 Severity: grave Tags: patch Justification: renders package unusable The default installation with Apache2 won't work with the provided configuration file because that file uses "Directory" instead of "Location". A fixed version is shown below. -- System Information: Debian Release: 9.1 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/16 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) Versions of packages iipimage-server depends on: ii libapache2-mod-fcgid 1:2.3.9-1+b1 ii libc6 2.24-11+deb9u1 ii libfcgi0ldbl 2.4.0-8.4+b1 ii libgcc1 1:6.3.0-18 ii libgomp1 6.3.0-18 ii libjpeg62-turbo 1:1.5.1-2 ii libmemcached111.0.18-4.1 ii libstdc++66.3.0-18 ii libtiff5 4.0.8-2+deb9u1 Versions of packages iipimage-server recommends: ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11+deb9u1 pn libvips-tools Versions of packages iipimage-server suggests: pn iipimage-doc pn memcached -- Configuration Files: /etc/apache2/mods-available/iipsrv.conf changed: ScriptAlias /iipsrv/ "/usr/lib/iipimage-server/" AllowOverride None Options None Order allow,deny Allow from all = 2.4> Require all granted # Set the module handler AddHandler fcgid-script .fcgi FcgidInitialEnv VERBOSITY "1" FcgidInitialEnv LOGFILE "/var/log/iipsrv.log" FcgidInitialEnv MAX_IMAGE_CACHE_SIZE "10" FcgidInitialEnv JPEG_QUALITY "90" FcgidInitialEnv MAX_CVT "5000" FcgidInitialEnv MEMCACHED_SERVERS "localhost" FcgidIdleTimeout 0 FcgidMaxProcessesPerClass 1 -- no debconf information --- End Message --- --- Begin Message --- Source: iipimage Source-Version: 1.0-1+deb9u1 We believe that the bug you reported is fixed in the latest version of iipimage, 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 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated iipimage 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, 27 Feb 2018 19:48:33 +0200 Source: iipimage Binary: iipimage-server iipimage-doc Architecture: source Version: 1.0-1+deb9u1 Distribution: stretch Urgency: medium Maintainer: Mathieu Malaterre Changed-By: Adrian Bunk Description: iipimage-doc - Web-based streamed viewing and zooming of ultra high-resolution i iipimage-server - Web-based streamed viewing and zooming of ultra high-resolution i Closes: 875637 Changes: iipimage (1.0-1+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Fix apache configuration. Closes: #875637 Checksums-Sha1: 6b5a3dbf28e68cbf2aa2c442be747d409b9c63ac 2110 iipimage_1.0-1+deb9u1.dsc 09c4b40bcdeb27702e6f209805db0856f27ed122 37224 iipimage_1.0-1+deb9u1.debian.tar.xz Checksums-Sha256: 6fadb1fac8003bcf6a2df35db1ec4ffd3a269824ca219f9b876f4f90013ad31f 2110 iipimage_1.0-1+deb9u1.dsc 133e535e1158d0344e798cb46c66865e81aa56b7af503a3e3c65cb003a7835c8 37224 iipimage_1.0-1+deb9u1.debian.tar.xz Files: da2a163c606fc80514e3fe098da1641a 2110 web optional iipimage_1.0-1+deb9u1.dsc b57b53fc151d006b97c96104c680bd55 37224 web optional iipimage_1.0-1+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqVnbkACgkQiNJCh6LY
Bug#889210: marked as done (libdap-doc is empty)
Your message dated Sun, 02 Sep 2018 20:47:12 + with message-id and subject line Bug#889210: fixed in libdap 3.18.2-2+deb9u1 has caused the Debian Bug report #889210, regarding libdap-doc is 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.) -- 889210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdap-doc Version: 3.18.2-2 Severity: grave $ dpkg -L libdap-doc /. /usr /usr/share /usr/share/doc /usr/share/doc/libdap-doc /usr/share/doc/libdap-doc/changelog.Debian.gz /usr/share/doc/libdap-doc/changelog.gz /usr/share/doc/libdap-doc/copyright /usr/share/doc/libdap-doc/readme.txt.gz $ readme.txt.gz contains installation instructions that shouldn't even be in the binary package. The package in jessie contains 80 MB that seem to be missing. --- End Message --- --- Begin Message --- Source: libdap Source-Version: 3.18.2-2+deb9u1 We believe that the bug you reported is fixed in the latest version of libdap, 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 889...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated libdap 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, 27 Feb 2018 19:01:38 +0200 Source: libdap Binary: libdap23 libdapclient6v5 libdapserver7v5 libdap-bin libdap-dev libdap-doc Architecture: source Version: 3.18.2-2+deb9u1 Distribution: stretch Urgency: medium Maintainer: Alastair McKinstry Changed-By: Adrian Bunk Description: libdap-bin - Binaries for the libdap Data Access Protocol library libdap-dev - Development files (headers and static libraries) for libdap libdap-doc - Documentation for the libdap Data Access Protocol library libdap23 - Open-source Project for a Network Data Access Protocol library libdapclient6v5 - Client library for the Network Data Access Protocol libdapserver7v5 - Server library for the Network Data Access Protocol Closes: 837429 889210 Changes: libdap (3.18.2-2+deb9u1) stretch; urgency=medium . * Non-maintainer upload. * Add libdap-doc.docs to install docs. Closes: #889210 * Drop description reference to external docs. Closes: #837429 Checksums-Sha1: 050ac10ddfc1a43b595b0aa9278b31a75557364b 2362 libdap_3.18.2-2+deb9u1.dsc 60b3db9e004fe919ec8ca22af5037a41bd875731 13108 libdap_3.18.2-2+deb9u1.debian.tar.xz Checksums-Sha256: b89ddafb4bd915db5edda6b3c705cb098f51918887ba86b4e8f7ac7f489355d3 2362 libdap_3.18.2-2+deb9u1.dsc 0f5863da77272a60528afd5865c880c1f77ccb47c3686f7083037e7e52fa6fb7 13108 libdap_3.18.2-2+deb9u1.debian.tar.xz Files: b3abdc626ecb2d8c231933c5385431cf 2362 utils optional libdap_3.18.2-2+deb9u1.dsc 3ba23e4940ca40010eeac1e3aaa25615 13108 utils optional libdap_3.18.2-2+deb9u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqVma4ACgkQiNJCh6LY mLHLrxAAiSU1FpjJYQecGmb5NYlDOxnXhu7YCnDC6ZNH7UYMtZaapFuqsOYQMB9o 0sYLgqCC+0XMvfEwG7FGseUEA0Ri3zZ06+dAOEGbOISQNrwjihYtLSytfEC6q8aT 2s9JjD6XkRYIcKfpkiy8F6eDOIIaOXo1PpSDmedHQXwBs+NVK04wazSNEsFgsz+e 6B5f/bsnyKOf0S3errjXbDdCEKmanEdD+T+IGAZ8botvdH9BCoV/XhWRPvjKbXjw yJUgC0RAAkeMLCt2xyphNX5jcjviQjKLGm6JzHQNfchB741cc6b/yoGpM1ZfXfyM qEq+pt/WSZ+flQQ0W2uzno/k3u0cCVj3m98wqZm7Umt6Nj3SkVtabwIPhCKw8RKT EgpnoQi/VFzyoyMc8vFydLWC1CXpZNth4BbIG6Z1qkbApH3naWf2Hr3KKof86Zbs +Ogf/23oYUanKTcVHCuEYaVlHJHkwf0Mw9SROdXZOX+H3Gf1lJbUmPQAubwivi51 JUx1e50vBp/DKFI1O+zutIqi9QXtmcXjgKXl+Bz65F+e/wl7vXysYfbGkPJeEicA ceuzQ0rfnrl7NdGeWSIRidcg4ujRH6a7OK1BWvWC/WuUAfY5u/rbZwPLvOx3ktZe myAh2O4O1tMFyrJYhXvCIJnWub5OIe4AmSvy8tHPBrF6ysPi3ww= =4m93 -END PGP SIGNATURE End Message ---
Bug#895959: marked as done (libnet-ssleay-perl: FTBFS with openssl 1.1.1 in exp)
Your message dated Sun, 02 Sep 2018 20:36:43 +
with message-id
and subject line Bug#895959: fixed in libnet-ssleay-perl 1.85-2
has caused the Debian Bug report #895959,
regarding libnet-ssleay-perl: FTBFS with openssl 1.1.1 in exp
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.)
--
895959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnet-ssleay-perl
Version: 1.85-1
Severity: important
There is openssl 1.1.1-pre4 in experimental right now and
libnet-ssleay-perl fails the testsuite with it. I was playing with it
for the last month or so and already figured out a few things. This is
t/local/07_sslecho.t I refer here to.
The SSL_read() and SSL_write() wrapper need to handle a possible retry.
The man-page for both function [0] says that it might need to be retried
with the same arguments. With the following hunk:
diff --git a/SSLeay.xs b/SSLeay.xs
--- a/SSLeay.xs
+++ b/SSLeay.xs
@@ -1999,7 +1999,17 @@ SSL_read(s,max=32768)
int got;
PPCODE:
New(0, buf, max, char);
- got = SSL_read(s, buf, max);
+
+ do {
+ int err;
+
+ got = SSL_read(s, buf, max);
+ if (got > 0)
+ break;
+ err = SSL_get_error(s, got);
+ if (err != SSL_ERROR_WANT_READ)
+ break;
+ } while (1);
/* If in list context, return 2-item list:
* first return value: data gotten, or undef on error (got<0)
@@ -2051,10 +2061,20 @@ SSL_write(s,buf)
SSL * s
PREINIT:
STRLEN len;
+ int err;
+ int ret;
INPUT:
char * buf = SvPV( ST(1), len);
CODE:
- RETVAL = SSL_write (s, buf, (int)len);
+ do {
+ret = SSL_write (s, buf, (int)len);
+if (ret > 0)
+break;
+err = SSL_get_error(s, ret);
+if (err != SSL_ERROR_WANT_WRITE)
+break;
+ } while (1);
+ RETVAL = ret;
OUTPUT:
RETVAL
@@ -2083,8 +2103,20 @@ SSL_write_partial(s,from,count,buf)
if (len < 0) {
croak("from beyound end of buffer");
RETVAL = -1;
- } else
- RETVAL = SSL_write (s, &(buf[from]), (count<=len)?count:len);
+ } else {
+int ret;
+int err;
+
+do {
+ret = SSL_write (s, &(buf[from]), (count<=len)?count:len);
+if (ret > 0)
+break;
+err = SSL_get_error(s, ret);
+if (err != SSL_ERROR_WANT_WRITE)
+break;
+} while (1);
+RETVAL = ret;
+ }
OUTPUT:
RETVAL
I was able to let the test-suite continue a little further. As per
upstream [1] this was always the case it worked by coincidence before.
The next thing is that step 24 within 07_sslecho.t blocks forever. As it
turns out one side does "shutdown $s, 2;" (around line 170) while the
other does a read+write operation. In "older" openssl is seems to just
work but in the newer one SIGPIPE is received and this seems to
stall/block the test case. By adding:
index 5e16b04b55ea..c60afccc0051 100644
--- a/t/local/07_sslecho.t
+++ b/t/local/07_sslecho.t
@@ -14,6 +14,7 @@ BEGIN {
}
plan tests => 78;
+$SIG{'PIPE'} = 'IGNORE';
my $sock;
my $pid;
(
it does not stall anymore but complains about the return value from
write:
ok 21 - get_cipher
ok 22 - get_shared_ciphers
ok 23 - ssl_read_all
not ok 24 - ssl_write_all
# Failed test 'ssl_write_all'
# at t/local/07_sslecho.t line 88.
ok 25 - new
This should be okay since the other side never reads anything and just
shutdowns the socket.
Could you please take a look and forward it upstream?
[0] https://manpages.debian.org/stretch/libssl-doc/SSL_read.3ssl.en.html#WARNING
[1] https://github.com/openssl/openssl/issues/5637#issuecomment-381364019
Sebastian
--- End Message ---
--- Begin Message ---
Source: libnet-ssleay-perl
Source-Version: 1.85-2
We believe that the bug you reported is fixed in the latest version of
libnet-ssleay-perl, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Damyan Ivanov (supplier of updated
Processed: Re: Bug#907819: jellyfish: Does not build on paths containing "-L"
Processing commands for cont...@bugs.debian.org: > retitle 907819 jellyfish: Does not build on paths containing "-L" resulting > in random FTBFS when built by sbuild Bug #907819 [src:jellyfish] jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0) Changed Bug title to 'jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild' from 'jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0)'. > severity 907819 serious Bug #907819 [src:jellyfish] jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild Severity set to 'serious' from 'minor' > thanks Stopping processing here. Please contact me if you need assistance. -- 907819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905578: Install script from emacs-goodies-el package failed
On Fri, Aug 10, 2018 at 09:53:52AM +0100, Sean Whitton wrote: > > On Tue 07 Aug 2018 at 09:28PM -0400, Nicholas D Steeves wrote: > > > On Tue, Aug 07, 2018 at 10:12:25AM +0800, Sean Whitton wrote: > >> Hello, > >> > >> On Mon 06 Aug 2018 at 09:18AM -0400, Nicholas D Steeves wrote: > >> > >> > Thank you for not overriding the default apt behaviour of allowing > >> > upgrades to install additional recommended packages. The Debian > >> > Emacsen team is in the process of transitioning emacs-goodies-el to a > >> > dummy transitional package that depends on a set of elpa-packages, > >> > which are more resistant to the type of issue [1] represents. > >> > >> Just to be clear, as a package maintainer you may not assume that > >> recommends will be installed. > > > > Yes, of course... > > > > In your opinion, should emacs-goodies-el use hard depends at this > > time? Also, as a matter of policy, must dummy transitional packages > > use hard depends? > > ISTM that it should be a Depends: relation. Thanks! I've committed changes to git changing these to Depends. Also David recommended providing a status update to delay autoremoval due to this bug, so here it is: The resolution of this bug in testing has taken longer than expected because emacsen-common and emacs (unversioned) have not yet migrated. My best guess why is the 'auto-emacs-defaults-rm' transition where the emacs-defaults package will be removed from the archive, and maybe also the removal of src:emacs25. bin:emacs25 is now provided by src:emacs. Regards, Nichola signature.asc Description: PGP signature
Bug#907835: newer version in stable
Source: xen Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Severity: serious The version of the Xen packages in unstable and buster is lower than the one in Debian stretch. That seems highly irregular and will obviously break upgrades to buster. The reason this is marked as "serious" is because I consider this a "severe violation of Debian policy". This would be section 3 of the Debian policy, although it curiously does not explicitely state that versions between different suites should be incrementing. I still consider this a release critical bug and that new upstream packages should first be uploaded to unstable, unless there is a security issue (which is the case here) in which case they should be simultaneously uploaded to both suites. Thanks, A. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#905735: emacs-goodies-el: postinst failure due to missing lcomp.el
The resolution of this bug in testing has taken longer than expected because emacsen-common and emacs (unversioned) have not yet migrated. My best guess why is the 'auto-emacs-defaults-rm' transition where the emacs-defaults package will be removed from the archive, and maybe also the removal of src:emacs25. bin:emacs25 is now provided by src:emacs. Regards, Nicholas signature.asc Description: PGP signature
Bug#907829: p4est: FTBFS on single CPU machines (?)
Control: severity -1 important On Sun, Sep 02, 2018 at 05:21:28PM +, Santiago Vila wrote: >... > The error message (not enough slots available) suggests that this package is > not ready to be built on single-CPU machines. >... This matches the build failure on hppa, but is not a problem for any release architecture buildd. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#907829: p4est: FTBFS on single CPU machines (?)
Processing control commands: > severity -1 important Bug #907829 [src:p4est] p4est: FTBFS on single CPU machines (?) Severity set to 'important' from 'serious' -- 907829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#907819: jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0)
Processing control commands: > severity -1 minor Bug #907819 [src:jellyfish] jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0) Severity set to 'minor' from 'serious' -- 907819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907819: jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0)
Control: severity -1 minor On Sun, Sep 02, 2018 at 03:41:11PM +, Santiago Vila wrote: > Package: src:jellyfish > Version: 2.2.8-3 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in sid and it failed with this error: > > > /usr/bin/ld: cannot find -ljellyfish-2.0 > collect2: error: ld returned 1 exit status > error: command 'x86_64-linux-gnu-g++' failed with exit status 1 > > > I'm building on amd64 and this error happens randomly for me > (sometimes it fails, sometimes it does not), but it happened at least > once in the official autobuilders in another architecture: > > https://buildd.debian.org/status/fetch.php?pkg=jellyfish=powerpc=2.2.8-3=1531093335=0 > > so it seems that the error is not architecture-specific and we can > assume it will also fail randomly on the official buildds too. >... This powerpc build failure is completely unrelated and non-random, that's a missing -latomic. https://people.debian.org/~sanvila/build-logs/jellyfish/jellyfish_2.2.8-3_amd64-20180902T150417Z ... I: NOTICE: Log filtering will replace 'build/jellyfish-La3pVw/jellyfish-2.2.8' with '<>' ... x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-3.7/jellyfish_wrap.o -L/build/jellyfisha3pVw/jellyfish-2.2.8/debian/tmp//usr/lib/x86_64-linux-gnu -Wl,--enable-new-dtags,-R/<>/debian/tmp/usr/lib/x86_64-linux-gnu -ljellyfish-2.0 -lpthread -o /<>/.pybuild/cpython3_3.7_dna-jellyfish/build/_dna_jellyfish.cpython-37m-x86_64-linux-gnu.so /usr/bin/ld: cannot find -ljellyfish-2.0 Something (libtool?) removes the "-L" from the "jellyfish-La3pVw", this is not a problem on the buildds that use sane paths. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#885823: marked as done (evolution-rss: Unnecessary Build-Depends on libgconf2-dev)
Your message dated Sun, 02 Sep 2018 18:18:57 + with message-id and subject line Bug#885823: fixed in evolution-rss 0.3.95-9 has caused the Debian Bug report #885823, regarding evolution-rss: Unnecessary Build-Depends on libgconf2-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.) -- 885823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: evolution-rss Version: 0.3.95-8 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster Your package depends or build-depends on gconf, but gconf will be removed from Debian soon. gconf's last release was about 5 years ago. It has been replaced by gsettings (provided in Debian by source glib2.0 ) References -- https://developer.gnome.org/gio/stable/ch34.html https://developer.gnome.org/gio/stable/GSettings.html On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: evolution-rss Source-Version: 0.3.95-9 We believe that the bug you reported is fixed in the latest version of evolution-rss, 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 885...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated evolution-rss 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: Sun, 02 Sep 2018 14:02:47 -0400 Source: evolution-rss Binary: evolution-rss Architecture: source Version: 0.3.95-9 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Description: evolution-rss - Evolution RSS Reader Plugin Closes: 885823 Changes: evolution-rss (0.3.95-9) unstable; urgency=medium . * Update Vcs fields for migration to https://salsa.debian.org/ * Add dont-require-gconf.patch * Drop obsolete Build-Depends on gconf (Closes: #885823) Checksums-Sha1: c052e09b0dbc17ce808f432e565f932b7303799c 2341 evolution-rss_0.3.95-9.dsc 15f8ba9ec8783baf66b893c457bb53b17d297a74 9356 evolution-rss_0.3.95-9.debian.tar.xz c15d850e71379d48381cf1bd60526e576e1d8a5f 17565 evolution-rss_0.3.95-9_source.buildinfo Checksums-Sha256: 776cf3bfb3dee36e1c89c2fe96b75459429a1a1f421cfeea8fb01c481304b068 2341 evolution-rss_0.3.95-9.dsc f0ae7f4aaf23628f788ccd19439f245d0b801616c4fb1ad554295e6271a3af2b 9356 evolution-rss_0.3.95-9.debian.tar.xz 28d089029f7fc8c634f8a36ebbdf412f048edb8386ab62e9c831134650d9393c 17565 evolution-rss_0.3.95-9_source.buildinfo Files: b2588b697e7f5c9c4abaa3e275906141 2341 gnome optional evolution-rss_0.3.95-9.dsc 5e6704268d4958a3013e7214f2b4ac34 9356 gnome optional evolution-rss_0.3.95-9.debian.tar.xz ac17e4c4025c7ec3866c2f737fe52ddb 17565 gnome optional evolution-rss_0.3.95-9_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAluMJhYACgkQ5mx3Wuv+ bH2c0hAApcfoIGrZ2Jy1TWTFJmopOtYNET2TKLcdFsl3iNrtHJIYxFPzLHgAc1gu BPYIc/Kao2AsnA7wnLZOlSLKtm74SHfbxZ/lKFnbyd72m5iFNQ1AghAMhRPFibpd OEyKDi//zrDDQv2jRkEoBgsz0l07Xrk5teer+SexD0OdVbsU/LtO3i++mKkc/YE9 m8VVAZWluoVnPODYMYEKLqG/A5quJ1ugQIf+B0qbIndFbyBSIL59FzSq+21/D0TA KXxOgDpG3h0FW6syfc7sY9mjZFIHyq9W1AgokNZXeH+KraKiLPFvJog1t/bnuZPy cro4IjsxS0Uj24O+5S1n94eJCuVvAVa1S3/4/Gqo6FABKLlstpLaHGrP3HijoFql sgd5XxI1Qr60g5fxVXu1q3EZBFBm95cyDa+jzf4pxX/SBwzPbdCQB+DiYPjnjFm2 4AqTh3GxlnWVRkwrr9C+r8hirp07niWvrL6GVqNC9C486+WJTOAiXE5RMvHZ443x pnLJ1bnKCHC8bgkZ6So6HpF7p9pmeP8RqPIZ6i3BP2H0Jpr/JuDGc9Nc9SUe+E2H fTtfJspuV67XBi6nOtKXcwXIBN1fBj8WfN/TLGA5sDHWD9ENBYOIYkPAAohDkeQ8 pxqyoEM6ghEyBmA+mzTiPV47C+2zjd6DUTXQURIzqmNhsHhcFro= =l0Ah -END PGP SIGNATURE End Message ---
Bug#885823: evolution-rss: raising severity of gconf dependency bug
On Sun, Sep 2, 2018 at 1:28 PM Yavor Doganov wrote: > AFAICS it's already ported and the code uses conditionals based on > EVOLUTION_VERSION, which evaluate to true. The only thing that has to > be done is to remove libgconf2-dev from B-D. Thank you! It also needed a minor patch for its configure.ac. Jeremy Bicha
Bug#885823: evolution-rss: raising severity of gconf dependency bug
retitle 885823 evolution-rss: Unnecessary Build-Depends on libgconf2-dev thanks On Mon, Mar 12, 2018 at 03:40:35PM -0400, Jeremy Bicha wrote: > Please try to port your package away from gconf. AFAICS it's already ported and the code uses conditionals based on EVOLUTION_VERSION, which evaluate to true. The only thing that has to be done is to remove libgconf2-dev from B-D.
Bug#906955: marked as done (isync: can't verify some ssl certificate(e.g. imap.gmail.com))
Your message dated Sun, 02 Sep 2018 17:49:01 + with message-id and subject line Bug#906955: fixed in isync 1.3.0-2 has caused the Debian Bug report #906955, regarding isync: can't verify some ssl certificate(e.g. imap.gmail.com) 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.) -- 906955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: isync Version: 1.3.0-1 Severity: grave Dear Maintainer, % mbsync -V -l gmail -c test-mbsyncrc Reading configuration file /test-mbsyncrc Channel gmail-inbox Opening master store gmail-remote... Resolving imap.gmail.com... ok Connecting to imap.gmail.com (108.177.125.109:993)... Opening slave store gmail-local... SSL error connecting imap.gmail.com (108.177.125.109:993): self signed certificate But openssl s_client -connect imap.gmail.com:993 -CAfile /etc/ssl/certs/ca-certificates.crt ... Start Time: 1534954195 Timeout : 7200 (sec) Verify return code: 0 (ok) Extended master secret: yes ... When I rollback libssl ver. 1.1.0h-4, All fine. Maybe we have to rebuild or modify isync for libssl 1.1.1 test-mbsyncrc as follows: ... IMAPAccount gmail Host imap.gmail.com User MY ACCOUT NAME Pass MY APP PASSWORD Port 993 SSLType IMAPS SSLVersions TLSv1.2 CertificateFile /etc/ssl/certs/ca-certificates.crt ... Best Wishes, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages isync depends on: ii libc6 2.27-5 ii libdb5.35.3.28+dfsg1-0.1 ii libsasl2-2 2.1.27~101-g0780600+dfsg-3.1 ii libssl1.1 1.1.1~~pre9-1 ii zlib1g 1:1.2.11.dfsg-1 isync recommends no packages. Versions of packages isync suggests: pn mutt -- no debconf information --- End Message --- --- Begin Message --- Source: isync Source-Version: 1.3.0-2 We believe that the bug you reported is fixed in the latest version of isync, 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 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessandro Ghedini (supplier of updated isync 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: Sun, 02 Sep 2018 18:31:35 +0100 Source: isync Binary: isync Architecture: source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Nicolas Boullis Changed-By: Alessandro Ghedini Description: isync - IMAP and MailDir mailbox synchronizer Closes: 906955 Changes: isync (1.3.0-2) unstable; urgency=medium . * Update vcs-* to point to salsa.d.o * Bump Standards-Version to 4.2.1 (no changes needed) * Remove myself from Uploaders * Use SNI when connecting with SSL. Thanks to Vincent Bernat for the patch (Closes: #906955) * Fix insecure-copyright-format-uri Checksums-Sha1: 9c43b6b7ea7dfdba30878fad686dd42804fe8026 1886 isync_1.3.0-2.dsc 226d270ede1071f18c049483009f1860e64b385e 7612 isync_1.3.0-2.debian.tar.xz fabeca8ca6313852a22bc5df42d2e77bcbfc57b6 6087 isync_1.3.0-2_amd64.buildinfo Checksums-Sha256: 812ec4a49b8b9a517883df51016558a71d2b3e4f8215e99ca80e089203e0a112 1886 isync_1.3.0-2.dsc da72e00f8159ddec843f6cfb94f82583e4af33a133596af1b14749fbe68c2480 7612 isync_1.3.0-2.debian.tar.xz a4d81c89eaa135d76efe9e28294fa311a64d7587060c0f3d0c6dabace137b0fd 6087 isync_1.3.0-2_amd64.buildinfo Files: e4504221b9d7e6b30fb3e6405681cd07 1886 mail optional isync_1.3.0-2.dsc d892315352e580fadd26c5497a1d97bb 7612 mail optional isync_1.3.0-2.debian.tar.xz 60c1b591f1deb7dca588357906b48d77 6087 mail optional isync_1.3.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBsId305pBx+F583DbwzL4CFiRygFAluMHuoACgkQbwzL4CFi RyjeEw//SXSKNxMi7blQsegmdbW6oA5YhyShbt4NJ19niEzeCKM65OruoMOHyR1Y VRNV4jxZXlruZemRxO4TElVW6VaNbujwtQm2WPRnSYzae5lfhFmJNQp3GlAb2KTL
Processed: Re: Bug#885823: evolution-rss: raising severity of gconf dependency bug
Processing commands for cont...@bugs.debian.org: > retitle 885823 evolution-rss: Unnecessary Build-Depends on libgconf2-dev Bug #885823 [src:evolution-rss] evolution-rss: Depends on gconf Changed Bug title to 'evolution-rss: Unnecessary Build-Depends on libgconf2-dev' from 'evolution-rss: Depends on gconf'. > thanks Stopping processing here. Please contact me if you need assistance. -- 885823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907829: p4est: FTBFS on single CPU machines (?)
Package: src:p4est Version: 1.1-5 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a debian/rules override_dh_autoreconf make[1]: Entering directory '/<>' echo 1.1 > .tarball-version echo 1.1 > sc/.tarball-version dh_autoreconf ./bootstrap Running bootstrap in subdirectory sc --- This is the bootstrap script for libsc --- It is NOT required to run bootstrap to build from a tar.gz archive Development requires a libtool recent enough to contain LT_INIT (2.2 works) Current directory is /<>/sc libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. [... snipped ...] ./test/sc_test_sort Either request fewer slots for your application, or make more slots available for use. -- FAIL test/sc_test_sort (exit status: 1) FAIL: test/sc_test_sortb -- There are not enough slots available in the system to satisfy the 2 slots that were requested by the application: ./test/sc_test_sortb Either request fewer slots for your application, or make more slots available for use. -- FAIL test/sc_test_sortb (exit status: 1) Testsuite summary for libsc 1.1 # TOTAL: 12 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 12 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to p4...@librelist.com make[4]: *** [Makefile:2031: test-suite.log] Error 1 make[4]: Leaving directory '/<>/sc' make[3]: *** [Makefile:2139: check-TESTS] Error 2 make[3]: Leaving directory '/<>/sc' make[2]: *** [Makefile:2426: check-am] Error 2 make[2]: Leaving directory '/<>/sc' make[1]: *** [Makefile:3388: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:8: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 To reproduce, please try building with sbuild on a single-CPU machine, as I did. The error message (not enough slots available) suggests that this package is not ready to be built on single-CPU machines. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. My guess is that this is a bug in p4est but it's triggered by a build depends which changed behaviour somewhere between 2017-12-24 (where version 1.1-5 still built ok for me in buster) and 2018-06-03 (where it did not anymore). Thanks.
Bug#907828: debiman: FTBFS randomly (Test killed with quit: ran too long (10m0s))
Package: src:debiman Version: 0.0~git20180809.210e94b-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster and sid but it failed: [...] debian/rules binary-arch dh binary-arch --buildsystem=golang --with=golang dh_update_autotools_config -a -O--buildsystem=golang dh_autoreconf -a -O--buildsystem=golang dh_auto_configure -a -O--buildsystem=golang dh_auto_build -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=\"-trimpath=/<>/debiman-0.0\~git20180809.210e94b/obj-x86_64-linux-gnu/src\" -asmflags=\"-trimpath=/<>/debiman-0.0\~git20180809.210e94b/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/Debian/debiman github.com/Debian/debiman/cmd/debiman github.com/Debian/debiman/cmd/debiman-auxserver github.com/Debian/debiman/cmd/debiman-idx2rwmap github.com/Debian/debiman/cmd/debiman-minisrv github.com/Debian/debiman/internal/aux github.com/Debian/debiman/internal/bundled github.com/Debian/debiman/internal/commontmpl github.com/Debian/debiman/internal/convert github.com/Debian/debiman/internal/manpage github.com/Debian/debiman/internal/proto github.com/Debian/debiman/internal/recode github.com/Debian/debiman/internal/redirect github.com/Debian/debiman/internal/sitemap github.com/Debian/debiman/internal/tag github.com/Debian/debiman/internal/write github.com/Debian/debiman github.com/Debian/debiman/internal/bundled golang.org/x/text/internal/tag golang.org/x/text/language golang.org/x/text/internal/format golang.org/x/text/language/display github.com/Debian/debiman/internal/commontmpl golang.org/x/net/html/atom golang.org/x/net/html golang.org/x/net/context golang.org/x/sync/errgroup github.com/Debian/debiman/internal/convert github.com/Debian/debiman/internal/tag pault.ag/go/debian/version github.com/Debian/debiman/internal/manpage github.com/golang/protobuf/proto github.com/Debian/debiman/internal/proto golang.org/x/text/encoding/internal/identifier golang.org/x/text/transform golang.org/x/text/encoding golang.org/x/text/encoding/internal golang.org/x/text/encoding/charmap golang.org/x/text/encoding/japanese golang.org/x/text/encoding/korean golang.org/x/text/encoding/simplifiedchinese golang.org/x/text/encoding/traditionalchinese github.com/Debian/debiman/internal/recode github.com/Debian/debiman/internal/sitemap github.com/Debian/debiman/internal/write golang.org/x/crypto/openpgp/errors golang.org/x/crypto/openpgp/armor golang.org/x/crypto/cast5 golang.org/x/crypto/openpgp/elgamal golang.org/x/crypto/openpgp/s2k golang.org/x/crypto/openpgp/packet golang.org/x/crypto/openpgp golang.org/x/sys/unix golang.org/x/crypto/openpgp/clearsign pault.ag/go/blobstore pault.ag/go/debian/dependency pault.ag/go/debian/hashio pault.ag/go/debian/internal pault.ag/go/topsort pault.ag/go/debian/control github.com/kjk/lzma github.com/xi2/xz pault.ag/go/debian/deb pault.ag/go/archive github.com/Debian/debiman/cmd/debiman github.com/Debian/debiman/internal/redirect github.com/Debian/debiman/internal/aux github.com/Debian/debiman/cmd/debiman-auxserver github.com/Debian/debiman/cmd/debiman-idx2rwmap github.com/Debian/debiman/cmd/debiman-minisrv dh_auto_test -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/Debian/debiman github.com/Debian/debiman/cmd/debiman github.com/Debian/debiman/cmd/debiman-auxserver github.com/Debian/debiman/cmd/debiman-idx2rwmap github.com/Debian/debiman/cmd/debiman-minisrv github.com/Debian/debiman/internal/aux github.com/Debian/debiman/internal/bundled github.com/Debian/debiman/internal/commontmpl github.com/Debian/debiman/internal/convert github.com/Debian/debiman/internal/manpage github.com/Debian/debiman/internal/proto github.com/Debian/debiman/internal/recode github.com/Debian/debiman/internal/redirect github.com/Debian/debiman/internal/sitemap github.com/Debian/debiman/internal/tag github.com/Debian/debiman/internal/write ? github.com/Debian/debiman [no test files] === RUN TestWriteManpage === RUN TestWriteManpage//usr/share/man/man1/noref.1 === PAUSE TestWriteManpage//usr/share/man/man1/noref.1 === RUN TestWriteManpage//usr/share/man/man1/unresolved.1 === PAUSE TestWriteManpage//usr/share/man/man1/unresolved.1 === RUN TestWriteManpage//usr/share/man/man1/samepkg.1 === PAUSE TestWriteManpage//usr/share/man/man1/samepkg.1 === RUN TestWriteManpage//usr/share/man/man1/samepkgaux.1 === PAUSE TestWriteManpage//usr/share/man/man1/samepkgaux.1 === RUN TestWriteManpage//usr/share/man/man1/samedir.1 === PAUSE TestWriteManpage//usr/share/man/man1/samedir.1 === RUN TestWriteManpage//usr/share/man/man1/absolute.1 === PAUSE TestWriteManpage//usr/share/man/man1/absolute.1 === RUN TestWriteManpage//usr/share/man/man1/absolutenotfound.1 === PAUSE TestWriteManpage//usr/share/man/man1/absolutenotfound.1 === RUN
Bug#904669: xmds2: autopkgtest times out since 2018-07-19
* Paul Gevers [2018-07-26 14:28]: Source: xmds2 Version: 2.2.3+dfsg-10 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: timeout Dear maintainers, Since 2018-07-19 the autopkgtest of your package times out (after 2:47h) on ci.debian.net. I have copied the output below. Could you please make your autopkgtest robust against this? The autpkgtest used to pass in around 13 minutes, so something really changed. (gcc-8 was introduced as default around that time if I am correct). Don't hesitate to ask for help for the Debian CI team² if you need help solving this issue. I will blacklist this package on the ci.debian.net infrastructure and will remove the blacklist once this bug is fixed. I just uploaded version 2.2.3+dfsg-11 of the xmds2 package to unstable. The time-out problem seems to be fixed in this version. Could you please remove xmds2 from the blacklist to see what happens? Thanks, Rafael
Bug#907827: orocos-kdl: FTBFS (kdl/jntarray.hpp: No such file or directory)
Package: src:orocos-kdl Version: 1.4.0-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster and sid but it failed: [...] debian/rules binary-arch dh binary-arch --buildsystem=cmake --with python3 dh_update_autotools_config -a -O--buildsystem=cmake dh_autoreconf -a -O--buildsystem=cmake dh_auto_configure -a -O--buildsystem=cmake cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" .. -- The C compiler identification is GNU 8.2.0 -- The CXX compiler identification is GNU 8.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done [... snipped ...] cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile.cpp.o -c /<>/orocos_kdl/src/velocityprofile.cpp [ 78%] Building CXX object orocos_kdl/src/CMakeFiles/orocos-kdl.dir/velocityprofile_dirac.cpp.o cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile_dirac.cpp.o -c /<>/orocos_kdl/src/velocityprofile_dirac.cpp [ 80%] Building CXX object orocos_kdl/src/CMakeFiles/orocos-kdl.dir/velocityprofile_rect.cpp.o cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile_rect.cpp.o -c /<>/orocos_kdl/src/velocityprofile_rect.cpp [ 81%] Building CXX object orocos_kdl/src/CMakeFiles/orocos-kdl.dir/velocityprofile_spline.cpp.o cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile_spline.cpp.o -c /<>/orocos_kdl/src/velocityprofile_spline.cpp [ 83%] Building CXX object orocos_kdl/src/CMakeFiles/orocos-kdl.dir/velocityprofile_trap.cpp.o cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile_trap.cpp.o -c /<>/orocos_kdl/src/velocityprofile_trap.cpp [ 84%] Building CXX object orocos_kdl/src/CMakeFiles/orocos-kdl.dir/velocityprofile_traphalf.cpp.o cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/c++ -Dorocos_kdl_EXPORTS -I/usr/include/eigen3 -I/<>/obj-x86_64-linux-gnu/orocos_kdl/src -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/eigen3 -o CMakeFiles/orocos-kdl.dir/velocityprofile_traphalf.cpp.o -c /<>/orocos_kdl/src/velocityprofile_traphalf.cpp [ 85%] Linking CXX shared library liborocos-kdl.so cd /<>/obj-x86_64-linux-gnu/orocos_kdl/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/orocos-kdl.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -shared -Wl,-soname,liborocos-kdl.so.1.4 -o liborocos-kdl.so.1.4.0 CMakeFiles/orocos-kdl.dir/articulatedbodyinertia.cpp.o CMakeFiles/orocos-kdl.dir/chain.cpp.o CMakeFiles/orocos-kdl.dir/chaindynparam.cpp.o CMakeFiles/orocos-kdl.dir/chainfksolverpos_recursive.cpp.o CMakeFiles/orocos-kdl.dir/chainfksolvervel_recursive.cpp.o CMakeFiles/orocos-kdl.dir/chainidsolver_recursive_newton_euler.cpp.o CMakeFiles/orocos-kdl.dir/chainidsolver_vereshchagin.cpp.o CMakeFiles/orocos-kdl.dir/chainiksolverpos_lma.cpp.o CMakeFiles/orocos-kdl.dir/chainiksolverpos_nr.cpp.o
Bug#904669: xmds2: autopkgtest times out since 2018-07-19
Hi Rafael, On 02-09-18 18:10, Rafael Laboissière wrote: > I just uploaded version 2.2.3+dfsg-11 of the xmds2 package to unstable. > The time-out problem seems to be fixed in this version. Could you > please remove xmds2 from the blacklist to see what happens? I'll manually trigger a run (actually already did before even checking if the package was available). If it succeeds, I'll lift the blacklist. Paul signature.asc Description: OpenPGP digital signature
Bug#907239: ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double
Control: reopen -1 Control: severity -1 important On Sun, Sep 02, 2018 at 04:20:44PM +0200, Matthias Klumpp wrote: > Hi! > > After a conversation with upstream, this issue won't be fixed anytime soon. > So a removal request for the ppc64el binaries was filed instead. As long as we have FTBFS on the buildds there should be a (no longer RC) bug open. Changing the Architecture: list would be fine to close this bug. > Cheers, > Matthias cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#907239: ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double
Processing control commands:
> reopen -1
Bug #907239 {Done: Matthias Klumpp } [src:ldc] ldc: FTBFS on
ppc64el with .../disassembler.cpp.o uses 64-bit long double,
.../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double
Bug reopened
Ignoring request to alter fixed versions of bug #907239 to the same values
previously set
> severity -1 important
Bug #907239 [src:ldc] ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses
64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit
long double
Severity set to 'important' from 'serious'
--
907239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#907819: jellyfish: FTBFS randomly (ld: cannot find -ljellyfish-2.0)
Package: src:jellyfish Version: 2.2.8-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid and it failed with this error: /usr/bin/ld: cannot find -ljellyfish-2.0 collect2: error: ld returned 1 exit status error: command 'x86_64-linux-gnu-g++' failed with exit status 1 I'm building on amd64 and this error happens randomly for me (sometimes it fails, sometimes it does not), but it happened at least once in the official autobuilders in another architecture: https://buildd.debian.org/status/fetch.php?pkg=jellyfish=powerpc=2.2.8-3=1531093335=0 so it seems that the error is not architecture-specific and we can assume it will also fail randomly on the official buildds too. I've put all my failed build logs (buster and sid) here: https://people.debian.org/~sanvila/build-logs/jellyfish/ (but some of those failures are not linking failures). If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#900269: ifupdown: last version breaks upgrade
On 9/2/18 16:42, Guus Sliepen wrote: > On Sun, Sep 02, 2018 at 03:34:46PM +0200, Michael Biebl wrote: > >> On Mon, 28 May 2018 11:08:00 +0200 Eric Valette >> wrote: >> >>> When upgrading, you're stuck with the last message in console "setting up >>> ifupdown" and nothing else. The machine dropped its ip address but >>> seems to fails to acquire a new one. and stay like this for minutes. >> >> I'm suprised ifupdown reconfigures interfaces during package upgrades. >> Guus, is that intentional? > > That's not intentional. It seems I forgot to add --no-start to the calls > to dh_installsystemd. Well, networking.service has a corresponding init script of the same name, so dh_installinit should already cover that (a bit strange, but atm dh_installinit and dh_installsystemd are entangled that way for services which have a matching init script. This will change in the future though, where dh_installinit and dh_installsystemd will be disentangled). So yeah, it's probably a good idea to be pro-active and add --no-start to dh_installsystemd (even if it does nothing atm). That said, I notice that you have the dh_installsystemd calls in override_dh_installinit. You should consider moving those to override_dh_installsystemd, otherwise you'll get unexpected results (just have a look at the generated maintscript code where e.g. ifupdown-pre.service is handled twice). Looking at https://buildd.debian.org/status/fetch.php?pkg=ifupdown=i386=0.8.34=1527284212=0 you'll see: debian/rules override_dh_installinit make[1]: Entering directory '/<>' dh_installinit --name=networking --no-start dh_installinit --name=ifupdown-wait-online --no-start --no-scripts install -p -m 0644 debian/networking.defaults debian/ifupdown/etc/default/networking dh_installinit --name=networking --noscripts dh_installsystemd --name=networking dh_installsystemd --name=ifup@ dh_installsystemd --name=ifupdown-pre dh_installsystemd --no-enable --no-start --name=ifupdown-wait-online make[1]: Leaving directory '/<>' dh_installsystemd -a "dh_installsystemd -a" will generate maintscript code for ifupdown-pre and ifupdown-wait-online (again) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#900269: ifupdown: last version breaks upgrade
On Sun, Sep 02, 2018 at 03:34:46PM +0200, Michael Biebl wrote: > On Mon, 28 May 2018 11:08:00 +0200 Eric Valette > wrote: > > > When upgrading, you're stuck with the last message in console "setting up > > ifupdown" and nothing else. The machine dropped its ip address but > > seems to fails to acquire a new one. and stay like this for minutes. > > I'm suprised ifupdown reconfigures interfaces during package upgrades. > Guus, is that intentional? That's not intentional. It seems I forgot to add --no-start to the calls to dh_installsystemd. -- Met vriendelijke groet / with kind regards, Guus Sliepen signature.asc Description: PGP signature
Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop
Control: tags -1 + moreinfo On Tue, 28 Aug 2018 at 12:45:05 -0500, william l-k wrote: > The portion of the log near the times of start attempts had sections like > these: > > Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in > required component org.gnome.SettingsDaemon.Power.desktop > Aug 28 10:13:07 Username dbus-daemon[603]: [system] Activating via systemd: > service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostna > Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in > required component org.gnome.SettingsDaemon.XSettings.desktop > Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App > 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 > Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App > 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1 > Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not > connect: Connection refused > Aug 28 10:13:07 Username unknown[8630]: Cannot open display: > Aug 28 10:13:07 Username dbus-daemon[8532]: [session uid=1000 pid=8532] > Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.se > Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not > connect: Connection refused This looks as though these various programs were unable to connect to an X or Wayland display: that's a symptom, not a cause. If you go further back in the log, are there any log messages from gdm, gnome-shell or Xorg that might indicate why the X or Wayland display could not start? Thanks, smcv
Processed: Re: Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop
Processing control commands: > tags -1 + moreinfo Bug #907490 [gnome-shell] gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop Added tag(s) moreinfo. -- 907490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907239: marked as done (ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double)
Your message dated Sun, 2 Sep 2018 16:20:44 +0200 with message-id and subject line Re: Bug#907239: ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double has caused the Debian Bug report #907239, regarding ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double 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.) -- 907239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldc Version: 1:1.11.0-1 Severity: serious Hi, The ldc package FTBFS on ppc64el but built there in the past. """ /usr/bin/c++ -DLDC_DYNAMIC_COMPILE -DLDC_DYNAMIC_COMPILE_API_VERSION=1 -DLDC_ENABLE_PLUGINS -DLDC_LLVM_SUPPORTED_TARGET_AArch64=1 -DLDC_LLVM_SUPPORTED_TARGET_AMDGPU=1 -DLDC_LLVM_SUPPORTED_TARGET_ARM=1 -DLDC_LLVM_SUPPORTED_TARGET_AVR=1 -DLDC_LLVM_SUPPORTED_TARGET_BPF=1 -DLDC_LLVM_SUPPORTED_TARGET_Hexagon=1 -DLDC_LLVM_SUPPORTED_TARGET_Lanai=1 -DLDC_LLVM_SUPPORTED_TARGET_MSP430=1 -DLDC_LLVM_SUPPORTED_TARGET_Mips=1 -DLDC_LLVM_SUPPORTED_TARGET_NVPTX=1 -DLDC_LLVM_SUPPORTED_TARGET_PowerPC=1 -DLDC_LLVM_SUPPORTED_TARGET_Sparc=1 -DLDC_LLVM_SUPPORTED_TARGET_SystemZ=1 -DLDC_LLVM_SUPPORTED_TARGET_WebAssembly=1 -DLDC_LLVM_SUPPORTED_TARGET_X86=1 -DLDC_LLVM_SUPPORTED_TARGET_XCore=1 -I/<>/. -I/<>/dmd -I/<>/dmd/root -I/<>/build-static/dmd -I/<> -isystem /usr/lib/llvm-6.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DDMDV2 -DHAVE_SC_ARG_MAX -I/usr/lib/llvm-6.0/include -std=c++0x -fuse-ld=gold -Wl,--no-keep-files-mapped -Wl,--no-map-whole-files -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -O2 -DNDEBUG -fno-exceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wno-non-virtual-dtor -Wno-pedantic -mlong-double-64 -DLDC_POSIX -DIN_LLVM -DOPAQUE_VTBLS "-DLDC_INSTALL_PREFIX=/usr" -DLDC_LLVM_VER=600 "-DLDC_LIBDIR_SUFFIX=\"\"" -DLDC_HOST_LDMD=1 -DLDC_HOST_FE_VER=2068 -o CMakeFiles/LDCShared.dir/gen/arrays.cpp.o -c /<>/gen/arrays.cpp /usr/bin/ld: CMakeFiles/ldc-jit-rt-so.dir/jit-rt/cpp-so/disassembler.cpp.o uses 64-bit long double, /usr/lib/llvm-6.0/lib/libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double /usr/bin/ld: failed to merge target specific data of file /usr/lib/llvm-6.0/lib/libLLVMCore.a(LegacyPassManager.cpp.o) collect2: error: ld returned 1 exit status """ This issue prevents ldc from migrating to testing. Thanks, ~Niels --- End Message --- --- Begin Message --- Hi! After a conversation with upstream, this issue won't be fixed anytime soon. So a removal request for the ppc64el binaries was filed instead. Cheers, Matthias--- End Message ---
Bug#907239: ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double
Hi! After a conversation with upstream, this issue won't be fixed anytime soon. So a removal request for the ppc64el binaries was filed instead. Cheers, Matthias
Bug#900269: ifupdown: last version breaks upgrade
On Mon, 28 May 2018 11:08:00 +0200 Eric Valette wrote: > When upgrading, you're stuck with the last message in console "setting up > ifupdown" and nothing else. The machine dropped its ip address but > seems to fails to acquire a new one. and stay like this for minutes. I'm suprised ifupdown reconfigures interfaces during package upgrades. Guus, is that intentional? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#907785: Get "TypeError: mime.lookup is not a function" and failing to run
Processing commands for cont...@bugs.debian.org: > severity 907785 grave Bug #907785 [groovebasin] Get "TypeError: mime.lookup is not a function" and failing to run Severity set to 'grave' from 'important' > tags 907785 sid buster Bug #907785 [groovebasin] Get "TypeError: mime.lookup is not a function" and failing to run Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 907785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900269: ifupdown: last version breaks upgrade
On Thu, 7 Jun 2018 12:34:31 + Martin Hradil wrote: > This is caused by systemd-tty-ask-password-agent: > > rxvt-unicode(28371)-+-bash(28373)---sudo(14210)---dpkg(14211)---ifupdown.postin(14214)---systemctl(15338)---systemd-tty-ask(15342) > systemd-tty-ask-password-agent is a symptom, not the cause. Unfortunately the root cause is unknown. If there was a way to reliably reproduce the situation, the problem could be debugged further. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907806: scikit-learn: FTBFS in buster/sid (could not import 'distributed')
Package: src:scikit-learn
Version: 0.19.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
: # Explicit build system to avoid use of all-in-1 Makefile
dh build-indep --buildsystem=python_distutils --with python2,python3,autoreconf
dh_update_autotools_config -i -O--buildsystem=python_distutils
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh_autoreconf debian/rules -- clean_generated
make[2]: Entering directory '/<>'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
[... snipped ...]
raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'
==
ERROR: sklearn.tests.test_common.test_import_all_consistency
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
line 291, in wrapper
return fn(*args, **kwargs)
File
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_common.py",
line 131, in test_import_all_consistency
package = __import__(modname, fromlist="dummy")
File "/usr/lib/python2.7/dist-packages/joblib/test/test_dask.py", line 12, in
distributed = pytest.importorskip('distributed')
File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 138, in
importorskip
raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'
==
ERROR: sklearn.tests.test_docstring_parameters.test_tabs
--
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
line 291, in wrapper
return fn(*args, **kwargs)
File
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_docstring_parameters.py",
line 143, in test_tabs
mod = importlib.import_module(modname)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/usr/lib/python2.7/dist-packages/joblib/test/test_dask.py", line 12, in
distributed = pytest.importorskip('distributed')
File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 138, in
importorskip
raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'
--
Ran 3895 tests in 169.771s
FAILED (SKIP=19, errors=6)
make[1]: *** [debian/rules:89: python-test2.7] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:42: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess
returned exit status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scikit-learn.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
Processed: bug 907716 is forwarded to https://github.com/tomerfiliba/rpyc/issues/299
Processing commands for cont...@bugs.debian.org: > forwarded 907716 https://github.com/tomerfiliba/rpyc/issues/299 Bug #907716 [src:rpyc] rpyc: FTBFS in buster/sid (failing tests) Set Bug forwarded-to-address to 'https://github.com/tomerfiliba/rpyc/issues/299'. > thanks Stopping processing here. Please contact me if you need assistance. -- 907716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907493: ghostscript causes multiple autopkgtests to time out
Control: reassign -1 ghostscript 9.22~dfsg-3 Control: retitle -1 ghostscript causes multiple autopkgtests to time out Control: affects -1 src:cups src:gutenprint src:dymo-cups-drivers Control: affects -1 src:epson-inkjet-printer-escpr On 31-08-18 21:49, Paul Gevers wrote: > I have requested the cups test in testing with ghostscript from > experimental. I hasn't finished yet, albeit it probably started soon > after I requested it at 2018-08-31 19:20:50 UTC, so this isn't looking > good. Feel free to check in 2:30 hours or so, it should be visible at > the page linked above with the trigger "elbrus ghostscript from > experimental". If that ran for 2:47 and failed it probably timed out > (which you can confirm by looking at the bottom of the test log). It timed out. Additionally, I spotted multiple packages on the ci.d.n that started to time out [1] that seem to be related to printing. I have triggered tests with ghostscript from unstable for them too. They all time out as well (marked as affected by this bug). Paul [1] https://ci.debian.net/status/slow/ signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#907493: ghostscript causes multiple autopkgtests to time out
Processing control commands: > reassign -1 ghostscript 9.22~dfsg-3 Bug #907493 [src:ghostscript, src:cups] ghostscript breaks cups autopkgtest: test times out Bug reassigned from package 'src:ghostscript, src:cups' to 'ghostscript'. No longer marked as found in versions ghostscript/9.22~dfsg-3. Ignoring request to alter fixed versions of bug #907493 to the same values previously set Bug #907493 [ghostscript] ghostscript breaks cups autopkgtest: test times out Marked as found in versions ghostscript/9.22~dfsg-3. > retitle -1 ghostscript causes multiple autopkgtests to time out Bug #907493 [ghostscript] ghostscript breaks cups autopkgtest: test times out Changed Bug title to 'ghostscript causes multiple autopkgtests to time out' from 'ghostscript breaks cups autopkgtest: test times out'. > affects -1 src:cups src:gutenprint src:dymo-cups-drivers Bug #907493 [ghostscript] ghostscript causes multiple autopkgtests to time out Added indication that 907493 affects src:cups, src:gutenprint, and src:dymo-cups-drivers > affects -1 src:epson-inkjet-printer-escpr Bug #907493 [ghostscript] ghostscript causes multiple autopkgtests to time out Added indication that 907493 affects src:epson-inkjet-printer-escpr -- 907493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887666: any update on fixing the javahelper bug ?
Dear all, Any update on getting the javahelper bug fixed ? -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#907799: fai - Does not execute scripts
Source: fai Version: 5.7 Severity: serious fai-do-scripts tries to detect the type of the file, bailing out if it does not know about it, instead of just executing it. It's okay to du that if execution fails with 127 (shell for ENOENT, aka interpreter not found). But it is not okay to do that as primary method. Bastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 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)
Bug#907718: python-dateutil breaks python-vobject autopkgtest
Hi Adrian, On 02-09-18 10:04, Adrian Bunk wrote: >>> This also causes FTBFS, the first two seen are: >>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-icalendar.html >>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-vobject.html >> This was broken by efba12d3 due to >> >> https://github.com/dateutil/dateutil/issues/620 >> >> so we likely want reverse deps to catch up and fix this. > > Adding khal as affected package: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/khal.html Any reason why you don't also create FTBFS bug reports for these reverse dependencies while you're at it (as Guido said this change is here to stay)? They are now not notified that they need to fix anything IIUC. (Merely having one's package being affected by an other bug isn't enough to trigger action in my mind). Those bugs should be blocking this bug, like what we do with other bugs that need versioned Breaks. Paul signature.asc Description: OpenPGP digital signature
Processed: ruby2.5: FTBFS due to openssl 1.1.1: test suite times out
Processing control commands: > block 907015 by -1 Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed 907015 was blocked by: 907079 907518 898804 897643 900159 898802 898807 900157 907528 907135 906981 907215 906997 906955 897652 900152 907427 891665 898803 907216 898801 900982 900158 895959 897658 907049 907351 898805 907339 900156 898800 907028 907118 907031 907022 907278 900154 900160 897651 907219 907033 907055 907168 907491 907340 900161 891625 900153 907015 was not blocking any bugs. Added blocking bug(s) of 907015: 907790 -- 907015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907015 907790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907790: ruby2.5: FTBFS due to openssl 1.1.1: test suite times out
Source: ruby2.5 Version: 2.5.1-5 Severity: serious Tags: ftbfs Control: block 907015 by -1 X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org User: debian...@lists.debian.org Usertags: timeout Dear ruby2.5 maintainers, Recently openssl was updated to upstream version 1.1.1. There have been multiple changes to increase security. As a result, some packages started to time out during autopkgtest and/or building of the package. Your package is one of them and does both: https://ci.debian.net/packages/r/ruby2.5/testing/amd64/ https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby2.5/865947/log.gz https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby2.5.html The CI wiki [1] has an entry about time out: SSL_MODE_AUTO_RETRY is enabled by default. Applications that use blocking I/O in combination with something like select() or poll() will hang. This can be turned off again using SSL_CTX_clear_mode(). Many applications do not properly handle non-application data records, and TLS 1.3 sends more of such records. Setting SSL_MODE_AUTO_RETRY works around the problems in those applications, but can also break some. It's recommended to read the manpages about SSL_read(), SSL_write(), SSL_get_error(), SSL_shutdown(), SSL_CTX_set_mode() and SSL_CTX_set_read_ahead() again. Note: openssl is currently blocked from migration to testing for reverse (build) dependencies to catch up and to detect run time errors, such that the right versioned Breaks can be in place. Blocking the bug that tracks that by this bug. Paul [1] https://wiki.debian.org/ContinuousIntegration/TriagingTips/openssl-1.1.1 signature.asc Description: OpenPGP digital signature
Bug#907718: python-dateutil breaks python-vobject autopkgtest
Control: affects -1 src:khal
On Sat, Sep 01, 2018 at 03:47:58PM +0200, Guido Günther wrote:
>...
> > On Fri, Aug 31, 2018 at 09:41:32PM +0200, Paul Gevers wrote:
> > > Source: python-dateutil, python-vobject
> > > Control: found -1 python-dateutil/2.7.3-1
> > > Control: found -1 python-vobject/0.9.5-2
> > > X-Debbugs-CC: debian...@lists.debian.org
> > > User: debian...@lists.debian.org
> > > Usertags: breaks needs-update
> > >
> > > Dear maintainers,
> > >
> > > With a recent upload of python-dateutil the autopkgtest of
> > > python-vobject started to fail in testing. I copied some of the output
> > > below.
> > >...
> >
> > This also causes FTBFS, the first two seen are:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-icalendar.html
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-vobject.html
> >
> > I strongly suspect that there will also be runtime issues with other
> > packages using python-dateutil currently in stretch and buster, so even
> > in case this is considered a bug in reverse dependencies there will
> > still be Breaks required in python{,3}-dateutil against packages in
> > stretch and buster that got broken (unless it was only a broken test).
>
> This was broken by efba12d3 due to
>
> https://github.com/dateutil/dateutil/issues/620
>
> so we likely want reverse deps to catch up and fix this.
Adding khal as affected package:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/khal.html
> Cheers,
> -- Guido
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Processed: Re: elk: FTBFS in buster/sid (No rule to make target '../src/libelk.la')
Processing control commands: > tags -1 patch Bug #906353 [src:elk] elk: FTBFS in buster/sid (No rule to make target '../src/libelk.la') Added tag(s) patch. -- 906353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#907718: python-dateutil breaks python-vobject autopkgtest
Processing control commands: > affects -1 src:khal Bug #907718 [src:python-dateutil] python-dateutil: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware Added indication that 907718 affects src:khal -- 907718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906353: elk: FTBFS in buster/sid (No rule to make target '../src/libelk.la')
Control: tags -1 patch Dear maintainer, On Fri, 17 Aug 2018 11:19:34 + Santiago Vila wrote: > Dear maintainer: > > I tried to build this package in buster but it failed: > [...]> Making all in src > make[3]: Entering directory '/<>/src' > gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -Wdate-time > -D_FORTIFY_SOURCE=2 -DSCM_DIR="\"/usr/share/elk\"" > -DLIB_DIR="\"/usr/lib/x86_64-linux-gnu/elk\"" -Wpointer-arith -Wcast-align > -Wcast-qual -Wshadow -Wmissing-prototypes -Wnested-externs -Wsign-compare > -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -c -o main.o main.c > make[3]: *** No rule to make target '../src/libelk.la', needed by 'elk'. > Stop. I managed to fix the build simplifying src/Makefile.am: -elk_LDADD = $(top_builddir)/src/libelk.la +elk_LDADD = libelk.la Why this helps is still a mystery to me :) Cheers, Juhani Description: Fix "No rule to make target '../src/libelk.la', needed by 'elk'." Author: Juhani Numminen Bug-Debian: https://bugs.debian.org/906353 Forwarded: no Last-Update: 2018-09-02 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -66,7 +66,7 @@ $(NULL) bin_PROGRAMS = elk -elk_LDADD = $(top_builddir)/src/libelk.la +elk_LDADD = libelk.la elk_SOURCES = main.c install-exec-hook:
