Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1791985

Summary: libgpiod fails to build from dist-git in Fedora 32
Product: [Fedora] Fedora Reporter: Miro Hrončok <mhroncok>
Component: libgpiodAssignee: Peter Robinson <pbrobinson>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cstratak, mhroncok, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-28 13:46:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1750908, 1785415    

Description Miro Hrončok 2020-01-16 19:37:39 UTC
When we attempted to rebuild libgpiod for Python 3.9 we have realized that it has broken sources:

[libgpiod (master)]$ fedpkg prep
error: Bad source: .../libgpiod/libgpiod-1.5-rc2.tar.gz: No such file or directory
Could not execute prep: Failed to execute command.
[libgpiod (master)]$ cat sources 
SHA512 (libgpiod-1.5-rc2.tar.xz) = 64a877e0a73f8db59d24c88583f04fc9a0ab18ec0aee19a794812e9c9462c81407f4f73dfb5515b6c330b7b7ab694a5553f120b730e3f3e78e886d9320d6988f


Even with:

-Source0:       https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/snapshot/%{name}-%{version}%{?candidate:-%{candidate}}.tar.gz
+Source0:       https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/snapshot/%{name}-%{version}%{?candidate:-%{candidate}}.tar.xz


I get:

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3wRSJB
+ umask 022
+ cd /home/churchyard/rpmbuild/fedora-scm/libgpiod
+ cd /home/churchyard/rpmbuild/fedora-scm/libgpiod
+ rm -rf libgpiod-1.5-rc2
+ /usr/bin/xz -dc /home/churchyard/rpmbuild/fedora-scm/libgpiod/libgpiod-1.5-rc2.tar.xz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd libgpiod-1.5-rc2
/var/tmp/rpm-tmp.3wRSJB: line 38: cd: libgpiod-1.5-rc2: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.3wRSJB (%prep)


This gets me trough:

-%setup -q -n %{name}-%{version}%{?candidate:-%{candidate}}
+%setup -q -n %{name}-%{version}


Started a scratchbuild in https://koji.fedoraproject.org/koji/taskinfo?taskID=40629818

Comment 1 Miro Hrončok 2020-01-16 20:15:13 UTC
That gets it fixed. May I just push it?

Comment 2 Peter Robinson 2020-01-17 02:27:44 UTC
(In reply to Miro Hrončok from comment #1)
> That gets it fixed. May I just push it?

The RC2 was generated incorrectly upstream if you compare it to RC1, there will be a GA release in the next day or so. That change will then break future RCs, so I've left it broken an am awaiting the next RC or GA upstream. It's a known problem and I've left it that way for a reason.

Comment 3 Miro Hrončok 2020-01-17 10:13:37 UTC
Thanks for clarifying, I won't push anything and will await the next RC or GA upstream.