1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1099205: elpa-magit: Error Symbol's value as variable is void: magi

    From =?ISO-8859-1?Q?S=E9bastien?= Villem@21:1/5 to olivier.berger@telecom-sudparis.eu on Wed Mar 12 16:40:01 2025
    XPost: linux.debian.maint.emacsen

    On Sat, 1 Mar 2025 18:28:29 +0100 Olivier Berger <olivier.berger@telecom-sudparis.eu> wrote:
    Package: elpa-magit
    Version: 4.3.0-1
    Severity: normal

    If I'm not mistaken, there's now an issue with magit 4.3.0 running
    Emacs 30.1 in testing.

    Issueing M-x magit-status after Emacs has started, from a directory
    containing a git checkout of a repo, I get an error about magit-commit-
    absorb

    The Messages buffer reports :
    require: Symbol’s value as variable is void: magit-commit-absorb

    I also experience this issue.

    It seems that reinstall the elpa-magit package or deleting native-
    compiled files under ~/.config/emacs/eln-cache helps, because the error disappears just after that, but it comes back later after Emacs has
    been restarted.

    Also I manage to reproduce the problem by running “emacs -q” and then
    just “(require 'magit)”.

    --
    ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
    ⣾⠁⢠⠒⠀⣿⡁  Debian Developer ⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmfRqQEACgkQLOzpNQ7O vkr96w//RWIdr/PwB4NdjgTDOLXpnVDs6AoASDrI4F1sJInGisJfRbff62x167bU /khz/RPermshhq/wNmig6wTxoBxiKfuQC8/oxaI7Jq+LUPdpv9B0wPDlBrGxWgCA IVVjju5cFWzJd0hkrMxnD3fd8zdbK3RupMRgryL7+FS3G1s/wvhFkIYAOfYu/L9S WdJ0L6MiZZ9CnOs2kXsa6I7TYxcqh3OQOGsBRWmgQ6+jLY8iqrzKpEjbcQoy03AP X6se3hsLAU4LQ9VZ7FM4dZ6C/Lm6jIwCq2OzDYctMPc+825Jzlrp/RuF1Q/EJKGy 0iaOQA6kvECDQeMfZlCZuWl5iYplAZIfYLZUB43CQpG2TddlDhTsH/LRyo3LGvHb +ZklM2eQYleSooTAYd9ukbFjg11G3mgRxH4nobbYe0GZFSPMOPK6JQVxctNTAwlw exvM37Df5KzlTcDj1IViuBOWkoS6BF9/8SyJqeQoo9ePAcpQUK+iJ6r3/7+XSQzt rj7MNx/uvnXgaddTnuYClWG4G7VjTYgTNufcXzrhomwRcvvB3xk0Alse+EKPLDcn LSxYJCPGa7Gi1wRHqi3eLiFc8t6bTStCYkxpTcPEnelAdD737f5X1iqjj9DjyjRt yySouUqzxuMLPv7KdZH6LBrxMFcCZI7poHK96peYCD9KIdMvGzs=
    =RdTv
    -
  • From =?ISO-8859-1?Q?S=E9bastien?= Villem@21:1/5 to All on Wed Mar 12 17:00:01 2025
    XPost: linux.debian.maint.emacsen

    Le mercredi 12 mars 2025 à 16:32 +0100, Sébastien Villemot a écrit :
    On Sat, 1 Mar 2025 18:28:29 +0100 Olivier Berger <olivier.berger@telecom-sudparis.eu> wrote:
    Package: elpa-magit
    Version: 4.3.0-1
    Severity: normal

    If I'm not mistaken, there's now an issue with magit 4.3.0 running
    Emacs 30.1 in testing.

    Issueing M-x magit-status after Emacs has started, from a directory containing a git checkout of a repo, I get an error about magit-commit- absorb

    The Messages buffer reports :
    require: Symbol’s value as variable is void: magit-commit-absorb

    I also experience this issue.

    I think I found the cause of the problem. There was an old bytecode-
    compiled version of transient under /usr/share/emacs/site- lisp/elpa/transient-0.3.7/

    I removed that directory, then also removed ~/.config/emacs/eln-cache/,
    and everything seems to be working fine again.

    So ultimately this may be a bug in elpa-transient. It would be useful
    to test a clean upgrade from bookworm to trixie to see whether this is reproducible.

    --
    ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
    ⣾⠁⢠⠒⠀⣿⡁  Debian Developer ⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀  https://www.debian.org

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmfRrJ4ACgkQLOzpNQ7O vkrB7w/9FSUDSloWkOzdf5mN8EPbigPNWklFD42d/XzW3Xsd6XZthdov2KoNP0uS CVaeNnCSmr03Tlss2EX+aKa02iMbENNXiu9uvNdDs6s/funnm4O2EyMOSsh2uGQg WxV/BnAq39vByiv3/m64VGzknLpxuFhnzc79i29DYYzgGwse+NljDl/nAH170Zc7 Fk2at1OOglkSjW97Cyv2UbpoTk957ASYV00RZpCGiwQ0s/JY+rscaMleBMc6dF1S Vv6Fc9yq4ZUmAbz+4P2RcJAbNQvK7RmzfoVQGhawFgV8quIy5k+sVUVpn72TOg0J RJ/AwSTCoM59a2EnIqK0K7YZgGfQ/pTS4PK63pMm+iOsn0BMc0dGMsI60Jr77sup aB4XJvD//5ea4vmHC8587ElQMLo0WN0GOyBeL7EUPTNz6QBvS3YIztz3DuzTQjhx xYXxacYg5RZ/pC6GeGQ/tRGLHj4Ea49BcLwtdjAa+ra7UJJeJZ5dgxxeTh6fGA9p sV2qnVb2t4EmR9xPJIsTX9OoMb+a3QTQapTBQu9IAPlbgrz4gd0fIMLnr8PA6Wf7 9ZFA+zV2kQxznF4V9bpXbzDTS6uAG3AfUV2VjP4omp6hTOjuJggHA9K1v3bImCF2 p5aIDD66BRDtikkPTWwup78F6LjqQWJ+cxXE3wgku4jPrj1rJK8=
    =6p2J
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sean Whitton@21:1/5 to Xiyue Deng on Fri Mar 14 09:10:01 2025
    XPost: linux.debian.maint.emacsen

    Hello,

    On Wed 12 Mar 2025 at 11:18am -07, Xiyue Deng wrote:

    This sounds like the upgrade issue that Rob, David, and Sean has been
    trying to address in dh-elpa 2.1.0 and later. transient 0.3.7 is from Bookworm, so I think this could probably happen when transient was
    upgraded with dh-elpa <2.1.0.

    Yeah, it's probably this one.

    --
    Sean Whitton

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmfT4koZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQL+vEACAYNIMN0aw4BcDF7Ur3oaD Dv05yu7Vx/DzwjW58aLe0f919gHzMszhzbsqXSqEwSSp/+y30kf04kpl0poYRhsl QbDw/S+32Wb9yaBZutxGfMUd3NCgcdteLlXu+uavmMnO6wENaTIX4N+kieHdSRwL nyurPV9LV9MEzCYZBzV1HTtIWdebPoi+oJneLT6f5/E2XBHOsDc72okMzyKcuA+N 8ZLuCdE/pI87+Y8y7wI4KmsnAic4L/iixcKHAD4aXt7XoQtcAi0DhSq18q+wixqj XWk9M0WIYD/GWZd48larjC5Y8OR4vMMTnb6q182mTBH6I+vbyMRFkjEkVhI88vRo ZQgfoo05iW3B1mbj4J4pbuaiGxILYii3RjeFLWz5ulm9fB5WxXEt8PmnePihR/Ap nbyaIdkdvA+1fzeLPyDF5xdGJdO9uISIHU9KeTtR/tAqlgv92x12Xjzn8Pe8osPG xjzf/5CKg/SgKrYKpzpPaz9Kk7+NVRinAiq8mCPewawg3vwWBi+9U3YmfxPWHCbR dKJ5lem/9mbOyH0ahvbeT9vuDrkNEIs9YknYMQTbfhMf9qhK2XmYCq0f+gAmlXKC GgdKAUCqlb6Qsx+dj8lQc0zTSBXlfPYMj+S1YvnCRP2KIF0JsGKot+q1im4lKXCo Mqh7q6/eW8yO8sAwPWcB5g==OkmH
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Us