[pkg-go] CoyIM outdated version may to lead to its deprecation

Sascha Steinbiss satta at debian.org
Fri May 31 15:14:46 BST 2019

Hi bo0od,

On 5/31/19 2:55 AM, bo0od wrote:
> CoyIM facing blocker bug in debian buster you may need to review this
> ticket:
> https://github.com/coyim/coyim/issues/527
> And already notified here (the new version)
> https://tracker.debian.org/pkg/coyim
> 0.3.11 fixes the issue according to one of the CoyIM developers.

[copying from my GitHub issue response (link above) to keep the team in
the loop]

Thanks for the input. However, it might be difficult to simply update
the version in Debian: we are quite far into the hard freeze for Debian
buster, which means that bug fixes must be backported to the exact
version that is currently in buster (0.3.8).
This is the case particularly in situations when an update to a newer
upstream version would result in the need to update a lot of new
dependencies as well -- I remember that there has been a restructuring
and moving of libraries like otr3 and gotk3adapter, which were all
located somewhere else before. In Debian we need to have all the Go code
needed for building as separate packages in Debian itself, so whenever
the import path changes, we would need to update the build dependency
packages as well to match the import paths in the new coyim versions. So
that update wouldn't just touch coyim, but also
golang-github-twstrike-gotk3adapter-dev and
golang-github-twstrike-otr3-dev at least, which would need to be
renamed, updated and the import paths changed.

I can try and check with the release team if we can make an exception
for a package with a low popcon count and the fact that it is apparently
unusable at the moment. But I guess there are no guarantees with an
update massive that late in the freeze.

Is there a way to find out why this problem occurs in that version and
come up with a patch?

Best regards

More information about the Pkg-go-maintainers mailing list