Skip to contentSkip to conversation

apt-native: don't let dpkg overwrite files by default

PATCH Jan Luebbe 1 participant 1 message Apr 27, 2020 1 message not in the archive

lore
Share & tools
lore

Jan Luebbe

author
#1 lore raw
In reply to a message not in the archive

Hi Armin and Anuj,

this fix has landed in master as 4292387ef6c4e80428bad6a07c844a288b27d9a1 and I'd like to request it to be cherry-picked for zeus. The cherry-pick should simply work without conflicts.

Thanks,
Jan

Quoted 30 lines · Jan Luebbe

With --force-overwrite (implied by --force-all), dpkg will not abort when a package overwrites files from different packages. As this can also lead to "The following package disappeared from your system as all files have been overwritten by other packages: <package>" and subsequently broken dependencies, this makes the simple case of conflicting files hard to debug.

Instead of finding all possibly required force options, only disable overwrite for now.

---
 meta/recipes-devtools/apt/files/apt.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes- renamed from meta/recipes-devtools/apt/files/apt.conf +0 -0

devtools/apt/files/apt.conf
index 03351356bc01..c95a5b07af54 100644

meta/recipes-devtools/apt/files/apt.conf +1 -3
@@ -39,4 +39,4 @@ APT
   };
 };
 
-DPkg::Options {"--root=#ROOTFS#";"
--admindir=#ROOTFS#/var/lib/dpkg";"--force-all";"--no-debsig"};
+DPkg::Options {"--root=#ROOTFS#";"
--admindir=#ROOTFS#/var/lib/dpkg";"--force-all";"--no-force-

overwrite";"--no-debsig"};