Joe Zeff writes:

On 12/21/2014 02:07 PM, Sam Varshavchik wrote:
I always thought that this was the whole reason behind rpm/yum: if
package X requires Y, then yum should install it automatically.

Yum will do that, if the package is available, but rpm doesn't.

Well, I used "yum" to install firewall-config. Therefore, I can reasonably expect that if firewall-config needs something installed, it should get pulled in as a direct or an indirect dependency.

But I have already established – and posted to the bug I earlier referenced – the fact that, apparently, nothing apparently stops me from doing this:

# rpm -e --test xorg-x11-fonts-ISO8859-1-100dpi-7.5-14.fc21.noarch xorg-x11- fonts-ISO8859-1-75dpi-7.5-14.fc21.noarch xorg-x11-fonts- misc-7.5-14.fc21.noarch xorg-x11-fonts-Type1-7.5-14.fc21.noarch

This succeeds, with the firewall-config installed.

But if I do that, and run firewall-config, it comes up just fine, but instead of seeing something written in king's English, I get ancient Egyptian hieroglyphics, all over firewall-config's window.

But it does warm my heart, a little bit, to know that at least something in Fedora managed to figure out this complicated concept:

# rpm -e --test lyx-fonts
error: Failed dependencies:
font(:lang=en) is needed by (installed) fontconfig-2.11.1-5.fc21.x86_64

So, that's how it's supposed to work. Now, in addition to some fonts, it would be real nice to know what else firewall-config actually depends on, but the dependency fails to be specified in the package's dependency chain, and, as a result, half of its widgets are completely garbled and they do not respond to pointer and keyboard events.

Attachment: pgp5pI1tf38_U.pgp
Description: PGP signature

-- 
users mailing list
[email protected]
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to