I have binpkgs enabled globally on my system and these two packages seem to be stuck built against Emacs 29.4, which is presumably the Emacs version that was present in the environment where these packages were compiled. Considering that the Emacs version these packages are compiled with is significant, packages such as these probably shouldn't be distributed as binpkgs at all.
We don't have a way to properly handle this right now. Some notes: 1. See bug 542480. 2. Users can do --buildpkg-exclude/--usepkg-exclude in EMERGE_DEFAULT_OPTS. 3. The incompatibility of Emacs bytecode _with the exception of JIT_ is actually not such a problem, it ends up being stable enough most of the time. 4. See the extensive discussion in bug 735148.
Please attach the output of this command: $ emacs-updater -b -- -pv
Created attachment 912868 [details] Output from running `emacs-updater -b -- -pv`
This should not happen. Maybe something in your configuration overrides --usepkg-n. Can you also attach the "emerge --info" output?
(In reply to Ulrich Müller from comment #4) > Can you also attach the "emerge --info" output? Sorry, this should have read "emerge --info app-admin/emacs-updater".
Created attachment 913012 [details] Output from running `emerge --info app-admin/emacs-updater`
(In reply to opensauce04 from comment #6) > Created attachment 913012 [details] > Output from running `emerge --info app-admin/emacs-updater` > EMERGE_DEFAULT_OPTS="--getbinpkg --binpkg-respect-use=y --binpkg-changed-deps=y --usepkg-exclude sys-apps/xdg-desktop-portal-gtk" emacs-updater does "emerge --usepkg=n --oneshot", and it looks like --usepkg=n doesn't override --getbinpkg from EMERGE_DEFAULT_OPTS. emerge(1) says: --getbinpkg [ y | n ], -g Using the server and location defined in PORTAGE_BINHOST (see make.conf(5)), portage will download the information from each binary package found and it will use that information to help build the dependency list. This option implies -k. (Use -gK for binary-only merging.) Since the -k option implies -k/--usepkg, I'd expect --usepkg=n in the command line to countermand it. CCing Portage team. Is this a Portage bug or a feature?
(In reply to Ulrich Müller from comment #7) > Since the -k option implies -k/--usepkg, ... This should of course read "Since the --getbinpkg option implies -k/--usepkg, ..."
https://gitweb.gentoo.org/proj/emacs-tools.git/commit/?h=emacs-updater&id=63e5e0fc544b5fdae32a2634996c868a1fe791a1 commit 63e5e0fc544b5fdae32a2634996c868a1fe791a1 Author: Ulrich Müller <ulm@gentoo.org> Date: Sat Dec 7 08:58:47 2024 +0100 Pass --getbinpkg=n to Portage * emacs-updater (pm_portage): Pass --getbinpkg=n to Portage. Fixes bug 945381. Bug: https://bugs.gentoo.org/945381 Signed-off-by: Ulrich Müller <ulm@gentoo.org>
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=43c1ad90cf8670eb8348773e2010e22da0604673 commit 43c1ad90cf8670eb8348773e2010e22da0604673 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2024-12-09 18:35:41 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2024-12-09 18:37:10 +0000 app-admin/emacs-updater: add 1.19 Closes: https://bugs.gentoo.org/945381 Signed-off-by: Ulrich Müller <ulm@gentoo.org> app-admin/emacs-updater/Manifest | 1 + app-admin/emacs-updater/emacs-updater-1.19.ebuild | 37 +++++++++++++++++++++++ 2 files changed, 38 insertions(+)
Thanks for reporting.
I emerged emacs-updater 1.19 and tried to run it, and it doesn't seem that this issue has been resolved. The behaviour appears identical to 1.18.
(In reply to opensauce04 from comment #12) > I emerged emacs-updater 1.19 and tried to run it, and it doesn't seem that > this issue has been resolved. The behaviour appears identical to 1.18. Try again with "getbinpkg" removed from your FEATURES.
That fixed it, not sure why I had both FEATURES and EMERGE_DEFAULT_OPTS set. I wonder why the behaviour is different. The [https://wiki.gentoo.org/wiki/Binary_package_guide](binary package guide) on the wiki states that it "equivalent" to just using --getbinpkg. This appears that in some way this is not the case.
Please ignore the horrible grammar and link fail in my previous comment, I somehow accidentally sent it before actually checking what I just wrote. For clarification, I am referring to the FEATURES value in that last sentence.
make.conf(5) says about FEATURES="getbinpkg": Force emerges to always try to fetch files from the PORTAGE_BINHOST. AFAICS there is no way to override this with a command line option. Presumably that wiki page shouldn't recommend setting it in FEATURES.
