Re: [racket-dev] current packages' docs, errors, and conflicts
Ah, great. I didn't know about --tidy. Thank you. I just pushed this change: https://github.com/greghendershott/rackjure/commit/a70fa27662fd10c3c458f9dce77dff7bc73ef6fc That should clear the rightmost column for all my packages (rackjure, and projects using it). On Thu, Jul 10, 2014 at 3:28 AM, Matthew Flatt wrote: > Yes, `raco setup` with no arguments would succeeded and should fix > things up at this point. > > When you use `raco pkg update`, it effectively passes the `--tidy` flag > to `raco setup`. That is, `raco setup --tidy rackjure` would avoid the > problem, and it should also fix things up at this point. > > It's tempting to conclude that `--tidy` mode should be the default for > `raco setup`, and that may be right. I'm not yet sure; `raco setup` is > trying to provide a "do only things that I've requested" interface when > collections are specified, and that competes with its "do the right > thing" job. > > At Wed, 9 Jul 2014 20:29:52 -0400, Greg Hendershott wrote: >> On Wed, Jul 9, 2014 at 8:21 PM, Greg Hendershott >> wrote: >> > On the next raco setup I get: >> > >> > raco setup: --- building documentation --- >> > raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") >> > alist)) >> > raco setup: in: >> > raco setup: in: >> > /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl >> > raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") >> > current-curly-dict)) >> > raco setup: in: >> > raco setup: in: >> > /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl >> > ... and many more... >> >> To clarify, that was when I tried `raco setup rackjure`. >> >> Maybe a full `raco setup` would have succeeded? But even if so, what >> will `raco pkg update rackjure` do -- the full `raco setup` or just >> the `raco setup rackjure`? _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] racket/fasl allows sandbox escape
Credit for this discovery goes to Jens -- I just wrote the email. Sam On Jul 10, 2014 2:36 AM, "Matthew Flatt" wrote: > I've pushed a repair. To double-check it, change 1140 to something like > 1340, since the table of primitives changed as part of the repair. > > Thanks for the report! > > At Wed, 9 Jul 2014 09:39:50 -0400, Sam Tobin-Hochstadt wrote: > > The following exchange with rudybot, which is running the programs in > > a sandbox, demonstrates the issue: > > > > 09:35 rudybot: eval (let () (local-require compiler/zo-marshal > > compiler/zo-structs racket/fasl) (fasl->s-exp (zo-marshal > > (compilation-top 3 (prefix 0 '() '()) (let-void 1 #t (install-value 1 > > 0 #t (primval 1140) (localref #t 0 #f #f #f ))) > > 09:35 samth: ; Value: # > > 09:36 rudybot: eval ((let () (local-require > > compiler/zo-marshal compiler/zo-structs racket/fasl) (fasl->s-exp > > (zo-marshal (compilation-top 3 (prefix 0 '() '()) (let-void 1 #t > > (install-value 1 0 #t (primval 1140) (localref #t 0 #f #f #f ))) > > vector-ref vector-ref) > > 09:36 samth: ; Value: 32681168 > > > > The relevant program is: > > > > (let () > > (local-require compiler/zo-marshal compiler/zo-structs racket/fasl) > > (fasl->s-exp (zo-marshal > > (compilation-top 3 > > (prefix 0 '() '()) > > (let-void 1 #t (install-value 1 0 #t (primval > > 1140) (localref #t 0 #f #f #f ))) > > > > Sam > > _ > > Racket Developers list: > > http://lists.racket-lang.org/dev > _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] current packages' docs, errors, and conflicts
Yes, `raco setup` with no arguments would succeeded and should fix things up at this point. When you use `raco pkg update`, it effectively passes the `--tidy` flag to `raco setup`. That is, `raco setup --tidy rackjure` would avoid the problem, and it should also fix things up at this point. It's tempting to conclude that `--tidy` mode should be the default for `raco setup`, and that may be right. I'm not yet sure; `raco setup` is trying to provide a "do only things that I've requested" interface when collections are specified, and that competes with its "do the right thing" job. At Wed, 9 Jul 2014 20:29:52 -0400, Greg Hendershott wrote: > On Wed, Jul 9, 2014 at 8:21 PM, Greg Hendershott > wrote: > > On the next raco setup I get: > > > > raco setup: --- building documentation --- > > raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") alist)) > > raco setup: in: > > raco setup: in: > > /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl > > raco setup: WARNING: duplicate tag: (def ((lib "rackjure/alist.rkt") > > current-curly-dict)) > > raco setup: in: > > raco setup: in: > > /Users/greg/src/scheme/collects/rackjure/rackjure/rackjure.scrbl > > ... and many more... > > To clarify, that was when I tried `raco setup rackjure`. > > Maybe a full `raco setup` would have succeeded? But even if so, what > will `raco pkg update rackjure` do -- the full `raco setup` or just > the `raco setup rackjure`? _ Racket Developers list: http://lists.racket-lang.org/dev
