Re: createrepo -c problems
seth vidal <[email protected]>
| Newsgroups | gmane.linux.rpm.metadata |
|---|---|
| Message-ID | <1151411442.20913.17.camel@cutter> |
On Tue, 2006-06-27 at 09:42 +0200, Hans-Peter Jansen wrote:
> Am Dienstag, 27. Juni 2006 03:35 schrieb John Newbigin:
> > This is a follow up to the thread "yum won't update vmware" on the
> > yum list. I was having problems which were introduced by using
> > createrepo -c
> >
> > I did some digging, and found that the cache relies of the rpm header
> > field %HDRID (or %SHA1HEADER, depending on your version). A quick
> > check showed that this was missing from the vmware packages,
> > resulting in duplicate hashes for the key in the cache directory (ie,
> > blank (well it uses [] for some reason)).
> >
> > The Sun j2sdk also missing the tags, but surprisingly Sun jdk has
> > them.
> >
> > The command
> > rpm -q --queryformat '%{NAME}-%{HDRID}\n' -p *.rpm
> > will show more or less the problem. Example output:
> > j2sdk-(none)
> > j2sdk-(none)
> > jdk-8bfd4b333a68559d382f5683d845f4ae91e6a410
> > jdk-ee3a94f8e4cb4b4253cc67dc162c442ba0231b04
> >
> >
> > Perhaps if there is no useful id/sum then use the version-release
> > strings? Or just refuse to use the cache for that file.
> >
> > I am not much good with python but I might have a play.
>
> then search the list for some of my patches, test them and call back.
> This problem is somewhat common for commercial rpms, but luckily, the
> rpm header contains fields to mitigate this, but I don't remember the
> gory details ATM.
I'm sorry, I must have screwed up, then. I thought I had merged those
patches.
I've added them to my short list for createrepo.
Again, I'm sorry.
-sv