Plan for tomorrows (20070418) FESCO meeting

[Thorsten Leemhuis]

On 19.04.2007 10:47, Michael Schwendt wrote:
> On Thu, 19 Apr 2007 07:10:26 +0200, Thorsten Leemhuis wrote:
>> On 18.04.2007 23:05, Brian Pepple wrote:
>>> /topic FESCO-Meeting -- MISC -- Vote on rebuilding packages with old
>>> disttag - jwb 
>> Something related to this (mentioned on FAB-list 24 hours ago, but 
>> didn't get any replies) to fix the problem in F8 and later:
>> Why don't we just expand the disttag to something else without the
>> "fc<I>n</I>" in it in the devel branch? Then we don't have run into the 
>> "package disttag doesn't match the release it is shipped in" problem 
>> when a package is not rebuild during a devel cycle. A simple ".1" maybe 
>> -- that should make everybody happy afaics:
>> [thl at thl tmp]$ # this is how we do it right now:
>> [thl at thl tmp]$ rpmdev-vercmp 0 1.0 5.fc6 0 1.0 5.fc7
>> 0:1.0-5.fc7 is newer
>> [thl at thl tmp]$ # why not do it like this:
>> [thl at thl tmp]$ rpmdev-vercmp 0 1.0 5.fc6 0 1.0 5.1
>> 0:1.0-5.1 is newer
>> Or am I or rpmdev-vercmp missing something here?
> You are missing the rebuild.

I thought it wasn't needed to mention that, as a new distag of course 
are only picked on the next build.

> Assume we create the FC-7 branch from current devel and target Fedora 8 in
> devel. Then devel starts with the packages that have a dist tag .fc7 (or
> older) or no dist tag. All the packages need at least one rebuild to
> change the package release field.

Sure.

> Only packages, which are not rebuilt,
> keep their old Release. But builds in devel would get a .fc8 dist tag, so
> when rebuilding a package why jump to .1 instead of .fc8?

Because we solve the problem in the *long term* once and for all.

Example:

- after F7 was branched change the disttag in devel to be ".1"
- packages that get build afterwards pick it up
- assume we have a mass-rebuild in F8 (we'll have one sooner or later in 
any case, so lets just assume F8 for now)
- F8 gets released and no packages shipped with it have a disttag "fc8" 
now; new packages build after release get one, as that easier
- F9 sees no mass rebuild; packages that were not rebuild during the 
devel cycle F8 -> F9 can stay as they are; F9 gets release and there are 
no packages with a ".fc8" in it, so we avoid the confusion we have now 
(that is: ship F7 with packages that have fc6 in ENVR)

> If you want to rebuild all packages with a changed %dist and without
> modifying the spec files to bump Release, the plan is flawed. "1" > "f",
> hence "1" is newer than all fcN dist tags, okay, but you only get an
> upgrade path from Fedora <= 7 to "1", since for Fedora 9 you would need to
> jump from "1" to "2" for any rebuilds to be newer than Fedora 8 again.

No, you don't need to jump from "1" to "2" -- packages that were not 
rebuild during that devel cycle simply stay as they are. Packages that 
got build due to updates will have the release-integer increased that's 
*before* the %{?dist} in the spec file.

CU
thl