On Thu, Dec 1, 2016 at 7:28 AM, Dave Page <dave.p...@codethink.co.uk> wrote:

> Package: golang-go.tools
> Version: 1:0.0~git20161028.0.b814a3b+ds-3
> Severity: grave
> File: golang-go
> Justification: renders package unusable
>
> Dear Maintainer,
>
>
> I am in the middle of a dist-upgrade from jessie to lennie, and the
>

Did you mean from lenny to jessie?

As per
https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#system-status,
Debian only supports upgrades from the previous stable version to the
current stable version.

I think you need to upgrade lenny → squeeze → wheezy → jessie.


> process has broken on golang-go:
>
> Preparing to unpack .../golang-go_2%3a1.7~1_amd64.deb ...
> dpkg-maintscript-helper: error: directory '/usr/lib/go' contains files
> not owned by package golang-go:amd64, cannot switch to symlink
> dpkg: error processing archive
> /var/cache/apt/archives/golang-go_2%3a1.7~1_amd64.deb (--unpack):
>  subprocess new pre-installation script returned error exit status 1
> Errors were encountered while processing:
>  /var/cache/apt/archives/golang-go_2%3a1.7~1_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> # dpkg -S /usr/lib/go /usr/lib/go/doc
> golang-go, golang-doc: /usr/lib/go
> golang-doc: /usr/lib/go/doc
>
> So it looks like having golang-doc installed alongside, breaks the
> upgrade of golang-go.
>
> Purging golang golang-go golang-doc allowed me to complete the
> dist-upgrade.
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages golang-go.tools depends on:
> ii  golang-golang-x-tools  1:0.0~git20161028.0.b814a3b+ds-3
>
> golang-go.tools recommends no packages.
>
> golang-go.tools suggests no packages.
>
> -- no debconf information
>



-- 
Best regards,
Michael

Reply via email to