Re: Problem with some RPM's

On Mon, 2002-11-11 at 04:26, Klaus Steinberger wrote:
> Hello,
> 
> I've got the following problem with some RPM's from IBM for the Tivoli 
> Storage Manager Software:
> 
> When I add them to a channel on my current server, anything run's well 
> until a machine want's to fetch the header for one of those packages. I 
> get then the following error Message:
> 
> Fetching rpm headers...
> There was a fatal error communicating with the server.  The message was:
> 404: "Not Found" while attempting to get
> $RHN/lmugar-i386-7.3/getPackageHeader/TIVsm-BA-5.1.5-0.i386.hdr

Try running Johns query against these rpms, and see what you get:

  rpm -qp --queryformat "%{NAME}-%{VERSION}-%{EPOCH}\n" <filename>

> 
> After some investigation I found out, that getPackageHeader directory 
> contain's indeed the files, but without the version number:
> 
> [root@etprd02 getPackageHeader]# ls TIV*
> TIVguid.i386.hdr              TIVsm-BA.GPFS.i386.hdr
> TIVsm-API.i386.hdr            TIVsm-BA.i386.hdr
> TIVsm-API.msg.de_DE.i386.hdr  TIVsm-BA.msg.de_DE.i386.hdr
> TIVsm-API.msg.es_ES.i386.hdr  TIVsm-BA.msg.es_ES.i386.hdr
> TIVsm-API.msg.fr_FR.i386.hdr  TIVsm-BA.msg.fr_FR.i386.hdr
> TIVsm-API.msg.it_IT.i386.hdr  TIVsm-BA.msg.it_IT.i386.hdr
> TIVsm-API.msg.ja_JP.i386.hdr  TIVsm-BA.msg.ja_JP.i386.hdr
> TIVsm-API.msg.ko_KR.i386.hdr  TIVsm-BA.msg.ko_KR.i386.hdr
> TIVsm-API.msg.pt_BR.i386.hdr  TIVsm-BA.msg.pt_BR.i386.hdr
> TIVsm-API.msg.zh_CN.i386.hdr  TIVsm-BA.msg.zh_CN.i386.hdr
> TIVsm-API.msg.zh_TW.i386.hdr  TIVsm-BA.msg.zh_TW.i386.hdr
> 
> Also the original files do not contain the version number in the name.
> That are the rpm's:
> 
> [cdadmin@bagheera RPMS]$ ls TIV*
> TIVguid.i386.rpm              TIVsm-API.msg.ko_KR.i386.rpm 
> TIVsm-BA.msg.fr_FR.i386.rpm
> TIVsm-API.i386.rpm            TIVsm-API.msg.pt_BR.i386.rpm 
> TIVsm-BA.msg.it_IT.i386.rpm
> TIVsm-API.msg.de_DE.i386.rpm  TIVsm-API.msg.zh_CN.i386.rpm 
> TIVsm-BA.msg.ja_JP.i386.rpm
> TIVsm-API.msg.es_ES.i386.rpm  TIVsm-API.msg.zh_TW.i386.rpm 
> TIVsm-BA.msg.ko_KR.i386.rpm
> TIVsm-API.msg.fr_FR.i386.rpm  TIVsm-BA.i386.rpm 
> TIVsm-BA.msg.pt_BR.i386.rpm
> TIVsm-API.msg.it_IT.i386.rpm  TIVsm-BA.msg.de_DE.i386.rpm 
> TIVsm-BA.msg.zh_CN.i386.rpm
> TIVsm-API.msg.ja_JP.i386.rpm  TIVsm-BA.msg.es_ES.i386.rpm 
> TIVsm-BA.msg.zh_TW.i386.rpm
> 
> 
> 
> So I suspect that IBM built their RPM's with the version number in the 
> file name, but distributed them differently.
> 
> Of course I could change the filename's of the RPM's and then recreate 
> the channel as a workaround.
> 
> But do you think we could do something inside current to get around this 
> problem, like not creating the .hdr file's from the filename but instead 
> according to the data inside the RPM?
> 
> Sincerely,
> Klaus Steinberger
> 
> -- 
> Klaus Steinberger         Maier-Leibnitz Labor
> Phone: (+49 89)289 14287  Am Coulombwall 6, D-85748 Garching, Germany
> FAX:   (+49 89)289 14280  EMail: [email protected]
> URL: http://www.physik.uni-muenchen.de/~k2/
> 
> In a world without Walls and Fences, who needs Windows and Gates
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.