Failed RPM build on COPR. #1358

Closed
opened 2026-02-06 20:50:43 +03:00 by OVERLORD · 8 comments
Owner

Originally created by @brianjmurrell on GitHub (Mar 9, 2020).

Describe the bug
COPR RPM build failure

System (please complete the following information):

  • OS: Fedora, EL7

From the build.log:

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.fNa7Lu
+ umask 022
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf jellyfin-10.5.0
+ rm -rf jellyfin-10.5.0
+ /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-web-10.5.0.tar.gz
+ /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-web-10.5.0.tar.gz
+ /usr/bin/tar -xof -
+ /usr/bin/tar -xof -
+ STATUS=0
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ '[' 0 -ne 0 ']'
+ /usr/bin/tar -xof -
+ /usr/bin/tar -xof -
+ /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-10.5.0.tar.gz
+ /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-10.5.0.tar.gz
+ STATUS=0
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ '[' 0 -ne 0 ']'
+ cd jellyfin-10.5.0
+ cd jellyfin-10.5.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
++ mktemp -d
++ mktemp -d
+ web_build_dir=/tmp/tmp.bUTLhKfhUw
+ web_build_dir=/tmp/tmp.bUTLhKfhUw
~/build/BUILD/jellyfin-web-10.5.0 ~/build/BUILD/jellyfin-10.5.0
~/build/BUILD/jellyfin-web-10.5.0 ~/build/BUILD/jellyfin-10.5.0
+ web_target=/builddir/build/BUILD/jellyfin-10.5.0/MediaBrowser.WebDashboard/jellyfin-web
+ web_target=/builddir/build/BUILD/jellyfin-10.5.0/MediaBrowser.WebDashboard/jellyfin-web
+ pushd ../jellyfin-web-10.5.0
+ pushd ../jellyfin-web-10.5.0
+ nodejs-yarn install
+ nodejs-yarn install
yarn install v1.21.1
yarn install v1.21.1
[1/4] Resolving packages...
[1/4] Resolving packages...
[2/4] Fetching packages...
[2/4] Fetching packages...
error Couldn't find the binary git
error Couldn't find the binary git

Has some new dependency on git been introduced into whatever yarn install does? Maybe a new/first dependency using a git repo?

If so, a BuildRequires: git likely needs adding to the specfile.

mock can be used (requires a Linux system/docker container to run on, which can be done with GitHub Actions -- I'm not familiar with Azure Pipelines as a CI engine) to create a CI test for PRs to prevent this sort of thing from happening in the future. mock validates that an RPM's BuildRequires: is complete and that no new build dependencies have been introduced.

Originally created by @brianjmurrell on GitHub (Mar 9, 2020). **Describe the bug** COPR RPM build failure **System (please complete the following information):** - OS: Fedora, EL7 From the [build.log](https://copr-be.cloud.fedoraproject.org/results/brianjmurrell/jellyfin/fedora-rawhide-x86_64/01298335-jellyfin/build.log.gz): ``` Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.fNa7Lu + umask 022 + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf jellyfin-10.5.0 + rm -rf jellyfin-10.5.0 + /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-web-10.5.0.tar.gz + /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-web-10.5.0.tar.gz + /usr/bin/tar -xof - + /usr/bin/tar -xof - + STATUS=0 + STATUS=0 + '[' 0 -ne 0 ']' + '[' 0 -ne 0 ']' + /usr/bin/tar -xof - + /usr/bin/tar -xof - + /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-10.5.0.tar.gz + /usr/bin/gzip -dc /builddir/build/SOURCES/jellyfin-10.5.0.tar.gz + STATUS=0 + STATUS=0 + '[' 0 -ne 0 ']' + '[' 0 -ne 0 ']' + cd jellyfin-10.5.0 + cd jellyfin-10.5.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . ++ mktemp -d ++ mktemp -d + web_build_dir=/tmp/tmp.bUTLhKfhUw + web_build_dir=/tmp/tmp.bUTLhKfhUw ~/build/BUILD/jellyfin-web-10.5.0 ~/build/BUILD/jellyfin-10.5.0 ~/build/BUILD/jellyfin-web-10.5.0 ~/build/BUILD/jellyfin-10.5.0 + web_target=/builddir/build/BUILD/jellyfin-10.5.0/MediaBrowser.WebDashboard/jellyfin-web + web_target=/builddir/build/BUILD/jellyfin-10.5.0/MediaBrowser.WebDashboard/jellyfin-web + pushd ../jellyfin-web-10.5.0 + pushd ../jellyfin-web-10.5.0 + nodejs-yarn install + nodejs-yarn install yarn install v1.21.1 yarn install v1.21.1 [1/4] Resolving packages... [1/4] Resolving packages... [2/4] Fetching packages... [2/4] Fetching packages... error Couldn't find the binary git error Couldn't find the binary git ``` Has some new dependency on `git` been introduced into whatever `yarn install` does? Maybe a new/first dependency using a git repo? If so, a `BuildRequires: git` likely needs adding to the specfile. [`mock`](https://github.com/rpm-software-management/mock) can be used (requires a Linux system/docker container to run on, which can be done with [GitHub Actions](https://github.com/features/actions) -- I'm not familiar with Azure Pipelines as a CI engine) to create a CI test for PRs to prevent this sort of thing from happening in the future. `mock` validates that an RPM's `BuildRequires:` is complete and that no new build dependencies have been introduced.
OVERLORD added the bugstale labels 2026-02-06 20:50:43 +03:00
Author
Owner

@brianjmurrell commented on GitHub (Mar 9, 2020):

Or you can of course just use COPR to build-test each PR as an additional CI stage. COPR can report status back to GitHub.

@brianjmurrell commented on GitHub (Mar 9, 2020): Or you can of course just use [COPR](https://copr.fedorainfracloud.org/) to build-test each PR as an additional CI stage. COPR can report status back to GitHub.
Author
Owner

@dkanada commented on GitHub (Mar 9, 2020):

@brianjmurrell if you want to make a quick addition to the CI we would definitely merge that. We were thinking of moving the entire build process to CI anyways, so this would get COPR much closer.

@dkanada commented on GitHub (Mar 9, 2020): @brianjmurrell if you want to make a quick addition to the CI we would definitely merge that. We were thinking of moving the entire build process to CI anyways, so this would get COPR much closer.
Author
Owner

@brianjmurrell commented on GitHub (Mar 10, 2020):

Have GitHub Actions been enabled on this repo?

@brianjmurrell commented on GitHub (Mar 10, 2020): Have [GitHub Actions](https://github.com/features/actions) been enabled on this repo?
Author
Owner

@dkanada commented on GitHub (Mar 10, 2020):

We use Azure at the moment.

@dkanada commented on GitHub (Mar 10, 2020): We use Azure at the moment.
Author
Owner

@brianjmurrell commented on GitHub (Mar 10, 2020):

Indeed, I am aware of this. However is there any issues with enabling GitHub Actions also?

In all honesty I am just not interested in learning how to build Azure pipelines.

GitHub actions report in the Checks tab just like Azure pipelines would so it would just look like yet another Check.

@brianjmurrell commented on GitHub (Mar 10, 2020): Indeed, I am aware of this. However is there any issues with enabling [GitHub Actions](https://github.com/features/actions) also? In all honesty I am just not interested in learning how to build Azure pipelines. GitHub actions report in the Checks tab just like Azure pipelines would so it would just look like yet another Check.
Author
Owner

@joshuaboniface commented on GitHub (Mar 16, 2020):

I'd indeed love for us to use Mock to get this building automatically - I've got no issues using GitHub Actions for this if it's fully supported.

For now I'll manually add Git to the deps for 10.5.1.

@joshuaboniface commented on GitHub (Mar 16, 2020): I'd indeed love for us to use Mock to get this building automatically - I've got no issues using GitHub Actions for this if it's fully supported. For now I'll manually add Git to the deps for 10.5.1.
Author
Owner

@brianjmurrell commented on GitHub (Mar 16, 2020):

I've got no issues using GitHub Actions

Have they been enabled for this repo? Although now that it's out of beta, maybe this is something that doesn't need to specifically be done and it's just enabled for everyone who wants to use it. If I can find some time, I will see if this is the case.

@brianjmurrell commented on GitHub (Mar 16, 2020): > I've got no issues using GitHub Actions Have they been enabled for this repo? Although now that it's out of beta, maybe this is something that doesn't need to specifically be done and it's just enabled for everyone who wants to use it. If I can find some time, I will see if this is the case.
Author
Owner

@stale[bot] commented on GitHub (Jul 14, 2020):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@stale[bot] commented on GitHub (Jul 14, 2020): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#1358