Okay, I finally got the channel populated with packages. When I initially created the channel,I selected "Sparc" as the architecture type. However, there is "Sparc Solaris" further down in the list. Once I selected that, I was able to populate the channel with patches.
Daryl On Tue, Nov 11, 2014 at 10:07 AM, Amedeo Salvati <[email protected]> wrote: > I never used sparc repositories, and for this I can make a mistake, but > logically you can't define a repository/ies and define only a channels > (with sparc option on arch) and then you will push your packages by using > rhnpush -> so you will use a repo if you have an upstream that will be on > sync to your spacewalk > > hth > Amedeo Salvati > > Da: [email protected] > A: [email protected] > Cc: > Data: Tue, 11 Nov 2014 09:54:00 -0600 > Oggetto: Re: [Spacewalk-list] Follow up question to solaris2mpm > > > Okay, I'm making progress, but I've ran into another road-block. > > > I figured out that I need to add --dir to my syntax. That seemed to > resolve the error with rhnpush not being able to find the patch. However, > now I'm getting the following error: > > > Error Message: > > Package arch sparc-solaris-patch incompatible with channel solaris-10 > > Error Class Code: 50 > > Error Class Info: Invalid information uploaded to the server > > > Adding verbose to the syntax revels this: > > > Package > /usr/local/src/mpm_patches/patch-solaris-151355-01-1.sparc-solaris-patch.mpm > already exists on the RHN Server-- Skipping Upload.... > > > The SW server is CentOS 6.5, while the server with the Solaris patches > is a Solaris 10 server. The patches are not on the SW server. So, I'm > wondering if I have my channel/repository setup correctly? > > > I'm wondering if the Repository URL is correct? > > > On the SW server I have the following directory configured: > > > /var/satellite/solaris > > > So, I have the following Repository URL. > > > file:///var/satellite/solaris > > > The patches are not out on the net anywhere. I downloaded them, and I > put them in the mpm format. So I think that it is proper to use the file:// > syntax in that field. Is that correct? Should I copy the mpm files to that > directory first? > > > Thanks > > > Daryl > > > > > > > > > > On Tue, Nov 11, 2014 at 9:02 AM, Daryl Rose <[email protected]> wrote: > >> > Never mind. I decided to try and add a -vv to the syntax and saw that >> it is actually hitting my SW server. So, I authenticated with my >> administrator user and password. >> >> > Now I get the following error: >> >> > Package patch-solaris-126440-01-1.sparc-solaris-patch.mpm Not Found on >> RHN Server -- Uploading >> > Uploading package patch-solaris-126440-01-1.sparc-solaris-patch.mpm >> > Using POST request >> >> > I'm not sure what it means by it can't find the patch on the RHN >> server. This command is supposed to be uploading the patches to the server. >> >> > Thoughts? >> >> > Thank you >> >> > Daryl >> >> >> > On Tue, Nov 11, 2014 at 8:49 AM, Daryl Rose <[email protected]> wrote: >> >>> > I know that I was told that Solaris support will be dropped in future >>> releases, but I'm still moving forward with trying to make this version >>> work. >>> >>> > I've figured out that solaris2mpm will work with individual patches, >>> but not on the Solaris Patch Cluster. So, my work around is to unzip the >>> cluster, zip up the individual patches and then run solaris2mpm on those >>> individual patches. I now have a directory with mpm files that can be >>> added to my SpaceWalk server. >>> >>> > According to the documentation, I need to run "rhnpush --server= >>> http://SW_FQDN/APP --channel=CHANNEL_LABEL *.mpm". However, when I run >>> this command, I get prompted for a Red Hat Network username. >>> >>> > This command should be accessing my SW server, not RHN. >>> >>> > Can I copy these file from the client server to the SW server and put >>> them in the channel that way, or do they have to be copied via the rhnpush >>> command? >>> >>> > Thanks >>> >>> > Daryl >>> >> >> > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
