Prior to this commit, the uid was the plain package's name.
Internal lister's mechanism would result in preventing to see new versions.
So it's important this uid is unique per version.
Details
- Reviewers
douardda vlorentz - Group Reviewers
Reviewers - Commits
- rDLS767c4c6dc775: cran.lister: Version uid so we can list new package versions
tox
Diff Detail
- Repository
- rDLS Listers
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/524/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/525/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/527/ for more details.
Doesn't this require a migration of existing data?
Yes and no.
Yes, but that's something not seen in the lister's code...
I do not know why we are inconsistent regarding model migration in that repository.
And no because, in any case, i will truncate the existing rows.
I will start the cran listing from scratch when this will be deployed ;)
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/529/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DLS/job/tox/530/ for more details.