-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Debian 9 runs apt update on startup, blocks user apt commands #2621
Comments
I caution of removing the timer. /lib/systemd/system/apt-daily.service runs /usr/lib/apt/apt.systemd.daily. I would not wonder if it does or will do in later releases of Debian other stuff than unattended upgrades (database stuff that was previously done using cron). When you Another option is to disable unattended-upgrades using apt.conf.d. See: |
When I disabled the timer, I assumed that apt could take care of any delayed housekeeping when it is called manually. This is 'traditional', I think, and would seem to be necessary; otherwise there are side-effects like having the Qubes template update procedure fail. The package description "unattended-upgrades" says it is for enabling full download and installation of packages... this sounds pretty specific, and I wonder if that would stop apt from running on boot (it could still do updates without download/upgrade?). Regardless, it seems you have already addressed this in Whonix. Best thing may be to just copy your conf file approach. |
What package pulls in `unattended-upgrades`?
Anyway, conf approach looks fine.
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Works for me. No more auto run of apt-get update after that package had been purged.
That. Or install the https://github.com/Whonix/pkg-manager-no-autoupdate package. |
This isn't a bug, and certainly not Qubes specific.
It's a recommended package from (at root) gnome-packagekit. Users chose to install it on the upgrade. @adrelanos suggests purging the package if it's been installed in error. Definitely this, rather than disabling the timer. @andrewdavidwong I'd suggest closing. |
This at very least needs to be documented for users who upgrade their
packages. Otherwise most users will run into having that package
installed and the issue described here.
Enabling automatic updates by default is a separate discussion. Imo not
an easy decision.
|
Changed to a documentation task. |
Suggestion: Move the new blurb about unattended-upgrades to |
I just discovered the problem remains in one of my templates if unattended-upgrades is not installed but
Another template has |
@tasket: Consider submitting a doc PR for that, if you think it appropriate. |
Update: Debian appears to have changed |
Debian stretch in default configuration calls apt-get update every 24h. And additionally, have automatic unattended security updates enabled. Generally it would be good thing on standalone system, but in AppVM which loose its rootfs changes after restart it is a waste of resources. Especially when it kicks in on multiple VMs simultaneously, while on battery (apt-daily.service have ConditionACPower=true, but VM don't have that information...). It would make some sense on TemplateVM/StandaloneVM, but then it kicks in just at VM startup. Which conflicts with starting the update manually then (by clicking "update VM" button in manager for example, or using salt). So, disable this feature completely. The actual solution is based on pkg-manager-no-autoupdate by @adrelanos. Fixes QubesOS/qubes-issues#2621
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
This has nothing to do with
|
On Mon, Mar 23, 2020 at 11:37:29AM -0700, Farid Cheraghi wrote:
This has nothing to do with `unattended-upgrades`. You need to remove `gnome-software` to stop this:
```
sudo apt remove gnome-software
```
And yet, disabling that service stopped the unwanted behaviour, whereas
gnome-software isnt installed in the debian-9 template and therefore
cant be responsible.
|
Qubes OS version (e.g.,
R3.2
):R3.2
Affected TemplateVMs (e.g.,
fedora-23
, if applicable):Debian 9 stretch
Expected behavior:
User can run updates immediately after starting template (or appVM)
Actual behavior:
Apt-related files are locked, and sometimes this takes more than 5 min to clear.
Steps to reproduce the behavior:
Start Debian 9 template and issue
sudo apt-get update
command.General notes:
Stretch has a new systemd unit called
apt-daily.timer
and this activatesapt-daily.service
on most boots. I thinksystemctl disable apt-daily.timer
is working (so far) to prevent activation.It seems in Qubes' case it would be a good idea to permanently disable this timer for templates.
The text was updated successfully, but these errors were encountered: