Processed: Re: Bug#785198: transition: GStreamer 0.10 removal
Processing commands for cont...@bugs.debian.org: > tags 785198 + confirmed Bug #785198 [release.debian.org] transition: GStreamer 0.10 removal Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 785198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#785198: transition: GStreamer 0.10 removal
On 16/05/15 09:50, Sebastian Dröge wrote: > On Sa, 2015-05-16 at 09:31 +0200, Emilio Pozuelo Monfort wrote: >> Hi Sebastian, >> >> On 13/05/15 13:09, Sebastian Dröge wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> >>> Hi, >>> >>> see rationale in this mailing list thread: >>> https://lists.debian.org/debian-devel/2015/05/msg00335.html >>> >>> It was suggested in that thread to also set up a transition tracker for >>> this. The main package involved here would be libgstreamer0.10-0, which >>> should go away and has libgstreamer1.0-0 as replacement already. >>> >>> The qt-gstreamer transition (#760003) already clears part of the >>> remaining GStreamer 0.10 dependencies. Additionally there are further >>> GStreamer 0.10 bindings: >>> >>> python-gst0.10 is replaced by python-gst1.0 / python3-gst1.0 >>> >>> libgstreamer0.9-cil is replaced by libgstreamer1.0-cil >>> (which is not yet uploaded, upstream release exists) >>> >>> libgstreamermm-0.10-2 would be replaced by libgstreamermm-1.0-XXX >>> (which is also not yet uploaded, upstream release exists) >>> >>> libgstreamer-perl, haskell-gstreamer >>> I'm not aware what the plans there are, the latter also has nothing >>> depending on it. >> >> I don't want to have hundreds of RC bugs just for this. You can file bugs at >> say >> important severity though, and when the list of rdeps gets down >> significantly, >> they can be raised to serious. Also sending a dd-list to debian-devel can be >> useful. > > I'll send a follow-up with dd-list to debian-devel later. > > As nobody did any porting of any of these packages over the last 3 > years, I doubt that any porting will happen just because I file non-RC > bugs for them :) But if you prefer that, I'm going to just file bugs > with important severity. You can warn that the goal is to remove gst 0.10 before the Stretch release and that if $package isn't ported, it is very likely to be removed from testing and not be included in Stretch. Also please usertag them so it's easy to track progress. > Not sure if I should also orphan the GStreamer > 0.10 packages on the next uploads, might be the most sensible thing to > do though. Your call. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55570d98.9080...@debian.org
Bug#785198: transition: GStreamer 0.10 removal
On Sa, 2015-05-16 at 09:31 +0200, Emilio Pozuelo Monfort wrote: > Hi Sebastian, > > On 13/05/15 13:09, Sebastian Dröge wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > Hi, > > > > see rationale in this mailing list thread: > > https://lists.debian.org/debian-devel/2015/05/msg00335.html > > > > It was suggested in that thread to also set up a transition tracker for > > this. The main package involved here would be libgstreamer0.10-0, which > > should go away and has libgstreamer1.0-0 as replacement already. > > > > The qt-gstreamer transition (#760003) already clears part of the > > remaining GStreamer 0.10 dependencies. Additionally there are further > > GStreamer 0.10 bindings: > > > > python-gst0.10 is replaced by python-gst1.0 / python3-gst1.0 > > > > libgstreamer0.9-cil is replaced by libgstreamer1.0-cil > > (which is not yet uploaded, upstream release exists) > > > > libgstreamermm-0.10-2 would be replaced by libgstreamermm-1.0-XXX > > (which is also not yet uploaded, upstream release exists) > > > > libgstreamer-perl, haskell-gstreamer > > I'm not aware what the plans there are, the latter also has nothing > > depending on it. > > I don't want to have hundreds of RC bugs just for this. You can file bugs at > say > important severity though, and when the list of rdeps gets down significantly, > they can be raised to serious. Also sending a dd-list to debian-devel can be > useful. I'll send a follow-up with dd-list to debian-devel later. As nobody did any porting of any of these packages over the last 3 years, I doubt that any porting will happen just because I file non-RC bugs for them :) But if you prefer that, I'm going to just file bugs with important severity. Not sure if I should also orphan the GStreamer 0.10 packages on the next uploads, might be the most sensible thing to do though. signature.asc Description: This is a digitally signed message part
Bug#785198: transition: GStreamer 0.10 removal
Hi Sebastian, On 13/05/15 13:09, Sebastian Dröge wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > see rationale in this mailing list thread: > https://lists.debian.org/debian-devel/2015/05/msg00335.html > > It was suggested in that thread to also set up a transition tracker for > this. The main package involved here would be libgstreamer0.10-0, which > should go away and has libgstreamer1.0-0 as replacement already. > > The qt-gstreamer transition (#760003) already clears part of the > remaining GStreamer 0.10 dependencies. Additionally there are further > GStreamer 0.10 bindings: > > python-gst0.10 is replaced by python-gst1.0 / python3-gst1.0 > > libgstreamer0.9-cil is replaced by libgstreamer1.0-cil > (which is not yet uploaded, upstream release exists) > > libgstreamermm-0.10-2 would be replaced by libgstreamermm-1.0-XXX > (which is also not yet uploaded, upstream release exists) > > libgstreamer-perl, haskell-gstreamer > I'm not aware what the plans there are, the latter also has nothing > depending on it. I don't want to have hundreds of RC bugs just for this. You can file bugs at say important severity though, and when the list of rdeps gets down significantly, they can be raised to serious. Also sending a dd-list to debian-devel can be useful. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5556f241.6030...@debian.org
Bug#785198: transition: GStreamer 0.10 removal
Hi Sebastian, On 13/05/15 13:09, Sebastian Dröge wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > see rationale in this mailing list thread: > https://lists.debian.org/debian-devel/2015/05/msg00335.html > > It was suggested in that thread to also set up a transition tracker for > this. The main package involved here would be libgstreamer0.10-0, which > should go away and has libgstreamer1.0-0 as replacement already. > > The qt-gstreamer transition (#760003) already clears part of the > remaining GStreamer 0.10 dependencies. Additionally there are further > GStreamer 0.10 bindings: > > python-gst0.10 is replaced by python-gst1.0 / python3-gst1.0 > > libgstreamer0.9-cil is replaced by libgstreamer1.0-cil > (which is not yet uploaded, upstream release exists) > > libgstreamermm-0.10-2 would be replaced by libgstreamermm-1.0-XXX > (which is also not yet uploaded, upstream release exists) > > libgstreamer-perl, haskell-gstreamer > I'm not aware what the plans there are, the latter also has nothing > depending on it. I don't want to have hundreds of RC bugs just for this. You can file bugs at say important severity though, and when the list of rdeps gets down significantly, they can be raised to serious. Also sending a dd-list to debian-devel can be useful. Cheers, Emilio -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5556f241.6000...@debian.org
Bug#785198: transition: GStreamer 0.10 removal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, see rationale in this mailing list thread: https://lists.debian.org/debian-devel/2015/05/msg00335.html It was suggested in that thread to also set up a transition tracker for this. The main package involved here would be libgstreamer0.10-0, which should go away and has libgstreamer1.0-0 as replacement already. The qt-gstreamer transition (#760003) already clears part of the remaining GStreamer 0.10 dependencies. Additionally there are further GStreamer 0.10 bindings: python-gst0.10 is replaced by python-gst1.0 / python3-gst1.0 libgstreamer0.9-cil is replaced by libgstreamer1.0-cil (which is not yet uploaded, upstream release exists) libgstreamermm-0.10-2 would be replaced by libgstreamermm-1.0-XXX (which is also not yet uploaded, upstream release exists) libgstreamer-perl, haskell-gstreamer I'm not aware what the plans there are, the latter also has nothing depending on it. Sebastian signature.asc Description: This is a digitally signed message part
