Mandriva

Return to the main archive index.

Custom Search

Mandriva Linux Archives: cooker@mandrivalinux.org

Mandriva Linux: cooker@mandrivalinux.org


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


* [2008-04-30 13:28:59 +0100] Colin Guthrie wrote:

Le mercredi 30 avril 2008 à 02:37 +0300, Anssi Hannula a écrit :
Indeed, it shouldn't be 1.1mdv2008.0 since there never was a
1mdv2008.0
release in 2008.0.

Should not the first update have the release "0.1mdv2008.0" ? If you name this first release "1mdv2008.0", the second will be "1.1mdv2008.0" or "2mdv2008.0", but that won't solve the issue...

Actually I think that 0.1mdv would probably be better yes. This would allow for several releases to be made (0.2mdv, 0.3mdv etc.) for whatever reason (simple rebuilds for example) and still have the next distro's 1mdv still beat it. Due to the distsuffix of 2008.1 2009.0 etc. this works but only if there is one and only one build for the older distro.

Yeah, this isn't really something we're going to be changing. See, %mkrel used to work this way automatically... if %mkrel 1 was used with subrel being 1, we'd get 0.1mdv, but now we get 1.1mdv. I don't know why, and I don't care. I'm supporting two different versions here and firefox is lucky enough to build on them all.

So I can't change %mkrel to 0 because then it won't work on corp3 or
corp4.  It has to stay 1 because I'm rapid fire building these by
rebuilding one src.rpm on all the platforms and am not going to start
making it more manual just to satisfy cosmetics.

Besides, you're saying it causes upgrade problems but you're not saying
what the problems are.

Maybe when we push ff or tb or whatnot in updates, someone can bump the
version in cooker?  That would probably be the *simplest* solution.

--
Vincent Danen @ http://linsec.ca/

Attachment: pgp00061.pgp
Description: PGP signature



Date Index | Thread Index

Looking for a job?



Advertisement