Erik Bray wrote: > On Mon, Jul 25, 2016 at 11:56 AM, Volker Braun <vbraun.n...@gmail.com> wrote: >> Please don't attach binaries to trac; Everything that is attached becomes >> forever part of the trac database. Which is already in the multi-gigabyte >> range IIRC. > > That's not exactly true--attachments are not stored in the database. > But the collection of attachments is quite large. I wouldn't be > worried about disk space though.
I thought that was rather a backup than a trac problem. In the past we were told to not attach *any* binary files because they would end up in some (VCS?) repo where they would remain forever even after deletion on trac. I couldn't find any reference to that in our current documentation though. (I'm pretty sure there used to be a note on that in the Sage trac guidelines, or at least on the main page of the Sage trac wiki, and at some point we had spkg-upload.googlecode.com for exactly that purpose, at least for those without a sage.math cluster account, when everybody's home folder was accessible via HTTP.) -leif >> On Monday, July 25, 2016 at 12:43:28 AM UTC+2, Andrey Novoseltsev wrote: >>> >>> Is there any deep reason to 2MB attachment limit on Trac? Can it be >>> increased to, say, 100MB? Would be convenient to be able to upload new >>> packages there rather than figuring out some place to post them. >>> >>> Thank you, >>> Andrey > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
