ASDF upgrade script fails on cmucl/Linux

Robert Goldman rpgoldman at sift.info
Tue Feb 12 22:45:32 UTC 2019


What's interesting is that this is a *new* failure, triggered by the new 
dependencies added to the UIOP system definitions.

Note that this is a test run; maybe I should simply stop testing upgrade 
on cmucl?

R


On 12 Feb 2019, at 16:32, Faré wrote:

> I believe this is an issue with ASDF upgrade not working on CMUCL due
> to CLOS issues.
>
> The workaround is to use the install-asdf.lisp script to overwrite
> CMUCL's builtin ASDF with a newer one. — Although I'm not sure 
> whether
> the script will work if ASDF can't upgrade itself.
>
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• 
> http://fare.tunes.org
> Every great truth begins as heresy and ends as superstition.
>         — Thomas Henry Huxley
>
>
> On Tue, Feb 12, 2019 at 3:51 PM Robert Goldman <rpgoldman at sift.info> 
> wrote:
>>
>> I'm getting a failure of the ASDF upgrade tests on CMUCL since the 
>> UIOP dependencies mod:
>>
>> Upgrading ASDF from version 3.1.7 to version 3.3.2.13
>>
>> TEST ABORTED: Error while trying to load definition for system 
>> test-asdf from pathname 
>> /var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd: don't 
>> recognize component type :MODULE
>>
>> This looks like the key bit of the backtrace:
>>
>> 10: (ERROR
>>      ASDF/FIND-SYSTEM:LOAD-SYSTEM-DEFINITION-ERROR
>>      :NAME "test-asdf"
>>      :PATHNAME 
>> #P"/var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd"
>>      :CONDITION #<ASDF/SESSION:FORMATTED-SYSTEM-DEFINITION-ERROR 
>> {5A92F6A5}>)
>> 11: ("LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. O S)"
>>      #<ASDF/SESSION:FORMATTED-SYSTEM-DEFINITION-ERROR {5A92F6A5}>)
>> 12: (SIGNAL #<ASDF/SESSION:FORMATTED-SYSTEM-DEFINITION-ERROR 
>> {5A92F6A5}>)
>> 13: (ERROR
>>      ASDF/SESSION:FORMATTED-SYSTEM-DEFINITION-ERROR
>>      :FORMAT-CONTROL "don't recognize component type ~S"
>>      :FORMAT-ARGUMENTS (:MODULE))
>> 14: (ASDF/SESSION:SYSDEF-ERROR "don't recognize component type ~S" 
>> :MODULE)[:OPTIONAL]
>> 15: (ASDF/PARSE-DEFSYSTEM:PARSE-COMPONENT-FORM
>>      NIL
>>      (:MODULE "test-asdf" :PATHNAME NIL)
>>      :PREVIOUS-SERIAL-COMPONENT NIL)[:OPTIONAL]
>> 16: (LISP::SLOLOAD
>>      #<Stream for file 
>> "/var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd">)
>> 17: (LISP::INTERNAL-LOAD
>>      #P"/var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd"
>>      #P"/var/lib/jenkins/workspace/asdf-upgrade/test/test-asdf.asd"
>>      :ERROR :SOURCE
>>      :UTF-8)
>>
>> TBH, I'm inclined to regard 3.1.7 as so old that I don't have to 
>> think about it, but I'm open to contradiction. If I don't hear any, 
>> I'll prune that from the set of origin versions to test for upgrades, 
>> and move on.
>>
>> Best,
>>
>> R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/asdf-devel/attachments/20190212/3a71a9b0/attachment.html>


More information about the asdf-devel mailing list