Bug#884136: marked as done (lilypond: CVE-2017-17523)

Your message dated Sat, 12 May 2018 21:20:39 + with message-id and subject line Bug#884136: fixed in lilypond 2.19.81+really-2.18.2-13 has caused the Debian Bug report #884136, regarding lilypond: CVE-2017-17523 to be marked as done. This means that you

Bug#884136: marked as done (lilypond: CVE-2017-17523)

Your message dated Fri, 11 May 2018 20:48:14 + with message-id and subject line Bug#884136: fixed in lilypond 2.19.81-1~exp2 has caused the Debian Bug report #884136, regarding lilypond: CVE-2017-17523 to be marked as done. This means that you claim that

Bug#884136: marked as done (lilypond: CVE-2017-17523)

Your message dated Fri, 11 May 2018 16:35:58 + with message-id and subject line Bug#884136: fixed in lilypond 2.18.2-13 has caused the Debian Bug report #884136, regarding lilypond: CVE-2017-17523 to be marked as done. This means that you claim that the

Bug#884136: marked as done (lilypond: CVE-2017-17523)

Your message dated Sun, 04 Feb 2018 13:38:14 + with message-id and subject line Bug#884136: fixed in lilypond 2.19.81-1~exp1 has caused the Debian Bug report #884136, regarding lilypond: CVE-2017-17523 to be marked as done. This means that you claim that

Bug#884136: marked as done (lilypond: CVE-2017-17523)

Your message dated Mon, 29 Jan 2018 21:07:27 + with message-id and subject line Bug#884136: fixed in lilypond 2.18.2-12 has caused the Debian Bug report #884136, regarding lilypond: CVE-2017-17523 to be marked as done. This means that you claim that the