https://bugzilla.redhat.com/show_bug.cgi?id=2510630

Hans de Goede <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]



--- Comment #2 from Hans de Goede <[email protected]> ---
Note the -devel pkg does not install:

hans@t14s:/var/lib/mock/fedora-44-aarch64/result$ sudo rpm -ivh
quic-teec-1.0.2-1.fc44.aarch64.rpm quic-teec-devel-1.0.2-1.fc44.aarch64.rpm  
error: Failed dependencies:
        pkgconfig(qcbor) is needed by quic-teec-devel-1.0.2-1.fc44.aarch64

hans@t14s:/var/lib/mock/fedora-44-aarch64/result$ sudo dnf install
'pkgconfig(qcbor)' 
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
No match for argument: pkgconfig(qcbor)
You can try to add to command line:
  --skip-unavailable to skip unavailable packages

I think rpmbuild automatically adds the 'pkgconfig(qcbor)' dependency based on
a requires in the .pc file in the -devel package, but the actual provided
pkgconfig by libcbor-devel is 'pkgconfig(libcbor)'. So I think we need to patch
the .pc file and submit a fix for the .pc file upstream .


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2510630

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202510630%23c2

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to