On Sun, 2020-09-27 at 14:27 +0900, Roger Shimizu wrote: > I think this can explain why an old version of package is still in > archive, but still cannot explain why it appears in *experimental* > column in DDPO page. This simply because DDPO just reflects what is in the archive, if you grep the Packages/Sources files from the archive you can confirm this. > I checked one package I mentioned previously: > ==== > $ apt-cache showsrc golang-github-google-go-github | grep -E > '^(Version|Extra-Source-Only|)(:|$)' I see more versions than you for some reason: $ apt-cache showsrc golang-github-google-go-github | grep -E '^(Version|Extra-Source-Only|)(:|$)' Version: 32.1.0-1 Version: 32.1.0-1 Extra-Source-Only: yes Version: 32.1.0-2 Version: 28.1.1-1 Extra-Source-Only: yes > But 28.1.1-1 still appears in my DDPO [2] in experimental column. It also appears in the archive too, in experimental vault:amd64 has Built-Using with that version of golang-github-google-go-github and src:golang-github-google-go-github is present too with ESO: yes. > - golang-github-google-go-github version 28.1.1-1 was never uploaded > to experimental, but unstable. It seems if a package from experimental has Built-Using on a package in unstable, then dak pulls the unstable source package into experimental and adds ESO: yes. > - golang-github-google-go-github 28.1.1-1 is not in ESO anymore, but > still appears in DDPO. It definitely is, in experimental. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part