Bug 426848

Summary:	Broken dependencies in Fedora stable repository.
Product:	[Fedora] Fedora	Reporter:	Jan ONDREJ <ondrejj>
Component:	python-gammu	Assignee:	Xavier Lamien <lxtnow>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	russ+bugzilla-redhat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.24-1.fc8.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-03 17:05:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan ONDREJ 2007-12-27 10:39:31 UTC

Description of problem:
After unpushing gammu in fedora stable repositories (both F7 and F8) there are
broken dependencies.

Version-Release number of selected component (if applicable):
gammu-1.17.0-1.fc8
python-gammu-0.22-3.fc8

How reproducible:
Always

Steps to Reproduce:
1. yum install python-gammu
  
Actual results:
--> Running transaction check
---> Package python-gammu.i386 0:0.22-3.fc8 set to be updated
--> Processing Dependency: libGammu.so.2 for package: python-gammu
--> Finished Dependency Resolution
Error: Missing Dependency: libGammu.so.2 is needed by package python-gammu

Expected results:
You know. :-)

Additional info:
I can build this package, if you give me permissions to commit to this package.
I am in state "Awaiting Review" for commit to python-gammu.
Also there is a new release of python-gammu (0.24), which need to bude updated.

laxathom do not respond on my bodhi comment three days ago:
https://admin.fedoraproject.org/updates/F8/FEDORA-2007-4743

Comment 1 Cezary Zemis 2007-12-28 10:47:56 UTC

Perhaps this bug duplicates 425831.

Comment 2 Xavier Lamien 2007-12-30 15:28:57 UTC

*** Bug 427035 has been marked as a duplicate of this bug. ***

Comment 3 Jan ONDREJ 2008-01-03 17:05:06 UTC

I think somebody forgot to close this bug.