Bug#906459: marked as done (ephoto: FTBFS in buster/sid (Cannot create run dir '/sbuild-nonexistent/.run'))
Your message dated Sun, 26 Aug 2018 05:18:54 + with message-id and subject line Bug#906459: fixed in ephoto 1.5-2 has caused the Debian Bug report #906459, regarding ephoto: FTBFS in buster/sid (Cannot create run dir '/sbuild-nonexistent/.run') 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.) -- 906459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ephoto Version: 1.5-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a Copying file m4/codeset.m4 Copying file m4/fcntl-o.m4 Copying file m4/glibc2.m4 Copying file m4/glibc21.m4 Copying file m4/intdiv0.m4 Copying file m4/intl.m4 Copying file m4/intldir.m4 Copying file m4/intmax.m4 Copying file m4/inttypes-pri.m4 Copying file m4/inttypes_h.m4 [... snipped ...] from ephoto.h:15, from ephoto_ipc.c:1: /usr/include/eina-1/eina/eina_module.h:232:2: warning: ignoring attribute 'malloc' because it conflicts with attribute 'pure' [-Wattributes] eina_module_symbol_path_get(const void *symbol, const char *sub_dir) EINA_PURE EINA_MALLOC EINA_ARG_NONNULL(1, 2); ^~~ /usr/include/eina-1/eina/eina_module.h:249:2: warning: ignoring attribute 'malloc' because it conflicts with attribute 'pure' [-Wattributes] eina_module_environment_path_get(const char *env, const char *sub_dir) EINA_PURE EINA_MALLOC EINA_ARG_NONNULL(1, 2); ^~~~ gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/bin -DPACKAGE_DATA_DIR=\"/usr/share/ephoto\" -DPACKAGE_LIB_DIR=\"/usr/lib/x86_64-linux-gnu/ephoto\" -Wall -Wextra -Wshadow -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wpointer-arith -Wno-missing-field-initializers -fvisibility=hidden -fdata-sections -ffunction-sections -pthread -I/usr/include/elementary-1 -I/usr/include/libdrm -I/usr/include/efl-1 -I/usr/include/ecore-wl2-1 -I/usr/include/efl-1 -I/usr/include/ecore-fb-1 -I/usr/include/efl-1 -I/usr/include/ecore-x-1 -I/usr/include/elocation-1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/emotion-1 -I/usr/include/efl-1 -I/usr/include/ethumb-client-1 -I/usr/include/efl-1 -I/usr/include/ethumb-1 -I/usr/include/efl-1 -I/usr/include/edje-1 -I/usr/include/efl-1 -I/usr/include/ecore-audio-1 -I/usr/include/efl-1 -I/usr/include/eio-1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/embryo-1 -I/usr/include/ efl-1 -I/usr/include/ecore-imf-evas-1 -I/usr/include/efl-1 -I/usr/include/ecore-imf-1 -I/usr/include/efl-1 -I/usr/include/ecore-evas-1 -I/usr/include/efl-1 -I/usr/include/ecore-drm2-1 -I/usr/include/efl-1 -I/usr/include/elput-1 -I/usr/include/efl-1 -I/usr/include/ecore-input-evas-1 -I/usr/include/efl-1 -I/usr/include/ecore-input-1 -I/usr/include/efl-1 -I/usr/include/eeze-1 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/efl-1 -I/usr/include/evas-1 -I/usr/include/evas-1/canvas -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/luajit-2.1 -I/usr/include/efl-1 -I/usr/include/efreet-1 -I/usr/include/efl-1 -I/usr/include/ecore-ipc-1 -I/usr/include/efl-1 -I/usr/include/ecore-file-1 -I/usr/include/efl-1 -I/usr/include/ecore-con-1 -I/usr/include/efl-1 -I/usr/include/eldbus-1 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/efl-1 -I/usr/include/ecore-1 -I/usr/include /glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 -I/usr/include/eet-1 -I/usr/include/efl-1 -I/usr/include/emile-1 -I/usr/include/efl-1 -I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 -I/usr/include/eina-1/eina -I/usr/include/p11-kit-1 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o ephoto_thumbnail-ephoto_thumb.o `test -f 'ephoto_thumb.c' || echo './'`ephoto_thumb.c In file included from /usr/include/eina-1/Eina.h:226, from /usr/include/eet-1/Eet.h:100, from ephoto.h:15, from ephoto_thumb.c:1: /usr/include/eina-1/eina/eina_module.h:232:2: warning: ignoring attribute 'malloc' because it conflicts with attribute 'pure' [-Wattributes] eina_module_symbol_path_get(const
Bug#906375: Tried new upstream version
Hi, On Sun, Aug 26, 2018 at 01:22:21AM +0200, Emmanuel Bourg wrote: > > [ERROR] The project com.itextpdf:itextpdf:5.5.13 > > (/build/libitext5-java-5.5.13/itext/pom.xml) has 1 error > > [ERROR] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: > > Cannot access central (https://repo.maven.apache.org/maven2) in offline > > mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been > > downloaded from it before. and 'parent.relativePath' points at no local POM > > @ line 5, column 11 -> [Help 2] > > Adding --no-parent for the root pom.xml in debian/libitext5-java.poms > will probably help. The project now uses multiple Maven modules, they'll > have to be listed in the file too. That was the case even before: https://salsa.debian.org/java-team/libitext5-java/blob/master/debian/libitext5-java.poms Kind regards Andreas. -- http://fam-tille.de
Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1
Package: cups-filters Version: 1.21.0-1 Followup-For: Bug #907026 This bug has been fixed upstream, more info at https://github.com/OpenPrinting/cups-filters/issues/57 I tested the upstream patch and it works. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, mipsel, riscv64 Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8), LANGUAGE=zh_CN:zh (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups-filters depends on: ii bc 1.07.1-2+b1 ii cups-filters-core-drivers 1.21.0-1 ii ghostscript9.22~dfsg-2.1 ii libc6 2.27-5 ii libcups2 2.2.8-5 ii libcupsfilters11.21.0-1 ii libcupsimage2 2.2.8-5 ii libfontconfig1 2.13.0-5 ii libfontembed1 1.21.0-1 ii libgcc11:8.2.0-4 ii libqpdf21 8.2.1-1 ii libstdc++6 8.2.0-4 ii poppler-utils 0.63.0-2 Versions of packages cups-filters recommends: ii colord 1.3.3-2 ii imagemagick 8:6.9.10.8+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.8+dfsg-1 ii liblouisutdml-bin2.7.0-2+b3 Versions of packages cups-filters suggests: pn antiword pn docx2txt ii foomatic-db-compressed-ppds [foomatic-db] 20180604-1 -- no debconf information
Bug#906391: marked as done (nordugrid-arc: FTBFS in buster/sid (autoreconf fails))
Your message dated Sun, 26 Aug 2018 03:20:01 + with message-id and subject line Bug#906391: fixed in nordugrid-arc 5.4.2-4 has caused the Debian Bug report #906391, regarding nordugrid-arc: FTBFS in buster/sid (autoreconf fails) 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.) -- 906391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nordugrid-arc Version: 5.4.2-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh_testdir if [ ! -f po/POTFILES.in.save ] ; then \ cp -p po/POTFILES.in po/POTFILES.in.save ; \ fi dh_autoreconf Copying file m4/codeset.m4 Copying file m4/glibc21.m4 Copying file m4/intdiv0.m4 Copying file m4/inttypes-pri.m4 Copying file m4/inttypes.m4 Copying file m4/inttypes_h.m4 Copying file m4/isc-posix.m4 Copying file m4/lcmessage.m4 [... snipped ...] config.status: creating src/utils/hed/Makefile config.status: creating src/utils/gridmap/nordugridmap.cron config.status: creating src/utils/gridmap/nordugridmap.8 config.status: creating src/utils/gridmap/Makefile config.status: creating src/utils/Makefile config.status: creating src/doc/Makefile config.status: creating src/doc/arc.conf.5 config.status: creating swig/Makefile config.status: creating java/Makefile config.status: creating java/test/Makefile config.status: creating java/test/strip_test_file_name_and_run_junit config.status: creating java/examples/Makefile config.status: creating python/Makefile config.status: creating python/Doxyfile.api config.status: creating python/python/Makefile config.status: creating python/python/arc/Makefile config.status: creating python/altpython/Makefile config.status: creating python/altpython/arc/Makefile config.status: creating python/test/Makefile config.status: creating python/test/python/Makefile config.status: creating python/test/altpython/Makefile config.status: creating python/examples/Makefile config.status: creating po/Makefile.in config.status: WARNING: 'po/Makefile.in.in' seems to ignore the --datarootdir setting config.status: creating include/Makefile config.status: creating debian/Makefile config.status: creating debian/changelog.deb config.status: creating nordugrid-arc.spec config.status: creating mingw-nordugrid-arc.spec config.status: creating src/hed/daemon/arched.8 config.status: creating src/hed/daemon/scripts/arched config.status: creating src/hed/daemon/scripts/arched.service config.status: creating src/hed/daemon/scripts/arched-start config.status: creating arcbase.pc config.status: creating nsis/Makefile config.status: creating nsis/arc.nsis config.status: creating src/doxygen/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: error: in `/<>': config.status: error: Something went wrong bootstrapping makefile fragments for automatic dependency tracking. Try re-running configure with the '--disable-dependency-tracking' option to at least be able to build the package (albeit without support for automatic dependency tracking). See `config.log' for more details make: *** [debian/rules:23: configure-stamp] Error 1 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nordugrid-arc.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: nordugrid-arc Source-Version: 5.4.2-4 We believe that the bug you reported is fixed in the latest version of nordugrid-arc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert (supplier of updated nordugrid-arc package) (This message was generated automatically at
Bug#906375: Tried new upstream version
On 25/08/2018 17:44, Andreas Tille wrote: > No, it is different: > [ERROR] The project com.itextpdf:itextpdf:5.5.13 > (/build/libitext5-java-5.5.13/itext/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: > Cannot access central (https://repo.maven.apache.org/maven2) in offline mode > and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded > from it before. and 'parent.relativePath' points at no local POM @ line 5, > column 11 -> [Help 2] Adding --no-parent for the root pom.xml in debian/libitext5-java.poms will probably help. The project now uses multiple Maven modules, they'll have to be listed in the file too.
Bug#904063: marked as done (solr-tomcat: solr does not start due to NullPointerException)
Your message dated Sat, 25 Aug 2018 22:34:54 + with message-id and subject line Bug#904063: fixed in lucene-solr 3.6.2+dfsg-14 has caused the Debian Bug report #904063, regarding solr-tomcat: solr does not start due to NullPointerException 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.) -- 904063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solr-tomcat Version: 3.6.2+dfsg-13 Severity: grave Dear Maintainer, According to my logs, tomcat8 is not properly starting solr. I have checked, and to the best of my knowledge I have not modified any of the configuration files. I tried reverting to java-8, (by modifying JAVA_HOME in the /etc/default/tomcat8 file), but that did not turn out to be the problem. Here are the logs of the failure: 18-Jul-2018 22:01:19.148 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Deploying configuration descriptor [/etc/tomcat8/Catalina/localhost/solr.xml] 18-Jul-2018 22:01:19.505 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/solr]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:629) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.base/java.lang.Thread.run(Thread.java:844) Caused by: java.lang.NullPointerException at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:373) at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:191) at org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1888) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1116) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:765) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 10 more 18-Jul-2018 22:01:19.506 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Error deploying configuration descriptor [/etc/tomcat8/Catalina/localhost/solr.xml] java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/solr]] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:758) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:629) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1839) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.base/java.lang.Thread.run(Thread.java:844) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500,
Bug#906384: marked as done (lucene-solr: FTBFS in buster/sid)
Your message dated Sat, 25 Aug 2018 22:34:54 + with message-id and subject line Bug#906384: fixed in lucene-solr 3.6.2+dfsg-14 has caused the Debian Bug report #906384, regarding lucene-solr: FTBFS in buster/sid 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.) -- 906384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lucene-solr Version: 3.6.2+dfsg-13 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with maven_repo_helper dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/lucene-solr-3.6.2+dfsg' # Link in jars from /usr/share/java rather # than patching the build process for pkg in `cat debian/build-jars`; \ do \ ln -sf `echo $pkg | cut -d : -f 1` `echo $pkg | cut -d : -f 2`; \ done ln: failed to create symbolic link './lucene/lib/ant.jar': No such file or directory ln: failed to create symbolic link './lucene/lib/junit4.jar': No such file or directory [... snipped ...] prep-lucene-jars: lucene-jars-to-solr: [copy] Copying 11 files to /<>/lucene-solr-3.6.2+dfsg/solr/build/lucene-libs dist: [exec] Execute failed: java.io.IOException: Cannot run program "svnversion" (in directory "/<>/lucene-solr-3.6.2+dfsg/solr/webapp"): error=2, No such file or directory [echo] Building solr... contribs-add-to-war: [mkdir] Created dir: /<>/lucene-solr-3.6.2+dfsg/solr/build/web [echo] Building solr-analysis-extras... add-to-war: [echo] Building solr-clustering... add-to-war: [echo] Building solr-dataimporthandler-extras... add-to-war: [echo] Building solr-dataimporthandler... add-to-war: [copy] Copying 2 files to /<>/lucene-solr-3.6.2+dfsg/solr/build/web [echo] Building solr-cell... add-to-war: [echo] Building solr-langid... add-to-war: [echo] Building solr-uima... add-to-war: [echo] Building solr-velocity... add-to-war: [war] Building war: /<>/lucene-solr-3.6.2+dfsg/solr/dist/apache-solr-3.6.2.war BUILD FAILED /<>/lucene-solr-3.6.2+dfsg/solr/build.xml:322: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/solr/webapp/build.xml:65: Problem creating war: /<>/lucene-solr-3.6.2+dfsg/solr/lib/wstx-lgpl.jar Total time: 16 seconds make[1]: *** [debian/rules:24: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>/lucene-solr-3.6.2+dfsg' make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lucene-solr.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-14 We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Aug 2018 23:23:24 +0200 Source: lucene-solr Binary: liblucene3-java liblucene3-contrib-java liblucene3-java-doc libsolr-java solr-common solr-tomcat solr-jetty Architecture: source Version: 3.6.2+dfsg-14 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: liblucene3-contrib-java - Full-text search engine library for Java - additional
Bug#906384: lucene-solr: FTBFS in buster/sid
Am 25.08.2018 um 23:27 schrieb Markus Koschany: > Control: tags -1 pending > > The FTBFS was caused by the latest upgrade of libwoodstox-java. The jar > files were renamed and could not be found anymore. > > I am quite sure this is related to #904063 somehow. Once #906447 is > resolved I could try to verify this assumption. Ok, I forgot to install OpenJDK 10 on this system hence I got hit by #906447 too. I can confirm now that the libwoodstox-java upgrade caused the build failure and the runtime error. I am going to upload the fix shortly. Markus signature.asc Description: OpenPGP digital signature
Bug#906191: marked as done (libvkd3d-dev: missing Depends: libvkd3d-utils1 (= ${binary:Version}))
Your message dated Sat, 25 Aug 2018 21:49:23 +
with message-id
and subject line Bug#906191: fixed in vkd3d 1.0-5
has caused the Debian Bug report #906191,
regarding libvkd3d-dev: missing Depends: libvkd3d-utils1 (= ${binary: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.)
--
906191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvkd3d-dev
Version: 1.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m28.3s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/libvkd3d-utils.so -> libvkd3d-utils.so.1.0.0
cheers,
Andreas
libvkd3d-dev_1.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.0-5
We believe that the bug you reported is fixed in the latest version of
vkd3d, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 906...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Gilbert (supplier of updated vkd3d package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 25 Aug 2018 21:22:32 +
Source: vkd3d
Binary: libvkd3d-dev libvkd3d1 libvkd3d-utils1 vkd3d-demos
Architecture: source
Version: 1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party
Changed-By: Michael Gilbert
Description:
libvkd3d-dev - Direct3D 12 to Vulkan translation - development files
libvkd3d-utils1 - Direct3D 12 to Vulkan translation - utilities library
libvkd3d1 - Direct3D 12 to Vulkan translation - library
vkd3d-demos - Direct3D 12 to Vulkan translation - demos
Closes: 906191
Changes:
vkd3d (1.0-5) unstable; urgency=medium
.
* Update standards version.
* Add missing libvkd3d-utils1 dependency (closes: #906191).
Checksums-Sha1:
ee83118a6471e3b2aa7e810af9ff29023397e866 2941 vkd3d_1.0-5.dsc
f1f8dc9dc728369a8ee7a903a0f1c09c80ad349c 4816 vkd3d_1.0-5.debian.tar.xz
4813a3590cbcf4211b706907a83954cb4ddbd42b 6962 vkd3d_1.0-5_source.buildinfo
Checksums-Sha256:
6acec3c8016ccb126a8c8f5587bf853df59824112870cc3d1a347274851862c7 2941
vkd3d_1.0-5.dsc
721ea6c6ccf9bcf704a3ccd3bbb74ca57446f5370818d76f393c70f1b3648929 4816
vkd3d_1.0-5.debian.tar.xz
be800a2d5b0500133ada57b49fbfc876b56c6c49fd47981b1bf75e652aadac81 6962
vkd3d_1.0-5_source.buildinfo
Files:
0069d47fa0f5243b7e0284aa86522cf6 2941 libs optional vkd3d_1.0-5.dsc
e0eedc14d8d1b859f7a467102a670e13 4816 libs optional vkd3d_1.0-5.debian.tar.xz
b4f3d1d36df18cedbc1ebe81cbeec9f1 6962 libs optional
vkd3d_1.0-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAluByqgACgkQuNayzQLW
9HNXVSAAqikrLahFv2AvKSuIswyYXK+kyYV++Ykn0ub10QO1CdDn1fvN4nKO/EEz
gnyOcPFkfcHuYaWvyq9a4SYqqto88XOWlKeXeqNQ8Wefv7ZYcmVEeHxcNYA1l4A5
FHfTxVHMLBZKUpPEal8r0bghzPnUoOKuXpx5xxURC6bSkkuRo3Wm3785HzJ5IyB7
WXmPaScj8SuwnwUg7P44DbGkKVrfeUuxBojhogUHwPZgOsNwT6DOVx1eTotV4wuM
gXwF9xjZbyCjwUNq1oLcPBiwsWIZD1+U+x0U9bX4xY4p+O7ccXGpB5OFGQCG2GZR
nyp3+FPDVTiGqadmUMlGFtjwLpEsEWuOkjrcfYNqEasO+43s704db6xygtQWqZt7
2ot1RG/CTcyoM6BpHvoqE90fKkx0Arx0Ho0JdNAUc0+iOlZ2bHx8dVk4HNiYXUc6
CeYmx4nOLLhUurZrJ0aeIEImXI4ifQmIESACpwUo2PFjeqyExRJVYjdhxnlfYcrX
C0WHspLlB7RG1X8rvQuxBOAR2QI8973SPN+bADKz4b/Pl0kxQVZ0aQBTT1sMOirx
6k9UB7Q5/2+Ah1rr0X/o0cKhmga04wUp+cRb0W0KbLjEarJ4UiAyx1JLVga9ASyb
bFQuC/d9/XJPh7nv4KmVsLVnYFfT1LISwnBPJsG5GkLKHobGxb3kYfvt/64+Jbx9
M7mxFLbvM65iysDXZY6S1uUj5OX5V59ZQS/fXmuWSIUrFYb8VZTDfpsXua5veK9X
mOeyiYqdh8U+hWU5hTOgWjOXzlzo29wRq7bhw2+PIcVxSeaaIttwmmH/QqENeNun
28GQuXN8CgndRp6w3PCx6EA0BsNUXw6x5M/6N//Sve1ugOYcpPwjSViCMTdZzXdX
6qiwxWzwhuexoWLJNqbUSlRpG6m/ZWRHLWBVEuhRRanW077eqhb/j/7J7i0qXSjc
6xBrhXrbl7KEvxYZLzSHPl9trGFmV2xTlBZFOA/zxIJPm5Ya4KhayPhMvPRQRnEv
5/EJna9zbeujd9YqYic0ccIRYHC1DA5olEUlfV0h4eVx7C5AaT/I6C1WAM3FEfkc
oUedQUNlPJS29GD19mcec7AbCkuAsA6U1nBH3BdlE06iSMKKuzd3SshAkch9zXu7
QCmXrOhmqgU1aDVl8uxqqjxdKS6fmPEkTnU85i5Riue5tGTGP4UeADlOmW6f7x+r
Q1DODUA/OonPKTbn4kcT0doczFcu6JUYjS9Mzzh6fsvdUTRE5MKuTqVsI3XhkIgL
Bug#906384: lucene-solr: FTBFS in buster/sid
Control: tags -1 pending The FTBFS was caused by the latest upgrade of libwoodstox-java. The jar files were renamed and could not be found anymore. I am quite sure this is related to #904063 somehow. Once #906447 is resolved I could try to verify this assumption. Markus signature.asc Description: OpenPGP digital signature
Processed: Re: lucene-solr: FTBFS in buster/sid
Processing control commands: > tags -1 pending Bug #906384 [src:lucene-solr] lucene-solr: FTBFS in buster/sid Added tag(s) pending. -- 906384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907158: mpi-testsuite: FTBFS in buster/sid (ln: failed to create symbolic link)
Control: severity -1 important On Fri, Aug 24, 2018 at 11:03:54AM +, Santiago Vila wrote: >... > for i in `find . -name "testlist" | grep -v ^..build`;\ > do\ > if [ ! -e build-openmpi/$i ]; \ > then\ > ln -s `pwd`/$i `pwd`/build-openmpi/$i;\ > fi; \ > done > ln: failed to create symbolic link > '/<>/mpi-testsuite-3.2+dfsg/build-openmpi/./.pc/disable_large_tests.patch/group/testlist': > No such file or directory > make[1]: *** [debian/rules:16: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>/mpi-testsuite-3.2+dfsg' > make: *** [debian/rules:7: build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit > status 2 > > > I don't know why it does not fail in the same way in reproducible builds, > but it is easy to see why it fails for me: The find command is finding > things inside the .pc directory used by quilt and friends. I would do > something like "find *" instead, if that's enough for the intended purpose. This message is "normal", it is even in the arm64 build that just succeeded on a buildd. I don't know what actually causes your build failure, but this does not seem to be a problem on the buildds. > Thanks. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#907158: mpi-testsuite: FTBFS in buster/sid (ln: failed to create symbolic link)
Processing control commands: > severity -1 important Bug #907158 [src:mpi-testsuite] mpi-testsuite: FTBFS in buster/sid (ln: failed to create symbolic link) Severity set to 'important' from 'serious' -- 907158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#860298: marked as done (undertaker requires whatthepatch)
Your message dated Sat, 25 Aug 2018 21:19:10 + with message-id and subject line Bug#860298: fixed in undertaker 1.6.1-4.2 has caused the Debian Bug report #860298, regarding undertaker requires whatthepatch 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.) -- 860298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: undertaker Version: 1.6.1-4+b1 Severity: important Dear Maintainer, undertaker-checkpatch requires python module whatthepatch [1], but this is not packaged for Debian. Could you please package it? Workaround to install whatthepatch with pip isn't really a solution. $ /usr/bin/undertaker-checkpatch Traceback (most recent call last): File "/usr/bin/undertaker-checkpatch", line 28, in import vamos.defect_analysis as defect_analysis File "/usr/lib/python2.7/dist-packages/vamos/defect_analysis.py", line 23, in from vamos.block import Block File "/usr/lib/python2.7/dist-packages/vamos/block.py", line 20, in import whatthepatch ImportError: No module named whatthepatch [1] https://github.com/cscorley/whatthepatch Kind regards, Petr -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages undertaker depends on: ii git1:2.11.0-2 ii libboost-filesystem1.62.0 1.62.0+dfsg-4 ii libboost-regex1.62.0 1.62.0+dfsg-4 ii libboost-system1.62.0 1.62.0+dfsg-4 ii libboost-thread1.62.0 1.62.0+dfsg-4 ii libboost-wave1.62.01.62.0+dfsg-4 ii libc6 2.24-9 ii libgcc11:6.3.0-11 ii libstdc++6 6.3.0-11 ii python 2.7.13-2 pn python:any undertaker recommends no packages. undertaker suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: undertaker Source-Version: 1.6.1-4.2 We believe that the bug you reported is fixed in the latest version of undertaker, 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 860...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated undertaker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Aug 2018 23:11:23 +0300 Source: undertaker Binary: undertaker Architecture: source Version: 1.6.1-4.2 Distribution: unstable Urgency: high Maintainer: Christoph Egger Changed-By: Adrian Bunk Description: undertaker - variability-aware tool for static code analysis Closes: 860298 Changes: undertaker (1.6.1-4.2) unstable; urgency=high . * Non-maintainer upload. * Add the missing dependency on python-whatthepatch. (Closes: #860298) Checksums-Sha1: e7c33389d6a534c2ea2f0829fbc2d16ac7b6c6ef 2220 undertaker_1.6.1-4.2.dsc 0425ad886df347314c9db2aed196ef045649f0e2 19988 undertaker_1.6.1-4.2.debian.tar.xz Checksums-Sha256: 49753bdb39c1b37b7361b1a4ef1dfb2600b39abf0b3b91a70fd1a4cca3b0e996 2220 undertaker_1.6.1-4.2.dsc 7a84b800a246d3bd266540dd32cc279d2b244dbd84a43b7c011d97761ebcbc67 19988 undertaker_1.6.1-4.2.debian.tar.xz Files: 52ce1783f1bf2e130a9889918a110963 2220 devel optional undertaker_1.6.1-4.2.dsc e2d0dd2cccb2ea3a06958f5527e1284d 19988 devel optional undertaker_1.6.1-4.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltvRLkACgkQiNJCh6LY mLGSYhAAsr5gtOax7UrxWb0sZUrx2PSqK963n9ts+JZVrYAQSoe9t0pDc3YUDo+W vZ3pOFbEWAYjdLMi9xwUsFWdD/sskBmaTENA4Zj8D72qhc4TALEIxcsi9T7lrCr+ CwvYYiNepbGgcRRcyvSSpvzJPxhBktpAXHFDUGEzy0OJcMGx304cgW7GaHYPYhZT KXzyjCrP6Je78Uvmb56MgprEcGUGUcbTEt/samGVC2BwUGF3bf88fUuTO+XZZyJb QHOJuf5eE/WWyVJFxQPx0/dlARp/QE/BdEiQEnBgOAPoxMFLTpimWMbiuau6bUeR
Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)
Control: tags -1 wontfix On 8/25/18 7:45 PM, Christoph Biedl wrote: > Christoph, who'd like to have a usable qlandkartegt in Debian - how is > QMapShack supposed to be a replacement? Upstream stopped developing QLGT and switches his attention to QMS. You will have to take over maintenance of qlandkartegt if you want to keep it in Debian, but the package and upstream development. As long as there is no one actively working on QLGT upstream the fate of the package is sealed. No one in the Debian GIS team is willing to maintain this EOL package any longer, qmapshack is were we invest our effort. Kind Regards, Bas signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)
Processing control commands: > tags -1 wontfix Bug #906505 [src:qlandkartegt] qlandkartegt: FTBFS in buster/sid (unable to find string literal operator) Added tag(s) wontfix. -- 906505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907146: marked as done (gitless: FTBFS in buster/sid (AttributeError: 'NoneType' object has no attribute 'decode'))
Your message dated Sat, 25 Aug 2018 20:37:52 +
with message-id
and subject line Bug#907146: fixed in gitless 0.8.6-2
has caused the Debian Bug report #907146,
regarding gitless: FTBFS in buster/sid (AttributeError: 'NoneType' object has
no attribute 'decode')
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.)
--
907146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gitless
Version: 0.8.6-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh 'binary-indep' --with=python3 --buildsystem=pybuild
dh_update_autotools_config -i -O--buildsystem=pybuild
dh_autoreconf -i -O--buildsystem=pybuild
dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.6 setup.py config
running config
dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.6_gitless/build/gitless
copying gitless/core.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless
copying gitless/__init__.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless
creating /<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/file_cmd.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/pprint.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_remote.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_resolve.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_history.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_status.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_publish.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_tag.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_init.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_diff.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_track.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_checkout.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_merge.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_fuse.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_commit.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_branch.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/commit_dialog.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_untrack.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl_switch.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/helpers.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/__init__.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
copying gitless/cli/gl.py ->
/<>/.pybuild/cpython3_3.6_gitless/build/gitless/cli
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
'/<>/debian/run-simple-test.sh'
Using directory /tmp/gitless-test.k8LJMc
+ [ 1 -ne 1 ]
+ dir=/tmp/gitless-test.k8LJMc
+ : python3.6
+ : git
+ pwd
+ : /<>/gl.py
+ gl=python3.6 /<>/gl.py
+ [ -d /tmp/gitless-test.k8LJMc ]
+ cd /tmp/gitless-test.k8LJMc
+ python3.6 /<>/gl.py init
Traceback (most recent call last):
File "/<>/gl.py", line 10, in
from gitless.cli import gl
File "/<>/gitless/cli/gl.py", line 43, in
repo = core.Repository()
File "/<>/gitless/core.py", line 115, in __init__
self.git_repo = pygit2.Repository(path)
File "/usr/lib/python3/dist-packages/pygit2/repository.py", line 1208, in
__init__
path = path.decode('utf-8')
AttributeError: 'NoneType' object has no attribute 'decode'
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:
Bug#906139: marked as done (Demote libjs-sphinxdoc hard dependency to a recommendation)
Your message dated Sat, 25 Aug 2018 20:36:48 + with message-id and subject line Bug#906139: fixed in debian-policy 4.2.1.0 has caused the Debian Bug report #906139, regarding Demote libjs-sphinxdoc hard dependency to a recommendation 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.) -- 906139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 4.2.0.1 Severity: wishlist Thanks for maintaining debian-policy; it is one of the things that really distinguishes Debian in an excellent way! For many years, I've installed debian-policy from sid on a stable system to have it readily available, but recent versions of debian-policy have a versioned dependency that is unsatisfyable in stable: Depends: libjs-sphinxdoc (<< 1.7.6.0~), libjs-sphinxdoc (>= 1.7.6) I'm not sure exactly what necessitates a dependency on these (html documentation?). The main files of interest to me are policy.txt.gz and upgrading-checklist.txt.gz, and find it hard to believe those require libjs-sphinxdoc to read. I imagine several of the other formats (.epub, .pdf) also shouldn't require libjs-sphinxdoc. If it is plausible to downgrade to a Recommends, or split out the libjs-sphinxdoc documentation into a separate package, or the text-only documentation into a separate package, or some other resolution, that would be much appreciated! live well, vagrant -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (500, 'stable'), (120, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf, arm64 Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debian-policy depends on: ii libjs-sphinxdoc 1.4.9-2 debian-policy recommends no packages. Versions of packages debian-policy suggests: pn doc-base -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.2.1.0 We believe that the bug you reported is fixed in the latest version of debian-policy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated debian-policy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Aug 2018 13:05:54 -0700 Source: debian-policy Binary: debian-policy debian-policy-ja Architecture: source Version: 4.2.1.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Description: debian-policy - Debian Policy Manual and related documents debian-policy-ja - Debian Policy Manual and related documents (Japanese) Closes: 905251 905696 905909 906139 906901 Changes: debian-policy (4.2.1.0) unstable; urgency=medium . * Policy & Perl Policy: /usr/bin/perl shebang 'must' -> 'should' Wording: Russ Allbery Seconded: Jonathan Nieder Seconded: Dominic Hargreaves Seconded: Sean Whitton Closes: #906901 * Fix inconsistent wording in 4.9 by dropping the word 'maximally' (Closes: #905251). Thanks to several people who pointed out this issue, both in the BTS and in person. . * Demote libjs-sphinxdoc hard dependencies to recommendations by using an override_dh_linktree stanza (Closes: #906139). Thanks to Vagrant Cascadian and Sven Joachim for the report and Ian Jackson for suggesting the fix. * README.md improvements: - Add references to salsa:dbnpolicy/policy-l10n-merge-requests-here repo. - Improve the description of the release process (Closes: #905909) Thanks Osamu Aoki for the patch. - Add a link to the new 'by-complexity' BTS view. - Some other small fixes (Closes: #905696). Thanks Helge Kreutzmann for pointing them out. * Update and alphabetise lists of the Policy delegates in various places.
Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')
Santiago Vila wrote... > make -j1 check > make[1]: Entering directory '/<>' > sparse -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -std=gnu99 -Wall -Wextra -g -I. -DDO_DEBUG > -I/usr/include/libnl3 *.[ch] > /usr/include/err.h:25:11: error: unable to open 'stdarg.h' To reproduce this it's important to remove gcc-7 from the build chroot (apt purge libgcc-7-dev ; apt --purge autoremove). Problem is, sparse appearently uses hardcoded paths and looks for stdarg.h in (among other places) | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h | ^ ... which fails. Solution is to rebuild sparse, building horst was successful then. If this is true (please check!), the interesting question is why this wasn't a problem in earlier gcc version bumps. Christoph signature.asc Description: PGP signature
Bug#907106: (no subject)
On Fri, Aug 24, 2018 at 04:15:14PM +1200, Amos Jeffries wrote:
> For the record the specific autoconf macro:
>
> AC_SEARCH_LIBS([__atomic_load_8],[atomic], ...)
>
> Produces this test code:
>
> "
> | #ifdef __cplusplus
> | extern "C"
> | #endif
> | char __atomic_load_8 ();
> | int
> | main ()
> | {
> | return __atomic_load_8 ();
> | ;
> | return 0;
> | }
> "
>
> Which produces this (on all buildd's including the working ones):
>
> "
> conftest.cpp:56:6: error: new declaration 'char __atomic_load_8()'
> ambiguates built-in declaration 'long long unsigned int
> __atomic_load_8(const volatile void*, int)' [-fpermissive]
> char __atomic_load_8 ();
> ^~~
> conftest.cpp: In function 'int main()':
> conftest.cpp:60:25: error: too few arguments to function 'long long
> unsigned int __atomic_load_8(const volatile void*, int)'
> return __atomic_load_8 ();
> ^
> "
>
> "checking for library containing __atomic_load_8... no"
Thanks for this debugging.
I wrongly thought this was just a case of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
But squid has this already workarounded upstream with -latomic.
I've opened #907277 for this regression with gcc 8.
> Amos
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
Hi Sando, I do support uploading 2 source packages, one for py2, and one for py3. This is the most reasonable solution. Worst case, if that cannot be done, then we got to move forward and restore Py3 support (and eventually drop Py2), but I prefer the former solution. The issue has been opened for nearly 2 months now, with nearly a month without any news, and this makes me a bit nervous, as I need the py3 support to be restored. What's holding you off more? Cheers, Thomas Goirand (zigo)
Bug#907277: autoconf: AC_SEARCH_LIBS with AC_LANG([C++]) broken when using gcc 8
Package: autoconf
Version: 2.69-11
Severity: serious
Originally debugged by Amos Jeffries in #907106:
$ cat configure.ac
AC_INIT
AC_PROG_CXX
AC_LANG([C++])
AC_SEARCH_LIBS([__atomic_load_8],[atomic])
$ autoconf
$ CXX=g++-7 ./configure
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++-7 accepts -g... yes
checking for library containing __atomic_load_8... -latomic
$ CXX=g++-8 ./configure
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++-8 accepts -g... yes
checking for library containing __atomic_load_8... no
$
config.log says:
...
| #ifdef __cplusplus
| extern "C"
| #endif
| char __atomic_load_8 ();
| int
| main ()
| {
| return __atomic_load_8 ();
| ;
| return 0;
| }
configure:2326: g++-8 -o conftest -g -O2 conftest.cpp -latomic >&5
conftest.cpp:16:6: error: new declaration 'char __atomic_load_8()' ambiguates
built-in declaration 'long unsigned int __atomic_load_8(const volatile void*,
int)' [-fpermissive]
char __atomic_load_8 ();
^~~
conftest.cpp: In function 'int main()':
conftest.cpp:20:25: error: too few arguments to function 'long unsigned int
__atomic_load_8(const volatile void*, int)'
return __atomic_load_8 ();
^
...
Processed: fixed 889053 in 1.5.19-1
Processing commands for cont...@bugs.debian.org: > fixed 889053 1.5.19-1 Bug #889053 [gir1.2-ibus-1.0] [gir1.2-ibus-1.0] Fails to install Multi-Arch Bug #897363 [gir1.2-ibus-1.0] gir1.2-ibus-1.0:amd64: Unqualified gir1.2-ibus-1.0 package name in prerm Bug #900077 [gir1.2-ibus-1.0] gir1.2-ibus-1.0: co-installation of amd64 and i386 packages will cause non-recoverable error Bug #905624 [gir1.2-ibus-1.0] Impossible to configure gir1.2-ibus-1.0:amd64, gir1.2-ibus-1.0:i386, libibus-1.0-dev:i386 and libsdl2-dev:i386 Marked as fixed in versions ibus/1.5.19-1. Marked as fixed in versions ibus/1.5.19-1. Marked as fixed in versions ibus/1.5.19-1. Marked as fixed in versions ibus/1.5.19-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 889053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889053 897363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897363 900077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900077 905624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906468: marked as done (goobox: FTBFS in buster/sid (aclocal-1.15: command not found))
Your message dated Sat, 25 Aug 2018 19:19:12 +
with message-id
and subject line Bug#906468: fixed in goobox 3.4.2-9
has caused the Debian Bug report #906468,
regarding goobox: FTBFS in buster/sid (aclocal-1.15: command not found)
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.)
--
906468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:goobox
Version: 3.4.2-8
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh_testdir
# Configuring package
#-./autogen.sh
[ -f config.sub.upstream ] || mv config.sub config.sub.upstream
cp -f /usr/share/misc/config.sub config.sub
[ -f config.guess.upstream ] || mv config.guess config.guess.upstream
cp -f /usr/share/misc/config.guess config.guess
# autoreconf
CFLAGS="-Wall -g -O2" ./configure --build x86_64-linux-gnu CFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2"
CXXFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security" FCFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong" FFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong" GCJFLAGS="-g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong"
LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security" --prefix=/usr --mandir=\${prefix}/share/man
--sysconfdir=/etc --disable-silent-rules
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
[... snipped ...]
config.status: creating data/icons/256x256/apps/Makefile
config.status: creating data/icons/48x48/Makefile
config.status: creating data/icons/48x48/apps/Makefile
config.status: creating data/icons/scalable/Makefile
config.status: creating data/icons/scalable/apps/Makefile
config.status: creating help/Makefile
config.status: creating src/Makefile
config.status: creating src/icons/Makefile
config.status: creating src/ui/Makefile
config.status: creating po/Makefile.in
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing po/stamp-it commands
Configuration:
Source code location : .
Compiler : gcc
Prefix : /usr
CFLAGS : -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wno-deprecated-declarations -Wall
Run in place : no
Enable notification : yes
Enable media keys: yes
Use libcoverart : yes
dh_testdir
# Building package
/usr/bin/make
make[1]: Entering directory '/<>'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /<>/missing
aclocal-1.15 -I m4
/<>/missing: line 81: aclocal-1.15: command not found
WARNING: 'aclocal-1.15' is missing on your system.
You should only need it if you modified 'acinclude.m4' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'aclocal' program is part of the GNU Automake package:
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)
On Fri, 17 Aug 2018 19:22:33 + Santiago Vila wrote: > Package: src:qlandkartegt > Version: 1.8.1+ds-8 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: Hi, I had the same error (and some more) today when building the Arch Linux package. Have a look at my patches here: https://aur.archlinux.org/packages/qlandkartegt/ Do "Download snapshot" and get fix-ver_str.patch from there. Maybe fix-qtgui-include.patch as well if more errors arise. Markus
Processed: Re: Bug#906595: clevis: FTBFS when built with dpkg-buildpackage -A
Processing commands for cont...@bugs.debian.org: > tags 906595 confirmed pending Bug #906595 [src:clevis] clevis: FTBFS when built with dpkg-buildpackage -A Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 906595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907168: pytest-httpbin FTBFS with OpenSSL 1.1.1
This is caused by a Debian change to require a 2048 bit key by default instead of a 1024 bit key. Since this is just for a test, you can either just replace the certificates with larger keys, or lower the security level for the test from 2 to 1. I suggest you just create a new certificates. Kurt
Bug#907022: puma: autopkgtest times out after update of openssl
The most likely reason for a timeout is this: *) SSL_MODE_AUTO_RETRY is enabled by default. Applications that use blocking I/O in combination with something like select() or poll() will hang. This can be turned off again using SSL_CTX_clear_mode(). Many applications do not properly handle non-application data records, and TLS 1.3 sends more of such records. Setting SSL_MODE_AUTO_RETRY works around the problems in those applications, but can also break some. It's recommended to read the manpages about SSL_read(), SSL_write(), SSL_get_error(), SSL_shutdown(), SSL_CTX_set_mode() and SSL_CTX_set_read_ahead() again. Kurt
Bug#907079: offlineimap: Not using SNI
For more information about this, see: https://wiki.openssl.org/index.php/TLS1.3#Server_Name_Indication
Bug#906955: isync: can't verify some ssl certificate(e.g. imap.gmail.com)
This is google enforcing SNI when you use TLS 1.3, see https://wiki.openssl.org/index.php/TLS1.3#Server_Name_Indication Kurt
Bug#907135: boxbackup: FTBFS with OpenSSL 1.1.1
The log shows: > ERROR: SSL or crypto error: loading certificates from > testfiles/clientCerts.pem: error:140AB18F:SSL > routines:SSL_CTX_use_certificate:ee key too small This is caused by a Debian change to require a 2048 bit key by default instead of a 1024 bit key. Since this is just for a test, you can either just replace the certificate with a larger key, or lower the security level for the test from 2 to 1. I suggest you just create a new certificate. Kurt
Bug#906997: lua-sec: FTBFS with OpenSSL 1.1.1: test failure
Hi, The problem is: > Generating a 1024 bit RSA private key Which then later results in: > lua: server.lua:19: error loading certificate (ee key too small) We've changed the default in Debian to require 2048 bit keys. Kurt
Bug#907233: marked as done (qtscrob: FTBFS with Qt 5.11)
Your message dated Sat, 25 Aug 2018 18:04:41 + with message-id and subject line Bug#907233: fixed in qtscrob 0.11+git-5 has caused the Debian Bug report #907233, regarding qtscrob: FTBFS with Qt 5.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qtscrob Version: 0.11+git-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch -Dsrc dh_testdir -a -O-Dsrc dh_update_autotools_config -a -O-Dsrc dh_autoreconf -a -O-Dsrc dh_auto_configure -a -O-Dsrc cd src && qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr Info: creating stash file /<>/qtscrob-0.11+git/src/.qmake.stash Project MESSAGE: Qt version used: 5.11.1 dh_auto_build -a -O-Dsrc cd src && make -j1 make[1]: Entering directory '/<>/qtscrob-0.11+git/src' cd lib/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile /<>/qtscrob-0.11+git/src/lib/lib.pro 'QMAKE_CFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now' 'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now' QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile Project MESSAGE: Scrobbler will be installed in /usr [... snipped ...] g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild/.moc -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o build/.o/moc_libscrobble.o build/.moc/moc_libscrobble.cpp /usr/lib/qt5/bin/moc -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB --include build/.moc/moc_predefs.h -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/<>/qtscrob-0.11+git/src/lib -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtSql -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/8 -I/usr/include/x86_64-linux-gnu/c++/8 -I/usr/include/c++/8/backward -I/usr/lib/gcc/x86_64-linux-gnu/8/include -I/usr/local/include -I/usr/lib/gcc/x86_64-linux-gnu/8/include-fixed -I/usr/include/x86_64-linux-gnu -I/usr/include submit.h -o build/.moc/moc_submit.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>/qtscrob-0.11+git=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
Processed: limit source to debian-policy, tagging 906139, tagging 906901
Processing commands for cont...@bugs.debian.org: > limit source debian-policy Limiting to bugs with field 'source' containing at least one of 'debian-policy' Limit currently set to 'source':'debian-policy' > tags 906139 + pending Bug #906139 [debian-policy] Demote libjs-sphinxdoc hard dependency to a recommendation Added tag(s) pending. > tags 906901 + pending Bug #906901 [debian-policy] debian-policy: Perl script shebang requirement is disturbing and inconsistent with rest of policy Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 906139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906139 906901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: openmpi: liggghts build on i386 times out
Processing commands for cont...@bugs.debian.org: > affects 907267 + src:liggghts Bug #907267 [src:openmpi] openmpi: liggghts build on i386 times out Added indication that 907267 affects src:liggghts > thanks Stopping processing here. Please contact me if you need assistance. -- 907267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906505: qlandkartegt: FTBFS in buster/sid (unable to find string literal operator)
Santiago Vila wrote... > /<>/qlandkartegt-1.8.1+ds/3rdparty/map2gcm/main.cpp:43:46: error: > unable to find string literal operator 'operator""_MKSTR' with 'const char > [20]', 'long unsigned int' arguments > #define VER_STR > _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) > ^ That was easy to catch, earlier compiler versions gave according warnings. But there is more, it seems (wild guess) the Qt header were re-organized or there is another reason why several modules fail to build with "error: invalid use of incomplete type 'class XXX'". Fix was done by wild-guessing. The result however is not usable - qlandkartegt stalls at the splash screen, waiting for some data. This is the point where somebody with Qt programming experience should take over. Or I'll try to continue, but not today. Patches are attached. Christoph, who'd like to have a usable qlandkartegt in Debian - how is QMapShack supposed to be a replacement? --- a/3rdparty/cache2gtiff/main.cpp +++ b/3rdparty/cache2gtiff/main.cpp @@ -35,7 +35,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR"cache2gtiff, Version " VER_STR --- a/3rdparty/map2gcm/main.cpp +++ b/3rdparty/map2gcm/main.cpp @@ -40,7 +40,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR"map2gcm, Version " VER_STR #define MAX_TILE_SIZE 1024 --- a/3rdparty/map2jnx/main.cpp +++ b/3rdparty/map2jnx/main.cpp @@ -51,7 +51,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR"map2jnx, Version " VER_STR #define JNX_MAX_TILES 5 //6250 --- a/3rdparty/map2rmap/main.cpp +++ b/3rdparty/map2rmap/main.cpp @@ -33,7 +33,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR"map2rmap, Version " VER_STR --- a/3rdparty/map2rmp/CFileGenerator.cpp +++ b/3rdparty/map2rmp/CFileGenerator.cpp @@ -27,7 +27,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) extern "C" --- a/3rdparty/map2rmp/main.cpp +++ b/3rdparty/map2rmp/main.cpp @@ -32,7 +32,7 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR"map2rmp, Version " VER_STR int main(int argc, char ** argv) --- a/src/version.h +++ b/src/version.h @@ -23,6 +23,6 @@ #define _MKSTR(x) _MKSTR_1(x) #endif -#define VER_STR _MKSTR(VER_MAJOR)"."_MKSTR(VER_MINOR)"."_MKSTR(VER_STEP) +#define VER_STR _MKSTR(VER_MAJOR) "." _MKSTR(VER_MINOR) "." _MKSTR(VER_STEP) #define WHAT_STR "QLandkarte GT, Version " VER_STR #endif //VERSION_H --- a/src/CDlgProxy.cpp +++ b/src/CDlgProxy.cpp @@ -21,6 +21,7 @@ #include "CMainWindow.h" #include +#include CDlgProxy::CDlgProxy(QString , QString , QWidget *parent) : QDialog(parent) --- a/src/CDiaryEdit.cpp +++ b/src/CDiaryEdit.cpp @@ -34,6 +34,7 @@ #include "CSettings.h" #include +#include #include #include #include --- a/src/CTextEditWidget.cpp +++ b/src/CTextEditWidget.cpp @@ -56,6 +56,7 @@ #include "CCanvas.h" #include +#include #include CTextEditWidget::CTextEditWidget(QWidget * parent) --- a/src/CLiveLogToolWidget.cpp +++ b/src/CLiveLogToolWidget.cpp @@ -20,6 +20,7 @@ #include "CLiveLogDB.h" #include +#include CLiveLogToolWidget::CLiveLogToolWidget(QTabWidget * parent) :QWidget(parent) signature.asc Description: PGP signature
Processed: Re: Bug#906139: debian-policy: versioned depends on libjs-sphinxdoc unsatisfiable on stretch
Processing control commands: > severity -1 serious Bug #906139 [debian-policy] Switch back to dh_sphinxdoc from dh_linktree Severity set to 'serious' from 'wishlist' > retitle -1 Demote libjs-sphinxdoc hard dependency to a recommendation Bug #906139 [debian-policy] Switch back to dh_sphinxdoc from dh_linktree Changed Bug title to 'Demote libjs-sphinxdoc hard dependency to a recommendation' from 'Switch back to dh_sphinxdoc from dh_linktree'. > unblock -1 by 658238 Bug #906139 [debian-policy] Demote libjs-sphinxdoc hard dependency to a recommendation 906139 was blocked by: 658238 906139 was not blocking any bugs. Removed blocking bug(s) of 906139: 658238 > tag -1 -help Bug #906139 [debian-policy] Demote libjs-sphinxdoc hard dependency to a recommendation Removed tag(s) help. -- 906139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902470: Status?
Hi, My packages have been removed from testing due to this bug. Can we remove failing test and lower bug severity waiting for upstream fix? Else i will need to patch my packages to remove influx support, removing features. Bug impact looks quite low. Thanks Olivier
Bug#907267: openmpi: liggghts build on i386 times out
Source: openmpi Version: 3.1.1.real-6 Severity: serious Hi Alastair The last two builds of liggghts on i386 [1] against openmpi 3.1.1.real-6 and 3.1.1.real-7 have timed out. Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=liggghts=i386
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 907239 https://github.com/ldc-developers/ldc/issues/2824 Bug #907239 [src:ldc] ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double Set Bug forwarded-to-address to 'https://github.com/ldc-developers/ldc/issues/2824'. > -- Stopping processing here. Please contact me if you need assistance. -- 907239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907210: marked as done (libfastahack: ftbfs on some architectures (symbols))
Your message dated Sat, 25 Aug 2018 16:04:19 + with message-id and subject line Bug#907210: fixed in libfastahack 0.0+git20160702.bbc645f+dfsg-3 has caused the Debian Bug report #907210, regarding libfastahack: ftbfs on some architectures (symbols) 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.) -- 907210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: libfastahack version: 0.0+git20160702.bbc645f+dfsg-2 severity: serious Hi, The latest upload of libfastahack FTBFS on a number of architectures (it seems to be related to the symbols): https://buildd.debian.org/status/package.php?p=libfastahack Cheers, Ivo --- End Message --- --- Begin Message --- Source: libfastahack Source-Version: 0.0+git20160702.bbc645f+dfsg-3 We believe that the bug you reported is fixed in the latest version of libfastahack, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libfastahack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Aug 2018 17:40:36 +0200 Source: libfastahack Binary: libfastahack0 libfastahack-dev fastahack Architecture: source Version: 0.0+git20160702.bbc645f+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: fastahack - utility for indexing and sequence extraction from FASTA files libfastahack-dev - library for indexing and sequence extraction from FASTA files (de libfastahack0 - library for indexing and sequence extraction from FASTA files (li Closes: 907210 Changes: libfastahack (0.0+git20160702.bbc645f+dfsg-3) unstable; urgency=medium . * Provide symbols for selected architectures only Closes: #907210 Checksums-Sha1: 82e1a4156bb0688b1794ae4245130a5b03b41fa1 2273 libfastahack_0.0+git20160702.bbc645f+dfsg-3.dsc c87ec103523e1495d830aaa00a003e7f563f865d 5972 libfastahack_0.0+git20160702.bbc645f+dfsg-3.debian.tar.xz Checksums-Sha256: d2308b88e7fa9e25cd7730dc219a689b5f2ce8f536605d0b037ba9b1a420fdea 2273 libfastahack_0.0+git20160702.bbc645f+dfsg-3.dsc 27f0ff9427e8c2793f5f134026b96de7db8bc71195a71b6c019ae772e24fd283 5972 libfastahack_0.0+git20160702.bbc645f+dfsg-3.debian.tar.xz Files: 57ccf2bf92ce86dcc11553801a1904ec 2273 science optional libfastahack_0.0+git20160702.bbc645f+dfsg-3.dsc d126cfa0ec1791be20cb5e3d2b07cd21 5972 science optional libfastahack_0.0+git20160702.bbc645f+dfsg-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAluBebcRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEkMBAAllBsyOGZPAY17ITpaJe5Dz4TMmS7APF0 JI3kzU3fctStIbVtcRhCt+FaEdnyJsOnl7V+e4JTRTdxNsA32fWDhetjlaB9dAXY NPzrdjhlsAm0kI+GsGMyzrKJJl5psbRbpFx1knymb7L5x0PjhGNtWZxcZ36VaY6u LtlRHwchk6iCCX1/kp0GnzR4aIfiOIDpAwCxK79FuQiOThwMzzQpT5ZpAmfvlhqm znpSCJ/lkxATlJTLVmK4IPGSUMd4flnTvIorbg3jakhjsL8se4IirDdhoKeQch+1 v9c+1Ib0F3V0bT0Ah2FNqGM2GEIrljAHGyjkeMwOCy7RCoyyA3buBMHTa7Bt+057 yQ2JTpWqZxFmLnF6OI/CuvvAdoT1k7UVOt4auRLugxNT14Al+/okIA2OwSOHh1+W 8kN40Sp1U9XFuqTYM/6m0MQTz8gnkiVzzqBnBpYEfcezHWgpfYTlLxiPBJUl/va8 fPz/eC7LexrkKjqXRbSLHGkcgKXR9ACyZlaVbTpl7GuH60E5d/meCJeWkhuMFgkd evxUYvjfwq96V4U94z2SU3c5UBKhIopwdBQWbOR1tyx+xLQhg/Jm7a7e2L95/cJ7 hsYXNNlRxAZruSXtdZWRuXvDkzhALzXOMv4CFMxgOCw6a630anOqd4qSFN32ZMbB iwIn+X5M2ds= =dXyQ -END PGP SIGNATURE End Message ---
Processed: tagging 906426
Processing commands for cont...@bugs.debian.org: > tags 906426 - fixed Bug #906426 [automake] gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo) Bug #906557 [automake] ratpoison: FTBFS in buster/sid (makeinfo: command not found) Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found) Bug #906775 [automake] hamlib: FTBFS in buster/sid (makeinfo: command not found) Bug #906778 [automake] guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found) Bug #906790 [automake] libtasn1-6 FTBFS during arch-only: missing makeinfo Removed tag(s) fixed. Removed tag(s) fixed. Removed tag(s) fixed. Removed tag(s) fixed. Removed tag(s) fixed. Removed tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426 906557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906557 906774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906774 906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775 906778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906778 906790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906426: Further information is in #906774
Further information is in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906774#30 cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: tagging 906426
Processing commands for cont...@bugs.debian.org: > tags 906426 - pending Bug #906426 [automake] gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo) Bug #906557 [automake] ratpoison: FTBFS in buster/sid (makeinfo: command not found) Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found) Bug #906775 [automake] hamlib: FTBFS in buster/sid (makeinfo: command not found) Bug #906778 [automake] guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found) Bug #906790 [automake] libtasn1-6 FTBFS during arch-only: missing makeinfo Removed tag(s) pending. Removed tag(s) pending. Removed tag(s) pending. Removed tag(s) pending. Removed tag(s) pending. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426 906557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906557 906774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906774 906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775 906778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906778 906790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906375: Tried new upstream version
On Sat, Aug 25, 2018 at 04:48:05PM +0200, Emmanuel Bourg wrote: > > Do you get the same build failure with the new version? No, it is different: ... [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 [FATAL] Non-resolvable parent POM for com.itextpdf:itext-pdfa:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 [FATAL] Non-resolvable parent POM for com.itextpdf:itext-xtra:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 [FATAL] Non-resolvable parent POM for com.itextpdf.tool:xmlworker:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 @ [ERROR] The build could not read 4 projects -> [Help 1] [ERROR] [ERROR] The project com.itextpdf:itextpdf:5.5.13 (/build/libitext5-java-5.5.13/itext/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 -> [Help 2] [ERROR] [ERROR] The project com.itextpdf:itext-pdfa:5.5.13 (/build/libitext5-java-5.5.13/pdfa/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.itextpdf:itext-pdfa:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 -> [Help 2] [ERROR] [ERROR] The project com.itextpdf:itext-xtra:5.5.13 (/build/libitext5-java-5.5.13/xtra/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.itextpdf:itext-xtra:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 -> [Help 2] [ERROR] [ERROR] The project com.itextpdf.tool:xmlworker:5.5.13 (/build/libitext5-java-5.5.13/xmlworker/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.itextpdf.tool:xmlworker:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. ... So probably some missing Maven dependencies which might be promissing respecting the old bug (or the old bug is covered by these issues. Hope this helps Andreas. -- http://fam-tille.de
Bug#906774: Bug#906790: libtasn1-6 FTBFS during arch-only: missing makeinfo
Control: reassign 906790 automake Control: reassign 906778 automake Control: reassign 906775 automake Control: reassign 906557 automake Control: reassign 906426 automake Control: forcemerge -1 906790 906778 906775 906557 906426 Control: affects -1 src:guile-gnome-platform src:hamlib src:ratpoison src:gnuchess On Sat, Aug 25, 2018 at 01:28:34PM +0200, Andreas Metzler wrote: > On 2018-08-23 Andreas Metzler wrote: > [...] > > Almost, it is caused by upgrading automake. Building with automake > > 1:1.16.1-1 fails, downgrading to 1:1.15.1-3.1 lets the build succeed. > > Which seems to have hit other packages, too. With one report (#906774) > > reassigned to automake. > > > FWIW at first glance I have not found not-too-involved a workaround yet. > > I might be forced to move stuff from Build-Depends-Indep to > > Build-Depends. > > Hello, > > this is caused mdate-sh. > > The rule that checks whether version.texi is up to date runs mdate-sh on > the source texi file and compares whether the result differs from the > current timestamp in version.texi state.[1] If the timestamp differs > version.texi is regenerated and a rebuild of the info documentation is > triggered. > > mdate-sh in automake 1:1.16.1-1 has grown "support" for > SOURCE_DATE_EPOCH. If SOURCE_DATE_EPOCH is set in the environment then > its value is used and the modification time of the file is ignored. > Which causes the build-failure by tricking make into thinking the info > file is out of date. > > This seems to be a Debian specific change. The patch was already present > in 1:1.15.1-3 (and -3.1) *source* but did not end up changing > usr/share/automake-1.15/mdate-sh. It is however present in 1:1.16.1-1's > /usr/share/automake-1.16/mdate-sh. Thanks for your analysis. I am merging the other bugs with this one in automake: It might be desirable to rebuild .info files when building Debian packages, but the problem is that this currently also forces users of a tarball of upstream software generated on Debian to install texinfo. > cu Andreas >... cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: Re: Bug#906774: Bug#906790: libtasn1-6 FTBFS during arch-only: missing makeinfo
Processing control commands: > reassign 906790 automake Bug #906790 [src:libtasn1-6] libtasn1-6 FTBFS during arch-only: missing makeinfo Bug reassigned from package 'src:libtasn1-6' to 'automake'. No longer marked as found in versions libtasn1-6/4.13-3. Ignoring request to alter fixed versions of bug #906790 to the same values previously set > reassign 906778 automake Bug #906778 [src:guile-gnome-platform] guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found) Bug reassigned from package 'src:guile-gnome-platform' to 'automake'. No longer marked as found in versions guile-gnome-platform/2.16.4-5. Ignoring request to alter fixed versions of bug #906778 to the same values previously set > reassign 906775 automake Bug #906775 [src:hamlib] hamlib: FTBFS in buster/sid (makeinfo: command not found) Bug reassigned from package 'src:hamlib' to 'automake'. No longer marked as found in versions hamlib/3.1-8. Ignoring request to alter fixed versions of bug #906775 to the same values previously set > reassign 906557 automake Bug #906557 [src:ratpoison] ratpoison: FTBFS in buster/sid (makeinfo: command not found) Bug reassigned from package 'src:ratpoison' to 'automake'. No longer marked as found in versions ratpoison/1.4.8-2. Ignoring request to alter fixed versions of bug #906557 to the same values previously set > reassign 906426 automake Bug #906426 [gnuchess] gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo) Bug reassigned from package 'gnuchess' to 'automake'. No longer marked as found in versions gnuchess/6.2.5-1. Ignoring request to alter fixed versions of bug #906426 to the same values previously set > forcemerge -1 906790 906778 906775 906557 906426 Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found) Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found) Added tag(s) sid, fixed, buster, patch, confirmed, and pending. Bug #906790 [automake] libtasn1-6 FTBFS during arch-only: missing makeinfo Added indication that 906790 affects src:libtasn1-6,src:dico Marked as found in versions automake-1.16/1:1.16.1-1. Added tag(s) pending, confirmed, patch, sid, buster, and fixed. Bug #906426 [automake] gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo) Added indication that 906426 affects src:libtasn1-6,src:dico Marked as found in versions automake-1.16/1:1.16.1-1. Added tag(s) fixed, sid, buster, confirmed, and pending. Bug #906775 [automake] hamlib: FTBFS in buster/sid (makeinfo: command not found) Added indication that 906775 affects src:libtasn1-6,src:dico Marked as found in versions automake-1.16/1:1.16.1-1. Added tag(s) patch, sid, and buster. Bug #906778 [automake] guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found) Added indication that 906778 affects src:libtasn1-6,src:dico Marked as found in versions automake-1.16/1:1.16.1-1. Added tag(s) fixed, sid, buster, patch, confirmed, and pending. Bug #906557 [automake] ratpoison: FTBFS in buster/sid (makeinfo: command not found) Added indication that 906557 affects src:libtasn1-6,src:dico Marked as found in versions automake-1.16/1:1.16.1-1. Added tag(s) patch, fixed, confirmed, and pending. Merged 906426 906557 906774 906775 906778 906790 > affects -1 src:guile-gnome-platform src:hamlib src:ratpoison src:gnuchess Bug #906774 [automake] dico: FTBFS in buster/sid (makeinfo: command not found) Bug #906426 [automake] gnuchess: FTBFS: makeinfo: command not found (missing build-dependency on texinfo) Bug #906557 [automake] ratpoison: FTBFS in buster/sid (makeinfo: command not found) Bug #906775 [automake] hamlib: FTBFS in buster/sid (makeinfo: command not found) Bug #906778 [automake] guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found) Bug #906790 [automake] libtasn1-6 FTBFS during arch-only: missing makeinfo Added indication that 906774 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess Added indication that 906426 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess Added indication that 906557 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess Added indication that 906775 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess Added indication that 906778 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess Added indication that 906790 affects src:guile-gnome-platform, src:hamlib, src:ratpoison, and src:gnuchess -- 906426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906426 906557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906557 906774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906774 906775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906775 906778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906778 906790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906790 Debian Bug Tracking System Contact ow...@bugs.debian.org
Bug#906338: marked as done (blitz++: FTBFS in buster/sid (texi2dvi: pdfetex exited with bad status))
Your message dated Sat, 25 Aug 2018 15:04:03 + with message-id and subject line Bug#906338: fixed in blitz++ 1:1.0.1+ds-3 has caused the Debian Bug report #906338, regarding blitz++: FTBFS in buster/sid (texi2dvi: pdfetex exited with bad status) 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.) -- 906338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:blitz++ Version: 1:1.0.1+ds-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep -with autoreconf --builddirectory=_build --no-parallel dh_update_autotools_config -i -O--builddirectory=_build dh_autoreconf -i -O--builddirectory=_build libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'. libtoolize: copying file 'config/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:86: installing 'config/compile' configure.ac:12: installing 'config/config.guess' [... snipped ...] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/arrays-usertype.texi (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build/doc/examples/fixed-point.texi [63]) (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build/doc/examples/fixed.texi) (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build/doc/examples/fixed.out)) Chapter 6 [64] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/arrays-indirect.texi [65] [66] [67]) Chapter 7 [68] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/tinyvector.texi [69]) Chapter 8 [70] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/parallel.texi) Chapter 9 [71] [72] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/random.texi [73] [74] [75]) Chapter 10 [76] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/numinquire.texi [77] [78]) Chapter 11 [79] [80] (/build/blitz++-jbzMEc/blitz++-1.0.1+ds/doc/faq.texi [81] [82]) (Blitz Keyword Index) [83] [84] No file blitz.fns. (Concept Index) [85] [86] No file blitz.cps. [87] [88] ) (see the transcript file for additional information) Output written on blitz.pdf (94 pages, 501569 bytes). Transcript written on blitz.log. /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. make[4]: *** [Makefile:615: blitz.pdf] Error 1 make[4]: Leaving directory '/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build/doc' make[3]: *** [Makefile:754: pdf-recursive] Error 1 make[3]: Leaving directory '/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build/doc' make[2]: *** [Makefile:562: pdf-recursive] Error 1 make[2]: Leaving directory '/build/blitz++-jbzMEc/blitz++-1.0.1+ds/_build' make[1]: *** [debian/rules:29: override_dh_auto_build-indep] Error 2 make[1]: Leaving directory '/build/blitz++-jbzMEc/blitz++-1.0.1+ds' make: *** [debian/rules:13: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/blitz++.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: blitz++ Source-Version: 1:1.0.1+ds-3 We believe that the bug you reported is fixed in the latest version of blitz++, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated blitz++ package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Aug 2018 14:37:39 + Source: blitz++ Binary: libblitz0v5
Processed: tagging 907233
Processing commands for cont...@bugs.debian.org: > tags 907233 + pending Bug #907233 [src:qtscrob] qtscrob: FTBFS with Qt 5.11 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 907233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907228: kaffeine: FTBFS with Qt 5.11
Hello, this might be fixed by upstream commit [1], connected to this upstream bug [2]. Unfortunately not yet contained in an upstream release. [1] https://cgit.kde.org/kaffeine.git/commit/src/dvb/dvbdevice_linux.cpp?id=06b78c5f24891fd38d25ed64f5029106eec7c4fb [2] https://bugs.kde.org/show_bug.cgi?id=393222 Kind regards, Bernhard
Bug#859791: marked as done (wvstreams: Please migrate to openssl1.1 in Buster)
Your message dated Sat, 25 Aug 2018 14:49:28 + with message-id and subject line Bug#859791: fixed in wvstreams 4.6.1-13 has caused the Debian Bug report #859791, regarding wvstreams: Please migrate to openssl1.1 in Buster 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.) -- 859791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wvstreams Version: 4.6.1-11 Severity: important Tags: sid buster User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1-trans Please migrate to libssl-dev in the Buster cycle. The bug report about the FTBFS is #828603. The log of the FTBFS can be found at https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/wvstreams_4.6.1-8_amd64-20160529-1553 Sebastian --- End Message --- --- Begin Message --- Source: wvstreams Source-Version: 4.6.1-13 We believe that the bug you reported is fixed in the latest version of wvstreams, 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 859...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated wvstreams package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Aug 2018 16:29:57 +0200 Source: wvstreams Binary: libwvstreams4.6-base libwvstreams4.6-extras libuniconf4.6 libwvstreams4.6-doc libwvstreams-dev uniconfd uniconf-tools Architecture: source Version: 4.6.1-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Gianfranco Costamagna Description: libuniconf4.6 - C++ network libraries for rapid application development libwvstreams-dev - Development libraries and header files for libwvstreams4.6 libwvstreams4.6-base - C++ network libraries for rapid application development libwvstreams4.6-doc - Documentation for WvStreams libwvstreams4.6-extras - C++ network libraries for rapid application development uniconf-tools - Tools to interface with UniConf uniconfd - Server that manages UniConf elements Closes: 859791 Changes: wvstreams (4.6.1-13) unstable; urgency=medium . * QA upload. * Remove old openssl build-dependency . [ Reiner Herrmann ] * Port to openssl 1.1 (Closes: #859791) Checksums-Sha1: 105bedaaf4f3646b0ff1eac60256be9765cd39c0 2275 wvstreams_4.6.1-13.dsc c4aa7220cbce3203d6971161a088c62c42897e5d 20452 wvstreams_4.6.1-13.debian.tar.xz 8719dec7df77a2154f8474d96ce6963c996eab61 8135 wvstreams_4.6.1-13_source.buildinfo Checksums-Sha256: 3c9e4542678e368cd8ff403e830549fcc5b3ee80385e3174125a11ea7336c400 2275 wvstreams_4.6.1-13.dsc de294bf90970c5256397fa96c9dd34cf9fb3b9f85786ef13e015f9c8c1acd4ff 20452 wvstreams_4.6.1-13.debian.tar.xz cd664d2c98140cb6c2884a70b2a7011ec4e709fe68c1a2c784b564f55797cb87 8135 wvstreams_4.6.1-13_source.buildinfo Files: 1d99a2a3a1198a026a5846b16a138b51 2275 libs optional wvstreams_4.6.1-13.dsc 50952ea9ab616a13a8f928a83a6162af 20452 libs optional wvstreams_4.6.1-13.debian.tar.xz ca0ff4fe1e69a5c2332909052ce483a1 8135 libs optional wvstreams_4.6.1-13_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAluBaLwACgkQ808JdE6f XdkQ7BAAm5TfSYH2T0FziyThZLqZ52qDa6BAWXG2dlwX4R/eKXF15EPYxUPtPo3l ilwInoyvtkHOsNkUXnyE0mDIMMrV8mZ2FoRxlwYHg81awYLObepsgt54YBYaNA7r avJ0gHkcBnKBiX2SYbGaETswmImBvxyDgRdAzRSSvwccU7K1syNFgd9gYWsHDhTy 458RkssOSuPTIklpXb7mrnLupKjOT/v3worwnwkBRRhprIcZsxmZf9LZr+LAqoLQ Q9R2V6CIWJkUjSDkAZHYwpMsGZwRa9xU/EW2nKJa/LpZFB6jAexp4WFbMTKFAntO l4K8NOeiiKgyS3AGoCKa9mGA1Zatdgql3ltLf9bv7mZ5j/GM/okakCmzgZni1L1C CwSVriWaaRSXPadG9bcpBdY+Hl3UgV3vimaeimDOjyXWuGtVwoCX5qizh+DG7zbH uz046o6l58uNEZexC5wBk43+UzLeoIS0/oftK/yGTBrZC03VyH6MVK2wHiTkI351 zECLwhmc8FZswcbOobsSlhCn6VuiEa9lJ4Pqsv2Mz1iFQks23cmDHH5ijzgYdtNT 7ETvOe9aKa66KLgV36yOi2Sck3L3gUidWGI5ZNw1mLBHMKE7BvsxrxQGM0beg4hG UW536Vi/VIZdd22QksZUAFgBpH74hxi8YHqk6gK0oSaCQhgdRaA= =JJCW -END PGP SIGNATURE End Message ---
Bug#906375: Tried new upstream version
On 25/08/2018 09:00, Andreas Tille wrote: > I realised that there is a new upstream version, fixed the watch file in > Git and tried to build the package. Unfortunately the build fails as > well. Do you get the same build failure with the new version? Emmanuel Bourg
Bug#906346: compiz: FTBFS in buster/sid (unrecognized command line option '-Wno-unused-private-field')
Hi, Santiago Vila (2018-08-17): > [ 28%] Building CXX object > plugins/animationaddon/CMakeFiles/animationaddon.dir/src/particle.cpp.o > cd > /<>/compiz-0.9.13.1+18.04.20180302/obj-x86_64-linux-gnu/plugins/animationaddon > && /usr/bin/c++ -DANIMATIONADDON_DEFSADD -DHAVE_CONFIG_H > -DHAVE_SCANDIR_POSIX -Danimationaddon_EXPORTS > -I/<>/compiz-0.9.13.1+18.04.20180302/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src > -I/<>/compiz-0.9.13.1+18.04.20180302/src/timer/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/string/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/pluginclasshandler/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/point/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/rect/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/servergrab/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/region/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/window/geometry/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/window/geometry-saver/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/window/extents/ > include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/window/constrainment/include > -I/<>/compiz-0.9.13.1+18.04.20180302/src/logmessage/include > -I/<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src > -I/<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/include > -I/<>/compiz-0.9.13.1+18.04.20180302/obj-x86_64-linux-gnu/generated > -I/<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/../composite/include > > -I/<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/../opengl/include > > -I/<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/../animation/include > -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 > -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 > -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include > -I/usr/include/startup-notification-1.0 > -I/<>/compiz-0.9.13.1+18.04.20180302/obj-x86_64-lin > ux-gnu -g -O2 > -fdebug-prefix-map=/<>/compiz-0.9.13.1+18.04.20180302=. > -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 > -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Wno-unused-private-field > -Wno-unused-local-typedefs -Wno-deprecated-declarations -Werror -std=c++11 > -fPIC -Wall -Wno-unused-private-field -Wno-unused-local-typedefs > -Wno-deprecated-declarations -Werror -std=c++11 -fPIC -Wall > -Wno-unused-private-field -Wno-unused-local-typedefs > -Wno-deprecated-declarations -Werror -std=c++11 -fPIC -Wall > -Wno-unused-private-field -Wno-unused-local-typedefs > -Wno-deprecated-declarations -Werror -std=c++11 -fPIC -Wall > -Wno-unused-private-field -Wno-unused-local-typedefs > -Wno-deprecated-declarations -Werror -std=c++11 -O2 -g -DNDEBUG -fPIC > -DPREFIX='"/usr"' -o CMakeFiles/animationaddon.dir/src/particle.cpp.o -c > /<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src/particle.cpp > In file included from /usr/include/string.h:494, > from > /<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src/private.h:1, > from > /<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src/particle.cpp:37: > In function 'void* memcpy(void*, const void*, size_t)', > inlined from 'void ParticleSystem::draw(const GLMatrix&, int, int)' at > /<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src/particle.cpp:178:9: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:33: error: 'void* > __builtin_memcpy(void*, const void*, long unsigned int)' accessing 16 bytes > at offsets 8 and 0 overlaps 8 bytes at offset 8 [-Werror=restrict] >return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); > ~~~^~~ > In function 'void* memcpy(void*, const void*, size_t)', > inlined from 'void ParticleSystem::draw(const GLMatrix&, int, int)' at > /<>/compiz-0.9.13.1+18.04.20180302/plugins/animationaddon/src/particle.cpp:192:13: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:33: error: 'void* > __builtin_memcpy(void*, const void*, long unsigned int)' accessing 16 bytes > at offsets 8 and 0 overlaps 8 bytes at offset 8 [-Werror=restrict] >return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); > ~~~^~~ > At global scope: > cc1plus: error: unrecognized command line option '-Wno-unused-private-field' > [-Werror] > cc1plus: error: unrecognized command line option '-Wno-unused-private-field' > [-Werror] > cc1plus: error: unrecognized command line option '-Wno-unused-private-field' > [-Werror] > cc1plus: error: unrecognized command line option '-Wno-unused-private-field' > [-Werror] > cc1plus: error: unrecognized command line option '-Wno-unused-private-field' > [-Werror] > cc1plus: all warnings being treated as errors I've seen this, memcpy vs. memmove issues,
Bug#907049: [Pkg-openssl-devel] Bug#907049: Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
severity 907049 important thanks On Sat, Aug 25, 2018 at 03:06:47PM +0200, Kurt Roeckx wrote: > Anyway, that seems to mean that openvpn only supports TLS 1.0 for > some reason. I have no idea how openvpn works, but if it uses > TLS 1.0, it really should switch to 1.2 or 1.3. So it's my understanding now that it might be a client that tries to connect to your server that doesn't support TLS 1.2. openvpn also supports configurating the minimum TLS version, you can change the openvpn configuration file to override that the minimum should be TLSv1. Kurt
Processed: Re: [Pkg-openssl-devel] Bug#907049: Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
Processing commands for cont...@bugs.debian.org: > severity 907049 important Bug #907049 [openvpn] openvpn: ssl_choose_client_version:version too low Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 907049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904761: marked as done (wammu: missing dependency on python-six)
Your message dated Sat, 25 Aug 2018 13:51:37 + with message-id and subject line Bug#904761: fixed in wammu 0.44-1.1 has caused the Debian Bug report #904761, regarding wammu: missing dependency on python-six 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.) -- 904761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wammu Version: 0.44-1 Severity: serious $ wammu Traceback (most recent call last): File "/usr/bin/wammu", line 47, in import Wammu.Locales File "/usr/lib/python2.7/dist-packages/Wammu/Locales.py", line 31, in import six ImportError: No module named six Andreas --- End Message --- --- Begin Message --- Source: wammu Source-Version: 0.44-1.1 We believe that the bug you reported is fixed in the latest version of wammu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated wammu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Aug 2018 15:40:03 +0300 Source: wammu Binary: wammu Architecture: source Version: 0.44-1.1 Distribution: unstable Urgency: high Maintainer: Michal Čihař Changed-By: Adrian Bunk Description: wammu - GTK application to control your mobile phone Closes: 904761 Changes: wammu (0.44-1.1) unstable; urgency=high . * Non-maintainer upload. * Add the missing dependency on python-six. (Closes: #904761) Checksums-Sha1: 2b9665183b2c4eeec4added4c82470bd7315632e 1864 wammu_0.44-1.1.dsc 8792f6fa1439ebc1009ae1d3ad6685d40d6fd202 4892 wammu_0.44-1.1.debian.tar.xz Checksums-Sha256: d1bccfb976363327a5fe8bfc6809428b7d128bef5d5bdbc8fbcce21a4a989366 1864 wammu_0.44-1.1.dsc 0dc3f3c549b0bb02e04f6265dbba375a505a38f6df332bdd22ab46348b82fcb3 4892 wammu_0.44-1.1.debian.tar.xz Files: f727943914b06b14ae9cb078e901e09c 1864 comm optional wammu_0.44-1.1.dsc 57bee67e482b91426e8ff1fdc02b3dbb 4892 comm optional wammu_0.44-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltu2bIACgkQiNJCh6LY mLFtYxAAtz4nxzH6wNC5VrWU3dpVmhMm0y+zzqw1kD1AQoLoIKdOMHG/hBV+hhcK UCC9tUCiJrp8u5e32RyqS8q3AqwdPT379AsBgSmUZ5k5j1f0kRMgPQQsW94sWrcS I+lIK7yXUN7vtUzu8eYpPJy+5xq7WMLTQtEoifyOi9gdrtJN9u3nHw9zjNx0rkyf YZsYXilr5DTQumKlrh7wUpyJ9ksZpcBAi23YeNddOPtUs8ehB6J2S35dNG0N+1r+ ToerFO+NgWoLoCw8P6cazRgcjCAP8jh1p4X4WWh4rrOGaiyo/c1S9yaWx5JObTkC 57/XbM0dQZ0qry2JNqAFIxmZ0PS89ZU8DyhqY+L4iybEWkZEJ+NIL4NJqGxvwJHe 19a8hpj9N0/f2P1Wg0Ed1+Rn03rrXpnMcO5Pz/CJikqTC/fuyb90OW3knUdNsrVh 0mrJE3G13dXKGXjn7cIAZzfdCyberwKzudtF106jYBvsqLYXyBzjedeaPx6++Sd+ pqO+RC0WLXF8+jv8g9kB2HF4usRSB/HA5XrM1EIJH7zZ7Xy6/kBJnmfVeaYvbwKZ BP0iML5q/lvNWe7JmxhfuK4aaCllAEEr2J/qXFBhKGntxoMsWMkT802wAq4qxP8B 6R4G4DQFIpRqB0MsjrTx7MecaEkVOEVayAwP4Fs8aZ/OFJFWy6c= =4KcP -END PGP SIGNATURE End Message ---
Processed: tagging 873747, severity of 873747 is important
Processing commands for cont...@bugs.debian.org: > tags 873747 + moreinfo unreproducible Bug #873747 [astroidmail] astroid segfault on startup when config is available. Added tag(s) unreproducible and moreinfo. > severity 873747 important Bug #873747 [astroidmail] astroid segfault on startup when config is available. Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 873747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904756: marked as done (wfuzz: missing dependency on python-pkg-resources)
Your message dated Sat, 25 Aug 2018 13:36:42 + with message-id and subject line Bug#904756: fixed in wfuzz 2.2.11-1.1 has caused the Debian Bug report #904756, regarding wfuzz: missing dependency on python-pkg-resources 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.) -- 904756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wfuzz Version: 2.2.11-1 Severity: serious $ wfuzz Traceback (most recent call last): File "/usr/bin/wfuzz", line 6, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources Andreas --- End Message --- --- Begin Message --- Source: wfuzz Source-Version: 2.2.11-1.1 We believe that the bug you reported is fixed in the latest version of wfuzz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated wfuzz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Aug 2018 15:32:14 +0300 Source: wfuzz Binary: wfuzz Architecture: source Version: 2.2.11-1.1 Distribution: unstable Urgency: high Maintainer: Debian Security Tools Changed-By: Adrian Bunk Description: wfuzz - Web application bruteforcer Closes: 904756 Changes: wfuzz (2.2.11-1.1) unstable; urgency=high . * Non-maintainer upload. * Add the missing dependency on python-pkg-resources. (Closes: #904756) Checksums-Sha1: 63798b501e6ccd3ab661105b20e0b6569afbe0fb 1931 wfuzz_2.2.11-1.1.dsc fde9aedee89d45673180ae75c6ded27e7d2fd138 5120 wfuzz_2.2.11-1.1.debian.tar.xz Checksums-Sha256: 652b0ecd47611aa36c21328fd5d4c6ccce1ef4198f683a8f4a25e3c2b33b106c 1931 wfuzz_2.2.11-1.1.dsc 76ecbe1f15324a3dab9dfa50a5dfb0b8354de3982271c20b1615ab0594c0b7a8 5120 wfuzz_2.2.11-1.1.debian.tar.xz Files: e19aa2ef20eaa0513eb0d77e23c88d29 1931 utils optional wfuzz_2.2.11-1.1.dsc 64c9fafaac6a5228f2bdc69cf12e985f 5120 utils optional wfuzz_2.2.11-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltu1+QACgkQiNJCh6LY mLEOmA/8CM5VmwVNsNV6Vg3UScknVahOMH2ZB2OWQo5exf/OkEjKhjiNbAlKJ9jp MpPeiJa481BSImrPNCy5R3cQf4wYO+XA48l8nU7jvL4V45ienN3MrJSqo4i/UFn6 gzJ7SPoiqYSN028Mb/qd1AUQjicpvyb0WVU1pylvbOErX6qXbwBwuDrtJXSjGe14 oIRr+8eVZyLz+eA049mWq08ciUgn1HTrrg1qxM2s0nYuBP+2apbdnE7UNRuGE/BK x8EqS9i1uCEmRrsutB/CC4PmNmG442MFGQuBRblHb5B6mkUahvmkNgXAYw8wacJc d/KK2sygZU2TkIRbuGTPYxoK2osd9E5xamdLwhjYlhslUC5p49MdSTwafVHF8+rW 1CI7t+LuAzSjNBHZfl3P72o63rcKBKy2AHM8+f69Xe+NVPTbxpO3IDkIalVNJdMT YQAKnEHPiHiKS/6Nbx32JVkoqW3dUZLgt5psark1Wo+o39ko2YXCjZLDJ/ipWwDe HNaYivR9I5NkCJj35DrjAewRpUk5VN/ku0bBIW+3Q4FQmPOnKfh1FRrXHT0/4EFk zZ7IbxvPY2SXhgBL+GzXCEhbmHZD3AlGmYG6Vm0AR4xt01rpFN2HT0OB0uWPQktC fw9/7IRopGYw0PHDeygst8AXIPaWrPXzLzNPcvfnITTICEUrwdY= =2flD -END PGP SIGNATURE End Message ---
Bug#907049: [Pkg-openssl-devel] Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
reassign 907049 openvpn severity 907049 serious retitle 907049 openvpn: ssl_choose_client_version:version too low block 907015 by 907049 thanks On Sat, Aug 25, 2018 at 02:49:12PM +0200, Samuel Hym wrote: > > Can you try with: > > MinProtocol = TLSv1 > > > > And with: > > #MinProtocol = TLSv1.2 > > Both options work in my case. > So I leave the first enabled, I guess it is a bit more secure than > commenting it out. If both work, it's there really isn't much difference. Anyway, that seems to mean that openvpn only supports TLS 1.0 for some reason. I have no idea how openvpn works, but if it uses TLS 1.0, it really should switch to 1.2 or 1.3. Kurt
Processed: Re: [Pkg-openssl-devel] Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
Processing commands for cont...@bugs.debian.org: > reassign 907049 openvpn Bug #907049 [openssl] openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable Bug reassigned from package 'openssl' to 'openvpn'. No longer marked as found in versions openssl/1.1.1~~pre9-1. Ignoring request to alter fixed versions of bug #907049 to the same values previously set > severity 907049 serious Bug #907049 [openvpn] openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable Severity set to 'serious' from 'critical' > retitle 907049 openvpn: ssl_choose_client_version:version too low Bug #907049 [openvpn] openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable Changed Bug title to 'openvpn: ssl_choose_client_version:version too low' from 'openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable'. > block 907015 by 907049 Bug #907015 [src:openssl] openssl version 1.1.1 breaks multiple reverse dependencies; versioned Breaks needed 907015 was blocked by: 891665 898803 907219 897652 898807 898801 898800 907215 898804 906955 907216 906997 907135 900160 906981 907118 907033 898802 897651 900161 907079 900157 907022 900158 891625 900159 907055 898805 907168 907031 900154 897643 900152 900156 900153 897658 907028 900982 895959 907015 was not blocking any bugs. Added blocking bug(s) of 907015: 907049 > thanks Stopping processing here. Please contact me if you need assistance. -- 907015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907015 907049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907049: [Pkg-openssl-devel] Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
Hi Kurt, Le 23 août 2018 à 22h20, Kurt Roeckx disait : > On Thu, Aug 23, 2018 at 02:54:36PM +0200, Antonin Kral wrote: > > Thu Aug 23 14:46:07 2018 OpenSSL: error:1425F18C:SSL > > routines:ssl_choose_client_version:version too low > > Thu Aug 23 14:46:07 2018 TLS_ERROR: BIO read tls_read_plaintext error > > Thu Aug 23 14:46:07 2018 TLS Error: TLS object -> incoming plaintext read > > error > > Thu Aug 23 14:46:07 2018 TLS Error: TLS handshake failed I have the same issue. > This is most likely caused by this in /etc/ssl/openssl.cnf: > [system_default_sect] > MinProtocol = TLSv1.2 > CipherString = DEFAULT@SECLEVEL=2 > > Does openvpn use DTLS? I don’t know about that but… > Can you try with: > MinProtocol = TLSv1 > > And with: > #MinProtocol = TLSv1.2 Both options work in my case. So I leave the first enabled, I guess it is a bit more secure than commenting it out. Thank you very much! Samuel
Bug#873747: astroid segfault on startup when config is available
Hi Abhijit, Can you please test if this issue still persist with 0.13? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#873484: marked as done (astroid: Crash at start)
Your message dated Sat, 25 Aug 2018 14:49:59 +0200 with message-id <153520139972.26921.18414741315884956...@auryn.jones.dk> and subject line Re: Bug#873484: astroid: Crash at start has caused the Debian Bug report #873484, regarding astroid: Crash at start 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.) -- 873484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: astroid Version: 0.9.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've just installed astroid. At start, I get the following: astroid [11:17:55.594602] [0x7efd0669cfc0] [info] welcome to astroid! - 0.9.1-1 [11:17:55.594722] [0x7efd0669cfc0] [debug] utf8: true, UTF-8 [...] (astroid:19045): Gtk-WARNING **: Theme parsing error: gtk.css:4190:73: Using one color stop with linear-gradient() is deprecated. [11:17:55.626727] [0x7efd0669cfc0] [debug] HOME: /home/jean-luc [11:17:55.626774] [0x7efd0669cfc0] [info] cf: loading: "/home/jean-luc/.config/astroid/config" [11:17:55.626827] [0x7efd0669cfc0] [warning] cf: making config dir.. [11:17:55.626899] [0x7efd0669cfc0] [warning] cf: making runtime dir.. [11:17:55.626947] [0x7efd0669cfc0] [warning] cf: no config, using defaults. [11:17:55.627533] [0x7efd0669cfc0] [warning] cf: writing back config to: "/home/jean-luc/.config/astroid/config" terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' what(): /home/jean-luc/.notmuch-config: cannot open file [1]19045 abort astroid Whe I tried to report the bug, I got the following from reportbug: Getting status for astroid... Checking for newer versions at madison, incoming.debian.org and http://ftp-master.debian.org/new.html Your version (0.9.1-1) of astroid appears to be out of date. The following newer release(s) are available in the Debian archive: oldstable: 1.2.1-3 stable: 1.4.9-1 testing: 1.4.9-1 unstable: 1.4.9-1 Do you still want to file a report [y|N|q|?]? I use sid and I've not found any newer version… Regards Jean-Luc - -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (600, 'unstable'), (500, 'buildd-unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-rc6-i7-0.1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages astroid depends on: ii libatk1.0-0 2.24.0-1 ii libatkmm-1.6-1v52.24.2-2 ii libboost-date-time1.62.01.62.0+dfsg-4+b1 ii libboost-filesystem1.62.0 1.62.0+dfsg-4+b1 ii libboost-log1.62.0 1.62.0+dfsg-4+b1 ii libboost-program-options1.62.0 1.62.0+dfsg-4+b1 ii libboost-system1.62.0 1.62.0+dfsg-4+b1 ii libboost-thread1.62.0 1.62.0+dfsg-4+b1 ii libc6 2.24-17 ii libcairo-gobject2 1.14.10-1 ii libcairo2 1.14.10-1 ii libcairomm-1.0-1v5 1.12.2-1 ii libgcc1 1:7.2.0-1 ii libgdk-pixbuf2.0-0 2.36.5-3 ii libgirepository-1.0-1 1.53.2-4 ii libglib2.0-02.53.6-1 ii libglibmm-2.4-1v5 2.50.1-1 ii libgmime-2.6-0 2.6.23+dfsg1-1 ii libgnutls30 3.5.15-2 ii libgtk-3-0 3.22.18-1 ii libgtkmm-3.0-1v53.22.1-1 ii libjavascriptcoregtk-3.0-0 2.4.11-3 ii libnotmuch5 0.25-6 ii libpango-1.0-0 1.40.11-1 ii libpangocairo-1.0-0 1.40.11-1 ii libpangomm-1.4-1v5 2.40.1-3 ii libpcre2-8-010.22-3 ii libpeas-1.0-0 1.20.0-1+b1 ii libsass03.4.3-1 ii libsigc++-2.0-0v5 2.10.0-1 ii libsoup2.4-12.56.1-1 ii libstdc++6 7.2.0-1 ii libvte-2.91-0 0.46.2-1 ii libwebkitgtk-3.0-0 2.4.11-3 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages astroid recommends: ii emacs2525.2+1-5 ii gnupg 2.1.23-2 ii notmuch0.25-6 ii xdg-utils 1.1.1-1 astroid suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWaPhJgAKCRBR0YZfPMac
Bug#906412: svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found)
On Fri, 17 Aug 2018 11:21:39 + Santiago Vila wrote: > I tried to build this package in buster but it failed: > > > [...] > debian/rules build-indep > dh build-indep > dh: Compatibility levels before 9 are deprecated (level 7 in use) >dh_update_autotools_config -i >dh_auto_configure -i > dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in > use) >dh_auto_build -i > dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use) > make -j1 > make[1]: Entering directory '/<>' > po4a-build > make[1]: po4a-build: Command not found > make[1]: *** [Makefile:10: docbuild] Error 127 > make[1]: Leaving directory '/<>' > dh_auto_build: make -j1 returned exit code 2 > make: *** [debian/rules:4: build-indep] Error 2 > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit > status 2 > > > The build was made with "dpkg-buildpackage -A" in my autobuilder. > Most probably, it also fails here in reproducible builds: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/svn-buildpackage.html > > where you can get a full build log if you need it. > > If this is really a bug in one of the build-depends, please use reassign and > affects, > so that this is still visible in the BTS web page for this package. Upstream version 0.54 of po4a removed po4a-build: https://github.com/mquinson/po4a/releases There are two packages in Debian that seem to FTBFS because of that. In addition to this bug, there is also the following bug against multistrap: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906386 Since it is unclear to me what the correct replacement for po4a-build is, I contacted upstream about it: https://github.com/mquinson/po4a/issues/144 Since this bug is also still unfixed, I thought that this information might be helpful for you as well. :) Just in case, I also CC-ed the po4a maintainers. Thanks! cheers, josch signature.asc Description: signature
Bug#871109: marked as done (libtomcrypt: FTBFS: Fatal error occurred, no output PDF file produced!)
Your message dated Sat, 25 Aug 2018 14:02:21 +0200
with message-id <20180825120219.w7l77hs4dxw5p...@ugent.be>
and subject line Re: libtomcrypt: FTBFS: Fatal error occurred, no output PDF
file produced!
has caused the Debian Bug report #871109,
regarding libtomcrypt: FTBFS: Fatal error occurred, no output PDF file produced!
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.)
--
871109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtomcrypt
Version: 1.17-9
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> rm -f doc/crypt.pdf *.dvi *.log *.aux *.toc *.idx *.ilg *.ind *.out
> cp crypt.tex crypt.bak
> touch --reference=crypt.tex crypt.bak
> (echo "\\def\\fixedpdfdate{"; date +'D:%Y%m%d%H%M%S%:z' -d @$(stat
> --format=%Y crypt.tex) | sed "s/:\([0-9][0-9]\)$/'\1'}/g") >
> crypt-deterministic.tex
> echo "\\pdfinfo{" >> crypt-deterministic.tex
> echo "/CreationDate (\fixedpdfdate)" >> crypt-deterministic.tex
> echo "/ModDate (\fixedpdfdate) }" >> crypt-deterministic.tex
> cat crypt.tex >> crypt-deterministic.tex
> mv crypt-deterministic.tex crypt.tex
> touch --reference=crypt.bak crypt.tex
> echo "hello" > crypt.ind
> latex crypt
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian)
> (preloaded format=latex)
> restricted \write18 enabled.
> entering extended mode
> (./crypt.tex
> LaTeX2e <2017-04-15>
> Babel <3.12> and hyphenation patterns for 3 language(s) loaded.
>
> pdfTeX warning (\pdfinfo): not allowed in DVI mode (\pdfoutput <= 0);
> ignoring
> it
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
>
> Package hyperref Message: Driver (default): hdvips.
>
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hdvips.def
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pdfmark.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def))
> (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/layout.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> Writing index file crypt.idx
>
> LaTeX Warning: Unused global option(s):
> [synpaper].
>
> No file crypt.aux.
> *geometry* detected driver: dvips
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
>
> Package hyperref Warning: Rerun to get /PageLabels entry.
>
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd) [1] [2] [3] [4]
>
> Package hyperref Warning: old lof file detected, not
Bug#903980: marked as done (ruby-doorkeeper: CVE-2018-1000211: Public apps can't revoke OAuth access & refresh tokens in Doorkeeper)
Your message dated Sat, 25 Aug 2018 12:05:32 + with message-id and subject line Bug#903980: fixed in ruby-doorkeeper 4.4.2-1 has caused the Debian Bug report #903980, regarding ruby-doorkeeper: CVE-2018-1000211: Public apps can't revoke OAuth access & refresh tokens in Doorkeeper 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.) -- 903980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-doorkeeper Version: 4.2.0-1 Severity: grave Tags: security upstream Forwarded: https://github.com/doorkeeper-gem/doorkeeper/issues/891 Hi, The following vulnerability was published for ruby-doorkeeper. CVE-2018-1000211[0]: | Doorkeeper version 4.2.0 and later contains a Incorrect Access Control | vulnerability in Token revocation API's authorized method that can | result in Access tokens are not revoked for public OAuth apps, leaking | access until expiry. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-1000211 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000211 [1] https://github.com/doorkeeper-gem/doorkeeper/issues/891 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ruby-doorkeeper Source-Version: 4.4.2-1 We believe that the bug you reported is fixed in the latest version of ruby-doorkeeper, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-doorkeeper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Aug 2018 17:22:16 +0530 Source: ruby-doorkeeper Binary: ruby-doorkeeper Architecture: source Version: 4.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: ruby-doorkeeper - OAuth 2 provider for Rails and Grape Closes: 903980 Changes: ruby-doorkeeper (4.4.2-1) unstable; urgency=medium . * New upstream version 4.4.2 (Closes: #903980) (Fixes: CVE-2018-1000211, CVE-2018-188) * Bump Standards-Version to 4.2.0 (no changes needed) Checksums-Sha1: 0e13999814a960ccc70b72ddb44de777b3f95c52 2110 ruby-doorkeeper_4.4.2-1.dsc 8aa946fc778687ede70bbda5772ce26498bc0e28 117423 ruby-doorkeeper_4.4.2.orig.tar.gz 5f54660d5177bee2ac64243bed64e02b8fe12253 2696 ruby-doorkeeper_4.4.2-1.debian.tar.xz 4ca735e58e2814dada791d18f9cae01fcbc14201 7783 ruby-doorkeeper_4.4.2-1_source.buildinfo Checksums-Sha256: 708debf6a4e83342dc4f39503aa9f0edc4dbe0f3eec6a32886ea34aa87a65779 2110 ruby-doorkeeper_4.4.2-1.dsc fed606a0f01801bca3042c0b546b393c972fd7353785f1798f915e924bca7b99 117423 ruby-doorkeeper_4.4.2.orig.tar.gz 15ac648a3979d592bed6dcaca46186edcdf5fe81f186d9b86475f8573c31b3cc 2696 ruby-doorkeeper_4.4.2-1.debian.tar.xz a0f14aeb00394069231226c98b60058aecf7b39d218a6853a5e63e903ebb13df 7783 ruby-doorkeeper_4.4.2-1_source.buildinfo Files: 8d41947fa5223bb8cf8956dea016e863 2110 ruby optional ruby-doorkeeper_4.4.2-1.dsc 5d6242a2044ee1bd17bb5db5ffe4cb93 117423 ruby optional ruby-doorkeeper_4.4.2.orig.tar.gz b7deefbb4b39e73c74cc78f78d40 2696 ruby optional ruby-doorkeeper_4.4.2-1.debian.tar.xz 45e87db42f4976ba2c8aa6d70deb5d8f 7783 ruby optional ruby-doorkeeper_4.4.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAluBRR8ACgkQzh+cZ0US wirOOhAAhGJMnW22eN+ItffQsVdLwTOBvEDeVjuSW6UWeAr9VzwYfip8e4H6vfzs KNgfThLExXcV1G/pgUYERLYlejqVzBBPfDASnc++Ez9PjEct+CrVo1Q7OKX8wiDk FT3fGi7QNhJfHo/pGyyNSEKVErLyUeanmlKxsDa6ctRj2wcxfyDpYN2hykI+JhW1 V07kbVWtR7qayQP59JAwRzY33xh9Be4I6F4/5bFBRhO05kkDeJFx4C09a4qhQ1xw +K9/aaako4Pc8PXe6Yx57nurqajvErkHzn1YjeGL8/TSEKoyeN+KJX/Fi/ul1IPl 4g3bZiZbjqeQFTP4UTwy8qBDOg7k4CES8ZYeaD1RMKIpkV7zh18UgV5h3/oYFWjZ b+TUnX46uDjtZXjIWKKBFgGPzTmpa8yS7FFwAFSbi5f7N3E1dYAV+RC4Tuz6gKal J+RW6x25RvzrwjoTLCSxBOVuXd70dVWeqtWGl++Brd27Q+uFXmB7BSHNhVGRS073
Bug#904751: marked as done (zeitgeist-explorer fails to start: ImportError: No module named gi.repository)
Your message dated Sat, 25 Aug 2018 11:34:14 + with message-id and subject line Bug#904751: fixed in zeitgeist-explorer 0.2-1.2 has caused the Debian Bug report #904751, regarding zeitgeist-explorer fails to start: ImportError: No module named gi.repository 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.) -- 904751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zeitgeist-explorer Version: 0.2-1.1 Severity: serious $ zeitgeist-explorer Traceback (most recent call last): File "/usr/bin/zeitgeist-explorer", line 22, in from gi.repository import Gtk ImportError: No module named gi.repository Andreas --- End Message --- --- Begin Message --- Source: zeitgeist-explorer Source-Version: 0.2-1.2 We believe that the bug you reported is fixed in the latest version of zeitgeist-explorer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 904...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated zeitgeist-explorer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 11 Aug 2018 13:37:22 +0300 Source: zeitgeist-explorer Binary: zeitgeist-explorer Architecture: source Version: 0.2-1.2 Distribution: unstable Urgency: high Maintainer: Manish Sinha Changed-By: Adrian Bunk Description: zeitgeist-explorer - GUI application for monitoring and debugging zeitgeist Closes: 904751 Changes: zeitgeist-explorer (0.2-1.2) unstable; urgency=high . * Non-maintainer upload. * Dependency fixes: - python3-gi -> python-gi - add python-zeitgeist (Closes: #904751) Checksums-Sha1: 2e89ca4f1b3cb952e1b6311838a3d49ea07cd670 1930 zeitgeist-explorer_0.2-1.2.dsc ea5700ef2afec9a3b9914cdd46fe47d9ff42b348 2296 zeitgeist-explorer_0.2-1.2.debian.tar.xz Checksums-Sha256: d79191c38017c3ec88328837f1e110a9490a343f99b061f0f108e62efd677765 1930 zeitgeist-explorer_0.2-1.2.dsc 2c0e1f30f7049cf46b20601313b777ab67292a622006fbb1c66adb00f2735c4d 2296 zeitgeist-explorer_0.2-1.2.debian.tar.xz Files: 8a6d685a5206915e55a11bd1564664b0 1930 devel extra zeitgeist-explorer_0.2-1.2.dsc 2672f40f1f916753fdafd7146a34a137 2296 devel extra zeitgeist-explorer_0.2-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltuvY4ACgkQiNJCh6LY mLFYhBAAtWRN7jy0pdPy2+fsaiutT40mXX2ex0DmfeZBaWzQcWC9rCFkOJ4xzZby +AncHpmIJtwj7lVdPK1aowS/DTdzHZGEl3POvrUnXdiZCPRUJEL5yyf9dFLeqA2N SsbME12KljKZ7xqS1Zw37mE7VNTrIhNTmbWYFKAwDwprcSU1YZx7RVTZieDmiHp4 pnNzaxN7WDaKEu2h6UYUgeBD8b9CkYB4TtaKUeaelLiHAASUM/XWvif2x/NTCvBI WLGAKwqQMs9L1CXQ9GHrHrTPx4BRc8pPfvflLMySOg+6FXTmHfKVp5drN+zl8gqE mRl1lLk4eYmNfMbntcPPp45ApLQ8HeZJVuYJNPG2BfcsHJIs0plimPw3mg5o2quh vCr0U7CpmlBTrxiOPulPd3eTxbU54CfwdPFV9j9JJIfqtGVmAhsq4rx0ol/p07wv FK4xcW0AuC0Gve5yadPMfwHAPUaUzBfjPmzBl8sfEKIihSwhTdwN+T3niQqfXKeW AT9oeRDARfKmAD5Pn5qAoiQmxcdpMEO4jT834CnRnUvU2Aem1BkdEUzILkV61Xo7 XwLobBD6xx37w8Z7CZSwGRKkuKbBKnv/WK7IqKvv7zG2rMyg3KsdHMfhxwEl+ldK MGNR/Q/0/3+HhWtDb7R0dd2BcP/wCMsT6XBEM1/krPlm8osWGzU= =V/42 -END PGP SIGNATURE End Message ---
Bug#906790: libtasn1-6 FTBFS during arch-only: missing makeinfo
On 2018-08-23 Andreas Metzler wrote: [...] > Almost, it is caused by upgrading automake. Building with automake > 1:1.16.1-1 fails, downgrading to 1:1.15.1-3.1 lets the build succeed. > Which seems to have hit other packages, too. With one report (#906774) > reassigned to automake. > FWIW at first glance I have not found not-too-involved a workaround yet. > I might be forced to move stuff from Build-Depends-Indep to > Build-Depends. Hello, this is caused mdate-sh. The rule that checks whether version.texi is up to date runs mdate-sh on the source texi file and compares whether the result differs from the current timestamp in version.texi state.[1] If the timestamp differs version.texi is regenerated and a rebuild of the info documentation is triggered. mdate-sh in automake 1:1.16.1-1 has grown "support" for SOURCE_DATE_EPOCH. If SOURCE_DATE_EPOCH is set in the environment then its value is used and the modification time of the file is ignored. Which causes the build-failure by tricking make into thinking the info file is out of date. This seems to be a Debian specific change. The patch was already present in 1:1.15.1-3 (and -3.1) *source* but did not end up changing usr/share/automake-1.15/mdate-sh. It is however present in 1:1.16.1-1's /usr/share/automake-1.16/mdate-sh. cu Andreas [1] $(srcdir)/stamp-vti: libtasn1.texi $(top_srcdir)/configure @(dir=.; test -f ./libtasn1.texi || dir=$(srcdir); \ set `$(SHELL) $(top_srcdir)/build-aux/mdate-sh $$dir/libtasn1.texi`; \ echo "@set UPDATED $$1 $$2 $$3"; \ echo "@set UPDATED-MONTH $$2 $$3"; \ echo "@set EDITION $(VERSION)"; \ echo "@set VERSION $(VERSION)") > vti.tmp && \ (cmp -s vti.tmp $(srcdir)/version.texi \ || (echo "Updating $(srcdir)/version.texi" && \ cp vti.tmp $(srcdir)/version.texi.tmp && \ mv $(srcdir)/version.texi.tmp $(srcdir)/version.texi)) && \ rm -f vti.tmp $(srcdir)/version.texi. @cp $(srcdir)/version.texi $@ -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#907249: qml-module-qtwebview: "No WebView plug-in found!" when -dev packages are not installed
Juhani Numminen kirjoitti 25.08.2018 klo 14:19: > I am trying out QtWebView in QML with a small test file that > is attached to this mail. After running the following command, > a window with completely white content pops up. I am expecting > to see the Debian website instead. > > juhani@computer:~$ qmlscene webviewtest.qml > No WebView plug-in found! > ^C > > Installing the libqt5webview5-dev package. > > juhani@computer:~$ sudo apt install -y libqt5webview5-dev > > Now that those packages are installed, a window pops up and this time > it's correctly showing the Debian.org website. Also, a cert error is > printed out in the console. > > juhani@computer:~$ qmlscene webviewtest.qml > [5881:5903:0825/135426.420134:ERROR:nss_util.cc(727)] After loading Root > Certs, loaded==false: NSS error code: -8018 I just found out that removing qml-module-qtwebengine also causes "No WebView plug-in found!" and no website shown. -- Juhani
Processed: Re: Bug#865417: efibootmgr: grub-install dummy failed in Stretch installation
Processing control commands: > severity -1 important Bug #865417 [efibootmgr] efibootmgr: grub-install dummy failed in Stretch installation Severity set to 'important' from 'critical' -- 865417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865417: efibootmgr: grub-install dummy failed in Stretch installation
Control: severity -1 important Hi Steve, On Wed, Jun 21, 2017 at 03:52:39PM +0100, Steve McIntyre wrote: > Date: Wed, 21 Jun 2017 15:52:39 +0100 > From: Steve McIntyre > To: saulius , 865...@bugs.debian.org > Subject: Re: Bug#865417: efibootmgr: grub-install dummy failed in Stretch > installation > > Contro: severity -1 important I guess you meant 'Control' here. Resending so the downgrade reaches the BTS. Cheers, Ivo
Bug#907249: qml-module-qtwebview: "No WebView plug-in found!" when -dev packages are not installed
Package: qml-module-qtwebview
Version: 5.11.1-2
Severity: grave
Justification: renders package unusable
Dear maintainer,
I am trying out QtWebView in QML with a small test file that
is attached to this mail. After running the following command,
a window with completely white content pops up. I am expecting
to see the Debian website instead.
juhani@computer:~$ qmlscene webviewtest.qml
No WebView plug-in found!
^C
Installing the libqt5webview5-dev package.
juhani@computer:~$ sudo apt install -y libqt5webview5-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libqt5quicktest5 qtdeclarative5-dev qtdeclarative5-dev-tools
The following NEW packages will be installed:
libqt5quicktest5 libqt5webview5-dev qtdeclarative5-dev
qtdeclarative5-dev-tools
0 upgraded, 4 newly installed, 0 to remove and 31 not upgraded.
Need to get 0 B/752 kB of archives.
After this operation, 4784 kB of additional disk space will be used.
Selecting previously unselected package libqt5quicktest5:amd64.
(Reading database ... 359884 files and directories currently installed.)
Preparing to unpack .../libqt5quicktest5_5.11.1-4_amd64.deb ...
Unpacking libqt5quicktest5:amd64 (5.11.1-4) ...
Selecting previously unselected package qtdeclarative5-dev-tools.
Preparing to unpack .../qtdeclarative5-dev-tools_5.11.1-4_amd64.deb ...
Unpacking qtdeclarative5-dev-tools (5.11.1-4) ...
Selecting previously unselected package qtdeclarative5-dev:amd64.
Preparing to unpack .../qtdeclarative5-dev_5.11.1-4_amd64.deb ...
Unpacking qtdeclarative5-dev:amd64 (5.11.1-4) ...
Selecting previously unselected package libqt5webview5-dev:amd64.
Preparing to unpack .../libqt5webview5-dev_5.11.1-2_amd64.deb ...
Unpacking libqt5webview5-dev:amd64 (5.11.1-2) ...
Setting up libqt5quicktest5:amd64 (5.11.1-4) ...
Processing triggers for libc-bin (2.27-5) ...
Setting up qtdeclarative5-dev-tools (5.11.1-4) ...
Setting up qtdeclarative5-dev:amd64 (5.11.1-4) ...
Setting up libqt5webview5-dev:amd64 (5.11.1-2) ...
Now that those packages are installed, a window pops up and this time
it's correctly showing the Debian.org website. Also, a cert error is
printed out in the console.
juhani@computer:~$ qmlscene webviewtest.qml
[5881:5903:0825/135426.420134:ERROR:nss_util.cc(727)] After loading Root
Certs, loaded==false: NSS error code: -8018
Cheers,
Juhani
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8),
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qml-module-qtwebview depends on:
ii libc6 2.27-5
ii libqt5core5a5.11.1+dfsg-6
ii libqt5qml5 5.11.1-4
ii libqt5quick55.11.1-4
ii libqt5webview5 5.11.1-2
ii libstdc++6 8.2.0-4
qml-module-qtwebview recommends no packages.
qml-module-qtwebview suggests no packages.
-- no debconf information
import QtWebView 1.1
WebView {
url: "https://www.debian.org/;
}
Processed: bug 904648 is forwarded to https://github.com/tweepy/tweepy/issues/1017
Processing commands for cont...@bugs.debian.org: > forwarded 904648 https://github.com/tweepy/tweepy/issues/1017 Bug #904648 [python3-tweepy] python3-tweepy: fails to install with Python 3.7 Set Bug forwarded-to-address to 'https://github.com/tweepy/tweepy/issues/1017'. > thanks Stopping processing here. Please contact me if you need assistance. -- 904648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts / replaces
Processing control commands: > found -1 libopenmpi3/3.1.1.real-7 Bug #907248 [libopenmpi3,libpmix2] libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts / replaces The source libopenmpi3 and version 3.1.1.real-7 do not appear to match any binary packages Marked as found in versions libopenmpi3/3.1.1.real-7. > found -1 libpmix2/3.0.1-1 Bug #907248 [libopenmpi3,libpmix2] libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts / replaces The source libpmix2 and version 3.0.1-1 do not appear to match any binary packages Marked as found in versions libpmix2/3.0.1-1. -- 907248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907248: libopenmpi3, libpmix2: both ship libpmix.so.2 without suitable conflicts / replaces
Package: libopenmpi3,libpmix2 Severity: grave Control: found -1 libopenmpi3/3.1.1.real-7 Control: found -1 libpmix2/3.0.1-1 Hi, Attempting to upgrade libopenmpi3 to 3.1.1.real-7 after libpmix2 has already been upgraded to 3.0.1-1 results in this error: > Preparing to unpack .../libopenmpi3_3.1.1.real-7_amd64.deb ... > Unpacking libopenmpi3:amd64 (3.1.1.real-7) over (3.1.1.real-4+b1) ... > dpkg: error processing archive > /var/cache/apt/archives/libopenmpi3_3.1.1.real-7_amd64.deb (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/libpmix.so.2', which is also > in package libpmix2:amd64 3.0.1-1 > Errors were encountered while processing: > /var/cache/apt/archives/libopenmpi3_3.1.1.real-7_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Both libopenmpi3 and libpmix2 ship libpmix.so.2, but the replaces relation in libopenmpi3 only applies to libpmix2 (<< 3.0.0-2). Presumably the same error would occur if libpmix2 is upgraded after libopenmpi3. I've filed the bug against both packages, but please reassign it to the one that needs fixing. James signature.asc Description: OpenPGP digital signature
Bug#904709: Blocked by ITP bugs
Control: block -1 by 907241 Control: block -1 by 907244
Processed: Blocked by ITP bugs
Processing control commands: > block -1 by 907241 Bug #904709 [src:python-cobra] python-cobra ftbfs (test failures) 904709 was blocked by: 904359 904709 was not blocking any bugs. Added blocking bug(s) of 904709: 907241 > block -1 by 907244 Bug #904709 [src:python-cobra] python-cobra ftbfs (test failures) 904709 was blocked by: 904359 907241 904709 was not blocking any bugs. Added blocking bug(s) of 904709: 907244 -- 904709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 904491 is forwarded to https://github.com/klen/pylama/issues/123
Processing commands for cont...@bugs.debian.org: > forwarded 904491 https://github.com/klen/pylama/issues/123 Bug #904491 [python3-pylama] python3-pylama: fails to install with Python 3.7 Set Bug forwarded-to-address to 'https://github.com/klen/pylama/issues/123'. > thanks Stopping processing here. Please contact me if you need assistance. -- 904491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1
Processing control commands: > tags -1 +confirmed Bug #907026 [cups-filters] cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1 Ignoring request to alter tags of bug #907026 to the same tags previously set -- 907026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907026: cups-filters: filter failed on Ricoh MP 3554 SP after upgrading to 1.21.0-1
Package: cups-filters Followup-For: #907026 Control: tags -1 +confirmed I get a `(/usr/lib/cups/filter/foomatic-rip) crashed on signal 11' on a Samsung ML-6060 as well. Downgrading to 1.20.4-1 fixes the problem. Ciao Elimar -- The path to source is always uphill! -unknown-
Bug#831519: marked as done ([vizigrep] ImportError: cannot import name GtkSource)
Your message dated Sat, 25 Aug 2018 13:27:47 +0300
with message-id <20180825102747.GN3214@localhost>
and subject line Fixed in 1.4-1
has caused the Debian Bug report #831519,
regarding [vizigrep] ImportError: cannot import name GtkSource
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.)
--
831519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vizigrep
Version: 1.3-1
Severity: normal
--- Please enter the report below this line. ---
Add dependency on "gir1.2-gtksource-3.0". Otherwise you get something like:
marek@dell-e6220:~$ vizigrep
** (vizigrep:4562): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.a11y.Bus was not provided by any .service files
/usr/lib/python2.7/dist-packages/vizigrep/main.py:5: PyGIWarning: Gtk
was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right
version gets loaded.
from gi.repository import Gtk, GObject
Traceback (most recent call last):
File "/usr/bin/vizigrep", line 9, in
load_entry_point('vizigrep==1.3', 'gui_scripts', 'vizigrep')()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 542, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2569, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2229, in load
return self.resolve()
File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2235, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python2.7/dist-packages/vizigrep/main.py", line 7, in
from ViziGrepWindow import ViziGrepWindow
File "/usr/lib/python2.7/dist-packages/vizigrep/ViziGrepWindow.py",
line 3, in
from guiapp.Window import Window
File "/usr/lib/python2.7/dist-packages/vizigrep/guiapp/Window.py",
line 2, in
from SuperGtkBuilder import SuperGtkBuilder
File
"/usr/lib/python2.7/dist-packages/vizigrep/guiapp/SuperGtkBuilder.py",
line 1, in
from gi.repository import Gtk, GObject, GtkSource
ImportError: cannot import name GtkSource
--- System information. ---
Architecture: amd64
Kernel: Linux 4.6.0-1-amd64
Debian Release: stretch/sid
500 testing ftp.at.debian.org
--- Package information. ---
Depends (Version) | Installed
==-+-==
python:any (<< 2.8) |
python:any (>= 2.7.5-5~) |
python-pkg-resources | 20.10.1-1.1
gir1.2-gtk-3.0 | 3.20.6-2
python-gi | 3.20.1-1
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
Version: 1.4-1
vizigrep (1.4-1) unstable; urgency=low
...
* deb: Added missing dependency on gir1.2-gtksource-3.0
-- Jason J. Herne Wed, 20 Jul 2016 19:11:42 -0400
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed--- End Message ---
Bug#859791: wvstreams now has a patch for OpenSSL 1.1 in the BTS
wvstreams now has a patch for OpenSSL 1.1 in the BTS, there is no point in removing it after Reiner Herrmann provided a fix. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#905300: marked as done (gfan: FTBFS on 32bit architectures: test 0602ResultantFanProjection hangs)
Your message dated Sat, 25 Aug 2018 09:50:24 + with message-id and subject line Bug#905300: fixed in gfan 0.6.2-1~exp2 has caused the Debian Bug report #905300, regarding gfan: FTBFS on 32bit architectures: test 0602ResultantFanProjection hangs 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.) -- 905300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gfan Version: 0.6.2-1~exp1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, gfan/experimental FTBFS on all 32bit architectures since a test hangs: https://buildd.debian.org/status/package.php?p=gfan=experimental [...] Running command:"cat testsuite/0602ResultantFanProjection/outputNew" E: Build killed with signal TERM after 150 minutes of inactivity Andreas --- End Message --- --- Begin Message --- Source: gfan Source-Version: 0.6.2-1~exp2 We believe that the bug you reported is fixed in the latest version of gfan, 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 905...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated gfan 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: Wed, 22 Aug 2018 14:37:22 -0400 Source: gfan Binary: gfan Architecture: source Version: 0.6.2-1~exp2 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Doug Torrance Description: gfan - program for computing with Groebner fans Closes: 905300 Changes: gfan (0.6.2-1~exp2) experimental; urgency=medium . * debian/control - Bump Standards-Version to 4.2.0. * debian/patches/remove_failing_tests_on_32bits.patch - Remove patch. * debian/rules - Remove tests which fail on 32-bit architectures. Previously, we removed 0009RenderStairCase on *all* architectures using quilt. We now use dpkg-architecture to only remove this and the newly-introduced 0602ResultantFanProjection on the architectures on which they fail (Closes: #905300). Checksums-Sha1: f87c09655b5d1841d7e6036afb099e6215c8d803 2143 gfan_0.6.2-1~exp2.dsc df7d5485b135e16a1fff18a9896086d541b30aab gfan_0.6.2-1~exp2.debian.tar.xz 38be2e75943db10068f5df0dc58dfc52066a5ae5 7653 gfan_0.6.2-1~exp2_source.buildinfo Checksums-Sha256: fb3fb25bfd1b02104f684305744907bd4976c53a099d614463ba35d15c1af0c0 2143 gfan_0.6.2-1~exp2.dsc 5421847a3ce84a78c642b2391d068d1e09b7da6f2d3dc7cc891c0808110b3160 gfan_0.6.2-1~exp2.debian.tar.xz 876596df4cf9f0ac3cbc3529d660167ec028cb0b2e0110758805fdcdff50e327 7653 gfan_0.6.2-1~exp2_source.buildinfo Files: 44a85f4712e6ac60bcc8f224a7072691 2143 math optional gfan_0.6.2-1~exp2.dsc 6f67d82efabfbf25a891f7fef6643d55 math optional gfan_0.6.2-1~exp2.debian.tar.xz bff406ae466186516e8dc179ed6c9b0a 7653 math optional gfan_0.6.2-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAluBIiEACgkQjIIWnY7O zSriIA/8Dk9VhbAUSSDL4m2vJtbuYfH2akofo0mBU6hWhEicYQCAD8YLmNVi9P1x qbqNBz69mEvoOM9bBiXY31nnv5jywCxcBYZ0aJLqSc6UTPmFEj7rnpu6L5MLaXf8 0B/hS+YNOizyfmh7YEf+YIclinZHIHcpaPkIs7xExKm4VyQX0+T1t6PmwOQFIi4V dC7rn+bfpt7ZInLsEfx5DQLV64snPEJa/5sbg1JzYu1JFnGGytY8hSJpICE1egdV +2nFIbleW6+FTMqs1M8qRELtcUMl9t7CQ+zF8Heg3CgaLfK23sYkmIzbeAU97iTY 2Fh67oTJTyUhJj9JOgokH84l7TmNwXGX31TBEjH5ZTjriXiN7HsaBZgaBjZFKOuU X4EyDew2O3XIGPYk4xyIskxnKFd3CKHds/elwZ0ULtaeQ5FySQmYLiBwuQ5I3SeF Ti3N04+UpAjZNSmyBhIS+pSWdY1SMOYISqMXZ82ttbC075gf2bHADlSdx3NaInUc AKPgBcIrmZZqCIXKC7sfitgkr4+7H860Ruvn+R8e7wG0giyESsmlMnKWYs6ChfSy cU9ffmV4Lb+qaT7HZuTupvC18SEc+N687aFWcA04rl7niGIuq1cm3fXQzgIc09oW d58+IsYfDp+TYdUNFovo0c8paEdqSmX3QXVPyUGgON2Wj3nGotI= =tcHG -END PGP SIGNATURE End Message ---
Processed: Re: Bug#907230: kmail-account-wizard: FTBFS with Qt 5.11
Processing control commands: > fixed -1 4:18.07.90-1 Bug #907230 [src:kmail-account-wizard] kmail-account-wizard: FTBFS with Qt 5.11 The source 'kmail-account-wizard' and version '4:18.07.90-1' do not appear to match any binary packages Marked as fixed in versions kmail-account-wizard/4:18.07.90-1. -- 907230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907205: marked as done (psi: FTBFS in buster/sid (no type named 'type' in 'struct std::enable_if'))
Your message dated Sat, 25 Aug 2018 09:35:02 + with message-id and subject line Bug#907205: fixed in psi 1.3-5 has caused the Debian Bug report #907205, regarding psi: FTBFS in buster/sid (no type named 'type' in 'struct std::enable_if') 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.) -- 907205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:psi Version: 1.3-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --parallel dh_update_autotools_config -a -O--parallel debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' qt-qconf Project name: Psi Profile: psi.pro Deps: qt4* buildmodeapp* idn* qca* zlib* qjdns* x11* universal qdbus qtmultimedia* webkit growl whiteboarding xss aspell enchant hunspell spell* plugins conf* recursiveprl* 'configure' written. 'configure.exe' written. ls -al total 464 [... snipped ...] from /usr/include/Qca-qt5/QtCrypto/qca.h:36, from /usr/include/Qca-qt5/QtCrypto/QtCrypto:1, from accountmanagedlg.cpp:21: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note: candidate: 'template static typename std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, Func2)' connect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, Func2 slot) ^~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note: template argument deduction/substitution failed: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 'template static typename std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, Func2) [with Func1 = const char*; Func2 = const char*]': accountmanagedlg.cpp:115:66: required from here /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: error: no type named 'type' in 'struct std::enable_if' /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 'template static typename std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) && (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, Qt::ConnectionType)' connect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, const QObject *context, Func2 slot, ^~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: template argument deduction/substitution failed: accountmanagedlg.cpp:115:66: note: candidate expects 5 arguments, 3 provided connect(d->bg, SIGNAL(buttonClicked(int)), SLOT(bg_clicked(int))); ^ In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qiodevice.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdatastream.h:44, from /usr/include/x86_64-linux-gnu/qt5/QtGui/qregion.h:49, from /usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtGui/QList:1, from /usr/include/Qca-qt5/QtCrypto/qca_core.h:38, from /usr/include/Qca-qt5/QtCrypto/qca.h:36, from /usr/include/Qca-qt5/QtCrypto/QtCrypto:1, from accountmanagedlg.cpp:21: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 'template static typename std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), QMetaObject::Connection>::type QObject::connect(const typename QtPrivate::FunctionPointer::Object*, Func1, Func2)' connect(const typename QtPrivate::FunctionPointer::Object *sender, Func1 signal, Func2 slot) ^~~ /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: template argument deduction/substitution failed: /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 'template static typename std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), QMetaObject::Connection>::type
Bug#907230: kmail-account-wizard: FTBFS with Qt 5.11
Control: fixed -1 4:18.07.90-1 Hey, these bugs are handled with the new upstream version of KDE PIM, that is currently sitting in experimental and NEW queue. But at least I have compile the whole new KDE PIM against Qt 5.11. Please check before filing those bugs if a new version waits in experimental/NEW queue. hefee -- signature.asc Description: This is a digitally signed message part.
Bug#905434: marked as done (fpylll: FTBFS: error: 'class fplll::MatrixRow<...>' has no member named 'dot_product')
Your message dated Sat, 25 Aug 2018 09:18:51 +
with message-id
and subject line Bug#905434: fixed in fpylll 0.4.1+ds1-2
has caused the Debian Bug report #905434,
regarding fpylll: FTBFS: error: 'class fplll::MatrixRow<...>' has no member
named 'dot_product'
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.)
--
905434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fpylll
Version: 0.4.1+ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
fpylll/experimental recently started to FTBFS, maybe related to the
switch of the default gcc to gcc-8.
[...]
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/fpylll-0.4.1+ds1=.
-fstack-protector-strong -Wformat -Werror=format-security -W
date-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/lib/python2.7/dist-packages/cysignals -I/usr/include
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7
-c build/src/fpylll/fplll/integer_matr
ix.cpp -o build/temp.linux-amd64-2.7/build/src/fpylll/fplll/integer_matrix.o
-std=c++11 -g -O2 -fdebug-prefix-map=/build/fpylll-0.4.1+ds1=.
-fstack-protector-strong -Wformat -Werror=format-security
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC
but not for C++
build/src/fpylll/fplll/integer_matrix.cpp: In function 'PyObject*
__pyx_pf_6fpylll_5fplll_14integer_matrix_16IntegerMatrixRow_10__abs__(__pyx_obj_6fpylll_5fplll_14integer_matrix_IntegerMatrixRow*)':
build/src/fpylll/fplll/integer_matrix.cpp:3285:58: error: 'class
fplll::MatrixRow >' has no member named
'dot_product'
((__pyx_v_self->m->_core.mpz[0])[__pyx_v_self->row]).dot_product(__pyx_v_t_mpz,
((__pyx_v_self->m->_core.mpz[0])[__pyx_v_self->row]));
^~~
build/src/fpylll/fplll/integer_matrix.cpp:3374:65: error: 'class
fplll::MatrixRow >' has no member named 'dot_product'
((__pyx_v_self->m->_core.__pyx_long[0])[__pyx_v_self->row]).dot_product(__pyx_v_t_l,
((__pyx_v_self->m->_core.__pyx_long[0])[__pyx_v_self->row]));
^~~
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1:
/usr/bin/python setup.py build
dh_auto_build: pybuild --build --test-pytest -i python{version} -p 2.7 returned
exit code 13
make: *** [debian/rules:11: build] Error 25
Andreas
fpylll_0.4.1+ds1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fpylll
Source-Version: 0.4.1+ds1-2
We believe that the bug you reported is fixed in the latest version of
fpylll, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Tobias Hansen (supplier of updated fpylll package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 21 Aug 2018 10:50:26 +0200
Source: fpylll
Binary: python-fpylll python3-fpylll python-fpylll-doc
Architecture: source
Version: 0.4.1+ds1-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Tobias Hansen
Description:
python-fpylll - Python wrapper for LLL-reduction of Euclidean lattices --
Python
python-fpylll-doc - Python wrapper for LLL-reduction of Euclidean lattices --
doc
python3-fpylll - Python wrapper for LLL-reduction of Euclidean lattices --
Python
Closes: 905434
Changes:
fpylll (0.4.1+ds1-2) experimental; urgency=medium
.
* Team upload.
.
[ Ondřej Nový ]
* Convert git repository from git-dpm to gbp layout
.
[ Tobias Hansen ]
* Build-Depend on fplll 5.2.1. (Closes: #905434)
Checksums-Sha1:
c55d4df83db17502f3e831fb87b83205f06953b3 2716 fpylll_0.4.1+ds1-2.dsc
4201aa98d6d27713c80d8ebd02c161776fe97576 3796 fpylll_0.4.1+ds1-2.debian.tar.xz
c57fbf660f4619ca87b808ceeb95fabf793bcc68 7199
fpylll_0.4.1+ds1-2_source.buildinfo
Checksums-Sha256:
Bug#907108: marked as done (cockpit: binary-all FTBFS)
Your message dated Sat, 25 Aug 2018 08:49:03 + with message-id and subject line Bug#907108: fixed in cockpit 176-2 has caused the Debian Bug report #907108, regarding cockpit: binary-all FTBFS 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.) -- 907108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cockpit Version: 176-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=cockpit=all=176-1=1534952311=0 ... make[2]: Leaving directory '/<>' if [ -z "" ]; then rm debian/cockpit-ws/usr/lib/firewalld/services/cockpit.xml; rmdir -p --ignore-fail-on-non-empty debian/cockpit-ws/usr/lib/firewalld/services/; fi rm: cannot remove 'debian/cockpit-ws/usr/lib/firewalld/services/cockpit.xml': No such file or directory rmdir: failed to remove 'debian/cockpit-ws/usr/lib/firewalld/services/': No such file or directory make[1]: *** [debian/rules:78: override_dh_install] Error 1 --- End Message --- --- Begin Message --- Source: cockpit Source-Version: 176-2 We believe that the bug you reported is fixed in the latest version of cockpit, 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 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated cockpit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Aug 2018 08:35:14 + Source: cockpit Binary: cockpit cockpit-bridge cockpit-dashboard cockpit-doc cockpit-docker cockpit-machines cockpit-networkmanager cockpit-pcp cockpit-packagekit cockpit-storaged cockpit-system cockpit-tests cockpit-ws Architecture: source Version: 176-2 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Martin Pitt Description: cockpit- User interface for Linux servers cockpit-bridge - Cockpit bridge server-side component cockpit-dashboard - Cockpit remote servers and dashboard cockpit-doc - Cockpit deployment and developer guide cockpit-docker - Cockpit user interface for Docker containers cockpit-machines - Cockpit user interface for virtual machines cockpit-networkmanager - Cockpit user interface for networking cockpit-packagekit - Cockpit user interface for packages cockpit-pcp - Cockpit PCP integration cockpit-storaged - Cockpit user interface for storage cockpit-system - Cockpit admin interface for a system cockpit-tests - Tests for Cockpit cockpit-ws - Cockpit Web Service Closes: 907108 Changes: cockpit (176-2) unstable; urgency=medium . * Fix arch-indep build. When building only arch-indep packages, the cockpit-ws package does not get built, and trying to remove the firewalld service failed. (Closes: #907108) Checksums-Sha1: c6adff9ee0d587bd9a91d9852694501d228a72e5 3108 cockpit_176-2.dsc 81c3cae3464a3650cda02536e2f160e70444722b 14268 cockpit_176-2.debian.tar.xz f330f206f61b2cdc02f66f2333abc532f8765fd3 10195 cockpit_176-2_source.buildinfo Checksums-Sha256: 30c7bac5d3a954ee75702c6f7204b15267346cdbb6570510a15e2adef79e51a0 3108 cockpit_176-2.dsc 83250556cbb905fb072ff3afe3e1e82a37cac91b7343d7acb92cba7aee35b293 14268 cockpit_176-2.debian.tar.xz 0882a605c46990c17ed68785cf26730a9be241903769a18791387a7ee648da44 10195 cockpit_176-2_source.buildinfo Files: 05c0c933141759c33faf318178c96dde 3108 admin optional cockpit_176-2.dsc 961b9d6430be4561275b616a1540c6db 14268 admin optional cockpit_176-2.debian.tar.xz c95a43bf08cec5eb6bd2ec27b006cc7a 10195 admin optional cockpit_176-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAluBFWIACgkQxrkYDUvY t66dFQ/+Nf2dSQVVSTCj7IcidUbOHXRffbGI5bB5DYXhJwhLm3zf4ZbvoX41ixhv TM1dJkAANRIx3igLFKwAS9Yimxe7Q+YXDNOfyYrxn0ZqvgQv/bJxCRTqTX28P/Qv gu3SRWluWKBU96rbi1C9B47/tdai48VWY9nW/uksdR3LSYPcznOWHT/8vaz5wmf8 LpRZMry1s2YjoaeC+R0iLArweewkmTaeqo3EQqQ/tvyPIj0E77Gvl9avL0U/JZhK jSKQzH+XN+oNwu+u7fZtX/ky2zkpCcY7o2gGOHizFmc7dQ+sI+4p3IVsmIj2j8ij bzRIL4LXG2nqlCxjv0R/qo/QQu3Wmt9IneMfV0EP4HRR0nHz6+89N/bTDy8d0o9Z Ub8XoWDF1rErKCVibMdYAiSc4B/GtC6ptHYtHGJGx3IRP4hYQpUK5iJh4MefPJSD
Bug#858938: fixed in kopete 4:18.04.1-1
On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote: > Source: kopete > Source-Version: 4:18.04.1-1 > > We believe that the bug you reported is fixed in the latest version of > kopete, which is due to be installed in the Debian FTP archive. Any plans to upload this to unstable? Kurt
Bug#906385: Bug #906385 in ms-gsl marked as pending
Control: tag -1 pending Hello, Bug #906385 in ms-gsl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/debian/ms-gsl/commit/b06f095c5b83f113e3cedd3beffde42e5c02f7c7 Add Catch-Classic-Workaround.patch Closes: #906385 (this message was generated automatically) -- Greetings https://bugs.debian.org/906385
Processed: Bug #906385 in ms-gsl marked as pending
Processing control commands: > tag -1 pending Bug #906385 [src:ms-gsl] ms-gsl: FTBFS in buster/sid (error: catching polymorphic type 'struct gsl::fail_fast' by value) Added tag(s) pending. -- 906385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904709: New upstream version requires new Build-Depends
Hi, to fix this I'm trying the latest upstream version which needs python-depinfo and python-pipdeptree. I'm about to upload these packages to new. Kind regards Andreas. -- http://fam-tille.de
Bug#907239: ldc: FTBFS on ppc64el with .../disassembler.cpp.o uses 64-bit long double, .../libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double
Source: ldc Version: 1:1.11.0-1 Severity: serious Hi, The ldc package FTBFS on ppc64el but built there in the past. """ /usr/bin/c++ -DLDC_DYNAMIC_COMPILE -DLDC_DYNAMIC_COMPILE_API_VERSION=1 -DLDC_ENABLE_PLUGINS -DLDC_LLVM_SUPPORTED_TARGET_AArch64=1 -DLDC_LLVM_SUPPORTED_TARGET_AMDGPU=1 -DLDC_LLVM_SUPPORTED_TARGET_ARM=1 -DLDC_LLVM_SUPPORTED_TARGET_AVR=1 -DLDC_LLVM_SUPPORTED_TARGET_BPF=1 -DLDC_LLVM_SUPPORTED_TARGET_Hexagon=1 -DLDC_LLVM_SUPPORTED_TARGET_Lanai=1 -DLDC_LLVM_SUPPORTED_TARGET_MSP430=1 -DLDC_LLVM_SUPPORTED_TARGET_Mips=1 -DLDC_LLVM_SUPPORTED_TARGET_NVPTX=1 -DLDC_LLVM_SUPPORTED_TARGET_PowerPC=1 -DLDC_LLVM_SUPPORTED_TARGET_Sparc=1 -DLDC_LLVM_SUPPORTED_TARGET_SystemZ=1 -DLDC_LLVM_SUPPORTED_TARGET_WebAssembly=1 -DLDC_LLVM_SUPPORTED_TARGET_X86=1 -DLDC_LLVM_SUPPORTED_TARGET_XCore=1 -I/<>/. -I/<>/dmd -I/<>/dmd/root -I/<>/build-static/dmd -I/<> -isystem /usr/lib/llvm-6.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DDMDV2 -DHAVE_SC_ARG_MAX -I/usr/lib/llvm-6.0/include -std=c++0x -fuse-ld=gold -Wl,--no-keep-files-mapped -Wl,--no-map-whole-files -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -O2 -DNDEBUG -fno-exceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wno-non-virtual-dtor -Wno-pedantic -mlong-double-64 -DLDC_POSIX -DIN_LLVM -DOPAQUE_VTBLS "-DLDC_INSTALL_PREFIX=/usr" -DLDC_LLVM_VER=600 "-DLDC_LIBDIR_SUFFIX=\"\"" -DLDC_HOST_LDMD=1 -DLDC_HOST_FE_VER=2068 -o CMakeFiles/LDCShared.dir/gen/arrays.cpp.o -c /<>/gen/arrays.cpp /usr/bin/ld: CMakeFiles/ldc-jit-rt-so.dir/jit-rt/cpp-so/disassembler.cpp.o uses 64-bit long double, /usr/lib/llvm-6.0/lib/libLLVMCore.a(LegacyPassManager.cpp.o) uses 128-bit long double /usr/bin/ld: failed to merge target specific data of file /usr/lib/llvm-6.0/lib/libLLVMCore.a(LegacyPassManager.cpp.o) collect2: error: ld returned 1 exit status """ This issue prevents ldc from migrating to testing. Thanks, ~Niels
Bug#835962: marked as done (llvm-toolchain-snapshot: non-standard gcc/g++ used for build (gcc-5))
Your message dated Sat, 25 Aug 2018 10:40:36 +0300 with message-id <20180825074036.GL3214@localhost> and subject line This seems to be already fixed has caused the Debian Bug report #835962, regarding llvm-toolchain-snapshot: non-standard gcc/g++ used for build (gcc-5) 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.) -- 835962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-toolchain-snapshot Version: 1:4.0~svn279916-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-5, gcc-5-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-6/g++-6. Please keep this report open until the package uses the default compiler version (or gcc-6) for the package build. If the package cannot be built anymore, please file a bug report for ftp.debian.org, asking for the removal of the package. The severity of this report is likely to be raised before the release, so that the gcc-5 package can be removed for the release. --- End Message --- --- Begin Message --- I don't know when it was fixed, but llvm-toolchain-snapshot no longer uses a non-standard gcc/g++ (and definitely no longer gcc 5). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed--- End Message ---
Processed: tagging 907227
Processing commands for cont...@bugs.debian.org: > tags 907227 + buster sid Bug #907227 [src:equalx] equalx: FTBFS with Qt 5.11 Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 907227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906375: Tried new upstream version
Hi, I realised that there is a new upstream version, fixed the watch file in Git and tried to build the package. Unfortunately the build fails as well. I commited my attempt anyway and hope this small contribution will help fixing the issue some more skilled Java developer than me. Kind regards Andreas. -- http://fam-tille.de
Bug#906972: aspectc++: FTBFS in buster/sid
Package: aspectc++ Version: 1:2.2+git20170823-7 Followup-For: Bug #906972 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic ubuntu-patch Dear Reinhard, Attached is a patch that fixes this bug. It ends up that this is a bug introduced as a direct consequence of the fix for bug #902220, because now aspectc++ build-depends on unversioned llvm-dev / libclang-dev, but still references llvm-config-4.0 in debian/rules; so now that llvm-dev no longer points at llvm 4.0, this doesn't work. I tried replacing the references to llvm-config-4.0 with plain llvm-config, but this also fails because aspectc++ isn't yet compatible with llvm 6.0. So instead, it's best to revert to build-depending specifically on llvm-4.0 for now. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru aspectc++-2.2+git20170823/debian/control aspectc++-2.2+git20170823/debian/control --- aspectc++-2.2+git20170823/debian/control2018-06-25 07:59:10.0 -0700 +++ aspectc++-2.2+git20170823/debian/control2018-08-24 21:29:52.0 -0700 @@ -2,7 +2,7 @@ Section: devel Priority: optional Maintainer: Reinhard Tartler -Build-Depends: debhelper (>= 9), libxml2-dev, docbook-to-man, zlib1g-dev, libedit-dev, llvm-dev, libclang-dev +Build-Depends: debhelper (>= 9), libxml2-dev, docbook-to-man, zlib1g-dev, libedit-dev, llvm-4.0-dev, libclang-4.0-dev Build-Depends-Indep: doxygen, graphviz, gsfonts Standards-Version: 4.0.0 Homepage: http://www.aspectc.org
