Hi Frederic-Emmanuel, picca <pi...@debian.org> writes:
> "Debian Bug Tracking System" <ow...@bugs.debian.org> writes: > > It seems that I found the culprite. > > on the working machine > > $ ls > company-1.0.2 compat-30.1.0.0 debian-el-37.19 dpkg-dev-el-37.19 > haskell-mode-17.5 htmlize-1.58 llama-0.6.2 magit-4.3.5 > magit-section-4.3.5 notmuch-0.39 transient-0.8.8 with-editor-3.4.3 > > on the non working machine > > # ls > company-0.9.13 dash-2.19.1 debian-el-37.19 dpkg-dev-el-37.19 > flycheck-35.0 ht-2.3 llama-0.6.2 lv-0.15.0 > magit-section-3.3.0 notmuch-0.39 spinner-1.7.4 > with-editor-3.4.3 company-1.0.2 dash-2.20.0 devscripts-40 f-0.21.0 > > haskell-mode-17.2snapshot > > htmlize-1.56 lsp-haskell-1.0 > magit-4.3.3 magit-section-4.3.3 powerline-2.4 transient-0.8.8 > compat-30.1.0.0 debian-el-37 dpkg-dev-el-37.0 > > flycheck-32snapshot > > haskell-mode-17.5 htmlize-1.58 lsp-mode-9.0.0 magit-popup-2.13.3 > markdown-mode-2.7 s-1.13.0 with-editor-3.0.5 > > > look at these snapshot directory... > > what is the best way to clean this properly ? > > Fred > Ah, this finding seems to have proved my conjecture. Even though in my test it doesn't actually caused the issue you were experiencing, those lingering files would be problematic anyway. In my test, this only happens when you run `apt upgrade' (with or without `--without-new-pkgs'), but not for `apt dist-upgrade'. Can you confirm which command you used for upgrading? For the testing purpose, I'd like to ask for a favor: can you try to move them out (e.g. to /tmp) and try to reproduce; and then move them back and retry to reproduce? This can help confirm that it was those lingering directories that was causing the issues for you. Thanks! -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
