From: Michael Folsom (mwfolsom_at_gmail.com)
Date: Mon Aug 27 2007 - 18:15:57 CEST
Message-ID: <ea5f6c090708270915u58784453oabb78399becfde11@mail.gmail.com> Date: Mon, 27 Aug 2007 10:15:57 -0600 From: "Michael Folsom" <mwfolsom@gmail.com> Subject: [suse-sles-e] Re: Problems with YUP and SLES10 SP1 & SLED10 SP1 setup
Thanks -
Yes, it does need a " --" (two dashes) before type, not one " - " that was
my mistake.
When I add the 2nd dash "rug sa" will simply hang -
Question - is the "-i586" directory supposed to be "TOTALLY" empty save the
"repodata" directory (which is also empty)?
Thanks -
M-
On 8/27/07, Skip Paul <spaul@novell.com> wrote:
>
> make sure that you use "--"
> rug sa --type=YUM http://system.name.com/yup/-i586 repodata
>
> -skip
>
> >>> "Michael Folsom" <mwfolsom@gmail.com> 08/26/07 6:45 PM >>>
> Having decide to set Zenworks to the side for now and setup a YUP update
> server
>
> I've setup a SLES10 box and put YUP, yup-222-3.1, on it and have
> downloaded
> the SP1 patches -
>
> Basically there a few sets of instructions out there on the web, see:
> http://www.novell.com/coolsolutions/feature/19279.html
>
> http://opseast.wordpress.com/2007/07/19/configuring-a-yup-update-server/
>
> And getting the download to work is fairly obvious but I still have a few
> questions.
>
> It appears that I should be able to just crank up the apache server, set
> yup
> so that it downloads the patches in the proper place under the web
> server's
> document root, add a few other tidbits to the /etc/sysconfig/yup file,
> type
> yup and off it goes - which is pretty much what has happened.
>
> Essentially the base of the patch repository is:
> /srv/www/htdocs/yup
>
> Besides starting apache2 with /etc/sysconfig I've done nothing else to the
> web server or changed its default setup in any way, shape or form.
>
> I configured yup to download patches for:
> SLES10 x86 SP1
> SLES10 x86-64 SP1
> SLES10 ia64 SP1
> SLED10 x86 SP1
> SLES10 x86-64 SP1
>
> During the download process the following top level directories was
> created
> under /srv/www/htdocs/yup:
> -i586
> -ia64
> -x86_64
> SLED10-SP1-Online
> SLED10-SP1-Updates
> SLES10-SP1-Online
> SLES10-SP1-Updates
>
> Note the first three directories, -i586, -ia64 & -x86_64, besides
> containing
> the subdirectory "repodata", are totally empty. However all of the other
> directories contain many subdirectories and many gigs of data.
>
> Besides the weirdness of the -i586, -ia64 & -x86_64 directories all else
> looks fine.
>
> As a test when I direct a browser to:
>
> http://system.name.com/yup/SLED10-SP1-Updates/sled-10-i586/rpm/i586/samba-3.0.24-2.28.i586.rpm
> the samba rpm is found and I can save it to my disk. So, the web server
> seems to be working as expected.
>
> My problem is getting rug on a SP1 client to add it as a service - for
> example as one document suggests when I tried to do the following on a
> client:
> rug sa -type=YUM http://system.name.com/yup/-i586 repodata
>
> I get the error:
> ERROR: No valid URI was specified.
>
> If I try:
> rug sa -type=YUM
> http://system.name.com/yup/SLES10-SP1-Updates/sles-10-i586 repodata
> or, frankly more logically
> rug sa -type=YUM
> http://system.name.com/yup/SLES10-SP1-Updates/sles-10-i586/repodata
>
> I still get the same error:
> ERROR: No valid URI was specified
>
> So the question is - am I using the wrong URI (URL) or is there a problem
> elsewhere?
>
> Any & all help appreciated.........
>
>
>
> Michael
>
>
This archive was generated by hypermail 2.1.7 : Mon Aug 27 2007 - 20:19:44 CEST