Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJapheth Cleaver
2019-08-22 12:28:34 UTC
Cloned for RHEL8
+++ This bug was initially created as a clone of Bug #1658379 +++
+++ This bug was initially created as a clone of Bug #1472006 +++
Description of problem:
We have an rpmbuild server which NFS mounts a directory with build artifacts from a separate server farm. We had hoped to use spectool to automatically transfer Source#: files in .SPECS to our SOURCEDIR, which works fine for remote URLs but doesn't do anything useful with absolute paths.
Version-Release number of selected component (if applicable):
rpmdevtools-8.10-7.el8.noarch
How reproducible:
Always
Steps to Reproduce:
1. Specify a SOURCE# using a file:// URL or absolute path in package.spec
2. spectool -v -g -S -R package.spec
3.
Actual results:
Couldn't fetch file:///mnt/foobar/build/package/1.0.0/package-1.0.0.tar.gz: missing URL
Expected results:
spectool copies the specified file into rpm's %{_sourcedir}
--- Additional comment from Ville Skyttä on 2017-07-18 08:47:25 UTC ---
I opted to remove the internal check for specific protocols altogether, everything that looks like it has a protocol is passed to curl now:
https://pagure.io/rpmdevtools/c/ecbe7300237b74abfbaa7c429b0e0b78468a89c6
--- Additional comment from Japheth Cleaver on 2018-08-27 23:31:41 UTC ---
Thank you. Is there any chance this patch could be backported into RHEL? file URLs are a useful feature for those wanting to automate this.
--- Additional comment from Neal Gompa on 2018-12-11 21:21:14 UTC ---
I can't do anything about RHEL rpmdevtools, a separate bug will need to be filed against the RHEL package.
--- Additional comment from Japheth Cleaver on 2019-03-18 20:27:10 UTC ---
Is there any chance this can be cherry-picked from upstream? Likewise for RHEL8?
https://pagure.io/rpmdevtools/c/ecbe7300237b74abfbaa7c429b0e0b78468a89c6?branch=master
*** Bug 1658379 has been marked as a duplicate of this bug. ***
Comment 6RHEL Program Management
2021-02-24 07:30:29 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.