All this interest in atomic workstation made me dust off my vm.
While upgrading it, I ran into a number of questions that I couldn't find any answers for. This might be useful information to put on a new atomic workstation website.
1) How do I find out what I'm running ?
I guess the answer to this is rpm-ostree status, but what does it actually tell me ?
● atomicws:atomicws/fedora/x86_64/continuous Version: 26.447 (2018-01-29 04:58:49) BaseCommit: ba986d4649f08705185ba1ce7208e72d149b1e35314d112a86348cb1d61f6f52 LayeredPackages: powerline
It would be nice to explain this output a bit - I assume the first 'atomicws' is a repository name, and 'atomicws/fedora/x86_64/continuous' is a branch name. Version 26.447 may indicate that I am running some version of Fedora 26.
Unfortunately, I haven't really seen the gnome-software support in action yet, but I hope it shows this information as well.
2) How do I get the latest updates ?
rpm-ostree upgrade is easy enough (once I've found it).
3) How do I upgrade to a newer release ? 4) How do I find out what branches are available to rebase to ? 5) Where is the repo configuration stored ?
This is where I got stuck - I could not find any answers to these. Very frustrating, a normal user would have given up here.
Eventually, Kalev told me to create a file in /etc/ostree/remotes.d/ with some content, and then I figured out to run
ostree remote refs fedora
to see the branches in the repo, and
rpm-ostree rebase fedora:fedora/27/x86_64/workstation
to upgrade to one of them. I blindly picked this branch, since I have no idea what the difference between
fedora/27/x86_64/testing/workstation fedora/27/x86_64/updates/workstation fedora/27/x86_64/workstation
might be...
Also, I had to disable gpg verification, since I didn't know where to find the key for that repo.
We need to make the rpm-ostree plugin support distro-upgrades inside gnome-software. And also make this information available in some obvious place.
Basically, the vast majority of this is going to be fixed by: https://github.com/projectatomic/rpm-ostree/issues/1081 Which is my highest priority right now.
It's 100% true that learning rpm-ostree today requires learning *both* ostree and rpm. From my talk: https://fedorapeople.org/~walters/2018.01-devconf/index.html#/4 It's like we have one dashboard, but it has two separate sections. We're like a plug-in hybrid where you have to understand how to fill with *both* gas and electric, and how they interoperate.
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense.
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense.
It makes sense, as far as fluffy metaphors ever do. But I was looking more for concrete answers that we can put on a webpage _now_, not for promises of an eventual bright future...
On Tue, Jan 30, 2018 at 3:42 PM Colin Walters walters@verbum.org wrote:
Basically, the vast majority of this is going to be fixed by: https://github.com/projectatomic/rpm-ostree/issues/1081 Which is my highest priority right now.
It's 100% true that learning rpm-ostree today requires learning *both* ostree and rpm. From my talk: https://fedorapeople.org/~walters/2018.01-devconf/index.html#/4 It's like we have one dashboard, but it has two separate sections. We're like a plug-in hybrid where you have to understand how to fill with *both* gas and electric, and how they interoperate.
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense. _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
Here is another question (maybe this is more a bug):
Rebasing is a long operation, so inevitably my laptop will suspend halfway through. When it resumes, the rpm-ostree rebase operation running inside my vm never continues downloading - it just sits there, despite an operational network connection. When I eventually hit Ctrl-C, it takes a very long time (like a minute, at least) to actually stop, telling me to wait for it to cancel its transaction. The wait seems excessive...
On Tue, Jan 30, 2018 at 3:47 PM Matthias Clasen mclasen@redhat.com wrote:
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense.
It makes sense, as far as fluffy metaphors ever do. But I was looking more for concrete answers that we can put on a webpage _now_, not for promises of an eventual bright future...
On Tue, Jan 30, 2018 at 3:42 PM Colin Walters walters@verbum.org wrote:
Basically, the vast majority of this is going to be fixed by: https://github.com/projectatomic/rpm-ostree/issues/1081 Which is my highest priority right now.
It's 100% true that learning rpm-ostree today requires learning *both* ostree and rpm. From my talk: https://fedorapeople.org/~walters/2018.01-devconf/index.html#/4 It's like we have one dashboard, but it has two separate sections. We're like a plug-in hybrid where you have to understand how to fill with *both* gas and electric, and how they interoperate.
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense. _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
Here is another question (maybe this is more a bug):
Rebasing is a long operation, so inevitably my laptop will suspend halfway through. When it resumes, the rpm-ostree rebase operation running inside my vm never continues downloading - it just sits there, despite an operational network connection. When I eventually hit Ctrl-C, it takes a very long time (like a minute, at least) to actually stop, telling me to wait for it to cancel its transaction. The wait seems excessive...
Not sure about the "never doing anything after suspend" part. Maybe that is something we can look at.
Regarding CTRL-C not working, you are probably hitting https://github.com/projectatomic/rpm-ostree/issues/897. Where it's actually an underlying library that is taking control of the signal handling. It would be nice to get that fixed somehow.
On Tue, Jan 30, 2018, at 9:47 AM, Matthias Clasen wrote:
But rpm-ostree jigdo ♲📦 is going to take us a lot closer to a "full hybrid" like the Prius, where you can sort of ignore the electric side and treat it as just a car, if that makes sense.
It makes sense, as far as fluffy metaphors ever do. But I was looking more for concrete answers that we can put on a webpage _now_, not for promises of an eventual bright future...
I think about 80% of the problem here too is you dusted off a previous experimental build. Installing the ISO fresh means you don't need to set up remotes or worry about it - you just `rpm-ostree upgrade` and `rpm-ostree install` (until such time as F28, which is its own topic).
All this interest in atomic workstation made me dust off my vm.
While upgrading it, I ran into a number of questions that I couldn't find any answers for. This might be useful information to put on a new atomic workstation website.
Yep. Upgrading from a previous existing install of workstation might be problematic some of the baked in config may have been off. Hopefully people starting from the Fedora 27 ISO will have a smoother experience.
- How do I find out what I'm running ?
I guess the answer to this is rpm-ostree status,
Yep!
but what does it actually tell me ?
● atomicws:atomicws/fedora/x86_64/continuous Version: 26.447 (2018-01-29 04:58:49) BaseCommit: ba986d4649f08705185ba1ce7208e72d149b1e35314d112a86348cb1d61f6f52 LayeredPackages: powerline
It would be nice to explain this output a bit - I assume the first 'atomicws' is a repository name, and 'atomicws/fedora/x86_64/continuous' is a branch name. Version 26.447 may indicate that I am running some version of Fedora 26.
Correct. `atomicws` is the name of the ostree remote (like a git remote) and the ref (branch) you are following in that remote is `atomicws/fedora/x86_64/continuous`.
Unfortunately, I haven't really seen the gnome-software support in action yet, but I hope it shows this information as well.
probably not yet :(
- How do I get the latest updates ?
rpm-ostree upgrade is easy enough (once I've found it).
- How do I upgrade to a newer release ?
We'll publish guides on this for example when F28 Atomic Workstation is released, but it would be an `rpm-ostree rebase` command to make your system start following a different ref.
- How do I find out what branches are available to rebase to ?
ostree refs does work, but mostly as a user we should guide you enough so you don't have to muck around too much with that.
- Where is the repo configuration stored ?
/etc/ostree/remotes.d/
This is where I got stuck - I could not find any answers to these. Very frustrating, a normal user would have given up here.
Yep. A lot of this is related to you being on a pre-27 atomic workstation. And our docs aren't great
Eventually, Kalev told me to create a file in /etc/ostree/remotes.d/ with some content, and then I figured out to run
ostree remote refs fedora
to see the branches in the repo, and
rpm-ostree rebase fedora:fedora/27/x86_64/workstation
to upgrade to one of them. I blindly picked this branch, since I have no idea what the difference between
you chose the right one :)
fedora/27/x86_64/testing/workstation fedora/27/x86_64/updates/workstation fedora/27/x86_64/workstation
so the testing branch has content that includes rpms that are in the updates-testing fedora yum repository. The updates branch has content that includes the updates repo. The other branch right now just points to the updates branch. In Fedora Atomic Host we only release every 2 weeks, if we did the same thing for workstation then the `fedora/27/x86_64/workstation` branch would only get updated when we did the release (so not every day).
might be...
Also, I had to disable gpg verification, since I didn't know where to find the key for that repo.
This should help you: here is the ostree remote config if you installed from the ISO: ``` [dustymabe@localhost ~]$ cat /etc/ostree/remotes.d/fedora-workstation.conf [remote "fedora-workstation"] url=https://dl.fedoraproject.org/ostree/27/ gpg-verify=true gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-primary ```
We need to make the rpm-ostree plugin support distro-upgrades inside gnome-software. And also make this information available in some obvious place.
That would be great!
desktop@lists.fedoraproject.org
-
Colin Walters -
Dusty Mabe -
Dusty Mabe -
Matthias Clasen