#1025: account to upload to downloads.osgeo.org/postgis
---------------------------+------------------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone:
Component: Systems Admin | Keywords:
---------------------------+------------------------------------------------
Can I have account/rights to upload to http://download.osgeo.org/postgis/
I'll need it soon to upload the latest windows stable builds for upcoming
2.0.2 and 1.5.8.
Not sure it matters I currently lend my account for old postgis to the
buildbots we have Winnie and Debbie (others may be born soon). They too
will probably be uploading things. Like debbie will be uploading the
latest tarballs and winnie might be uploading the buildbot windows
experimental binaries.
Is it customary to give bots their own accounts or are they allowed to use
mine? If they need their own, they'll also need a subversion account to
post updates (though I think I have rights to do that)
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1025>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1025: account to upload to downloads.osgeo.org/postgis
---------------------------+------------------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone:
Component: Systems Admin | Resolution: fixed
Keywords: download |
---------------------------+------------------------------------------------
Changes (by warmerdam):
* keywords: => download
* status: new => closed
* resolution: => fixed
Comment:
Regina,
I have added account "robe" to the list that can ssh/sftp into
download.osgeo.org (and a few other systems like the ProjectsVM).
I have also added group write permissions on
/osgeo/download/postgis/source in the hopes that you will be able to write
there. If not, Paul or I should be able to alter things as needed.
I don't have a strong answer to the accounts for robot uploads. I think
you can decide yourself how to handle it, as long as the account is setup
with an email address that ends up at a human who is somewhat responsible
for the account.
Note that uploading nightly binary builds send to fill our backup system
up with cruft.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1025#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1025: account to upload to downloads.osgeo.org/postgis
---------------------------+------------------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone:
Component: Systems Admin | Resolution: fixed
Keywords: download |
---------------------------+------------------------------------------------
Comment(by robe):
As far as the nightly builds go - they all have the same name (we don't
date interims) so it shouldn't fill up.
We just overwrite the same 2.1, 2.0, 1.5 SVN branches.
For the windows binaries, I'll probably just keep those on my server (and
change the download page to point to my server uploading 200 MB each time
a change is getting a bit much) or upload once a week. Those get
overwritten too. Just one for each permutation of PostgreSQL 9.0 x64),9.1
(x64),9.2 (x32, x64) (for the 2.0 and 2.1 branches currently) -- so 10 in
all.
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1025#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#1025: account to upload to downloads.osgeo.org/postgis
---------------------------+------------------------------------------------
Reporter: robe | Owner: sac@…
Type: task | Status: closed
Priority: normal | Milestone:
Component: Systems Admin | Resolution: fixed
Keywords: download |
---------------------------+------------------------------------------------
Comment(by warmerdam):
Regina - replacing the existing one in this fashion works nicely, thanks!
--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/1025#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.