Closed Bug 702131 Opened 13 years ago Closed 11 years ago

ftp latest-link does not point to the latest

Categories

(Release Engineering :: Release Automation: Other, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: GbSlack, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

try to get the latest thunderbird via
ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/


Actual results:

ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/ points to 7.0.1 instead to latest-8.0 as expected

It is a revitalisation of the Bug 679678 (https://bugzilla.mozilla.org/show_bug.cgi?id=679678)


Expected results:

ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/
should point to 
ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest-8.0/
By making a bug security sensitive you restrict the number of people who can view and act upon it. Please use the security flag responsibly. I'm not sure which product/component this should fit under though.
Group: core-security
Status: UNCONFIRMED → NEW
Ever confirmed: true
overnight it has been fixed by somebody. Now it works and ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/ points to ftp://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/latest-8.0/. But maybe something in the linking automatism is not quite fully functional. How to avoid it for the next release, if we set the status now to resolved?
Coop, where should we have filed this and is it resolved for future releases?
mozilla.org: Release Engineering
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
it is back again

the latest link (ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/) does not point to the latest. 
E.g. ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/linux-i686/de/ points to version 17.0.3, but current version is 17.0.5.

Seems, that the release mechanism is vulnerable for this failure.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Version: 8 → 17
Component: General → Release Engineering
Product: Thunderbird → mozilla.org
Version: 17 → other
I've just verified that the following links are correctly pointing to the latest available:

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/ --> FF21.0
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/latest/ --> TB17.0.6

Hence I'm closing as WORKSFORME. However, if you see differently, please do reopen with specific URLs and we'll investigate. 



(Found in triage, and moving to correct component. We've modified our bug components since this bug was first filed and fixed in 2011. If you see this again, please file bugs in "mozilla.org:ReleaseEngineering Automation (Release Automation)" and we'll fix it.)
Status: REOPENED → RESOLVED
Closed: 13 years ago11 years ago
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: bhearsum
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
It's not working again. Latest FF is 29.0.1, while http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/ points to 29. The same problem occurred with previous update.

It's a security problem for me, since I'm deploying FF in an automated manner (that is automated download to network folder and automated installation from it on all machines in my network).

Please fix it.
(In reply to Krzysztof Radomski from comment #7)
> It's not working again. Latest FF is 29.0.1, while
> http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/ points to
> 29. The same problem occurred with previous update.
> 
> It's a security problem for me, since I'm deploying FF in an automated
> manner (that is automated download to network folder and automated
> installation from it on all machines in my network).
> 
> Please fix it.

Post-release task was triggered before this comment, and will update the link.
Please be patient.
(In reply to Aki Sasaki [:aki] from comment #8)

> Post-release task was triggered before this comment, and will update the
> link.
> Please be patient.

Previously (that is from 28 to 29 update) it took solid few days, that's why I'm perhaps too rushy now. Thank you.
You need to log in before you can comment on or make changes to this bug.