I know you are usually announcing here when some major branch change is being made but is there an up-to-date document/pinned post describing their current state?
Something like this? https://docs.turris.cz/basics/changelog/
EDIT: not much about āfutureā releases in there, if thatās what you wanted; also https://docs.turris.cz/basics/tos_versions/
And itĀ“s reason why I need kernel 4.19.
You mean the SFP patches? Those are currently not available in kernel 4.19 either, or even kernel 5.4, unless backported [8]
Backport the phy/phylink/sfp patches currently queued in netdev or in mainline
also
Really?
https://git.openwrt.org/?p=openwrt%2Fopenwrt.git&a=search&h=HEAD&st=commit&s=sfp
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=1c16b574c4f77a30a0268acee30be96ae0dc5948
Yes really, those patches are currently not included in kernel 4.19 or 5.4, unless backported. The emphasis is on backported and that is what those OpenWrt commits are.
The source code repository for those patches is
and/or
That aside, OpenWrt may not even branch off a release with kernel 4.19 in March and instead skip ahead to a release with kernel 5.4 at a later date - depending on the outcome of the aforementioned poll. And current results are 12 votes in favour of 5.4 vs. 11 votes in favour of 4.19 with 8 eligible votes pending, not sure when the poll is to closed.
You can track our work on Gitlab (https://gitlab.labs.nic.cz/groups/turris/-/issues?scope=all&utf8=ā&state=opened&milestone_title=Turris%20OS%205.0, https://gitlab.labs.nic.cz/groups/turris/-/merge_requests?scope=all&utf8=ā&state=opened&milestone_title=Turris%20OS%205.0)
I am not sure what information you want to know. In general we are not working with roadmap. We release when it is ready. That means that we donāt have some pinned date or state updates. Everything in reality is in public on our Gitlab.
I want exactly this kind of information:
But I guess it is partially derivable from this documentation page.
Results are in (though void of targeted branch off date)
5.4 kernel is prefered for the next release as this option got 14 votes, whereas 4.19 kernel got 13 votes.
Probably a relief for the TOS developer team not having to carry yet another branch any time soon.
[9] http://lists.infradead.org/pipermail/openwrt-adm/2020-February/001316.html
1 Like
Turris OS 6 with kernel 5.4 sounds good. I believe in an early release of Turris OS 5 (unfortunately without kernel 4.19). Turris OS 3 and 4 are obsolete.
According to the workflow it would have to traverse the build chain to HBS
Branch for the real releases that are deployed to the end users automatically.
whilst TOS4.x currently occupying slots: HBK ā HBT ā HBS.
Do you really think that I am linking all of your posts?
Why I canĀ“t answer to your question? This message was written polite.
Turris OS 5 is coming (into HBK).
1 Like
Well today I finally did it and tried to migrate to TOS 5 as I wanted to skip TOS 4 on my blue Turris 1.0.
I made sure to download latest 5.0 medkit form here turris1x-medkit-latest.tar.gz 2020-03-10 04:29 39M
Then
schnapps import -f turris1x-medkit-*.tar.gz
schnapps rollback factory
and verified with schnapps mount factory that there is 5.0 version in /etc/turris_version
reboot
After reboot logged to forris @ http://192.168.1.1 made basic config and selected packages after that logged with putty on console and found out running updater in the background but /etc/turris_version showed 4.0.5 version even it should be 5.0 as it was after medkit installation
within about 10 minutes followed another restart and finally i still am on 4.0.5 HBS instead 5.0 HBL
root@turris:~# uname -a
Linux turris 4.14.172 #0 SMP Tue Mar 10 00:13:43 2020 ppc GNU/Linux
BusyBox v1.28.4 () built-in shell (ash)
______ _ ____ _____
/_ __/_ ____________(_)____ / __ \/ ___/
/ / / / / / ___/ ___/ / ___/ / / / /\__
/ / / /_/ / / / / / (__ ) / /_/ /___/ /
/_/ \__,_/_/ /_/ /_/____/ \____//____/
TurrisOS 4.0.5, Turris 1.x
root@turris:~#
Now tried switch-branch to hbl
-
echo āOPKG update failed. Please see previous output to know what went wrong.ā
OPKG update failed. Please see previous output to know what went wrong. -
set +x
,%%%%%%%%, ,%%/\%%%%/\%% ,%%%\c "" J/%%%
%. %%%%/ o o %%%
%%. %%%% _ |%%%%% %%%%(__Y__)%%' // ;%%%%-/%%%ā
(( / `%%%%%%%ā
\ .ā |
\ / \ | |
\/ ) | |
\ /_ | |__
(___________)))))))
You are now in branch containing software build every night. It often contains bugs and sometimes requires manual intervention!
It is based on latest stable OpenWRT branch with latest Turris OS changes.
Turris team provides no guarantees and no support for this branch. You can get some help on forum (https://forum.test.turris.cz/).
If you encounter some bugs than please debug cause and report it to developers trough gitlab (https://gitlab.labs.nic.cz/),
You shouldnāt be in this branch unless you are advanced user!
To return to stable branch run this command: switch-branch hbs
after about another 10 minutes and anouther restart
BusyBox v1.30.1 () built-in shell (ash)
______ _ ____ _____
/_ __/_ ____________(_)____ / __ \/ ___/
/ / / / / / ___/ ___/ / ___/ / / / /\__
/ / / /_/ / / / / / (__ ) / /_/ /___/ /
/_/ \__,_/_/ /_/ /_/____/ \____//____/
TurrisOS 5.0.0, Turris 1.x
root@turris:~# uname -a
Linux turris 4.14.162 #0 SMP Thu Jan 16 13:58:33 2020 ppc GNU/Linux
this is slightly less obsolete, even kernel bit older but newer version of busybox
after that I double checked that I have really 5.0 in factory and yes I do
root@turris:~# schnapps mount factory
Snapshot factory mounted in /mnt/snapshot-@factory
root@turris:~# cd /mnt/snapshot-@factory/
root@turris:/mnt/snapshot-@factory# cd etc
root@turris:/mnt/snapshot-@factory/etc# cat turris-version
5.0.0
So it is unclear to me why intermezzo with 4.0.5 is needed even factory TOS to which rollback was initiated is 5.0
I eventually end up on HBS anyway as upgrade every night is maybe too much for me to handle.
1 Like
Yes, I can confirm that it is going to be merged in HBK. A forum thread will follow soon or would you like to create it? I donāt have anything against that. 
Thatās why I havenāt posted a changelog as I know that you will publish it here without providing any further details.
Rest assured that we are providing details as soon as we know. This time it was a little bit delayed as I had a vacation just for this day.
3 Likes
Well I can publish any details you request as it is under my fingerprints right now. Take your vacation, maybe I will have a lot of free time to play with TOS 5 due to quarantine. Please create the forum thread for all of us as I am no familiar with that.
Your finding was already discussed here on the forum. Iām including forum threads as reference:
This is expected. See this English thread below or you can find also other posts related to it:
If you prefer Czech, you can take a look here:
In this case, you havenāt provided details why update failed. But most likely you encountered this issue:
Otherwise, there is no need to provide more details.
1 Like