unhelpful error when building a classic snap: classic confinement requires the core_dynamic_linker to be set

Bug #1650946 reported by Leo Arias on 2016-12-18
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Snapcraft
High
Sergio Schvezov
launchpad-buildd
High
Colin Watson

Bug Description

I got this error when trying to snap the git demo in xenial 16.04:

classic confinement requires the core_dynamic_linker to be set

And then I have no idea what else to do.

The error message should explain a little more about what it's missing, and how to get it.

Related branches

XiaoGuo, Liu (liu-xiao-guo) wrote :

I got the same issue. How to proceed with it? Thanks!

Sergio Schvezov (sergiusens) wrote :

I need more information, I have git from that branch running just fine with classic confinement

Changed in snapcraft:
status: New → Incomplete
XiaoGuo, Liu (liu-xiao-guo) wrote :

I have a very simple sample code at:

https://github.com/liu-xiao-guo/helloworld-classic

When I build the sample code, it shows http://imgur.com/a/zJbCk

XiaoGuo, Liu (liu-xiao-guo) wrote :

liuxg@liuxg:~/snappy/desktop/helloworld-classic$ snapcraft --version
2.24

XiaoGuo, Liu (liu-xiao-guo) wrote :

I have tried it using LXD container (yaketty). Inside the container, I tried to build my sample project at https://github.com/liu-xiao-guo/helloworld-classic, and it was the same issue.

liuxg@flying-snake:~/apps/helloworld-classic$ snapcraft
Use of build-properties in the schema is deprecated.
Plugins should now implement get_build_properties
DEPRECATED: The 'copy' plugin's functionality has been replaced by the 'dump' plugin, and it will soon be removed.
Use of build-properties in the schema is deprecated.
Plugins should now implement get_build_properties
Preparing to pull gnu-hello
classic confinement requires the core_dynamic_linker to be set

Sergio Schvezov (sergiusens) wrote :

I suspect this is a fallout of not having `core` snap installed on the system where building.

Sergio Schvezov (sergiusens) wrote :

I'll see how we can automate this or figure out why we have such an ugly error message.

Changed in snapcraft:
status: Incomplete → In Progress
milestone: none → next
assignee: nobody → Sergio Schvezov (sergiusens)
importance: Undecided → High
Changed in snapcraft:
status: In Progress → Fix Committed
Leo Arias (elopio) wrote :

Thank Sergio!

Stuart Bishop (stub) wrote :

Is there a work around? Running 2.24 (along with most people trying to test classic snaps, which we have announced)

Stuart Bishop (stub) wrote :

Work around involves removing snapd (and all snaps and their contained data!) and reinstalling:

sudo apt purge -y snapd
sudo apt install snapd
sudo snap install core

Stuart Bishop (stub) wrote :

Launchpad builds of classic snaps are failing with this error

Colin Watson (cjwatson) on 2017-01-11
affects: launchpad → launchpad-buildd
Colin Watson (cjwatson) wrote :

We have an email thread at the moment to try to work out the right approach for this in Launchpad builds.

Changed in launchpad-buildd:
status: New → Triaged
importance: Undecided → High
Changed in snapcraft:
status: Fix Committed → Fix Released
Colin Watson (cjwatson) wrote :

This will start working once snapcraft 2.27 gets into -updates.

launchpad-buildd (142) trusty; urgency=medium

  * lpbuildd.binarypackage: Pass DEB_BUILD_OPTIONS=noautodbgsym if we have
    not been told to build debug symbols (LP: #1623256).
  * debian/upgrade-config, lpbuildd.slave: Drop compatibility with ancient
    pre-lucid versions of python-apt.
  * lpbuildd.pottery.intltool: Remove unused and Python-3-unfriendly
    string/file conditional from ConfigFile.__init__.
  * Use Python-3-compatible forms of "print" and "except".
  * buildsnap: Set SNAPCRAFT_SETUP_CORE=1 during pull phase so that
    snapcraft will fetch and unpack the core snap for classic confinement
    when necessary (LP: #1650946).

 -- Colin Watson <email address hidden> Fri, 10 Feb 2017 14:53:43 +0000

Changed in launchpad-buildd:
assignee: nobody → Colin Watson (cjwatson)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers