Package: release.debian.org Severity: normal Tags: buster User: release.debian....@packages.debian.org Usertags: pu
Capistrano is a widely used tool for deployments, one of the steps of a deployment is to remove the old releases, this consists in removing the last Nth releases' folders. Recently a bug has been found when one had too many releases, as they are removed with the "rm" command, having too many arguments on the command triggers the "argument list too long" error. The fix[0] is a small change that splices the arguments in bulks of 100. Note that the commit is also changing more things, but they're an extra test and a changelog entry, thus I decided it would be better to add the whole commit to the package. In order for the fix to be applied, another commit[1][2] had to be applied as well so there's no conflict and need to update the fix commit. I understand an alternative would be to adapt the fix in some way that this commit is not needed, I see the chosen approach as more stable and reliable as it's the upstream's code that was well tested, besides this extra commit being a small change. In summary I believe this is a problem that should be fixed in stable and the approach taken was consistent to our stable philosophy. Let's make buster even more rock solid. Thanks, [0] https://github.com/capistrano/capistrano/pull/2027/commits/89a77085780fbcae9b21d0aa10001969172cfa0a#diff-aa4465f31474e46370f8f1f204f7d51eR171 [1]https://github.com/capistrano/capistrano/pull/1995 [2] https://github.com/capistrano/capistrano/pull/1995/commits/ad9c0a455516426e3c634e9c9925b9cfd77d5108 -- Samuel Henrique <samueloph>
capistrano_3.11.0-3+deb10u1.debdiff
Description: Binary data
