[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Wed, 17 Mar 2021 16:47:02 +0100
with message-id <YFIkdu/yMVRjx3Tr@mapreri.org>
and subject line Re: Bug#985404: qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
has caused the Debian Bug report #985404,
regarding qa.debian.org: Packages overview VCS field doesn't consider a debian/experimental branch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
985404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985404
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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
gusnan@debian.org

--- End Message ---
--- Begin Message --- 
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?

> 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?

DEP-14 or any naming standard does not matter here.  vcswatch doesn't
have any specific implementation regarding this.

-- 
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  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: