folder in /var/cache/pacman/pkg
Good afternoon, I just discovered this folder /var/cache/pacman/pkg/download-LyI4Km/ with the following content: -rw-r--r-- 1 alpm alpm 34091008 5. Apr 07:49 calibre-8.0.1-3- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 62468096 5. Apr 07:49 electron34-34.5.0-2- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 19755008 2. Apr 21:00 mesa-1:25.0.3-1- x86_64.pkg.tar.zst -rw-r--r-- 1 alpm alpm 60813312 5. Apr 07:49 qt6-webengine-6.9.0-1- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 37257216 5. Apr 07:49 telegram-desktop-5.13.1- 2-x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 106354016 5. Apr 01:17 zen-browser-bin-1.11b-2- x86_64.pkg.tar.zst -rw-r--r-- 1 alpm alpm 566 5. Apr 01:17 zen-browser-bin-1.11b-2- x86_64.pkg.tar.zst.sig Don't know where this is coming from but am wondering whether it's safe to delete it? THX Frank
Hi, for me this looks as the remains from an interrupted package update. Everything below /var/cache/pacman/pkg is save to delete as long as no pacman process is currently running. You could even automate that by running "paccache -rk2" after a system update to only keep the latest 2 versions of the downloaded / installed packages. Regards, Uwe Am 31.07.25 um 14:26 schrieb Frank:
Good afternoon,
I just discovered this folder /var/cache/pacman/pkg/download-LyI4Km/ with the following content: -rw-r--r-- 1 alpm alpm 34091008 5. Apr 07:49 calibre-8.0.1-3- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 62468096 5. Apr 07:49 electron34-34.5.0-2- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 19755008 2. Apr 21:00 mesa-1:25.0.3-1- x86_64.pkg.tar.zst -rw-r--r-- 1 alpm alpm 60813312 5. Apr 07:49 qt6-webengine-6.9.0-1- x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 37257216 5. Apr 07:49 telegram-desktop-5.13.1- 2-x86_64.pkg.tar.zst.part -rw-r--r-- 1 alpm alpm 106354016 5. Apr 01:17 zen-browser-bin-1.11b-2- x86_64.pkg.tar.zst -rw-r--r-- 1 alpm alpm 566 5. Apr 01:17 zen-browser-bin-1.11b-2- x86_64.pkg.tar.zst.sig
Don't know where this is coming from but am wondering whether it's safe to delete it?
THX Frank
Am Donnerstag, dem 31.07.2025 um 14:50 +0200 schrieb Uwe Sauter:
Hi,
for me this looks as the remains from an interrupted package update.
Everything below /var/cache/pacman/pkg is save to delete as long as no pacman process is currently running.
ok willremove
You could even automate that by running "paccache -rk2" after a system update to only keep the latest 2 versions of the downloaded / installed packages.
paccache does not delete any folders under /var/cache/pacman/pkg
Regards Frank
On 7/31/25 5:40 PM, Frank wrote:
Am Donnerstag, dem 31.07.2025 um 14:50 +0200 schrieb Uwe Sauter:
Hi,
for me this looks as the remains from an interrupted package update.
Everything below /var/cache/pacman/pkg is save to delete as long as no pacman process is currently running.
ok willremove
You could even automate that by running "paccache -rk2" after a system update to only keep the latest 2 versions of the downloaded / installed packages.
paccache does not delete any folders under /var/cache/pacman/pkg
I think that's normal, given that directories such as download-* are present only if the package download got interrupted (they therefore contain temporary files and not valid cached packages). I usually remove these directories manually. -- Sincerely, Camelia Lavender (she/they) PGP: 0xDBCC70EFBC360E97
Camelia Lavender <cam@camelia.dev> wrote:
On 7/31/25 5:40 PM, Frank wrote:
Am Donnerstag, dem 31.07.2025 um 14:50 +0200 schrieb Uwe Sauter:
Hi,
for me this looks as the remains from an interrupted package update.
Everything below /var/cache/pacman/pkg is save to delete as long as no pacman process is currently running.
ok willremove
You could even automate that by running "paccache -rk2" after a system update to only keep the latest 2 versions of the downloaded / installed packages.
paccache does not delete any folders under /var/cache/pacman/pkg
I think that's normal, given that directories such as download-* are present only if the package download got interrupted (they therefore contain temporary files and not valid cached packages).
If the whole package file was downloaded before the process was interrupted then it is probably a valid package. They are valid package files if they were downloaded in full, and also the sig files verifies them. When downloading an update that conatins many packages, try to $ watch ls /var/cache/pacman/pkg/download-* -- u34
I usually remove these directories manually.
-- Sincerely,
Camelia Lavender (she/they) PGP: 0xDBCC70EFBC360E97
Uwe Sauter <uwe.sauter.de@gmail.com> on Thu, 2025/07/31 14:50:
for me this looks as the remains from an interrupted package update.
It is. And I think this commit will fix the situation: https://gitlab.archlinux.org/pacman/pacman/-/commit/45c4eef61de33bcdf3efcc2e... Wondering when we will see another pacman release... This (and others) would be worth having packaged. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
participants (5)
-
Camelia Lavender
-
Christian Hesse
-
Frank
-
u34＠net9.cf
-
Uwe Sauter