Lightning nightly for Thunderbird daily version 22.0a1 - No auto-update?

[Peter Lairo]

Thunderbird daily just updated to version 22.0a1. Lightning trunk did
*not* auto-update (2.3a1 to 2.4a1), even though bug 808668 was fixed on
14.02.2013 and I am reasonably sure I had (manually) installed Lightning
trunk[1] after that date. I had to download the new version of Lightning
(2.4.a1) from the FTP server[1] and install it manually.

Related: Since there is no way to see the Lightning build *date*, it is
impossible to know whether Lightning nightly is auto-updating. This is a
bad situation because it forces us to manually update Lightning to be
current and certain.

[1]
https://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-central/

PS. https://developer.mozilla.org/en-US/docs/Calendar/Calendar_Versions
needs to be updated.
--
Regards,
Peter Lairo

Bugs I think are important:
https://bugzilla.mozilla.org/show_bug.cgi?id=250539
https://bugzilla.mozilla.org/show_bug.cgi?id=391057
https://bugzilla.mozilla.org/show_bug.cgi?id=436259
https://bugzilla.mozilla.org/show_bug.cgi?id=446444

Islam: http://www.jihadwatch.org/islam101/
Israel: http://www.jewishvirtuallibrary.org/jsource/myths2/
Church of the Flying Spaghetti Monster: http://www.venganza.org/
Anthropogenic Global Warming skepsis: http://tinyurl.com/AGW-Skepsis

[Philipp Kewisch]

The script that does the updates is not driven by available builds, but
by expected merge/release dates. Please expect glitches in the day or
two around the merge date (which was yesterday), it should be fine tomorrow.

Next time just wait a day, auto-updates should work automatically.

Philipp

[Stefan Sitter]

On 20.02.2013 15:15, Peter Lairo wrote:
> Related: Since there is no way to see the Lightning build *date*, it
> is impossible to know whether Lightning nightly is auto-updating.
> This is a bad situation because it forces us to manually update
> Lightning to be current and certain.

You can see the BuildID that includes the build date and time in Tools >
Add-ons > Extensions > Lightning > context menu > About.

If you want to know the specific source code change id for the
comm-central or mozilla-central repositories take a look at the file
"...\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103}\application.ini"
in your profile folder. This is useful e.g. if you want to see the
changes between two specific Lightning builds.

/Stefan

[Peter Lairo]

On Mi. 20.02.2013 20:39, Stefan Sitter wrote:
> On 20.02.2013 15:15, Peter Lairo wrote:
>> Related: Since there is no way to see the Lightning build *date*, it
>> is impossible to know whether Lightning nightly is auto-updating.
>> This is a bad situation because it forces us to manually update
>> Lightning to be current and certain.
>
> You can see the BuildID that includes the build date and time in Tools >
> Add-ons > Extensions > Lightning > context menu > About.

Thanks! *That* answered my question. :-)

Now if I can only remember this obscure location the next time I want to
know the build date...

Oh, I just noticed that the "more" screen has a line titled "Last
updated", and it seems to show the build date. Is that true? If so, that
would be a discoverable place for the build date.

[Peter Lairo]

On Mi. 20.02.2013 19:37, Philipp Kewisch wrote:
>
> The script that does the updates is not driven by available builds, but
> by expected merge/release dates.

I don't understand that sentence. Does that mean that Lightning will
only check for updates every few days/weeks/months because that is the
normal "merge/release" cycle for updates?

> Please expect glitches in the day or
> two around the merge date (which was yesterday), it should be fine
> tomorrow.

OK. I don't mind glitches. I was uncertain because I couldn't find a way
to verify the update.

> Next time just wait a day, auto-updates should work automatically.

I don't mind waiting 10 days or more. I just want a way to verify if
it's working at all.

BTW: Can you recommend a good German speaking web programmer and
database expert for my new company (an online dating service)? It will
be a respectable service, and I want to use good web practices too. :-)

[Stefan Sitter]

On 20.02.2013 20:53, Peter Lairo wrote:
> Oh, I just noticed that the "more" screen has a line titled "Last
> updated", and it seems to show the build date. Is that true? If so,
> that would be a discoverable place for the build date.

I think it shows only the date the extension was installed the last
time, either manually or by automatic update.

The Lightning nightly update mechanism is very simple and just points to
the most current nightly build. This means you can receive an update but
the build that will be installed is already days or weeks old -
depending on the date of the last successful nightly build.

Risks for that are now minimized because Lightning is build together
with the official Thunderbird builds on the Thunderbird build servers.
If a new Thunderbird nightly is available a new Lightning nightly should
be available too.

/Stefan

[WaltS]

Updated Thunderbird to Mozilla/5.0 (X11; Linux x86_64; rv:22.0)
Gecko/20100101 Thunderbird/22.0a1 BuildID: 20130221030459.

Attempted updating Lightning, but update failed with these errors in the
Error Console...

versioncheck.addons.mozilla.org : server does not support RFC 5746, see
CVE-2009-3555

Timestamp: 02/21/2013 08:58:35 AM
Warning: WARN addons.xpi: Download failed: 404 Not Found
Source File: resource://gre/modules/XPIProvider.jsm
Line: 4922

Activated "Try Again" twice, and got the second error twice more.

--
Fedora 18.0 (64-bit) KDE 4.9.5
Thunderbird Daily
If we burn in hell, do we freeze in heaven?

[Stefan Sitter]

On 21.02.2013 15:05, WaltS wrote:
> Updated Thunderbird to Mozilla/5.0 (X11; Linux x86_64; rv:22.0)
> Gecko/20100101 Thunderbird/22.0a1 BuildID: 20130221030459.
>
> Attempted updating Lightning, but update failed with these errors in
> the Error Console...
>

> Warning: WARN addons.xpi: Download failed: 404 Not Found
>

> Activated "Try Again" twice, and got the second error twice more.

I noticed the same and commented in Bug 808668.
https://bugzilla.mozilla.org/show_bug.cgi?id=808668#c23

/Stefan