My old server, red hat 9 uses up2date. Its brilliant. I've had cobalt raqs for the last five years and moved from one to the next but always was annoyed at how restrictive it is. To top that I got mega sick of having to install patches all the time through that stupid gui and when I realised how cool up2date was I decided enough was enough and it swung my decision to move onto red hat full time......
So it works fine.
But I get one of these new enterprise beast's and run up2date and well, not only does it display soooo much more (I use up2date -u) it bombs out at the end saying dependancies relating to spam assassin have failed.
Some of the output is below ;
___________________________________________
nss_ldap 207 5 i386
openssl 0.9.7a 33.4 i686
openssl-devel 0.9.7a 33.4 i386
oprofile 0.5.4 13 i386
oprofile-devel 0.5.4 13 i386
popt 1.8.1 4.4 i386
pstack 1.2 3.EL.1 i386
redhat-config-kickstart 2.3.20 1 noarch
redhat-config-network 1.2.59 1 noarch
redhat-config-network-tui 1.2.59 1 noarch
redhat-config-packages 1.2.9 1 noarch
redhat-release 3ES 7 i386
rh-postgresql-devel 7.3.4 9 i386
rh-postgresql-libs 7.3.4 9 i386
rh-postgresql-python 7.3.4 9 i386
rpm 4.2.1 4.4 i386
rpm-build 4.2.1 4.4 i386
rpm-devel 4.2.1 4.4 i386
rpm-python 4.2.1 4.4 i386
samba 3.0.2 6.3E i386
samba-client 3.0.2 6.3E i386
samba-common 3.0.2 6.3E i386
shadow-utils 4.0.3 15 i386
slocate 2.7 3 i386
spamassassin 2.55 3.1 i386
strace 4.5.1 1.EL.1 i386
tcpdump 3.7.2 7.E3.1 i386
up2date 4.2.5 1 i386
ypbind 1.12 5 i386
Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:
Unresolvable chain of dependencies:
psa-spamassassin-7.0.0-rhel3.build040206 requires spamassassin >= 2.60
spamassassin-tools-2.61-1 requires perl-Mail-SpamAssassin = 2.61-1
_________________________________________-
Whats all that about then?
IS IT ACTUALLY updating stuff, or is laughing at me?
Is it because I'm british?
Rufo