[Yum] Re: Yum Digest, Vol 5, Issue 14

Harish Chauhan Harish_Chauhan at in.ibm.com
Fri Dec 12 16:38:57 UTC 2003


Thanks, things are working fine. 

1. Can I have additional "yumgroups.xml" with different packages listed in 
it ?

Looking forward to someone's response.

Thanks in advance.....
Regards, Harish Chauhan





yum-request at lists.dulug.duke.edu
Sent by: yum-bounces at lists.dulug.duke.edu
12/11/2003 06:19 PM
Please respond to yum
 
        To:     yum at lists.dulug.duke.edu
        cc: 
        Subject:        Yum Digest, Vol 5, Issue 14

 

Send Yum mailing list submissions to
                 yum at lists.dulug.duke.edu

To subscribe or unsubscribe via the World Wide Web, visit
                 https://lists.dulug.duke.edu/mailman/listinfo/yum
or, via email, send a message with subject or body 'help' to
                 yum-request at lists.dulug.duke.edu

You can reach the person managing the list at
                 yum-owner at lists.dulug.duke.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum digest..."


Today's Topics:

   1. Re: Yum Digest, Vol 5, Issue 13 (Harish Chauhan)
   2. Re: Re: Yum Digest, Vol 5, Issue 13 (Jeff Sheltren)
   3. Use Yum for replace i386 for i686 (Josep M.)
   4. yum doesn't list all installed kernels (Charles Curley)


----------------------------------------------------------------------

Message: 1
Date: Thu, 11 Dec 2003 12:17:42 -0500
From: Harish Chauhan <harish at us.ibm.com>
Subject: [Yum] Re: Yum Digest, Vol 5, Issue 13
To: yum at lists.dulug.duke.edu
Message-ID:
 <OF740F6941.40D6D939-ON85256DF9.005EA55E-85256DF9.005EFE7F at us.ibm.com>
Content-Type: text/plain; charset="us-ascii"

Hi,

I have the following queries regarding "yum.conf" :

1. How can I define the channels for specific groups.
2. How can I let the groups have access to certains channels only.
3. How a normal user exclude the packages he/she doesn;t want to install 
without specifying anything in the yum.conf (as he doesn't have the access 

for modifying the file)

Looking forward to your help

Thanks in advance,,,,,

Regards, Harish Chauhan




yum-request at lists.dulug.duke.edu 
Sent by: yum-bounces at lists.dulug.duke.edu
12/11/2003 12:00 PM
Please respond to
yum


To
yum at lists.dulug.duke.edu
cc

Subject
Yum Digest, Vol 5, Issue 13






Send Yum mailing list submissions to
                 yum at lists.dulug.duke.edu

To subscribe or unsubscribe via the World Wide Web, visit
                 https://lists.dulug.duke.edu/mailman/listinfo/yum
or, via email, send a message with subject or body 'help' to
                 yum-request at lists.dulug.duke.edu

You can reach the person managing the list at
                 yum-owner at lists.dulug.duke.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum digest..."


Today's Topics:

   1. Re: Retrieving packages from Red Hat Network (Ian Masterson)
   2. Re: Retrieving packages from Red Hat Network (Ian Masterson)
   3. Re: Retrieving packages from Red Hat Network (Jim Wildman)
   4. Re: Retrieving packages from Red Hat Network (Robert G. Brown)
   5. Re: Retrieving packages from Red Hat Network (seth vidal)
   6. Re: Retrieving packages from Red Hat Network (Jim Wildman)


----------------------------------------------------------------------

Message: 1
Date: Wed, 10 Dec 2003 13:58:54 -0800 (PST)
From: Ian Masterson <ian at ssli-mail.ee.washington.edu>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID:
 <Pine.LNX.4.58.0312101335080.22856 at basho.ee.washington.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 9 Dec 2003, Joseph Tate wrote:

> You could go through a caching web proxy.
> If you have enough systems to warrant it, you can purchase the RHN to
> run locally (though I can't remember what this product is called, or how
> much it costs).

We have a local RHN proxy. It is sold along with the RHEL licenses, since
Red Hat would (understandably) prefer that they provide only the bandwidth
required to send packages to your site once rather than to every computer
individually.

Unfortunately, we'd have the same problem as running 'up2date -d'. The RHN
proxy only caches those packages which have been requested by clients. It
doesn't seem to be any easier to get all packages from an RHN proxy than
it is to do the same directly from RHN.

> Generally, however, unless bandwidth on your end is a limiting factor,
> using up2date on each server is recommended, as there's a whole lot more
> that you can do with RHN than keep your servers up to date.

I agree that RHN is nifty, but there are things we can do with yum that
aren't as easy (or perhaps possible) with RHN.

Thanks,

Ian Masterson
Dept. of Electrical Engineering (SSLI)
University of Washington, Seattle

------------------------------

Message: 2
Date: Wed, 10 Dec 2003 14:01:34 -0800 (PST)
From: Ian Masterson <ian at ssli-mail.ee.washington.edu>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID:
 <Pine.LNX.4.58.0312101359560.22856 at basho.ee.washington.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Dec 2003, seth vidal wrote:

> I'm pretty sure this is a way to request the packages available via the
> xmlrpc interface to rhn. You should ask your sales rep about this. I
> know it's not something they object to.
>
> -sv

Thanks, Seth. I'll see if he has anything to suggest.

-Ian

------------------------------

Message: 3
Date: Wed, 10 Dec 2003 17:03:40 -0500 (EST)
From: Jim Wildman <jawildman at rossberry.com>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID:
 <Pine.LNX.4.58.0312101702170.3197 at newross.rossberry.private>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Dec 2003, Ian Masterson wrote:

> 
> Unfortunately, we'd have the same problem as running 'up2date -d'. The 
RHN
> proxy only caches those packages which have been requested by clients. 
It
> doesn't seem to be any easier to get all packages from an RHN proxy than
> it is to do the same directly from RHN.

So grab an old box, put 'everything' on it and register it.  Or
designate one of your newer boxes for the same purpose.  And mark, 'save
packages after installation' and 'retrieve source rpms'.

------------------------------------------------------------------------
Jim Wildman, CISSP, RHCE                                jim at rossberry.com
http://www.rossberry.com

------------------------------

Message: 4
Date: Wed, 10 Dec 2003 17:10:13 -0500 (EST)
From: "Robert G. Brown" <rgb at phy.duke.edu>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID:
 <Pine.LNX.4.44.0312101706130.12467-100000 at ganesh.phy.duke.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Dec 2003, Jim Wildman wrote:

> On Wed, 10 Dec 2003, Ian Masterson wrote:
> 
> > 
> > Unfortunately, we'd have the same problem as running 'up2date -d'. The 

RHN
> > proxy only caches those packages which have been requested by clients. 

It
> > doesn't seem to be any easier to get all packages from an RHN proxy 
than
> > it is to do the same directly from RHN.
> 
> So grab an old box, put 'everything' on it and register it.  Or
> designate one of your newer boxes for the same purpose.  And mark, 'save
> packages after installation' and 'retrieve source rpms'.

Or beat RH about the head and ears about wanting a trivial software tool
that doesn't require hundreds of users to burn an entire computer doing
something that is clearly a useful and common thing to do well within
the capabilities of simple software.

That would work even better.

I'm not sure that "everything" would install on any single box.  What
are you going to do about installing smp kernels on a non-SMP box?  What
about add-on packages?  What about package dependency conflicts (which
should not exist, of course:-)?

Maybe they should just provide a button that says "build local yum
repository"...

  rgb

> 
> ------------------------------------------------------------------------
> Jim Wildman, CISSP, RHCE jim at rossberry.com
> http://www.rossberry.com
> _______________________________________________
> Yum mailing list
> Yum at lists.dulug.duke.edu
> https://lists.dulug.duke.edu/mailman/listinfo/yum
> 

Robert G. Brown 
http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb at phy.duke.edu




------------------------------

Message: 5
Date: 10 Dec 2003 17:15:59 -0500
From: seth vidal <skvidal at phy.duke.edu>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID: <1071094559.32740.75.camel at opus>
Content-Type: text/plain

On Wed, 2003-12-10 at 17:03, Jim Wildman wrote:
> On Wed, 10 Dec 2003, Ian Masterson wrote:
> 
> > 
> > Unfortunately, we'd have the same problem as running 'up2date -d'. The 

RHN
> > proxy only caches those packages which have been requested by clients. 

It
> > doesn't seem to be any easier to get all packages from an RHN proxy 
than
> > it is to do the same directly from RHN.
> 
> So grab an old box, put 'everything' on it and register it.  Or
> designate one of your newer boxes for the same purpose.  And mark, 'save
> packages after installation' and 'retrieve source rpms'.

Short of a --force you can't install i686 and athlon kernels on the same
system.

-sv



------------------------------

Message: 6
Date: Wed, 10 Dec 2003 18:20:03 -0500 (EST)
From: Jim Wildman <jawildman at rossberry.com>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID:
 <Pine.LNX.4.58.0312101818190.3197 at newross.rossberry.private>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Dec 2003, seth vidal wrote:

> Short of a --force you can't install i686 and athlon kernels on the same
> system.

Good point.  But it goes a long way.

------------------------------------------------------------------------
Jim Wildman, CISSP, RHCE                                jim at rossberry.com
http://www.rossberry.com

------------------------------

_______________________________________________
Yum mailing list
Yum at lists.dulug.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum


End of Yum Digest, Vol 5, Issue 13
**********************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.dulug.duke.edu/pipermail/yum/attachments/20031211/6b5bde13/attachment-0001.htm


------------------------------

Message: 2
Date: Thu, 11 Dec 2003 09:28:46 -0800
From: Jeff Sheltren <sheltren at cs.ucsb.edu>
Subject: Re: [Yum] Re: Yum Digest, Vol 5, Issue 13
To: "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Message-ID: <1071163725.7626.5.camel at forsberg>
Content-Type: text/plain

Hi Harish, to define your groups you'll need to create a yumgroups.xml
file and put it on your yum repository.  It'll look something like this:

<?xml version="1.0"?>
<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN"
"comps.dtd">
<comps>
  <group>
   <id>cs-common</id>
   <uservisible>true</uservisible>
   <name>CS Common</name>
   <packagelist>
     <packagereq type="mandatory">cfengine</packagereq>
     <packagereq type="mandatory">ngtools</packagereq>
     <packagereq type="mandatory">spamassassin</packagereq>
     <packagereq type="mandatory">subversion</packagereq>
     <packagereq type="mandatory">yum</packagereq>
   </packagelist>
  </group>
</comps>

I wrote a perl script to help create this for you, which can be found
here: http://www.cs.ucsb.edu/~sheltren/download.php?id=7  Seth wrote a
python program with much the same functionality which is located
somehwere on the yum site (I lost the link).

#2 I'm not sure how to do...

I don't think you can exclude stuff on the command line, but I'm not
sure what you are doing where a 'normal user' is installing RPMs on the
system - how is that setup?

-Jeff

On Thu, 2003-12-11 at 09:17, Harish Chauhan wrote:
> Hi,
> 
> I have the following queries regarding "yum.conf" :
> 
> 1. How can I define the channels for specific groups.
> 2. How can I let the groups have access to certains channels only.
> 3. How a normal user exclude the packages he/she doesn;t want to
> install without specifying anything in the yum.conf (as he doesn't
> have the access for modifying the file)
> 
> Looking forward to your help
> 
> Thanks in advance,,,,,
> 
> Regards, Harish Chauhan



------------------------------

Message: 3
Date: Thu, 11 Dec 2003 22:38:54 +0100
From: "Josep M." <websurfer_email at yahoo.es>
Subject: [Yum] Use Yum for replace i386 for i686
To: yum at lists.dulug.duke.edu
Message-ID: <6.0.1.1.2.20031211223724.02828f68 at 172.26.0.4>
Content-Type: text/plain; charset="us-ascii"

Hello.

I have several packages that I have installed in i386, I want replace for 
i686 versions 
compiled for myself...Can Yum do this?

Thanks
Josep


------------------------------

Message: 4
Date: Thu, 11 Dec 2003 16:18:23 -0700
From: Charles Curley <charlescurley at charlescurley.com>
Subject: [Yum] yum doesn't list all installed kernels
To: yum at lists.dulug.duke.edu
Message-ID: <20031211231822.GC21763 at charlescurley.com>
Content-Type: text/plain; charset="us-ascii"

While upgrading from RH 80 to Fedora Core 1 via yum, I noticed that
yum does not list all the kernels I have installed.

[root at taltos root]# yum list kernel*
Gathering header information file(s) from server(s)
Server: Red Hat Linux 8.0 - i386 - Base
Server: Red Hat Linux 8.0 - Updates
Finding updated packages
Downloading needed headers
Looking in Available Packages:
Name                                Arch   Version                  Repo
--------------------------------------------------------------------------------
kernel-BOOT                         i386   2.4.22-1.2115.nptl       base
kernel-doc                          i386   2.4.22-1.2115.nptl       base
kernel-pcmcia-cs                    i386   1:3.1.31-13              base
kernel-smp                          i686   2.4.22-1.2115.nptl       base
kernel-smp                          athlon 2.4.22-1.2115.nptl       base
kernel-source                       i386   2.4.22-1.2115.nptl       base
kernel-utils                        i386   1:2.4-9.1.101.fedora     base
 
Looking in Installed Packages:
Name                                Arch   Version                  Repo
--------------------------------------------------------------------------------
kernel                              athlon 2.4.22-1.2115.nptl       db
kernel-pcmcia-cs                    i386   1:3.1.31-9               db
 
[root at taltos root]# pre kernel
kernel-2.4.20-18.8
kernel-pcmcia-cs-3.1.31-9
kernel-2.4.18-14
kernel-2.4.20-19.8
kernel-2.4.20-20.8
kernel-2.4.22-1.2115.nptl
[root at taltos root]#


Where "pre" is a wrapper for "rpm -qa | grep" and some other goodies.

There was nothing in the directory where I rand this that would expand
the "kernel*".

I'm not on this list, so please CC any replies to me.

Thanks.

-- 

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.dulug.duke.edu/pipermail/yum/attachments/20031211/77ce7b3f/attachment.bin


------------------------------

_______________________________________________
Yum mailing list
Yum at lists.dulug.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum


End of Yum Digest, Vol 5, Issue 14
**********************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.baseurl.org/pipermail/yum/attachments/20031212/a9fc3a53/attachment-0001.htm 


More information about the Yum mailing list