On 12/10/2017 01:48, David E. Ross wrote:
> On 10/11/2017 2:24 PM, Rob Steinmetz wrote:
>> I have a server that had a problem with a share. I think I have fixed
>> that but my users cannot access their existing SeaMonkey Profiles. They
>> are located on a a SAMBA [homes] share on an Ubuntu 16.04
On 10/11/2017 2:24 PM, Rob Steinmetz wrote:
> I have a server that had a problem with a share. I think I have fixed
> that but my users cannot access their existing SeaMonkey Profiles. They
> are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in
> a directory called
I have a server that had a problem with a share. I think I have fixed
that but my users cannot access their existing SeaMonkey Profiles. They
are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in
a directory called ~/.seamonkey.
In the past I have been able to conned to
On 11/10/2017 6:12 PM, Frank-Rainer Grahl wrote:
So using .1 does not distinguish the official build from
Adrian's ESR-based builds.
1 will be release channel and 2 it will distingush it from his 2.49
(without the .1)
FRG
Frank-Rainer, over this recent period where the SeaMonkey-Project has
> So using .1 does not distinguish the official build from
> Adrian's ESR-based builds.
>
1 will be release channel and 2 it will distingush it from his 2.49
(without the .1)
FRG
Mason83 wrote:
On 10/10/2017 08:38, Frank-Rainer Grahl wrote:
You can update Adrians build to the official
There will still be 2.49.x ESR releases. Plan is/was to do a 2.56 ESR
later but with so much broken and the infrastucture failing it will be
some time.
FRG
Ant wrote:
https://blog.seamonkey-project.org/2017/10/11/re-future-releases/
___
6 matches
Mail list logo
