I have tagged successfully all the other releases for rubygem-asciidoctor. However, there's a possibility that my certificates got messed up somehow. Oddly enough, it allows me to request a build just fine...it's just failing on the server side...which makes me think this isn't about certificates.

-Dan

On Thu, Jun 27, 2013 at 8:49 PM, Dan Allen dan.j.allen@gmail.com wrote:

Btw, the message is:

ActionNotAllowed: tag requires admin permission

-Dan

On Thu, Jun 27, 2013 at 8:48 PM, Dan Allen dan.j.allen@gmail.com wrote:

...

I'm the maintainer of the rubygem-asciidoctor package. Thanks to work by Jimmi Dyson, the package now builds successfully for epel6.

https://koji.fedoraproject.org/koji/taskinfo?taskID=5552396

However, the el6 build is fails when it tries to tag the release. Do I need some extra permission in order to tag for el6, or is something else wrong?

Thanks,

-Dan

-- Dan Allen | http://google.com/profiles/dan.j.allen

-- Dan Allen | http://google.com/profiles/dan.j.allen

Yeah! That worked! I bumped the build number, built on F19 and used el6-candidate as target.

fedpkg --user <me> build --target el6-candidate

https://koji.fedoraproject.org/koji/taskinfo?taskID=5555277

It would be really nice if *somewhere* in the instructions for packaging it listed which target name to use for epel6. I searched and searched and in the end, that's why I ended up just guessing.

If I run "koji list-targets", I get:

Name Buildroot Destination --------------------------------------------------------------------------------------------- dist-5E-epel dist-5E-epel-build dist-5E-epel dist-5E-epel-testing-candidate dist-5E-epel-build dist-5E-epel-testing-candidate dist-6E-epel dist-6E-epel-build dist-6E-epel dist-6E-epel-testing-candidate dist-6E-epel-build dist-6E-epel-testing-candidate el5-candidate dist-5E-epel-build dist-5E-epel-testing-candidate el6-candidate dist-6E-epel-build dist-6E-epel-testing-candidate el6-docs el6-docs el6-docs f17 f17-build f17-updates-candidate f17-candidate f17-build f17-updates-candidate f18 f18-build f18-updates-candidate f18-candidate f18-build f18-updates-candidate f19 f19-build f19-updates-candidate f19-candidate f19-build f19-updates-candidate f20 f20-build f20 f20-candidate f20-build f20 rawhide f20-build f20 rawhide-repo-holder rawhide rawhide

That's not helpful.

-Dan

On Fri, Jun 28, 2013 at 1:47 AM, Vít Ondruch vondruch@redhat.com wrote:

Dne 28.6.2013 04:48, Dan Allen napsal(a):

I'm the maintainer of the rubygem-asciidoctor package. Thanks to work by

...

Jimmi Dyson, the package now builds successfully for epel6.

https://koji.fedoraproject.**org/koji/taskinfo?taskID=**5552396https://koji.fedoraproject.org/koji/taskinfo?taskID=5552396

However, the el6 build is fails when it tries to tag the release. Do I need some extra permission in order to tag for el6, or is something else wrong?

Thanks,

-Dan

Hm, looking into this issue and it looks like you might use old fedpkg or koji tools? If I compare your build [1] with some other recent build [2], your build says "Build Target: dist-6E-epel" while the other build "Build Target: el6-candidate". The latter looks more realistic to me.

Vít

[1] https://koji.fedoraproject.**org/koji/taskinfo?taskID=**5552368https://koji.fedoraproject.org/koji/taskinfo?taskID=5552368 [2] https://koji.fedoraproject.**org/koji/taskinfo?taskID=**5530454https://koji.fedoraproject.org/koji/taskinfo?taskID=5530454 ______________________________**_________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.**org ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/ruby-sighttps://admin.fedoraproject.org/mailman/listinfo/ruby-sig

Thanks for the pointer Vit!

fedpkg is much more useful than I originally realized. Quite a time saver!

-Dan

On Mon, Jul 1, 2013 at 12:46 AM, Vít Ondruch vondruch@redhat.com wrote:

Dne 28.6.2013 22:43, Dan Allen napsal(a):

Yeah! That worked! I bumped the build number, built on F19 and used

...

el6-candidate as target.

fedpkg --user <me> build --target el6-candidate

Hm, that is weird command you use. You need just "fedpkg build" without any additional parameter and of course you need to have checked out the correct branch.

Vít

______________________________**_________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.**org ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/ruby-sighttps://admin.fedoraproject.org/mailman/listinfo/ruby-sig