Hello all,
I noticed yesterday while polishing up gdata-sharp for review that, after the fixes in the latest Rawhide mono packages, it was no longer necessary to use mono-nunit22; the unit tests compile just fine against mono-nunit.
There are several packages that are still depending, directly or indirectly, on mono-nunit22, and if we could work through them in time for the beta release, that would be super!
$ repoquery --alldeps --whatrequires mono-nunit22 banshee-0:1.5.1-0.2.git20090831.fc12.i686 mono-sharpcvslib-0:0.35-11.fc12.x86_64 mono-nunit22-devel-1:2.2.10-10.fc12.i686 banshee-0:1.5.1-0.2.git20090831.fc12.x86_64 nant-1:0.85-30.fc12.x86_64 mono-nunit-0:2.4.2.3-2.fc12.x86_64 monodevelop-0:2.0-5.fc12.x86_64 mono-nunit22-1:2.2.10-10.fc12.x86_64 mono-nunit22-devel-1:2.2.10-10.fc12.x86_64
The banshee dependency is through banshee --> boo --> nant. nant BRs nunit22 directly, and also inherits the dependency through its requirement on mono-sharpcvslib.
How repoquery computed that mono-nunit depends on mono-nunit22 is rather odd. Could anyone shed a light on this?
Regards,
2009/9/3 Michel Alexandre Salim michael.silvanus@gmail.com
Hello all,
I noticed yesterday while polishing up gdata-sharp for review that, after the fixes in the latest Rawhide mono packages, it was no longer necessary to use mono-nunit22; the unit tests compile just fine against mono-nunit.
There are several packages that are still depending, directly or indirectly, on mono-nunit22, and if we could work through them in time for the beta release, that would be super!
$ repoquery --alldeps --whatrequires mono-nunit22 banshee-0:1.5.1-0.2.git20090831.fc12.i686 mono-sharpcvslib-0:0.35-11.fc12.x86_64 mono-nunit22-devel-1:2.2.10-10.fc12.i686 banshee-0:1.5.1-0.2.git20090831.fc12.x86_64 nant-1:0.85-30.fc12.x86_64 mono-nunit-0:2.4.2.3-2.fc12.x86_64 monodevelop-0:2.0-5.fc12.x86_64 mono-nunit22-1:2.2.10-10.fc12.x86_64 mono-nunit22-devel-1:2.2.10-10.fc12.x86_64
The banshee dependency is through banshee --> boo --> nant. nant BRs nunit22 directly, and also inherits the dependency through its requirement on mono-sharpcvslib.
How repoquery computed that mono-nunit depends on mono-nunit22 is rather odd. Could anyone shed a light on this?
I believe spot did this because of some included precompiled binary
2009/9/3 David Nielsen gnomeuser@gmail.com:
2009/9/3 Michel Alexandre Salim michael.silvanus@gmail.com
How repoquery computed that mono-nunit depends on mono-nunit22 is rather odd. Could anyone shed a light on this?
I believe spot did this because of some included precompiled binary
Ah, but how?
$ rpm -q --requires mono-nunit /bin/sh glib2-devel mono(System) = 1.0.5000.0 mono(System.Runtime.Remoting) = 1.0.5000.0 mono(System.Xml) = 1.0.5000.0 mono(mscorlib) = 1.0.5000.0 mono(mscorlib) = 2.0.0.0 mono(nunit-console-runner) = 2.4.8.0 mono(nunit.core) = 2.4.8.0 mono(nunit.core.interfaces) = 2.4.8.0 mono(nunit.framework) = 2.4.8.0 mono(nunit.util) = 2.4.8.0 mono-core = 2.4.2.3-2.fc12 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1 rpmlib(PayloadIsXz) <= 5.2-1
Thanks,
mono@lists.stg.fedoraproject.org
-
David Nielsen -
Michel Alexandre Salim