extension: kde-neon fails on arm64

Bug #1881963 reported by Kyle Nitzsche
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Trying to use the snapcraft kde-neon extension fails on arm64:

ubuntu@ubuntu:~/snap/qt1$ snap try prime
error: cannot perform the following tasks:
- Ensure prerequisites for "test-qt" are available (cannot install prerequisite "kde-frameworks-5-core18": no snap revision available as specified)

And indeed, the kde-frameworks-5-core18 snap is not avail on arm64 (preinstalled server bionic for pi3):
ubuntu@ubuntu:~/snap/qt1$ snap info kde-frameworks-5-core18
error: no snap found for "kde-frameworks-5-core18"

But it is available, for example on classic xenial amd64:

$ snap info kde-frameworks-5-core18
name: kde-frameworks-5-core18
summary: KDE Frameworks 5
publisher: KDE✓
store-url: https://snapcraft.io/kde-frameworks-5-core18
contact: https://www.kde.org/support/
license: unset
description: |
  KDE Frameworks are addons and useful extensions to Qt
snap-id: GeIofQKAwadB4OEM8lOzdSMAc56sCNdL
tracking: latest/stable
refresh-date: 40 days ago, at 10:39 EDT
  latest/stable: 5.61.0 2019-08-27 (32) 273MB -
  latest/candidate: 5.67.0 2020-02-17 (35) 303MB -
  latest/beta: ↑
  latest/edge: 5.54.0+p18.04+git20190115.0202 2019-01-16 (25) 250MB -
installed: 5.61.0 (32) 273MB -

I'd expect an extension to snapcraft would work on the supported/reference platforms.


Revision history for this message
Merlijn Sebrechts (merlijn-sebrechts) wrote :

The kde frameworks snap is maintained by the kde-neon team. It might be better to post this bug on their bugtracker. Although I have no idea where that is.

Revision history for this message
Jonathan Riddell (jr) wrote :

You can report here if you like, others have asked for this too so we should look into it


Changed in snapcraft:
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

While I am eager to see snaps on arm64 using the kde extension, extensions are just prescribed ways of operating, and as can be seen from the results, extensions are bound to snap (base/content-interface) availability.

This is not the only extension to have this trait. So I am closing this since the upstream bug exists to track this.

If the bug is about handling the error differently, then please log a new bug about this.

Changed in snapcraft:
status: Confirmed → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers