The 'trash-empty' utility fails with: [....] return S_IFMT(mode) == S_IFLNK RuntimeError: maximum recursion depth exceeded .. when the recursion depth of removed directory is bigger than 992. I know that this is quite huge number but it would be nice to allow user of trash-cli at least remove these directories without checking the depth somehow (new option?). Workaround for this issue is 'trash-restore' this directory and after that use '/bin/rm -rf directory'. Pavel Version-Release number: trash-cli-0.11.3-0.5.r315.fc17.noarch How reproducible: 100% reproducible Steps to Reproduce: | #!/bin/bash | rm -rf 1 | | [ -z $stop ] && stop=933 | i=0 | | pushd . >/dev/null | while [ "$i" -le "$stop" ]; | do | let i=i+1 | mkdir 11 | cd 11 | done | popd >/dev/null | | trash-put 11 | trash-empty # fails.. Actual results: RuntimeError: maximum recursion depth exceeded Expected results: trash-empty should empty trash bin successfully (or at least say which directory we should remove by hand.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.