<div dir="ltr"><div class="gmail_quote">On Sun, May 8, 2011 at 4:38 PM, Alon Levy <span dir="ltr"><<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Sun, May 08, 2011 at 03:43:21PM +0400, Emre Erenoglu wrote:<br>
> Dear Developers,<br>
><br>
> I'm the package maintainer for some virtualization related packages in<br>
> Pardus distribution. I would like to take spice into our package<br>
> repositories, however, I'm facing an issue with the celt package.<br>
><br>
> I'm sure you're aware of the issue. Spice is depending on celt 0.5.1, while<br>
> we have version 0.10.0 in our repositories. The distribution managers are<br>
> not willing to introduce another version of the same celt package, nor<br>
> downgrading the existing one.<br>
><br>
> Is there any way to link spice to the newer celt, or are we in a dead end?<br>
><br>
<br>
</div></div>This problem has been raised multiple times on the list, you should read the<br>
archives. To recap: historically when spice had to choose a codec it chose the<br>
current celt then, 0.5.1. That celt is not compatible with newer celts. The<br>
decision was to wait for celt's on wire format to stabilize. This hasn't happened<br>
yet (perhaps it will happen soon). It is however possible to introduce support<br>
for multiple codecs and have the client and server negotiate. This will still not<br>
allow a celt 0.10.0 linked spice server to connect to celt 0.5.1 client, or vice<br>
versa.<br></blockquote><div><br></div><div>Thanks Alon, I know the history, I had a small hope that situation could have been resolved by now. Anyway, I understand that spice is not compatible with 0.10 and therefore we can't link it to the celt in our repository. </div>
<div><br></div><div>In this case, I will try to negotiate with the distribution managers to see what we can do to include spice in the repos.</div></div>-- <br>Emre<br>
</div>