[packman] Blender that supports x264, etc

Stefan Botter jsj at jsj.dyndns.org
Wed Nov 4 09:49:52 CET 2015

Hi Jimmy,

On Tue, 3 Nov 2015 00:42:47 -0600
Jimmy Berry <jimmy at boombatower.com> wrote:

> I branched obs package, merged in previous packman build changes to
> enable ffmpeg, and cleaned up a bit. I was able to successfully build
> for Tumbleweed x86_64. When I installed locally the package worked
> great and I was able to use features that depend on ffmpeg which I am
> unable to do in the obs version.
> See for successful build:
> https://pmbs.links2linux.de/package/binaries/home:boombatower:branches:Extra/blender-update?repository=openSUSE_Tumbleweed
> Unfortunately, the majority of the time the packman obs instance seems
> to just loop trying to build the package since it ends up terminating
> the build process at some random percentage through the build. It
> seems like it is running out of ram.

Seems possible, as most workers are running chroot builds, where there
are no guaranteed resources, and hence builds with contraints are not
scheduled to build. ATM only swkj11-swkj14 are workers building in KVM,
and all but 11 had a configuration problem throughout October - so
nothing was built there. They are fixed now.

> The previous build on packman had
> the following memory _constraint:
>     <physicalmemory>
>       <size unit="M">1700</size>
>     </physicalmemory>
> I upped to 2000, but then it seems to never be scheduled. I am
> assuming none of the packman workers have that much ram?

> If so does anyone have suggestions for different build flags to
> possibly reduce ram usage during compile or acquire a more powerful
> worker or two?

Stefan Botter zu Hause
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.links2linux.de/pipermail/packman/attachments/20151104/cf108974/attachment.sig>

More information about the Packman mailing list