Change logs for arpack source package in Jessie

  • arpack (3.1.5-3) unstable; urgency=medium
    
    
      * update the symbol list for mips64 & mips64el (Closes: #746277)
    
     -- Sylvestre Ledru <email address hidden>  Wed, 30 Apr 2014 18:26:52 +0200
  • arpack (3.1.5-2) unstable; urgency=medium
    
    
      * fix FTBFS on various port architectures by updating the symbol list.
        Thanks to Adrian Glaubitz (Closes: #740198)
    
     -- Sylvestre Ledru <email address hidden>  Thu, 27 Feb 2014 11:16:07 +0100
  • arpack (3.1.5-1) unstable; urgency=medium
    
    
      * New upstream release
      * Fix the m86k symbols list (Closes: #726969)
      * Fix the arm64 symbol list
      * Remove mpi-dep-lib.diff (applied upstream)
      * Standards-Version updated to version 3.9.5
    
     -- Sylvestre Ledru <email address hidden>  Sat, 15 Feb 2014 15:16:49 +0100
  • arpack (3.1.4-1) unstable; urgency=low
    
    
      * New upstream release
    
     -- Sylvestre Ledru <email address hidden>  Wed, 13 Nov 2013 09:56:18 +0100
  • arpack (3.1.3-3) unstable; urgency=low
    
    
      * libparpack: Missing dependency on MPI (Closes: #718790)
    
     -- Sylvestre Ledru <email address hidden>  Tue, 06 Aug 2013 15:12:13 +0200
  • arpack (3.1.3-2) unstable; urgency=low
    
    
      * Update the symbols file for:
        mips, mipsel, s390, s390x and powerpcspe
        (Closes: #706940)
      * Reintroduce changes from 3.1.1-2.1
    
     -- Sylvestre Ledru <email address hidden>  Tue, 07 May 2013 13:59:56 +0200
  • arpack (3.1.1-2.1) unstable; urgency=low
    
    
      * Non-maintainer upload.
      * libarpack2: add Breaks: octave3.2  (Closes: #684773)
        This fixes some upgrade paths by removing the obsolete octave3.2 (and its
        triggers) a bit earlier.  dpkg may run trigger processing of a package
        even if its dependencies are not satisfied.  The octave3.2 triggers may
        be run in such a state and will fail, aborting the upgrade, even if
        octave3.2 would be removed later anyway.
        This is a dpkg bug, but probably won't be fixed for wheezy (see #678848).
    
     -- Andreas Beckmann <email address hidden>  Thu, 13 Sep 2012 21:01:02 +0200