Thanks Gustavo, That was a cool idea. I enjoyed the opportunity to hack on some of the pkg files.
Unfortunately, I wasn't able to reproduce the error today -- even on my quarantined machine. I'm not sure if that's because the error pattern somewhat random or because I've been updating the repos for the dependencies in question since I first noticed the error. Anyway, I will definitely keep this in mind the next time I see this error. And I'll post if I figure out what's going on. Thanks again! --Stephen On Sat, Mar 23, 2019 at 7:08 AM Gustavo Massaccesi <gust...@oma.org.ar> wrote: > > 2) The error seems to happen on computers where I am switching some > package > > in the dependency graph from a catalog installation to a github repo > installation. > > I'm not sure if this could contribute to raco deciding that two > packages with the > > same name are actually different and, for some reason, trying to update > them both. > > > I have no clue about what is happening here, but this part sounds > promising. For debugging, you can modify the in the file > pkg/private/install.rkt the function format-deps near > https://github.com/racket/racket/blob/master/racket/collects/pkg/private/install.rkt#L128 > so it shows all the fields of the pkg-desc instead of showing only the name. > > The definition is > (struct pkg-desc (source type name checksum auto? extra-path)) > > Gustavo > > > -- Stephen Foster ThoughtSTEM Co-Founder 318-792-2035 -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
