Bug#921558: lsb-base: killproc does not pass name parameter to start-stop-daemon

On 2019-03-11 Axel Beckert wrote: [...] > Here's the change I made to /lib/lsb/init-functions (as Dmitry already > suggested): > --- /lib/lsb/init-functions~2018-11-28 20:21:37.0 +0100 > +++ /lib/lsb/init-functions 2019-03-11 21:46:41.673767215 +0100 > @@ -141,7 +141,7 @@ > i

Bug#924373: qiime: Does not install due to outdated dependencies

Source: qiime Severity: grave Tags: patch Justification: renders package unusable # sudo apt install qiime Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situ

Bug#915584: marked as done (dicoweb: fails to install with python 3.7)

Your message dated Tue, 12 Mar 2019 04:19:16 + with message-id and subject line Bug#915584: fixed in dico 2.7-2 has caused the Debian Bug report #915584, regarding dicoweb: fails to install with python 3.7 to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: closing 899610

Processing commands for cont...@bugs.debian.org: > close 899610 4.1-2 Bug #899610 [src:mdadm] mdadm: Invalid maintainer address pkg-mdadm-de...@lists.alioth.debian.org The source 'mdadm' and version '4.1-2' do not appear to match any binary packages Marked as fixed in versions mdadm/4.1-2. Bug #

Bug#924047: FTBFS: package don't build successful after new GCC version

On Sun, Mar 10, 2019 at 08:03:57AM +0100, Carsten Schoenert wrote: > That's the last option in my eyes as it's a step backwards and is > absolutely not needed as I fixed the problem already. ---end quoted text--- Yes, but this needs to be done for every gcc update ! I tried unmangling the c++ sym

Bug#915298: marked as done (gdebi FTBFS with pyflakes 2.0.0-1)

Your message dated Tue, 12 Mar 2019 01:34:02 + with message-id and subject line Bug#915298: fixed in gdebi 0.9.5.7+nmu3 has caused the Debian Bug report #915298, regarding gdebi FTBFS with pyflakes 2.0.0-1 to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: found 924232 in 5.7.4-1, tagging 866354, tagging 912445, tagging 922947

Processing commands for cont...@bugs.debian.org: > found 924232 5.7.4-1 Bug #924232 [python-notebook, python3-notebook] python{,3}-notebook: unhandled symlink to directory conversion: /usr/lib/python{2.7,3}/dist-packages/notebook/static/components/bootstrap Marked as found in versions jupyter-no

Processed: temporarily lower severity for epiphany: can't browse anything

Processing commands for cont...@bugs.debian.org: > severity 922730 important Bug #922730 [epiphany-browser] cannot browse anything Severity set to 'important' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 922730: https://bugs.debian.org/cgi

Bug#923654: marked as done (libowasp-java-html-sanitizer-java-doc: Depends on libjsr305-java-doc which is no longer built in sid/buster)

Your message dated Tue, 12 Mar 2019 00:54:14 + with message-id and subject line Bug#923654: fixed in owasp-java-html-sanitizer 0.1+r88-2 has caused the Debian Bug report #923654, regarding libowasp-java-html-sanitizer-java-doc: Depends on libjsr305-java-doc which is no longer built in sid/bus

Bug#923654: Bug #923654 in owasp-java-html-sanitizer marked as pending

Control: tag -1 pending Hello, Bug #923654 in owasp-java-html-sanitizer 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/owasp-java-html-sanitizer/comm

Processed: Bug #923654 in owasp-java-html-sanitizer marked as pending

Processing control commands: > tag -1 pending Bug #923654 [libowasp-java-html-sanitizer-java-doc] libowasp-java-html-sanitizer-java-doc: Depends on libjsr305-java-doc which is no longer built in sid/buster Added tag(s) pending. -- 923654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92365

Processed: tagging 915298

Processing commands for cont...@bugs.debian.org: > tags 915298 + pending Bug #915298 [src:gdebi] gdebi FTBFS with pyflakes 2.0.0-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 915298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=91529

Bug#924356: marked as done (google-authenticator: FTBFS)

Your message dated Mon, 11 Mar 2019 23:22:23 + with message-id <20190311232223.ga19...@espresso.pseudorandom.co.uk> and subject line Re: Bug#924356: google-authenticator: FTBFS has caused the Debian Bug report #924356, regarding google-authenticator: FTBFS to be marked as done. This means that

Bug#924359: augustus: hardcoded built-using

package: augustus version: 3.3.2+dfsg-1 severity: serious Hi, Augustus has hardcoded built-using: https://sources.debian.org/src/augustus/3.3.2+dfsg-1/debian/control/?hl=31#L31 "Built-Using: samtools-legacy (= 0.1.19-2)" The built-using information should be determined based on the version tha

Bug#913165: marked as done (zziplib: CVE-2018-7726 CVE-2018-7725)

Your message dated Mon, 11 Mar 2019 23:05:24 + with message-id and subject line Bug#913165: fixed in zziplib 0.13.62-3.2 has caused the Debian Bug report #913165, regarding zziplib: CVE-2018-7726 CVE-2018-7725 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#923465: Update alternatives fixes problem

I followed what John did, except I did not uninstall freecad-python2 and did not install freecad-python3. Running update-alternatives was enough to resolved the issue. If the new package was supposed to do that, I don't think it worked, at least upgrading from -4. rleblanc@riker:~/code$ dpkg -l "*

Bug#923465: fixed in freecad 0.18~pre1+dfsg1-5

On Sat, 02 Mar 2019 10:20:00 + Kurt Kremitzki wrote: > Source: freecad > Source-Version: 0.18~pre1+dfsg1-5 > > We believe that the bug you reported is fixed in the latest version of > freecad, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this ver

Bug#924356: google-authenticator: FTBFS

Source: google-authenticator Version: 20170702-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I do: apt-get source google-authenticator cd google-authenticator-20170702 fakeroot make -f debian/rules binary

Processed: tagging 924351

Processing commands for cont...@bugs.debian.org: > tags 924351 + upstream fixed-upstream Bug #924351 [mupdf] CVE-2018-16647 CVE-2018-16648 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 924351: https://bugs.debian.org/cgi

Bug#924351: CVE-2018-16647 CVE-2018-16648

Package: mupdf Version: 1.14.0+ds1-3 Severity: grave Tags: security CVE-2018-16648: https://bugs.ghostscript.com/show_bug.cgi?id=699685 http://www.ghostscript.com/cgi-bin/findgit.cgi?38f883fe129a5e89306252a4676eaaf4bc968824 CVE-2018-16647: https://bugs.ghostscript.com/show_bug.cgi?id=699686 http:

Bug#923903: marked as done (cjs: FTBFS (dh_makeshlibs fails))

Your message dated Mon, 11 Mar 2019 21:49:23 + with message-id and subject line Bug#923903: fixed in cjs 3.8.0-5 has caused the Debian Bug report #923903, regarding cjs: FTBFS (dh_makeshlibs fails) to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: found 924348 in 2.01.5-1

Processing commands for cont...@bugs.debian.org: > found 924348 2.01.5-1 Bug #924348 [tintin++] CVE-2019-7629 Marked as found in versions tintin++/2.01.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 924348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9

Bug#924312: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

Hi Peter, Peter Pentchev wrote: > > […], this looks like a bug in lsb-base. And indeed, it is and > > is also already reported: https://bugs.debian.org/921558 > > > > Reassigning accordingly. > > Thanks for reporting this and for your analysis! You're welcome. > I came up with the same result

Bug#924348: CVE-2019-7629

Package: tintin++ Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7629 Cheers, Moritz

Bug#862373: The State of the YAML

On Mon, 11 Mar 2019 22:14:13 +0100, Ivo De Decker wrote: > Control: tags -1 buster-ignore Thanks. > > So I guess we have to consider if we're happy with the ability to > > turn off loading objects and recommend it to consumers and close the > > bugs; or if we want to change the defaults, which

Bug#923782: Relax dependency on faraday to allow updating ruby-faraday

Package: ruby-puppet-forge Followup-For: Bug #923782 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! With the provided patch, I am able to use librarian-puppet without any issue. Unless someone protests, I'll do a NMU next week to fix this bug. - -- System Information: Debian Release: bust

Processed: Re: The State of the YAML

Processing control commands: > tags -1 buster-ignore Bug #862373 [libyaml-libyaml-perl] libyaml-libyaml-perl: Unconditionally instantiates objects from yaml data Added tag(s) buster-ignore. -- 862373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862373 Debian Bug Tracking System Contact ow

Processed: Re: The State of the YAML

Processing control commands: > tags -1 buster-ignore Bug #862475 [libyaml-syck-perl] libyaml-syck-perl: Unconditionally instantiates objects from yaml data Added tag(s) buster-ignore. -- 862475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862475 Debian Bug Tracking System Contact ow...@bu

Bug#862373: The State of the YAML

Control: tags -1 buster-ignore Hi, On Fri, May 18, 2018 at 11:09:23AM +0200, gregor herrmann wrote: > Quick status update on the perl YAML modules and the problem of > instantiating objects: > > * libyaml-syck-perl has $YAML::LoadBlessed since a long time > * libyaml-libyaml-perl since 0.69 and

Bug#924346: xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on malformed XML declaration

Source: xmltooling Version: 3.0.3-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://issues.shibboleth.net/jira/browse/CPPXT-143 Control: found -1 1.6.0-4+deb9u1 Control: found -1 1.6.0-4 Hi, The following vulnerability was published for xmltooling, fil

Processed: xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on malformed XML declaration

Processing control commands: > found -1 1.6.0-4+deb9u1 Bug #924346 [src:xmltooling] xmltooling: CVE-2019-9628: XML parser class fails to trap exceptions on malformed XML declaration Marked as found in versions xmltooling/1.6.0-4+deb9u1. > found -1 1.6.0-4 Bug #924346 [src:xmltooling] xmltooling:

Bug#818366: synaptic: fails to start under Wayland

Hi Trevis, all, On Sun, 10 Mar 2019 20:46:02 +0530 Trevis Schiffer wrote: > Check this commit. > > > Looks like it is fixed on version 0.84.3 The reported failure in one of the recent merged bug reports was for v

Bug#924312: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

On Mon, Mar 11, 2019 at 09:28:04PM +0100, Axel Beckert wrote: > Control: reassign -1 lsb-base > Control: forcemerge 921558 -1 > Control: affects 921558 + stunnel4 > > Hi Paul, > > Paul Gevers wrote: > > On Mon, 11 Mar 2019 14:15:25 +0100 Axel Beckert wrote: > > > Version: 3:5.50-3 > > > > ^

Bug#921558: lsb-base: killproc does not pass name parameter to start-stop-daemon

Control: tag -1 + patch Hi Dmitry, Dmitry Bogatov wrote: > > base=${1##*/} > > if [ ! $pidfile ]; then > > name_param="--name $base --pidfile /var/run/$base.pid" > > else > > name_param="--pidfile $pidfile" > > fi > > > > The if clause checks for nonempty $pidfile inst

Processed: Re: Bug#921558: lsb-base: killproc does not pass name parameter to start-stop-daemon

Processing control commands: > tag -1 + patch Bug #921558 [lsb-base] lsb-base: killproc does not pass name parameter to start-stop-daemon Bug #924312 [lsb-base] stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecu

Bug#924312: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

Control: reassign -1 lsb-base Control: forcemerge 921558 -1 Control: affects 921558 + stunnel4 Hi Paul, Paul Gevers wrote: > On Mon, 11 Mar 2019 14:15:25 +0100 Axel Beckert wrote: > > Version: 3:5.50-3 > > ^^^ > I don't think the bug is only in this version, is it? No. But for

Processed: Re: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

Processing control commands: > reassign -1 lsb-base Bug #924312 [stunnel4] stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure Bug reassigned from package 'stunnel4' to 'lsb-base'. No longer marked as found in v

Bug#924341: pygnuplot: FTBFS due to unsatisfiable build-dependency debhelper (= 12)

Source: pygnuplot Version: 0.11.16-1 Severity: serious Tags: ftbfs Dear Maintainer, pygnuplot fails to build because it cannot install its build dependencies: $ sudo apt build-dep pygnuplot Reading package lists... Done Building dependency tree Reading state information... Done Some packages c

Bug#907277: autoconf: AC_SEARCH_LIBS for __atomic_foo fails with AC_LANG([C++]) and g++-8

Hi all, On 10-03-2019 13:41, Simon McVittie wrote: > On Thu, 17 Jan 2019 at 11:00:40 -0500, Nick Bowler wrote: >> I'm not familiar with the library in question but the problem >> appears to be specific to these __atomic_xyz builtins which seem >> to get special treatment in g++. Other builtins I

Processed: severity of 922669 is grave

Processing commands for cont...@bugs.debian.org: > severity 922669 grave Bug #922669 [src:sqlalchemy] sqlalchemy: CVE-2019-7164 CVE-2019-7548 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 922669: https://bugs.debian.org/c

Processed: tagging 899949

Processing commands for cont...@bugs.debian.org: > tags 899949 + buster-ignore Bug #899949 {Done: Ondřej Surý } [src:softhsm2] softhsm2: Invalid maintainer address pkg-dns-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me if you need a

Bug#921952: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

On Mon, Mar 11, 2019 at 12:29:10PM +0100, Jonas Smedegaard wrote: > control: reopen -1 > > Quoting Jonas Smedegaard (2019-03-11 12:22:03) > > Quoting Moritz Muehlenhoff (2019-02-10 14:47:49) > > > Source: libsass > > > Severity: serious > > > > > > None of the security bugs filed in the BTS has s

Bug#924339: javahelper regressed building -doc packages

Package: javahelper Version: 0.72-5 Severity: serious Tags: sid buster javahelper regressed building -doc packages, as seen with the android-platform-build package. See #924328.

Bug#924312: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

Hi Axel, On Mon, 11 Mar 2019 14:15:25 +0100 Axel Beckert wrote: > Version: 3:5.50-3 ^^^ I don't think the bug is only in this version, is it? > This is caused by the following change in dpkg 1.19.3 from 22 Jan 2019: > > * start-stop-daemon: Check whether standalone --pidfile

Bug#923446: marked as done (m2crypto: autopkgtest with new version of openssl: Connection refused)

Your message dated Mon, 11 Mar 2019 19:04:31 + with message-id and subject line Bug#923446: fixed in m2crypto 0.31.0-3 has caused the Debian Bug report #923446, regarding m2crypto: autopkgtest with new version of openssl: Connection refused to be marked as done. This means that you claim that

Bug#912445: marked as done (openhft-chronicle-threads: FTBFS with Java 11 due to JAXWS removal)

Your message dated Sun, 10 Mar 2019 23:20:26 + with message-id and subject line Bug#917738: fixed in openhft-chronicle-threads 1.1.6-2 has caused the Debian Bug report #912445, regarding openhft-chronicle-threads: FTBFS with Java 11 due to JAXWS removal to be marked as done. This means that y

Bug#923891: Workarounds?

Is there a short-term workaround that will fix the broken login system?  For example, can Redmine 4.0.1-1 be safely downgraded to 3.4.6-1 or will that cause database problems? -- Soren Stoutner Small Business Tech Solutions so...@smallbusinesstech.net 623-262-6169

Processed: tagging 899951

Processing commands for cont...@bugs.debian.org: > tags 899951 + buster-ignore Bug #899951 {Done: Yves-Alexis Perez } [src:xfce4-weather-plugin] xfce4-weather-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here.

Processed: tagging 899749

Processing commands for cont...@bugs.debian.org: > tags 899749 + buster-ignore Bug #899749 {Done: Yves-Alexis Perez } [src:xfconf] xfconf: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me if you nee

Processed: tagging 899744

Processing commands for cont...@bugs.debian.org: > tags 899744 + buster-ignore Bug #899744 {Done: Yves-Alexis Perez } [src:xfce4-panel] xfce4-panel: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me

Processed: tagging 899865

Processing commands for cont...@bugs.debian.org: > tags 899865 + buster-ignore Bug #899865 {Done: Yves-Alexis Perez } [src:libxfce4util] libxfce4util: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact m

Processed: tagging 899912

Processing commands for cont...@bugs.debian.org: > tags 899912 + buster-ignore Bug #899912 {Done: Yves-Alexis Perez } [src:xfce4-appfinder] xfce4-appfinder: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please co

Processed: tagging 899849

Processing commands for cont...@bugs.debian.org: > tags 899849 + buster-ignore Bug #899849 {Done: Yves-Alexis Perez } [src:xfce4-session] xfce4-session: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact

Processed: tagging 899595

Processing commands for cont...@bugs.debian.org: > tags 899595 + buster-ignore Bug #899595 {Done: Yves-Alexis Perez } [src:libxfce4ui] libxfce4ui: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me if

Processed: m2crypto: autopkgtest with new version of openssl: Connection refused

Processing control commands: > severity -1 serious Bug #923446 [src:m2crypto] m2crypto: autopkgtest with new version of openssl: Connection refused Severity set to 'serious' from 'important' -- 923446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923446 Debian Bug Tracking System Contact o

Bug#924328: Acknowledgement (android-platform-build ftbfs, using new javahelper)

The real issue is: debian/rules override_dh_auto_build-indep make[1]: Entering directory '/home/packages/tmp/at/d/android-platform-build-8.1.0+r23' jh_build --javacopts="-source 7" --no-javadoc --main=com.android.signapk.SignApk signapk.jar tools/signapk/ warning: [options] bootstrap class path

Bug#924329: xastir: FTBFS (magick/image-private.h: No such file or directory)

Package: src:xastir Version: 2.1.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --with autoreconf dh_update_

Bug#924328: android-platform-build ftbfs, using new javahelper

Package: src:android-platform-build Version: 1:8.1.0+r23-2 Severity: serious Tags: sid buster dh override_dh_auto_build-arch --with javahelper make[1]: Leaving directory '/home/packages/tmp/at/d/android-platform-build-8.1.0+r23' debian/rules override_dh_auto_build-indep make[1]: Entering direct

Bug#921780: esajpip: FTBFS (LaTeX error)

On Mon, Mar 11, 2019 at 05:50:16PM +0100, Mathieu Malaterre wrote: > Control: tags -1 wontfix > > Hi, > > On Sat, Feb 9, 2019 at 1:18 AM Santiago Vila wrote: > > ! ==> Fatal error occurred, no output PDF file produced! > > I cannot also reproduce this Latex issue. Are you sure there has not >

Bug#924327: directfb FTBFS for armel,armhf: error: implicit declaration of function 'makedev'

Source: directfb Version: 1.7.7-8 Severity: serious Tags: ftbfs User: helm...@debian.org Usertags: rebootstrap directfb has build failures. A cross build for armel fails: http://crossqa.subdivi.de/build/directfb_1.7.7-8_armel_20190223000250.log | /bin/bash ../../libtool --tag=CC --mode=compile

Bug#921780: marked as done (esajpip: FTBFS (LaTeX error))

Your message dated Mon, 11 Mar 2019 17:50:16 +0100 with message-id and subject line Re: Bug#921780: esajpip: FTBFS (LaTeX error) has caused the Debian Bug report #921780, regarding esajpip: FTBFS (LaTeX error) to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#921780: esajpip: FTBFS (LaTeX error)

Processing control commands: > tags -1 wontfix Bug #921780 [src:esajpip] esajpip: FTBFS (LaTeX error) Added tag(s) wontfix. -- 921780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#921780: esajpip: FTBFS (LaTeX error)

Control: tags -1 wontfix Hi, On Sat, Feb 9, 2019 at 1:18 AM Santiago Vila wrote: > ! ==> Fatal error occurred, no output PDF file produced! I cannot also reproduce this Latex issue. Are you sure there has not been a broken latex package upload recently ? In any case esajpip should migrate bac

Processed: severity of 923416 is grave

Processing commands for cont...@bugs.debian.org: > severity 923416 grave Bug #923416 [src:advancecomp] advancecomp: CVE-2019-9210 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 923416: https://bugs.debian.org/cgi-bin/bugre

Bug#915298: Thank you and +1

Hi Axel, thanks for the NMU diff - the proposed patch looks good. Cheers, Michael

Processed: found 924321 in 2017.2b1+dfsg-2, severity of 924321 is serious, block 924018 with 924321

Processing commands for cont...@bugs.debian.org: > found 924321 2017.2b1+dfsg-2 Bug #924321 [src:python-openflow] python-openflow: please stop buildd-depending on py3.6 Marked as found in versions python-openflow/2017.2b1+dfsg-2. > severity 924321 serious Bug #924321 [src:python-openflow] python-

Processed: Re: Bug#924018: RM: python3.6 -- superseded by python3.7

Processing control commands: > tag -1 moreinfo Bug #924018 [ftp.debian.org] RM: python3.6 -- superseded by python3.7 Added tag(s) moreinfo. > block -1 by 916820 918427 Bug #924018 [ftp.debian.org] RM: python3.6 -- superseded by python3.7 924018 was blocked by: 924322 924018 was not blocking any bu

Processed: python3-vitrage: please drop dependency on py3.6

Processing control commands: > block 924018 by -1 Bug #924018 [ftp.debian.org] RM: python3.6 -- superseded by python3.7 924018 was not blocked by any bugs. 924018 was not blocking any bugs. Added blocking bug(s) of 924018: 924322 -- 924018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92401

Bug#924322: python3-vitrage: please drop dependency on py3.6

Package: python3-vitrage Version: 3.2.0-1 Severity: serious Control: block 924018 by -1 Dear maintainer, somehow this got this far without a bug, but apparently your package python3-vitrage has a dependency on python3.6:any. Please use dh-python to change whatever shebang you have to use /usr/bi

Bug#915298: [NMU] Re: Bug#915298: gdebi FTBFS with pyflakes 2.0.0-1

Control: tag -1 + patch Hi, Andrey Rahmatullin wrote: > ./gdebi-kde:92: local variable 'e' is assigned to but never used > ./gdebi-gtk:80: local variable 'e' is assigned to but never used > ./GDebi/KDEAptDialogs.py:147: local variable 'e' is assigned to but never used > ./GDebi/GDebiKDE.py:363: l

Processed: [NMU] Re: Bug#915298: gdebi FTBFS with pyflakes 2.0.0-1

Processing control commands: > tag -1 + patch Bug #915298 [src:gdebi] gdebi FTBFS with pyflakes 2.0.0-1 Added tag(s) patch. -- 915298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#919139: marked as done (cli-common: Invalid maintainer email address)

Your message dated Mon, 11 Mar 2019 15:34:15 + with message-id and subject line Bug#919139: fixed in cli-common 0.10 has caused the Debian Bug report #919139, regarding cli-common: Invalid maintainer email address to be marked as done. This means that you claim that the problem has been dealt

Bug#921785: marked as done (gtk-sharp3: FTBFS ('MONO_PROFILE_ENTER_LEAVE' undeclared))

Your message dated Mon, 11 Mar 2019 13:35:12 + with message-id and subject line Bug#921785: fixed in gtk-sharp3 2.99.3-3 has caused the Debian Bug report #921785, regarding gtk-sharp3: FTBFS ('MONO_PROFILE_ENTER_LEAVE' undeclared) to be marked as done. This means that you claim that the probl

Bug#924312: stunnel4: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/lib/stunnel4///stunnel4.pid is insecure

Package: stunnel4 Version: 3:5.50-3 Severity: serious stopping or restarting stunnel4 on systems with sysvinit (or probably also any other init system using start-stop-daemon) fails as follows for me: invoke-rc.d stunnel4 restart Restarting TLS tunnels: /etc/stunnel/stunnel.conf: /sbin/start-sto

Bug#924311: miredo: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/run/miredo.pid is insecure

Package: miredo Version: 1.2.6-7 Severity: serious Hi, stopping or restarting miredo on systems with sysvinit (or probably also any other init system using start-stop-daemon) fails as follows for me: invoke-rc.d miredo restart [] Stopping Teredo IPv6 tunneling daemon: miredostart-stop-daemo

Bug#924310: xrdp: post-install script fails

$ sudo tail -n 100 /var/log/xrdp.log [20190311-13:57:54] [INFO ] starting xrdp with pid 10763 [20190311-13:57:54] [ERROR] xrdp_listen_main_loop: listen error, possible port already in use [20190311-13:57:54] [DEBUG] Closed socket 11 (AF_INET6 :: port 0) This looks strange. Might be related to

Bug#924310: xrdp: post-install script fails

Package: xrdp Version: 0.9.1-9+deb9u3 Severity: serious Justification: Policy 6.4 Dear Maintainer, on my system, xrdp fails to install. (see log) Not sure what the problem here is - if it is just missing configuration, post-install script should not fail and just skip starting the service. Best

Processed: Breaks for the armel libstdc++ symbol version changes

Processing control commands: > reopen -1 Bug #866354 {Done: Sylvestre Ledru } [libstdc++6] armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 Bug #873200 {Done: Sylvestre Ledru } [libstdc++6] /usr/bin/llvm-config-4.0: relocation error:

Bug#866354: Breaks for the armel libstdc++ symbol version changes

Control: reopen -1 Control: tags -1 buster sid The following breaks are needed to handle the moved symbols from the pr64735 fix in gcc-6 in stretch->buster upgrades on armel: dnsdist (<< 1.3.3-3) lambda-align (<< 1.0.3-5) libllvm3.8 libllvm3.9 libllvm4.0 mednafen (<< 1.22.1+dfsg-1) nghttp2-proxy

Processed: unarchiving 866354

Processing commands for cont...@bugs.debian.org: > unarchive 866354 Bug #866354 {Done: Sylvestre Ledru } [libstdc++6] armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 Bug #873200 {Done: Sylvestre Ledru } [libstdc++6] /usr/bin/llvm-co

Bug#922416: marked as done (cache.commit() doesn't release the archives lock)

Your message dated Mon, 11 Mar 2019 12:07:33 + with message-id and subject line Bug#922416: fixed in python-apt 1.8.4 has caused the Debian Bug report #922416, regarding cache.commit() doesn't release the archives lock to be marked as done. This means that you claim that the problem has been

Bug#922416: Bug #922416 in python-apt marked as pending

Control: tag -1 pending Hello, Bug #922416 in python-apt 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/apt-team/python-apt/commit/9de87aea78562aba5eae556ff795

Processed: Bug #922416 in python-apt marked as pending

Processing control commands: > tag -1 pending Bug #922416 [python-apt] cache.commit() doesn't release the archives lock Added tag(s) pending. -- 922416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

Processing control commands: > reopen -1 Bug #921952 {Done: Jonas Smedegaard } [src:libsass] Don't include in buster without proper commitment to update in stable Bug reopened Ignoring request to alter fixed versions of bug #921952 to the same values previously set -- 921952: https://bugs.debi

Bug#921952: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable

control: reopen -1 Quoting Jonas Smedegaard (2019-03-11 12:22:03) > Quoting Moritz Muehlenhoff (2019-02-10 14:47:49) > > Source: libsass > > Severity: serious > > > > None of the security bugs filed in the BTS has seen any maintainer followup > > (dating back to 2017 in some cases), and that's ju

Bug#921952: marked as done (Don't include in buster without proper commitment to update in stable)

Your message dated Mon, 11 Mar 2019 12:22:03 +0100 with message-id <155230332346.19101.5067034024862523...@auryn.jones.dk> and subject line Re: [Pkg-sass-devel] Bug#921952: Don't include in buster without proper commitment to update in stable has caused the Debian Bug report #921952, regarding Don

Processed: severity of 922416 is serious

Processing commands for cont...@bugs.debian.org: > severity 922416 serious Bug #922416 [python-apt] cache.commit() doesn't release the archives lock Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 922416: https://bugs.debian

Bug#924254: dmtx-utils: diff for NMU version 0.7.6-1.1

Yes, go ahead. On Mon, Mar 11, 2019 at 10:30 AM Simon McVittie wrote: > On Mon, 11 Mar 2019 at 10:09:21 +0100, Roberto Lumbreras wrote: > > You can reschedule it to unstable without delay. > > Thanks, rescheduled. > > My changes to libdmtx are waiting in the NEW queue. When they get accepted, >

Processed: Re: Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)

Processing control commands: > severity -1 serious Bug #915333 [git-annex] git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x) Severity set to 'serious' from 'important' > reassign -1 ghc 8.4.4+dfsg1-1 Bug #915333 [git-annex] git-annex: Illegal Instruction on armel (Fuj

Bug#923454: marked as done (renderdoc: FTBFS (error: braces around scalar initializer for type 'int'))

Your message dated Mon, 11 Mar 2019 09:49:34 + with message-id and subject line Bug#923454: fixed in renderdoc 1.2+dfsg-2 has caused the Debian Bug report #923454, regarding renderdoc: FTBFS (error: braces around scalar initializer for type 'int') to be marked as done. This means that you cl

Bug#924254: marked as done (dmtx-utils: hard-codes dependency on libdmtx0a)

Your message dated Mon, 11 Mar 2019 09:49:02 + with message-id and subject line Bug#924254: fixed in dmtx-utils 0.7.6-1.1 has caused the Debian Bug report #924254, regarding dmtx-utils: hard-codes dependency on libdmtx0a to be marked as done. This means that you claim that the problem has bee

Bug#918012: fix docker-compose in backports

Just ran into this. So basically, "someone" only has to kick up the dependency of docker-compose to python3-docker (>= 3.2.1). Thanks @someone 😁

Bug#924254: dmtx-utils: diff for NMU version 0.7.6-1.1

On Mon, 11 Mar 2019 at 10:09:21 +0100, Roberto Lumbreras wrote: > You can reschedule it to unstable without delay. Thanks, rescheduled. My changes to libdmtx are waiting in the NEW queue. When they get accepted, may I re-upload to unstable as soon as the release team are ready for the transition?

Bug#924254: dmtx-utils: diff for NMU version 0.7.6-1.1

Hi Simon, You can reschedule it to unstable without delay. As soon I have a time slot I'll work on the package to merge in your changes, but in the meantime it's good to have all of it fixed. Thank you very much for your help! On Sun, Mar 10, 2019 at 6:24 PM Simon McVittie wrote: > Control: tag

Processed: severity of 918339 is serious

Processing commands for cont...@bugs.debian.org: > severity 918339 serious Bug #918339 [dovecot-mysql] dovecot-mysql: dovecot/auth segfaults with double-free in mysql_close() / passdb_deinit() Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Bug#922031: Timer Disabling on Package Update? (is: #922031)

Am 10.03.19 um 17:54 schrieb Michael Biebl: > Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg: >> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote: >>> Can you provide the output of >>> systemctl status certbot.timer >>> journalctl -u certbot.timer >> >> The output of `systemctl show certbo