28 lines
1.8 KiB
Markdown
28 lines
1.8 KiB
Markdown
---
|
|
name: project_gururmm_legacy_disabled
|
|
description: GuruRMM's legacy Rust 1.77 (Server 2008R2 / Win7) build variant is DISABLED as of 2026-07-04 — do not just re-enable it; 2008R2 support returns via a separate legacy agent (C++/.NET or clean rewrite)
|
|
metadata:
|
|
type: project
|
|
---
|
|
|
|
The GuruRMM Windows build's **legacy Rust 1.77 variant is disabled** (2026-07-04) via
|
|
`LEGACY_ENABLED=false` in `deploy/build-pipeline/build-windows.sh`.
|
|
|
|
**Why:** the legacy build moves `Cargo.lock` aside and re-resolves deps unpinned; crates.io now
|
|
serves edition2024 versions of transitive deps (`chacha20`/`rand_core` 0.10.1) that Rust 1.77
|
|
cannot parse ("feature `edition2024` is required"). This fail-closed the ENTIRE Windows build and
|
|
blocked modern (amd64/x86/tray) deploys. It is a **BUG-021 recurrence** and is NOT caused by any
|
|
agent code change — it reproduces at any base commit right now. This is at least the 3rd edition2024
|
|
break of the 1.77 build (the `agent/Cargo.toml` transitive-pin list is a monument to it).
|
|
|
|
**What the disable does:** skips the legacy wave/copy/deploy/symlink and EXCLUDES legacy from the
|
|
artifact cleanup, so the last-built legacy binaries (**0.6.76**) are PRESERVED and existing Server
|
|
2008R2 / Win7 endpoints stay supported *frozen at 0.6.76*. Modern agents advance normally.
|
|
|
|
**Mike's directive (2026-07-04):** "Kill the legacy version for now, but we will come back to it" —
|
|
2008R2 support is REQUIRED (a number are still in the wild) and will return via a **different
|
|
architecture (C++/.NET) or a clean rewrite for legacy**, NOT by flipping `LEGACY_ENABLED` back on
|
|
without first solving the 1.77 edition2024 pin problem. Do NOT re-enable it blindly. Tracked in
|
|
`projects/msp-tools/guru-rmm/docs/RMM_THOUGHTS.md`. Related: the policy-controlled tray feature that
|
|
was shipping when this surfaced ([[project_guruconnect]] is a different project).
|