In regard to: Re: [Networker] NetWorker client RPMv3, Clark, Patti said (at...:

Do you get an error when you attempt to --resign/--addsign to
the package,
or does signing it just corrupt the package?

Per the RHN Satellite list, RPMv4 only corrupts packages signed via
RPMv3.

That's what I thought, but I couldn't remember for certain so I thought
I better ask.

 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.

Not true; there is another option.

One could install the lgtoclnt RPM on your build box, and then use your
own spec file to scoop up the binaries that legato's RPM dropped on the
system and create a binary RPM.  You're repacking a binary only package
so there will be no %prep, no %build, and likely no %install.  I've done
this type of thing before (not for lgto* RPMs, yet), and it works fine.
It's not as nice as having the source, but on the positive side, your
home-grown RPM for the lgtoclnt package can avoid some of the problems
with the stock EMC RPM (such as never incrementing the release -- I would
make it match the build #) and not correctly handling upgrades.

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

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