On 10/22/2013 11:27 AM, Xavier Bachelot wrote:
On 10/15/2013 10:13 AM, Xavier Bachelot wrote:
ECC seems to be allowed in Fedora now.
I've filled a bug against libgcrypt requesting to enable it :
https://bugzilla.redhat.com/show_bug.cgi?id=1019126
Once this is done, the libgcrypt-freeworld will
On Wed, Oct 23, 2013 at 4:16 AM, Xavier Bachelot xav...@bachelot.orgwrote:
Tested OK and karma given.
A major roadblock has been removed, enjoy :-)
Awesome!
Thanks,
Richard
On 10/15/2013 10:13 AM, Xavier Bachelot wrote:
ECC seems to be allowed in Fedora now.
I've filled a bug against libgcrypt requesting to enable it :
https://bugzilla.redhat.com/show_bug.cgi?id=1019126
Once this is done, the libgcrypt-freeworld will become useless.
ECC-enabled libgcrypt is now
On 07/31/2013 11:21 PM, Xavier Bachelot wrote:
Hi,
New version, merging changes from the new Fedora release :
spec : http://www.bachelot.org/fedora/SPECS/libgcrypt-freeworld.spec
srpm :
http://www.bachelot.org/fedora/SRPMS/libgcrypt-freeworld-1.5.3-1.fc19.1.src.rpm
Shall I open a formal review
On 08/09/2013 12:37 AM, Xavier Bachelot wrote:
On 08/08/2013 11:01 PM, Richard Shaw wrote:
For me the problem wasn't libaacs, but the aacs_info binary which seems to
independently link to libgcrypt. Before setting the LD_PRELOAD environment
variable it pretty much gave up getting any
On 08/03/2013 06:00 PM, Richard Shaw wrote:
Have you been able to set this?
I installed the resultant RPM but even with the ldconf file, all programs seem
to prefer the official libgcrypt library. In order to force it I had to
specify
the freeworld library with
For me the problem wasn't libaacs, but the aacs_info binary which seems to
independently link to libgcrypt. Before setting the LD_PRELOAD environment
variable it pretty much gave up getting any information about the blu-ray
video, afterwards it still failed, but it did try.
# ldd
On 08/08/2013 11:01 PM, Richard Shaw wrote:
For me the problem wasn't libaacs, but the aacs_info binary which seems to
independently link to libgcrypt. Before setting the LD_PRELOAD environment
variable it pretty much gave up getting any information about the blu-ray
video,
afterwards it
Have you been able to set this?
I installed the resultant RPM but even with the ldconf file, all programs
seem to prefer the official libgcrypt library. In order to force it I had
to specify the freeworld library with LD_PRELOAD=/path/to/freeworld/lib
Thanks,
Richard
Hi,
New version, merging changes from the new Fedora release :
spec : http://www.bachelot.org/fedora/SPECS/libgcrypt-freeworld.spec
srpm :
http://www.bachelot.org/fedora/SRPMS/libgcrypt-freeworld-1.5.3-1.fc19.1.src.rpm
Shall I open a formal review ticket or does anyone think that another
On Wed, Jul 31, 2013 at 4:21 PM, Xavier Bachelot xav...@bachelot.orgwrote:
Hi,
New version, merging changes from the new Fedora release :
spec : http://www.bachelot.org/fedora/SPECS/libgcrypt-freeworld.spec
srpm :
Hi,
On 06/11/2012 08:27 PM, Xavier Bachelot wrote:
On 06/11/2012 06:08 PM, Nicolas Chauvet wrote:
Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This is actually libgcrypt, not openssl,
Xavier,
Thanks for taking this up. I recently got a bluray drive for my desktop
machine but haven't gotten around to trying it yet...
Some pre-review comments:
1. Are you planning to keep a minimal diff from the upstream spec?
If not you can remove BuildRoot: and Group: tags.
2. Shouldn't
Hi Richard,
On 07/19/2013 05:17 PM, Richard Shaw wrote:
Xavier,
Thanks for taking this up. I recently got a bluray drive for my desktop
machine
but haven't gotten around to trying it yet...
It should hopefully be quite straightforward now.
yum install $PREFERRED_VIDEO_PLAYER libaacs
2012/8/19 Julian Sikorski beleg...@gmail.com:
W dniu 11.06.2012 18:08, Nicolas Chauvet pisze:
Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This lead the libaacs package to be partially
W dniu 11.06.2012 18:08, Nicolas Chauvet pisze:
Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This lead the libaacs package to be partially unuseable for it's target usage.
I would like to
2012/6/13 Kevin Kofler kevin.kof...@chello.at:
Nicolas Chauvet wrote:
I would like to list what would be possible workarounds for this
issue. We likely need to build a openssl-freeworld package:
- Build a similar package and drop a file in ld.conf.d to make it
system wide ? (the
Nicolas Chauvet wrote:
This could be true before the gold linker, I expect it tend to
disappear since we explicitly link a given library. I don't think
preload would mix symbols in this case.
The checks that got added are only link-time checks. The runtime ld.so still
works the same way as
Nicolas Chauvet wrote:
I would like to list what would be possible workarounds for this
issue. We likely need to build a openssl-freeworld package:
- Build a similar package and drop a file in ld.conf.d to make it
system wide ? (the freetype-freeworld way)
This seems unpractical as we may
On 06/11/2012 10:56 PM, Ken Dreyer wrote:
On Mon, Jun 11, 2012 at 12:23 PM, Richard Shaw hobbes1...@gmail.com wrote:
Unless something other than libaacs will use the freeworld package, I
think this is a prime example of why there needs to be exceptions to
the rules :)
I don't know of any
Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This lead the libaacs package to be partially unuseable for it's target usage.
I would like to list what would be possible workarounds for this
issue.
Unless something other than libaacs will use the freeworld package, I
think this is a prime example of why there needs to be exceptions to
the rules :)
I don't know of any formal approval mechanism here, but my vote would
be to allow the bundled/static linking for this and just following the
On 06/11/2012 06:08 PM, Nicolas Chauvet wrote:
Hi,
As you may know, the libaacs package from RPM Fusion rely on openssl
functions that have been disabled in the fedora package for some
reason.
This is actually libgcrypt, not openssl, but this is the same issue. ECC
is possibly
On Mon, Jun 11, 2012 at 12:23 PM, Richard Shaw hobbes1...@gmail.com wrote:
Unless something other than libaacs will use the freeworld package, I
think this is a prime example of why there needs to be exceptions to
the rules :)
I don't know of any formal approval mechanism here, but my vote
24 matches
Mail list logo