* Russ Allbery <rra@debian.org> [2021-11-19 11:46]:
I also don't understand why this isn't the correct solution. It seems obvious to me that we should simply teach dpkg about path aliases and have it update both its internal state and its processing of new packages to canonicalize paths so that it has an accurate representation of the world, and then ensure dpkg is upgraded first.
+1
Are we missing something? If not, what is blocking this solution? Is it simply a matter of someone digging into dpkg's code sufficiently to put these changes in the correct location? Or is there some other issue?
AFAIR, Guillem has not commented on the solution when it was brought up on d-devel [1], so I'm not sure if he would accept patches, let alone support anyone working on this. I'd be willing to assist him and contribute code, but I'm not going to spend a good chunk of my spare time just to see me work summarily rejected. Cheers Timo [1] https://lists.debian.org/debian-devel/2021/08/msg00438.html -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
Attachment:
signature.asc
Description: PGP signature