Bug#875173: [robocut] Future Qt4 removal from Buster

2017-09-13 Thread Markus Schulz
On 09/13/2017 10:28 AM, Lisandro Damián Nicanor Pérez Meyer wrote:
> On 9 September 2017 at 21:53, Markus Schulz  wrote:
>> Hello Lisandro,
>> the latest version supports Qt5 now... but it looks like we need to change
>> the upstream URL. Here is the new upstream:
>> https://github.com/Ti/robocut/blob/master/Readme.md
>> It's like 6 to 7 years that I submitted the package and I forgot a lot...
>> please give me a hint how we can fix this.
>> Thanks!
> 
> Sure! The Qt specifics can be found at:
> 
> 
> 
> But, looking at how long has passed since your last upload, I wonder
> if you need more help than that :-/
> 
> If that's the case please take a look at https://mentors.debian.net/
> and ping me if needed.
> 
> 

Thanks Lisandro for your answer.
Good news is upstream is already working fine with QT5. After using qmake from 
the QT5 directory and a simple make the compile and program work good.
I was able to merge all the files and the new version is now on all the 
repositories and download links.
I guess now the most difficult part for me is updating the Debian package... I 
will now try to do this.
I will post my progress to this bug report, thanks.
Markus



Bug#875173: [robocut] Future Qt4 removal from Buster

2017-09-13 Thread Lisandro Damián Nicanor Pérez Meyer
On 9 September 2017 at 21:53, Markus Schulz  wrote:
> Hello Lisandro,
> the latest version supports Qt5 now... but it looks like we need to change
> the upstream URL. Here is the new upstream:
> https://github.com/Ti/robocut/blob/master/Readme.md
> It's like 6 to 7 years that I submitted the package and I forgot a lot...
> please give me a hint how we can fix this.
> Thanks!

Sure! The Qt specifics can be found at:



But, looking at how long has passed since your last upload, I wonder
if you need more help than that :-/

If that's the case please take a look at https://mentors.debian.net/
and ping me if needed.




-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/



Bug#875173: [robocut] Future Qt4 removal from Buster

2017-09-09 Thread Markus Schulz
Hello Lisandro,
the latest version supports Qt5 now... but it looks like we need to change the 
upstream URL. Here is the new upstream:
https://github.com/Ti/robocut/blob/master/Readme.md
It's like 6 to 7 years that I submitted the package and I forgot a lot... 
please give me a hint how we can fix this.
Thanks!


On September 9, 2017 5:09:21 PM EDT, "Lisandro Damián Nicanor Pérez Meyer" 
 wrote:
>Source: robocut
>Version: 1.0.8-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

Regards,
Markus Schulz

Bug#875173: [robocut] Future Qt4 removal from Buster

2017-09-09 Thread Lisandro Damián Nicanor Pérez Meyer
Source: robocut
Version: 1.0.8-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