Comment 6 for bug 7637

Daniel Burrows <email address hidden> writes:

> I just remembered that sig *1.2* is frozen for sarge, not 2.0, so
> there isn't a problem with uploading a new version. However, I'd rather
> not stress the autobuilders unnecessarily. I think that upstream is
> slowly working towards another release, and I was planning to just roll
> this into that release; does that work for you? (note that 2.0.4 might
> not make sarge in that case, depending on how long they take)
>
> Daniel

Not realy.

The amd64 and intel em64t cpus will be very common in the near future
and if all goes well sarge will have a 64bit kernel image for
them (so people don't have to compile their own).

The package has a FTBFS bug on those cpus because you fail to pass
"--host" and the configure script is too old to work without.
libsig2.0 needs to be fixed for sarge or removed. Since you just need
to update the generated files and add a "--host=..." in rules to be
policy compliant I don't see a reason to make an exception.

MfG
        Goswin