Hi, I'd like to chime back in and say that renaming manual.rkt to typed-compose.rkt didn't seem to affect much the list of install conflicts for typed-compose. I also get a lot of conflicts with mischief (but not only), even though typed-compose doesn't depend on it, or doesn't even define names which would be similar to what mischief defines.
That's puzzling. - Sergiu On Wednesday, May 5, 2021 at 9:16:14 PM UTC+2 Siddhartha Kasivajhula wrote: > Hi, > I'd like to report that I'm seeing conflicts being reported on my packages > as well. I haven't made recent changes to these packages so the conflicts > seem to have appeared spontaneously. > > Here is one example: https://pkgs.racket-lang.org/package/lazytree > Clicking into the "conflicts" results in a 404. > > Another example: https://pkgs.racket-lang.org/package/on-macro > Here, clicking into "conflicts" seems to implicate, believe it or not, the > `mischief` package, of which it appears there are two separate versions > <https://pkgd.racket-lang.org/pkgn/search?q=mischief> on the package > index. This does seem rather mischievous, and maybe raco doesn't like it? > Yet, it doesn't look like either mischief or mischief-dev have been changed > in years, so I'm not sure why it should complain now about these > longstanding shenanigans. > > A third example: https://pkgs.racket-lang.org/package/social-contract > Clicking into "conflicts" once again seems to implicate mischief, but > mischief isn't even in the dependencies for this package so this just seems > unfair! > > On other packages that I've uploaded, the conflicts link was a 404. > > Similar questions as OP - should I fix something here, for instance by > avoiding the mischief dependency? Should mischief itself be updated in some > way? Or is this (as seems likely) caused by a recent change in the package > index, and if so, how should package authors respond (assuming it isn't a > bug)? What to do about the 404s -- e.g. is there a command to generate the > conflicts locally? > > Thanks, > > > > On Sun, May 2, 2021 at 6:59 AM unlimitedscolobb <[email protected]> > wrote: > >> Hi Jay, >> >> Thanks a lot for helping me read that file! >> >> I didn't know Scribble outputs shared the same namespace. I renamed the >> documentation file to typed-compose.scrbl as you suggest and I'm waiting >> for build reports from the package catalog. >> >> In fact, I hesitated between manual.scrbl and typed-compose.scrbl >> initially, and couldn't find a reason to prefer one over the other. Now I >> have a reason :-) >> >> - >> Sergiu >> >> On Saturday, May 1, 2021 at 3:23:47 PM UTC+2 [email protected] wrote: >> >>> Howdy Sergiu, >>> >>> The conflicts file you link to has all the conflicts for everything >>> that `pkg-build` builds. The line relevant for you is: >>> >>> ``` >>> doc "manual": >>> bystroTeX cbor print-debug ratchet riff simply-scheme typed-compose >>> ``` >>> >>> The solution is to rename your manual from `manual.scrbl` to >>> `typed-compose.scrbl`. Scribble outputs are in a kind of "global" >>> namespace. >>> >>> Jay >>> >>> -- >>> Jay McCarthy >>> Associate Professor @ CS @ UMass Lowell >>> http://jeapostrophe.github.io >>> Vincit qui se vincit. >>> >>> >>> -- >>> Jay McCarthy >>> Associate Professor @ CS @ UMass Lowell >>> http://jeapostrophe.github.io >>> Vincit qui se vincit. >>> >>> >>> On Sat, May 1, 2021 at 5:56 AM unlimitedscolobb >>> <[email protected]> wrote: >>> > >>> > Hello, >>> > >>> > I checked my package >>> https://pkgd.racket-lang.org/pkgn/package/typed-compose recently and >>> noticed that it listed some "Conflicts" in the field "Most recent build >>> results". On the other hand, the separate field "Conflicts" slightly above >>> says "None". >>> > >>> > When I open the log shown in "Most recent build results" (attached) it >>> starts with the line "Install conflicts:", which as far as I get are not >>> the same thing as "Package Conflicts" explained here in the manual: >>> https://docs.racket-lang.org/pkg/Package_Concepts.html#(part._concept~3aconflicts) >>> >>> . >>> > >>> > What are install conflicts? Should I fix them? What is the command >>> that generates that log? >>> > >>> > (typed-compose also used to have an undeclared dependency, which I >>> have just fixed by updating it's info.rkt.) >>> > >>> > - >>> > Sergiu >>> > >>> > -- >>> > 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 [email protected]. >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/racket-users/03bfa876-6418-41a2-a37a-5c39ad13121cn%40googlegroups.com. >>> >>> >>> >> -- >> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/racket-users/eb380f03-7a73-40e7-a3a6-0e8c3252525an%40googlegroups.com >> >> <https://groups.google.com/d/msgid/racket-users/eb380f03-7a73-40e7-a3a6-0e8c3252525an%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/310449db-1450-4043-9d73-c80c95587653n%40googlegroups.com.
