[Yum-devel] pain and suffering and allowdowngrade

[Skahan, Vince]

How would the system know what version to downgrade to ?   Consider the
case where you've done multiple updates of a particular package along
the way and you want to go to some intermediate step, or where multiple
old versions exist in the repo(s) you have enabled.

How would the system know where to get the rpm from (again) to do the
downgrade ?  I've seen cases where intermediate versions disappear from
some of the official repo mirrors in past Fedoras as time progressed.

How would you address the reverse-requires issue ?   Yum has a great
'resolve deps when installing package-XYZ' feature where it figures out
what other things you should have asked for as corequisites.  Would you
get into a position where you'd need to calculate which
previously-upgraded versions of other rpms would need to be backed down
too (example - downgrade net-snmp which should downgrade its libs too,
etc.)

Seems like a toughie....

------ vince.skahan at boeing.com ------



-----Original Message-----
From: seth vidal [mailto:skvidal at fedoraproject.org] 
Sent: Friday, October 24, 2008 2:25 PM
To: yum-devel
Subject: [Yum-devel] pain and suffering and allowdowngrade

Been thinking about allowdowngrade.

How does that work for things like this:

yum --allowdowngrade update \*

Does that revert you back to GA of your distro?

If we bit the bullet and put in a downgrade command or implemented it in
plugin what is the behavior for it?

I'm not looking for bikeshedding, pony-desiring requests. I'm looking
for real thoughts on how downgrades should work. Maybe downgrade bans
wildcards?

Maybe downgrade has a transaction size limit?

maybe downgrade is doomed to failure due to the depsolver definitely not
playing nicely and due to scriptlets screwing all this anyway?

Thoughts?

thanks,
-sv

-- 
I only speak for me.

_______________________________________________
Yum-devel mailing list
Yum-devel at lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel