• 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
Name
Last commit
Last update
alembic Loading commit data...
config Loading commit data...
dak Loading commit data...
daklib Loading commit data...
dakweb Loading commit data...
debian Loading commit data...
docs Loading commit data...
integration-tests Loading commit data...
scripts Loading commit data...
setup Loading commit data...
templates Loading commit data...
tests Loading commit data...
tools Loading commit data...
.coveragerc Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
.nobackup Loading commit data...
COPYING Loading commit data...
README.coding Loading commit data...
README.md Loading commit data...
alembic.ini Loading commit data...
setup.cfg Loading commit data...