On 2010-10-25, at 11:44 AM, David Greaves wrote: > On 25/10/10 16:28, Anas Nashif wrote: >>> >>> quote:"To be exact, it's 0.61.25-1.1 and the fix is in 0.61.25-2.1. (As in, >>> same upstream version, newer packaging.)" >>> >> >> What is the upstream version? > Sorry, upstream also includes ourselves. > I was being pessimistic and assuming we couldn't increment the x.y.z because > we were tracking an upstream source tarball releases - hence my use of 'may'. > >> You are referring to a packaging version in >> some other build system and want to reference that in meego? > No. > >>> If the packaging changes then the proper package version should be >>> incremented - right? And since the source is not modified and the -release >>> can't be used then a non-numeric should be appended. >>> >> >> Packaging version 0 starts in meego, and not somewhere else. We cant adopt >> versioning history of packages from other systems into meego. > > I agree. Absolutely not. > > The problem is that using the .changes file I cannot look at two rpms with > different -release values and know: > * Was there a source change > * Was there a packaging change > * Were any bugs/security issues fixed
if you compare 2 packages with different same release but different build numbers, then there should not be any diff in the changelog if you compare 2 packages with different release number, there should be a log entry related to that change, since obs bumps the release when there is a source change. The diff in the changelog should give you a description of what has changed. source change mandates a version change, thats why we reject package changes that change the source directly instead of submitting a new tarball version. If no source change then most likely a patch has changed or something in the packaging. If a package just rebuilds because of a dependency, this package is also subject to QA, since an API might have changed. Anas > > From a QA/validation perspective this makes life harder than it needs to be. > > Also see my other reply please. > > David > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
