Bug#907907: golang-google-cloud: FTBFS randomly (failing tests)

2019-04-14 Thread Stephen Gelman
FYI, unblock request filed as #927099. Stephen

Bug#907907: marked as done (golang-google-cloud: FTBFS randomly (failing tests))

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 05:18:33 + with message-id and subject line Bug#907907: fixed in golang-google-cloud 0.9.0-10 has caused the Debian Bug report #907907, regarding golang-google-cloud: FTBFS randomly (failing tests) to be marked as done. This means that you claim that the

Bug#927015: marked as done (node-serve-static: FTBFS (failing tests))

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 05:18:38 + with message-id and subject line Bug#927015: fixed in node-serve-static 1.6.4-3 has caused the Debian Bug report #927015, regarding node-serve-static: FTBFS (failing tests) to be marked as done. This means that you claim that the problem has

Processed: Bug #927015 in node-serve-static marked as pending

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #927015 [src:node-serve-static] node-serve-static: FTBFS (failing tests) Added tag(s) pending. -- 927015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#927015: Bug #927015 in node-serve-static marked as pending

2019-04-14 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #927015 in node-serve-static 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#907907: golang-google-cloud: FTBFS randomly (failing tests)

2019-04-14 Thread Stephen Gelman
> On Apr 14, 2019, at 4:04 PM, Santiago Vila wrote: > > Please, please, please, let us not release buster with packages > failing randomly like this. Santiago, I agree with you that this should not ship with this issue in buster and will upload a new release with your patch (and then request

Bug#923843: marked as done (redmine: Upgrade to Redmine 4.0.1-1 fails on post-installation)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 04:18:54 + with message-id and subject line Bug#923843: fixed in redmine 4.0.1-2 has caused the Debian Bug report #923843, regarding redmine: Upgrade to Redmine 4.0.1-1 fails on post-installation to be marked as done. This means that you claim that the

Bug#923891: marked as done (redmine: Cannot login after upgrade to 4.0.1-1)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 04:18:54 + with message-id and subject line Bug#923891: fixed in redmine 4.0.1-2 has caused the Debian Bug report #923891, regarding redmine: Cannot login after upgrade to 4.0.1-1 to be marked as done. This means that you claim that the problem has been

Bug#924110: redmine-plugin-local-avatars: fails to install: NoMethodError: undefined method `to_prepare' for ActionDispatch::Callbacks:Class

2019-04-14 Thread duck
Quack, This PR may help: https://github.com/ncoders/redmine_local_avatars/pull/21 There is a typo though: s/prepere/prepare/ You may wish to give it a try. At the moment I'm going to add a conflict on the current version from the redmine package to avoid migration failures. Regards. \_o<

Bug#926652: marked as done (python-trustme: FTBFS on all)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 03:03:35 + with message-id and subject line Bug#926652: fixed in python-trustme 0.4.0-3 has caused the Debian Bug report #926652, regarding python-trustme: FTBFS on all to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: golang-google-cloud: FTBFS randomly (failing tests)

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 907907 serious Bug #907907 [src:golang-google-cloud] golang-google-cloud: FTBFS randomly (failing tests) Severity set to 'serious' from 'important' > tags 907907 + patch Bug #907907 [src:golang-google-cloud] golang-google-cloud: FTBFS

Bug#926254: marked as done (ruby-websocket: needs Breaks+Replaces: ruby-websocket-parser (<= 1.0.0-1))

2019-04-14 Thread Debian Bug Tracking System
Your message dated Mon, 15 Apr 2019 00:35:53 + with message-id and subject line Bug#926254: fixed in ruby-websocket 1.2.8-2 has caused the Debian Bug report #926254, regarding ruby-websocket: needs Breaks+Replaces: ruby-websocket-parser (<= 1.0.0-1) to be marked as done. This means that you

Bug#888547: CVE-2017-1000190

2019-04-14 Thread Emmanuel Bourg
Le 14/04/2019 à 23:27, Markus Koschany a écrit : > Simple-xml is only required to build carrotsearch-randomizedtesting. It > is not a test-dependency though. > Apparently the removal makes no difference for lucene4.10. Indeed, because carrotsearch-randomizedtesting is just a test dependency of

Bug#834089: Bug #834089 in socklog marked as pending

2019-04-14 Thread Mathieu Mirmont
Control: tag -1 pending Hello, Bug #834089 in socklog 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 #834089 in socklog marked as pending

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #834089 [socklog-run] runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory Ignoring request to alter tags of bug #834089 to the same tags previously set -- 834089:

Processed: Bug #857208 in socklog marked as pending

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #857208 [src:socklog] socklog: building with -A doesn't put the changelog in usr/share/doc/socklog-run/changelog.Debian.gz Ignoring request to alter tags of bug #857208 to the same tags previously set -- 857208:

Bug#857208: Bug #857208 in socklog marked as pending

2019-04-14 Thread Mathieu Mirmont
Control: tag -1 pending Hello, Bug #857208 in socklog 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#888547: CVE-2017-1000190

2019-04-14 Thread Markus Koschany
Hi, Am 13.04.19 um 11:31 schrieb Ivo De Decker: [...] > It is possible to remove the test-dependency (probably by disabling the > tests)? That way simple-xml could be removed from buster. Even if we don't do > this for buster, it might be good to do this for bullseye anyway, if the > package

Processed: tagging 388141

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 388141 + buster-ignore Bug #388141 [www.debian.org] www.debian.org SPI copyright claim not legally valid until all contributors are contacted for relicensing Added tag(s) buster-ignore. > thanks Stopping processing here. Please contact me

Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Steinar H. Gunderson
severity 923773 normal retitle 923773 broken fstab entries stop logind sessions in X thanks On Sun, Apr 14, 2019 at 10:56:17PM +0200, Michael Biebl wrote: > Could you also please paste the output of > grep pam_systemd /etc/pam.d/* I think maybe I found it; it seems that there was a bad entry in

Processed: Re: Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 923773 normal Bug #923773 [libpam-systemd] logind sessions are ended immediately after login Severity set to 'normal' from 'grave' > retitle 923773 broken fstab entries stop logind sessions in X Bug #923773 [libpam-systemd] logind

Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Michael Biebl
Am 14.04.19 um 14:51 schrieb Steinar H. Gunderson: > On Sun, Apr 14, 2019 at 01:33:43PM +0200, Michael Biebl wrote: >> What's the output of >> reportbug --template systemd >> reportbug --template libpam-systemd > > Attaching. Hm, something is borked in the encoding, making the log a bit hard to

Processed: tagging 926279

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # new libcgroup will not be in buster, so this issue doesn't affect buster > tags 926279 + buster-ignore Bug #926279 [mininet] mininet: switch from cgroup-bin to cgroup-tools Added tag(s) buster-ignore. > thanks Stopping processing here. Please

Bug#908427: marked as done (nzbget depends on libjs-twitter-bootstrap that will not be in buster)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 21:46:00 +0200 with message-id <4b2bdcdf-b5b0-dac6-aba7-41ffc07a1...@warperbbs.de> and subject line Fixed in latest upload has caused the Debian Bug report #908427, regarding nzbget depends on libjs-twitter-bootstrap that will not be in buster to be marked as

Processed: Set severity

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #926735 [libparted2] Include upstream patch for extended partition size Severity set to 'serious' from 'normal' -- 926735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926735 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#918393: opensips FTBFS with MariaDB 10.3

2019-04-14 Thread Otto Kekäläinen
su 14. huhtik. 2019 klo 14.06 peter green (plugw...@p10link.net) kirjoitti: > > Could you please check if it is still valid and happening in Debian > unstable there has had several updates MariaDB client libraries / > connector C libraries recently? > > According to >

Bug#926952: sa-exim: Unbuildable/uninstallable in sid

2019-04-14 Thread Magnus Holmgren
fredag 12 april 2019 kl. 19:23:40 CEST skrev du: > The dlopen localscan patch in exim4 has been nonfunctional in unstable > for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 > unstable/26 Dec and buster/03 Jan). The issue only popped up end of > March on the upstream user support ML.

Bug#916375: [debian-mysql] Bug#916375: Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

2019-04-14 Thread Otto Kekäläinen
Control: severity important Severity: important > Can you still reproduce this with latest versions of MariaDB 10.3.13 > and mod_perl ? Downgrading severity since no more info has been provided in past month and there are no new reports that somebody would be affected.

Bug#921194: I have the same problem

2019-04-14 Thread Davide Lombardo
I have made the mistake of remove Amarok from my system and now when I try to install the packages with "apt" I get this output: "sudo apt install amarok Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean

Bug#926916: marked as done (python3-dotenv-cli: /usr/bin/dotenv is already provided by ruby-dotenv)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 16:33:33 + with message-id and subject line Bug#926916: fixed in dotenv-cli 1.0.2-1 has caused the Debian Bug report #926916, regarding python3-dotenv-cli: /usr/bin/dotenv is already provided by ruby-dotenv to be marked as done. This means that you claim

Processed: Bug #927065 in perlbrew marked as pending

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #927065 [perlbrew] perlbrew versions before 0.84 don't find perl release tarballs because of URL changes Added tag(s) pending. -- 927065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927065 Debian Bug Tracking System Contact

Bug#927065: Bug #927065 in perlbrew marked as pending

2019-04-14 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #927065 in perlbrew 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#927066: python-gdata: Should not ship with Buster

2019-04-14 Thread Dmitry Shachnev
Package: python-gdata Version: 2.0.18+dfsg1-2 Severity: serious Tags: buster sid I am uploader of python-gdata and my intention is that it should not be part of Debian Buster release. There are two main reasons for it: 1) It does not actually work anymore: Google has shut down most of gdata API

Processed: fixed 927065 in 0.84-1

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 927065 0.84-1 Bug #927065 [perlbrew] perlbrew versions before 0.84 don't find perl release tarballs because of URL changes Marked as fixed in versions perlbrew/0.84-1. > thanks Stopping processing here. Please contact me if you need

Bug#927065: perlbrew versions before 0.84 don't find perl release tarballs because of URL changes

2019-04-14 Thread gregor herrmann
Package: perlbrew Version: 0.71-1 Severity: grave Tags: patch upstream fixed-upstream Justification: renders package unusable Forwarded: https://github.com/gugod/App-perlbrew/pull/618 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 perlbrew downloads and builds perl. Due to changes in the CPAN

Bug#897975: [gdm3]

2019-04-14 Thread Iain Lane
Hi, Sorry for the delay. Niels pointed me at this bug, which is suspiciously similar to one we saw on Ubuntu around the same time ... On Wed, Jun 13, 2018 at 01:43:18PM +0200, rastersoft wrote: > After several tests, I started to suspect that the problem could be in the > firmware loading: my

Bug#917535: debian-archive-keyring: ftp-master key for buster

2019-04-14 Thread Ansgar Burchardt
Niels Thykier writes: > We need new archive signing keys for buster, so we can include them in > a debian-archive-keyring upload before the buster release. The two keys are prepared; I'm waiting for a few more signatures from other ftp masters. FWIW they will be: pub rsa4096 2019-04-14 [SC]

Bug#926350: marked as done (CAS middleware incompatible with Django >= 1.10)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 12:34:38 + with message-id and subject line Bug#926350: fixed in python-django-casclient 1.2.0-2.2 has caused the Debian Bug report #926350, regarding CAS middleware incompatible with Django >= 1.10 to be marked as done. This means that you claim that the

Processed: retitle 927057 1Gb of logs is too much

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 927057 1Gb of logs is too much Bug #927057 [matrix-synapse] matrix-synapse: logs are not rotated Changed Bug title to '1Gb of logs is too much' from 'matrix-synapse: logs are not rotated'. > End of message, stopping processing here.

Bug#927057: 1Gb of logs is too much

2019-04-14 Thread sergio
Really, I was wrong, logs are rotated by synapse itself. But it will produce 1Gb of log files in default configuration. Moreover very rapidly, as default loglevel is INFO. -- sergio.

Bug#927057: matrix-synapse: logs are not rotated

2019-04-14 Thread sergio
Package: matrix-synapse Version: 0.99.2-3 Severity: serious Justification: Policy 10.8 Dear Maintainer, https://www.debian.org/doc/debian-policy/ch-files.html Log files must be rotated occasionally so that they don’t grow indefinitely. The best way to do this is to install a log rotation

Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Michael Biebl
Control: tags -1 moreinfo unreproducible Doesn't look like libpam-systemd is properly installed > dbus-update-activation-environment: systemd --user not found, ignoring > --systemd argument > cinnamon-session[23689]: WARNING: t+0,00945s: Could not get session id for > session. Check that

Processed: Re: logind sessions are ended immediately after login

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo unreproducible Bug #923773 [libpam-systemd] logind sessions are ended immediately after login Added tag(s) moreinfo and unreproducible. -- 923773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923773 Debian Bug Tracking System Contact

Processed: your mail

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 914517 critical Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set Severity set to 'critical' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 914517:

Bug#918393: opensips FTBFS with MariaDB 10.3

2019-04-14 Thread peter green
Could you please check if it is still valid and happening in Debian unstable there has had several updates MariaDB client libraries / connector C libraries recently? According to https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/opensips.html it is still failing in the same

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

2019-04-14 Thread Sebastian Andrzej Siewior
On 2019-04-14 11:28:59 [+0100], Adam D. Barratt wrote: > In the interest of keeping things moving, please feel free to go ahead. thanks, uploaded. > Adam Sebastian

Bug#912187: ca-certificates-java: Wrong jvm options for armhf

2019-04-14 Thread Jochen Sprickerhof
Hi, * Markus Koschany [2019-01-28 20:22]: On Sun, 28 Oct 2018 22:53:56 +0100 =?UTF-8?Q?Gero_M=c3=bcller?= wrote: Package: ca-certificates-java Version: 20170531+nmu1 On armhf the server JVM is not available. But the postinst script assumes so and uses it to setup a temporary configuration

Bug#926389: marked as done (wget: CVE-2019-5953)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 10:33:17 + with message-id and subject line Bug#926389: fixed in wget 1.18-5+deb9u3 has caused the Debian Bug report #926389, regarding wget: CVE-2019-5953 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#921969: marked as done (CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 10:32:08 + with message-id and subject line Bug#921969: fixed in gpac 0.5.2-426-gc5ad4e4+dfsg5-3+deb9u1 has caused the Debian Bug report #921969, regarding CVE-2018-20760 CVE-2018-20761 CVE-2018-20762 CVE-2018-20763 to be marked as done. This means that

Bug#924965: marked as done (libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 10:32:11 + with message-id and subject line Bug#924965: fixed in libssh2 1.7.0-1+deb9u1 has caused the Debian Bug report #924965, regarding libssh2: CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861

Bug#926764: marked as done (spip: CVE-2019-11071: arbitrary code execution by any identified visitor)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 10:32:49 + with message-id and subject line Bug#926764: fixed in spip 3.1.4-4~deb9u2 has caused the Debian Bug report #926764, regarding spip: CVE-2019-11071: arbitrary code execution by any identified visitor to be marked as done. This means that you

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

2019-04-14 Thread Adam D. Barratt
Control: tags 919043 + confirmed On Sun, 2019-04-14 at 12:26 +0200, Sebastian Andrzej Siewior wrote: > On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote: > > On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote: > > > I'm proposing this attached debdiff. > > > For testing I

Bug#892526: marked as done (gpac: CVE-2018-7752: Stack buffer overflow in av_parsers.c)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 10:32:08 + with message-id and subject line Bug#892526: fixed in gpac 0.5.2-426-gc5ad4e4+dfsg5-3+deb9u1 has caused the Debian Bug report #892526, regarding gpac: CVE-2018-7752: Stack buffer overflow in av_parsers.c to be marked as done. This means that you

Bug#917485: Bug#919043: nmu: ckermit_302-5.3 (stretch)

2019-04-14 Thread Sebastian Andrzej Siewior
On 2019-04-13 22:25:19 [+0100], Adam D. Barratt wrote: > On Fri, 2019-02-15 at 00:04 +0100, Sebastian Andrzej Siewior wrote: > > I'm proposing this attached debdiff. > > For testing I compiled it against libssl1.0-dev 1.0.2j-5 and then > > upgraded to the version provided by the security

Bug#926567: marked as done (gmp-doc: does this package need to be updated to match gmp 6.1.2?)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 09:33:46 + with message-id and subject line Bug#926567: fixed in gmp-doc 6.1.2-1 has caused the Debian Bug report #926567, regarding gmp-doc: does this package need to be updated to match gmp 6.1.2? to be marked as done. This means that you claim that the

Bug#924273: marked as done (makehuman: Always fail in export)

2019-04-14 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2019 09:04:49 + with message-id and subject line Bug#924273: fixed in makehuman 1.1.1-1.2 has caused the Debian Bug report #924273, regarding makehuman: Always fail in export to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 923773 libpam-systemd Bug #923773 [libpam-systemd] logind sessions are ended immediately after login Ignoring request to reassign bug #923773 to the same package > severity 923773 grave Bug #923773 [libpam-systemd] logind sessions are

Processed: Re: Bug#923773: logind sessions are ended immediately after login

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 923773 libpam-systemd Bug #923773 [lightdm] logind sessions are ended immediately after login Bug reassigned from package 'lightdm' to 'libpam-systemd'. No longer marked as found in versions lightdm/1.26.0-4. Ignoring request to alter

Processed: Bug #924273 in makehuman marked as pending

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #924273 [makehuman] makehuman: Always fail in export Added tag(s) pending. -- 924273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#924273: Bug #924273 in makehuman marked as pending

2019-04-14 Thread Jochen Sprickerhof
Control: tag -1 pending Hello, Bug #924273 in makehuman 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#883872: Bumping Severity

2019-04-14 Thread Jochen Sprickerhof
Hi Wilmer, I've prepared an new copyright file, could you please review it? Cheers Jochen Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Files: * Copyright: 1998-1999, Adam Fritzler 2002-2006, Jelmer Vernooij 2006, Marijn

Processed: unblock: cross-gcc/230

2019-04-14 Thread Debian Bug Tracking System
Processing control commands: > close 925950 Bug #925950 [cross-gcc-dev] patches no longer apply for gcc-8 and gcc-9 Marked Bug as done -- 925950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925950 927051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927051 Debian Bug Tracking System

Processed: found 927029 in 1.4~hg15916-1

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 927029 1.4~hg15916-1 Bug #927029 [graphicsmagick] graphicsmagick: Multiple heap-based buffer over-reads Marked as found in versions graphicsmagick/1.4~hg15916-1. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: found 927029 in 1.4~hg15916-2

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 927029 1.4~hg15916-2 Bug #927029 [graphicsmagick] graphicsmagick: Multiple heap-based buffer over-reads Marked as found in versions graphicsmagick/1.4~hg15916-2. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: tagging 927029

2019-04-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 927029 + upstream fixed-upstream Bug #927029 [graphicsmagick] graphicsmagick: Multiple heap-based buffer over-reads Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. --