Needs to check if our version is affected this bug https://github.com/FRRouting/frr/issues/18555
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 6 2025
Apr 5 2025
Apr 4 2025
Apr 3 2025
Any chance this might be backported to 1.4 ?
Apr 2 2025
@dmbaturin Are you sure that should be 100 instead of a two digit number? I think those will be done in lexicographic order, I suspect there may be confusion generated if someone tries to make a 110, and 11 runs first.
Thank you for the quick response to this, and the work to mitigate it 🙌
@mjones-vsat I think the wording is good.
Apr 1 2025
your assumption is correct, but:
In T7159#219749, @dmbaturin wrote:@MPStudyly Well, it's open-source, so anyone can remove the banner by editing the script. The intention of the banner is simply to explain that rolling release and stream builds offer no stability guarantees.
I was looking into backporting it myself lately, at a glance your approach seems correct. I'll look deeper into it.
Mar 31 2025
The current fix is necessary, but it's not complete.
The above linked PR is ready for review by a maintainer. I've tried to cherry-pick only the most relevant commits from the upstream. The build was tested in the vyos-build container (as modified in https://vyos.dev/T7300) after each commit and the overall authentication flow was tested once as described in the PR.
@MPStudyly Well, it's open-source, so anyone can remove the banner by editing the script. The intention of the banner is simply to explain that rolling release and stream builds offer no stability guarantees.
Regarding the failure of the PR integration tests, this may have been a result of a typo, now corrected in rolling here:
https://github.com/vyos/vyos-1x/pull/4425
or an inconsistent github action (I will check that).
SUMMARY:
working versions:
7.5.1-20240509-02-gc9dd2977e 8.0.1
Not working:
8.1 8.2.2 8.3-2 9+ 10+
Mar 30 2025
also failed in PR
Using relative url in .gitmodules will get forked repos difficult to build if not modify .gitmodules manually.
I looked through some Debian and Ubuntu ISOs and didn't notice dropbear installed in the live image. It's likely we are mostly susceptible to this because the live image is used as a loopback mount during normal installation. Many other Debian-based systems would be debootstrapped onto the host.