Bug 2224027 - libzypp: FTBFS in Fedora Rawhide
Summary: libzypp: FTBFS in Fedora Rawhide
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libzypp
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-19 15:31 UTC by Ben Beasley
Modified: 2023-08-16 08:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Beasley 2023-07-19 15:31:15 UTC
Description of problem:
Package libzypp fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
17.31.8-2.fc39

Steps to Reproduce:
koji build --scratch f39 libzypp-17.31.8-2.fc39.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/libzypp

----

In file included from /builddir/build/BUILD/libzypp-17.31.8/zypp-curl/proxyinfo/ProxyInfoLibproxy:1,
                 from /builddir/build/BUILD/libzypp-17.31.8/zypp-curl/proxyinfo/proxyinfos.h:20,
                 from /builddir/build/BUILD/libzypp-17.31.8/zypp-curl/proxyinfo.cc:19:
/builddir/build/BUILD/libzypp-17.31.8/zypp-curl/proxyinfo/proxyinfolibproxy.h:18:10: fatal error: proxy.h: No such file or directory
   18 | #include <proxy.h>
      |          ^~~~~~~~~


Reproducible: Always

Steps to Reproduce:
1. fedpkg co libzypp
2. cd libzypp
3. fedpkg mockbuild
Actual Results:  
Build fails due to missing proxy.h.

Expected Results:  
Successful build.

Discovered while checking impact of https://src.fedoraproject.org/rpms/protobuf/pull-request/25.

Comment 1 Fedora Release Engineering 2023-08-16 08:13:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


Note You need to log in before you can comment on or make changes to this bug.