Bug 16385 - chicken egg problem with pkgconfig(sane-backends)
Summary: chicken egg problem with pkgconfig(sane-backends)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-15 00:57 CEST by Herbert Poetzl
Modified: 2015-10-25 11:17 CET (History)
0 users

See Also:
Source RPM: sane-1.0.24-10.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Herbert Poetzl 2015-07-15 00:57:55 CEST 
Description of problem:
sane-1.0.24-10.mga5.src.rpm requires pkgconfig(sane-backends) for building, but pkgconfig(sane-backends) is provided by lib(64)sane1-devel, which is the result of rebuilding the sane-1.0.24-10.mga5.src.rpm

Version-Release number of selected component (if applicable):
sane-1.0.24-10.mga5

How reproducible:
Always

Steps to Reproduce:
1. get a clean system without sane development libraries
2. try to rebuild sane-1.0.24-10.mga5.src.rpm
3.

error: Failed build dependencies:
	pkgconfig(sane-backends) is needed by sane-1.0.24-10.mga5.x86_64

# urpmf -q --provides lib64sane1-devel
lib64sane1-devel:devel(libsane(64bit))
lib64sane1-devel:lib64sane1-devel[== 1.0.24-10.mga5]
lib64sane1-devel:lib64sane1-devel(x86-64)[== 1.0.24-10.mga5]
lib64sane1-devel:libsane-devel[== 1.0.24-10.mga5]
lib64sane1-devel:pkgconfig(sane-backends)[== 1.0.24]
lib64sane1-devel:sane-devel[== 1.0.24-10.mga5]


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-09-11 09:49:31 CEST 
Assigning to new sane maintainer.

Assignee: bugsquad => lists.jjorge

Comment 2 José Jorge 2015-10-25 11:17:17 CET 
This was fixed by blino in cauldron.

http://svnweb.mageia.org/packages/cauldron/sane/current/SPECS/sane.spec?r1=879479&r2=882168

 As this does not affect end users, I will not push an update for that.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.