[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]


Looks like every build of the package results in a random public key
signature. So, it gets built once on amd64 and once on i386, resulting
in this problem.

This should probably be addressed. Does upstream IKVM not distribute a
public/private pair like Mono does? If so, we should work with them to
address this.

In the meantime, at least stabilizing the keys between a the exact
version on separate archs would solve MY problem. is there any reason
that ikvm is not architecture all? Looks like all the platform specific
pieces are in other packages anyways.

Reply to: