Getting the following error on this one package only.
We've uploaded this package in the past, but the current binary won't upload. We're uploading other packages just fine, and we've not received any notifications that we've exceeded any limits.
Please advise.
Uploading msys2_installer/20161025@bincrafters/stable
Recipe is up to date, upload skipped
Uploading package 1/1: c0519e2d9702ec12d057bb15adb7a02baaf18107
Requesting upload permissions...Done!
Uploading conanmanifest.txt
[==================================================] 2.0MB/2.0MB
Uploading conaninfo.txt
[==================================================] 189B/189B
Uploading conan_package.tgz
[==================================================] 371.8MB/371.8MB
ERROR:
Error uploading file: conan_package.tgz, '<html>
<head><title>405 Not Allowed</title></head>
<body bgcolor="white">
<center><h1>405 Not Allowed</h1></center>
<hr><center>nginx</center>
</body>
</html>
'
ERROR: Execute upload again to retry upload the failed files: conan_package.tgz. [Remote: bincrafters]
We reduced the package size under 250 MB and we were able to upload to Bintray. @memsharded stated he was discussing this limitation internally for the future.
We, at Inexor, have a Conan package for CEF (https://github.com/inexorgame/conan-cef)
We don't upload build packages right now, because it isn't a clean from-scratch package but rather downloads prebuilds from Spotify's open source server.
We definitely want to change that at some point and have a clean, self-contained, building locally from scratch package (mostly a lot of huge dependecies are holding us back).
We also might switch to Servo (https://github.com/inexorgame/inexor-core/issues/535).
But no matter what we do, both are huge dependencies, so this is very likely to become a problem for us in the future as well.
Would be nice to see the max file size upload on Bintray increased :)
We, as in Boost, negotiated with Bintray to increase the upload limit as a condition of switching to using them. I don't know what they increased it to. But it was enough to be able to upload the 1.3 GiB Windows full archive -- https://bintray.com/boostorg/release/boost-binaries#files/1.66.0%2Fbinaries
Yes, we had been able to increase the bincrafters quota too. I cannot guarantee that we could do this for all users but please, contact us and will see what can we do.
In general, as a free service to prevent abuse bintray has a number of somewhat arbitrary limitations that we impose on OSS accounts. (For example the file size limitation among other things helps prevent people from using us to distribute video files, the overall disk space quotas prevent people from using bintray to store snapshots and other non-releasable artifacts). It is also generally the case that if you open a discussion with JFrog and you are demonstrably not abusing the service, we will work to adjust the limits based on your use case, and this is granted fairly routinely, although we reserve the right not to. If we eventually determine that the quotas are too low for the Conan community in general (as opposed to just a small number of specific packages) we can also look at adjusting them upwards.
Hello guys, I have the same error on some of my builds, do you think it has something to do with limitations ? https://travis-ci.org/lucienboillod/conan-qt/builds/373078417
Hi @lucienboillod
Sorry for the delay. Still having the same error? I see all the jobs green in travis in the link you provided.
Indeed if packaging Qt, it is easy to hit some of the limits. If that is the case, please write us an email with your bintray repo details. Thanks!
Hi @memsharded
It is ok now :) thank you for the support, I'm now packaging llvm I may hit the limit also, I will tell you in this case. Thank again
@memsharded sorry for the notification, I sent a mail but I'm not sure it's the right one ([email protected])
I'm pretty sure this has been completely fixed for Bintray. Can reopen if not.
Most helpful comment
In general, as a free service to prevent abuse bintray has a number of somewhat arbitrary limitations that we impose on OSS accounts. (For example the file size limitation among other things helps prevent people from using us to distribute video files, the overall disk space quotas prevent people from using bintray to store snapshots and other non-releasable artifacts). It is also generally the case that if you open a discussion with JFrog and you are demonstrably not abusing the service, we will work to adjust the limits based on your use case, and this is granted fairly routinely, although we reserve the right not to. If we eventually determine that the quotas are too low for the Conan community in general (as opposed to just a small number of specific packages) we can also look at adjusting them upwards.