Ticket #4224 (closed task: fixed)
break build inheritance between F14 and F15 and update deltarpm files
|Reported by:||toshio||Owned by:||jkeating|
|Keywords:||Cc:||jnovy, jdieter, robatino|
After talking with jnovy and jdieter about the new xz and its effect on deltarpms we've come up with this plan:
- rpm moves to the new xz as soon as possible. This should just be a rebuild. It's needed so that the rpms being created from that point forward all use the same version of xz for compression rather than having incompatible client-side and server side tools. Doing this step soon cuts the number of packages built with the old xz and thus getting the hash warning for a second and third time.
- Break build inheritance from F14 to F15. This is where releng comes in. This could be done with a mass rebuild or just by making a setting change in koji.
- If a setting change is used rather than a mass rebuild, remove the current F15 deltarpms so only deltarpms that match with the xz people have on their systems will be available in the future.
These steps protect against the scenario where the new xz is installed clientside but the packages being installed via deltarpms were generated with the old xz (for instance, via build inheritance from f14). Rawhide users will still get a warning in the transaction where they update from the rpm/deltarpm using the old xz to the one using the new xz.
Assuming this looks okay to releng, jnovy could you update this ticket when the new rpm and deltarpm packages are built?
comment:10 Changed 4 years ago by jkeating
- Status changed from new to assigned
- Owner changed from rel-eng@… to jkeating
comment:11 Changed 4 years ago by jkeating
- Status changed from assigned to closed
- Resolution set to fixed