Re: Supercollider in wheezy
On Sun, 2012-08-19 at 18:05 -0400, Felipe Sateler wrote: > On Sun, Aug 19, 2012 at 5:56 PM, Adam D. Barratt > wrote: > > On Wed, 2012-08-15 at 18:23 -0400, Felipe Sateler wrote: > >> I write to fix the issue of supercollider in wheezy. Current SC in > >> testing is upstream version 3.4.5. Current in sid is 3.5.3. The > >> version in wheezy has a FTBFS bug (#674386), so we need to get rid of > >> that. Options are: > >> > >> 1. Upload a fix via tpu. > > > > Apparently this happened. Whilst the package does look sane, was that > > actually acked in advance? > > No. I was under the impression that the ack has to come after the > upload (because the rt uses the actuall uploaded package for the ack). We'd likely ack the proposed diff and then unblock after reviewing the actual uploaded diff. > The devref even says to wait until the package has built on all archs > before notifying the RT. I was waiting for that before sending a mail. Hmmm, we should probably review that, particularly during a freeze. fwiw, britney won't try and migrate the package until all the architectures are built anyway; that's "new", as in implemented within the past couple of years - I suspect the previous behaviour may have been the reasoning behind the devref suggestion. > I went for uploading the fixes to tpu because: > > 1. There was a fix available so it makes no sense to not fix the package. > 2. If 3.5 is going to be allowed to migrate, it should be because it > makes sense to have 3.5 instead of 3.4, and not because of some > unrelated bug. Sounds reasonable. I've added an "approve" hint (effectively an unblock for t-p-u); thanks. Regards, Adam ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Supercollider in wheezy
On Sun, Aug 19, 2012 at 5:56 PM, Adam D. Barratt wrote: > On Wed, 2012-08-15 at 18:23 -0400, Felipe Sateler wrote: >> I write to fix the issue of supercollider in wheezy. Current SC in >> testing is upstream version 3.4.5. Current in sid is 3.5.3. The >> version in wheezy has a FTBFS bug (#674386), so we need to get rid of >> that. Options are: >> >> 1. Upload a fix via tpu. > > Apparently this happened. Whilst the package does look sane, was that > actually acked in advance? No. I was under the impression that the ack has to come after the upload (because the rt uses the actuall uploaded package for the ack). The devref even says to wait until the package has built on all archs before notifying the RT. I was waiting for that before sending a mail. I went for uploading the fixes to tpu because: 1. There was a fix available so it makes no sense to not fix the package. 2. If 3.5 is going to be allowed to migrate, it should be because it makes sense to have 3.5 instead of 3.4, and not because of some unrelated bug. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Supercollider in wheezy
On Wed, 2012-08-15 at 18:23 -0400, Felipe Sateler wrote: > I write to fix the issue of supercollider in wheezy. Current SC in > testing is upstream version 3.4.5. Current in sid is 3.5.3. The > version in wheezy has a FTBFS bug (#674386), so we need to get rid of > that. Options are: > > 1. Upload a fix via tpu. Apparently this happened. Whilst the package does look sane, was that actually acked in advance? Regards, Adam ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Supercollider in wheezy
Dear Relase Team,
I write to fix the issue of supercollider in wheezy. Current SC in
testing is upstream version 3.4.5. Current in sid is 3.5.3. The
version in wheezy has a FTBFS bug (#674386), so we need to get rid of
that. Options are:
1. Upload a fix via tpu.
2. Migrate 3.5.3 to wheezy (we had uploaded 3.5.2 before the freeze,
but it didn't migrate because it didn't build in some archs. More
details later).
3. Remove sc from wheezy.
We would like to avoid option 3, and we favor option 2. At [1] there
is a description of the changes since the uploaded 3.5.2 version
before the freeze and the current version in unstable.
We would prefer the 3.5 series over the 3.4 series for the following reasons:
* SC 3.4.x relied optionally on a third-party java-based kit
("SwingOSC") to provide for building user interface widgets. (This
provides standard server- and addon-management interfaces as well as
user-made GUIs. It's not compulsory to have GUIs but it's typically
assumed in tutorials and the official book.) This was never packaged
for debian, so the provision is kinda incomplete. SC 3.5 includes a
QT-based widget system which provides all of this functionality and
with the same programming interface. It's very nice.
* The GEdit plugin "sced" has been updated to support GEdit version 3,
which is what is in wheezy. (We previously just deactivated the gedit
plugin in wheezy which is a shame as it's a recommended editor for
beginners.)
* The old and overgrown SCons build system has been removed in favour
of Cmake. Requires much less downstream packaging effort.
* User config files are moved to a much more XDG-friendly location:
instead of ~/share/supercollider it's now
~/.local/share/SuperCollider and ~/.config/SuperCollider. (Old
config is detected and migration info is output.)
* Other changes, detailed in http://doc.sccode.org/Guides/News-3_5.html
If a migration of sc from sid to testing is unacceptable, we can
upload a fix to t-p-u. However, g++ 4.7 ICEs while building 3.4.
Therefore, the fix would have to include a build-dependency on gcc/g++
4.6 and force its use in debian/rules, besides the fix for the build
failure. Full diff attached.
[1]
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-July/028351.html
--
Saludos,
Felipe Sateler
wheezy.diff
Description: Binary data
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
