You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@googlemail.com> on 2012/02/23 17:59:46 UTC
Re: [CODE] update services
On 1/27/12 8:06 PM, Ariel Constenla-Haile wrote:
> Hi Jürgen,
>
> On Fri, Jan 27, 2012 at 07:41:58PM +0100, Jürgen Schmidt wrote:
>>> Unfortunately I cannot test how this is implemented because the feature
>>> depends on functionality removed in the IP clearance (libneon), and
>>> I don't have a pre-ip-clearance build to test.
>>>
>>>
>> We are working on the replacement for neon with libserf. It's the last big
>> missing feature for IP clearance. We have to reimplement the UCP and have
>> to integrate 3 libs (apr, apr-util and serf) in our buil env. It's mainly
>> Oliver and Andre who are working on this right now.
>
>
> As I work in Linux, I managed to do the trick with:
>
> * configure --with-system-neon will enable the WebDav content provider
> * export BUILD_SPECIAL=YES because the update component is not installed
> without that env. var. set, vid. scp2/util/makefile.mk:
>
> .IF "$(BUILD_SPECIAL)"!=""
> SCP1FILES += \
> module_onlineupdate.par \
> file_onlineupdate.par
> .ENDIF
>
>
> Side note: that BUILD_SPECIAL adds other stuff. It should be replaced
> with an --enable-update-service or the like.
did you have worked on this already?
>
>
>> If the update feature is based on the http/WebDAV UCP, we can probably test
>> it soon.
>
> yes, it does use WebDAV UCP, the UpdateInformationProvider sends a request
> as explained in
> http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request
> see
> /mnt/build/openoffice/apache/trunk/main/extensions/source/update/feed/updatefeed.cxx
> specially the CTOR UpdateInformationProvider::UpdateInformationProvider
>
> /mnt/build/openoffice/apache/trunk/main/extensions/source/update/check/updateprotocol.cxx
> specially checkForUpdates
Now where we have the neon replacement in place we should try to bring
up a working online update service. I think it would be very useful for
our upcoming release to promote it to our users. A basic version should
be enough for now to simply inform our users.
Any volunteers to drive this forward?
Juergen
>
>
> Regards
Re: [CODE] update services
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 2/24/12 6:08 AM, Ariel Constenla-Haile wrote:
> On Thu, Feb 23, 2012 at 05:59:46PM +0100, Jürgen Schmidt wrote:
>> On 1/27/12 8:06 PM, Ariel Constenla-Haile wrote:
>>> Hi Jürgen,
>>>
>>> On Fri, Jan 27, 2012 at 07:41:58PM +0100, Jürgen Schmidt wrote:
>>>>> Unfortunately I cannot test how this is implemented because the feature
>>>>> depends on functionality removed in the IP clearance (libneon), and
>>>>> I don't have a pre-ip-clearance build to test.
>>>>>
>>>>>
>>>> We are working on the replacement for neon with libserf. It's the last big
>>>> missing feature for IP clearance. We have to reimplement the UCP and have
>>>> to integrate 3 libs (apr, apr-util and serf) in our buil env. It's mainly
>>>> Oliver and Andre who are working on this right now.
>>>
>>>
>>> As I work in Linux, I managed to do the trick with:
>>>
>>> * configure --with-system-neon will enable the WebDav content provider
>>> * export BUILD_SPECIAL=YES because the update component is not installed
>>> without that env. var. set, vid. scp2/util/makefile.mk:
>>>
>>> .IF "$(BUILD_SPECIAL)"!=""
>>> SCP1FILES += \
>>> module_onlineupdate.par \
>>> file_onlineupdate.par
>>> .ENDIF
>>>
>>>
>>> Side note: that BUILD_SPECIAL adds other stuff. It should be replaced
>>> with an --enable-update-service or the like.
>>
>> did you have worked on this already?
>
> Committed as revision 1293078
> http://svn.apache.org/viewvc?view=revision&revision=1293078
> Online Update is enabled by default. It can be turned off with
> --disable-online-update
> --enable-online-update=no
>
>
> Tested it by changing the URL to
> http://people.apache.org/~arielch/ProductUpdateService/check.Update.feed
> and both checking for updates and downloading the tar file worked fine.
great, one item less on my list.
Thanks
Juergen
>
>>
>> Now where we have the neon replacement in place we should try to
>> bring up a working online update service. I think it would be very
>> useful for our upcoming release to promote it to our users. A basic
>> version should be enough for now to simply inform our users.
>>
>> Any volunteers to drive this forward?
>
> I guess that first it has to be decided where it would be hosted, this
> will determinate the language used to implement the service (Java, PHP,
> etc.).
>
>
> Regards
Re: [CODE] update services
Posted by Ariel Constenla-Haile <ar...@apache.org>.
On Thu, Feb 23, 2012 at 05:59:46PM +0100, Jürgen Schmidt wrote:
> On 1/27/12 8:06 PM, Ariel Constenla-Haile wrote:
> >Hi Jürgen,
> >
> >On Fri, Jan 27, 2012 at 07:41:58PM +0100, Jürgen Schmidt wrote:
> >>>Unfortunately I cannot test how this is implemented because the feature
> >>>depends on functionality removed in the IP clearance (libneon), and
> >>>I don't have a pre-ip-clearance build to test.
> >>>
> >>>
> >>We are working on the replacement for neon with libserf. It's the last big
> >>missing feature for IP clearance. We have to reimplement the UCP and have
> >>to integrate 3 libs (apr, apr-util and serf) in our buil env. It's mainly
> >>Oliver and Andre who are working on this right now.
> >
> >
> >As I work in Linux, I managed to do the trick with:
> >
> >* configure --with-system-neon will enable the WebDav content provider
> >* export BUILD_SPECIAL=YES because the update component is not installed
> > without that env. var. set, vid. scp2/util/makefile.mk:
> >
> >.IF "$(BUILD_SPECIAL)"!=""
> >SCP1FILES += \
> > module_onlineupdate.par \
> > file_onlineupdate.par
> >.ENDIF
> >
> >
> >Side note: that BUILD_SPECIAL adds other stuff. It should be replaced
> >with an --enable-update-service or the like.
>
> did you have worked on this already?
Committed as revision 1293078
http://svn.apache.org/viewvc?view=revision&revision=1293078
Online Update is enabled by default. It can be turned off with
--disable-online-update
--enable-online-update=no
Tested it by changing the URL to
http://people.apache.org/~arielch/ProductUpdateService/check.Update.feed
and both checking for updates and downloading the tar file worked fine.
>
> Now where we have the neon replacement in place we should try to
> bring up a working online update service. I think it would be very
> useful for our upcoming release to promote it to our users. A basic
> version should be enough for now to simply inform our users.
>
> Any volunteers to drive this forward?
I guess that first it has to be decided where it would be hosted, this
will determinate the language used to implement the service (Java, PHP,
etc.).
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: [CODE] update services
Posted by Kay Schenk <ka...@gmail.com>.
On Fri, Feb 24, 2012 at 9:40 AM, Kay Schenk <ka...@gmail.com> wrote:
>
>
> 2012/2/23 Jürgen Schmidt <jo...@googlemail.com>
>
>> On 2/24/12 1:03 AM, Ariel Constenla-Haile wrote:
>>
>>> Hi *,
>>>
>>> On Thu, Feb 23, 2012 at 03:41:40PM -0800, Kay Schenk wrote:
>>>
>>>> Now where we have the neon replacement in place we should try to bring
>>>>> up
>>>>> a working online update service. I think it would be very useful for
>>>>> our
>>>>> upcoming release to promote it to our users. A basic version should be
>>>>> enough for now to simply inform our users.
>>>>>
>>>>> Any volunteers to drive this forward?
>>>>>
>>>>> Juergen
>>>>>
>>>>>
>>>> Juergen--
>>>>
>>>> I would not exactly sayy I am volunteering, but I do have some questions
>>>> about this. I looked at the spec that was posted on --
>>>>
>>>> http://wiki.services.**openoffice.org/wiki/Update_**
>>>> Notification_Protocol#Request<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request>
>>>>
>>>> specifically, the "Update Document and Feeds" portion. Looking at just
>>>> the
>>>> "simplest possible reply". This, to me, implies that we should have
>>>> <inst...> entries for all conceivable platforms etc. Does anyone know
>>>> how
>>>> this "feed" file was generated in the past?
>>>>
>>>> Conceivably we could of course use "cron" and perl to generate the feed
>>>> file, and use it as the URL, but where to get the needed info??? I'll
>>>> see
>>>> if I can contact one of the former distribution folks on this. I've
>>>> spent
>>>> some time thinking about it, but that's as far as I got.
>>>>
>>>
>>> My guessing is that this was handled by a web service, and the data was
>>> dynamically generated upon the http request.
>>>
>>
> hmmm...OK. I was thinking more of like a nightly update to the XML feed.
> Still we need to investigate where the "inputs" (version, distribution
> number, languages,etc.) and how to get to them.
>
>
>>
>>>
>> that is what I am assuming as well. But we can start with a static page
>> if that is possible.
>>
>
> Based on Ariel's successes, this should be easy enough. we can use Dave's
> suggestion, slightly modified, and put the XML feed at --
>
> www.openoffice.org/updates/check.update
> <http://www.openoffice.org/updates/check.html>
>
> or something. (I need to see how the server responds to xml files.)
>
> If someone sends me details, I will be happy to put the feed file together
> a la Ariel's --
>
> (simple)
>
> http://people.apache.org/~arielch/ProductUpdateService/check.Update.win
>
> -- or --
>
> (atom)
>
> http://people.apache.org/~arielch/ProductUpdateService/check.Update.feed
>
> Which format will we be using?
>
>
>
>> Juergen
>>
>
>
>
> --
>
> ----------------------------------------------------------------------------------------
> MzK
>
> "Follow your bliss."
> -- attributed to Joseph Campbell
>
>
>
>
well...a tiny little breakthrough on the update service...
I did the following today--
* reassigned the old update service ( update36.services.openoffice.org) to
the current web server IP via my /etc/host file
* created a ProductUpdateService directory on www.openoffice.org and dumped
Ariel's atom feed file into the directory with the name check.Update
Now, on my exisiting OOo3.3, when I click "Check for updates", it *gets*
somewhere but of course, my system is expecting an ".rpm" package and not a
tar ball as spec'd in the DL url, so nothing happens. Really I didn't try
to find something reasonable, I just wanted to see if the ideas I had about
re-routing the connection would work.
Bottom line. I think we should have infra also make this DNS change. At
least folks with current "auto upgrades" will not continue to suffer from
NO conenctions AND we now have an place to test/implement the feed,
assuming we can get it in the right format for what we will be releasing
with 3.4.
Thoughts?
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell
Re: [CODE] update services
Posted by Kay Schenk <ka...@gmail.com>.
2012/2/23 Jürgen Schmidt <jo...@googlemail.com>
> On 2/24/12 1:03 AM, Ariel Constenla-Haile wrote:
>
>> Hi *,
>>
>> On Thu, Feb 23, 2012 at 03:41:40PM -0800, Kay Schenk wrote:
>>
>>> Now where we have the neon replacement in place we should try to bring up
>>>> a working online update service. I think it would be very useful for our
>>>> upcoming release to promote it to our users. A basic version should be
>>>> enough for now to simply inform our users.
>>>>
>>>> Any volunteers to drive this forward?
>>>>
>>>> Juergen
>>>>
>>>>
>>> Juergen--
>>>
>>> I would not exactly sayy I am volunteering, but I do have some questions
>>> about this. I looked at the spec that was posted on --
>>>
>>> http://wiki.services.**openoffice.org/wiki/Update_**
>>> Notification_Protocol#Request<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request>
>>>
>>> specifically, the "Update Document and Feeds" portion. Looking at just
>>> the
>>> "simplest possible reply". This, to me, implies that we should have
>>> <inst...> entries for all conceivable platforms etc. Does anyone know
>>> how
>>> this "feed" file was generated in the past?
>>>
>>> Conceivably we could of course use "cron" and perl to generate the feed
>>> file, and use it as the URL, but where to get the needed info??? I'll see
>>> if I can contact one of the former distribution folks on this. I've spent
>>> some time thinking about it, but that's as far as I got.
>>>
>>
>> My guessing is that this was handled by a web service, and the data was
>> dynamically generated upon the http request.
>>
>
hmmm...OK. I was thinking more of like a nightly update to the XML feed.
Still we need to investigate where the "inputs" (version, distribution
number, languages,etc.) and how to get to them.
>
>>
> that is what I am assuming as well. But we can start with a static page if
> that is possible.
>
Based on Ariel's successes, this should be easy enough. we can use Dave's
suggestion, slightly modified, and put the XML feed at --
www.openoffice.org/updates/check.update
<http://www.openoffice.org/updates/check.html>
or something. (I need to see how the server responds to xml files.)
If someone sends me details, I will be happy to put the feed file together
a la Ariel's --
(simple)
http://people.apache.org/~arielch/ProductUpdateService/check.Update.win
-- or --
(atom)
http://people.apache.org/~arielch/ProductUpdateService/check.Update.feed
Which format will we be using?
> Juergen
>
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell
Re: [CODE] update services
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 2/24/12 1:03 AM, Ariel Constenla-Haile wrote:
> Hi *,
>
> On Thu, Feb 23, 2012 at 03:41:40PM -0800, Kay Schenk wrote:
>>> Now where we have the neon replacement in place we should try to bring up
>>> a working online update service. I think it would be very useful for our
>>> upcoming release to promote it to our users. A basic version should be
>>> enough for now to simply inform our users.
>>>
>>> Any volunteers to drive this forward?
>>>
>>> Juergen
>>>
>>
>> Juergen--
>>
>> I would not exactly sayy I am volunteering, but I do have some questions
>> about this. I looked at the spec that was posted on --
>>
>> http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request
>>
>> specifically, the "Update Document and Feeds" portion. Looking at just the
>> "simplest possible reply". This, to me, implies that we should have
>> <inst...> entries for all conceivable platforms etc. Does anyone know how
>> this "feed" file was generated in the past?
>>
>> Conceivably we could of course use "cron" and perl to generate the feed
>> file, and use it as the URL, but where to get the needed info??? I'll see
>> if I can contact one of the former distribution folks on this. I've spent
>> some time thinking about it, but that's as far as I got.
>
> My guessing is that this was handled by a web service, and the data was
> dynamically generated upon the http request.
>
that is what I am assuming as well. But we can start with a static page
if that is possible.
Juergen
Re: [CODE] update services
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi *,
On Thu, Feb 23, 2012 at 03:41:40PM -0800, Kay Schenk wrote:
> > Now where we have the neon replacement in place we should try to bring up
> > a working online update service. I think it would be very useful for our
> > upcoming release to promote it to our users. A basic version should be
> > enough for now to simply inform our users.
> >
> > Any volunteers to drive this forward?
> >
> > Juergen
> >
>
> Juergen--
>
> I would not exactly sayy I am volunteering, but I do have some questions
> about this. I looked at the spec that was posted on --
>
> http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request
>
> specifically, the "Update Document and Feeds" portion. Looking at just the
> "simplest possible reply". This, to me, implies that we should have
> <inst...> entries for all conceivable platforms etc. Does anyone know how
> this "feed" file was generated in the past?
>
> Conceivably we could of course use "cron" and perl to generate the feed
> file, and use it as the URL, but where to get the needed info??? I'll see
> if I can contact one of the former distribution folks on this. I've spent
> some time thinking about it, but that's as far as I got.
My guessing is that this was handled by a web service, and the data was
dynamically generated upon the http request.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: [CODE] update services
Posted by Dave Fisher <da...@comcast.net>.
On Feb 23, 2012, at 3:41 PM, Kay Schenk wrote:
> 2012/2/23 Jürgen Schmidt <jo...@googlemail.com>
>
>> On 1/27/12 8:06 PM, Ariel Constenla-Haile wrote:
>>
>>> Hi Jürgen,
>>>
>>> On Fri, Jan 27, 2012 at 07:41:58PM +0100, Jürgen Schmidt wrote:
>>>
>>>> Unfortunately I cannot test how this is implemented because the feature
>>>>> depends on functionality removed in the IP clearance (libneon), and
>>>>> I don't have a pre-ip-clearance build to test.
>>>>>
>>>>>
>>>>> We are working on the replacement for neon with libserf. It's the last
>>>> big
>>>> missing feature for IP clearance. We have to reimplement the UCP and have
>>>> to integrate 3 libs (apr, apr-util and serf) in our buil env. It's mainly
>>>> Oliver and Andre who are working on this right now.
>>>>
>>>
>>>
>>> As I work in Linux, I managed to do the trick with:
>>>
>>> * configure --with-system-neon will enable the WebDav content provider
>>> * export BUILD_SPECIAL=YES because the update component is not installed
>>> without that env. var. set, vid. scp2/util/makefile.mk:
>>>
>>> .IF "$(BUILD_SPECIAL)"!=""
>>> SCP1FILES += \
>>> module_onlineupdate.par \
>>> file_onlineupdate.par
>>> .ENDIF
>>>
>>>
>>> Side note: that BUILD_SPECIAL adds other stuff. It should be replaced
>>> with an --enable-update-service or the like.
>>>
>>
>> did you have worked on this already?
>>
>>
>>
>>>
>>> If the update feature is based on the http/WebDAV UCP, we can probably
>>>> test
>>>> it soon.
>>>>
>>>
>>> yes, it does use WebDAV UCP, the UpdateInformationProvider sends a request
>>> as explained in
>>> http://wiki.services.**openoffice.org/wiki/Update_**
>>> Notification_Protocol#Request<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request>
>>> see
>>> /mnt/build/openoffice/apache/**trunk/main/extensions/source/**
>>> update/feed/updatefeed.cxx
>>> specially the CTOR UpdateInformationProvider::**UpdateInformationProvider
>>>
>>> /mnt/build/openoffice/apache/**trunk/main/extensions/source/**
>>> update/check/updateprotocol.**cxx
>>> specially checkForUpdates
>>>
>>
>> Now where we have the neon replacement in place we should try to bring up
>> a working online update service. I think it would be very useful for our
>> upcoming release to promote it to our users. A basic version should be
>> enough for now to simply inform our users.
>>
>> Any volunteers to drive this forward?
>>
>> Juergen
>>
>
> Juergen--
>
> I would not exactly sayy I am volunteering, but I do have some questions
> about this. I looked at the spec that was posted on --
>
> http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request
>
> specifically, the "Update Document and Feeds" portion. Looking at just the
> "simplest possible reply". This, to me, implies that we should have
> <inst...> entries for all conceivable platforms etc. Does anyone know how
> this "feed" file was generated in the past?
>
> Conceivably we could of course use "cron" and perl to generate the feed
> file, and use it as the URL, but where to get the needed info??? I'll see
> if I can contact one of the former distribution folks on this. I've spent
> some time thinking about it, but that's as far as I got.
Hi Kay,
When you finally understand how to create this file then I think we should put it in a new directory on the website so that it can be found at www.openoffice.org/updates/check.html. With that we have Infra point the old url to the new one. One less address hooked to Oracle.
Regards,
Dave
>
>
>
>>
>>
>>
>>>
>>> Regards
>>>
>>
>>
>
>
> --
> ----------------------------------------------------------------------------------------
> MzK
>
> "Follow your bliss."
> -- attributed to Joseph Campbell
Re: [CODE] update services
Posted by Kay Schenk <ka...@gmail.com>.
2012/2/23 Jürgen Schmidt <jo...@googlemail.com>
> On 1/27/12 8:06 PM, Ariel Constenla-Haile wrote:
>
>> Hi Jürgen,
>>
>> On Fri, Jan 27, 2012 at 07:41:58PM +0100, Jürgen Schmidt wrote:
>>
>>> Unfortunately I cannot test how this is implemented because the feature
>>>> depends on functionality removed in the IP clearance (libneon), and
>>>> I don't have a pre-ip-clearance build to test.
>>>>
>>>>
>>>> We are working on the replacement for neon with libserf. It's the last
>>> big
>>> missing feature for IP clearance. We have to reimplement the UCP and have
>>> to integrate 3 libs (apr, apr-util and serf) in our buil env. It's mainly
>>> Oliver and Andre who are working on this right now.
>>>
>>
>>
>> As I work in Linux, I managed to do the trick with:
>>
>> * configure --with-system-neon will enable the WebDav content provider
>> * export BUILD_SPECIAL=YES because the update component is not installed
>> without that env. var. set, vid. scp2/util/makefile.mk:
>>
>> .IF "$(BUILD_SPECIAL)"!=""
>> SCP1FILES += \
>> module_onlineupdate.par \
>> file_onlineupdate.par
>> .ENDIF
>>
>>
>> Side note: that BUILD_SPECIAL adds other stuff. It should be replaced
>> with an --enable-update-service or the like.
>>
>
> did you have worked on this already?
>
>
>
>>
>> If the update feature is based on the http/WebDAV UCP, we can probably
>>> test
>>> it soon.
>>>
>>
>> yes, it does use WebDAV UCP, the UpdateInformationProvider sends a request
>> as explained in
>> http://wiki.services.**openoffice.org/wiki/Update_**
>> Notification_Protocol#Request<http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request>
>> see
>> /mnt/build/openoffice/apache/**trunk/main/extensions/source/**
>> update/feed/updatefeed.cxx
>> specially the CTOR UpdateInformationProvider::**UpdateInformationProvider
>>
>> /mnt/build/openoffice/apache/**trunk/main/extensions/source/**
>> update/check/updateprotocol.**cxx
>> specially checkForUpdates
>>
>
> Now where we have the neon replacement in place we should try to bring up
> a working online update service. I think it would be very useful for our
> upcoming release to promote it to our users. A basic version should be
> enough for now to simply inform our users.
>
> Any volunteers to drive this forward?
>
> Juergen
>
Juergen--
I would not exactly sayy I am volunteering, but I do have some questions
about this. I looked at the spec that was posted on --
http://wiki.services.openoffice.org/wiki/Update_Notification_Protocol#Request
specifically, the "Update Document and Feeds" portion. Looking at just the
"simplest possible reply". This, to me, implies that we should have
<inst...> entries for all conceivable platforms etc. Does anyone know how
this "feed" file was generated in the past?
Conceivably we could of course use "cron" and perl to generate the feed
file, and use it as the URL, but where to get the needed info??? I'll see
if I can contact one of the former distribution folks on this. I've spent
some time thinking about it, but that's as far as I got.
>
>
>
>>
>> Regards
>>
>
>
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell