Bug#794681: marked as done (qt4-x11: please support timestamps from environment)

Your message dated Tue, 5 Jul 2022 21:57:33 +0200 with message-id <6e238183-ac9c-26cf-e350-e4fa0414f...@inventati.org> and subject line Re: qt4-x11: please support timestamps from environment has caused the Debian Bug report #794681, regarding qt4-x11: please support timestamps from environm

Bug#935003: marked as done (qt4-x11: Should not be released with bullseye)

Your message dated Wed, 9 Dec 2020 01:04:46 +0100 with message-id <024fac99-893c-fb08-bc45-ec8a911d1...@debian.org> and subject line qt4-x11 has been removed from Debian has caused the Debian Bug report #935003, regarding qt4-x11: Should not be released with bullseye to be marked as done.

qt4-x11_4.8.7+dfsg-18+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 14 Sep 2020 10:56:35 -0300 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-18+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor

Bug#970308: marked as done (qt4-x11: CVE-2020-17507)

Your message dated Sat, 19 Sep 2020 10:17:10 + with message-id and subject line Bug#970308: fixed in qt4-x11 4:4.8.7+dfsg-18+deb10u1 has caused the Debian Bug report #970308, regarding qt4-x11: CVE-2020-17507 to be marked as done. This means that you claim that the problem has been dealt

qt4-x11_4.8.7+dfsg-18+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new

Mapping buster to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 14 Sep 2020 10:56:35 -0300 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-18+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian

Processing of qt4-x11_4.8.7+dfsg-18+deb10u1_source.changes

qt4-x11_4.8.7+dfsg-18+deb10u1_source.changes uploaded successfully to localhost along with the files: qt4-x11_4.8.7+dfsg-18+deb10u1.dsc qt4-x11_4.8.7+dfsg-18+deb10u1.debian.tar.xz qt4-x11_4.8.7+dfsg-18+deb10u1_source.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#953388: marked as done (kdesdk-scripts: suggests obsolete qt4-doc (package removed from debian))

Your message dated Sat, 01 Aug 2020 12:19:39 + with message-id and subject line Bug#953388: fixed in kde-dev-scripts 4:20.04.3-1 has caused the Debian Bug report #953388, regarding kdesdk-scripts: suggests obsolete qt4-doc (package removed from debian) to be marked as done. This means that

Bug#953388: kdesdk-scripts: suggests obsolete qt4-doc (package removed from debian)

Package: kdesdk-scripts Version: 4:18.08.0-1 Severity: normal Dear Qt/KDE Maintainers, kdesdk-scripts suggests qt4-doc which has been removed from Debian unstable and testing. Best Regards, Juhani

Bug#610294: marked as done (qt4-demos: visibly ugly dithering under vnc4server (not with clean $HOME))

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #610294, regarding qt4-demos: visibly ugly dithering under vnc4server (not with clean $HOME) to be marked as done. This means that

Bug#564548: marked as done (qt4-qtconfig does not store font settings)

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #564548, regarding qt4-qtconfig does not store font settings to be marked as done. This means that you claim that the problem has been

Bug#614977: marked as done ([qt4-demos] Application bugs message)

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #614977, regarding [qt4-demos] Application bugs message to be marked as done. This means that you claim that the problem has been

Bug#606180: marked as done (assistant-qt4: prints warning to console at startup)

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #606180, regarding assistant-qt4: prints warning to console at startup to be marked as done. This means that you claim that the

Bug#652855: marked as done (qt4-dev-tools: Help window is broken (regression))

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #606073, regarding qt4-dev-tools: Help window is broken (regression) to be marked as done. This means that you claim that the problem

Bug#415246: marked as done (qt4-doc: QT >= 4.2 documentation suggestions)

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #415246, regarding qt4-doc: QT >= 4.2 documentation suggestions to be marked as done. This means that you claim that the problem

Bug#392902: marked as done (qmake-qt4 no longer escapes quotes for -Dfoo="value" on gcc command line)

Your message dated Sat, 07 Mar 2020 23:24:03 + with message-id and subject line Bug#953294: Removed package(s) from unstable has caused the Debian Bug report #392902, regarding qmake-qt4 no longer escapes quotes for -Dfoo="value" on gcc command line to be marked as done. This mean

qt4-x11_4.8.7+dfsg-20_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Feb 2020 15:25:09 +0300 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-20 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Changes: qt4

Processing of qt4-x11_4.8.7+dfsg-20_source.changes

qt4-x11_4.8.7+dfsg-20_source.changes uploaded successfully to localhost along with the files: qt4-x11_4.8.7+dfsg-20.dsc qt4-x11_4.8.7+dfsg-20.debian.tar.xz qt4-x11_4.8.7+dfsg-20_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#875151: marked as done ([qt-assistant-compat] Future Qt4 removal from Buster)

Your message dated Mon, 23 Dec 2019 07:39:35 + with message-id and subject line Bug#945194: Removed package(s) from unstable has caused the Debian Bug report #875151, regarding [qt-assistant-compat] Future Qt4 removal from Buster to be marked as done. This means that you claim that the

[bts-link] source package qt4-x11

# # bts-link upstream status pull for source package qt4-x11 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #650828 (http://bugs.debian.org/650828

Processed: [bts-link] source package qt4-x11

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package qt4-x11 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l..

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

I've created a WIP merge request at https://salsa.debian.org/med-team/sofa-framework/merge_requests/1 I could solve TinyXML (at least in the aspect of finding it, I might need to adjust something else later on) but came across libgtest-dev... It ships static libraries! I would have to check ho

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi Lisandro, On Wed, Sep 18, 2019 at 07:42:23PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > On 19/09/17 10:17, Andreas Tille wrote: > > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez > > Meyer wrote: > > > > > > Is the embedded stuff all in extlibs/? or is there

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

On 19/09/17 10:17, Andreas Tille wrote: > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty code? > > A lot is excluded in advance from the packaging Git: > > Files-Excluded: */li

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi! El mar., 17 sep. 2019 17:17, Andreas Tille escribió: > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty > code? > > A lot is excluded in advance from the packaging Git: > > Fi

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty code? A lot is excluded in advance from the packaging Git: Files-Excluded: */libQGLViewer* */csparse */

Re: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Moritz Mühlenhoff wrote: > > > > > > > > The current releases on https://github.com/sofa-framework claim to be > > > > Qt5 > > > > compatible. Is anyone working on updating the package or should it be > > > > removed? > > > > > > &g

Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

//github.com/sofa-framework claim to be Qt5 > > > compatible. Is anyone working on updating the package or should it be > > > removed? > > > > > > sofa-framework is one of the three remaining reverse dependencies of > > > libqwt5-qt4-dev at this point. &

Bug#939711: marked as done (phonon-backend-gstreamer-common: The package does not need to break the older (Qt4) version)

Your message dated Sun, 8 Sep 2019 14:26:28 -0300 with message-id and subject line Re: Bug#939711: phonon-backend-gstreamer-common: The package does not need to break the older (Qt4) version has caused the Debian Bug report #939711, regarding phonon-backend-gstreamer-common: The package does

Bug#939711: phonon-backend-gstreamer-common: The package does not need to break the older (Qt4) version

Package: phonon-backend-gstreamer-common Version: 4:4.9.1-2 Severity: minor Dear Maintainer, as reported also by upstream, the two versions of phonon (Qt4 and Qt5) can be installed at the same time. https://mail.kde.org/pipermail/kde-distro-packagers/2019-August/000383.html The current Break

Bug#875130: marked as done ([qimageblitz] Future Qt4 removal from Buster)

Your message dated Tue, 03 Sep 2019 05:35:29 + with message-id and subject line Bug#939273: Removed package(s) from unstable has caused the Debian Bug report #875130, regarding [qimageblitz] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#875092: marked as done ([polkit-qt-1] Future Qt4 removal from Buster)

Your message dated Sat, 31 Aug 2019 19:53:58 + with message-id and subject line Bug#875092: fixed in polkit-qt-1 0.112.0-7 has caused the Debian Bug report #875092, regarding [polkit-qt-1] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#875095: marked as done ([phonon] Future Qt4 removal from Buster)

Your message dated Sat, 31 Aug 2019 17:10:52 + with message-id and subject line Bug#875095: fixed in phonon 4:4.10.3-3 has caused the Debian Bug report #875095, regarding [phonon] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#875088: marked as done ([phonon-backend-vlc] Future Qt4 removal from Buster)

Your message dated Fri, 30 Aug 2019 19:20:49 + with message-id and subject line Bug#875088: fixed in phonon-backend-vlc 0.10.3-2 has caused the Debian Bug report #875088, regarding [phonon-backend-vlc] Future Qt4 removal from Buster to be marked as done. This means that you claim that the

Bug#875087: marked as done ([phonon-backend-gstreamer] Future Qt4 removal from Buster)

Your message dated Fri, 30 Aug 2019 18:36:41 + with message-id and subject line Bug#875087: fixed in phonon-backend-gstreamer 4:4.9.1-2 has caused the Debian Bug report #875087, regarding [phonon-backend-gstreamer] Future Qt4 removal from Buster to be marked as done. This means that you

Bug#875087: [phonon-backend-gstreamer] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 10:18:38PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: phonon-backend-gstreamer > Version: 4:4.9.0-1 > Severity: wishlist > User: debian-qt-kde@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team

Bug#875183: marked as done ([sni-qt] Future Qt4 removal from Buster)

Your message dated Thu, 29 Aug 2019 03:31:36 + with message-id and subject line Bug#935962: Removed package(s) from unstable has caused the Debian Bug report #875183, regarding [sni-qt] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875092: [polkit-qt-1] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 10:19:00PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: polkit-qt-1 > Usertags: qt4-removal With the removal of src:kde4libs, the Qt4 packages can now go away, patch attached. Cheers, Moritz diff -Naur polkit-qt-1-0.112.0.orig/debian/c

Bug#874822: marked as done ([automoc] Future Qt4 removal from Buster)

Your message dated Tue, 27 Aug 2019 01:03:47 + with message-id and subject line Bug#935847: Removed package(s) from unstable has caused the Debian Bug report #874822, regarding [automoc] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875130: [qimageblitz] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:01:46PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: qimageblitz > Version: 1:0.0.6-5 > Severity: wishlist > User: debian-qt-kde@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are prep

Bug#875133: marked as done ([qca2] Future Qt4 removal from Buster)

Your message dated Mon, 26 Aug 2019 17:59:12 + with message-id and subject line Bug#875133: fixed in qca2 2.2.1-2 has caused the Debian Bug report #875133, regarding [qca2] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#875078: marked as done ([oxygen] Future Qt4 removal from Buster)

Your message dated Mon, 26 Aug 2019 16:19:25 + with message-id and subject line Bug#875078: fixed in oxygen 4:5.14.5-2 has caused the Debian Bug report #875078, regarding [oxygen] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#874840: marked as done ([breeze] Future Qt4 removal from Buster)

Your message dated Mon, 26 Aug 2019 11:19:07 + with message-id and subject line Bug#874840: fixed in breeze 4:5.14.5-2 has caused the Debian Bug report #874840, regarding [breeze] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#874818: marked as done ([attica] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 19:14:24 + with message-id and subject line Bug#935735: Removed package(s) from unstable has caused the Debian Bug report #874818, regarding [attica] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875021: marked as done ([libdbusmenu-qt] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 16:36:45 + with message-id and subject line Bug#875021: fixed in libdbusmenu-qt 0.9.3+16.04.20160218-2 has caused the Debian Bug report #875021, regarding [libdbusmenu-qt] Future Qt4 removal from Buster to be marked as done. This means that you claim that

Bug#874808: marked as done ([akonadi4] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:45:47 + with message-id and subject line Bug#935718: Removed package(s) from unstable has caused the Debian Bug report #874808, regarding [akonadi4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875159: marked as done ([qtwebkit] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:35:34 + with message-id and subject line Bug#935668: Removed package(s) from unstable has caused the Debian Bug report #875159, regarding [qtwebkit] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874945: marked as done ([kde4libs] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #874945, regarding [kde4libs] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#842408: marked as done (qt4-designer: SIGSEGV with designer-qt4)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #842408, regarding qt4-designer: SIGSEGV with designer-qt4 to be marked as done. This means that you claim that the problem has been

Bug#784479: marked as done ([kde4libs] Qt4's WebKit removal)

Your message dated Sun, 25 Aug 2019 15:34:27 + with message-id and subject line Bug#935666: Removed package(s) from unstable has caused the Debian Bug report #784479, regarding [kde4libs] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been

Bug#874944: marked as done ([kde-runtime] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:29:15 + with message-id and subject line Bug#935664: Removed package(s) from unstable has caused the Debian Bug report #874944, regarding [kde-runtime] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#874937: marked as done ([kdepimlibs] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:30:26 + with message-id and subject line Bug#935663: Removed package(s) from unstable has caused the Debian Bug report #874937, regarding [kdepimlibs] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#874932: marked as done ([kate4] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:29:50 + with message-id and subject line Bug#935222: Removed package(s) from unstable has caused the Debian Bug report #874932, regarding [kate4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#784477: marked as done ([kde-runtime] Qt4's WebKit removal)

Your message dated Sun, 25 Aug 2019 15:29:15 + with message-id and subject line Bug#935664: Removed package(s) from unstable has caused the Debian Bug report #784477, regarding [kde-runtime] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been

Bug#874925: marked as done ([kactivities] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 15:28:01 + with message-id and subject line Bug#935219: Removed package(s) from unstable has caused the Debian Bug report #874925, regarding [kactivities] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#874908: marked as done ([grantlee] Future Qt4 removal from Buster)

Your message dated Sat, 24 Aug 2019 01:23:44 + with message-id and subject line Bug#935554: Removed package(s) from unstable has caused the Debian Bug report #874908, regarding [grantlee] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874908: [grantlee] Future Qt4 removal from Buster

2017 at 09:05:49PM +0200, Lisandro Damián Nicanor > Pérez Meyer wrote: > > > > Source: grantlee > > > > Version: 0.4.0-4 > > > > Severity: wishlist > > > > User: debian-qt-kde@lists.debian.org > > > > Usertags: qt4-removal > > &

Bug#874908: [grantlee] Future Qt4 removal from Buster

> Source: grantlee > > > Version: 0.4.0-4 > > > Severity: wishlist > > > User: debian-qt-kde@lists.debian.org > > > Usertags: qt4-removal > > > > The changelog mentions that as of 5.0.0 upstream switched to Qt5. > > Currently the archive has bo

Bug#874980: marked as done ([kremotecontrol] Future Qt4 removal from Buster)

Your message dated Thu, 22 Aug 2019 03:13:31 + with message-id and subject line Bug#935236: Removed package(s) from unstable has caused the Debian Bug report #874980, regarding [kremotecontrol] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#874987: marked as done ([kscd] Future Qt4 removal from Buster)

Your message dated Thu, 22 Aug 2019 03:14:05 + with message-id and subject line Bug#935237: Removed package(s) from unstable has caused the Debian Bug report #874987, regarding [kscd] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874953: marked as done ([kfilemetadata] Future Qt4 removal from Buster)

Your message dated Thu, 22 Aug 2019 01:45:10 + with message-id and subject line Bug#935226: Removed package(s) from unstable has caused the Debian Bug report #874953, regarding [kfilemetadata] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#874970: marked as done ([kppp] Future Qt4 removal from Buster)

Your message dated Thu, 22 Aug 2019 01:47:16 + with message-id and subject line Bug#935232: Removed package(s) from unstable has caused the Debian Bug report #874970, regarding [kppp] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874927: marked as done ([kaccessible] Future Qt4 removal from Buster)

Your message dated Thu, 22 Aug 2019 01:41:38 + with message-id and subject line Bug#935218: Removed package(s) from unstable has caused the Debian Bug report #874927, regarding [kaccessible] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#874826: marked as done ([baloo] Future Qt4 removal from Buster)

Your message dated Tue, 20 Aug 2019 04:13:25 + with message-id and subject line Bug#935024: Removed package(s) from unstable has caused the Debian Bug report #874826, regarding [baloo] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875181: marked as done ([smokegen] Future Qt4 removal from Buster)

Your message dated Tue, 20 Aug 2019 04:06:15 + with message-id and subject line Bug#935074: Removed package(s) from unstable has caused the Debian Bug report #875181, regarding [smokegen] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#784480: marked as done ([kdepim4] Qt4's WebKit removal)

Your message dated Tue, 20 Aug 2019 03:57:25 + with message-id and subject line Bug#935024: Removed package(s) from unstable has caused the Debian Bug report #784480, regarding [kdepim4] Qt4's WebKit removal to be marked as done. This means that you claim that the problem has been dealt

Bug#874947: marked as done ([kdepim4] Future Qt4 removal from Buster)

Your message dated Tue, 20 Aug 2019 03:57:25 + with message-id and subject line Bug#935024: Removed package(s) from unstable has caused the Debian Bug report #874947, regarding [kdepim4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#935003: qt4-x11: Should not be released with bullseye

Source: qt4-x11 Version: 4:4.8.7+dfsg-19 Severity: serious Justification: Should not be released with bullseye With my maintainer hat on: Qt 4 has been dead upstream for too long now, and should not be released with bullseye. Note that we are creating this bug at the beggining of bullseye&#

qt4-x11_4.8.7+dfsg-19_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 14 Jul 2019 12:19:27 +0200 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-19 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Felix Geyer Closes: 925811

Bug#925811: marked as done (qt4-x11: ftbfs with GCC-9)

Your message dated Sun, 14 Jul 2019 10:40:15 + with message-id and subject line Bug#925811: fixed in qt4-x11 4:4.8.7+dfsg-19 has caused the Debian Bug report #925811, regarding qt4-x11: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Processing of qt4-x11_4.8.7+dfsg-19_source.changes

qt4-x11_4.8.7+dfsg-19_source.changes uploaded successfully to localhost along with the files: qt4-x11_4.8.7+dfsg-19.dsc qt4-x11_4.8.7+dfsg-19.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: Bug#925811 marked as pending in qt4-x11

Processing control commands: > tag -1 pending Bug #925811 [src:qt4-x11] qt4-x11: ftbfs with GCC-9 Added tag(s) pending. -- 925811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#874908: [grantlee] Future Qt4 removal from Buster

Hi Moritz! On Fri, 5 Jul 2019 at 15:33, Moritz Mühlenhoff wrote: > > On Sat, Sep 09, 2017 at 09:05:49PM +0200, Lisandro Damián Nicanor Pérez Meyer > wrote: > > Source: grantlee > > Version: 0.4.0-4 > > Severity: wishlist > > User: debian-qt-kde@lists.debian.org

Bug#874908: [grantlee] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 09:05:49PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: grantlee > Version: 0.4.0-4 > Severity: wishlist > User: debian-qt-kde@lists.debian.org > Usertags: qt4-removal The changelog mentions that as of 5.0.0 upstream switched to Qt5. Cheers, Moritz

qt4-x11_4.8.7+dfsg-18_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Apr 2019 23:10:28 +0300 Source: qt4-x11 Architecture: source Version: 4:4.8.7+dfsg-18 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 923003

Processing of qt4-x11_4.8.7+dfsg-18_source.changes

qt4-x11_4.8.7+dfsg-18_source.changes uploaded successfully to localhost along with the files: qt4-x11_4.8.7+dfsg-18.dsc qt4-x11_4.8.7+dfsg-18.debian.tar.xz qt4-x11_4.8.7+dfsg-18_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: Bug #923003 in qt4-x11 marked as pending

Processing control commands: > tag -1 pending Bug #923003 [src:qt4-x11] CVE-2018-19873 CVE-2018-19871 CVE-2018-19870 Added tag(s) pending. -- 923003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#925811: qt4-x11: ftbfs with GCC-9

before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/qt4-x11_4.8.7+dfsg-17_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either

Bug#920992: marked as done (qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf)

Your message dated Thu, 21 Mar 2019 20:24:05 +0100 with message-id <5fa6513e-ed9e-7072-21c8-5be6b36ea...@debian.org> and subject line Re: qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf has caused the Debian Bug report #920992, regarding qt4-x11: FTBFS against libmariadb3 on amd6

Qt4 Removal : Trimage

Hi! Trimage 1.0.6 is available with Qt5 and Python3 instead of Qt4 and Python2. <https://github.com/Kilian/Trimage/releases/tag/1.0.6> Maybe, you could update the package? Thank's in advance!

Bug#784479: [kde4libs] Qt4's WebKit removal

Hi Scott, On Tue, 15 Jan 2019 11:03:33 + Scott Kitterman wrote: > I think rebuilding the rdepends is a reasonable next step. I'll try > that and see if anything is affected. Did you get around to do this? Paul signature.asc Description: OpenPGP digital signature

Bug#920992: qt4-x11: FTBFS against libmariadb3 on amd64,i386,armhf

Source: qt4-x11 Version: 4:4.8.7+dfsg-17 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, qt4-x11 did FTBFS against mariadb-10.3 on a few architectures: https://buildd.debian.org/status/package.php?p=qt4-x11&suite=unstable but given that

Bug#875185: marked as done ([soprano] Future Qt4 removal from Buster)

Your message dated Sun, 27 Jan 2019 11:33:17 + with message-id and subject line Bug#917019: Removed package(s) from unstable has caused the Debian Bug report #875185, regarding [soprano] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

[bts-link] source package qt4-x11

# # bts-link upstream status pull for source package qt4-x11 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #647470 (http://bugs.debian.org/647470

Processed: [bts-link] source package qt4-x11

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package qt4-x11 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l..

Re: Bug#784479: [kde4libs] Qt4's WebKit removal

> > > >Again: something worth to mention, since apparently it is not clear: > >removing bits from either kde4libs or kde-runtime has consequences, > >either build time or runtime ones. Randomly chopping pieces without > >checking what changes, and potentially what br

Bug#784479: [kde4libs] Qt4's WebKit removal

andomly chopping pieces without >checking what changes, and potentially what breaks, is generally a >big no-no from me. I do not see how "remove qtwebkit" is an excuse to >start messing up with packages, just for the sake of package removal. I didn't do rebuild tests, but

Bug#784479: [kde4libs] Qt4's WebKit removal

In data lunedì 14 gennaio 2019 22:28:46 CET, Adrian Bunk ha scritto: > What is actually the overall plan for KDE4 in buster now? kdelibs 4.x will stay in buster. Period. Dropping stuff just for the sake of removal is a no-go, especially when done from people who have NO IDEA about Qt/KDE librarie

Bug#784479: [kde4libs] Qt4's WebKit removal

In data lunedì 14 gennaio 2019 12:22:52 CET, Scott Kitterman ha scritto: > On Thu, 01 Nov 2018 14:04:12 -0300 Lisandro > =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer wrote: > > On Wed, 17 Oct 2018 15:57:25 +0200 Ivo De Decker wrote: > > > Hi, > > > > > > On Fri, Nov 24, 2017 at 04:59:58PM -0

Bug#784479: [kde4libs] Qt4's WebKit removal

On Mon, Jan 14, 2019 at 06:22:52AM -0500, Scott Kitterman wrote: > > That patch no longer seems to be available, so I made my own. Patches for > kde4libs and kde-runtime attached. I looked at the KDE4 packages still in > Buster and I don't believe this interferes with anything. This also fixe

Bug#784479: [kde4libs] Qt4's WebKit removal

kde4libs-4.14.38/debian/changelog 2019-01-14 06:15:38.0 -0500 @@ -1,3 +1,17 @@ +kde4libs (4:4.14.38-4) UNRELEASED; urgency=medium + + * Team upload. + * Drop support for Qt4 WebKit (Closes: #784479) +- Drop build-depends +- Add d/p/no_kdewebkit.patch to patch out building kdewebkit, k

[bts-link] source package qt4-x11

# # bts-link upstream status pull for source package qt4-x11 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #523413 (http://bugs.debian.org/523413

Bug#874942: marked as done ([kde-baseapps] Future Qt4 removal from Buster)

Your message dated Fri, 21 Dec 2018 15:45:19 + with message-id and subject line Bug#917017: Removed package(s) from unstable has caused the Debian Bug report #874942, regarding [kde-baseapps] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#875015: marked as done ([libkdegames-kde4] Future Qt4 removal from Buster)

Your message dated Fri, 21 Dec 2018 15:40:19 + with message-id and subject line Bug#917012: Removed package(s) from unstable has caused the Debian Bug report #875015, regarding [libkdegames-kde4] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#784479: [kde4libs] Qt4's WebKit removal

On Wed, 17 Oct 2018 15:57:25 +0200 Ivo De Decker wrote: > Hi, > > On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > > Control: tag -1 patch > > > > There is patch available for this at > packages.git/tree/trunk/kdelibs-

Bug#784479: [kde4libs] Qt4's WebKit removal

Hi, On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Control: tag -1 patch > > There is patch available for this at packages.git/tree/trunk/kdelibs-no-kdewebkit.patch?h=packages/kdelibs> > > We might want to wait for t

Bug#875193: marked as done ([smokeqt] Future Qt4 removal from Buster)

Your message dated Tue, 09 Oct 2018 16:56:07 + with message-id and subject line Bug#904584: Removed package(s) from unstable has caused the Debian Bug report #875193, regarding [smokeqt] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#887687: marked as done (libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS)

Your message dated Tue, 09 Oct 2018 16:56:07 + with message-id and subject line Bug#904584: Removed package(s) from unstable has caused the Debian Bug report #887687, regarding libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS to be marked as done. This means that you claim that

Re: [Debconf-devel] Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

On Fri, Jun 29, 2018 at 10:22:50AM +0300, Niko Tyni wrote: > On Fri, Jun 29, 2018 at 12:55:50AM +, Scott Kitterman wrote: > > I had hoped to work on this this week. It hasn't happened and it's not > > going to. > > > > In the end, I the Qt4 stuff has

Bug#904090: expeyes: Build-depends on Qt4 toolchain

Source: expeyes User: debian-qt-kde@lists.debian.org Usertags: qt4-removal X-Debbugs-CC: debian-qt-kde@lists.debian.org Severity: normal Tags: patch mail template starts Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as announced in: [announced] <ht

Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

Control: tag -1 patch On Fri, Jan 19, 2018 at 06:23:25AM +0200, Adrian Bunk wrote: > Package: libsmokeqt4-dev > Version: 4:4.14.3-1.2 > Severity: serious > Control: affects -1 src:qt4-perl > > qt4-perl FTBFS: > > https://tests.reproducible-builds.org/debian/rb-pkg/unst

  1   2   3   4   5   6   7   8   9   10   >