Re: Call to retire gstreamer-0.10

2017-02-13 Thread Scott Talbert
On Tue, 31 Jan 2017, Sérgio Basto wrote: How about handling it the same way we handle old GtkWebKit versions? As soon as F26 is branched from Rawhide (expected in 2017-02-21), retire this package? This would give package maintainers enough time to get their packages fixed (about 9 months) until

Re: Call to retire gstreamer-0.10

2017-01-31 Thread Sérgio Basto
On Ter, 2017-01-31 at 11:29 +, Christian Stadelmann wrote: > How about handling it the same way we handle old GtkWebKit versions? > As soon as F26 is branched from Rawhide (expected in 2017-02-21), > retire this package? This would give package maintainers enough time > to get their packages fi

Re: Call to retire gstreamer-0.10

2017-01-31 Thread Ms Sanchez
On 31/01/17 11:29, Christian Stadelmann wrote: How about handling it the same way we handle old GtkWebKit versions? As soon as F26 is branched from Rawhide (expected in 2017-02-21), retire this package? This would give package maintainers enough time to get their packages fixed (about 9 mont

Re: Call to retire gstreamer-0.10

2017-01-31 Thread Christian Stadelmann
sorry, I meant webkitgtk4 instead of gtkwebkit4. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Call to retire gstreamer-0.10

2017-01-31 Thread Christian Stadelmann
How about handling it the same way we handle old GtkWebKit versions? As soon as F26 is branched from Rawhide (expected in 2017-02-21), retire this package? This would give package maintainers enough time to get their packages fixed (about 9 months) until Fedora 27 is released. Any package that h

Re: Call to retire gstreamer-0.10

2017-01-31 Thread Christian Stadelmann
> exaile They are working on a port to Gtk3/GObject including a port to Gtk3WebKit2 a.k.a. gtkwebkit4. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Call to retire gstreamer-0.10

2017-01-30 Thread Johnny Robeson
> beets-plugins Beets can use gstreamer 1.x in the latest releases. I sent this weeks ago when it was a popular topic, but my email client was misconfigured, so it never made it. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe se

Re: Call to retire gstreamer-0.10

2016-12-11 Thread Heiko Adams
I've got a radiotray package which includes patches from a pending pull request to use gstreamer-1 instead of gstreamer: https://copr.fedorainfracloud.org/coprs/heikoada/xfce4-addons/package/radiotray/ Maybe someone wants to grab it and update radiotray to use gstreamer-1 Am 11.12.2016 um 14:43

Re: Call to retire gstreamer-0.10

2016-12-11 Thread William Moreno
I have checked the git history of exile upstream and did not seem gstreamer1 related work :( El 7/12/2016 10:47 p. m., "Michael Cronenworth" escribió: On 12/07/2016 05:07 PM, Sérgio Basto wrote: > gstreamermm-1.4.3-1.fc25 looks like already use gstreamer1 > subtitleeditor-0.53.0-1.fc25 also

Re: Call to retire gstreamer-0.10

2016-12-11 Thread Peter Oliver
On 10 Dec 2016 1:45 p.m., "Ralf Corsepius" wrote: On 12/10/2016 02:16 PM, Peter Oliver wrote: > On 9 Dec 2016 5:02 a.m., "Kevin Kofler" > wrote: > > Retiring such a library > is a very long process and not doable within a Fedora release. > > Is this true?

Re: Call to retire gstreamer-0.10

2016-12-10 Thread Ralf Corsepius
On 12/10/2016 02:16 PM, Peter Oliver wrote: On 9 Dec 2016 5:02 a.m., "Kevin Kofler" mailto:kevin.kof...@chello.at>> wrote: Retiring such a library is a very long process and not doable within a Fedora release. Is this true? Yes, it is. One could drop a library and it's dependants a

Re: Call to retire gstreamer-0.10

2016-12-10 Thread Peter Oliver
On 9 Dec 2016 5:02 a.m., "Kevin Kofler" wrote: Retiring such a library is a very long process and not doable within a Fedora release. Is this true? One could drop a library and it's dependants and that would be that. The trouble only comes if one wants to drop a library without dropping it's

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Kevin Kofler
Michael Cronenworth wrote: > Last month there were a handful of security vulnerabilities disclosed[1] > and upstream no longer maintains the 0.10 series. While we could patch and > update our Fedora packages this is a perfect opportunity to retire it. You will need to address the vulnerabilities a

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Michael Catanzaro
On Thu, 2016-12-08 at 14:24 +0100, Dominik 'Rathann' Mierzejewski wrote: > One important example is the Citrix Receiver for Linux[1], which > depends on > gstreamer-0.10: > $ rpm -qR ICAClient|grep gst > libgstapp-0.10.so.0()(64bit) > libgstbase-0.10.so.0()(64bit) > libgstinterfaces-0.10.so.0()(64b

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Dec 07, 2016 at 10:47:12PM -0600, Michael Cronenworth wrote: > On 12/07/2016 05:07 PM, Sérgio Basto wrote: > > gstreamermm-1.4.3-1.fc25 looks like already use gstreamer1 > >subtitleeditor-0.53.0-1.fc25 also already use gstreamer1 > > > > That's good! My initial list was run from Fedora 24

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Petr Pisar
On 2016-12-07, Michael Cronenworth wrote: > perl-GStreamer > perl-GStreamer-Interfaces No problem. We have perl-GStreamer1 as a binding for the new API and no other package uses these two. -- Petr ___ devel mailing list -- devel@lists.fedoraproject.org

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Michael Schwendt
On Wed, 07 Dec 2016 11:46:52 -0800, Adam Williamson wrote: > On Wed, 2016-12-07 at 10:51 -0600, Yaakov Selkowitz wrote: > > soundconverter > > I use this a lot, but there is active work on it upstream and the > active git branch (py3k) uses gstreamer 1.0: > > https://github.com/kassoulet/sound

Re: Call to retire gstreamer-0.10

2016-12-08 Thread Dominik 'Rathann' Mierzejewski
Hi! On Wednesday, 07 December 2016 at 17:06, Michael Cronenworth wrote: [...] > Here is an approximate list of packages depending on gst-0.10. They > themselves should be considered obsolete or retirement material as their > upstreams may not have adopted gst-1.0. If the package doesn't have a > g

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Michael Cronenworth
On 12/07/2016 04:29 PM, Peter Robinson wrote: -1 at least for the moment. b Is this due to sugar? Would you accept patches? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Peter Robinson
On Thu, Dec 8, 2016 at 4:53 AM, Peter Robinson wrote: > On Thu, Dec 8, 2016 at 4:49 AM, Michael Cronenworth wrote: >> On 12/07/2016 04:29 PM, Peter Robinson wrote: >>> >>> -1 at least for the moment. b >> >> >> Is this due to sugar? Would you accept patches? > > One of the reasons, and of course,

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Peter Robinson
On Thu, Dec 8, 2016 at 4:49 AM, Michael Cronenworth wrote: > On 12/07/2016 04:29 PM, Peter Robinson wrote: >> >> -1 at least for the moment. b > > > Is this due to sugar? Would you accept patches? One of the reasons, and of course, I think if we want to actively retire packages we need to enage w

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Michael Cronenworth
On 12/07/2016 05:07 PM, Sérgio Basto wrote: gstreamermm-1.4.3-1.fc25 looks like already use gstreamer1 subtitleeditor-0.53.0-1.fc25 also already use gstreamer1 That's good! My initial list was run from Fedora 24 at the time. Here is a revised list run from Rawhide (with Python packages):

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Scott Talbert
On Wed, 7 Dec 2016, Sérgio Basto wrote: Hi, like webkit < 3 retirement , you shouldn't repoquery with --recursive, If I am correct . Again after wxGTK and wxGTK3 be updated all dependencies will be solved automatically , also same case for wxPython , If I am correct. Incorrect.  I was talking

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Sérgio Basto
On Qua, 2016-12-07 at 10:51 -0600, Yaakov Selkowitz wrote: > On 2016-12-07 10:06, Michael Cronenworth wrote: > > > > As I'm sure everyone is well aware gstreamer-0.10 is obsolete and > > has > > been replaced by gstreamer-1.0. An upstream release for gst-0.10 > > has not > > been made in over 4 ye

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Peter Robinson
On Wed, Dec 7, 2016 at 4:59 PM, Michael Catanzaro wrote: > On Wed, 2016-12-07 at 10:06 -0600, Michael Cronenworth wrote: >> While we could patch and update our >> Fedora packages this is a perfect opportunity to retire it. > > I just want to add an explicit +1 in support of this proposal. Package

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Johnny Robeson
> beets-plugins Beets uses gstreamer 1.x in the latest release. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Adam Williamson
On Wed, 2016-12-07 at 10:51 -0600, Yaakov Selkowitz wrote: > soundconverter I use this a lot, but there is active work on it upstream and the active git branch (py3k) uses gstreamer 1.0: https://github.com/kassoulet/soundconverter/ there hasn't been a stable release of the 'new generation' code

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Simon Farnsworth
> On 7 Dec 2016, at 18:20, Sérgio Basto wrote: > > Thanks for reply > > On Qua, 2016-12-07 at 11:56 -0600, Yaakov Selkowitz wrote: >> On 2016-12-07 11:49, Sérgio Basto wrote: >>> >>> Hi, like webkit < 3 retirement , you shouldn't repoquery with >>> --recursive, If I am correct . >>> >>> Agai

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Michael Cronenworth
On 12/07/2016 12:20 PM, Sérgio Basto wrote: But for gstreamer-python we don't have gstreamer1-python ? so how we can fix the packages that have dependencies on gstreamer-python ? Gstreamer 1.0 introduced GI support so you would port your python apps to use that instead. __

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Sérgio Basto
Thanks for reply  On Qua, 2016-12-07 at 11:56 -0600, Yaakov Selkowitz wrote: > On 2016-12-07 11:49, Sérgio Basto wrote: > > > > Hi, like webkit < 3 retirement , you shouldn't repoquery with > > --recursive, If I am correct . > > > > Again after wxGTK and wxGTK3 be updated all dependencies will b

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Yaakov Selkowitz
On 2016-12-07 11:49, Sérgio Basto wrote: Hi, like webkit < 3 retirement , you shouldn't repoquery with --recursive, If I am correct . Again after wxGTK and wxGTK3 be updated all dependencies will be solved automatically , also same case for wxPython , If I am correct. Incorrect. I was talking

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Sérgio Basto
On Qua, 2016-12-07 at 10:51 -0600, Yaakov Selkowitz wrote: > On 2016-12-07 10:06, Michael Cronenworth wrote: > > > > As I'm sure everyone is well aware gstreamer-0.10 is obsolete and > > has > > been replaced by gstreamer-1.0. An upstream release for gst-0.10 > > has not > > been made in over 4 ye

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Yaakov Selkowitz
On 2016-12-07 10:06, Michael Cronenworth wrote: As I'm sure everyone is well aware gstreamer-0.10 is obsolete and has been replaced by gstreamer-1.0. An upstream release for gst-0.10 has not been made in over 4 years. Last month there were a handful of security vulnerabilities disclosed[1] and up

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Michael Catanzaro
On Wed, 2016-12-07 at 10:06 -0600, Michael Cronenworth wrote: >  While we could patch and update our  > Fedora packages this is a perfect opportunity to retire it. I just want to add an explicit +1 in support of this proposal. Packages with insecure dependencies like gstreamer-0.10 are not likely

Re: Call to retire gstreamer-0.10

2016-12-07 Thread Yaakov Selkowitz
On 2016-12-07 10:06, Michael Cronenworth wrote: As I'm sure everyone is well aware gstreamer-0.10 is obsolete and has been replaced by gstreamer-1.0. An upstream release for gst-0.10 has not been made in over 4 years. Last month there were a handful of security vulnerabilities disclosed[1] and up