On Thu, Oct 27, 2016 at 2:11 PM arnaud gaboury <[email protected]> wrote:
> On Thu, Oct 27, 2016 at 12:47 PM arnaud gaboury <[email protected]> > wrote: > > Here is part of my spec file: > > ----------------------------------------------- > Name: mattermost > Version: 3.4.0 > Release: 1%{?dist} > Summary: Mattermost is an open source, self-hosted Slack-alternative > URL: http://www.mattermost.org > Source0: > https://releases.mattermost.com/%{version}/mattermost-%{version}-linux-amd64.tar.gz > License: MIT > Group: System Environment/Daemons > ........ > %prep > %autosetup > > --------------------------- > Now testing: > $ fedpkg --dist f24 prep > > leaves me with this error: mattermost-3.4.0: No such file or directory > $ ls returns in fact mattermost. I guess the difference is due to untar. > > How can I tell in my spec file that the source directory will be named > %{name} and not %{name}.%{version} ? > > > EDIT : In fact, the unpacked directory is called platform-release-3.4 when > the macro is looking for mattermost-3.4. I used this setup option: > > %autosetup -n platform-release-3.4 > > but it doesn't solve my issue. I still get cd: mattermost-3.4: No such > file or directory > > What is wrong ? > NEW EDIT: the autosetup command as described above works indeed. The culprit was a line before poorly commented by #, which in fact is not the correct way to comment in spec file. > > > Then, I though the %autosetup macro would have download the source, which > is not the case. I need to run $ spectool -g *spec to get the source. Is it > the normal behavior? > > Thank you for help. > >
_______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected]
