Closed
Bug 66738
Opened 24 years ago
Closed 24 years ago
PSM failure
Categories
(Core Graveyard :: Security: UI, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: curt, Assigned: javi)
Details
(Keywords: smoketest)
Cannot enter a secure site.
Comment 1•24 years ago
|
||
This is a blocker but we are not holding the tree for it. If this still exists
on monday it might stop tree from opening then.
Comment 2•24 years ago
|
||
--> crypto
Assignee: asa → ddrinan
Component: Browser-General → Security: Crypto
QA Contact: doronr → junruh
Curt: Are there any indications you have PSM is installed at all?
Asking because I saw bug 64649 was marked fixed, but noticed that with installer
from linux sea.tar.gz, no PSM is installed w/build 2001012611.
(Added comment in 64649)
Comment 4•24 years ago
|
||
this is a code problem, it fails to build in the automation. reassigning to
javi.
We'll hold the tree hostage again Monday if it's not fixed then.
Assignee: ddrinan → javi
Comment 5•24 years ago
|
||
this is a stupid gmake/autoconf problem... wtc checked in new Makefile files,
which led the Makefile.in->Makefile dependency to not get triggered (since the
Makefiles were "up to date" or "newer than the dependency file, Makefile.in").
Checking in some white space will fix this. Yay, srcdir builds!
Assignee | ||
Updated•24 years ago
|
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•24 years ago
|
||
Added some white space to mozilla/security/psm/Makefile.in
Problem should be fixed next time around.
Comment 7•24 years ago
|
||
PSM still doesn't install with build 2001012821.
Comment 8•24 years ago
|
||
did you check the .tar.gz? It's possible you're seeing an installer/build
process bug, not a psm building bug.
Comment 10•23 years ago
|
||
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Comment 11•23 years ago
|
||
Mass changing Security:Crypto to PSM
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•