Bug#875192: [simplescreenrecorder] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

El 26 nov. 2017 10:33 a.m., "James Cowgill" <jcowg...@debian.org> escribió:

Hi,

On 26/11/17 13:27, Lisandro Damián Nicanor Pérez Meyer wrote:
> El 26 nov. 2017 10:24 a.m., "Lisandro Damián Nicanor Pérez Meyer" <
> perezme...@gmail.com> escribió:
>
> El 26 nov. 2017 10:22 a.m., "James Cowgill" <jcowg...@debian.org>
escribió:
>
> Hi,
> [...]
>
>> The only minor thing I noted is that QPainter is included twince in
> 0003*, but
>> definitely nothing to worry too much.
>
> I have applied the patches with some slight modifications:
> - Remove the duplicate QPainter include.
> - Use DEB_CXXFLAGS_MAINT_APPEND instead of overriding QT5_CFLAGS.
>
>
> It might be worth to note that that
>
> My son little G came and pressed the right key to send the mail ;-)

Not to worry :)

> I was about to write that that flag should be already present if the
> project is using cmake or qmake. I have not checked the build system.

The build system is autotools and it uses pkg-config to discover all the
Qt libs and cflags etc. I did do some Google searching and I did notice
that CMake would fix this up for you, but I couldn't find anything about
this with autotools. I think adding -fPIC is fine for the moment, even
if it's only a workaround.


Yes, it's perfectly fine! And I think it's a qt bug already reported
upstream.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#875192: [simplescreenrecorder] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

El 26 nov. 2017 10:22 a.m., "James Cowgill"  escribió:

Hi,
[...]
> The only minor thing I noted is that QPainter is included twince in
0003*, but
> definitely nothing to worry too much.

I have applied the patches with some slight modifications:
- Remove the duplicate QPainter include.
- Use DEB_CXXFLAGS_MAINT_APPEND instead of overriding QT5_CFLAGS.


It might be worth to note that that
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#875192: [simplescreenrecorder] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

On sábado, 25 de noviembre de 2017 05:37:36 -03 gregor herrmann wrote:
> Control: tag -1 + patch
[snip]
> simplescreenrecorder bascially has Qt5 support upstream.
> With a bit of trial I managed to build the package, and the
> binary also seems to work afterwards :)
> 
> Find attached my changes
> - as one diff
> - as 3 git patches against HEAD of the packaging repo

Thanks gregor!!!

The only minor thing I noted is that QPainter is included twince in 0003*, but 
definitely nothing to worry too much.


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

Bug#875209: [traverso] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: traverso
Version: 0.49.4-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

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

Bug#875195: [stretchplayer] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: stretchplayer
Version: 0.503-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

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

Bug#875192: [simplescreenrecorder] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: simplescreenrecorder
Version: 0.3.8-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

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

Bug#875188: [soundscaperenderer] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: soundscaperenderer
Version: 0.4.2~dfsg-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

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

Bug#875112: [projectm] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: projectm
Version: 2.1.0+dfsg-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

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

Bug#874865: [faustworks] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: faustworks
Version: 0.5~repack0-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

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

Bug#874907: [hydrogen] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: hydrogen
Version: 0.9.7-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

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

Bug#874955: [kmidimon] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kmidimon
Version: 0.7.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

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

Bug#875047: [midisnoop] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: midisnoop
Version: 0.1.2~repack0-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

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

Bug#875049: [muse] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: muse
Version: 2.1.2-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

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

Bug#875050: [mustang-plug] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: mustang-plug
Version: 1.2-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

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

Bug#875042: [mixxx] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: mixxx
Version: 2.0.0~dfsg-7.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

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

Bug#875010: [libdrumstick] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: libdrumstick
Version: 0.5.0-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

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

Bug#874954: [kmetronome] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: kmetronome
Version: 0.10.1-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

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

Bug#874874: [ffdiaporama] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: ffdiaporama
Version: 1.5-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

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

Bug#874823: [ams] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: ams
Version: 2.1.1-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

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

Bug#874857: [dssi] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: dssi
Version: 1.1.1~dfsg0-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

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

Bug#874806: [abgate] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: abgate
Version: 1.1.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

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

Bug#874910: [iannix] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: iannix
Version: 0.9.17~dfsg0-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

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

Bug#874852: [dgedit] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: dgedit
Version: 0~git20160401-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

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

Bug#785576: Rosegarden crash due to presence of libqspiaccessiblebridge.so

[Lisandro Damián Nicanor Pérez Meyer]

On lunes, 11 de abril de 2016 11:24:46 A. M. ART Alexis wrote:
> Just wanted to add that i too experience this issue, which i've
> worked around by renaming:
> 
> /usr/lib/x86_64-linux-gnu/qt4/plugins/accessiblebridge/libqspiaccessiblebrid
> ge.so
> 
> to:
> 
> /usr/lib/x86_64-linux-gnu/qt4/plugins/accessiblebridge/.libqspiaccessiblebri
> dge.so
> 
> (i can't simply uninstall the qt-at-spi package, as that's
> transitively a dependency of gnome-core.)

qt-at-spi in initiated from

./X11/Xsession.d/90qt-a11y

You might want to take a look at that file and also try unsetting
QT_ACCESSIBILITY and QT_LINUX_ACCESSIBILITY_ALWAYS_ON

Maybe someone should file a bug to request the accessibility maintainers to 
add an option to disable the bridge system-wide by default.

-- 
"No es el crecimiento de la tecnología lo que excluye, sino la
protección sistemática de los derechos de uso de la misma,
lo cual se puede aplicar al arte."
  David Cuartielles

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

Bug#824956: Raising severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 824956 serious
thanks

Hi! Qt 5.6.1 has been released and we are ready to push it to unstable.

Kinds regards, Lisandro.

-- 
Paris, Je suis impregnée de ta présence!!!
vous cette une fleche alée qui traspase mon cour
  muxbalsoc. Comment posted in
  http://youtube.com/watch?v=G3S_sOEjsmo

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

Bug#824956: Errata

[Lisandro Damián Nicanor Pérez Meyer]

retitle 824956 QtQuick1 will be removed from the archive with Qt 5.6
thanks

I'm afraid I made a mistake: it's going away with 5.6.

-- 
"In college, I cooked some hot dogs by putting metal forks in each end of the
hot dog and running 120 volts through it. Hot dogs have just enough
conductivity so that this works well"
  greenroom(576281) - on a truly geeky way to cook hot dogs.
  Posted in Slashdot, also found in The Open Source Cookbook for Geeks.

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

Bug#824956: QtQuick1 will be removed from the archive with Qt 5.7

[Lisandro Damián Nicanor Pérez Meyer]

Source: musescore
Version: 2.0.2+dfsg-2
Severity: important

Hi! According to Qt's [upstream] QtQuick1 will be totally removed and
unsuported with Qt 5.7.

I'm afraid there is no way for us to keep this working.

Please suggest to your upstream to port the relevant code to QtQuick2 aka
QtDeclarative.

[upstream] 

Thanks, Lisandro.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

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

Bug#784457: 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.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#784456: 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.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#784496: Bumping severity

[Lisandro Damián Nicanor Pérez Meyer]

severity 784481 normal
severity 784483 normal
severity 784485 normal
severity 784484 normal
severity 784486 normal
severity 784487 normal
severity 784490 normal
severity 784491 normal
severity 784493 normal
severity 784496 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.

-- 
For want of a nail, the shoe was lost;
For want of the shoe, the horse was lost;
For want of the horse, the rider was lost;
For want of the rider, the battle was lost;
For want of the battle, the kingdom was lost;
And all for the want of a horseshoe nail
  http://www.everything2.com/index.pl?node_id=1097943

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

Bug#784531: Bumping severities

[Lisandro Damián Nicanor Pérez Meyer]

severity 784510 normal
severity 784511 normal
severity 784512 normal
severity 784516 normal
severity 784518 normal
severity 784527 normal
severity 784529 normal
severity 784531 normal
severity 784559 normal
severity 784560 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.

-- 
Wiki participants are, by nature, a pedantic, ornery, and unreasonable bunch.
So there's a camaraderie here we seldom see outside of our professional
contacts.
  http://www.c2.com/cgi/wiki?WhyWikiWorks

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

Bug#802710: ping!

[Lisandro Damián Nicanor Pérez Meyer]

Hi! I'm pining this bug because we are getting near of Qt 5.6 and we would 
really like to avoid having to rebuild musescore. Do you need any help with 
this?

Kinds regards, Lisandro.

-- 
Simulations are like miniskirts, they show a lot and hide the essentials.
  Hubert Kirrman

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

Bug#808781: Ping! We are near to remove qtquick1-5-dev

[Lisandro Damián Nicanor Pérez Meyer]

Hi! We will remove qtquick1-5-dev with Qt 5.6. Please check if the dependency 
is really needed, if you need help please ping Sune and I.

Kinds regards, Lisandro.

-- 
Contrary to popular belief, Unix is user friendly. It just happens to be
very selective about who it decides to make friends with.
  Unknown - http://www.linfo.org/q_unix.html

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

Re: Bug#809176: vlc: Should depend upon libqt5xcbqpa5

[Lisandro Damián Nicanor Pérez Meyer]

retitle 809176 Merge platforms plugins into libqt5gui5
thanks

With the team we decided to merge the plugins with libqt5gui5 for the time 
being.

This means that installing libqt5gui5 will need more dependencies. We summed 
up to be around ~3MiB in libs.

If at some point we are requested to split the plugins due to size issues 
(specially if the footprint somehow becomes ~10MiB) then I'm afraid that 
packages will start to need to depend/recommend the necessary plugins.

Kinds regards, Lisandro.

-- 
If you have an apple and I have an apple and we exchange these apples then you
and I will still each have one apple. But if you have an idea and I have an
idea and we exchange these ideas, then each of us will have two ideas.
 George Bernard Shaw

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

Re: Bug#809176: vlc: Should depend upon libqt5xcbqpa5

[Lisandro Damián Nicanor Pérez Meyer]

On Thursday 31 December 2015 18:52:57 Sebastian Ramacher wrote:
[snip] 
> vlc is not the place to fix broken Qt dependencies. If linking against
> libqt5x11extras5 requires libqt5xcbqppa5 to work, libqt5x11extras5 needs to
> depend on that package or emit proper dependencies via its symbols / shlibs
> file.

Hi Sebastian, vlc packagers! I'm afraid there is one misleading point here: 
the name of the package. It's not a lib at all, it just happens to be a plugin 
which links against a lib. The lib is totally private to the plugin. I'm 
planning to fix this in Qt 5.6.

So basically if you want to use Qt5 and *depend* on X11 you should really 
consider depending on this plugin.

Now I won't play ping-pong with the BTS. I'll let you decide what to do: 
either reassign this bug back to VLC or I'll close it on a few days.

Kinds regards, and the best for 2016, Lisandro.


-- 
So that's it - insecure, indiscriminate, user-hostile, slow, and full
of difficult, nit-picking people. Any other online community would
count each of these strengths as a terrible flaw. Perhaps wiki works
because the other online communities don't.
  PeterMerel about wikis

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

Bug#809176: vlc: Should depend upon libqt5xcbqpa5

[Lisandro Damián Nicanor Pérez Meyer]

Package: vlc
Version: 2.2.1-5+b1
Severity: normal

Hi! Sebastian Ramacher told me that vlc is a X11-only app. In other words,
even if it's built against Qt5 it depends upon X11 itself (Qt5 apps can run
without X11).

If that's the case then it should depend upon libqt5xcbqpa5, which is the
pluging used by Qt5 to use X11.

This is the case of a non-automatic dependency (ie, not catched by our
Debian tools) like QML stuff.

Kinds regards, Lisandro.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg-extra56   7:2.8.4-1
ii  libavutil-ffmpeg54  7:2.8.4-1
ii  libc6   2.21-4
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.4-1
ii  libegl1-mesa [libegl1-x11]  11.0.7-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-4
ii  libgl1-mesa-glx [libgl1]11.0.7-1
ii  libgles1-mesa [libgles1]11.0.7-1
ii  libgles2-mesa [libgles2]11.0.7-1
ii  libglib2.0-02.46.2-1
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-9
ii  libqt5gui5  5.5.1+dfsg-9
ii  libqt5widgets5  5.5.1+dfsg-9
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.12-1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-4
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-5+b1
ii  vlc-plugin-samba   2.2.1-5+b1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

-- no debconf information

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

Bug#807604: Not a VLC bug but a radeon one.

[Lisandro Damián Nicanor Pérez Meyer]

reassign 807604 xserver-xorg-video-radeon
thanks

The bug was not in VLC itself, so I'm reassign it.

X maintainers: the bug is the radeon driver crashing when VLC
is pointed to a specific stream, present in the original bug report.

Please do not heasitate to ask for more details as you see suitable.
I'll ad more info in a couple of minutes.

[ 1976.421686] [drm:cypress_dpm_set_power_state [radeon]] *ERROR* 
rv770_restrict_performance_levels_before_switch failed
[ 1986.592063] radeon :01:00.0: ring 5 stalled for more than 1msec
[ 1986.592079] radeon :01:00.0: GPU lockup (current fence id 
0x0002 last fence id 0x0008 on ring 5)
[ 1987.092053] radeon :01:00.0: ring 0 stalled for more than 10124msec
[ 1987.092069] radeon :01:00.0: GPU lockup (current fence id 
0x0003173b last fence id 0x00031744 on ring 0)
[ 1987.092080] radeon :01:00.0: ring 5 stalled for more than 10500msec
[ 1987.092086] radeon :01:00.0: GPU lockup (current fence id 
0x0002 last fence id 0x0008 on ring 5)
[ 1987.380171] [drm:rv770_stop_dpm [radeon]] *ERROR* Could not force DPM to low.
[ 1987.387114] radeon :01:00.0: couldn't schedule ib
[ 1987.387114] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)! 
[ 1987.389279] radeon :01:00.0: Saved 311 dwords of commands on ring 0.
[ 1987.389294] radeon :01:00.0: GPU softreset: 0x0088
[ 1987.389297] radeon :01:00.0:   GRBM_STATUS   = 0xA0003828
[ 1987.389299] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
[ 1987.389302] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[ 1987.389304] radeon :01:00.0:   SRBM_STATUS   = 0x20084AC0
[ 1987.389307] radeon :01:00.0:   SRBM_STATUS2  = 0x
[ 1987.389309] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
[ 1987.389312] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x0001
[ 1987.389314] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x0002
[ 1987.389317] radeon :01:00.0:   R_008680_CP_STAT  = 0x80010243
[ 1987.389320] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[ 1987.406730] radeon :01:00.0: GRBM_SOFT_RESET=0x4001
[ 1987.406784] radeon :01:00.0: SRBM_SOFT_RESET=0x8100
[ 1987.407930] radeon :01:00.0:   GRBM_STATUS   = 0x3828
[ 1987.407933] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
[ 1987.407935] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
[ 1987.407938] radeon :01:00.0:   SRBM_STATUS   = 0x200800C0
[ 1987.407940] radeon :01:00.0:   SRBM_STATUS2  = 0x
[ 1987.407943] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
[ 1987.407945] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x
[ 1987.407948] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x
[ 1987.407951] radeon :01:00.0:   R_008680_CP_STAT  = 0x
[ 1987.407953] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[ 1987.407968] radeon :01:00.0: GPU reset succeeded, trying to resume
[ 1987.428909] [drm] PCIE GART of 1024M enabled (table at 0x0025E000).
[ 1987.428986] radeon :01:00.0: WB enabled
[ 1987.428990] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x2c00 and cpu addr 0x8800bb3c9c00
[ 1987.428992] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x2c0c and cpu addr 0x8800bb3c9c0c
[ 1987.429964] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x0005c418 and cpu addr 0xc9c1c418
[ 1987.445975] [drm] ring test on 0 succeeded in 1 usecs
[ 1987.445981] [drm] ring test on 3 succeeded in 2 usecs
[ 1987.641630] [drm] ring test on 5 succeeded in 1 usecs
[ 1987.641641] [drm] UVD initialized successfully.


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

Bug#807604: Not a VLC bug but a radeon one.

[Lisandro Damián Nicanor Pérez Meyer]

On Wednesday 16 December 2015 21:04:02 Lisandro Damián Nicanor Pérez Meyer 
wrote:
[snip]
> I'll ad more info in a couple of minutes.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 17  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 27 20:43 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-8) ) #1 SMP Debian 4.2.6-3 (2015-12-06)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root  19031 Jul 24 19:37 /var/log/Xorg.3.log
-rw-r--r-- 1 root root  19030 Jul 24 19:37 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 416334 Aug 20 18:45 /var/log/Xorg.1.log
-rw-r--r-- 1 root root  51816 Dec 16 21:05 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[36.048]
X.Org X Server 1.17.3
Release Date: 2015-10-26
[36.048] X Protocol Version 11, Revision 0
[36.048] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[36.048] Current Operating System: Linux luna 4.2.0-1-amd64 #1 SMP Debian 
4.2.6-3 (2015-12-06) x86_64
[36.048] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=78cb5efd-5ed7-4d61-9beb-6cb55e9d0e53 ro drm.edid_strict=0 quiet
[36.048] Build Date: 27 October 2015  11:41:02PM
[36.048] xorg-server 2:1.17.3-2 (http://www.debian.org/support)
[36.048] Current version of pixman: 0.33.4
[36.048]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[36.048] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[36.049] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Dec 16 20:59:49 
2015
[36.265] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[36.592] (==) No Layout section.  Using the first Screen section.
[36.592] (==) No screen section available. Using defaults.
[36.592] (**) |-->Screen "Default Screen Section" (0)
[36.592] (**) |   |-->Monitor ""
[36.706] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[36.706] (==) Automatically adding devices
[36.706] (==) Automatically enabling devices
[36.706] (==) Automatically adding GPU devices
[36.957] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[36.957]Entry deleted from font path.
[37.299] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[37.299] (==) ModulePath set to "/usr/lib/xorg/modules"
[37.299] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[37.299] (II) Loader magic: 0x55ff8791bde0
[37.299] (II) Module ABI versions:
[37.299]X.Org ANSI C Emulation: 0.4
[37.299]X.Org Video Driver: 19.0
[37.299]X.Org XInput driver : 21.0
[37.299]X.Org Server Extension : 9.0
[37.303] (EE) systemd-logind: failed to get session: PID 1017 does not 
belong to any known session
[37.304] (II) xfree86: Adding drm device (/dev/dri/card0)
[37.307] (--) PCI:*(0:1:0:0) 1002:68f9:1682:3030 rev 0, Mem @ 
0xd000/268435456, 0xfdcc/131072, I/O @ 0xde00/256, BIOS @ 
0x/131072
[37.353] (II) LoadModule: "glx"
[37.505] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[38.341] (II) Module glx: vendor="X.Org Foundation"
[38.342]compiled for 1.17.3, module version = 1.0.0
[38.342]ABI class: X.Org Server Extension, version 9.0
[38.342] (==) AIGLX enabled
[38.342] (==) Matched ati as autoconfigured driver 0
[38.342] (==) Matched ati as autoconfigured driver 1
[38.342] (==) Matched modesetting as autoconfigured driver 2
[38.342] (==) Matched fbdev as autoconfigured driver 3
[38.342] (==) Matched vesa as autoconfigured driver 4
[38.342]

Bug#807604: Video stream makes PC hang

[Lisandro Damián Nicanor Pérez Meyer]

On Thursday 10 December 2015 17:46:28 Lisandro Damián Nicanor Pérez Meyer 
wrote:
[snip] 
> If in my phone I use something else than VLC the quality is far superior.

Or even Plasma 5's Dragon Player.

-- 
No hay preguntas tontas, solo tontos que no preguntan.
 personaje, en un mail del LugFi.

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

Bug#807604: Video stream makes PC hang

[Lisandro Damián Nicanor Pérez Meyer]

Package: vlc
Version: 2.2.1-5+b1
Severity: normal

Hi! If I point VLC at

  rtsp://stream.tn.com.ar/live/tnmovil3

Or whatever live stream [0] proposes at a certain time (the browser asks for
permission to launch an external app and VLC is used) I consistently
suffer from PC hangs. Sometimes a few minutes are displayed but at some point
the PC hangs, leaving no possibility to use neither keyboard nor mouse.

I have tried running it in both KDE's Plasma 5 and fluxbox with the same
end result.

I have also tried it in two machines, both amd64 running sid, one with an ATi
video card and the other with an Intel one.

I have not tried to ssh to the machine while this happens.

[0] 

As a different issue, the video quality is far from ideal, the problem
happening both on my machines and my android-based phone.

If in my phone I use something else than VLC the quality is far superior.


Kinds regards, Lisandro.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg-extra56   7:2.8.3-1
ii  libavutil-ffmpeg54  7:2.8.3-1
ii  libc6   2.21-3
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.4-1
ii  libegl1-mesa [libegl1-x11]  11.0.6-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-1
ii  libgl1-mesa-glx [libgl1]11.0.6-1
ii  libgles1-mesa [libgles1]11.0.6-1
ii  libgles2-mesa [libgles2]11.0.6-1
ii  libglib2.0-02.46.2-1
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.12-1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-1
ii  libva-drm1  1.6.1-1
ii  libva-x11-1 1.6.1-1
ii  libva1  1.6.1-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
pn  vlc-plugin-notify  
ii  vlc-plugin-samba   2.2.1-5+b1
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

-- no debconf information

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

Bug#802710: musescore: Embeds Qt5's private headers without putting them in a namespace

[Lisandro Damián Nicanor Pérez Meyer]

On Friday 23 October 2015 15:53:37 Sebastian Ramacher wrote:
> Hi
[snip]
> > By building this header without a namespace the symbols that it generates
> > matchs the symbols of qtbase's private stuff, so unnecesarily being part
> > of transitions like this.
> The xmlstream stuff is not the problem. They are not unresolved symbols and
> do not cause a dependency on qtbase-abi-5-5-1. They probably clash with the
> symbols from Qt, but that's easy to fix with a namespace or renaming the
> copy of QXmlUtils.
> 
> Looking at the output of dpkg-shlibdeps with -v -v shows the actual problem:
> |  Looking up symbol
> |  _ZN12QPaintEngineC2ER19QPaintEnginePrivate6QFlagsINS_18PaintEngineFeatur
> |  eEE@Base Found in symbols file of libQt5Gui.so.5 (minver: 5.0.2, dep:
> |  libqt5gui5 #MINVER#, qtbase-abi-5-5-1)
> This might be caused by mscore/paintengine_p.h and mscore/svgenerator.*
> where the QPaintEngine and QPaintEnginePrivate are used.

Thanks a lot for the head up Sebastian :)

Indeed that seems to be the cause, and using a namespace or renaming the 
classes should fix it.

Or avoiding using Qt's internal at all, of course.

-- 
http://xkcd.com/150/
Personas como ésta no se encuentran todos los días. Y cuando uno las
encuentra, suelen no estar disponibles.
Si encontrás una, no la pierdas.

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

Bug#802705: musescore: FTBFS while rebuilding against newest Qt5 private headers

[Lisandro Damián Nicanor Pérez Meyer]

Source: musescore
Version: 2.0.2+dfsg-1
Severity: serious
Justification: FTBFS

Hi! Musescore FTBFS when rebuilding against the new Qtbase's private headers:

https://buildd.debian.org/status/package.php?p=musescore

The problem seems to be:

/«BUILDDIR»/musescore-2.0.2+dfsg/libmscore/clef.cpp:58:7: error: narrowing 
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
   };



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

Bug#802710: musescore: Embeds Qt5's private headers without putting them in a namespace

[Lisandro Damián Nicanor Pérez Meyer]

Source: musescore
Version: 2.0.2+dfsg-1
Severity: important

Hi! While doing qt5's qtbase's private headers transition we noted that 
musescore
got into the list of packages that needed a transition [lop] but without
build depending on qtbase5-dev.

[lop] 

My teammate Dmitry Schanev found out that musescore ships a Qt5 private header:



By building this header without a namespace the symbols that it generates 
matchs the symbols
of qtbase's private stuff, so unnecesarily being part of transitions like this.

This is easily solvable by putting the headers under a namespace (like 
musescore3rdparty,
for example) and using them trough it.

Another better solution is to avoid embedding private stuff at all, of course :)

Kinds regards, Lisandro.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

Bug#789481: My bad

[Lisandro Damián Nicanor Pérez Meyer]

My bad, musescore in testing is still built against qt4, so it should not be a 
problem for Qt5 transitioning.

Sorry for the noise!

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!

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

Bug#789481: Stops Qt5 transition

[Lisandro Damián Nicanor Pérez Meyer]

Hi musescore maintainers! I'm afraid this FTBFS is stopping the Qt5 
transition. I'll try to look at the proposed fix in the other related bug, but 
it would be really cool if you can get to it sooner.

Kinds regards, Lisandro.

-- 
Tiempo para el tiempo y un rato mas.
  Profecías, Vox Dei, basado en Eclesiastes 3:1-9

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

Bug#661418: Does not works with ALSA, but it does with Jack

[Lisandro Damián Nicanor Pérez Meyer]

Package: vlc
Version: 2.0.0-3
Severity: important

Hi! After I upgraded to 2.0.0-2 (I just went to -3 to see if the bug is fixed,
but it seems not) I can't output sound using ALSA. If I switch to Jack, it will 
work
perfectly.

If I downgrade to the version in testing (1.1.13-1+b1), it works perfectly.

To test, try getting an flv with youtubdl and play it.

I'm running KDE with phonon using either the vlc or gstreamer backends, same 
problem
with both of them.

Interestingly enough, using VLC as a phonon backend, sounds is as good as usual.

Feel free to ask for more info if needed.

Kinds regards, Lisandro.

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

Kernel: Linux 3.2.1+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages vlc depends on:
ii  libaa11.4p5-39
ii  libavcodec53  4:0.8-1+b1
ii  libavutil51   4:0.8-1+b1
ii  libc6 2.13-26
ii  libfreetype6  2.4.8-1
ii  libfribidi0   0.19.2-2
ii  libgcc1   1:4.6.2-15
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libice6   2:1.0.7-2
ii  libqtcore44:4.7.4-2
ii  libqtgui4 4:4.7.4-2
ii  libsdl-image1.2   1.2.12-1
ii  libsdl1.2debian   1.2.15-2
ii  libsm62:1.2.0-2
ii  libstdc++64.6.2-15
ii  libtar0   1.2.11-8
ii  libva-x11-1   1.0.14-1
ii  libva11.0.14-1
ii  libvlccore5   2.0.0-3
ii  libx11-6  2:1.4.4-4
ii  libxcb-composite0 1.8-2
ii  libxcb-keysyms1   0.3.8-1
ii  libxcb-randr0 1.8-2
ii  libxcb-render01.8-2
ii  libxcb-shape0 1.8-2
ii  libxcb-shm0   1.8-2
ii  libxcb-xfixes01.8-2
ii  libxcb-xv01.8-2
ii  libxcb1   1.8-2
ii  libxext6  2:1.3.0-3
ii  libxinerama1  2:1.1.1-3
ii  libxpm4   1:3.5.9-4
ii  ttf-freefont  20100919-1
ii  vlc-nox   2.0.0-3
ii  zlib1g1:1.2.6.dfsg-2

Versions of packages vlc recommends:
ii  vlc-plugin-notify  none
ii  vlc-plugin-pulse   none
ii  xdg-utils  1.1.0~rc1+git20111210-6

Versions of packages vlc suggests:
pn  videolan-doc  none

-- no debconf information



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

Bug#630549: More info

[Lisandro Damián Nicanor Pérez Meyer]

tag 630549 moreinfo
thanks

Hi Christian!

Could you please tell me if you are using an nvidia or ati video card? If so, 
wich driver are you using?

Kinds regards, Lisandro.

-- 
* lisandropm debería escribir una canción mientras compila
elruso soy un ractor... soy un riciclo...
elruso ...que sufreee. en este mundooo...
elruso despues vas a operacion triunfo
elruso entrevista a lisandro:
elruso * Como compuso su super-exito?
elruso * Estaba compìlando qtopia-core para una gumstix y me puse a
 componer...
elruso -_-
  Visto en #bblug irc.freenode.net

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

Re: Bug#578750: ITP: kmid -- MIDI/Karaoke player for KDE

[Lisandro Damián Nicanor Pérez Meyer]

2010/4/22 Adrian Knoth a...@drcomp.erfurt.thur.de:
 On Thu, Apr 22, 2010 at 10:40:54AM -0300, Lisandro Damián Nicanor Pérez Meyer 
 wrote:
[big snip]

 The best solution for a dynamically linked program would be to simply
 upgrade the drumstick library. But as Debian is distributing a
 statically compiled  KMidimon, please apply preventively a patch
 before the next KMidimon release.


 In other words: it's now the right time to package drumstick separately
 and change the build requirements for kmidimon.

 Do you mind packaging drumstick?

First of all, sorry for not replying sooner. I just found out that I
had a broken mail filter :-/

No, I don't mind packaging drumstick. I'll fill the ITP ASAP.

 I'm also Cc pkg-multimedia-maintainers, perhaps somebody is interested.

I just checked the web and couldn't find an ITP bug for it, so I
assume nobody has started to package it.

 Don't know if you do a lot of multimedia stuff, if so, you might want to
 consider joining our team. ;)

I'm currently doing mostly KDE related packaging, but I will consider
your suggestion :-)

Regards, Lisandro.

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

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers