346093 - No nightly update since 20060615 for 1.8.0 branch

Status: RESOLVED FIXED

(Toolkit :: Application Update, defect)

Description

[Jesus Cea]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060726 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060726 Firefox/1.5.0.5

My firefox and thunderbird (1.8.0 branches) are not finding any nightly since 20060615 update. Checking manually for new updates reports none is found.

I can't see what query string are sending, because changing "app.update.url" to point to my web server to capture the string in the logs doesn't work. Is that URL hardcoded?.

Googling around I find a sample url query:

https://aus2.mozilla.org/update/1/Firefox/1.5.0.4/2006010101/WINNT_x86-msvc/en-US/nightly/update.xml

Getting that URL I receive:

<?xml version="1.0"?>
<updates>
    <update type="minor" version="1.5.0.4" extensionVersion="1.5.0.4" buildID="2006061506" >
        <patch type="complete" URL="http://mozilla.osuosl.org/pub/mozilla.org/firefox/nightly//2006-06-15-06-mozilla1.8.0/firefox-1.5.0.4.en-US.win32.mar" hashFunction="SHA1" hashValue="a6d418e805ca002918dcf16ffe2b4580e1cfc6d1" size="6374151"/>
    </update>
</updates>

The update only goes to 2006061506 release.

If I try an URL like https://aus2.mozilla.org/update/1/Firefox/1.5.0.5/2006070101/WINNT_x86-msvc/en-US/nightly/update.xml

I get:

<?xml version="1.0"?>
<updates>
</updates>

That is, no updates available.

Reproducible: Always

Steps to Reproduce:
1. Install an old 1.5.0.* (1.8.0 branch) Firefox/Thunderbird, nightly version
2. Do a manual check for updates.

Actual Results:  
No updates available.

Expected Results:  
Download a more current version.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

This is a known issue, and depends on the resolution of bug 342797.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

*** Bug 346495 has been marked as a duplicate of this bug. ***

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

For reference, the current tinderbox configs for $update_version are

			Win		Lin		Mac
Firefox			1.5.0.5		1.5.0.x		*
Thunderbird		1.5.0.x		1.5.0.x		1.5.0.x

* Can't tell from the build log, $update_pushinfo isn't set

[Background: this variable controls where on AUS the snippets for nightly builds are copied to, and may need to be modifed after bug 342797 is fixed]

Comment 4

[Chris Cooper [:coop] (he/him)]

I've made changes to the configs for win32 and Mac UB that should help get updates flowing again.

Comment 5

[J. Paul Reed [:preed]]

TR:

Could you make sure that nightly updates on all the 1.8.0-branch builds are working, and close this bug when they are?

Thanks!

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

Tinderbox configs are all ok now, they are using $update_version="1.5.0.x". We needs the changes to the AUS server in bug 342797 to move forward.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to comment #6)
> Tinderbox configs are all ok now, they are using $update_version="1.5.0.x". We
> needs the changes to the AUS server in bug 342797 to move forward.

So apparently I was wrong with the "all ok now" comment, there are two more niggles to fix. On the windows Firefox machine (moz180-win32-tbox) the variables $update_appv and $update_extv are set to "1.5.0.x", which shows up in the update snippets and makes it look like all extensions will be disabled. Better would be to comment out those two definitions in tinder-config.pl and replace it with
   $update_ver_file = "browser/config/version.txt";
so that the version tracks along automatically.

This machine also needs to set
   ac_add_options --enable-update-channel="nightly"
instead of "release" in the mozconfig.

In other news, morgamic's changes to the AUS staging server means we have update information for Firefox & Thunderbird now.

Comment 8

[T.R. Fullhart]

I committed those changes:
Checking in win32/mozconfig;
/mofo/release/tinderbox-configs/firefox/win32/mozconfig,v  <--  mozconfig
new revision: 1.3.4.4; previous revision: 1.3.4.3
done
Checking in win32/tinder-config.pl;
/mofo/release/tinderbox-configs/firefox/win32/tinder-config.pl,v  <--  tinder-config.pl
new revision: 1.4.2.16; previous revision: 1.4.2.15
done

Marking as fixed, Nick can reopen it if he needs to.

Comment 9

[Jesus Cea]

I just received an "update available" notification for my firefox 2006080604 build (branch 1.8.0). Good!. It downloads 7.6 MB, I think; a full download, it seems.

But my thunderbird 2006080603 (branch 1.8.0) has no updates available, even when manually checking for them.

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to comment #9)
> I just received an "update available" notification for my firefox 2006080604
> build (branch 1.8.0). Good!. It downloads 7.6 MB, I think; a full download, it
> seems.

Not sure how this happened, as far as I can see the production instance of AUS doesn't give out update info yet. Did you modify app.update.url (or set app.update.url.override) to use aus2-staging.m.o instead aus2.m.o ?

> But my thunderbird 2006080603 (branch 1.8.0) has no updates available, even
> when manually checking for them.

As above. I checked that build defaults to the nightly channel, maybe you didn't make the change on thunderbird.

Comment 11

[Jesus Cea]

Nick, my update configuration is the default one, with the nightly channel selected.

Today I have a couple of extra data points:

1. My FF just downloaded a new nightly update a few minutes ago, so the auto update seems working right. The only issue: I already updated my FF yesterday, and today FF downloaded 7.6 MB again. That is, not "delta" download here, but a "full" download. Ugly.

2. My thunderbird installation (the one commented yesterday) just detected and downloaded a 9MB update...

Comment 12

[Nick Thomas [:nthomas] (UTC+12)]

I don't know why you would have seen that behaviour with Firefox, but it implies the first update didn't take cleanly or you weren't given the latest build. I can't reproduce it now though.

As you found with Thunderbird, updates for nightly 1.5.0.x builds are working. If you have further problems over the next few days then please open a new bug.