Should a working fedup in Fedora N's stable repository be a release criterion for N+1?

[Adam Williamson]

On Wed, 2013-12-18 at 11:54 +0000, David Howells wrote:
> Adam Williamson <awilliam at redhat.com> wrote:
> 
> > >  - Install fedup 0.7.0
> > >  - Try it and watch it fail or hang
> > >  - Update to fedup 0.8.0 from updates-testing
> > >  - Run fedup
> > > 
> > > ends up downloading all rpms *twice* a sucking up a correspondingly
> > > immense amount of disk space.
> > 
> > Um, I'm fairly sure it doesn't. It only re-downloads stuff that's
> > different from the previous run.
> 
> There was a bug whereby fedup-0.7.3 would delete all the downloaded RPMs after
> failing to install them.  See:
> 
> 	https://bugzilla.redhat.com/show_bug.cgi?id=1020898

I think that's only if it fails for lack of space, though.

What I found out later yesterday is that fedup 0.8 changed the path
where it downloads packages, so if you update to fedup 0.8 it doesn't
see 0.7's cache, so it re-downloads everything. It's trivial to work
around: 'mv /var/lib/fedora-upgrade /var/lib/system-upgrade',
'mv /var/tmp/fedora-update /var/tmp/system-upgrade' .
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net