Re: Anyone have the akalla x64 SM 2.52b somewhere?

[TCW]

On 9/11/2017 12:00 PM, John Duncan wrote:
The seemingly arbitrary and heavily bureaucratic decimation of a large 
number of older APIs and core features that power users depend on (in 
Mozilla's desperate bid to stay relevant in a world dominated by people 
who get flustered when the homepage of google tells them to download and 
install a new browser for an enhanced browsing experience) is more of 
the issue in this case.
And I have yet to understand why Mozilla doesn't just put code that 
changes that stupid mis-advertisement to promote to their product. 
Google knows full well what they're doing when they show that message: 
leveraging they playing field in their favor. Fight fire with fire I 
say. If good artists borrow and great artists steal, then steal from 
Google the way they steal from everyone else. What are they going to do, 
cry?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

Frank-Rainer Grahl wrote:
They still have a lot of money to burn. Market share in 5 to 6 months 
should show if it is a success. I have my doubts. If you p*ss off enough 
power users who recommend it to others not much left. "Normal" users 
will just continue using Chrome. They don't care about privacy and all 
the other things Mozilla is touting as achievements for 57.
Totally agree. We shall see what is left of the FF user-base once the 
dust settles.


Cheers,
-john
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

WaltS48 wrote:

On 9/10/17 11:04 AM, Frank-Rainer Grahl wrote:
I probably need to do a Fx Nightly again just to see what changed but 
this is all so much urgkkk for only fanboys to love. This is all 
rushed and I personally hope it backfires but even this would do 
SeaMonkey no good.


Do you really call Photon and Quantum development over version 55, 56 
and 57 nighties, and 57 betas rushed?


When I first saw Australis, I went wtf?, then working with it over a 
series of Nightlies, I learned how to customize and use it.


Sure about 500,000 users installed CTR, but what percentage of total 
Firefox users is that.


When I first saw Photon in Fx 55.0, I went wtf?, where did my Menu 
Button icons go!. Now working with Photon over a series of Nightlies 
I've learned how to customize and use it.


Do I like all the changes. Not really, but clicking the Library button 
and having access to Bookmarks, Pocket List, History, Synced Tabs, 
Screenshots and Downloads is nice.


Call me fanboy if you like. Somebody has to counter the doom and gloom 
of the whiners.


The seemingly arbitrary and heavily bureaucratic decimation of a large 
number of older APIs and core features that power users depend on (in 
Mozilla's desperate bid to stay relevant in a world dominated by people 
who get flustered when the homepage of google tells them to download and 
install a new browser for an enhanced browsing experience) is more of 
the issue in this case.


Ignoring the random changes in Firefox's UI over the years, most of 
which are ignorable and/or inconsequential, there has been a troubling 
trend recently of an arbitrary reduction and deprecation of many 
different parts of the mozilla-central tree (you can't even keep history 
longer than like six months without yielding to extension fodder! 
They're removing 10+ years of work from add-on developers under the 
guise of techno-'modernity' and 'safety').


I am not saying that our community has all of the answers to these 
problems (the largest, imo, is a socio-cultural norm established by 
Google that socializes users in such a way as to passively accept a 
heavily simplified browsing experience, leading to a much smaller 
community of 'hackers'/power-users (which was, in comparison, fostered 
by orgs like Netscape/old Mozilla/etc.) thus causing other 
projects/organizations to follow suite to gain back the user-base that 
they lose).


Anyway, complaining about this probably won't really change any of the 
decisions coming from Mozilla, so for the foreseeable future, we'll just 
need to continuously re-build from the pieces that are left after the 
insanity of the Firefox 57 release dissipates.


-john
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[Frank-Rainer Grahl]

I call the whole package rushed. Photon should be fine. With it overall 
further reduction of colors in icons and styles it does not appeal to me but 
it should work.


The biggest problems I am having is with web extensions deficits/design and 
the gutting of the source tree two release before an ESR. This is burning down 
the house with no backup.


Market share in 6 months will tell if the strategy will work.

As for numbers. I only really trust the ones I make up myself :)
So for market share probably more than one source needs to be evaluated to get 
the big picture.


I simply do no longer care about Fx. Joe Average can run what he wants to run. 
In the past when I set up a pc for friends I installed Fx when I fully knew 
well that SeaMonkey wouldn't work for this user. Which were for most of them. 
I don't do this any more. Most ended up with Chrome anyway.


FRG



WaltS48 wrote:

On 9/10/17 11:04 AM, Frank-Rainer Grahl wrote:
I probably need to do a Fx Nightly again just to see what changed but this 
is all so much urgkkk for only fanboys to love. This is all rushed and I 
personally hope it backfires but even this would do SeaMonkey no good.


Do you really call Photon and Quantum development over version 55, 56 and 57 
nighties, and 57 betas rushed?


When I first saw Australis, I went wtf?, then working with it over a series of 
Nightlies, I learned how to customize and use it.


Sure about 500,000 users installed CTR, but what percentage of total Firefox 
users is that.


When I first saw Photon in Fx 55.0, I went wtf?, where did my Menu Button 
icons go!. Now working with Photon over a series of Nightlies I've learned how 
to customize and use it.


Do I like all the changes. Not really, but clicking the Library button and 
having access to Bookmarks, Pocket List, History, Synced Tabs, Screenshots and 
Downloads is nice.


Call me fanboy if you like. Somebody has to counter the doom and gloom of the 
whiners.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[WaltS48]

On 9/10/17 11:04 AM, Frank-Rainer Grahl wrote:
I probably need to do a Fx Nightly again just to see what changed but 
this is all so much urgkkk for only fanboys to love. This is all rushed 
and I personally hope it backfires but even this would do SeaMonkey no 
good.


Do you really call Photon and Quantum development over version 55, 56 
and 57 nighties, and 57 betas rushed?


When I first saw Australis, I went wtf?, then working with it over a 
series of Nightlies, I learned how to customize and use it.


Sure about 500,000 users installed CTR, but what percentage of total 
Firefox users is that.


When I first saw Photon in Fx 55.0, I went wtf?, where did my Menu 
Button icons go!. Now working with Photon over a series of Nightlies 
I've learned how to customize and use it.


Do I like all the changes. Not really, but clicking the Library button 
and having access to Bookmarks, Pocket List, History, Synced Tabs, 
Screenshots and Downloads is nice.


Call me fanboy if you like. Somebody has to counter the doom and gloom 
of the whiners.


--
Go Bucs, Pitt, Steelers!
Coexist 
National Popular Vote 
Ubuntu 16.04 LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[Frank-Rainer Grahl]

> Right, I keep forgetting that the C++ download manager is being retired.

Gone in 2.52.

> Cool. I will try out 2.53 then, as there is a noticeable speed difference
> (especially javascript) between the current FF nightly and SM 2.48.

2.49.1 should be quite nice. Its my main browser for months now and very 
stable. I think the most polished and best release yet. Hope not too many new 
bugs pop up.


> If things do not go well with the 57 release, it really could be
> corporate suicide from Mozilla.

They still have a lot of money to burn. Market share in 5 to 6 months should 
show if it is a success. I have my doubts. If you p*ss off enough power users 
who recommend it to others not much left. "Normal" users will just continue 
using Chrome. They don't care about privacy and all the other things Mozilla 
is touting as achievements for 57.


Have fun
FRG

John Duncan wrote:

 > Download Manager e.g. needs a serious makeover before I would want it to
 > be released. This is more a case study since 2.52 :)
Right, I keep forgetting that the C++ download manager is being retired.
 > I am still on 2.53. Didn't check if DOMi and cZ still work but if not
 > they could surely being patched up. But Adblock+ and uBlock are both
 > broken.
Right, with those moving toward pure web-extensions, I suppose SM will need to 
land web-extension support to properly run their most recent versions.

 > We switched to ESR so that we have more time to prepare a release.
 > Unless 4 to 5 programmers pop up it is unlikely then we will return the
 > do releases from the release repo. After the 52 ESR branch is eol we
 > plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
 > still unsure if Mozilla continues to destroy the old codebase. We need
 > to port Web Extension support and e10s at least for later releases but
 > this is a huge task for such a small team.
Totally agree. That sounds like a relatively gargantuan undertaking for the 
tiny council/SM team.

 >
 > I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
 > unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
 > switched to esr 52 for testing only. I probably need to do a Fx Nightly
 > again just to see what changed but this is all so much urgkkk for only
 > fanboys to love. This is all rushed and I personally hope it backfires
 > but even this would do SeaMonkey no good.
Cool. I will try out 2.53 then, as there is a noticeable speed difference 
(especially javascript) between the current FF nightly and SM 2.48.
It all does seem extremely rushed and unprofessional; perhaps Mozilla has 
finally lost their way. I swear the only thing people on /r/Firefox talk about 
is the current Nightly icon change and other trivial and/or unimportant minor 
browser features (theming userChrome.css, etc.) If things do not go well with 
the 57 release, it really could be corporate suicide from Mozilla.

 >
 > Building 2.49.1 should atart soon. Everything has been checked in now. A
 > little late but we do what we can with the limited resourced at hand.
No rush. The fact that the team gets such a great deal done with so little 
resources is a considerable achievement.


-john

Frank-Rainer Grahl wrote:

Forgive me if I have misunderstood the meeting minutes, but since the

nightly

release channel will continue to support things like XUL overlays, legacy
extensions, webextension eperiments, etc. [0], why don't you continue to
ingest & build off of mozilla-central?


Nightlies will, of course be build. The list of bug which needs to be
fixed before a SeaMonkey 2.54 would be usable is quite long and I didn't
even file one or two for bookmark and other problems yet:

https://bugzilla.mozilla.org/show_bug.cgi?id=1394144

Download Manager e.g. needs a serious makeover before I would want it to
be released. This is more a case study since 2.52 :)


Is the plan to eventually switch back from ESR once bug fixes are

landed and

the API removal spree has subsided? Or will the API changes break more
essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current

2.54

builds, which is a good sign.


I am still on 2.53. Didn't check if DOMi and cZ still work but if not
they could surely being patched up. But Adblock+ and uBlock are both
broken.

We switched to ESR so that we have more time to prepare a release.
Unless 4 to 5 programmers pop up it is unlikely then we will return the
do releases from the release repo. After the 52 ESR branch is eol we
plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
still unsure if Mozilla continues to destroy the old codebase. We need
to port Web Extension support and e10s at least for later releases but
this is a huge task for such a small team.

I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
switched to esr 52 for testing only. I probably 

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

> Download Manager e.g. needs a serious makeover before I would want it to
> be released. This is more a case study since 2.52 :)
Right, I keep forgetting that the C++ download manager is being retired.
> I am still on 2.53. Didn't check if DOMi and cZ still work but if not
> they could surely being patched up. But Adblock+ and uBlock are both
> broken.
Right, with those moving toward pure web-extensions, I suppose SM will 
need to land web-extension support to properly run their most recent 
versions.

> We switched to ESR so that we have more time to prepare a release.
> Unless 4 to 5 programmers pop up it is unlikely then we will return the
> do releases from the release repo. After the 52 ESR branch is eol we
> plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
> still unsure if Mozilla continues to destroy the old codebase. We need
> to port Web Extension support and e10s at least for later releases but
> this is a huge task for such a small team.
Totally agree. That sounds like a relatively gargantuan undertaking for 
the tiny council/SM team.

>
> I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
> unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
> switched to esr 52 for testing only. I probably need to do a Fx Nightly
> again just to see what changed but this is all so much urgkkk for only
> fanboys to love. This is all rushed and I personally hope it backfires
> but even this would do SeaMonkey no good.
Cool. I will try out 2.53 then, as there is a noticeable speed 
difference (especially javascript) between the current FF nightly and SM 
2.48.
It all does seem extremely rushed and unprofessional; perhaps Mozilla 
has finally lost their way. I swear the only thing people on /r/Firefox 
talk about is the current Nightly icon change and other trivial and/or 
unimportant minor browser features (theming userChrome.css, etc.) If 
things do not go well with the 57 release, it really could be corporate 
suicide from Mozilla.

>
> Building 2.49.1 should atart soon. Everything has been checked in now. A
> little late but we do what we can with the limited resourced at hand.
No rush. The fact that the team gets such a great deal done with so 
little resources is a considerable achievement.


-john

Frank-Rainer Grahl wrote:

Forgive me if I have misunderstood the meeting minutes, but since the

nightly

release channel will continue to support things like XUL overlays, legacy
extensions, webextension eperiments, etc. [0], why don't you continue to
ingest & build off of mozilla-central?


Nightlies will, of course be build. The list of bug which needs to be
fixed before a SeaMonkey 2.54 would be usable is quite long and I didn't
even file one or two for bookmark and other problems yet:

https://bugzilla.mozilla.org/show_bug.cgi?id=1394144

Download Manager e.g. needs a serious makeover before I would want it to
be released. This is more a case study since 2.52 :)


Is the plan to eventually switch back from ESR once bug fixes are

landed and

the API removal spree has subsided? Or will the API changes break more
essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current

2.54

builds, which is a good sign.


I am still on 2.53. Didn't check if DOMi and cZ still work but if not
they could surely being patched up. But Adblock+ and uBlock are both
broken.

We switched to ESR so that we have more time to prepare a release.
Unless 4 to 5 programmers pop up it is unlikely then we will return the
do releases from the release repo. After the 52 ESR branch is eol we
plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
still unsure if Mozilla continues to destroy the old codebase. We need
to port Web Extension support and e10s at least for later releases but
this is a huge task for such a small team.

I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
switched to esr 52 for testing only. I probably need to do a Fx Nightly
again just to see what changed but this is all so much urgkkk for only
fanboys to love. This is all rushed and I personally hope it backfires
but even this would do SeaMonkey no good.

Building 2.49.1 should atart soon. Everything has been checked in now. A
little late but we do what we can with the limited resourced at hand.

FRG

John Duncan wrote:

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build 

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[Frank-Rainer Grahl]

> Forgive me if I have misunderstood the meeting minutes, but since the nightly
> release channel will continue to support things like XUL overlays, legacy
> extensions, webextension eperiments, etc. [0], why don't you continue to
> ingest & build off of mozilla-central?

Nightlies will, of course be build. The list of bug which needs to be fixed 
before a SeaMonkey 2.54 would be usable is quite long and I didn't even file 
one or two for bookmark and other problems yet:


https://bugzilla.mozilla.org/show_bug.cgi?id=1394144

Download Manager e.g. needs a serious makeover before I would want it to be 
released. This is more a case study since 2.52 :)


> Is the plan to eventually switch back from ESR once bug fixes are landed and
> the API removal spree has subsided? Or will the API changes break more
> essential SeaMonkey features as well? It seems as if DOM
> Inspector/Lightning/Chatzilla all still seem to be working in current 2.54
> builds, which is a good sign.

I am still on 2.53. Didn't check if DOMi and cZ still work but if not they 
could surely being patched up. But Adblock+ and uBlock are both broken.


We switched to ESR so that we have more time to prepare a release. Unless 4 to 
5 programmers pop up it is unlikely then we will return the do releases from 
the release repo. After the 52 ESR branch is eol we plan to switch to ESR 59 
for 2.56.x. If nad when it comes to that is still unsure if Mozilla continues 
to destroy the old codebase. We need to port Web Extension support and e10s at 
least for later releases but this is a huge task for such a small team.


I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is unusable 
right now. Uninstalled all Fx 56/57 betas and nightlies and switched to esr 52 
for testing only. I probably need to do a Fx Nightly again just to see what 
changed but this is all so much urgkkk for only fanboys to love. This is all 
rushed and I personally hope it backfires but even this would do SeaMonkey no 
good.


Building 2.49.1 should atart soon. Everything has been checked in now. A 
little late but we do what we can with the limited resourced at hand.


FRG

John Duncan wrote:

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the Mozilla 
API decimation.


Forgive me if I have misunderstood the meeting minutes, but since the nightly 
release channel will continue to support things like XUL overlays, legacy 
extensions, webextension eperiments, etc. [0], why don't you continue to 
ingest & build off of mozilla-central?


Is the plan to eventually switch back from ESR once bug fixes are landed and 
the API removal spree has subsided? Or will the API changes break more 
essential SeaMonkey features as well? It seems as if DOM 
Inspector/Lightning/Chatzilla all still seem to be working in current 2.54 
builds, which is a good sign.


Total removal of complete themes could be a larger issue, though.

Thanks for your continued support.

[0]: https://wiki.mozilla.org/Add-ons/Firefox57

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[John Duncan]

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the 
Mozilla API decimation.


Forgive me if I have misunderstood the meeting minutes, but since the 
nightly release channel will continue to support things like XUL 
overlays, legacy extensions, webextension eperiments, etc. [0], why 
don't you continue to ingest & build off of mozilla-central?


Is the plan to eventually switch back from ESR once bug fixes are landed 
and the API removal spree has subsided? Or will the API changes break 
more essential SeaMonkey features as well? It seems as if DOM 
Inspector/Lightning/Chatzilla all still seem to be working in current 
2.54 builds, which is a good sign.


Total removal of complete themes could be a larger issue, though.

Thanks for your continued support.

[0]: https://wiki.mozilla.org/Add-ons/Firefox57
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[Frank-Rainer Grahl]

Please send me an email for the download link.

FRG

TCW wrote:

On 9/8/2017 11:24 AM, Frank-Rainer Grahl wrote:
I have a pacthes up 2.54 but it still needs at least two bugs fixed before I 
would call it usable.


I am using a 2.53 with a few fixes still in review applied. If you want it 
shoot me a mail Can bake any platform but Linux i686.


FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64 akalla 
built but it seems to be corrupt. Tried google but nothing's coming up. 
2.51 is the newest I could fine. Anyone have the x64 2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because it is 
over 72 MG. I think is the last nightly build that I downloaded.  The only 
other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a hosting 
place is happening (https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) 
but it might be a while. I was already playing with the 2.54a builds but 
the amount of stuff busted in it is forcing me to revert back.


Sure, I'd like to try out x64 2.53 if you can throw it up to Zippyshare or 
some such place? FTP? Google Drive? What's easiest for you?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[TCW]

On 9/8/2017 11:24 AM, Frank-Rainer Grahl wrote:
I have a pacthes up 2.54 but it still needs at least two bugs fixed 
before I would call it usable.


I am using a 2.53 with a few fixes still in review applied. If you want 
it shoot me a mail Can bake any platform but Linux i686.


FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64 
akalla built but it seems to be corrupt. Tried google but nothing's 
coming up. 2.51 is the newest I could fine. Anyone have the x64 
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because 
it is over 72 MG. I think is the last nightly build that I 
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a 
hosting place is happening 
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be 
a while. I was already playing with the 2.54a builds but the amount of 
stuff busted in it is forcing me to revert back.


Sure, I'd like to try out x64 2.53 if you can throw it up to Zippyshare 
or some such place? FTP? Google Drive? What's easiest for you?

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[Frank-Rainer Grahl]

I have a pacthes up 2.54 but it still needs at least two bugs fixed before I 
would call it usable.


I am using a 2.53 with a few fixes still in review applied. If you want it 
shoot me a mail Can bake any platform but Linux i686.


FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64 akalla 
built but it seems to be corrupt. Tried google but nothing's coming up. 
2.51 is the newest I could fine. Anyone have the x64 2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because it is 
over 72 MG. I think is the last nightly build that I downloaded.  The only 
other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a hosting place 
is happening (https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it 
might be a while. I was already playing with the 2.54a builds but the amount 
of stuff busted in it is forcing me to revert back.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[TCW]

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64 
akalla built but it seems to be corrupt. Tried google but nothing's 
coming up. 2.51 is the newest I could fine. Anyone have the x64 2.52b 
build handy?


I have 2.53a1, but this newsgroup would not let me attach it because it 
is over 72 MG. I think is the last nightly build that I downloaded.  The 
only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a hosting 
place is happening 
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be a 
while. I was already playing with the 2.54a builds but the amount of 
stuff busted in it is forcing me to revert back.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

[S Slicer]

TCW wrote:
Before l10n.mozilla-community.org went down, I had the 2.52b x64 akalla 
built but it seems to be corrupt. Tried google but nothing's coming up. 
2.51 is the newest I could fine. Anyone have the x64 2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because it 
is over 72 MG. I think is the last nightly build that I downloaded.  The 
only other 64-bit one that I have saved is 2.45.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey