The sound of silence, again... and I'm afraid it probably means confirmation. While technically this is compliant with the licenses (it is true what was said that the GPL doesn't require source code to be public, just available to those who get binaries), it loses one of the important advantages of Open Source - the "many eyes" - https://en.wikipedia.org/wiki/Linus%27s_law
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mon, Oct 28
Sun, Oct 27
No worries, I'm all good here. I can turn off signing and carry on with the unsigned drivers as before. It is all good if I load them in the pre-script. If I figure it out I'll let you know.
I’d prefer to drop it at all for now.
Until someone can investigate it more deeply.
I don’t have any idea what is wrong.
Thanks
address in https://github.com/vyos/vyos.vyos/pull/217
but have conflicts, we need to return to it after merging T6815
Addressed in https://github.com/vyos/vyos.vyos/pull/190
Addressed in https://github.com/vyos/vyos.vyos/pull/246
Addressed by PR
https://github.com/vyos/vyos.vyos/pull/248
Looking at dmesg from a working config we can see:
On systems that do not support SecureBoot, mokutil will exit with code 255. This causes show version to break as the cmd() that launches it raises an error. The mokutil execution through cmd() should catch that return code as normal:
nothing in the difference between .51 & .52. I'm beginning to doubt myself now that that was the point it broke. That was also the point where you started requiring signed drivers and maybe I'm conflating the problems I had at that point.
Sat, Oct 26
Still broken I'm afraid.
@SteveP Can you try the latest rolling?
PR list below; after the first two are reviewed/merged, the others can be moved out of draft, in order of dependencies.
https://github.com/vyos/vyconf/pull/11
https://github.com/vyos/vyos1x-config/pull/31
https://github.com/vyos/vyatta-cfg/pull/94
https://github.com/vyos/libvyosconfig/pull/21
https://github.com/vyos/vyos-1x/pull/4176
https://github.com/vyos/vyos-build/pull/824
Fri, Oct 25
Thu, Oct 24
I just built from the current top-of-tree and installed onto my working system and I no longer am getting that log message filling up my system logs. I'm not sure if something indirectly fixed it or what - regardless it appears fixed now. Therefore, I'm moving the status to resolved.
The issue of breaking smoketest is not with iproute2
Updated repos below; one minor change needed for replacements to my_set/my_delete before PR: