![]() arm-stable extra aarch64: 373 new and 374 removed package(s).arm-stable core aarch64: 29 new and 27 removed package(s).arm-stable community aarch64: 748 new and 577 removed package(s).The packages hplip and firewalld requires manual intervention:Īrch Linux - News: hplip 3.20.3-2 update requires manual interventionĪrch Linux - News: firewalld>=0.8.1-2 update requires manual intervention The nss and zn_poly packages requires manual intervention:Īrch Linux - News: nss>=3.51.1-1 and lib32-nss>=3.51.1-1 updates require manual interventionĪrch Linux - News: zn_poly 0.9.2-2 update requires manual intervention 9.5.7 of Pamac is also included in this one.The uboot-rockpi4 also got renamed to uboot-rockpi4b, so users of the Rock Pi 4B should replace the old uboot package with this one.Please select yes when it asks if you want to replace your current kernel with linux. Our linux-aarch64 got renamed to linux while it got updated to 5.8.Users that have installed the “next” kernel needs to switch to linux-rpi4 as linux-rpi4-next has been removed from the repository. The Raspberry Pi default kernel now updated to 5.4.So somehow it got out already.Another Stable update is upon us! This is a huge one! I'd like to see the project return to a state allowing sever owners to do that.Įdit: and before someone tells me that 0.4.17 doesn't exist yet, I should point out that I have a client right in front of me that reports 0.4.17 as its version. That's what I used to do, server-side, until the breaking changes started comming in. This was the state (with a few exceptions I believe) before 0.5.0 was being worked on. What I want to see happen is for the network protocol to become stable again during further development after the official release, so that servers (including mine) can use the latest dev versions as much as possible. I understand the network breakage is necessary for 0.5.0 and I'm not really troubled by it yet. All my players are still on 0.4.16 or 0.4.17. ![]() There are a lot of server-side performance enhancements and other good stuff in the dev versions beyond the last stable release, but I cannot upgraded my server to use them because of network incompatibility. Thus, if the latest version on Github changes the network layer then a server cannot upgrade to it immediately without cutting players off, and instead must wait for players to update first, which can take a long time.įor a real example, take my own server. Most players (99% probably) don't have the ability to update their client at will. So i guess i should decide what mapgen bugfixes should be applied. We can't just do a point release because a lot of compatibility breakage has already happened and started immediately after 0.4.16 was released, all we can do is take 0.4.16 stable and add bugfix PRs to it. Also, some nasty forked Android apps may not update to 0.5.0 so we have a rare chance now to encourage mobile players to switch to the official app (which hopefully will be worked on and improved before 0.5.0 is released), there will be more encouragement if servers move to 0.5.0 earlier than later.įor 0.4.17 let's not put too much work into it, just 0.4.16 stable plus a few major bufixes, no features. ![]() For example enforcing CSM restrictions (flavours) is only possible in 0.5.0. However i do not want to encourage people to stay on 0.4 as there are good reasons to encourage people to move to 0.5.0 as soon as possible. The idea of 0.4.17 was to provide a final 0.4 version for those who want to stay with 0.4 for a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |