#12238 rust-interprocess1 not properly tagged, blocking updates
Closed: Fixed 5 months ago by jnsamyak. Opened 5 months ago by salimma.

  • Describe the issue
    These updates are stuck in pending because they contain rust-interprocess1, a new package that somehow is not added to the right tags

F39 https://bodhi.fedoraproject.org/updates/FEDORA-2024-bbb9ec2e70
F40 https://bodhi.fedoraproject.org/updates/FEDORA-2024-ea85e5d364

For some reason the F41 update is fine though

https://bodhi.fedoraproject.org/updates/FEDORA-2024-e6cac4423c

  • When do you need this? (YYYY/MM/DD)
    2024/08/05

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    This blocks updating any package that needs interprocess 2, as there are still others that need interprocess 1


So looking at it, this feels like Bodhi untagged it but not:

f40-updates-testing-pending -> f40-updates-candidate (need to look at what happened there)

```
Sat Aug 3 06:41:22 2024 rust-interprocess1-1.2.1-1.fc40 untagged from f40-updates-testing-pending by bodhi
Sat Aug 3 07:20:51 2024 rust-interprocess1-1.2.1-1.fc39 untagged from f39-updates-testing-pending by bodhi
````

@salimma; Did you push this in a side tag? I can tag it in again, and see how it goes with the compose tonight.

@jnsamyak I built this in side tags, yes - one for F40 and one for f39

@kevin since you have handled like this before, is it okay to directly merge the side tag to the min tag?

Looks like interprocess1 got ejected again

I think rust-interprocess1-1.2.1-1.fc40 needs to be tagged with f40-updates-candidate

Testing updates for both 39 and 40 just got tripped up by this again. Let's hope bodhi is smart enough today to work around the problem quickly. Last time, it took a day.

Hey, I added the build rust-interprocess1-1.2.1-1.fc40 manually for f40 in the relevant tag, https://koji.fedoraproject.org/koji/taskinfo?taskID=121665713; Can you confirm if this works? If yes, then we can do the same process for f39;

However, I need to investigate why this happened!

@jnsamyak F40 got to testing, but F39 has not, can you tag F39 too? Thanks

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

5 months ago

Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, medium-trouble, ops

5 months ago

Thanks, let's see if it goes in tonight, the last failure message was from before your last comment

F39 went to testing as well, I think this should be good now right?

Closing this now, but in case of any problems please let me know.

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

5 months ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog