Closed
Bug 41991
Opened 24 years ago
Closed 1 month ago
Logfile shows extra "./" in pathway for Linux installs
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
Future
People
(Reporter: depman1, Assigned: slogan)
References
Details
(Keywords: platform-parity)
build 2000-06-08-08-M16. Linux installed build only. 1. On Linux, go to http://jimbob/trigger3.html 2. Select any test case installing something, say a_addtestfile. 3. Trigger and OK. 4. Check logfile. Result: Pathways for "Create Folder" and "Installing" contain and extra "./". This is where "package" folder is for extracted builds. logfile examples: ------------------------------------------------------------------------------- http://jimbob/jars/a_addtestfile.xpi -- 06/08/2000 17:37:51 ------------------------------------------------------------------------------- Acceptance: a_addtestfile ------------------------- [1/2] Create Folder: /u/depstein/builds/M16/jun08/./testFolder [2/2] Installing: /u/depstein/builds/M16/jun08/./testFolder/smrtupdt.txt Install completed successfully Finished Installation 06/08/2000 17:37:52 ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- http://jimbob/jars/a_adddir_full_iver_ver.xpi -- 06/08/2000 14:38:38 ------------------------------------------------------------------------------- Acceptance: a_adddir_full_iver_ver ---------------------------------- [1/3] Create Folder: /u/depstein/builds/M16/jun08/./adddir_full_iver_ver [2/3] Create Folder: /u/depstein/builds/M16/jun08/./adddir_full_iver_ver/subdir [3/3] Installing: /u/depstein/builds/M16/jun08/./adddir_full_iver_ver/subdir/smrtupdt.txt Install completed successfully Finished Installation 06/08/2000 14:38:38
Updated•24 years ago
|
Assignee: dveditz → sgehani
Comment 1•24 years ago
|
||
I'm not sure this is a problem, that is indeed the path to which we installed. Apparently XPCOM is giving us directory paths with that character in it, but it is accurate as far as it goes. Maybe nsIFile should be squeezing out these characters? Reassigning to Samir for evaluation, with an eye toward closing it though.
Comment 2•24 years ago
|
||
Dep, Did you provide a relative path in the folder selection dialog in the installer?
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Reporter | ||
Comment 3•24 years ago
|
||
no, I'm using an absolute path selected from the File Change dialog.
Reporter | ||
Comment 4•24 years ago
|
||
changed qa owner to depstein
Keywords: pp
QA Contact: jimmylee → depstein
Comment 5•24 years ago
|
||
How do you start mozilla? if it's something like ./mozilla that could be where XPCOM is getting the extra slash. In any case this is an XPCOM or nsIFile bug at best and most likely won't get fixed.
Reporter | ||
Comment 6•24 years ago
|
||
Yes, Mozilla is started with ./mozilla. But it's only happening in the installed build. In the extracted build, the file pathway correctly appears with the "package" folder (i.e. .../package/testFolder/file.txt) without the extra "./". Yesterday's build was the first time I saw this occur.
Updated•24 years ago
|
Priority: P3 → P2
Comment 10•23 years ago
|
||
Over to Syd for installer bug triage
Assignee: sgehani → syd
Status: ASSIGNED → NEW
Comment 11•20 years ago
|
||
Is this still an issue?
Updated•15 years ago
|
QA Contact: jimmykenlee → xpi-engine
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•