From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v3 backup stable-2] pbs2to3: add upgrade checker binary
Date: Wed, 28 Jun 2023 14:17:44 +0200 [thread overview]
Message-ID: <27cc8bfe-c42d-6e20-ce3c-2fb561cefd44@proxmox.com> (raw)
In-Reply-To: <20230628115328.77255-1-c.ebner@proxmox.com>
Am 28.06.23 um 13:53 schrieb Christian Ebner:
> Adds the pbs2to3 upgrade checker with some basic checks.
>
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
Didn't give it an in-depth look, because of limited time, but:
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
Tested-by: Fiona Ebner <f.ebner@proxmox.com>
Potential for follow-up:
After upgrade, I got
WARN: a suitable kernel 'pve-kernel-6.2' is installed, but an unsuitable
'6.2.9-1-pve' is booted, missing reboot?!
which is a bit confusing because the booted one is a pve-kernel-6.2,
just not the newest ;)
> +
> + fn check_repo_file(
> + &mut self,
> + found_suite: &mut Option<(String, String)>,
> + mismatches: &mut Vec<(String, String)>,
> + strange_suite: &mut bool,
> + repo_file: APTRepositoryFile,
> + ) -> Result<(), Error> {
> + for repo in repo_file.repositories {
> + if !repo.enabled || repo.types == [APTRepositoryPackageType::DebSrc] {
> + continue;
> + }
> + for suite in &repo.suites {
> + let suite = match suite.find(&['-', '/'][..]) {
> + Some(n) => &suite[0..n],
> + None => suite,
> + };
> +
> + if suite != OLD_SUITE && suite != NEW_SUITE {
> + let location = repo_file.path.clone().unwrap_or_default();
> + self.output.log_notice(format!(
> + "found unusual suite '{suite}', neighter old '{OLD_SUITE}' nor new \
typo: s/neighter/neither/
next prev parent reply other threads:[~2023-06-28 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:53 Christian Ebner
2023-06-28 12:17 ` Fiona Ebner [this message]
2023-06-28 15:06 ` [pbs-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27cc8bfe-c42d-6e20-ce3c-2fb561cefd44@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox