Bug#528021: unowned files after purge (policy 6.8)
Holger Levsen <holger@layer-acht.org> wrote:
>> That is a _should_ requirement and reading the start of the policy you
>> could see that
>
> ... thats right, but...
>
>> So please refrain from playing with severities without checking the
>> details.
>
> I'm setting the severity based on the release goals for squeeze, see
> http://release.debian.org/squeeze/goals.txt
Then please take the time and explain the correct rationale. Not every
package maintainer (not even one in every team...) has the capacity to
remember all release goals by heart.
Furthermore, I'm a bit surprised that a violation of a should in policy
and of a realease goal warrants a serious but this early in the release
cycle. Ours is easy to fix; however if it wasn't, I'd not appreciate if
improvements that are important to have in squeeze wouldn't propagate to
testing in time because of this.
>> Furthermore, removing tex-common will remove /u/l/s/texmf as can be seen
>> from the prerm script containing:
>> rmdir /usr/local/share/texmf 2>/dev/null || true
>
> This doesnt happen as you could have seen in the attached log.
Okay, there still seems to be a bug in tex-common.
> So there is definitly a bug and I like to see it fixed. Could it be that a
> cronjob is putting some files in /usr/local/share/texmf/ ?
No.
> $ ls -la /usr/local/share/texmf/ls-R
> lrwxrwxrwx 1 root staff 25 Jan 7
> 2007 /usr/local/share/texmf/ls-R -> /var/lib/texmf/ls-R-LOCAL
>
> And I'm quite certain that I didnt put it there myself.
No, that needs to be done by the postinst script when it creates the
directory - otherwise it'd be useless. We need to remove that upon
purge, too.
Regards, Frank
--
Dr. Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg
Reply to: