Read this thread:
The documentation is poorly worded. The recommendation which I have been following since has been to use fedpkg import srpm.
Once I get the solution to this rpmlintrc issue, I’m going to revise the documentation myself and run it up through the packaging committee for approval.
“new-sources” should not be mentioned in basic documentation. These
should be added via means of “fedpkg import package.srpm”.
The workflow for new package is then:
$ fedpkg import mypackage.srpm
$ git commit -m "initial import"
and for updated package:
$ git add -u
$ fedpkg clog
$ git commit -F clog
$ fedpkg import updated.srpm
$ git commit --am
This way, the question if the file is stored in lookaside cache or git
is done by fedpkg. Also please note that the “import” command removes
patches which are not used any longer (not sure if it adds new patches …).
fedpkg import currently "extracts sources, patches, and the spec file from an srpm
and update the current module accordingly. It will import to the current branch by default.
Since more people are beginning to use .rpmlintrc it should handle that also. As I mentioned above, I can probably add it as an additional source in the spec file, put it in the fedpkg directory, run the build which should pull it into the srpm. Then I suppose fedpkg will treat it as an additional source file and store it in the lookaside. So, it wouldn’t be included in the source tarball, nor would it handled by git add - and it would be pulled into subsequent builds via fedpkg sources.