Re: Request to remove ikvm from testing & etch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Langasek wrote:
> On Thu, Oct 19, 2006 at 11:04:15PM -0700, Dave Beckett wrote:
>
>> ikvm is too buggy to ship in a release, it needs to be removed
>> from testing. the 2 RC bugs it has so far should be marked
>> somehow as not-for-etch. They won't be closing anytime soon
>> since ikvm still has big building problems.
>
> I don't understand. You're saying the RC bugs it has should be marked as
> not-for-etch, but the package itself is also not for etch? Why?
>
> The RC bugs currently filed against ikvm are listed as applying only to the
> version of ikvm in unstable. Is there reason to believe they also apply to
> the version in testing? Are there other reasons why the version of ikvm in
> testing is unreleasable?
The ikvm in testing (0.18.0.0-2) managed to get compiled and built at some
point in the past. Since then, the mono compiler and runtimes have moved on
so that the version in testing won't compile (FTBFS). When the runtime and
compiler changes below the application, it can't be detected.
The same failure to build applies to ikvm in unstable, and also the latest
release of ikvm (0.30.0.0) won't build either.
Yes, I'm considering orphaning this.
Dave
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFOrdTQ+ySUE9xlVoRAnGWAKCkYeJ8athKkxaKrE++4d6WhsVcUgCfcBHj
tj9zYhiUiV3m0lWgwmymqBI=
=LOSE
-----END PGP SIGNATURE-----
Reply to: