Alternatively, rpkg could ship the hook in a more central location (which has
exec). This would allow you to set `core.hooksPath` for your fedpkg repos,
maybe even automatically by using something like `git config
includeif.gitdir:~/fedora/.path ~/.config/git/config.fedora` and putting the
hook
On 27/03/2023 14:41, Fabio Valentini wrote:
It's doing new pre-push checks that were introduced in rpkg 1.66:
Thanks for the information.
As far as I know, there's no way to disable the checks for now, other
than to do "rm .git/hooks/pre-push".
Will do, because my $HOME is mounted with 'noe
On Mon, Mar 27, 2023 at 2:14 PM Vitaly Zaitsev via devel
wrote:
>
> Hello.
>
> All of the newly cloned Fedora package repositories have a strange Git
> pre-push hook.
>
> Code listing:
>
> ```
> #!/bin/bash
>
> _remote="$1"
> _url="$2"
>
> exit_code=0
> while read -r _local_ref local_sha _remote_r
Hello.
All of the newly cloned Fedora package repositories have a strange Git
pre-push hook.
Code listing:
```
#!/bin/bash
_remote="$1"
_url="$2"
exit_code=0
while read -r _local_ref local_sha _remote_ref _remote_sha
do
command -v fedpkg >/dev/null 2>&1 || { echo >&2 "Warning: 'fedpkg'
