[Pkg-kde-extras] Bug#717011: marked as done (konverstaion: depends on transitional package kdebase-runtime)
Your message dated Wed, 06 May 2015 09:40:05 +0200 with message-id 1430898005.2261.11.ca...@debian.org and subject line has caused the Debian Bug report #717011, regarding konverstaion: depends on transitional package kdebase-runtime to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 717011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: konversation Version: 1.4-1 Severity: normal From the description: This transitional package takes care of pulling in the new kde-runtime package and can safely be removed after installation. Thank you -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages konversation depends on: ii kdebase-runtime4:4.10.5-1 ii kdepim-runtime 4:4.10.5-1 ii konversation-data 1.4-1 ii libc6 2.17-7 ii libgcc11:4.8.1-6 ii libkabc4 4:4.10.5-1 ii libkde3support44:4.10.5-1 ii libkdecore54:4.10.5-1 ii libkdeui5 4:4.10.5-1 ii libkemoticons4 4:4.10.5-1 ii libkidletime4 4:4.10.5-1 ii libkio54:4.10.5-1 ii libknotifyconfig4 4:4.10.5-1 ii libkparts4 4:4.10.5-1 ii libkresources4 4:4.10.5-1 ii libnepomuk44:4.10.5-1 ii libnepomukutils4 4:4.10.5-1 ii libphonon4 4:4.6.0.0-3 ii libqca22.0.3-4 ii libqt4-dbus4:4.8.5+dfsg-2 ii libqt4-network 4:4.8.5+dfsg-2 ii libqt4-qt3support 4:4.8.5+dfsg-2 ii libqt4-svg 4:4.8.5+dfsg-2 ii libqt4-xml 4:4.8.5+dfsg-2 ii libqtcore4 4:4.8.5+dfsg-2 ii libqtgui4 4:4.8.5+dfsg-2 ii libsolid4 4:4.10.5-1 ii libsoprano42.9.2+dfsg.1-1 ii libstdc++6 4.8.1-6 ii phonon 4:4.6.0.0-3 konversation recommends no packages. konversation suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Triaging this: Neither sid, jessie nor oldstable depends on kdebase-runtime; they migrated to kde-runtime already [1],[2] Closing. [1] https://packages.debian.org/wheezy/konversation [2] https://packages.debian.org/jessie/konversation Tobi---End Message--- ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Processed: fixed 717011 in 1.4-1+deb7u1, fixed 717011 in 1.5-2
Processing commands for cont...@bugs.debian.org:
fixed 717011 1.4-1+deb7u1
Bug #717011 {Done: Tobias Frost t...@debian.org} [konversation] konverstaion:
depends on transitional package kdebase-runtime
Marked as fixed in versions konversation/1.4-1+deb7u1.
fixed 717011 1.5-2
Bug #717011 {Done: Tobias Frost t...@debian.org} [konversation] konverstaion:
depends on transitional package kdebase-runtime
Marked as fixed in versions konversation/1.5-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
717011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Processed: notfound 717011 in 1.4-1+deb7u1, notfound 717011 in 1.5-2
Processing commands for cont...@bugs.debian.org: notfound 717011 1.4-1+deb7u1 Bug #717011 [konversation] konverstaion: depends on transitional package kdebase-runtime Ignoring request to alter found versions of bug #717011 to the same values previously set notfound 717011 1.5-2 Bug #717011 [konversation] konverstaion: depends on transitional package kdebase-runtime Ignoring request to alter found versions of bug #717011 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 717011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784460: [digikam] Qt4's WebKit removal
Source: digikam Version: 4:4.4.0-1.1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784466: [gammaray] Qt4's WebKit removal
Source: gammaray Version: 2.1.0-3.1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784471: [k3b] Qt4's WebKit removal
Source: k3b Version: 2.0.2-8 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784490: [kvirc] Qt4's WebKit removal
Source: kvirc Version: 4:4.2.0-2 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784448: [amarok] Qt4's WebKit removal
Source: amarok Version: 2.8.0-2.1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784476: [kchmviewer] Qt4's WebKit removal
Source: kchmviewer Version: 6.0-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784487: [ktorrent] Qt4's WebKit removal
Source: ktorrent Version: 4.3.1-2 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784488: [ktp-auth-handler] Qt4's WebKit removal
Source: ktp-auth-handler Version: 0.8.1-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784489: [ktp-text-ui] Qt4's WebKit removal
Source: ktp-text-ui Version: 0.8.1-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784486: [krecipes] Qt4's WebKit removal
Source: krecipes Version: 2.0~beta2-3 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784527: [skrooge] Qt4's WebKit removal
Source: skrooge Version: 1.9.3-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#784560: [webkitkde] Qt4's WebKit removal
Source: webkitkde Version: 1.3.4-2 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org, As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit as announced in [announce]. [announce] https://lists.debian.org/debian-devel-announce/2015/05/msg1.html Basically we are about to get the latest Qt4 point release and upstream is migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. In order to make this move, all packages directly or indirectly depending on the Qt4's WebKit library have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. In order to ease the transition time we have provided Wheezy backports for Qt5. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Ana, on behalf of the Qt4 maintainers ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#763852: Preparing the upload that removes libqt4-private-dev
Hi! i would like to get this fixed in the next Qt4 upload which will surely happen next week. I know the fix is already commited in the repo, is it possible to get this uploaded soon? Thanks a lot! Lisandro. -- Lo que me sorprende de las mujeres es que se arrancan los pelos desde la raíz con cera caliente y aún así le temen a las arañas. Jerry Seinfeld lis: comentario sobre tu frase yo soy mujer, yo me arranco los pelos y VOS le tenes miedo a las arañas María Luján Pérez Meyer (mi hermana) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
