On Fri, Jun 23, 2006, Caleb Epstein wrote:
> After doing an openpkg build -Ua yesterday (yes, I'm a glutton for hte
> bleeding
> edge!) I am unable to build anything today:
>
> % openpkg -v
> OpenPKG-CURRENT (20060622)
>
> % openpkg build -Ua
> # curling index ftp://ftp.openpkg.org/current/SRC/00INDEX.rdf
> # using XML parser
>
> no element found at line 1, column 0, byte 0 at /openpkg/lib/perl/vendor_perl/
> 5.8.8/i86pc-solaris/XML/Parser.pm line 187
>
> The 00INDEX.rdf file is not there (there is a .bz2) on the OpenPKG FTP server
> and it seems like the current tools can't handle this.
Ops, yes, I see. That's a problem we unfortunately introduced the last
days with the creation of the "openpkg release" command and its new
download URL determination algorithm. The problem actually is that
CURRENT is a special case and in the past it just worked because the
.../current/00INDEX.rdf was read instead of .../current/SRC/00INDEX.rdf
-- but this is no longer possible as it prevents us from storing CURRENT
snapshots into .../current/YYYYMMDD/ in the future.
I've now workarounded it by manually creating a hard-coded 00INDEX.rdf
which simply points to the automatically generated 00INDEX.rdf.bz2. Not
really as elegant as I would like it, but I see no alternative solution
at this time (except to teach the "openpkg build" command about the
special case of CURRENT, too).
Can you retry now that I've created the 00INDEX.rdf?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [email protected]
