kpcyrd
Save Debian release in DB
In a2f3ca47e952d99ec3a6c507c9b2e4163da76613 support for multiple Debian releases was added but this is not saved in the DB. Please add support for that. Note that a package can be part of multiple releases at the same time. I think adding it to pkgbases should be enough, not sure if it also should be in packages.
also please take into consideration that there are many Debian releases, like bookworm, bookworm-security, bookworm-updates, bookworm-proposed-updates, trixie, trixie-security and so on.
(and then Debian also has archive areas like main and non-free-firmware (and contrib and non-free))
Why do we care about the release in the database? Isn't all that matters the version? (At least in my WIP code for britney2 I just look up the right version, I wouldn't look for the suite.)
On Sat, May 24, 2025 at 01:42:52PM -0700, Paul Gevers wrote:
Why do we care about the release in the database? Isn't all that matters the version? (At least in my WIP code for britney2 I just look up the right version, I wouldn't look for the suite.)
actually we have had packages with the same version but different content in different suites. and that bug in dak is not yet fixed:
see #1072205 "dak: prevent re-using package versions"
-- cheers, Holger
⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄
Only change is constant.