cockpit-project / cockpit-ostree Goto Github PK

This came up during the review of #5599
The current of the dialog uses inline editing, and this has two big drawbacks:

• It becomes very mode-heavy. There is the regular mode, where you can switch remotes, and the edit mode, where you edit an individual remote.
• The dialog will change a lot in size when you expand individual items, moving the Switch branch button around.

Garrett said he was interested in working on this, so assigning him to it.

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

I have a machine with Cockpit and Fedora IoT installed.

Because of this issue cockpit-project/cockpit#12932, I cannot sync my account. So I have to input my password every time to login.

I installed cockpit-ostree with rpm-ostree install cockpit-ostree. The version installed is

[root@fedora-iot-3 ~]# rpm -qa cockpit-ostree
cockpit-ostree-180-1.fc31.noarch

After doing an rpm-ostree update through the Software Update tabs (with the nice UI provided by this project), the machine rebooted automatically. And the tab was displaying a "Machine is restarting" message. Once the machine restarted, the tab tried to log in, without success, and keep trying forever. I assume that it kept trying an invalid credential.

To get cockpit to show the login window again, I had to close that tab, wait some time, and open the tab again. Then I can do my normal password input flow.

Nice project!

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Sporadically, the "Operating System Updates" page under "Software Update" tab fails to load, showing a "PackageKit is not installed" error (apparently, a fall-back to the default Software Updates provider)

The Firefox console shows the following message

PackageKit went away from D-Bus - updates.js:43:98887
loading available updates failed: {"problem":"not-found","name":null,"message":"not-found"} - updates.js:43:126634

Not sure how to capture host logs for the web ui. I could provide them if you tell me how.

ostree ui appears after some reloads

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

The dropdown should be filtered to the compatible architectures only.

It's probably correct to show only the currently booted arch, as ostrees don't have 32-bit support typically (even though it should be possible).

Here's a screenshot (it's so huge it flows off the page, which is another problem):

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Background

I'm using cockpit-157 with atomic 1.20.1. Using the ostree "hotfix" capability renders the cockpit Software Updates page useless. If you're on a hotfix deployment, then the Software Updates page will show the deployment that your hotfix is based off of twice, without any option to rollback. There is also no indication on the Software Updates page that you are on a hotfix deployment.

Proposed Capability

It would be very useful to me if, when you were on a hotfix, the Software Updates page would show an indication that you are currently on a hotfix and provide the ability to rollback the hotfix. Then, from there, you could continue utilizing the normal functionality of the updates page without the hotfix complication.

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

Cockpit-ostree is out of date with the look of Cockpit. It needs the latest version of the PF3 overrides (to look like PF4) and the new RedHat* fonts (instead of Overpass).

Check for any outstanding update of point version of any outstanding NPM package dependency

• npm-update

We are in the process of a fundamental rework to rpm-ostree to add rojig mode ♲📦.

Since the current ostree.js pkg does things like parse refspecs, it's going to have to learn about this. We're still debating the design on the DBus side though.

It'd actually be very useful to think about how this looks and feels on the Cockpit side. Note this also strongly intersects with our push for automatic updates 🆕⌚️.

One thing I want to specifically highlight is this subthread.

Basically the analogies we're currently building are:

• ostree remote = rpm-md (yum) repo
• ostree refspec = jigdoRPM package name + (enabled repo state, just like packages)
• ostree version = jigdoRPM version

For example, after jigdo there's no separate fedora/27/x86_64/atomic-host and fedora/27/x86_64/updates-testing/atomic-host. A bit like traditional, you'd rpm-ostree rebase --repo=updates-testing which would be short for going from fedora:fedora-atomic-host to fedora-updates-testing:fedora-atomic-host.