Bug#844034: marked as done (pbhoney: incompatible with blasr 5.x)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 07:19:02 + with message-id and subject line Bug#844034: fixed in pbsuite 15.8.24+dfsg-2 has caused the Debian Bug report #844034, regarding pbhoney: incompatible with blasr 5.x to be marked as done. This means that you claim that the problem has been dealt

Bug#844666: marked as done (libpam-ldap-186: regression: reads from the wrong conf file)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 06:48:52 + with message-id and subject line Bug#844666: fixed in libpam-ldap 186-2 has caused the Debian Bug report #844666, regarding libpam-ldap-186: regression: reads from the wrong conf file to be marked as done. This means that you claim that the probl

Bug#847969: marked as done (RFS: libpam-ldap/186-2)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 11:29:54 +0500 with message-id <20161229062954.o7g7k7p4awl4l...@belkar.wrar.name> and subject line Re: Bug#847969: RFS: libpam-ldap/186-2 has caused the Debian Bug report #847969, regarding RFS: libpam-ldap/186-2 to be marked as done. This means that you claim t

Bug#816394: marked as done (elfutils: FTBFS[!linux] with gcc-6: unused const, functions)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 06:03:29 + with message-id and subject line Bug#816394: fixed in elfutils 0.168-0.1 has caused the Debian Bug report #816394, regarding elfutils: FTBFS[!linux] with gcc-6: unused const, functions to be marked as done. This means that you claim that the prob

Bug#849499: marked as done (llvmlite: ERROR: test_get_host_cpu_features (llvmlite.tests.test_binding.TestMisc))

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 05:03:46 + with message-id and subject line Bug#849499: fixed in llvmlite 0.15.0+git20161228.95d8c7c-1 has caused the Debian Bug report #849499, regarding llvmlite: ERROR: test_get_host_cpu_features (llvmlite.tests.test_binding.TestMisc) to be marked as don

Bug#784115: marked as done (inn: incoming feed is garbled)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 05:03:29 + with message-id and subject line Bug#784115: fixed in inn 1:1.7.2q-45 has caused the Debian Bug report #784115, regarding inn: incoming feed is garbled to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#779745: marked as done (inn: Transition to libsystemd)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 05:03:29 + with message-id and subject line Bug#779745: fixed in inn 1:1.7.2q-45 has caused the Debian Bug report #779745, regarding inn: Transition to libsystemd to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#836788: marked as done (inn: not installable in sid)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 05:03:29 + with message-id and subject line Bug#836788: fixed in inn 1:1.7.2q-45 has caused the Debian Bug report #836788, regarding inn: not installable in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#843390: marked as done (gpick: FTBFS on kfreebsd, hurd: needs to be linked with -lexpat)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 03:03:29 + with message-id and subject line Bug#843390: fixed in gpick 0.2.5+git20161221-1 has caused the Debian Bug report #843390, regarding gpick: FTBFS on kfreebsd, hurd: needs to be linked with -lexpat to be marked as done. This means that you claim th

Bug#849455: marked as done (dput: gpgme reports “Invalid value” when checking signature)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 12:48:49 +1100 with message-id <20161229014844.nvwvh5lejl5yp...@benfinney.id.au> and subject line Re: Bug#849455: dput: gpgme reports “Invalid value” when checking signature has caused the Debian Bug report #849455, regarding dput: gpgme reports “Invalid value”

Bug#846404: marked as done (Missing dependency on glib introspection data)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:18:28 + with message-id and subject line Bug#846404: fixed in meld 3.16.4-1 has caused the Debian Bug report #846404, regarding Missing dependency on glib introspection data to be marked as done. This means that you claim that the problem has been dealt

Bug#812823: marked as done (utopia-documents: Segmentation fault on start)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:03:35 + with message-id and subject line Bug#812823: fixed in utopia-documents 3.0.0-1 has caused the Debian Bug report #812823, regarding utopia-documents: Segmentation fault on start to be marked as done. This means that you claim that the problem has

Bug#804807: marked as done (utopia-documents: FTBFS with swig 3.0)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:03:35 + with message-id and subject line Bug#804807: fixed in utopia-documents 3.0.0-1 has caused the Debian Bug report #804807, regarding utopia-documents: FTBFS with swig 3.0 to be marked as done. This means that you claim that the problem has been dea

Bug#828588: marked as done (utopia-documents: FTBFS with openssl 1.1.0)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:03:35 + with message-id and subject line Bug#828588: fixed in utopia-documents 3.0.0-1 has caused the Debian Bug report #828588, regarding utopia-documents: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has bee

Bug#774704: marked as done (utopia-documents: constantly keeps the CPU busy)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:03:35 + with message-id and subject line Bug#774704: fixed in utopia-documents 3.0.0-1 has caused the Debian Bug report #774704, regarding utopia-documents: constantly keeps the CPU busy to be marked as done. This means that you claim that the problem ha

Bug#816813: marked as done ([utopia-documents] Qt4's WebKit removal)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 01:03:35 + with message-id and subject line Bug#816813: fixed in utopia-documents 3.0.0-1 has caused the Debian Bug report #816813, regarding [utopia-documents] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been d

Bug#849561: marked as done (libopendht-dev: Missing dependency on libmsgpack-dev)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 22:48:56 + with message-id and subject line Bug#849561: fixed in opendht 1.2.1~dfsg1-8 has caused the Debian Bug report #849561, regarding libopendht-dev: Missing dependency on libmsgpack-dev to be marked as done. This means that you claim that the problem

Bug#848271: marked as done (docbook-defguide FTBFS in stretch due to missing docbook-ebnf)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 00:46:09 +0200 with message-id <20161228224609.plqwwi3mm6ukj2bq@localhost> and subject line docbook-ebnf is back in testing has caused the Debian Bug report #848271, regarding docbook-defguide FTBFS in stretch due to missing docbook-ebnf to be marked as done. Th

Bug#849449: marked as done (jackson-datatype-guava: FTBFS: guava/ser/TableSerializer.java:[92,30] reference to construct is ambiguous)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 22:48:46 + with message-id and subject line Bug#849449: fixed in jackson-datatype-guava 2.7.3-2 has caused the Debian Bug report #849449, regarding jackson-datatype-guava: FTBFS: guava/ser/TableSerializer.java:[92,30] reference to construct is ambiguous to

Bug#843796: marked as done (civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/bower_components/jquery-ui/themes/smoothness/images is a directory)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 22:30:42 + with message-id and subject line Bug#843796: fixed in civicrm 4.7.14+dfsg-1 has caused the Debian Bug report #843796, regarding civicrm: FTBFS: dh_linktree: link destination debian/civicrm-common/usr/share/civicrm/bower_components/jquery-ui/theme

Bug#847324: marked as done (civicrm: Build-Depends on packages to be removed from Debian archive)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 22:30:42 + with message-id and subject line Bug#847324: fixed in civicrm 4.7.14+dfsg-1 has caused the Debian Bug report #847324, regarding civicrm: Build-Depends on packages to be removed from Debian archive to be marked as done. This means that you claim t

Bug#730965: marked as done (htmlunit: FTBFS: Reason: Cannot find parent: org.apache.james:apache-mime4j-project )

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 22:31:45 + with message-id and subject line Bug#730965: fixed in htmlunit 2.8-2 has caused the Debian Bug report #730965, regarding htmlunit: FTBFS: Reason: Cannot find parent: org.apache.james:apache-mime4j-project to be marked as done. This means that y

Bug#849479: marked as done (tigervnc: CVE-2014-8240: integer overflow flaw, leading to a heap-based buffer overflow in screen size handling)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 23:05:35 +0100 with message-id and subject line Was corrected in first version uploaded has caused the Debian Bug report #849479, regarding tigervnc: CVE-2014-8240: integer overflow flaw, leading to a heap-based buffer overflow in screen size handling to be ma

Bug#849553: marked as done (RFS: python-coards/1.0.5-1 [ITP])

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:27:01 + with message-id <1482960421.1926.4.ca...@gmail.com> and subject line has caused the Debian Bug report #849553, regarding RFS: python-coards/1.0.5-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#849560: marked as done (RFS: python-imageio/2.1.1+ds1-1 [ITP])

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:26:22 + with message-id <1482960382.1926.3.ca...@gmail.com> and subject line has caused the Debian Bug report #849560, regarding RFS: python-imageio/2.1.1+ds1-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. I

Processed: closing 598004

2016-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 598004 0.95-1 Bug #598004 [pitivi] pitivi: needs gnonlin 0.10.16 Marked as fixed in versions pitivi/0.95-1. Bug #598004 [pitivi] pitivi: needs gnonlin 0.10.16 Marked Bug as done > thanks Stopping processing here. Please contact me if you ne

Bug#844753: marked as done (vorbis-java FTBFS in stretch due to missing tika)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:08:12 + with message-id and subject line Bug#844753: fixed in vorbis-java 0.8-2 has caused the Debian Bug report #844753, regarding vorbis-java FTBFS in stretch due to missing tika to be marked as done. This means that you claim that the problem has been

Bug#843754: marked as done (Updating the libautobox-core-perl Uploaders list)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:05:30 + with message-id and subject line Bug#843754: fixed in libautobox-core-perl 1.33-1 has caused the Debian Bug report #843754, regarding Updating the libautobox-core-perl Uploaders list to be marked as done. This means that you claim that the proble

Bug#849453: marked as done (python3-swiftclient: Depends on not installed "futures".)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:07:19 + with message-id and subject line Bug#849453: fixed in python-swiftclient 1:3.1.0-3 has caused the Debian Bug report #849453, regarding python3-swiftclient: Depends on not installed "futures". to be marked as done. This means that you claim that t

Bug#844841: marked as done (jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:05:12 + with message-id and subject line Bug#844841: fixed in jruby-maven-plugins 1.1.5+ds1-1 has caused the Debian Bug report #844841, regarding jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecif

Bug#849529: marked as done (icedove: Icedove closes segfaults randomly while browsing mails. Started from clii to see error, only segmentation fault shows with no obvious additional information)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:44:50 +0100 with message-id <20161228204450.daen5y4ier5zs...@x201s.cruise.homelinux.net> and subject line Re: Bug#849529: icedove: Icedove closes segfaults randomly while browsing mails. Started from clii to see error, only segmentation fault shows with no o

Bug#849573: marked as done (auto-backports should not abort on error)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 20:58:53 +0100 with message-id <20161228195853.gg2...@torres.zugschlus.de> and subject line Re: auto-backports should not abort on error has caused the Debian Bug report #849573, regarding auto-backports should not abort on error to be marked as done. This means

Bug#628748: marked as done (typo correction)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 19:34:35 + with message-id and subject line Bug#628748: fixed in u3-tool 0.3-2 has caused the Debian Bug report #628748, regarding typo correction to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#729312: marked as done (u3-tool: Segmentation fault upon zero-size CD-ROM)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 19:34:35 + with message-id and subject line Bug#729312: fixed in u3-tool 0.3-2 has caused the Debian Bug report #729312, regarding u3-tool: Segmentation fault upon zero-size CD-ROM to be marked as done. This means that you claim that the problem has been de

Bug#848547: marked as done (ITA: u3-tool -- tool for controlling the special features of a U3 USB flash disk)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 19:34:35 + with message-id and subject line Bug#848547: fixed in u3-tool 0.3-2 has caused the Debian Bug report #848547, regarding ITA: u3-tool -- tool for controlling the special features of a U3 USB flash disk to be marked as done. This means that you cl

Bug#599167: marked as done (u3-tool: Typographical errors)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 19:34:35 + with message-id and subject line Bug#599167: fixed in u3-tool 0.3-2 has caused the Debian Bug report #599167, regarding u3-tool: Typographical errors to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#738912: marked as done (ITA: cadubi -- Creative ASCII Drawing Utility By Ian)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 19:33:30 + with message-id and subject line Bug#738912: fixed in cadubi 1.3.3-1 has caused the Debian Bug report #738912, regarding ITA: cadubi -- Creative ASCII Drawing Utility By Ian to be marked as done. This means that you claim that the problem has bee

Bug#849563: marked as done (Please enable lz4 support)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 18:19:04 + with message-id and subject line Bug#849563: fixed in openvpn 2.4.0-2 has caused the Debian Bug report #849563, regarding Please enable lz4 support to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#841048: marked as done (zsh: temporarily removes symlink /usr/bin/zsh on upgrade)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 18:03:47 + with message-id and subject line Bug#841048: fixed in zsh 5.3.1-1 has caused the Debian Bug report #841048, regarding zsh: temporarily removes symlink /usr/bin/zsh on upgrade to be marked as done. This means that you claim that the problem has be

Bug#821393: marked as done (/usr/share/applications/display-im6.desktop has wrong Icon=)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 17:24:43 +0100 with message-id <6682735.UmA4GStWXN@portable2015-bastien> and subject line Done: /usr/share/applications/display-im6.desktop has wrong Icon= has caused the Debian Bug report #821393, regarding /usr/share/applications/display-im6.desktop has wrong

Bug#845650: marked as done (imagemagick: Shortcuts ending with %f does not work)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 17:21:49 +0100 with message-id <2904854.0uUgtbWkqP@portable2015-bastien> and subject line Done: imagemagick: Shortcuts ending with %f does not work has caused the Debian Bug report #845650, regarding imagemagick: Shortcuts ending with %f does not work to be marke

Bug#844594: marked as done (imagemagick: Artefacts running -sharpen on CMYK images)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 17:22:53 +0100 with message-id <3700925.9tSlqdMfdr@portable2015-bastien> and subject line Done: imagemagick: Artefacts running -sharpen on CMYK images has caused the Debian Bug report #844594, regarding imagemagick: Artefacts running -sharpen on CMYK images to be

Bug#804738: marked as done (libre: FTBFS on kFreeBSD: missing ar flags, dlsym (-ldl))

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 16:18:35 + with message-id and subject line Bug#804738: fixed in libre 0.5.0-3 has caused the Debian Bug report #804738, regarding libre: FTBFS on kFreeBSD: missing ar flags, dlsym (-ldl) to be marked as done. This means that you claim that the problem has

Processed: bug has gone away

2016-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 678367 Bug #678367 [src:refpolicy] dirmngr: please label /var/run/dirmngr for SE Linux Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 678367: http://bugs.debian.org/cgi-bin/bugreport.cgi?

Bug#849535: marked as done (tnat64: ťešť büĝ řéṕóŕť)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 16:37:05 +0100 with message-id and subject line Re: Bug#849535: Acknowledgement (tnat64: ťešť büĝ řéṕóŕť) has caused the Debian Bug report #849535, regarding tnat64: ťešť büĝ řéṕóŕť to be marked as done. This means that you claim that the problem has been deal

Bug#697814: marked as done (selinux-policy-default: exim4 and bitlbee want access to sysctl_crypto_t)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:33:51 + with message-id and subject line Bug#697814: fixed in refpolicy 2:2.20161023.1-5 has caused the Debian Bug report #697814, regarding selinux-policy-default: exim4 and bitlbee want access to sysctl_crypto_t to be marked as done. This means that y

Bug#734192: marked as done (selinux-policy-default: Context unconfined_u:unconfined_r:mono_t:s0-s0:c0.c1023 would be invalid if enforcing)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:33:51 + with message-id and subject line Bug#734192: fixed in refpolicy 2:2.20161023.1-5 has caused the Debian Bug report #734192, regarding selinux-policy-default: Context unconfined_u:unconfined_r:mono_t:s0-s0:c0.c1023 would be invalid if enforcing to

Bug#757994: marked as done (selinux-policy-default: Installing x11-common fails when SELinux is set to enforcing)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:33:51 + with message-id and subject line Bug#757994: fixed in refpolicy 2:2.20161023.1-5 has caused the Debian Bug report #757994, regarding selinux-policy-default: Installing x11-common fails when SELinux is set to enforcing to be marked as done. This

Bug#619855: marked as done (selinux-policy-default: avc denial errors for munin plugins memory and if_)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:33:51 + with message-id and subject line Bug#619855: fixed in refpolicy 2:2.20161023.1-5 has caused the Debian Bug report #619855, regarding selinux-policy-default: avc denial errors for munin plugins memory and if_ to be marked as done. This means that

Bug#619979: marked as done (selinux-policy-default: avc denial errors in rsync for fifos and unix sockets when using rsync_export_all_ro)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:33:51 + with message-id and subject line Bug#619979: fixed in refpolicy 2:2.20161023.1-5 has caused the Debian Bug report #619979, regarding selinux-policy-default: avc denial errors in rsync for fifos and unix sockets when using rsync_export_all_ro to b

Bug#848771: marked as done (numexpr: FTBFS: Test failures)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:05:18 + with message-id and subject line Bug#848771: fixed in numexpr 2.6.1-3 has caused the Debian Bug report #848771, regarding numexpr: FTBFS: Test failures to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#849208: marked as done (Nvidia driver does not use DPMS)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 15:47:57 +0100 with message-id <1482936477.23920.0.ca...@gmail.com> and subject line Re: Bug#849208: Nvidia driver does not use DPMS has caused the Debian Bug report #849208, regarding Nvidia driver does not use DPMS to be marked as done. This means that you cla

Bug#847041: marked as done (ImportError: cannot import name is_windows)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 09:35:32 -0500 with message-id <1715234.vsYvlhcqzc@kitterma-e6430> and subject line Bug should be closed has caused the Debian Bug report #847041, regarding ImportError: cannot import name is_windows to be marked as done. This means that you claim that the probl

Bug#849451: marked as done (opendnssec-signer: hardcodes dependency on libldns1)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:49:17 + with message-id and subject line Bug#849451: fixed in opendnssec 1:2.0.3-5 has caused the Debian Bug report #849451, regarding opendnssec-signer: hardcodes dependency on libldns1 to be marked as done. This means that you claim that the problem ha

Bug#847960: marked as done (qemu: CVE-2016-9921 CVE-2016-9922)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847960: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847960, regarding qemu: CVE-2016-9921 CVE-2016-9922 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#847381: marked as done (qemu: CVE-2016-9845: display: virtio-gpu-3d: information leakage in virgl_cmd_get_capset_info)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847381: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847381, regarding qemu: CVE-2016-9845: display: virtio-gpu-3d: information leakage in virgl_cmd_get_capset_info to be marked as done. This

Bug#847496: marked as done (qemu: CVE-2016-9913 CVE-2016-9914 CVE-2016-9915 CVE-2016-9916)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847496: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847496, regarding qemu: CVE-2016-9913 CVE-2016-9914 CVE-2016-9915 CVE-2016-9916 to be marked as done. This means that you claim that the pro

Bug#846797: marked as done (qemu: CVE-2016-9776: net: mcf_fec: infinite loop while receiving data in mcf_fec_receive)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#846797: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #846797, regarding qemu: CVE-2016-9776: net: mcf_fec: infinite loop while receiving data in mcf_fec_receive to be marked as done. This means

Bug#847957: marked as done (qemu: CVE-2016-9923: char: use after free issue in char backend)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847957: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847957, regarding qemu: CVE-2016-9923: char: use after free issue in char backend to be marked as done. This means that you claim that the p

Bug#847400: marked as done (qemu: CVE-2016-9908: display: virtio-gpu-3d: information leakage in virgl_cmd_get_capset)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847400: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847400, regarding qemu: CVE-2016-9908: display: virtio-gpu-3d: information leakage in virgl_cmd_get_capset to be marked as done. This means

Bug#844361: marked as done (qemu: Upgraded from 2.6 to 2.7. Win 2008 R2 machine crasches during boot. I can see "qemu-system-x86_64: pci_get_msi_message: unknown interrupt type" in libvirt log.)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#844361: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #844361, regarding qemu: Upgraded from 2.6 to 2.7. Win 2008 R2 machine crasches during boot. I can see "qemu-system-x86_64: pci_get_msi_messa

Bug#847951: marked as done (qemu: CVE-2016-9911: usb: ehci: memory leakage in ehci_init_transfer)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847951: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847951, regarding qemu: CVE-2016-9911: usb: ehci: memory leakage in ehci_init_transfer to be marked as done. This means that you claim that

Bug#847953: marked as done (qemu: CVE-2016-9907: usb: redirector: memory leakage when destroying redirector)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847953: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847953, regarding qemu: CVE-2016-9907: usb: redirector: memory leakage when destroying redirector to be marked as done. This means that you

Bug#840948: marked as done (qemu: CVE-2016-8668: net: OOB buffer access in rocker switch emulation)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840948: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840948, regarding qemu: CVE-2016-8668: net: OOB buffer access in rocker switch emulation to be marked as done. This means that you claim tha

Bug#847382: marked as done (qemu: CVE-2016-9846: display: virtio-gpu: memory leakage while updating cursor)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847382: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847382, regarding qemu: CVE-2016-9846: display: virtio-gpu: memory leakage while updating cursor to be marked as done. This means that you

Bug#840236: marked as done (qemu: CVE-2016-7995: usb: hcd-ehci: memory leak in ehci_process_itd)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840236: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840236, regarding qemu: CVE-2016-7995: usb: hcd-ehci: memory leak in ehci_process_itd to be marked as done. This means that you claim that t

Bug#841955: marked as done (qemu: CVE-2016-8910: net: rtl8139: infinite loop while transmit in C+ mode)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#841955: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #841955, regarding qemu: CVE-2016-8910: net: rtl8139: infinite loop while transmit in C+ mode to be marked as done. This means that you clai

Bug#839835: marked as done (qemu: CVE-2016-7908: net: Infinite loop in mcf_fec_do_tx)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#839835: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #839835, regarding qemu: CVE-2016-7908: net: Infinite loop in mcf_fec_do_tx to be marked as done. This means that you claim that the problem

Bug#840945: marked as done (qemu: CVE-2016-8669: char: divide by zero error in serial_update_parameters)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840945: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840945, regarding qemu: CVE-2016-8669: char: divide by zero error in serial_update_parameters to be marked as done. This means that you cla

Bug#847391: marked as done (qemu: CVE-2016-9912: display: virtio-gpu: memory leakage when destroying gpu resource)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#847391: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #847391, regarding qemu: CVE-2016-9912: display: virtio-gpu: memory leakage when destroying gpu resource to be marked as done. This means th

Bug#841950: marked as done (qemu: CVE-2016-8909: audio: intel-hda: infinite loop in processing dma buffer stream)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#841950: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #841950, regarding qemu: CVE-2016-8909: audio: intel-hda: infinite loop in processing dma buffer stream to be marked as done. This means tha

Bug#842463: marked as done (qemu: Various 9ps security issues (CVE-2016-9102 CVE-2016-9103 CVE-2016-9104 CVE-2016-9105 CVE-2016-9106))

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#842463: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #842463, regarding qemu: Various 9ps security issues (CVE-2016-9102 CVE-2016-9103 CVE-2016-9104 CVE-2016-9105 CVE-2016-9106) to be marked as

Bug#837191: marked as done (CVE-2016-7156: scsi: pvscsi: infinite loop when building SG list)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#837191: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #837191, regarding CVE-2016-7156: scsi: pvscsi: infinite loop when building SG list to be marked as done. This means that you claim that the

Bug#840340: marked as done (qemu: CVE-2016-8578)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840340: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840340, regarding qemu: CVE-2016-8578 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#833619: marked as done (/usr/bin/qemu-system-x86_64: Option -memory doesn't work. But -m do.)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#833619: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #833619, regarding /usr/bin/qemu-system-x86_64: Option -memory doesn't work. But -m do. to be marked as done. This means that you claim that

Bug#840341: marked as done (qemu: CVE-2016-8577: 9pfs: host memory leakage in v9fs_read)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840341: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840341, regarding qemu: CVE-2016-8577: 9pfs: host memory leakage in v9fs_read to be marked as done. This means that you claim that the probl

Bug#840343: marked as done (qemu: CVE-2016-8576: usb: xHCI: infinite loop vulnerability in xhci_ring_fetch)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840343: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840343, regarding qemu: CVE-2016-8576: usb: xHCI: infinite loop vulnerability in xhci_ring_fetch to be marked as done. This means that you

Bug#839695: marked as done (qemu: Please build qemu with –enable-gtk)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#839695: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #839695, regarding qemu: Please build qemu with –enable-gtk to be marked as done. This means that you claim that the problem has been dealt w

Bug#787112: marked as done (Add GlusterFS support to Qemu)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#775431: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #775431, regarding Add GlusterFS support to Qemu to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#840228: marked as done (qemu: CVE-2016-7994: virtio-gpu: memory leak in virtio_gpu_resource_create_2d)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#840228: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #840228, regarding qemu: CVE-2016-7994: virtio-gpu: memory leak in virtio_gpu_resource_create_2d to be marked as done. This means that you c

Bug#839834: marked as done (qemu: CVE-2016-7909: net: pcnet: infinite loop in pcnet_rdra_addr)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#839834: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #839834, regarding qemu: CVE-2016-7909: net: pcnet: infinite loop in pcnet_rdra_addr to be marked as done. This means that you claim that the

Bug#833162: marked as done (qemu-doc: backslashes eaten at build time; please make the build reproducible (shell))

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#833162: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #833162, regarding qemu-doc: backslashes eaten at build time; please make the build reproducible (shell) to be marked as done. This means th

Bug#813658: marked as done (Please enable virgl support)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#813658: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #813658, regarding Please enable virgl support to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#758189: marked as done (numa (libnuma) support is not enabled)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#758189: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #758189, regarding numa (libnuma) support is not enabled to be marked as done. This means that you claim that the problem has been dealt with

Bug#837316: marked as done (qemu: CVE-2016-7170: vmware_vga: OOB stack memory access when processing svga command)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#837316: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #837316, regarding qemu: CVE-2016-7170: vmware_vga: OOB stack memory access when processing svga command to be marked as done. This means th

Bug#775431: marked as done (qemu: please build with gluster/libgfapi support)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#775431: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #775431, regarding qemu: please build with gluster/libgfapi support to be marked as done. This means that you claim that the problem has been

Bug#819755: marked as done (qemu-user-static: "Temporary failure in name resolution" with qemu-{mips, mipsel}-static)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 13:35:00 + with message-id and subject line Bug#819755: fixed in qemu 1:2.8+dfsg-1 has caused the Debian Bug report #819755, regarding qemu-user-static: "Temporary failure in name resolution" with qemu-{mips, mipsel}-static to be marked as done. This means

Bug#703842: marked as done (dkms: consider adding dependency on lsb-release)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:21:53 +0800 with message-id and subject line fixed in version dkms/2.3-2 has caused the Debian Bug report #703842, regarding dkms: consider adding dependency on lsb-release to be marked as done. This means that you claim that the problem has been dealt with

Bug#837542: marked as done (mate-power-manager: segfault (infinite recursion) after changing brightness with brightness keys)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 14:07:18 +0100 with message-id <59c1bc26-4c68-a292-8245-4bf368f09...@kodafritt.se> and subject line Re: Bug#837542: mate-power-manager: segfault (infinite recursion) after changing brightness with brightness keys has caused the Debian Bug report #837542, regardi

Bug#560145: marked as done (steghide: unlean diff - steghide_0.5.1-9.diff contains compilation artifacts)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 10:55:16 -0200 with message-id and subject line has caused the Debian Bug report #560145, regarding steghide: unlean diff - steghide_0.5.1-9.diff contains compilation artifacts to be marked as done. This means that you claim that the problem has been dealt wi

Bug#593930: marked as done (steghide: /usr/share/man/man3/* generated iff doxygen is installed)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 10:55:16 -0200 with message-id and subject line has caused the Debian Bug report #593930, regarding steghide: /usr/share/man/man3/* generated iff doxygen is installed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#323015: marked as done (dput: make it possible to use gnupg2 instead of gnupg)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 23:27:06 +1100 with message-id <20161228122653.gweaqfxwxabli...@benfinney.id.au> and subject line Re: Bug#323015: dput: make it possible to use gnupg2 instead of gnupg has caused the Debian Bug report #323015, regarding dput: make it possible to use gnupg2 inste

Bug#782696: marked as done (dput: Please give a way to specify the path to the gpg(1) binary)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 23:27:06 +1100 with message-id <20161228122653.gweaqfxwxabli...@benfinney.id.au> and subject line Re: Bug#323015: dput: make it possible to use gnupg2 instead of gnupg has caused the Debian Bug report #323015, regarding dput: Please give a way to specify the pat

Processed: closing 835474

2016-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 835474 Bug #835474 [systemd] systemd: timesyncd does not sync time after resume from suspend (need to do so manually with timedatectl) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 8354

Bug#849484: marked as done (libchromaprint1 has circular Depends on libavformat57)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 11:48:24 + with message-id and subject line Bug#849347: fixed in chromaprint 1.4.1-2 has caused the Debian Bug report #849347, regarding libchromaprint1 has circular Depends on libavformat57 to be marked as done. This means that you claim that the problem h

Bug#849347: marked as done (libchromaprint1 has circular Depends on libavformat57)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 11:48:24 + with message-id and subject line Bug#849347: fixed in chromaprint 1.4.1-2 has caused the Debian Bug report #849347, regarding libchromaprint1 has circular Depends on libavformat57 to be marked as done. This means that you claim that the problem h

Bug#845416: marked as done (libstdc++-arm-none-eabi-newlib: Please update to 5.4.1)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 11:18:46 + with message-id and subject line Bug#845416: fixed in libstdc++-arm-none-eabi 9 has caused the Debian Bug report #845416, regarding libstdc++-arm-none-eabi-newlib: Please update to 5.4.1 to be marked as done. This means that you claim that the pr

Bug#849495: marked as done (python-crypto: CVE-2013-7459)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 11:03:34 + with message-id and subject line Bug#849495: fixed in python-crypto 2.6.1-7 has caused the Debian Bug report #849495, regarding python-crypto: CVE-2013-7459 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#847129: marked as done (kodi-pvr-vdr-vnsi: Repeating timer displayed as single timer in kodi)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 10:42:08 +0100 with message-id and subject line Re: Bug#847129: kodi-pvr-vdr-vnsi: Repeating timer displayed as single timer in kodi has caused the Debian Bug report #847129, regarding kodi-pvr-vdr-vnsi: Repeating timer displayed as single timer in kodi to be m

Bug#849263: marked as done (kodi-pvr-vdr-vnsi: New 17.beta needs a new API (again))

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 10:34:23 +0100 with message-id and subject line Re: Bug#849263: kodi-pvr-vdr-vnsi: New 17.beta needs a new API (again) has caused the Debian Bug report #849263, regarding kodi-pvr-vdr-vnsi: New 17.beta needs a new API (again) to be marked as done. This means t

  1   2   >