1. 24 Mar, 2019 1 commit
    • Gabriel Francisco's avatar
      Remove few PendingDeprecationWarning from tests · 99cd46c6
      Gabriel Francisco authored
      when building in Buster.
      
      ============================= test session starts ==============================
      platform linux2 -- Python 2.7.16rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- /usr/bin/python2
      cachedir: .pytest_cache
      rootdir: /srv/dak, inifile:
      collecting ... collected 166 items
      
      [...]
      
      =============================== warnings summary ===============================
      tests/test_parse_changes.py::ParseChangesTestCase::test_3
        /srv/dak/tests/test_parse_changes.py:95: PendingDeprecationWarning: Please use assertFalse instead.
          self.failIf(changes.get('you'))
        /srv/dak/tests/test_parse_changes.py:95: PendingDeprecationWarning: Please use assertFalse instead.
          self.failIf(changes.get('you'))
        /srv/dak/tests/test_parse_changes.py:95: PendingDeprecationWarning: Please use assertFalse instead.
          self.failIf(changes.get('you'))
      
      tests/test_parse_changes.py::ParseDscTestCase::test_9
        /srv/dak/tests/test_parse_changes.py:66: PendingDeprecationWarning: Please use assertFalse instead.
          self.failIf(changes.get('this'))
      
      -- Docs: https://docs.pytest.org/en/latest/warnings.html
      =================== 166 passed, 4 warnings in 19.14 seconds ====================
      99cd46c6
  2. 14 Mar, 2019 1 commit
  3. 13 Mar, 2019 2 commits
  4. 11 Mar, 2019 5 commits
  5. 10 Mar, 2019 4 commits
  6. 09 Mar, 2019 1 commit
  7. 08 Mar, 2019 1 commit
  8. 02 Mar, 2019 1 commit
  9. 16 Feb, 2019 3 commits
  10. 30 Jan, 2019 2 commits
  11. 27 Jan, 2019 3 commits
  12. 25 Jan, 2019 2 commits
  13. 24 Jan, 2019 2 commits
  14. 23 Jan, 2019 1 commit
  15. 13 Jan, 2019 4 commits
  16. 11 Jan, 2019 2 commits
  17. 30 Dec, 2018 1 commit
  18. 25 Dec, 2018 1 commit
  19. 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
  20. 03 Dec, 2018 2 commits