Closed Bug 1256567 Opened 8 years ago Closed 8 years ago

SeaMonkey 2.40 not recognized as valid update for SeaMonkey 2.39

Categories

(SeaMonkey :: Release Engineering, defect)

Product:
SeaMonkey
Component:
Release Engineering
Version:
SeaMonkey 2.40 Branch
Platform:
Unspecified
Windows
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
seamonkey2.40

People

(Reporter: RainerBielefeldNG, Assigned: ewong)

References

Details

(Whiteboard: [easyconfirm]) 

Menu 'Help → Search for Updates ...' ends with message "No updates available. ...", although we have 2.40
Confirmed. Exact same behavior on Windows 10 (64 bit w/32 bit SeaMonkey). 

SeaMonkey 2.39 does not see the available 2.40 update.
Confirmed with comment 1, de.comm.software.mozilla.browser / "[SM 2.40] Automatisches Update kommt nicht", <https://blog.seamonkey-project.org/2016/03/14/2-40-is-out/#comment-2254>

I am worried that I can't find a DUP, I am pretty sure that this problem started more early.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → Windows
It happens in my very old, updated Windows XP Pro SP3 too.
Due to <nntp://news.mozilla.org.mozilla.dev.apps.seamonkey> "updates... *finally*?" I did a test with SeaMonkey German 2.39 final Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area)  Gecko/20100101  Firefox/42.0  Build 20151103191810  (Classic Theme) on German WIN7 64bit:
'Help → Search for updates' finds SeaMonkey 2.40. I did not try to proceed the update because I want to keep my 2.39 for tests.

Really seems fixed.

Assignee due to facts.
Assignee: nobody → ewong
Status: NEW → ASSIGNED
(In reply to Rainer Bielefeld from comment #4)
oops, typo! Should have been <nntp://news.mozilla.org/mozilla.dev.apps.seamonkey>
Worked for me today:
* From Seamonkey 2.39/de
* To Seamonkey 2.40/de
* On Windows 7/de
FIXED due to comments here and in NG
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.40
See Also: → 1259523
It might be that the problem has returned? The same Version SeaMonkey German 2.39 final Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area)  Gecko/20100101  Firefox/42.0  Build 20151103191810  (Classic Theme) on German WIN7 64bit which I used for my test in Comment 4 today states: "No updates available. ...".

Same result with blank new user profile for that Version.
Not seeing the 2.40 update.
Windows 7, currently running 2.39, Build identifier: 20151103191810
Check for updates tells me none are available.
Still broken.
Same here:

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
Build-Identifikator: 20151103191810

Check for updates tells me none are available.
Still broken.

This Bug is NOT resolved!
This bug is NOT resolved.  

I am still waiting for SeaMonkey 2.39 to update to 2.40 via "check for updates".  It still tells me none available.

This is on Windows 8.0 Pro.

This bug needs to be reopened.
REOPENED due to several comments.

@Edmund:
Did the fix vanish or do we have a new problem?
Status: RESOLVED → REOPENED
Flags: needinfo?(ewong)
Resolution: FIXED → ---
The issue here is that I wasn't sure if the update was right when
I linked the msvc-x86-x64 to msvc-x86.    Having tried this, I
think it works; but whether it's right, that's a different matter.
I need to clarify with Callek.
Flags: needinfo?(ewong)
(In reply to JustOff from comment #15)
> I've tested how several versions of SeaMonkey checks for updates:
> 
> 24: no updates (WRONG)
> https://aus2-community.mozilla.org/update/3/SeaMonkey/2.24/20140203230027/
> WINNT_x86-msvc/en-US/release/Windows_NT%206.1.1.0%20(x64)/default/default/
> update.xml?force=1
> 
> 38: updates (OK)
> https://aus2-community.mozilla.org/update/3/SeaMonkey/2.38/20150923195647/
> WINNT_x86-msvc/en-US/release/Windows_NT%206.1.1.0%20(x64)/default/default/
> update.xml?force=1
> 
> 39: no updates (WRONG)
> https://aus2-community.mozilla.org/update/3/SeaMonkey/2.39/20151103191810/
> WINNT_x86-msvc-x64/en-US/release/Windows_NT%206.1.1.0%20(x64)/default/
> default/update.xml?force=1
> 
> 40: no updates (OK)
> https://aus2-community.mozilla.org/update/3/SeaMonkey/2.40/20160120202951/
> WINNT_x86-msvc-x64/en-US/release/Windows_NT%206.1.1.0%20(x64)/default/
> default/update.xml?force=1
> 
> What is the difference between x86-msvc and x86-msvc-x64, which prevents the
> correct update result?

At this point, there isn't any difference except that between 2.24 and 2.39/2.40,
we had changed to use a loaner which is 64bit, and I suppose the build id
was changed as well.  Then there's the possibility of me screwing up.

Will get this fixed soon.
Status: REOPENED → ASSIGNED
Flags: needinfo?(ewong)
Another week passed, today it's almost a month since the 2.40 release, but windows users still stucked with 2.39. Do you have any resonable explanations what's going on?
Flags: needinfo?(ewong)
(In reply to JustOff from comment #17)
> Another week passed, today it's almost a month since the 2.40 release, but
> windows users still stucked with 2.39. Do you have any resonable
> explanations what's going on?

The only explanation for this is because I can't access the update host
since the ssh key to access this host (and the build master and the
build slaves) is now revoked and needs to be regenerated. 

Once this is done, I can safely fix this problem (amongst other issues).

I do apologize for keeping everyone waiting.
Flags: needinfo?(ewong)
Next two weeks passed. Still no progress. Your new ssh key will be super strong, if you spend all this time for generating it.
Flags: needinfo?(ewong)
(In reply to JustOff from comment #19)
> Next two weeks passed. Still no progress. Your new ssh key will be super
> strong, if you spend all this time for generating it.

Sorry to keep you waiting.  I believe the updating should be ok, provided
it's not for anything < 2.35; due to the fact that post-2.35, the certificate for 
the update server had changed and pre-2.35 versions will not be able to update 
directly to 2.40.  This means a manual download of 2.40.

As for the updating, please check now.
Flags: needinfo?(ewong)
It's done at last! Thank you.
Info: I just got an Update for my 2.39 german Seamonkey. Now its 2.40 *g*
Looks like this should be considered fixed. :)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.