rg now works correctly
Ok, then I will change the AOO 4.0 Update URL to
https://ooo-updates.apache.org/...
I will also move the corresponding XML file accessed by the update
functionality to the new location.
Best regards, Oliver.
but
http://updates.openoffice.org/ <https://updates
tp://ooo-updates.apache.org <https://ooo-updates.apache.org>
https://ooo-updates.apache.org now works correctly
but
http://updates.openoffice.org/ <https://updates.openoffice.org/>
https://updates.openoffice.org/ gives a 404, it seems still to be pointing
at ^/openoffice/projects/updates
Hi,
On 11.06.2013 18:21, janI wrote:
Hi
I have now filed an issue:
https://issues.apache.org/jira/browse/INFRA-6378
I will follow up on it (actually already done on #asfinfra)
Good news is that the cert was just reported to be in our hands. It still
needs to be deployed and work with our set
Hi
I have now filed an issue:
https://issues.apache.org/jira/browse/INFRA-6378
I will follow up on it (actually already done on #asfinfra)
Good news is that the cert was just reported to be in our hands. It still
needs to be deployed and work with our setup.
rgds
jan I.
On 11 June 2013 13:47
Hi,
On 11.06.2013 13:29, Rob Weir wrote:
On Tue, Jun 11, 2013 at 7:08 AM, Oliver-Rainer Wittmann
wrote:
Hi,
On 11.06.2013 12:55, janI wrote:
On 6 June 2013 18:33, Kay Schenk wrote:
[snip]
It seems I was too fast (or more correctly too slow), at least the
agrement
disapeared, and I have
On Tue, Jun 11, 2013 at 7:08 AM, Oliver-Rainer Wittmann
wrote:
> Hi,
>
>
> On 11.06.2013 12:55, janI wrote:
>>
>> On 6 June 2013 18:33, Kay Schenk wrote:
>>
>> [snip]
>>
>>
>>
>> It seems I was too fast (or more correctly too slow), at least the
>> agrement
>> disapeared, and I have been asked to
Hi,
On 11.06.2013 12:55, janI wrote:
On 6 June 2013 18:33, Kay Schenk wrote:
[snip]
It seems I was too fast (or more correctly too slow), at least the agrement
disapeared, and I have been asked to file a jira, for this part of the
https upgrade, and specifically not for the cert part (which
Hi,
damn - I just noticed that I have given the wrong fallback URL.
It must be https://ooo-updates.apache.org/
instead of https://ooo-updates.openoffice.org/
Best regards, Oliver.
On 05.06.2013 11:05, Oliver-Rainer Wittmann wrote:
Hi,
sorry for top-posting, but I think it makes sense to
gt;>>>>
> > > >>>>>>> Hi,
> > > >>>>>>>
> > > >>>>>>> sorry for top-posting, but I think it makes sense to clean up
> > some
> > > >>>>> things.
> > > >>&g
t;> On 5 June 2013 11:05, Oliver-Rainer Wittmann <
> > >>> orwittm...@googlemail.com
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>&
>>>>>> wrote:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> sorry for top-posting, but I think it makes sense to clean up some
> >>>>> things.
> >>>>>>>
> &g
t;>>
>>>>>>> sorry for top-posting, but I think it makes sense to clean up some
>>>>> things.
>>>>>>>
>>>>>>> Some facts and my opinions:
>>>>>>> (1)
>>>>>>> Fact: I
> > > >> >wrote:
> > > > >> >
> > > > >> >> Hi,
> > > > >> >>
> > > > >> >> sorry for top-posting, but I think it makes sense to clean up
> > some
> > > > >> thi
t; > >> >>
> > > >> >> sorry for top-posting, but I think it makes sense to clean up
> some
> > > >> things.
> > > >> >>
> > > >> >> Some facts and my opinions:
> > > >> >> (1)
> &g
n up some
> > >> things.
> > >> >>
> > >> >> Some facts and my opinions:
> > >> >> (1)
> > >> >> Fact: In communication with infra, infra had proposed
> > >> >> https://updates.openoffice.**org/ &
>> >> things.
>> >> >>
>> >> >> Some facts and my opinions:
>> >> >> (1)
>> >> >> Fact: In communication with infra, infra had proposed
>> >> >> https://updates.openoffice.**org/ <https://updates.op
glemail.com
> >> >wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> sorry for top-posting, but I think it makes sense to clean up some
> >> things.
> >> >>
> >> >> Some facts and my opinion
;> sorry for top-posting, but I think it makes sense to clean up some
>> things.
>> >>
>> >> Some facts and my opinions:
>> >> (1)
>> >> Fact: In communication with infra, infra had proposed
>> >> https://updates.openoffice.**org/ <htt
s.
> >>
> >> Some facts and my opinions:
> >> (1)
> >> Fact: In communication with infra, infra had proposed
> >> https://updates.openoffice.**org/ <https://updates.openoffice.org/> (
> >> https://ooo-updates.**openoffice.org/<
> https://o
nication with infra, infra had proposed
>> https://updates.openoffice.**org/ <https://updates.openoffice.org/> (
>> https://ooo-updates.**openoffice.org/<https://ooo-updates.openoffice.org/>as
>> the backup) as the URL for the resources accessed by the update
>>
openoffice.**org/ <https://updates.openoffice.org/> (
> https://ooo-updates.**openoffice.org/<https://ooo-updates.openoffice.org/>as
> the backup) as the URL for the resources accessed by the update
> functionality by AOO 4.0 and later. Nobody objects.
> My opinion: I think we should go for it.
>
Hi,
sorry for top-posting, but I think it makes sense to clean up some things.
Some facts and my opinions:
(1)
Fact: In communication with infra, infra had proposed
https://updates.openoffice.org/ (https://ooo-updates.openoffice.org/ as
the backup) as the URL for the resources accessed by the
13 16:43, janI wrote:
>>>
>>> Hi.
>>>>
>>>> I have asked by my infra collegaues, to ensuere we (AOO) have consensus
>>>> on
>>>> how to handle updates.openoffice.org
>>>>
>>>> I nobody objects I will assume
term stable". The URL is an artifact of the CMS
> >>> 3) We're looking for a stable URL. One could be
> >>> https://updates.openoffice.org**, but that requires an SSL cert for
> >>> *.openoffice.org. But will that be supported in time for the AOO 4
g> is not
>>>> HTTPS.
>>>>
>>>> 2) The URL
>>>> https://ooo-site.openoffice.**apache.org<https://ooo-site.openoffice.apache.org>
>>>> supports SSL, but is
>>>> not considered "long term stable". The URL is an
ffice.org> is not
>>> HTTPS.
>>>
>>> 2) The URL
>>> https://ooo-site.openoffice.**apache.org<https://ooo-site.openoffice.apache.org>
>>> supports SSL, but is
>>> not considered "long term stable". The URL is an artifact of th
; https://ooo-site.openoffice.**apache.org<https://ooo-site.openoffice.apache.org>
>> supports SSL, but is
>> not considered "long term stable". The URL is an artifact of the CMS
>> 3) We're looking for a stable URL. One could be
>> https://updates.open
e looking for a stable URL. One could be
https://updates.openoffice.org, but that requires an SSL cert for
*.openoffice.org. But will that be supported in time for the AOO 4.0
release?
4) Backup plan is updates.openoffice.apache.org, which could be
supported via SSL today, using the *.apache.org cert.
t;
>>>> Hi.
>>>>
>>>> I have asked by my infra collegaues, to ensuere we (AOO) have consensus
>>>> on
>>>> how to handle updates.openoffice.org
>>>>
>>>> I nobody objects I will assume lazy consensus in 72 hours from no
Hi,
On 03.06.2013 13:50, janI wrote:
On 3 June 2013 11:43, Oliver-Rainer Wittmann wrote:
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus
On 3 June 2013 11:43, Oliver-Rainer Wittmann wrote:
> Hi,
>
> On 02.06.2013 16:43, janI wrote:
>
>> Hi.
>>
>> I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
>> how to handle updates.openoffice.org
>>
>> I nobody objects I
Hi,
On 02.06.2013 16:43, janI wrote:
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus in 72 hours from now and
1) create trunk/ooo-site/upates
My understandings of the
On Sun, Jun 2, 2013 at 7:43 AM, janI wrote:
> Hi.
>
> I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
> how to handle updates.openoffice.org
>
> I nobody objects I will assume lazy consensus in 72 hours from now and
>
> 1) create trunk/ooo-si
Hi.
I have asked by my infra collegaues, to ensuere we (AOO) have consensus on
how to handle updates.openoffice.org
I nobody objects I will assume lazy consensus in 72 hours from now and
1) create trunk/ooo-site/upates
2) let https://updates.openoffice.org point to trunk/ooo-site/update
rgds
34 matches
Mail list logo
