| Re: [eclipse-mirrors] (8422) rsync ERROR on 2012.11.30-15:48:16] |
Hi, On Thu, Apr 18, 2013 at 09:16:35AM -0400, Denis Roy wrote: > On _our_ side, no. OK. Since this means many warnings sent to me, I will ignore those mails. > We do not "care" because, if the project teams want users to download > their bits, it will be quickly apparent that there is a problem and > they will fix their permissions. There are problems that are not related to permissions. Furthermore, there are several ways to deal with permission errors without having mirror admins see them. > However, I do care about errors on _your_ side if _you_ care about > errors on your side. Good. Feel free to tell us when something goes wrong. I guess we will not notice anymore because of the ignored mails from our scripts. > I was under the assumption that most mirrors simply sent errors to > /dev/null since, as above, if there were permissions problems, the > onus is on us to fix them. This may be true for most mirrors (although I doubt it), but it seems very foolish to me. Error messages are meant to be read. As said, there are more errors than permission errors. > I've opened this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=405981 Let's hope a good solution pops up. I suggest to have two repositories: Eclipse developers push to Repo A and do what they want (permission-wise). Repo B is mirrored from Repo A using hardlinks. Here a non-root user is used to access the files, so that errors can be detected here. Furthermore, there will be no inaccessible files in Rebo B. Repo B is served to the public mirrors. I think I mentioned this already... Best regards, -- Carsten Otto otto@xxxxxxxxxxxxxxxxxxxxxxxxx LuFG Informatik 2 http://verify.rwth-aachen.de/otto/ RWTH Aachen phone: +49 241 80-21211
Attachment:
signature.asc
Description: Digital signature