Hi.
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
On Tue, Sep 16, 2003 at 09:33:40AM +0200, Matthias Kurz wrote:
rdf:Description about=-- href=kerberos-1.3.1-20030910.src.rpm
When i do a openpkg build locally, the generated 00INDEX.rdf.bz2 looks
better. No 'about=--'.
That's a corrupted specfile cache database.
The href attribute is
On Tue, Sep 16, 2003 at 09:53:47AM +0200, Michael van Elst wrote:
On Tue, Sep 16, 2003 at 09:33:40AM +0200, Matthias Kurz wrote:
rdf:Description about=-- href=kerberos-1.3.1-20030910.src.rpm
When i do a openpkg build locally, the generated 00INDEX.rdf.bz2 looks
better. No
On Tue, Sep 16, 2003 at 10:11:02AM +0200, Matthias Kurz wrote:
I hope it is clear, that this happens with the 00INDEX.rdf.bz2 on
openpkg.org, not here.
Sure.
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
On Tue, Sep 16, 2003 at 11:03:10AM +0200, Michael van Elst wrote:
On Tue, Sep 16, 2003 at 10:11:02AM +0200, Matthias Kurz wrote:
[...]
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
On Tue, Sep 16, 2003, Michael van Elst wrote:
rdf:Description about=-- href=kerberos-1.3.1-20030910.src.rpm
When i do a openpkg build locally, the generated 00INDEX.rdf.bz2 looks
better. No 'about=--'.
That's a corrupted specfile cache database.
The href attribute is computed from
On Tue, Sep 16, 2003 at 11:31:00AM +0200, Matthias Kurz wrote:
Just delete the cache file. It will be recreated (slowly). I don't
think there is a reliable method to repair a broken database.
What is its name ?
You should know :) You pass the name to 'openpkg index' with the -C
option.
On Tue, Sep 16, 2003 at 11:35:26AM +0200, Michael van Elst wrote:
On Tue, Sep 16, 2003 at 11:31:00AM +0200, Matthias Kurz wrote:
Just delete the cache file. It will be recreated (slowly). I don't
think there is a reliable method to repair a broken database.
What is its name ?
You
On Tue, Sep 16, 2003, Ralf S. Engelschall wrote:
On Tue, Sep 16, 2003, Michael van Elst wrote:
[...]
Database corruption usually occurs when the indexer is killed,
Berkeley-DB then gets quickly inconsistent and corrupted.
We had yesterday some other brokeness in the index of CURRENT
On Tue, Sep 16, 2003 at 12:09:01PM +0200, Thomas Lotterer wrote:
Problem persisted but is now fixed manually on openpkg.org for one time.
The index is not only broken if the indexer is killed but also when
two or more instances of the indexer are running simultaneously.
Correct. Berkeley-DB
10 matches
Mail list logo
