This avoids that no standard Proxmox repository can be detected during
upgrade anymore. There is a 'ignore-pre-upgrade-warning' about the
suite already, that the frontend can display when upgrading is not
allowed yet.
Signed-off-by: Fiona Ebner <f.eb...@proxmox.com>
---
It's not ideal, for the time between when the update for proxmox-apt
is rolled out and when the Bookworm repositories are actually made
available. And it would need to be done for each major upgrade.
For next time, I'll try to come up with something better. Probably,
the callers should let the backend here know when upgrade is allowed
and then the backend can act accordingly.
src/repositories/mod.rs | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/repositories/mod.rs b/src/repositories/mod.rs
index d8848b8..6588b90 100644
--- a/src/repositories/mod.rs
+++ b/src/repositories/mod.rs
@@ -106,7 +106,12 @@ pub fn standard_repositories(
continue;
}
- if repo.is_referenced_repository(entry.handle, product,
&suite.to_string()) {
+ if repo.is_referenced_repository(entry.handle, product,
&suite.to_string())
+ || repo.is_referenced_repository(
+ entry.handle,
+ product,
+ &suite.next().unwrap().to_string(),
+ ) {
entry.status = Some(repo.enabled);
}
}
--
2.30.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
