How about you actually try some of the suggestions that you've had so far first?

Install the EPEL repo if it isn't already, then install keychecker and run `keychecker squid` and see what that says.

Run `rpm -qi squid` and look at the Vendor and build hosts and see if you can work it out from that. If you cannot, then post the output from the rpm -qi here and see if one of us can.

Hello,

Many thanks for your help.

Just another quick question, where to find non-src rpm??

actually, I extract this package name from our production server, it used yum method to install that. I really had no idea why it is a src rpm.

many thanks!

What you've downloaded there is the source rpm that can be used to build binary RPMs for installation. You cannot install a src RPM directly (well you can but it just unpacks itself into the rpmbuild directory, default /usr/src). If you want to find out where your existing squid 3 RPM came from then you have to run rpm -qi squid to find out then go there and get it from there (or add the particular yum repo that it came from to your system). The EPEL keychecker utility can also be used and does a good job of identifying the source of signed RPMs. e.g.

Nothing wrong with those warnings. You can safely proceed to rebuild the source RPM if you wish to produce binaries for CentOS5; however, doing so as root is dangerous. Please read the link on how to build safely as a normal users. Only installs should be done as root.

Quote:

Hello,

many thanks for your help.

But I think I still need to trouble you again...

Since I really like to keep all my servers running squid 3.1, I do not want to go back to 2.6 (because some features are not supported in 2.6), so then I downloaded 3.1 version rpm, but I got some warnings again to prevent me to continue...

here is the output:

[root@localhost tmp]# rpm -ivh squid-3.1.8-1.el5.src.rpm
1:squid warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root

What was that mean??? I googled a lot, but I did not find the answer, so I went back for help again...
many thanks in advance!

You must have installed squid 3 from some non-CentOS repository as CentOS 5's squid is 2.6. If you run



then you'll see more information about squid. The Vendor and/or Build Host fields will probably help to identify the package source. If it doesn't help then the EPEL repository has a neat utility called keychecker which can tell you which repo a package came from based on its signing GPG key.

You have probably installed the 3 from some non-default repository.

Yum of CentOS 5 does simply say "installed" in the repository column of "yum list" output. I don't know whether it has internally stored more data. Note: Yum of CentOS 6 stores and shows the source repository for each installed package.

Quote:

Hello,

many thanks for your help,

I issued that command, and I have found some very interesting output:

[root@localhost ~]# yum --showduplicates list squid\*
Loaded plugins: downloadonly, fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.btte.net
* extras: mirrors.btte.net
* updates: mirrors.btte.net
base | 1.1 kB 00:00
extras | 2.1 kB 00:00
nginx | 1.2 kB 00:00
updates | 1.9 kB 00:00
updates/primary_db | 243 kB 00:00
Installed Packages
squid.i386 7:3.1.8-1.el5 installed
Available Packages
squid.i386 7:2.6.STABLE21-6.el5 base

Do you have any ideas that why we only have squid 2.6 version available now? I installed squid3 version long time ago, but now we downgrade to version 2???
I do not quite get it, why

Quote:
That should not happen. Something must be different. If more help is needed then please provide more information about your systems by running "./getinfo.sh package" on each and showing us the output files. It may be that just inspecting the results yourself will suffice.

Details are needed for anyone to help. You can get some idea by running

Hello CentOS,

I just confused with yum packages installation. I have several CentOS servers and I would like to install the same version of squid in every server, but unfortunately, each server installs an unique version of squid. I have checked /etc/yum.repos.d/ folders, all config files are the same, so does anyone know how to keep all the servers update packages from the same repository? It is so hard to manage so many different versions of squids just by one human being...

Many thanks in advance!

AGA-CN