Fixing #654506 and #674386 in Wheezy

Mehdi Dogguy mehdi at dogguy.org
Wed Jul 11 14:30:19 UTC 2012


On 11/07/12 16:01, Felipe Sateler wrote:
> On Wed, Jul 11, 2012 at 8:20 AM, Mehdi Dogguy<mehdi at dogguy.org>
> wrote:
>> Hi,
>>
>> We would like to fix #654506 and #674386 in Wheezy. Unfortunately,
>> we are not able to accept supercollider/1:3.5.2-1 from Unstable
>> since the changes are quite large.
>
> I think you mean 1:3.5.3~repack-1?

Yes, sorry. It was a bad copy/paste :/

> That is what's currently in unstable, and 1:3.5.2-1 was uploaded
> before the freeze. Unfortunately, it couldn't migrate because it
> failed to build on non-x86 archs. We are currently working on fixing
> that. So, in a way, the changes are not that large ;).
>

We don't seem to have the same definition of "large". For this specific
case, the changes between the unblocked version and sid's current
version look like:

$ debdiff supercollider_3.5.2-1.dsc supercollider_3.5.3~repack-1.dsc \
   | diffstat | tail -n1
  3040 files changed, 5266 insertions(+), 581639 deletions(-)

This pretty looks as "large". Ignoring the bits that were deleted when
repacking, the debian/ directory, etc… this leads us to:

  53 files changed, 746 insertions(+), 701 deletions(-)

which is nicer indeed but still qualifies as large.

Why did you import 3.5.3 instead of working on fixing 3.5.2? (I'm not
sure it is relevant now but that might help us to understand the
situation better).

> I had planned to mail d-r after we got the last round of fixes ready.
> Is there a chance we can convince you to let 3.5.3 migrate to
> testing?
>

We would prefer targeted fixes based on the version of testing.

Kind Regards,

-- 
Mehdi Dogguy مهدي الدڤي



More information about the pkg-multimedia-maintainers mailing list