| Age | Commit message (Collapse) | Author |
|
Kernel: T9067: Update Linux Kernel to 6.18.38
|
|
|
|
|
|
|
|
T9040: Build FIPS-provider OpenSSL version
|
|
Build FIPS-compatible OpenSSL binaries
The FIPS provider does not get built and installed automatically.
To enable it, you need to configure OpenSSL using the `enable-fips` option.
|
|
for the fix for legacy hash algorithm loading
to make MS-CHAP work correctly again
|
|
podman: T9024: package upgrade from v4.9.5 to v5.8.4
|
|
This updates the used Podman version from 4.9.5 to 5.8.4 which is a major bump.
For this update to work on Vyos we also do need to switch from crun to runc, as
the Debian Bookworm provided version of crun is not working with podman 5.8.4.
Building crun from Debian trixie package sources does not work due to missing
build time dependencies.
|
|
Kernel: T8914: add support for 2.5G pluggables on BCM57810S
|
|
Kernel: T8605: net/l2tp: allow unmanaged tunnel setup without route to peer
|
|
Add the well-known JAMESMTL kernel module patch for bnx2x to advertise 2.5Gbit/s
capabilities on Broadcom NetXtreme2-X cards with BCM57810S chipset.
This is useful for ISP GPON access networks that use 2.5Gbit/s pluggables and
need the NIC to negotiate beyond 1000baseT/Full, avoiding the 940Mbit/s
practical cap on overprovisioned 1G services.
References:
* https://hack-gpon.org/broadcom-57810s/
* https://github.com/JAMESMTL/snippets/blob/dceb2fee74d80c66d/bnx2x/patches/bnx2x_warpcore_8727_2_5g_sgmii_txfault.patch
|
|
|
|
T9013: Add FRR patch to fix BMP connect source-interface deletion
|
|
T9010: Update Linux Kernel to 6.18.36 and re-fresh Intel OOT driver versions
|
|
|
|
T8599: Make source packages required and fix them
|
|
|
|
Update versions:
* igb v5.20.28
* ixgbe v6.4.4
* ixgbevf v5.3.36
* i40e v2.30.18
* ice v2.6.6
* iavf v4.13.35
|
|
T8099: Update strongswan to 6.0.6
|
|
1.0 source format version needs tarball without '.orig' suffix as described in https://www.man7.org/linux/man-pages/man1/dpkg-source.1.html.
Only if debian/source/format exists and contains 3.0, use '.orig'
|
|
Patch modifies debian/control and debian/rules, there is no easy way to
fix source package creation in such case. As quick solution disable
source package build for this package (previously it failed silently)
|
|
Exit with error for other failures:
* Creating/installing dependency package should be error: e.g. debugging
why strongswan cannot find systemd could be easier if build.py failed
when it couldn't install systemd and not when `configure` couldn't
find it.
* Creating tarball
* pre_hook run
|
|
A lot of packages failed to build source package.
Stop ignoring source package build errors and fix it.
To fix source packages:
* Use <source_package>_<upstream_version>.orig.tar.gz naming for source
archive.
* Get `source_package` and `upstream_version` from changelog using
dpkg-parsechangelog utility
* Clean build-deps after usage or dpkg-source sees these files as
changes relative to upstream.
* Add '.github' to --diff-ignore source option
|
|
|
|
|
|
salt: T8973: remove package build due to feature removal
|
|
* Upgrade to 6.0.6
* Update 30-strongswan-configs.chroot to not change
/etc/strongswan.d/charon.conf as the file is part of package
strongswan-charon that should not be installed
* Rebase all patches
* Enable ML-KEM for Post Quantum
|
|
* Remove systemd-dev from dependencies
* Add `set -e` to build_cmd.
Strongswan depends on `systemd` and `systemd-dev`, installing both fails with:
```
The following packages have unmet dependencies:
systemd-dev : Breaks: systemd (< 253-2~) but 252.39-1~deb12u2 is to be installed
E: Unable to correct problems, you have held broken packages.
```
`systemd-dev` contains pkg-config files for systemd and udev, but
current `systemd` package installs identical
`/usr/share/pkgconfig/systemd.pc` - maybe that's why packages cannot be
installed simultaneously.
So remove it from dependencies.
Though the package failed to build, `./build.py` returned 0 as
`build_cmd` has two build commands one after another without any checks
of exit value of first one that builds strongswan. Added `set -e` so
that any failure in any of commands results to build failure.
|
|
T8426: FRR support for EVPN Anycast
|
|
As salt has been marked deprecated via T8056 and is thus deprecated in VyOS 1.5
and VyOS 1.4 it is time to remove it from the rolling release.
|
|
|
|
|
|
Commit 75a495b237 ("sbom: T8542: create during ISO assembly") will shadow any
subsequent calls to vyos.utils.process.cmd() as cmd has be redefined as
variable to hold the CLI command strings for SBOM generation using the syft
binary.
This has been fixed by replacing the cmd variable with another name syft_cmd.
|
|
|
|
|
|
|
|
+ VRF)
Extend check-qemu-install with --test-image-update: build a nested installer
ISO as a second CD-ROM, serve the inner image over HTTP, and exercise add/delete
system image in the default routing context and in a named VRF.
Add make test-image-update and ignore/clean nested_installer_payload.iso artefacts.
|
|
Sometimes I do call scripts/check-qemu-install directly without the Makefile
wrapper, thus it should be ensured that the ISO image exists also from within
the test-case launcher, too.
|
|
|
|
Abusing cats is a prevalent problem in the Linux user community. Users,
ranging from know-nothing neophytes to all-knowing professionals, engage in
cat abuse on a daily basis, whether in their scripts or simple terminal
commands.
https://rseragon.github.io/posts/cat-abuse/
|
|
|
|
There is no need in keeping the old --configd option when starting the
smoketests. VyOS heavily relies on vyos-configd and derivates, so there is no
need anymore to disable it for our smoketests.
|
|
|
|
This reverts commit 194f38b2d9582110d14b21b67e48ed13b58152f9.
|
|
This reverts commit 16ced6d41f030f5621e667abfe0e35aa498bc71b.
|
|
This reverts commit d84d127f91186082df2a786c7e20fe2af55dfa3b.
|
|
This reverts commit 3c3df90237c39caa1e5f7e2cf3180fa4f5f4b0bb.
|
|
Syft from the CDN to prevent a possible supply chain attack"
This reverts commit a0f74b5a2565956ce405b7185842cbdd0b4f1768.
|
|
PR #1204 ("ci: T8943: migrate branch-name refs current->rolling (rollout
1c)") covered .github/workflows/ only and missed seven commit_id values
in scripts/package-build/ that referenced the pre-1c default-branch
names of vyos-owned repos.
The GitHub branch-rename redirect works for the REST API and web UI,
not for git refs in a fresh clone — scripts/package-build/build.py
clones the upstream and `git checkout <commit_id>`, which fails after
the source repo was renamed.
Updated:
libnss-mapuser/package.toml current -> rolling
libpam-radius-auth/package.toml current -> rolling
vpp/package.toml (vyos-vpp-patches) current -> rolling
vyos-1x/package.toml current -> rolling
tacacs/package.toml (libtacplus-map) master -> rolling
tacacs/package.toml (libpam-tacplus) master -> rolling
tacacs/package.toml (libnss-tacplus) master -> rolling
Verified post-rename defaults via `gh api repos/vyos/<r> --jq
.default_branch` for all seven; verified the failure mode via a fresh
`git clone https://github.com/vyos/vyos-1x.git` + `git checkout current`
which errors with "pathspec 'current' did not match any file(s) known
to git".
LTS branches (sagitta/circinus/equuleus) were scanned and require no
changes — only third-party `evgeny-gridasov/openvpn-otp` master appears
there, unaffected by 1c.
🤖 Generated by [robots](https://vyos.io)
|