Jim Perrin wrote: > As I remember it, the major problem stems from the fact that rpm just > packages up the files and stuffs them in an archive when it creates > the rollback. Any scripting or specialness of the original rpm is > lost. This is getting a touch outside the area where I claim to know > what I'm talking about, so your best bet would be to ask someone > slightly more familiar with it here on the list, or one of the rpm > developers. I did it even on the rpm mailing list, here's the answer: -------- Original Message -------- Subject: Re: A Rollback question Date: Thu, 27 Oct 2005 10:58:54 -0400 From: James Olin Oden <james.oden@xxxxxxxxx> Reply-To: RPM Package Manager <rpm-list@xxxxxxxxxx> To: RPM Package Manager <rpm-list@xxxxxxxxxx> References: <4360B2EC.6040908@xxxxxx> On 10/27/05, Igor Jagec <igorm5@xxxxxx> wrote: > Hi there, > I read on the Yum mailing list that Rollback feature doesn't work fine > and that it is going to be removed from rpm. Is that true? I like that > feature very much and I never experienced any problem with it. > Hi Igor, No its not going away. Sure there are issues and they are being addressed. I think the truth of the matter is that RedHat has no desire to support them. That said I and Jeff Johnson are actively working on it, and Jeff actually works for Tekelec now, which is where I work. Its also true that rollbacks are as yet an experimental feature, but that said they are being used in production in some places, and if you are in the telcom business needed to support some form of backout, its the only game in town that works within the confines of package management (there are other approaches like splitting mirrors and restoring an entire image which have their places, but they do not work within the confines of package management). So, don't be alarmed by comments like that, but at the same time keep your eyes wide open if you try to use the feature. Also, any suggestions and/or patches are very much welcome. Cheers...james P.S. Yum supporting rollbacks is not something Seth Vidal is looking into, but the more stable they get and the more people start using (and carefully crafted patches to yum) may sway Seth's oppinion. The real problem is that most people don't work within the confines of the Telco space so they don't really understand our needs. While their all looking at network depsolvers (which is a good thing) these solutions seldom work well for vendors of telco companies because they typically have strong seperation of their telephony networks and the internet. -- Igor Jagec