> olpcsound is a subset of the Csound sound and music
> synthesis system, tailored specifically for XO platform.
Still you can set proper "Conflicts" tags. In particular, since this
package provides the same SONAMEs as csound:
olpcsound-5.08.92-12.fc11.i386 in rawhide-development-i386
File conflict with: csound-5.03.0-16.fc9.i386
File conflict with: csound-jack-5.03.0-16.fc9.i386
File conflict with: csound-osc-5.03.0-16.fc9.i386
File conflict with: csound-python-5.03.0-16.fc9.i386
olpcsound-devel-5.08.92-12.fc11.i386 in rawhide-development-i386
File conflict with: csound-devel-5.03.0-16.fc9.i386
There is nothing to triage here.
Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it.
F10 is affected, too.
Still reproducible with:
As I said before olpcsound was never meant to anything but
a XO (OLPC) specific subset of Csound. (What do you mean
I don't know what you want,
somehow this package was moved to be built for other targets than
OLPC, which was meant in the beginning.
So if you have a suggestion for a solution, please say so, because
I am not sure what needs to be done here.
If this package is in Fedora 10 and Fedora 11 Development by mistakes, then contact Fedora Release Engineering and request removal. If you haven't done these builds, reassign this ticket to the right person, please.
All I see is a package that conflicts with other packages and also conflicts with SONAME Provides. That's bad.
I'd like to see this getting fixed. I'm willing to take this in front of FESCo or similar if you continue with such desinterest.
OK, I am happy to make any changes to the package as long as I know
what changes need to be done, which I don't. If you know what needs to be
done, please let me know. It is not a question of disinterest.
I have requested the removal of olpcsound from the FC* targets:
Looking at http://fedoraproject.org/wiki/Packaging/Conflicts
I am not allowed to mark the package with a Conflicts field. The
only other solution would be to rename binaries, but there are
olpc programs that link to the existing libraries and these
will be broken. So that would be perhaps more confusing.
Another solution is to remove the Csound 5.03 package, which
is old and obsolete. In fact, there is a newer package version
which should have been the one to be included in FC builds instead
(that would also cause conflicts nevertheless).
You misread the packaging guidelines. Take your time and read them more slowly.
Btw, even with explicit "Conflicts:" tags in this package, there would still be the conflicting SONAME Provides, which require another fix.
I've contacted the person in charge of the Fedora builds. [Something's wrong here. The pkgdb doesn't list him at all.] If you don't take care of these builds, you ought not be the one to receive the bugzilla tickets.
> You misread the packaging guidelines. Take your time and read them more
To me it reads like there is a file conflicts issue and renaming is
what they tell you to do. The only other chance for using Conflicts is
to ask them permission. You can enlighten me otherwise.
> Btw, even with explicit "Conflicts:" tags in this package, there would still > be the conflicting SONAME Provides, which require another fix.
I don't know how to fix this.
> If you don't take care of these
> builds, you ought not be the one to receive the bugzilla tickets.
I was the packager and maintained the OLPC-N builds, I have never
built the FC ones. I see that probinson was the person doing
the FC builds. Should this be reassigned to him?
is what is relevant here.
> The only other chance for using Conflicts is
> to ask them permission.
Yes, that ought to be done, if there is no other fix.
The conflicting SONAME Provides are this (that multiple csound pkgs provide it is another separate problem):
$ repoquery --whatprovides libcsound.so.5.1
olpcsound-0:5.08.92-15.fc11.i386 <-- (!)
Typically, the shorted package name (of a pkg that provides something) wins during Yum depsolving, but that's not the point here. Here are implicit conflicts in files and library sonames, and they are not allowed.
Thanks. I suppose if we end up having to change the SONAME, that
will break the packages linked agains olpcsound in OLPC, will
I see that the if this is an implicit conflict, then we can just
mark it as so in the spec.
I've been slowly investigating this in my spare time (which has been minimal during march but is improving this week) and it seems that once we get Fedora up to csound versions either 5.08 or 5.10 the olpcsound package can just go away all together. See a short discussion on the olpc-devel list  and the requirements of sugar 0.84  for more details. It seems the main reason Fedora has such an ancient version of csound is due to lack of time for the maintainer (See bug 250829 for details). I'm in the process of updating the spec for a 5.10.1 build that builds on rawhide and will file a bug, which this one will depend on, with the updated csound package and we'll take it from there.
I've created an updated csound package and filed a bug to update csound to 5.10, once this is done olpc sound can be obsoleted by csound and be marked as a dead package.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I've just built csound 5.10.1-7 for F-12/rawhide which obsoletes olpcsound. Victor are you happy if I mark olpcsound as a dead package as I think now with csound 5.10 in mainline now everything that is needed by OLPC is now included in csound?
csound-5.10.1-7.fc11 has been submitted as an update for Fedora 11.
csound-5.10.1-7.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update csound'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6801
csound-5.10.1-7.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
oplcsound still conflicts with csound in Rawhide.
* The Obsoletes added to csound are not high enough.
> Obsoletes: olpcsound <= 5.08
Ought to be:
> Obsoletes: olpcsound <= 5.08.92
* The Obsoletes for olpcsound-devel are missing.
* olpcsound ought to be removed from Rawhide. If it cannot be untagged, ask Fedora Release Engineering to do it.
Fixed in rawhide. I will get the olpcsound untagged.
*** Bug 517358 has been marked as a duplicate of this bug. ***