[AG-DEV] Potential bug in agpm or Node management?

[Thomas D. Uram]

We've always named service packages with a '.zip', and have
been moving toward letting them be named either 'zip' or 'agpkg'
(or 'agpkg3' in AG3).  The service manager, however, only looks for
service packages with a 'zip' extension.  So, when you ran
agpy against the agpkg3 file, it did actually install it; it just wasn't
picked up by node management.

I've committed a fix to AGServiceManager.py so that it will
pick up agpkg or agpkg3 extensions also. 

Meanwhile, the workaround is to use 'zip' for service
packages.

Tom


On 8/20/06 11:41 PM, Rhys Hawkins wrote:
> Hi,
>
> I just noticed that if I create a node service, but call it an agpkg3, that double
> click claims to have installed it but the new node service doesn't show up in the
> list of services when trying to add a new service in the Node Management dialog.
>
> Similarly if I run:
>
> runag3.py agpm3.py -s -p MyService.agpkg3
>
> It says its installed but is not visible in the list of services, whereas if I
> rename the file to .zip and do:
>
> runag3.py agpm3.py -s -p MyService.zip
>
> Everything works.
>
> Bug or should I not use the agpkg3 extension?
>
> Versions: 
> Windows XP SP2, AGTK3.02, dependencies as per accessgrid.org web page.
>
> Cheers,
>     Rhys
>
>
>