[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1030394: reassign bug to correct package



Nicholas D Steeves wrote:

> 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.

Before the upgrade to bookworm I was running an almost pure bullseye.
The exception were a few elpa packages from bookworm (i.e. then
testing).  We can try to reconstruct the list of these package from the
output of the following command:

  zgrep -h ' elpa-' /var/log/dpkg.log* | grep ' upgrade '

2023-07-20 20:31:46 upgrade elpa-adaptive-wrap:all 0.8-1 0.8-3
2023-07-20 20:31:46 upgrade elpa-websocket:all 1.13-1 1.13-3
2023-07-20 20:31:47 upgrade elpa-atomic-chrome:all 2.0.0-2 2.0.0-4
2023-07-20 20:31:47 upgrade elpa-dash:all 2.19.1+dfsg-1 2.19.1+git20220608.1.0ac1ecf+dfsg-1
2023-07-20 20:31:47 upgrade elpa-emacsql:all 3.0.0+ds-2 3.1.1+ds-1
2023-07-20 20:31:48 upgrade elpa-git-commit:all 3.3.0-1 3.3.0-2
2023-07-20 20:31:48 upgrade elpa-htmlize:all 1.55-1 1.56-1
2023-07-20 20:31:49 upgrade elpa-magit-section:all 3.3.0-1 3.3.0-2
2023-07-20 20:31:49 upgrade elpa-magit:all 3.3.0-1 3.3.0-2
2023-07-20 20:31:50 upgrade elpa-markdown-mode:all 2.4-1 2.5-1
2023-07-20 20:31:51 upgrade elpa-notmuch:all 0.31.4-2 0.37-1
2023-07-20 20:31:52 upgrade elpa-org:all 9.4.0+dfsg-1 9.5.2+dfsh-5
2023-07-20 20:31:52 upgrade elpa-transient:all 0.3.6-2 0.3.7-1
2023-07-20 20:31:53 upgrade elpa-yaml-mode:all 0.0.15-1 0.0.15-2
2023-07-20 21:19:26 upgrade elpa-emacsql-sqlite:amd64 3.0.0+ds-2 3.1.1+ds-1

(The main upgrade from bullseye to bookworm occurred around 20:30.)

Comparing the left versions in the log to the ones in bullseye one can
see that at least the following packages were from testing:

elpa-dash
elpa-git-commit
elpa-magit-section
elpa-magit
elpa-transient

To this list one should add elpa-org-roam which did not require an
upgrade during the bullseye -> bookworm transition and perhaps other
elpa packages that I lost track of.

> 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 do not remember ever installing dh-elpa from any source, nor can
I find any trace of it in the logs.

Attachment: signature.asc
Description: PGP signature


Reply to: