Subject: | |
From: | |
Reply To: | |
Date: | Tue, 11 Nov 2008 15:50:20 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, Nov 11, 2008 at 02:37:34PM -0600, Troy Dawson wrote:
> http://ftp.scientificlinux.org/linux/scientific/5rolling/testing/i386/java/
> http://ftp.scientificlinux.org/linux/scientific/5rolling/testing/x86_64/java/
> jdk-1.6.0_10-fcs.i586.rpm
> jdk-1.6.0_10-fcs.x86_64.rpm
> java-1.6.0-sun-compat-1.6.0.10-3.sl5.jpp.i586.rpm
> java-1.6.0-sun-compat-1.6.0.10-3.sl5.jpp.x86_64.rpm
> java-1.5.0-sun-compat-1.5.0.90-2.sl.jpp.noarch.rpm
Troy, can you clarify - these rpms will have proper gpg signatures?
P.S. (Sorry to beat the dead horse) If un-signed rpms are released by SL,
they block all further yum automatic updates (with error "package xxx is not signed")
until local administrator goes to each affected machine and manually installs
the offending packages.
P.P.S. I am puzzled why yum does not have the obvious improvement, where if
you install 100 packages and yum does not like 1 of them, it still installs
the 99 packages it is happy with.
--
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
|
|
|