Bug#917726: globus-gass-copy: FTBFS: tests failed
On 08/01/19 at 10:16 +0100, Mattias Ellert wrote: > mån 2019-01-07 klockan 09:20 +0100 skrev Lucas Nussbaum: > > Hi, > > > > On 07/01/19 at 08:28 +0100, Mattias Ellert wrote: > > > Hi! > > > > > > The globus-gass-copy package and dependent packaged have now been > > > tagged for autoremoval due to this RC bug. So I need to resolve this > > > with some urgency. > > > > > > Since I did not receive any reply to my previous comment I need to > > > resolve this without the additional feedback I requested. > > > > > > I will close this as "not a bug" since I believe the failure to be due > > > to a misconfiguration of the rebuild test build server, and not a real > > > bug (see the above mentioned comment for details). > > > > > > If this is not satisfactory, please feel welcome to reopen the bug and > > > provide additional information about why you believe the bug report is > > > valid. > > > > > > Mattias > > > > Well, I'm not sure about this bug. > > > > It seems that it fails to build with '!' in /etc/shadow, with '*' in > > /etc/shadow, and even with a password in /etc/shadow. I don't know if > > sbuild is doing something strange, but it doesn't look like it. > > > > Also, this is (AFAIK) the only package failing because of this. > > > > Lucas > > Checking the code of the server binary used during the test, what is > checked by the server to ensure logins are not enabled is: > > 1. That a shell is defined for the user and that this shell exists > 2. That the defined shell is a regular file > 3. That the defined shell has executable permissions. Ah! thanks! I can confirm that after setting a shell, it builds fine. I'll go through the other failures to detect misfiled bugs. Lucas signature.asc Description: PGP signature
Processed: severity 918648 important
Processing commands for cont...@bugs.debian.org: > severity 918648 important Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 918648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918648: watcher: FTBFS (autobuilder hangs)
On 1/8/19 3:20 PM, Adrian Bunk wrote: > On Tue, Jan 08, 2019 at 02:38:47PM +0100, Santiago Vila wrote: >> ... >> I see you have downgraded this from serious, but Release Policy says >> packages must build without failure. Could you please tell me >> in which sense this: >> >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/watcher.html >> >> is not a failure? I never contested that it fails in reproducible-builds.org, I wrote it builds for me on my environment which isn't tweaked like the one from reproducible-builds.org. Also, I would appreciate if you do not play BTS-ping-pong. Since I haven't reproduced the build failure locally, I'm declaring that it doesn't build *in certain environment*, which isn't a general FTBFS. Therefore, I'm considering this not an RC bug. Ultimately, this is up to me to decide, and if you want to override, then you must go to a higher authority (like the tech ctte or the release team). Also, the severity that I'm setting has nothing to do with my will to fix it, so there's no reason to get mad at it. > This error in reproducible looks pretty different (it is also not a hang) > from what you reported. Very much! > In any case it would be good if the package would be uploaded source-only, > since this would have made it easy to see whether it also fails on the > buildds. Has the issue that the package has to go through NEW again if it fails been fixed? Cheers, Thomas Goirand (zigo)
Processed: Bug #894202 in rdkit marked as pending
Processing control commands: > tag -1 pending Bug #894202 [src:rdkit] rdkit FTBFS on 32bit: test hang Added tag(s) pending. -- 894202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#894202: Bug #894202 in rdkit marked as pending
Control: tag -1 pending Hello, Bug #894202 in rdkit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/rdkit/commit/aa0d8bb34b21038d01bdcc4c2121423ae4bfb457 * debian/patches/disable_hanging_test.patch: New patch, removes the testEnumeration test, which makes 32-bit architectures hang (Closes: #894202). (this message was generated automatically) -- Greetings https://bugs.debian.org/894202
Processed: tagging 917686
Processing commands for cont...@bugs.debian.org:
> tags 917686 + help
Bug #917686 [src:lightproof] lightproof: FTBFS: "zipfile is empty" with python
3.7 ("Key Error")
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#918569: Could not find 'activerecord' (~> 4.2) - did find: [activerecord-5.2.0]
On Mon, 07 Jan 2019 22:39:41 +0100 t...@schleuder.org wrote: > > Upstream (aka us) is working on switching to activerecord 5.2: > https://0xacab.org/schleuder/schleuder/issues/372 Hi paz, Would it be possible to upload a release candidate/dev version right now to help with rails transition? You can update it to stable version as per your current schedule. Thanks Praveen signature.asc Description: OpenPGP digital signature
Bug#918769: ocaml-migrate-parsetree FTBFS:dh_install fails
Source: ocaml-migrate-parsetree
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
ocaml-migrate-parsetree fails to build on sid using debhelper version 12
(12 is the version of the debhelper package, I haven't touched the DH
compat level) :
dh_install: libmigrate-parsetree-ocamlbuild-ocaml missing files:
usr/doc/ocaml-migrate-parsetree-ocamlbuild/{CHANGES.md,README.md,LICENSE.md}
dh_install: missing files, aborting
make: *** [debian/rules:8: binary] Error 25
-Ralf.
Bug#911514: closing 911514
close 911514 5.0.0.2801-2~bpo9+1 thanks
Bug#917715: Bug #917715 in openconnect marked as pending
Control: tag -1 pending Hello, Bug #917715 in openconnect reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/openconnect/commit/44cb37cd3f82e52b09306fa8298bb7e952341724 Update Build-Depends on ocserv (>= 0.12.1-2) to fix failing unit tests Closes: #917715 Signed-off-by: Mike Miller (this message was generated automatically) -- Greetings https://bugs.debian.org/917715
Bug#918768: opencolorio FTBFS with yaml-cpp 0.6.2
Source: opencolorio Version: 1.1.0~dfsg0-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opencolorio.html ... /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/build/1st/opencolorio-1.1.0~dfsg0=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wshadow -Wconversion -Wcast-qual -Wformat=2 -Wl,-z,relro -shared -Wl,-soname,libOpenColorIO.so.1 -o libOpenColorIO.so.1.1.0 CMakeFiles/OpenColorIO.dir/AllocationOp.cpp.o CMakeFiles/OpenColorIO.dir/AllocationTransform.cpp.o CMakeFiles/OpenColorIO.dir/Baker.cpp.o CMakeFiles/OpenColorIO.dir/CDLTransform.cpp.o CMakeFiles/OpenColorIO.dir/Caching.cpp.o CMakeFiles/OpenColorIO.dir/ColorSpace.cpp.o CMakeFiles/OpenColorIO.dir/ColorSpaceTransform.cpp.o CMakeFiles/OpenColorIO.dir/Config.cpp.o CMakeFiles/OpenColorIO.dir/Context.cpp.o CMakeFiles/OpenColorIO.dir/Display.cpp.o CMakeFiles/OpenColorIO.dir/DisplayTransform.cpp.o CMakeFiles/OpenColorIO.dir/Exception.cpp.o CMakeFiles/OpenColorIO.dir/ExponentOps.cpp.o CMakeFiles/OpenColorIO.dir/ExponentTransform.cpp.o CMakeFiles/OpenColorIO.dir/FileFormat3DL.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatCC.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatCCC.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatCDL.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatCSP.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatHDL.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatIridasCube.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatIridasItx.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatIridasLook.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatPandora.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatSpi1D.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatSpi3D.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatSpiMtx.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatTruelight.cpp.o CMakeFiles/OpenColorIO.dir/FileFormatVF.cpp.o CMakeFiles/OpenColorIO.dir/FileTransform.cpp.o CMakeFiles/OpenColorIO.dir/GpuShaderDesc.cpp.o CMakeFiles/OpenColorIO.dir/GpuShaderUtils.cpp.o CMakeFiles/OpenColorIO.dir/GroupTransform.cpp.o CMakeFiles/OpenColorIO.dir/HashUtils.cpp.o CMakeFiles/OpenColorIO.dir/ImageDesc.cpp.o CMakeFiles/OpenColorIO.dir/ImagePacking.cpp.o CMakeFiles/OpenColorIO.dir/LogOps.cpp.o CMakeFiles/OpenColorIO.dir/LogTransform.cpp.o CMakeFiles/OpenColorIO.dir/Logging.cpp.o CMakeFiles/OpenColorIO.dir/Look.cpp.o CMakeFiles/OpenColorIO.dir/LookParse.cpp.o CMakeFiles/OpenColorIO.dir/LookTransform.cpp.o CMakeFiles/OpenColorIO.dir/Lut1DOp.cpp.o CMakeFiles/OpenColorIO.dir/Lut3DOp.cpp.o CMakeFiles/OpenColorIO.dir/MathUtils.cpp.o CMakeFiles/OpenColorIO.dir/MatrixOps.cpp.o CMakeFiles/OpenColorIO.dir/MatrixTransform.cpp.o CMakeFiles/OpenColorIO.dir/NoOps.cpp.o CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o CMakeFiles/OpenColorIO.dir/Op.cpp.o CMakeFiles/OpenColorIO.dir/OpOptimizers.cpp.o CMakeFiles/OpenColorIO.dir/ParseUtils.cpp.o CMakeFiles/OpenColorIO.dir/PathUtils.cpp.o CMakeFiles/OpenColorIO.dir/Platform.cpp.o CMakeFiles/OpenColorIO.dir/Processor.cpp.o CMakeFiles/OpenColorIO.dir/ScanlineHelper.cpp.o CMakeFiles/OpenColorIO.dir/Transform.cpp.o CMakeFiles/OpenColorIO.dir/TruelightOp.cpp.o CMakeFiles/OpenColorIO.dir/TruelightTransform.cpp.o CMakeFiles/OpenColorIO.dir/UnitTest.cpp.o CMakeFiles/OpenColorIO.dir/md5/md5.cpp.o CMakeFiles/OpenColorIO.dir/pystring/pystring.cpp.o -ltinyxml -lyaml-cpp /usr/bin/ld: CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o: in function `YAML::BadSubscript::BadSubscript()': /usr/include/yaml-cpp/exceptions.h:122: undefined reference to `vtable for YAML::Exception' /usr/bin/ld: CMakeFiles/OpenColorIO.dir/OCIOYaml.cpp.o: relocation R_X86_64_PC32 against undefined hidden symbol `_ZTVN4YAML9ExceptionE' can not be used when making a shared object /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status make[3]: *** [src/core/CMakeFiles/OpenColorIO.dir/build.make:1004: src/core/libOpenColorIO.so.1.1.0] Error 1 The Ubuntu diff seems to contain a fix.
Bug#918767: rivet FTBFS with yaml-cpp 0.6.2
Source: rivet Version: 1.8.3-2 Severity: serious Tags: ftbfs patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rivet.html ... In file included from /usr/include/c++/8/array:35, from /usr/include/yaml-cpp/node/convert.h:10, from /usr/include/yaml-cpp/yaml.h:18, from AnalysisInfo.cc:7: /usr/include/c++/8/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options. #error This file requires compiler and library support \ Fix attached. Description: Don't force a lower C++ standard with -ansi This causes FTBFS with yaml-cpp 0.6.2. Author: Adrian Bunk --- rivet-1.8.3.orig/configure.ac +++ rivet-1.8.3/configure.ac @@ -316,7 +316,6 @@ AM_CPPFLAGS="$AM_CPPFLAGS -I\$(BOOSTINCP AM_CPPFLAGS="$AM_CPPFLAGS -I\$(HEPMCINCPATH)" AM_CPPFLAGS="$AM_CPPFLAGS -I\$(FASTJETINCPATH)" AC_CEDAR_CHECKCXXFLAG([-pedantic], [AM_CXXFLAGS="$AM_CXXFLAGS -pedantic"]) -AC_CEDAR_CHECKCXXFLAG([-ansi], [AM_CXXFLAGS="$AM_CXXFLAGS -ansi"]) AC_CEDAR_CHECKCXXFLAG([-Wall], [AM_CXXFLAGS="$AM_CXXFLAGS -Wall"]) AC_CEDAR_CHECKCXXFLAG([-Wno-long-long], [AM_CXXFLAGS="$AM_CXXFLAGS -Wno-long-long"]) AC_CEDAR_CHECKCXXFLAG([-Wno-format], [AM_CXXFLAGS="$AM_CXXFLAGS -Wno-format"])
Processed: Bug #917715 in openconnect marked as pending
Processing control commands: > tag -1 pending Bug #917715 [src:openconnect] openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 917715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 911514
Processing commands for cont...@bugs.debian.org: > close 911514 5.0.0.2801-2~bpo9+1 Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage Marked as fixed in versions davmail/5.0.0.2801-2~bpo9+1. Bug #911514 [davmail] davmail: fails to install: wrong update-rc.d usage Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 911514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 915679 in 1.2.0~DEVEL+20181202-1
Processing commands for cont...@bugs.debian.org:
> fixed 915679 1.2.0~DEVEL+20181202-1
Bug #915679 {Done: Yangfl } [pcc] pcc: broken symlinks on
i386: /usr/bin/x86_64-linux-gnu-p* -> x86_64-linux-gnu-pcc
Marked as fixed in versions pcc/1.2.0~DEVEL+20181202-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 918685 is forwarded to https://github.com/silnrsi/graphite/issues/49
Processing commands for cont...@bugs.debian.org: > forwarded 918685 https://github.com/silnrsi/graphite/issues/49 Bug #918685 [src:graphite2] graphite2: FTBFS with test failures: awamicmp[123] Set Bug forwarded-to-address to 'https://github.com/silnrsi/graphite/issues/49'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#894202: marked as done (rdkit FTBFS on 32bit: test hang)
Your message dated Tue, 08 Jan 2019 18:00:16 + with message-id and subject line Bug#894202: fixed in rdkit 201803.4+dfsg-2 has caused the Debian Bug report #894202, regarding rdkit FTBFS on 32bit: test hang 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.) -- 894202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdkit Version: 201709.3+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=rdkit=sid ... debian/rules override_dh_auto_test make[1]: Entering directory '/<>/rdkit-201709.3+dfsg' cp -r rdkit obj-*/ find /<>/rdkit-201709.3+dfsg -name rdchem.so /<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/rdkit/Chem/rdchem.so #export RDBASE=/<>/rdkit-201709.3+dfsg PYTHONPATH=/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/ LD_LIBRARY_PATH="/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//lib:" RDBASE=/<>/rdkit-201709.3+dfsg PYTHONPATH=/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu/:/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//rdkit/Chem/ LD_LIBRARY_PATH="/<>/rdkit-201709.3+dfsg/obj-i686-linux-gnu//lib:" dh_auto_test cd obj-i686-linux-gnu && make -j4 -O test ARGS\+=-j4 E: Build killed with signal TERM after 150 minutes of inactivity --- End Message --- --- Begin Message --- Source: rdkit Source-Version: 201803.4+dfsg-2 We believe that the bug you reported is fixed in the latest version of rdkit, 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 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated rdkit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 Jan 2019 17:03:28 +0100 Source: rdkit Binary: python-rdkit rdkit-doc rdkit-data librdkit1 librdkit-dev postgresql-11-rdkit Architecture: source amd64 all Version: 201803.4+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Michael Banck Description: librdkit-dev - Collection of cheminformatics and machine-learning software (deve librdkit1 - Collection of cheminformatics and machine-learning software (shar postgresql-11-rdkit - Collection of cheminformatics and machine-learning software (Post python-rdkit - Collection of cheminformatics and machine-learning software rdkit-data - Collection of cheminformatics and machine-learning software (data rdkit-doc - Collection of cheminformatics and machine-learning software (docu Closes: 894202 Changes: rdkit (201803.4+dfsg-2) unstable; urgency=medium . [ Andreas Tille ] * Point Vcs fields to Salsa . [ Michael Banck ] * debian/patches/disable_hanging_test.patch: New patch, removes the testEnumeration test, which makes 32-bit architectures hang (Closes: #894202). Checksums-Sha1: dfe921dd8f50eac8760f6a37864f3a310ded2b0a 2721 rdkit_201803.4+dfsg-2.dsc 067bca04b883b3ef00af6b842dc91fdef29aadd8 13044 rdkit_201803.4+dfsg-2.debian.tar.xz 36cb6553a5bcb11420c4616257a7a3d2edc7bb9c 281676 librdkit-dev_201803.4+dfsg-2_amd64.deb 71e541e8ab0a4ef2ce12dc11aa50293a1b2db508 61718224 librdkit1-dbgsym_201803.4+dfsg-2_amd64.deb 9739dd71df0a8dc16ff1f66568a58a1ed3c7df33 2500420 librdkit1_201803.4+dfsg-2_amd64.deb 47f88051cf6b2964f463f411ba1f2faeba13254f 957016 postgresql-11-rdkit-dbgsym_201803.4+dfsg-2_amd64.deb 3c40abd0a58f4ce49f0be77649a15662912384ce 398640 postgresql-11-rdkit_201803.4+dfsg-2_amd64.deb 814beb4e51f3e8b4ece377c1441fe6af4fe0b548 43908796 python-rdkit-dbgsym_201803.4+dfsg-2_amd64.deb d6abafc097800986b88a67eb64e0b06b3d5ebb52 3807272 python-rdkit_201803.4+dfsg-2_amd64.deb c8f30162d04ae8ea8c58327d2288e75655f06027 6760292 rdkit-data_201803.4+dfsg-2_all.deb 07b5208919d2a4f92b1fa149eda32a7b7431116c 5890288 rdkit-doc_201803.4+dfsg-2_all.deb 7749dbfa23999d9a736f97a0fb568c6f762c976d 15630 rdkit_201803.4+dfsg-2_amd64.buildinfo Checksums-Sha256: 1c3dfd723aeb4c1d6ab4c43f22839d6dbda987e88cf040eff0bc1db6c5964af5 2721 rdkit_201803.4+dfsg-2.dsc bfcc2a0e4685bff801140c03b7c2f5b0e31cd5283dbcfbf53e33bd4731024128 13044 rdkit_201803.4+dfsg-2.debian.tar.xz e6d3c0eef54f1bceaa78a29d7a2fe272fa708f653479e03976f3e548b9f6e891
Bug#911507: offlineimap: fails to load imaplib2
Hi, On Sun, Oct 21, 2018 at 08:50AM, Hans-Joachim wrote: > Dear Maintainer, > > calling offlineimap stops reporting > > Error while trying to import system imaplib2: name '__revision__' is not > defined > Traceback (most recent call last): > File "/usr/bin/offlineimap", line 20, in > from offlineimap import OfflineImap > File "/usr/share/offlineimap/offlineimap/__init__.py", line 20, in > from offlineimap.init import OfflineImap > File "/usr/share/offlineimap/offlineimap/init.py", line 29, in > import offlineimap.virtual_imaplib2 as imaplib > File "/usr/share/offlineimap/offlineimap/virtual_imaplib2.py", line 43, in > > from offlineimap.bundled_imaplib2 import * > ImportError: No module named bundled_imaplib2 > > looks like to be related to the 'new' python-imaplib2 (2.57-5) First of all, sorry for the late reply. Unfortunately I cannot reproduce this on my machine. Could you please provide the versions of offlineimap and python-imaplib2 you are using? I am asking because you said that the 'new' python-imaplib2 (2.57-5) is at fault, but the following suggests you are using python-imaplib2 2.55-1+deb9u1 from stable: > Versions of packages offlineimap depends on: > ii python 2.7.13-2 > ii python-imaplib2 2.55-1+deb9u1 > ii python-six 1.10.0-3 Best, -- Ilias
Bug#913346: libsane1: Cannot update libsane1
Hello! On 1/3/19 11:51 PM, Jeremy Bicha wrote: > This issue is more serious for Ubuntu which will need to keep a > libsane1 transitional package around until after 20.04 LTS. It's not serious for Debian since the package never entered testing in the first place. > I've prepared an NMU for sane-backends (versioned as 1.0.27-3.2) and > uploaded it to DELAYED/15. Please feel free to tell me if I > should delay it longer. I disagree with change as this particular version of sane never left unstable. Please don't add kludges to support something which is not supported in the first place. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: Re: libsane1: Cannot update libsane1
Processing control commands: > severity -1 normal Bug #913346 [sane-backends] libsane1: Cannot update libsane1 Severity set to 'normal' from 'serious' -- 913346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913346: libsane1: Cannot update libsane1
Control: severity -1 normal On 1/8/19 4:26 PM, John Paul Adrian Glaubitz wrote: > It's not serious for Debian since the package never entered testing in > the first place. Adjusting severity accordingly. Please don't set the severity to serious unless providing a reference to the corresponding chapter in the Debian Policy. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Processed: Re: Bug#918648: watcher: FTBFS (autobuilder hangs)
Processing control commands: > clone -1 -2 Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs) Bug 918648 cloned as bug 918712 > retitle -2 watcher FTBFS in some timezones Bug #918712 [src:watcher] watcher: FTBFS (autobuilder hangs) Changed Bug title to 'watcher FTBFS in some timezones' from 'watcher: FTBFS (autobuilder hangs)'. > severity -1 serious Bug #918648 [src:watcher] watcher: FTBFS (autobuilder hangs) Severity set to 'serious' from 'important' -- 918648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918648 918712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918575: marked as done (abyss FTBFS on 32bit big endian: test failures)
Your message dated Tue, 08 Jan 2019 16:04:01 + with message-id and subject line Bug#918575: fixed in abyss 2.1.5-2 has caused the Debian Bug report #918575, regarding abyss FTBFS on 32bit big endian: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abyss Version: 2.1.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=abyss ... FAIL: common_kmer = Running main() from gtest_main.cc [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from Kmer [ RUN ] Kmer.canonicalize Common/KmerTest.cpp:18: Failure Value of: kmer Actual: AGGC Expected: canonical Which is: ATGC Common/KmerTest.cpp:30: Failure Value of: kmer Actual: TTCGG Expected: oddLengthCanonical Which is: CGAGC [ FAILED ] Kmer.canonicalize (0 ms) [--] 1 test from Kmer (1 ms total) [--] Global test environment tear-down [==] 1 test from 1 test case ran. (1 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] Kmer.canonicalize 1 FAILED TEST FAIL common_kmer (exit status: 1) FAIL: BloomFilter = Running main() from gtest_main.cc [==] Running 8 tests from 2 test cases. [--] Global test environment set-up. [--] 6 tests from BloomFilter [ RUN ] BloomFilter.base Konnector/BloomFilter.cc:30: Failure Value of: x[b] Actual: false Expected: true Konnector/BloomFilter.cc:31: Failure Value of: x[Bloom::hash(b) % x.size()] Actual: false Expected: true Konnector/BloomFilter.cc:34: Failure Value of: x[c] Actual: false Expected: true Konnector/BloomFilter.cc:35: Failure Value of: x[Bloom::hash(c) % x.size()] Actual: false Expected: true [ FAILED ] BloomFilter.base (0 ms) [ RUN ] BloomFilter.serialization Konnector/BloomFilter.cc:55: Failure Value of: origBloom[b] Actual: false Expected: true Konnector/BloomFilter.cc:56: Failure Value of: origBloom[c] Actual: false Expected: true Konnector/BloomFilter.cc:73: Failure Value of: copyBloom[b] Actual: false Expected: true Konnector/BloomFilter.cc:74: Failure Value of: copyBloom[c] Actual: false Expected: true [ FAILED ] BloomFilter.serialization (1 ms) [ RUN ] BloomFilter.union_ Konnector/BloomFilter.cc:92: Failure Value of: bloom2[b] Actual: false Expected: true Konnector/BloomFilter.cc:109: Failure Value of: unionBloom[b] Actual: false Expected: true [ FAILED ] BloomFilter.union_ (0 ms) [ RUN ] BloomFilter.intersect Konnector/BloomFilter.cc:132: Failure Value of: bloom2[b] Actual: false Expected: true [ FAILED ] BloomFilter.intersect (0 ms) [ RUN ] BloomFilter.windowSerialization [ OK ] BloomFilter.windowSerialization (0 ms) [ RUN ] BloomFilter.windowUnion [ OK ] BloomFilter.windowUnion (0 ms) [--] 6 tests from BloomFilter (1 ms total) [--] 2 tests from CascadingBloomFilter [ RUN ] CascadingBloomFilter.base Konnector/BloomFilter.cc:178: Failure Value of: 2U Actual: 2 Expected: x.popcount() Which is: 1 Konnector/BloomFilter.cc:179: Failure Value of: x[b] Actual: false Expected: true Konnector/BloomFilter.cc:180: Failure Value of: x[Bloom::hash(b) % x.size()] Actual: false Expected: true Konnector/BloomFilter.cc:182: Failure Value of: 3U Actual: 3 Expected: x.popcount() Which is: 1 Konnector/BloomFilter.cc:183: Failure Value of: x[c] Actual: false Expected: true [ FAILED ] CascadingBloomFilter.base (1 ms) [ RUN ] CascadingBloomFilter.window [ OK ] CascadingBloomFilter.window (0 ms) [--] 2 tests from CascadingBloomFilter (1 ms total) [--] Global test environment tear-down [==] 8 tests from 2 test cases ran. (2 ms total) [ PASSED ] 3 tests. [ FAILED ] 5 tests, listed below: [ FAILED ] BloomFilter.base [ FAILED ] BloomFilter.serialization [ FAILED ] BloomFilter.union_ [ FAILED ] BloomFilter.intersect [ FAILED ] CascadingBloomFilter.base 5 FAILED TESTS FAIL BloomFilter (exit status: 1) FAIL: Konnector_DBGBloomAlgorithms == Running main() from gtest_main.cc [==] Running 8 tests from 2 test cases. [--] Global test environment set-up. [--] 4 tests from GetStartKmerPosTest [ RUN ] GetStartKmerPosTest.FullReadMatch [ OK ] GetStartKmerPosTest.FullReadMatch (0 ms) [ RUN ] GetStartKmerPosTest.FullReadMismatch [ OK ]
Bug#918713: libopenmpi3: test failure triggered by mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version
Package: libopenmpi3 Version: 3.1.3-8 Severity: serious Justification: Policy 8.6 openmpi 3.1.3-8 is triggering test failure on a wide range of client packages, including combblas, dolfin and family, petsc and family, superlu-dist. dolfin and petsc (etc) leave a record of the fault, e.g. petsc https://ci.debian.net/data/autopkgtest/unstable/amd64/p/petsc/1662208/log.gz run SNES testex19 Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process See http://www.mcs.anl.gov/petsc/documentation/faq.html [ci-1546915814:12491] mca_base_component_repository_open: unable to open mca_pmix_pmix2x: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pmix_pmix2x.so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored) [ci-1546915814:12491] [[63830,0],0] ORTE_ERROR_LOG: Not found in file ess_hnp_module.c at line 325 -- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): opal_pmix_base_select failed --> Returned value Not found (-13) instead of ORTE_SUCCESS hypre and scotch are unaffected. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenmpi3 depends on: ii libc62.28-4 ii libevent-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-6 2.1.8-stable-4 ii libfabric1 1.6.1-5 ii libgcc1 1:8.2.0-13 ii libgfortran5 8.2.0-13 ii libhwloc-plugins 2.0.0-1 ii libhwloc51.11.12-1 ii libibverbs1 21.0-1 ii libnl-3-200 3.4.0-1 ii libnl-route-3-2003.4.0-1 ii libpmix2 3.1.0~rc2-2 ii libpsm-infinipath1 3.3+20.604758e7-6 ii libpsm2-211.2.68-4 ii libquadmath0 8.2.0-13 ii libstdc++6 8.2.0-13 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages libopenmpi3 recommends: ii openmpi-bin 3.1.3-7 libopenmpi3 suggests no packages. -- no debconf information
Bug#918685: graphite2: FTBFS with test failures: awamicmp[123]
Am 8. Januar 2019 12:08:56 MEZ schrieb Andreas Beckmann : >Source: graphite2 >Version: 1.3.13-3 >Severity: serious >Justification: fails to build from source (but built successfully in >the past) > >Hi, > >graphite2/experimental FTBFS on all architectures: > >https://buildd.debian.org/status/package.php?p=graphite2=experimental > > >The following tests FAILED: > 75 - awamicmp1 (Failed) > 76 - awamicmp2 (Failed) > 77 - awamicmp3 (Failed) >Errors while running CTest > > >Andreas Hi, I *do* follow build logs. You don't need to tell the obvious. Interestingly It builds in my sid chroot. But indeed also fails for me in pbuilder. Now the question is what is different/missing... Diffing 1.3.12 and 1.3 13 definitely shows adaptions in the expected values... Regards Rene
Processed: This is the same bug
Processing commands for cont...@bugs.debian.org: > reassign 917587 libceres-dev Bug #917587 [src:colmap] colmap: FTBFS (dh_auto_configure fails) Bug reassigned from package 'src:colmap' to 'libceres-dev'. No longer marked as found in versions colmap/3.5-1. Ignoring request to alter fixed versions of bug #917587 to the same values previously set > severity 883619 serious Bug #883619 [libceres-dev] libceres-dev: dependency on libeigen3-dev isn't strong enough Severity set to 'serious' from 'normal' > forcemerge 883619 917587 Bug #883619 [libceres-dev] libceres-dev: dependency on libeigen3-dev isn't strong enough Bug #917587 [libceres-dev] colmap: FTBFS (dh_auto_configure fails) 917587 was not blocked by any bugs. 917587 was not blocking any bugs. Added blocking bug(s) of 917587: 868355 Marked as found in versions ceres-solver/1.13.0+dfsg0-1. Added tag(s) confirmed. Bug #883619 [libceres-dev] libceres-dev: dependency on libeigen3-dev isn't strong enough Added tag(s) ftbfs. Merged 883619 917587 > affects 883619 src:colmap Bug #883619 [libceres-dev] libceres-dev: dependency on libeigen3-dev isn't strong enough Bug #917587 [libceres-dev] colmap: FTBFS (dh_auto_configure fails) Added indication that 883619 affects src:colmap Added indication that 917587 affects src:colmap > thanks Stopping processing here. Please contact me if you need assistance. -- 883619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883619 917587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915432: dhcpd-pools: diff for NMU version 2.29-1.1
Hi Adrian, On 2019-01-01 15:10, Adrian Bunk wrote: Control: tags 915432 + patch Control: tags 915432 + pending Dear maintainer, I've prepared an NMU for dhcpd-pools (versioned as 2.29-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. Thanks! Fine with me. I will contact upstream. Kind regards, Martijn van Brummelen
Bug#916106: marked as done (arptables provides the same executables as iptables packages without using alternatives)
Your message dated Tue, 08 Jan 2019 11:34:03 + with message-id and subject line Bug#916106: fixed in arptables 0.0.4+snapshot20181021-1 has caused the Debian Bug report #916106, regarding arptables provides the same executables as iptables packages without using alternatives 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.) -- 916106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ebtables Version: 2.0.10.4-5 Severity: serious Hi, When running debsums -ac, it complains that: debsums: Error: symlink loop detected in path 'sbin/ebtables'. Please file a bug against ebtables. So here is the bug report. Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages ebtables depends on: ii libc6 2.27-6 Versions of packages ebtables recommends: ii iptables 1.8.1-2 ii kmod 25-1 ebtables suggests no packages. -- no debconf information -- debsums errors found: debsums: Error: symlink loop detected in path 'sbin/ebtables'. Please file a bug against ebtables. --- End Message --- --- Begin Message --- Source: arptables Source-Version: 0.0.4+snapshot20181021-1 We believe that the bug you reported is fixed in the latest version of arptables, 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 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alberto Molina Coballes (supplier of updated arptables 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, 06 Jan 2019 17:00:42 + Source: arptables Binary: arptables Architecture: source Version: 0.0.4+snapshot20181021-1 Distribution: unstable Urgency: medium Maintainer: Debian Netfilter Packaging Team Changed-By: Alberto Molina Coballes Description: arptables - ARP table administration Closes: 916106 Changes: arptables (0.0.4+snapshot20181021-1) unstable; urgency=medium . * [2c7c7c6] New upstream version 0.0.4+snapshot20181021 * [c6b2324] d/patches: Adapt the default patch to the latest upstream version * [3076713] arptables: introduce /sbin compatibility symlinks * [4108b0d] arptables: introduce alternatives for /usr/sbin/arptables (Closes: #916106) * [f7b48be] d/control: bump std-version to 4.3.0 Checksums-Sha1: d2467abf1fd22f93cc956803b3296c9c5b16a661 2073 arptables_0.0.4+snapshot20181021-1.dsc 818a09d48199ed6ebfe05cbffe9aef9f8f0dec70 51555 arptables_0.0.4+snapshot20181021.orig.tar.gz 4badc9f7b4c1bb9e3bf32b57bfcc2e0947345f03 4580 arptables_0.0.4+snapshot20181021-1.debian.tar.xz 04d984a3cf164f3fa6d2a6288f1c5ee6a7e30471 5416 arptables_0.0.4+snapshot20181021-1_amd64.buildinfo Checksums-Sha256: fcab08437f1cb17be79b2d9510ebf71989ad511978e3cd7df81ee587bd4b2335 2073 arptables_0.0.4+snapshot20181021-1.dsc 0dd7d9f60c01fce467e7797e8d7c917a8a558dd7bbec0d204dbdbfeeeb1771db 51555 arptables_0.0.4+snapshot20181021.orig.tar.gz e771a169956544756a160f8a67f9259264bb00a0f22b3904d2bc9ebf8f321d4b 4580 arptables_0.0.4+snapshot20181021-1.debian.tar.xz ddc4152214f35d993aec938704a059c20c97048a427b381ea99ac0706dcf8766 5416 arptables_0.0.4+snapshot20181021-1_amd64.buildinfo Files: 1476765d6a5d6223b09fd2fc05ead7eb 2073 net optional arptables_0.0.4+snapshot20181021-1.dsc b305d4209e2a075e4de7e8ae0f826968 51555 net optional arptables_0.0.4+snapshot20181021.orig.tar.gz f257bf1f18c047cbb575780a45044483 4580 net optional arptables_0.0.4+snapshot20181021-1.debian.tar.xz 9815f950785dac717e09837bd080feb8 5416 net optional arptables_0.0.4+snapshot20181021-1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#917695: marked as done (mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16))
Your message dated Tue, 8 Jan 2019 12:43:31 +0100 with message-id <20190108114331.obwxxp7etgcon...@mail.anaproy.nl> and subject line Re: mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16) has caused the Debian Bug report #917695, regarding mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16) 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.) -- 917695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mbtserver Version: 0.11-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > Filtered Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > dpkg-deb: building package 'sbuild-build-depends-mbtserver-dummy' in > '/<>/resolver-LNLJQQ/apt_archive/sbuild-build-depends-mbtserver-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-mbtserver-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-LNLJQQ/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-LNLJQQ/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-LNLJQQ/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-LNLJQQ/apt_archive ./ Sources [563 B] > Get:5 copy:/<>/resolver-LNLJQQ/apt_archive ./ Packages [647 B] > Fetched 2173 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install mbtserver build dependencies (apt-based resolver) > - > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-mbtserver-dummy : Depends: libtimbl4-dev (>= 6.4.8) but > it is not going to be installed > Depends: libtimblserver4-dev (>= > 1.11) but it is not going to be installed > Depends: libmbt1-dev (>= 3.2.16) but > it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/mbtserver_0.11-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Hi Lucas, This issue should be solved by the new release (0.12) that was already prepared but has been uploaded yesterday. It may take a bit for the migration to testing. Kind regards, -- Maarten van Gompel Language Machines research group Centre for Language and Speech Technology Radboud Universiteit Nijmegen proy...@anaproy.nl https://proycon.anaproy.nl https://github.com/proycon GnuPG key: 0x39FE11201A31555C XMPP: proy...@anaproy.nl Matrix: @proycon:matrix.org Telegram: proycon IRC: proycon (freenode) Discord:proycon#8272 Mastodon: https://mastodon.social/@proycon
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Hi, There are 162 packages in Debian containing the string MurmurHash. Some of them use an implementation called PMurHash which fixes the endianess issue. On 07.01.19 16:42, Andreas Tille wrote: > It seems to be time to package MurmurHash3 separately, isn't it? Yeah, I think it makes sense to create a libmurmurhash package and then have all "bad" implementations link against that. I will look at some oof the code and start a project. Best, Fabian
Bug#915432: marked as done (dhcpd-pools FTBFS with glibc 2.28)
Your message dated Tue, 08 Jan 2019 11:49:27 + with message-id and subject line Bug#915432: fixed in dhcpd-pools 2.29-1.1 has caused the Debian Bug report #915432, regarding dhcpd-pools FTBFS with glibc 2.28 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.) -- 915432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dhcpd-pools Version: 2.29-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dhcpd-pools.html ... fseeko.c: In function 'rpl_fseeko': fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." ^ make[5]: *** [Makefile:1764: fseeko.lo] Error 1 See #915151 for background. --- End Message --- --- Begin Message --- Source: dhcpd-pools Source-Version: 2.29-1.1 We believe that the bug you reported is fixed in the latest version of dhcpd-pools, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated dhcpd-pools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Jan 2019 16:04:26 +0200 Source: dhcpd-pools Binary: dhcpd-pools Architecture: source Version: 2.29-1.1 Distribution: unstable Urgency: low Maintainer: Martijn van Brummelen Changed-By: Adrian Bunk Description: dhcpd-pools - ISC dhcpd lease analysis and reporting tool Closes: 915432 Changes: dhcpd-pools (2.29-1.1) unstable; urgency=low . * Non-maintainer upload. * Add patch for gnulib with glibc 2.28. (Closes: #915432) Checksums-Sha1: ba04f51457d2a43e2be9edaf80a2d7fed110776d 1869 dhcpd-pools_2.29-1.1.dsc 1d634b275f70a4e4ab0fee29eb2b64e61dc08e55 4672 dhcpd-pools_2.29-1.1.debian.tar.xz Checksums-Sha256: 48ba34a755498f6aca8170a75d4d8fed3da866c087ac06a0fa188bd9dece8aaa 1869 dhcpd-pools_2.29-1.1.dsc e11ba8282897f737cec985aad519750d4a6ca3658412ef6d1ff636b390f12958 4672 dhcpd-pools_2.29-1.1.debian.tar.xz Files: c226822472a546651381fecda2716682 1869 net optional dhcpd-pools_2.29-1.1.dsc abc8c7da212e9694e11b1674db72aaf6 4672 net optional dhcpd-pools_2.29-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlwrdJ0ACgkQiNJCh6LY mLEpEQ//aysQ5izx7XUidGuhb2QUNkkXSwpcjGyEFoyPkleeHOD4JhX5kQwPdyJd KXCbpJqmQd13d6leSQc26CX8aLzEvKn06phI7wCjGDIIZz5t3AnZUAI6wS7vH0BA nL8LsgdebHHZpCP9HlPAv/yh06vfbJvyyULQj1EsHv/Cb3yDiX9DDB/iqAWNj4pa 0F9B7awD6iD5FysOjJrmgDUcCz52hXiOg0PzwauG7MoiLlveUojglU9aO91WuVLF 4OwXaMzXHDdqdlIhQA28OLzwfrZhgqXVm3yZDwKRBV5YWN4iNcMhc+tCM5Ra6Ug6 LJfbVYTgtvrBTcCvkIw7fgW9ZNtsUDXh4h7p7ODKo18DPym+l2Hvv+M4OSXPsUT0 t+y7xldZrC/UFyWHXNPPyxxksO5IEHI7byB84ZH1VoWDwC1tYbBbF4b/1nkbbxU2 3lTtLUH4aJH2UesaGyH46NBUL9WpD1n4wot+beO8UlZ39QWdQNwMfW+kyjahszKa aH1hqI3N9bAtsYImdtHjhsUVKbH40SX7mdLIyFFfHPUoc6KRQvWQc8i/5mu4WyW9 RHTKVzzaKAxk3kNBVOQAicFUgfVIqdBtYaisnuCRC/lTH17OV2lCtIXIhXSirRWT HXRHatmbJF7MAQHnhX4f0xdC8kWzlMpV85ZQ+7TJRzRvpP75LS0= =Nxok -END PGP SIGNATURE End Message ---
Processed: pluto-jpl-eph: diff for NMU version 0.0~git20180228-1.1
Processing control commands: > tags 913369 + patch Bug #913369 [src:pluto-jpl-eph] pluto-jpl-eph: Release to unstable Added tag(s) patch. > tags 913369 + pending Bug #913369 [src:pluto-jpl-eph] pluto-jpl-eph: Release to unstable Added tag(s) pending. -- 913369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913369: pluto-jpl-eph: diff for NMU version 0.0~git20180228-1.1
Control: tags 913369 + patch Control: tags 913369 + pending Dear maintainer, I've prepared an NMU for pluto-jpl-eph (versioned as 0.0~git20180228-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru pluto-jpl-eph-0.0~git20180228/debian/changelog pluto-jpl-eph-0.0~git20180228/debian/changelog --- pluto-jpl-eph-0.0~git20180228/debian/changelog 2018-02-28 18:28:41.0 +0200 +++ pluto-jpl-eph-0.0~git20180228/debian/changelog 2019-01-08 13:57:07.0 +0200 @@ -1,3 +1,10 @@ +pluto-jpl-eph (0.0~git20180228-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Upload to unstable. (Closes: #913369) + + -- Adrian Bunk Tue, 08 Jan 2019 13:57:07 +0200 + pluto-jpl-eph (0.0~git20180228-1) experimental; urgency=medium * Initial release (Closes: #891852)
Bug#918676: r-cran-worrms: autopkgtest regression
Hi, I've just uploaded r-cran-worrms_0.3.2+dfsg-1 right before I realised this bug. Since I'm running autopkgtest pbuilder hook and did not realised any problem I guess this is fixed with this version. Can you confirm this? Kind regards Andreas. -- http://fam-tille.de
Bug#917857: NMU diff for aufs 4.19+20181217-0.1
Hey, thank you for the upload and your work. I am sorry that I did not manage to upload the new version due to too much other workload. I have seen that your delete the dependency on linux-kbuild. I have added it to avoid transition of the aufs-packages to testing before the linux package is available in the requested version. One time there was the problem that the aufs-package already migrated but the linux package had some RC-bug. Jan Am 07.01.19 um 20:08 schrieb Ben Hutchings: > I made an NMU to fix this bug (and related ones). I also fixed some > more minor issues with the packaging that I noticed. > > The attached debdiff is restricted to the debian/ directory. I created > the new orig tarball from upstream git commit > dc68432bc8fed5faf20f2a0889739a13110abdc1. > > Ben. >
Bug#917056: marked as done (python-libarchive-c FTBFS with libarchive 3.3.3)
Your message dated Tue, 08 Jan 2019 12:05:35 +
with message-id
and subject line Bug#917056: fixed in python-libarchive-c 2.8-0.1
has caused the Debian Bug report #917056,
regarding python-libarchive-c FTBFS with libarchive 3.3.3
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.)
--
917056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-libarchive-c
Version: 2.1-3.1
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-libarchive-c.html
...
=== FAILURES ===
_ test_check_archiveentry_using_python_testtar _
def test_check_archiveentry_using_python_testtar():
> check_entries(join(data_dir, 'testtar.tar'))
tests/test_entry.py:63:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
test_file = '/build/1st/python-libarchive-c-2.1/tests/data/testtar.tar'
regen = False, ignore = []
def check_entries(test_file, regen=False, ignore=''):
ignore = ignore.split()
fixture_file = test_file + '.json'
if regen:
entries = list(get_entries(test_file))
with open(fixture_file, 'w', encoding='UTF-8') as ex:
json.dump(entries, ex, indent=2)
with open(fixture_file, encoding='UTF-8') as ex:
expected = json.load(ex)
actual = list(get_entries(test_file))
for e1, e2 in zip(actual, expected):
for key in ignore:
e1.pop(key)
e2.pop(key)
> assert e1 == e2
E AssertionError: assert {'isblk': Fal...': False, ...} == {'isblk':
Fals...': False, ...}
E Common items:
E {u'isblk': False,
E u'ischr': False,
E u'isdev': False,
E u'isdir': False,
E u'isfifo': False,
E u'islnk': False,
E u'isreg': True,
E u'issym': False,
E u'linkpath': None,
E u'mode': u'rw-r--r--',
E u'mtime': 1041808783,
E u'path': u'pax/regtype4'}
E Differing items:
E {'size': 7011} != {'size': 0}
E Full diff:
E {u'isblk': False,
E u'ischr': False,
E u'isdev': False,
E u'isdir': False,
E u'isfifo': False,
E u'islnk': False,
E u'isreg': True,
E u'issym': False,
E u'linkpath': None,
E u'mode': u'rw-r--r--',
E u'mtime': 1041808783,
E u'path': u'pax/regtype4',
E - u'size': 7011}
E ? - --
E + u'size': 0}
tests/test_entry.py:96: AssertionError
-- Captured log call ---
ffi.py 82 WARNING Pathname can't be converted from UTF-8
to current locale.
= 1 failed, 15 passed in 0.30 seconds ==
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: python-libarchive-c
Source-Version: 2.8-0.1
We believe that the bug you reported is fixed in the latest version of
python-libarchive-c, 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 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mattia Rizzolo (supplier of updated python-libarchive-c
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 08 Jan 2019 12:51:18 +0100
Source: python-libarchive-c
Binary: python-libarchive-c python3-libarchive-c
Architecture: source
Version: 2.8-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jérémy Bobbio
Changed-By: Mattia Rizzolo
Description:
python-libarchive-c - Python interface to libarchive
python3-libarchive-c - Python3 interface to libarchive
Closes: 917056
Changes:
python-libarchive-c (2.8-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* New upstream version 2.8.
Bug#918548: About possibility to translate AppArmor tunables
Ian Jackson writes:
> Package: apparmor
> Version: 2.13.2-3
> Severity: serious
>
> Vincas, thanks for reporting this bug on the debian-i18n list.
> I think it needs a much higher profile.
>
> Vincas Dargis writes ("About possibility to translate AppArmor tunables"):
> > Let's look at one tunable file example. Currently, Debian and
> > upstream version of `/etc/apparmor.d/tunables/xdg-user-dirs`
That's OK for defaults, but it should be tunable per user.
> > (from apparmor package) have these contents:
> >
> > ```
> > @{XDG_DESKTOP_DIR}="Desktop"
> ...
> > The problem is that on my machine, "Desktop" is actually "Darbastalis",
>
> I think you mean "in your account" ? I mean, if you had several users
> who used different languages, wouldn't their "Desktop" directory be
> called different things ?
I should think so.
For this reason, this really should be dealt with in XDG, and I think
a variation on the /etc/alternatives model would be appropriate. That
is, the "real directory" is something like ~/.local/Desktop, and
~/Darbastalis is a link to that. (Or it could be the other way around,
for all I care! ;-)
Obviously this is a long-run (maybe never) solution, so I don't
propose that apparmor devs ignore this if it can be ameliorated with
reasonable effort in apparmor.
Steve
Bug#917726: globus-gass-copy: FTBFS: tests failed
mån 2019-01-07 klockan 09:20 +0100 skrev Lucas Nussbaum: > Hi, > > On 07/01/19 at 08:28 +0100, Mattias Ellert wrote: > > Hi! > > > > The globus-gass-copy package and dependent packaged have now been > > tagged for autoremoval due to this RC bug. So I need to resolve this > > with some urgency. > > > > Since I did not receive any reply to my previous comment I need to > > resolve this without the additional feedback I requested. > > > > I will close this as "not a bug" since I believe the failure to be due > > to a misconfiguration of the rebuild test build server, and not a real > > bug (see the above mentioned comment for details). > > > > If this is not satisfactory, please feel welcome to reopen the bug and > > provide additional information about why you believe the bug report is > > valid. > > > > Mattias > > Well, I'm not sure about this bug. > > It seems that it fails to build with '!' in /etc/shadow, with '*' in > /etc/shadow, and even with a password in /etc/shadow. I don't know if > sbuild is doing something strange, but it doesn't look like it. > > Also, this is (AFAIK) the only package failing because of this. > > Lucas Checking the code of the server binary used during the test, what is checked by the server to ensure logins are not enabled is: 1. That a shell is defined for the user and that this shell exists 2. That the defined shell is a regular file 3. That the defined shell has executable permissions. Mattias signature.asc Description: This is a digitally signed message part
Bug#917765: octave-interval: FTBFS: tests failed
Le samedi 29 décembre 2018 à 23:53 +0100, Lucas Nussbaum a écrit :
> Source: octave-interval
> Version: 3.2.0-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> Relevant part (hopefully):
> > [src/mpfr_matrix_mul_d.cc]
> > > > > > > /<>/src/mpfr_matrix_mul_d.cc
> >
> > * test;
> > [l, u] = mpfr_matrix_mul_d (magic (3), magic (3)', magic (3) + 1,
> > magic (3)' + 1);
> > assert (l, [101, 71, 53; 71, 83, 71; 53, 71, 101]);
> > assert (u, [134, 104, 86; 104, 116, 104; 86, 104, 134]);
> > * test;
> > if (((exist ("__octave_config_info__") && ...
> > __octave_config_info__.ENABLE_OPENMP) || ...
> > (not (exist ("__octave_config_info__")) && ...
> > octave_config_info ("features").OPENMP)) ...
> > && nproc ("overridable") > 1)
> > ## OpenMP is enabled and may use more than one thread.
> > ## We should observe speed-ups by that.
> > A = vec (magic (2000));
> > tic;
> > mpfr_matrix_mul_d (A', A, A', A);
> > time_per_element = toc;
> > A = [A A];
> > tic;
> > mpfr_matrix_mul_d (A', A, A', A);
> > time_per_element_parallel = toc / numel (ans);
> >
> > ## Ideally, the runtime would be cut in half (at least),
> > ## however, there is an overhead, so let's be pessimistic and
> > ## assume that the parallel execution is at least 20% faster.
> > assert (time_per_element > 1.2 * time_per_element_parallel)
> > endif
> > ! test failed
> > assert (time_per_element > 1.2 * time_per_element_parallel) failed
> > 2 tests, 1 passed, 0 known failure, 0 skipped
The problem comes from the 2nd test in mpfr_matrix_mul_d.cc, which
fails if the buildd is heavily loaded (because the speedup of
parallelization does not materialize).
I think this test should be patched out for Debian.
Oliver, what do you think?
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄ http://www.debian.org
signature.asc
Description: This is a digitally signed message part
Bug#918670: node-duplexer3 FTBFS with nodejs 10.15.0
Source: node-duplexer3 Version: 0.1.4-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-duplexer3.html ... debian/rules override_dh_auto_test make[1]: Entering directory '/build/1st/node-duplexer3-0.1.4' mocha -R tap 1..13 ok 1 duplexer3 should interact with the writable stream properly for writing ok 2 duplexer3 should interact with the readable stream properly for reading ok 3 duplexer3 should end the writable stream, causing it to finish ok 4 duplexer3 should finish when the writable stream finishes ok 5 duplexer3 should end when the readable stream ends ok 6 duplexer3 should bubble errors from the writable stream when no behaviour is specified ok 7 duplexer3 should bubble errors from the readable stream when no behaviour is specified ok 8 duplexer3 should bubble errors from the writable stream when bubbleErrors is true ok 9 duplexer3 should bubble errors from the readable stream when bubbleErrors is true ok 10 duplexer3 should not bubble errors from the writable stream when bubbleErrors is false ok 11 duplexer3 should not bubble errors from the readable stream when bubbleErrors is false ok 12 duplexer3 should export the DuplexWrapper constructor not ok 13 duplexer3 should not force flowing-mode AssertionError [ERR_ASSERTION]: false == null at Context. (test/tests.js:176:12) at callFnAsync (/usr/lib/nodejs/mocha/lib/runnable.js:377:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:324:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at /usr/lib/nodejs/mocha/lib/runner.js:329:7 at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7) at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) # tests 13 # pass 12 # fail 1 make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
Bug#918674: osmo-hlr FTBFS on big endian: test failure
Source: osmo-hlr Version: 0.2.1-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=osmo-hlr ... /bin/bash './testsuite' ## ## ## osmo-hlr UNKNOWN test suite. ## ## ## Regression tests. 1: auc FAILED (testsuite.at:8) 2: auc_ts_55_205_test_sets ok 3: gsupok 4: gsup_server ok 5: db ok ## - ## ## Test results. ## ## - ## ERROR: All 5 tests were run, 1 failed unexpectedly.
Bug#918616: marked as done (octave: missing build dependency on libglu1-mesa-dev)
Your message dated Tue, 08 Jan 2019 10:17:32 +
with message-id
and subject line Bug#918616: fixed in octave 4.4.1-4
has caused the Debian Bug report #918616,
regarding octave: missing build dependency on libglu1-mesa-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.)
--
918616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave
Version: 4.4.1-3
Severity: serious
Tags: ftbfs
On most architectures qtbase5-dev happens to depend on libglu1-mesa-dev
so this bug is hidden, but not on armel/armhf where Qt uses OpenGL ES:
https://buildd.debian.org/status/package.php?p=octave=sid
...
checking for GL/gl.h... yes
checking for GL/glu.h... no
checking for OpenGL/glu.h... no
configure: WARNING: OpenGL libs (GL and GLU) not found. OpenGL graphics will
be disabled.
...
# Run builtin-features to ensure important features are included
env OCTAVE=./run-octave debian/tests/builtin-features
error: assert (__have_feature__ ('OPENGL')) failed
make[1]: *** [debian/rules:64: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 4.4.1-4
We believe that the bug you reported is fixed in the latest version of
octave, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sébastien Villemot (supplier of updated octave package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 08 Jan 2019 10:30:45 +0100
Source: octave
Binary: octave octave-common octave-doc octave-htmldoc octave-info liboctave6
liboctave-dev
Architecture: source
Version: 4.4.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group
Changed-By: Sébastien Villemot
Description:
liboctave-dev - development files for the GNU Octave language
liboctave6 - shared libraries of the GNU Octave language
octave - GNU Octave language for numerical computations
octave-common - architecture-independent files for octave
octave-doc - documentation of the GNU Octave language
octave-htmldoc - transitional package for Octave HTML documentation
octave-info - transitional package for Octave info documentation
Closes: 918616
Changes:
octave (4.4.1-4) unstable; urgency=medium
.
* Add libglu1-mesa-dev to Build-Depends. This is necessary to have
OpenGL support on armel and armhf (on other archs, it is pulled in by
qtbase5-dev). Thanks to Adrian Bunk (Closes: #918616)
Checksums-Sha1:
10cf75ed80401e19300835778e5cd8044a2e5b4b 3393 octave_4.4.1-4.dsc
7e08e8f14398426745bfe238c8ac6094ef712d39 75884 octave_4.4.1-4.debian.tar.xz
fb70b6dea4ed9c4c565b2b8dd7f8e595946ea91a 20697 octave_4.4.1-4_source.buildinfo
Checksums-Sha256:
02cbd98ef39ff7760bf762ba74c29d1a2ceae3e54a736061549f23835a28dfe7 3393
octave_4.4.1-4.dsc
65914d887bdef43fee9d292e51a8322c6462cf3277ad748d8004691bdfa94992 75884
octave_4.4.1-4.debian.tar.xz
5cbee401284c45c48ccb8c5be4ba01fb885393f1599b6deee33b9f30e1226e28 20697
octave_4.4.1-4_source.buildinfo
Files:
0ba7aa2abf924a098d3b1cac9d047259 3393 math optional octave_4.4.1-4.dsc
589386fa9e1c7550f77b9187e13d8e84 75884 math optional
octave_4.4.1-4.debian.tar.xz
6f4633f0507710b4c5a97a55b61ed61a 20697 math optional
octave_4.4.1-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlw0dMYACgkQLOzpNQ7O
vkpJpg/+LW0GTtuG9JMmT9A+R1/LM5TDI6z5J8HugnRyqHlpT3m8hRQX+JW10iBU
OjHjs+8IaIAKa7alg+8YvMl/HEpQCb/PXDN0irjGWXYah1B+QEchvR0g8h+7EF93
yxPe7k+RCoiuadgaM3ieaMUd2ygLvh+fLJbdNPSHaN/p3oAYQ8Q95AN7RjXoe/Ee
98nqCcfrIuvqbnRrEMwnai3wEv3zMMLdwAhKV+B0kAeOmWCsLzGMY9DAeCa5z7eb
HyxZCBLk+gAbfCWT85c2V2OXzw92OeMFE2WjXPD7kLjd8Hm1Ou5XtFVCComEs3WR
TcGIQlh91GLmkt+EITcEg1T8txhKnsHWvsRBqxdrvI0dGbt58NTOdSBpGC0SUmVZ
rCI4V5PWS3lvytQvyAVETZ2pe/ZildQrgR940G5qZRilHZBRv7nbW+rctsq46CyW
4A8MwmcPwqhKlf1ypFoeSxCBHjaB1FZa2W9rFEDSblJ+1BFp0lCZjYaAG7xHoUQt
RKGhKQn+uMD/xvg2TSm2cuYyY4NcwIGfG0cWwlHyW7vG0R8DSZI4qIAwh4ia0rWR
mGsV4EeFWjniYZyG8+8lApaXzIx+PMBPE4M9wxZEZ/8+Hlfhr5F/Q9FRB90mbhDM
gOV9U7n2dKHVvMbsaikf3mOeK9reXjgBtBstxS4IuiJJH5mUnKI=
=UMx4
-END PGP
Bug#918669: waitress FTBFS: An error happened in rendering the page api. Reason: TemplateNotFound()
Source: waitress Version: 1.2.0~b2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=waitress=all=1.2.0~b2-1=1546883794=0 ... sphinx-build -b html -d _build/doctrees -N -D html_last_updated_fmt="January 07, 2019" . _build/html Running Sphinx v1.7.9 loading pickled environment... not yet created loading intersphinx inventory from https://docs.python.org/3/objects.inv... building [mo]: targets for 0 po files that are out of date building [html]: targets for 12 source files that are out of date updating environment: 12 added, 0 changed, 0 removed reading sources... [ 8%] api reading sources... [ 16%] arguments reading sources... [ 25%] design reading sources... [ 33%] differences reading sources... [ 41%] filewrapper reading sources... [ 50%] glossary reading sources... [ 58%] index reading sources... [ 66%] logging reading sources... [ 75%] reverse-proxy reading sources... [ 83%] runner reading sources... [ 91%] socket-activation reading sources... [100%] usage looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done writing output... [ 8%] api Theme error: An error happened in rendering the page api. Reason: TemplateNotFound() make[2]: *** [Makefile:30: html] Error 2
Processed: found 916415 in 1.0-1
Processing commands for cont...@bugs.debian.org:
> found 916415 1.0-1
Bug #916415 {Done: Dmitry Smirnov } [nocache] nocache
broken with glibc 2.28: several programs just hang in call to futex(...,
FUTEX_WAIT_PRIVATE, 2, NULL)
Marked as found in versions nocache/1.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#917064: marked as done (praat FTBFS on big endian: 2 tests segfault)
Your message dated Tue, 8 Jan 2019 14:21:45 +0200 with message-id <20190108122145.GD13260@localhost> and subject line Fixed since 6.0.46-2 has caused the Debian Bug report #917064, regarding praat FTBFS on big endian: 2 tests segfault 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.) -- 917064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: praat Version: 6.0.43-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=praat ... = test_SpeechSynthesizer_alignment.praat test_SpeechSynthesizer_alignment.praat Segmentation fault ... = test_alignment.praat test_alignment.praat Segmentation fault ... 113 tests passed, 111 ok Failed test(s): test_SpeechSynthesizer_alignment.praat test_alignment.praat make[1]: *** [debian/rules:86: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Version: 6.0.46-2 This bug is fixed since 6.0.46-2: https://buildd.debian.org/status/package.php?p=praat cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Bug#910856: marked as done (sollya: test fails on most architectures)
Your message dated Tue, 08 Jan 2019 12:22:48 + with message-id and subject line Bug#910856: fixed in sollya 7.0+ds-3 has caused the Debian Bug report #910856, regarding sollya: test fails on most architectures 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.) -- 910856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sollya Version: 7.0+ds-2 Severity: normal Tags: upstream Dear Sollya enthusiasts ! It appears that tests fails randomly on most architectures. The issue seems to be an AutoMake scripting issue. Jerome -- System Information: Debian Release: Stretch* APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages sollya depends on: ii libc6 2.24-11+deb9u3 ii libfplll2 5.0.3-1 ii libgmp102:6.1.2+dfsg-1 ii libmpfi01.5.1+ds-4 ii libmpfr43.1.5-1 ii libsollya6 6.0+ds-1 ii libstdc++6 6.3.0-18+deb9u1 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 Versions of packages sollya recommends: ii gnuplot 5.0.5+dfsg1-6+deb9u1 ii rlwrap 0.42-3 Versions of packages sollya suggests: ii libsollya-dev 6.0+ds-1 ii sollya-doc 6.0+ds-1 -- no debconf information --- End Message --- --- Begin Message --- Source: sollya Source-Version: 7.0+ds-3 We believe that the bug you reported is fixed in the latest version of sollya, 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 910...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated sollya package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 Jan 2019 11:56:17 + Source: sollya Binary: sollya libsollya7 libsollya-dev sollya-doc Architecture: source Version: 7.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: libsollya-dev - library for safe floating-point code development -- libdev libsollya7 - library for safe floating-point code development -- lib sollya - library for safe floating-point code development -- tool sollya-doc - library for safe floating-point code development -- doc Closes: 910856 Changes: sollya (7.0+ds-3) unstable; urgency=medium . * FTBFS fix release, no-parallel build as workaround (Closes: #910856). * Debianization: - debian/copyright: - Copyright year tuples, update; - debian/control: - Standards Version, bump to 4.3.0 (no change). Checksums-Sha1: 21170cdb947131fc7d64ec049380f2700d458543 3011 sollya_7.0+ds-3.dsc bc7e6539ccf31b18e1bb5405dd5795a6eacb9528 14876 sollya_7.0+ds-3.debian.tar.xz 787f723a49a2634bdc754895f8f8dc3e7a6c3af8 6735 sollya_7.0+ds-3_source.buildinfo Checksums-Sha256: 1b904def5f400c7b8381bf8352fb918787fb0dac7dfa1b4422528e533d80d102 3011 sollya_7.0+ds-3.dsc 164805dd3443e39e1991cbaf43a4ae85a5f9091f9537e605eb7a064f6c3766b9 14876 sollya_7.0+ds-3.debian.tar.xz 7db4e8eb544c374c395ab789da0bd554d6746dbe6e311b16832d1f4b2d5c8ce4 6735 sollya_7.0+ds-3_source.buildinfo Files: 5d3970b384580ff51e9f705ff1c3e8f8 3011 math optional sollya_7.0+ds-3.dsc 9c0cb2f4d12304ac40904548c33dfa8d 14876 math optional sollya_7.0+ds-3.debian.tar.xz 8b4a61f4028fd369cb065d21ef71232a 6735 math optional sollya_7.0+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAlw0kQ4VHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaL+kogAJ+zCuawooh5R3c0kDBcwupXR/IZ MJSxS55/IuV2JTOyoVs8OGM40mzT7stryowR7bqPLbVQeTVg23aoZc+NMYt0/S2g pbsPHPcRxiUVAl+PbIqlxLFdgoRZBhTdXkktzy+2rSYy2Wz0ftlkykrM4okb2PGY 0Kj707wgGz6R3BZGTRXIyNbp8nQkj2P2uYYS+CVB6iVoMx8kddfA9E5k4t8sJVhz qer1ycKFqy67GED8E6BL/4/GhaJXcrKWzUxiI1eZahNJGfvnUZmybSb3k6oPpoEG IZ0eSqFQwrPJ2hnARasAl3JWTSBLvDYEXq9lDKhW1pTZDysDT0k7UOs4PY+/bcnV
Bug#911285: Current version is incompatible with Thunderbird 60
Please disregard my prior email, because > > > A new upstream version exists, that should be compatible. this is no longer true. The current version of this extension does not work with the current Thunderbird version. Therefore there is no point in upgrading. > > The package wasn't updated for a year, shall we remove it? Yes. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
Bug#913369: pluto-jpl-eph: diff for NMU version 0.0~git20180228-1.1
Hi Adrian, On 08.01.19 13:00, Adrian Bunk wrote: Control: tags 913369 + patch Control: tags 913369 + pending I've prepared an NMU for pluto-jpl-eph (versioned as 0.0~git20180228-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. Thank you for your interest in the pluto-* packages. The package is team maintained on https://salsa.debian.org/debian-astro-team/pluto-jpl-eph I would appreciate if that resource would be used and I cordially invite you to help with co-maintenance. The package is a bit tricky in that Upstream only evolves over time to get his bits separated to independent parts and some circular dependencies are ambiguous to dissect and may even have changed over time. That is why first uploads of pluto-* went to experimental. Support in transitioning it all to unstable is very welcome. Best, Steffen
Bug#918566: Lost of code copies of MurmurHash3 (Was: Bug#918566: mash FTBFS on big endian: test failures)
Cool. Thanks a lot, Andreas. On Tue, Jan 08, 2019 at 12:56:55PM +0100, Fabian Klötzl wrote: > Hi, > > There are 162 packages in Debian containing the string MurmurHash. Some > of them use an implementation called PMurHash which fixes the endianess > issue. > > On 07.01.19 16:42, Andreas Tille wrote: > > It seems to be time to package MurmurHash3 separately, isn't it? > > Yeah, I think it makes sense to create a libmurmurhash package and then > have all "bad" implementations link against that. I will look at some > oof the code and start a project. > > Best, > Fabian > -- http://fam-tille.de
