Upstream repo: https://github.com/awslabs/git-secrets

Can you not do `%make_build PREFIX=%{_prefix}` (not %{_usr}!)?

Also, please use raw links so fedora-review works.

(In reply to Elliott Sales de Andrade from comment #2)
> Can you not do `%make_build PREFIX=%{_prefix}` (not %{_usr}!)?
> 
> Also, please use raw links so fedora-review works.

Please define what you mean with raw links to make fedora-review work, then I'll have a look to fix it. Do you perhaps mean that I should've posted the fedora-review data also in GitHub and provide that as a link?
Your suggestion to override the prefix doesn't work. I'm also not entirely sure if it can be overridden in the conventional way, since there is no ./configure needed for this install. Just `make install`, which then uses the prefixes in the Makefile to install the files in the specified paths.

The links you've used go to a GitHub webpage; they need to point directly to the raw file. Use the Download button on GitHub to get it.

In the Makefile, PREFIX is set using ?=, which means it should only be set if undefined. So setting it on the command-line would override (or rather, skip setting) the value from the file. But you'd need to override PREFIX for both %build and %install to work.

> Use the Download button on GitHub to get it.

Download or Raw button, depending on where you're looking at the file.

(In reply to Elliott Sales de Andrade from comment #4)
> The links you've used go to a GitHub webpage; they need to point directly to
> the raw file. Use the Download button on GitHub to get it.
> 
> In the Makefile, PREFIX is set using ?=, which means it should only be set
> if undefined. So setting it on the command-line would override (or rather,
> skip setting) the value from the file. But you'd need to override PREFIX for
> both %build and %install to work.

Perfect! Thanks for your help, it indeed works when the prefix is overridden in both stages.

Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=38853301
Spec URL: https://raw.githubusercontent.com/AquaL1te/git-secrets/master/git-secrets.spec
SRPM URL: https://github.com/AquaL1te/git-secrets/raw/master/git-secrets-1.3.0-1.fc30.src.rpm

Source0 can be written https://github.com/awslabs/%{name}/archive/%{version}/%{name}-%{version}.tar.gz

Missing version in %changelog.

Can you not run tests in %check? There seems to be a test directory.

Package Review
==============

Legend:
[x] = Pass, [!] = Fail, [-] = Not applicable, [?] = Not evaluated
[ ] = Manual review needed



===== MUST items =====

Generic:
[x]: Package is licensed with an open-source compatible license and meets
     other legal requirements as defined in the legal section of Packaging
     Guidelines.
[x]: License field in the package spec file matches the actual license.
     Note: There is no build directory. Running licensecheck on vanilla
     upstream sources. No licenses found. Please check the source files for
     licenses manually.
[x]: Package contains no bundled libraries without FPC exception.
[!]: Changelog in prescribed format.
[x]: Sources contain only permissible code or content.
[-]: Package contains desktop file if it is a GUI application.
[x]: Development files must be in a -devel package
[x]: Package uses nothing in %doc for runtime.
[x]: Package consistently uses macros (instead of hard-coded directory
     names).
[x]: Package is named according to the Package Naming Guidelines.
[?]: Package does not generate any conflict.
[x]: Package obeys FHS, except libexecdir and /usr/target.
[-]: If the package is a rename of another package, proper Obsoletes and
     Provides are present.
[x]: Requires correct, justified where necessary.
[x]: Spec file is legible and written in American English.
[-]: Package contains systemd file(s) if in need.
[x]: Package is not known to require an ExcludeArch tag.
[x]: Large documentation must go in a -doc subpackage. Large could be size
     (~1MB) or number of files.
     Note: Documentation size is 10240 bytes in 1 files.
[x]: Package complies to the Packaging Guidelines
[x]: Package successfully compiles and builds into binary rpms on at least
     one supported primary architecture.
[x]: Package installs properly.
[x]: Rpmlint is run on all rpms the build produces.
     Note: There are rpmlint messages (see attachment).
[x]: If (and only if) the source package includes the text of the
     license(s) in its own file, then that file, containing the text of the
     license(s) for the package is included in %license.
[x]: Package requires other packages for directories it uses.
[x]: Package must own all directories that it creates.
[x]: Package does not own files or directories owned by other packages.
[x]: Package uses either %{buildroot} or $RPM_BUILD_ROOT
[x]: Package does not run rm -rf %{buildroot} (or $RPM_BUILD_ROOT) at the
     beginning of %install.
[x]: Macros in Summary, %description expandable at SRPM build time.
[x]: Dist tag is present.
[x]: Package does not contain duplicates in %files.
[x]: Permissions on files are set properly.
[x]: Package must not depend on deprecated() packages.
[x]: Package use %makeinstall only when make install DESTDIR=... doesn't
     work.
[x]: Package is named using only allowed ASCII characters.
[x]: Package does not use a name that already exists.
[x]: Package is not relocatable.
[x]: Sources used to build the package match the upstream source, as
     provided in the spec URL.
[x]: Spec file name must match the spec package %{name}, in the format
     %{name}.spec.
[x]: File names are valid UTF-8.
[x]: Packages must not store files under /srv, /opt or /usr/local

===== SHOULD items =====

Generic:
[-]: If the source package does not include license text(s) as a separate
     file from upstream, the packager SHOULD query upstream to include it.
[x]: Final provides and requires are sane (see attachments).
[?]: Package functions as described.
[x]: Latest version is packaged.
[x]: Package does not include license text files separate from upstream.
[-]: Sources are verified with gpgverify first in %prep if upstream
     publishes signatures.
     Note: gpgverify is not used.
[-]: Description and summary sections in the package spec file contains
     translations for supported Non-English languages, if available.
[x]: Package should compile and build into binary rpms on all supported
     architectures.
[!]: %check is present and all tests pass.
[x]: Packages should try to preserve timestamps of original installed
     files.
[x]: Reviewer should test that the package builds in mock.
[x]: Buildroot is not present
[x]: Package has no %clean section with rm -rf %{buildroot} (or
     $RPM_BUILD_ROOT)
[x]: No file requires outside of /etc, /bin, /sbin, /usr/bin, /usr/sbin.
[x]: Packager, Vendor, PreReq, Copyright tags should not be in spec file
[x]: Sources can be downloaded from URI in Source: tag
[x]: SourceX is a working URL.
[x]: Spec use %global instead of %define unless justified.

===== EXTRA items =====

Generic:
[x]: Rpmlint is run on all installed packages.
     Note: There are rpmlint messages (see attachment).
[x]: Spec file according to URL is the same as in SRPM.


Rpmlint
-------
Checking: git-secrets-1.3.0-1.fc32.noarch.rpm
          git-secrets-1.3.0-1.fc32.src.rpm
git-secrets.noarch: W: spelling-error Summary(en_US) repos -> ropes, reps, repose
git-secrets.noarch: W: no-version-in-last-changelog
git-secrets.src: W: spelling-error Summary(en_US) repos -> ropes, reps, repose
git-secrets.src: W: no-version-in-last-changelog
git-secrets.src: W: strange-permission git-secrets-1.3.0.tar.gz 640
git-secrets.src: W: strange-permission git-secrets.spec 640
2 packages and 0 specfiles checked; 0 errors, 6 warnings.




Rpmlint (installed packages)
----------------------------
git-secrets.noarch: W: spelling-error Summary(en_US) repos -> ropes, reps, repose
git-secrets.noarch: W: no-version-in-last-changelog
1 packages and 0 specfiles checked; 0 errors, 3 warnings.



Source checksums
----------------
https://github.com/awslabs/git-secrets/archive/1.3.0.tar.gz#/git-secrets-1.3.0.tar.gz :
  CHECKSUM(SHA256) this package     : f1d50c6c5c7564f460ff8d279081879914abe920415c2923934c1f1d1fac3606
  CHECKSUM(SHA256) upstream package : f1d50c6c5c7564f460ff8d279081879914abe920415c2923934c1f1d1fac3606


Requires
--------
git-secrets (rpmlib, GLIBC filtered):
    /usr/bin/bash



Provides
--------
git-secrets:
    git-secrets



Generated by fedora-review 0.7.3 (44b83c7) last change: 2019-09-18
Command line :/usr/bin/fedora-review -b 1768192 -m fedora-rawhide-x86_64
Buildroot used: fedora-rawhide-{{ target_arch }}
Active plugins: Shell-api, Generic
Disabled plugins: PHP, fonts, Haskell, Java, SugarActivity, C/C++, Ocaml, Perl, R, Python
Disabled flags: EPEL6, EPEL7, DISTTAG, BATCH, EXARCH

Thanks! I forgot about that option. I've included the %check and your other suggestions. The changes are included in git. The `make test` runs without errors.

New koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=39170765
New SRC RPM (F31): https://github.com/AquaL1te/git-secrets/blob/master/git-secrets-1.3.0-1.fc31.src.rpm

You shouldn't use internal macros like %__make; just run make directly.

Also, remember to link both spec and srpm.

If you need git at build time, do you not need it at runtime, too? Also, do you need full git, or can git-core work?

> You shouldn't use internal macros like %__make; just run make directly.
Is there a reason for this? If the macro exists, then it can be used, right? I haven't read anything about this in the maintainer guide. I figured, the macro exists, so that implies it may be used.

> Also, remember to link both spec and srpm.
The links are still the same, but are changed on GitHub. I'll include them now anyway.

> If you need git at build time, do you not need it at runtime, too? Also, do you need full git, or can git-core work?
Good one! git-core is indeed sufficient too and is indeed also needed for runtime.

I've updated the spec file and created new builds:
Spec URL: https://github.com/AquaL1te/git-secrets/blob/master/git-secrets.spec
SRPM URL: https://github.com/AquaL1te/git-secrets/blob/master/git-secrets-1.3.0-1.fc30.src.rpm
Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=40051909

I copy pasted the URLs from the top of the thread, which did not contain the raw links. Below are the raw links.

Spec URL: https://raw.githubusercontent.com/AquaL1te/git-secrets/master/git-secrets.spec
SRPM URL: https://github.com/AquaL1te/git-secrets/raw/master/git-secrets-1.3.0-1.fc30.src.rpm

fedora-review 404s downloading those links.

(In reply to Kees de Jong from comment #11)
> > You shouldn't use internal macros like %__make; just run make directly.
> Is there a reason for this? If the macro exists, then it can be used, right?
> I haven't read anything about this in the maintainer guide. I figured, the
> macro exists, so that implies it may be used.
> 

No, it's internal, and there's no need to use it. Just because it exists, doesn't mean it should be used.

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_macros

> Macro forms of system executables SHOULD NOT be used except when there is a need to allow the location of those executables to be configurable. For example, rm should be used in preference to %{__rm}, but %{__python3} is acceptable.

Seems like I need to read those docs again. Below are the correct links.


Spec URL: https://raw.githubusercontent.com/AquaL1te/git-secrets/master/git-secrets.spec
SRPM URL: https://github.com/AquaL1te/git-secrets/raw/master/git-secrets-1.3.0-1.fc31.src.rpm
Koji build: https://koji.fedoraproject.org/koji/taskinfo?taskID=40051909

LGTM now.

(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/git-secrets

FEDORA-2020-928c1fe149 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-928c1fe149

git-secrets-1.3.0-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-928c1fe149

git-secrets-1.3.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-64bad07edc

git-secrets-1.3.0-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

git-secrets-1.3.0-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.