Re: Unattended Upgrades Ran Anyway.

, but from unit and scripts content my impression is that apt-daily-upgrade.service may apply security updates even when the unattended-upgrades package is not installed. Despite apt-daily-upgrade.timer is enabled out of the box, without unattended-upgrades, the service does nothing in de

Re: Unattended Upgrades Ran Anyway.

Dan Ritter wrote: > Stefan Monnier wrote: >> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having >> them run unexpectedly can be a real problem, so I tried to prevent >> unattended upgrades a few months ago. > > > I have always preferred the apti

Re: Unattended Upgrades Ran Anyway.

On Sun, 10 Dec 2023 17:27:39 -0500 Greg Wooledge wrote: > > > > Thanks. I will disable as well. > > Disable *what*? Disabling a .service unit which is triggered by a > timer event isn't going to stop it from running. Sorry. I had already stopped the apt-daily-upgrade.timer, which triggers t

Re: Unattended Upgrades Ran Anyway.

On Sun, Dec 10, 2023 at 02:10:43PM -0700, Charles Curley wrote: > On Sun, 10 Dec 2023 14:51:48 -0600 > David Wright wrote: > > > I think it might be worth googling and reading "three levels of off" > > (with the quotes). > > > > 1. You can stop a service. That simply terminates the running > >

Re: Unattended Upgrades Ran Anyway.

On Sun, 10 Dec 2023 14:51:48 -0600 David Wright wrote: > I think it might be worth googling and reading "three levels of off" > (with the quotes). > > 1. You can stop a service. That simply terminates the running > instance of the service and does little else. If due to some form > o

Re: Unattended Upgrades Ran Anyway.

Stefan Monnier wrote: > On my trusty Thinkpad X30, upgrades are sufficiently taxing that having > them run unexpectedly can be a real problem, so I tried to prevent > unattended upgrades a few months ago. I have always preferred the apticron package, which by default updates daily and

Re: Unattended Upgrades Ran Anyway.

On Sun 10 Dec 2023 at 13:39:50 (-0700), Charles Curley wrote: > On Sun, 10 Dec 2023 14:17:36 -0600 > David Wright wrote: > > > Why is the service loaded, enabled and enabled then? Don't you need > > to disable or mask it? Presumably it sits there, dead, all day > > normally, and pops up at an app

Re: Unattended Upgrades Ran Anyway.

On Sun, 10 Dec 2023 14:17:36 -0600 David Wright wrote: > Why is the service loaded, enabled and enabled then? Don't you need > to disable or mask it? Presumably it sits there, dead, all day > normally, and pops up at an appropriate time. As I understand things, start and stop are for immediate c

Re: Unattended Upgrades Ran Anyway.

gt; > Exactly how did you "shut down" unattended-upgrades? > > > > root@chaffee:/etc/dhcp# systemctl stop unattended-upgrades.service > root@chaffee:/etc/dhcp# systemctl status unattended-upgrades.service > ● unattended-upgrades.service - Unattended Upgrades Shutdown >

Re: Unattended Upgrades Ran Anyway.

On Sun, 10 Dec 2023 23:59:04 +0700 Max Nikulin wrote: > On 10/12/2023 22:49, Charles Curley wrote: > [...] > > systemctl status apt-daily-upgrade.timer > root@issola:~# systemctl status apt-daily-upgrade.timer ● apt-daily-upgrade.timer - Daily apt upgrade and clean activities Loaded: l

Re: Unattended Upgrades Ran Anyway.

On Sun, 10 Dec 2023 16:11:44 + Michael Kjörling <2695bd53d...@ewoof.net> wrote: > On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com > (Charles Curley): [...] > > Exactly how did you "shut down" unattended-upgrades? > root@chaffee:/etc/

Re: Unattended Upgrades Ran Anyway.

> I double checked this morning. All machines had unattended upgrades > shut off as of yesterday evening, well before the > unattended-uogrades ran. On my trusty Thinkpad X30, upgrades are sufficiently taxing that having them run unexpectedly can be a real problem, so I tried t

Re: Unattended Upgrades Ran Anyway.

On 10/12/2023 22:49, Charles Curley wrote: root@issola:/var# systemctl status unattended-upgrades.service systemctl status apt-daily-upgrade.timer

Re: Unattended Upgrades Ran Anyway.

On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com (Charles Curley): > Due to the recent traffic about the defective kernel in Bookworm > (12.3), I shut down unattended-upgrades on all my machines (Bookworm > and Bullseye). To my surprise, three of them ran unattended

Unattended Upgrades Ran Anyway.

Due to the recent traffic about the defective kernel in Bookworm (12.3), I shut down unattended-upgrades on all my machines (Bookworm and Bullseye). To my surprise, three of them ran unattended-upgrades anyway. One of them is Bullseye, so it was a harmless error. But still…. The two Bookworm

Re: Report a bug against which package - unattended-upgrades / apt / dpkg ??

David Wright wrote: > On Mon 21 Mar 2022 at 15:07:45 (+), Dr. Alex Sheppard wrote: > > On 21/03/2022 14:02, Dan Ritter wrote: > > > Dr. Alex Sheppard wrote: > > So, unless anyone can explain otherwise, I think there is a bug to > > report against unattended-u

Re: Report a bug against which package - unattended-upgrades / apt / dpkg ??

On Mon 21 Mar 2022 at 15:07:45 (+), Dr. Alex Sheppard wrote: > On 21/03/2022 14:02, Dan Ritter wrote: > > Dr. Alex Sheppard wrote: > > > > > >     Unattended upgrades ended up removing some of the packages it was was > > > going to upgrade ... bind9 being

Re: Report a bug against which package - unattended-upgrades / apt / dpkg ??

On 21/03/2022 14:02, Dan Ritter wrote: Dr. Alex Sheppard wrote: Hi,     Unattended upgrades ended up removing some of the packages it was was going to upgrade ... bind9 being one of them and thereby breaking DNS on a client's network.     Is this a bug in unattended upgrades, or a b

Re: Report a bug against which package - unattended-upgrades / apt / dpkg ??

Dr. Alex Sheppard wrote: > Hi, > >     Unattended upgrades ended up removing some of the packages it was was > going to upgrade ... bind9 being one of them and thereby breaking DNS on a > client's network. > >     Is this a bug in unattended upgrades, or a bug in

Report a bug against which package - unattended-upgrades / apt / dpkg ??

Hi,     Unattended upgrades ended up removing some of the packages it was was going to upgrade ... bind9 being one of them and thereby breaking DNS on a client's network.     Is this a bug in unattended upgrades, or a bug in apt or dpkg? Here is an extract from my unattended-upgrades.l

Re: Graphical session does not close until unattended-upgrades has applied all updates

Le 23/04/2021 à 21:07, Yvan Masson a écrit : Le 23/04/2021 à 20:18, didier gaumet a écrit : 1) Unattended-upgrade at shutdown and after Lightdm is stopped: Perhaps a solution would be to : - stop and disable the unattended-upgrade systemd service - edit the unattended-upgrades config

Re: Graphical session does not close until unattended-upgrades has applied all updates

Le 23/04/2021 à 20:18, didier gaumet a écrit : 1) Unattended-upgrade at shutdown and after Lightdm is stopped: Perhaps a solution would be to : - stop and disable the unattended-upgrade systemd service - edit the unattended-upgrades config file to setup the shutdown to false - write/enable

Re: Graphical session does not close until unattended-upgrades has applied all updates

1) Unattended-upgrade at shutdown and after Lightdm is stopped: Perhaps a solution would be to : - stop and disable the unattended-upgrade systemd service - edit the unattended-upgrades config file to setup the shutdown to false - write/enable/start your custom systemd service that runs /usr

Re: Graphical session does not close until unattended-upgrades has applied all updates

it is not already the case (when unattended-upgrades the A bit is missing there (cut/past and absent-minded poster): ..." systemd service is started after the LightDM systemd service is stopped), it is perhaps possible to modify the "... unattended-upgrades.service syste

Re: Graphical session does not close until unattended-upgrades has applied all updates

Le 23/04/2021 à 11:59, didier gaumet a écrit : I should check what I wrote before posting :-( [...] Disclaimer: I have never experimented myself whait I suggest "what" [...] As for Plymouth notifying about ugrades during shutdown, if it is not already the case (when unattended-up

Re: Graphical session does not close until unattended-upgrades has applied all updates

the unattended-upgrades.service systemd service by declaring that the lightdm service is to be stopped before this service is started would do. As for Plymouth notifying about ugrades during shutdown, if it is not already the case (when unattended-upgrades the unattended-upgrades.service

Graphical session does not close until unattended-upgrades has applied all updates

Hi list, I am preparing some Debian 11 desktops for a school (for when it will be the new stable). The setup is very simple: no root account, one partition, tasks desktop/Cinnamon/SSH. Unattended-upgrades is configured to install updates on shutdown (see 1): upgrading works properly, but is

Re: SOLVED: Re: How to add an origin to unattended upgrades?

On Mon, 19 Oct 2020 12:51:20 -0600 Charles Curley wrote: > On Fri, 16 Oct 2020 13:24:06 -0600 > Charles Curley wrote: > > > I have unattended upgrades running on a testbed laptop. I would like > > to add an origin to the list, but I don't think I am getting the

Re: SOLVED??: Re: How to add an origin to unattended upgrades?

On Tue, 20 Oct 2020 10:38:20 +0300 Andrei POPESCU wrote: > > -- > > // "o=Debian Backports,a=${distro_codename}-backports,l=Debian > > Backports"; "o=Vivaldi Technologies,a=stable,l=Official Vivaldi > > package repository"; }; > > -

Re: SOLVED??: Re: How to add an origin to unattended upgrades?

On Lu, 19 oct 20, 12:51:20, Charles Curley wrote: > > On further reflection, I looked at the sample entries for origins, and > realized that the line for Debian Backports in the Archive or Suite > section might be a better model to try. After commenting out my > original effort, I added: > >

SOLVED??: Re: How to add an origin to unattended upgrades?

On Fri, 16 Oct 2020 13:24:06 -0600 Charles Curley wrote: > I have unattended upgrades running on a testbed laptop. I would like > to add an origin to the list, but I don't think I am getting the entry > quite right. The origin is for vivaldi, which has its own repo outside >

Re: How to add an origin to unattended upgrades?

On Sun, 18 Oct 2020 13:29:26 +0300 Andrei POPESCU wrote: > This looks good to me. > > After looking through the bugs list for unattended-upgrades I would > suggest you check whether upgrading vivaldi-stable requires > installing new packages or package removals ('apt upgra

Re: How to add an origin to unattended upgrades?

.1929.45-1 100 > 100 /var/lib/dpkg/status > root@orca:~# > -- This looks good to me. After looking through the bugs list for unattended-upgrades I would suggest you check whether upgrading vivaldi-stable requires installing new packages or package

Re: How to add an origin to unattended upgrades?

On Sat, 17 Oct 2020 09:21:22 +0300 Andrei POPESCU wrote: > Please show also the output of 'apt policy vivaldi' (or whatever the > package name is). -- root@orca:~# apt policy vivaldi-stable vivaldi-stable: Installed: 3.1.1929.45-1 Candidate: 3

Re: How to add an origin to unattended upgrades?

On Vi, 16 oct 20, 13:24:06, Charles Curley wrote: > > -- > root@orca:~# apt-cache policy | grep -i vivaldi > 500 http://repo.vivaldi.com/stable/deb stable/main i386 Packages > release o=Vivaldi Technologies,a=stable,l=Official Vivaldi package

How to add an origin to unattended upgrades?

I have unattended upgrades running on a testbed laptop. I would like to add an origin to the list, but I don't think I am getting the entry quite right. The origin is for vivaldi, which has its own repo outside the Debian repos. I set things up according to https://wiki.debia

Re: Question on Unattended Upgrades

On 12.05.20 07:25, Keifer Bly wrote: Is there a way to configure it to automatically restart when a package that needs to be restarted is upgraded? Thx. Restarting might not be needed at all if applying some "live patching" mechanism. It might not be helpful for you, but I thought to mention i

Re: Question on Unattended Upgrades

Hi, 13 mai 2020 à 06:39 de keifer@gmail.com: > I am not backing this machine up to a physical drive, it is a VPS, so being > hosted in the cloud and all. We are not dealing with databases, but just > pushing traffic between nodes, etc. They strongly advise be running both the > most secure

Re: Question on Unattended Upgrades

On Wednesday 13 May 2020 03:53:36 l0f...@tuta.io wrote: > Hi, > > 13 mai 2020 à 06:39 de keifer@gmail.com: > > I am not backing this machine up to a physical drive, it is a VPS, > > so being hosted in the cloud and all. We are not dealing with > > databases, but just pushing traffic between no

Re: Question on Unattended Upgrades

ded? > >>>> > >>>> I think 'Unattended-Upgrade::Automatic-Reboot "true";' should do > >>>> it in /etc/apt/apt.conf.d/50unattended-upgrades. If I were you, I > >>>> would check /etc/apt/apt.conf.d/20auto-upgrades as well beca

Re: Question on Unattended Upgrades

o automatically restart when a > >>>>> package that needs to be restarted is upgraded? > >>>> > >>>> I think 'Unattended-Upgrade::Automatic-Reboot "true";' should do > >>>> it in /etc/apt/apt.conf.d/50unattended-upg

Re: Question on Unattended Upgrades

;true";' should do >>>> it in /etc/apt/apt.conf.d/50unattended-upgrades. If I were you, I >>>> would check /etc/apt/apt.conf.d/20auto-upgrades as well because >>>> those are the 2 most important configuration files for >>>> unattended-upgrades

Re: Question on Unattended Upgrades

upgrades I see the lines: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Unattended-Upgrade "1"; What I am doing is running a small web server via a Debian Linux VPS, which I am trying to use Unattended Upgrades to keep the software for this web server and he OS Kernel up

Re: Question on Unattended Upgrades

ption? > APT::Periodic::Unattended-Upgrade "1"; enables "apt upgrade" itself.More details on: * https://wiki.debian.org/UnattendedUpgrades. * man unattended-upgrades * /usr/share/doc/unattended-upgrades/README.md.gz Best regards, l0f4r0

Re: Question on Unattended Upgrades

s > > apt::periodic::unattended-upgrade "1"; > > > > Here is my 50-unattended-upgrades > > […] > > You appear to have removed the line > > APT::Periodic::Update-Package-Lists "1"; > > from 20-auto-upgrades. Is something else responsible for

Re: Question on Unattended Upgrades

uot;1"; > > Here is my 50-unattended-upgrades > […] You appear to have removed the line APT::Periodic::Update-Package-Lists "1"; from 20-auto-upgrades. Is something else responsible for updating them? Also, I assume that there's no 20auto-upgrades-disabled pre

Re: Question on Unattended Upgrades

To get back to the topic -- I have unattended updates set supposedly, but they do nothing. Here are the relevant files from my apt.conf.d directory 20-auto-upgrades apt::periodic::unattended-upgrade "1"; Here is my 50-unattended-upgrades // Unattended-Upgrade::Origins-Pattern cont

Re: Question on Unattended Upgrades

On Tue 12 May 2020 at 07:48:49 (-0400), rhkra...@gmail.com wrote: > On Tuesday, May 12, 2020 02:22:13 AM Keifer Bly wrote: > > Is there a way to configure it to automatically restart when a package that > > needs to be restarted is upgraded? Thx. > > If there is a comand named "needrestart" (I don

Re: Question on Unattended Upgrades

nattended-Upgrade::Automatic-Reboot "true";' should do > > > > it in /etc/apt/apt.conf.d/50unattended-upgrades. If I were you, I > > > > would check /etc/apt/apt.conf.d/20auto-upgrades as well because > > > > those are the 2 most important configuratio

Re: Question on Unattended Upgrades

-upgrades. If I were you, I > > > would check /etc/apt/apt.conf.d/20auto-upgrades as well because > > > those are the 2 most important configuration files for > > > unattended-upgrades. > > > > > > Best regards, > > > l0f4r0 > > >

Re: Question on Unattended Upgrades

age that needs to be restarted is upgraded? > > > > I think 'Unattended-Upgrade::Automatic-Reboot "true";' should do it > > in /etc/apt/apt.conf.d/50unattended-upgrades. If I were you, I would > > check /etc/apt/apt.conf.d/20auto-upgrades as well

Re: Question on Unattended Upgrades

Keifer Bly writes: > I am wondering, does the OS need to be restarted for the upgrade to > take effect? Only if the kernel was upgraded. > What file would I check to make sure the unattended upgrades is > working and the packages it updated? >From the man page: All operation

Re: Question on Unattended Upgrades

Hi. On Tue, May 12, 2020 at 07:48:49AM -0400, rhkra...@gmail.com wrote: > On Tuesday, May 12, 2020 02:22:13 AM Keifer Bly wrote: > > Is there a way to configure it to automatically restart when a package that > > needs to be restarted is upgraded? Thx. > > If there is a comand named "need

Re: Question on Unattended Upgrades

On Tue, May 12, 2020 at 07:48:49AM -0400, rhkra...@gmail.com wrote: > On Tuesday, May 12, 2020 02:22:13 AM Keifer Bly wrote: > > Is there a way to configure it to automatically restart when a package that > > needs to be restarted is upgraded? Thx. > > If there is a comand named "needrestart" (I d

Re: Question on Unattended Upgrades

On Tuesday, May 12, 2020 02:22:13 AM Keifer Bly wrote: > Is there a way to configure it to automatically restart when a package that > needs to be restarted is upgraded? Thx. If there is a comand named "needrestart" (I don't see it on my Wheezy system), then presumably a (bash?) script could be w

Re: Question on Unattended Upgrades

Hi, 12 mai 2020 à 12:03 de ghesk...@shentel.net: > I can see a major disaster in the making, what if that reboot was > commanded in the middle of your nightly backup run, leaving your backup > program with a totally bogus database it cannot recover from? > > Frankly the update shouldn't be allo

Re: Question on Unattended Upgrades

omatic-Reboot "true";' should do it > in /etc/apt/apt.conf.d/50unattended-upgrades. If I were you, I would > check /etc/apt/apt.conf.d/20auto-upgrades as well because those are > the 2 most important configuration files for unattended-upgrades. > > Best regards, &g

Re: Question on Unattended Upgrades

ended-upgrades. If I were you, I would check /etc/apt/apt.conf.d/20auto-upgrades as well because those are the 2 most important configuration files for unattended-upgrades. Best regards, l0f4r0

Re: Question on Unattended Upgrades

Is there a way to configure it to automatically restart when a package that needs to be restarted is upgraded? Thx. --Keifer On Mon, May 11, 2020 at 11:14 PM Charles Curley < charlescur...@charlescurley.com> wrote: > On Tue, 12 May 2020 11:54:48 +0700 > Victor Sudakov wrote: > > > > Does the OS

Re: Question on Unattended Upgrades

On Tue, 12 May 2020 11:54:48 +0700 Victor Sudakov wrote: > > Does the OS need to be restarted for this to take effect? Thx. > > That depends. If the kernel has been upgraded, then probably yes. > > If some daemon has been upgraded, it could be enough to restart the > daemon (or does apt rest

Re: Re: Question on Unattended Upgrades

Is there a way to configure it to automatically restart when a package that needs to be restarted is upgraded? Thx. --Keifer Virus-free. www.avast.com

Re: Re: Question on Unattended Upgrades

Keifer Bly wrote: >So upon doing that, I am seeing this: Please don't use graphics where you could have shown plain text. Not everyone here is using a graphical mail client. > >Does this mean it is updating these automatically? Look for lines matching "Commandline: /usr/bin/unattended-

Re: Question on Unattended Upgrades

Keifer Bly wrote: > What file would > I check to make sure the unattended upgrades is working and the > packages it updated? Thanks. I look for lines matching "Commandline: /usr/bin/unattended-upgrade" in /var/log/apt/history.log, but there may be a better approach. -- Vi

Question on Unattended Upgrades

Hello, So I am using unattended upgrades for my Debian Linux OS, as well as a certain package I added to be updated by it. I am wondering, does the OS need to be restarted for the upgrade to take effect? What file would I check to make sure the unattended upgrades is working and the packages it

Re: unattended-upgrades does not install upgrades on shutdown

On Tue, 15 Oct 2019 17:03:19 +1100 Keith Bainbridge wrote: > Also, there is a process to get one PC to download the updates, and > share that /var/cache/apt/archives/ to your other PCs You might look into apt-cacher or apt-cacher-ng for that. -- Does anybody read signatures any more? https:

Re: unattended-upgrades does not install upgrades on shutdown

Le 15/10/2019 à 14:10, Curt a écrit : On 2019-10-15, Yvan Masson wrote: I am currently using a VM with snapshots to try to find the culprit, I will let you know. I could not find the culprit so I reported the bug: https://github.com/mvo5/unattended-upgrades/issues/229 There's this

Re: unattended-upgrades does not install upgrades on shutdown

On 2019-10-15, Yvan Masson wrote: >> >> I am currently using a VM with snapshots to try to find the culprit, I >> will let you know. > > I could not find the culprit so I reported the bug: > https://github.com/mvo5/unattended-upgrades/issues/229 >>> There&#x

Re: unattended-upgrades does not install upgrades on shutdown

the time for unattended-upgrades to calculate what should be upgraded. Also, unattended-upgrades download packages before the computer shuts down. I am currently using a VM with snapshots to try to find the culprit, I will let you know. I could not find the culprit so I reported the bu

Re: unattended-upgrades does not install upgrades on shutdown

?? There was a response suggesting getting cron to run something like this: # apt update  && # apt -dy full-upgrade Reminded me I did that as well. I believe the timeout in this case is never reached: computer goes off after 1 or 2 minutes, just the time for unattended-upgrades to calcula

Re: unattended-upgrades does not install upgrades on shutdown

On 15/10/19 11:31 am, Keith Bainbridge wrote: How to prevent a repeat is the real question. My only suggestion is extend the time-out, but how long.  Maybe run manual upgrades on one machine every day, before shutting down the others?? There was a response suggesting getting cron to run som

Re: unattended-upgrades does not install upgrades on shutdown

On Tue, 15 Oct 2019 11:31:22 +1100 Keith Bainbridge wrote: > It was intuition rather than any knowledge I had - beyond the fact > that sometimes upgrade takes longer than normal. > > How to prevent a repeat is the real question. Upgrades and updates often require fetching across the network, wh

Re: unattended-upgrades does not install upgrades on shutdown

On 14/10/19 7:42 pm, Yvan Masson wrote: You were right Keith: after applying some updates manually, remaining updates are properly installed with unattended-upgrade… Now I need to understand what was blocking. It was intuition rather than any knowledge I had - beyond the fact that sometim

Re: unattended-upgrades does not install upgrades on shutdown

12/10/2019 à 18:45, Yvan Masson a écrit : Hi list, I configured some Buster desktops in a school to upgrade automatically on shutdown via unattended-upgrades. I am almost sure it worked at first but it does not anymore. I would really appreciate any suggestion as I already spent a few hours on

Re: unattended-upgrades does not install upgrades on shutdown

, I configured some Buster desktops in a school to upgrade automatically on shutdown via unattended-upgrades. I am almost sure it worked at first but it does not anymore. I would really appreciate any suggestion as I already spent a few hours on this issue without any result. Symptoms are

Re: unattended-upgrades does not install upgrades on shutdown

school to upgrade automatically on shutdown via unattended-upgrades. I am almost sure it worked at first but it does not anymore. I would really appreciate any suggestion as I already spent a few hours on this issue without any result. Symptoms are: shutdown is long (more than 2 minutes

unattended-upgrades does not install upgrades on shutdown

Hi list, I configured some Buster desktops in a school to upgrade automatically on shutdown via unattended-upgrades. I am almost sure it worked at first but it does not anymore. I would really appreciate any suggestion as I already spent a few hours on this issue without any result

Re: Differences between apt-listchanges/unattended-upgrades/apticron/cron-apt

cron-apt (still with apt-listchanges) can do all of this but the configuration seems more complex/tricky. Is that all correct please? Best regards, l0f4r0 10 sept. 2019 à 19:05 de l0f...@tuta.io: > Hello, > > Can somebody explain to me the differences between apt-listchanges, > unattend

Re: Differences between apt-listchanges/unattended-upgrades/apticron/cron-apt

l0f...@tuta.io wrote: > Hello, > > Can somebody explain to me the differences between apt-listchanges, > unattended-upgrades, apticron and cron-apt please? > > I have the following feeling: > * apt-listchanges: its main purpose is to indicate what's new between >

Re: Differences between apt-listchanges/unattended-upgrades/apticron/cron-apt

Quoting l0f...@tuta.io (2019-09-10 19:05:39) > Can somebody explain to me the differences between apt-listchanges, > unattended-upgrades, apticron and cron-apt please? > > I have the following feeling: > * apt-listchanges: its main purpose is to indicate what's new between

Differences between apt-listchanges/unattended-upgrades/apticron/cron-apt

Hello, Can somebody explain to me the differences between apt-listchanges, unattended-upgrades, apticron and cron-apt please? I have the following feeling: * apt-listchanges: its main purpose is to indicate what's new between different packages versions. So it's handy to lear

Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file

Hi, looks like the culprit is a /etc/cron.daily/do-agent cron-job which executes the /opt/digitalocean/do-agent/scripts/update.sh script which includes following if statement: if command -v apt-get 2&>/dev/null; then apt-get -qq update -o Dir::Etc::sourcelist="sources.list

Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file

> I did some further debugging and it is the > /usr/lib/apt/apt.systemd.daily script executed by apt-daily systemd > service unit which updates the package index from the sources: I configured cron with one minute interval to log the output of "apt policy" with a timestamp into a log file in order

Re: unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file

> Looks like the "apt update" or equivalent ran by unattended-upgrades > ignored the /etc/apt/sources.list file and used only > /etc/apt/sources.list.d/digitalocean-agent.list as a source for > repositories. > What might cause this behavior? I did some further debugging a

unattended-upgrades downloaded package information only from the sources in sources.list.d directory ignoring sources.list file

Hi, in order to test unattended-upgrades I downgraded yesterday(4.06) packages iceweasel, qemu-utils and thunderbird: # # "apt list --upgradable" command below was executed on 4.06 # apt list --upgradable Listing... Done iceweasel/stable 60.7.0esr-1~deb9u1 all [upgradable from: 5

Re: Unattended Upgrades question

it. We all make our own choices, of course. 1) Not everyone likes unattended upgrades. 2) If simply disabled, it can always be accidentally reactivated by an upgrade (probably not by an unattended one, though). 3) If it's _never_ going to be used, why keep it? -- Regards _ /

Re: Unattended Upgrades question

swer is 'yes': which would be the best/proper way to do >>>>> it? >>>> >>>> apt purge unattended upgrades >>> >> >> I'll never  understand why being so drastic is a good idea when you can >> simply disable it: >> &

Re: Unattended Upgrades question

likcoras composed on 2018-10-16 15:35 (UTC+0900): > john doe wrote: >> I'll never understand why being so drastic is a good idea when you can >> simply disable it: >> https://wiki.debian.org/UnattendedUpgrades >> "Below is an example /etc/apt/apt.conf.d/02periodic: >> // Control parameters for

Re: Unattended Upgrades question

On 10/16/18 2:42 PM, john doe wrote: On 10/16/2018 7:23 AM, Tixy wrote: On Mon, 2018-10-15 at 21:54 +0100, Brian wrote: On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote: 2. If the answer is 'yes': which would be the best/proper way to do it? apt purge unattended upgrade

Re: Unattended Upgrades question

On 10/16/2018 7:23 AM, Tixy wrote: > On Mon, 2018-10-15 at 21:54 +0100, Brian wrote: >> On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote: >> >>> Hi, two doubts: >>> >>> 1. Is it OK to disable/remove Unattended Upgrades on Debian >>>

Re: Unattended Upgrades question

On Mon, 2018-10-15 at 21:54 +0100, Brian wrote: > On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote: > > > Hi, two doubts: > > > > 1. Is it OK to disable/remove Unattended Upgrades on Debian > > testing? > > Of course it is; if that is what you w

Re: Unattended Upgrades question

On 16/10/2018 09:45, rv riveravaldez wrote: Hi, two doubts: 1. Is it OK to disable/remove Unattended Upgrades on Debian testing? 2. If the answer is 'yes': which would be the best/proper way to do it? Thanks a lot! I use systemctl to mask all the apt-daily units: systemctl mask

Re: Unattended Upgrades question

On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote: > Hi, two doubts: > > 1. Is it OK to disable/remove Unattended Upgrades on Debian testing? Of course it is; if that is what you want. > 2. If the answer is 'yes': which would be the best/proper way to do it?

Unattended Upgrades question

Hi, two doubts: 1. Is it OK to disable/remove Unattended Upgrades on Debian testing? 2. If the answer is 'yes': which would be the best/proper way to do it? Thanks a lot!

Unattended upgrades - feedback

Trying to install Unattended upgrades for Debian Stable including contrib and non-free packages on a friends computer. Also testing main packages (papirus icon set, testing is downpinned). Not sure if this is working. // "o=Debian,a=stable"; // "o=Debian,a=stable-updates"; //

Re: unattended upgrades does not do anything

On Tuesday 18 April 2017 15:55:25 Jonathan Dowland wrote: > If you Lisi revisit this and it doesn't work, I could try to help. Thanks, Jonathan. I may therefore revisit it later this week! :-) Lisi

Re: unattended upgrades does not do anything

I've just had a look, and I didn't do anything particularly special: I installed unattended-upgrades, ran dpkg-reconfigure -plow unattended-upgrades which created the necessary file in /etc/apt/apt.conf.d, and it is working. However, the default settings only do security updates; I

Re: unattended upgrades does not do anything

er wrote: > >>>> I am going to have a go at getting unattended-upgrades to work > >>>> sometime in the next few days, I will post back what my results, even > >>>> if the only thing that results is sympathy for your situation and a > >>>>

Re: unattended upgrades does not do anything

On Wednesday 05 April 2017 20:59:02 Tom Dial wrote: > On 04/05/2017 10:22 AM, Lisi Reisz wrote: > > On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote: > >> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote: > >>> I am going to have a go at getti

Re: unattended upgrades does not do anything

Le 04/05/17 à 21:59, Tom Dial a écrit : > > > On 04/05/2017 10:22 AM, Lisi Reisz wrote: >> On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote: >>> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote: >>>> I am going to have a go at getting

Re: Re: unattended upgrades does not do anything

On 04/05/2017 10:22 AM, Lisi Reisz wrote: > On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote: >> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote: >>> I am going to have a go at getting unattended-upgrades to work sometime >>> in the next few day

  1   2   >