Bug#1111039: Upgrading a system installed with Debian live from Bookworm to Trixie does not change /etc/os-release due to dpkg diversion
On Thu, 14 Aug 2025 at 09:30, Luca Boccassi <bluca@debian.org> wrote:
>
> On Thu, 14 Aug 2025 at 07:15, Johannes Schauer Marin Rodrigues
> <josch@debian.org> wrote:
> >
> > Hi,
> >
> > On Wed, 13 Aug 2025 22:03:37 +0100 Luca Boccassi <bluca@debian.org> wrote:
> > > This was meant to be applied only in the read-only portion of the live
> > > image filesystem, as it contains image IDs that makes sense for an
> > > immutable image to identify it, but not for an upgradable rootfs. If it
> > > gets copied to an installed disk then something went wrong somewhere
> > > and yeah it should be fixed.
> > >
> > > I am not really familiar with calamares so not surprised I missed it,
> > > if you know what to do would you be able to send a MR on Salsa to fix it
> > > please?
> >
> > I wonder about the rationale of the diversion. Is this to guard against
> > upgrades of base-files that happen *during* image creation?
> >
> > If the diversion is somehow useful during image creation, the easiest fix might
> > be to just remove the diversion at the end of the image creation process. If
> > the diversion does not end up in the live system, then calamares cannot copy it
> > over.
>
> Yes that's exactly it, so yes what you propose should be just fine.
Actually not quite enough: the local copy with IMAGE_ID et al. also
needs to be deleted by the installer and replaced with a symlink when
copying to a persistent, writable rootfs as well. Is that code that
copies the rootfs in live-build or elsewhere?
Reply to: