Bug#874877: Freecad 0.17, current latest version, is based on Qt5

[Lisandro Damián Nicanor Pérez Meyer]

Hi! The current last release of Freecad is qt5-based. Please consider
switching to this version.

Remember there are links to uselfull packaging tips in the original
mail and you can always contacts us if you need help during the
packaging.

Kinds regards, Lisandro.

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

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874877: [freecad] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Hi Martin!


On 9 September 2017 at 18:18, W. Martin Borgert <deba...@debian.org> wrote:
> On 2017-09-09 21:04, Lisandro Damián Nicanor Pérez Meyer wrote:
>> = 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.
>
> If I understand the various posts in the FreeCAD forums correct,
> they seem to go for PySide2. It would be very helpful, if the
> Debian Qt maintainers could package PySide2! Maybe before Qt4 is
> removed, because otherwise some packages have to be removed just
> to introduce them again. I don't think that packaging PySide2
> outside of the Qt team makes sense, because PySide2 will be the
> "official" Python API of Qt, if I'm not mistaken.
> --
> "Furthermore, I consider that PySide2 must be packaged" -- Qt the Elder

So far no one in the team is interested in PySide2 and our current
manpower does not allows us to even take it as a pet package. I don't
know if asking upstream to use PyQt5 (which is kind of more official)
would be a good idea, else someone needs to step up to maintain
PySide2. Of course [s]he is welcomed in the team to do that!

Kinds regards, Lisandro.

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

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875202: [taurus] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: taurus
Version: 4.0.3+dfsg-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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875186: [soqt] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: soqt
Version: 1.6.0~e8310f-3
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875167: [qwtplot3d] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: qwtplot3d
Version: 0.2.7+svn191-10.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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875172: [rlplot] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: rlplot
Version: 1.5-3
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875158: [qtexengine] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: qtexengine
Version: 0.3-3
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875150: [qtiplot] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: qtiplot
Version: 0.9.8.9-16
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875086: [paraview] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: paraview
Version: 5.1.2+dfsg1-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] 


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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874901: [gle-graphics] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: gle-graphics
Version: 4.2.5-6
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875064: [octomap] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: octomap
Version: 1.8.1+dfsg-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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875041: [meshlab] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: meshlab
Version: 1.3.2+dfsg1-4
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875036: [libqglviewer] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: libqglviewer
Version: 2.6.3+dfsg2-3
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#875028: [liggghts] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: liggghts
Version: 3.4.0+repack1-2
3.7.0+repack1-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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874934: [kbibtex] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kbibtex
Version: 0.4-4
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874878: [freemat] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: freemat
Version: 4.2+dfsg1-1
4.2+dfsg1-5
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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874877: [freecad] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: freecad
Version: 0.16+dfsg2-3
0.16.6712+dfsg1-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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#874898: [gazebo] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: gazebo
Version: 7.8.1+dfsg-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-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784475: Done some work but crash before main()

[Lisandro Damián Nicanor Pérez Meyer]

On 5 September 2017 at 15:51, Bastien ROUCARIES
 wrote:
> Hi,
>
> I have done porting work but now it fail before main():

I'm afraid that the version you are working against is not yet ready for Qt5.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

[Lisandro Damián Nicanor Pérez Meyer]

And qt also does not produces exceptions, and that's by design.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

[Lisandro Damián Nicanor Pérez Meyer]

In other words: if you want to use Qt you *need* a QApplication instance.
That's Qt basics. Not using it is a bug.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

[Lisandro Damián Nicanor Pérez Meyer]

On sábado, 19 de noviembre de 2016 14:02:27 ART PICCA Frederic-Emmanuel wrote:
> > From the original bug report (the only thing I had up to know):
> I attached my backtrace in the bug report. this is why we are speaking about
> different things;)

And you seem to be solving another bug and not what the original reporter 
reported.

> > Then if the gdb backtrace in the original bug report is to be trusted then
> > you are indeed mixing Qt4 and Qt5. And you can expect dragons for doing
> > that ;-)
> the original bactrace was done by the initial bug reporter
> 
> then I tryed to reproduce the failure and I also got a segfault, but for a
> different reason.
> 
> so I think that there is a problem in the python pyqt5 binding...
> 
> let's investigate

I'm CCing the pyqt5 maintainer and expert. Python is not my realm really.

-- 
La vida no se mide por la cantidad de veces que respiramos,
sino por la cantidad de momentos que nos quitan la respiración.
  Anónimo

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

[Lisandro Damián Nicanor Pérez Meyer]

On sábado, 19 de noviembre de 2016 13:40:56 ART PICCA Frederic-Emmanuel wrote:
> > Hi Picca! Please next time you reassign a bug also CC the maintainer/team
> > that receives the bug, else we don't get this very text you wrote above
> > :-)
> sorry about that.

No problems, I've made the same mistake too :)
 
> > No, this not seems to be a Qt bug, and even less a Qt5 bug, as the lib
> > mentioned in the backtrace is from Qt4. By looking at the bug log I am
> > wondering if you are not happen to be mixing Qt4 and Qt5 in the same
> > package.
> I am not at all a Qt specialiste, so I red the first lines of the backtrace
> 
> #0  registerFont (fnt=0xbfffdd24) at text/qfontdatabase.cpp:1025
> #1  QFontDatabasePrivate::addAppFont (this=, fontData=...,
> fileName=...) at text/qfontdatabase.cpp:2436 #2  0xb47ea5dd in
> QFontDatabase::addApplicationFont (fileName=...) at
> text/qfontdatabase.cpp:2482 #3  0xb4c5bc0a in ?? () from
> /usr/lib/python2.7/dist-packages/PyQt5/QtGui.i386-linux-gnu.so #4 
> 0x800d6ba1 in call_function (oparg=, pp_stack=0xbfffde88) at
> ../Python/ceval.c:4352
> 
> then I seems to me that we where talking about PyQT5 (the binding) and then
> I deducted that the #0 where commin from qt5.
>
> How do I know from which library this is comming from.

From the original bug report (the only thing I had up to know): 

Few days ago, it was causing segmentation fault with the following backtrace:

(gdb) bt
#0  0x7f5b8788cca3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4

Note the 4 at the end, that comes from the SONAME of the lib. That's Qt4.

$ dpkg -S /usr/lib/x86_64-linux-gnu/libQtGui.so.4 

> I obtained these backtrace by installing the qt5 debug symbols and not the
> qt4 ones.

Then if the gdb backtrace in the original bug report is to be trusted then you 
are indeed mixing 
Qt4 and Qt5. And you can expect dragons for doing that ;-)

[snip]
> > Pass a null pointer to be dereferenced and you will get a segfault. And
> > that's purely missuse.
> 
> Yes this si why I like haskell ;)

Sadly haskell has no concept of ABI yet and everything needs a static build :-/

-- 
No subestimes el ancho de banda de un camión
cargado de cintas.
  Andrew S. Tanenbaum

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



signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

[Lisandro Damián Nicanor Pérez Meyer]

reassign 844601 python-spyder 3.0.1+dfsg1-1
thanks

Hi Picca! Please next time you reassign a bug also CC the maintainer/team that 
receives the bug, else we don't get this very text you wrote above :-)

On sábado, 19 de noviembre de 2016 12:40:25 ART picca wrote:
> Hello libqt5gui5 maintainer, I will reassign this bug to you since it seems
> that the segfault is in your library.

No, this not seems to be a Qt bug, and even less a Qt5 bug, as the lib 
mentioned in the backtrace is from Qt4. By looking at the bug log I am 
wondering if you are not happen to be mixing Qt4 and Qt5 in the same package.

Please double check all your dependencies that you are not mixing Qt4 and Qt5. 
And before reassigning to Qt please check that the issue is not in the 
bindings. Hint: try coding a minimal example.

Due to the above I'm reassigning you the bug.

> It can be caused by a missued of your
> library but nevertheless it should not segfault :).

Pass a null pointer to be dereferenced and you will get a segfault. And that's 
purely missuse.

Kinds regards, Lisandro.

-- 
A child of five could understand this.
Fetch me a child of five.
 -- Groucho Marx

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: Bug#828252: qtcreator is marked for autoremoval from testing

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 6 de noviembre de 2016 21:12:14 ART Ondřej Surý wrote:
> In the end it was very easy (hopefully) - the OpenSSL module is optional
> and hopefully this won't break anything :). Ccing other botan1.10 users.
> 
> Please test with botan1.10 - 1.10.13-1 that just got uploaded to
> unstable.

Hi Ondřej! Will check for sure!


-- 
Una sola bomba nuclear puede arruinar el resto de tu día.

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784455: Bumping severity to normal

[Lisandro Damián Nicanor Pérez Meyer]

severity 784449 normal
severity 784448 normal
severity 784612 normal
severity 784450 normal
severity 784451 normal
severity 784452 normal
severity 784453 normal
severity 784454 normal
severity 784456 normal
severity 784455 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
Videogames do not influence kids. I mean, if Pac-Man influenced our
generation, we would all be jumping in dark rooms, chomping magic pills
and listening to electronic repeating music.
  Kristian Wilson, Nintendo Inc. 1989

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784475: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784468 normal
severity 784470 normal
severity 784471 normal
severity 784472 normal
severity 784473 normal
severity 784475 normal
severity 784476 normal
severity 784477 normal
severity 784479 normal
severity 784480 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
Alas, I am dying beyond my means.
  Oscar Wilde, as he sipped champagne on his deathbed

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784464: Bumping severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 784457 normal
severity 784458 normal
severity 784459 normal
severity 784616 normal
severity 784460 normal
severity 784461 normal
severity 784462 normal
severity 784463 normal
severity 784464 normal
severity 784610 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.


-- 
"So long, and thanks for all the fish!"
  The Hitchhickers guide to the Galaxy

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784505: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784498 normal
severity 784615 normal
severity 784501 normal
severity 784614 normal
severity 784502 normal
severity 784503 normal
severity 784505 normal
severity 784507 normal
severity 784508 normal
severity 784509 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784613: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784619 normal
severity 784513 normal
severity 784514 normal
severity 784522 normal
severity 784523 normal
severity 784524 normal
severity 784525 normal
severity 784613 normal
severity 784532 normal
severity 784618 normal
thanks

Hi! As we intend to go further with this removal we are bumping it's severity.
If you need help please do not hesitate in replying to the bug, I am 
subscribed to it.

-- 
This end should point toward the ground if you want to go to space.
If it starts pointing toward space you are having a bad problem
and you will not get to space today.
  http://xkcd.com/1133/

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784613: Keep the severity in serious

[Lisandro Damián Nicanor Pérez Meyer]

severity 784614 serious
severity 784610 serious
severity 784615 serious
severity 784613 serious
severity 784616 serious
severity 784612 serious
thanks

My most sincere apologies to everyone in this mail, the python stuff is coming 
out sooner than the rest, so the severity should be kept as serious.


-- 
"So long, and thanks for all the fish!"
  The Hitchhickers guide to the Galaxy

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: libdxflib changes

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 05 January 2016 07:33:51 Alastair McKinstry wrote:
> Hi,
> 
> dxflib 3.12.2 is now upstream, and I have packaged it in the repo for
> review.
> git.debian.org/git/debian-science/packages/dxflib.git
> 
> I've made some changes:
> * I've changed the package name from libdxflib-2.5.0.0 to libdxflib3
> * Changed the SONAME accordingly to libdxflib.so.3
> 
> AIUI the package name should not include the minor release version, etc.
> as this means a
> transition on every minor change. It should include the major version
> only.  If library
> symbols are used correctly, the only change that should necessitate a
> full transition
> should then be one that deletes symbols. (The change from -2.5.0.0 would
> require
> a transition anyway).
> 
> Some changes still needed for upload:
> * update the symbols file
> * Add a libdxflib.so.3 -> libdxflib.so.3.12.2
> * Test transition.

Hi Alastair! I have removed myself from Uploaders in librecad but forgot this 
one. Please remove me from Uploaders whenever you can.

Thanks! Lisandro.



-- 
Outside of a dog, a book is man's best friend.
Inside of a dog, it's too dark to read.
 -- Groucho Marx

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784767: Cmake 3.2 uploaded

[Lisandro Damián Nicanor Pérez Meyer]

severity 784767 serious
thanks

CMake 3.2 has been uploaded to the archive.

-- 
Only wimps use tape backup: real men just upload their important stuff on
ftp, and let the rest of the world mirror it ;)
  Linus Benedict Torvalds.

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#784769: CMake 3.2 uploaded

[Lisandro Damián Nicanor Pérez Meyer]

severity 784769 serious
severity 784768 serious
severity 784766 serious
thanks

CMake has been uploaded to the archive.

-- 
Los chicos tienen un mayor dominio de la tecnología (y las habilidades y
lenguaje que eso implica) que los adultos con los que se relacionan. Por lo
general saben más que sus propios padres, sus docentes, sus pediatras,
psicólogos, que los políticos y funcionarios de sus comunidades. Eso afectó la
autoridad que tenía un adulto para habilitar al mundo.
  Luis Pescetti
  http://www.luispescetti.com/regale-su-obra/

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#699849: Bug#778644: qtdeclarative-opensource-src: port to m68k

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 18 February 2015 18:44:16 Thorsten Glaser wrote:
[snip]
 This is #699849 already – Cc’ing that bug since its main‐
 tainers should know we have a fix and upstream also fixed
 it. Note that this does not prevent you from applying the
 patch to any further uploads that d̲o̲ include the code un‐
 der 3rdparty/.

There will be no uploads to Qt 5.3.2 unless an RC bug is found, in which case 
only the RC bug will be fixed as required by the RT.
The newer versions (currently 5.4.0) are already available in experimental.

-- 
One World, One web, One program - Microsoft Promo ad.
Ein Volk, Ein Reich, Ein Führer - Adolf Hitler

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#756480: What is really needed

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 06 February 2015 22:27:14 Lisandro Damián Nicanor Pérez Meyer wrote:
[snip]
 I'll try to add a patch.

And here it is. I have checked that the package build fine but I haven't
checked if the generated cmake files work. If something arises do not hesitate
in pinging me and I'll fix it.

--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
diff --git a/debian/libdouble-conversion-dev.install b/debian/libdouble-conversion-dev.install
index fcc3f61..499e35d 100755
--- a/debian/libdouble-conversion-dev.install
+++ b/debian/libdouble-conversion-dev.install
@@ -2,4 +2,5 @@

 libdouble-conversion.so/usr/lib/${DEB_HOST_MULTIARCH}/
 libdouble-conversion.a /usr/lib/${DEB_HOST_MULTIARCH}/
+*.cmake/usr/lib/${DEB_HOST_MULTIARCH}/cmake/double-conversion/
 src/*.h/usr/include/double-conversion/
diff --git a/debian/rules b/debian/rules
index 2f0c291..5f6bc94 100755
--- a/debian/rules
+++ b/debian/rules
@@ -14,6 +14,9 @@ endif
 SO=1
 VERS=$(SO).0

+# Check CMakeLists.txt and update as necesary.
+CMAKE_VERSION=1.1.1
+
 SRC=$(shell echo src/*.cc)
 OBJ=$(SRC:.cc=.o)

@@ -52,11 +55,15 @@ run_tests: $(TEST_OBJ) libdouble-conversion.a
 	$(CXX) $(LDFLAGS) -o run_tests $^

 override_dh_auto_build: libdouble-conversion.so libdouble-conversion.a run_tests
+	sed s/@CONF_REL_INCLUDE_DIR@/usr/  double-conversionConfig.cmake.in  double-conversionConfig.cmake
+	sed s/@double-conversion_VERSION@/$(CMAKE_VERSION)/ double-conversionConfigVersion.cmake.in  double-conversionConfigVersion.cmake

 override_dh_auto_clean:
 	rm -f libdouble-conversion.* run_tests test/cctest/*.o
 	rm -rf debian/shared debian/static
 	rm -f debian/static_dir debian/shared_dir
+	rm -f double-conversionConfig.cmake
+	rm -f double-conversionConfigVersion.cmake

 override_dh_strip:
 	dh_strip --dbg-package=libdouble-conversion-dbg


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#756480: What is really needed

[Lisandro Damián Nicanor Pérez Meyer]

What the user asks is to generate the files that will help CMake to find 
libdouble-conversion.
The templates are already in the source (*.cmake.in) and should be installed 
in /usr/lib/arch-triplet/cmake/double-conversion/*.cmake

If you want to avoid modifying the scons file you can simply use sed in 
debian/rules to replace the @foo@ patterns in the *.cmake.in files with the 
correct values and you are ready to go.

I'll try to add a patch.

-- 
Q. How did the programmer die in the shower?
A. He read the shampoo bottle instructions: Lather. Rinse. Repeat.
  http://www.devtopics.com/best-programming-jokes/

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


signature.asc
Description: This is a digitally signed message part.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#765491: vtk6: Should not conditionally use Qt4 or Qt5

[Lisandro Damián Nicanor Pérez Meyer]

Source: vtk6
Version: 6.1.0+dfsg2-2
Severity: important

Hi! Since the mentioned version you conditionally depend on qt4 or qt5, such as:

qtbase5-dev [!armel !armhf]

That's a bug and a diservice to your users, as they need to also conditionally
use Qt4 on armel and armhf and Qt5 on the rest.

There are various possible solutions here:

- Keep vtk6 either in Qt4 or Qt5. If by keeping Qt5 vtk6 can not be built/used
  on armel/armhf any longer then it must be removed from those archs, along
  with the packages that build depend upon it.

- Provide packages both for Qt4 and Qt5. This requires double compilation, but
  it's doable. Sadly I think you are late for this option due to freeze being
  very near.

Please also note that by changing to Qt5 you also started an unnanounced
transition, as the packages that build depend upon vtk6 needs to get rebuilt.

As you didn't ask for the transition and you are late for doing it, you might
get a removal of vtk6 from testing along with all the packages that build
depend upon it. Please also note that I'm just warning you about the
posibility, as I am not part of the release team and so it's not my decistion.

Kinds regards, Lisandro.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers