Personally, no.  The thread on the satellite list suggested building a
virtual machine and threw out the RedHat 6.2 download link which has the
RPMv3 in it:
ftp://legacy.redhat.com/pub/redhat/linux/6.2/en/iso/i386/
<ftp://legacy.redhat.com/pub/redhat/linux/6.2/en/iso/i386/> 

To me that is a lot of work for the simple pleasure of resigning a
package.  I don't know how many other 3rd party packages you need to
resign.  I would push EMC to update their RPM package manager.  The sat
list was discussing sun java x86_64 specifically and there were a couple
of other companies providing software that were mentioned.  I wish I
could be of more help, but I've not reached the enviable point of
creating custom channels and pushing out networker, yet.  I would
certainly benefit if EMC fixed this issue.

Patti 
________________________________

From: Kenneth Holter [mailto:kenneho.ndu AT gmail DOT com] 
Sent: Friday, June 20, 2008 2:25 AM
To: EMC NetWorker discussion; Clark, Patti
Subject: Re: [Networker] NetWorker client RPMv3



         
        Yes, resigning the packages with RPMv3 would be an alternative.
I don't, however, have RPMv3 installed on any of our systems, and would
need to downgrade from RPMv4. I'm not sure if this is a very good idea,
as I'm afraid it will break my RPM DB. You don't happen to have
experience with this sort of issue?
        
         
        On 6/19/08, Clark, Patti <clarkp AT osti DOT gov> wrote: 

                > -----Original Message-----
                > From: EMC NetWorker discussion
                > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of
Tim Mooney
                > Sent: Thursday, June 19, 2008 12:22 PM
                > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
                > Subject: Re: [Networker] NetWorker client RPMv3
                >
                > In regard to: [Networker] NetWorker client RPMv3,
Kenneth
                > Holter said (at...:
                >
                > > Has anyone experienced the same issue? The way I see
it I
                > need either the
                > > source RPM so that I can rebuild it myself, or I
need an
                > ordinary client RPM
                > > built for RPMv4. Any thoughts?
                >
                > Does this have something to do with distributing the
package
                > via something
                > like Red Hat Network Satellite?
                >
                > Do you get an error when you attempt to
--resign/--addsign to
                > the package,
                > or does signing it just corrupt the package?
                >
                > Tim
                > --
                > Tim Mooney
Tim.Mooney AT ndsu DOT edu
                > Information Technology Services
(701)
                > 231-1076 (Voice)
                > Room 242-J6, IACC Building
(701) 231-8541 (Fax)
                > North Dakota State University, Fargo, ND 58105-5164
                >
                Per the RHN Satellite list, RPMv4 only corrupts packages
signed via
                RPMv3.  Unless the source is available (which it isn't
of course) the
                only choice is to resign the packages in question with
RPMv3 an option
                that wasn't in the list.  EMC is not the only 3rd party
presenting these
                types of issues.
                
                Patti Clark
                Sr. Unix System Administrator - RHCT, GSEC
                Office of Scientific and Technical Information
                
                
                


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER