无法从 17.10 升级到 18.04：计算升级时出现无法解决的问题

Question

我听说在新的 Ubuntu 版本发布后等待几周通常是个好主意，所以我才刚刚开始尝试安装更新。事实证明，当我尝试sudo do-release-upgrade在我的笔记本电脑上安装更新时，我得到了这个：

Calculating the changes

Calculating the changes

Could not determine the upgrade 

An unresolvable problem occurred while calculating the upgrade. 

This can be caused by: 
* Upgrading to a pre-release version of Ubuntu 
* Running the current pre-release version of Ubuntu 
* Unofficial software packages not provided by Ubuntu 

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. 


Restoring original system state

Aborting
Reading package lists... Done    
Building dependency tree          
Reading state information... Done

我觉得这很奇怪，所以我做了一些搜索，人们建议我跑去grep Broken /var/log/dist-upgrade/apt.log找出问题所在。但是在运行它时，我发现我的问题似乎很重要。这是我的输出：

Broken curl:amd64 Depends on libcurl4:amd64 < none | 7.58.0-2ubuntu3.1 @un uH > (= 7.58.0-2ubuntu3.1)
Broken libopencv-imgcodecs3.1:amd64 Depends on gdal-abi-2-2-1:amd64 < none @un H >
Broken librubberband2:amd64 Conflicts on librubberband2v5:amd64 < 1.8.1-6ubuntu2 @ii mK Ib >
Broken libsmbios-c2:amd64 Conflicts on libsmbios2v5:amd64 < 2.3.1-0ubuntu2 @ii mK Ib >
Broken libopencv-videoio3.1:amd64 Depends on libopencv-imgcodecs3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libopencv-highgui3.1:amd64 Depends on libopencv-videoio3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libubuntu-app-launch4:amd64 Depends on libcurl4:amd64 < none | 7.58.0-2ubuntu3.1 @un uH > (>= 7.16.2)
Broken gnupg1:amd64 Conflicts on gnupg1-curl:amd64 < 1.4.22-1ubuntu1 @ii mK >
Broken gir1.2-spiceclientglib-2.0:amd64 Breaks on gir1.2-spice-client-glib-2.0:amd64 < 0.33-3.3 @ii mK > (< 0.34)
Broken gir1.2-totemplparser-1.0:amd64 Conflicts on gir1.2-totem-plparser-1.0:amd64 < 3.10.8-3ubuntu1 @ii mK >
Broken libdbusmenu-qt5-2:amd64 Breaks on libdbusmenu-qt5:amd64 < 0.9.3+16.04.20160218-0ubuntu1 @ii mK >
Broken gir1.2-ggit-1.0:amd64 Conflicts on gir1.2-git2-glib-1.0:amd64 < 0.24.4-1 @ii mK >
Broken libglib2.0-dev:amd64 Depends on libpcre3-dev:amd64 < none | 2:8.39-9 @un uH > (>= 1:8.31)
Broken libcurl4-openssl-dev:amd64 Depends on libcurl4:amd64 < none | 7.58.0-2ubuntu3.1 @un uH > (= 7.58.0-2ubuntu3.1)
Broken gir1.2-spiceclientgtk-3.0:amd64 Breaks on gir1.2-spice-client-gtk-3.0:amd64 < 0.33-3.3 @ii mK Ib > (< 0.34)
Broken libharfbuzz-dev:amd64 Depends on libglib2.0-dev:amd64 < none | 2.56.1-2ubuntu1 @un uH > (>= 2.19.1)
Broken libopencv-objdetect3.1:amd64 Depends on libopencv-highgui3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libopencv-videostab3.1:amd64 Depends on libopencv-videoio3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR >
Broken libopencv-stitching3.1:amd64 Depends on libopencv-objdetect3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libopencv-superres3.1:amd64 Depends on libopencv-videoio3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libopenimageio1.6:amd64 Depends on libopencv-videoio3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR >
Broken libopencv-contrib3.1:amd64 Depends on libopencv-highgui3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken libopencv-features2d3.1:amd64 Depends on libopencv-highgui3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken url-dispatcher:amd64 Depends on libubuntu-app-launch4:amd64 < 0.12+17.04.20170404.2-0ubuntu4 | 0.12+17.04.20170404.2-0ubuntu6 @ii ugR > (>= 0.10)
Broken libicu-le-hb-dev:amd64 Depends on libharfbuzz-dev:amd64 < none | 1.7.2-1ubuntu1 @un uH >
Broken url-dispatcher-tools:amd64 Depends on url-dispatcher:amd64 < 0.1+17.04.20170328-0ubuntu3 | 0.1+17.04.20170328-0ubuntu4 @ii ugR > (= 0.1+17.04.20170328-0ubuntu4)
Broken libopencv-calib3d3.1:amd64 Depends on libopencv-features2d3.1:amd64 < 3.1.0+dfsg1-1~exp1ubuntu3 @ii mR > (= 3.1.0+dfsg1-1~exp1ubuntu3)
Broken unity-greeter-session-broadcast:amd64 Depends on url-dispatcher-tools:amd64 < 0.1+17.04.20170328-0ubuntu3 | 0.1+17.04.20170328-0ubuntu4 @ii ugR >
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >
Broken icu-devtools:amd64 Breaks on libicu-dev:amd64 < 57.1-6ubuntu0.3 | 60.2-3ubuntu3 @ii umH > (< 60.2-3ubuntu3)
Broken libicu-dev:amd64 Depends on libicu-le-hb-dev:amd64 < none | 1.0.3+git161113-4 @un uH >

有谁知道这里发生了什么以及我如何解决它？在这一点上重新安装不是一个选项 - 我喜欢我的配置！

我已经检查过，没有一个类似的问题似乎是我的问题。

附加系统信息：

• 我目前在 17.10（巧妙的土豚）
• 我要升级到 18.04（仿生海狸）
• uname -a： Linux <REDACTED> 4.13.0-43-generic #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• 我正在使用 Unity 桌面，因为我非常不喜欢新的 gnome 桌面
• 我有英特尔 i7-7500U、英特尔高清显卡 620 r02、16GB 内存和独立显卡。
• 可应要求提供其他信息。

Answer 1

看起来我已经设法解决了我自己的问题。对于那些自己有这个问题的人，这里有一些我用来解决我的问题的技巧。

读取 的输出grep Broken /var/log/dist-upgrade/apt.log只是第一步。接下来，我用

grep -C5 broken_package_name /var/log/dist-upgrade/apt.log

显示一些围绕损坏的包名称的附加输出，以获取有关出错的更多信息。结合apt-cache'srdepends选项，您可以开始找出可能导致问题的原因：

apt-cache rdepends --installed broken_package_name

另外值得注意的是底部的附加输出/var/log/dist-upgrade/apt.log。对于每个Broken包，它们中的一些被显示为Fixed依赖问题解决程序。这些通常可以被忽略 - 而其他更重要的则首先关注。

sudo do-release-upgrade每次更改一件事时不要忘记继续运行，以便获得有关更改内容的最新读数。

一旦确定了问题包，它们可以被更新（如果它们来自第三方），或者被暂时删除（如果它们来自 3rd 方 PPA）并稍后重新安装，因为所有 3rd 方 PPA 都被禁用作为升级过程的一部分 - 因此，如果 PPA 中存在用于您要升级到的 Ubuntu 版本的所述软件包的更新版本（例如，在我的情况下它是仿生的），则会无意中导致问题，因为它看不到要安装的它。请注意，除非您使用apt purge.