Re: [packman] Packman for Tumbleweed
Am Sonntag, 26. Juni 2016, 19:52:17 schrieb Dave Plater: > Is xine-lib linked to multimedia:xine? Yes, until this has been changed recently... > I just submitted a fix for the > Tumbleweed/Factory build Great, thanks! Kind Regards, Wolfgang ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
Is xine-lib linked to multimedia:xine? I just submitted a fix for the Tumbleweed/Factory build Dave On 6/20/16, Dave Plater wrote: > On 6/20/16, Olaf Hering wrote: >> On Mon, Jun 20, Dave Plater wrote: >> >>> So we can safely delete the other gstreamer packages or are there >>> packages that will get broken as a result? >> >> A few packages which are linked in but have no BUILD_ORIG or other knobs >> can be excluded from openSUSE_Tumbleweed. Looks like all _linked >> gstreamer packages (except -bad and -ugly), chromaprint and very few >> others are affected. I have done that already for 42.2. >> >> Some packages have now a hard requirement for ffmpeg3. I think today one >> can live without MPlayer and xine-lib. There are likely elegant ways to >> let such packages pick the available ffmpeg variant. >> >> Olaf >> > I can't live without xine, it's my primary video player, there's a > project still going on at mercurial but no release has happened for > years. It's also the only gui that emulates a dvd player properly for > preview in DVDStyler. MPlayer is for mswindows it never worked for me. > If there's a problem with xine ui or libs I'll have a look. > Dave > ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
On 6/20/16, Olaf Hering wrote: > On Mon, Jun 20, Dave Plater wrote: > >> So we can safely delete the other gstreamer packages or are there >> packages that will get broken as a result? > > A few packages which are linked in but have no BUILD_ORIG or other knobs > can be excluded from openSUSE_Tumbleweed. Looks like all _linked > gstreamer packages (except -bad and -ugly), chromaprint and very few > others are affected. I have done that already for 42.2. > > Some packages have now a hard requirement for ffmpeg3. I think today one > can live without MPlayer and xine-lib. There are likely elegant ways to > let such packages pick the available ffmpeg variant. > > Olaf > I can't live without xine, it's my primary video player, there's a project still going on at mercurial but no release has happened for years. It's also the only gui that emulates a dvd player properly for preview in DVDStyler. MPlayer is for mswindows it never worked for me. If there's a problem with xine ui or libs I'll have a look. Dave ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
On Mon, Jun 20, Dave Plater wrote: > So we can safely delete the other gstreamer packages or are there > packages that will get broken as a result? A few packages which are linked in but have no BUILD_ORIG or other knobs can be excluded from openSUSE_Tumbleweed. Looks like all _linked gstreamer packages (except -bad and -ugly), chromaprint and very few others are affected. I have done that already for 42.2. Some packages have now a hard requirement for ffmpeg3. I think today one can live without MPlayer and xine-lib. There are likely elegant ways to let such packages pick the available ffmpeg variant. Olaf ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
On 20 June 2016 at 12:02, Olaf Hering wrote: > On Mon, Jun 20, Richard Brown wrote: > >> Packman's current model for Tumbleweed, building against >> multimedia:libs and not Tumbleweed, means that Packman users get >> packages of the NEXT version of ffmpeg, gstreamer, etc, BEFORE it is >> ready for Tumbleweed > > Regarding gstreamer, I wonder what kind of testing is done. Can it do > anything useful in the variant from OBS? Looking at the spec files, only > -bad and -ugly rely on packman. openQA is fully capable of loading a video, going to a specific frame and confirming it renders properly, and listening to audio and ensuring the output from the sound card spectrographically matches a reference audience sample. So in short, we test if it works, not whether it's got a pretty spec file. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
On 6/20/16, Olaf Hering wrote: > On Mon, Jun 20, Richard Brown wrote: > >> Packman's current model for Tumbleweed, building against >> multimedia:libs and not Tumbleweed, means that Packman users get >> packages of the NEXT version of ffmpeg, gstreamer, etc, BEFORE it is >> ready for Tumbleweed We maintain packman in multimedia especially multimedia:libs, it takes too long for a package to filter through into Factory and even longer into Tumbleweed for us to do our job properly. I restored multimedia:libs/ffmpeg to 2.8 at the ire of the maintainers that first submitted it because of the builds that it might have broken in Packman. This is why there is an ffmpeg-2.8 package in Packman, to wait until upstream catches up, which they will do. >From an installation point of view ffmpeg library abi versions exist happily with each other on any system. Olaf has worked hard on ensuring that there are no system breakages due to the ffmpeg abi change. When all of the packages in OBS build against ffmpeg3 . Users don't use openSUSE's ffmpeg, it's crippled. It's main purpose in OBS is for packages to build against it and for a few packages that don't rely on it's libavcodec. There is nothing wrong with Tumbleweed having ffmpeg-2.8, users of ffmpeg have all updated to 3 from Packman anyway. See below for gstreamer. > > Regarding gstreamer, I wonder what kind of testing is done. Can it do > anything useful in the variant from OBS? Looking at the spec files, only > -bad and -ugly rely on packman. > >> This causes disruption, pain, heartache, and I've now lost track of >> the amount of times it's broken GNOME applications that used >> gstreamer. > > That would have been valueable information actually, especially for this > thread. > > Olaf > So we can safely delete the other gstreamer packages or are there packages that will get broken as a result? Dave ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman for Tumbleweed
On Mon, Jun 20, Richard Brown wrote: > Packman's current model for Tumbleweed, building against > multimedia:libs and not Tumbleweed, means that Packman users get > packages of the NEXT version of ffmpeg, gstreamer, etc, BEFORE it is > ready for Tumbleweed Regarding gstreamer, I wonder what kind of testing is done. Can it do anything useful in the variant from OBS? Looking at the spec files, only -bad and -ugly rely on packman. > This causes disruption, pain, heartache, and I've now lost track of > the amount of times it's broken GNOME applications that used > gstreamer. That would have been valueable information actually, especially for this thread. Olaf ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
