FAKE has target "CI" on Travis#166
Conversation
is really strange. is this an issue with FsCheck, FAKE or NuGet? |
|
It is weird. My guess would be fake or nuget. Don't think we build that path in the build script ourselves. I finally see what you mean with the #I though. |
|
do you know who could we ask for help? would @forki know? |
|
I think it's worth opening an issue on the FAKE repo in the first instance. The NuGet folder is where the nuspec files are. Unfortunately the error is not very clear, I looked a bit at the source code of NuGetHelper.fs in FAKE but couldn't really figure out what is going on. Also, when I try to run on mono locally, it fails at an earlier instance (can't find xunit.console.exe, although it is there...these linux/windows path and case issues are maddening... :( ) |
|
reported fsprojects/FAKE#975 |
|
What happens when you run the same nuget command manually after that error? I guess nuget can't handle your nuspec on mono correctly. |
btw this issues is quite similar to that one I'm fighting over here: fsprojects/FSharpx.Extras#330 |
|
please try to upgrade to FAKE 4.5.4 - I tried to work around it. |
|
@sideeffffect I upgraded FAKE on main, can you try merging from main to this PR so we can check? |
|
Changing the backslashes in the nuspec to forward slashes didn't help either. All out of ideas... |
|
we need to know where is that string coming from. @forki is it possible to debug FAKE? |
|
Actually my strategy in such nuget / mono issues to move to paket. There we need to know where is that string coming from. @forki — |
|
but FsCheck already uses Paket, no? |
|
Yes but not for pack and push.
|
|
Ok, we should do that. Another day, another nuget annoyance. Should be another pull though, I'd like to keep this one open meanwhile. |
because of `Microsoft.Web.XmlTransform.dll`
|
being solved in #170 |
No description provided.