Regression reports at regression-logs/developer in-accessible.
I get permission denied errors when trying to look at the regression outputs in .../developer/output. Seems someone forgot to make that directory+files world readable. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
Rene Rivera <grafik.list@redshift-software.com> writes:
I get permission denied errors when trying to look at the regression outputs in .../developer/output. Seems someone forgot to make that directory+files world readable.
There's a serious usability problem with uploading files to SF: you have to consciously make all files world readable and group writable. Does anyone know a way around that? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams wrote:
Rene Rivera <grafik.list@redshift-software.com> writes:
I get permission denied errors when trying to look at the regression outputs in .../developer/output. Seems someone forgot to make that directory+files world readable.
There's a serious usability problem with uploading files to SF: you have to consciously make all files world readable and group writable. Does anyone know a way around that?
Only way I can think of is to put an intermediate script on the web server that accepts uploads and ensures that the permissions are all correct. But doing that instead of using scp makes automating the test machines much harder. And on a related note... -bash-2.05b$ du -ks regression-logs du: cannot change to directory `regression-logs/output': Permission denied du: cannot change to directory `regression-logs/output2/mbergal': Permission denied du: cannot change to directory `regression-logs/output2/metacomm': Permission denied 899356 regression-logs So: (a) it's not just that it's not world readable, it's also not readable at all :-( and (b) yes that's 900Meg just on the regression logs... Just *slightly* above the 100Meg quota ;-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
On Fri, Jul 23, 2004 at 10:42:21AM -0500, Rene Rivera wrote:
David Abrahams wrote:
Rene Rivera <grafik.list@redshift-software.com> writes:
I get permission denied errors when trying to look at the regression outputs in .../developer/output. Seems someone forgot to make that directory+files world readable.
There's a serious usability problem with uploading files to SF: you have to consciously make all files world readable and group writable. Does anyone know a way around that?
Only way I can think of is to put an intermediate script on the web server that accepts uploads and ensures that the permissions are all correct. But doing that instead of using scp makes automating the test machines much harder.
If you can accept that all boost files are also world readable on your machine then you can use scp's `-p' switch that will preserve the time stamps and access modes. (Disclaimer: I never tested this feature with a Windows scp client. And I don't have an SF account whence I didn't try whether it actually works with the SF server.) Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html
Rene Rivera writes:
I get permission denied errors when trying to look at the regression outputs in .../developer/output.
Oh, sorry for disturbance; fixed now, with the caveat that http://www.boost.org/regression-logs/developer/ now redirects you to http://www.meta-comm.com/engineering/boost-regression/ (it became cost-prohibitive to upload the Boost-wide results to SourceForge). -- Aleksey Gurtovoy MetaCommunications Engineering
participants (4)
-
Aleksey Gurtovoy -
Christoph Ludwig -
David Abrahams -
Rene Rivera