Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
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 report a problem, and mine does. > > It's not about gbp.conf. src:python-cartopy has this in d/control: > Vcs-Git: https://salsa.debian.org/debian-gis-team/python-cartopy.git -b > experimental > note the "-b experimental". We update both when switching away from the master branch: https://salsa.debian.org/debian-gis-team/python-cartopy/-/commit/e8131f281c67a1e9b348051e06c654a91d4f3bdc And those commits get reverted when switching back. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
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, 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 report a problem, and mine does. It's not about gbp.conf. src:python-cartopy has this in d/control: Vcs-Git: https://salsa.debian.org/debian-gis-team/python-cartopy.git -b experimental note the "-b experimental". Also read file:///usr/share/doc/debian-policy/policy.html/ch-controlfields.html#version-control-system-vcs-fields -- 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#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
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 interested >in) go about knowing that. > >> The Package overview shows Git - 4.4.5-2 (with the version in red as >> if there's a problem with it) as if that is the latest in Git. > >The problem is in your packages. >The branch vcswatch is using the one pointed by HEAD. If that doesn't >contain the version it is expecting, that's marked as an error. > >In your case, you should be specifying the branch in Vcs-Git, using the >-b flag, as documented in Policy. > >> I can see other packages that have experimental packaging in the >> debian/master branch not showing this as a problem, > >Yes, that's correct, because HEAD points to the branch containing the >most up-to-date packaging. > >> 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, 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 report a problem, and mine does. Sorry for the noise, and thanks for the education! best /Andreas gus...@debian.org
Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
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 5.0.0-1~exp1 in experimental, and the tag debian/5.0.0-1_exp1 on the debian/experimental branch. The Package overview shows Git - 4.4.5-2 (with the version in red as if there's a problem with it) as if that is the latest in Git. My package overview where the problem is visible at https://qa.debian.org/developer.php?login=gusnan%40debian.org I can see other packages that have experimental packaging in the debian/master branch not showing this as a problem, or even those where the experimental branch is called simply experimental (and not debian/experimental) also not showing the version as problematic. DEP-14 mentions debian/experimental and debian/unstable, but it shouldn't be an error to use debian/experimental as branch name even if using debian/master, right? Please inform me if it is simply user error. -- Andreas Rönnquist gus...@debian.org
