A broken package is a package (i.e. rpm) that is in some way broken.
Iron can be installed and does work on my system, so it isn't broken.
OK, then please consider this if you will .......
Iron appears to be working properly on this system too, so it is just an example ......
Iron reports what appears to me to be an error when launched from a terminal.
If that 'error' can be repaired only by a rebuild of the package, then the package is obviously broken.
At present I do not know if - in this case - it is a 'real' error that needs to be corrected, or even if it is real is it caused by the Iron package or the package that it complains about.
So in this particular case I did and do agree with moving this thread to software ....... until the cause is located, at which point maybe this or another thread would be needed in broken Packages.
All of that is by way of explanation why I disagree with Andy's post about what is and is not a Broken Package.
There have been many packages which installed and ran, but when some specific option was attempted, that failed.
Those packages were broken, until they were rebuilt to be corrected.
Its not a broken software section its a broken package ie. RPM section. If it installs but its not working it belongs somewhere else
That is what I disagree with. The cause of something not working may very well be an incorrectly built package.
If it occurs on many installs then some package is likely the cause - as opposed to a user setting or such.
Hopefully you understand what I was trying to say.
No upsets, just comments and clarifications