Bug#873765: gnome-tweak-tool: Error on start: GLib-GIO-ERROR
On Wed, 30 Aug 2017 19:34:26 -0400 Jeremy Bicha wrote: > Control: severity -1 serious > > Sorry about this. I wasn't aware that this required gnome-shell >= > 3.24. The good news is that we are working on getting gnome-shell 3.24 > into unstable but it will probably be a few more days. > > Thanks, > Jeremy Bicha > > I can also confirm this issue on Debian Sid.
Bug#877966: marked as done (deb.debian.org 503 Quorum weight not reached)
Your message dated Sun, 08 Oct 2017 07:51:52 +0200 with message-id <87vajq5gqv@err.no> and subject line This has been fixed has caused the Debian Bug report #877966, regarding deb.debian.org 503 Quorum weight not reached 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.) -- 877966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mirrors Severity: grave Err:13 http://deb.debian.org/debian stretch Release 503 Quorum weight not reached [IP: 151.101.0.204 80] Err:14 http://deb.debian.org/debian stretch-updates Release 503 Quorum weight not reached [IP: 151.101.0.204 80] Err:15 http://deb.debian.org/debian stretch-backports Release 503 Quorum weight not reached [IP: 151.101.0.204 80] --- End Message --- --- Begin Message --- Thanks for the report, this has been fixed now, the problem was a mismatch between what hosts the CDN was using as backends and what hosts were taken into account when those hosts health checked themselves. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are--- End Message ---
Bug#877419: Lowering severity
control: severity -1 important Hi, I have pinged ftpmaster to do the removals requested in #877700 to make this bug non-RC. I guess this will happen soon so I set severity important now to avoid that rdepends were kicked from testing. Kind regards Andreas. -- http://fam-tille.de
Processed: Lowering severity
Processing control commands: > severity -1 important Bug #877419 [src:pandas] pandas FTBFS on !x86/ppc64el: test failures Severity set to 'important' from 'serious' -- 877419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to lintian, tagging 877147
Processing commands for cont...@bugs.debian.org: > limit source lintian Limiting to bugs with field 'source' containing at least one of 'lintian' Limit currently set to 'source':'lintian' > tags 877147 + pending Bug #877147 [lintian] lintian: FTBFS on armhf/arm64: dh_shlibdeps: file -e apptype -e ascii -e encoding -e cdf -e compress -e tar debian/binaries-from-other-arch/usr/bin/elfobject returned exit code 1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877966: deb.debian.org 503 Quorum weight not reached
Package: mirrors Severity: grave Err:13 http://deb.debian.org/debian stretch Release 503 Quorum weight not reached [IP: 151.101.0.204 80] Err:14 http://deb.debian.org/debian stretch-updates Release 503 Quorum weight not reached [IP: 151.101.0.204 80] Err:15 http://deb.debian.org/debian stretch-backports Release 503 Quorum weight not reached [IP: 151.101.0.204 80]
Bug#877963: u-boot: FTBFS on armel with gcc-7
Source: u-boot Severity: serious Version: 2017.07+dfsg1-1 Tags: patch X-Debbugs-Cc: debian-...@lists.debian.org Several armel targets FTBFS on armel: https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=armel&ver=2017.09%2Bdfsg1-2&stamp=1507251912&raw=0 The boot log fails on the first (dockstar), but I believe openrd*, sheevaplug and possibly guruplug and/or dreamplug are also affected. I've set the version to 2017.07+dfsg1-1, as it also FTBFS when rebuilding with gcc-7 on armel. Though this obviously doesn't seem like a good long-term solution, I've been able to work around the issue by patching u-boot to use gcc-6 only on armel, see patch below. live well, vagrant diff --git a/debian/control b/debian/control index d4116be54e..3393470c5e 100644 --- a/debian/control +++ b/debian/control @@ -8,6 +8,7 @@ Build-Depends: debhelper (>= 9.20141010), device-tree-compiler, dpkg-dev (>= 1.17.14), + gcc-6 [armel] , gcc-6-arm-linux-gnueabi [armel] , libfdt-dev:native [arm64], libc6:arm64 [arm64] , libc6:armhf [armhf] , diff --git a/debian/patches/allow-setting-gcc b/debian/patches/allow-setting-gcc new file mode 100644 index 00..a0ccd9ca18 --- /dev/null +++ b/debian/patches/allow-setting-gcc @@ -0,0 +1,13 @@ +Index: u-boot/Makefile +=== +--- u-boot.orig/Makefile u-boot/Makefile +@@ -338,7 +338,7 @@ LD = $(CROSS_COMPILE)ld.bfd + else + LD= $(CROSS_COMPILE)ld + endif +-CC= $(CROSS_COMPILE)gcc ++CC= $(CROSS_COMPILE)$(GCC) + CPP = $(CC) -E + AR= $(CROSS_COMPILE)ar + NM= $(CROSS_COMPILE)nm diff --git a/debian/patches/series b/debian/patches/series index 03cf73d313..65fb2b11d6 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -32,3 +32,4 @@ odroid-xu3/877074-u-boot-exynos-Default-environment-for-Odr.patch upstream/rk3399/0003-rockchip-rk3399-spl-remove-hard-coded-addresses-for-.patch upstream/rk3399/0004-rockchip-clk-rk3399-add-clk_enable-function-and-supp.patch +allow-setting-gcc diff --git a/debian/rules b/debian/rules index 4fae806b0c..42b772a2c0 100755 --- a/debian/rules +++ b/debian/rules @@ -11,6 +11,11 @@ export CROSS_COMPILE ?= $(DEB_HOST_GNU_TYPE)- cross_build_tools ?= y endif +export GCC = gcc +ifeq ($(DEB_HOST_ARCH),armel) +export GCC = gcc-6 +endif + # support parallel build using DEB_BUILD_OPTIONS=parallel=N ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) DEB_UBOOT_FLAGS += -j$(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) signature.asc Description: PGP signature
Bug#877962: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua
Package: prosody Version: 0.10~hg745e0a783055-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../prosody_0.10~hg745e0a783055-3_amd64.deb ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of stop. Unpacking prosody (0.10~hg745e0a783055-3) over (0.9.12-2) ... dpkg: error processing archive /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is also in package prosody-modules 0.0~hg20170929.c53cc1ae4788+dfsg-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Errors were encountered while processing: /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb cheers, Andreas prosody-modules=0.0~hg20170929.c53cc1ae4788+dfsg-1_prosody=0.10~hg745e0a783055-3.log.gz Description: application/gzip
Bug#877960: kodi-data,kodi-repository-kodi: both ship usr/share/kodi/addons/repository.xbmc.org/{addon.xml,icon.png}
Package: kodi-data,kodi-repository-kodi Version: 2:17.3+dfsg1-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package kodi-repository-kodi. Preparing to unpack .../kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb ... Unpacking kodi-repository-kodi (2:17.3+dfsg1-3) ... dpkg: error processing archive /var/cache/apt/archives/kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb (--unpack): trying to overwrite '/usr/share/kodi/addons/repository.xbmc.org/addon.xml', which is also in package kodi-data 2:17.3+dfsg1-3 Errors were encountered while processing: /var/cache/apt/archives/kodi-repository-kodi_2%3a17.3+dfsg1-3_all.deb Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/kodi/addons/repository.xbmc.org/addon.xml usr/share/kodi/addons/repository.xbmc.org/icon.png Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html kodi-data=2%17.3+dfsg1-3_kodi-repository-kodi=2%17.3+dfsg1-3.log.gz Description: application/gzip
Bug#853338: marked as done (bossa: ftbfs with GCC-7)
Your message dated Sun, 08 Oct 2017 01:04:04 + with message-id and subject line Bug#853338: fixed in bossa 1.3~20120408-5.1 has caused the Debian Bug report #853338, regarding bossa: ftbfs with GCC-7 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.) -- 853338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bossa Version: 1.3~20120408-5 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The severity of this report may be raised before the buster release. There is no need to fix this issue in time for the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc7-20170126/bossa_1.3~20120408-5_unstable_gcc7.log The last lines of the build log are at the end of this report. To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-7/porting_to.html [...] In file included from /usr/include/c++/7/memory:80:0, from src/Samba.h:25, from src/Command.h:25, from src/Shell.cpp:23: /usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here template class auto_ptr; ^~~~ CPP src/Command.cpp g++ -Wall -MT obj/Command.o -MD -MP -MF obj/Command.d -DVERSION=\"1.3a\" -g -O2 `dpkg-buildflags --get CXXFLAGS` `dpkg-buildflags --get CPPFLAGS` -Isrc/arm-dis -c -o obj/Command.o src/Command.cpp In file included from src/Samba.h:27:0, from src/Command.h:25, from src/Command.cpp:29: src/SerialPort.h:64:18: warning: 'template class std::auto_ptr' is deprecated [-Wdeprecated-declarations] typedef std::auto_ptr Ptr; ^~~~ In file included from /usr/include/c++/7/memory:80:0, from src/Samba.h:25, from src/Command.h:25, from src/Command.cpp:29: /usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here template class auto_ptr; ^~~~ In file included from src/FlashFactory.h:25:0, from src/Command.h:27, from src/Command.cpp:29: src/Flash.h:107:18: warning: 'template class std::auto_ptr' is deprecated [-Wdeprecated-declarations] typedef std::auto_ptr Ptr; ^~~~ In file included from /usr/include/c++/7/memory:80:0, from src/Samba.h:25, from src/Command.h:25, from src/Command.cpp:29: /usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here template class auto_ptr; ^~~~ src/Command.cpp: In member function 'virtual void CommandMwb::invoke(char**, int)': src/Command.cpp:710:26: error: ISO C++ forbids comparison between pointer and integer [-fpermissive] if (input == '\0' || ^~~~ src/Command.cpp: In member function 'virtual void CommandMww::invoke(char**, int)': src/Command.cpp:813:26: error: ISO C++ forbids comparison between pointer and integer [-fpermissive] if (input == '\0' || ^~~~ Makefile:243: recipe for target 'obj/Command.o' failed make[1]: *** [obj/Command.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 debian/rules:13: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 --- End Message --- --- Begin Message --- Source: bossa Source-Version: 1.3~20120408-5.1 We believe that the bug you reported is fixed in the latest version of bossa, 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 fu
Bug#872202: marked as done (hamradio-maintguide: FTBFS with Sphinx 1.6: Needs build-dep on latexmk)
Your message dated Sun, 08 Oct 2017 00:04:06 + with message-id and subject line Bug#872202: fixed in hamradio-maintguide 0.4 has caused the Debian Bug report #872202, regarding hamradio-maintguide: FTBFS with Sphinx 1.6: Needs build-dep on latexmk 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.) -- 872202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hamradio-maintguide Version: 0.3 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.6 Dear maintainer, hamradio-maintguide fails to build with Sphinx 1.6, currently available in experimental: make -C _build/latex all-pdf make[3]: Entering directory '/<>/_build/latex' latexmk -pdf -dvi- -ps- 'DebianHamradio.tex' make[3]: latexmk: Command not found Makefile:33: recipe for target 'DebianHamradio.pdf' failed make[3]: *** [DebianHamradio.pdf] Error 127 Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1]. Adding a build-dependency on latexmk should help. [1]: https://github.com/sphinx-doc/sphinx/pull/3082 -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: hamradio-maintguide Source-Version: 0.4 We believe that the bug you reported is fixed in the latest version of hamradio-maintguide, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iain R. Learmonth (supplier of updated hamradio-maintguide 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, 08 Oct 2017 00:33:34 +0100 Source: hamradio-maintguide Binary: hamradio-maintguide Architecture: source all Version: 0.4 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: Iain R. Learmonth Description: hamradio-maintguide - Debian Hamradio Maintainers Guide Closes: 872202 Changes: hamradio-maintguide (0.4) unstable; urgency=medium . * Add build dependency on latexmk (Closes: #872202) Checksums-Sha1: 57e2e952f40c2ab25a65c591db6570446eba9a92 1473 hamradio-maintguide_0.4.dsc 05203644713c07a384defc7969703d0555ab0d74 13132 hamradio-maintguide_0.4.tar.xz bbc4258b2491bd908f5bee6af1c729df2fa6c640 193238 hamradio-maintguide_0.4_all.deb ee89faed6b67f83d52290099be40f985c89c46df 8908 hamradio-maintguide_0.4_amd64.buildinfo Checksums-Sha256: 65200cbe721372967e7ffee10198c7022ea9c4bda4546c926849069303eb00e4 1473 hamradio-maintguide_0.4.dsc da0dfdeba33226bc5c58329067dbeaa27431166ab89e8a41e030737a938b9bc8 13132 hamradio-maintguide_0.4.tar.xz ca6306daf8da292179e6e61a199e3c26c34d65890f4bdbcfda0137dbfcb9044e 193238 hamradio-maintguide_0.4_all.deb b6483e802a11ae3847d74aa81ef7e6c48b6027d1a10f6a4675b1e841dedbde59 8908 hamradio-maintguide_0.4_amd64.buildinfo Files: d29ac1d98f06f1ce8986505882f6f916 1473 doc optional hamradio-maintguide_0.4.dsc dcdd26e0f871d5009360b8308b854a69 13132 doc optional hamradio-maintguide_0.4.tar.xz c608c225d0732e6208d2988dbf9bbe5b 193238 doc optional hamradio-maintguide_0.4_all.deb 56100393ddff85132d84692e45fef001 8908 doc optional hamradio-maintguide_0.4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEfGEElJRPyB2mSFaW0hedW4oe0BEFAlnZZj8ACgkQ0hedW4oe 0BHABwf/RGp20RYiwHwrbLcHskcIppbnooIFF5eUZLz6rzseRmEDi+gf0skO81FS tajSKRQeXW+owiIk9Sd5umEwVfKWVLvafNPVLfvSzOT855Gg9aaSUL/HLQWmmKMC urHUHFgFpVfIUQtHXEI+HQeEL1HGg07Lpm6Q1zMQZg/Z+WqbAwbAY4Zz7EjPL92e CYUOh3Jw+5wy2ul4g13j6Rh2ARLsnAUVfmKHr6REnNf3z+apZRLIn40l4aGGTD+b +xtNIaaIUVw395/ovSakG76tLbypNvA8xTOJ5Th8bFNsPdOQZ3y/LLkGfcH15ix2 7FZPYotxGPGlO0Bz/gVXsJBWGHJxug== =GMkf -END PGP SIGNATURE End Message ---
Bug#873326: marked as done (sysdig FTBFS with luajit 2.1)
Your message dated Sun, 08 Oct 2017 00:04:17 + with message-id and subject line Bug#873326: fixed in sysdig 0.19.1-1 has caused the Debian Bug report #873326, regarding sysdig FTBFS with luajit 2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 873326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sysdig Version: 0.17.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sysdig.html ... -- Could NOT find Lua51 (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) CMake Error at CMakeLists.txt:117 (message): Couldn't find system LuaJIT or Lua -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: sysdig Source-Version: 0.19.1-1 We believe that the bug you reported is fixed in the latest version of sysdig, 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 873...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Harlan Lieberman-Berg (supplier of updated sysdig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2017 19:45:37 -0400 Source: sysdig Binary: sysdig sysdig-dkms Architecture: source Version: 0.19.1-1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Harlan Lieberman-Berg Closes: 872035 873326 Description: sysdig-dkms - system-level exploration and troubleshooting tool - kernel source sysdig - system-level exploration and troubleshooting tool Changes: sysdig (0.19.1-1) unstable; urgency=medium . * New upstream release. (Closes: #872035) * Apply patch to fix LuaJIT compilation failures. (Closes: #873326) * Bump S-V to 4.1.1; no changes needed. * Switch sysdig-dkms to kernel section. Checksums-Sha1: a65c7b734b3345a1430975fa879393432b8886c1 2377 sysdig_0.19.1-1.dsc 425ea9fab8e831274626a9c9e65f0dfb4f9bc019 742149 sysdig_0.19.1.orig.tar.gz 556e0d04ecb4c3ac25e96f49dd699133006f485a 6824 sysdig_0.19.1-1.debian.tar.xz Checksums-Sha256: 3ce887b50d207f0aeacf2f5e658bb74b5d3d848e103c4af07f3b3b8ae391dadd 2377 sysdig_0.19.1-1.dsc 480d5d8fd7e7373c08008c30bd8e2c7595d5c45d710bf07bd15a522021b560f6 742149 sysdig_0.19.1.orig.tar.gz bc100b9c6e16928373ef0a71850cbf47dedff61ee2f07fac5b6aa2c1753e5ba6 6824 sysdig_0.19.1-1.debian.tar.xz Files: dfb4b36cacdffe98bbaea95496483828 2377 admin optional sysdig_0.19.1-1.dsc 6ad8b4a7d1b0aa10cd62397318117a67 742149 admin optional sysdig_0.19.1.orig.tar.gz 5242eced2c0843f45979aa1c1ee87788 6824 admin optional sysdig_0.19.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKqBAEBCgCUFiEEhiNlIJf/8kpE2Nai6afXk4v2O6UFAlnZaDFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg2 MjM2NTIwOTdGRkYyNEE0NEQ4RDZBMkU5QTdENzkzOEJGNjNCQTUWHGhsaWViZXJt YW5AZGViaWFuLm9yZwAKCRDpp9eTi/Y7pVtGEACO+KrmbslPQQlnckviHCfcLM+I u4oWDmHhKyu8FOVwzBngq5AkWhRRE+QwCaHB09MklaMIevP5BtFHj9FC3t8G18LH yDTow8yqCcwwbGZfG6nFiHkx1s+KHO9MPr3Pm3nolOGC8Jfb1ytW3ZVlJceRT4gb jjZ16e5xzJ7tzIpzYu2wVv4ot8NbwY9VFACknZPyrk0Fp3gQWZJeI1D9cNjRY3gt 8wRuGH4xyvfxmHF/1iVIl3gEKmWXFs6rSpkQsQHScakWGWnAf9LVj3DzRO0JzTC2 FnWn0eXjGe9J7UcK4m3Jy4Rf7h5V7zQUQN2hqyNap19To/sGBKXzBdXy2J5hVZ6Y Na9Z0yGwd9OvAzUU/wmRlA5ie8i6s2og+LtZUgQwefLKpO3DM+iOSV8vvDJx6dGs WqX8ORhZS4fEhhncYRjNZg8Xz7px+OF0p846kjqh6mO/JQgwRMhsElg//kRXGykK D2bXkyo0cCv/QMSpbqCNM1Gy0UMuarqYGiquVtGHP9w/bQFzhNcoeG/M5Hf0wblE zUvq9eb7sr8iytOjAKOOfLpzi1Mu1lXJ/VpAO7eB0BcHvWMmsY95cCd3x6Rt7jqt 7+RCZjgJ9Vw/X5vPU2Bjj79RXf2NiXNWaP2ksXv7ONwypeJZgCX07fERhls1oDSI jSFDzSQsuzFRUVzn5Q== =oNC6 -END PGP SIGNATURE End Message ---
Bug#872035: marked as done (sysdig FTBFS with curl 7.55.0-1)
Your message dated Sun, 08 Oct 2017 00:04:17 + with message-id and subject line Bug#872035: fixed in sysdig 0.19.1-1 has caused the Debian Bug report #872035, regarding sysdig FTBFS with curl 7.55.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 872035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sysdig Version: 0.17.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sysdig.html ... /build/1st/sysdig-0.17.0/userspace/libsinsp/marathon_http.cpp:10:10: fatal error: curl/curlbuild.h: No such file or directory #include "curl/curlbuild.h" ^~ compilation terminated. userspace/libsinsp/CMakeFiles/sinsp.dir/build.make:1049: recipe for target 'userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o' failed make[3]: *** [userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o] Error 1 --- End Message --- --- Begin Message --- Source: sysdig Source-Version: 0.19.1-1 We believe that the bug you reported is fixed in the latest version of sysdig, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Harlan Lieberman-Berg (supplier of updated sysdig package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2017 19:45:37 -0400 Source: sysdig Binary: sysdig sysdig-dkms Architecture: source Version: 0.19.1-1 Distribution: unstable Urgency: medium Maintainer: Evgeni Golov Changed-By: Harlan Lieberman-Berg Closes: 872035 873326 Description: sysdig-dkms - system-level exploration and troubleshooting tool - kernel source sysdig - system-level exploration and troubleshooting tool Changes: sysdig (0.19.1-1) unstable; urgency=medium . * New upstream release. (Closes: #872035) * Apply patch to fix LuaJIT compilation failures. (Closes: #873326) * Bump S-V to 4.1.1; no changes needed. * Switch sysdig-dkms to kernel section. Checksums-Sha1: a65c7b734b3345a1430975fa879393432b8886c1 2377 sysdig_0.19.1-1.dsc 425ea9fab8e831274626a9c9e65f0dfb4f9bc019 742149 sysdig_0.19.1.orig.tar.gz 556e0d04ecb4c3ac25e96f49dd699133006f485a 6824 sysdig_0.19.1-1.debian.tar.xz Checksums-Sha256: 3ce887b50d207f0aeacf2f5e658bb74b5d3d848e103c4af07f3b3b8ae391dadd 2377 sysdig_0.19.1-1.dsc 480d5d8fd7e7373c08008c30bd8e2c7595d5c45d710bf07bd15a522021b560f6 742149 sysdig_0.19.1.orig.tar.gz bc100b9c6e16928373ef0a71850cbf47dedff61ee2f07fac5b6aa2c1753e5ba6 6824 sysdig_0.19.1-1.debian.tar.xz Files: dfb4b36cacdffe98bbaea95496483828 2377 admin optional sysdig_0.19.1-1.dsc 6ad8b4a7d1b0aa10cd62397318117a67 742149 admin optional sysdig_0.19.1.orig.tar.gz 5242eced2c0843f45979aa1c1ee87788 6824 admin optional sysdig_0.19.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKqBAEBCgCUFiEEhiNlIJf/8kpE2Nai6afXk4v2O6UFAlnZaDFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg2 MjM2NTIwOTdGRkYyNEE0NEQ4RDZBMkU5QTdENzkzOEJGNjNCQTUWHGhsaWViZXJt YW5AZGViaWFuLm9yZwAKCRDpp9eTi/Y7pVtGEACO+KrmbslPQQlnckviHCfcLM+I u4oWDmHhKyu8FOVwzBngq5AkWhRRE+QwCaHB09MklaMIevP5BtFHj9FC3t8G18LH yDTow8yqCcwwbGZfG6nFiHkx1s+KHO9MPr3Pm3nolOGC8Jfb1ytW3ZVlJceRT4gb jjZ16e5xzJ7tzIpzYu2wVv4ot8NbwY9VFACknZPyrk0Fp3gQWZJeI1D9cNjRY3gt 8wRuGH4xyvfxmHF/1iVIl3gEKmWXFs6rSpkQsQHScakWGWnAf9LVj3DzRO0JzTC2 FnWn0eXjGe9J7UcK4m3Jy4Rf7h5V7zQUQN2hqyNap19To/sGBKXzBdXy2J5hVZ6Y Na9Z0yGwd9OvAzUU/wmRlA5ie8i6s2og+LtZUgQwefLKpO3DM+iOSV8vvDJx6dGs WqX8ORhZS4fEhhncYRjNZg8Xz7px+OF0p846kjqh6mO/JQgwRMhsElg//kRXGykK D2bXkyo0cCv/QMSpbqCNM1Gy0UMuarqYGiquVtGHP9w/bQFzhNcoeG/M5Hf0wblE zUvq9eb7sr8iytOjAKOOfLpzi1Mu1lXJ/VpAO7eB0BcHvWMmsY95cCd3x6Rt7jqt 7+RCZjgJ9Vw/X5vPU2Bjj79RXf2NiXNWaP2ksXv7ONwypeJZgCX07fERhls1oDSI jSFDzSQsuzFRUVzn5Q== =oNC6 -END PGP SIGNATURE End Message ---
Bug#841556: libcdio: ftbfs with GCC-7
> > /usr/include/cdio/iso9660.h:277:45: error: flexible array member
> > 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
> >char filename[EMPTY_ARRAY_SIZE];
> > ^
> > /usr/include/cdio/iso9660.h:310:20: note: next member 'char
> > iso9660_pvd_s::root_directory_filename' declared here
> >char root_directory_filename; /**< Is '\\0' or root
> > ^~~
> > /usr/include/cdio/iso9660.h:283:8: note: in the definition of 'struct
> > iso9660_pvd_s'
> > struct iso9660_pvd_s {
> > ^
> > /usr/include/cdio/iso9660.h:277:45: error: flexible array member
> > 'iso9660_dir_s::filename' not at end of 'struct iso9660_svd_s'
> >char filename[EMPTY_ARRAY_SIZE];
> > ^
> > /usr/include/cdio/iso9660.h:424:20: note: next member 'char
> > iso9660_svd_s::root_directory_filename' declared here
> >char root_directory_filename; /**< Is '\\0' or root
> > ^~~
> > /usr/include/cdio/iso9660.h:392:8: note: in the definition of 'struct
> > iso9660_svd_s'
> > struct iso9660_svd_s {
> > ^
this seems to be fixed in libcdio 0.92 in experimental, so maybe it's
time to upload that (or current 0.94 even?) to unstable?
Alternatively, 0.83-4.3 seems to build all right with the following,
slightly amended commit from upstream git (soname bump?):
commit 0bdb015d47b95abaa79fc2b83ffacdd63429a992
Author: R. Bernstein
Date: Sat Mar 3 11:38:44 2012 -0500
pbatard empty array changes for iso9660.h. I think the last of the header
patches.
--- a/include/cdio/iso9660.h
+++ b/include/cdio/iso9660.h
@@ -60,7 +60,7 @@
typedef char achar_t; /*! See section 7.4.1 */
typedef char dchar_t; /*! See section 7.4.1 */
-#ifndef EMPTY_ARRAY_SIZE
+#ifndef EMPTY_ARRAY_SIZE
#define EMPTY_ARRAY_SIZE 0
#endif
@@ -273,8 +273,18 @@
the Extent described by this
Directory Record is
recorded. (9.1.9) */
- iso711_t filename_len; /*! number of bytes in filename field */
- char filename[EMPTY_ARRAY_SIZE];
+/*! MSVC compilers cannot handle a zero sized array in the middle
+of a struct, and iso9660_dir_s is reused within iso9660_pvd_s.
+Therefore, instead of defining:
+ iso711_t filename_len;
+ char filename[];
+we leverage the fact that iso711_t and char are the same size
+and use an union. The only gotcha is that the actual string
+payload of filename.str[] starts at 1, not 0. */
+ union {
+iso711_tlen;
+charstr[1];
+ } filename;
} GNUC_PACKED;
/*!
@@ -976,7 +986,7 @@
uint8_t iso9660_get_dir_len(const iso9660_dir_t *p_idr);
-#if FIXME
+#ifdef FIXME
uint8_t iso9660_get_dir_size(const iso9660_dir_t *p_idr);
lsn_t iso9660_get_dir_extent(const iso9660_dir_t *p_idr);
--- a/lib/iso9660/iso9660.c
+++ b/lib/iso9660/iso9660.c
@@ -301,7 +301,7 @@
*/
void
iso9660_set_dtime_with_timezone (const struct tm *p_tm,
- int timezone,
+ int time_zone,
/*out*/ iso9660_dtime_t *p_idr_date)
{
memset (p_idr_date, 0, 7);
@@ -317,7 +317,7 @@
/* The ISO 9660 timezone is in the range -48..+52 and each unit
represents a 15-minute interval. */
- p_idr_date->dt_gmtoff = timezone / 15;
+ p_idr_date->dt_gmtoff = time_zone / 15;
if (p_idr_date->dt_gmtoff < -48 ) {
@@ -337,16 +337,16 @@
void
iso9660_set_dtime (const struct tm *p_tm, /*out*/ iso9660_dtime_t *p_idr_date)
{
- int timezone = 0;
+ int time_zone = 0;
if (p_tm) {
#ifdef HAVE_TM_GMTOFF
/* Convert seconds to minutes */
-timezone = p_tm->tm_gmtoff / 60;
+time_zone = p_tm->tm_gmtoff / 60;
#else
-timezone = (p_tm->tm_isdst > 0) ? -60 : 0;
+time_zone = (p_tm->tm_isdst > 0) ? -60 : 0;
#endif
}
- iso9660_set_dtime_with_timezone (p_tm, timezone, p_idr_date);
+ iso9660_set_dtime_with_timezone (p_tm, time_zone, p_idr_date);
}
/*!
@@ -356,7 +356,7 @@
*/
void
iso9660_set_ltime_with_timezone (const struct tm *p_tm,
- int timezone,
+ int time_zone,
/*out*/ iso9660_ltime_t *pvd_date)
{
char *_pvd_date = (char *) pvd_date;
@@ -373,7 +373,7 @@
0 /* 1/100 secs */ );
/* Set time zone in 15-minute interval encoding. */
- pvd_date->lt_gmtoff -= (timezone / 15);
+ pvd_date->lt_gmtoff -= (time_zone / 15);
if (pvd_date->lt_gmtoff < -48 ) {
cdio_warn ("Converted ISO 9660 timezone %d is less than -48. Adjusted",
@@ -392,16 +392,16 @@
void
iso9660_set_ltime (const struct tm *p_tm, /*out*/ iso9660_ltime_t *pvd_date)
{
- int timezone = 0;
+ i
Bug#873322: bpfc-tools: bpfcc FTBFS with luajit 2.1
Hi,
To make it build I had to:
- set LUAJIT_DIR=/usr/include/luajit-2.1 when invoking dpkg-buildpackage.
As alternative you can add /usr/include/luajit-2.1 in PATH_SUFFIXES in
cmake/FindLuaJIT.cmake
- force using llvm/clang 3.8 in CMakeLists.txt as it does not compile with
llvm-5.0 (I did not try with 6.0):
find_package(LLVM 3.8 REQUIRED CONFIG)
I attached a patch but I am not sure if it will be in the right format as I
have a little experience with quilt and debian BTS.
Regards
diff --git a/debian/patches/fix-luajit-path.diff b/debian/patches/fix-luajit-path.diff
new file mode 100644
index 000..ae3514c
--- /dev/null
+++ b/debian/patches/fix-luajit-path.diff
@@ -0,0 +1,11 @@
+--- a/cmake/FindLuaJIT.cmake
b/cmake/FindLuaJIT.cmake
+@@ -31,7 +31,7 @@
+ FIND_PATH(LUAJIT_INCLUDE_DIR lua.h
+ HINTS
+ $ENV{LUAJIT_DIR}
+- PATH_SUFFIXES include/luajit-2.0 include/luajit2.0 include/luajit include
++ PATH_SUFFIXES include/luajit-2.0 include/luajit2.0 include/luajit include include/luajit-2.1
+ PATHS
+ ~/Library/Frameworks
+ /Library/Frameworks
diff --git a/debian/patches/force-using-clang-3.8.diff b/debian/patches/force-using-clang-3.8.diff
new file mode 100644
index 000..ad971fc
--- /dev/null
+++ b/debian/patches/force-using-clang-3.8.diff
@@ -0,0 +1,11 @@
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -16,7 +16,7 @@
+ if(NOT PYTHON_ONLY)
+ find_package(BISON)
+ find_package(FLEX)
+-find_package(LLVM REQUIRED CONFIG)
++find_package(LLVM 3.8 REQUIRED CONFIG)
+ message(STATUS "Found LLVM: ${LLVM_INCLUDE_DIRS}")
+
+ # clang is linked as a library, but the library path searching is
diff --git a/debian/patches/series b/debian/patches/series
index aa18d63..13bf968 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,5 @@
fix-install-path.patch
fix-uint128-build-failure.patch
disable-massive-cpp-binaries.patch
+fix-luajit-path.diff
+force-using-clang-3.8.diff
Bug#877461: logol: broken symlinks: /usr/share/logol/lib/{activation, drmaa}.jar -> ../../java/*.jar
Hi, On Mon, Oct 02, 2017 at 02:41:16AM +0200, Andreas Beckmann wrote: > >From the attached log (scroll to the bottom...): > > 1m29.3s ERROR: FAIL: Broken symlinks: > /usr/share/logol/lib/drmaa.jar -> ../../java/drmaa.jar > /usr/share/logol/lib/activation.jar -> ../../java/activation.jar > > Is logol missing a dependency on libdrmaa1.0-java? Yes, I've added it in Git[1] > I cannot find activation.jar in the archive at all. True I can not find it as well. Olivier, do you have a clue? Kind regards Andreas. [1] Please note that I moved logol from SVN to Git https://anonscm.debian.org/git/debian-med/logol.git -- http://fam-tille.de
Processed: reassign 877694 to spl-dkms, user debian...@lists.debian.org, usertagging 877910, usertagging 877548 ...
Processing commands for cont...@bugs.debian.org: > reassign 877694 spl-dkms 0.6.5.11-1 Bug #877694 [src:spl-linux] spl-linux: Fails to build with kernel 4.13 Bug reassigned from package 'src:spl-linux' to 'spl-dkms'. Ignoring request to alter found versions of bug #877694 to the same values previously set Ignoring request to alter fixed versions of bug #877694 to the same values previously set Bug #877694 [spl-dkms] spl-linux: Fails to build with kernel 4.13 Marked as found in versions spl-linux/0.6.5.11-1. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 877910 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 877548 piuparts There were no usertags set. Usertags are now: piuparts. > affects 877548 + liblwt-ocaml-dev Bug #877548 [src:lwt] lwt FTBFS: Error: This variant or record definition does not match that of type Unix.open_flag Added indication that 877548 affects liblwt-ocaml-dev > usertags 843315 piuparts Usertags were: piuparts. Usertags are now: piuparts. > affects 843315 + libcore-kernel-ocaml Bug #843315 [janest-core-kernel] FTBFS: libsexplib-camlp4-dev is no longer available Added indication that 843315 affects libcore-kernel-ocaml > usertags 877507 piuparts There were no usertags set. Usertags are now: piuparts. > affects 877507 + libppx-core-ocaml Bug #877507 [src:ppx-core] ppx-core FTBFS: E: Cannot find external tool 'ocamlbuild' Added indication that 877507 affects libppx-core-ocaml > usertags 877496 piuparts There were no usertags set. Usertags are now: piuparts. > thanks Stopping processing here. Please contact me if you need assistance. -- 843315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843315 877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496 877507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877507 877548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877548 877694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877945: dm-writeboost-dkms: module FTBFS for Linux 4.13: error: 'struct bio' has no member named 'bi_error'
Package: dm-writeboost-dkms Version: 2.2.7-1 Severity: serious Justification: fails to build from source Hi, dm-writeboost-dkms fails to build a kernel module for the latest kernel in sid: gcc-6 -Wp,-MD,/var/lib/dkms/dm-writeboost/2.2.7/build/.dm-writeboost-target.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/6/include -I/usr/src/linux-headers-4.13.0-1-common/arch/x86/include -I./arch/x86/include/generated -I/usr/src/linux-headers-4.13.0-1-common/include -I./include -I/usr/src/linux-headers-4.13.0-1-common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I/usr/src/linux-headers-4.13.0-1-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-4.13.0-1-common/include/linux/kconfig.h -I/var/lib/dkms/dm-writeboost/2.2.7/build -I/var/lib/dkms/dm-writeboost/2.2.7/build -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mn o-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -Wno-frame-address -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -DMODULE -DKBUILD_BASENAME='"dm_writeboost_target"' -DKBUILD_MODNAME='"dm_writeboost"' -c -o /var/lib/dkms/dm-writeboost/2.2.7/build/.tmp_dm-wri teboost-target.o /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c: In function 'bio_endio_compat': /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:116:5: error: 'struct bio' has no member named 'bi_error'; did you mean 'bi_iter'? bio->bi_error = error; ^~ /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c: At top level: /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:1946:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .end_io = writeboost_end_io, ^ /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:1946:12: note: (near initialization for 'writeboost_target.end_io') cc1: some warnings being treated as errors /usr/src/linux-headers-4.13.0-1-common/scripts/Makefile.build:307: recipe for target '/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.o' failed make[4]: *** [/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.o] Error 1 Andreas
Bug#871086: extsmail: patch for the FTBFS error
Control: tags 871086 + patch Dear maintainer, The cause for the error is that the package build system defines "-Wno-format", which clashes with the hardening build flags that are exported via dpkg-buildflags. I have attached a patch that fixes this build error by disabling the "format" hardening feature via debian/rules. I'll be looking for a sponsor, feel free to upload a fix yourself or tell me if I shouldn't upload the nmu. Thanks. Regards. -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 diff -Nru extsmail-2.0/debian/changelog extsmail-2.0/debian/changelog --- extsmail-2.0/debian/changelog 2015-05-14 22:55:21.0 +0200 +++ extsmail-2.0/debian/changelog 2017-10-07 20:11:23.0 +0200 @@ -1,3 +1,10 @@ +extsmail (2.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Disable the "format" hardening-feature to fix FTBFS (Closes: #871086) + + -- Andreas Moog Sat, 07 Oct 2017 20:11:23 +0200 + extsmail (2.0-2) unstable; urgency=low * Upload to unstable. signature.asc Description: PGP signature
Processed: extsmail: patch for the FTBFS error
Processing control commands: > tags 871086 + patch Bug #871086 [src:extsmail] extsmail: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security] Added tag(s) patch. -- 871086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 876755 is serious
Processing commands for cont...@bugs.debian.org:
> severity 876755 serious
Bug #876755 {Done: Apollon Oikonomopoulos }
[mongodb-server] mongodb-server: segfault on spidermonkey GC under load
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
876755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#877941: igv: FTBFS: SVGTest.java:111: error: cannot access Localizable
Source: igv Version: 2.3.90+dfsg-1 Severity: serious Tags: sid buster Justification: fails to build from source Hi, igv recently started to FTBFS in sid: compile: [javac] Compiling 893 source files to /build/igv-2.3.90+dfsg/tmp [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6 [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/tools/sort/BAMSorter.java:33: warning: NotImplementedException is internal proprietary API and may be removed in a future release [javac] import sun.reflect.generics.reflectiveObjects.NotImplementedException; [javac] ^ [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/tools/sort/BAMSorter.java:33: warning: NotImplementedException is internal proprietary API and may be removed in a future release [javac] import sun.reflect.generics.reflectiveObjects.NotImplementedException; [javac] ^ [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/tools/sort/BAMSorter.java:33: warning: NotImplementedException is internal proprietary API and may be removed in a future release [javac] import sun.reflect.generics.reflectiveObjects.NotImplementedException; [javac] ^ [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/tools/sort/BAMSorter.java:102: warning: NotImplementedException is internal proprietary API and may be removed in a future release [javac] throw new NotImplementedException(); [javac] ^ [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/ui/svg/SVGTest.java:111: error: cannot access Localizable [javac] DOMImplementation domImpl = GenericDOMImplementation.getDOMImplementation(); [javac] ^ [javac] class file for org.apache.batik.i18n.Localizable not found [javac] /build/igv-2.3.90+dfsg/src/org/broad/igv/ui/svg/SVGTest.java:126: error: cannot access XMLConstants [javac] svgGenerator.stream(out, false); [javac] ^ [javac] class file for org.apache.batik.util.XMLConstants not found [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors [javac] 4 warnings BUILD FAILED /build/igv-2.3.90+dfsg/build.xml:181: Compile failed; see the compiler error output for details. Andreas igv_2.3.90+dfsg-1.log.gz Description: application/gzip
Bug#877210: normaliz FTBFS on i386/armhf: Some error in the normaliz input data detected: Error while reading grading (a 1x2 matrix) !
Dear bunk, thanks for your report. I have just realized that d/watch is obsolete and that normaliz has evolved a lot since the last packaging. I am on my way to package the latest version (3.4.0). So, let see what will happen with this new version. Thanks, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature
Bug#877411: marked as done (flycheck FTBFS and Debci failure with elpa-buttercup 1.9)
Your message dated Sat, 07 Oct 2017 16:20:09 +
with message-id
and subject line Bug#877411: fixed in flycheck 31-1
has caused the Debian Bug report #877411,
regarding flycheck FTBFS and Debci failure with elpa-buttercup 1.9
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.)
--
877411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flycheck
Version: 30-3
Severity: serious
Tags: buster sid
https://ci.debian.net/packages/f/flycheck/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flycheck.html
...
Ran 91 specs,[31m 42 failed[0m, in 3.7 seconds.
dh_elpa_test: buttercup -L . returned exit code 255
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 255
--- End Message ---
--- Begin Message ---
Source: flycheck
Source-Version: 31-1
We believe that the bug you reported is fixed in the latest version of
flycheck, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton (supplier of updated flycheck package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 07 Oct 2017 08:42:58 -0700
Source: flycheck
Binary: elpa-flycheck flycheck-doc
Architecture: all source
Version: 31-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacs addons team
Changed-By: Sean Whitton
Closes: 865910 877411
Description:
elpa-flycheck - modern on-the-fly syntax checking for Emacs
flycheck-doc - modern on-the-fly syntax checking for Emacs - documentation
Changes:
flycheck (31-1) unstable; urgency=medium
.
* New upstream release (Closes: #877411).
- Updates to d/copyright.
* Update dependency dash-el => elpa-dash (Closes: #865910).
Thanks to Mykola Nikishov for reporting the problem.
- Bump dh-elpa build dependency to (>= 1.7).
Ensures that elpa-dash is included in ${elpa:Depends}.
* Bump debhelper build-dep to match compat.
- Drop Lintian override package-needs-versioned-debhelper-build-depends.
* Drop fix-flake8-expected-values.patch
Obsoleted by upstream changes.
* Refresh patches.
* Bump standards version to 4.1.1 (no changes required).
Checksums-Sha1:
8d32c4c23f8aea10e6c3d01b5322aef3120ba845 2342 flycheck_31-1.dsc
cc2328b1d2abba6cb50bbeed86efc7686ec584b9 971736 flycheck_31.orig.tar.xz
11889c6795e6a0391c1fa8f3630e8f5ff26cc963 30668 flycheck_31-1.debian.tar.xz
070f8065049ed8fd0b55dee3789b00ee9fb876c5 330978 elpa-flycheck_31-1_all.deb
eecd644cfc68348f429932d1427fcc37ac88a87e 895588 flycheck-doc_31-1_all.deb
ff85dae71112ef3004a013d085319997607a2601 9122 flycheck_31-1_amd64.buildinfo
Checksums-Sha256:
94a583f77492664d00c81101a26b66157d9f7a842a0e145a469e9a0a5898 2342
flycheck_31-1.dsc
44272b3ddc50296110d4b5ef3c3aa40e00e16efa747c64aaf7dfb95d46cd5665 971736
flycheck_31.orig.tar.xz
c0c1fc77233e766a691433c065726cc13503d34feb2fb47694497b0a01c793b6 30668
flycheck_31-1.debian.tar.xz
f4f7e8bb86f4288915fe2427a846ca700f708c56daf18316128d7f7edbba5757 330978
elpa-flycheck_31-1_all.deb
65cf5306619f9ee7be1d68f8fb123e0feb3b6fc0a74ab8850dd71e48f32bb0d2 895588
flycheck-doc_31-1_all.deb
d0f76de3787dbb038611d3bf4362b1a038f603d4341d84c85fecdc27cadf995c 9122
flycheck_31-1_amd64.buildinfo
Files:
8f6ee2ea5dbd9902e0ce0ef3eab7d3de 2342 lisp optional flycheck_31-1.dsc
4e68d9c8b928ef68ca153d6f8a910928 971736 lisp optional flycheck_31.orig.tar.xz
7548a2b3a86f3bfe5d878ae2a76692c8 30668 lisp optional
flycheck_31-1.debian.tar.xz
a152e70f8e7d5d572d969859ee531f31 330978 lisp optional
elpa-flycheck_31-1_all.deb
11cedbe314700012e95fe86c0d9eed3b 895588 doc optional flycheck-doc_31-1_all.deb
2ac1a8bc63eda228691b067406165286 9122 lisp optional
flycheck_31-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlnY+gMACgkQaVt65L8G
YkCvdA/+KayVL1/gkY4YwwqKicTNno+6m3AON0FGT5lEiu3xL12njM/0mqAWi75K
9fDIyu72X6ZUgVlVw0MEmb6yG2ruXn+tHu8ZvtUwJ7VC06uvHEexdfN2Kc73WnVu
UEqGzu2SgBkCj4mhA64I7XDgvVVfX9j8Y8CIL9dZm3r3p7leEkE6XfPI+pINLXA/
mJ17VLjiYcSj+u1iQDF95iwClSNEi1
Bug#877939: FTBFS: t/06-sru.t
Package: libcatmandu-mab2-perl
Version: 0.14-1
Severity: serious
Tags: buster sid
Justification: fails to build from source (but built successfully in the past)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
libcatmandu-mab2-perl doesn't build any more, presumably due to
changes in some libcatmandu-* dependencies.
Entity: line 1: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xF4 0x7F 0x00 0x00
can('each')
ok 3
Dubious, test returned 2 (wstat 512, 0x200)
All 3 subtests passed
t/07-mab-each.t
ok 1 - use Catmandu::Fix::Bind::mab_each;
ok 2 - require Catmandu::Fix::Bind::mab_each;
ok 3 - created a MAB2 record
ok 4 - created is_ger tag
ok 5 - fields 542 deleted
1..5
ok
t/author-pod-syntax.t .. skipped: these tests are for testing by the author
Test Summary Report
- ---
t/06-sru.t (Wstat: 512 Tests: 3 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output
Files=9, Tests=61, 2 wallclock secs ( 0.04 usr 0.02 sys + 2.09 cusr 0.15
csys = 2.30 CPU)
Result: FAIL
First seen on ci.debian.net:
https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libcatmandu-mab2-perl/20171006_154226/log.gz
t/06-sru.t ...
ok 1 - An object of class 'Catmandu::Importer::SRU' isa
'Catmandu::Importer::SRU'
ok 2 - Catmandu::Importer::SRU->can('each')
ok 3
Entity: line 1: parser error : error parsing attribute name
Bug#868773: khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address')
Hi,
we (the khal developers) finally managed to reproduce this bug with the
help of docker, where /dev/tty does not exist. I would assume that the
environment where Debian runs these tests suffers from the very same
issue (can someone confirm this?). As these tests test reading from
stdin, I would advise you to skip those tests for now, as their failing
does not indicate a bug in khal, but a peculiarity in Debian's test
system.
Best regards,
Christian Geier
Quoting Guido Günther (2017-08-24 18:55:50)
> Hi,
> On Tue, Jul 18, 2017 at 03:41:33PM +0300, Adrian Bunk wrote:
> > Source: khal
> > Version: 1:0.9.6-1
> > Severity: serious
> >
> > https://buildd.debian.org/status/fetch.php?pkg=khal&arch=all&ver=1:0.9.6-1&stamp=1500381224&raw=0
> >
> > ...
> > === FAILURES
> > ===
> > test_import_from_stdin
> >
> >
> > runner =
> >
> > def test_import_from_stdin(runner):
> > ics_data = 'This is some really fake icalendar data'
> >
> > with mock.patch('khal.controllers.import_ics') as mocked_import:
> > runner = runner()
> > result = runner.invoke(main_khal, ['import'], input=ics_data)
> >
> > > assert not result.exception
> > E AssertionError: assert not OSError(6, 'No such device or address')
> > E+ where OSError(6, 'No such device or address') = > OSError(6, 'No such device or address')>.exception
> >
> > tests/cli_test.py:505: AssertionError
> > test_printics_read_from_stdin
> > _
> >
> > runner =
> >
> > def test_printics_read_from_stdin(runner):
> > runner = runner(command='printics')
> > result = runner.invoke(main_khal, ['printics'],
> > input=_get_text('cal_d'))
> > > assert not result.exception
> > E AssertionError: assert not OSError(6, 'No such device or address')
> > E+ where OSError(6, 'No such device or address') = > OSError(6, 'No such device or address')>.exception
> >
> > tests/cli_test.py:683: AssertionError
> > == 2 failed, 261 passed, 7 skipped, 3 xfailed in 9.52 seconds
> > ==
> > E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
> > /<>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
> > dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5
> > returned exit code 13
> > debian/rules:26: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 25
>
> Any chance this gets fixed? It would be great to have a recent khal in
> unstable/testing.
> -- Guido
>
Bug#877720: Pending fixes for bugs in the libdbd-firebird-perl package
tag 877720 + pending thanks Some bugs in the libdbd-firebird-perl package are closed in revision 60d59ec5ea61c29f0e8a627d2f6099dec497ad9b in branch ' stretch' by Damyan Ivanov The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libdbd-firebird-perl.git/commit/?id=60d59ec Commit message: add upstream patch fixing fetching of decimal(x,y) values between -1 and 0 Closes: #877720
Processed: Pending fixes for bugs in the libdbd-firebird-perl package
Processing commands for cont...@bugs.debian.org:
> tag 877720 + pending
Bug #877720 {Done: Damyan Ivanov } [libdbd-firebird-perl]
libdbd-firebird-perl: bad conversion of numerics between -1 and 0
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
877720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#876685: marked as done (mssh FTBFS with libvte-2.91-dev 0.50.0-1)
Your message dated Sat, 07 Oct 2017 15:49:32 + with message-id and subject line Bug#876685: fixed in mssh 2.2-2.1 has caused the Debian Bug report #876685, regarding mssh FTBFS with libvte-2.91-dev 0.50.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 876685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mssh Version: 2.2-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mssh.html ... mssh-terminal.c: In function 'mssh_terminal_start_session': mssh-terminal.c:70:5: error: 'vte_terminal_spawn_sync' is deprecated [-Werror=deprecated-declarations] vte_terminal_spawn_sync(VTE_TERMINAL(terminal), ^~~ compilation terminated due to -Wfatal-errors. cc1: all warnings being treated as errors Makefile:378: recipe for target 'mssh-terminal.o' failed make[3]: *** [mssh-terminal.o] Error 1 --- End Message --- --- Begin Message --- Source: mssh Source-Version: 2.2-2.1 We believe that the bug you reported is fixed in the latest version of mssh, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated mssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 02 Oct 2017 14:53:23 +0200 Source: mssh Binary: mssh Architecture: source amd64 Version: 2.2-2.1 Distribution: unstable Urgency: medium Maintainer: Hector Garcia Changed-By: Axel Beckert Description: mssh - tool to administrate multiple servers at once Closes: 876685 Changes: mssh (2.2-2.1) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS due to deprecated functions by replacing the call to vte_terminal_spawn_sync() with a call to vte_terminal_spawn_async(). (Closes: #876685) Checksums-Sha1: a3dc6ad7c07e2f2988c5ccdd1faa054725dbb6c4 1871 mssh_2.2-2.1.dsc 116ade2c9a71726cbd0510ff69e827dc241227e7 5256 mssh_2.2-2.1.debian.tar.xz 31cceefcec36c68c0fe1b1291c35f84a9d2c8c2f 77520 mssh-dbgsym_2.2-2.1_amd64.deb d268e5e273ec11370a76053f4c6b87c2b1fa034a 15429 mssh_2.2-2.1_amd64.buildinfo 7ddf188b950ca17c07cf59c11fea7790c0ac4f76 24600 mssh_2.2-2.1_amd64.deb Checksums-Sha256: 73aa2c3cfcdf33dd93f5f4ef3661bf985a9a9893ec2306ea2da2637bfe15240d 1871 mssh_2.2-2.1.dsc 929784ccb11ade024a4336fe3d4a42da844e6de4995adb6e3e427bfa56edf56b 5256 mssh_2.2-2.1.debian.tar.xz 9ac3e9ca02fbd37cc305540cc796b2d3e70807dc061dec3d4aa103d24931af76 77520 mssh-dbgsym_2.2-2.1_amd64.deb 1cb92d4ae98d57f059b29bd3698026c8b1c910c5d6d0054580147becb2992d53 15429 mssh_2.2-2.1_amd64.buildinfo 9ab2cc376acceaf0eb256e282e38ca58cdc142da4af0feaf23f19610f9c81005 24600 mssh_2.2-2.1_amd64.deb Files: c63dbbe5e11efa5a5a628cf7892ee310 1871 admin optional mssh_2.2-2.1.dsc 428d9869daca3a960ee81a74511feaad 5256 admin optional mssh_2.2-2.1.debian.tar.xz 5ab5e908f548be33d49b263aecb073f5 77520 debug optional mssh-dbgsym_2.2-2.1_amd64.deb e7b4057d2a489db761a75e5d356c5c70 15429 admin optional mssh_2.2-2.1_amd64.buildinfo d7334013f0b23a28c36572816322080d 24600 admin optional mssh_2.2-2.1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAlnSVywACgkQa+Zjx1o1 yXX+Dw//WKnuGhuPWexD2bj8mBAk30AlaOWloJXY6xghgr7tInCsBWkIMhK3HMNB JqkK1qCKsc+XbddRO0bQFdmrr0xj5fl4H8yp0uywLIvILKDEUR+SdBtOJfHrW6wh oe526ehx8IOFP8AKwIMCdJl2S9aw5TH6BWn/CQMowZA9fOtEYEbZQ0XjpweXHeb+ a/AeWBwbps3Ig+StT2Gpiq/3xSIpIj86s38iJuhBx1YfWROO0XgOXO+8PBky44wb 3MlWAv+f/xfH7/1R3mIGk9tP1EizK7TtwUpNcG6aSsJdlzI5a/pxwsqQizeGxqL+ nnHQZOKRZyOVg7k+UHh3L5G/3qK+lgPmUcZUh11yIp3TOq1eCRL9AweJ9FJPChPu UUEGc2m4r5mNPk3upkRyJ6+HGGOblIZgc9MrhWplASUUXguFURYGlqVNyaZY8moV TBp/1TzHS7GYyWOfSx9GU3Yqozsb578Rckc2HTMdaiH1Fp8DdvTtGbgKuG1JpVOd ggarLWD+WS/S/WnFRUc35Uguyb/qP5Jmer3K8lZnPaRk9NIWuJW9eDbfDY5/guI8 SgHkXElaOxJKT09WUUTkMJ9opGXepefuvTClaeiwvh9YBrqUDIrttLFMpDI1AJqE 5W5lqdIne+aXHMSQcx4D2ZpxgTbMC/+yocspoOYyAczLBEBVy94= =PFtM -END PGP SIGNATURE End Message ---
Bug#785565: [Ns-developers] State of ns3 in the Debian distribution
Hi, Just stating along the same lines as Tom did: NetAnim has been compatible with Qt5 for a few versions now. But many users had Qt4 and were just beginning to transition to Qt5 and our documentation for NetAnim has not kept pace. However, in the coming days, we will remove references to Qt4 in our documentation after testing out the Qt5 installation for various distributions. Thanks John On Sat, Oct 7, 2017 at 2:58 AM, Martin Quinson wrote: > Hello, > > Please do not applogize, there is nothing to be ashamed for. Real life > often restrain us from contributing to Debian and others... That's life. > Thank you for all you did in the past, and what you will manage to do > in the future. That would be really great if you could do an upload > without the python-pygoocanvas dependency, please. > > Thanks in advance, Mt. > > On Sat, Oct 07, 2017 at 04:28:59PM +0800, YunQiang Su wrote: > > Sorry for everyone. > > I didn't take care of ns3 for years. > > > > I will update it in few days. > > > > On Thu, Oct 5, 2017 at 3:54 AM, Martin Quinson > > wrote: > > > Hello Tom, thanks for your reply. > > > > > > On Wed, Oct 04, 2017 at 06:08:01PM +, Tom Henderson wrote: > > >> Hi Martin, responses inline below. > > >> > > >> On 10/04/2017 05:26 AM, Martin Quinson wrote: > > >> > Hello dear developers, > > >> > > > >> > Also, if you have an easy way to drop these dependencies (by > disabling > > >> > them at build time), that could solve the issue on our side. I > know I > > >> > should RTFM for that, but I fail to find the time, and I would > > >> > appreciate this help in the package maintainance, please. The > current > > >> > build receipe is here (that's a makefile): > > >> > http://sources.debian.net/src/ns3/3.26%2Bdfsg-1/debian/rules/ > > >> There isn't an ns-3 build dependency on netanim. The pyviz > visualizer is > > >> automatically left out of the configuration if the prerequisites are > not > > >> found by Waf. Is this sufficient (if we don't resolve these package > > >> dependencies in time)? > > > > > > Ok, then I will rebuild the package without that dependency, upload > > > it, and it should do the trick for now, I guess. I'll keep you posted. > > > > > >> We are about to make a new ns-3 release (3.27). We also noticed that > the > > >> netanim package in Debian stretch is very old (3.100+ while we are > now at > > >> 3.108). Can we work towards replacing the old versions with the new > > >> versions in the current release of Debian, or must we wait until the > next > > >> Debian release? > > > > > > There is a plenty of time before the next official Debian release > > > (maybe one year and half). So we can definitely work something out for > > > Debian. Ubuntu regularly picks the packages in the Debian rolling > > > release as a basis for their own releases, but I'm unaware of their > > > schedule. I'd say that March 2018 is the target for the next LTS > > > release of Ubuntu. > > > > > > The problem is that I have personnally I don't have any personal > > > interest in netanim myself, and absolutely no time to devote to that > > > task. If you can come up with a patch against the packaging scripts > > > that refresh it, I can certainly mentor the package upload. > > > > > > Thanks, Mt. > > > > > > -- > > > It's so easy to laugh, it's so easy to hate, > > > it takes strength to be gentle and kind. -- Morrissey, I Know It's > Over. > > > > > > > > -- > > YunQiang Su > > -- > alvin: mais ça, au moins dans ma tête, c'est à peu près clair > frs69wq: bah t'enverra ta tête aux relecteurs alors... >
Bug#876654: marked as done (prosody: incompatible lua-sec version as dependency of prosody in stable)
Your message dated Sat, 7 Oct 2017 15:37:18 +0200 with message-id <7090c370-0e98-8e4d-3960-4413974b7...@debian.org> and subject line Re: prosody: incompatible lua-sec version as dependency of prosody in stable has caused the Debian Bug report #876654, regarding prosody: incompatible lua-sec version as dependency of prosody in stable 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.) -- 876654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prosody Version: 0.9.12-2 Severity: grave Justification: renders package unusable Dear Maintainer, I've installed prosody on a nearly new installed debian strech system. After installation I noticed s2s connections issues with some of my jabber/xmpp contacts as the server was't able to connect to their servers. It reported for example: Out of connection options, can't connect to jabber.ccc-mannheim.de Debug log could be found here: https://paste.ffrn.de/?9702bb47d8bebc03#RSO1WEP787I9p1n0+U0WsFqizvxMprPCl2n4QjggOSw= On the remote server we could see in the logs that my prosody instance couldn't handle any of the ssl ciphers the remote server offers although the openssl version is supporting this ciphers and I can establish a working connection directly with openssl. It seems that this bug occures becaus the package lua5.1-sec that is a dependency of prosody resolves to the lua-sec package with version 0.6-3 in debian stretch. But lua-sec with version 0.6 isn't supported by prosody 0.9.x. See: https://prosody.im/doc/depends It seems this issue makes prosody mostly unusable for encrypted connections. -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-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) Versions of packages prosody depends on: ii adduser 3.115 ii libc6 2.24-11+deb9u1 ii libidn111.33-1 ii libssl1.1 1.1.0f-3 ii lsb-base9.20161125 ii lua-expat [lua5.1-expat]1.3.0-4 ii lua-filesystem [lua5.1-filesystem] 1.6.3-1 ii lua-sec [lua5.1-sec]0.6-3 ii lua-socket [lua5.1-socket] 3.0~rc1+git+ac3201d-3 ii lua5.1 5.1.5-8.1+b2 ii ssl-cert1.0.39 Versions of packages prosody recommends: ii lua-event [lua5.1-event] 0.4.3-2 Versions of packages prosody suggests: pn lua-dbi-mysql pn lua-dbi-postgresql pn lua-dbi-sqlite3 pn lua-zlib -- Configuration Files: /etc/prosody/conf.avail/example.com.cfg.lua /etc/prosody/conf.avail/localhost.cfg.lua /etc/prosody/prosody.cfg.lua pgpJmz6ZXUo7w.pgp Description: Digitale Signatur von OpenPGP --- End Message --- --- Begin Message --- Hi Leah, On 06.10.2017 22:36, Leah Oswald wrote: > Hey Felix, > > thanks for your reply. > > On Fri, 6 Oct 2017 22:11:15 +0200 Felix Geyer wrote: >> I don't think this analysis is correct. > > I've checked your suggestions and it seems to solve the problem to set > the curve manually to prime256v1. The current default therefor ins't > that great but no issue to discuss here. So I think we could close > this report. > > Thanks and kind regards, Thanks for checking, closing the bug accordingly. Felix--- End Message ---
Bug#876768: Re: ruby-pygments.rb: fails to run if RLIMIT_NOFILE is very high
Control: block 877043 by -1 Hi, On Mon, 2017-09-25 at 17:44 +0100, James Cowgill wrote: > weechat recently FTBFS due to asciidoctor dying: > https://buildd.debian.org/status/fetch.php?pkg=weechat&arch=mips64el&; > ver=1.9.1-1&stamp=1506204287&raw=0 > > This happens because: > - The RLIMIT_NOFILE hard limit is set to a large value (eg 1048576). > - On startup, ruby-pygments's mentos.py attempts to close all files. > - Since RLIMIT_NOFILE is large, it will attempt to close 1 million > file > descriptors. > - The mips64el buildds are not powerful enough to complete this in > the > timeout time set in popen.rb (default 8 seconds). > - The pygments call fails, returns nil, and causes asciidoctor to > crash. This also happens on several architectures in stretch, affecting the recent update to weechat there, which unfortunately didn't make it in to today's point release as a result. I'd therefore like to get this fixed in stretch. Would you like to handle that yourself? Regards, Adam
Processed: Bug#876768: Re: ruby-pygments.rb: fails to run if RLIMIT_NOFILE is very high
Processing control commands: > block 877043 by -1 Bug #877043 [release.debian.org] stretch-pu: package weechat/1.6-1+deb9u2 877043 was not blocked by any bugs. 877043 was not blocking any bugs. Added blocking bug(s) of 877043: 876768 -- 876768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876768 877043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#876328: marked as done (asterisk: CVE-2017-14603: RTP/RTCP information leak (AST-2017-008))
Your message dated Sat, 07 Oct 2017 11:47:08 + with message-id and subject line Bug#876328: fixed in asterisk 1:13.14.1~dfsg-2+deb9u2 has caused the Debian Bug report #876328, regarding asterisk: CVE-2017-14603: RTP/RTCP information leak (AST-2017-008) 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.) -- 876328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asterisk Version: 1:13.17.1~dfsg-1 Severity: grave Tags: patch security upstream Hi, the following vulnerability was published for asterisk. CVE-2017-14603[0]: followup-to AST-2017-005: RTP/RTCP information leak If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-14603 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14603 [1] http://downloads.asterisk.org/pub/security/AST-2017-008.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: asterisk Source-Version: 1:13.14.1~dfsg-2+deb9u2 We believe that the bug you reported is fixed in the latest version of asterisk, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated asterisk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Sep 2017 21:26:19 +0200 Source: asterisk Binary: asterisk asterisk-modules asterisk-dahdi asterisk-vpb asterisk-voicemail asterisk-voicemail-imapstorage asterisk-voicemail-odbcstorage asterisk-ooh323 asterisk-mp3 asterisk-mysql asterisk-mobile asterisk-doc asterisk-dev asterisk-config Architecture: source Version: 1:13.14.1~dfsg-2+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian VoIP Team Changed-By: Bernhard Schmidt Description: asterisk - Open Source Private Branch Exchange (PBX) asterisk-config - Configuration files for Asterisk asterisk-dahdi - DAHDI devices support for the Asterisk PBX asterisk-dev - Development files for Asterisk asterisk-doc - Source code documentation for Asterisk asterisk-mobile - Bluetooth phone support for the Asterisk PBX asterisk-modules - loadable modules for the Asterisk PBX asterisk-mp3 - MP3 playback support for the Asterisk PBX asterisk-mysql - MySQL database protocol support for the Asterisk PBX asterisk-ooh323 - H.323 protocol support for the Asterisk PBX - ooH323c asterisk-voicemail - simple voicemail support for the Asterisk PBX asterisk-voicemail-imapstorage - IMAP voicemail storage support for the Asterisk PBX asterisk-voicemail-odbcstorage - ODBC voicemail storage support for the Asterisk PBX asterisk-vpb - VoiceTronix devices support for the Asterisk PBX Closes: 875450 876328 Changes: asterisk (1:13.14.1~dfsg-2+deb9u2) stretch-security; urgency=high . * CVE-2017-14603 / AST-2017-008 This is a follow-up for AST-2017-005: RTP/RTCP information leak improving robustness of the security fix and fixing a regression with re-INVITEs (Closes: #876328) * Fix one-way audio with chan_sip when transcoding (Closes: #875450) Checksums-Sha1: 2977c66a23be109bc4fbe53e5b85fc46638f63d5 4133 asterisk_13.14.1~dfsg-2+deb9u2.dsc 3970e2be900e02197c18a09a4e2b3590de5c9a5e 142904 asterisk_13.14.1~dfsg-2+deb9u2.debian.tar.xz 35a01eb8ebbe0158edae6e99bdb8af87e6437aa1 26743 asterisk_13.14.1~dfsg-2+deb9u2_amd64.buildinfo Checksums-Sha256: 2e507bdb0d01d9f6d4995aca883f93397c2109a0640e8e74d46fe510c7f0d091 4133 asterisk_13.14.1~dfsg-2+deb9u2.dsc fab80768a606e74b95c4ff4023b9374aebf3558f266c7df46627baacc68e51d3 142904 asterisk_13.14.1~dfsg-2+deb9u2.debian.tar.xz 4a62a738b59acf852d56826a1595963800cc01fe70ddad0656a41bca81ee1929 26743 asterisk_13.14.1~dfsg-2+deb9u2_amd64.buildinfo Files: 94f072e4715994f227382b8d5ad82ddd 4133 comm optional asterisk_13.14.1~dfsg-2+deb9u2.dsc 929b8e75c065f52baa01cb276fb37e20 142904 comm optional asterisk_13.14.1~dfsg-2+deb9u2.debian.tar.
Bug#864219: marked as done (qemu: CVE-2017-9375: usb: xhci infinite recursive call via xhci_kick_ep)
Your message dated Sat, 07 Oct 2017 11:47:42 + with message-id and subject line Bug#864219: fixed in qemu 1:2.8+dfsg-6+deb9u3 has caused the Debian Bug report #864219, regarding qemu: CVE-2017-9375: usb: xhci infinite recursive call via xhci_kick_ep 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.) -- 864219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qemu Version: 1:2.8+dfsg-6 Severity: normal Tags: patch security upstream fixed-upstream Hi, the following vulnerability was published for qemu. CVE-2017-9375[0]: usb: xhci infinite recursive call via xhci_kick_ep If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-9375 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9375 [1] http://www.openwall.com/lists/oss-security/2017/06/05/2 [2] http://git.qemu.org/?p=qemu.git;a=commitdiff;h=96d87bdda3919bb16f754b3d3fd1227e1f38f13c Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: qemu Source-Version: 1:2.8+dfsg-6+deb9u3 We believe that the bug you reported is fixed in the latest version of qemu, 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 864...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated qemu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 02 Oct 2017 16:11:47 +0300 Source: qemu Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm Architecture: source Version: 1:2.8+dfsg-6+deb9u3 Distribution: stretch-security Urgency: high Maintainer: Debian QEMU Team Changed-By: Michael Tokarev Description: qemu - fast processor emulator qemu-block-extra - extra block backend modules for qemu-system and qemu-utils qemu-guest-agent - Guest-side qemu-system agent qemu-kvm - QEMU Full virtualization on x86 hardware qemu-system - QEMU full system emulation binaries qemu-system-arm - QEMU full system emulation binaries (arm) qemu-system-common - QEMU full system emulation binaries (common files) qemu-system-mips - QEMU full system emulation binaries (mips) qemu-system-misc - QEMU full system emulation binaries (miscellaneous) qemu-system-ppc - QEMU full system emulation binaries (ppc) qemu-system-sparc - QEMU full system emulation binaries (sparc) qemu-system-x86 - QEMU full system emulation binaries (x86) qemu-user - QEMU user mode emulation binaries qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user qemu-user-static - QEMU user mode emulation binaries (static version) qemu-utils - QEMU utilities Closes: 864219 869945 871648 871702 872257 873849 873851 873875 874606 Changes: qemu (1:2.8+dfsg-6+deb9u3) stretch-security; urgency=high . * xhci-dont-kick-in-xhci_submit-and-xhci_fire_ctl_transfer.patch This is a pre-required patch for the next patch to work right. Closes: #869945 * xhci-guard-xhci_kick_epctx-against-recursive-calls-CVE-2017-9375.patch After applying previous patch, this one can be applied again Closes: #864219, CVE-2017-9375 * ide-do-not-flush-empty-CDROM-drives-CVE-2017-12809.patch Closes: #873849, CVE-2017-12809 * vga-stop-passing-pointers-to-vga_draw_line-functions-CVE-2017-13672.patch Closes: #873851, CVE-2017-13672 * multiboot-validate-multiboot-header-address-values-CVE-2017-14167.patch Closes: #874606, CVE-2017-14167 * slirp-fix-clearing-ifq_so-from-pending-packets-CVE-2017-13711.patch Closes: #873875, CVE-2017-13711 * exec-add-lock-parameter-to-qemu_ram_ptr_length.patch upstream patch fixing memory leak after exec-use-qemu_ram_ptr_length-to-access-guest-ram-CVE-2017-11334.patch Closes: #871648, #871702, #872257 C
Bug#877927: mwc: Fails to start with No module named 'mwc-config'
Package: mwc Version: 2.0.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, A little mistake makes mwc fail to find the config module. Please, consider the following patch: --- mwc 2017-10-01 20:21:11.0 +0200 +++ mwc.new 2017-10-07 12:47:23.830697699 +0200 @@ -198,7 +198,7 @@ if __name__ == "__main__": -configMod = 'config' +configMod = config dryrun = None try: Best Regards, -- Traceback Traceback (most recent call last): File "/usr/bin/mwc", line 218, in config = importlib.import_module(configMod) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 985, in _gcd_import File "", line 968, in _find_and_load File "", line 955, in _find_and_load_unlocked ImportError: No module named 'mwc-config'
Bug#877925: bpfcc-tools: Missing kernel dependency
Control: tag -1 +pending Control: severity -1 normal I'm lowering the severity as this will be part of next upload. On Sat, 2017-10-07 at 12:59 +0200, Damien R. wrote: > this package does JIT compilation and it fails when kernel headers > are not installed. > Possible fix: > add a dependency to kernel headers Thank you for the bug report. I've fixed it in the dev repo and it'll be part of the next upload, after I fix the other RC bug, 873322. If you have some time and can assist on the mentioned bug, that'd be appreciated. Thanks, Ritesh -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#877925: bpfcc-tools: Missing kernel dependency
Processing control commands: > tag -1 +pending Bug #877925 [bpfcc-tools] bpfcc-tools: Missing kernel dependency Added tag(s) pending. > severity -1 normal Bug #877925 [bpfcc-tools] bpfcc-tools: Missing kernel dependency Severity set to 'normal' from 'grave' -- 877925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877015: Closing #877015
Hi, fizmo has been migrated from a single package (which is the one that this bug is filed against and which now fails to build) to frontend-specific packaging, so there are now packages like "fizmo-ncursesw" and "fizmo-console" which provide a virtual fizmo package. Thus it actually helps when the old version 0.7.10 package is dropped from testing as it should be automatically replaced by the new, 0.8 version packages. Best regards, Christoph.
Bug#877907: marked as done (music ftbfs on all archs except for amd64)
Your message dated Sat, 07 Oct 2017 11:05:20 + with message-id and subject line Bug#877907: fixed in music 1.0.7-3 has caused the Debian Bug report #877907, regarding music ftbfs on all archs except for amd64 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.) -- 877907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:music Version: 1.0.7-1.3 Severity: serious Tags: sid buster see https://buildd.debian.org/status/package.php?p=music make[2]: Leaving directory '/<>' ( cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu; chrpath -d libmusic.so libmusic-c.so ) /bin/sh: 1: cd: can't cd to /<>/debian/tmp/usr/lib/x86_64-linux-gnu open: No such file or directory elf_open: Invalid argument debian/rules:10: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' debian/rules:7: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 2 --- End Message --- --- Begin Message --- Source: music Source-Version: 1.0.7-3 We believe that the bug you reported is fixed in the latest version of music, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mikael Djurfeldt (supplier of updated music package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 07 Oct 2017 12:48:54 +0200 Source: music Binary: libmusic-dev libmusic1v5 music-bin music-doc Architecture: source amd64 all Version: 1.0.7-3 Distribution: unstable Urgency: high Maintainer: Mikael Djurfeldt Changed-By: Mikael Djurfeldt Description: libmusic-dev - Multi-Simulation Coordinator for MPI -- Development files libmusic1v5 - Multi-Simulation Coordinator for MPI -- Runtime library music-bin - Multi-Simulation Coordinator for MPI -- Utilities music-doc - Multi-Simulation Coordinator for MPI -- Manual Closes: 877907 Changes: music (1.0.7-3) unstable; urgency=high . * Fix FTBFS on non-amd64 archs. (Closes: #877907) Checksums-Sha1: 56b443a184fbb6686402188f2afb9e3beaad3d9b 1979 music_1.0.7-3.dsc b62fcba456e1d5d0c5469713b0d2cc44a7572453 26108 music_1.0.7-3.debian.tar.xz b977d2ed547c9c80840c7da93ab1b21fd0140022 252584 libmusic-dev_1.0.7-3_amd64.deb 2319b6586bf3d4328511340c3d854ba1da284d3a 2093612 libmusic1v5-dbgsym_1.0.7-3_amd64.deb dfe4036e0acf69958dc012866c74a6ad9597e687 131876 libmusic1v5_1.0.7-3_amd64.deb b9b50d2abbdd40de51fc2089c3edc588ab500fdb 1811948 music-bin-dbgsym_1.0.7-3_amd64.deb d1018bef8a45836f786c85a3933d95acf67b6474 122150 music-bin_1.0.7-3_amd64.deb 4bf8fcf18139d85f62266e5748dab1a1bbe39ac6 310052 music-doc_1.0.7-3_all.deb 9bcd70d8d172e72035d1d1fd5c142fd96a20a21e 13492 music_1.0.7-3_amd64.buildinfo Checksums-Sha256: de949ed431a483d64370201f8f4bd4fb617f273e301b277d6af270bba4f5 1979 music_1.0.7-3.dsc d8b2c11873f86e4fe62c489160bef40be404fb2b0f78cf60fac1cb731805c78a 26108 music_1.0.7-3.debian.tar.xz 1a7e1be5e39ca97e16fe2eba029cd252c68660797e6ca38f9b0c998430fb4724 252584 libmusic-dev_1.0.7-3_amd64.deb 5b520edc7d3df078f1254bd22c05559a1100bc81ec0d02a017eb91d3ecb29809 2093612 libmusic1v5-dbgsym_1.0.7-3_amd64.deb b1f0dda79fe840efa87914763245d8e84d987bc7e1e9526cffdb2662ea7e6b96 131876 libmusic1v5_1.0.7-3_amd64.deb 994072366c4c65967766de2fc7723c1b5055352c5f4007895956ee025824a3bd 1811948 music-bin-dbgsym_1.0.7-3_amd64.deb c3933f946fb09638fce165951ca79fde54c6b07132795552d2fb8d040417b53a 122150 music-bin_1.0.7-3_amd64.deb 5c624f65dc6534f0f45a92c36edf039c8374d262e5626aab3a61503b847041b7 310052 music-doc_1.0.7-3_all.deb cf8b740b17893cb1ab0941e7135767abc79852ec1d7a2549f59925c6e6453aae 13492 music_1.0.7-3_amd64.buildinfo Files: e1ea6d6e28309089c43cc515e04b2afc 1979 libs extra music_1.0.7-3.dsc 872b7d0a1ef7b185b6a104c52e10c3f9 26108 libs extra music_1.0.7-3.debian.tar.xz d97c46a49cd1add02afa9c84a05826d8 252584 libdevel extra libmusic-dev_1.0.7-3_amd64.deb 004aa159c55da79ae96aad9065730222 2093612 debug extra libmusic1v5-dbgsym_1.0.7-3_amd64.deb df7a613fc16c62bba2cd7cccf33ae236 131876 libs extra libmusic1v5_1.0.7-3_amd6
Bug#877925: bpfcc-tools: Missing kernel dependency
Package: bpfcc-tools Version: 0.3.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, this package does JIT compilation and it fails when kernel headers are not installed. Possible fix: add a dependency to kernel headers Regards -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bpfcc-tools depends on: ii python 2.7.14-1 ii python-bpfcc0.3.0-1 ii python-netaddr 0.7.18-2 bpfcc-tools recommends no packages. bpfcc-tools suggests no packages. -- no debconf information
Bug#877924: mwc: Fails to start: mwctools module is missing.
Package: mwc Version: 2.0.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, Just downloading https://github.com/mtill/MailWebsiteChanges/blob/master/mwctools.py mwc works as expected. Please, append this module to the package. Best Regards, Manolo Díaz -- Traceback: Traceback (most recent call last): File "/usr/bin/mwc", line 218, in config = importlib.import_module(configMod) File "/usr/lib/python3.5/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 985, in _gcd_import File "", line 968, in _find_and_load File "", line 955, in _find_and_load_unlocked ImportError: No module named 'mwc-config' -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.13.5 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mwc depends on: ii python33.5.3-3 ii python3-cssselect 1.0.1-1 ii python3-lxml 4.0.0-1 mwc recommends no packages. mwc suggests no packages. -- no debconf information
Bug#876622: marked as done (spambayes: missing build dependency on rename)
Your message dated Sat, 07 Oct 2017 10:23:37 + with message-id and subject line Bug#876622: fixed in spambayes 1.1b1-4 has caused the Debian Bug report #876622, regarding spambayes: missing build dependency on rename 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.) -- 876622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spambayes Version: 1.1b1-1.1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/spambayes.html ... # Install Python modules python setup.py -q install --root=debian/spambayes --no-compile --install-layout=deb rm debian/spambayes/usr/bin/sb_notesfilter.py prename "s/.py//" debian/spambayes/usr/bin/*.py /bin/sh: 1: prename: not found debian/rules:33: recipe for target 'install-stamp' failed make: *** [install-stamp] Error 127 --- End Message --- --- Begin Message --- Source: spambayes Source-Version: 1.1b1-4 We believe that the bug you reported is fixed in the latest version of spambayes, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugo Lefeuvre (supplier of updated spambayes package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2017 09:56:27 +0200 Source: spambayes Binary: spambayes Architecture: source all Version: 1.1b1-4 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Hugo Lefeuvre Description: spambayes - Python-based spam filter using statistical analysis Closes: 785503 876622 Changes: spambayes (1.1b1-4) unstable; urgency=medium . * Upload to unstable (Closes: #876622). * Modify debian/patches/asyncore.patch: Instead of importing incompatible asyncore and asynchat modules from Python, remove affected functionalities (Closes: #785503). * Bump Standards-Version to 4.1.1. Checksums-Sha1: 6423341b2a36dd837c7073912625b73a6d8a6017 1692 spambayes_1.1b1-4.dsc 4b1b79f30b278bc7e63e66c8739f70f55a560265 12832 spambayes_1.1b1-4.debian.tar.xz 3c7d6dcf5b34ef8dd2cf44ba4b9d2ae7c28f0723 385482 spambayes_1.1b1-4_all.deb 7fa3e116b2e631f5fe5f49ea4ce253d69617ac93 5749 spambayes_1.1b1-4_amd64.buildinfo Checksums-Sha256: 09eb4567a36841a112f106384993cb9872835e0b90bcb61e40ba986b1614ad9f 1692 spambayes_1.1b1-4.dsc 7be02468b93cfbaba6378373d0e007b7da874f2bb561534f0bdf7ff3172b42a0 12832 spambayes_1.1b1-4.debian.tar.xz 553a8994b3db5e036bf2539079f1fe69e06914e6f3fe3a77cfaa635d1be8b229 385482 spambayes_1.1b1-4_all.deb f711f4d01bae4b289d2d1ee9db4286c44857aba8335128d6330bdd08e27a6eef 5749 spambayes_1.1b1-4_amd64.buildinfo Files: e4b14bf968e8056ee6df7063534e0ecb 1692 mail optional spambayes_1.1b1-4.dsc 0764cb5e80aa690339c804c0f224e19d 12832 mail optional spambayes_1.1b1-4.debian.tar.xz ce08ceb597d184c71a44b21381fa01cf 385482 mail optional spambayes_1.1b1-4_all.deb 6cc5db0f499e4974c2964c4ddfcfb5ed 5749 mail optional spambayes_1.1b1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE5LpPtQuYJzvmooL3LVy48vb3khkFAlnYjakACgkQLVy48vb3 khmYQQf/T0o1e4vxGmpysm+7NpYBMiVGiDVEx3OeWABohbcwizd1Sw+K3TxcP0Mv g3CcgW9lmtuFx6zfGmmWyAPvHbC/iYev0gmRu/kS8YMm9AUjLQ3tfDa2Lc+OEpzr oYjJVuUm6gcrLA+lLtlai1wcIYGtb+7lD/aF4iIRJADiDrgP7pH4KlOhmf+pxkQe c+yu+JWPH1UQuHzF9dThjqPDA83HyTYOz/miyGAW+o6e4WHJLg43jyu+Afgkjkke WEZul9j3crUsKWvZU1nEIp2ahcDkYA9bM40v0VRlkKXt/X8De2CkcXvl2FzghR6f qKaVFISbu1IgC74d6WV997rKoAUCSg== =+Lng -END PGP SIGNATURE End Message ---
Bug#877840: marked as done (python-magnumclient: FTBFS ImportError: No module named oslo_log, openstackclient.tests.unit)
Your message dated Sat, 07 Oct 2017 10:22:38 +
with message-id
and subject line Bug#877840: fixed in python-magnumclient 2.7.0-2
has caused the Debian Bug report #877840,
regarding python-magnumclient: FTBFS ImportError: No module named oslo_log,
openstackclient.tests.unit
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.)
--
877840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-magnumclient
Version: 2.7.0-1
Severity: serious
Justification: fails to build from source
Hi,
python-magnumclient/experimental FTBFS due to undeclared build
dependencies:
===> Testing with python (python2)
+ rm -rf .testrepository
+ testr-python2 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.HyG3Fo4P04
+ tee /tmp/tmp.HyG3Fo4P04
+ subunit2pyunit
+ pwd
+ PYTHONPATH=/build/python-magnumclient-2.7.0 PYTHON=python2.7 testr-python2
run --subunit
magnumclient\.tests\.(?!.*test_utils\.CliUtilsTest\.test_keys_and_vals_to_strs.*)
ruNon-zero exit code (2) from test listing.
nning=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ . --list
--- import errors ---
Failed to import test module:
magnumclient.tests.osc.unit.v1.test_cluster_templates
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in
_find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in
_get_module_from_name
__import__(name)
File "magnumclient/tests/osc/unit/v1/test_cluster_templates.py", line 20, in
from magnumclient.osc.v1 import cluster_templates as osc_ct
File "magnumclient/osc/v1/cluster_templates.py", line 20, in
from oslo_log import log as logging
ImportError: No module named oslo_log
Failed to import test module: magnumclient.tests.osc.unit.v1.test_clusters
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in
_find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in
_get_module_from_name
__import__(name)
File "magnumclient/tests/osc/unit/v1/test_clusters.py", line 21, in
from magnumclient.tests.osc.unit.v1 import fakes as magnum_fakes
File "magnumclient/tests/osc/unit/v1/fakes.py", line 20, in
from magnumclient.tests.osc.unit import osc_utils
File "magnumclient/tests/osc/unit/osc_utils.py", line 21, in
from openstackclient.tests.unit import fakes
ImportError: No module named openstackclient.tests.unit
--
Ran 0 tests in 0.510s
Andreas
python-magnumclient_2.7.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-magnumclient
Source-Version: 2.7.0-2
We believe that the bug you reported is fixed in the latest version of
python-magnumclient, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-magnumclient
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 07 Oct 2017 12:03:00 +0200
Source: python-magnumclient
Binary: python-magnumclient python-magnumclient-doc python3-magnumclient
Architecture: source all
Version: 2.7.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Description:
python-magnumclient - client library for Magnum API - Python 2.x
python-magnumclient-doc - client library for Magnum API - doc
python3-magnumclient - client library for Magnum API - Python 3.x
Closes: 877840
Changes:
python-magnumclient (2.7.0-2) experimental; urgency=medium
.
* Added missing build-depends: python{3,}-oslo.log (Closes: #877840).
Checksums-Sha1:
b887661465d2c5a3aba892476237e7f842a1d7f7 3559 python-magnumclient_2.7.0-2.dsc
714c43ce668c9c177cba7dcbdb75c0e43b72a682 3660
python-magnu
Bug#877875: marked as done (python-requestsexceptions: insufficiently versioned B-D: python-pbr/python3-pbr)
Your message dated Sat, 07 Oct 2017 10:22:46 +
with message-id
and subject line Bug#877875: fixed in python-requestsexceptions 1.3.0-2
has caused the Debian Bug report #877875,
regarding python-requestsexceptions: insufficiently versioned B-D:
python-pbr/python3-pbr
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.)
--
877875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-requestsexceptions
Version: 1.3.0-1
Severity: serious
Justification: fails to build from source
Hi,
python-requestsexceptions FTBFS in a current sid+experimental
environment with the sid versions of python-pbr/python3-pbr (1.10.0-1):
fakeroot debian/rules clean
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh clean --buildsystem=python_distutils --with python2,python3
dh_auto_clean -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
Download error on https://pypi.python.org/simple/pbr/: [Errno -3] Temporary
failure in name resolution -- Some packages may not be found!
Download error on https://pypi.python.org/simple/: [Errno -3] Temporary failure
in name resolution -- Some packages may not be found!
No local packages or working download links found for pbr>=2.0.0
Traceback (most recent call last):
File "setup.py", line 29, in
pbr=True)
File "/usr/lib/python2.7/distutils/core.py", line 111, in setup
_setup_distribution = dist = klass(attrs)
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 325, in
__init__
self.fetch_build_eggs(attrs['setup_requires'])
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 446, in
fetch_build_eggs
replace_conflicting=True,
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 855,
in resolve
dist = best[req.key] = env.best_match(req, ws, installer)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1127,
in best_match
return self.obtain(req, installer)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1139,
in obtain
return installer(requirement)
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 518, in
fetch_build_egg
return cmd.easy_install(req)
File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py",
line 691, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for
Requirement.parse('pbr>=2.0.0')
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:7: recipe for target 'clean' failed
make: *** [clean] Error 1
Andreas
PS: network access is not available during build
python-requestsexceptions_1.3.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-requestsexceptions
Source-Version: 1.3.0-2
We believe that the bug you reported is fixed in the latest version of
python-requestsexceptions, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-requestsexceptions
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 07 Oct 2017 12:06:52 +0200
Source: python-requestsexceptions
Binary: python-requestsexceptions python3-requestsexceptions
Architecture: source all
Version: 1.3.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Description:
python-requestsexceptions - import exceptions from bundled packages in
requests. - Python 2.7
python3-requestsexceptions - import exceptions from bundled packages in
requests. - Python 3.x
Closes: 877875
Changes:
python-requestsexceptions (1.3.0-2) experimen
Bug#877875: marked as pending
tag 877875 pending thanks Hello, Bug #877875 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/openstack/libs/python-requestsexceptions.git/commit/?id=58a5e30 --- commit 58a5e30f723e3ba409b72338fba39fea0ff30840 Author: Thomas Goirand Date: Sat Oct 7 10:07:58 2017 + changelog closes 877875 diff --git a/debian/changelog b/debian/changelog index 4cbb6db..8d355e0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,6 @@ python-requestsexceptions (1.3.0-2) experimental; urgency=medium - * Fixed pbr version in (build-)depends. + * Fixed pbr version in (build-)depends (Closes: #877875). -- Thomas Goirand Sat, 07 Oct 2017 12:06:52 +0200
Processed: Bug#877875 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 877875 pending Bug #877875 [src:python-requestsexceptions] python-requestsexceptions: insufficiently versioned B-D: python-pbr/python3-pbr Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877840: marked as pending
tag 877840 pending
thanks
Hello,
Bug #877840 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
https://anonscm.debian.org/cgit/openstack/clients/python-magnumclient.git/commit/?id=a9db6bc
---
commit a9db6bcd1492ea96204bc5bce7a53700b928fb9f
Author: Thomas Goirand
Date: Sat Oct 7 12:03:33 2017 +0200
Added missing build-depends: python{3,}-oslo.log (Closes: #877840).
diff --git a/debian/changelog b/debian/changelog
index 56dcadc..637febb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-magnumclient (2.7.0-2) experimental; urgency=medium
+
+ * Added missing build-depends: python{3,}-oslo.log (Closes: #877840).
+
+ -- Thomas Goirand Sat, 07 Oct 2017 12:03:00 +0200
+
python-magnumclient (2.7.0-1) experimental; urgency=medium
[ Ondřej Nový ]
Processed: Bug#877840 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 877840 pending Bug #877840 [src:python-magnumclient] python-magnumclient: FTBFS ImportError: No module named oslo_log, openstackclient.tests.unit Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 877840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#785565: [Ns-developers] State of ns3 in the Debian distribution
Hello, Please do not applogize, there is nothing to be ashamed for. Real life often restrain us from contributing to Debian and others... That's life. Thank you for all you did in the past, and what you will manage to do in the future. That would be really great if you could do an upload without the python-pygoocanvas dependency, please. Thanks in advance, Mt. On Sat, Oct 07, 2017 at 04:28:59PM +0800, YunQiang Su wrote: > Sorry for everyone. > I didn't take care of ns3 for years. > > I will update it in few days. > > On Thu, Oct 5, 2017 at 3:54 AM, Martin Quinson > wrote: > > Hello Tom, thanks for your reply. > > > > On Wed, Oct 04, 2017 at 06:08:01PM +, Tom Henderson wrote: > >> Hi Martin, responses inline below. > >> > >> On 10/04/2017 05:26 AM, Martin Quinson wrote: > >> > Hello dear developers, > >> > > >> > Also, if you have an easy way to drop these dependencies (by disabling > >> > them at build time), that could solve the issue on our side. I know I > >> > should RTFM for that, but I fail to find the time, and I would > >> > appreciate this help in the package maintainance, please. The current > >> > build receipe is here (that's a makefile): > >> > http://sources.debian.net/src/ns3/3.26%2Bdfsg-1/debian/rules/ > >> There isn't an ns-3 build dependency on netanim. The pyviz visualizer is > >> automatically left out of the configuration if the prerequisites are not > >> found by Waf. Is this sufficient (if we don't resolve these package > >> dependencies in time)? > > > > Ok, then I will rebuild the package without that dependency, upload > > it, and it should do the trick for now, I guess. I'll keep you posted. > > > >> We are about to make a new ns-3 release (3.27). We also noticed that the > >> netanim package in Debian stretch is very old (3.100+ while we are now at > >> 3.108). Can we work towards replacing the old versions with the new > >> versions in the current release of Debian, or must we wait until the next > >> Debian release? > > > > There is a plenty of time before the next official Debian release > > (maybe one year and half). So we can definitely work something out for > > Debian. Ubuntu regularly picks the packages in the Debian rolling > > release as a basis for their own releases, but I'm unaware of their > > schedule. I'd say that March 2018 is the target for the next LTS > > release of Ubuntu. > > > > The problem is that I have personnally I don't have any personal > > interest in netanim myself, and absolutely no time to devote to that > > task. If you can come up with a patch against the packaging scripts > > that refresh it, I can certainly mentor the package upload. > > > > Thanks, Mt. > > > > -- > > It's so easy to laugh, it's so easy to hate, > > it takes strength to be gentle and kind. -- Morrissey, I Know It's Over. > > > > -- > YunQiang Su -- alvin: mais ça, au moins dans ma tête, c'est à peu près clair frs69wq: bah t'enverra ta tête aux relecteurs alors... signature.asc Description: PGP signature
Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1
On 2017-10-07 02:14:10 [+0200], Gedalya wrote: > This is affecting EAP with wpa_supplicant. > See https://bugs.debian.org/877904 You need to do two steps in wpa supplicant: - Add an option to set minimum TLS version - if that option is set, forwarded its value (1.0 or 1.1) to SSL_CTX_set_min_proto_version() or SSL_set_min_proto_version() Sebastian
Bug#868958: [Debian-med-packaging] Bug#868958: bcftools FTBFS on 32bit: test failures
On 3 October 2017 at 13:52, peter green wrote: > Unfortunately while 1.4-3 built successfully on armel, armhf and mipsel > 1.5-1 did not. I think some patches were missed from the update_1.4.1 branch. https://anonscm.debian.org/cgit/debian-med/bcftools.git/log/?h=update_1.4.1
Bug#864947: Re: parl-desktop-world depends on cruft package firefox-esr-l10n-be
On Sun, 2017-06-18 at 12:19 +0100, peter green wrote: > Tags 864947 +patch > Thanks > > > parl-desktop-world depends on firefox-esr-l10n-be which is no > > longer built by firefox-esr. I'm still trying to figure out where > > this is coming from, I can't find any evidence of it in the source > > package but rebuilding the binaries doesn't make it go away. > > > > Ok, figured it out, the reference comes from boxer-data > > So to fix this bug requires an update to boxer-data followed by a > (sourceful) rebuild of debian-parl. Patch for boxer-data is at http:/ > /debdiffs.raspbian.org/main/b/boxer-data/boxer- > data_10.5.20%2brpi1.debdiff , once I have confirmed this mail is in > the buglog I will clone/block. The crufty firefox-esr binaries were removed during today's stretch point release, so both packages will need updates in stable - once they're fixed in unstable. Regards, Adam
Processed: found 864985 in 10.5.20
Processing commands for cont...@bugs.debian.org: > found 864985 10.5.20 Bug #864985 [boxer-data] boxer-data references cruft package firefox-esr-l10n-be Marked as found in versions boxer-data/10.5.20. > thanks Stopping processing here. Please contact me if you need assistance. -- 864985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#785565: [Ns-developers] State of ns3 in the Debian distribution
Sorry for everyone. I didn't take care of ns3 for years. I will update it in few days. On Thu, Oct 5, 2017 at 3:54 AM, Martin Quinson wrote: > Hello Tom, thanks for your reply. > > On Wed, Oct 04, 2017 at 06:08:01PM +, Tom Henderson wrote: >> Hi Martin, responses inline below. >> >> On 10/04/2017 05:26 AM, Martin Quinson wrote: >> > Hello dear developers, >> > >> > Also, if you have an easy way to drop these dependencies (by disabling >> > them at build time), that could solve the issue on our side. I know I >> > should RTFM for that, but I fail to find the time, and I would >> > appreciate this help in the package maintainance, please. The current >> > build receipe is here (that's a makefile): >> > http://sources.debian.net/src/ns3/3.26%2Bdfsg-1/debian/rules/ >> There isn't an ns-3 build dependency on netanim. The pyviz visualizer is >> automatically left out of the configuration if the prerequisites are not >> found by Waf. Is this sufficient (if we don't resolve these package >> dependencies in time)? > > Ok, then I will rebuild the package without that dependency, upload > it, and it should do the trick for now, I guess. I'll keep you posted. > >> We are about to make a new ns-3 release (3.27). We also noticed that the >> netanim package in Debian stretch is very old (3.100+ while we are now at >> 3.108). Can we work towards replacing the old versions with the new >> versions in the current release of Debian, or must we wait until the next >> Debian release? > > There is a plenty of time before the next official Debian release > (maybe one year and half). So we can definitely work something out for > Debian. Ubuntu regularly picks the packages in the Debian rolling > release as a basis for their own releases, but I'm unaware of their > schedule. I'd say that March 2018 is the target for the next LTS > release of Ubuntu. > > The problem is that I have personnally I don't have any personal > interest in netanim myself, and absolutely no time to devote to that > task. If you can come up with a patch against the packaging scripts > that refresh it, I can certainly mentor the package upload. > > Thanks, Mt. > > -- > It's so easy to laugh, it's so easy to hate, > it takes strength to be gentle and kind. -- Morrissey, I Know It's Over. -- YunQiang Su
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> tag 876622 + pending
Bug #876622 {Done: Adrian Bunk } [src:spambayes] spambayes:
missing build dependency on rename
Added tag(s) pending.
> tag 785503 + pending
Bug #785503 [spambayes] spambayes: /usr/bin/core_server incompatible with
python 2.7 (jessie's {current stable} python)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
785503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785503
876622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#865497: CVE-2017-9781 not yet fixed in 1.2.8p26-1?
Hi Matt! On Fri, Oct 06, 2017 at 03:43:38PM -0700, Matt Taggart wrote: > On 10/06/2017 02:28 PM, Salvatore Bonaccorso wrote: > > Control: notfixed -1 1.2.8p26-1 > > > > Hi! > > > > On Fri, Oct 06, 2017 at 09:09:03PM +, Debian Bug Tracking System wrote: > > > This is an automatic notification regarding your Bug report > > > which was filed against the src:check-mk package: > > > > > > #865497: check-mk: CVE-2017-9781: reflected XSS in webapi.py > > > > I looked up the source for 1.2.8p26-1. > > > > The fix for CVE-2017-9781 is > > > > http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=c248f0b6ff7b15ced9f07a3df8a80fad656ea5b1 > > > > which does not yet seem to be applied to 1.2.8p26-1? > > > > Can you please double-check? > > > > > > Note, there is a second CVE now for check-mk, that one got addressed > > in 1.2.8p26, but it's not clear yet in which version in was > > introduced. > Hi, > > You are right, the fix for CVE-2017-9781, which upstream calls "werk #4757" > is _not_ in 1.2.8p26. I was confused with upstream #5208 when I wrote the > changelog that closed the bug. Thanks for confirming! > Upstream lists the following security related fixes for 1.2.8 > == > #5208 > http://mathias-kettner.com/check_mk_werks.php?werk_id=5208&HTML=yes > http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=673360408b90f99bd54cf936091cff08d979a057 > > #4902 > http://mathias-kettner.com/check_mk_werks.php?werk_id=4902&HTML=yes > http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=96e39a0f024d9b2b521576c1eb71aca7fb3e818d > > #7661 (fixed in 1.4.0p8, supposedly fixed in 1.2.8p25?) > http://mathias-kettner.com/check_mk_werks.php?werk_id=7661&HTML=yes > > #7631 > http://mathias-kettner.com/check_mk_werks.php?werk_id=7631&HTML=yes > > #3970 (fixed in 1.2.8p14) > http://mathias-kettner.com/check_mk_werks.php?werk_id=3970&HTML=yes > > #3855 (fixed in 1.2.8p11) > http://mathias-kettner.com/check_mk_werks.php?werk_id=3855&HTML=yes > > #3743 (fixed in 1.2.8p10) > http://mathias-kettner.com/check_mk_werks.php?werk_id=3743&HTML=yes > > Full list of changes for 1.2.8p26 > = > http://mathias-kettner.com/check_mk_werks.php?edition_id=raw&branch=1.2.8&version=1.2.8p26&HTML=yes > > Full list of changes for 1.4.0p14 > = > http://mathias-kettner.com/check_mk_werks.php?edition_id=raw&branch=1.4.0&version=1.4.0p14&HTML=yes > > which additionally lists > > #4757 (as you mentioned above, fixed in 1.4.0p6) > http://mathias-kettner.com/check_mk_werks.php?werk_id=4757&HTML=yes > http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=14a5b79c6f549502244a60146ed6831dc3473f2a > > #7643 (only in 1.4 and newer) > http://mathias-kettner.com/check_mk_werks.php?werk_id=7643&HTML=yes > > So I think the Debian 1.2.8p16 package is only missing #4757. Ok. Do you know something about https://mathias-kettner.de/check_mk_werks.php?werk_id=5208&HTML=yes . I twas fixed in 1.2.8p26, but I failed to see if it was introduced *after* 1.2.8p14-1. But I will try to handle that in a seprate bug. I tried to git clone the git repository mentioned at http://git.mathias-kettner.de/check_mk.git but that just does not work for me. > > I will ask upstream if they intend to fix #4757 in the 1.2.8 series. > Unfortunately due to how the upstream tarball/build works, it is tricky to > patch upstream files. If upstream doesn't intend to include this fix I can > generate a patch to make it work. Ok thanks. > I had started working on packaging 1.4.0 as a way to fix these security bugs > (and even did an upload to experimental) but I recently learned from > upstream that: > > "The use of Check_MK without OMD environment and customization of paths is > explicitly not supported anymore." > > ie you can't use check-mk stand-alone, you have to use OMD (and > livestatus/WATO/multisite, the whole stack) and you have to use upstream's > installer to upstream's paths. It's very much the "network appliance" model > (or flatpak, docker image, etc) > I don't know if we'll be able to make this work in Debian. (not to mention > that nagios is gone and icinga1 will go away at some point) Hmm, that sounds bad. I guess if that turns out to be true, then would better alternative to drop check-mk completely from the Debian archive? I mean specifically, for the buster release cycle, if 1.2.8 based series should be included then still. > That prompted me to go back to 1.2.8 and package the latest release there in > order to at least have something working without the security bugs. Ok. I'm not too familiar with check-mk itself, I only worked on it from tracking security fixes point of view. Can you say something, on how long are the 1.2.8 series planned to be supported upstream? Regards, Salvatore
Bug#877910: marked as done (irssi-plugin-xmpp: Fails to install due to conflict with irssi)
Your message dated Sat, 07 Oct 2017 07:34:17 + with message-id and subject line Bug#877910: fixed in irssi-plugin-xmpp 0.54-2 has caused the Debian Bug report #877910, regarding irssi-plugin-xmpp: Fails to install due to conflict with irssi 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.) -- 877910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: irssi-plugin-xmpp Version: 0.54-1 Severity: grave Justification: renders package unusable Trying to upgrade the package to 0.54-1 from 0.53-1+b1 fails with the following error: Preparing to unpack .../irssi-plugin-xmpp_0.54-1_amd64.deb ... Unpacking irssi-plugin-xmpp:amd64 (0.54-1) over (0.53-1+b1) ... dpkg: error processing archive /var/cache/apt/archives/irssi-plugin-xmpp_0.54-1_amd64.deb (--unpack): trying to overwrite '/usr/share/irssi/help/ban', which is also in package irssi 1.0.4-1+b2 Errors were encountered while processing: /var/cache/apt/archives/irssi-plugin-xmpp_0.54-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) So it looks like some package needs a rebuild or a Breaks/Replaces config item needs to be added. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages irssi-plugin-xmpp depends on: ii irssi1.0.4-1+b2 ii libc62.24-17 ii libglib2.0-0 2.54.1-1 ii libloudmouth1-0 1.5.3-2 irssi-plugin-xmpp recommends no packages. irssi-plugin-xmpp suggests no packages. -- no debconf information signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: irssi-plugin-xmpp Source-Version: 0.54-2 We believe that the bug you reported is fixed in the latest version of irssi-plugin-xmpp, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated irssi-plugin-xmpp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 07 Oct 2017 09:18:25 +0200 Source: irssi-plugin-xmpp Binary: irssi-plugin-xmpp Architecture: source amd64 Version: 0.54-2 Distribution: unstable Urgency: medium Maintainer: Florian Schlichting Changed-By: Florian Schlichting Description: irssi-plugin-xmpp - XMPP plugin for irssi Closes: 877910 Changes: irssi-plugin-xmpp (0.54-2) unstable; urgency=medium . * Rename ban and kick help pages to not conflict with irssi (closes: #877910) Checksums-Sha1: 19a530d068217d6faf7ccb19530acd65dbfc4ae6 1979 irssi-plugin-xmpp_0.54-2.dsc 945968766b06d74b7fa2d9e9947f5dcdedd7f2c5 29820 irssi-plugin-xmpp_0.54-2.debian.tar.xz ef227daa9193d624daac2c386cd8ebb9b1ec7dc7 170260 irssi-plugin-xmpp-dbgsym_0.54-2_amd64.deb df126823df13e2d05fa37b3fed580b6264df3cbf 7287 irssi-plugin-xmpp_0.54-2_amd64.buildinfo 5601416b31f7c530f6d83b41520195bba0efd8cc 72378 irssi-plugin-xmpp_0.54-2_amd64.deb Checksums-Sha256: 0b8538197fb2b5433c41403bc1d1d11923efa91aa0fcb3a88622da1fdeacfce4 1979 irssi-plugin-xmpp_0.54-2.dsc 3961bc2ac2ce2a6c8cd2180141bcf2fbb01c136a39da4892ecad1a4e2255822b 29820 irssi-plugin-xmpp_0.54-2.debian.tar.xz 5a766140528df313e6e9784fb96b7a7e26912734f66cad29ee35366f9236efcb 170260 irssi-plugin-xmpp-dbgsym_0.54-2_amd64.deb f112f9236fcd2ca3a2c1e8b89827c85aa65f5c4ab5f4b765fa1d8e42aefdb806 7287 irssi-plugin-xmpp_0.54-2_amd64.buildinfo 7d8d9efa5c1d2dd43797333d49e59de29d6190da6a8765815716b9e49d505313 72378 irssi-plugin-xmpp_0.54-2_amd64.deb Files: c932cffd01170362529cea0f95832c9e 1979 net optional irssi-plugin-xmpp_0.54-2.dsc 20e4533434e462b38163d960c39a9c53 29820 net optional irssi-plugin-xmpp_0.54-2.debian.tar.xz 61a61f7d0074a2ab9242b6ca5343809a 1702
Bug#876606: marked as done (zeal: missing build dependency on libsqlite3-dev)
Your message dated Sat, 07 Oct 2017 07:20:34 + with message-id and subject line Bug#876606: fixed in zeal 1:0.4.0-2 has caused the Debian Bug report #876606, regarding zeal: missing build dependency on libsqlite3-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.) -- 876606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zeal Version: 1:0.4.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=zeal&suite=sid ... Project ERROR: sqlite3 development package not found Makefile:122: recipe for target 'sub-util-make_first' failed make[3]: *** [sub-util-make_first] Error 3 --- End Message --- --- Begin Message --- Source: zeal Source-Version: 1:0.4.0-2 We believe that the bug you reported is fixed in the latest version of zeal, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) (supplier of updated zeal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Oct 2017 15:07:40 +0800 Source: zeal Binary: zeal Architecture: source Version: 1:0.4.0-2 Distribution: unstable Urgency: medium Maintainer: ChangZhuo Chen (陳昌倬) Changed-By: ChangZhuo Chen (陳昌倬) Description: zeal - Simple offline API documentation browser Closes: 876606 Changes: zeal (1:0.4.0-2) unstable; urgency=medium . * Add missing Build-Depends libsqlite3-dev (Closes: #876606). Checksums-Sha1: d2101b1331d8366eb1192addc4d47f1d1d5b7ddb 2010 zeal_0.4.0-2.dsc d52e5c95373bc7c2accf61bc4eb9acc4a315f153 3520 zeal_0.4.0-2.debian.tar.xz de52fa45325daf4dcbc4b356608cfcc84eaef4b9 15114 zeal_0.4.0-2_source.buildinfo Checksums-Sha256: 26dd78974cf7ee7e949423ffb7cab3a7129c31aa82b4c9fb5ec8e5b6fb5a400c 2010 zeal_0.4.0-2.dsc 1200c55f7e94c6e9fdad4bf8546e52a7724dddc8e7076651e64319499a92f3e5 3520 zeal_0.4.0-2.debian.tar.xz 746b6cb49194ffbce967922a16918bd93c2bfbf87ed09f5249ab09c0a27091d9 15114 zeal_0.4.0-2_source.buildinfo Files: cf435baf195a3bbfe3c95a9bc7123d55 2010 utils optional zeal_0.4.0-2.dsc e3aeb316803e54abd97e45bb5ac104c5 3520 utils optional zeal_0.4.0-2.debian.tar.xz ac64df51245af2b03f4bf31e37f706dc 15114 utils optional zeal_0.4.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEE5H9tOJ8ReWWaF1PGrc2MXdaTaQFAlnYfVIACgkQGrc2MXda TaSHgg//Y9dJAvOHyGXwmURb0Imw+eCKN8N+WKRgLKrcC+3CG/JkEnAZqsPsmmkO hivYGZhccpp/RI+mIHEkiLP0FedPkOJGC/mhTykA1aeB/GKvAgklFSc40szzD27v q/qpBRmKXf9M1R+vdFogkY36VkZnHPW7UDw7WMjbtKj22q/zY/F6Y6cHBkO1oJlf SHkuk9aFr7iaz00KGM+HGYv1DQhSxKDSex0Nc4t4rOM9FY6nomB2ILSyVnWrCFQA 5/bRPduyXN0ov1ECJaSeu7lzIqniicQQ0bMVAF5c3vl1hRmPGc56BUPMb7N3Ev47 /haCfUew7qVshU+UC8+5x+vxiBKnUjrxxTh/U6FGubBu7hv88OdxTUWURpYsyrot IGayLyluAXLbJUzeTliR6e2GW4laQUsoIIe4YOgMb0l7Km5vW2QDIfup2sc3yWNP WbLOwYigyN/QDFNcq73tGo7x2Auc2KzZDl9SnyqjJHT4gytsBdMv8YgUvJPi1K9D 2mbfX3hHYktScU0RPTAlQV+ormuZoXAXlHVILe+KMPePoJxYO4phQGnsalCQI+89 cVrUAe7DbNxw0jeL7S5E0UNTdLJ+W/gIbQFM2z6KPovg5GK684efwjTXs41D1BN0 WhcNFPbNHzZDVwc7CsmtV1bvdec4dBtLKhefhkYaGO+6P4MnwSE= =3v6o -END PGP SIGNATURE End Message ---
