Bug 216007

Summary:	Violated upgrade path
Product:	[Fedora] Fedora	Reporter:	Michael Schwendt <bugs.michael>
Component:	kbibtex	Assignee:	Christian Nolte <ch.nolte>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	extras-qa, kevin
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-12-07 10:53:09 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 Michael Schwendt 2006-11-16 19:29:00 UTC

Please see
https://www.redhat.com/archives/fedora-maintainers/2006-November/msg00190.html

and look for your e-mail address in that message.

Packages published for old distributions must have a lower Version-Release than packages for newer distributions.


(This is an automated bugzilla submission.
)

Comment 1 Kevin Fenzi 2006-12-05 21:32:09 UTC

Hey Christian. 

In an effort to get these E-V-R issues solved I took a look at this bug...

It appears you updated all the branches, but forgot to check in some patches. 
Then you fixed that on fc4/fc5 branches, but not on fc6 or devel. 

It looks like checking in the missing patches: 
kbibtex-0.1.5-filteredselection.patch
kbibtex-0.1.5-gcc4.2.patch
kbibtex-0.1.5-viewdocument.patch

And syncing up the spec file changes to fc6 and devel and doing a rebuild should
fix this. I did some test mock builds and they seemed to work fine...

If you could fix fc6/devel that would be great. If I don't hear from you soon I
will push in the fix myself...

Comment 2 Christian Nolte 2006-12-05 22:26:15 UTC

Thanks for your support Kevin! I have bumped the release version on the devel
branch to fix the problem. Furthermore I have requested a FC-6 branch as I
haven't have one. Let me know if I did something wrong to solve this problem.

Comment 3 Kevin Fenzi 2006-12-05 22:29:43 UTC

I sent you some private email already, but to add here... 
Your package already has a FC-6 branch. You just need to 'cvs update -d' to get
the new branch locally... 

(The -d is important to tell cvs you want new directories).

Comment 4 Christian Nolte 2006-12-05 22:43:03 UTC

Ok. Thanks again. I synced the branch and requested a build. This bug should be
fixed then.