Re: [racket-dev] raco pkg remove needs to state package dependencies

2013-02-13 Thread Jay McCarthy 
I pushed a fix to this issue.

Jay

On Tue, Feb 5, 2013 at 5:36 PM, Danny Yoo d...@hashcollision.org wrote:
 I tried the following:


 128-110-72-21:ragg dyoo$ ~/local/racket/bin/raco pkg remove ragg
 raco pkg remove: cannot remove packages that are dependencies of other 
 packages
   dependencies:
ragg

 The error message needs to say which package is depending on what
 other packages.  Otherwise, the user is forced to manually search for
 which package is causing the problem.



--
Jay McCarthy j...@cs.byu.edu
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay

The glory of God is Intelligence - DC 93
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

[racket-dev] Segfault on HEAD?

2013-02-13 Thread Asumu Takikawa 
Hi all,

I get a reproducible segfault when I built Racket from git HEAD. This is
what I see:

raco setup: 7 making: redex/examples (Reduction Semantics examples)
reverse: contract violation
  expected: list?
  given: 4193052015854236082

SIGSEGV SI_KERNEL SI_CODE 128 fault on addr (nil) sent by kernel
Aborted
make[1]: *** [install-3m] Error 134
make[1]: Leaving directory `/home/asumu/plt/racket-git-segfault/src/build'
make: *** [install] Error 2

It always seems to segfault at that point in the build. I'm building a
fresh copy of the tree, so it's not a stale zo problem or anything.

Anything I can do to diagnose?

Cheers,
Asumu
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] Segfault on HEAD?

2013-02-13 Thread Asumu Takikawa 
On 2013-02-13 11:24:35 -0500, Asumu Takikawa wrote:
 I get a reproducible segfault when I built Racket from git HEAD. This is
 what I see:

A git bisect seems to pinpoint the segfault to commit
4a0adb6a74630f4afc7fd85275ffca76836037b4.

Cheers,
Asumu
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] Segfault on HEAD?

2013-02-13 Thread Robby Findler 
I don't know what would help, but one thing that usually does is a stack
trace. You can probably get it from a coredump file or by something like
this:

$ gdb `which racket`

   [... stuff ...]

(gdb) set args -l setup
(gdb) run



On Wed, Feb 13, 2013 at 10:24 AM, Asumu Takikawa as...@ccs.neu.edu wrote:

 Hi all,

 I get a reproducible segfault when I built Racket from git HEAD. This is
 what I see:

 raco setup: 7 making: redex/examples (Reduction Semantics examples)
 reverse: contract violation
   expected: list?
   given: 4193052015854236082

 SIGSEGV SI_KERNEL SI_CODE 128 fault on addr (nil) sent by kernel
 Aborted
 make[1]: *** [install-3m] Error 134
 make[1]: Leaving directory `/home/asumu/plt/racket-git-segfault/src/build'
 make: *** [install] Error 2

 It always seems to segfault at that point in the build. I'm building a
 fresh copy of the tree, so it's not a stale zo problem or anything.

 Anything I can do to diagnose?

 Cheers,
 Asumu
 _
   Racket Developers list:
   http://lists.racket-lang.org/dev

_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] Segfault on HEAD?

2013-02-13 Thread Matthew Flatt 
I'm trying a clean build now, and maybe the problem will be obvious.

At Wed, 13 Feb 2013 10:36:09 -0600, Robby Findler wrote:
 I don't know what would help, but one thing that usually does is a stack
 trace. You can probably get it from a coredump file or by something like
 this:
 
 $ gdb `which racket`
 
[... stuff ...]
 
 (gdb) set args -l setup
 (gdb) run
 
 
 
 On Wed, Feb 13, 2013 at 10:24 AM, Asumu Takikawa as...@ccs.neu.edu wrote:
 
  Hi all,
 
  I get a reproducible segfault when I built Racket from git HEAD. This is
  what I see:
 
  raco setup: 7 making: redex/examples (Reduction Semantics examples)
  reverse: contract violation
expected: list?
given: 4193052015854236082
 
  SIGSEGV SI_KERNEL SI_CODE 128 fault on addr (nil) sent by kernel
  Aborted
  make[1]: *** [install-3m] Error 134
  make[1]: Leaving directory `/home/asumu/plt/racket-git-segfault/src/build'
  make: *** [install] Error 2
 
  It always seems to segfault at that point in the build. I'm building a
  fresh copy of the tree, so it's not a stale zo problem or anything.
 
  Anything I can do to diagnose?
 
  Cheers,
  Asumu
  _
Racket Developers list:
http://lists.racket-lang.org/dev
 
 _
   Racket Developers list:
   http://lists.racket-lang.org/dev
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

[racket-dev] Missing indentation rules for for{*}/set

2013-02-13 Thread Pierpaolo Bernardi 
(I know how to add them, but maybe should be included out of the box?)

Cheers
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] Missing indentation rules for for{*}/set

2013-02-13 Thread Robby Findler 
Sure. I'll add that.

Robby


On Wed, Feb 13, 2013 at 10:41 AM, Pierpaolo Bernardi olopie...@gmail.comwrote:

 (I know how to add them, but maybe should be included out of the box?)

 Cheers


 _
   Racket Developers list:
   http://lists.racket-lang.org/dev


_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] 5.3.3

2013-02-13 Thread Matthias Felleisen 

Correct. 


On Feb 13, 2013, at 6:05 PM, Danny Yoo wrote:

 On Wed, Feb 6, 2013 at 5:17 PM, Danny Yoo d...@cs.wpi.edu wrote:
 How likely is that authors of planet2 packages use the released version 
 rather than the git head version?
 
 
 Ok, I rescind my point then, since PLaneT2 is in beta.
 
 
 But just to confirm, the release isn't waiting for anything on my end, right?


_
  Racket Developers list:
  http://lists.racket-lang.org/dev