Re: source RPM "(contains no files)"

[Jeff Johnson <n3npq jbj gmail com>]

On Nov 14, 2006, at 6:19 PM, Tim Mooney wrote:

> In regard to: source RPM "(contains no files)", Kevin Cosgrove 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).

There are intrinsic incompatibilities in the format change that have  
forced
all rpm development to track with the lowest common denominator  
rpm-3.0.x
packaging. Everyone has had years to change.

73 de Jeff