Hi Eric, you might have noticed that the development platform for Debian packages has changed from alioth.d.o to salsa.d.o. I have injected the latest version of Freemedforms (1.0.0) into the new repository
https://salsa.debian.org/med-team/freemedforms-project Unfortunately I'm facing build issues I do not feel really competent to solve. It would be great if you would create a user ID on salsa.debian.org and have a look (I'd happily add you to the Debian Med team to get push permissions). Kind regards Andreas. On Wed, Dec 13, 2017 at 06:53:18PM +0100, Eric Maeker wrote: > Hi Andreas > > > Thanks for you work and the reminder. I will check this bug asap. > > Belle journée > Cordialement > Dr Maeker Éric > > Le 13 déc. 2017 10:57 AM, "Andreas Tille" <ti...@debian.org> a écrit : > > > Hi Eric, > > > > this bug has been unanswered so far. My attempt in Git goes as far as > > importing the new upstream version and add Qt5 Build-Depends. I admit > > I have no capacity to care more. Would you please have a look at the > > packaging. > > > > Kind regards > > > > Andreas. > > > > On Sat, Sep 09, 2017 at 09:04:58PM +0200, Lisandro Damián Nicanor Pérez > > Meyer wrote: > > > Source: freemedforms-project > > > Version: 0.9.4-1 > > > 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 > > > > > > _______________________________________________ > > > Debian-med-packaging mailing list > > > debian-med-packag...@lists.alioth.debian.org > > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ > > debian-med-packaging > > > > > > > -- > > http://fam-tille.de > > > _______________________________________________ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de