You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2024. It is now read-only.
I've noticed that you're "setting UMASK to 0022 for the script to avoid APT errors" on line 1418 of the script. Can you please elaborate on the relation between the two? Is this how you deal with packagekitd locking the file /var/lib/apt/lists/lock during apt updates? Why not to disable the apt-daily*** services and then re-enable them when necessary instead?
I'm asking because I'm working on a similar but less sophisticated script myself for Pop!_OS and currently stuck with an apt problem caused by packagekitd, as I described above. To solve it, I simply stop the daemon, which is re-started by apt during the update anyway.
Thank you!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Good day,
I've noticed that you're "setting UMASK to 0022 for the script to avoid APT errors" on line 1418 of the script. Can you please elaborate on the relation between the two? Is this how you deal with
packagekitd
locking the file/var/lib/apt/lists/lock
duringapt
updates? Why not to disable theapt-daily***
services and then re-enable them when necessary instead?I'm asking because I'm working on a similar but less sophisticated script myself for Pop!_OS and currently stuck with an
apt
problem caused by packagekitd, as I described above. To solve it, I simply stop the daemon, which is re-started byapt
during the update anyway.Thank you!
The text was updated successfully, but these errors were encountered: