On Thu, Feb 02, Pascal Bleser wrote:
> Having a look at it, but I'm currently stuck because they require a
> patched libbluray so I have to submit the changes there first.
Is libbluray ABI compatible with the version that was released with Leap?
Both share the same SONAME, but given the history
@Olaf
weren't 13.x repos supposed to be removed by now?
Or perhaps the plan has been scuttled?
Regards
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
On Tue, Feb 07, Pascal Bleser wrote:
> Then the better solution would be to make a static build of libbluray
> into Handbrake, but not sure that is going to work without some heavy
> patching
Well, until then the latest and greatest is only available in
Tumbleweed. There is nothing wrong with
On Tue, Feb 07, Luigi Baldoni wrote:
> weren't 13.x repos supposed to be removed by now?
13.x was removed, its still available on the mirrors.
Its time to add a 42.3 target at some point.
Olaf
signature.asc
Description: PGP signature
___
Packman
2017-02-07 11:00 GMT+01:00 Olaf Hering :
> On Thu, Feb 02, Pascal Bleser wrote:
>
>> Having a look at it, but I'm currently stuck because they require a
>> patched libbluray so I have to submit the changes there first.
>
> Is libbluray ABI compatible with the version that was
2017-02-07 11:00 GMT+01:00 Olaf Hering :
> On Thu, Feb 02, Pascal Bleser wrote:
[...]
> Is libbluray ABI compatible with the version that was released with Leap?
> Both share the same SONAME, but given the history of libbluray failures
> its very likely that binaries not built
Hello,
I've been solving in #suse in past weeks with several ppl same problem:
They had installed some package(s) from packman but its deps (usually
subpackages from same build) were from repo-oss .. Good example is ffmpeg,
which shall looks after the successful installation:
# rpm -qa
On Tue, Feb 07, Daniel Pecka wrote:
> We were discussing this with olaf few weeks ago and I've suggested to
> ensure that proper libs from proper vendor are satisfied if you explicitely
> set your deps to be `= %version-%release' (eg they will require lib
> packages that have same version-release
It is indeed annoying because you end up with a setup that doesn't
play closed formats properly as it should be, with ffmpeg/libav
packages from different repositories. It also affects mplayer.
Until zypper implements that behavior (which sounds like a very good
idea to me), which won't be
On Mon, Jan 30, Olaf Hering wrote:
> It seems the bug was that publishing is disabled for Leap/i586, which
> appearently also covers all the -32bit packages in Leap/x86_64. Now
> publishing is enabled for Leap/i586, hopefully that was the missing
> knob. It may take some time until the packages
On Tue, Jan 10, Guo Yunhe wrote:
> Maybe the Git version is not stable enough for daily use yet. Could you
> package stable release as pcsx2 and unstable release pcsx2-beta?
There is now a pcsx2-32bit.rpm for Leap, please check if it works.
Olaf
signature.asc
Description: PGP signature
11 matches
Mail list logo