[SCM] xvidcore packaging branch, master, updated. upstream/1.2.2-16-g5c1e21e

[Reinhard Tartler]

fabian-guest at users.alioth.debian.org writes:

> The following commit has been merged in the master branch:
> commit 5c1e21e327b04d86140e8ffa31bae3f435110b81
> Author: Fabian Greffrath <fabian at greffrath.com>
> Date:   Fri Jun 26 09:00:00 2009 +0200
>
>     Imported Debian patch 1.2.2+debian-0fab5

This was a really huge patch. I know that we discussed this via email
before, but there has been regressions here. Specifically this hunk:

> diff --git a/debian/control b/debian/control
> index c07b7a3..7eed0d8 100644
> --- a/debian/control
> +++ b/debian/control
> [...]
> -               nasm [i386 amd64]
> +               yasm (>= 0.8) [i386 amd64] | nasm (>= 2.0) [i386 amd64]
> [...]

your comment for this seems to be this:

> +xvidcore (1.2.2+debian-0fab2) unstable; urgency=low
> +
> +  * debian/control: Adjusted Build-Depends on nasm and yasm.

can you please elaborate here? unstable only has yasm version 0.7, no
idea where you have yasm 0.8 from. when sbuild encounters an alternative
(|) dependency, it will always check for existence for the package. If
that is positive, it will be installed. After having all packages
installed, it will then check the package version. here it will always
fail.

I generally suggest to just avoid alternate dependencies if
possible. Fabian, you seem to have some expertise here, can you please
give a rationale for the required versions and ideally decide what
assembler should be used on what arch? We can of course use yasm on i386
and nasm on amd64 iff there is a point in doing so.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4