Project

Profile

Help

Issue #9191

Migrated advisories with dates-as-timestamps end up with start-of-epoch dates

Added by ggainey about 2 months ago. Updated about 2 months ago.

Status:
NEW
Priority:
Low
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Advisory-migration only allows datetime formats. Unfortunately, createrepo allows date-fields to be timestamps, which happens "in the wild" with some SUSE repositories.

Teach advisory-migration to try decoding-as-timestamp if decoding-as-datetime fails.

Please register to edit this issue

Also available in: Atom PDF