Source: golang-1.7
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Golang 1.7 has recently been made available in jessie backports. However, it is
not installable in armel (and possibly other
architectures) because the golang-1.7-go package is missing for it. In turn
this is due to a failure in building golang-1.7-go
(see
https://buildd.debian.org/status/package.php?p=golang-1.7&suite=jessie-backports#problem-1)
The issue is that, as a consequence of the above, if one had previously
installed golang 1.6 from the backports, then spurious
information about the availability of package upgrades is constantly showns.
For many days now, the system has been indicating that 4 packages are
upgradable (the 4 golang packages), when in fact, no one
can be successfully updated. This makes the information that the system
automatically provides on updates at best useless and
at worst confusing and misguiding unnecessary actions.
I would suggest removing golang 1.7 from jessie-backports for those
architectures where it cannot be installed anyway because
some part of it cannot be built (at least until it can be built).
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 4.8.0-0.bpo.2-marvell
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
