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

Bug#906663: marked as done (vcswatch: should not flag an UNRELEASED changelog entry as "ready for upload")

Your message dated Thu, 13 Sep 2018 09:50:03 +0200
with message-id <20180913075003.GA24170@home.ouaza.com>
and subject line Re: Bug#906663: vcswatch: should not flag an UNRELEASED changelog entry as "ready for upload"
has caused the Debian Bug report #906663,
regarding vcswatch: should not flag an UNRELEASED changelog entry as "ready for upload"
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.)


-- 
906663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906663
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: wishlist

Hi,

I have made it a custom for many years to immediately create a new
changelog entry right after uploading and tagging a new version of any
package, for example:

aide (0.16-4.0) UNRELEASED; urgency=medium

  * NOT YET RELEASED

 -- Marc Haber <mh+debian-packages@zugschlus.de>  Fri, 17 Aug 2018 19:51:16 +0200

Please note the ".0" suffix to the version number that was just uploaded
to avoid "using" a new version number. I only use the new version number
right before the upload so that I can build test versions of the package
without "burning" a new number.

Please also note the UNRELEASED distribution and the NOT YET RELEASED
changelog entry which will stay the top changelog entry until the
package is eventually uploaded.

vcswatch makes this "VCS has unreleased changes", which is correct. The
tracker, however, makes this "A new version is available int the VCS"
which is not the case.

I don't have the slightest idea about how to make this any way less
ambiguous, but I would prefer that the tracker would stop advertising a
new version as being "available" when this is clearly marked as
unreleased work.

I could work in a branch, but that would mean additional rules for team
maintained packages which I'd rather avoid. I mean, there are valid
reasons, for example an upload held back due to an ongoing library
transition, for not immediately uploading any new commit to a master
branch in git.

For me, the hint given in the tracker is kind of useless if it's always
there. How about only showing it when the new commits do have a certain
age such as a month?

Greetings
Marc

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.1-zgws1 (SMP w/6 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Hi,

On Sun, 19 Aug 2018, Christoph Berg wrote:
> Control: reassign -1 tracker.debian.org
> 
> Re: Marc Haber 2018-08-19 <153468174721.19286.15758469883614485339.reportbug@fan.zugschlus.de>
> > vcswatch makes this "VCS has unreleased changes", which is correct. The
> > tracker, however, makes this "A new version is available int the VCS"
> > which is not the case.
> 
> That sounds like this should be fixed on the tracker side.

I improved the descriptions a few weeks ago but the webhook was down and
it failed to close this bug.

It was fixed in commit ef47c39ee4eddd7f5d6de934cedcd8e0ee17f7ff.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

--- End Message ---
Reply to: