Bug#945147: marked as done (kmail: Printing produces a blank page or a blank pdf file)

Your message dated Fri, 22 Nov 2019 18:26:20 -0500 with message-id <11253523.QeEtE2Lfbl@t450> and subject line Closing [kmail] blank page on print preview has caused the Debian Bug report #919504, regarding kmail: Printing produces a blank page or a blank pdf file to be marked as done. This

Bug#931860: marked as done (kmail print empty page)

Your message dated Fri, 22 Nov 2019 18:26:20 -0500 with message-id <11253523.QeEtE2Lfbl@t450> and subject line Closing [kmail] blank page on print preview has caused the Debian Bug report #919504, regarding kmail print empty page to be marked as done. This means that you claim that the problem

Bug#933278: marked as done (kmail: Kmail printing Mails prints blank pages)

Your message dated Fri, 22 Nov 2019 18:26:20 -0500 with message-id <11253523.QeEtE2Lfbl@t450> and subject line Closing [kmail] blank page on print preview has caused the Debian Bug report #919504, regarding kmail: Kmail printing Mails prints blank pages to be marked as done. This means that you

Bug#919504: marked as done ([kmail] blank page on print preview)

Your message dated Fri, 22 Nov 2019 18:26:20 -0500 with message-id <11253523.QeEtE2Lfbl@t450> and subject line Closing [kmail] blank page on print preview has caused the Debian Bug report #919504, regarding [kmail] blank page on print preview to be marked as done. This means that you claim that

Bug#929286: marked as done (kmail - can not print mails (get no content))

Your message dated Fri, 22 Nov 2019 18:26:20 -0500 with message-id <11253523.QeEtE2Lfbl@t450> and subject line Closing [kmail] blank page on print preview has caused the Debian Bug report #919504, regarding kmail - can not print mails (get no content) to be marked as done. This means that you

Bug#945696: lokalize: Python2 removal in sid/bullseye

Source: lokalize Version: 4:19.08.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in

Bug#945645: calligra: Python2 removal in sid/bullseye

Source: calligra Version: 1:3.1.0+dfsg-6 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in

krita_4.2.8.2+dfsg-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 27 Nov 2019 19:43:14 +0100 Source: krita Architecture: source Version: 1:4.2.8.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: krita

Processing of krita_4.2.8.2+dfsg-1_source.changes

krita_4.2.8.2+dfsg-1_source.changes uploaded successfully to localhost along with the files: krita_4.2.8.2+dfsg-1.dsc krita_4.2.8.2+dfsg.orig.tar.xz krita_4.2.8.2+dfsg-1.debian.tar.xz krita_4.2.8.2+dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#945554: marked as done (Qt5: link against OpenSSL at compile-time)

Your message dated Wed, 27 Nov 2019 17:30:14 +0300 with message-id <20191127143014.ga12...@mitya57.me> and subject line Re: Bug#945554: Qt5: link against OpenSSL at compile-time has caused the Debian Bug report #945554, regarding Qt5: link against OpenSSL at compile-time to be marked as done.

Bug#942429:

Hi, On Wed, 16 Oct 2019 20:25:19 +0200 Gregor Riepl wrote: > > I reported this problem some time ago, it depends on the 5.62.0 framework. > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872 > > I'm positive this is not the same bug, as I don't have problems with keyboard > lock