Opened 15 years ago

Closed 14 years ago

Last modified 14 years ago

#2217 closed task (fixed)

Seamonkey 1.1.1

Reported by: bdubbs@… Owned by: bdubbs@…
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

Version increment

http://www.mozilla.org/projects/seamonkey/releases/seamonkey1.1/

I use seamonkey as my usual browser/mail client. I am proposing putting this in 6.2.0.

Attachments (1)

seamonkey-1.1-location_hostname-1.patch (2.8 KB ) - added by Ag. Hatzimanikas 15 years ago.

Download all attachments as: .zip

Change History (14)

comment:1 by bdubbs@…, 15 years ago

Owner: changed from blfs-book@… to bdubbs@…
Status: newassigned

comment:2 by Randy McMurchy, 15 years ago

Could you ensure you check that the BLFS version of NSS/NSPR works? Also, ensure you check that the Enigmail version is updated if necessary.

comment:3 by bdubbs@…, 15 years ago

I'll check. I jsut verified that both the pango and system nss patches are in the new code and that Enigmail has rolled a minor version to enigmail-0.94.2.tar.gz

comment:4 by bdubbs@…, 15 years ago

Resolution: fixed
Status: assignedclosed

Fixed at revision 6434.

I had to put the enigmail tarfile on anduin for now. The url can be updated as soon as its fixed upstream. The only thing that should change are the url and the md5sum.

comment:5 by Randy McMurchy, 15 years ago

Resolution: fixed
Status: closedreopened
Type: taskdefect

Reopening the ticket for two things:

1) We need to keep the ticket open until there is a stable release of the Enigmail tarball.

2) Noted that you removed some instances of the calendar client notes, but there is still a config note about it, and it is still described as being there in the "short description" of seamonkey.

comment:6 by bdubbs@…, 15 years ago

Resolution: fixed
Status: reopenedclosed

Fixed both remaining issues at revision 6439.

comment:7 by Ag. Hatzimanikas, 15 years ago

Resolution: fixed
Status: closedreopened

Reopening the ticket,because of the critical flaw mentioned in #2218

No new version yet.

The following workaround might work.

Type about:config in location bar and then add a new string capability.policy.default.Location.hostname.

Set the value to 'noAccess'.

One old seamonkey 1.1 beta it did pass the test after doing the above. Bruce can you verified it?

I am building now 1.1 with the attached patch.

by Ag. Hatzimanikas, 15 years ago

in reply to:  7 comment:8 by Ag. Hatzimanikas, 15 years ago

Replying to Ag.Hatzim:

capability.policy.default.Location.hostname.

Please remove the dot at the end.

comment:9 by Randy McMurchy, 15 years ago

Milestone: 6.2.06.2.1
Priority: normalhigh
Severity: normalmajor

I would prefer if we opened new tickets for new issues. This is FYI for future items.

This ticket was for the SeaMonkey update and was completed. This is a new, unrelated item (the update was complete, and this is now a defect discovered later). I like seeing new issues at the bottom of the list (easy to locate new items).

in reply to:  9 comment:10 by Ag. Hatzimanikas, 15 years ago

Replying to randy@linuxfromscratch.org:

I would prefer if we opened new tickets for new issues.

Ok.

The build done. Seamonkey now passes the test.

Please if you applied first the workaround,remove the relative line in ~/.mozilla/default/xxxx/prefs.js before you start seamonkey.

comment:11 by Randy McMurchy, 14 years ago

Priority: highnormal
Severity: majornormal
Summary: Seamonkey 1.1Seamonkey 1.1.1
Type: defecttask

Version increment to 1.1.1

Also note the previous remarks in this ticket. The issue may still be valid.

comment:12 by bdubbs@…, 14 years ago

Resolution: fixed
Status: reopenedclosed

Updated to version 1.1.1. The patch referred to previously is incorporated into this version. Revision 6764.

comment:13 by (none), 14 years ago

Milestone: 6.2.1

Milestone 6.2.1 deleted

Note: See TracTickets for help on using tickets.