https://bugzilla.redhat.com/show_bug.cgi?id=1877006



--- Comment #39 from Jordi Sanfeliu <[email protected]> ---
> FIX: Source0 looks like a VCS snapshot. Put a URL you cloned it from into a 
> comment above Source0 tag 
> <https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_using_revision_control>.
>  Or use a URL of the snapshot if the upstream VCS hosting system supports it.

The problem here is that if I include an URL to download the source code
directly from upstream VCS (GitHub in this case), the directory inside the .zip
file is different than what the Version tag says:

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.IQOr91
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd /root/rpmbuild/BUILD
+ rm -rf 'smf-spf-2.5.1^20220423g061e937'
+ /usr/lib/rpm/rpmuncompress -x
/root/rpmbuild/SOURCES/061e9371f761f70afd40af349f4037fe0460725c.zip
replace
smf-spf-061e9371f761f70afd40af349f4037fe0460725c/.devcontainer/Dockerfile?
[y]es, [n]o, [A]ll, [N]one, [r]ename: A
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd 'smf-spf-2.5.1^20220423g061e937'
/var/tmp/rpm-tmp.IQOr91: line 40: cd: smf-spf-2.5.1^20220423g061e937: No such
file or directory

How can I provide an upstream URL and tell to the specfile the exact name of
the directory where the source code is?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=1877006

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%201877006%23c39
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to