#4224: break build inheritance between F14 and F15 and update deltarpm files

Fedora Release Engineering rel-eng at fedoraproject.org
Tue Oct 26 19:10:59 UTC 2010


#4224: break build inheritance between F14 and F15 and update deltarpm files
---------------------+------------------------------------------------------
  Reporter:  toshio  |       Owner:  rel-eng at lists.fedoraproject.org
      Type:  task    |      Status:  new                            
 Milestone:          |   Component:  koji                           
Resolution:          |    Keywords:                                 
---------------------+------------------------------------------------------
Comment (by toshio):

 The deltas themselves don't hold any information that's problematic but
 the existence of a delta is the trigger for reconstructing an rpm and the
 reconstructed rpm can lead to the hash mismatch in certain circumstances:

  1. when the client has the old xz/rpm/deltarpm but the new package has
 been built by rpm with the new xz the client will construct a package with
 a different payload than the new package leading to a hash mismatch.  This
 is usually a one-time occurrence in the yum update that pulls in the new
 xz/rpm/deltarpm combination.  I can't think of a way to address this but
 it doesn't affect people using media to upgrade from F14 to F15 as they
 aren't using deltarpms in order to get the new rpm.  (Would this affect
 preupgrade or other yum upgrade paths?  I don't think we have deltarpms
 between releases but I'm not sure.)
  2. when the client has the new xz/rpm/deltarpm but the package has been
 built by rpm with the old xz the same hash mismatch will occur.  AFAICT,
 this occurs in two cases:
     1. if the client updates xz/rpm/deltarpm specifically and then updates
 a package where the update was built by the old rpm/xz combination.  This
 is taken care of by removing the deltarpms for F15 generated before the
 new rpm/xz combo is used in the buildroots.  As there's no longer a
 deltarpm present, there's nothing to trigger recreating the rpm on the
 client's machine.
     2. if the update is built using the old xz/rpm combination on F14 and
 build inheritance pulls that build into F15.  This case is taken care of
 by breaking build inheritance with F14 so that an update with an old
 payload is never pushed to F15.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4224#comment:6>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project


More information about the rel-eng mailing list