Bug#1040787: Bug#1040690: reassign bug to correct package
On Fri, 21 Jul 2023 at 23:39, Nicholas D Steeves <sten@debian.org> wrote:
> retitle 1030394 dh-elpa: elpa-csv-mode 1.20 not cleaned up
important to note that it's not just this one package, but many elpa
packages (but not all) which were either upgraded or purged as part of
the upgrade: I get the same set of warnings on two separate systems.
(I have elpa-csv-mode and no issue, but i don't know if i had it
installed in bullseye)
Warnings i have:
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/helpful-0.18/helpful.elc
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/elisp-refs-1.3/elisp-refs.elc
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/dash-2.17.0/dash.elc
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/loop-1.3/loop.elc
Warning (comp): Cannot look-up eln file as no source file was found
for /usr/share/emacs/site-lisp/elpa/dash-functional-1.2.0/
But i also have duplicate subdirectories in
/usr/share/emacs/site-lisp/elpa for dash,elisp-refs,git-commit,
helpful, magit and with-editor
Lots of broken symlinks, eg
/usr/share/emacs/site-lisp/elpa/transient-0.2.0.30 has
transient-autoloads.el ->
/usr/share/emacs/site-lisp/elpa-src/transient-0.2.0.30//transient-autoloads.el
which doesnt exist
Lots of 'empty' (32-byte) Install.log.gz files such as
/usr/share/emacs/site-lisp/elpa/rainbow-delimiters-2.1.5/Install.log.gz
-- which unzul to an empty file
Current versions of packages
elpa-helpful:all/bookworm 0.19-2 uptodate
elpa-elisp-refs:all/bookworm 1.4-1 uptodate
elpa-dash:all/bookworm 2.19.1+git20220608.1.0ac1ecf+dfsg-1 uptodate
elpa-loop:all not installed # was installed as a recommends of
something in bullseye i assume
elpa-csv-mode:all/bookworm 1.22-1 uptodate # i dont know if i had this
via dependencies in bullseye
> To all affected users: Do you remember if you ever manually installed an
> affected elpa-package from sid/unstable or from testing? I'm curious if
> this might be part of the trigger condition. Likewise, do you remember
> if you installed dh-elpa from backports? While I think both of these
> cases are unlikely to have caused problems, one might as well be
> thorough!
I have never installed anything emacs-related from anywhere other than stable.
All systems have only run stable, and have been upgraded from stable
to stable (from stretch i think).
While I havn't tried to make it reproducible, i did reproduce it in
the sense that two separate systems which had the same set of
emacs-related packages installed ended up with the same warnings. I
have the upgrade log for one - are there bits that are helpful to look
at - i didnt see anything complain, but the new emacs and new dh-elpa
were unpacked before the other elpa- packages (i think)
I can see dh-elpa tried to purge the old files, but presumably this
did not actualy work, although there is no error message:
dh-elpa: purging flavor specific files for emacs^M
Remove elpa-helpful for emacs^M
remove/helpful-0.19: Handling removal of emacsen flavor emacs^M
dh-elpa: purging flavor specific files for emacs^M
(i was surprised it says removing 0.19 not 0.18 but all the other elpa
packages have the new version here too.
this bit came after new emacs and dh-elpa were unpacked but before
they were 'Set up' (configured?))
Later there is some tsort issue,
Setting up elpa-helpful (0.19-2) ...^M
tsort: -: input contains a loop:^M
tsort: elpa-dash^M
tsort: emacsen-common^M
tsort: -: input contains a loop:^M
tsort: emacsen-common^M
tsort: elpa-s^M
My emacs-related packages: all would have been at the previous
bullseye point-release/security upgrade before upgrading:
emacs-gtk, emacs-el
emacs-common-non-dfsg, emacs-goodies-el, bbdb3, elpa-debian-el,
elpa-dpkg-dev-el, elpa-org, elpa-org-bullets, elpa-company,
elpa-dumb-jump, elpa-flycheck, elpa-helpful, elpa-systemd,
elpa-magit, elpa-ag, elpa-rainbow-delimiters, elpa-rich-minority
(Plus all recommends. And a couple of locally packaged variants -
which were not changed on upgrade but did use dh-elpa).
I used aptitude to upgrade to bookworm, and set anything removed to be purged.
Reply to: