Bug 379091 - wrong libastro1 package to be installed borks update
Summary: wrong libastro1 package to be installed borks update
Status: RESOLVED NOT A BUG
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-22 16:45 UTC by mlt
Modified: 2017-04-23 12:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mlt 2017-04-22 16:45:14 UTC
Tried to update today and the got the following error messages:

The following packages have unmet dependencies.
 libmarblewidget-qt5-27 : Depends: libastro1 (= 4:17.04.0-0neon+16.04+build31) but 4:16.12.3-0neon+16.04+build28 is to be installed
 marble-plugins : Depends: libastro1 (= 4:17.04.0-0neon+16.04+build31) but 4:16.12.3-0neon+16.04+build28 is to be installed
Comment 1 Jonathan Riddell 2017-04-22 20:21:55 UTC
something is depending on the old libastro1, needs working out what.

what if you run:
apt install libastro1
Comment 2 mlt 2017-04-23 12:15:58 UTC
I get this:

Starting pkgProblemResolver with broken count: 3
Starting 2 pkgProblemResolver with broken count: 3
Investigating (0) marble-plugins [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc )
Broken marble-plugins:amd64 Depends on libmarblewidget-qt5-27 [ amd64 ] < none -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:17.04.0-0neon+16.04+build31)
  Considering libmarblewidget-qt5-27:amd64 0 as a solution to marble-plugins:amd64 3
  Re-Instated libmarblewidget-qt5-27:amd64
  Re-Instated marble-plugins:amd64
Investigating (0) libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs )
Broken libmarblewidget-qt5-26:amd64 Depends on libastro1 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:16.12.3-0neon+16.04+build28)
  Considering libastro1:amd64 10004 as a solution to libmarblewidget-qt5-26:amd64 2
  Removing libmarblewidget-qt5-26:amd64 rather than change libastro1:amd64
Investigating (0) marble-qt [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc )
Broken marble-qt:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) (= 4:16.12.3-0neon+16.04+build28)
  Considering libmarblewidget-qt5-26:amd64 2 as a solution to marble-qt:amd64 0
  Re-Instated marble-qt:amd64
Investigating (0) digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics )
Broken digikam:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs )
  Considering libmarblewidget-qt5-26:amd64 2 as a solution to digikam:amd64 0
  Re-Instated digikam-data:amd64
  Re-Instated digikam:amd64
Done
The following package was automatically installed and is no longer required:
  kde-l10n-engb
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  digikam digikam-data kde-l10n-engb libmarblewidget-qt5-27 marble marble-data marble-plugins marble-qt
Suggested packages:
  digikam-doc gosmore monav-routing-daemon routino
The following packages will be REMOVED
  libmarblewidget-qt5-26
The following NEW packages will be installed
  libmarblewidget-qt5-27
The following packages will be upgraded:
  digikam digikam-data kde-l10n-engb libastro1 marble marble-data marble-plugins marble-qt

When I ran this, the system upgraded without issue.

Thanks for the suggestion.
Comment 3 mlt 2017-04-23 12:16:37 UTC
I get this:

Starting pkgProblemResolver with broken count: 3
Starting 2 pkgProblemResolver with broken count: 3
Investigating (0) marble-plugins [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc )
Broken marble-plugins:amd64 Depends on libmarblewidget-qt5-27 [ amd64 ] < none -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:17.04.0-0neon+16.04+build31)
  Considering libmarblewidget-qt5-27:amd64 0 as a solution to marble-plugins:amd64 3
  Re-Instated libmarblewidget-qt5-27:amd64
  Re-Instated marble-plugins:amd64
Investigating (0) libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs )
Broken libmarblewidget-qt5-26:amd64 Depends on libastro1 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:16.12.3-0neon+16.04+build28)
  Considering libastro1:amd64 10004 as a solution to libmarblewidget-qt5-26:amd64 2
  Removing libmarblewidget-qt5-26:amd64 rather than change libastro1:amd64
Investigating (0) marble-qt [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc )
Broken marble-qt:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) (= 4:16.12.3-0neon+16.04+build28)
  Considering libmarblewidget-qt5-26:amd64 2 as a solution to marble-qt:amd64 0
  Re-Instated marble-qt:amd64
Investigating (0) digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics )
Broken digikam:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs )
  Considering libmarblewidget-qt5-26:amd64 2 as a solution to digikam:amd64 0
  Re-Instated digikam-data:amd64
  Re-Instated digikam:amd64
Done
The following package was automatically installed and is no longer required:
  kde-l10n-engb
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  digikam digikam-data kde-l10n-engb libmarblewidget-qt5-27 marble marble-data marble-plugins marble-qt
Suggested packages:
  digikam-doc gosmore monav-routing-daemon routino
The following packages will be REMOVED
  libmarblewidget-qt5-26
The following NEW packages will be installed
  libmarblewidget-qt5-27
The following packages will be upgraded:
  digikam digikam-data kde-l10n-engb libastro1 marble marble-data marble-plugins marble-qt

When I ran this, the system upgraded without issue.

Thanks for the suggestion.
Comment 4 Jonathan Riddell 2017-04-23 12:32:58 UTC
so looks all good