There is the --repackage rpm option, but despite several reports, I am afraid it is
still broken because the %_repackage_dir macro expands to a non existing
/var/spool/repackage directory.
-o-
kk1
> torsdagen den 23 oktober 2003 19.11 skrev Levi Ramsey:
> > On Thu Oct 23 18:55 +0200, Buchan Milne wrote:
> > > > I'd be happy if there were simply a "rollback" directory on the
> > >
> > > mirrors. In
> > >
> > > > other words when a package is updated, yesterday's version rolls over
> > >
> > > to the
> > >
> > > > rollback directory. Also, the reason I said "yesterday's" is often
> > >
> > > there are
> > >
> > > > 2-3 quick updates in a row, as little packaging bugs get caught by the
> > > > packager and quickly fixed - would hate to have two broken packages,
> > > > the rollback and the new one, on the mirrors.
> > >
> > > Why does this need to be on the mirrors? Wouldn't it be better if you
> > > could set urpmi to auto-repackage some packages (like rpm --repackage)?
> > > Then, you would have the last package you had working (since youhave no
> > > guarantees about yesterday's package anyway).
> > >
> > > For cookers, this would be quite useful ...
> >
> > Excellent idea, Buchan... you are a veritable fountain of such.
>
> I concur. This could also be used with the idea I had with the term
> "update_media":
>
> 1. pack needed installed package(s)
> 2. put it in the urpmi cache (or where ever...)
> 3. rename it (pretty much like the troels perl script)
> 4. run rsync
> 5. do update
>
>
>
