Your message dated Sun, 21 May 2023 02:26:43 +0200
with message-id <[email protected]>
and subject line Re: Bug#677834: writes to /usr/share/jed/lib during postinst
has caused the Debian Bug report #677834,
regarding writes to /usr/share/jed/lib during 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.)
--
677834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677834
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jed-common
Version: 1:0.99.19-2.1
Severity: normal
I am not sure whether this is a policy violation, but it is most
probably a surprise for most users. In Debian I expect all files under
/usr to come from packages, and thus be static. This is not the case
for the *.slc files that are written to /usr/share/jed/lib during
postinst with a call to /usr/share/jed/compile/jed-common install.
In my expectations, such files should be in /var/lib since they're
variable data and not registered with the packaging system.
Greetings
Marc
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.4.2-zgws1 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages jed-common depends on:
ii dpkg 1.16.4.2
ii install-info 4.13a.dfsg.1-10
ii slsh 2.2.4-13
Versions of packages jed-common recommends:
ii jed 1:0.99.19-2.1
ii xjed 1:0.99.19-2.1
Versions of packages jed-common suggests:
ii jed [info-browser] 1:0.99.19-2.1
ii jed-extra [info-browser] 2.5.6-2
ii konqueror [info-browser] 4:4.8.4-1
ii pinfo [info-browser] 0.6.9-5.1
ii xjed [info-browser] 1:0.99.19-2.1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
I am hereby closing this 10-years old bug report. See below for
comments.
* Marc Haber <[email protected]> [2013-11-25 09:10]:
On Mon, Jun 18, 2012 at 10:52:36AM +0200, Guenter Milde wrote:
I am not sure whether this is a policy violation, but it is most
probably a surprise for most users. In Debian I expect all files under
/usr to come from packages, and thus be static. This is not the case
for the *.slc files that are written to /usr/share/jed/lib during
postinst with a call to /usr/share/jed/compile/jed-common install.
The *.slc files are bye-compiled versions of the corresponding *.sl files in
the packages jed-common and jed-extra.
Placing them alongside the sources is common practice and prevents
surprises when customizing the editor (using a custom jed-library-path,
using drop-in replacements from jed-extra or locally installed).
It might be easy for packaging, but is confusing for users. One
usually expects that dpkg --search is able to give an owner for every
file under /usr sans /usr/local.
The same scheme is used by Python-2 packages: the generated *.pyc files are
stored alongside the *.py source under usr/lib/...
python-support tries hard to place those files in /var, but not all
packages do already use it.
Well, this is what I see on my system:
$ find /usr -name \*.pyc | wc -l
61520
$ find /var -name \*.pyc | wc -l
0
It is hard to imagine that putting these compiled files (generated at
install time) in /usr would be a Policy violation.
Feel free to reopen this bug report if you find any evidence to the
contrary.
Best,
Rafael Laboissière
--- End Message ---
