Re: first try at actions of suiteparse/openmpi transition (was: Re: SuiteSparse 3.2.0->3.4.0 transition)
Rene Engelhard wrote:
> Rene Engelhard wrote:
> > Can the RM team then please:
> > a) add a hint
> > hint freemat/3.6+dfsg-8+b1 illuminator/0.11.0-3 hypre/2.4.0b-2 openmpi/1.3.2-4 lp-solve/184.108.40.206-6 octave3.0/1:3.0.5-6+b1 octave3.0/1:3.0.5-6+b2 openoffice.org/1:3.1.0-5 petsc/3.0.0.dfsg-5 trilinos/9.0.3.dfsg-1 python-scipy/0.7.0-1+b1 pysparse/1.0.1-5.1 pysparse/1.0.1-5.1+b1 
> > (no idea about the correct version specifiers for bin-NMUs and what do to
> > in the ocave3.0 case where different archs have different +bX)
> please apply. The last package needing aging (mono) will become aged
> this next nights (18->19.) testing run.
OK, it's now, but there's need for the hint be extended with a hint for
mono/mod-mono going in together.
Unfortunately mod-mono is broken right now (and only 2/10) anyway.
02:30 < _rene_> directhex: ping?
02:31 < directhex> _rene_, what's up?
02:31 < _rene_> mod-mono, and it being uninstallable virtually everywhere
02:31 < _rene_> which would break its transition to testing which breaks monos
which breaks two transitions' :)
02:32 < directhex> _rene_, uninstallable? hm, let me check that
02:32 < _rene_> libapache2-mod-mono/i386 unsatisfiable Depends:
mono-apache-server (>= 2.4.2) | mono-apache-server2 (>= 2.4.2)
| mono-apache-server1 (>= 2.4.2)
02:33 < _rene_> (just verified that it's indeed uninstallable)
02:33 < directhex> oh bollocks
02:33 < directhex> i see it
02:39 < directhex> here's your problem:
02:39 < directhex> binary NEW
02:39 < KiBi> yay for NEW!
02:39 < directhex> which is even more out of my hands than most things
hint mono/2.4+dfsg-6 mod-mono/2.4.2-1 xsp/2.4.2-1 should then work afaics
when xsp is out of NEW....
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' firstname.lastname@example.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73