Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli/upgrade: Initial support for offline upgrades #47

Closed
wants to merge 1 commit into from

Conversation

joebonrichie
Copy link
Contributor

@Justinzobel
Copy link
Contributor

Is this ready for testing?

@joebonrichie joebonrichie force-pushed the offline-updates branch 2 times, most recently from 3f3b00c to 901c7a1 Compare March 28, 2024 19:20
@Justinzobel
Copy link
Contributor

Not listed in eopkg help ?

# 4. System reboots and /system-update file is removed

# a bit of a hard coded safety hack here
if not os.path.exists('/usr/lib/systemd/system/system-update.target.wants/eopkg-offline-update.service'):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be checking for the normal service file, not the symlink?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or rather, both. As both should always exist on the system and the system-update.target.wants is only executed when offline updates are detected by the /system-update symlink?

@Justinzobel
Copy link
Contributor

Sweet, got the offline update to work on my test laptop, very nice! It would also be nice to just get it to either A) display text showing eopkg output or B) show some sort of progress indicator and info that updates are in progress, please wait, etc.

I think we should probably also log all output from the upgrade attempt somewhere on the disk so that if an offline upgrade fails, we can direct the user to a log file so we can analyze it.

@Justinzobel
Copy link
Contributor

Justinzobel commented Apr 1, 2024

Oh interesting, this did the updates before rebooting... 🤔

I pulled the latest commits and did it on my test laptop and I ran the updates, but it didn't reboot before doing the updates, it just appears to have dropped to a TTY, done the updates and then rebooted.

Edit: Though it does show the text now which is good, which is why I now know that it does the updates before instead of after rebooting.

@ermo ermo deleted the branch master June 12, 2024 17:38
@ermo ermo closed this Jun 12, 2024
@Justinzobel
Copy link
Contributor

Is this being abandoned?

@EbonJaeger
Copy link
Member

I think some of the branches have been renamed, so the PR has to target one of the new ones. I don't know if that can be done without opening a new PR.

@Justinzobel
Copy link
Contributor

Ah, OK. Good to know it's not abandoned. It's an excellent feature to avoid issues when users do updates and do not reboot.

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.

Offline Updates
4 participants