fedora-infrastructure

#7771 PSA: maybe don't upgrade pungi in prod either
Closed: Fixed by bowlofeggs. Opened by bowlofeggs.

Closed: Fixed
Reopen Issue

Today I hit an issue in staging with the latest pungi in F29:

https://pagure.io/pungi/issue/1182

I worked around it for now by downgrading pungi back to the same version that production has : pungi-4.1.33-3.fc29.noarch

I recommend avoiding updating pungi in production until we know what the issue is. Though I guess it's not an emergency if we accidentally do, since we can just downgrade again.

This should be fixed now in pungi-4.1.36-3.fc29.

pungi-4.1.36-3.fc29.noarch is now installed on staging, and I am about to start a compose. Wish me luck!

I just ran a compose in stg with that build and it worked.

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

bodhi

None
None
Normal
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.