-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update to 1.41.1 #17
Comments
|
Hi @pizzamig, I have update to the VSCode repo to 1.41.1. Can you check and commit the changes? |
|
So it seems that this finally landed in the ports tree recently, but when I try to build the port in poudriere, it fails on me from what looks to be an attempt to use the Internet for marketplace extensions? I'm not 100% sure, but the failure build log can be found here: (Note: The only change I've made to the port is to use the patch in issue #12 to support Node 13.) |
|
Hi @CyberBotX, Thanks for the report. According to the log, it did attempt to download marketplace extensions and failed. I guess the issue can be solved by renaming a patch file as follows: The patch, which was applied only when |
|
Hi @pizzamig, Thanks for committing the changes along with electron6. There seems one leftover with the latest update and the port seems now broken (see #17 (comment)) Could you rename the following file in
|
|
Hi @tagattie , I got the same error and it was fixed by renaming extra-patch-build_gulpfile.extensions.js to patch-build_gulpfile.extensions.js. I have built VS Code package successfully with poudriere after renaming the patch. Thanks! |
|
This issue is now also at FreeBSD Bugzilla: @pizzamig, I hope you can commit the change (renaming a patch file) at your earliest convenience. |
|
On it |
|
Hi @pizzamig, Thanks for so quick action!! I have confirmed the port can be built successfully. So closing this issue. |
VS Code 1.41.1 has been released.
https://github.com/Microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22November+2019+Recovery%22+is%3Aclosed
The text was updated successfully, but these errors were encountered: