Bug 209886 - An extra dir appears in the system root / after last updates
Summary: An extra dir appears in the system root / after last updates
Alias: None
Product: Fedora
Classification: Fedora
Component: tetex   
(Show other bugs)
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-07 14:09 UTC by Dmitry Butskoy
Modified: 2013-07-02 23:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-10 12:08:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dmitry Butskoy 2006-10-07 14:09:15 UTC
After the updating of tetex packages an extra directory has appeared in the
system root:
(This directory contains only an empty subdir web2c and a file ls-R).

At least both tetex-3.0-20.FC5 and tetex-3.0-29.fc5 are affected.

It seems that update/install process expects the invoking under a user, and
tries to write the ~/.texmf-var to the homedir of the user. The actual install
knows nothing about "a user", or just has the empty HOME environment. And
"private-user-config" subdir appears at the system root "/" ...

Comment 1 Jindrich Novy 2006-10-09 11:38:14 UTC
Weird, I cannot see it while installing tetex-3.0-29.fc5 to a pristine chroot.
I'll try to install tetex-3.0-20.FC5 and to upgrade to tetex-3.0-29.fc5 to see
what happens.

Comment 2 Dmitry Butskoy 2006-10-09 11:48:42 UTC
It seems that it happened at some previous updates of tetex.
When I remove this dir before the updating to the latest tetex, it not appears
after the update.

IMHO if you cannot reproduce this issue, just let foo on it... :)

Comment 3 Jindrich Novy 2006-10-10 12:08:49 UTC
Ok, I tested the update from tetex-3.0-20.FC5 to tetex-3.0-29.fc5 and saw no
/.texmf-var in root of the chroot -> closing NOTABUG, feel free to open another
bug when some other breakage occurs though ;-)

Note You need to log in before you can comment on or make changes to this bug.