[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Package EVR problems in Fedora 2008-06-10



Le Mer 11 juin 2008 17:13, Paul Howarth a écrit :
> Richard W.M. Jones wrote:
>> On Tue, Jun 10, 2008 at 12:24:36PM -0400, buildsys fedoraproject org
>> wrote:
>>> ocaml-deriving:
>>>   F8-updates > F9-updates (0:0.1.1a-4.fc8 > 0:0.1.1a-3.fc9)
>>>
>>> ocaml-gsl:
>>>   F8-updates > F9-updates (0:0.6.0-4.fc8 > 0:0.6.0-3.fc9)
>>>
>>> ocaml-json-static:
>>>   F8-updates > F9-updates (0:0.9.6-4.fc8 > 0:0.9.6-3.fc9)
>> [etc etc]
>>
>> Is this wrong?
>>
>> I'm afraid to say that a lot of packages I have do this.  The reason
>> is that I develop and build packages on Rawhide, then backport them
>> to
>> F-8.  However when backporting to F-8 I have to bump the release
>> number up, typically because I have to add an ExcludeArch: ppc64[*]
>> for F-8, but may be because of other packing twiddling too.
>>
>> I wasn't aware that there had to be a strict increase in package
>> numbering between branches.  (In fact, I wasn't aware that Fedora
>> even
>> allowed updating between Fedora releases).
>
> When you do this backporting, add a release bump after the %{?dist}
> instead of before it, e.g.:
>
> ocaml-json-static-0.9.6-3.fc9
> ocaml-json-static-0.9.6-3.fc8.1

I really don't see why ocaml-json-static-0.9.6-3.fc8 can not be
created instead. Our tools allow the following workflow

push foo-x-1.fc8
push foo-x-1.fc9
push foo-x-2.fc9
push foo-x-2.fc8

There is zero reason why foo-x-2.fc8 can not be built after foo-x-2.fc9


-- 
Nicolas Mailhot


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]