[pkg-go] Bug#924728: ITP: Upgrading golang-github-ghodss-yaml
Tong Sun
suntong001 at users.sourceforge.net
Sat Mar 16 14:22:47 GMT 2019
package: wnpp
Severity: wishlist
Owner: Debian Go packaging team <pkg-go-maintainers at lists.alioth.debian.org>
Upgrading golang-github-ghodss-yaml to the new upstream version (and
the new packaging standards).
https://salsa.debian.org/go-team/packages/golang-github-ghodss-yaml
Check the following for the discussion details.
---------- Forwarded message ---------
From: Shengjing Zhu <zhsj at debian.org>
Date: Sun, Mar 10, 2019 at 5:00 AM
Subject: Re: Updating golang-github-ghodss-yaml
On Sun, Mar 10, 2019 at 1:15 PM Tong Sun wrote:
>
> Hi,
>
> I'm thinking to update golang-github-ghodss-yaml as it is about two years old now and some useful functionalities have been added in. So, the questions are:
>
> - would there be any objections?
> - for two years the upstream author didn't publish any new version. Would the procedure be trying to nudge him for a new version first before going to the latest git version? How long should I normally wait, if upstream author is not responsive, before going to the latest git version?
>
I think you can update when it's needed. For example, your package
needs new version, or bugs in old version.
And just pay attention to coordinate with the reverse dependencies,
you can use ratt[1] to check if the new version causes regressions.
[1] https://packages.debian.org/unstable/ratt
--
Shengjing Zhu
More information about the Pkg-go-maintainers
mailing list