fedora-infrastructure

#8957 create a jbangdev group
Closed: Fixed by pingou. Opened by maxandersen.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

create a group called jbangdev to have https://copr.fedorainfracloud.org/coprs/maxandersen/jbang/ forked to https://copr.fedorainfracloud.org/coprs/jbangdev/jbang/

When do you need this to be done by? (YYYY/MM/DD)

2020-05-29 if at all possible

Metadata Update from @pingou:
- Issue assigned to pingou

Done, the groups has been created: https://admin.fedoraproject.org/accounts/group/view/jbangdev

Let us know if you need anything more from us :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

sorry missed this ! i can see the group but when I go and fork maxandersen/jbang I don't see jbangdev listed as possible owner. Am I doing it the right way or am I missing something here ?

Metadata Update from @maxandersen:
- Issue status updated to: Open (was: Closed)

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, medium-trouble

COPR groups work similar to pagure ones, please log out and log in again. Then please update the ticket

Metadata Update from @smooge:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

Apparently groups are sync upon login, did you try login out and back in?

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Waiting on Reporter)

Metadata Update from @pingou:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

ping?

sorry - thought I commented already.

I had to go activate the group first then I could see the group.

Now what is weird though is that both https://copr.fedorainfracloud.org/coprs/g/jbangdev/jbang/ and https://copr.fedorainfracloud.org/coprs/g/maxandersen/jbang/ no longer seem to react on github webhooks ...

it been working fine for months.

Any idea if having two webhooks triggered from same git repo somehow causes issues ?

I am unfortunately not able to help you with this. The Fedora Infrastructure team does not maintain copr (and I don't use it enough to know how to help you here).

I recommend you reach out to them at https://pagure.io/copr/copr/ on or #fedora-buildsys on IRC (freenode).

I'm going to close this ticket as fixed though as the original request seems to be (fixed) :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

ack, thank you @pingou

Metadata

low-gain medium-trouble

None
None
High
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.