vim-gtk install failed in feisty (7.0.4)

[schwan]

Binary package hint: vim-gtk

After I upgrade from ubuntu 6.10 to 7.04 via update-manager, during the install
process, I failed to upgrade due to conflict dependence vim-tiny, so remove the
vim-gtk installed in 6.10. then, it managed to upgrade to 7.04.
after the system is reboot, I tried to install vim-gtk via synaptic, it show
the message below.
vim-gtk:
  Depends: vim-runtime (=1:7.0-164+1ubuntu7) but 1:7.0-017+4-1ubuntu1 is to be installed

[Micah Cowan (micahcowan)]

Are you still experiencing this problem?

[schwan (schwanliu)]

Hi, Micah
I fixed in this way:
1. remove the gvim (vim-gtk)
2. apt-get dist-upgrade
anyway, Thanks!

Schwan Liu

Micah Cowan wrote:
> Are you still experiencing this problem?
>
> ** Changed in: vim (Ubuntu)
> Assignee: (unassigned) => Micah Cowan
> Status: Unconfirmed => Needs Info
>
>

[schwan (schwanliu)]

Yes, Micah
I made a mistake when I replied the email. the same message is shown when I install it with synaptic.

vim-gtk:
  Depends: vim-runtime (=1:7.0-164+1ubuntu7) but 1:7.0-017+4-1ubuntu1 is to be installed

[Micah Cowan (micahcowan)]

Can you attempt to specifically install the correct version of vim-runtime directly in Synaptic, rather than as a dependency from vim? That is, choose vim-runtime version 7.0-164+1ubunt7 in Synaptic and install that? Let me know how that goes.

Also, please attach your /etc/apt/sources.list.

[Wade Simmons (wadesimmons)]

I am running into a similar problem (cannot install vim-gtk in feisty), but with the following cause:

The following packages have unmet dependencies:
  vim-gtk: Depends: vim-common (= 1:7.0-164+1ubuntu7) but 1:7.0-164+1ubuntu7.1 is to be installed
           Depends: vim-runtime (= 1:7.0-164+1ubuntu7) but 1:7.0-164+1ubuntu7.1 is to be installed

Looks like a package for vim-gtk 1:7.0-164-1ubuntu7.1 has not been created.

[Ryan Koppenhaver (ryan-koppenhaver)]

I had the same issue trying to (re)install vim-perl after a dist-upgrade. FYI, I can confirm that forcing the old versions of vim-gui-common, vim-common, and vim-runtime in Synaptic allowed me to reinstall vim-perl.

However, I noticed this...

  $ sudo apt-get update >/dev/null; apt-cache show vim-perl | grep Version
  Version: 1:7.0-164+1ubuntu7

... but packages.ubuntu.com lists the most recent version as 1:7.0-164+1ubuntu7.1 (And after redoing the dist-upgrade, I manually downloaded and install the .deb with dpkg -i with no errors.)

Since vim-perl and vim-gtk, but not the prerequisite vim-* packages, are in universe, I wonder if this might be (for me at least) a configuration issue with my sources.list.

Hope someone finds this helpful!

[Ryan Koppenhaver (ryan-koppenhaver)]

Quick update: It turns out that changing

  deb http://security.ubuntu.com/ubuntu feisty-security main restricted

to

  deb http://security.ubuntu.com/ubuntu feisty-security main restricted universe

in /etc/apt/sources.list and rerunning apt-get update makes everything work right for me again.

[Wade Simmons (wadesimmons)]

Thanks Ryan, adding universe to my feisty-security apt.source fixed it for me as well. Should the vim updates be split across sources like this?

[Micah Cowan (micahcowan)]

Aside from the question as to whether vim updates should be split across sources (which I've just asked on ubuntu-devel-discuss), there will always be packages in universe that depend on packages in main, so this scenario can crop up regardless. For those of you with unmatched feisty and feisty-security lines: had you edited your sources.list file by hand, or did you use the "Software Sources" manager to deal with it?

[Wade Simmons (wadesimmons)]

I edited my sources.list manually. I must have just missed the feisty-security entry when I did it. Thanks for the help with this.

[addius (davidjh)]

I also edited sources.list manually when I upgraded - I just did %s/edgy/feisty/g

[Micah Cowan (micahcowan)]

As the problem currently appears to be caused by user error, I'm going to close this bug out.

If any of you that experienced problems had never manually adjusted your sources.list file, this probably indicates a bug with whatever software generated the sources.list automatically ("Software Sources"?); either reopen this bug and alter the description and package target suitably, or create a new bug, which should include a reference to this one.

A question remains as to whether more could be done to prevent this situation; but the solution is not obvious, and would require discussion. It would also be inappropriate for a bug report, and more suitable instead as a feature specification. If any of you have ideas related to this, please do submit them to ubuntu-devel-discuss, and/or create a new feature specification, so that we can help users to avoid this problem in the future.

[Micah Cowan (micahcowan)]

addius: I'm actually more interested in whether the mismatch between feisty and feisty-security was caused by manual editing or not; if all you did was s/edgy/feisty, then I'd still be curious as to how edgy-security had lacked "universe" as well. Had you manually edited your sources.list, perhaps adding the edgy-security line in, prior to that substitution command?

[addius (davidjh)]

Micah, I wouldn't keep this bug open on my account. I had indeed edited apt.sources way back when I was running dapper. I'd mostly just uncommented lines, so I'm still not sure why I didn't wind up with dapper-security having "universe", but since I can't recall the exact edits I made I'm not going to be able to provide you with very reliable steps to reproduce and won't be able to say for certain that it wasn't just user error.