Control: severity -1 serious Yasuhiro Kimura <y...@utahime.org> writes:
> Package: elpa-magit > Version: 4.1.2-1 > Severity: normal > > Dear Maintainer, > > After elp-magit is updated 4.1.2-1, it doesn't depend on elpa-git-commit > any more. If I uninstall the latter, however, then the error as below > happens when I start Magit with `M-x magit` > > Cannot open load file: No such file or directory, git-commit > > And it is fixed by installing elpa-git-commit again. So it seems > elpa-magit still requires elpa-git-commit. > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.11.5-amd64 (SMP w/4 CPU threads; PREEMPT) > Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages elpa-magit depends on: > ii dh-elpa-helper 2.1.5 > ii elpa-compat 30.0.0.0+dfsg-3 > ii elpa-dash 2.19.1+git20220608.1.0ac1ecf+dfsg-3 > ii elpa-magit-section 4.1.2-1 > ii elpa-seq 2.24-2 > ii elpa-transient 0.7.8-1 > ii elpa-with-editor 3.4.2-1 > ii emacsen-common 3.0.5 > ii git 1:2.45.2-1.1 > > elpa-magit recommends no packages. > > elpa-magit suggests no packages. > > -- no debconf information > It looks like git-commit has become part of magit since version 4.1.0[1]. We may need to rework packaging and make elpa-git-commit a transition package that depends on newer version of elpa-magit. Will try to work on the fix. [1] https://github.com/magit/magit/commit/c170fcf39918e567948fec43b70a592765ed5fe7 -- Regards, Xiyue Deng
signature.asc
Description: PGP signature