[Bug 44949] no upload possible when mysql database contains a . in its name, due to 'Swift and S3 restrictions'

2014-04-22 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44949 Aaron Schulz aschulz4...@gmail.com changed: What|Removed |Added CC|

[Bug 44949] no upload possible when mysql database contains a . in its name, due to 'Swift and S3 restrictions'

2013-09-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44949 Andre Klapper aklap...@wikimedia.org changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Bug 44949] no upload possible when mysql database contains a . in its name, due to 'Swift and S3 restrictions'

2013-09-04 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=44949 --- Comment #10 from Elliott Eggleston ejeggles...@gmail.com --- My pleasure! I'm new here, so I'm not sure where to propose the following fix: For the FSFileBackend backend (local filesystem), it seems like container names are only ever