In regard to: Re: source RPM "(contains no files)", Jeff Johnson said (at...:
I created an rpm with rpm-3.0.6. I subsequently upgraded to rpm
4.4.6. Now when I list the rpm contents with 'rpm -qip <package>'
I get
(contains no files)
I've seen this too, though I thought it was because the Source RPMs in
questions were generated with RPM 2.5.6.
Yep. rpm-3.0.x and earlier stored paths as absolute file names,
rpm-4.0.x and later stores paths as a (dirname,basename,dirindex)
triple.
I've removed the code from rpm-4.4.6 after years of patiently waiting.
I'll be happy to send you a patch to restore the behavior, and writing a
conversion utility is not hard either (but all signatures/digests on the
original
package will be lost).
I certainly don't need it; when I need to explode one of our older
source RPMs, I just use your rpm2cpio script to extract the bits.
Works great.
Tim
--
Tim Mooney mooney@xxxxxxxxxxxxxxxxxxxxxxxxx
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
