Re: Use with Ximian RPMs?
John HEARNS <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <1026837092.4633.61.camel@ues4> |
On Tue, 2002-07-16 at 18:16, Hunter Matthews wrote: > On Tue, 2002-07-16 at 12:02, John HEARNS wrote: > > > > > Incidentally, I have come across a similar problem recently. > > No names, no pack drill (this is a public list) > > A package was upgraded - RPM renamed from package-1.1.rpm to > > package-latest.rpm > > Current barfs on this also when trying to create a channel > > (it tries to find package-1.2.hdr for instance) > > No fault at all in current. > > > > I'm no RPM expert at all, but I idly wonder if there is a better > > way than getting the version number from the file name. > > Guess this would involve some fundamental changes, so I'll > > keep quiet. > > We don't. We use the rpm python bindings to get that information from > the rpm itself. The only thing we use the filename for is actually > finding the package on disk. > Aha. I learn. > What does rpm -qpi package-latest.rpm tell you? I don't want to get too deeply into this - I didn't build it. but in short: Name: package Version: 7.2 Release: 1.30 Source RPM: package-7.2-1.30.src.rpm As I say - current is correct. The package should be named differently, IMHO.