Steve Langasek <[EMAIL PROTECTED]> writes:
> On Wed, Nov 22, 2006 at 09:03:34PM +0100, Goswin von Brederlow wrote:
>
>> > reassign 399384 r-cran-fmultivar
>> > found 399384 221.10064a-1
>> > close 399384 240.10068-1
>> > thanks
>
>> > On Sun, Nov 19, 2006 at 09:32:37AM +0100, Goswin von Brederlow wrote:
>> >> Package: r-cran-fmultivar
>> >> Version: 240.10068-1
>> >> Depends: libc6 (>= 2.3.5-1), libgcc1 (>= 1:4.1.1-12), libgfortran1 (>=
>> >> 4.1.1-12), r-base-core (>= 2.4.0), r-cran-fbasics, r-cran-fseries,
>> >> r-cran-fcalendar, r-cran-fecofin, r-cran-mvtnorm, r-cran-mgcv
>
>> >> There seems to be a mismatch between the libgfortran library in
>> >> Depends and the one actualy used.
>
>> > No, you're simply reporting this bug against a different version of
>> > r-cran-fmultivar than the one that was actually used in your build.
>
>> Sorry. I missed that the version moved into testing between the
>> compile and me reporting the bug.
>
> FWIW, it had not; it only moved into testing after you filed the bug,
> because the sparc build had gotten stuck due to uninstallable build-deps and
> I gave the build back in reaction to your bug report. ;) So you might want
> to still double-check how you're determining the versions of packages to
> file these bugs against.
Ups, you are right. Typo in the script that checks versions for
me. Used VER1 instead of VER2. Rewrote that part now to use VER_TESTING
and VER_UNSTABLE to avoid that. My bad.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
