$ echo foo > foo $ rpm -qlp foo The above causes an apparently infinite loop in rpmq, with no output. $ echo "bar foo" > foo $ rpm -qlp foo error: open of bar failed: No such file or directory error: open of bar failed: No such file or directory error: open of bar failed: No such file or directory [...] Another infinite loop, this time with output. I'd expect rpm to detect the loops and break out of them, outputting an error message.
Yes, a file that contains its own name will loop forever. Hint: for extra credit, try the doubly recursive variant echo "pong" > ping echo "ping" > pong rpm -qlp ping I'm sure you can devise the N+1 failures by induction.
Perhaps a progress bar reminescent of the ancient arcade game pong would suffice to give the user feed back while waiting for memory to be exhausted by rpm. Nah, that only works with the doubly recursive variant failure mode, and the wit is likely wasted.
And lets not firget this type of recursion either. I too would expect error messages that are simple, direct, and translated to my specific locale in every failure instance, including this one: [jbj@wellfleet rpm]$ cat /etc/rpm/macros.loop %bing %{bang} %bang %{boom} %boom %{bing} [jbj@wellfleet rpm]$ rpm -qp '%bing' error: Recursion depth(17) greater than max(16) 15< (empty) 14< (empty) 13< (empty) 12< (empty) 11< (empty) 10< (empty) 9< (empty) 8< (empty) 7< (empty) 6< (empty) 5< (empty) 4< (empty) 3< (empty) 2< (empty) 1< (empty) 0< (empty) *** Fstrerror((nil)) error: open of failed: No such file or directory [jbj@wellfleet rpm]$ rpm --version rpm (RPM) 5.1.DEVEL Is that expecting too much? I think not ...
Then there are the other variant failures. Note two error messages, that is so so wrong: jbj@wellfleet wdj51]$ ln -s foo bar [jbj@wellfleet wdj51]$ ln -s bar foo [jbj@wellfleet wdj51]$ rpm -qp foo error: open of foo failed: Too many levels of symbolic links error: open of foo failed: Too many levels of symbolic links Shall we move along to named pipes and fifos misbehavior with rpm -qp?
And then there is [jbj@wellfleet wdj51]$ echo "foo*" > foo [jbj@wellfleet wdj51]$ rpm -qp foo ^C that needs to be handled with simple concise error messages. Don't you hate infinite recursions? I do ...
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.
Moving to rawhide to avoid timeouting.
Fixed upstream b2bde386f609145f14fe9c98bba67b9db6e2b4ff.