Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
On Mon, Sep 28, 2020 at 10:12 AM Paul Wise wrote: > > Updating the bug metadata to reflect that suggestion. Thanks, pabs! Hope this fix can be deployed soon. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
Control: tags -1 - wontfix Control: retitle -1 DDPO: hide Extra-Source-Only packages by default, add option to show them On Sun, Sep 27, 2020 at 6:00 AM Paul Wise wrote: > The version in experimental is ESO, so I think it is fine to hide it by > default, perhaps with a parameter to show ESO packages? Updating the bug metadata to reflect that suggestion. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
On Sun, 2020-09-27 at 14:54 +0900, Roger Shimizu wrote: > I think above perfectly explains why the original issue of the ticket > occurs, and it's by design. > So I add the "wontfix" tag to this ticket. The version in experimental is ESO, so I think it is fine to hide it by default, perhaps with a parameter to show ESO packages? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
control: tags -1 +wontfix On Sun, Sep 27, 2020 at 2:38 PM Paul Wise wrote: > > 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. I think above perfectly explains why the original issue of the ticket occurs, and it's by design. So I add the "wontfix" tag to this ticket. Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
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 signature.asc Description: This is a digitally signed message part
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
On Sun, Sep 27, 2020 at 9:08 AM Paul Wise wrote: > > On Sat, Sep 26, 2020 at 1:57 PM Roger Shimizu wrote: > > > So what's ESO? > > A package which has this in the Packages file: > > Extra-Source-Only: yes > > dak uses this to indicate that the source package is only kept around > for license compliance purposes because another package still has a > Built-Using header with the ESO version of the package. Once the other > package has been rebuilt against the newer version, then the ESO > version can be removed. > > https://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using Thanks for the explanation! 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. > > How can I check the ESO status for a specific package? > > $ apt-cache showsrc golang-github-jinzhu-inflection | grep -E > '^(Version|Extra-Source-Only|)(:|$)' Great example. Thanks again! I checked one package I mentioned previously: $ apt-cache showsrc golang-github-google-go-github | grep -E '^(Version|Extra-Source-Only|)(:|$)' Version: 32.1.0-1 Extra-Source-Only: yes Version: 32.1.0-2 But 28.1.1-1 still appears in my DDPO [2] in experimental column. So I think there might be two possible bugs in DDPO: - golang-github-google-go-github version 28.1.1-1 was never uploaded to experimental, but unstable. - golang-github-google-go-github 28.1.1-1 is not in ESO anymore, but still appears in DDPO. [2] https://qa.debian.org/developer.php?login=rosh Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
On Sat, Sep 26, 2020 at 1:57 PM Roger Shimizu wrote: > So what's ESO? A package which has this in the Packages file: Extra-Source-Only: yes dak uses this to indicate that the source package is only kept around for license compliance purposes because another package still has a Built-Using header with the ESO version of the package. Once the other package has been rebuilt against the newer version, then the ESO version can be removed. https://www.debian.org/doc/debian-policy/ch-relationships.html#s-built-using > How can I check the ESO status for a specific package? $ apt-cache showsrc golang-github-jinzhu-inflection | grep -E '^(Version|Extra-Source-Only|)(:|$)' Version: 0.0~git20170102.0.1c35d90-2 Extra-Source-Only: yes Version: 1.0.0-1 Version: 1.0.0-1 Extra-Source-Only: yes -- bye, pabs https://wiki.debian.org/PaulWise
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
Dear Mattia, I also met this issue on a few packages I uploaded [2]: - golang-golang-x-xerrors - golang-github-google-go-github - golang-go.crypto [2] https://qa.debian.org/developer.php?login=rosh >> I have noticed that the package 'golang-github-jinzhu-inflection' is >> still listed in the experimental column of my DDPO page [1] but it has >> in the meantime been superseded by a newer version in testing. rmadison >> also shows this package to no longer be in experimental: > > As a data point, that package is listed there in the version of > 0.0~git20170102.0.1c35d90-2, which indeed is listed in the experimental > Sources index as ESO. So what's ESO? How can I check the ESO status for a specific package? > So it might just be that whatever in DDPO is in charge of cleaning up > disappearing sources doesn't do the job if the source is left there as > ESO. So what do you suggest to solve this issue? Thanks! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
On Fri, Jul 19, 2019 at 10:58:15AM +0200, Sascha Steinbiss wrote: > I have noticed that the package 'golang-github-jinzhu-inflection' is > still listed in the experimental column of my DDPO page [1] but it has > in the meantime been superseded by a newer version in testing. rmadison > also shows this package to no longer be in experimental: As a data point, that package is listed there in the version of 0.0~git20170102.0.1c35d90-2, which indeed is listed in the experimental Sources index as ESO. So it might just be that whatever in DDPO is in charge of cleaning up disappearing sources doesn't do the job if the source is left there as ESO. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#932431: DDPO: package removed from experimental but still shown in DDPO column
Package: qa.debian.org Severity: normal Dear DDPO team, I have noticed that the package 'golang-github-jinzhu-inflection' is still listed in the experimental column of my DDPO page [1] but it has in the meantime been superseded by a newer version in testing. rmadison also shows this package to no longer be in experimental: $ rmadison golang-github-jinzhu-inflection golang-github-jinzhu-inflection | 0.0~git20170102.0.1c35d90-1~bpo9+1 | stretch-backports | source golang-github-jinzhu-inflection | 0.0~git20170102.0.1c35d90-2| stable| source golang-github-jinzhu-inflection | 1.0.0-1| testing | source golang-github-jinzhu-inflection | 1.0.0-1| unstable | source I would have expected the package to be removed from the DDPO view. At least I have been observing this behaviour in the past. Not sure if it's a bug or something else, maybe a side effect from the freeze? Cheers Sascha [1] https://qa.debian.org/developer.php?login=satta
