1. 15 Aug, 2019 1 commit
  2. 04 Aug, 2019 3 commits
  3. 03 Aug, 2019 2 commits
  4. 31 Jul, 2019 6 commits
  5. 02 Apr, 2019 2 commits
    • Drew Parsons's avatar
      upload 3.11.0+dfsg1-1exp1 to experimental · 6c80c165
      Drew Parsons authored
    • Drew Parsons's avatar
      invoke dh_python3 with --shebang=/usr/bin/python3 · ec3363e6
      Drew Parsons authored
      The aim is to handle petsc without depending on python2.
      petsc python scripts (e.g. PetscBinaryIOTrajectory.py and other
      scripts in lib/petsc/bin/) provide a shebang
        #!/usr/bin/env python
      which is rewritten by dh_python3 into /usr/bin/python2, not
      /usr/bin/python3 (this is intentional, see Bug#926187. Use of python3
      must be explicit)
      So force dh_python3 to rewrite the shebangs as /usr/bin/python3
      (any actual python2ism remaining in the scripts must be treated as a
  6. 01 Apr, 2019 14 commits
  7. 10 Jan, 2019 2 commits
  8. 09 Jan, 2019 3 commits
  9. 24 Dec, 2018 3 commits
    • Drew Parsons's avatar
      upload 3.10.3+dfsg1-3 to unstable · f76fa2e2
      Drew Parsons authored
    • Drew Parsons's avatar
      Standards-Version: 4.3.0 · 1f56f566
      Drew Parsons authored
    • Drew Parsons's avatar
      update petsckspmod_split.patch to handle header files separately · 186a97cb
      Drew Parsons authored
      the split files petscpcmod.F and petsckspmod.F still need to contain
      the included header files, even though they are used in the
      petscpcdefdummy module. Otherwise compilation of the modules fails
      ("unclassifiable statement", i.e. definitions of KSP, VEC, MAT etc are
      not known).  The definitions cannot be taken from the existing
      petscpcdefdummy module, which is now split into a separate .F file.
      The included headers must be contained within a module.  But petscpc
      and petscksp must not use that module, otherwise there will be an
      ambiguous definition of tksp (from the new dummy header module and from the
      original petscpcdefdummy), which causes SLEPc builds, for instance, to
      break. The new dummy module including the headers must simply appear
      in the .F file to provide the definitions.
  10. 23 Dec, 2018 2 commits
  11. 22 Dec, 2018 2 commits