[AutoQA] #230: upgradepath: current implementation is broken when pushing older packages - autoqa-devel - Fedora mailing-lists

29 Sep 2010


      #230: upgradepath: current implementation is broken when pushing older packages
--------------------+-------------------------------------------------------
 Reporter:  kparal  |       Owner:                                     
     Type:  defect  |      Status:  new                                
 Priority:  major   |   Milestone:  Package Update Acceptance Test Plan
Component:  tests   |     Version:  1.0                                
 Keywords:          |  
--------------------+-------------------------------------------------------
 Currently upgradepath takes into account only the given NVR and compares
 it with other repositories. This approach works, except for one use case -
 when you want to push an older package version into the repository.
Technically you can have multiple package versions in a single repository.
 Yum prefers the most recent one, but you can have more of them there. It's
 hard to imagine a use case where you want to push an older version, but
 let's say for example an older kernel that is needed for hardware
 compatibility reasons. In this case, our current upgradepath fails - it
 supposes the given NVR is always the latest.
We need to modify upgradepath in such a way, that is supposes that given
 NVR has been pushed into the repository and then traverses all
 repositories from bottom up and checks for upgradepath constraint
 everywhere - including the repo you pushed into, including all package
 versions which might be there.
-- 
Ticket URL: https://fedorahosted.org/autoqa/ticket/230
AutoQA http://autoqa.fedorahosted.org
Automated QA project