Can i make a snap that solely has an edge channel?

snapcraft
1

I’m planning on a making a snap for Scribus https://www.scribus.net/ There is a huge gap between the current stable 1.6.2 and the development build 1.7.0

Can i just make the snap solely for the development build?

2

Well, yes! you can. if you need help feel free to ask UwU

1 Like
3

Great. Are there examples of this already? Could you point me to one ?

Is that a username ?

1 Like
4

oh, that’s an emoticon. <facepalm>

1 Like
5

If you register a snap name on the snap store and connect it to a repository, the builds will be automatically published to the edge channel, so there isn’t anything special you need to do.

If you build and publish locally, you can choose what channel to release the snap to (Build and publishing example | Snapcraft documentation).

1 Like
6

You can simply set the grade to devel, and then, even you cannot knowingly push that snap to candidate or stable. It’ll have to be within beta or edge

7

Thanks. I will have a go at this then and report back any issues.

8

Haven’t been able to build so far:

Edit: note here is the scribus-svn from the AUR https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=scribus-svn

9

your indentation is messed up, move scribus-git and all lines below it til the end of the file two spaces to the right so it is on the same level as “my-part” … (and remove the whole my-part boilerplate part :slight_smile: )

1 Like
10

Thanks. That’s a newb mistake, apologies.

Progress.

Now I’m getting a lot of
Cannot find package listed in 'build-packages': ${package-name}
where package-name changes. How do I check if the packages are named correctly ? Is there a list I can cross-reference ?

11

reposting for visibility

12

There is a flatpak for Scribus v1.7.0[1] in addition to the the AUR SVN PKGBUILD[2]. This will be even more of a help. Can someone help make this snapcraft.yaml more robust ?

1: https://codeberg.org/Scribus/scribus-flatpak-devel/src/branch/main/net.scribus.Scribus.yaml 2: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=scribus-svn

13

I’m having a go at using github co-pilot to see if it can help me in the meantime.

14

Is there a steeamlined way of figuring out what the names of the ubuntu packages x-reffed with say AUR or Flatpak ?

15

The only names you need are the ones from the Ubuntu archive, just use apt …

16

I’m on manjaro, but i guess i can find a shell that uses apt. Maybe github codespaces ?

17

Try https://packages.ubuntu.com/ - ensure the repo being searched matches the base snap you’re using.

1 Like
18

OK, i got through the compilation process! But then the build fails mysteriously at:

Creating snap package...
Command '['snap', 'pack', '--filename', 'scribus-git_1.7.0_armhf.snap', '--compression', 'xz', PosixPath('/build/scribus-git/prime'), PosixPath('/build/scribus-git')]' returned non-zero exit status 1.
Full execution log: '/root/.local/state/snapcraft/log/snapcraft-20241229-215101.633829.log'
Build failed
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 302, in run
    self.build()
  File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 286, in build
    self.run_build_command(["snapcraft"], cwd=output_path, env=env)
  File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 62, in run_build_command
    return self.backend.run(args, cwd=cwd, env=full_env, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 733, in run
    subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-noble-armhf', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/lpbuildd-git-proxy', '--env', 'SNAPPY_STORE_NO_CDN=1', '--env', 'LAUNCHPAD_INSTANCE=production', '--env', 'LAUNCHPAD_SERVER_URL=launchpad.net', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build-request-id": "lp-94830750", "build-request-timestamp": "2024-12-29T21:35:17Z", "build_url": "https://launchpad.net/~build.snapcraft.io/+snap/b3f864eabb44d111e6d453a28e872f5c/+build/2693001"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--env', 'SNAPCRAFT_BUILD_FOR=armhf', '--', '/bin/sh', '-c', 'cd /build/scribus-git && linux32 snapcraft']' returned non-zero exit status 1.

I don’t have access to the
/root/.local/state/snapcraft/log/snapcraft-20241229-215101.633829.log
logfile because I’m compiling through https://snapcraft.io/scribus-git/builds

19

I’m stumped here. Any help would be appreciated :pray:

20

I guess my issue now is more about building the snap and is a digression of the original question. Should I mark this as solved and open a new thread ?