A problem was reported via Gitter chat that an RPM was not able to be located. The RPMs are being produced and synced to the S3 repo but not showing up on the release listing on the page. The location of that listing code is https://github.com/ngageoint/geowave/blob/master/docs/content/packages.html#L165
@larpar 14:23
@rfecher : We are unable to locate geowave-core.201605201930.noarch.rpm. Could you please point us to that resource?
@rfecher 16:14
@larpar I'm not entirely sure, but @spohnan is looking into it now
larpar @larpar 16:22
@spohnan : BTW, this is for the release, not a SNAPSHOT.
Andy Spohn @spohnan 17:33
Thank you for pointing out the problem. I'm guessing you're looking at the repo listing page and noticed that artifact is missing from the list - http://ngageoint.github.io/geowave/packages.html
Tracing through our build pipeline the rpm seems to have been staged to the S3 bucket I'm going to guess there's something up with my home-grown bucket listing script at the moment. This is not the solution to the problem you're reporting but in answer to the location of that artifact the URL is https://s3.amazonaws.com/geowave-rpms/release/noarch/geowave-core.201605201930.noarch.rpm
A problem was reported via Gitter chat that an RPM was not able to be located. The RPMs are being produced and synced to the S3 repo but not showing up on the release listing on the page. The location of that listing code is https://github.com/ngageoint/geowave/blob/master/docs/content/packages.html#L165
@larpar 14:23
@rfecher : We are unable to locate geowave-core.201605201930.noarch.rpm. Could you please point us to that resource?
@rfecher 16:14
@larpar I'm not entirely sure, but @spohnan is looking into it now
larpar @larpar 16:22
@spohnan : BTW, this is for the release, not a SNAPSHOT.
Andy Spohn @spohnan 17:33
Thank you for pointing out the problem. I'm guessing you're looking at the repo listing page and noticed that artifact is missing from the list - http://ngageoint.github.io/geowave/packages.html
Tracing through our build pipeline the rpm seems to have been staged to the S3 bucket I'm going to guess there's something up with my home-grown bucket listing script at the moment. This is not the solution to the problem you're reporting but in answer to the location of that artifact the URL is https://s3.amazonaws.com/geowave-rpms/release/noarch/geowave-core.201605201930.noarch.rpm