Skip to content

Conversation

@joebonrichie
Copy link
Contributor

@joebonrichie joebonrichie commented Aug 4, 2025

To test this PR, build it as follows:

gotoaosrepo && gh pr checkout 968
for pkg in packagekit gnome-software
do
    { chpkg ${pkg} && just build && just mv-local ;} \
    || { echo "Something went wrong while building ${pkg} -- stopping." && break ;}
done

There is no need to build and install moss on its own, as packagekit links statically to the moss functionality it needs.

Then run sudo moss repo update && sudo moss it packagekit && sudo moss dr volatile && sudo moss sync -u && sudo moss er volatile to install the packagekit package and sync the gnome-software package without installing available updates from volatile in the same go.

At this point, you need to ensure that your session can see the new /usr directory. So at the very least, you should re-log (a reboot might be necessary).

After this, run:

pkcon backend-details

... which should output something like this:

❯ pkcon backend-details
Name:           moss
Description:    Moss - atomic stateful package manager
Author: Aeryn OS Developers <copyright@aerynos.com>

If you see something like this above, you are now ready to run gnome-software and try using it to update your system.

IFF the PackageKit backend is working like it should, THEN you should be able to see your installed moss-format .stone packages in the Installed list in G-S.

@joebonrichie joebonrichie force-pushed the packagekit branch 5 times, most recently from c1d5475 to aea0c27 Compare August 7, 2025 16:38
@joebonrichie joebonrichie force-pushed the packagekit branch 2 times, most recently from 2d7e761 to a1bedf5 Compare August 17, 2025 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant