Merge ~litios/ubuntu-cve-tracker:sis-changes-forget-binaries into ubuntu-cve-tracker:master
Status: | Merged |
---|---|
Merged at revision: | 7408a55d2de9501b5e57de61d540c409c0fbdc7d |
Proposed branch: | ~litios/ubuntu-cve-tracker:sis-changes-forget-binaries |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
12 lines (+1/-0) 1 file modified
scripts/sis-changes (+1/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alex Murray | Approve | ||
Review via email: mp+443737@code.launchpad.net |
Description of the change
During the gathering of package information for the USN script generation, when specifying several PPAs, there is a check to always use the most up-to-date version (line 238). The pkg struct is reset to the default state, so everything is regenerated according to this newer version.
Nevertheless, the binaries are not reset. The information is added with the `setdefault` function, so if it already exists, it is not overridden (line 419).
This situation happens when publishing an ESM update when the same package is on the security proposed PPA. The source information in the USN is added from the ESM PPA but the binary information is added from the security proposed PPA. Example:
usn.py --db "$DB" $USN --release bionic --package jhead --source-version 1:3.00-
usn.py --db "$DB" $USN --release focal --package jhead --source-version 1:3.04-
usn.py --db "$DB" $USN --release jammy --package jhead --source-version 1:3.06.
[...]
usn.py --db "$DB" $USN --release bionic --package jhead --binary-version 1:3.00-8~ubuntu0.2 --pocket security
usn.py --db "$DB" $USN --release focal --package jhead --binary-version 1:3.04-1ubuntu0.2 --pocket security
usn.py --db "$DB" $USN --release jammy --package jhead --binary-version 1:3.06.
To follow the same logic as what's already done in line 238, this PR also cleans the binaries when it detects there is a newer version.
Thanks @iosifache for detecting the issue!
LGTM!