Bug#890317: marked as done (gnucash: FTBFS on 32-bit architectures due to test failures)

Your message dated Wed, 14 Mar 2018 05:42:45 + with message-id and subject line Bug#890317: fixed in gnucash 1:2.7.6-1 has caused the Debian Bug report #890317, regarding gnucash: FTBFS on 32-bit architectures due to test failures to be marked as done.

Bug#892884: python-neutron-taas build-depends on cruft package python-neutron

Package: python-neutron-taas Severity: serious Tags: buster, sid python-neutron-taas depends on python-neutron which is no longer built by the neutron source package. It appears to have been replaced by python3-neutron.

Bug#892882: python-networking-mlnx build-depends on cruft package python-neutron

Package: python-networking-mlnx Severity: serious Tags: buster, sid python-networking-mlnx depends on python-neutron which is no longer built by the neutron source package. It appears to have been replaced by python3-neutron.

Bug#892881: python-networking-arista build-depends on cruft package python-neutron

Package: python-networking-arista Severity: serious Tags: buster, sid python-networking arista depends on python-neutron which is no longer built by the neutron source package. It appears to have been replaced by python3-neutron.

Bug#892877: python-urwid-doc: removal of python-urwid-doc makes files disappear from python-urwid

Package: python-urwid-doc Version: 2.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using

Bug#892710: {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}

Followup-For: Bug #892710 Control: found -1 4.1.1-2 Control: found -1 4.1.0-2 Hi, unfortunately i{tcl,tk}3-dev in stretch did not provide a virtual package, so you'll need Breaks+Replaces or Conflicts against the real packages. (Sorry, didn't check the -dev packages in detail, just assumed they

Processed: Re: {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}

Processing control commands: > found -1 4.1.1-2 Bug #892710 {Done: Sergei Golovan } [tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev] {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc} There is no source info for the package 'tk-itk4-doc' at version

Bug#892874: libmatio-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libmatio-dev/NEWS.gz

Package: libmatio-doc Version: 1.5.12-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#892871: tome: Segfaults when started

On 2018-03-13 23:26:26 +, Pelle Hjek wrote: > Package: tome > Version: 2.4~0.git.2015.12.29-1.2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Starting Tome gives me this error: > > % tome > ASAN:DEADLYSIGNAL >

Processed: tagging 892872

Processing commands for cont...@bugs.debian.org: > tags 892872 + buster sid Bug #892872 [redsocks] redsocks: Redsocks 0.5 is incompatible with libevent 2.1 Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 892872:

Bug#892096: libc6:i386 yields invalid writes, triggered by GCC's AddressSanitizer

On 2018-03-05 20:46:32 +0100, Aurelien Jarno wrote: > The AddressSanitizer is using glibc internal functions though dlsym(), > and such functions have the right to change in new major versions: > > From libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc: > | void *get_tls_static_info_ptr =

Processed: found 892096 in 201803012-1

Processing commands for cont...@bugs.debian.org: > found 892096 201803012-1 Bug #892096 [gcc-snapshot] gcc-snapshot: AddressSanitizer uses glibc internal functions Marked as found in versions gcc-snapshot/201803012-1. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#790158: sugar-toolkit: depends on python-rsvg which is deprecated

Hi, It's been 2.5 months since I last pinged Jonas about this issue and 4 months since sugar-toolkit was removed from testing. It doesn't look like there's been any activity on this recently. sugar-toolkit is now one of only two packages preventing us from removing gnome-python-desktop from

Bug#892872: redsocks: Redsocks 0.5 is incompatible with libevent 2.1

Package: redsocks Version: 0.5-1+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Redsocks doesn't function on Debian buster. It hangs after receiving packets direct by iptables and never redirects packets to proxy. It seems redsocks 0.5 is incompatible

Bug#892871: tome: Segfaults when started

Package: tome Version: 2.4~0.git.2015.12.29-1.2 Severity: grave Justification: renders package unusable Dear Maintainer, Starting Tome gives me this error: % tome ASAN:DEADLYSIGNAL = ==28204==ERROR: AddressSanitizer: SEGV on

Bug#892121: libxml-saxon-xslt2-perl FTBFS with libsaxonhe-java 9.8.0.8+dfsg+1-1

On Mon, 05 Mar 2018 21:54:43 +0200, Adrian Bunk wrote: > Source: libxml-saxon-xslt2-perl > Version: 0.010-2 > Severity: serious > Tags: buster sid > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libxml-saxon-xslt2-perl.html > PERL_DL_NONLAZY=1 "/usr/bin/perl"

Bug#892766: marked as done (CVE-2017-15422)

Your message dated Tue, 13 Mar 2018 22:35:04 + with message-id and subject line Bug#892766: fixed in icu 57.1-9 has caused the Debian Bug report #892766, regarding CVE-2017-15422 to be marked as done. This means that you claim that the problem has been

Bug#892865: CVE-2017-11428

Package: ruby-saml Severity: grave Tags: security https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations

Bug#892864: CVE-2017-11430

Package: ruby-omniauth-saml Severity: grave Tags: security https://github.com/omniauth/omniauth-saml/issues/156 https://github.com/omniauth/omniauth-saml/pull/157 https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations https://www.kb.cert.org/vuls/id/475445 Cheers,

Bug#891338: marked as done (micropolis-activity: FTBFS with glibc 2.27: error: 'DOMAIN' undeclared (first use in this function))

Your message dated Tue, 13 Mar 2018 21:20:33 + with message-id and subject line Bug#891338: fixed in micropolis-activity 0.0.20071228-9 has caused the Debian Bug report #891338, regarding micropolis-activity: FTBFS with glibc 2.27: error: 'DOMAIN'

Bug#892859: paramiko: CVE-2018-7750: Server implementation does not check for auth before serving later requests

Source: paramiko Version: 1.15.1-1 Severity: grave Tags: security upstream Forwarded: https://github.com/paramiko/paramiko/issues/1175 Hi, the following vulnerability was published for paramiko. CVE-2018-7750[0]: | transport.py in the SSH server implementation of Paramiko before | 1.17.6,

Bug#888193: marked as done (ruby-rmagick: FTBFS on ruby2.5: <FrozenError(<can't modify frozen Magick::Image>)>)

Your message dated Tue, 13 Mar 2018 22:09:34 +0200 with message-id <20180313200934.GA21628@localhost> and subject line Re: Bug#888193: ruby-rmagick: FTBFS on ruby2.5: )> has caused the Debian Bug report #888193, regarding ruby-rmagick: FTBFS on

Bug#892849: [3dprinter-general] Bug#892849: cura: Exception while launching cura

> the sip module implements API v12.0 to v12.2 but the Arcus module requires > API v12.3 Can you give me the output of dpkg-query -l libarcus3 python3-arcus python3-sip ? signature.asc Description: OpenPGP digital signature

Bug#877433: stretch update for r-cran-mi

On Tue, Mar 13, 2018 at 08:56:52PM +0200, Adrian Bunk wrote: > On Sun, Oct 01, 2017 at 09:39:04PM +, Debian Bug Tracking System wrote: > >... > > r-cran-mi (1.0-5) unstable; urgency=medium > >... > >* Convert to dh-r. > > Incidentally, this implies that r-cran-arm is a Depends.

Bug#881225: stretch update for wicd

Hi Adrian, Adrian Bunk wrote: > >* Replace dependencies on "net-tools | ethtool" and "net-tools | > > iproute2" in wicd-daemon with a hard dependency on net-tools and > > suggesting ethtool and iproute2 in python-wicd. Thanks to Neels > > Hofmeyr for the bug report. (Closes:

Bug#877433: stretch update for r-cran-mi

On Sun, Oct 01, 2017 at 09:39:04PM +, Debian Bug Tracking System wrote: >... > r-cran-mi (1.0-5) unstable; urgency=medium >... >* Convert to dh-r. > Incidentally, this implies that r-cran-arm is a Depends. (Closes: > #877433) >... Thanks a lot for fixing this bug for unstable. It

Processed: tagging 870289

Processing commands for cont...@bugs.debian.org: > tags 870289 + buster sid Bug #870289 {Done: Jameson Graef Rollins } [xapers] xapers: Must depend on python-pybtex Added tag(s) buster and sid. > thanks Stopping processing here. Please contact me if you need

Bug#892849: cura: Exception while launching cura

Package: cura Version: 3.1.0-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, While laaunching cura, I get the following: Error in sys.excepthook: Traceback (most recent call last): File "", line 983, in _find_and_load File "", line

Bug#881225: stretch update for wicd

On Sat, Nov 11, 2017 at 12:09:03AM +, Debian Bug Tracking System wrote: >... > wicd (1.7.4+tb2-5) unstable; urgency=medium >... >* Replace dependencies on "net-tools | ethtool" and "net-tools | > iproute2" in wicd-daemon with a hard dependency on net-tools and > suggesting

Bug#889740: stretch update for xmotd

On Sun, Feb 18, 2018 at 09:51:05AM +, Debian Bug Tracking System wrote: >... > xmotd (1.17.3b-10) unstable; urgency=medium > . >* debian/patches/bugfix/fix-warnings-hardening-build.patch: > - Fix most compile time warnings and avoid crash with hardening >flags

Bug#886044: syncmaildir: raising severity of gconf dependency bug

Control: tag -1 + patch On Mon, 12 Mar 2018 01:24:02 -0400, Jeremy Bicha wrote: > Please try to port your package away from gconf. Otherwise, please > consider requesting that your package be removed from Debian to help us > complete this goal. Looking at the ChangeLog and the git history, it

Processed: Re: Bug#886044: syncmaildir: raising severity of gconf dependency bug

Processing control commands: > tag -1 + patch Bug #886044 [src:syncmaildir] syncmaildir: Depends on gconf Added tag(s) patch. -- 886044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug #892723 in dehydrated marked as pending

Processing control commands: > tag -1 pending Bug #892723 [dehydrated] dehydrated: Dehydrated broken in stable due to unhandled redirect Added tag(s) pending. -- 892723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892723 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#892723: Bug #892723 in dehydrated marked as pending

Control: tag -1 pending Hello, Bug #892723 in dehydrated 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:

Processed: Re: Bug#892844: [libreoffice-impress] Impress cant be use

Processing commands for cont...@bugs.debian.org: > severity 892844 important Bug #892844 [libreoffice-impress] [libreoffice-impress] Impress cant be use Severity set to 'important' from 'grave' > tag 892844 + moreinfo Bug #892844 [libreoffice-impress] [libreoffice-impress] Impress cant be use

Bug#892844: [libreoffice-impress] Impress cant be use

Package: libreoffice-impress Version: 1:6.0.2-1+b1 Severity: grave --- Please enter the report below this line. --- Impress just can’t be use … slow as a rock. It especially start when i try to use some template/ master page feature.  after that i can’t do anything instead of kill -9 the process

Processed: your mail

Processing commands for cont...@bugs.debian.org: > found 892723 0.3.1-3 Bug #892723 [dehydrated] dehydrated: Dehydrated broken in stable due to unhandled redirect Marked as found in versions dehydrated/0.3.1-3. > -- Stopping processing here. Please contact me if you need assistance. -- 892723:

Bug#888123: marked as done (ruby-crack: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime)

Your message dated Tue, 13 Mar 2018 15:23:08 + with message-id and subject line Bug#888123: fixed in ruby-safe-yaml 1.0.4-2 has caused the Debian Bug report #888123, regarding ruby-crack: FTBFS on ruby2.5: uninitialized constant

Bug#888194: marked as done (ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime)

Your message dated Tue, 13 Mar 2018 15:23:08 + with message-id and subject line Bug#888123: fixed in ruby-safe-yaml 1.0.4-2 has caused the Debian Bug report #888123, regarding ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant

Bug#892833: marked as done (gpaste: Update dependencies for mutter transition)

Your message dated Tue, 13 Mar 2018 15:20:48 + with message-id and subject line Bug#892833: fixed in gpaste 3.26.0-5 has caused the Debian Bug report #892833, regarding gpaste: Update dependencies for mutter transition to be marked as done. This means

Processed: Bug#892131: gem2deb: generates spurious dependencies on ruby

Processing control commands: > severity -1 serious Bug #892131 [gem2deb] gem2deb: generates spurious dependencies on ruby Severity set to 'serious' from 'important' -- 892131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892131 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: limit source to gpaste, tagging 892833

Processing commands for cont...@bugs.debian.org: > limit source gpaste Limiting to bugs with field 'source' containing at least one of 'gpaste' Limit currently set to 'source':'gpaste' > tags 892833 + pending Bug #892833 [src:gpaste] gpaste: Update dependencies for mutter transition Added tag(s)

Bug#892757: marked as done (openstack-trove FTBFS: FAIL: common.test_context.TestTroveContext.test_create_with_bogus)

Your message dated Tue, 13 Mar 2018 15:16:36 +0100 with message-id <12c4-efd3-a163-8acf-99239af3f...@debian.org> and subject line Re: Bug#892757: openstack-trove FTBFS: FAIL: common.test_context.TestTroveContext.test_create_with_bogus has caused the Debian Bug report #892757, regarding

Bug#888135: marked as done (ruby-lapack: FTBFS on ruby2.5: `dirname': no implicit conversion of nil into String)

Your message dated Tue, 13 Mar 2018 22:58:43 +0900 with message-id <20180313135843.ga3...@lilith.infoblue.home> and subject line Re: ruby-lapack: FTBFS on ruby2.5: `dirname': no implicit conversion of nil into String has caused the Debian Bug report #888135, regarding ruby-lapack: FTBFS on

Bug#888123: Bug #888123 in ruby-safe-yaml marked as pending

Control: tag -1 pending Hello, Bug #888123 in ruby-safe-yaml 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:

Processed: Bug #888123 in ruby-safe-yaml marked as pending

Processing control commands: > tag -1 pending Bug #888123 [src:ruby-safe-yaml] ruby-crack: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime Added

Bug#824628: marked as done (golang-metrics-dev and golang-github-rcrowley-go-metrics-dev: error when trying to install together)

Your message dated Tue, 13 Mar 2018 13:50:07 + with message-id and subject line Bug#824628: fixed in golang-github-rcrowley-go-metrics 0.0~git20180125.8732c61-2 has caused the Debian Bug report #824628, regarding golang-metrics-dev and

Bug#892833: gpaste: Update dependencies for mutter transition

Source: gpaste Version: 3.26.0-4 Severity: serious Tags: patch Please build gpaste against libmutter-2-dev for the ongoing mutter 3.28 transition. Ubuntu has a diff you can use with trivial modification: https://launchpad.net/ubuntu/+source/gpaste/3.26.0-4ubuntu1 Please do this upload now with

Processed: Actually execute the reassign

Processing commands for cont...@bugs.debian.org: > reassign 891450 python-coverage 4.5+dfsg.1-3 Bug #891450 [src:custodia] custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType Bug reassigned from package 'src:custodia' to 'python-coverage'. No

Bug#892831: ipsec-tools FTBFS with flex 2.6.4-6

Source: ipsec-tools Version: 1:0.8.2+20140711-10 Severity: serious Tags: patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ipsec-tools.html ... /bin/bash ../../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -D_GNU_SOURCE -include ../../src/include-glibc/glibc-bugs.h

Bug#892824: libtgvoip FTBFS on !amd64: symbol differences

Source: libtgvoip Version: 1.0.3-1 Severity: serious https://buildd.debian.org/status/package.php?p=libtgvoip=sid ... dh_makeshlibs -a -O--sourcedirectory=obj-aarch64-linux-gnu/Release dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below

Bug#892823: libtgvoip: baseline violation on i386

Source: libtgvoip Version: 1.0~git20170704.445433f-4 Severity: serious debian/patches/Modify-build-scripts.patch still sets -msse2. It shouldn't, it should just use the gcc defaults (which are SSE2 on amd64 and no SSE on i386).

Processed (with 1 error): forcibly merging 888123 892798

Processing commands for cont...@bugs.debian.org: > forcemerge 888123 892798 Bug #888123 [src:ruby-safe-yaml] ruby-crack: FTBFS on ruby2.5: uninitialized constant SafeYAML::Parse::Date::DateTime Bug #888194 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS on ruby2.5: uninitialized constant

Bug#880047: stretch update for postgrey

On 03/12/2018 07:03 PM, Adrian Bunk wrote: > On Sat, Nov 25, 2017 at 10:36:10AM +, Debian Bug Tracking System wrote: >> ... >> postgrey (1.36-5) unstable; urgency=medium >> . >>* debian/postgrey.init: create /var/run/postgrey if it >> does not exist, patch provided by Laurent

Bug#887856: they have backdated it to 20171117

Dear Julien, I tried the microcode today and this is what it says - ~$ apt-cache policy intel-microcode intel-microcode: Installed: 3.20180108.1+really20171117.1 Candidate: 3.20180108.1+really20171117.1 Version table: *** 3.20180108.1+really20171117.1 900 900

Bug#892812: [libdrm-radeon1] Periodic UI freezes

Package: libdrm-radeon1 Version: 2.4.90 Severity: serious --- Please enter the report below this line. --- I have been experiencing periodic general UI freezes since last reboot. UI (Gnome) freezes for 1 second or two every 30 seconds. This is extremely annoying and makes UI almost unusable.

Bug#892124: marked as done (389-ds-base: CVE-2018-1054: remote Denial of Service (DoS) via search filters in SetUnicodeStringFromUTF_8 in collate.c)

Your message dated Tue, 13 Mar 2018 10:05:09 + with message-id and subject line Bug#892124: fixed in 389-ds-base 1.3.7.10-1 has caused the Debian Bug report #892124, regarding 389-ds-base: CVE-2018-1054: remote Denial of Service (DoS) via search filters

Bug#891450: [Pkg-freeipa-devel] Bug#891450: custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

reassign 891450 python-coverage thanks On 25.02.2018 19:17, Adrian Bunk wrote: > Source: custodia > Version: 0.5.0-3 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/custodia.html > > ... > 67 passed, 43 skipped in 14.94 seconds >

Bug#892808: src:libthrust: cuda toolkit ships a newer version

Package: src:libthrust Version: 1.8.2-1 Severity: serious Unfortunately the github repository does not contain any newer releases, therefore src:nvidia-cuda-toolkit now builds an updated libthrust-dev (1.9.1) package in non-free. Let's make this RC to kick the outdated version out of testing.

Processed: Bug #892785 in zaqar-ui marked as pending

Processing control commands: > tag -1 pending Bug #892785 [src:zaqar-ui] zaqar-ui FTBFS: ImportError: No module named openstack_dashboard.test.settings Ignoring request to alter tags of bug #892785 to the same tags previously set -- 892785:

Bug#892785: Bug #892785 in zaqar-ui marked as pending

Control: tag -1 pending Hello, Bug #892785 in zaqar-ui 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:

Bug#892785: Bug #892785 in zaqar-ui marked as pending

Control: tag -1 pending Hello, Bug #892785 in zaqar-ui 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:

Processed: Bug #892785 in zaqar-ui marked as pending

Processing control commands: > tag -1 pending Bug #892785 [src:zaqar-ui] zaqar-ui FTBFS: ImportError: No module named openstack_dashboard.test.settings Added tag(s) pending. -- 892785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892785 Debian Bug Tracking System Contact

Bug#892652: marked as done (tj3 FTBFS with Ruby 2.5)

Your message dated Tue, 13 Mar 2018 07:49:23 + with message-id and subject line Bug#892652: fixed in tj3 3.6.0-5 has caused the Debian Bug report #892652, regarding tj3 FTBFS with Ruby 2.5 to be marked as done. This means that you claim that the problem

Bug#892801: kubernetes: CVE-2017-1002101: Volume security can be sidestepped with innocent emptyDir and subpath

Source: kubernetes Version: 1.7.7+dfsg-3 Severity: grave Tags: security upstream Forwarded: https://github.com/kubernetes/kubernetes/issues/60813 Hi, the following vulnerability was published for kubernetes, and fixed in v1.7.14 for 1.7.x. CVE-2017-1002101[0]: Volume security can be sidestepped