Bug 4238 - Links broken on page: Maemo 5 pre-alpha2 SDK
: Links broken on page: Maemo 5 pre-alpha2 SDK
Status: RESOLVED FIXED
Product: maemo.org Website
General
: unspecified
: All Linux
: Low normal (vote)
: ---
Assigned To: Marcell Lengyel
: general@maemo.org
:
:
:
:
  Show dependency tree
 
Reported: 2009-03-24 22:46 UTC by Uwe Kaminski
Modified: 2009-03-25 13:43 UTC (History)
3 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Uwe Kaminski (reporter) 2009-03-24 22:46:13 UTC
I wantetd to try out the Fremantle alpha2 SDK but there are broken links on the
page:
http://maemo.org/development/sdks/maemo5_prealpha2_main/

The following links in the "Downloads and documentation" section of the page
are broken:

Scratchbox installer:
http://repository.maemo.org/unstable/fremantle/maemo-scratchbox-install_5.0.sh

Maemo SDK installer:
http://repository.maemo.org/unstable/fremantle/maemo-sdk-install_5.0.sh

Content comparision between Maemo 5.0 pre-alpha and Maemo 5.0 pre-alpha2
http://repository.maemo.org/unstable/fremantle/maemo5.0prealpha_vs_5.0prealpha2_content_comparison.html


Content changes between Maemo 5.0 pre-alpha and Maemo 5.0 pre-alpha2
http://repository.maemo.org/unstable/fremantle/maemo5.0prealpha_vs_5.0prealpha2_content_changes.html


Content comparision between Maemo 4.1.2 and Maemo 5.0 pre-alpha2
http://repository.maemo.org/unstable/fremantle/maemo4.1.2_vs_5.0prealpha2_content_comparison.html


Content changes between Maemo 4.1.2 and Maemo 5.0 pre-alpha2
http://repository.maemo.org/unstable/fremantle/maemo4.1.2_vs_5.0prealpha2_content_changes.html
Comment 1 Ryan Abel maemo.org 2009-03-25 03:40:43 UTC
Well, the easy fix is to replace the codename with the real version number in
the URL. I'll do something about this if a Nokian doesn't step up by tomorrow,
though.
Comment 2 Quim Gil nokia 2009-03-25 07:14:53 UTC
I guess we need to come up with a more solid way to handle URLs for unstable
releases.
Comment 3 Ryan Abel maemo.org 2009-03-25 13:43:33 UTC
(In reply to comment #2)
> I guess we need to come up with a more solid way to handle URLs for unstable
> releases. 
> 

Well, repository-side everything is golden. The codename contains the latest
update for that release and previous updates are contained in versioned
folders. Some care just needs to be paid to this documentation-side.