public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v3] deb-dl-dir: Fallback to copying when import-export
Date: Mon, 13 Feb 2023 08:44:39 +0100	[thread overview]
Message-ID: <20230213074439.23410-1-ubely@ilbers.de> (raw)

By default, hardlinks are used when doing DL_DIR import and export.
This fails if DL_DIR's filesystem differs from TMPDIR's one.

Fallback to file copying (with lower performance and huge disk usage)
in this case.

Also rework sudo using when import/export by preferring "sudo/while"
approach instead of "while/sudo" (less spam in system logs).

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/classes/deb-dl-dir.bbclass | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

Changes since v2:
 - Reworked sudo usage approach from "while/sudo" to "sudo/while".

Changes since v1:
 - Try create handrlink first and then copy if failed. It should better
handle hardlink issues that may happen even on the same partition.

diff --git a/meta/classes/deb-dl-dir.bbclass b/meta/classes/deb-dl-dir.bbclass
index 7db25251..ca2a1ee2 100644
--- a/meta/classes/deb-dl-dir.bbclass
+++ b/meta/classes/deb-dl-dir.bbclass
@@ -81,20 +81,24 @@ deb_dl_dir_import() {
     export rootfs="${1}"
     sudo mkdir -p "${rootfs}"/var/cache/apt/archives/
     [ ! -d "${pc}" ] && return 0
-    flock -s "${pc}".lock -c '
+    flock -s "${pc}".lock sudo -Es << 'EOSUDO'
         set -e
         printenv | grep -q BB_VERBOSE_LOGS && set -x
 
-        sudo find "${pc}" -type f -iname "*\.deb" -exec \
-            ln -Pf -t "${rootfs}"/var/cache/apt/archives/ {} +
-    '
+        find "${pc}" -type f -iname "*\.deb" |\
+        while read p; do
+            ln -Pf -t "${rootfs}"/var/cache/apt/archives/ "$p" 2>/dev/null ||
+                cp -n --no-preserve=owner -t "${rootfs}"/var/cache/apt/archives/ "$p"
+        done
+EOSUDO
 }
 
 deb_dl_dir_export() {
     export pc="${DEBDIR}/${2}"
     export rootfs="${1}"
+    export owner=$(id -u):$(id -g)
     mkdir -p "${pc}"
-    flock "${pc}".lock -c '
+    flock "${pc}".lock sudo -Es << 'EOSUDO'
         set -e
         printenv | grep -q BB_VERBOSE_LOGS && set -x
 
@@ -109,8 +113,9 @@ deb_dl_dir_export() {
             if [ -n "$package" ]; then
                 cmp --silent "$package" "$p" && continue
             fi
-            sudo ln -Pf "${p}" "${pc}"
+            ln -Pf "${p}" "${pc}" 2>/dev/null ||
+                cp -n "${p}" "${pc}"
         done
-        sudo chown -R $(id -u):$(id -g) "${pc}"
-    '
+        chown -R ${owner} "${pc}"
+EOSUDO
 }
-- 
2.20.1


             reply	other threads:[~2023-02-13  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:44 Uladzimir Bely [this message]
2023-02-16  4:44 ` Uladzimir Bely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230213074439.23410-1-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox