Why is collections is failing pkg-build?

[Alexis King]

I recently split up my collections package into the usual lib, doc, and
test packages, and I noticed today that pkg-build seems to be barfing on
it in such a way that is causing its dependencies to have issues, too.
Unfortunately, I can’t seem to figure out what’s wrong. If I look at
http://pkg-build.racket-lang.org, it claims that the collections package
has “conflicts in dependency”, but clicking on the link gives me
information that doesn’t seem to make much sense. Furthermore, all of
the collections-{lib,doc,test} packages say that “install both succeeds
and fails”, which manages to be even more confusing.

What am I missing here? How can I get these to build properly? The build
failure is also affecting downstream dependents, such as my functional
and megaparsack libraries.

Alexis

[Alexis King]

Can anyone answer this? I’d really like to get my packages’
documentation indexed again, but I really have no idea what’s wrong.

[Matthew Flatt]

I think it's a problem with the package server's calculation of mutual
dependencies. It generates the build plan

functional-doc
collections-doc
collections-lib collections functional-lib

where the third step there correctly identifies three packages as
needing to be built together, because they're mutually dependent.
However, "functional-doc" and "collections-doc" should be in the same
mutually dependent set --- because "functional-doc" depends on
"functional-lib", which depends on "collections", which depends on
collections-doc".

I'll work on this as soon as I can. Meanwhile, you might have intended
for "functional-lib" to depend on "collections-lib", and it's possible
that change avoid the bug in the dependency calculation.

> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/B7D9731F-E236-4023-8996-C5055A761E
> 25%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Alexis King]

> On Oct 14, 2016, at 1:49 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
>
> I'll work on this as soon as I can. Meanwhile, you might have intended
> for "functional-lib" to depend on "collections-lib", and it's possible
> that change avoid the bug in the dependency calculation.

Wonderful, thank you for the explanation! No rush on fixing it,
since you are indeed right: I only recently split my collections
package into lib/doc/test, and I apparently forgot to update
functional to depend on the split out variants, which triggered the
issue. I’ve fixed functional-lib now, so if that works fine, it
should be fixed for the time being, anyway.

Thanks again,
Alexis