[packman] rebuilding gstreamer every day?

Olaf Hering olaf at aepfle.de
Mon Jun 20 06:22:35 CEST 2016


On Sun, Jun 19, Richard Brown wrote:

> On 19 June 2016 at 16:41, Dave Plater <davejplater at gmail.com> wrote:
> >> The pkg in multimedia:libs is about one hundred, thousand, million
> >> times more at risk of being broken than the pkg in Factory
> >
> > Not if it's well maintained
> 
> There is _NO SUCH THING_ as a well maintained Devel Project.

Are you sure about that?! In the end they are not more than a compile
test unless they are actively used.

> End result: Any Packman user is now forced to upgrade ffmpeg and
> potentially ffmpeg related packages, including many multimedia
> applications, to the versions in packman to a version of ffmpeg which
> is UNTESTED and NOT SUPPORTED by the openSUSE Project (yet)

The installed packages have to be switched to the variants from packman
anyway to get an consistent state. Usually the advice is 'zypper dup -r
packman' or the yast2 gui equivalent. Also I'm not sure why any of that
should be "supported" by anyone. If one wants the codecs one switches
parts of the system to packman due to lack of an other vehicle to
deliver such things.

> Packman for Leap should be linked to the version in Leap, so that
> users do not have to suffer needless risk upgrading their packages.

This comes up every now and then, and so far there was no need for that.
Due to the lack of details from the OP I assume it was just the ordinary
rebuild and the fact that gstreamer is not 100% safe regarding
build-compare, which caused all the upgrades.

There is always a tradeoff between "wanting the latest" and "just wand
the codecs". The latter could be tested for 42.2 by creating a few
42.2_<pkg> (gstreamer*, ffmpeg) which link to OBS:42.2:Update.


Other than that I think you should take a walk around the building
before using the "Send" button, followed by rephrasing the entire reply.

Olaf




More information about the Packman mailing list