Regression with symbol conflict with SBCL/sb-grovel and 2.006

Bug #623992 reported by Zach Beane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ASDF
Fix Released
High
Faré

Bug Description

ASDF cannot be upgraded to 2.006 if sb-grovel has been loaded before. Here's how to reproduce:

    $ sbcl --noinform --no-userinit --no-sysinit
    * (require 'sb-grovel)

    ("SB-GROVEL" "ASDF")
    * (load "asdf.lisp")

    Upgrading ASDF package to version 2.006

    debugger invoked on a SB-EXT:NAME-CONFLICT in thread #<THREAD
          "initial thread" RUNNING
          {1002ABB181}>:
      EXPORT OUTPUT-FILE causes name-conflicts in #<PACKAGE "SB-GROVEL"> between
      the following symbols:
 ASDF::OUTPUT-FILE, SB-GROVEL::OUTPUT-FILE
    See also:
      The ANSI Standard, Section 11.1.1.2.5

    Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

    restarts (invokable by number or by possibly-abbreviated name):
      0: [RESOLVE-CONFLICT] Resolve conflict.
      1: [ABORT ] Exit debugger, returning to top level.

    (SB-EXT:NAME-CONFLICT #<PACKAGE "SB-GROVEL"> EXPORT OUTPUT-FILE)[:EXTERNAL]
    0]

It's not all that strange to load sb-grovel, because it's loaded as a requirement of sb-posix.

asdf 2.004 did not have this problem.

Revision history for this message
Faré (fahree) wrote :

I posted a fix to sb-grovel some time ago. I'll attach a patch to SBCL...

Changed in asdf:
assignee: nobody → Faré (fahree)
importance: Undecided → High
milestone: none → version2.1
status: New → Confirmed
Revision history for this message
Faré (fahree) wrote :

Here's a patch to SBCL.

Revision history for this message
Faré (fahree) wrote :

Scratch that, I'm preparing a better patch against HEAD that I'll test first...

Revision history for this message
Faré (fahree) wrote :

No, I was confusing with another issue someone had with a bad SBCL installation of SB-GROVEL.

Upgrading SBCL to 2.006 would be nice, but ASDF still has to be able to run in such cases and I'll have to patch it. Grrr.

Revision history for this message
Faré (fahree) wrote :

To reproduce the bug:
rlwrap sbcl --eval '(require :sb-posix)' --eval '(require :asdf)' --eval '(format t "~A~%" (asdf:asdf-version))' --eval '(asdf:load-system :asdf)'

Revision history for this message
Faré (fahree) wrote :

2.124 has a fix.
Is it important to make a 2.007 release now?
Zach, can you use the master branch for testing, rather than the release branch? This would find bugs earlier.

Changed in asdf:
status: Confirmed → Fix Committed
Revision history for this message
Zach Beane (xach) wrote :

I will try to use the master branch for testing and provide prompt bug reports for breakage.

Revision history for this message
Zach Beane (xach) wrote :

Regarding the release of 2.007, it would be extremely helpful to me if it were made very soon. 2.006 fixes some important bugs for me, but is unusable because of this issue.

Revision history for this message
Faré (fahree) wrote :

OK, released 2.007, because SBCL is worth it.

Changed in asdf:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.