Bug 214269

Summary: autoyast2-utils-2.14.8-2 conflicts
Product: [openSUSE] openSUSE 10.2 Reporter: Olaf Hering <ohering>
Component: YaST2Assignee: Lars Vogdt <lars.vogdt>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: andreas.hanke
Version: Alpha 5 plus   
Target Milestone: ---   
Hardware: PowerPC   
OS: Linux   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Olaf Hering 2006-10-22 13:41:24 UTC 
file /usr/bin/create_package_descr from install of inst-source-utils-2006.10.22-1 conflicts with file from package autoyast2-utils-2.14.8-2
file /usr/bin/create_update_source.sh from install of inst-source-utils-2006.10.22-1 conflicts with file from package autoyast2-utils-2.14.8-2

why is this line in inst-source-utils.spec?

Obsoletes:      autoyast2-utils <= 2.14.6
Comment 1 Andreas Hanke 2006-10-22 14:02:55 UTC 
Why is autoyast2-utils still provided at all?

(In reply to comment #0)
> why is this line in inst-source-utils.spec?
> 
> Obsoletes:      autoyast2-utils <= 2.14.6

Because 2.14.6 is supposed to be the last version of autoyast2-utils, now dropped and replaced by inst-source-utils.

Might this be wrong? According to

http://lists.opensuse.org/opensuse-commit/2006-10/msg00786.html

the last version of autoyast2-utils was not 2.14.6, but 2.14.9!
Comment 3 Lars Vogdt 2006-10-23 11:47:24 UTC 
1) Error in specfile: should be Obsoletes:      autoyast2-utils <= 2.14.10

2) autoyast2-utils should not exist in STABLE any more

To 1: should be fixed with next rebuild

To 2: should already be fixed. I'll check this
Comment 4 Olaf Hering 2006-10-23 12:41:55 UTC 
why does it obsolete a specific version?
doesnt make much sense.
if it does, add a comment to the specfile.
Comment 5 Andreas Hanke 2006-10-23 13:27:01 UTC 
(In reply to comment #4)
> why does it obsolete a specific version?
> doesnt make much sense.

This is basically due to a proposal that originated from me, and there are cases where it clearly makes sense:

"Obsoletes" without version means "Obsoletes all versions", and this can cause troubles for cases where the obsoleted package name is re-introduced again later.

Assuming that the autoyast2-utils package name would be re-introduced again later, you would have to make autoyast2-utils obsolete inst-source-utils. Result: The packages are mutually obsoleting each other.

The version can be left out in cases where the old package name will never be reintroduced again (but really only then - the obove scenario already happened with kopete -> kdenetwork3-InstantMessenger -> kopete, where the kopete package was reintroduced after it had been obsoleted without version).

Whether the versioned obsoletes makes sense here, I'm not sure, because the packages have different versioning schemes. But it should not cause troubles if the version is correct (that is, it *really* corresponds to the last existing autoyast2-utils package).
Comment 6 Lars Vogdt 2006-10-24 23:32:33 UTC 
Close as fixed:
- specfile updated
- package autoyast2-utils doesn't exist in factory any more