On Tue, Apr 15, 2008, Jeff Johnson wrote:

>
> On Apr 15, 2008, at 3:39 PM, Ralf S. Engelschall wrote:
>
>> On Tue, Apr 15, 2008, Jeff Johnson wrote:
>>
>>> See if this patch avoids erasing perl. It should.
>>> [...]
>>
>> Yes, successfully fixed the problem when applied to RPM 5.1.0!
>> Many thanks, Jeff.
>
> np.
>
> We can instantly (well I'd like to wait a few days to see how the
> segfault resolves) release 5.1.1 if necessary. OTOH, I suspect that
> you are using a different
> %___NVRA
> macro than most, the default pattern N-V-R.A should parse just fine.

Yes, as the architecture part is useless for OpenPKG, I use:

%___NVRA                 %%{NAME}-%%{VERSION}-%%{RELEASE}

> It would have been nice if RPMTAG_NVRA could be split
> up reliably. That might have been a way to rename and/or
> change encodings for rpmdb entries. There are certainly
> efforts underway to impose UTF8 on rpmdb key retrieval
> underway for several years (rpm-python patch is what I think of).
> Too bad that there is simply no guarenteed encoding yet for
> rpmdb keys no matter how much one wishes there was.

It it has to be split reliably, the only possibility would be to
configure 4 additional macros: ___NVRA_N, __NVRA_V, __NVRA_R and
__NVRA_A which then contain just the pieces and the code uses this. The
__NVRA even then can be defined by expanding the other 4 macros plus the
separator characters.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com