Bug 29561

Summary: libbluray, and 64 bit and -devel, does not contain bdnav or examples
Product: Mageia Reporter: Ken Arromdee <arromdee2>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA8TOO
Source RPM: libbluray-1.2.1-1.mga8.src.rpm CVE:
Status comment:

Description Ken Arromdee 2021-10-17 22:15:49 CEST 
Description of problem:
I was trying to find the bd_info program and it doesn't seem to exist anywhere, nor do the headers so I could build it myself.

Version-Release number of selected component (if applicable):
Mageia 8

How reproducible:
Always

Steps to Reproduce:
1. Try to find program "bd_info"
2. It does not exist
3. Try to find /usr/include/libbluray/bdnav directory
4. It does not exist
5. Notice that https://code.videolan.org/videolan/libbluray/-/blob/master/src/examples/bd_info.c exists
6. Notice that https://code.videolan.org/videolan/libbluray/-/tree/master/src/libbluray/bdnav exists

I don't know if parts were removed because of DRM reasons, but since the videolan version already doesn't include decryption because of DRM, I suspect this is not the reason.  I also don't see a tainted version of this.
Comment 1 Dave Hodgins 2021-10-18 00:35:51 CEST 
It's present in the srpm which is available on the mirrors, for example
https://mirror.math.princeton.edu/pub/mageia/distrib/8/SRPMS/core/release/libbluray-1.2.1-1.mga8.src.rpm which is what should be used for building
for yourself.

CC: (none) => davidwhodgins

Comment 2 Ken Arromdee 2021-10-18 07:21:00 CEST 
If bdnav headers are supposed to be exposed to users, they should be in -devel.  If they're not supposed to be exposed to users, then users can't be expected to compile anything that uses them, so executables that need them should be available already compiled as part of the package. 

The problem is that the way they are packaged is a sort of limbo where they're not exposed to users but the programs that use them aren't there either.

Putting them in the source RPM isn't a solution.  The source RPM is supposed to be there so you can compile the things that Mageia is distributing.  Compiling things that Mageia is not distributing is normally done by using -devel headers and linking against libraries.
Marja Van Waes 2021-10-19 22:46:48 CEST

Whiteboard: (none) => MGA8TOO
Version: 8 => Cauldron
CC: (none) => marja11
Assignee: bugsquad => pkg-bugs