#163

The fedora-common-ostree.yaml manifest is not a complete manifest and more of an header to be included in other manifests. The minimum manifest to build is fedora-base.yaml from this branch (not yet upstream).

#164

Thanks the fedora-base.yaml worked for me.

#165

I am having trouble installing kvm virtualization packages. I get an error saying that base packages gnutls, pcre2 can not be updated. I tried the fedora-xfce tree and fedora-base tree and in both cases I get the same error. I even removed every layered package but I get the same error.

This issue does not exist with when I switch back to fedora:fedora/32/x86_64/silverblue. I thought packages were in sync with the fedora-32 workstation or is there something I am missing.

#166

Yes, this is a classic case of my images being outdated (there have been several cases reported here). I will rebuild and update them soon. I really need to find the time to automate all that :slight_smile:. In the mean time you should be able to manually download just the RPM needed and install them on top.

#167

Ok. Can I use the comps-sync.py to update it myself. If there are any instructions you can give me on how I can update them myself on a separate tree, I am willing to put in the work. I am grateful any help.

#168

Thanks for the help offer! Unfortunately there is nothing much to do with the sources. I started a new build which will pick up the latest packages and will upload it on my server as soon as I checked that it at least boots up my test system.

I you are interested in helping and want to get involved, we can work on automating builds or trying to make those builds happen on official Fedora infrastructure (but that’s a harder task).

#169

Hi Tim. Thanks for working on the updates. Going forward I think it would be good if more of the community helped out in maintaining these branches too. It would put less demand on your time and we have less bus factor risk. I agree that we need to be automating the builds too. I would like to see Kinoite become the KDE (et. al.) defacto alternative spin. Thanks for all the work you do, I really appreciate it.

1 Like
#170

Thanks! I’ve pushed updates for F32 and Rawhide branches are back (with the usual caveats and the Pantheon branch missing).

#171

I have just uploaded Fedora 33 branches! :tada: Be careful as those have just been branched from Rawhide and will contain bugs. But at the same time they are great for testing. As always, I will stop producing Rawhide branches for a while and will resume once Fedora 33 is released.

The Pantheon branch is currently failing to build due to BZ #1831478. Please help upstream if you want this spin to succeed!

3 Likes
#172

So the elementary-greeter package can’t install because of changing libmutter library name, is that right?

#173

It’s more than just a name change. As mentioned in the ticket, there usually are API changes that requires changes in upstream projects. I don’t use Pantheon nor have the time to work on that so you will have to reach out to upstream.

#174

Fedora 33 Beta is here and is now available for all variants in my repo as the Patheon variant is building again. As always be careful (make backups!) as I can not test every single variant, although I can now pretty much guarantee that the stable KDE variant works well as I uses it on my main laptop.

Happy beta testing! :tada:

Screenshot_fedora_kinoite_33_2020-10-03_14:35:42
Screenshot_fedora_kinoite_33_2020-10-03_14:35:421166×830 242 KB

5 Likes
Official Desktop Environment branches like Kinoite
#175

and unpinned all GNOME based deployments

I had to look up how to do that.
Based on http://www.projectatomic.io/blog/2018/05/pinning-deployments-ostree-based-systems/
I did: rpm-ostree status to see which one was the GNOPE,
and: sudo ostree admin pin --unpin 2 to unpin it.

#176

Fedora 33 has been released :tada: and I have updated all variants with the latest packages. You can update with the following commands:

# Pin your current deployment (optional)
$ sudo ostree admin pin 0

# Rebase to the new version
$ sudo rpm-ostree rebase kinoite:fedora/33/x86_64/kinoite

Example instructions to rebase if you have enabled the rpm-fusion repository:

$ sudo rpm-ostree rebase kinoite:fedora/33/x86_64/kinoite \
      --uninstall rpmfusion-free-release-32-1.noarch \
      --uninstall rpmfusion-nonfree-release-32-1.noarch \
      --install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-33.noarch.rpm \
      --install https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-33.noarch.rpm

As I made a mistake during the initial Fedora 33 build, you will probably get a warning message on the login screen about SDDM and wrong permissions for the KDE variant. This can be easily worked around (and should only be needed once) after the update by logging in via a TTY (use Ctrl + Alt + F2 for example) and using:

$ sudo chown sddm: -R /var/lib/sddm
$ sudo systemctl restart sddm

As always, this is the last Fedora 32 build that I will make as I focus on Fedora 33 and will resume Rawhide builds soon.

Enjoy!

4 Likes
#177

Thank you. Does your distro contains Gnome? Did you consider such combined deployment?

#178

Kinoite does not have multiple desktop environments. If you would like to have multiple desktop environments, you can stay with official GNOME version and install other desktop environments using package layering.

#179

See Kinoite, a KDE (and now XFCE) version of Fedora Silverblue for lists of packages to layer to get additional desktops on top of Silverblue.

#180

Thanks, I already have that packages layered. Just thought Kinoite could add benefit of more quick upgrades etc.

#181

Can’t start my containers:

[bam@host bam]$ toolbox enter 
Error: failed to start container fedora-toolbox-33
#182

Hello @bam,
Try podman healthcheck run on the toolbox container.

1 Like