Bug 246801

Summary:	ZMD does not handle epoch of local RPMs
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Peter Surda <peter.surda>
Component:	Zenworks	Assignee:	E-mail List <zlm-code10-bugs>
Status:	RESOLVED WONTFIX	QA Contact:	Forgotten User YrvzK78Vmi <forgotten_YrvzK78Vmi>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	SLES 10
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Peter Surda 2007-02-19 17:40:15 UTC

If you install a RPM, zmd thinks it has epoch 0 regardless of what it actually is.

------------------------------------------
> rpm -q permissions --qf '%{NAME}-%{EPOCH}-%{VERSION}-%{RELEASE}\n'
permissions-1-2007.1.18-6

> rug search -i permissions
S | Catalog | Bundle | Name        | Version     | Arch
--+---------+--------+-------------+-------------+-----
i | System  |        | permissions | 2007.1.18-6 | i586

-------------------------------------------

Compare it to yum repository from which I installed it:

-------------------------------------------
> rug search -u permissions
S | Catalog           | Bundle | Name        | Version       | Arch
--+-------------------+--------+-------------+---------------+-----
v | local-blahblah    |        | permissions | 1:2007.1.18-6 | i586
-------------------------------------------

I was able to trace it as far as the database (the zmd.db), which contains 0 in the epoch column (for @system). Non-local catalogs (e.g. the one I installed it from) contain proper values. I tried digging in the zmd source but I am unfamiliar with C# and so far was not able to trace it any further.

I have SLES10:
> rpm -q zmd rug rpm
zmd-7.1.1.0-39.49
rug-7.1.1.0-18.23
rpm-4.4.2-43.7

Comment 1 Stanislav Visnovsky 2007-06-21 13:39:41 UTC

We are not going to fix this for openSUSE.