Still exists
https://github.com/vyos/vyos-build/blob/current/data/live-build-config/package-lists/vyos-utils.list.chroot
https://github.com/vyos/vyos-build/blob/equuleus/data/live-build-config/package-lists/vyos-utils.list.chroot

Implemented, checked in VyOS 1.3-stable-202308240442

vyos@r1# set policy local-route
Possible completions:
 > local-route  IPv4 policy route of local traffic
 > local-route6 IPv6 policy route of local traffic

Should be fixed, needs testing.

PR 1.3 https://github.com/vyos/vyos-user-utils/pull/6

I tried on VyOS 1.4-rolling-202308300021 .

PR1 didnt seem to have any affect on this night build:

PR https://github.com/vyos/vyos-1x/pull/2185

Fixed in https://vyos.dev/rVYOSONEX0c2384114e8abbd9c883a57729564c70c0a86eec

Done https://github.com/vyos/vyos-user-utils/tree/equuleus

It's trying to find the template in /etc/, but it is located in /opt/vyatta/etc

vyos@r1:~$ generate vpn x509 key-pair testone
Can't open /etc/key-pair.template for reading, No such file or directory
140089191929024:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/etc/key-pair.template','r')
140089191929024:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
vyos@r1:~$ cat /etc/key-pair.template
cat: /etc/key-pair.template: No such file or directory
vyos@r1:~$ 
vyos@r1:~$ sudo find / -name key-pair.template
/boot/rw/opt/vyatta/etc/key-pair.template
/opt/vyatta/etc/key-pair.template

Already fixed https://github.com/vyos/vyos-cloud-init/blob/dac6d08b6ba40f9b39622e00a32974532cf03de4/cloudinit/config/cc_vyos.py#L309

PR for 1.4 https://github.com/vyos/vyos-1x/pull/2184

Sep 21 09:31:58 home-r1 pppd[2827]: Unsupported protocol 'IPv6 Control Protocol' (0x8057) received

You can ignore it or configure ipv6

set interfaces pppoe pppoe2 ipv6

We should avoid raw options for configurations.
We agree don’t implement it anymore.

PR created: https://github.com/vyos/vyos-live-build/pull/1

PR:
https://github.com/vyos/vyatta-cfg-system/pull/204

In T1311#157738, @syncer wrote:

@Viacheslav will you backport this to 1.3 ?

PR https://github.com/vyos/vyos-1x/pull/2183

@Viacheslav will you backport this to 1.3 ?

The event handler was rewritten to python3 and doesn't use pipes.

Fixed

[edit]
vyos@r1# set policy route-map TEST rule 10 set metric -10
[edit]
vyos@r1# commit
[edit]
vyos@r1# sudo vtysh -c "show run"
Building configuration...

This task for the ldpd
https://vyos.dev/T4020

My bad, I don't know how I missed them!

The smoketest was in the same PR https://github.com/vyos/vyos-1x/pull/2162/files#diff-59a88cf4e56c56db9de173bbdeb31600f9733d8598570831364d2d368402af77

@Apachez thanks to you.
Let me check it.

Some tests on filesystem.squashfs from VyOS 1.4-rolling-202308280021.

In T5472#157591, @aderouineau wrote:

Should a smoke test be added?

Better to have it

A note from https://forum.vyos.io/t/clear-logs-on-vyos/6878/10?u=viacheslav that there might be issues if removing directories from within / var/log/* doesnt occur to PR381 since that PR was specific about which files and directories to remove when it comes to / var/log. That is only files NOT directories were removed from / var/log.

Validated the change on version 1.4-rolling-202308250021.

https://github.com/vyos/vyos-1x/pull/2180 implement a workaround by changing the default values of stdout and stderr from PIPE to None.

https://github.com/vyos/vyos-1x/pull/2179

A baseline could be to look at the linux kernel config used by Alpine Linux for their RPI-builds:

@sdev I saw c-po revert the merge.
and I didn't expect that it will cost lots of time also.
It's better to revert it.
Currently, I will maintain kernel configs in my own branch.

@tjjh89017 This will need to be re-evaluated. The build from your PR was taking in excess of 8 hours on the build server - the defconfig likely needs to be brought down to only the minimum required modules/drivers for successful builds on target devices.

Just a comment: