1. 02 Mar, 2019 1 commit
  2. 16 Feb, 2019 3 commits
  3. 30 Jan, 2019 2 commits
  4. 27 Jan, 2019 3 commits
  5. 25 Jan, 2019 2 commits
  6. 24 Jan, 2019 2 commits
  7. 23 Jan, 2019 1 commit
  8. 13 Jan, 2019 4 commits
  9. 11 Jan, 2019 2 commits
  10. 30 Dec, 2018 1 commit
  11. 25 Dec, 2018 1 commit
  12. 12 Dec, 2018 1 commit
    • Guillem Jover's avatar
      Stop requiring a Binary field in .changes files in the database · d48ebfac
      Guillem Jover authored
      The changes table requires a not NULL binaries column. But we should not
      be requiring a Binary field for source-only uploads. There have been
      other changes to accommodate that, but the schema still requires the
      values, and uploading such .changes files returns this misleading
      rejection message:
      
        source_version_arch.changes is already known.
      
      from daklib/archive.py:_install_changes() due to an exception when
      inserting the DBChange() into the database.
      d48ebfac
  13. 03 Dec, 2018 3 commits
  14. 10 Nov, 2018 7 commits
  15. 05 Nov, 2018 1 commit
  16. 23 Oct, 2018 6 commits