On Sun, 2018-05-20 at 08:30 -0700, stan wrote:
On Sun, 20 May 2018 13:07:35 +0100
Russel Winder <russel(a)winder.org.uk> wrote:
> Lots of the fc29 package have a number of fc28 and fc27 package
> dependencies. Is this how it works, or will at some point all the
> fc28 and fc27 dependencies get recompiled to be fc29?
This is how it works for releases that aren't mass rebuild releases. I
don't think f29 is a mass rebuild release. If an updated package gets
released during the lifetime of f29, it will be an f29 package.
I'm not sure of how mass rebuilds are scheduled, but F28 was a mass
rebuild release. If there are packages before that in rawhide, they
probably failed to build during the mass rebuild, and weren't
replaced. This also happens if you have an existing rawhide that rolls
through several releases, since obsoletes and orphans will not get
rebuilt. I had a rawhide with packages all the way back to f24 because
of that. Caused problems with updates, because those old packages
wanted to hang onto their old dependencies.
I was on a campaign to remove as many fc1* and fc2[0-8] packages as I assumed
they were garbage that had not been collected. Also one or two were causing
upgrade problem for exactly the reason you highlight.
I found a fc26 package that I actually need, and various fc27 and fc28
packages that would cause the removal of needed or necessary fc29 packages.
All others I deleted since any dependent packages that went were also no
useful for me.
I seems though that this mix of a few f27 and a number of f28 packages is
normal for an f29 Rawhide, so that is fine.
Dr Russel Winder t: +44 20 7585 2200
41 Buckmaster Road m: +44 7770 465 077
London SW11 1EN, UK w: www.russel.org.uk