agowa / WSL-DistroLauncher-Alpine

Alpine WSL Microsoft Store packages.
MIT License
211 stars 28 forks source link

Upgrade to 3.13 without waiting for MS Store update? #35

Closed Zegnat closed 3 years ago

Zegnat commented 3 years ago

Currently the Alpine version shipped on the Microsoft Store is on 3.12.1. Not only is that 3 patch versions out of date, a v3.13 branch has been around for 2 months now.

This repository seems to be up-to-date, updating its internal files to get the latest 3.13 patch barely a day after official release. But the store page has not been updated at all.

Is there a way to update the Alpine version in my WSL without waiting for the packaged version in the store to be updated? Preferably without setting up a C++ building environment.

If not, let this issue be a friendly nudge to update the Microsoft Store distribution. I would like to grab some packages currently shipped only in the 3.13 repository without risking them requiring something 3.12 cannot support. Thanks for the hard work!

agowa commented 3 years ago

Is there a way to update the Alpine version in my WSL

It's simple just run the normal update command using apk. Apk will take care of updating all packages to the latest version. The only requirement for the alpine launcher is to bootstraps an alpine Linux environment. Everything else (like upgrading versions) can be done from within the wsl environment.

Updating the version within the launcher will also only take effect for new setups or if one deletes (aka. wslconfig /t) the local wsl distribution first.

Zegnat commented 3 years ago

Ah, hmm, interesting.

I updated /etc/apk/repositories as per the Alpine wiki and did a full upgrade, followed by sync. But never got /etc/alpine-release to change, so I was thinking something about the Alpine core / kernel was being kept back.

What would be the recommended way to check that the Alpine environment was actually updated internally? 🤔

dougbreaux commented 3 years ago

Heh, just wondering the exact same thing.

benjarrell commented 3 years ago

Ah, hmm, interesting.

I updated /etc/apk/repositories as per the Alpine wiki and did a full upgrade, followed by sync. But never got /etc/alpine-release to change, so I was thinking something about the Alpine core / kernel was being kept back.

What would be the recommended way to check that the Alpine environment was actually updated internally? 🤔

You need to install the alpine-base package for those files.

slycordinator commented 2 years ago

It's also of note that sometimes when you install the alpine-base package, the files /etc/alpine-release , /etc/issue, and /etc/os-release get left alone. Instead, it updates/creates files called /etc/alpine-release.apk-new, /etc/issue.apk-new, and /etc/os-release.apk-new