On Sun, Mar 10, 2019 at 5:00 AM Shengjing Zhu <[email protected]> wrote: > > On Sun, Mar 10, 2019 at 1:15 PM Tong Sun <[email protected]> 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
Thanks Shengjing. Anywhere I can read about how to update golang packages? All the docs that I read were on *creating* packages with dh-make-golang, and haven't got to updating them yet. please help. thanks
