Skip to content

Instantly share code, notes, and snippets.

@YaLTeR
Last active August 7, 2026 08:40
Show Gist options
  • Select an option

  • Save YaLTeR/c33138145633d9eb83ad5076ef1620e1 to your computer and use it in GitHub Desktop.

Select an option

Save YaLTeR/c33138145633d9eb83ad5076ef1620e1 to your computer and use it in GitHub Desktop.
AerynOS notes
  • Installer just panics and quits if it fails to download some package, and you have to go through the entire configuration again to retry.
  • Installer didn't add boot entry to my EFI for some reason so I had to mount boot and EFI partitions and call bootctl install to fix it.
  • moss state export on a clean install produces a file with many packages. I'd expect just a few metapackages that I can base off of and remove/add my own. So that the base metapackages can get updated automatically.
    • The pkgsets like pkgset-aeryn-base-desktop seem to be missing a lot of important stuff. You need to specify quite a bit of extra packages in system-model for a working system.
  • The pkgsets are missing some packages I would expect them to have. For example, in the GNOME desktop, there was no networkmanager-openvpn-gnome or gvfs-smb. Printing also doesn't currently quite work out of the box apparently.
  • Ability to override-remove a package so I can install a pkgset, then remove some specific app from it.
  • No easy way to see/track my own changes to /etc compared to (many) files that are created there automatically.
  • Can't exit out of "Blitting filesystem" even with Ctrl-C.
  • Auto-installed command doesn't re-run automatically. (80-command-not-found.sh) (also there's no fish version)
  • boulder recipe new doesn't work properly when given a non-archive file URL.
  • Confusing warning when building one of my packages: Warning | 'version' and first parsed upstream version do not match. Expected: v2rayA, got: 2.2.7.5. What? Why is the name the "expected version"? Where did it even get it from?
  • Ability to moss install build dependencies of a package like dnf builddep.
  • Package -dbgsource in addition to -dbginfo so debuggers and profilers can show the actual package source.
  • Some kind of debuginfo() matcher to install dbginfo + dbgsource for a given package or filename like dnf debuginfo-install. Because sometimes it's more convenient, or unclear, e.g. mesa-vulkan-drivers-dbginfo does not exist for the .so it provides.
  • In system-model.kdl, ability to install specific packages (like vscode-bin which doesn't have any deps) from a different repo (like volatile).
  • moss sync doesn't seem to sort packages alphabetically.
  • moss sync doesn't tell you which package caused an unsatisfied dependency:
    $ sudo moss sync -u
    Refreshed local
    Refreshed unstable
    Error: sync: sync: transaction: No such name: soname(libcava.so.0(x86_64))
    
  • All moss commands output the system-model spam all the time (and don't tell you how to silence it).
    • You can silence by putting disable_warning #true in system-model.kdl, but it doesn't tell you that.
  • moss search-file doesn't search available (not installed) packages.
  • moss info -f doesn't show the file list on not-installed packages.
  • The Rust uutils are still buggy. E.g. something I've hit right away: uutils/coreutils#12393 (already fixed in next release) There's also been concerning reports from Ubuntu trying them. I wouldn't really mind GNU coreutils.
  • Due to the use of a blanket-disable systemd preset, systemctl enable doesn't work (gets automatically reset). This is not obvious and not really expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment