-
Notifications
You must be signed in to change notification settings - Fork 586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.IO.Stream
error when using SharpCompress
#2702
Comments
System.IO.Stream
error when using System.IO.Stream
error when using SharpCompress
Welcome to the FAKE community! Thank you so much for creating your first issue and therefore improving the project! |
I accidently pressed the submit button before filling out the bug. I'll update the description and notify when ready. Sorry. |
Ok, now the description is ready. |
Can you please re-try with the latest FAKE release? |
Hi, thanks for the update. It might take me a few days. It seems that since the release of dotnet 7 together with the fact that I have |
Sadly I can not test it at this time. Since the release of dotnet 7 (with my project Thanks |
Hi, I'm terribly sorry, I completely forgot about this issue. Only a couple of days ago I went to fix something and I was reminded about this issue 🙁. I'm still having trouble running fake-cli with DotNet 6.0 so I converted the Sorry again for the long delay ... |
Description
When trying to use the SharpCompress library to create tar.gz archives (It seems that the functionality was removed in Fake 5) I used the following code:
(The complete script is attached as TXT file).
When running
dotnet fake build -t Publish
I get the following error:Repro steps
I guess running build script in an empty directory will generate the same error, but it could be copied to the top of the this repository to have the required files.
Expected behavior
To run correctly and compress the files 🙂.
Actual behavior
See errors above
Known workarounds
None that I know of.
Related information
Thanks in advance (and thank you for this great library).
The text was updated successfully, but these errors were encountered: