When an update that removes packages is available, mintUpdate falsely reports that there are broken packages that need to be fixed first.

Bug #565013 reported by platnicat
30
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Linux Mint
Fix Released
Undecided
abe
synaptic (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

There was an update to avant-window-navigator available, it showed up fine, but when I clicked "Update", it told me "Please fix broken packages first." Synaptic handled the update fine, and it told me that 2 packages (awn-manager and something I forgot :-P) were to be removed.

Revision history for this message
Clement Lefebvre (clementlefebvre) wrote :

This message comes from the CLI version of synaptic. If considered a bug then the CLI version should be able to handle this kind of scenario instead of displaying an error.

Marking as upstream on synaptic.

Not to upstream devs: This is how synaptic is called:

sudo /usr/sbin/synaptic --hide-main-window --non-interactive --progress-str "Please wait, this can take some time" --finish-str "Update is complete" --set-selections-file filename

filename refers to a file containing a set of "package install" lines (following dpkg --set-selection format).

Changed in linuxmint:
status: New → Triaged
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

Could you please attach the file /var/log/apt/term.log to this report ? Thanks.

Changed in synaptic (Ubuntu):
status: New → Incomplete
Revision history for this message
platnicat (platnicat) wrote :
Download full text (97.5 KiB)

Sure, here it is:

Log started: 2010-04-01 13:23:54
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 193009 files and directories currently installed.)

Preparing to replace guayadeque-svn 0803~karmic-1 (using .../guayadeque-svn_0865~karmic-1_i386.deb) ...

Unpacking replacement guayadeque-svn ...

Processing triggers for desktop-file-utils ...

Setting up guayadeque-svn (0865~karmic-1) ...

Log ended: 2010-04-01 13:24:38

Log started: 2010-04-01 15:15:00
Selecting previously deselected package iw.

(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 193009 files and directories currently installed.)

Unpacking iw (from .../archives/iw_0.9.14-1_i386.deb) ...

Selecting previously deselected package aircrack-ng.

Unpacking aircrack-ng (from .../aircrack-ng_1%3a1.0-1_i386.deb) ...

Processing triggers for man-db ...

Setting up iw (0.9.14-1) ...

Setting up aircrack-ng (1:1.0-1) ...

Log ended: 2010-04-01 15:15:43

Log started: 2010-04-02 19:07:15
Selecting previously deselected package python2.5-minimal.

(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 193169 files and directories currently installed.)

Unpacking python2.5-minimal (from .../python2.5-minimal_2.5.4-1ubuntu6.1_i386.deb) ...

Selecting previously deselected package libdb4.6.

Unpacking libdb4.6 (from .../libdb4.6_4.6.21-13ubuntu2_i386.deb) ...

Selecting previously deselected package libmimic-dev.

Unpacking libmimic-dev (from .../libmimic-dev_1.0.4-2_i386.deb) ...

Selecting previously deselected package python2.5.

Unpacking python2.5 (from .../python2.5_2.5.4-1ubuntu6.1_i386.deb) ...

Selecting previously deselected package python-libmimic.

Unpacking py...

Revision history for this message
Clement Lefebvre (clementlefebvre) wrote :

Well, it looks like this won't be fixed upstream, so we'll workaround it. Setting the milestone to Katya.

Changed in linuxmint:
milestone: none → katya-rc1
status: Triaged → Confirmed
Revision history for this message
Clement Lefebvre (clementlefebvre) wrote :

mintupdate mistakenly reports updates on dependencies which need to be removed. This sends synaptic conflicting messages as it's told to upgrade but also to keep the packages that need to be removed.

The issue was identified in mintupdate and will make its way towards LMDE and Mint 11.

The error message from synaptic is a bit cryptic and doesn't pinpoint the package in cause... but the bug itself is definitely related to mintupdate.

Sorry for the confusion on this and the time it took us to find the cause.

Changed in synaptic (Ubuntu):
status: Incomplete → Invalid
Changed in linuxmint:
status: Confirmed → Fix Committed
Changed in linuxmint:
status: Fix Committed → Fix Released
abe (p-horne81)
Changed in linuxmint:
assignee: nobody → abe (p-horne81)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.