RE: Newbie Question
Jarrad Wilkinson <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
They are under /current/etrials-7.2/i386/RedHat/RPMS. It's not the noarch updates that I am having trouble with, but the noarch rpms from the 7.2 CDs being added. -----Original Message----- From: Dennis Pinckard [mailto:[email protected]] Sent: Monday, March 25, 2002 1:19 PM To: [email protected] Subject: RE: [Current-server] Newbie Question Just curious, but where are your noarch rpms? For example, my current config contains this: [redhat72] label = redhat-linux-i386-7.2 name = RedHat Linux i386 7.2 parent_channel = arch = i386 os_release = 7.2 description = RedHat i386 7.2, with all errata applied. rpm_dirs = /export/install/admin/linux/redhat/7.2/en/os/i386/RedHat/RPMS /export/install/admin/linux/redhat/updates/7.2/en/os/i386 /export/install/admin/linux/redhat/updates/7.2/en/os/i586 /export/install/admin/linux/redhat/updates/7.2/en/os/i686 /export/install/admin/linux/redhat/updates/7.2/en/os/noarch src_dirs = db_dir = /etc/current/db/redhat-7.2 and I'm getting the noarch updates. -----Original Message----- From: Jarrad Wilkinson [mailto:[email protected]] Sent: Monday, March 25, 2002 12:10 PM To: '[email protected]' Subject: RE: [Current-server] Newbie Question I'm running cadmin as root. I generated the directory tree as root and then copied over the Redhat RPMS directory from the CDs and then copied all the patches over after I FTP them down and burned them to a CD. Here is what my current.conf file looks like. Thanks. # current config file # # Don't blame me for the format: I'm using as many standard python modules # as possible # # General guidelines: # 1. Every current.conf must have a "current" section, which is the # main config section. # 2. Section name rule -> '-', '_', alphanum # 3. field name rule -> '-', '.', '_', alphanum # 4. All fields must be present, even if blank. # # General Section descriptions: # [current] # valid_channels = list of all the channels to actually use. This allows # the admin to define a channel for future use, or disable # an old channel without deleting anything. # log_file = File to send log messages to # log_level = How much should we send to the log file? # port_number = what port number should the server be listening on? # # # [channel-section] # label = Text identifier for this channel. Used as a text index. # Values are "redhat-linux-i386-7.1" or "redhat-rawhide-i386" # Not the same as the channel section name because labels need '.' # name = Text name (human readable) name of this distribution # Should be only 1 line. # parent_channel = Channel representing the base channel that provides most # of the packages to this one, blank otherwise. # arch = The cannonical architecture (a family of archs that this # channel supports. (i386, sparc, alpha. Not i686, etc) # os_release = Release of the channel. 6.2, 7.0, 7.2, whatever. # description = Textual description of what the channel represents. This # can be blank or a short paragraph. # rpm_dirs = list of all the dirs that contain binary rpms that should be # served to clients # src_dirs = similarly, list of all the src rpms that should be served. # Can be empty, but not missing (currently) # db_dir = directory containing the current databases # # Note that all channels will also have a "last_modified" field, which will # will automatically be created/updated. [current] valid_channels = etrials-i386-7.2 etrials-i386-7.1 #log_file = ./current.log #pid_file = ./current.pid log_level = 0 http_port = 8080 https_port = 8081 server_secret = etrials current server Copyright (c) 2001 Hunter Matthews server_id = legolas.int.etrials.com key_file = /etc/current/current.pem # These are some text messages that the server can return to the clients # in various API calls. ## FIXME: ConfigParser just keeps getting more and more broken by this ## stuff. The period is there ot provide a "blank line". Sheesh. welcome_message = "Welcome to etrials's up2date server." privacy_statement = "Please see etrials corporate privacy statement." [etrials72] label = etrials-i386-7.2 name = etrials 7.2 parent_channel = arch = i386 os_release = 7.2 description = etrials 7.2 is Red Hat Linux 7.2 witth all the errata applied rpm_dirs = /current/etrials-7.2/i386/RedHat/RPMS /current/etrials-7.2/i386/other-pkgs/rh-updates /current/etrials-7.2/i386/other-pkgs/powertools /current/etrials-7.2/i386/other-pkgs/powertools-updates /current/etrials-7.2/i386/other-pkgs/rawhide xrpm_dirs = /current/etrials-7.2/i386/other-pkgs/rawhide src_dirs = /current/etrials-7.2/i386/src db_dir = /current/etrials-7.2/i386/current [etrials71] label = etrials-i386-7.1 name = etrials 7.1 parent_channel = arch = i386 os_release = 7.1 description = etrials 7.1 is Red Hat Linux 7.1 witth all the errata applied rpm_dirs = /current/etrials-7.1/i386/RedHat/RPMS /current/etrials-7.1/i386/other-pkgs/rh-updates /current/etrials-7.1/i386/other-pkgs/powertools /current/etrials-7.1/i386/other-pkgs/powertools-updates /current/etrials-7.1/i386/other-pkgs/rawhide xrpm_dirs = /current/etrials-7.1/i386/other-pkgs/rawhide src_dirs = /current/etrials-7.1/i386/src db_dir = /current/etrials-7.1/i386/current # Note: since they are NOT included in valid_channels above, these channels # won't be created or used. They are just "live" doc. # The following is an example of what a sub-channel might look like. # It might be better to leave arch and os_release out of sub-channels, as # they'll have to have the same values as the parent anyway. #[bio71] #label = biology-7.1 #name = Duke Biology 7.1 #parent_channel = dulug-i386-7.1 #arch = i386 #os_release = 7.1 #description = Duke Biology specific package will build upon Dulug 7.1 #rpm_dirs = /local/scratch/dulug-7.1/i386/other-pkgs/bio #src_dirs = #db_dir = /local/scratch/dulug-7.1/i386/current/bio #[redhat62] #label = redhat-linux-i386-6.2 #name = Red Hat Linux i386 6.2 #parent_channel = #arch = i386 #os_release = 6.2 #description = Red Hat i386 6.2, with all errata applied. #rpm_dirs = /local/scratch/redhat-6.2/i386/RedHat/RPMS # /local/scratch/redhat-6.2/i386/other-pkgs/dukebio # /local/scratch/redhat-6.2/i386/other-pkgs/dulug # /local/scratch/redhat-6.2/i386/other-pkgs/helix # /local/scratch/redhat-6.2/i386/other-pkgs/misc # /local/scratch/redhat-6.2/i386/other-pkgs/powertools # /local/scratch/redhat-6.2/i386/other-pkgs/powertools-updates # /local/scratch/redhat-6.2/i386/other-pkgs/rh-updates #src_dirs = #db_dir = /local/scratch/redhat-6.2/i386/current ## END OF LINE ## -----Original Message----- From: John Berninger [mailto:[email protected]] Sent: Monday, March 25, 2002 11:21 AM To: [email protected] Subject: Re: [Current-server] Newbie Question The info a output should be a /lot/ longer than that... from that output, it looks like you're generating a database from a tree that only has the kernel and glibc packages available. Are you running cadmin create as root, or as a user? How did you generate the directory tree you're trying to create, and how many packages are in it? On Mon, 25 Mar 2002, Jarrad Wilkinson wrote: > It didn't seem to work. Do I need to change the arch = line in my > current.conf file to something other than just i386? > > This is the output from the cadmin info a CHANNEL command > > ARCH_INDEX > ===================================== > glibc:2.2.4:19.3: = [['glibc', '2.2.4', '19.3', '', 'i386', 5193282], > ['glibc', '2.2.4', '19.3', '', 'i686', 5871264]] > kernel:2.4.9:31: = [['kernel', '2.4.9', '31', '', 'i386', 10440802], > ['kernel', '2.4.9', '31', '', 'i686', 10543295]] > > I have tried removing the i386 from the arch = and leaving it blank. It > still didn't seem to pick up the noarch packages. I have also tried making > that line arch = i386 noarch. > > > > -----Original Message----- > From: John Berninger [mailto:[email protected]] > Sent: Monday, March 25, 2002 11:03 AM > To: [email protected] > Subject: Re: [Current-server] Newbie Question > > > OK, took less time thatn I thought it would. For me, 1.0.2 added noarch > packages just the same is did arch-specific. Try running > > cadmin info a CHANNEL > > and see if it lists the noarch packages. > > On Mon, 25 Mar 2002, Jarrad Wilkinson wrote: > > > I was wondering how current handles noarch packages. > > > > I have created my channels with the cadmin -v create CHANNEL_LABEL and > > noticed that it only adds the packages that are arch specific. In my case > > i386, etc packages. None of the noarch packages are added. > > > > Any suggests would be appreciated. > > > > Jarrad P. Wilkinson > > Sr. Systems Administrator > > etrials > > [email protected] > > > > > > _______________________________________________ > > Current-server mailing list > > [email protected] > > http://lists.dulug.duke.edu/mailman/listinfo/current-server > > -- > Thank you, > John Berninger > > Systems Administrator [email protected] > Department of Mathematics Box 8205, Harrelson Hall > NC State University Raleigh, NC 27695 > Phone: (919)515-6315 Fax: (919)515-3798 > > GPG Key ID: A8C1D45C > Fingerprint: B1BB 90CB 5314 3113 CF22 66AE 822D 42A8 A8C1 D45C > -- > _______________________________________________ > Current-server mailing list > [email protected] > http://lists.dulug.duke.edu/mailman/listinfo/current-server > _______________________________________________ > Current-server mailing list > [email protected] > http://lists.dulug.duke.edu/mailman/listinfo/current-server -- Thank you, John Berninger Systems Administrator [email protected] Department of Mathematics Box 8205, Harrelson Hall NC State University Raleigh, NC 27695 Phone: (919)515-6315 Fax: (919)515-3798 GPG Key ID: A8C1D45C Fingerprint: B1BB 90CB 5314 3113 CF22 66AE 822D 42A8 A8C1 D45C -- _______________________________________________ Current-server mailing list [email protected] http://lists.dulug.duke.edu/mailman/listinfo/current-server _______________________________________________ Current-server mailing list [email protected] http://lists.dulug.duke.edu/mailman/listinfo/current-server