1. 14 Mar, 2019 1 commit
  2. 13 Mar, 2019 2 commits
  3. 11 Mar, 2019 5 commits
  4. 10 Mar, 2019 4 commits
  5. 09 Mar, 2019 1 commit
  6. 08 Mar, 2019 1 commit
  7. 02 Mar, 2019 1 commit
  8. 16 Feb, 2019 3 commits
  9. 30 Jan, 2019 2 commits
  10. 27 Jan, 2019 3 commits
  11. 25 Jan, 2019 2 commits
  12. 24 Jan, 2019 2 commits
  13. 23 Jan, 2019 1 commit
  14. 13 Jan, 2019 4 commits
  15. 11 Jan, 2019 2 commits
  16. 30 Dec, 2018 1 commit
  17. 25 Dec, 2018 1 commit
  18. 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
  19. 03 Dec, 2018 3 commits