Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Andreas Tille]

Dear Julien,

On Wed, Feb 07, 2018 at 09:37:23AM +0100, Julien Yann Dutheil wrote:
> Sorry, I only did push and not push --all, this is now corrected.

:-)

> libbpp-qt
> now works, but I had to split the regex in 3 to get it to work. The dev
> package is apparently now named qtdeclarative5-dev.

Its perfectly fine to split the regex if this works without spending
extra brain cycles.

> I still need to proceed the 2 omics libs and the program packages, I will
> pas a message to the list when everything is ready.

Fine.  Just take your time.  I'll probably upload if I'm in Barcelona
for the Debian Med sprint[1].

Thanks for your work on this

Andreas.

[1] https://wiki.debian.org/Sprints/2018/DebianMed2018 

-- 
http://fam-tille.de

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Julien Yann Dutheil]

Dear Andreas,

Sorry, I only did push and not push --all, this is now corrected. libbpp-qt
now works, but I had to split the regex in 3 to get it to work. The dev
package is apparently now named qtdeclarative5-dev.

I still need to proceed the 2 omics libs and the program packages, I will
pas a message to the list when everything is ready.

Cheers,

Julien.

On Wed, Feb 7, 2018 at 8:41 AM, Andreas Tille  wrote:

> On Tue, Feb 06, 2018 at 10:24:58PM +0100, Julien Yann Dutheil wrote:
> > Hi,
> >
> > While trying to update the libbpp-qt package to use Qt5 instead of Qt4,
> I'm
> > getting this error (using debuild -us -uc):
> >
> > devlibs error: There is no package matching [libQt5Core5-dev] and noone
> > provides it, please report bug to d-shlibs maintainer
> > devlibs error: There is no package matching [libQt5Gui5-dev] and noone
> > provides it, please report bug to d-shlibs maintainer
> > devlibs error: There is no package matching [libQt5Widgets5-dev] and
> noone
> > provides it, please report bug to d-shlibs maintainer
> >
> > Any idea of what is going on?
>
> Yes, that's caused by d-shlibs.  D-shlibs is verifying the existence of
> the library and assumes that a package is named like the library.  If
> the package name is different from the library name you sometimes need
> an override (several overrides are contained in d-shlibs - I'll sent a
> patch once we found the correct one to simplify the rules file).
>
> I commited an **untested** override which hopefully works - may be the
> regexp needs some adjustment.  I was not able to test since I would have
> needed to build all the other libs which I do not have time right now.
> If you confirm that the other libbpp* packages are ready for upload I'll
> do so step by step and then I'll check libbpp-qt.
>
> Hint: For libbpp-qt pristine-tar was not updated.  I did so now but
> please make sure the other libbpp* repositories are updated as well
> since this simplifies my work. :-)
>
> > The code otherwise compiles smoothly. I can
> > see the packages for Qt5 changed names (no more libqt5-dev, etc), and I
> am
> > probably missing sthg :s Git repos is updated to reproduce the error.
> >
> > Any insight welcome!
>
> Hope this hint was sufficiently helpful
>
>  Andreas.
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Andreas Tille]

On Tue, Feb 06, 2018 at 10:24:58PM +0100, Julien Yann Dutheil wrote:
> Hi,
> 
> While trying to update the libbpp-qt package to use Qt5 instead of Qt4, I'm
> getting this error (using debuild -us -uc):
> 
> devlibs error: There is no package matching [libQt5Core5-dev] and noone
> provides it, please report bug to d-shlibs maintainer
> devlibs error: There is no package matching [libQt5Gui5-dev] and noone
> provides it, please report bug to d-shlibs maintainer
> devlibs error: There is no package matching [libQt5Widgets5-dev] and noone
> provides it, please report bug to d-shlibs maintainer
> 
> Any idea of what is going on?

Yes, that's caused by d-shlibs.  D-shlibs is verifying the existence of
the library and assumes that a package is named like the library.  If
the package name is different from the library name you sometimes need
an override (several overrides are contained in d-shlibs - I'll sent a
patch once we found the correct one to simplify the rules file).

I commited an **untested** override which hopefully works - may be the
regexp needs some adjustment.  I was not able to test since I would have
needed to build all the other libs which I do not have time right now.
If you confirm that the other libbpp* packages are ready for upload I'll
do so step by step and then I'll check libbpp-qt.

Hint: For libbpp-qt pristine-tar was not updated.  I did so now but
please make sure the other libbpp* repositories are updated as well
since this simplifies my work. :-)

> The code otherwise compiles smoothly. I can
> see the packages for Qt5 changed names (no more libqt5-dev, etc), and I am
> probably missing sthg :s Git repos is updated to reproduce the error.
> 
> Any insight welcome!

Hope this hint was sufficiently helpful

 Andreas.

-- 
http://fam-tille.de

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Julien Yann Dutheil]

Hi,

While trying to update the libbpp-qt package to use Qt5 instead of Qt4, I'm
getting this error (using debuild -us -uc):

devlibs error: There is no package matching [libQt5Core5-dev] and noone
provides it, please report bug to d-shlibs maintainer
devlibs error: There is no package matching [libQt5Gui5-dev] and noone
provides it, please report bug to d-shlibs maintainer
devlibs error: There is no package matching [libQt5Widgets5-dev] and noone
provides it, please report bug to d-shlibs maintainer

Any idea of what is going on? The code otherwise compiles smoothly. I can
see the packages for Qt5 changed names (no more libqt5-dev, etc), and I am
probably missing sthg :s Git repos is updated to reproduce the error.

Any insight welcome!

Julien.


On Wed, Dec 13, 2017 at 11:09 AM, Julien Yann Dutheil <
julien.duth...@univ-montp2.fr> wrote:

> Dear Andreas,
>
> The fix was made upstream on the master branch, but has not been released
> yet. We have recently discussed a change in our release strategies: we will
> release more frequently "minor" updates based on the master branch (version
> x.y.1, x.y.2 etc) which will only be distributed as source archives. I will
> only package the x.1, x.2, etc more serious updates. Maybe the watch file
> could only check for these new updates? Or should we use a distinct tagging
> system for the minor updates?
>
> Best,
>
> Julien.
>
> On Wed, Dec 13, 2017 at 10:43 AM, Andreas Tille  wrote:
>
>> Dear Julien,
>>
>> thanks for the information.  The watch file did not catched any new
>> upstream version.  May be this needs to be adapted as well?
>>
>> Thanks for your quick response
>>
>>  Andreas.
>>
>> On Wed, Dec 13, 2017 at 10:08:18AM +0100, Julien Yann Dutheil wrote:
>> > Dear Andreas,
>> >
>> > The software was ported to Qt5 upstream, but still need to make a new
>> > package version. Will try do that asap.
>> >
>> > Best,
>> >
>> > Julien.
>> >
>> > On Wed, Dec 13, 2017 at 10:03 AM, Andreas Tille 
>> wrote:
>> >
>> > > Hi Julien,
>> > >
>> > > could you please have a look?
>> > >
>> > > Kind regards
>> > >
>> > >  Andreas.
>> > >
>> > > On Sat, Sep 09, 2017 at 08:58:21PM +0200, Lisandro Damián Nicanor
>> Pérez
>> > > Meyer wrote:
>> > > > Source: bppphyview
>> > > > Version: 0.5.1-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] > an-devel-announce/2017/08/
>> > > msg6.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] > > > 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.o
>> rg/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 > >
>> > > >
>> > > > 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
>> > >
>> >
>> >
>> >
>> > --
>> > Julien Y. Dutheil, Ph-

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Andreas Tille]

Hi Julien,

On Wed, Dec 13, 2017 at 11:09:34AM +0100, Julien Yann Dutheil wrote:
> The fix was made upstream on the master branch, but has not been released
> yet. We have recently discussed a change in our release strategies: we will
> release more frequently "minor" updates based on the master branch (version
> x.y.1, x.y.2 etc) which will only be distributed as source archives. I will
> only package the x.1, x.2, etc more serious updates. Maybe the watch file
> could only check for these new updates? Or should we use a distinct tagging
> system for the minor updates?

The watch file takes regular expressions.  If you just delete the micro
version in an uversionmangle watch will not spot those x.y.[1-9]
releases as "new version".  Feel free to ask for more detailed
explanation.  However to be really sure that the watch file works
correctly it would be sensible to just add these tags in GitHub and test
if its working.
 
Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Julien Yann Dutheil]

Dear Andreas,

The fix was made upstream on the master branch, but has not been released
yet. We have recently discussed a change in our release strategies: we will
release more frequently "minor" updates based on the master branch (version
x.y.1, x.y.2 etc) which will only be distributed as source archives. I will
only package the x.1, x.2, etc more serious updates. Maybe the watch file
could only check for these new updates? Or should we use a distinct tagging
system for the minor updates?

Best,

Julien.

On Wed, Dec 13, 2017 at 10:43 AM, Andreas Tille  wrote:

> Dear Julien,
>
> thanks for the information.  The watch file did not catched any new
> upstream version.  May be this needs to be adapted as well?
>
> Thanks for your quick response
>
>  Andreas.
>
> On Wed, Dec 13, 2017 at 10:08:18AM +0100, Julien Yann Dutheil wrote:
> > Dear Andreas,
> >
> > The software was ported to Qt5 upstream, but still need to make a new
> > package version. Will try do that asap.
> >
> > Best,
> >
> > Julien.
> >
> > On Wed, Dec 13, 2017 at 10:03 AM, Andreas Tille 
> wrote:
> >
> > > Hi Julien,
> > >
> > > could you please have a look?
> > >
> > > Kind regards
> > >
> > >  Andreas.
> > >
> > > On Sat, Sep 09, 2017 at 08:58:21PM +0200, Lisandro Damián Nicanor Pérez
> > > Meyer wrote:
> > > > Source: bppphyview
> > > > Version: 0.5.1-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]  > > msg6.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]  > > 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 
> > > >
> > > > 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
> > >
> >
> >
> >
> > --
> > Julien Y. Dutheil, Ph-D
> > 0 (+49) 6421 178 986
> >
> > § Max Planck Institute for Evolutionary Biology
> > Molecular Systems Evolution
> > Department of Evolutionary Genetics
> > Plön -- GERMANY
> >
> > § Institute of Evolutionary Sciences - Montpellier
> > University of Montpellier 2 -- FRANCE
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Andreas Tille]

Dear Julien,

thanks for the information.  The watch file did not catched any new
upstream version.  May be this needs to be adapted as well?

Thanks for your quick response

 Andreas.

On Wed, Dec 13, 2017 at 10:08:18AM +0100, Julien Yann Dutheil wrote:
> Dear Andreas,
> 
> The software was ported to Qt5 upstream, but still need to make a new
> package version. Will try do that asap.
> 
> Best,
> 
> Julien.
> 
> On Wed, Dec 13, 2017 at 10:03 AM, Andreas Tille  wrote:
> 
> > Hi Julien,
> >
> > could you please have a look?
> >
> > Kind regards
> >
> >  Andreas.
> >
> > On Sat, Sep 09, 2017 at 08:58:21PM +0200, Lisandro Damián Nicanor Pérez
> > Meyer wrote:
> > > Source: bppphyview
> > > Version: 0.5.1-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]  > msg6.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]  > 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 
> > >
> > > 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
> >
> 
> 
> 
> -- 
> Julien Y. Dutheil, Ph-D
> 0 (+49) 6421 178 986
> 
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
> 
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE

-- 
http://fam-tille.de

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Julien Yann Dutheil]

Dear Andreas,

The software was ported to Qt5 upstream, but still need to make a new
package version. Will try do that asap.

Best,

Julien.

On Wed, Dec 13, 2017 at 10:03 AM, Andreas Tille  wrote:

> Hi Julien,
>
> could you please have a look?
>
> Kind regards
>
>  Andreas.
>
> On Sat, Sep 09, 2017 at 08:58:21PM +0200, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > Source: bppphyview
> > Version: 0.5.1-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]  msg6.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]  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 
> >
> > 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
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Andreas Tille]

Hi Julien,

could you please have a look?

Kind regards

 Andreas.

On Sat, Sep 09, 2017 at 08:58:21PM +0200, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Source: bppphyview
> Version: 0.5.1-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] 
> 
> 
> 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] 
> 
> 
> 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 
> 
> 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

Bug#874835: [bppphyview] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: bppphyview
Version: 0.5.1-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] 


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] 

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 

Lisandro,
on behalf of the Qt4 maintainers