If you load 2.25.4 on that release, it will not use the prebuilt asdf but rather just load the *.fas files, which misses totally the point: prebuilt components do not work.
If you want to reproduce the error and see how component-relative-pathname fails to produce the right output, use this
(ext::install-bytecodes-compiler)
(setf *load-verbose* t)
(progn
(load "~/devel/ecl/contrib/asdf/asdf.lisp" :verbose t)
(load "~/devel/ecl/contrib/asdf/specials.lisp" :verbose t)
(load "~/devel/ecl/contrib/asdf/bundle.lisp" :verbose t)
(load "~/devel/ecl/contrib/asdf/ecl.lisp" :verbose t))
(trace asdf::component-relative-pathname)
(load "~/quicklisp/setup")
The definition of component-relative-pathname wraps around the slot value, totally ignoring the value of the pathname type
(defmethod component-relative-pathname ((component component))
(coerce-pathname
(or (slot-value component 'relative-pathname)
(component-name component))
:type (source-file-type component (component-system component))
:defaults (component-parent-pathname component)))
Thus the screwed output:
1> (COMPONENT-RELATIVE-PATHNAME #<compiled-file "sockets" "sockets">)
<1 (COMPONENT-RELATIVE-PATHNAME #P"SYS:SOCKETS.FASC")
1> (COMPONENT-RELATIVE-PATHNAME #<compiled-file "sockets" "sockets">)
<1 (COMPONENT-RELATIVE-PATHNAME #P"SYS:SOCKETS.FASC")