On 06/04/2018 11:39 AM, David C. Rankin wrote:
On 06/04/2018 04:30 AM, Bennett Piater wrote:
This is a different error, is it not? Does your most recent commit contain the LICENSE file, or did you only add PKGBUILD and .SRCINFO?
Oh, it's there...
$ tar -tzf console-blanking-0.0.1-4.src.tar.gz tar: Ignoring unknown extended header keyword 'SCHILY.fflags' console-blanking/ tar: Ignoring unknown extended header keyword 'SCHILY.fflags' console-blanking/PKGBUILD tar: Ignoring unknown extended header keyword 'SCHILY.fflags' console-blanking/LICENSE ^^^^^^^^^^^^^^^^^^^^^^^^^^^ tar: Ignoring unknown extended header keyword 'SCHILY.fflags' console-blanking/.SRCINFO tar: Ignoring unknown extended header keyword 'SCHILY.fflags' console-blanking/console-blanking.service
Where does that tarball come from? What I am asking is if the commit contains the files. If you got that tarball from the aur, then it obviously doesn't contain what the rejected commit does since that is not online yet :) Or are you trying to push a commit containing the tarball? That's not going to work, the aur expects flat files. Also feel free to ping me on irc if you think that's more productive, just be aware that my timezone is CEST, GMT+2 :) That is the tarball generated by: $ makepkg --printsrcinfo > .SRCINFO $ makepkg -S --sign -f That results in the two untracked files: console-blanking-0.0.1-4.src.tar.gz console-blanking-0.0.1-4.src.tar.gz.sig The tarballs are the source package for the console-blanking package I am trying to push. The flat files are there as well. $ git ls-files .SRCINFO LICENSE PKGBUILD console-blanking.service and show the files that are currently being tracked in the repo. There must be some other strange issue that isn't readily apparent -- at least to me.