alpine-mksite issueshttps://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/issues2023-12-07T10:07:01Zhttps://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/issues/16explain colored dots meaning on2023-12-07T10:07:01Ztxt.fileexplain colored dots meaning onIn the "End of support" table column on https://alpinelinux.org/releases/ are colored dots. Sadly the whole page does not explain what the different colors mean.
I am puzzled about the meaning of the dots
* v3.16 has support status "sec...In the "End of support" table column on https://alpinelinux.org/releases/ are colored dots. Sadly the whole page does not explain what the different colors mean.
I am puzzled about the meaning of the dots
* v3.16 has support status "sec fixes" and a green dot.
* v3.15 has support status "sec fixes" and an orange dot.
Why does v3.16 have a green dot and v3.16 an orange when the support status is the same?
I understand why it it rendered that way because I understand what https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/blob/5b6615fe0655fb715266a3c1861fbca57b795cd0/_scripts/generate_release_branches.lua#L6 does. I do not understand why it is written that way.https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/issues/15use actual EOL date instead of index of array2024-01-07T15:24:32Ztxt.fileuse actual EOL date instead of index of arrayCurrently https://alpinelinux.org/releases/ shows that alpine Linux v3.15 is EOL but reciving the same support level as v3.16 (which is not EOL). Which datapoint should I trust more? The EOL date or the support state?
![Screenshot_2023-...Currently https://alpinelinux.org/releases/ shows that alpine Linux v3.15 is EOL but reciving the same support level as v3.16 (which is not EOL). Which datapoint should I trust more? The EOL date or the support state?
![Screenshot_2023-11-11_at_20-58-57_Alpine_release_branches_Alpine_Linux](/uploads/b9004392b0fc216a1bea32761b8434d0/Screenshot_2023-11-11_at_20-58-57_Alpine_release_branches_Alpine_Linux.png)
According to https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/blob/5b6615fe0655fb715266a3c1861fbca57b795cd0/_scripts/generate_release_branches.lua#L37 the support state is taken from the index of the array. This seems kind of a bad idea.
Sadly I am missing lua knowledge and have to many other project to send you a proper merge request. 😦Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/issues/14Include Alpine into rpi-imager2024-03-27T19:28:55ZmacmpiInclude Alpine into rpi-imager[`rpi-imager`](https://www.raspberrypi.com/news/raspberry-pi-imager-imaging-utility/) is now default multi-platform tool from Pi Foundation to seamlessly generate installation media for Pi-compatible distributions.\
Many distributions as...[`rpi-imager`](https://www.raspberrypi.com/news/raspberry-pi-imager-imaging-utility/) is now default multi-platform tool from Pi Foundation to seamlessly generate installation media for Pi-compatible distributions.\
Many distributions aside Pi OS are supported (Ubuntu variants, Manjaro, Apertis, RISC OS,...).
Being listed & supported is very easy, with just a couple of short `.json` files as described [here](https://github.com/raspberrypi/rpi-imager/issues/545#issuecomment-1408682589), one of which being hosted/updated on original distribution web site (hence my post here).\
According to instructions, request to get listed needs to come from @ncopa I guess.
Being supported in that tool will probably drive more Pi users to Alpine distribution.\
Any interest?3.19.0