Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch

2021-03-17 Thread Sebastiaan Couwenberg
On 3/17/21 5:07 PM, Mattia Rizzolo wrote: > On Wed, Mar 17, 2021 at 05:05:15PM +0100, Andreas Ronnquist wrote: >> Ah, thanks. I was looking at python-cartopy but didn't notice that >> there gbp.conf is also updated with proper branch info for each branch. >> I guess that is why that package don't

Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch

2021-03-17 Thread Mattia Rizzolo
On Wed, Mar 17, 2021 at 05:05:15PM +0100, Andreas Ronnquist wrote: > >> or even those where > >> the experimental branch is called simply experimental (and not > >> debian/experimental) also not showing the version as problematic. > > > >This sounds weird, do you have an example? > > Ah,

Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch

2021-03-17 Thread Andreas Ronnquist
On Wed, 17 Mar 2021 16:47:02 +0100 Mattia Rizzolo wrote: >On Wed, Mar 17, 2021 at 03:59:43PM +0100, Andreas Rönnquist wrote: >> The VCS field on developer Packages overview doesn't seem to >> consider a debian/experimental branch. > >How would DDPO (actually, vcswatch is the component you are

Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch

2021-03-17 Thread Andreas Rönnquist
Package: qa.debian.org Severity: wishlist The VCS field on developer Packages overview doesn't seem to consider a debian/experimental branch. In my example, the package scite, where unstable has version 4.4.5-2, and salsa has the tag debian/4.4.5-2 on the debian/master branch, and it has