SCIENTIFIC-LINUX-USERS Archives

October 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stephen J. Gowdy" <[log in to unmask]>
Reply To:
Stephen J. Gowdy
Date:
Mon, 10 Oct 2005 12:21:15 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (80 lines)
Hi Tony,
	I thought using "rolling" was similar to what RH did. By default
you get to the latest update.

							regards,

							Stephen.

On Mon, 10 Oct 2005, Troy Dawson wrote:

> Ah ... a 40rolling user :)
>
> In order to test to see if rpm's would install, I put the recompiled
> rpm's in the 40rolling area.  I then tested and found that, sure enough,
> redhat had made these rpm's depend on packages that were not labled as
> 'security updates' in Update 2.
> These packages (openssh, and vixi-cron) were not put into the main errata.
>
> So, first comment.  Pointing your updates to the 'rolling' area, is
> essentially like pointing your area to the 'rawhide' area.
> Second comment.  Maybe Connie can put in the dependancies into the
> rolling area.  Which is pam, which requires audit, which requires
> glibc-headers.
>
> Troy
>
> p.s. My favorite dependancy this go round was evolution, which required
> the mozilla from Update 1 (hardcoded in, for that one version), and yet,
> we had to have the mozilla from the latest release to build other packages.
>
> Stephen J. Gowdy wrote:
> > From 4.x, I mean just doing yum update on a running system;
> >
> > [root@localhost ~]# yum update
> > Setting up Update Process
> > Setting up Repos
> > sl-base                   100% |=========================| 1.1 kB    00:00
> > sl-errata                 100% |=========================|  951 B    00:00
> > Reading repository metadata in from local files
> > sl-base   : ################################################## 1502/1502
> > sl-errata : ################################################## 136/136
> > Resolving Dependencies
> > --> Populating transaction set with selected packages. Please wait.
> > ---> Package vixie-cron.i386 4:4.1-36.EL4 set to be updated
> > --> Running transaction check
> > --> Processing Dependency: pam >= 0.77-66.8 for package: vixie-cron
> > --> Finished Dependency Resolution
> > Error: Missing Dependency: pam >= 0.77-66.8 is needed by package
> > vixie-cron
> >
> > I removed my openssh-server, previously it also complained about a pam
> > shared library too.
> >
> > On Mon, 10 Oct 2005, Connie Sieh wrote:
> >
> >
> >>Stephen,
> >>
> >>On Mon, 10 Oct 2005, Stephen J. Gowdy wrote:
> >>
> >>
> >>>I'm trying to update this via yum but it looks like a new version of pam
> >>
> >>Updating from what to 4.x?
> >>
> >>
> >>>is required that it can't find. Do I need to use the new version of yum?
> >>
> >>-Connie Sieh
> >>
>

--
 /------------------------------------+-------------------------\
|Stephen J. Gowdy                     | SLAC, MailStop 34,       |
|http://www.slac.stanford.edu/~gowdy/ | 2575 Sand Hill Road,     |
|http://calendar.yahoo.com/gowdy      | Menlo Park CA 94025, USA |
|EMail: [log in to unmask]       | Tel: +1 650 926 3144     |
 \------------------------------------+-------------------------/

ATOM RSS1 RSS2