On Wed, 19 Jan 2005 18:40:17 +0100 Marcus Meissner <.> wrote: ...
We relase binary packagesets, not all binary packages belonging to one source rpm.
So while internally xine-ui is a newer version, only xine-lib was released to the outside.
If you think we released the wrong RPM at some times, please do tell.
Ciao, Marcus
Hi, I'm not sure, that I can explain completely, what I meant in my previous posting to the mailing-list. Let's take another example, the 'subversion' package. There are two groups of updates available for the subversion-related packages: 2004-09-24 17:50:26 RPM1: subversion-1.0.0-73.14.i586.rpm RPM2: subversion-devel-1.0.0-73.14.i586.rpm RPM3: subversion-server-1.0.0-73.14.i586.rpm SRC: (subversion-1.0.0-73.14.src.rpm) 2004-12-17 23:46:55 RPM1: subversion-viewcvs-1.0.0-73.17.i586.rpm SRC: (subversion-1.0.0-73.17.src.rpm) So there was a first round of updates, and also a second one; and these two groups of rpms were build from two different source as well. My question was, that in December 2004, when the updated subversion-viewcvs package appeared via YOU; shouldn't be all of the other subversion-related packages updated again? I mean, that the later source has 1.0.0-73.17, and all of the previously patched rpms were just 1.0.0-73.14 ! Hope, that it's clear now. Actually do you know, where to check in case I would like to know more about the version and release numbers? I would like to know a little more on the nomenclature; and actually find an explanation, how you (and others) make up this numbers. I have e.g. subversion 1.0.0-51 originally, but after a security-flaw when update was needed, I have to change two lines in the code, so should be now 1.0.0-51.2 or just something similar? Is it related somehow also to the different kernel versions as 2.4.x and 2.6.x ? I guess, that with the first update-problem I'm not right; but please explain in brief, and any advice would be appreciated concerning the version-numbers. Thank you again:) Pelibali