qgis and osgearth stuck in trusty-proposed for armhf

Bug #1632800 reported by Nish Aravamudan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

update_excuses and update_output both indicate that qgis and osgearth should be migrateable to the release pocket, but for some reason the armhf build never did. In disucssions on #ubuntu-devel, it was suggested these were post-release builds that went from failed-to-build to successful. However, Steve Langasek was unable to use:

copy-package -e $ver --force-same-destination --from-suite=trusty-proposed -b foo

as suggested by Adam Conrad, with an error like:

'binaries conflicting with the existing ones'.

However, rmadison indicates no published binaries for armhf in the release pocket for qgis or osgearth.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

somewhere this might be related to the fact that the build have been started and published for ubuntu Utopic [armhf]
https://launchpad.net/ubuntu/+source/osgearth/2.4.0+dfsg-6
https://launchpad.net/ubuntu/+source/qgis/2.0.1-2build2
the fact that only armhf has been copied (not sure how) to utopic seems to be the reason preventing it from migrate
(this is a wild guess, just based on two minutes of spare time)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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