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
Bug 1791985 - libgpiod fails to build from dist-git in Fedora 32
Summary: libgpiod fails to build from dist-git in Fedora 32
Alias: None
Product: Fedora
Classification: Fedora
Component: libgpiod
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-01-16 19:37 UTC by Miro Hrončok
Modified: 2020-01-28 13:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-01-28 13:46:09 UTC
Type: Bug

Attachments (Terms of Use)

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:


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 -
+ '[' 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

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.

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