-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El Tue, 14 Jan 2014 14:18:38 +0000
Paul Howarth <paul(a)city-fan.org> escribió:
On 10/01/14 23:52, Dennis Gilmore wrote:
> Hi All,
>
> Se we have composes working automatically now, the job had been
> failing. I'm trying to get epel 7 to the point where the packaging
> tools are available on epel7. hopefully that will be by the end of
> today. In order to submit builds for epel7 you need to have
> fedpkg-1.15-1 installed, versions prior will fail due to not
> understanding the epel7 branch.
>
>
https://fedoraproject.org/wiki/EPEL/epel7 lists all the packages in
> RHEL 7 Beta.
>
>
> Please put branching request in
>
https://fedoraproject.org/wiki/EPEL/epel7/Requests if you think of a
> better way to file requests please speak up.
>
>
> We will do some checking that the package is not in RHEL before
> branching but please check the list if you are not sure.
I'm getting along nicely with most of my packages, but I'm having
trouble pushing a single fast-forward commit for one of my packages:
$ git status
# On branch epel7
# Your branch is ahead of 'origin/epel7' by 1 commit.
# (use "git push" to publish your local commits)
#
nothing to commit, working directory clean
$ fedpkg push
Total 0 (delta 0), reused 0 (delta 0)
remote: W refs/heads/epel7 perl-Compress-Raw-Lzma pghmcfc DENIED by
refs/heads/epel[0-9]
remote: error: hook declined to update refs/heads/epel7
To ssh://pghmcfc@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma
! [remote rejected] epel7 -> epel7 (hook declined)
error: failed to push some refs to
'ssh://pghmcfc@pkgs.fedoraproject.org/perl-Compress-Raw-Lzma'
Could not execute push: Command '['git', 'push']' returned
non-zero
exit status 1
Any ideas? The branch is done in git but I didn't get the email about
it being added to pkgdb, and a pkgdb query doesn't show the epel7
branch. Something gone wrong during branching?
Im guessing you put EL-6 as the acl source in your request, and the
package currently does not exist in EPEL so you needed to use devel as
the source to copy the acls from. I thought it was clear what you
needed to do, but apparently not so please help to make the wording
better so that everyone gets it. you will need to put in a new request
with the correct acl source
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS1UlCAAoJEH7ltONmPFDR0pUP/16yAjytDEVHZheDn2xadJk0
YypUwoKxlKYmlZATjTeGg6+JvooOsGoOlz6Rtpp6ZHp+KGKkdwnNXN2PBQmZs6wB
NV2UU8ScDIro/bw+nAB+SyfyDa4jr9Fpqqc3Gbh8t70JeFwF8yL5Z0JxRopYP4v0
NnwpKo8nq3l9TgRbZ3Jm5G/VdQuaWJcU7xtPfdvIzv7pUqoDNvs8KH5Lc148Hlbw
l0sdhR94bq3a0X9ld6j6/pXK1LpaaORLemkSzBk7NX6ebfDIYVSIFJl5RfxeanYe
8tmJ2QwYnaJO4yWtmqTM1FD3gNgPQ8p0Dvm/jNUr5GxlVuhAKw0mXPV0067m0rzG
qtWGKWpfnr3STyDL9ap7XW4bga7JT4fmB2ZSjhwcTWBloWBUsXZ71dAVP1pOFKEp
/my+Jt+BkOL2fIllkpNy3YxBsTS8orKFyi1utodtCN0397Cwr1vqbSZFZwyWkXnw
N10t908Eo7lJSGDMCKGwiJsfVIdgiUeIQFoCCly1JIO/O0JK9/TvvBsJ4Fs60DEg
J/osathMxQZVXeNhx9O0E/YA1YLs8kTKus2Smo5aBx9AXXS3JYsc8o3/ZIH8LgGQ
7FwBgjbWkEwU4TWDmgADcm2g8z8KfxsR9QF6SVb7zTjdv5g27eA7ALGJtmMLcoFl
8iKbgMudbParrnHIXPGU
=Y1gL
-----END PGP SIGNATURE-----