#7910 simple-koji-ci is broken on (at least) rust-* packages
Closed: Upstream 4 years ago by pingou. Opened 4 years ago by ignatenkobrain.

For example, https://src.fedoraproject.org/rpms/rust-prometheus/pull-request/2.

My guess is that since simple-koji-ci is generating SRPM locally, it is just broken with rich dependencies or something else. Instead it should get that SCM url and use koji to build SRPM.


Instead it should get that SCM url and use koji to build SRPM.

We cannot build from forks, so we can't use this approach.

If you think of a different way, feel free to open a ticket upstream but I don't think this is infra related :)

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

4 years ago

If you think of a different way, feel free to open a ticket upstream but I don't think this is infra related :)

well, the thing is I don't know the real reason why it fails. I just guessed.

So please take a look (since I don't have access to the server where s-k-ci is running) and open upstream ticket.

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

4 years ago

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

4 years ago

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

Was there an upstream issue opened?

Was there an upstream issue opened?

I didn't and I have not seen a notification of someone doing it :)

I didn't and I have not seen a notification of someone doing it :)

Then why did you mark this ticket as closed?

Then why did you mark this ticket as closed?

Because as I've said in my first comment, this is not an infra issue. From infrastructure's point of view, the hardware this service relies on is running and performing as it should. If the service isn't behaving as it should, then it's the service's problem, not infra.

Then why did you mark this ticket as closed?

Because as I've said in my first comment, this is not an infra issue. From infrastructure's point of view, the hardware this service relies on is running and performing as it should. If the service isn't behaving as it should, then it's the service's problem, not infra.

That's fair, but could we help the user know where to file the upstream ticket or who to talk to? If the user opening the ticket were me I wouldn't know where to go next.

Login to comment on this ticket.

Metadata