Hi, I am one of Fedora nextcloud-client maintainers.
Concerning client theming releases, like
https://github.com/nextcloud/client_theming/releases/tag/v2.3.3
under Source code (tar.gz) button you get URL
https://github.com/nextcloud/client_theming/archive/v2.3.3.tar.gz
instead when you download the file, you get a file named client_theming-2.3.3.tar.gz
Could you please avoid inconsistency between URL and filename?
During RPM building on Fedora / RHEL / CentOS / Scientific Linux, a source code is given as Source tag and it contains a full URL, so if I set
Source0: https://github.com/nextcloud/client_theming/archive/v2.3.3.tar.gz
the build system expects a file named v2.3.3.tar.gz not client_theming-2.3.3.tar.gz and the build fails.
Hi, I am one of Fedora nextcloud-client maintainers. Concerning client theming releases, like https://github.com/nextcloud/client_theming/releases/tag/v2.3.3 under
Source code (tar.gz)
button you get URL https://github.com/nextcloud/client_theming/archive/v2.3.3.tar.gz instead when you download the file, you get a file namedclient_theming-2.3.3.tar.gz
Could you please avoid inconsistency between URL and filename? During RPM building on Fedora / RHEL / CentOS / Scientific Linux, a source code is given asSource
tag and it contains a full URL, so if I setSource0: https://github.com/nextcloud/client_theming/archive/v2.3.3.tar.gz
the build system expects a file namedv2.3.3.tar.gz
notclient_theming-2.3.3.tar.gz
and the build fails.https://src.fedoraproject.org/rpms/nextcloud-client/blob/master/f/nextcloud-client.spec