On 23/09/09 at 07:22 +0200, Peter Van Eynde wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello Lucas,
>
> Lucas Nussbaum wrote:
> > On 22/09/09 at 18:47 +0200, Peter Van Eynde wrote:
> >> I'm a bit surprised by this FTBFS as ecl is also auto-build for other
> >> platforms. What
Processing commands for cont...@bugs.debian.org:
> close 547682
Bug#547682: sbcl + common-lisp-controller install raises package lock error
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to "Jonathan E. Magen"
> merge 547682 53
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Lucas,
Lucas Nussbaum wrote:
> On 22/09/09 at 18:47 +0200, Peter Van Eynde wrote:
>> I'm a bit surprised by this FTBFS as ecl is also auto-build for other
>> platforms. What research did you do in this failure?
>
> I have done no research at
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cl-yacc | 0.3-2 | source, all
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) w
Hi Peter,
On 22/09/09 at 18:47 +0200, Peter Van Eynde wrote:
> I'm a bit surprised by this FTBFS as ecl is also auto-build for other
> platforms. What research did you do in this failure?
I have done no research at all. But it's easily reproducible.
Have you actually tried to build it in a clean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Lucas,
I'm a bit surprised by this FTBFS as ecl is also auto-build for other
platforms. What research did you do in this failure?
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
http://www.livejournal.com/users/pvaneynd/
"God, roo
Processing commands for cont...@bugs.debian.org:
> reassign 547682 common-lisp-controller
Bug #547682 [sbcl] sbcl + common-lisp-controller install raises package lock
error
Bug reassigned from package 'sbcl' to 'common-lisp-controller'.
Bug No longer marked as found in versions sbcl/1:1.0.25.0-1.
