Debian Support

I went and had a look at all fields in pulp_deb that have max_length=255 and I don't think any of them are likely to have caused this sync failure. (Given what I know about the repo being synced).

Without the ability to test the upstream repo, I do not know how to proceed...

Ok, I was given the relevant release file, and the problem is that the repo has uncharacteristically many components, thus exceeding the max length of the field in pulp_deb. The following is from the upstream release file:

Components: main mysql postgresql ldap cloud-s3 cloud-glacier cloud-azure cloud-google cloud-oracle shstore delta ndmp vsphere demo demo-support bweb netapp-hfc html-manuals kvm snapshot dedup aligned single-item-restore sybase kubernetes docker rhv db2 xenserver hdfs m365

Several possibilities for improving components fields:

• Increase the max_length?
• Chane to TextField(null=True)?
• Change to ArrayField(CharField(max_length=255), null=True)?

Also update architectures and distributions fields?

I decided against the array option, since I want to do as little as possible processing of upstream metadata, before storing it in the DB. In other words, I want to keep upstream fields containing space separated string lists as a single string (containing space separated list values) in the DB.