[2102] in SIPB_Linux_Development
Re: add new 4.2 rpm updates?
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Thu Aug 27 15:55:13 1998
From: mhpower@MIT.EDU
Date: Thu, 27 Aug 1998 15:54:54 -0400
To: amu@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: "[2101] in SIPB_Linux_Development"
>New since when? I'm pretty sure the only update I haven't grabbed is
>the recent apache one.
I meant new with respect to the differences between what's on
ftp.redhat.com and what's on sipb-nfs:
version at ftp.redhat.com version on sipb-nfs
------------------------- -------------------
XFree86-100dpi-fonts-3.3.2-1.i386.rpm XFree86-100dpi-fonts-3.3.1-1.2.i386.rpm
XFree86-3.3.2-1.i386.rpm XFree86-3.3.1-1.2.i386.rpm
XFree86-75dpi-fonts-3.3.2-1.i386.rpm XFree86-75dpi-fonts-3.3.1-1.2.i386.rpm
XFree86-8514-3.3.2-1.i386.rpm XFree86-8514-3.3.1-1.2.i386.rpm
XFree86-AGX-3.3.2-1.i386.rpm XFree86-AGX-3.3.1-1.2.i386.rpm
XFree86-I128-3.3.2-1.i386.rpm XFree86-I128-3.3.1-1.2.i386.rpm
XFree86-Mach32-3.3.2-1.i386.rpm XFree86-Mach32-3.3.1-1.2.i386.rpm
XFree86-Mach64-3.3.2-1.i386.rpm XFree86-Mach64-3.3.1-1.2.i386.rpm
XFree86-Mach8-3.3.2-1.i386.rpm XFree86-Mach8-3.3.1-1.2.i386.rpm
XFree86-Mono-3.3.2-1.i386.rpm XFree86-Mono-3.3.1-1.2.i386.rpm
XFree86-P9000-3.3.2-1.i386.rpm XFree86-P9000-3.3.1-1.2.i386.rpm
XFree86-S3-3.3.2-1.i386.rpm XFree86-S3-3.3.1-1.2.i386.rpm
XFree86-S3V-3.3.2-1.i386.rpm XFree86-S3V-3.3.1-1.2.i386.rpm
XFree86-SVGA-3.3.2-1.i386.rpm XFree86-SVGA-3.3.1-1.2.i386.rpm
XFree86-VGA16-3.3.2-1.i386.rpm XFree86-VGA16-3.3.1-1.2.i386.rpm
XFree86-W32-3.3.2-1.i386.rpm XFree86-W32-3.3.1-1.2.i386.rpm
XFree86-devel-3.3.2-1.i386.rpm XFree86-devel-3.3.1-1.2.i386.rpm
XFree86-libs-3.3.2-1.i386.rpm XFree86-libs-3.3.1-1.2.i386.rpm
apache-1.2.5-0.1.i386.rpm apache-1.2.5-0.i386.rpm
elm-2.4.25-8.1.i386.rpm elm-2.4.25-8.1.i386.rpm
iBCS-2.0-8.i386.rpm iBCS-2.0-6.1.i386.rpm
kernel-2.0.35-0.i386.rpm kernel-2.0.32-1.2.i386.rpm
kernel-headers-2.0.35-0.i386.rpm kernel-headers-2.0.32-1.2.i386.rpm
kernel-modules-2.0.35-0.i386.rpm kernel-modules-2.0.32-1.2.i386.rpm
kernel-source-2.0.35-0.i386.rpm kernel-source-2.0.32-1.2.i386.rpm
kernelcfg-0.4-1.i386.rpm kernelcfg-0.4-1.i386.rpm
libtermcap-2.0.8-4.2.i386.rpm libtermcap-2.0.8-4.1.1.i386.rpm
libtermcap-devel-2.0.8-4.2.i386.rpm libtermcap-devel-2.0.8-4.1.1.i386.rpm
pcmcia-cs-2.9.12-0.i386.rpm pcmcia-cs-2.9.12-1.2.i386.rpm
svgalib-1.2.13-0.i386.rpm svgalib-1.2.10-3.i386.rpm
svgalib-devel-1.2.13-0.i386.rpm svgalib-devel-1.2.10-3.i386.rpm
Of these, four were in the AFS directory, so there wasn't any
particular need for me to have ftp'd them again:
-rw-r--r-- 1 svalente 407158 Aug 23 00:10 apache-1.2.5-0.1.i386.rpm
-rw-r--r-- 1 svalente 263996 Aug 23 00:10 pcmcia-cs-2.9.12-0.i386.rpm
-rw-r--r-- 1 svalente 171224 Aug 23 00:09 svgalib-1.2.13-0.i386.rpm
-rw-r--r-- 1 svalente 159353 Aug 23 00:09 svgalib-devel-1.2.13-0.i386.rpm
One issue is that RedHat apparently decided to issue an update of
pcmcia-cs with a lower release number than an older version:
Name : pcmcia-cs Distribution: Red Hat Linux
Biltmore
Version : 2.9.12 Vendor: (none)
Release : 0 Build Date: Fri Jul 17 14:01:17 1998
Group : Daemons Source RPM: kernel-2.0.35-0.src.rpm
Name : pcmcia-cs Distribution: Red Hat Linux
Biltmore
Version : 2.9.12 Vendor: (none)
Release : 1.2 Build Date: Sat Apr 18 17:22:06 1998
Group : Daemons Source RPM: kernel-2.0.32-1.2.src.rpm
I suppose the new version is still appropriate for machines running
the 2.0.32 kernel, though?
Anyway, leaving out the kernel*-2.0.35 rpm's would make a total of 23
rpm's that are new for the AFS directory, and 27 rpm's that are new
for sipb-nfs. (This includes elm and kernelcfg for which RedHat issued
an update with a filename they had already used in the past.)
>Machines only get updated versions of packages they already have
>installed.
I meant the part of update.pl that seems to make exceptions to that
general rule, i.e.,
push (@rpmlist, $rpm) if ($inst || $name eq 'xserver-wrapper'
|| $name eq 'mktemp');
Probably it'd be easiest to continue leaving out the inews rpm, as has
been done in the past. We have inews for linux in the sipb locker.
Presumably most users can use that version when they're connected to
the network, and when they aren't connected they can't reach the news
server and most likely won't have any use for nntp posting ability.
Matt
