On 1/23/21 2:58 AM, Vasyl Gello wrote: >> See policy 7.6 at >> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces > > I think the Policy should be clarified stating that B+R must point to a > version that has been accepted into Debian archive.
It doesn't have to. > That was unclear for me to the dare because of > >> There are >> B+R: kodi-addons-dev (<< 2:19.0~beta2+dfsg1-6~) >> but that is the wrong version. > > kodi-addons-dev (<< 2:19.0~beta2+dfsg1-6~) was uploaded to NEW queue but > rejected by FTP Master. And then 2:19.0~rc1+git20210119.8c761c4+dfsg1-1 was uploaded without the split and -2 was sent to NEW with the split, but the B+R were not adjusted to cover the new unsplit version uploaded inbetween. (If 2:19.0~rc1+git20210119.8c761c4+dfsg1-1 had contained the package split and was sent to NEW, the B+R on 2:19.0~beta2+dfsg1-6~ would have worked fine, despite of being hard to read in a few years: why is there a strange version that never existed?) > Mattia suggests just changing that paragraph to: > > kodi-addons-dev (<< 2:19.0~rc1+git20210119.8c761c4+dfsg1-2~) Perfect, the '~' suffix is the backports-safe solution. (Even if noone will backport the buggy -2.) Andreas
