curtin-dev team mailing list archive

Thread
Date

Re: [Merge] ~dbungert/curtin:skip-if-installed into curtin:master

To: mp+469605@xxxxxxxxxxxxxxxxxx
From: Dan Bungert <mp+469605@xxxxxxxxxxxxxxxxxx>
Date: Tue, 23 Jul 2024 00:22:13 -0000
In-reply-to: <172134026250.171436.17020628116003990419.launchpad@scripts-bzrsyncd.lp.internal>
Reply-to: mp+469605@xxxxxxxxxxxxxxxxxx
Sender: noreply@xxxxxxxxxxxxx

> I was a bit worried that this would change behaviour for the case that we have an old generic kernel in the base layer and a new one in the archive, but I guess the unattended-upgrade would get that case?

I believe that is correct.  However, with the updated approach I have planned for https://github.com/canonical/subiquity/pull/2034 I'm not sure I need this MP.
-- 
https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/469605
Your team curtin developers is requested to review the proposed merge of ~dbungert/curtin:skip-if-installed into curtin:master.

References

[Merge] ~dbungert/curtin:skip-if-installed into curtin:master
From: Dan Bungert, 2024-07-18