X-Debbugs-CC: christ...@debian.org bi...@debian.org frede...@lehobey.net Dear qrfcview maintainer and previous uploaders,
As you might already know, Qt4 and all its reverse dependencies are planned to be removed from Debian. Package "qrfcview" in Debian (build-)depends on Qt4 and has no upstream activity since 2006. Besides, its last maintainer upload happened back in 2008 and received no upload since 2013. Its project homepage is also dead now. There seems to be no fork around on the Internet. Considering all those facts, I assume that package qrfcview might not be able to get ported to Qt5 and have to be removed from the Debian Archive. Dear maintainer and previous uploaders, please consider sharing your idea about whether qrfcview will be picked up by someone or should it be removed. Otherwise I will submit a Removal bug to have qrfcview removed from Debian 14 days later. -- Regards, Boyuan Yang On Sat, 9 Sep 2017 23:06:38 +0200 Lisandro =?iso-8859-1?Q? Dami=E1n_Nicanor_P=E9rez?= Meyer <lisan...@debian.org> wrote: > Source: qrfcview > Version: 0.62-5.2 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: > > [announced] <https://lists.debian.org/debian-devel-announce/2017/08/ msg00006.html> > > Currently Qt4 has been dead upstream and we are starting to have problems > maintaining it, like for example in the [OpenSSL 1.1 support] case. > > [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=828522> > > In order to make this move, all packages directly or indirectly depending on > the Qt4 libraries 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. > > 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/packagingqtbasedstuff.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 > > The removal is being tracked in <https://wiki.debian.org/Qt4Removal> > > Lisandro, > on behalf of the Qt4 maintainers > > >
signature.asc
Description: This is a digitally signed message part.
