Request 257 was acted upon.
This is a comment. It is not sent to the Requestor(s).
_________________________________________________________________________

         URL: https://rt.openpkg.org/id/257
      Ticket: [OpenPKG #257]
     Subject: Flawed 00INDEX.rdf files are generated
  Requestors: [EMAIL PROTECTED]
       Queue: openpkg
       Owner: ms
      Status: open
 Transaction: Comentarios añadidos por ms
        Time: Mar. Sep. 16 11:33:44 2003
_________________________________________________________________________

>From Matthias Kurz:
> When i try to do a "openpkg build bash", i get "FATAL: cannot find package".
>
> Looking into 00INDEX.rdf.bz2, it looks somewhat strange. Try
> lesspipe .../current/SRC/00INDEX.rdf.bz2|grep Description|grep about|less
> and look at the "about=" and "href=":
> E.g.
>     <rdf:Description about="perl-time-20030821-20030821" 
> href="perl-time-20030821-20030821.src.rpm">
>     <rdf:Description about="--" href="kerberos-1.3.1-20030910.src.rpm">
>     <rdf:Description about="--" href="coreutils-5.0.91-20030912.src.rpm">
>                      ^^^^^^^^^^
>     <rdf:Description about="libnet-1.1.0-20030721" 
> href="dailystrips-1.0.28-20030825.src.rpm">
>                      ^^^^^^^^^^^^^^^^^             ^^^^^^^^^^^^^^^^^^^^^
> 
> When i do a "openpkg build" locally, the generated 00INDEX.rdf.bz2 looks
> better. No 'about="--"'.
> $ rpm -q perl
> perl-5.8.0-20030903

>From Michael van Elst:
> That's a corrupted specfile cache database.
>
> The href attribute is computed from the RPM filename.
> The about attribute is computed from the parsed specfile.
>
> Specfiles are extracted from the source RPMs and stored in a
> database to avoid unpacking the RPMs all the time. From the
> index you can see that sometimes even wrong specfiles are
> retrieved from the database, e.g.:
>
> <rdf:Description about="--" href="kerberos-1.3.1-20030910.src.rpm">
> ...
> <Description>
> Various Perl modules for Date and Time handling:
> ...
> </rdf:Description>
>
> Database corruption usually occurs when the indexer is killed,
> Berkeley-DB then gets quickly inconsistent and corrupted.
>
>> How does one clean up such a "corruption" ?                                         
>>                                   
>
> Just delete the cache file. It will be recreated (slowly). I don't
> think there is a reliable method to "repair" a broken database.

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Bug Database Interface                           www.openpkg.org/bugdb
Bug Database List                            [EMAIL PROTECTED]

Reply via email to