Closed Bug 1208702 Opened 4 years ago Closed 4 years ago
Monkey website for 2 .38
+++ This bug was initially created as a clone of Bug #1177048 +++ For making SeaMonkey 2.38 public, we'll need to update the website. Please "hg add src/releases/2.38.en.html" locally after applying the patch and before committing.
Pushed to website: https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/rev/9d05a02b5062
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
'apparently', we now use xz to compress the sourcecode. This patch changes the source to tar.xz.
Attachment #8667090 - Flags: review?(jh)
Comment on attachment 8667090 [details] [diff] [review] source code fix We need this for 2.38b1, too. You have r+ for that as well if you'd do it in one go.
Attachment #8667090 - Flags: review?(jh) → review+
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #4) > Comment on attachment 8667090 [details] [diff] [review] > source code fix > > We need this for 2.38b1, too. You have r+ for that as well if you'd do it in > one go. I'll update the patch and then do the push.
Comment on attachment 8667140 [details] [diff] [review] source code fix (v2) (w/ 2.38b1's change as well) Pushed to website: https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/rev/d69810501b9b
I've waited for probably around 10 minutes and it doesn't seem to be updating. Looking at the link itself, it goes to archive.mozilla.org/. I've looked at my push and I don't see anything wrong. Is anyone getting any complaints from the website update-mailer thingy?
(In reply to Edmund Wong (:ewong) from comment #8) > I've waited for probably around 10 minutes and it doesn't seem to be > updating. > Looking at the link itself, it goes to archive.mozilla.org/. > > I've looked at my push and I don't see anything wrong. Is anyone getting > any complaints from the website update-mailer thingy? nvm.. seems as if there was a longer delay. The 2.38b1's source link is updated, but the 2.38 one hasn't yet.
I'm a tad bit stumped here. Having pushed that patch, both 2.38b1.en.html and 2.38.en.html are updated (as shown by the source via hg.mo's source listing, but for some reasons the change to 2.38b1 is complete; but the change to 2.38 isn't. It's still showing the bzip extension. I've cleared my cache. I've asked a user on #seamonkey to confirm and indeed it's still showing bzip2. Jens, got any idea?
I think you got confused by the fact that for the current release at a time, there are two pages that almost look the same. One of them is the releases index page which you didn't adapt. That one is linked to from the news section. I just pushed the following which should fix it: https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/rev/55d016aaca7d Please verify.
Status: REOPENED → RESOLVED
Closed: 4 years ago → 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.