This appears to be happening because the previous version of collada-dom-dev depended on collada-dom2.4-dp-dev, and the upgraded version of collada-dom-dev depends on collada-dom2.4-sp-dev. Why was this dependency changed, and what implications does that have for downstream packages? I assume sp and dp stand for single and double precision, and the differences there can be pretty significant in certain applications. -Austin On 12/24/2015 08:17 AM, Austin Hendrix via ros-release wrote: > > Thanks for the link! > > I have family obligations today but I will try to dig through my logs > and figure out why it's trying to install the sp-dev version during > dist-upgrade. > > -Austin > > On December 24, 2015 11:13:57 AM Tully Foote via ros-release > wrote: > >> The issue with them properly colliding is ticketed. But if Austin was >> only doing an upgrade, it should not be switching. We cannot have >> dependencies on both the single precision and double precision >> versions. We need to find out why the single precision version is >> being installed on an upgrade and avoid that. >> >> Tully >> >> >> >> On Thu, Dec 24, 2015 at 7:30 AM, G.A. vd. Hoorn - 3ME via ros-release >> > wrote: >> >> On 24/12/15 16:26, Austin Hendrix via ros-release wrote: >> >> It looks like the new collada packages that were pulled in >> recently are >> causing upgrade problems. >> >> I did an apt-get dist-upgrade on my system today, and it >> looks like >> there's a collision between collada-dom2.4-sp-dev and >> collada-dom2.4-dp-dev, and apt wants to install both at the >> same time: >> >> $ sudo apt-get install -f >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Correcting dependencies... Done >> The following extra packages will be installed: >> collada-dom2.4-sp-dev >> The following NEW packages will be installed: >> collada-dom2.4-sp-dev >> 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. >> 47 not fully installed or removed. >> Need to get 0 B/206 kB of archives. >> After this operation, 5,285 kB of additional disk space will >> be used. >> Do you want to continue? [Y/n] >> (Reading database ... 333408 files and directories currently >> installed.) >> Preparing to unpack >> .../collada-dom2.4-sp-dev_2.4.4.1-ubuntu1~trusty1_amd64.deb ... >> Unpacking collada-dom2.4-sp-dev (2.4.4.1-ubuntu1~trusty1) ... >> dpkg: error processing archive >> /var/cache/apt/archives/collada-dom2.4-sp-dev_2.4.4.1-ubuntu1~trusty1_amd64.deb >> (--unpack): >> trying to overwrite >> '/usr/lib/cmake/collada_dom-2.4/collada_dom-config.cmake', >> which is also >> in package collada-dom2.4-dp-dev 2.4.4.0-ubuntu1~trusty1 >> dpkg-deb: error: subprocess paste was killed by signal >> (Broken pipe) >> Errors were encountered while processing: >> /var/cache/apt/archives/collada-dom2.4-sp-dev_2.4.4.1-ubuntu1~trusty1_amd64.deb >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> >> Thoughts? Known workarounds? >> >> >> This is a 'known' issue, see [1] and the linked issues in the >> answer. The packages have been fixed and are waiting for the next >> sync. >> >> >> Is there a known reason why apt would want to install the sp >> and dp >> versions at the same time? Up until now I think I've only had >> the dp >> version installed. >> >> If the sp and dp versions aren't supposed to be installed at >> the same >> time, can the maintainer please add a Conflicts: to the >> package header? >> >> >> >> Gijs >> >> [1] >> http://answers.ros.org/question/222892/collada-dom24-sp-dev-causes-dist-upgrade-to-fail-on-ubuntu-1404/ >> >> >> >> _______________________________________________ >> ros-release mailing list >> ros-release@lists.ros.org >> http://lists.ros.org/mailman/listinfo/ros-release >> >> >> _______________________________________________ >> ros-release mailing list >> ros-release@lists.ros.org >> http:/ ​/​lists​.​ros​.​org/​mailman/​listinfo/​ros-release >> >> > > > _______________________________________________ > ros-release mailing list > ros-release@lists.ros.org > http://lists.ros.org/mailman/listinfo/ros-release _______________________________________________ ros-release mailing list ros-release@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-release