Bug#911514: davmail: fails to install: wrong update-rc.d usage
On 2018-10-30 09:52, Alexandre Rossi wrote: > Hi Geert, > >> I've prepared updates for the davmail backport and its libhtmlcleaner >> dependency : >> https://sml.zincube.net/~niol/tmp/ >> >> Those are awaiting sponsorship (the process for granting me upload >> rights also to backports is ongoing). > > Granting me upload rights to the backports archive does not seem to > move forward. If you have some time to sponsor those uploads, please > go on. building the libhtmlcleaner-java backport in stretch fails: [INFO] Building HtmlCleaner 2.21 [INFO] [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ htmlcleaner --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /build/libhtmlcleaner-java-2.21/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ htmlcleaner --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ htmlcleaner --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 64 resources [INFO] [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ htmlcleaner --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ htmlcleaner --- [INFO] Surefire report directory: /build/libhtmlcleaner-java-2.21/target/surefire-reports --- T E S T S --- Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.729 s [INFO] Finished at: 2018-12-01T07:49:40+00:00 [INFO] Final Memory: 12M/365M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project htmlcleaner: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /build/libhtmlcleaner-java-2.21 && /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -jar /build/libhtmlcleaner-java-2.21/target/surefire/surefirebooter8827901967415424500.jar /build/libhtmlcleaner-java-2.21/target/surefire/surefire969640660163927236tmp /build/libhtmlcleaner-java-2.21/target/surefire/surefire_02387711883238815967tmp [ERROR] -> [Help 1] You may also want to update the devmail backport to the version in testing. Andreas
Bug#915150: gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
Control: clone -1 -2 Control: reassign -2 src:m4 On Sat, Dec 01, 2018 at 08:07:23AM +0100, Helmut Grohne wrote: > gzip fails to build from source in unstable (since the glibc upgrade to > 2.28): m4 has another copy of the bug. Helmut
Processed: Re: gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
Processing control commands: > clone -1 -2 Bug #915150 [src:gzip] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Bug 915150 cloned as bug 915152 > reassign -2 src:m4 Bug #915152 [src:gzip] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Bug reassigned from package 'src:gzip' to 'src:m4'. No longer marked as found in versions gzip/1.9-2.1. Ignoring request to alter fixed versions of bug #915152 to the same values previously set -- 915150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915150 915152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915150: gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
Source: gzip Version: 1.9-2.1 Severity: serious Tags: ftbfs User: helm...@debian.org Usertags: rebootstrap Control: clone -1 -2 Control: reassign -2 gnulib Control: found -2 gnulib/20140202+stable-3 Control: retitle -2 gnulib does not work with glibc/2.28 Control: affects -2 + src:lbzip2 gzip fails to build from source in unstable (since the glibc upgrade to 2.28): | CC fseeko.o | ../../lib/fseeko.c: In function 'rpl_fseeko': | ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." |#error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." | ^ | make[4]: *** [Makefile:1775: fseeko.o] Error 1 | make[4]: Leaving directory '/<>/builddir/lib' | make[3]: *** [Makefile:1580: all] Error 2 | make[3]: Leaving directory '/<>/builddir/lib' | make[2]: *** [Makefile:1746: all-recursive] Error 1 | make[2]: Leaving directory '/<>/builddir' | make[1]: *** [Makefile:1527: all] Error 2 | make[1]: Leaving directory '/<>/builddir' | make: *** [debian/rules:96: build-stamp] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 gnulib likes to use this construct to detect glibc: | #if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ Unfortunately, _IO_ftrylockfile got removed from glibc/2.28 and __GNU_LIBRARY__ is 6, so glibc is not a GNU libc. gnulib has a history of breaking packages frequently. What makes matters worse is that gnulib gets embedded rather than used like any other component. So fixing this bug in gnulib does not fix gzip. I therefore cloned a separate instance as it still breaks e.g. lbzip2. Helmut
Processed: gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
Processing control commands: > clone -1 -2 Bug #915150 [src:gzip] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Bug 915150 cloned as bug 915151 > reassign -2 gnulib Bug #915151 [src:gzip] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Bug reassigned from package 'src:gzip' to 'gnulib'. No longer marked as found in versions gzip/1.9-2.1. Ignoring request to alter fixed versions of bug #915151 to the same values previously set > found -2 gnulib/20140202+stable-3 Bug #915151 [gnulib] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Marked as found in versions gnulib/20140202+stable-3. > retitle -2 gnulib does not work with glibc/2.28 Bug #915151 [gnulib] gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." Changed Bug title to 'gnulib does not work with glibc/2.28' from 'gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."'. > affects -2 + src:lbzip2 Bug #915151 [gnulib] gnulib does not work with glibc/2.28 Added indication that 915151 affects src:lbzip2 -- 915150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915150 915151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > notfound 915148 3.12.3-3thanks Bug #915148 [cmake] cmake: regression in ros-ros-comm build There is no source info for the package 'cmake' at version '3.12.3-3thanks' with architecture '' Unable to make a source version for version '3.12.3-3thanks' Ignoring request to alter found versions of bug #915148 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 915148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915148: cmake: regression in ros-ros-comm build
control: affects -1 ros-ros-comm control: notfound -1 3.12.3-3 fixing tags. G.
Processed: Re: cmake: regression in ros-ros-comm build
Processing control commands: > affects -1 ros-ros-comm Bug #915148 [cmake] cmake: regression in ros-ros-comm build Added indication that 915148 affects ros-ros-comm > notfound -1 3.12.3-3 Bug #915148 [cmake] cmake: regression in ros-ros-comm build Ignoring request to alter found versions of bug #915148 to the same values previously set -- 915148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914688: Default defines discrepancy
Hello, >I don't know how I can help here. Performous only fails on powerpc >architectures which looks like a Boost bug to me. This only happened >recently when we switched to 1.67, so maybe forward upstream and let's >find out what the upstream developers think about that? the boost patch is now part of the archive, and upstream codebase.I requested a give-back of the package, so it should build with no source changes now. G.
Processed: Re: [Debian-med-packaging] Bug#911492: htslib breaks python-pysam autopkgtest
Processing control commands: > severity -1 serious Bug #911492 [src:htslib, src:python-pysam] htslib breaks python-pysam autopkgtest Severity set to 'serious' from 'normal' -- 911492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914685: marked as done (android-platform-frameworks-base FTBFS on C++ "atomic" lib)
Your message dated Sat, 01 Dec 2018 04:04:02 + with message-id and subject line Bug#914685: fixed in android-platform-system-core 1:8.1.0+r23-4 has caused the Debian Bug report #914685, regarding android-platform-frameworks-base FTBFS on C++ "atomic" lib 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.) -- 914685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: android-libcutils-dev Version: 1:8.1.0+r23-3 Severity: critical When building android-platform-frameworks-base, it fails to build with errors related to the C++ "atomic" lib. seamlik says this is due to an issue in android-libcutils-dev, which provides that lib for the Android packages. It is probably related to this patch: https://salsa.debian.org/android-tools-team/android-platform-system-core/commit/8199845aa4559672859f70876f099fb0312c7279 Two examples: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-frameworks-base.html https://salsa.debian.org/android-tools-team/android-platform-frameworks-base/-/jobs/77824 --- End Message --- --- Begin Message --- Source: android-platform-system-core Source-Version: 1:8.1.0+r23-4 We believe that the bug you reported is fixed in the latest version of android-platform-system-core, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kai-Chung Yan (supplier of updated android-platform-system-core 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, 01 Dec 2018 11:41:53 +0800 Source: android-platform-system-core Binary: android-sdk-libsparse-utils android-liblog android-liblog-dev android-libcutils android-libcutils-dev adb android-libsparse android-libsparse-dev android-libutils android-libutils-dev android-libziparchive android-libziparchive-dev android-platform-system-core-headers android-libbacktrace android-libbacktrace-dev android-libadb android-libadb-dev android-libbase android-libbase-dev android-libcrypto-utils android-libcrypto-utils-dev simg2img img2simg append2simg android-tools-adb android-tools-fastboot android-tools-mkbootimg mkbootimg fastboot android-libnativebridge android-libnativebridge-dev android-libnativeloader android-libnativeloader-dev Architecture: source Version: 1:8.1.0+r23-4 Distribution: unstable Urgency: medium Maintainer: Android Tools Maintainers Changed-By: Kai-Chung Yan Description: adb- Android Debug Bridge android-libadb - Library for Android Debug Bridge android-libadb-dev - Library for Android Debug Bridge - Development files android-libbacktrace - Android backtrace library android-libbacktrace-dev - Android backtrace library - Development files android-libbase - Android base library android-libbase-dev - Android base library - Development files android-libcrypto-utils - Android crypto-utils library android-libcrypto-utils-dev - Android crypto-utils library - Development files android-libcutils - Android utils library for C android-libcutils-dev - Android utils library for C - Development files android-liblog - Android NDK logger interfaces android-liblog-dev - Android NDK logger interfaces - Development files android-libnativebridge - Android native bridge library android-libnativebridge-dev - Android native bridge library - Development files android-libnativeloader - Android native loader library android-libnativeloader-dev - Android native loader library - Development files android-libsparse - Library for sparse files android-libsparse-dev - Library for sparse files - Development files android-libutils - Android Utility Function Library android-libutils-dev - Android Utility Function Library - Development files android-libziparchive - Library for ZIP archives android-libziparchive-dev - Library for ZIP archives - Development files android-platform-system-core-headers - Shared headers in AOSP repository platform/system/core android-sdk-libsparse-utils - Android sparse image creation tool android-tools-adb - transitional package android-tools-fastboot
Bug#840388: fusedav non-functional
Carsten Leonhardt wrote: > Control: severity -1 grave > > This software appears to be non-functional. A tcpdump confirms that no > network traffic between the client and the server is being generated. Fwiw, I have filed many bugfixes against this package years ago but the maintainer is not responsive. All my fixes are at, and I still use it daily (: git clone https://bogomips.org/fusedav.git AFAIK, there was one unresolved corner-case with readdirplus support I never got around to fixing[1], but it works for common cases with "ls" [1] https://marc.info/?i=20140609094046.ga1...@dcvr.yhbt.net
Bug#840388: fusedav non-functional
Eric Wong wrote: > AFAIK, there was one unresolved corner-case with readdirplus > support I never got around to fixing[1], but it works for common > cases with "ls" [1] Sorry, correct URL is: https://marc.info/?i=CAJfpeguWVhpPkUoTxGrW=kc43rrksjtwoq0ysczl0_oc9jl...@mail.gmail.com for Miklos's response to my attempted patch.
Bug#895418: marked as done (systemd-shim: incompatibility with a new version of systemd)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #895292, regarding systemd-shim: incompatibility with a new version of systemd 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.) -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: important Affects: gdm3 Hi, I admit I didn't spend much time investigating this issue (I need a working Sid box), but from past experience, I guess it comes from a new systemd-shim incompatibility introduced by some change in systemd-logind (or GDM, but IMHO it's less unlikely than systemd). The symptoms are identical to #801749 (but since people there mention journalctl, I guess they were not using SysV init, so it can't be a duplicate of this bug): GDM doesn't start (the screen keeps displaying the console, with the cursor blinking frenetically), and syslog shows lots and lots of "gdm3: Child process XYZ was already dead." and "gdm3: Unable to kill session worker process". lightdm (under SysV init) does start normally. Switching the init system to systemd gets rid of the problem, and allows GDM to start normally (this is why I'm filing this report against systemd-shim). Please note that I didn't try to downgrade systemd or GDM to find the exact culprit (or the version introducing the change), I made an educated guess and switched the init system directly, which worked. I have a lot of stuff to do on my Sid box ATM and I can't afford the time. Please also note that I don't reboot this box very often, so the incompatibility may have been introduced by a systemd update a long time ago, not necessarily the latest one. Regards, -- Raphaël Halimi --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#903295: marked as done (libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #903295, regarding libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed 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.) -- 903295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: grave Justification: renders package unusable Dear Maintainer, I am running sysvinit-core based desktop Debian system (sid). When recently trying to dist-upgrade, libpam-systend package requires systemd-shim version >=10-4~ but there is no such version in repositories. The only alternative is replacing sysvinit-core with systemd-sysv i.e. running systemd as init system. This renders package systemd-shim unusable. root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ libpam-systemd+ Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-core is already the newest version (2.88dsf-59.10). Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to be installed or systemd-sysv but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd-shim depends on: ii cgmanager 0.41-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-18 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#912267: marked as done (uddi4j: FTBFS with Java 11 due to JAXWS removal)
Your message dated Sat, 01 Dec 2018 03:05:12 + with message-id and subject line Bug#915029: Removed package(s) from unstable has caused the Debian Bug report #912267, regarding uddi4j: FTBFS with Java 11 due to JAXWS removal 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.) -- 912267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uddi4j Version: 2.0.5-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uddi4j.html ... compile: [mkdir] Created dir: /build/1st/uddi4j-2.0.5/build/classes [javac] /build/1st/uddi4j-2.0.5/build.xml:158: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 106 source files to /build/1st/uddi4j-2.0.5/build/classes [javac] error: module not found: java.xml.ws [javac] 1 error BUILD FAILED /build/1st/uddi4j-2.0.5/build.xml:158: Compile failed; see the compiler error output for details. Total time: 2 seconds dh_auto_build: ant -propertyfile ./debian/ant.properties -Duser.name debian dist returned exit code 1 make[1]: *** [debian/rules:9: override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Version: 2.0.5-4+rm Dear submitter, as the package uddi4j has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915029 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#895292: marked as done (Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #895292, regarding Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm 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.) -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: policykit-1 Version: 0.105-20 Severity: important After the upgrade to policykit-1 0.105-20, the Restart, Suspend, Hibernate, Shut Down menu entries are all greyed out. Note: lightdm and lightdm-gtk-greeter have not changed. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages policykit-1 depends on: ii dbus 1.12.6-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.0-6 ii libpam-systemd 238-4 ii libpam0g 1.1.8-3.7 ii libpolkit-agent-1-00.105-20 ii libpolkit-backend-1-0 0.105-20 ii libpolkit-gobject-1-0 0.105-20 policykit-1 recommends no packages. policykit-1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#901404: marked as done (systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #901404, regarding systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable 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.) -- 901404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: shim-patches-removal Hello Debian systemd-shim Maintainers, The Debian systemd package is currently carrying a debian-specific patch to enable usage of various systemd daemons via systemd-shim on Debian systems. In particular, it patches several systemd services to make them activatable by DBus. [1] Unfortunately none of the systemd maintainers actively tests the non-systemd code paths in those daemons anymore, so we don't feel comfortable enabling those services for sysvinit in the systemd package itself. systemd-shim already has code to dpkg-divert a dbus service provided by systemd, so we think systemd-shim should take over the divert of the rest of the units which it wants to support to run under sysvinit. We intend to drop the patch before buster is released in the not too distant future. When we do that, we will bump the severity of this bug report to serious. [1] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-logind-hostnamed-localed-timedated-D-Bus-activa.patch Saludos, Felipe Sateler -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-shim depends on: pn cgmanager ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: pn pm-utils --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#901405: marked as done (systemd-shim: Please add a sysvinit service to create directories on /run at boot)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #901405, regarding systemd-shim: Please add a sysvinit service to create directories on /run at boot 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.) -- 901405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: shim-patches-removal Hello Debian systemd-shim Maintainers, The Debian systemd package is currently carrying two debian-specific patches to enable usage of systemd-shim on Debian systems. In particular, we patch some code to continue even if /run/systemd/machines/ and /run/systemd/machines/ don't exist[1][2]. These two patches could be avoided if systemd-shim would create the relevant directories during early boot (sometime in rcS). Therefore we would like for systemd-shim to provide these directories so we can drop these patches. If you ship such a SysV init script, please make sure to mask that, so it is not accidentally run when systemd is the active PID 1 (assuming the SysV init script is called /etc/init.d/systemd-shim, the symlink would be /lib/systemd/system/systemd-shim.service → /dev/null). We intend to drop the patches before buster is released in the not too distant future. When we do that, we will bump the severity of this bug report to serious. [1] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Start-logind-on-demand-via-libpam-systemd.patch [2] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-sd_login_monitor_new-work-for-logind-without-sy.patch Saludos, Felipe Sateler -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-shim depends on: pn cgmanager ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: pn pm-utils --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#907486: marked as done (libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #903295, regarding libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed 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.) -- 903295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-systemd Version: 238-5 Severity: grave Justification: renders package unusable Dear Maintainer, (This bug has been reported also against systemd-shim: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 ) libpam-systemd requires systemd-shim version >=10-4~. No such version exists. This would make systemd-shim unusable. root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ libpam-systemd+ Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-core is already the newest version (2.88dsf-59.10). Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to be installed or systemd-sysv but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), LANGUAGE=es_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libpam-systemd depends on: ii dbus1.12.10-1 ii libc6 2.27-5 ii libpam-runtime 1.1.8-3.8 ii libpam0g1.1.8-3.8 ii systemd 238-5 ii systemd-shim10-3 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#866671: marked as done (webkitgtk: Unmaintained, not suitable for buster)
Your message dated Sat, 01 Dec 2018 02:45:29 +
with message-id
and subject line Bug#893863: Removed package(s) from unstable
has caused the Debian Bug report #866671,
regarding webkitgtk: Unmaintained, not suitable for 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.)
--
866671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webkitgtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1
Hi,
I am opening a tracking bug since we do not want webkitgtk in the next
major stable release of Debian ('buster").
Packages that use webkitgtk should be ported to webkit2gtk. Otherwise,
they will eventually need to be removed from Debian.
On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.4.11-4+rm
Dear submitter,
as the package webkitgtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/893863
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#914495: linux-image-4.18.0-3-amd64: The system hangs even before the screen font gets smaller. There's just a black screen.
Package: src:linux Version: 4.18.20-2 Followup-For: Bug #914495 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Booting into linux-image-4.18.0-3-amd64. * What exactly did you do (or not do) that was effective (or ineffective)? I crashed the system by switching off the power and then booted into linux-image-4.18.0-2-amd64. * What was the outcome of this action? It works as before. * What outcome did you expect instead? I expected it to work. *** End of the template - remove these template lines *** -- Package-specific info: ** Kernel log: boot messages should be attached I'll attach /var/log/kern.log if I can find out how to. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.18.0-3-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.132 ii kmod25-2 ii linux-base 4.5 Versions of packages linux-image-4.18.0-3-amd64 recommends: ii apparmor 2.13.1-3+b1 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-0.1 Versions of packages linux-image-4.18.0-3-amd64 suggests: ii debian-kernel-handbook 1.0.19 ii grub-pc 2.02+dfsg1-8 pn linux-doc-4.18 Versions of packages linux-image-4.18.0-3-amd64 is related to: ii firmware-amd-graphics 20180825+dfsg-1 ii firmware-atheros 20180825+dfsg-1 pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20180825+dfsg-1 pn firmware-libertas ii firmware-linux-nonfree20180825+dfsg-1 ii firmware-misc-nonfree 20180825+dfsg-1 pn firmware-myricom pn firmware-netxen pn firmware-qlogic ii firmware-realtek 20180825+dfsg-1 pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#910547: marked as done (gutenprint: make distclean deletes doc/gutenprint{,ui2}/* which is not regenerated)
Your message dated Sat, 01 Dec 2018 01:34:06 +
with message-id
and subject line Bug#910547: fixed in gutenprint 5.3.1-3
has caused the Debian Bug report #910547,
regarding gutenprint: make distclean deletes doc/gutenprint{,ui2}/* which is
not regenerated
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.)
--
910547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gutenprint
Version: 5.3.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gutenprint FTBFS twice in a row. The first build succeeds, but the
subsequent debian/rules clean causes doc/gutenprint/*,
doc/gutenprintui2/* (and possibly more relevant files) to be deleted,
which are not regenerated during the second build.
>From the attached logfile:
[first build succeeded]
[from debian/rules clean after the first build]
...
Making distclean in doc
make[2]: Entering directory '/build/gutenprint-5.3.1/doc'
Making distclean in developer
make[3]: Entering directory '/build/gutenprint-5.3.1/doc/developer'
rm -rf .libs _libs
if test . = "." -a false = false ; then \
echo "clean-local: Not removing reference-html" ; \
echo 'clean-local: Not removing gutenprint.pdf' ; \
echo 'clean-local: Not removing gutenprint.ps' ; \
else \
rm -f gutenprint.pdf gutenprint.ps; rm -rf *html-stamp reference-html ; \
fi
rm -f *.lo
clean-local: Not removing reference-html
clean-local: Not removing gutenprint.pdf
clean-local: Not removing gutenprint.ps
if test . = "." ; then \
: ; \
else \
rm -f copying.xml dither.xml escp2.xml gutenprint.xml gpl-appendix.xml
introduction.xml new-printer.xml problems.xml using.xml weave.xml ; \
fi
test -z "" || rm -f
rm -rf *.tex *.log *.aux *.dvi *.gz *.out *.junk *.out *.fot
test . = "." || test -z "" || rm -f
rm -rf db2html* DB2HTML* CATALOG.local
rm -f Makefile
make[3]: Leaving directory '/build/gutenprint-5.3.1/doc/developer'
make[3]: Entering directory '/build/gutenprint-5.3.1/doc'
rm -rf .libs _libs
rm -f *.lo
test -z "gutenprint.dox gutenprintui2.dox" || rm -f gutenprint.dox
gutenprintui2.dox
rm -rf gutenprint
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
test . = "." || test -z "" || rm -f
test -z "gutenprint-stamp gutenprintui2-stamp" || rm -f gutenprint-stamp
gutenprintui2-stamp
rm -rf gutenprintui2
make[3]: Leaving directory '/build/gutenprint-5.3.1/doc'
rm -f Makefile
make[2]: Leaving directory '/build/gutenprint-5.3.1/doc'
...
[building the source package after the first build+clean causes dpkg-source to
report many deleted files]
...
dpkg-source: warning: ignoring deletion of file doc/gutenprintui2-stamp, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/Makefile.in, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprint-stamp, use
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/developer/Makefile.in, use
--include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprintui2
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/gutenprintui2.tag, use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprintui2/html
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/index.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/bc_s.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/folderopen.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/sync_off.png, use --include-removal to override
...
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/bdwn.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/splitbar.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file
doc/gutenprintui2/html/functions_vars.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprintui2/html/doc.png,
use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprint
dpkg-source: warning: ignoring deletion of file doc/gutenprint/gutenprint.tag,
use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprint/html
dpkg-source: warning: ignoring deletion of file
Processed: parley: diff for NMU version 4:17.08.3-1.1
Processing control commands:
> tags 906977 + pending
Bug #906977 [src:parley] parley: FTBFS in buster/sid ('QItemSelection' does not
name a type)
Added tag(s) pending.
--
906977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906977: parley: diff for NMU version 4:17.08.3-1.1
Control: tags 906977 + pending
Dear maintainer,
I've prepared an NMU for parley (versioned as 4:17.08.3-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru parley-17.08.3/debian/changelog parley-17.08.3/debian/changelog
--- parley-17.08.3/debian/changelog 2017-12-02 09:33:57.0 +0100
+++ parley-17.08.3/debian/changelog 2018-12-01 00:38:45.0 +0100
@@ -1,3 +1,12 @@
+parley (4:17.08.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "FTBFS in buster/sid ('QItemSelection' does not name a type)":
+add patch from upstream Git repo to fix build with Qt 5.11.
+(Closes: #906977)
+
+ -- gregor herrmann Sat, 01 Dec 2018 00:38:45 +0100
+
parley (4:17.08.3-1) unstable; urgency=medium
* Team upload.
diff -Nru parley-17.08.3/debian/patches/qt_5.11.patch parley-17.08.3/debian/patches/qt_5.11.patch
--- parley-17.08.3/debian/patches/qt_5.11.patch 1970-01-01 01:00:00.0 +0100
+++ parley-17.08.3/debian/patches/qt_5.11.patch 2018-12-01 00:38:28.0 +0100
@@ -0,0 +1,70 @@
+From f57328e2ba2074bd9e53794525984447d426c38b Mon Sep 17 00:00:00 2001
+From: Andreas Sturmlechner
+Date: Sat, 17 Mar 2018 20:18:04 +0100
+Subject: Fix build with Qt 5.11 (missing headers)
+
+Reviewers: #kde_edu, aacid
+
+Reviewed By: aacid
+
+Tags: #kde_edu
+
+Differential Revision: https://phabricator.kde.org/D11428
+---
+ src/dashboard/buttondelegate.cpp | 1 +
+ src/editor/latexwidget.h | 1 +
+ src/practice/multiplechoicemodewidget.cpp | 1 +
+ src/statistics/statisticsmainwindow.cpp | 1 +
+ 4 files changed, 4 insertions(+)
+
+diff --git a/src/dashboard/buttondelegate.cpp b/src/dashboard/buttondelegate.cpp
+index a99dcc3..315f069 100644
+--- a/src/dashboard/buttondelegate.cpp
b/src/dashboard/buttondelegate.cpp
+@@ -19,6 +19,7 @@
+ #include
+ #include
+ #include
++#include
+ #include
+ #include
+ #include
+diff --git a/src/editor/latexwidget.h b/src/editor/latexwidget.h
+index 0424e43..e3156b0 100644
+--- a/src/editor/latexwidget.h
b/src/editor/latexwidget.h
+@@ -16,6 +16,7 @@
+ #include "ui_latexwidget.h"
+
+ #include
++#include
+ #include
+
+ class QDataWidgetMapper;
+diff --git a/src/practice/multiplechoicemodewidget.cpp b/src/practice/multiplechoicemodewidget.cpp
+index a4eff53..67bd6b5 100644
+--- a/src/practice/multiplechoicemodewidget.cpp
b/src/practice/multiplechoicemodewidget.cpp
+@@ -18,6 +18,7 @@
+
+ #include "ui_practice_widget_multiplechoice.h"
+
++#include
+ #include
+ #include
+ #include
+diff --git a/src/statistics/statisticsmainwindow.cpp b/src/statistics/statisticsmainwindow.cpp
+index 834091c..fe59460 100644
+--- a/src/statistics/statisticsmainwindow.cpp
b/src/statistics/statisticsmainwindow.cpp
+@@ -16,6 +16,7 @@
+
+ #include "statisticsmainwindow.h"
+
++#include
+ #include
+
+ #include
+--
+cgit v0.11.2
+
diff -Nru parley-17.08.3/debian/patches/series parley-17.08.3/debian/patches/series
--- parley-17.08.3/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ parley-17.08.3/debian/patches/series 2018-12-01 00:38:28.0 +0100
@@ -0,0 +1 @@
+qt_5.11.patch
signature.asc
Description: Digital Signature
Processed: Increase severity on #765854 as this is a gapping security problem
Processing commands for cont...@bugs.debian.org: > severity 765854 critical Bug #765854 [ecryptfs-utils] ecryptfs-utils: Private directory not automatically unmounted anymore on logout Severity set to 'critical' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 765854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: facter: diff for NMU version 3.11.0-1.1
Processing control commands:
> tags 906187 + patch
Bug #906187 [facter-dev] facter-dev: missing Depends: libfacter3.11.0 (=
${binary:Version})
Added tag(s) patch.
> tags 906187 + pending
Bug #906187 [facter-dev] facter-dev: missing Depends: libfacter3.11.0 (=
${binary:Version})
Added tag(s) pending.
--
906187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#906187: facter: diff for NMU version 3.11.0-1.1
Control: tags 906187 + patch
Control: tags 906187 + pending
Dear maintainer,
I've prepared an NMU for facter (versioned as 3.11.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`-
diff -Nru facter-3.11.0/debian/changelog facter-3.11.0/debian/changelog
--- facter-3.11.0/debian/changelog 2018-03-29 12:13:41.0 +0200
+++ facter-3.11.0/debian/changelog 2018-12-01 00:19:32.0 +0100
@@ -1,3 +1,12 @@
+facter (3.11.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "missing Depends: libfacter3.11.0 (= ${binary:Version})":
+add the Depends, as suggested by Andreas Beckmann.
+(Closes: #906187)
+
+ -- gregor herrmann Sat, 01 Dec 2018 00:19:32 +0100
+
facter (3.11.0-1) unstable; urgency=medium
* New upstream release
diff -Nru facter-3.11.0/debian/control facter-3.11.0/debian/control
--- facter-3.11.0/debian/control 2018-03-29 12:13:41.0 +0200
+++ facter-3.11.0/debian/control 2018-12-01 00:16:40.0 +0100
@@ -72,7 +72,7 @@
Package: facter-dev
Architecture: any
Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libfacter3.11.0 (= ${binary:Version})
Description: collect and display facts about the system -- development files
Facter is Puppet’s cross-platform system profiling library. It discovers and
reports per-node facts, which are collected by the Puppet agent and are made
signature.asc
Description: Digital Signature
Bug#914051: python-freecontact FTBFS with boost 1.67
Control: tags -1 help On Sun, Nov 18, 2018 at 10:42:22PM +0200, Adrian Bunk wrote: > /usr/bin/ld: cannot find -lboost_python-py27 It seems libboost_python-py*.so is not provided by libboost > 1.63 since these do not provide any libboost-python package any more. I have no idea how to work around this. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#914051: python-freecontact FTBFS with boost 1.67
Processing control commands: > tags -1 help Bug #914051 [src:python-freecontact] python-freecontact FTBFS with boost 1.67 Added tag(s) help. -- 914051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#914049: progressivemauve FTBFS with boost 1.67
Processing control commands: > tags -1 help Bug #914049 [src:progressivemauve] progressivemauve FTBFS with boost 1.67 Added tag(s) help. -- 914049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909383: xemacs21 stale
I think the main problem is that xemacs21 is quite stale, latest upstream release dating back to 2013. Thus it doesn't support (string-to-syntax) Regards Racke -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration. Provisioning with Ansible.
Bug#914049: progressivemauve FTBFS with boost 1.67
Control: tags -1 help
On Sun, Nov 18, 2018 at 10:36:52PM +0200, Adrian Bunk wrote:
> /usr/include/c++/8/bits/stl_vector.h:1074:7: note: candidate: 'void
> std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp =
> boost::tuples::tuple std::allocator >, std::vector std::allocator > >; _Alloc =
> std::allocator int, std::allocator >, std::vector std::allocator > > >; std::vector<_Tp, _Alloc>::value_type
> = boost::tuples::tuple std::allocator >, std::vector std::allocator > >]'
>push_back(const value_type& __x)
>^
> /usr/include/c++/8/bits/stl_vector.h:1074:7: note: no known conversion for
> argument 1 from 'GappedMatchRecord*' to 'const value_type&' {aka 'const
> boost::tuples::tuple std::allocator >, std::vector std::allocator > >&'}
> /usr/include/c++/8/bits/stl_vector.h:1090:7: note: candidate: 'void
> std::vector<_Tp, _Alloc>::push_back(std::vector<_Tp, _Alloc>::value_type&&)
> [with _Tp = boost::tuples::tuple std::allocator >, std::vector std::allocator > >; _Alloc =
> std::allocator int, std::allocator >, std::vector std::allocator > > >; std::vector<_Tp, _Alloc>::value_type
> = boost::tuples::tuple std::allocator >, std::vector std::allocator > >]'
>push_back(value_type&& __x)
>^
Any idea how to replace push_back?
Kind regards
Andreas.
--
http://fam-tille.de
Bug#909383: Fails to install
This even happens on a normal system - looks like it enters an infinite loop: Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Loading 20apel... Loading 50flim... Loading 50w3m-el... Regards from BSP in Bern Racke -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration. Provisioning with Ansible.
Bug#915096: marked as done (libperl-apireference-perl: Missing support for perl 5.28.1)
Your message dated Fri, 30 Nov 2018 22:19:56 + with message-id and subject line Bug#915096: fixed in libperl-apireference-perl 0.22-10 has caused the Debian Bug report #915096, regarding libperl-apireference-perl: Missing support for perl 5.28.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libperl-apireference-perl Version: 0.22-9 Severity: grave Justification: ftbfs This package needs an update for perl 5.28.1, which was uploaded to unstable yesterday. --- End Message --- --- Begin Message --- Source: libperl-apireference-perl Source-Version: 0.22-10 We believe that the bug you reported is fixed in the latest version of libperl-apireference-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libperl-apireference-perl 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: Fri, 30 Nov 2018 22:54:46 CET Source: libperl-apireference-perl Binary: libperl-apireference-perl Architecture: source Version: 0.22-10 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Description: libperl-apireference-perl - Perl module to programmatically query the perlapi Closes: 915096 Changes: libperl-apireference-perl (0.22-10) unstable; urgency=medium . * Add support for perl 5.28.1. (Closes: #915096) * Declare compliance with Debian Policy 4.2.1. * Remove trailing whitespace from debian/*. Checksums-Sha256: f7ffd266d37f08c860f01d6a234b6a17e1bf62522c28baf5a3e3bd4a772c9a00 2511 libperl-apireference-perl_0.22-10.dsc 1618ed8aeead03c32b09af6fedac6ba801d4f39ce22db441558b2868f64579eb 344512 libperl-apireference-perl_0.22-10.debian.tar.xz 554213b7f1242d1fc866624af58cd2b69cf179e4e0053cc175a12cb407042b70 5985 libperl-apireference-perl_0.22-10_sourceonly.buildinfo Checksums-Sha1: 9c2880b5984a03d04ea44dab2934704693ef97a7 2511 libperl-apireference-perl_0.22-10.dsc 74a117b6abbe5b70a970b846b51d843d1bb0f124 344512 libperl-apireference-perl_0.22-10.debian.tar.xz 72d1132760af3039d2a04929cada5afbf349f153 5985 libperl-apireference-perl_0.22-10_sourceonly.buildinfo Files: 0bd76731a866f76ae5ecee1d654e92d5 2511 perl optional libperl-apireference-perl_0.22-10.dsc be1098ff57c1ea5a91c5fb644194a2d7 344512 perl optional libperl-apireference-perl_0.22-10.debian.tar.xz 07708097e374c506854818b118d7a8a7 5985 - - libperl-apireference-perl_0.22-10_sourceonly.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlwBsapfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgb8vQ/+OExi/SFa958nTv9jKU6M/GSN1tdFz2oR5UZ3r4A4P/PXTuh7yFuN3Bvz S+DoTczbkmaMzjkk+T9sPXYevWWXcfrkoo0cWhNHs1DLntghirmseT3SozSRrFsG ssfTkZS0p0foZdovtVR0fJoowR3Emz3zdiKeTxgXznqwHUZuDXkg0w44wY+GM7VK jYhRmyf2h4vUr++ng9XKMzoAWbEH2eRnnCYtDtHFyoxZN6+bENOG/S3/xCRA6OE1 F2xiJ6x/1SG1N840rAc9zhsUcvAmrVC0Ru5uCYRqWuDz7AMNHU2E4fJa81jjQ6dX tsJTXhnqeloiIVQJKmoKB/EOFuxrYiyBAkYgAOsz+wzqzO3yzqxXZS859CpNxyG1 ZY5L6u/fdru5KIFOwwhZ9DXZ7k4QZ2xbXHvjT1Hl7G6Kg7eAygc0EL6AxSXkMlX9 sKuVyzFQmz8s2aGqUNij9DPfqi6DOM+h13MKV4k1U99CcdhWAaBgNAEx1ojVZDrO uJSaG9w2V38Sb0OMB+l/LP3LDyGzhu9zfewC2JBSrdscFg8csRZagYK3LYmhEM70 qhORhxmuD8HLT3KgLgaqi4B7LxuI3c2RorWrJBi5fz637ihAJSrg/3UtyxE15L6B snUKw/vYmhaauA0u1rTXz7dZm0+huTFs/xI9xcEf1aeHY4UVkCg= =qrdR -END PGP SIGNATURE End Message ---
Bug#909814: marked as done (r-cran-afex: autopkgtest regression)
Your message dated Fri, 30 Nov 2018 21:36:34 +
with message-id
and subject line Bug#909814: fixed in r-cran-afex 0.22-1-2
has caused the Debian Bug report #909814,
regarding r-cran-afex: autopkgtest regression
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.)
--
909814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-afex
Version: 0.22-1-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of r-cran-afex the autopkgtest of r-cran-afex fails
in testing when that autopkgtest is run with the binary packages of
r-cran-afex from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
r-cran-afexfrom testing0.22-1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. Is this bug
898441 [0] over again?
Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/898441
[1] https://qa.debian.org/excuses.php?package=r-cran-afex
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-afex/1070145/log.gz
autopkgtest [04:33:46]: test run-unit-test: [---
Loading required package: lme4
Loading required package: Matrix
Welcome to afex. For support visit: http://afex.singmann.science/
- Functions for ANOVAs: aov_car(), aov_ez(), and aov_4()
- Methods for calculating p-values with mixed(): 'KR', 'S', 'LRT', and 'PB'
- 'afex_aov' and 'mixed' objects can be passed to emmeans() for
follow-up tests
- NEWS: library('emmeans') now needs to be called explicitly!
- Get and set global package options with: afex_options()
- Set orthogonal sum-to-zero contrasts globally: set_sum_contrasts()
- For example analyses see: browseVignettes("afex")
Attaching package: 'afex'
The following object is masked from 'package:lme4':
lmer
Error: testthat unit tests failed
Execution halted
autopkgtest [04:34:58]: test run-unit-test: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-afex
Source-Version: 0.22-1-2
We believe that the bug you reported is fixed in the latest version of
r-cran-afex, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dylan Aïssi (supplier of updated r-cran-afex 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: Fri, 30 Nov 2018 21:43:02 +0100
Source: r-cran-afex
Binary: r-cran-afex
Architecture: source
Version: 0.22-1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Dylan Aïssi
Description:
r-cran-afex - GNU R package for analyzing factorial experiments using ANOVA or
Closes: 909814
Changes:
r-cran-afex (0.22-1-2) unstable; urgency=medium
.
* Team upload.
* Fix autopkgtest (Closes: #909814)
Checksums-Sha1:
c0f41faacf60b5f855d549b2bf68d2bcdfdc8090 2104 r-cran-afex_0.22-1-2.dsc
d3aa5042d7b599b59bfcd6bfd3df2b1b86fe8f76 5384
r-cran-afex_0.22-1-2.debian.tar.xz
1ff36adf9ec25fbf6b9bded0fd538b6cbf6f6793 11132
r-cran-afex_0.22-1-2_amd64.buildinfo
Checksums-Sha256:
71a5c50187d161857874dea0bd25a3619f841731fad76017827fa8a35e8ab6d8 2104
r-cran-afex_0.22-1-2.dsc
110e4de68f8a97b683ad164a61d5edf470f55731ccc5119b65c341c3807e7a0d 5384
r-cran-afex_0.22-1-2.debian.tar.xz
99eb3f5291d3f3fe25e710dc21de863f90b55806fb00e259410ab15b90b948b9 11132
r-cran-afex_0.22-1-2_amd64.buildinfo
Files:
e51678480cfd8a14f91eba742e261c48 2104 gnu-r optional r-cran-afex_0.22-1-2.dsc
8aaba983a8dd9f539ea359f9bc403d54 5384 gnu-r optional
r-cran-afex_0.22-1-2.debian.tar.xz
Processed: tagging 915128
Processing commands for cont...@bugs.debian.org: > tags 915128 + buster sid Bug #915128 [src:swftools] Dont't include in buster Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 915128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 915129
Processing commands for cont...@bugs.debian.org: > tags 915129 + buster sid Bug #915129 [src:jquery-jplayer] Stop using swftools Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 915129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 915128 with 915129
Processing commands for cont...@bugs.debian.org: > block 915128 with 915129 Bug #915128 [src:swftools] Dont't include in buster 915128 was not blocked by any bugs. 915128 was not blocking any bugs. Added blocking bug(s) of 915128: 915129 > thanks Stopping processing here. Please contact me if you need assistance. -- 915128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914393: marked as done (keepalived: CVE-2018-19115 heap-based buffer overflow and DoS)
Your message dated Fri, 30 Nov 2018 20:59:40 + with message-id and subject line Bug#914393: fixed in keepalived 1:2.0.10-1 has caused the Debian Bug report #914393, regarding keepalived: CVE-2018-19115 heap-based buffer overflow and DoS 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.) -- 914393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keepalived X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for keepalived. CVE-2018-19115[0]: | keepalived before 2.0.7 has a heap-based buffer overflow when parsing | HTTP status codes resulting in DoS or possibly unspecified other | impact, because extract_status_code in lib/html.c has no validation of | the status code and instead writes an unlimited amount of data to the | heap. 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-19115 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19115 Please adjust the affected versions in the BTS as needed. Regards, Markus signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: keepalived Source-Version: 1:2.0.10-1 We believe that the bug you reported is fixed in the latest version of keepalived, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Wirt (supplier of updated keepalived 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: Fri, 30 Nov 2018 21:20:05 +0100 Source: keepalived Binary: keepalived Architecture: source Version: 1:2.0.10-1 Distribution: unstable Urgency: high Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: keepalived - Failover and monitoring daemon for LVS clusters Closes: 810347 830196 900260 902978 909697 914393 Changes: keepalived (1:2.0.10-1) unstable; urgency=high . * [3b99bf9] Update vcs headers to salsa * [f697779] New upstream version 2.0.2 * [c97cc19] Enable dbus instance and json output support * [27c6d55] syslog is now socket activated * [7e2267b] Move to dh11 * [d0bf9db] there is not systemd sequence in dh11 * [903a5a0] dh-autoreconf dep is not needed anymore with dh11 * [c4996bd] Priority extra got replaced by optional * [822da17] Remove obsolete patches * [1c36cdc] New upstream version 2.0.10 - Fix overflow in extract_status_code (CVE-2018-19115) Closes: #914393, #900260 - Improve garp refresh handling (Closes: #810347) - Improve config parser (Closes: #909697) * [990c014] Improve keepalived service (Closes: #902978, #830196) Checksums-Sha1: c611f5fb693d49f2aaac1ef1d6d7ebdfcd56b314 2054 keepalived_2.0.10-1.dsc c0b62f6d20a4a322e4bd67b4ae447bb842c28c4c 927631 keepalived_2.0.10.orig.tar.gz 5e3bc91f4bcbb39067e8a4283c82cb14f09896ba 10124 keepalived_2.0.10-1.debian.tar.xz ec9e27ed8ea868d1e35118fb6a81027cc4a0f6e8 7638 keepalived_2.0.10-1_amd64.buildinfo Checksums-Sha256: e9b03181b770cee745d6b27e9827b20d1e241b73cd8193d50d872bafa09006ba 2054 keepalived_2.0.10-1.dsc 40e0e55afed9ca313d621a9c5878579696fafb5504dab521aadaf20ba6e7f597 927631 keepalived_2.0.10.orig.tar.gz 882e4d76ec1dea0aa865f092956ced5be0950e419681700ad70162635d230c05 10124 keepalived_2.0.10-1.debian.tar.xz dfc65817bd9ead59fee18bf0adfa37b75e7fb024b4c7b4985cb1ad1d4762a0d9 7638 keepalived_2.0.10-1_amd64.buildinfo Files: ffc64cfd50834d6025f571617ff7131d 2054 admin optional keepalived_2.0.10-1.dsc ac93d7eb5b69a9fbf7494fcf27b39ccf 927631 admin optional keepalived_2.0.10.orig.tar.gz 5196b8fba5962d72eda10925c88c7f36 10124 admin optional keepalived_2.0.10-1.debian.tar.xz aef5c84d1e23a54ea8887639aba7aa2e 7638 admin optional keepalived_2.0.10-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbjlmweHRXblz0FtJHkX4yp3iOxYFAlwBnx8ACgkQHkX4yp3i
Bug#914742: zeroc-ice ftbfs in unstable with Python 3.7
That is already fixed upstream in https://github.com/zeroc-ice/ice/commit/4aea9fc787892842af17d119332a7f6fef2f35c4 I will upload a patch On Mon, Nov 26, 2018 at 10:15 PM Matthias Klose wrote: > Package: src:zeroc-ice > Version: 3.7.1-5 > Severity: serious > Tags: sid buster patch > > zeroc-ice ftbfs in unstable with Python 3.7 > > x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -MT > modules/IcePy/build/x86_64-linux-gnu/shared/pic/Proxy.o -MMD -MP -MF > modules/IcePy/build/x86_64-linux-gnu/shared/pic/Proxy.Td -Wall -Wdeprecated > -Werror -pthread -DNDEBUG -Imodules/IcePy -I../cpp/include > -I../cpp/include/generated -I../cpp/src -I/usr/include/python3.7m > -I/usr/include/python3.7m -Wno-unused-result -Wsign-compare -g > -fdebug-prefix-map=/build/python3.7-0HyDJv/python3.7-3.7.1=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector -Wformat > -Werror=format-security -DNDEBUG -g -fwrapv -O3 -Wall -fPIC > -fvisibility=hidden > -Wdate-time -D_FORTIFY_SOURCE=2 -c modules/IcePy/Proxy.cpp -o > modules/IcePy/build/x86_64-linux-gnu/shared/pic/Proxy.o > modules/IcePy/Communicator.cpp: In function ‘PyObject* > communicatorWaitForShutdown(IcePy::CommunicatorObject*, PyObject*)’: > modules/IcePy/Communicator.cpp:475:36: error: comparison of integer > expressions > of different signedness: ‘long unsigned int’ and ‘long int’ > [-Werror=sign-compare] > if(PyThread_get_thread_ident() == _mainThreadId) > ^~~~ > cc1plus: all warnings being treated as errors > make[2]: *** [Makefile:41: > modules/IcePy/build/x86_64-linux-gnu/shared/pic/Communicator.o] Error 1 > make[2]: *** Waiting for unfinished jobs > > > work around patch available at > https://patches.ubuntu.com/z/zeroc-ice/zeroc-ice_3.7.1-5ubuntu1.patch > -- José Gutiérrez de la Concha ZeroC, Inc.
Bug#915007: opensaml2 FTBFS with xmltooling 3
Don't wait for me on shibboleth-resolver or moonshot-gss-eap to file the removal requests. They are both basically broken in unstable, so there's no reason to block.
Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default
On Fri, 2018-11-30 at 19:40 +0100, Didier 'OdyX' Raboud wrote: > Dear Hideki, dear src:debootstrap maintainers, > > tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by > default now, or are you OK letting the TC decide on this subject? There were discussions about enabling this by default years ago, I don't think minor issues should be a reason to delay this change. Note that it has been delayed for after the stretch release as there were major issues back then (it was enabled by default for a short time in stretch). It took >5 months for someone to find a problem this time which is pretty good for any change. Ansgar
Bug#915134: exiv2: CVE-2018-19607
Source: exiv2 Version: 0.26-1 Severity: grave Tags: patch security upstream Justification: user security hole Forwarded: https://github.com/Exiv2/exiv2/issues/561 Hi, The following vulnerability was published for exiv2, it only affects experimental (thus filling as RC severity so does not enter unstable) CVE-2018-19607[0]: | Exiv2::isoSpeed in easyaccess.cpp in Exiv2 v0.27-RC2 allows remote | attackers to cause a denial of service (NULL pointer dereference and | application crash) via a crafted file. 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-19607 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19607 [1] https://github.com/Exiv2/exiv2/issues/561 Regards, Salvatore
Bug#914355: [Pkg-electronics-devel] Bug#914355: gnucap-python: FTBFS (dh_auto_configure fails)
On Thu, Nov 22, 2018 at 04:35:20PM +, Santiago Vila wrote: > Package: src:gnucap-python > Version: 0.0.0-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package but it failed: Thank you. there's a new package for the 0.0.1 release [1]. the build issue caused by incomplete python dependencies is fixed. this was one reason for 914355. i checked with cowbuilder for amd64 and i386. on i386, only the tests fail due to numerical noise. please advise if that can wait until 0.0.2, ETA unknown. (i don't think there is a use case for gnucap on i386..) regards felix [1] https://salsa.debian.org/electronics-team/Gnucap/gnucap-python
Bug#915129: Stop using swftools
Source: jquery-jplayer Severity: serious jquery-jplayer currently depends on swftools for Flash support. swftools however is orphaned, has frequent security issues, is dead upstream (as is Flash). Also, per the package description Flash is entirely a fallback for browsers which don't support HTML5 video (but those are the norm today). Cheers, Moritz
Bug#915128: Dont't include in buster
Source: swftools Severity: serious swftools is orphaned for a year, dead upstream and has frequent security issues. Also, Flash is a thing of the past, so let's drop it from buster (initially filing this bug to out it out of testing, will also sort out the removal, which will take longer). One one rev dep is left in testing (jquery-jplayer), I'll file a separate bug against it. Cheers, Moritz
Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default
Dear Hideki, dear src:debootstrap maintainers, tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by default now, or are you OK letting the TC decide on this subject? Longer version: As you might be aware, #914897 (initially filed on src:debootstrap) has now been reassigned to the Technical Committee. As, formally, the Maintainer of src:debootstrap is "debian-boot@l.d.o and the current Uploaders", I would like to make sure that the TC is not going to overrule unnecessarily. Hideki, if I read the debootstrap history correctly, you enabled "merged /usr" by default in debootstrap 1.0.102. Given the recent discussion in debian- devel@ (starting at [0]) and on #914897, could you (or anyone speaking as with a "debootstrap maintainer" hat on) state if, either of: * you would be willing to toggle the "merged /usr" default in debootstrap in a subsequent upload; * you maintain that the "merged /usr" default (to yes) is here to stay. Many thanks in advance for your consideration, OdyX [0] https://lists.debian.org/debian-devel/2018/11/msg00354.html P.S. I'm aware that this might sound formal, or dismissive of Julien's statements. I just _really_ don't want the TC to eventually overrule "the debootstrap maintainers" without need.
Processed: severity of 835590 is serious
Processing commands for cont...@bugs.debian.org: > severity 835590 serious Bug #835590 [libsoundio1] libsoundio1: Missing hard dependency on libjack-jackd2-0 Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 835590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912461: marked as done (jaxb: FTBFS with Java 11 due to javax.activation removal)
Your message dated Fri, 30 Nov 2018 18:21:26 + with message-id and subject line Bug#912461: fixed in jaxb 2.3.0.1-6 has caused the Debian Bug report #912461, regarding jaxb: FTBFS with Java 11 due to javax.activation removal 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.) -- 912461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jaxb Version: 2.3.0.1-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jaxb.html ... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 18.186 s [INFO] Finished at: 2018-10-31T07:37:00-12:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project jaxb-core: Compilation failure: Compilation failure: [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/model/core/PropertyInfo.java:[45,23] error: package javax.activation does not exist [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/model/core/PropertyInfo.java:[143,4] error: cannot find symbol [ERROR] symbol: class MimeType [ERROR] location: interface PropertyInfo [ERROR] where T,C are type-variables: [ERROR] T extends Object declared in interface PropertyInfo [ERROR] C extends Object declared in interface PropertyInfo [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[44,23] error: package javax.activation does not exist [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[51,60] error: cannot find symbol [ERROR] symbol: class DataHandler [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[53,11] error: cannot find symbol [ERROR] symbol: class DataHandler [ERROR] location: class SwaRefAdapterMarker [ERROR] /build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[57,26] error: cannot find symbol [ERROR] symbol: class DataHandler [ERROR] location: class SwaRefAdapterMarker [ERROR] -> [Help 1] [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. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :jaxb-core dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/jaxb-2.3.0.1 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/1st/jaxb-2.3.0.1/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jaxb-2.3.0.1/debian -Dmaven.repo.local=/build/1st/jaxb-2.3.0.1/debian/maven-repo --batch-mode -f jaxb-ri/pom.xml package javadoc:aggregate -DskipTests -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: jaxb Source-Version: 2.3.0.1-6 We believe that the bug you reported is fixed in the latest version of jaxb, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated jaxb 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: Fri, 30 Nov 2018 18:59:21 +0100 Source: jaxb Binary: libjaxb-java
Processed: Bug #912461 in jaxb marked as pending
Processing control commands: > tag -1 pending Bug #912461 [src:jaxb] jaxb: FTBFS with Java 11 due to javax.activation removal Added tag(s) pending. -- 912461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912461: Bug #912461 in jaxb marked as pending
Control: tag -1 pending Hello, Bug #912461 in jaxb 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/java-team/jaxb/commit/3acccaec4959c8848a1cf5abeebe0db4bd661353 Fixed the build failure with Java 11 (Closes: #912461) (this message was generated automatically) -- Greetings https://bugs.debian.org/912461
Bug#914332: Debian Bug report logs #914377 - python3: syntax error in rtupdate hook prevents configuration
Pyzo is not compatible with Python-3.7 because using of the reserved word 'async. See also Pyzo on github: https://github.com/pyzo/pyzo/issues/529 Seems to be fixed in Pyzo 4.6.0 and 4.6.1. This bug should be linked to https://bugs.debian.org/914332 Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpDIfkNxRVW3.pgp Description: PGP signature
Processed: tagging 913014
Processing commands for cont...@bugs.debian.org: > tags 913014 + buster sid Bug #913014 [e3] e3 (all binaries): immediate segmentation fault Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 913014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913709: marked as done (boost1.67: intermitent FTBFS on mips64el: build hangs)
Your message dated Fri, 30 Nov 2018 17:34:38 + with message-id and subject line Bug#913709: fixed in boost1.67 1.67.0-11 has caused the Debian Bug report #913709, regarding boost1.67: intermitent FTBFS on mips64el: build 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.) -- 913709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost1.67 Version: 1.67.0-9 Severity: serious Hi, Your package fails to build quite often on mips64el, where the build gets killed due to inactivity: Cannot find class named 'action' Cannot find class named 'action' Cannot find class named 'file-target' Cannot find class named 'generator' Cannot find class named 'generator' Cannot find class named 'std::bad_cast' E: Build killed with signal TERM after 150 minutes of inactivity This may be due to an actual hang, or something just taking so long that causes the build to get killed. Cheers, Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: boost1.67 Source-Version: 1.67.0-11 We believe that the bug you reported is fixed in the latest version of boost1.67, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Giovanni Mascellani (supplier of updated boost1.67 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: Fri, 30 Nov 2018 18:12:49 +0100 Source: boost1.67 Binary: libboost1.67-dev libboost1.67-tools-dev libboost1.67-all-dev libboost1.67-doc libboost-atomic1.67.0 libboost-atomic1.67-dev libboost-chrono1.67.0 libboost-chrono1.67-dev libboost-container1.67.0 libboost-container1.67-dev libboost-context1.67.0 libboost-context1.67-dev libboost-contract1.67.0 libboost-contract1.67-dev libboost-coroutine1.67.0 libboost-coroutine1.67-dev libboost-date-time1.67.0 libboost-date-time1.67-dev libboost-exception1.67-dev libboost-fiber1.67.0 libboost-fiber1.67-dev libboost-filesystem1.67.0 libboost-filesystem1.67-dev libboost-graph1.67.0 libboost-graph1.67-dev libboost-graph-parallel1.67.0 libboost-graph-parallel1.67-dev libboost-iostreams1.67.0 libboost-iostreams1.67-dev libboost-locale1.67.0 libboost-locale1.67-dev libboost-log1.67.0 libboost-log1.67-dev libboost-math1.67.0 libboost-math1.67-dev libboost-mpi1.67.0 libboost-mpi1.67-dev libboost-mpi-python1.67.0 libboost-mpi-python1.67-dev libboost-numpy1.67.0 libboost-numpy1.67-dev libboost-program-options1.67.0 libboost-program-options1.67-dev libboost-python1.67.0 libboost-python1.67-dev libboost-random1.67.0 libboost-random1.67-dev libboost-regex1.67.0 libboost-regex1.67-dev libboost-serialization1.67.0 libboost-serialization1.67-dev libboost-signals1.67.0 libboost-signals1.67-dev libboost-stacktrace1.67.0 libboost-stacktrace1.67-dev libboost-system1.67.0 libboost-system1.67-dev libboost-test1.67.0 libboost-test1.67-dev libboost-thread1.67.0 libboost-thread1.67-dev libboost-timer1.67.0 libboost-timer1.67-dev libboost-type-erasure1.67.0 libboost-type-erasure1.67-dev libboost-wave1.67.0 libboost-wave1.67-dev Architecture: source Version: 1.67.0-11 Distribution: unstable Urgency: medium Maintainer: Debian Boost Team Changed-By: Giovanni Mascellani Description: libboost-atomic1.67-dev - atomic data types, operations, and memory ordering constraints libboost-atomic1.67.0 - atomic data types, operations, and memory ordering constraints libboost-chrono1.67-dev - C++ representation of time duration, time point, and clocks libboost-chrono1.67.0 - C++ representation of time duration, time point, and clocks
Bug#914688: marked as done ("boost: please do not use __linux macro")
Your message dated Fri, 30 Nov 2018 17:34:38 +
with message-id
and subject line Bug#914688: fixed in boost1.67 1.67.0-11
has caused the Debian Bug report #914688,
regarding "boost: please do not use __linux macro"
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.)
--
914688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-8
Version: 8.2.0-10
Severity: serious
Affects: src:performous
Hello, after trying to debug why src:performous was FTBFS on ppc64el, I got
this issue:
test example reproducing the issue:
cat test.c++
#include
#include
#if BOOST_OS_LINUX
#warning "OS LINUX DEFINED"
#endif
int main()
{
printf("%d\n", BOOST_OS_WINDOWS);
printf("%d\n", BOOST_OS_LINUX);
}
apt-get install libboost-dev
on an amd64 machine this happens:
$ g++ test.c++
test.c++:5:2: warning: #warning "OS LINUX DEFINED" [-Wcpp]
#warning "OS LINUX DEFINED"
^~~
$ g++ test.c++ -std=c++14
test.c++:5:2: warning: #warning "OS LINUX DEFINED" [-Wcpp]
#warning "OS LINUX DEFINED"
^~~
(everything is ok)
on a ppc64el machine this happens instead:
g++ test.c++
test.c++:5:2: warning: #warning "OS LINUX DEFINED" [-Wcpp]
#warning "OS LINUX DEFINED"
^~~
g++ test.c++ -std=c++14
(NO WARNINGS HERE).
this is why the package FTBFS, because that macro is not defined when std is
defined.
Any idea?
(this might be a boost issue, but I can't prove it!)
same happens with old g++-7, and with c++0x or c++11
G.
--- End Message ---
--- Begin Message ---
Source: boost1.67
Source-Version: 1.67.0-11
We believe that the bug you reported is fixed in the latest version of
boost1.67, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Giovanni Mascellani (supplier of updated boost1.67 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: Fri, 30 Nov 2018 18:12:49 +0100
Source: boost1.67
Binary: libboost1.67-dev libboost1.67-tools-dev libboost1.67-all-dev
libboost1.67-doc libboost-atomic1.67.0 libboost-atomic1.67-dev
libboost-chrono1.67.0 libboost-chrono1.67-dev libboost-container1.67.0
libboost-container1.67-dev libboost-context1.67.0 libboost-context1.67-dev
libboost-contract1.67.0 libboost-contract1.67-dev libboost-coroutine1.67.0
libboost-coroutine1.67-dev libboost-date-time1.67.0 libboost-date-time1.67-dev
libboost-exception1.67-dev libboost-fiber1.67.0 libboost-fiber1.67-dev
libboost-filesystem1.67.0 libboost-filesystem1.67-dev libboost-graph1.67.0
libboost-graph1.67-dev libboost-graph-parallel1.67.0
libboost-graph-parallel1.67-dev libboost-iostreams1.67.0
libboost-iostreams1.67-dev libboost-locale1.67.0 libboost-locale1.67-dev
libboost-log1.67.0 libboost-log1.67-dev libboost-math1.67.0
libboost-math1.67-dev libboost-mpi1.67.0 libboost-mpi1.67-dev
libboost-mpi-python1.67.0 libboost-mpi-python1.67-dev libboost-numpy1.67.0
libboost-numpy1.67-dev
libboost-program-options1.67.0 libboost-program-options1.67-dev
libboost-python1.67.0 libboost-python1.67-dev libboost-random1.67.0
libboost-random1.67-dev libboost-regex1.67.0 libboost-regex1.67-dev
libboost-serialization1.67.0 libboost-serialization1.67-dev
libboost-signals1.67.0 libboost-signals1.67-dev libboost-stacktrace1.67.0
libboost-stacktrace1.67-dev libboost-system1.67.0 libboost-system1.67-dev
libboost-test1.67.0 libboost-test1.67-dev libboost-thread1.67.0
libboost-thread1.67-dev libboost-timer1.67.0 libboost-timer1.67-dev
libboost-type-erasure1.67.0 libboost-type-erasure1.67-dev libboost-wave1.67.0
libboost-wave1.67-dev
Architecture: source
Version: 1.67.0-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team
Changed-By: Giovanni Mascellani
Description:
libboost-atomic1.67-dev - atomic data types, operations, and memory ordering
constraints
libboost-atomic1.67.0 - atomic data types, operations, and memory ordering
constraints
libboost-chrono1.67-dev - C++ representation of time duration, time point, and
clocks
libboost-chrono1.67.0 - C++ representation of time duration, time
Bug#915120: shibboleth-sp2 FTBFS with xmltooling 3.0.2
Source: shibboleth-sp2
Version: 2.6.1+dfsg1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=shibboleth-sp2=sid
...
SPConfig.cpp: In member function 'virtual bool
shibsp::SPConfig::instantiate(const char*, bool)':
SPConfig.cpp:427:117: error: no matching function for call to
'xmltooling::PluginManager, const
xercesc_3_2::DOMElement*>::newPlugin(const char [4], xercesc_3_2::DOMElement*)'
setServiceProvider(ServiceProviderManager.newPlugin(XML_SERVICE_PROVIDER,
dummydoc->getDocumentElement()));
^
In file included from SPConfig.h:38,
from internal.h:48,
from SPConfig.cpp:27:
/usr/include/xmltooling/PluginManager.h:97:12: note: candidate: 'T*
xmltooling::PluginManager::newPlugin(const Key&, const Params&,
bool) const [with T = shibsp::ServiceProvider; Key =
std::__cxx11::basic_string; Params = const xercesc_3_2::DOMElement*]'
T* newPlugin(const Key& type, const Params& p, bool
deprecationSupport) const {
^
/usr/include/xmltooling/PluginManager.h:97:12: note: candidate expects 3
arguments, 2 provided
SPConfig.cpp:439:111: error: no matching function for call to
'xmltooling::PluginManager, const
xercesc_3_2::DOMElement*>::newPlugin(const char*, xercesc_3_2::DOMElement*)'
setServiceProvider(ServiceProviderManager.newPlugin(type.get(),
dummydoc->getDocumentElement()));
^
In file included from SPConfig.h:38,
from internal.h:48,
from SPConfig.cpp:27:
/usr/include/xmltooling/PluginManager.h:97:12: note: candidate: 'T*
xmltooling::PluginManager::newPlugin(const Key&, const Params&,
bool) const [with T = shibsp::ServiceProvider; Key =
std::__cxx11::basic_string; Params = const xercesc_3_2::DOMElement*]'
T* newPlugin(const Key& type, const Params& p, bool
deprecationSupport) const {
^
/usr/include/xmltooling/PluginManager.h:97:12: note: candidate expects 3
arguments, 2 provided
make[4]: *** [Makefile:2355: libshibsp_la-SPConfig.lo] Error 1
Processed: severity of 890086 is grave
Processing commands for cont...@bugs.debian.org: > severity 890086 grave Bug #890086 [ufraw-batch] ufraw: CVE-2018-19655: stack buffer overflow while running ufraw-batch Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 890086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
On Fri, 30 Nov 2018 18:01:26 +0200 Jan Groenewald wrote: > There is https://packages.gitlab.com/gitlab/gitlab-ce > > (deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ stretch main) Sorry, but no. Just no, no, no and no. Those binary dumps are horrible. They are essentially just dumping 2/3 of an outdated(*) Linux system to /opt. Pirate Praveen is doing an awesome job of packaging this very complex piece of software in a proper way and I at least am very grateful for this. Even if it is only available in unstable, it's a lot better than those blobs provided upstream. Cheers, sur5r (*) - Postgres 9.6 - openSSL 1.0.0 (??!) - Python 3.4 ... the list goes on
Processed: ruby-sham-rack: diff for NMU version 1.4.1-1.1
Processing control commands: > tags 903190 + patch Bug #903190 [src:ruby-sham-rack] ruby-sham-rack: FTBFS in buster/sid (dh_installdocs: Cannot find "README.markdown") Added tag(s) patch. > tags 903190 + pending Bug #903190 [src:ruby-sham-rack] ruby-sham-rack: FTBFS in buster/sid (dh_installdocs: Cannot find "README.markdown") Added tag(s) pending. -- 903190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903190: ruby-sham-rack: diff for NMU version 1.4.1-1.1
Control: tags 903190 + patch Control: tags 903190 + pending Dear maintainer, I've prepared an NMU for ruby-sham-rack (versioned as 1.4.1-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru ruby-sham-rack-1.4.1/debian/changelog ruby-sham-rack-1.4.1/debian/changelog --- ruby-sham-rack-1.4.1/debian/changelog 2017-08-20 19:19:03.0 +0300 +++ ruby-sham-rack-1.4.1/debian/changelog 2018-11-30 18:12:36.0 +0200 @@ -1,3 +1,11 @@ +ruby-sham-rack (1.4.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS by no longer trying to install +a nonexisting README.markdown. (Closes: #903190) + + -- Adrian Bunk Fri, 30 Nov 2018 18:12:36 +0200 + ruby-sham-rack (1.4.1-1) unstable; urgency=medium * New upstream release (Closes: #868750) diff -Nru ruby-sham-rack-1.4.1/debian/ruby-sham-rack.docs ruby-sham-rack-1.4.1/debian/ruby-sham-rack.docs --- ruby-sham-rack-1.4.1/debian/ruby-sham-rack.docs 2017-08-20 19:19:03.0 +0300 +++ ruby-sham-rack-1.4.1/debian/ruby-sham-rack.docs 1970-01-01 02:00:00.0 +0200 @@ -1 +0,0 @@ -README.markdown
Bug#915112: glew: conflicting definitions in glext.h and glew.h cause pymol to FTBFS
Source: glew Version: 2.1.0-2 Severity: serious Control: affects -1 + src:pymol Hi, I just noticed that pymol stated to FTBFS, this seems to be caused by glew (which was updated recently, while libglvnd hasn't seen changes for some time): In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, const GLfloat *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, GLfloat* params); ^~~~ In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12068:103: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, const GLint*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, const GLint *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18736:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, GLint*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, GLint* params); ^~~~ and so on... Full log attached. This happens with both pymol in sid and experimental. Andreas pymol_2.2.0+dfsg-2.log.gz Description: application/gzip
Processed: glew: conflicting definitions in glext.h and glew.h cause pymol to FTBFS
Processing control commands: > affects -1 + src:pymol Bug #915112 [src:glew] glew: conflicting definitions in glext.h and glew.h cause pymol to FTBFS Added indication that 915112 affects src:pymol -- 915112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
Hi On Fri, 30 Nov 2018 at 16:43, Holger Levsen wrote: > On Fri, Nov 30, 2018 at 07:39:20PM +0530, Pirate Praveen wrote: > > >Backports are *always* from testing because a backport is > > >supposed to be replaced by the regular stable version of > > >the subsequent release. > > That is indeed the current definition. > > Me too is very happy with it. > > > Another option could be to have personal package archive for gitlab. > > That. And if you don't want to wait until they arrive in Debian proper, > I'd suggest you'd host such an archive yourself. > There is https://packages.gitlab.com/gitlab/gitlab-ce (deb https://packages.gitlab.com/gitlab/gitlab-ce/debian/ stretch main) Regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^
Processed: tagging 839161
Processing commands for cont...@bugs.debian.org: > tags 839161 + buster sid Bug #839161 [crrcsim] crrcsim: FTBFS on several architectures Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 839161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#912099: gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2
Processing control commands: > reassign -1 itstool 2.0.4-2 Bug #912099 [src:gnumeric] gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2 Bug reassigned from package 'src:gnumeric' to 'itstool'. No longer marked as found in versions gnumeric/1.12.43-1. Ignoring request to alter fixed versions of bug #912099 to the same values previously set Bug #912099 [itstool] gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2 Marked as found in versions itstool/2.0.4-2. > forwarded -1 https://github.com/itstool/itstool/issues/22 Bug #912099 [itstool] gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2 Changed Bug forwarded-to-address to 'https://github.com/itstool/itstool/issues/22' from 'https://gitlab.gnome.org/GNOME/gnumeric/issues/331'. > affects -1 src:gnumeric Bug #912099 [itstool] gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2 Added indication that 912099 affects src:gnumeric -- 912099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912099: gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2
Control: reassign -1 itstool 2.0.4-2
Control: forwarded -1 https://github.com/itstool/itstool/issues/22
Control: affects -1 src:gnumeric
On Sun, Oct 28, 2018 at 11:05:47AM +0200, Niko Tyni wrote:
> Source: gnumeric
> Version: 1.12.43-1
> Severity: serious
> Tags: ftbfs
> Control: block 902557 with -1
> X-Debbugs-Cc: itst...@packages.debian.org
>
> As seen at
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnumeric.html
>
> gnumeric fails to build on current sid/amd64. It seems to have broken
> with itstool 2.0.4 in early October or so. From the build log:
>
> if test -f "${mo}"; then mo="../${mo}"; else
> mo="/build/1st/gnumeric-1.12.43/doc/${mo}"; fi; \
> (cd "cs/" && itstool -m "${mo}" ${d}/C/gnumeric.xml) && \
> touch "cs/cs.stamp"
> Warning: Could not merge cs translation for msgid:
> The chapters of this version of the Gnumeric
> manual are organized as follows: <_:itemizedlist-1/>
> [...]
> Error: Could not merge translations:
> 'ascii' codec can't decode byte 0xc2 in position 97: ordinal not in
> range(128)
> make[3]: *** [Makefile:1414: cs/cs.stamp] Error 1
>
> This seems to be the same issue as
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1604169
>
> https://github.com/itstool/itstool/issues/22
>
> https://gitlab.gnome.org/GNOME/gnumeric/issues/331
The agrrement seems to be that this is a regression in itstool and
should be fixed there.
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#914332: pyzo: diff for NMU version 4.4.3-1.1
Control: tags 914332 + pending Dear maintainer, I've prepared an NMU for pyzo (versioned as 4.4.3-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru pyzo-4.4.3/debian/changelog pyzo-4.4.3/debian/changelog --- pyzo-4.4.3/debian/changelog 2017-10-09 21:59:11.0 +0300 +++ pyzo-4.4.3/debian/changelog 2018-11-30 17:17:18.0 +0200 @@ -1,3 +1,11 @@ +pyzo (4.4.3-1.1) unstable; urgency=high + + * Non-maintainer upload. + * Add upstream patch to fix installation with Python 3.7. +(Closes: #914332) + + -- Adrian Bunk Fri, 30 Nov 2018 17:17:18 +0200 + pyzo (4.4.3-1) unstable; urgency=medium * Add recommended get-orig-source target diff -Nru pyzo-4.4.3/debian/patches/0001-replace-async-per-basync-to-become-Python-3.7-compat.patch pyzo-4.4.3/debian/patches/0001-replace-async-per-basync-to-become-Python-3.7-compat.patch --- pyzo-4.4.3/debian/patches/0001-replace-async-per-basync-to-become-Python-3.7-compat.patch 1970-01-01 02:00:00.0 +0200 +++ pyzo-4.4.3/debian/patches/0001-replace-async-per-basync-to-become-Python-3.7-compat.patch 2018-11-30 17:16:51.0 +0200 @@ -0,0 +1,52 @@ +From 8a3ef256b17076a9d1a7d0a356806a2166a1ee3c Mon Sep 17 00:00:00 2001 +From: stonebig +Date: Mon, 5 Mar 2018 22:29:06 +0100 +Subject: [PATCH] replace async per basync to become Python-3.7 compatible + (#530) + +* repalce async per basync to become Python-3.7 compatible + +* move to async_val like ansible project +--- + pyzo/yoton/clientserver.py | 8 + 1 file changed, 4 insertions(+), 4 deletions(-) + +diff --git a/pyzo/yoton/clientserver.py b/pyzo/yoton/clientserver.py +index 6802db2..cd54454 100644 +--- a/pyzo/yoton/clientserver.py b/pyzo/yoton/clientserver.py +@@ -43,7 +43,7 @@ from yoton.core import send_all, recv_all + + + class RequestServer(threading.Thread): +-""" RequestServer(address, async=False, verbose=0) ++""" RequestServer(address, async_val=False, verbose=0) + + Setup a simple server that handles requests similar to a telnet server, + or asyncore. Starting the server using run() will run the server in +@@ -58,7 +58,7 @@ class RequestServer(threading.Thread): + -- + address : str + Should be of the shape hostname:port. +-async : bool ++async_val : bool + If True, handles each incoming connection in a separate thread. + This might be advantageous if a the handle_request() method + takes a long time to execute. +@@ -78,11 +78,11 @@ class RequestServer(threading.Thread): + + """ + +-def __init__(self, address, async=False, verbose=0): ++def __init__(self, address, async_val=False, verbose=0): + threading.Thread.__init__(self) + + # Store whether to handle requests asynchronously +-self._async = async ++self._async = async_val + + # Verbosity + self._verbose = verbose +-- +2.11.0 + diff -Nru pyzo-4.4.3/debian/patches/series pyzo-4.4.3/debian/patches/series --- pyzo-4.4.3/debian/patches/series 2017-10-09 21:59:11.0 +0300 +++ pyzo-4.4.3/debian/patches/series 2018-11-30 17:17:17.0 +0200 @@ -1 +1,2 @@ Disable-install-of-appdata.patch +0001-replace-async-per-basync-to-become-Python-3.7-compat.patch
Processed: pyzo: diff for NMU version 4.4.3-1.1
Processing control commands: > tags 914332 + pending Bug #914332 [pyzo] "SyntaxError: invalid syntax" in postinst Added tag(s) pending. -- 914332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913494: marked as done (bindex: FTBFS with Java 11 due to CORBA removal)
Your message dated Fri, 30 Nov 2018 15:19:33 + with message-id and subject line Bug#913494: fixed in bindex 2.2+svn101-4 has caused the Debian Bug report #913494, regarding bindex: FTBFS with Java 11 due to CORBA removal 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.) -- 913494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bindex Version: 2.2+svn101-3 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bindex.html ... jh_build dist/bindex-2.2.jar src find src -name *.java -and -type f -print0 | xargs -s 512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp /usr/share/ant/lib/ant.jar:/usr/share/java/kxml2-min.jar:/usr/share/java/org.osgi.service.obr.jar:/usr/share/java/osgi.core.jar:/usr/share/java/junit4.jar:/usr/share/java/bnd.annotation.jar:debian/_jh_build.bindex-2.2 -d debian/_jh_build.bindex-2.2 -source 1.7 -target 1.7 -encoding ISO8859-1 warning: [options] bootstrap class path not set in conjunction with -source 7 src/test/TestVersionImpl.java:24: error: package org.omg.PortableInterceptor does not exist import org.omg.PortableInterceptor.*; ^ Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 1 error 1 warning make[1]: *** [debian/rules:15: override_dh_auto_build] Error 123 --- End Message --- --- Begin Message --- Source: bindex Source-Version: 2.2+svn101-4 We believe that the bug you reported is fixed in the latest version of bindex, 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 913...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated bindex 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: Fri, 30 Nov 2018 15:52:28 +0100 Source: bindex Binary: libbindex-java Architecture: source Version: 2.2+svn101-4 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libbindex-java - OSGi BIndex reader Closes: 913494 Changes: bindex (2.2+svn101-4) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 11 (Closes: #913494) * Standards-Version updated to 4.2.1 * Switch to debhelper level 11 * Use salsa.debian.org Vcs-* URLs Checksums-Sha1: e40fb4b46d332cc539202f112e04d0faaad2e500 2090 bindex_2.2+svn101-4.dsc b5558ef00dcc12670cd5ce479fea4c64aab27cbd 3944 bindex_2.2+svn101-4.debian.tar.xz 6d0873a90c87953184852ff67ed7afa04cdfbef2 13298 bindex_2.2+svn101-4_source.buildinfo Checksums-Sha256: 37e587251e93848ba17ce933786cefc6d50d0676a42b0451b7b80dd44e3d3660 2090 bindex_2.2+svn101-4.dsc e204574b08804771c9a5635ddc0c6959d6e51b2c2373eb37cd691df9d3b4fe18 3944 bindex_2.2+svn101-4.debian.tar.xz c48fb684fc5914e2b2580631fa2c76c5cfaf8ccaf90163a1726130213a7ad6d6 13298 bindex_2.2+svn101-4_source.buildinfo Files: 83b65c5f38f571992d3710956f3c2347 2090 java optional bindex_2.2+svn101-4.dsc c10ae1110239319c73e52d5b2b19dcca 3944 java optional bindex_2.2+svn101-4.debian.tar.xz 2bb6d30e5571a1b53eff6c696a2eb195 13298 java optional bindex_2.2+svn101-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwBT3USHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsR14P/jF4VcTSSjTRq30YNTkbNBQE89qmi92O Y6sDzSaED1B0CyJOnQ4AhEfk0BIFX8H408o7sOoybQDK1AxBL0/33SNmqKh2GES0 PJvSQSzGtRivwZt/abk4L2u78/YXuvaE0ICwHTDNfXmUsekFEggFtFSzKFy00Sou iyHu/0gd2KVCUVQCi4vRXa2x/sGPx62OtDhwufX61KoOFjCY98HO02NyDjcsw1dD IBNvIfMIqbFjIipC1f9lnlLUHrGg8QSzZQB6ZqogsLfYq67yajyv+aOEMx21CyqB EnYtUBhc/DocEEGSIU+odCZ1wRoTmP2xVYveJIiqAIYmyHXBd4RCqrGfQ+0UV9JF rFVA8aM3WsZP3Fe97EvamStqdBCQssyL9IBa3JtALOxJRqnPGndUzcdNfUYUL5Qg t5GF3BS6nkveFXmQb83Joo578CsBKfWg9tkJR6m/HANMOPGdrQ+Q1Uzicqzc1T5/ ZpO2Zlf27INA+8FOZqt017ftNN5xIPR+CQSX3uJID37IMSmqbnBCv0dNwXqAWayR vpvbKS5e0uoumrCe6ccq43PydXqHjY5L0O61KgNTnju2y84JjUx4Add/rCvz6nZH PMwxuhEeUainu3u0tuYl2SqZmkq9iRJ7GZ/l89tKfyODNZ/KqmGt4lYhM5nLXDVz 6aWNu7HHhp5G
Bug#915108: caffe: FTBFS on mips and mips64el: test failures
Source: caffe Version: 1.0.0+git20180821.99bd997-1 Severity: serious Tags: ftbfs Hi, Your package failed to build on mips: [ FAILED ] 2 tests, listed below: [ FAILED ] AdaDeltaSolverTest/0.TestSnapshot, where TypeParam = caffe::CPUDevice [ FAILED ] AdaDeltaSolverTest/1.TestSnapshotShare, where TypeParam = caffe::CPUDevice and again on mips on a second try: [ FAILED ] 3 tests, listed below: [ FAILED ] AdaDeltaSolverTest/0.TestSnapshotShare, where TypeParam = caffe::CPUDevice [ FAILED ] AdaDeltaSolverTest/0.TestSnapshot, where TypeParam = caffe::CPUDevice [ FAILED ] AdaDeltaSolverTest/0.TestLeastSquaresUpdateWithEverythingAccumShare, where TypeParam = caffe::CPUDevice and on mips64el: [ FAILED ] 2 tests, listed below: [ FAILED ] AdaDeltaSolverTest/0.TestAdaDeltaLeastSquaresUpdateWithEverything, where TypeParam = caffe::CPUDevice [ FAILED ] AdaDeltaSolverTest/1.TestSnapshot, where TypeParam = caffe::CPUDevice mipsel built fine. Perhaps the different buildds are relevant, as some mips* ones lack an FPU. Cheers, Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#914495: linux-image-4.19.0-trunk-amd64: does boot here
Linux 4.19.5-1~exp1 works. On the other hand it possibly comes with ext4 file system corruption. https://bugzilla.kernel.org/show_bug.cgi?id=201685
Processed: forcemerge 914495 914980
Processing commands for cont...@bugs.debian.org: > forcemerge 914495 914980 Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here Bug #914495 [src:linux] linux-image-4.18.0-3-amd64: does not boot here Marked as found in versions linux/4.18.20-2. Bug #914980 [src:linux] linux-image-4.18.0-3-amd64: linux image installed via 4.18.0-3 stops gdm starting on T500 and X201 Severity set to 'critical' from 'important' Marked as found in versions linux/4.18.20-1. Merged 914495 914980 > thanks Stopping processing here. Please contact me if you need assistance. -- 914495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914495 914980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fwd: Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > block 915102 by 808839 Bug #915102 [src:scilab] scilab: FTBFS on amd64: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering 915102 was not blocked by any bugs. 915102 was not blocking any bugs. Added blocking bug(s) of 915102: 808839 > End of message, stopping processing here. Please contact me if you need assistance. -- 915102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913494: Bug #913494 in bindex marked as pending
Control: tag -1 pending Hello, Bug #913494 in bindex 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/java-team/bindex/commit/67fbbd602769f6ef5f180488d0c9162935cdc5e3 Fixed the build failure with Java 11 (Closes: #913494) (this message was generated automatically) -- Greetings https://bugs.debian.org/913494
Processed: Bug #913494 in bindex marked as pending
Processing control commands: > tag -1 pending Bug #913494 [src:bindex] bindex: FTBFS with Java 11 due to CORBA removal Added tag(s) pending. -- 913494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907409: marked as done (casync: FTBFS with glibc 2.28, header mismatch wih new renameat2())
Your message dated Fri, 30 Nov 2018 14:52:37 +
with message-id
and subject line Bug#907409: fixed in casync 2+20180321-2.1
has caused the Debian Bug report #907409,
regarding casync: FTBFS with glibc 2.28, header mismatch wih new renameat2()
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.)
--
907409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: casync
Version: 2+20180321-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch
Dear maintainers,
casync fails to build from source against glibc 2.28, as seen in the Ubuntu
autopkgtest:
[...]
cc -Isrc/src@@shared@sta -Isrc -I../src -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Werror=format=2
-Wformat-security -Wformat-nonliteral -Wlogical-op -Wmissing-include-dirs
-Werror=old-style-definition -Werror=pointer-arith -Winit-self
-Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn
-Werror=missing-prototypes -Werror=implicit-function-declaration
-Werror=missing-declarations -Werror=return-type
-Werror=incompatible-pointer-types -Werror=shadow -Werror=int-conversion
-Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wendif-labels
-Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter
-Wno-missing-field-initializers -Wno-unused-result -Werror=overflow
-Werror=sign-compare -Wdate-time -Wnested-externs -fno-common
-fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden
-fstack-protector -fstack-protector-strong -fPIE --param=ssp-buffer-size=4
-include config.h -g -O2
-fdebug-prefix-map=/tmp/autopkgtest.iBt8c8/build.W5z/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 'src/src@@shared@sta/cacache.c.o' -MF
'src/src@@shared@sta/cacache.c.o.d' -o 'src/src@@shared@sta/cacache.c.o' -c
../src/cacache.c
In file included from ../src/canametable.h:9,
from ../src/calocation.h:12,
from ../src/cacache.h:7,
from ../src/cacache.c:9:
../src/util.h:532:19: error: static declaration of ‘renameat2’ follows
non-static declaration
static inline int renameat2(int oldfd, const char *oldname, int newfd, const
char *newname, unsigned flags) {
^
In file included from ../src/util.h:12,
from ../src/canametable.h:9,
from ../src/calocation.h:12,
from ../src/cacache.h:7,
from ../src/cacache.c:9:
/usr/include/stdio.h:164:12: note: previous declaration of ‘renameat2’ was here
extern int renameat2 (int __oldfd, const char *__old, int __newfd,
^
ninja: build stopped: subcommand failed.
[...]
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/c/casync/20180825_081049_5b743@/log.gz)
The casync build system does include a check for a system-provided
renameat2() implementation, however, the new renameat2 in
/usr/include/stdio.h in glibc 2.28 is guarded with __USE_GNU which means its
availability is conditional on features.h selections - and while _GNU_SOURCE
winds up being defined in meson.build for the actual software build, it is
NOT defined while meson itself is doing feature detection.
Perhaps adding -D_GNU_SOURCE to c_args would fix the build failure, but I
used the larger hammer of defining it as
DEB_CFLAGS_MAINT_APPEND=-D_GNU_SOURCE in debian/rules.
Please consider the attached patch to fix this bug, which will become a
serious bug once glibc 2.28 is uploaded to Debian.
--
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 casync-2+20180321/debian/rules casync-2+20180321/debian/rules
--- casync-2+20180321/debian/rules 2018-05-03 06:12:33.0 -0700
+++ casync-2+20180321/debian/rules 2018-08-27 09:50:17.0 -0700
@@ -1,6 +1,7 @@
#! /usr/bin/make -f
export DEB_BUILD_MAINT_OPTIONS=hardening=+all
+export DEB_CFLAGS_MAINT_APPEND=-D_GNU_SOURCE
export LC_ALL=C.UTF-8
--- End Message ---
--- Begin Message ---
Source: casync
Source-Version: 2+20180321-2.1
We believe that the bug you reported is fixed in the latest version of
casync, which is due to be installed in the
Processed: Re: bindex FTBFS with OpenJDK 11
Processing commands for cont...@bugs.debian.org: > retitle 913494 bindex: FTBFS with Java 11 due to CORBA removal Bug #913494 [src:bindex] bindex FTBFS with OpenJDK 11 Changed Bug title to 'bindex: FTBFS with Java 11 due to CORBA removal' from 'bindex FTBFS with OpenJDK 11'. > End of message, stopping processing here. Please contact me if you need assistance. -- 913494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
On Fri, Nov 30, 2018 at 07:39:20PM +0530, Pirate Praveen wrote: > >Backports are *always* from testing because a backport is > >supposed to be replaced by the regular stable version of > >the subsequent release. > That is indeed the current definition. Me too is very happy with it. > Another option could be to have personal package archive for gitlab. That. And if you don't want to wait until they arrive in Debian proper, I'd suggest you'd host such an archive yourself. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Processed: Work is in progress
Processing commands for cont...@bugs.debian.org: > tags 911154 pending Bug #911154 [src:netkit-ntalk] netkit-ntalk misses the generator for configure Added tag(s) pending. > tags 912120 pending Bug #912120 [src:biff] biff misses the generator for configure Added tag(s) pending. > tags 912121 pending Bug #912121 [src:bsd-finger] bsd-finger misses the generator for configure Added tag(s) pending. > tags 912122 pending Bug #912122 [src:linux-ftpd] linux-ftpd misses the generator for configure Added tag(s) pending. > tags 912123 pending Bug #912123 [src:linux-ftpd-ssl] linux-ftpd-ssl misses the generator for configure Added tag(s) pending. > tags 912124 pending Bug #912124 [src:netkit-bootparamd] netkit-bootparamd misses the generator for configure Added tag(s) pending. > tags 912125 pending Bug #912125 [src:netkit-ftp] netkit-ftp misses the generator for configure Added tag(s) pending. > tags 912126 pending Bug #912126 [src:netkit-ftp-ssl] netkit-ftp-ssl misses the generator for configure Added tag(s) pending. > tags 912127 pending Bug #912127 [src:netkit-rsh] netkit-rsh misses the generator for configure Added tag(s) pending. > tags 912128 pending Bug #912128 [src:netkit-rusers] netkit-rusers misses the generator for configure Added tag(s) pending. > tags 912129 pending Bug #912129 [src:netkit-rwall] netkit-rwall misses the generator for configure Added tag(s) pending. > tags 912130 pending Bug #912130 [src:netkit-rwho] netkit-rwho misses the generator for configure Added tag(s) pending. > tags 912131 pending Bug #912131 [src:netkit-telnet] netkit-telnet misses the generator for configure Added tag(s) pending. > tags 912132 pending Bug #912132 [src:netkit-telnet-ssl] netkit-telnet-ssl misses the generator for configure Added tag(s) pending. > tags 912133 pending Bug #912133 [src:netkit-tftp] netkit-tftp misses the generator for configure Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 911154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154 912120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912120 912121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912121 912122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912122 912123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912123 912124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912124 912125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912125 912126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912126 912127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912127 912128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912128 912129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912129 912130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912130 912131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912131 912132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912132 912133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #915096 in libperl-apireference-perl marked as pending
Processing control commands: > tag -1 pending Bug #915096 [src:libperl-apireference-perl] libperl-apireference-perl: Missing support for perl 5.28.1 Added tag(s) pending. -- 915096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915096: Bug #915096 in libperl-apireference-perl marked as pending
Control: tag -1 pending Hello, Bug #915096 in libperl-apireference-perl 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/perl-team/modules/packages/libperl-apireference-perl/commit/9752384c797bc7555c14cd020fc73328d4661865 Add suport for perl 5.28.1. Closes: #915096 (this message was generated automatically) -- Greetings https://bugs.debian.org/915096
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
On Fri, 30 Nov 2018, Pirate Praveen wrote: > That is indeed the current definition. The question is about the > possibility of changing that definition or finding other ways to No. It’s there for good reasons, including stability. > accommodate fast changing software like gitlab. Broadening the Find a way to pick stable, slow changing versions of it and improve their packaging in testing/unstable so you can backport it. Work with upstream towards that goal. Some upstreams are receptive of stabilising certain versions in order to get packaged. If your upstreams aren’t, they’re probably not worth the effort using the software. bye, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"...
Bug#907409: casync: diff for NMU version 2+20180321-2.1
On Fri, Nov 30, 2018 at 01:52:30PM +0100, Michael Biebl wrote: > Am 30.11.2018 um 13:47 schrieb Adrian Bunk: > > Control: tags 907409 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for casync (versioned as 2+20180321-2.1) and > > uploaded it to DELAYED/14. Please feel free to tell me if I should > > cancel it. > > Feel free to upload without delay. Thanks, done. > Thanks > > Michael 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#914695: dgit autopkgtest breaks with git 2.20
I fixed this via https://public-inbox.org/git/pull.91.git.gitgitgad...@gmail.com/T/#t and the latest word is that this will be part of v2.20.0-rc2 (which I would expect before Monday, maybe even tonight).
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
On 2018, നവംബർ 30 5:14:20 PM IST, Thorsten Glaser wrote: >On Fri, 30 Nov 2018, Pirate Praveen wrote: > >> How about allowing gitlab to be backported directly from unstable? > >No. > >Backports are *always* from testing because a backport is >supposed to be replaced by the regular stable version of >the subsequent release. That is indeed the current definition. The question is about the possibility of changing that definition or finding other ways to accommodate fast changing software like gitlab. Broadening the definition of backports is one possible option I see. Another option could be to have personal package archive for gitlab. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#915102: scilab: FTBFS on amd64: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering
Source: scilab Version: 6.0.1-6 Severity: serious Hi, On a rebuild against libhdf5-103, scilab has failed on amd64 twice. The second failure was during configure: checking commons-logging... /usr/share/java/fop-transcoder-allinone.jar checking jlatexmath... /usr/share/java/jlatexmath-1.0.7.jar checking jlatexmath-fop... no configure: error: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering - FOP plugin (looking for package org.scilab.forge.jlatexmath.fop.JLaTeXMathObj) make[1]: *** [debian/rules:38: override_dh_auto_configure] Error 1 Full logs at https://buildd.debian.org/status/logs.php?pkg=scilab=6.0.1-6%2Bb1=amd64 Emilio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: Bug#839161: fixed in crrcsim 0.9.13-1
Processing control commands:
> reopen -1
Bug #839161 {Done: Agustin Henze } [crrcsim] crrcsim FTBFS on
hppa architecture (with patch)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions crrcsim/0.9.13-1.
> retitle -1 crrcsim: FTBFS on several architectures
Bug #839161 [crrcsim] crrcsim FTBFS on hppa architecture (with patch)
Changed Bug title to 'crrcsim: FTBFS on several architectures' from 'crrcsim
FTBFS on hppa architecture (with patch)'.
> severity -1 serious
Bug #839161 [crrcsim] crrcsim: FTBFS on several architectures
Severity set to 'serious' from 'normal'
--
839161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#914897: affects private debs too
On Nov 29, Adam Borowski wrote: > Thus: sorry but there is no way we can possibly support usrmerged and > non-usrmerged systems at the same time. Usrmerge is not viable without a > flag day. We have being doing exactly this opt-in (the usrmerge package) for over three years and opt-out (the debootstrap default) for six months with only minor problems. With growing adoptions we have found and addressed the bugs, and currently the only significant issue still open is #913883 (iptables doing diversions, which I am sure can be fixed). How much experience do you have in using merged-/usr systems? -- ciao, Marco signature.asc Description: PGP signature
Processed: fusedav non-functional
Processing control commands: > severity -1 grave Bug #840388 [fusedav] doers nothing Severity set to 'grave' from 'normal' -- 840388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: vdr-plugin-fritzbox: diff for NMU version 1.5.3-7.1
Processing control commands: > tags 914064 + patch Bug #914064 [src:vdr-plugin-fritzbox] vdr-plugin-fritzbox FTBFS with boost 1.67 Added tag(s) patch. > tags 914064 + pending Bug #914064 [src:vdr-plugin-fritzbox] vdr-plugin-fritzbox FTBFS with boost 1.67 Added tag(s) pending. -- 914064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914064: vdr-plugin-fritzbox: diff for NMU version 1.5.3-7.1
Control: tags 914064 + patch Control: tags 914064 + pending Dear maintainer, I've prepared an NMU for vdr-plugin-fritzbox (versioned as 1.5.3-7.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru vdr-plugin-fritzbox-1.5.3/debian/changelog vdr-plugin-fritzbox-1.5.3/debian/changelog --- vdr-plugin-fritzbox-1.5.3/debian/changelog 2018-04-15 20:13:53.0 +0300 +++ vdr-plugin-fritzbox-1.5.3/debian/changelog 2018-11-30 14:49:55.0 +0200 @@ -1,3 +1,10 @@ +vdr-plugin-fritzbox (1.5.3-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with Boost 1.67. (Closes: #914064) + + -- Adrian Bunk Fri, 30 Nov 2018 14:49:55 +0200 + vdr-plugin-fritzbox (1.5.3-7) unstable; urgency=medium * VCS moved to salsa.debian.org diff -Nru vdr-plugin-fritzbox-1.5.3/debian/patches/0001-Add-compatibility-with-boost-1.67.patch vdr-plugin-fritzbox-1.5.3/debian/patches/0001-Add-compatibility-with-boost-1.67.patch --- vdr-plugin-fritzbox-1.5.3/debian/patches/0001-Add-compatibility-with-boost-1.67.patch 1970-01-01 02:00:00.0 +0200 +++ vdr-plugin-fritzbox-1.5.3/debian/patches/0001-Add-compatibility-with-boost-1.67.patch 2018-11-30 14:49:13.0 +0200 @@ -0,0 +1,25 @@ +From 212847f0efaeffee8422059b8e202d844174aaf3 Mon Sep 17 00:00:00 2001 +From: Joachim Wilke +Date: Thu, 28 Jun 2018 12:56:54 +0200 +Subject: [PATCH] Add compatibility with boost 1.67 + +Refers to https://github.com/jowi24/vdr-fritz/issues/1 +--- + TcpClient.cpp | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/TcpClient.cpp b/TcpClient.cpp +index b9b38e9..c6cc08e 100644 +--- a/libnet++/TcpClient.cpp b/libnet++/TcpClient.cpp +@@ -19,6 +19,7 @@ + * + */ + ++#define BOOST_ASIO_USE_BOOST_DATE_TIME_FOR_SOCKET_IOSTREAM + #include "TcpClient.h" + + #include +-- +2.11.0 + diff -Nru vdr-plugin-fritzbox-1.5.3/debian/patches/series vdr-plugin-fritzbox-1.5.3/debian/patches/series --- vdr-plugin-fritzbox-1.5.3/debian/patches/series 2018-04-15 20:13:53.0 +0300 +++ vdr-plugin-fritzbox-1.5.3/debian/patches/series 2018-11-30 14:49:54.0 +0200 @@ -1 +1,2 @@ format-security.patch +0001-Add-compatibility-with-boost-1.67.patch
Bug#907409: casync: diff for NMU version 2+20180321-2.1
Am 30.11.2018 um 13:47 schrieb Adrian Bunk: > Control: tags 907409 + pending > > Dear maintainer, > > I've prepared an NMU for casync (versioned as 2+20180321-2.1) and > uploaded it to DELAYED/14. Please feel free to tell me if I should > cancel it. Feel free to upload without delay. Thanks Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: casync: diff for NMU version 2+20180321-2.1
Processing control commands: > tags 907409 + pending Bug #907409 [casync] casync: FTBFS with glibc 2.28, header mismatch wih new renameat2() Added tag(s) pending. -- 907409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907409: casync: diff for NMU version 2+20180321-2.1
Control: tags 907409 + pending
Dear maintainer,
I've prepared an NMU for casync (versioned as 2+20180321-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
diff -Nru casync-2+20180321/debian/changelog casync-2+20180321/debian/changelog
--- casync-2+20180321/debian/changelog 2018-05-03 16:12:33.0 +0300
+++ casync-2+20180321/debian/changelog 2018-11-30 14:37:06.0 +0200
@@ -1,3 +1,10 @@
+casync (2+20180321-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for FTBFS with glibc 2.28. (Closes: #907409)
+
+ -- Adrian Bunk Fri, 30 Nov 2018 14:37:06 +0200
+
casync (2+20180321-2) unstable; urgency=medium
* Add udev Build-Depends to be able to query udev.pc (Closes: #897597)
diff -Nru casync-2+20180321/debian/patches/0001-meson.build-pass-D_GNU_SOURCE-when-checking-for-func.patch casync-2+20180321/debian/patches/0001-meson.build-pass-D_GNU_SOURCE-when-checking-for-func.patch
--- casync-2+20180321/debian/patches/0001-meson.build-pass-D_GNU_SOURCE-when-checking-for-func.patch 1970-01-01 02:00:00.0 +0200
+++ casync-2+20180321/debian/patches/0001-meson.build-pass-D_GNU_SOURCE-when-checking-for-func.patch 2018-11-30 14:37:06.0 +0200
@@ -0,0 +1,28 @@
+From a110e8c7e266042b9d9703811621d04f46226719 Mon Sep 17 00:00:00 2001
+From: Daniel Mack
+Date: Tue, 13 Nov 2018 17:52:48 +0100
+Subject: [PATCH] meson.build: pass -D_GNU_SOURCE when checking for functions
+
+As described in #166, -D_GNU_SOURCE needs to be passed to the meson function
+availability checker. h/t to @tomeon for providing a link to the solution as
+well.
+---
+ meson.build | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/meson.build b/meson.build
+index f42ed16..c0f741e 100644
+--- a/meson.build
b/meson.build
+@@ -78,7 +78,7 @@ foreach ident : [
+ ['copy_file_range', '''#include
+ #include '''],
+ ]
+-have = cc.has_function(ident[0], prefix : ident[1])
++have = cc.has_function(ident[0], args : '-D_GNU_SOURCE', prefix : ident[1])
+ conf.set10('HAVE_' + ident[0].to_upper(), have)
+ endforeach
+
+--
+2.11.0
+
diff -Nru casync-2+20180321/debian/patches/series casync-2+20180321/debian/patches/series
--- casync-2+20180321/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ casync-2+20180321/debian/patches/series 2018-11-30 14:37:06.0 +0200
@@ -0,0 +1 @@
+0001-meson.build-pass-D_GNU_SOURCE-when-checking-for-func.patch
Bug#915096: libperl-apireference-perl: Missing support for perl 5.28.1
Source: libperl-apireference-perl Version: 0.22-9 Severity: grave Justification: ftbfs This package needs an update for perl 5.28.1, which was uploaded to unstable yesterday.
Bug#915020: marked as done (munin-plugins-java: copyright file missing after upgrade (policy 12.5))
Your message dated Fri, 30 Nov 2018 12:05:55 +
with message-id
and subject line Bug#915020: fixed in munin 2.999.9-3
has caused the Debian Bug report #915020,
regarding munin-plugins-java: copyright file missing after upgrade (policy 12.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.)
--
915020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin-plugins-java
Version: 2.999.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
This was observed on the following upgrade paths:
sid -> experimental
>From the attached log (scroll to the bottom...):
0m31.8s ERROR: WARN: Inadequate results from running adequate!
munin-plugins-java: missing-copyright-file
/usr/share/doc/munin-plugins-java/copyright
MISSING COPYRIGHT FILE: /usr/share/doc/munin-plugins-java/copyright
# ls -lad /usr/share/doc/munin-plugins-java
drwxr-xr-x 2 root root 40 Nov 16 01:10 /usr/share/doc/munin-plugins-java
# ls -la /usr/share/doc/munin-plugins-java/
total 0
drwxr-xr-x 2 root root 40 Nov 16 01:10 .
drwxr-xr-x 135 root root 2800 Nov 16 01:10 ..
Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
cheers,
Andreas
munin-plugins-java_2.999.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: munin
Source-Version: 2.999.9-3
We believe that the bug you reported is fixed in the latest version of
munin, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Holger Levsen (supplier of updated munin 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: Fri, 30 Nov 2018 12:56:45 +0100
Source: munin
Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-java
munin-plugins-http munin-plugins-mysql munin-plugins-pgsql munin-plugins-snmp
munin-plugins-ldap munin-plugins-irc munin-plugins-dns munin-plugins-mail
munin-plugins-time munin-plugins-network munin-plugins-jenkins libmunin-perl
libmunin-master-perl libmunin-node-perl libmunin-plugin-perl
libmunin-plugin-http-perl libmunin-plugin-snmp-perl libmunin-plugin-pgsql-perl
munin munin-common munin-async munin-doc
Architecture: source
Version: 2.999.9-3
Distribution: experimental
Urgency: medium
Maintainer: Munin Debian Maintainers
Changed-By: Holger Levsen
Description:
libmunin-master-perl - perl modules for munin master
libmunin-node-perl - perl module Munin::Node
libmunin-perl - common perl modules for munin
libmunin-plugin-http-perl - perl bindings for HTTP munin plugins
libmunin-plugin-perl - perl bindings for munin plugins
libmunin-plugin-pgsql-perl - perl bindings for PostgreSQL munin plugins
libmunin-plugin-snmp-perl - perl bindings for SNMP munin plugins
munin - network-wide graphing framework (grapher/gatherer)
munin-async - network-wide graphing framework (async master/client)
munin-common - network-wide graphing framework (common)
munin-doc - network-wide graphing framework (documentation)
munin-node - network-wide graphing framework (node)
munin-plugins-core - network-wide graphing framework (plugins for node)
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
On Fri, 30 Nov 2018, Pirate Praveen wrote: > How about allowing gitlab to be backported directly from unstable? No. Backports are *always* from testing because a backport is supposed to be replaced by the regular stable version of the subsequent release. Hence, only from testing, in the hope that the package being in testing means the package will be in the next stable. (Which also means that, when the package gets removed from testing, the backport should probably be deleted.) Backports are *not* a primary means of delivering software. Backports are for people who think they need the software from Debian x+1 on Debian x. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Processed: Fixed in 0.14
Processing commands for cont...@bugs.debian.org: > tags 913512 fixed-upstream Bug #913512 [src:ucto] ucto FTBFS with ICU 63.1 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 913512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913380: tarantool: diff for NMU version 1.9.1.26.g63eb81e3c-1.1
Control: tags 913380 + patch Control: tags 913380 + pending Dear maintainer, I've prepared an NMU for tarantool (versioned as 1.9.1.26.g63eb81e3c-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed diff -Nru tarantool-1.9.1.26.g63eb81e3c/debian/changelog tarantool-1.9.1.26.g63eb81e3c/debian/changelog --- tarantool-1.9.1.26.g63eb81e3c/debian/changelog 2018-06-08 23:03:14.0 +0300 +++ tarantool-1.9.1.26.g63eb81e3c/debian/changelog 2018-11-30 12:45:36.0 +0200 @@ -1,3 +1,10 @@ +tarantool (1.9.1.26.g63eb81e3c-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with curl >= 7.62. (Closes: #913380) + + -- Adrian Bunk Fri, 30 Nov 2018 12:45:36 +0200 + tarantool (1.9.1.26.g63eb81e3c-1) unstable; urgency=medium * New upstream version. diff -Nru tarantool-1.9.1.26.g63eb81e3c/debian/patches/0001-httpc-fix-compilation-with-libcurl-7.62.0.patch tarantool-1.9.1.26.g63eb81e3c/debian/patches/0001-httpc-fix-compilation-with-libcurl-7.62.0.patch --- tarantool-1.9.1.26.g63eb81e3c/debian/patches/0001-httpc-fix-compilation-with-libcurl-7.62.0.patch 1970-01-01 02:00:00.0 +0200 +++ tarantool-1.9.1.26.g63eb81e3c/debian/patches/0001-httpc-fix-compilation-with-libcurl-7.62.0.patch 2018-11-30 12:43:40.0 +0200 @@ -0,0 +1,49 @@ +From 02da15f7109b8bb7921eb97a751607b9dd2885b2 Mon Sep 17 00:00:00 2001 +From: Vladimir Davydov +Date: Thu, 1 Nov 2018 13:35:24 +0300 +Subject: [PATCH] httpc: fix compilation with libcurl >= 7.62.0 + +Starting from libcurl 7.62.0, CURL_SSL_CACERT is defined as a macro +alias to CURLE_PEER_FAILED_VERIFICATION, see + + https://github.com/curl/curl/commit/3f3b26d6feb0667714902e836af608094235fca2 + +This breaks compilation: + + httpc.c:337:7: error: duplicate case value 'CURLE_PEER_FAILED_VERIFICATION' + case CURLE_PEER_FAILED_VERIFICATION: + ^ + httpc.c:336:7: note: previous case defined here + case CURLE_SSL_CACERT: + ^ + curl.h:589:26: note: expanded from macro 'CURLE_SSL_CACERT' + #define CURLE_SSL_CACERT CURLE_PEER_FAILED_VERIFICATION + ^ + +Fix this by using CURLE_SSL_CACERT only if libcurl version is less +than 7.62.0. + +Note, we can't use CURL_AT_LEAST_VERSION to check libcurl version, +because it isn't available in libcurl shipped with CentOS 6. +--- + src/httpc.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/src/httpc.c b/src/httpc.c +index 4d48a313d..950f8b32f 100644 +--- a/src/httpc.c b/src/httpc.c +@@ -333,7 +333,9 @@ httpc_execute(struct httpc_request *req, double timeout) + ++env->stat.http_other_responses; + } + break; +- case CURLE_SSL_CACERT: ++#if LIBCURL_VERSION_NUM < 0x073e00 ++ case CURLE_SSL_CACERT: /* deprecated in libcurl 7.62.0 */ ++#endif + case CURLE_PEER_FAILED_VERIFICATION: + /* 495 SSL Certificate Error (nginx non-standard) */ + req->status = 495; +-- +2.11.0 + diff -Nru tarantool-1.9.1.26.g63eb81e3c/debian/patches/series tarantool-1.9.1.26.g63eb81e3c/debian/patches/series --- tarantool-1.9.1.26.g63eb81e3c/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ tarantool-1.9.1.26.g63eb81e3c/debian/patches/series 2018-11-30 12:44:26.0 +0200 @@ -0,0 +1 @@ +0001-httpc-fix-compilation-with-libcurl-7.62.0.patch
