Greetings All, In our rpm-md metadata at the moment we are using the package checksum as an identifier (pkgid). This leads to a problem when importing data into the software portal. When a repository has changed we could: * Simply delete all repository content and re-add the new content. This is rather slow and has other problems associated with it when we have hundreds of repositories changing per day (which we do, thanks to the buildservice). * Update the details of only the changed packages. The problem with the latter is that it's difficult to tie the packages in the new repository metadata to the packages in the old repository metadata. The checksum of a package changes every time it's rebuilt, so we can't use that as an identifier to match the old state to the new. There can be multiple packages with the same name+version. The buildid changes every build. If we can't match up the current packages with the old packages we can't just update the details. We also can't determine which packages have been removed or added. So my question is: Is there a set of attributes in the rpm-md that would uniquely identify a package that is build independent and allow diffing of the metadata? -- Benjamin Weber -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org