Bug#678679: Spice, current status and the fueture in Debian
On Wed, Jun 27, 2012 at 04:46:41PM +0930, Ron wrote: > > So far as I can see, you Michael and I all agree that the experimental > package is the only viable candidate for Wheezy. But you will lose that > option if you do not upload it very, very soon. The freeze happens in > the next few days. Michael, do you agree to upload spice 0.10.1-3~nocelt in experimental to unstable ? If you don't have time, I can upload. Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Bug#678679: Spice, current status and the fueture in Debian
28.06.2012 16:43, Liang Guo wrote: On Wed, Jun 27, 2012 at 04:46:41PM +0930, Ron wrote: So far as I can see, you Michael and I all agree that the experimental package is the only viable candidate for Wheezy. But you will lose that option if you do not upload it very, very soon. The freeze happens in the next few days. Michael, do you agree to upload spice 0.10.1-3~nocelt in experimental to unstable ? If you don't have time, I can upload. Yes, this should be a good candidate for the upload. The problem I have is not a time, but lack of any real internet access (I'm in a hotel till Jun-30). So if you can do the upload, please do it, maybe adding whatever other changes you think are missing still. I was hoped to have a more recent version of spice in wheezy, so maybe even the 0.11 version is better, but it is up to you (the nocelt patch should apply cleanly to 0.11 too). Thank you very much! /mjt -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fec645a.3020...@msgid.tls.msk.ru
Bug#678679: marked as done (Spice, current status and the fueture in Debian)
Your message dated Thu, 28 Jun 2012 08:51:42 -0700 with message-id <20120628155142.gb30...@virgil.dodds.net> and subject line Re: Bug#678679: Spice, current status and the fueture in Debian has caused the Debian Bug report #678679, regarding Spice, current status and the fueture in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 678679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tech-ctte Severity: normal Hi, Technical Committee, We'd like to decide how the spice[1] should be maintained in Debian. 1) Background The Simple Protocol for Independent Computing Environments (SPICE) is a remote display system built for virtual environments, just like vnc or remote desktop, but provide more rich feature and better performance. SPICE was developed by Qumranet[2], which was acquared by RedHat, RedHat is the primary sponsor of SPICE and includes it in RHEL (since 5.4) and RHEV platform. Spice has 2 different part, server part and client part, server part is intergrated to qemu, client part can be a standalone program, such as spice-gtk and virt-viewer, or run as a browser plugin. Spice client and spice server communicate with tcp socket. Spice can only works on x86 and i386 platform now. Spice project provide xserver-xorg-video-qxl and spice-vdagent as the guest xserver driver and the guest helper program to provide copy/pause support in qemu/kvm guest OS. 2) Celt, the root of our problem Spice uses celt[3] for audio codec. Different celt version may use different bitstream, it means that if Spice client want to correctly decode audio codec from spice server, it should use the same celt version as the spice server. For compatibility or other reason, the upstream decide to pin to celt 0.5.1. Celt is already in Debian[4], and is maintained by Ron Lee. For celt 0.5.1 is not maintained by upstream any more, including it in Debian may introduce potential security problem, so we decide to not include it in Debian. this problem has been discussed at bug 603699[5]. According messages from Ron, celt is offically dead, the upstream will not maintain it any more. A new codec, opus, is published as RFC by the IETF CODEC working group, and is encouraged to replace celt. Alon Levy is working on adding opus codec support to spice, but it is not merged into upstream git yet. Even opus codec support is added by upstream, in order to compatible with the previous version, they may not remove celt051 codec soon. 3) Current status of spice in Debian At the end of the discussion in bug 603699, I decide to package spice with a embeded celt051, and celt051 runtime library is in package libspice-server1[6] now. Spice package is in a bad shape, but it provide the same function as the upstream. Spice client program, spice-client and spice-gtk depends on libspice-server1, for they uses celt runtime library. xserver-xorg-video-qxl and spice-vdagent are in Debian and in a good shape. According the Popcon statistics[7], 0.13% Debian users uses spice-client, 3.21% Debian uses uses libspice-server1(for qemu/kvm depends on libspice-server1, this can be traded as qemu users), so 4% qemu/kvm user uses spice-client. 4) The fueture 4.1 Remove spice celt051 support in Debian Actually spice support another codec: RAW, when using raw codec, audio streams is not compressed, so more bandwidth is consumed, When using spice in Internet, the latency will become large and introduce bad user experience. Michael have tested the compatibility for spice server with and without celt051 and spice client with and without celt051, and send the patch[8] to the upstream, but the upstream refused to apply this patch, they insist spice should come with celt051 support now. We can apply this patch and ship spice without celt in Debian, but for we are not expert on spice and celt, and lack necessary device to test the compatibility with the upstream release, we may in the risk of shipping spice that not compatible with spice in other distribution. 4.2 Completely remove spice If spice is removed from Debian, We will not able to use debian as a spice server or spice client. We can still run Debian in RHEV or other spice compatible qemu/kvm hypervisor, xserver-xorg-video-qxl and spice-vdagent don't use celt. Thank you for your kindly help. [1] http://www.spice-space.org/ [2] http://en.wikipedia.org/wiki/Qumranet [3] http://celt-codec.org/ [4] http://packages.debian.org/search?keywords=celt&searchon=names&suite=all§ion=all [5] ht
Bug#614907: Draft resolution for node+nodejs
Hi all, Sorry this is so long in coming. Here's the draft resolution for this issue, agreed at the last IRC meeting. I thought about including a statement censuring nodejs upstream for their unhelpful behavior around this issue, but we didn't actually discuss that at the IRC meeting so I don't know if there's a consensus and don't want to hold this up any further. === Resolution === The Technical Committee reaffirms the importance of preventing namespace collisions for programs in the distribution, while recognizing that compatibility with upstreams and with previous Debian releases is also important and that sometimes an imperfect balance must be struck between these three goals. The Committee therefore resolves that: 1. The nodejs package shall be changed to provide /usr/bin/nodejs, not /usr/bin/node. The package should declare a Breaks: relationship with any packages in Debian that reference /usr/bin/node. 2. The nodejs source package shall also provide a nodejs-legacy binary package at Priority: extra that contains /usr/bin/node as a symlink to /usr/bin/nodejs. No package in the archive may depend on or recommend the nodejs-legacy package, which is provided solely for upstream compatibility. This package declares shall also declare a Conflicts: relationship with the node package. 3. The node source package shall rename its binary to /usr/sbin/ax25-node, and its binary package to ax25-node. 4. The node source package shall continue to build a transitional 'node' binary package for compatibility with deployed Debian installations, which provides /usr/sbin/node as a symlink to /usr/sbin/ax25-node. This package shall declare a reciprocal Conflicts: relationship with the nodejs-legacy package. Other packages may reference the 'node' package as a dependency or recommendation, but are encouraged to transition to 'ax25-node'. 5. The maintainers of these packages are required to implement the above changes immediately in unstable. Failing that, the Technical Committee reserves the right to NMU to implement these changes. 6. Once the above changes are implemented, the packages shall be considered suitable for release with respect to the Debian policy on conflicting packages. === End Resolution === Draft Ballot: 1. Approve transition plan for node and nodejs 2. Further discussion I'll wait for feedback until 30 Jun 00:00:00 UTC before calling for a vote, in case there are bugs above. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#614907: Draft resolution for node+nodejs
[Whoops, forgot the magic header for packages.qa.d.o; resending.] Hi all, Sorry this is so long in coming. Here's the draft resolution for this issue, agreed at the last IRC meeting. I thought about including a statement censuring nodejs upstream for their unhelpful behavior around this issue, but we didn't actually discuss that at the IRC meeting so I don't know if there's a consensus and don't want to hold this up any further. === Resolution === The Technical Committee reaffirms the importance of preventing namespace collisions for programs in the distribution, while recognizing that compatibility with upstreams and with previous Debian releases is also important and that sometimes an imperfect balance must be struck between these three goals. The Committee therefore resolves that: 1. The nodejs package shall be changed to provide /usr/bin/nodejs, not /usr/bin/node. The package should declare a Breaks: relationship with any packages in Debian that reference /usr/bin/node. 2. The nodejs source package shall also provide a nodejs-legacy binary package at Priority: extra that contains /usr/bin/node as a symlink to /usr/bin/nodejs. No package in the archive may depend on or recommend the nodejs-legacy package, which is provided solely for upstream compatibility. This package declares shall also declare a Conflicts: relationship with the node package. 3. The node source package shall rename its binary to /usr/sbin/ax25-node, and its binary package to ax25-node. 4. The node source package shall continue to build a transitional 'node' binary package for compatibility with deployed Debian installations, which provides /usr/sbin/node as a symlink to /usr/sbin/ax25-node. This package shall declare a reciprocal Conflicts: relationship with the nodejs-legacy package. Other packages may reference the 'node' package as a dependency or recommendation, but are encouraged to transition to 'ax25-node'. 5. The maintainers of these packages are required to implement the above changes immediately in unstable. Failing that, the Technical Committee reserves the right to NMU to implement these changes. 6. Once the above changes are implemented, the packages shall be considered suitable for release with respect to the Debian policy on conflicting packages. === End Resolution === Draft Ballot: 1. Approve transition plan for node and nodejs 2. Further discussion I'll wait for feedback until 30 Jun 00:00:00 UTC before calling for a vote, in case there are bugs above. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: CTTE IRC Meeting tomorrow June 28 2012 1700 UTC
Sorry I missed the meeting earlier, I got caught up with stuff at work which I had expected to finish by then... Ian. -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20460.63508.972303.623...@chiark.greenend.org.uk
