Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Just one precison, I'm using GDM (not sddm) and have the same issue. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#796310: libgraphicsmagick3: --with-quantum-depth=16 breaks ABI
Hi Niels, Bob, others, On Fri, Sep 25, 2015 at 8:34 AM, Niels Thykier wrote: > Thanks for getting it uploaded to NEW. > > I have prodded the FTP masters about fast tracking and will try to > finish the resulting transition as fast as possible. :) Now it's accepted, built fine on almost all architectures and the tracker seems to be correct. It fails on mipsel[1] with: -- cut -- Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"... /«PKGBUILDDIR»/scripts/tap-functions.shi: line 58: 2290 Aborted ( "$@" ) EXEC: ./rwfile -stdio -filespec out_truecolor_stdio_%d /«PKGBUILDDIR»/tests/input_truecolor.miff PCDS not ok 244 - PCDS truecolor (stdio) FAIL: tests/rwfile.tap 244 - PCDS truecolor (stdio) -- cut -- It was failed previously a few times as well, but a rescheduled build solved it. To be honest the reasons were: signal 01 (SIGBUS) "Bus Error" But I suspect the cause may be the same, please reschedule the build of graphicsmagick on mipsel. The build is strange on mips just for the record. Sometimes (just like in the past) it builds in a hour. Nowadays it's over twelve hours sometimes, but it seems to be at lease six hours[2]. Bob, how may I help you to find the root cause of the slow building on mips at least? Thanks, Laszlo/GCS [1] https://buildd.debian.org/status/fetch.php?pkg=graphicsmagick&arch=mipsel&ver=1.3.21-4&stamp=1443407301 [2] https://buildd.debian.org/status/logs.php?pkg=graphicsmagick&arch=mips
Bug#800118: binary directory problems loading mods
Control: severity -1 minor Hi, Am Samstag, den 26.09.2015, 21:49 -0430 schrieb PICCORO McKAY Lenz: > Severity: grave there is a policy regarding bug severities: https://www.debian.org/Bugs/Developer#severities This does not even remotely justify for a release-critical severity. > debian oficial yquake set base directory to binary installed engine > at /usr/lib/yamagi-quake2/ but last 5.30 release already set that > as changelog describes.. Alright, so this doesn't seem too wrong. > so i think this cause a problem, with debian package 5.21 or my > own build of 5.31 i can load doom2 mod but with the debian 5.30 > i cannot load, and got and error: How do you exactly attempt to load this mod? > When i installed the mod doom2 as root in the base lib dir (as > defined in rules) > the mod loads! ( i put the doom2 directory in the binary dir a side > baseq2) So, if you install the mod into the game data directory, it loads? This doesn't seem wrong to me, but I guess you want to load it from a user -writable directory, right? > I think the game path must not be set or maybe the system may change I have no idea what this is supposed to mean? > i still not report that to the upstream due i build a unchanged > binary and works How did you build an unchanged binary? What is required in the Debian packaging to make loading mods from directories outside the hard-coded data paths work? Thank you! - Fabian PS: It is not necessary to include the pkg-games-devel list in the bug's CC, bugs maintained by the Debian Games Team are reported to a public list anyway. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#800118: binary directory problems loading mods
Processing control commands: > severity -1 minor Bug #800118 [yamagi-quake2] binary directory problems loading mods Severity set to 'minor' from 'grave' -- 800118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#779703: marked as done (isort is missing build dependencies, trying to download from pypi)
Your message dated Mon, 28 Sep 2015 04:49:07 + with message-id and subject line Bug#779703: fixed in isort 4.2.2+ds1-1 has caused the Debian Bug report #779703, regarding isort is missing build dependencies, trying to download from pypi 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.) -- 779703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:isort Version: 3.9.2+ds1-1 Severity: serious Tags: sid without network connection, the package fails to build: dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: python3.4 setup.py test running test Searching for pies>=2.6.0 Reading https://pypi.python.org/simple/pies/ Download error on https://pypi.python.org/simple/pies/: [Errno 111] Connection refused -- Some packages may not be found! Couldn't find index page for 'pies' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading https://pypi.python.org/simple/ Download error on https://pypi.python.org/simple/: [Errno 111] Connection refused -- Some packages may not be found! No local packages or download links found for pies>=2.6.0 error: Could not find suitable distribution for Requirement.parse('pies>=2.6.0') E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: python3.4 setup.py test dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 13 --- End Message --- --- Begin Message --- Source: isort Source-Version: 4.2.2+ds1-1 We believe that the bug you reported is fixed in the latest version of isort, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tristan Seligmann (supplier of updated isort package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Sep 2015 05:43:58 +0200 Source: isort Binary: isort python3-isort Architecture: source all Version: 4.2.2+ds1-1 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Tristan Seligmann Description: isort - utility for sorting Python imports python3-isort - library for sorting Python imports Closes: 779703 Changes: isort (4.2.2+ds1-1) unstable; urgency=medium . * New upstream release. - Dropped dependency on python3-pies (closes: #779703 -- although I cannot confirm this due to being unable to reproduce in the first place). * Add a .pydist file. * Drop override as upstream now ships a changelog. * Actually run tests during build. Checksums-Sha1: 140430d8083b0e9b2c6a68afee64a175c367a9a5 1843 isort_4.2.2+ds1-1.dsc 475c3b08229491dbd966b9c02cdf5c60a842fef0 135231 isort_4.2.2+ds1.orig.tar.gz ce3cd7c1f0d2cbc67ab36d417901b7a682024286 4012 isort_4.2.2+ds1-1.debian.tar.xz 856224ba2b4587c4de75632c1427429417e84ae7 5566 isort_4.2.2+ds1-1_all.deb 410795bcf6c9f982865942bec40dc0ed62bb476a 36626 python3-isort_4.2.2+ds1-1_all.deb Checksums-Sha256: 80268cc24a0dc27dad5d12d4479f292bb0a101b0e48636343f363a70fd7b6603 1843 isort_4.2.2+ds1-1.dsc 553ee995e8c2781fe5765bbc13f08ce4d53462d594d7bb05b2364ca8e13947cc 135231 isort_4.2.2+ds1.orig.tar.gz f33e9e6c4b720346c401d84f1f94780c86c95c04574f3230ee9e0227580da435 4012 isort_4.2.2+ds1-1.debian.tar.xz e817e33a99f143bfc2ec915a5bf3d27e2a3219bab5e074f15d5313d5e242b8aa 5566 isort_4.2.2+ds1-1_all.deb aa31b96d72eaf5d70641d330895e1d41321d91da1c41e87dd6192bb058915760 36626 python3-isort_4.2.2+ds1-1_all.deb Files: 680b86119f089f839d098024b4363c92 1843 python optional isort_4.2.2+ds1-1.dsc 2141e84575a015685b6408cca174f864 135231 python optional isort_4.2.2+ds1.orig.tar.gz 0cfaec149cf08b11aa3c917060249026 4012 python optional isort_4.2.2+ds1-1.debian.tar.xz 8e51bc0c4ec276bf9ffd07ce4acfbb82 5566 python optional isort_4.2.2+ds1-1_all.deb ab5acd4fb4fc48e5462ed07afa4800a8 36626 python optional python3-isort_4.2.2+ds1-1_all.deb -BEGIN PGP SIGNATURE- iQF8BAEBCgBmBQJWCML0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1QzA2NTY4NTc1NTE2RDB
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 779703 + pending Bug #779703 [src:isort] isort is missing build dependencies, trying to download from pypi Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 779703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#796310: marked as done (libgraphicsmagick3: --with-quantum-depth=16 breaks ABI)
Your message dated Mon, 28 Sep 2015 01:00:11 + with message-id and subject line Bug#796310: fixed in graphicsmagick 1.3.21-4 has caused the Debian Bug report #796310, regarding libgraphicsmagick3: --with-quantum-depth=16 breaks ABI 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.) -- 796310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgraphicsmagick3 Version: 1.3.20-4 Severity: serious As I said in #795102, building with QuantumDepth=16 breaks the ABI. Please either revert the QuantumDepth change, or change the SONAME. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: graphicsmagick Source-Version: 1.3.21-4 We believe that the bug you reported is fixed in the latest version of graphicsmagick, 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 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated graphicsmagick 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, 21 Sep 2015 18:10:49 +0200 Source: graphicsmagick Binary: graphicsmagick libgraphicsmagick-q16-3 libgraphicsmagick1-dev libgraphicsmagick++-q16-11 libgraphicsmagick++1-dev libgraphics-magick-perl graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat graphicsmagick-dbg Architecture: source amd64 all Version: 1.3.21-4 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: graphicsmagick - collection of image processing tools graphicsmagick-dbg - format-independent image processing - debugging symbols graphicsmagick-imagemagick-compat - image processing tools providing ImageMagick interface graphicsmagick-libmagick-dev-compat - image processing libraries providing ImageMagick interface libgraphics-magick-perl - format-independent image processing - perl interface libgraphicsmagick++-q16-11 - format-independent image processing - C++ shared library libgraphicsmagick++1-dev - format-independent image processing - C++ development files libgraphicsmagick-q16-3 - format-independent image processing - C shared library libgraphicsmagick1-dev - format-independent image processing - C development files Closes: 796307 796310 Changes: graphicsmagick (1.3.21-4) unstable; urgency=low . * Change C library name to ending with -q16 for QuantumDepth=16 ABI change and compile shared library to include the QuantumDepth value (closes: #796310). * Remove breaks on pdf2djvu. * Make rebuildable (closes: #796307). . [ Jakub Wilk ] * Remove obsolete conflicts/replaces on libgraphicsmagick. * Version conflicts/replaces on libgraphicsmagick3. * No longer need to pass -l and -L switches to dh_shlibdeps. Checksums-Sha1: 706f40ef99d96ba1756800ed7c739121c9cadaf0 2795 graphicsmagick_1.3.21-4.dsc d6ae03b577250d620112a5d9dd6ec91d709653fa 136316 graphicsmagick_1.3.21-4.debian.tar.xz 38564d2ec79197c66facc792f9ca5a8d65eeb52c 2983412 graphicsmagick-dbg_1.3.21-4_amd64.deb 3cf5524879c71dfc24a13f86658d86461af7eb2d 22926 graphicsmagick-imagemagick-compat_1.3.21-4_all.deb 80e4b58015eb4faf506e29c841fbcbcd9c68c62f 26382 graphicsmagick-libmagick-dev-compat_1.3.21-4_all.deb 5618233e64dcf776e2571bcac0c1557408c7442b 797460 graphicsmagick_1.3.21-4_amd64.deb d1545ccd537a390090b38b2c5670745d2b4959bc 71278 libgraphics-magick-perl_1.3.21-4_amd64.deb 0478110b9a012333e770e4a98b88020090371f35 117376 libgraphicsmagick++-q16-11_1.3.21-4_amd64.deb 79dcea44f8b4ab8492bcd04f1149c4aebab107ce 299468 libgraphicsmagick++1-dev_1.3.21-4_amd64.deb 51258a24c21de5909d29705350cf701d1e5d719c 1103032 libgraphicsmagick-q16-3_1.3.21-4_amd64.deb 51039ed53115178fffe8fa6e1fa954c8fcdf92c1 1289646 libgraphicsmagick1-dev_1.3.21-4_amd64.deb Checksums-Sha256: 96420c217cf3bc881bd27520ead05854f2cda6fc7b00f26ca28b2a9818e9a263 2795 graphicsmagick_1.3.21-4.dsc 58570830acfe876ad8701db4e692d2035411a963500c0ddf2a45699b942da8d3 136316 graphicsmagick_1.3.21-4.debian.tar.xz 824b6a440e19dfbb361c698d73a8ece2deade025a0c44de0b506586fc74d7a
Bug#799937: closing 799937
close 799937 2:4.1.20+dfsg-1+b1 thanks Scheduled binNMU to pick up the correct version (which is available on mips/ mipsel now).
Processed: closing 799937
Processing commands for cont...@bugs.debian.org: > close 799937 2:4.1.20+dfsg-1+b1 Bug #799937 [samba-libs] samba-libs: mips and mipsel packages are build against the worng libldb1 package There is no source info for the package 'samba-libs' at version '2:4.1.20+dfsg-1+b1' with architecture '' Unable to make a source version for version '2:4.1.20+dfsg-1+b1' Marked as fixed in versions 2:4.1.20+dfsg-1+b1. Bug #799937 [samba-libs] samba-libs: mips and mipsel packages are build against the worng libldb1 package Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 799937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 751241 is forwarded to https://github.com/amule-project/amule/issues/2
Processing commands for cont...@bugs.debian.org: > forwarded 751241 https://github.com/amule-project/amule/issues/2 Bug #751241 [src:amule] amule: Please update to use wxwidgets3.0 Set Bug forwarded-to-address to 'https://github.com/amule-project/amule/issues/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 751241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800239: marked as done (py3cairo: FTBFS with python3.5 as a supported python3 version)
Your message dated Sun, 27 Sep 2015 23:18:50 + with message-id and subject line Bug#800239: fixed in py3cairo 1.10.0+dfsg-5 has caused the Debian Bug report #800239, regarding py3cairo: FTBFS with python3.5 as a supported python3 version 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.) -- 800239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: py3cairo Version: 1.10.0+dfsg-4 Severity: serious Justification: fails to build from source (but built successfully in the past) py3cairo FTBFS when binNMUed to add support for python3.5. Here's what appears to be the relevant bit of the build log: Checking for library python3.5 in LIBDIR : 06:20:11 runner ['/usr/bin/gcc', '-D_FORTIFY_SOURCE=2', '-g', '-O2', '-fstack-protector-strong', '-Wformat', '-Werror=format-security', '-pthread', '-fwrapv', '-fstack-protector-strong', '-flto', '-fuse-linker-plugin', '-ffat-lto-objects', '-DPYTHONDIR="/usr/lib/python3/dist-packages"', '-DPYTHONARCHDIR="[\'/usr/lib/python3/dist-packages\']"', '-DNDEBUG', '../test.c', '-c', '-o', 'test.c.0.o'] 06:20:11 runner ['/usr/bin/gcc', 'test.c.0.o', '-o', '/«BUILDDIR»/py3cairo-1.10.0+dfsg/build3.5/.conf_check_48bc0baa924006e4ec070860d537efdb/testbuild/testprog', '-Wl,-Bstatic', '-Wl,-Bdynamic', '-L/usr/lib', '-lpython3.5', '-Wl,-z,relro', '-Wl,-z,relro', '-pthread', '-Wl,-O1', '-Wl,-Bsymbolic-functions', '-Wl,-z,relro'] ./options() ./configure() Traceback (most recent call last): File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 93, in waf_entry_point run_commands() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 145, in run_commands run_command(cmd_name) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 138, in run_command ctx.execute() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 124, in execute super(ConfigurationContext,self).execute() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Context.py", line 87, in execute self.recurse([os.path.dirname(g_module.root_path)]) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Context.py", line 127, in recurse user_function(self) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/wscript", line 29, in configure ctx.check_python_headers() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/python.py", line 146, in check_python_headers result=conf.check(lib=name,uselib='PYEMBED',libpath=path,mandatory=False,msg='Checking for library %s in LIBDIR'%name) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/c_config.py", line 357, in check ret=self.run_c_code(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/c_config.py", line 435, in run_c_code bld.compile() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/errcheck.py", line 95, in check_compile ret=old_compile(self) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Build.py", line 190, in compile self.store() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Utils.py", line 300, in f ret=fun(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Build.py", line 164, in store cPickle.dump(data,f) AttributeError: Can't pickle local object 'Context.__init__..node_class' It does look like there is a fix for this in Ubuntu [1]. Scott K [1] https://launchpad.net/ubuntu/+source/py3cairo/1.10.0+dfsg-4ubuntu2 --- End Message --- --- Begin Message --- Source: py3cairo Source-Version: 1.10.0+dfsg-5 We believe that the bug you reported is fixed in the latest version of py3cairo, 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 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated py3cairo 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
Bug#759044: forward to upstream.
On Tue, Sep 15, 2015 at 11:29:00PM +0200, Moritz Mühlenhoff wrote: > On Tue, Sep 23, 2014 at 10:26:56PM +0800, Ying-Chun Liu (PaulLiu) wrote: > > forwarded 759044 https://github.com/Tribler/tribler/issues/875 > > thanks > > So apparently upstream doesn't have the time to work on this. > > A year later, shall we go ahead with the removal of tribler? It's > one of the last two packages blocking the removal of WX 2.8. That sounds appropriate to me - I can see no evidence of any progress on this in the last year. The upstream ticket has just been repeated repegged onto later and later milestones. The last wx 2.8 release (2.8.12) was 4.5 years ago (to the day!) while wx 3.0 is approaching 2 years old. It doesn't seem an unrealistic expectation to expect upstreams to support it by now. Upstream don't even seem to have looked at my patch to improve wx3 compatibility while maintaining support for wx2.8, which would at least be a first step towards getting this to work, and give some indication that they actually care. Cheers, Olly
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 800239 + pending Bug #800239 [src:py3cairo] py3cairo: FTBFS with python3.5 as a supported python3 version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 800239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations
Hi Aurelien, On 27.09.2015 23:10, Aurelien Jarno wrote: > On 2015-09-27 20:37, Andreas Cadhalpun wrote: > Thanks for the detailed testcase. I have been able to reproduce the > issue on mipsel, but not on mips. Indeed, this test case only works on mipsel. However, the same tests of ffmpeg's testsuite fail on mips, just with different checksums. So it likely has the same cause. >> This works correctly with gcc-5 5.2.1-16, so it is a regression in 5.2.1-17. >> The changelog reveals: >> [ Aurelien Jarno ] >> * Use --with-mips-plt on mips*. >> * Build for R2 ISA on mips, mips64 and mips64el. >> * Optimize for R2 ISA on mipsel. >> * Only apply mips-fix-loongson2f-nop on mipsel. >> >> I assume one of these changes is responsible for this regression. > > Indeed. At least on mipsel the issue is due to the use of > -mtune=mips32r2 by default. I guess the best is to change it back to > -mtune=mips32 until we better understand the issue. OK. > Does someone have time to look at the issue more in details? The > generated code is quite different between -mtune=mips32 and > -mtune=mips32r2 (not in terms of instructions, but in terms of > sequencing). > > As for mips, given I am not able to reproduce the issue, my guess is > that it's due to the switch to -march=mips32r2, but I currently have > no way to make sure. A slightly larger test case for mips is compiling ffmpeg... Best regards, Andreas
Bug#799948: Fixes (for me)
On Sun, 2015-09-27 at 19:25 +0200, Diederik de Haas wrote: > On Saturday 26 September 2015 10:47:13 Guy Roussin wrote: > > adduser sddm video > > This fixed the issue for me too. Same here. Kind regards, Luca Boccassi
Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations
On 2015-09-27 20:37, Andreas Cadhalpun wrote: > Package: gcc-5 > Version: 5.2.1-17 > Severity: serious > Justification: causes ffmpeg to FTBFS > Control: affects -1 ffmpeg > X-Debbugs-Cc: Aurelien Jarno , > debian-m...@lists.debian.org > > > Dear Maintainer, > > ffmpeg 7:2.8-1 failed to build on mips/mipsel due to test failures. > > I investigated the problem and it turns out to be caused by a compiler bug > that can be avoided by using '-fno-expensive-optimizations'. > > Attached is a reduced test case: > $ ls > Makefile main.c test.c > $ make > cc -fPIC -O2 -fno-expensive-optimizations -c -o working.o test.c > cc -shared -o libworking.so working.o > cc -o working main.c -L. -lworking > cc -fPIC -O2 -c -o broken.o test.c > cc -shared -o libbroken.so broken.o > cc -o broken main.c -L. -lbroken > LD_LIBRARY_PATH=. ./working || true > TEST: 0x12A15 > working > LD_LIBRARY_PATH=. ./broken || true > TEST: 0x1 > broken Thanks for the detailed testcase. I have been able to reproduce the issue on mipsel, but not on mips. > This works correctly with gcc-5 5.2.1-16, so it is a regression in 5.2.1-17. > The changelog reveals: > [ Aurelien Jarno ] > * Use --with-mips-plt on mips*. > * Build for R2 ISA on mips, mips64 and mips64el. > * Optimize for R2 ISA on mipsel. > * Only apply mips-fix-loongson2f-nop on mipsel. > > I assume one of these changes is responsible for this regression. Indeed. At least on mipsel the issue is due to the use of -mtune=mips32r2 by default. I guess the best is to change it back to -mtune=mips32 until we better understand the issue. Does someone have time to look at the issue more in details? The generated code is quite different between -mtune=mips32 and -mtune=mips32r2 (not in terms of instructions, but in terms of sequencing). As for mips, given I am not able to reproduce the issue, my guess is that it's due to the switch to -march=mips32r2, but I currently have no way to make sure. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags #793987 moreinfo Bug #793987 [xul-ext-torbirdy] xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0 Added tag(s) moreinfo. > tags #793987 unreproducible Bug #793987 [xul-ext-torbirdy] xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0 Added tag(s) unreproducible. > severity 793987 normal Bug #793987 [xul-ext-torbirdy] xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0 Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 793987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797483: closed by Varun Hiremath (Bug#797483: fixed in python-enable 4.5.1-2)
On Sat, Sep 26, 2015 at 9:51 PM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the python-enable package: > > #797483: python-enable: AGG renderer segfaults if built with optimization > > It has been closed by Varun Hiremath . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Varun Hiremath < > va...@debian.org> by > replying to this email. > > > -- > 797483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797483 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Forwarded message -- > From: Varun Hiremath > To: 797483-cl...@bugs.debian.org > Cc: > Date: Sun, 27 Sep 2015 04:49:39 + > Subject: Bug#797483: fixed in python-enable 4.5.1-2 > Source: python-enable > Source-Version: 4.5.1-2 > > We believe that the bug you reported is fixed in the latest version of > python-enable, 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 797...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Varun Hiremath (supplier of updated python-enable > 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, 27 Sep 2015 00:33:58 -0400 > Source: python-enable > Binary: python-enable > Architecture: source amd64 > Version: 4.5.1-2 > Distribution: unstable > Urgency: medium > Maintainer: Debian Python Modules Team < > python-modules-t...@lists.alioth.debian.org> > Changed-By: Varun Hiremath > Description: > python-enable - Drawing and interaction packages > Closes: 797483 > Changes: > python-enable (4.5.1-2) unstable; urgency=medium > . >[ Philip Chimento ] >* Add patch to build package without optimization (Closes: #797483) > Checksums-Sha1: > b4dabe179378b69abd6b4552c3d0903ccfc1d54f 2172 python-enable_4.5.1-2.dsc > af9e9053f6842f4616e941ba1a0be93a00fd7a9f 12280 > python-enable_4.5.1-2.debian.tar.xz > 05163b0d33c43f2d146db453d81322e49a650bbb 612156 > python-enable_4.5.1-2_amd64.deb > Checksums-Sha256: > ba8247b999feda8a9812f726b8c4addbb7a6ebbd6adf0c71c6703be555cfdb14 2172 > python-enable_4.5.1-2.dsc > 8d4ac884a039de637c987ef0269e720d5a28118cf9f2c91d81bb6f96a378a4cd 12280 > python-enable_4.5.1-2.debian.tar.xz > 4f59074466901af84dc668865ac8be780b5a9007de859f51427ba3439d134e85 612156 > python-enable_4.5.1-2_amd64.deb > Files: > 1b5d94c82db9a030b3adffe27328c1ee 2172 python optional > python-enable_4.5.1-2.dsc > 5478ca394824ccabd5a76daef903b4a6 12280 python optional > python-enable_4.5.1-2.debian.tar.xz > 8e20dcde67b5698784f325e5021f850b 612156 python optional > python-enable_4.5.1-2_amd64.deb > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQIcBAEBCgAGBQJWB3T7AAoJEHA3PPEpDbnOBpkP/jXApq68aBFpTs4ju/qX0HKO > 0/RrUpB8VU8XTfFHceIoiCmXtx0K54UtK+YAXyksddrfwsatBr4NvFLcgDPbwyhq > SYxbZJFzFf6bhjSA42GHaFYXUTEFbZ6QTOHKLeQdbWPgyyN8LzVmbYRUd6KFkMV/ > LRgTOlAtayEx4jXF9/aJNo2g5dBE8dT5WC29B1Z49grb/TnlPfzTP0yaZ7a7v431 > LOIq6Ns4TA7IDX4YE+53K3ASr5NEGns0AHtfuE6Nls6VHXCSNdUguwHMudrWZIjJ > zq3p2kPsm66o78J4HEfnupKCq1rheOQ5ouCVXJbiZ3rmnvtfMLxGzFfxKu3IlYD4 > cVimm+Uli5u/BgmzRugPb0m9GPrhRBxnTC7muDIoeLlzV8zf1JOo3L3WeRxTV5k8 > NZTrCsU+E1pBkFMomJvJzjvkYmcRgtktf6N5wp5TtMLYy8x2AYMZRnA0q+SSyldr > HsSTgSOs0ivv8l58yNoOk2ufBGCgju88DSaUGJ+UNdcxIQqhf/tj/w7ECbmgS4Rl > RWgDM3mqG+tsAtfgXyu+V+HM9ExhY2QnY3aEjm7uPkyRZeBThZwShPEHqwve/Qht > 2+BAsxbPOqhcsd6GH9EiKwDqUtCCQmGKjSDjELUcHMOT0yLQrtR7v2vFeptFNFAC > 2gNR3dh0Rt+UKlqcLpqc > =dwuU > -END PGP SIGNATURE- > > -- Forwarded message -- > From: Philip Chimento > To: Debian Bug Tracking System > Cc: > Date: Sun, 30 Aug 2015 16:17:22 -0700 > Subject: python-enable: AGG renderer segfaults if built with optimization > Package: python-enable > Version: 4.3.0-2.1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > See this Ubuntu bug for more information and a minimal example that > reproduces the problem: > https://bugs.launchpad.net/ubuntu/+source/python-chaco/+bug/1145575 > > Apparently building python-enable's AGG renderer with optimization on GCC > later than 4.6 causes it to segfault. This makes python-chaco's image > plots unusable and any applications which use that functionality from Chaco > will crash. > > It may be a compiler bug or it may be that the AGG code does something that > is undefined behaviour, causing GCC t
Processed: cyphesis-cpp: prompting due to modified conffiles which were not modified by the user: /etc/cyphesis/cyphesis.vconf
Processing control commands: > tags -1 confirmed Bug #794948 [cyphesis-cpp] cyphesis-cpp: prompting due to modified conffiles which were not modified by the user: /etc/cyphesis/cyphesis.vconf Added tag(s) confirmed. -- 794948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#794948: cyphesis-cpp: prompting due to modified conffiles which were not modified by the user: /etc/cyphesis/cyphesis.vconf
Control: tags -1 confirmed Andreas, Thanks for letting me know about this problem. It looks like my last fix didn't solve it. I'm looking at making a more-sweeping change in the packaging to solve what seems to be the root cause of this problem. Thanks again for reporting it and for the great details! -Olek
Bug#793987: RC bug, really?
Hi again, i should have tested this earlier... and you too probably :p I just installed Torbirdy 0.1.3-1 from Jessie on Icedove 31.8 in Wheezy. I use Torbirdy 0.1.3-1 on Icedove 31.8 in Jessie too. And there is *no* problem at all in both configs. So, is this really an RC bug? Downgrading this bug accordingly now <333 Updating to the new uostream version would be nice though, i'll see if i can help. cheers! u. signature.asc Description: OpenPGP digital signature
Bug#799276: libnl-3-200: depends on libc6 version that doesn't exist in wheezy-backports
Hi all, Am Donnerstag, 17. September 2015, 15:23:36 schrieb Heiko Stübner: > Am Donnerstag, 17. September 2015, 14:03:52 schrieben Sie: > > Package: libnl-3-200 > > Version: 3.2.24-2~bpo70+1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > I am trying to install keepalived from wheezy-backports on amd64, using: > > apt-get -t wheezy-backports install keepalived > > > > This returns the following error: > > The following packages have unmet dependencies: > >libnl-3-200 : Depends: libc6 (>= 2.14) but 2.13-38+deb7u8 is to be > >installed > >E: Unable to correct problems, you have held broken packages. > > > > Checking dependencies for current libnl-3-200 version in > > > > wheezy-backports (3.2.24-2~bpo70+1), I see: > > Depends: libc6 (>= 2.14) > > > > However, the most recent libc6 version available is 2.13-38+deb7u8. > > > > Since https://packages.debian.org/wheezy-backports/libnl-3-200 shows: > > dep: libc6 (>= 2.13) [s390x] > > > > Embedded GNU C Library: Shared libraries > > also a virtual package provided by libc6-udeb > > > > dep: libc6 (>= 2.13-28) [armhf] > > > > dep: libc6 (>= 2.14) [amd64] > > > > dep: libc6 (>= 2.8) [not amd64, armhf, ia64, s390x] > > > > I am guessing either libc6 >= 2.14 needs to be ported to > > wheezy-backports, or the amd64 dependency should be changed to a lower > > version. > > I guess we'll need to ask Sandro about this dependency, as he is one who did > the backports build. > > I have so far never touched the *-backports at all, so don't really know how > that works. the bug above got reported against libnl-3, but meaning the backported version in wheezy-backports. I just read up that backport-related bugs should be reported to the debian-backports list (included), also see the original #799276 bug. Thanks Heiko
Processed: Re: Bug#789739: libdevel-ebug-perl: FTBFS in sid: test failures
Processing control commands: > retitle -1 libdevel-ebug-perl: FTBFS in sid: test failures Bug #789739 [src:libdevel-ebug-perl] libdevel-ebug-perl: FTBFS in sid: t/ebug.t Changed Bug title to 'libdevel-ebug-perl: FTBFS in sid: test failures' from 'libdevel-ebug-perl: FTBFS in sid: t/ebug.t' -- 789739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#789739: libdevel-ebug-perl: FTBFS in sid: test failures
Control: retitle -1 libdevel-ebug-perl: FTBFS in sid: test failures On Tue, Aug 11, 2015 at 08:48:20PM +0200, gregor herrmann wrote: > On Wed, 24 Jun 2015 00:59:37 +0100, Dominic Hargreaves wrote: > > > Source: libdevel-ebug-perl > > Version: 0.56-1 > > Severity: serious > > Justification: FTBFS > > > > This package FTBFS in a clean sid sbuild setup: > https://reproducible.debian.net/rbuild/unstable/amd64/libdevel-ebug-perl_0.56-1.rbuild.log > > JFTR: > At the moment it fails for me with: > Test Summary Report > --- > t/stack.t (Wstat: 1792 Tests: 29 Failed: 7) > Failed tests: 12, 14-15, 19, 27-29 > Non-zero exit status: 7 This stack.t failure is a different issue from the original ebug.t one. It was probably caused by libdevel-stacktrace-perl 2.-1. AFAICS the test is just hardcoding Devel::StackTrace output so it would probably be enough to just update it to correspond to the new version. This is https://rt.cpan.org/Ticket/Display.html?id=100615 FWIW. Not sure if it's worth having two bugs, retitling this for now. The silence upstream suggests this module might be abandoned? -- Niko Tyni nt...@debian.org
Bug#793987: New package?
Hi Chris, thanks a lot for putting work into this issue. However, it might be interesting to know what exactly you patched there, so that rewviewing would be easier, what do you think? Care to send your patch or use the Git repo? Jake, should this package be co-maintained by pkg-privacy-maintainers? If it's simply about updating from upstream, i can commit to that. Cheers! u. signature.asc Description: OpenPGP digital signature
Bug#732723: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready
Am Donnerstag, den 24.09.2015, 20:35 +0200 schrieb Muammar El Khatib: > On Thu, Sep 24, 2015 at 8:33 PM, Tobias Frost > wrote: > > > > > > Thank you for offering me your help!. > > > > Perfect and thanks for putting in on alioth and I just cloned it. > > One question: As there is not the history imported, may I nuke the > > repository and re-create it using git-buildpackage's import-dscs - > > -debsnap magic? > > > Yes. Go ahead. Today I contacted FTP masters because I think the > debian/copyright file is ok. I will keep you posted about it. > Recreated the repository in the meantime. > Cheers, >
Bug#800318: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations
Package: gcc-5 Version: 5.2.1-17 Severity: serious Justification: causes ffmpeg to FTBFS Control: affects -1 ffmpeg X-Debbugs-Cc: Aurelien Jarno , debian-m...@lists.debian.org Dear Maintainer, ffmpeg 7:2.8-1 failed to build on mips/mipsel due to test failures. I investigated the problem and it turns out to be caused by a compiler bug that can be avoided by using '-fno-expensive-optimizations'. Attached is a reduced test case: $ ls Makefile main.c test.c $ make cc -fPIC -O2 -fno-expensive-optimizations -c -o working.o test.c cc -shared -o libworking.so working.o cc -o working main.c -L. -lworking cc -fPIC -O2 -c -o broken.o test.c cc -shared -o libbroken.so broken.o cc -o broken main.c -L. -lbroken LD_LIBRARY_PATH=. ./working || true TEST: 0x12A15 working LD_LIBRARY_PATH=. ./broken || true TEST: 0x1 broken This works correctly with gcc-5 5.2.1-16, so it is a regression in 5.2.1-17. The changelog reveals: [ Aurelien Jarno ] * Use --with-mips-plt on mips*. * Build for R2 ISA on mips, mips64 and mips64el. * Optimize for R2 ISA on mipsel. * Only apply mips-fix-loongson2f-nop on mipsel. I assume one of these changes is responsible for this regression. Best regards, Andreas -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: mipsel (mips) Kernel: Linux 4.2.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages gcc-5 depends on: ii binutils 2.25.1-3 ii cpp-5 5.2.1-17 ii gcc-5-base5.2.1-17 ii libc6 2.19-22 ii libcc1-0 5.2.1-17 ii libgcc-5-dev 5.2.1-17 ii libgcc1 1:5.2.1-17 ii libgmp10 2:6.0.0+dfsg-7 ii libisl13 0.14-2 ii libmpc3 1.0.3-1 ii libmpfr4 3.1.3-1 ii libstdc++65.2.1-17 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages gcc-5 recommends: ii libc6-dev 2.19-22 Versions of packages gcc-5 suggests: pn gcc-5-doc pn gcc-5-locales pn gcc-5-multilib pn libasan2-dbg pn libatomic1-dbg pn libcilkrts5-dbg pn libgcc1-dbg pn libgomp1-dbg pn libitm1-dbg pn liblsan0-dbg pn libmpx0-dbg pn libquadmath-dbg pn libtsan0-dbg pn libubsan0-dbg -- no debconf information #include #include typedef struct Context { int64_t out; int64_t A; int64_t B; int64_t C; int D; } Context; void init_tables(Context *c, int *table, int brightness, int contrast, int saturation); int main() { int64_t out = 0; Context c = { 0 }; int table[3] = {104597, 132201, 25675}; init_tables(&c, table, 0, 65536, 65536); fprintf(stderr, "TEST: 0x%"PRIX64"\n", c.out); if (c.out == 0x12A15) { printf("working\n"); return 0; } printf("broken\n"); return 1; } CFLAGS += -fPIC -O2 LDFLAGS += -shared all: working broken LD_LIBRARY_PATH=. ./working || true LD_LIBRARY_PATH=. ./broken || true working.o: $(CC) $(CFLAGS) -fno-expensive-optimizations -c -o working.o test.c broken.o: $(CC) $(CFLAGS) -c -o broken.o test.c libworking.so: working.o $(CC) $(LDFLAGS) -o libworking.so working.o libbroken.so: broken.o $(CC) $(LDFLAGS) -o libbroken.so broken.o working: libworking.so $(CC) -o working main.c -L. -lworking broken: libbroken.so $(CC) -o broken main.c -L. -lbroken clean: rm -f working.o libworking.so working broken.o libbroken.so broken #include typedef struct Context { int64_t out; int64_t A; int64_t B; int64_t C; int D; } Context; static uint8_t clip_uint8_c(int a) { if (a&(~0xFF)) return (-a)>>31; else return a; } static void fill_table(uint8_t* table[256 + 2*256], const int elemsize, const int64_t inc, void *y_tab) { int i; uint8_t *y_table = y_tab; y_table -= elemsize * (inc >> 9); for (i = 0; i < 256 + 2*256; i++) { int64_t cb = clip_uint8_c(i-256)*inc; table[i] = y_table + elemsize * (cb >> 16); } } static void fill_gv_table(int table[256 + 2*256], const int elemsize, const int64_t inc) { int i; int off = -(inc >> 9); for (i = 0; i < 256 + 2*256; i++) { int64_t cb = clip_uint8_c(i-256)*inc; table[i] = elemsize * (off + (cb >> 16)); } } static uint16_t roundToInt16(int64_t f) { int r = (f + (1 << 15)) >> 16; if (r < -0x7FFF) return 0x8000; else if (r > 0x7FFF) return 0x7FFF; else return r; } uint8_t yuvTable[1024]; int table_gV[256 + 2*256]; uint8_t *table_rV[256 + 2*256]; uint8_t *table_gU[256 + 2*256]; uint8_t *table_bU[256 + 2*256]; __attribute__((cold)) void init_tables(Context *c, int *table, int brightness, int contrast, int saturation) { int i, dst, base, rbase; const int bpp = c->D; const int yoffs = brightness ? 384 : 326; int64_t crv = tab
Processed: gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations
Processing control commands: > affects -1 ffmpeg Bug #800318 [gcc-5] gcc-5: [mips,mipsel] regression: miscompilation caused by -fexpensive-optimizations Added indication that 800318 affects ffmpeg -- 800318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#799979: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: not found
Processing control commands: > tags -1 confirmed pending Bug #799979 [kodi] /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: not found Added tag(s) confirmed and pending. -- 799979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#799979: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: not found
Control: tags -1 confirmed pending Hi Robert, 2015-09-25 2:31 GMT+02:00 Robert Luberda : > Package: kodi > Version: 15.2~rc1+dfsg1-1 > Severity: serious > > kodi tries to execute > /usr/lib/x86_64-linux-gnu/kodi/kodi.bin > > whereas the program in i386 is installed into > /usr/lib/i386-linux-gnu/kodi/kodi.bin > Thank you for the bug report. I have uploaded the fix to NEW and is waiting for FTP Masters' approval. Cheers, Balint
Bug#799948: Fixes (for me)
On Saturday 26 September 2015 10:47:13 Guy Roussin wrote: > adduser sddm video This fixed the issue for me too. signature.asc Description: This is a digitally signed message part.
Bug#800239: py3cairo: FTBFS with python3.5 as a supported python3 version
Source: py3cairo Version: 1.10.0+dfsg-4 Severity: serious Justification: fails to build from source (but built successfully in the past) py3cairo FTBFS when binNMUed to add support for python3.5. Here's what appears to be the relevant bit of the build log: Checking for library python3.5 in LIBDIR : 06:20:11 runner ['/usr/bin/gcc', '-D_FORTIFY_SOURCE=2', '-g', '-O2', '-fstack-protector-strong', '-Wformat', '-Werror=format-security', '-pthread', '-fwrapv', '-fstack-protector-strong', '-flto', '-fuse-linker-plugin', '-ffat-lto-objects', '-DPYTHONDIR="/usr/lib/python3/dist-packages"', '-DPYTHONARCHDIR="[\'/usr/lib/python3/dist-packages\']"', '-DNDEBUG', '../test.c', '-c', '-o', 'test.c.0.o'] 06:20:11 runner ['/usr/bin/gcc', 'test.c.0.o', '-o', '/«BUILDDIR»/py3cairo-1.10.0+dfsg/build3.5/.conf_check_48bc0baa924006e4ec070860d537efdb/testbuild/testprog', '-Wl,-Bstatic', '-Wl,-Bdynamic', '-L/usr/lib', '-lpython3.5', '-Wl,-z,relro', '-Wl,-z,relro', '-pthread', '-Wl,-O1', '-Wl,-Bsymbolic-functions', '-Wl,-z,relro'] ./options() ./configure() Traceback (most recent call last): File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 93, in waf_entry_point run_commands() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 145, in run_commands run_command(cmd_name) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Scripting.py", line 138, in run_command ctx.execute() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 124, in execute super(ConfigurationContext,self).execute() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Context.py", line 87, in execute self.recurse([os.path.dirname(g_module.root_path)]) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Context.py", line 127, in recurse user_function(self) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/wscript", line 29, in configure ctx.check_python_headers() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/python.py", line 146, in check_python_headers result=conf.check(lib=name,uselib='PYEMBED',libpath=path,mandatory=False,msg='Checking for library %s in LIBDIR'%name) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/c_config.py", line 357, in check ret=self.run_c_code(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Configure.py", line 217, in fun return f(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/c_config.py", line 435, in run_c_code bld.compile() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Tools/errcheck.py", line 95, in check_compile ret=old_compile(self) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Build.py", line 190, in compile self.store() File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Utils.py", line 300, in f ret=fun(*k,**kw) File "/«BUILDDIR»/py3cairo-1.10.0+dfsg/waflib/Build.py", line 164, in store cPickle.dump(data,f) AttributeError: Can't pickle local object 'Context.__init__..node_class' It does look like there is a fix for this in Ubuntu [1]. Scott K [1] https://launchpad.net/ubuntu/+source/py3cairo/1.10.0+dfsg-4ubuntu2
Bug#673844: marked as done (python-edbus: please build-depend on python-dbus-dev)
Your message dated Sun, 27 Sep 2015 15:23:36 + with message-id and subject line Bug#673844: fixed in python-edbus 0.7.3-1.2 has caused the Debian Bug report #673844, regarding python-edbus: please build-depend on python-dbus-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.) -- 673844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-edbus Version: 0.5.0+r49577-1 Severity: wishlist Before python-dbus 1.0.0-1, dbus-python.pc and dbus-python.h were in the main python-dbus package. Since version 1.0.0-1 they have been in a new python-dbus-dev package. To avoid breaking packages like yours, which build-depend on python-dbus and expect to find the header and .pc file, python-dbus temporarily depends on python-dbus-dev. Most users of python-dbus don't need the header or the .pc file, so I would like to remove that dependency (Bug #673779). Please update your build-dependencies: * build-depend on python-dbus-dev for the header and .pc file * if you will build Python 2 binaries, also build-depend on python-dbus * if you will build Python 3 binaries, also build-depend on python3-dbus Thanks, Simon --- End Message --- --- Begin Message --- Source: python-edbus Source-Version: 0.7.3-1.2 We believe that the bug you reported is fixed in the latest version of python-edbus, 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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated python-edbus 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: Thu, 17 Sep 2015 09:53:29 +0100 Source: python-edbus Binary: python-edbus Architecture: source Version: 0.7.3-1.2 Distribution: experimental Urgency: medium Maintainer: Debian Pkg-e Team Changed-By: Simon McVittie Description: python-edbus - Python bindings for the Enlightenment D-Bus wrapper library (edbu Closes: 673844 Changes: python-edbus (0.7.3-1.2) experimental; urgency=medium . * Non-maintainer upload. * Build-depend on python-dbus-dev in addition to python-dbus, allowing python-dbus to drop its dependency on python-dbus-dev (Closes: #673844) Checksums-Sha1: e7bc2eda1954290dace5fa8fbc6c2dd9fdfee614 2141 python-edbus_0.7.3-1.2.dsc 25a1f867babb789fef24d1daa5de3ece58394a57 2320 python-edbus_0.7.3-1.2.debian.tar.xz Checksums-Sha256: 8ab30aad53f0e9a3a01fa3ea8d9bde8a99cbfd928e0a03679ecd7b3213ae7b9b 2141 python-edbus_0.7.3-1.2.dsc 20239729f6e7471c2201abf3e024046f70344efced1b675c00103a4b901d48ac 2320 python-edbus_0.7.3-1.2.debian.tar.xz Files: 5077e1982879fc38a99e5a8ebafb7217 2141 python extra python-edbus_0.7.3-1.2.dsc abf9bc3a69e609e3057e52ac35bd1ba0 2320 python extra python-edbus_0.7.3-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJV/rrZAAoJEE3o/ypjx8yQgsIP/incSM3l+5AExOBYSERrJ1RO Tk7O+iNdJE72O5Zw9IkTJhJW62Y2M3CzxIA4UmreNTYBLdZge6O7wgoL1rwltU83 Sd4lMQFqRO1H6WoRixb7wWJHrnx4UKNYtAJvtBhoxZN7QnJsnoWmwOo/R5cCXNjp QcOV1TnYUPYqg6h34BtmbkWcflLOJFvsVapmLM6hYh3vR2XhkUMzOoDzkc0Gzfls VhUpkZRLQDF+RAHPmhnIvX4WDx+8/ZTEAq7Fpy9NhbYBOW92qstpEKMLAM2tJc99 g4d8FKl8ZnyoYqJUh2oobGQwlr0LIfYwuG7QAW92jDfLYzvsHxmxW7O81OLy0S30 ZvaCMFg7C1QtSLgN+7+UWhGuf6Rx4/tIuGFHZap7qPLGevfNxccmSy95LVrusnVT NWvw/CYCwHgHKeI12rmkhKcVe8RiZSmWOzrVgB2UG5dcp95uZkNTkp1mBRJQWQc4 FNemW4kn9IUQdiSWAq4SrlR70dB/EfcIUHgc07E8/Ml9Cfz4WKs7idu8E41f7JbL KvQAXkZrC+RkhZ3oUXwLtuDeyk3Yzu6creWq5rfBWcjcELS2tNIjuJeTnyCYZU46 qh3Unrjc+o2bQM1UQgn+uHDI/bZMR9JbZPSlVAArDEIzQa+jQw+HTKs1kfSfxXXH 8kcGxas8Y+aOgVh68+B/ =bfDp -END PGP SIGNATURE End Message ---
Bug#673844: marked as done (python-edbus: please build-depend on python-dbus-dev)
Your message dated Sun, 27 Sep 2015 15:23:32 + with message-id and subject line Bug#673844: fixed in python-edbus 0.5.0+r49577-1.2 has caused the Debian Bug report #673844, regarding python-edbus: please build-depend on python-dbus-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.) -- 673844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-edbus Version: 0.5.0+r49577-1 Severity: wishlist Before python-dbus 1.0.0-1, dbus-python.pc and dbus-python.h were in the main python-dbus package. Since version 1.0.0-1 they have been in a new python-dbus-dev package. To avoid breaking packages like yours, which build-depend on python-dbus and expect to find the header and .pc file, python-dbus temporarily depends on python-dbus-dev. Most users of python-dbus don't need the header or the .pc file, so I would like to remove that dependency (Bug #673779). Please update your build-dependencies: * build-depend on python-dbus-dev for the header and .pc file * if you will build Python 2 binaries, also build-depend on python-dbus * if you will build Python 3 binaries, also build-depend on python3-dbus Thanks, Simon --- End Message --- --- Begin Message --- Source: python-edbus Source-Version: 0.5.0+r49577-1.2 We believe that the bug you reported is fixed in the latest version of python-edbus, 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 673...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated python-edbus 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: Thu, 17 Sep 2015 09:52:52 +0100 Source: python-edbus Binary: python-edbus Architecture: source Version: 0.5.0+r49577-1.2 Distribution: unstable Urgency: medium Maintainer: Debian Pkg-e Team Changed-By: Simon McVittie Description: python-edbus - Python bindings for the Enlightenment D-Bus wrapper library (edbu Closes: 673844 Changes: python-edbus (0.5.0+r49577-1.2) unstable; urgency=medium . * Non-maintainer upload. * Build-depend on python-dbus-dev in addition to python-dbus, allowing python-dbus to drop its dependency on python-dbus-dev (Closes: #673844) Checksums-Sha1: a6e21c459e1c8c68f19ba156a4adf2cd54cccf94 2152 python-edbus_0.5.0+r49577-1.2.dsc a6567adf64605254ee656296b587f8f0242ebb71 1908 python-edbus_0.5.0+r49577-1.2.diff.gz Checksums-Sha256: 21a616fd6871bdcc70d658a1751ae1a17b11bbc841fd76e766a850d34b063f28 2152 python-edbus_0.5.0+r49577-1.2.dsc cca71045ed975c7fe0b880bf429c40ba53ce8ce211624f7038c3656e45b6561c 1908 python-edbus_0.5.0+r49577-1.2.diff.gz Files: 12d5fc3cf4fb88d60aa0fde724b2c761 2152 python extra python-edbus_0.5.0+r49577-1.2.dsc a5c35e95460210f8791186e0bd8b789a 1908 python extra python-edbus_0.5.0+r49577-1.2.diff.gz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJV/rrgAAoJEE3o/ypjx8yQrB0P/A0ZVc3PZk5ZXOyH18SeLWgg immjEIKaGV3EXoiPXB/mAvrhX91NGmilY898Qw2hGAk+Z8/AEuVfoHcWiOxIdMt9 qzax6MBfUqfPtTvgBnGo3mDiR0AhTEb34LU9Qk217tTS8DFBD1HcayF8US39t/wc eQNBrhONUOrvk8V//IbVYjVkthqS9kj5QM0CfvDAFrSmcnzBjKih6zHayGxjxjO/ A1ewqFCKZJYKBfDNSj4PF6yKfWgsZ25trovCfNG0LBE+DH6sWoyxtwAmF4waJHqD V6Dqe9bro9fJeAV7jEMaB0IYzUhMt7gJFzeTNFj7roDeFRCrbglUvYV8ZOZuf2b4 hdYpTUPfqN64+nCKTjIbR4GoR+dYb5QgpC2pv2qGMbXuSnG/Z8Z7BllDYvWWIJRZ 1LImEUb7JHwkeiz3Kr/iG5mWRnCe1wt3bLBXZIrFiDM4YRlP5kPUk7uJs5r2czsb r9AnLvkjKDAQSLcrX745fHdf1w5eUawhEpsWIc6FnCnKfQR1HXgctK6dNyyy+vQk AgffKj9l5CnTkfLV9CbtspyKp1Hcx+QkNbjrQMrgdpP4JaehxQbilgBQSbaSsMmE IDhmI2d6a7NtPfgo0JpWGjiISgKe67hLR8Yx1A4oqBWkuMD/M/DWN1KT8OEP5HF1 DcDU6njGTKd0FbB65d+t =64yW -END PGP SIGNATURE End Message ---
Bug#799781: device lock race condition between udev and multipathd may cause systemd to abort system boot
Control: severity -1 important I'm lowering the severity for the reasons below. On Wed, 2015-09-23 at 18:25 +0530, Ritesh Raj Sarraf wrote: > Thank you Niels, for confirming this. I'll now work on the stable > update. I'll ping you (soon) one more time, to verify the stable > update, before I push it to the Debian Security Team. I have a problem here. The fix, that you mentioned for the Shared Lock, does not seem to be committed upstream. Neither master, nor Hannes's suse-fixes branch. There have been many other changes post that commit that are in the repository, which gives me the impression that that change was not pushed. And the current version that you tested (now in Unstable), and confirmed to be working, does not have that fix. https://sources.debian.net/src/multipath-tools/0.5.0%2Bgit0.770e6d0d-3/ libmultipath/configure.c/#L545 So I guess the question here is, does and if the shared lock have a side effect ? And if you have not run into the same problem with the version in Unstable/Experimental, what exactly fixed it ? -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#799781: device lock race condition between udev and multipathd may cause systemd to abort system boot
Processing control commands: > severity -1 important Bug #799781 [multipath-tools] device lock race condition between udev and multipathd may cause systemd to abort system boot Severity set to 'important' from 'critical' -- 799781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800142: docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name
> [..] neither an autoreconf fan [..] How come? > (patches are *really* welcome, because I really have difficulties in > maintaining such buildsystem) Sure, coming up.. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Same for me. I confirm that reverting glx-diversion and *nvidia* from unstable to testing fixes this issue. > sudo apt-get install -t testing glx-alternative-nvidia/testing > glx-diversions/testing nvidia-kernel-dkms/testing nvidia-driver/testing > nvidia-driver-bin/testing xserver-xorg-video-nvidia/testing > libegl1-nvidia/testing nvidia-vdpau-driver/testing libgles1-nvidia/testing > libnvidia-eglcore/testing libnvidia-eglcore/testing Didn't tried the Guy suggestion. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Processed: Re: clang should use the new CXX11_ABI
Processing control commands: > forwarded -1 https://llvm.org/bugs/show_bug.cgi?id=23529 Bug #797917 [clang-3.5] clang should use the new CXX11_ABI Set Bug forwarded-to-address to 'https://llvm.org/bugs/show_bug.cgi?id=23529'. > found -1 clang-3.4/1:3.4.2-15 Bug #797917 [clang-3.5] clang should use the new CXX11_ABI The source clang-3.4 and version 1:3.4.2-15 do not appear to match any binary packages Marked as found in versions clang-3.4/1:3.4.2-15. > found -1 clang-3.6/1:3.6.2-1 Bug #797917 [clang-3.5] clang should use the new CXX11_ABI The source clang-3.6 and version 1:3.6.2-1 do not appear to match any binary packages Marked as found in versions clang-3.6/1:3.6.2-1. > found -1 clang-3.7/1:3.7-2 Bug #797917 [clang-3.5] clang should use the new CXX11_ABI The source clang-3.7 and version 1:3.7-2 do not appear to match any binary packages Marked as found in versions clang-3.7/1:3.7-2. > found -1 clang-3.8/1:3.8~svn247576-1 Bug #797917 [clang-3.5] clang should use the new CXX11_ABI The source clang-3.8 and version 1:3.8~svn247576-1 do not appear to match any binary packages Marked as found in versions clang-3.8/1:3.8~svn247576-1. -- 797917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797917: clang should use the new CXX11_ABI
Control: forwarded -1 https://llvm.org/bugs/show_bug.cgi?id=23529 Control: found -1 clang-3.4/1:3.4.2-15 Control: found -1 clang-3.6/1:3.6.2-1 Control: found -1 clang-3.7/1:3.7-2 Control: found -1 clang-3.8/1:3.8~svn247576-1 Hi, I've been trying to fix this, see the upstream bug report and http://reviews.llvm.org/D12834 Some clarifications: The dual ABI in libstdc++ is *enabled*, so linking libstdc++ should work fine with clang++ -D_GLIBCXX_USE_CXX11_ABI=0 The problem is with other c++ libraries which provide interfaces based on the new libstdc++ ABI (for example by using std::string). I don't think there is any library apart from libstdc++ out there providing dual ABI (and I don't think it is trivial to add, as you need separate translation units afaik); instead they are now all build against the new ABI. The main source of incompatibilities is: - functions returning an "abi_tag"ged type, like ``std::string getName()`` - global variables with "abi_tag"ged type (global as in "needs a symbols visible in all translation units". static variables in inline functions might not trigger a linker error, but are broken anyway) regards, Stefan PS: g++-4.9 doesn't work either.
Bug#800142: marked as done (docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name)
Your message dated Sun, 27 Sep 2015 12:18:49 + with message-id and subject line Bug#800142: fixed in docbook2x 0.8.8-12 has caused the Debian Bug report #800142, regarding docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name 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.) -- 800142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docbook2x Version: 0.8.8-10 Severity: serious Justification: breaks other packages User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, docbook2x-man always fails with: /usr/bin/utf8trans:${prefix}/share/docbook2X/charmaps/roff.charmap: No such file or directory This is because of: % grep prefix /usr/bin/docbook2x-man 'utf8trans-map-roff' => q<${prefix}/share/docbook2X/charmaps/roff.charmap>, 'utf8trans-map-texi' => q<${prefix}/share/docbook2X/charmaps/texi.charmap>, 'stylesheets-catalog' => q<${prefix}/share/docbook2X/xslt/catalog.xml>, The ${prefix} here should be the literal string "/usr/bin/" if you look back at, say, the version in wheezy. (If it helps, it's related to autoreconfing. As in, disabling that "fixes" the issue...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: docbook2x Source-Version: 0.8.8-12 We believe that the bug you reported is fixed in the latest version of docbook2x, 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 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated docbook2x package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Sep 2015 13:54:45 +0200 Source: docbook2x Binary: docbook2x Architecture: source Version: 0.8.8-12 Distribution: unstable Urgency: medium Maintainer: Debian XML/SGML Group Changed-By: Gianfranco Costamagna Description: docbook2x - Converts DocBook/XML documents into man pages and TeXinfo Closes: 800142 Changes: docbook2x (0.8.8-12) unstable; urgency=medium . * Use dh-autoreconf again, the problem was a patch "01_fix_static_datadir_evaluation.patch" applied to configure instead of configure.ac (Closes: #800142) * Remove 07_fix_597454_usr_share_info_dir_gz.patch, useless with autoreconf. Checksums-Sha1: 2a8f992d8eb7a3d064bb26359873c2d963579db5 2032 docbook2x_0.8.8-12.dsc 7dc34d420f8aae2a0c0cdb39f52146ce005bf902 723909 docbook2x_0.8.8.orig.tar.gz b6e8fd33669001bdfe97fd2be6f5cf191725a8e5 12048 docbook2x_0.8.8-12.debian.tar.xz Checksums-Sha256: 64dbf751559ac63c4dfc9da800ddb200b37a14b0624d3cfafb928228dd5535f6 2032 docbook2x_0.8.8-12.dsc 4077757d367a9d1b1427e8d5dfc3c49d993e90deabc6df23d05cfe9cd2fcdc45 723909 docbook2x_0.8.8.orig.tar.gz 8e7be01775b44c39a6154a3b178525b3854f433238d401b4121c8d83bcd44fac 12048 docbook2x_0.8.8-12.debian.tar.xz Files: c67d729c9f61215308f9ee07ec5ade46 2032 text optional docbook2x_0.8.8-12.dsc b9b76a6af198c4f44574cfd17a322f01 723909 text optional docbook2x_0.8.8.orig.tar.gz 12e9b4b2464157d769b9d6e3b37ed430 12048 text optional docbook2x_0.8.8-12.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWB91+AAoJEPNPCXROn13ZBpgQAJIzSdBhOChyPn0ixaKpInu/ F4WpQiuD6HJfDo7yf0E/cxQWLBgRSi4ebH2iScMm8++dJKJALT5kRhDZ8RsJE7W0 tMvZI4U4uxjrij2MrE0JFIZTc2SJkxZF5qQ7RP3bLmpJMZj+BSuxims5dI0qZDVC nSSdl2bXaBjaVALA8R0SpeDUauJJ8p0XxQ7UOslapRLsTyF73LBk0z4Nz8Erm8JN apPRyYKAsJhq6wW9JuilwkLvjSizoRDcVJf8Ubt8xWrKu7NHgIDyKujPg1vAEU8m uMSZosNEZdeHlMWmXVkCTh7uYd4/4qNf+F4fq6nLzPx2vklw5NaG/5T394cw4lko qR/8FLTRYz482nzFSxbPTxn2rdch5UEolizBBcFtlTG3Wn1vD1P5RI+uH7VJvoXj Vh/IHQ9jxcXlJcNcgT/Gtl5SpS3JmYkoDHY2dTJricaS3CFVx4SiWY7imECPhJAh 3Z3tUxCZnj5SqMTBCHgKJDY9JR0QmzM1nNXEmWdyiDM10vQXDGH1sG6xQgLVzZsm 6TmEkgMlKOxxXo3TLZ7Ml2iy2/sBkWp6pfBWe3ANg68uUoiWIQMvT8Pq1k55v5n3 bBWbcELVKil3NH2tcFmVsoR84m0e0vEjUljQqE2x5idqQrlSsv+nizjnQBs3HQts LeslAaNJgLX0xhx7OI1z =McPY -END PGP SIGNATURE End Message ---
Bug#797238: [debian-mysql] Bug#797238: Bug#797238: galera-3 ftbfs in unstable
Currenlty builds OK on all primary platforms: https://buildd.debian.org/status/package.php?p=galera-3
Bug#800142: docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name
Hi Chris, >Sorry, I must not have communicated that well - I was not suggesting >that you actually remove the autoreconfing, it was only a suggestion >where you initially start your debugging. I mentioned it so it might >save you a small amount of time fixing the underlying issue. > >Autoreconfing is a good practice and it would be a shame to revert it. >Besides, this might be a deeper bug in dh-autoreconf that needs >investigating. this is true, however I'm not a perl guy, neither an autoreconf fan, and I just don't understand it so much. I adopted this package because of boinc, and I prefer to just don't touch it anymore until it breaks again :) there is no active upstream, and I'm not sure I'll have time to dig into this issue. Moreover the broken one was 4 days old, and when I uploaded it I didn't see this RC :) so fixing was my real priority :) (patches are *really* welcome, because I really have difficulties in maintaining such buildsystem) cheers, G.
Bug#800099: marked as done (vdr-plugin-weather: FTBFS: sh: 0: Can't open /usr/share/vdr-dev/dependencies.sh)
Your message dated Sun, 27 Sep 2015 11:04:38 + with message-id and subject line Bug#800099: fixed in vdr-plugin-weather 0.2.1e-66 has caused the Debian Bug report #800099, regarding vdr-plugin-weather: FTBFS: sh: 0: Can't open /usr/share/vdr-dev/dependencies.sh 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.) -- 800099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-weather Version: 0.2.1e-63 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, vdr-plugin-weather fails to build from source in unstable/amd64: [..] debian/rules override_dh_gencontrol make[1]: Entering directory '/tmp/buildd/vdr-plugin-weather-0.2.1e' sh /usr/share/vdr-dev/dependencies.sh sh: 0: Can't open /usr/share/vdr-dev/dependencies.sh debian/rules:19: recipe for target 'override_dh_gencontrol' failed make[1]: *** [override_dh_gencontrol] Error 127 make[1]: Leaving directory '/tmp/buildd/vdr-plugin-weather-0.2.1e' debian/rules:9: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/vdr-plugin-weather_0.2.1e-63.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Fri Sep 25 00:21:19 GMT+12 2015 I: pbuilder-time-stamp: 1443183679 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (>= 7.0.50~), vdr-dev (>= 1.7.28), ftplib-dev, libmdsp-dev (>= 0.11-6) dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20290 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on vdr-dev (>= 1.7.28); however: Package vdr-dev is not installed. pbuilder-satisfydepends-dummy depends on ftplib-dev; however: Package ftplib-dev is not installed. pbuilder-satisfydepends-dummy depends on libmdsp-dev (>= 0.11-6); however: Package libmdsp-dev is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: ftplib-dev{a} ftplib3{a} libmdsp-dev{a} vdr-dev{a} 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 501 kB of archives. After unpacking 1591 kB will be used. Writing extended state information... Get: 1 http://ftp.de.debian.org/debian/ unstable/main ftplib3 amd64 3.1-1-9 [17.2 kB] Get: 2 http://ftp.de.debian.org/debian/ unstable/main ftplib-dev amd64 3.1-1-9 [51.3 kB] Get: 3 http://ftp.de.debian.org/debian/ unstable/main libmdsp-dev amd64 0.11-10 [52.0 kB] Get: 4 http://ftp.de.debian.org/debian/ unstable/main vdr-dev all 2.2.0-2 [380 kB] Fetched 501 kB in 0s (6628 kB/s) debconf: delaying package c
Bug#800142: docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name
Gianfranco, > (yes, as you said I just changed to autotools-dev back) Sorry, I must not have communicated that well - I was not suggesting that you actually remove the autoreconfing, it was only a suggestion where you initially start your debugging. I mentioned it so it might save you a small amount of time fixing the underlying issue. Autoreconfing is a good practice and it would be a shame to revert it. Besides, this might be a deeper bug in dh-autoreconf that needs investigating. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 800142 0.8.8-10 Bug #800142 {Done: Gianfranco Costamagna } [src:docbook2x] docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name Marked as fixed in versions docbook2x/0.8.8-10. > thanks Stopping processing here. Please contact me if you need assistance. -- 800142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800142: marked as done (docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name)
Your message dated Sun, 27 Sep 2015 10:52:57 + (UTC) with message-id <1425202971.2029434.1443351177969.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#800142: docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name has caused the Debian Bug report #800142, regarding docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name 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.) -- 800142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docbook2x Version: 0.8.8-10 Severity: serious Justification: breaks other packages User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, docbook2x-man always fails with: /usr/bin/utf8trans:${prefix}/share/docbook2X/charmaps/roff.charmap: No such file or directory This is because of: % grep prefix /usr/bin/docbook2x-man 'utf8trans-map-roff' => q<${prefix}/share/docbook2X/charmaps/roff.charmap>, 'utf8trans-map-texi' => q<${prefix}/share/docbook2X/charmaps/texi.charmap>, 'stylesheets-catalog' => q<${prefix}/share/docbook2X/xslt/catalog.xml>, The ${prefix} here should be the literal string "/usr/bin/" if you look back at, say, the version in wheezy. (If it helps, it's related to autoreconfing. As in, disabling that "fixes" the issue...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Control: fixed -1 0.8.8-11 Hi Chris, bad timing, I noticed it this morning while rebuilding boinc http://debomatic-amd64.debian.net/distribution#unstable/boinc/7.6.11+dfsg-1/buildlog I just uploaded a fixed version prior to see your mail... I would have given you credits, and avoided to dig into the issue (yes, as you said I just changed to autotools-dev back) sorry for that, Gianfranco Il Domenica 27 Settembre 2015 12:12, Chris Lamb ha scritto: Source: docbook2x Version: 0.8.8-10 Severity: serious Justification: breaks other packages User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, docbook2x-man always fails with: /usr/bin/utf8trans:${prefix}/share/docbook2X/charmaps/roff.charmap: No such file or directory This is because of: % grep prefix /usr/bin/docbook2x-man 'utf8trans-map-roff' => q<${prefix}/share/docbook2X/charmaps/roff.charmap>, 'utf8trans-map-texi' => q<${prefix}/share/docbook2X/charmaps/texi.charmap>, 'stylesheets-catalog' => q<${prefix}/share/docbook2X/xslt/catalog.xml>, The ${prefix} here should be the literal string "/usr/bin/" if you look back at, say, the version in wheezy. (If it helps, it's related to autoreconfing. As in, disabling that "fixes" the issue...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk ` End Message ---
Bug#800142: docbook2x: docbook2x-man binary broken due to literal ${prefix} instead of path name
Source: docbook2x Version: 0.8.8-10 Severity: serious Justification: breaks other packages User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, docbook2x-man always fails with: /usr/bin/utf8trans:${prefix}/share/docbook2X/charmaps/roff.charmap: No such file or directory This is because of: % grep prefix /usr/bin/docbook2x-man 'utf8trans-map-roff' => q<${prefix}/share/docbook2X/charmaps/roff.charmap>, 'utf8trans-map-texi' => q<${prefix}/share/docbook2X/charmaps/texi.charmap>, 'stylesheets-catalog' => q<${prefix}/share/docbook2X/xslt/catalog.xml>, The ${prefix} here should be the literal string "/usr/bin/" if you look back at, say, the version in wheezy. (If it helps, it's related to autoreconfing. As in, disabling that "fixes" the issue...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#800139: sphinx-paramlinks: Missing Build-Depends on python3-docutils & python3-sphinx
Source: sphinx-paramlinks Version: 0.2.2-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Tags: patch Dear Maintainer, sphinx-paramlinks fails to build from source in unstable/amd64 due to missing Build-Depends on python3-docutils and python3-sphinx: [..] I: pybuild base:170: cd /tmp/buildd/sphinx-paramlinks-0.2.2/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v sphinx_paramlinks (unittest.loader._FailedTest) ... ERROR == ERROR: sphinx_paramlinks (unittest.loader._FailedTest) -- ImportError: Failed to import test module: sphinx_paramlinks Traceback (most recent call last): File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.5/unittest/loader.py", line 369, in _get_module_from_name __import__(name) File "/tmp/buildd/sphinx-paramlinks-0.2.2/.pybuild/pythonX.Y_3.5/build/sphinx_paramlinks/__init__.py", line 3, in from .sphinx_paramlinks import setup File "/tmp/buildd/sphinx-paramlinks-0.2.2/.pybuild/pythonX.Y_3.5/build/sphinx_paramlinks/sphinx_paramlinks.py", line 3, in from docutils import nodes ImportError: No module named 'docutils' -- Ran 1 test in 0.000s FAILED (errors=1) E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd /tmp/buildd/sphinx-paramlinks-0.2.2/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v dh_auto_test: pybuild --test -i python{version} -p 3.4 3.5 --dir . returned exit code 13 debian/rules:5: recipe for target 'build' failed make: *** [build] Error 25 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/sphinx-paramlinks_0.2.2-2.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sat Sep 26 09:59:26 GMT+12 2015 I: pbuilder-time-stamp: 1443304766 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, python3-all, python3-setuptools dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20294 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on dh-python; however: Package dh-python is not installed. pbuilder-satisfydepends-dummy depends on python-all; however: Package python-all is not installed. pbuilder-satisfydepends-dummy depends on python-setuptools; however: Package python-setuptools is not installed. pbuilder-satisfydepends-dummy depends on python3-all; however: Package python3-all is not installed. pbuilder-satisfydepends-dummy depends on python3-setuptools; however: Package python3-setuptools is not installed. Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ... Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... Building tag database... pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) pbuilder-satisfydepends-dummy is already installed at the requested version (0.invalid.0) The following NEW packages will be installed: dh-python{a} libexpat1{a} libmpdec2{a} libpython-stdlib{a} libpython2.7-minima
Bug#800136: marked as done (python-mne: FTBFS: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory)
Your message dated Sun, 27 Sep 2015 10:48:02 +0100 with message-id <1443347282.4140634.394598041.3be51...@webmail.messagingengine.com> and subject line Re: Bug#800136: Acknowledgement (python-mne: FTBFS: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory) has caused the Debian Bug report #800136, regarding python-mne: FTBFS: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory 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.) -- 800136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-mne Version: 0.8.6+dfsg-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, python-mne fails to build from source in unstable/amd64. On the face of it you are missing openmpi-common in Build-Depends, but installing this surfaces a different error in the tests. Here's the build log with the shipped B-D: [..] debian/rules override_dh_auto_test make[1]: Entering directory '/tmp/buildd/python-mne-0.8.6+dfsg' MNE_DONTWRITE_HOME=true MNE_SKIP_SAMPLE_DATASET_TESTS=true MNE_FORCE_SERIAL=true MNE_SKIP_NETWORK_TESTS=1 \ xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" \ nosetests mne Xlib: extension "RANDR" missing on display ":20". /usr/lib/python2.7/dist-packages/pyface/toolkit.py:43: DeprecationWarning: Default toolkit will change to 'qt4' in PyFace 5.0 DeprecationWarning) [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 231 [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 140 [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file runtime/orte_init.c at line 128 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_errors_are_fatal unknown handle But I couldn't open the help file: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: ompi mpi abort:cannot guarantee all killed But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime.txt: No such file or directory. Sorry! -- debian/rules:18: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/python-mne-0.8.6+dfsg' debian/rules:7: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/python-mne_0.8.6+dfsg-2.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- sigh, duplicate.. On Sun, 27 Sep 2015, at 10:39 AM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message >
Bug#800137: django-countries: FTBFS: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'
Source: django-countries Version: 2.1.2-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, django-countries fails to build from source in unstable/amd64: [..] Creating test database for alias 'default'... Destroying test database for alias 'default'... Traceback (most recent call last): File "/usr/bin/django-admin", line 21, in management.execute_from_command_line() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 354, in execute django.setup() File "/usr/lib/python3/dist-packages/django/__init__.py", line 18, in setup from django.utils.log import configure_logging File "/usr/lib/python3/dist-packages/django/utils/log.py", line 13, in from django.views.debug import ExceptionReporter, get_exception_reporter_filter File "/usr/lib/python3/dist-packages/django/views/debug.py", line 10, in from django.http import (HttpResponse, HttpResponseServerError, File "/usr/lib/python3/dist-packages/django/http/__init__.py", line 4, in from django.http.response import ( File "/usr/lib/python3/dist-packages/django/http/response.py", line 13, in from django.core.serializers.json import DjangoJSONEncoder File "/usr/lib/python3/dist-packages/django/core/serializers/__init__.py", line 23, in from django.core.serializers.base import SerializerDoesNotExist File "/usr/lib/python3/dist-packages/django/core/serializers/base.py", line 6, in from django.db import models File "/usr/lib/python3/dist-packages/django/db/models/__init__.py", line 6, in from django.db.models.query import Q, QuerySet, Prefetch # NOQA File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 13, in from django.db.models.fields import AutoField, Empty File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", line 18, in from django import forms File "/usr/lib/python3/dist-packages/django/forms/__init__.py", line 6, in from django.forms.fields import * # NOQA File "/usr/lib/python3/dist-packages/django/forms/fields.py", line 18, in from django.forms.utils import from_current_timezone, to_current_timezone File "/usr/lib/python3/dist-packages/django/forms/utils.py", line 15, in from django.utils.html import format_html, format_html_join, escape File "/usr/lib/python3/dist-packages/django/utils/html.py", line 16, in from .html_parser import HTMLParser, HTMLParseError File "/usr/lib/python3/dist-packages/django/utils/html_parser.py", line 12, in HTMLParseError = _html_parser.HTMLParseError AttributeError: module 'html.parser' has no attribute 'HTMLParseError' debian/rules:14: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/django-countries-2.1.2' debian/rules:10: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/django-countries_2.1.2-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sat Sep 26 10:41:51 GMT+12 2015 I: pbuilder-time-stamp: 1443307311 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (>= 7.0.50~), dh-python, iso-codes, python-all, python-django, python-setuptools, python3-all, python3-django, python3-setuptools dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbu
Bug#800136: python-mne: FTBFS: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory
Source: python-mne Version: 0.8.6+dfsg-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, python-mne fails to build from source in unstable/amd64. On the face of it you are missing openmpi-common in Build-Depends, but installing this surfaces a different error in the tests. Here's the build log with the shipped B-D: [..] debian/rules override_dh_auto_test make[1]: Entering directory '/tmp/buildd/python-mne-0.8.6+dfsg' MNE_DONTWRITE_HOME=true MNE_SKIP_SAMPLE_DATASET_TESTS=true MNE_FORCE_SERIAL=true MNE_SKIP_NETWORK_TESTS=1 \ xvfb-run --auto-servernum --server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" \ nosetests mne Xlib: extension "RANDR" missing on display ":20". /usr/lib/python2.7/dist-packages/pyface/toolkit.py:43: DeprecationWarning: Default toolkit will change to 'qt4' in PyFace 5.0 DeprecationWarning) [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 231 [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 140 [profitbricks-build1-amd64:49321] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file runtime/orte_init.c at line 128 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_errors_are_fatal unknown handle But I couldn't open the help file: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: ompi mpi abort:cannot guarantee all killed But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime.txt: No such file or directory. Sorry! -- debian/rules:18: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/python-mne-0.8.6+dfsg' debian/rules:7: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/python-mne_0.8.6+dfsg-2.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#800053: marked as done (gedit-plugins: package depends on obsolete version of gedit)
Your message dated Sun, 27 Sep 2015 09:19:59 + with message-id and subject line Bug#800053: fixed in gedit-plugins 3.18.0-1 has caused the Debian Bug report #800053, regarding gedit-plugins: package depends on obsolete version of gedit 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.) -- 800053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gedit-plugins Version: 3.16.0-1 Severity: grave Justification: renders package unusable the gedit package in unstable is now at version 3.18.0-1. However gedit-plugin depends on gedit < 3.17, therefore currently it's not possible to install it with the latest version of gedit. I would like to upgrade gedit, but then I would hate to loose the plugins, because I am actively using some of them. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gedit-plugins depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gedit3.16.3-1 ii gir1.2-git2-glib-1.0 0.23.4-2 ii gir1.2-glib-2.0 1.44.0-1+b2 ii gir1.2-gtk-3.0 3.16.6-1 ii gir1.2-gtksource-3.0 3.18.0-1 ii gir1.2-gucharmap-2.901:3.14.1-1 ii gir1.2-pango-1.0 1.36.8-3 ii gir1.2-peas-1.0 1.16.0-1 ii gir1.2-vte-2.91 0.38.1-2 ii gir1.2-zeitgeist-2.0 0.9.14-2.2 ii libatk1.0-0 2.18.0-1 ii libc62.19-22 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u2 ii libgirepository-1.0-11.44.0-1+b2 ii libglib2.0-0 2.46.0-1 ii libgtk-3-0 3.16.6-1 ii libgtksourceview-3.0-1 3.18.0-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpeas-1.0-01.16.0-1 ii libzeitgeist-2.0-0 0.9.14-2.2 ii python3 3.4.2-2 ii python3-cairo1.10.0+dfsg-4+b1 ii python3-dbus 1.2.0-2+b3 ii python3-gi 3.14.0-1 ii python3-gi-cairo 3.14.0-1 ii python3.43.4.3-9 gedit-plugins recommends no packages. Versions of packages gedit-plugins suggests: pn zeitgeist-datahub -- debconf-show failed --- End Message --- --- Begin Message --- Source: gedit-plugins Source-Version: 3.18.0-1 We believe that the bug you reported is fixed in the latest version of gedit-plugins, 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 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated gedit-plugins 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, 27 Sep 2015 10:11:53 +0200 Source: gedit-plugins Binary: gedit-plugins Architecture: source amd64 Version: 3.18.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Andreas Henriksson Description: gedit-plugins - set of plugins for gedit Closes: 800053 Changes: gedit-plugins (3.18.0-1) unstable; urgency=medium . * New upstream release. (Closes: #800053) * Add build-dependency on valac (>= 0.28.0) and --enable-vala - this enables the new findinfiles plugin * Bump gtksourceview build-dep to >= 3.17.3 as
Processed: Debian bug #798657
Processing commands for cont...@bugs.debian.org: > tags 798657 + pending Bug #798657 [libsane-dev] libsane-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/sane-config.1.gz Added tag(s) pending. > -- Stopping processing here. Please contact me if you need assistance. -- 798657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797944: simgear: gcc5 transition - please upload libsimgear*3.4.0v5
Reassigning back so the maintainers see this. It appears to be random (race condition in the BTS??) whether the old or new package's maintainer gets the main text of a reassign message (this one went to the old one, but #793517 went to the new one). Is that a bug? (Both maintainers get the Processed: receipt.) There's no need to wait for libglu. This could be done at any time. Feel free to reassign to release.debian.org once this is uploaded. Patch is earlier in this bug. (Upstream still haven't released 3.6.)