On Wed, Mar 17, 2021 at 4:56 PM Ryan Harper <1918...@bugs.launchpad.net> wrote: > > I still don't understand: > > 1) why does which not find flash-kernel if it's present in the ephemeral > image (meaning it will also be present in the target filesystem > 2) What is the problem with flash-kernel such that you need to dpkg-divert it? > > Generally, we do not want to include paths to binaries; we install > Ubuntu and Centos, and possibly other distros which may not have the > same path to this tools so I would like to understand what's not working > to understand why we're hardcoding paths to binaries for dpkg-divert.
In my POC patch, it is because we need to divert flash-kernel before it is installed, *just in case* it gets installed as a dependency of some other package (in our case it happened due to a kernel Recommends relationship). We therefore can't use `which` to look up the path... unless we continue to always install f-k in the ephemeral for the sole purpose of looking up its path... but that seems to making assumptions as well - i.e. that the ephemeral OS has the same paths as the target OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
