search for: whatrequires

yum remove lightdm That command tells me that it's also going to remove lightdm-gobject and lightdm-gtk. rpm -q --whatrequires lightdm no package requires lightdm So obviously we can't take the word of the --whatrequires option from the rpm command since yum remove tells me that there are two. That being the case, using yum remove to determine the actual dependency chain is not all that helpful since (a) only the roo...

...would think it needs cups. Nevertheless, after the install I now have postfix *and* sendmail on the machine and sendmail even being enabled. And cups is installed. How can I find out what forced them (and probably many other unwanted packages) on the installation? I thought maybe "rpm -q --whatrequires sendmail" would tell me, but it doesn't. Nothing requires it. Same for cups. So, why did it get installed? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

Is there a way to identify if an rpm package is unused, or how much it is used? I would like to reduce my load time by removing unused packages in my kickstart, but do not want to cause problems for users on active systems by guessing which ones are not necessary (I load everything with kickstart now). If I could find the packages are not used I could start by excluding them from a load and be

...generate a report from the rpms installed on a system and tell you exactly what depends on what else. Among other things you could use that report to remove stuff that's not needed in any installation. While not a simple answer, this bash function will provide what you're looking for: whatrequires () { (rpm -q --qf '%{NAME}\n' "$1" ; rpm -q --provides "$1" ) | tr \\n \\0 | xargs -0 rpm -q --whatrequires ; }

...the rpms installed on a system and tell you exactly what depends on what else. Among other things you could use that report to remove stuff that's not needed in any installation. > > > While not a simple answer, this bash function will provide what you're looking for: > > whatrequires () { (rpm -q --qf '%{NAME}\n' "$1" ; rpm -q --provides "$1" ) | tr \\n \\0 | xargs -0 rpm -q --whatrequires ; } > or this one :-) rpm -ev --test PACKAGENAME will list all packages that require PACKAGENAME -- LF

I found that lm_sensors got installed because of a dependency on my first Xen VM that I updated to 5.3. lm_sensors doesn't make sense in a VM. I thought, ok let's check after the update who wants it. However: rpm -q --whatrequires lm_sensors no package requires lm_sensors (same for --triggeredby with lm_sensors or the packages below) Trying to remove lm_sensors reveals these packages: Removing: lm_sensors i386 2.10.7-4.el5 installed 1.8 M Removing for dependencies: cacti...

Quick search in bout "man yum" and "man rpm" shows how to find what package X depends upon, but not what depends upon package X. Of course, we could get a deplist for everything but I'm *guessing* that take more overhead and grep too. "yum remove" tells us. Then we just have to remember to say "No, don't remove". Am I missing something... like I

...too. I do >> use the RStudio rpm, but by command-line install, so it isn't the culprit. >> However, the choice of packages points to an injudicious editing of an rpm >> dependency list in some texlive package related to rmarkdown or similar. > > $ dnf repoquery --tree --whatrequires R-knitr > > texlive-scheme-medium installs texlive-collection-mathscience, which > installs texlive-includernw, which necessarily depends on R-knitr. Thanks for the analysis. I do not see that any other latex package in texlive-sceme-medium involves creating such havoc drawing in non-tex...

On upgrading my F28 to F29, I've found that R-core and a number of R packages: R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi R-stringr R-yaml are installed, although I only ever install R from source and always keep my Rs locally. So I don't use Fedora R rpms, but these were installed without my command. Something in texlive is doing this. A remedy is to

...ore takes out texlive too. I do > use the RStudio rpm, but by command-line install, so it isn't the culprit. > However, the choice of packages points to an injudicious editing of an rpm > dependency list in some texlive package related to rmarkdown or similar. $ dnf repoquery --tree --whatrequires R-knitr texlive-scheme-medium installs texlive-collection-mathscience, which installs texlive-includernw, which necessarily depends on R-knitr. The solution is not to depend on texlive collections. Install texlive-scheme-basic instead, plus additional packages as you need them. I?aki > I'...

Hello there I chose not to install the Xwindows and it still did ? a very minimal one (maybe xfce) any idea why ? I installed version 4 Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20060612/48bab885/attachment-0002.html>

At install I had Gnome and Not KDE. doing rpm -qa | grep qt results in qt-3.3.6-23.el5 qt4-4.2.1-1 How can I find out what package loaded the qt4 and qt? Thanks, Jerry

Hi, Once I'm working with Yum, can i safely remove pirut? cheers, Niki Kovacs -- Dyslexics have more fnu.

How exactly to use the tag "Obsoletes:" in a spec file ? I need to offer texlive to users on Centos-5.6, so I packaged it (based on a Mandriva src.rpm), and that works. But I want rpm to *replace* tetex by texlive, instead of just adding texlive, when users do a : $ yum install texlive (we have a local repo here). So I added this line in texlive.spec : Obsoletes: tetex and of

...gt; use the RStudio rpm, but by command-line install, so it isn't the culprit. >>> However, the choice of packages points to an injudicious editing of an rpm >>> dependency list in some texlive package related to rmarkdown or similar. >> >> $ dnf repoquery --tree --whatrequires R-knitr >> >> texlive-scheme-medium installs texlive-collection-mathscience, which >> installs texlive-includernw, which necessarily depends on R-knitr. > > Thanks for the analysis. I do not see that any other latex package in > texlive-sceme-medium involves creating such...

I've been spending some time backporting Samba 4.0.3 from Fedora 19 to RHEL 6, partly as proof of concept, partly to make it available to others. I've published my work at: https://github.com/nkadel/samba4repo/ The key RPM building tools are at: https://github.com/nkadel/samba-4.0.3-srpm/ And there are dependencies listed for libtalloc, libtevent,

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled,

...too. I do >> use the RStudio rpm, but by command-line install, so it isn't the culprit. >> However, the choice of packages points to an injudicious editing of an rpm >> dependency list in some texlive package related to rmarkdown or similar. > > $ dnf repoquery --tree --whatrequires R-knitr > > texlive-scheme-medium installs texlive-collection-mathscience, which > installs texlive-includernw, which necessarily depends on R-knitr. Thanks for the analysis. I do not see that any other latex package in texlive-sceme-medium involves creating such havoc drawing in non-texl...

I am hoping someone else is already doing what I need to do, and can give me some pointers. Situation: 1. I am running Centos 4.3 x86_64 on a machine at home, without broadband access. I have dialup access, but that doesn't work very well for something like "yum update", so I am still running 4.3 as issued on the CDs. 2. I have high speed access at work, and I have a USB drive to