codeowners added in private repo too
https://github.com/VyOS-Networks/vyos-1x/blob/circinus/CODEOWNERS

According to https://old.reddit.com/r/vyos/comments/1ggzxye/setting_forward_error_correction_in_vyos/lv09d09/ using eth-tool to both set (and show) current fec-setting(s) should be doable (tested on Intel and Mellanox nics using transceivers from FS.com, Flexoptix and Mikrotik):

I believe I am bumping into this issue aswell:

Nobody cares what you need @marekm

@Viacheslav please, one of the free ways that I know and actually used was to build from source - and it's not updated anymore (moved to private repo). BTW, it''s still mentioned on the VyOS website, which is misleading. So this is very much related to this report, I'd like to build my own sagitta images using the new improved build system (hooray no more Jenkins!) but can't, it's not spamming just raising valid concerns. I don't care about pre-built LTS images anymore, just open the sources again so it is possible to build own images as before. Thank you.

@marekm, stop spamming in every message about LTS.
You know all the ways to get LTS images, including entirely free ones.
Thanks!

@Apachez i think we need to add status Implemented for feature request it makes more sense
and for bugs mark them as resolved

Thanks - resolved means its implemented as the blog post stated :-)

The new build system is welcome, thank you. Restricted access to LTS sources, not so much...

The blog post over at https://blog.vyos.io/vyos-project-october-2024-update claims this have been implemented, there is a merge from 10th sept 2024 claiming to be merged - yet this task have been closed with "not applicable - out of scope for VyOS".

This version has a 6.9.0 section so you would think it would also cover 6.6.x

New version 2.19.2 same problem!

It is not a future-oriented solution to require an old version.
Apart from that, the bug has already been closed in https://github.com/vyos/vyos-documentation/pull/1562 - unfortunately I forgot to close the issue here as well.