-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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 suse-create-upload-vhd.md #121832
Update suse-create-upload-vhd.md #121832
Conversation
removed end-of- life version and made adjustments to the instruction examples.
@mries : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
updating link due to changes in document in this pull request: MicrosoftDocs#121832
Learn Build status updates of commit 0d7c115:
|
File | Status | Preview URL | Details |
---|---|---|---|
articles/virtual-machines/linux/disk-encryption-sample-scripts.md | Details | ||
articles/virtual-machines/linux/suse-create-upload-vhd.md | Details |
articles/virtual-machines/linux/disk-encryption-sample-scripts.md
- Line 282, Column 75: [Warning: bookmark-not-found]
Cannot find bookmark '#prepare-opensuse-152' in 'articles/virtual-machines/linux/suse-create-upload-vhd.md', did you mean '#prepare-opensuse-154'?
articles/virtual-machines/linux/suse-create-upload-vhd.md
- Line 240, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
- Line 248, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Can you review the proposed changes? Note that the validation warnings must be resolved before merging. When the changes are ready for publication, add a #label:"aq-pr-triaged" |
updated version number link
Learn Build status updates of commit d1fc86d:
|
File | Status | Preview URL | Details |
---|---|---|---|
articles/virtual-machines/linux/suse-create-upload-vhd.md | Details | ||
articles/virtual-machines/linux/disk-encryption-sample-scripts.md | ✅Succeeded |
articles/virtual-machines/linux/suse-create-upload-vhd.md
- Line 240, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
- Line 248, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
fixed code blocks
Learn Build status updates of commit 4ed83f5:
|
File | Status | Preview URL | Details |
---|---|---|---|
articles/virtual-machines/linux/suse-create-upload-vhd.md | Details | ||
articles/virtual-machines/linux/disk-encryption-sample-scripts.md | ✅Succeeded |
articles/virtual-machines/linux/suse-create-upload-vhd.md
- Line 240, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
- Line 248, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
more code blocks
Learn Build status updates of commit 63d0b22: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
sudo zypper ar -f https://download.opensuse.org/distribution/15.2/repo/oss openSUSE_15.2_OSS | ||
sudo zypper ar -f http://download.opensuse.org/update/15.2 openSUSE_15.2_Updates | ||
``` | ||
```bash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the repository path need to change here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes this was an oversight. I had the new repo links tested but didn't add them to the document (or, it looks like a copy paste issue) . That was an oversight. They should look like this:
sudo zypper ar -f https://download.opensuse.org/update/openSUSE-stable openSUSE_15.4_Updates
sudo zypper ar -f https://download.opensuse.org/repositories/Cloud:/Tools/15.4 Cloud:Tools_15.4
sudo zypper ar -f https://download.opensuse.org/distribution/openSUSE-stable/repo/oss openSUSE_stable_OSS
I will update in a patch.
Updated opensuse 15.4 version table and corrected links for adding repositories.
Learn Build status updates of commit 33d0b14: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 6275152: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
removed end-of- life version and made adjustments to the instruction examples.