Bug #2926

qgis-plugin-grass-common left out of ubuntuGIS unstable install

Added by gfleming - almost 3 years ago. Updated almost 3 years ago.

Status:Closed Start Date:
Priority:Low Due date:
Assigned to:nobody - % Done:

0%

Category:Build/Install
Target version:Version 1.6.0
Platform:Debian Patch supplied:
Platform version:Ubuntu 10.04.1 LTS 2.6.32-24-generic x86_64 Affected version:master
Status info:1 Causes crash or corruption:No
Resolution:fixed

Description

qgis-plugin-grass-common seems to have been left out - I did apt-get install of all marked upgrades that apt-get update picked up and this was left out. Once I installed it separately afterwards that seemed to solve the issue

Associated revisions

Revision 665157bd5a04de37a302a23c633926862a61a688
Added by Jürgen Fischer almost 3 years ago

debian packaging update (fixes #2926)

git-svn-id: http://svn.osgeo.org/qgis/trunk@14001 c8812cc2-4d05-0410-92ff-de0c093fc19c

Revision 41780e9ab0787530146cd583aeb64ef2a44f43b9
Added by Jürgen Fischer almost 3 years ago

debian packaging update (fixes #2926)

git-svn-id: http://svn.osgeo.org/qgis/trunk/qgis@14001 c8812cc2-4d05-0410-92ff-de0c093fc19c

History

Updated by Jürgen Fischer almost 3 years ago

did you have trunk builds of 1.5.0 installed before?

Updated by gfleming - almost 3 years ago

Replying to [comment:1 jef]:

did you have trunk builds of 1.5.0 installed before?

no, only 1.4 from ubuntugis-unstable.

but here are more details from qgis-users list:

On 07/31/2010 07:04 PM, Alex Mandel wrote:

This is a just note to help other users who may encounter the same issue upgrading to QGIS 1.5. If you go to upgrade and get the following error:

E: /var/cache/apt/archives/qgis-plugin-grass-common_1.5.0-1~lucid1_all.deb: trying to overwrite '/usr/share/qgis/themes/default/grass/grass_close_edit.png', which is also in package qgis-common 0

Just go back to your update tool/package manager and upgrade the qgis-plugin-grass-common package again.

Thanks, Alex

Same issue on my Ubuntu 10.4 machines. Workaround works, but can this be
fixed so that it doesn't occur on future updates?

Updated by Jürgen Fischer almost 3 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

fixed in .

Also available in: Atom PDF