From 6ccdf8f322d60da6b9eafac16d18640ecb5bd31b Mon Sep 17 00:00:00 2001
From: Krzesimir Nowak <knowak@microsoft.com>
Date: Tue, 30 Jan 2024 12:58:54 +0100
Subject: [PATCH] overlay profiles: Update unmask of virtual/libcrypt

virtual/libcrypt got a revision bump, but we still want to stay at
version 1, so instead of unmasking an outdated revision, unmask
anything with version lower than 2.
---
 .../coreos-overlay/profiles/coreos/base/package.unmask          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.unmask b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.unmask
index 1cf12438fc..b57d64a2cd 100644
--- a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.unmask
+++ b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.unmask
@@ -7,7 +7,7 @@
 # libxcrypt, because we need to figure out how to solve the dep loop
 # that results from the migration (python -> virtual/libcrypt ->
 # libxcrypt -> glibc -> python).
-=virtual/libcrypt-1-r1
+<virtual/libcrypt-2
 
 # Overwrite portage-stable mask. We haven't seen LLVM related problems
 # with rust so far, so keep using 1.70.0.