Hi Debian,
I'm the Opera package maintainer.
This bug doesn't say what the cause for the needed conflict is.
However, the .5 (sarge) and .1 (static) builds released at the same
time as the specified .6 (etch) build almost certainly had whatever
fix was relevant, just as good as the .6 one did. So the final .6
suffix causes builds from the same day, but for sarge and older, to be
in conflict. It may thus make some sense to drop this suffix.
You would also do well to conflict with opera-static with version
numbers matching the same constraint as opera.
I've been told that the conflict has to do with the opera symlink in
/usr/X11R6/bin/: I suppose the 20061214 build is the first official
release your correspondent met in which the bug is fixed. However,
the bug was fixed in 2006/May (and went into assorted unofficial
builds between then and the official release). This should have gone
into the 9.00 official release. So, if the conflict is about the
symlink, you should be able to amend the version to 9.00-20060600 or
similar.
If the problem wasn't that symlink, I'd greatly appreciate it if you
can tell me the details. I can ask our QA team to give a more precise
date on the correct release version. If it's a bug I didn't notice
myself fixing, I may need to port it to newer branches of the
packaging scripts !
Edward Welbourne, for the Opera packaging team.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
