[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#673657: Updating the kwin-style-crystal Uploaders list
Package: kwin-style-crystal Version: 2.0.5-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint haiz...@haizaar.com has not been working on the kwin-style-crystal package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
Re: [Pkg-kde-extras] kde-extras packages using kdelibs4c2a
On Sun, Feb 27, 2011 at 08:03:30AM +, Fathi Boudra wrote: Hello, On Sat, Feb 26, 2011 at 8:16 PM, Ana Guerrero a...@debian.org wrote: * kasablanca * kbarcode There's a port in progress but it's stuck since a year: http://gitorious.org/kbarcode-kde4 I am going to file removal from them. If the ports are finished in the future, we can reintroduce them in the archive. * keep * kfocus * klibido * kmobiletools * kpogre * ksniffer * kvdr * lensfun * libkipi * taskjuggler None of them seem to have a working KDE 4 port (except taskjuggler having something in ruby...). I guess we can go ahead and file them all for removal? +1 Except for lensfun, I filed the removal for all of those. Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] kde-extras packages using kdelibs4c2a
Hi folks! This is the list of packages using kdelibs4c2a maintained by kde-extras people. * kasablanca * kbarcode * keep * kfocus * klibido * kmobiletools * kpogre * ksniffer * kvdr * lensfun * libkipi * taskjuggler None of them seem to have a working KDE 4 port (except taskjuggler having something in ruby...). I guess we can go ahead and file them all for removal? Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#526313: kid3: New upstream release 1.2
Hi Patrick, On Thu, Apr 30, 2009 at 12:07:20PM +0200, Patrick Matthäi wrote: Package: kid3 Version: 1.1-1 Severity: wishlist Hello, please package kid3 1.2, there are many improved features which I need :) Thanks and cheers. Sorry, I have kept delaying to update kid3 or one reason or another. Will try to look at it soon. Seriously. Btw, the package is co-maintained inside kde-extras in case you want to join :) Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#522620: O: kpogre -- a graphical administrator tool for PostgreSQL
Package: wnpp Severity: normal I intend to orphan the kpogre package, it is currently mantained inside the kde extras team but it lacks of a proper primary maintainer. You do not need to maintain it inside the kde extras team, but it is usually better to maintain packages inside a team. The package description is: KPoGre is a GUI tool for PostgreSQL, using libpqxx library. . Features: * Browsing through PostgreSQL system catalog * Wizards for create, modify and drop database objects * Wizards for database administration tasks (backup, restore, vacuum, analyze) * Wizards for changing access privileges * SQL Query/result windows, for editing and executing SQL statements and viewing result * Datatable windows for edit database tables content * Executor windows for run database functions . libpqxx is the official C++ client API for PostgreSQL. . PostgreSQL is an opensource database system. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#518892: Please, package new version 1.6.6
Package: kpogre Severity: wishlist Hi, There are a newer versions of kpogre that has not been packaged (currently 1.6.6). Please, update the package and also specially, address the bug #514104 for avoid building breakage with upcoming KDE 4.2 in unstable. Latest (and only) upload was almost one year ago, and the package has not got too much love since then. So I am wondering if the current co-maintainers are still interested on it. If I do not get any answer in the next 2 weeks and nobody else from the KDE extras team want to adopt kpogre, I will do an QA upload orphaning the package and addressing #514104. I am X-Debbugs-CC'ing current maintainers, please answer! :) Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] kde update for Release Notes
Hi, For updating the release notes for Lenny [0], what about: There are not huge changes in the KDE Desktop Enviroment from the version shipped in Etch. Lenny ships an updated translation and service release of KDE 3.5 that is a mixture between 3.5.9 and 3.5.10. Modules labeled as version 3.5.9 are updated and they include mostly the same than the tenth revision. In overall, Lenny ships 3.5.10 without the kicker improvements shipped in kdebase and some bug fixes in kdepim. Lenny will be the latest stable release including a KDE 3 series environment. Any comments? Proofreading for english natives is totally welcome :D ana [0] Current stuff is from etch: http://www.debian.org/releases/lenny/i386/release-notes/ch-information.en.html#kde-desktop-changes ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
Re: [Pkg-kde-extras] kvpnc 0.9.1_rc1 hardy package starter without root privilege - openvpn not working
On Fri, Aug 29, 2008 at 11:33:15AM +0200, Enno Gröper wrote: Hello, is there a reason for changing the Exec line of kvpnc.desktop from Exec=su-to-root -X -c /usr/bin/kvpnc to Exec=kvpnc between gutsy and hardy packages? If not, I would appreciate if the package for hardy could use the old line because openvpn isn't working with the new variant (needs root privileges). You may want to ask to the *Ubuntu* packagers. Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
Re: [Pkg-kde-extras] Bug#482248: kwave: FTBFS: help_de.docbook:1743: element itemizedlist: validity error
On Thu, Jul 24, 2008 at 03:02:59PM +0200, Lucas Nussbaum wrote: [ Cced Bertrand Songis (the current maintainer), Aurelien Jarno (former maintainer) and the Debian KDE extras team (possible adopter?) ] On 17/07/08 at 20:26 +0200, forwarded by www.sneakemail.com wrote: Hi Lucas, could you please check whether this problem still exists with v0.7.11? It fails with 0.7.10-1.1 (currently in Debian unstable). I wonder because I did not see that issue on any od my test systems, using my upstream clean sources (I always make build tests on different distributions/platforms before releasing a new version, including Debian). That might be specific to the Debian packaging. Do you know if Bertrand Songis [EMAIL PROTECTED] is still active? It's the only package he maintains in Debian. If he isn't, it might be better to orphan the package and see if someone is interested in picking it up. Given that the package is not making Lenny, I think it is even better ask for removal and if somebody is interested, s/he can package the possible port to KDE4 instead: http://kwave.sourceforge.net/roadmap.html if not, it is pretty much dead upstream. Ana ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
