Your message dated Tue, 05 May 2026 03:33:57 +0000
with message-id <[email protected]>
and subject line Bug#1127102: fixed in emacs 1:30.2+1-3
has caused the Debian Bug report #1127102,
regarding emacs-common: odd behaviour around /usr/local in postinst
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127102
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs-common
Version: 1:30.2+1-2
Severity: normal
User: [email protected]
Usertags: dh-usrlocal
Prompted by recent changes in fontconfig's handling of
/usr/local/share/fonts, I noticed that emacs-common's postinst has some
open-coded script to create directories below /usr/local/share/, with
non-Policy-compliant permissions (unconditionally root:staff, instead of
preferring root:root).
This is mitigated by the fact that it doesn't actually seem to work as
intended: on a first installation, /usr/local/share/emacs doesn't yet
exist, and therefore /usr/local/share/emacs/30.2 isn't created below it
with the wrong permissions. There is probably some sequence of events
that would result in /usr/local/share/emacs/30.2 being created as
root:staff, but I couldn't work out what it is!
Please consider using dh_usrlocal(1) for this, as is already done for
/usr/local/share/emacs/site-lisp: that way, any implementation bugs can
be fixed centrally in debhelper, and they will take effect in all
packages that use dh_usrlocal at the next rebuild.
The procedure to do that would be something like:
1. create debian/emacs-common/usr/local/share/emacs/VERSION/site-lisp,
for example with some `install -d` in d/rules
2. remove open-coded logic in maintainer scripts to create and remove
the various /usr/local directories, relying on dh_usrlocal to do it
Or if /usr/local/share/emacs/VERSION/site-lisp isn't necessary in
practice, perhaps emacs-common could just not create it?
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:30.2+1-3
Done: Rob Browning <[email protected]>
We believe that the bug you reported is fixed in the latest version of
emacs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rob Browning <[email protected]> (supplier of updated emacs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 04 May 2026 18:20:35 -0500
Source: emacs
Architecture: source
Version: 1:30.2+1-3
Distribution: unstable
Urgency: high
Maintainer: Rob Browning <[email protected]>
Changed-By: Rob Browning <[email protected]>
Closes: 1127102 1129189 1134692
Changes:
emacs (1:30.2+1-3) unstable; urgency=high
.
[ Sean Whitton ]
* Remove myself from Uploaders.
.
[ Arto Jantunen ]
* Handle /usr/local/ via dh_usrlocal. Thanks to Simon McVittie for
reporting the issue. (Closes: #1127102)
.
[ Rob Browning ]
* Fix an SVG-related vulnerability (CVE-2026-6861)
Add 0025-src-image.c-svg_load_image-Fix-off-by-one-mistake-bu.patch
which includes the upstream patch to fix the problem.
Thanks to Salvatore Bonaccorso for reporting the issue. (Closes: 1134692)
* Don't run bytecomp-tests--dest-mountpoint where bwrap doesn't work.
Add 0026-bytecomp-tests-dest-mountpoint-only-run-test-if-bwra.patch to
address the issue. Thanks to Santiago Vila for reporting the
issue. (Closes: 1129189)
Checksums-Sha1:
79fcaf9b819de5749207b49c715f40fb50e0c729 2951 emacs_30.2+1-3.dsc
abf2ddeda340b0df72c16bfdac335d40fbccb8c0 73020 emacs_30.2+1-3.debian.tar.xz
e497c827a59aee69165c46cd3837256b5c7380a2 21682 emacs_30.2+1-3_amd64.buildinfo
Checksums-Sha256:
6abcb5fa90208b8d92973fa29f3f2f2461a5d3ac9852321710cc14683a361050 2951
emacs_30.2+1-3.dsc
581175f117c809648fe3054579ed04af1052c999ab3d7d763c7530dace49fb67 73020
emacs_30.2+1-3.debian.tar.xz
e8e10401e6be2cfdfb6288eda8015b7efb483870e1f2aa86449ff1a5ec27f4a8 21682
emacs_30.2+1-3_amd64.buildinfo
Files:
98063fd59c5e435f917ebdd05e791d9d 2951 editors optional emacs_30.2+1-3.dsc
f0b702bbea861e202cd6a3692822c4b0 73020 editors optional
emacs_30.2+1-3.debian.tar.xz
30072804b3c41622287bb9d7aef8d979 21682 editors optional
emacs_30.2+1-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCgAzFiEEPTFSABe5ruOuhW+97vEWxVpaQvEFAmn5YkAVHHJsYkBkZWZh
dWx0dmFsdWUub3JnAAoJEO7xFsVaWkLxMT4QAIVRiYw365soZRwU6a4WvNVQGr6k
DM2RDwBYp8nAe8krmJCF4QM9Es8+A2w+YSHnY0JrSoL2+qUI6vcvSNV76ECyAzed
U4OaIhkJ1TCp4ZkEgz9ZGxLZKUtIjmVMbcnDJWOerWUbIzfvqeq/rJso84r+0QoF
feTqEdtkRwydK8ta1Ktmzvi9txYjr8LM0nrG+0MJQy0wgyIUrzkU1/ZKRsQUP1Sq
PnK0/71eA+7G95zCUTbYDQJYNQbtMUoYP07VMg8Cmfr4FTugzUCF6mpBcuVbAUY7
JhOUIzuE9nq+PLklGowXxLxmE0Bc10xze3Dyg3Z2VVo1RvUnevDZ6+ktNPrjK1f/
R0O4EpAdXj3CZIeV8tuTvZQkSeYGmUt9gE5sM35UO7VW5mPh9wMlTYCeJn/IEuZ8
gknVHpI4nNWNP99PdmyX91/s7fy0n0TtgyM530u8K9+2BR7N1kFmmbfky9ArxsAh
0JKKrjjkWDTz6boXtev6B162s4hKWtZUzwsILdeO3WXiOg8H6CjjBK8+q4ygIdS1
ZQlj1e9FplvIt9e5zAatQ7+cfE3RGNXPRZYyvEGWTyMfIVW6CGyKm3m1e9Gk2rqs
Fo6z5W6+uomrIjrhieMRnEhFaiQgV5PVR6yBekmkzA2XPv3XsbkPx9s6N3kzdyxS
m64EA0ghdUjYe31A
=a/9j
-----END PGP SIGNATURE-----
pgpGqmwKu89GR.pgp
Description: PGP signature
--- End Message ---
