Re: Update mechanism for Raqcop.

David W Studeman wrote:

 
>> Everything is in general-functions.pl and updates.cgi.
>> 
>> Alternatively we could host the cobalt updates on SF, but that would
>> require renaming the update to something like
>> ipcop-<version>-update.cobalt.tgz.gpg
>> 
>> That could prove to be an interesting exercise...
>> 
>> 
>> Olaf
>> 
> 
> OK, I got Brian to allow wget and perl for the one directory and it
> doesn't throw errors when refreshing update. Brian is very conscious
> about allowing programs to perform get functions on his servers but he
> agreed to allow gets from the one directory. Your alternative sounds
> good as well. It may not be a bad idea to replace 486 in the update name
> in any case. If there was ever a case where an x86 was not 100% x86 this
> would be it.
> 
> Hopefully I will have it sorted by the time I can actually build 1.9.21
> (Python error, other topic).
> 

I set up the build to automatically name the update by substituting cobalt 
for i486 and in general functions had to change machine to cobalt so it will 
recognize the update. 

I updated 1.9.20 in a test machine to 1.9.21 and it worked fine doing it 
manually by upload but before that I tried to refresh updates and it doesn't 
show as explained ahead.

Where I have difficulty is with automation. I put the 1.9.21 signed file in 
updates along with a made up 1.9.21 release notes that at least says "IPCop 
1.4.21 is available" on the top of the file and put the xml file in patches 
which is just a renamed information.xml to 1.9.21.xml. Whenever I refreshed 
updates, I would look in /var/ipcop/patches and it still showed 
available.xml as 1.9.20. If I clean out the patches directory on the site 
and hit refresh it fails so I know the system is looking there.

What makes the system know there is something newer than what you are 
running? 
-- 
Dave
http://www.raqcop.com


------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT 
space for its ease of implementation, lower cost, and increased 
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/