Re: [racket-users] Package install conflicts on the Racket package catalog

[Ben Greenman]

On 5/5/21, Siddhartha Kasivajhula  wrote:
> Thank you, that helped me understand the issue. I've made the appropriate
> changes so hopefully that'll do it.
>
> This is reminding me that in python package distribution land, you are able
> to explicitly indicate which files make it into the package in a file
> analogous to info.rkt (setup.py, but also MANIFEST.in which allows you to
> bundle non-source files, I believe). Files besides these simply reside in
> the repository but don't make it into either source distributions or
> binaries. This could be a desirable feature to emulate in raco, since it
> would mean that (1) test modules need not be included as part of a
> collection even if present in the repo, (2) I've noticed that some Racket
> packages use a lib/test/docs breakdown with 3 separate packages; this seems
> non-ideal to me since they need to reside in 3 separate repos even though
> the non-source repos are essentially metadata (despite being written in
> full-fledged languages like scribble). By supporting something like a
> "source-include-paths" info.rkt declaration with a list of paths (similar
> to compile-omit-paths and test-include-paths), the tests and docs could all
> reside in the same source repo, without their (necessarily) becoming part
> of the installed package/collection. Any thoughts on this?

lib + tests + docs can all live in the same repo. For example:

https://github.com/97jaz/gregor

It does take some effort to get the organization right, but I don't
have any better ideas.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAFUu9R7SPEribrYXBXDxEx6gtzWit247AU4foO8iWsuGH1-OxQ%40mail.gmail.com.

Re: [racket-users] Package install conflicts on the Racket package catalog

[Siddhartha Kasivajhula]

Ah looking again, I was mistaken -- lib/test/docs breakdown does not
require 3 separate repos. I'll need to take a closer look at how that's set
up. Still, the ability to be explicit about package sources could be
useful, and may provide a simpler alternative.


On Wed, May 5, 2021 at 8:06 PM Siddhartha Kasivajhula 
wrote:

> Thank you, that helped me understand the issue. I've made the appropriate
> changes so hopefully that'll do it.
>
> This is reminding me that in python package distribution land, you are
> able to explicitly indicate which files make it into the package in a file
> analogous to info.rkt (setup.py, but also MANIFEST.in which allows you to
> bundle non-source files, I believe). Files besides these simply reside in
> the repository but don't make it into either source distributions or
> binaries. This could be a desirable feature to emulate in raco, since it
> would mean that (1) test modules need not be included as part of a
> collection even if present in the repo, (2) I've noticed that some Racket
> packages use a lib/test/docs breakdown with 3 separate packages; this seems
> non-ideal to me since they need to reside in 3 separate repos even though
> the non-source repos are essentially metadata (despite being written in
> full-fledged languages like scribble). By supporting something like a
> "source-include-paths" info.rkt declaration with a list of paths (similar
> to compile-omit-paths and test-include-paths), the tests and docs could all
> reside in the same source repo, without their (necessarily) becoming part
> of the installed package/collection. Any thoughts on this?
>
>
>
> On Wed, May 5, 2021 at 3:35 PM Robby Findler 
> wrote:
>
>> I think the issue is that you should not use "tests/private" as your
>> collection path. You should probably either "tests/my-collection/private"
>> or "my-collection/tests/private" as the name.
>>
>> Robby
>>
>>
>> On Wed, May 5, 2021 at 4:38 PM Siddhartha Kasivajhula 
>> wrote:
>>
>>> That makes sense. Is there a recommended way to exclude test paths from
>>> being part of the package modules? I have a `compile-omit-paths`
>>> declaration in the info.rkt
>>> 
>>> file. Since this is structured as a multi-collection package, could it be
>>> that these declarations need to be at the package-level info.rkt file
>>> instead of the collection-specific one to take effect on the package index?
>>> Another option I can think of is to move the `tests` folder which is
>>> currently at the package level down to the collection level, might that
>>> work?
>>>
>>> FTR re: the lazytree package, I assume it's showing conflicts because
>>> although it hasn't been changed recently, it depends on the relation
>>> package which depends on both on-macro and social-contract, which are in
>>> conflict per the above.
>>>
>>> Re: mischief, I've encountered some weird errors in the past with
>>> building docs, for instance see this comment
>>> .
>>> I wonder if that's related to the conflicting names.
>>>
>>>
>>> On Wed, May 5, 2021 at 1:38 PM Sam Tobin-Hochstadt 
>>> wrote:
>>>
 I think there's two things you're seeing.

 1. The results hadn't yet updated for your typed-compose change. I no
 longer see a conflict here: https://pkg-build.racket-lang.org/
 2. The conflicts page is for _all_ the packages in the whole package
 catalog. That's why it always mentions mischief.

 The issue for on-macro and social-contract is that they both have a
 file tests/private/util.rkt, which means they can't be installed at
 the same time.

 Finally, mischief has that issue intentionally -- there are two
 versions of it on the pkg server, one of which is the development
 branch. It's true that it hasn't been updated recently, but that's the
 idea.

 Sam


 On Wed, May 5, 2021 at 4:08 PM unlimitedscolobb
  wrote:
 >
 > 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 

Re: [racket-users] Package install conflicts on the Racket package catalog

[Siddhartha Kasivajhula]

Thank you, that helped me understand the issue. I've made the appropriate
changes so hopefully that'll do it.

This is reminding me that in python package distribution land, you are able
to explicitly indicate which files make it into the package in a file
analogous to info.rkt (setup.py, but also MANIFEST.in which allows you to
bundle non-source files, I believe). Files besides these simply reside in
the repository but don't make it into either source distributions or
binaries. This could be a desirable feature to emulate in raco, since it
would mean that (1) test modules need not be included as part of a
collection even if present in the repo, (2) I've noticed that some Racket
packages use a lib/test/docs breakdown with 3 separate packages; this seems
non-ideal to me since they need to reside in 3 separate repos even though
the non-source repos are essentially metadata (despite being written in
full-fledged languages like scribble). By supporting something like a
"source-include-paths" info.rkt declaration with a list of paths (similar
to compile-omit-paths and test-include-paths), the tests and docs could all
reside in the same source repo, without their (necessarily) becoming part
of the installed package/collection. Any thoughts on this?



On Wed, May 5, 2021 at 3:35 PM Robby Findler 
wrote:

> I think the issue is that you should not use "tests/private" as your
> collection path. You should probably either "tests/my-collection/private"
> or "my-collection/tests/private" as the name.
>
> Robby
>
>
> On Wed, May 5, 2021 at 4:38 PM Siddhartha Kasivajhula 
> wrote:
>
>> That makes sense. Is there a recommended way to exclude test paths from
>> being part of the package modules? I have a `compile-omit-paths`
>> declaration in the info.rkt
>> 
>> file. Since this is structured as a multi-collection package, could it be
>> that these declarations need to be at the package-level info.rkt file
>> instead of the collection-specific one to take effect on the package index?
>> Another option I can think of is to move the `tests` folder which is
>> currently at the package level down to the collection level, might that
>> work?
>>
>> FTR re: the lazytree package, I assume it's showing conflicts because
>> although it hasn't been changed recently, it depends on the relation
>> package which depends on both on-macro and social-contract, which are in
>> conflict per the above.
>>
>> Re: mischief, I've encountered some weird errors in the past with
>> building docs, for instance see this comment
>> .
>> I wonder if that's related to the conflicting names.
>>
>>
>> On Wed, May 5, 2021 at 1:38 PM Sam Tobin-Hochstadt 
>> wrote:
>>
>>> I think there's two things you're seeing.
>>>
>>> 1. The results hadn't yet updated for your typed-compose change. I no
>>> longer see a conflict here: https://pkg-build.racket-lang.org/
>>> 2. The conflicts page is for _all_ the packages in the whole package
>>> catalog. That's why it always mentions mischief.
>>>
>>> The issue for on-macro and social-contract is that they both have a
>>> file tests/private/util.rkt, which means they can't be installed at
>>> the same time.
>>>
>>> Finally, mischief has that issue intentionally -- there are two
>>> versions of it on the pkg server, one of which is the development
>>> branch. It's true that it hasn't been updated recently, but that's the
>>> idea.
>>>
>>> Sam
>>>
>>>
>>> On Wed, May 5, 2021 at 4:08 PM unlimitedscolobb
>>>  wrote:
>>> >
>>> > 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 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, 

Re: [racket-users] Package install conflicts on the Racket package catalog

[Robby Findler]

I think the issue is that you should not use "tests/private" as your
collection path. You should probably either "tests/my-collection/private"
or "my-collection/tests/private" as the name.

Robby


On Wed, May 5, 2021 at 4:38 PM Siddhartha Kasivajhula 
wrote:

> That makes sense. Is there a recommended way to exclude test paths from
> being part of the package modules? I have a `compile-omit-paths`
> declaration in the info.rkt
> 
> file. Since this is structured as a multi-collection package, could it be
> that these declarations need to be at the package-level info.rkt file
> instead of the collection-specific one to take effect on the package index?
> Another option I can think of is to move the `tests` folder which is
> currently at the package level down to the collection level, might that
> work?
>
> FTR re: the lazytree package, I assume it's showing conflicts because
> although it hasn't been changed recently, it depends on the relation
> package which depends on both on-macro and social-contract, which are in
> conflict per the above.
>
> Re: mischief, I've encountered some weird errors in the past with building
> docs, for instance see this comment
> .
> I wonder if that's related to the conflicting names.
>
>
> On Wed, May 5, 2021 at 1:38 PM Sam Tobin-Hochstadt 
> wrote:
>
>> I think there's two things you're seeing.
>>
>> 1. The results hadn't yet updated for your typed-compose change. I no
>> longer see a conflict here: https://pkg-build.racket-lang.org/
>> 2. The conflicts page is for _all_ the packages in the whole package
>> catalog. That's why it always mentions mischief.
>>
>> The issue for on-macro and social-contract is that they both have a
>> file tests/private/util.rkt, which means they can't be installed at
>> the same time.
>>
>> Finally, mischief has that issue intentionally -- there are two
>> versions of it on the pkg server, one of which is the development
>> branch. It's true that it hasn't been updated recently, but that's the
>> idea.
>>
>> Sam
>>
>>
>> On Wed, May 5, 2021 at 4:08 PM unlimitedscolobb
>>  wrote:
>> >
>> > 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
>> 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 
>> 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 :-)
>> >>>
>> >>> 

Re: [racket-users] Package install conflicts on the Racket package catalog

[Siddhartha Kasivajhula]

That makes sense. Is there a recommended way to exclude test paths from
being part of the package modules? I have a `compile-omit-paths`
declaration in the info.rkt

file. Since this is structured as a multi-collection package, could it be
that these declarations need to be at the package-level info.rkt file
instead of the collection-specific one to take effect on the package index?
Another option I can think of is to move the `tests` folder which is
currently at the package level down to the collection level, might that
work?

FTR re: the lazytree package, I assume it's showing conflicts because
although it hasn't been changed recently, it depends on the relation
package which depends on both on-macro and social-contract, which are in
conflict per the above.

Re: mischief, I've encountered some weird errors in the past with building
docs, for instance see this comment
.
I wonder if that's related to the conflicting names.


On Wed, May 5, 2021 at 1:38 PM Sam Tobin-Hochstadt 
wrote:

> I think there's two things you're seeing.
>
> 1. The results hadn't yet updated for your typed-compose change. I no
> longer see a conflict here: https://pkg-build.racket-lang.org/
> 2. The conflicts page is for _all_ the packages in the whole package
> catalog. That's why it always mentions mischief.
>
> The issue for on-macro and social-contract is that they both have a
> file tests/private/util.rkt, which means they can't be installed at
> the same time.
>
> Finally, mischief has that issue intentionally -- there are two
> versions of it on the pkg server, one of which is the development
> branch. It's true that it hasn't been updated recently, but that's the
> idea.
>
> Sam
>
>
> On Wed, May 5, 2021 at 4:08 PM unlimitedscolobb
>  wrote:
> >
> > 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
> 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 
> 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 jay.mc...@gmail.com
> 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
>  

Re: [racket-users] Package install conflicts on the Racket package catalog

[Sam Tobin-Hochstadt]

I think there's two things you're seeing.

1. The results hadn't yet updated for your typed-compose change. I no
longer see a conflict here: https://pkg-build.racket-lang.org/
2. The conflicts page is for _all_ the packages in the whole package
catalog. That's why it always mentions mischief.

The issue for on-macro and social-contract is that they both have a
file tests/private/util.rkt, which means they can't be installed at
the same time.

Finally, mischief has that issue intentionally -- there are two
versions of it on the pkg server, one of which is the development
branch. It's true that it hasn't been updated recently, but that's the
idea.

Sam


On Wed, May 5, 2021 at 4:08 PM unlimitedscolobb
 wrote:
>
> 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 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  
>> 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 jay.mc...@gmail.com 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
  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?
 >
 > 

Re: [racket-users] Package install conflicts on the Racket package catalog

[unlimitedscolobb]

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 
>  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  
> 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 jay.mc...@gmail.com 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 
>>>  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 racket-users...@googlegroups.com. 
>>> > 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 

Re: [racket-users] Package install conflicts on the Racket package catalog

[Siddhartha Kasivajhula]

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
 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 
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 jay.mc...@gmail.com 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
>>  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 racket-users...@googlegroups.com.
>> > 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 racket-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/eb380f03-7a73-40e7-a3a6-0e8c3252525an%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 racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[racket-users] Racket v8.1

['John Clements' via Racket Users]

--
Racket version 8.1 is now available from

https://racket-lang.org/


- DrRacket tabs can be dragged, and have new close buttons.

- Racket CS supports cross-compilation using `raco exe`.

- Racket CS supports Android on 32-bit and 64-bit ARM processors.

- The database library supports running queries in OS threads.

- Check-Syntax arrows correctly identify the definition site of
  identifiers with contracts.

- Racket CS performance has improved for structure predicates and
  accessors

- Racket CS is faster at multiplying extremely large numbers and
  dividing large integers.

- Racket CS allows callbacks to raise exceptions if they are annotated
  with `#:callback-exns?`.

- New ephemeron hash tables simplify the implementation of tables where
  keys can refer to values.

- Typed Racket supports for/foldr.

- The stepper works for #lang htdp/*sl.

- Struct signatures work for the ASL teaching language.

The following people contributed to this release:

Alex Harsányi, Alex Knauth, Alexander Shopov, Alexis King, Andrew
Mauer-Oats, Anish Athalye, Ben Greenman, Bert De Ketelaere, Bob Burger,
Bogdan Popa, Brian Adkins, Cameron Moy, David Van Horn, Dexter Lagan,
Dominik Pantůček, Fred Fu, Greg Hendershott, Gustavo Massaccesi, Hazel
Levine, Ismael Luceno, Jack Firth, Jarhmander, John Clements, Jörgen
Brandt, Laurent Orseau, Lazerbeak12345, Matthew Flatt, Matthias
Felleisen, Micah Cantor, Mike Sperber, Noah Ma, Patrick McCarty, Paulo
Matos, Pavel Panchekha, Philip McGrath, Philippe Meunier, R. Kent
Dybvig, Robby Findler, Ryan Culpepper, Ryan Kramer, Sam Tobin-Hochstadt,
Sergiu Ivanov, Shu-Hung You, Sorawee Porncharoenwase, Stephen De
Gabrielle, William J. Bowman, bmitc, xxyzz, yjqww6, and ymdarake

Feedback Welcome
--

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/9660bf5e-49ee-4b71-8407-4e1fcde01b36%40mtasv.net.

[racket-users] Having trouble with HtDP design recipe at exercise 213

['Because Of' via Racket Users]

Greetings,

I'm working through HtDP alone and am currently stuck.  All the relevant code 
can be found here: 
https://gist.github.com/simalaia/d5b50e9a0bd36b89128aecb43de71cf8

As suggested in the book I start with  (insert-everywhere/in-all-words)  and 
design a new function with signature  1String Word -> List-of-Words  and the 
purpose statement "insert 1String into every position of Word", I get stuck 
here.

I used the table method to try and work out what the next function I need to 
design is, however everything I try results in me coming up with needing 
exactly the function that I started with, along with the problem that I started 
with.

Every attempt at directly solving it (but see below on how this 'solving' is 
being done) without an auxiliary function results in some tests failing.  For 
example  (f "x" (list "a")) -> (("x" "a") ("a" "x"))  but this fails when given 
length zero or two words.  I have not managed any improvements on this.

There seems to be a fairly obvious solution along the lines of  (map append 
(prefixes w) (map (λ (x) (cons s x)) (suffixes w)))  however that seems to 
require the simultaneous processing chapter and is based more on intuition than 
design.  I am, either way, not asking as to the solution for this problem.

What I can't work out is where my understanding of the design recipe is 
failing?  The implementation I have so far is based on my extrapolation from 
the list-of-lists recipe to how trees would likely be processed and based on a 
pure intuitive guess rather than systematic application of the recipe.  The 
table method also doesn't seem to be producing any results that I understand.  
Nor are the tests helping...

Hence, could someone assist with debugging my understanding of the recipe?

Regards.

-- 
Sent with https://mailfence.com
Secure and private email

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/1801521434.203448.1620219317116%40ichabod.co-bxl.

[racket-users] Racket News - Issue 49

[Paulo Matos]

Hi all,

Apologies all for the yatus on Racket News - but we are back.
Issue 49 is finally here and packed with lots of Racket goodness:
https://racket-news.com/2021/05/racket-news-issue-49.html

Enjoy,

-- 
Paulo Matos

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/34c248a2-6546-43d6-8457-371c5cc7bcccn%40googlegroups.com.