Activity log for bug #110152

Date Who What changed Old value New value Message
2007-04-26 03:31:36 schwan bug added bug
2007-04-26 03:44:25 schwan bug added attachment 'vim-gtk_feisty_error.png' (screen capture of error)
2007-05-17 23:50:34 Micah Cowan vim: status Unconfirmed Needs Info
2007-05-17 23:50:34 Micah Cowan vim: assignee micahcowan
2007-05-17 23:50:34 Micah Cowan vim: statusexplanation Are you still experiencing this problem?
2007-05-18 19:23:45 Micah Cowan vim: status Needs Info Unconfirmed
2007-05-18 19:23:45 Micah Cowan vim: statusexplanation Are you still experiencing this problem?
2007-05-18 19:23:55 Micah Cowan vim: assignee micahcowan
2007-05-18 19:37:23 Micah Cowan vim: status Unconfirmed Needs Info
2007-05-18 19:37:23 Micah Cowan vim: assignee micahcowan
2007-05-18 19:37:23 Micah Cowan vim: statusexplanation 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.
2007-06-05 21:26:55 Micah Cowan vim: status Needs Info Confirmed
2007-06-05 21:26:55 Micah Cowan vim: statusexplanation 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.
2007-06-15 18:47:36 Micah Cowan vim: status Confirmed Needs Info
2007-06-15 18:47:36 Micah Cowan vim: statusexplanation 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?
2007-06-15 20:12:14 Micah Cowan vim: status Needs Info Rejected
2007-06-15 20:12:14 Micah Cowan vim: assignee micahcowan
2007-06-15 20:12:14 Micah Cowan vim: statusexplanation 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? 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.