Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179654 > unrolled thread

unattended upgrades does not do anything

Back to article view | Back to linux.debian.user

Contents

  unattended upgrades does not do anything Gregor Zattler <telegraph@gmx.net> - 2017-03-31 17:40 +0200
    Re: unattended upgrades does not do anything Gregor Zattler <telegraph@gmx.net> - 2017-04-01 18:10 +0200
      Re: unattended upgrades does not do anything Mark Fletcher <mark27q1@gmail.com> - 2017-04-03 14:10 +0200
        Re: unattended upgrades does not do anything Gregor Zattler <telegraph@gmx.net> - 2017-04-04 21:40 +0200
          Re: unattended upgrades does not do anything Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-05 02:30 +0200
            Re: unattended upgrades does not do anything Mark Fletcher <mark27q1@gmail.com> - 2017-04-05 15:30 +0200
              Re: unattended upgrades does not do anything Jonathan Dowland <jmtd@debian.org> - 2017-04-05 16:50 +0200
                Re: unattended upgrades does not do anything Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-05 18:30 +0200
                  Re: Re: unattended upgrades does not do anything Tom Dial <tddial@comcast.net> - 2017-04-05 22:30 +0200
                    Re: unattended upgrades does not do anything Erwan David <erwan@rail.eu.org> - 2017-04-05 22:30 +0200
                      Re: unattended upgrades does not do anything Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-06 00:40 +0200
                    Re: unattended upgrades does not do anything Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-06 00:40 +0200
                  Re: unattended upgrades does not do anything Jonathan Dowland <jmtd@debian.org> - 2017-04-18 17:00 +0200
                    Re: unattended upgrades does not do anything Lisi Reisz <lisi.reisz@gmail.com> - 2017-04-19 16:10 +0200

#179654 — unattended upgrades does not do anything

Dear fellow debian users,

this is about a debian stable (=jessie) system and it does not
upgrade unattended and I have no clue how to debug this:

It's configured for jessie repositories:

# egrep -v "(^[[:space:]]*[#;\\])|^[[:space:]]*$" sources.list
deb http://ftp.de.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb http://ftp.de.debian.org/debian/ jessie-updates main


unattended-upgrades is installed:
# dpkg -l unattended-upgrades |grep ii
ii  unattended-upgrades 0.83.3.2+deb8u1 all          automatic installation of security upgrades


To me the apt config files look fine:

# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/02periodic
Dir "/";
Dir::Cache "var/cache/apt/";
Dir::Cache::Archives "archives/";
APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::Download-Upgradeable-Packages-Debdelta "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::Verbose "2";

# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/20auto-upgrades
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

For some reasons there is obviously some dublification but I
don't think this is a problem.

I don't really know what the Origins-Pattern should look like but
I cannot remember to have messed with them:

# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
};
Unattended-Upgrade::Package-Blacklist {
};
        

Cron is installed...
# dpkg -l cron|grep ii
ii  cron           3.0pl1-127+deb8u1 i386         process scheduling daemon


... and running:


# ps fax|grep "[c]ron"
 1499 ?        Ss     0:02 /usr/sbin/cron -f



to me the basic configuration looks fine:

# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/cron
READ_ENV="yes"
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/anacron
ANACRON_RUN_ON_BATTERY_POWER=no


and the system is on corded power:
# acpi -a
Adapter 0: on-line




there are cron configuration files for apt:
# ls -l /etc/cron.daily/apt*
-rwxr-xr-x 1 root root 15333 Mär  2  2016 /etc/cron.daily/apt
-rwxr-xr-x 1 root root 15335 Aug 31  2015 /etc/cron.daily/apt~
-rwxr-xr-x 1 root root 15290 Feb 16  2015 /etc/cron.daily/apt.dpkg-old
-rwxr-xr-x 1 root root   314 Nov  5  2012 /etc/cron.daily/aptitude


The only change to the apt config file is:

# diff -Nur /etc/cron.daily/apt~ /etc/cron.daily/apt
--- /etc/cron.daily/apt~        2015-08-31 15:51:57.063709255 +0200
+++ /etc/cron.daily/apt 2016-03-02 10:04:25.595379714 +0100
@@ -282,7 +282,7 @@
# (some code taken from cron-apt, thanks)
random_sleep()
{
-    RandomSleep=1800
+    RandomSleep=18
eval $(apt-config shell RandomSleep APT::Periodic::RandomSleep)
if [ $RandomSleep -eq 0 ]; then
return


... because this maschine used to be up only for round about an
hour a day, but this is not true any more, the system is now up
long enough for it to caught some security upgrade:
# uptime
 17:25:41 up 12 days, 22:06,  3 users,  load average: 0,00, 0,02, 0,00
 


but there is not much of an activity lately:

# ls -Altr /var/log/unattended-upgrades/|tail
-rw-r--r-- 1 root root  191 Jul 27  2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log.1.gz
-rw-r--r-- 1 root root  384 Jul 29  2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log.1.gz
-rw-r--r-- 1 root root  995 Aug  1  2015 unattended-upgrades.log.1.gz
-rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-08_19:46:46.479193.log
-rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log
-rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log
-rw-r--r-- 1 root root 1058 Aug  4  2015 unattended-upgrades-dpkg_2015-08-04_20:25:14.411794.log
-rw-r--r-- 1 root root 1418 Aug  7  2015 unattended-upgrades-dpkg_2015-08-07_11:27:50.855330.log
-rw-r--r-- 1 root root  540 Aug 19  2015 unattended-upgrades-dpkg_2015-08-19_10:53:36.820176.log
-rw-r--r-- 1 root root 9056 Mär  2  2016 unattended-upgrades.log


Does anybody have an idea how to investigate this and who to
enable unattended upgrades?

Thanks, Gregor

[toc] | [next] | [standalone]

#179688

Hi Gregor,

one more detail about the configuration of said system (see below/between):

Any ideas how to proceed?

Ciao; Gregor 


* Gregor Zattler <telegraph@gmx.net> [2017-03-31; 17:34]:
> Dear fellow debian users,
>
> this is about a debian stable (=jessie) system and it does not
> upgrade unattended and I have no clue how to debug this:
>
> It's configured for jessie repositories:
>
> # egrep -v "(^[[:space:]]*[#;\\])|^[[:space:]]*$" sources.list
> deb http://ftp.de.debian.org/debian/ jessie main
> deb http://security.debian.org/ jessie/updates main
> deb http://ftp.de.debian.org/debian/ jessie-updates main
>
>
> unattended-upgrades is installed:
> # dpkg -l unattended-upgrades |grep ii
> ii  unattended-upgrades 0.83.3.2+deb8u1 all          automatic installation of security upgrades
>
>
> To me the apt config files look fine:
>
> # egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/02periodic
> Dir "/";
> Dir::Cache "var/cache/apt/";
> Dir::Cache::Archives "archives/";
> APT::Periodic::Enable "1";
> APT::Periodic::Update-Package-Lists "1";
> APT::Periodic::Download-Upgradeable-Packages "1";
> APT::Periodic::Download-Upgradeable-Packages-Debdelta "1";
> APT::Periodic::Unattended-Upgrade "1";
> APT::Periodic::Verbose "2";
>
> # egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/20auto-upgrades
> APT::Periodic::Update-Package-Lists "1";
> APT::Periodic::Unattended-Upgrade "1";
>
> For some reasons there is obviously some dublification but I
> don't think this is a problem.
>
> I don't really know what the Origins-Pattern should look like but
> I cannot remember to have messed with them:
>
> # egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/50unattended-upgrades
> Unattended-Upgrade::Origins-Pattern {
> "origin=Debian,codename=${distro_codename},label=Debian-Security";
> };
> Unattended-Upgrade::Package-Blacklist {
> };

I now checked for the origin, to me it seems OK, but
unattended-upgrade does still nothing:
# unattended-upgrades -v --dry-run
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: ['origin=Debian,codename=jessie,label=Debian-Security']
No packages found that can be upgraded unattended
root@shi:/etc/default# apt-cache policy | grep -v Translat
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.de.debian.org/debian/ jessie-updates/main i386 Packages
release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main
origin ftp.de.debian.org
500 http://security.debian.org/ jessie/updates/main i386 Packages
release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main
origin security.debian.org
500 http://ftp.de.debian.org/debian/ jessie/main i386 Packages
release v=8.7,o=Debian,a=stable,n=jessie,l=Debian,c=main
origin ftp.de.debian.org
Pinned packages:






>         
>
> Cron is installed...
> # dpkg -l cron|grep ii
> ii  cron           3.0pl1-127+deb8u1 i386         process scheduling daemon
>
>
> ... and running:
>
>
> # ps fax|grep "[c]ron"
>  1499 ?        Ss     0:02 /usr/sbin/cron -f
>
>
>
> to me the basic configuration looks fine:
>
> # egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/cron
> READ_ENV="yes"
> # egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/anacron
> ANACRON_RUN_ON_BATTERY_POWER=no
>
>
> and the system is on corded power:
> # acpi -a
> Adapter 0: on-line
>
>
>
>
> there are cron configuration files for apt:
> # ls -l /etc/cron.daily/apt*
> -rwxr-xr-x 1 root root 15333 Mär  2  2016 /etc/cron.daily/apt
> -rwxr-xr-x 1 root root 15335 Aug 31  2015 /etc/cron.daily/apt~
> -rwxr-xr-x 1 root root 15290 Feb 16  2015 /etc/cron.daily/apt.dpkg-old
> -rwxr-xr-x 1 root root   314 Nov  5  2012 /etc/cron.daily/aptitude
>
>
> The only change to the apt config file is:
>
> # diff -Nur /etc/cron.daily/apt~ /etc/cron.daily/apt
> --- /etc/cron.daily/apt~        2015-08-31 15:51:57.063709255 +0200
> +++ /etc/cron.daily/apt 2016-03-02 10:04:25.595379714 +0100
> @@ -282,7 +282,7 @@
> # (some code taken from cron-apt, thanks)
> random_sleep()
> {
> -    RandomSleep=1800
> +    RandomSleep=18
> eval $(apt-config shell RandomSleep APT::Periodic::RandomSleep)
> if [ $RandomSleep -eq 0 ]; then
> return
>
>
> ... because this maschine used to be up only for round about an
> hour a day, but this is not true any more, the system is now up
> long enough for it to caught some security upgrade:
> # uptime
>  17:25:41 up 12 days, 22:06,  3 users,  load average: 0,00, 0,02, 0,00
>  
>
>
> but there is not much of an activity lately:
>
> # ls -Altr /var/log/unattended-upgrades/|tail
> -rw-r--r-- 1 root root  191 Jul 27  2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log.1.gz
> -rw-r--r-- 1 root root  384 Jul 29  2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log.1.gz
> -rw-r--r-- 1 root root  995 Aug  1  2015 unattended-upgrades.log.1.gz
> -rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-08_19:46:46.479193.log
> -rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log
> -rw-r--r-- 1 root root    0 Aug  1  2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log
> -rw-r--r-- 1 root root 1058 Aug  4  2015 unattended-upgrades-dpkg_2015-08-04_20:25:14.411794.log
> -rw-r--r-- 1 root root 1418 Aug  7  2015 unattended-upgrades-dpkg_2015-08-07_11:27:50.855330.log
> -rw-r--r-- 1 root root  540 Aug 19  2015 unattended-upgrades-dpkg_2015-08-19_10:53:36.820176.log
> -rw-r--r-- 1 root root 9056 Mär  2  2016 unattended-upgrades.log
>
>
> Does anybody have an idea how to investigate this and who to
> enable unattended upgrades?
>
> Thanks, Gregor

[toc] | [prev] | [next] | [standalone]

#179725

On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> Hi Gregor,
> 
> one more detail about the configuration of said system (see below/between):
> 
> Any ideas how to proceed?
> 
> Ciao; Gregor 
> 
> 
There's another thread recently (during March, I think) on this mailing 
list about the same subject. The gyst is you need to do a 
dpkg-reconfigure unattended-upgrades after installation to create some 
config files needed to make the upgrades actually happen.

I suggest you search the archive of this list for the relevant thread. 
The details are in there.

Mark

[toc] | [prev] | [next] | [standalone]

#179780

Hi Mark, debian users,
* Mark Fletcher <mark27q1@gmail.com> [2017-04-03; 21:08]:
> On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> There's another thread recently (during March, I think) on this mailing 
> list about the same subject. The gyst is you need to do a 
> dpkg-reconfigure unattended-upgrades after installation to create some 
> config files needed to make the upgrades actually happen.

Yupp, I read this then and I did the dpkg-reconfigure to no
avail.  On April 2nd at 11:19 local time I purged and reinstalled
unattended-upgrades.  According to the log file
unattended-upgrade run on April, 2nd at 11:20 local time but did
not find anything to upgrade.  But actually there was a security
announcement on March, 28th and when I do apt-get update; apt-get
upgrade manually apt proposes to upgrade the eject package.  And:
unattended upgrades did not run yesterday or today.

This is all very strange.

Ciao; Gregor 

[toc] | [prev] | [next] | [standalone]

#179789

On Tuesday 04 April 2017 20:29:26 Gregor Zattler wrote:
> Hi Mark, debian users,
>
> * Mark Fletcher <mark27q1@gmail.com> [2017-04-03; 21:08]:
> > On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> > There's another thread recently (during March, I think) on this mailing
> > list about the same subject. The gyst is you need to do a
> > dpkg-reconfigure unattended-upgrades after installation to create some
> > config files needed to make the upgrades actually happen.
>
> Yupp, I read this then and I did the dpkg-reconfigure to no
> avail.  On April 2nd at 11:19 local time I purged and reinstalled
> unattended-upgrades.  According to the log file
> unattended-upgrade run on April, 2nd at 11:20 local time but did
> not find anything to upgrade.  But actually there was a security
> announcement on March, 28th and when I do apt-get update; apt-get
> upgrade manually apt proposes to upgrade the eject package.  And:
> unattended upgrades did not run yesterday or today.
>
> This is all very strange.
>
> Ciao; Gregor

As the OP of the above mentioned earlier thread I should point out that I have 
not got unattended-upgrades working either.  But I only wanted it as a 
temporary solution, so I have given up.

Lisi

[toc] | [prev] | [next] | [standalone]

#179803

I'm going to break my own self-imposed rule on top-posting to make sure 
you see my exhortation not to cc me as I am subscribed to the list

On Wed, Apr 05, 2017 at 01:20:56AM +0100, Lisi Reisz wrote:
> On Tuesday 04 April 2017 20:29:26 Gregor Zattler wrote:
> > Hi Mark, debian users,
> >
> > * Mark Fletcher <mark27q1@gmail.com> [2017-04-03; 21:08]:
> > > On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> > > There's another thread recently (during March, I think) on this mailing
> > > list about the same subject. The gyst is you need to do a
> > > dpkg-reconfigure unattended-upgrades after installation to create some
> > > config files needed to make the upgrades actually happen.
> >
> > Yupp, I read this then and I did the dpkg-reconfigure to no
> > avail.  On April 2nd at 11:19 local time I purged and reinstalled
> > unattended-upgrades.  According to the log file
> > unattended-upgrade run on April, 2nd at 11:20 local time but did
> > not find anything to upgrade.  But actually there was a security
> > announcement on March, 28th and when I do apt-get update; apt-get
> > upgrade manually apt proposes to upgrade the eject package.  And:
> > unattended upgrades did not run yesterday or today.
> >
> > This is all very strange.
> >
> > Ciao; Gregor
> 
> As the OP of the above mentioned earlier thread I should point out that I have 
> not got unattended-upgrades working either.  But I only wanted it as a 
> temporary solution, so I have given up.
> 

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 "me-too!"

Mark

[toc] | [prev] | [next] | [standalone]

#179808

[Multipart message — attachments visible in raw view] — view raw

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 days, I will post back what my results, even if the only 
> thing that results is sympathy for your situation and a "me-too!"

I have a working unattended-upgrades setup, I will try and remember what I
had to do.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀ Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [next] | [standalone]

#179814

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 days, I will post back what my results, even if the only
> > thing that results is sympathy for your situation and a "me-too!"
>
> I have a working unattended-upgrades setup, I will try and remember what I
> had to do.

Thank you!

Lisi

[toc] | [prev] | [next] | [standalone]

#179827

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 days, I will post back what my results, even if the only
>>> thing that results is sympathy for your situation and a "me-too!"
>>
>> I have a working unattended-upgrades setup, I will try and remember what I
>> had to do.
> 
> Thank you!
> 
> Lisi
> 

I know I am quite late to the party, but has

https://wiki.debian.org/UnattendedUpgrades

been offered as a possible answer? I have used it as a guide for
unattended-upgrades setup on a sizable handful of systems, and with
uniform success. As I recall it, install defaults apply only security
upgrades, and of course require that /etc/apt/sources.list include the
version appropriate reference to security.debian.org -

deb http://security.debian.org/ jessie/updates main contrib non-free

for example.

Tom Dial
tdial@acm.org

[toc] | [prev] | [next] | [standalone]

#179828

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 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 "me-too!"
>>>
>>> I have a working unattended-upgrades setup, I will try and remember what I
>>> had to do.
>>
>> Thank you!
>>
>> Lisi
>>
> 
> I know I am quite late to the party, but has
> 
> https://wiki.debian.org/UnattendedUpgrades
> 
> been offered as a possible answer? I have used it as a guide for
> unattended-upgrades setup on a sizable handful of systems, and with
> uniform success. As I recall it, install defaults apply only security
> upgrades, and of course require that /etc/apt/sources.list include the
> version appropriate reference to security.debian.org -
> 
> deb http://security.debian.org/ jessie/updates main contrib non-free
> 
> for example.
> 
> Tom Dial
> tdial@acm.org
> 

If I recall correctly unattended-upgrades needs to be reconfigured
(through dpkg-reconfigure) for applying upgrades.

[toc] | [prev] | [next] | [standalone]

#179832

On Wednesday 05 April 2017 21:26:16 Erwan David wrote:
> 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 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
> >>>> "me-too!"
> >>>
> >>> I have a working unattended-upgrades setup, I will try and remember
> >>> what I had to do.
> >>
> >> Thank you!
> >>
> >> Lisi
> >
> > I know I am quite late to the party, but has
> >
> > https://wiki.debian.org/UnattendedUpgrades
> >
> > been offered as a possible answer? I have used it as a guide for
> > unattended-upgrades setup on a sizable handful of systems, and with
> > uniform success. As I recall it, install defaults apply only security
> > upgrades, and of course require that /etc/apt/sources.list include the
> > version appropriate reference to security.debian.org -
> >
> > deb http://security.debian.org/ jessie/updates main contrib non-free
> >
> > for example.
> >
> > Tom Dial
> > tdial@acm.org
>
> If I recall correctly unattended-upgrades needs to be reconfigured
> (through dpkg-reconfigure) for applying upgrades.

That has also been said!

Lisi

[toc] | [prev] | [next] | [standalone]

#179831

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 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 "me-too!"
> >>
> >> I have a working unattended-upgrades setup, I will try and remember what
> >> I had to do.
> >
> > Thank you!
> >
> > Lisi
>
> I know I am quite late to the party, but has
>
> https://wiki.debian.org/UnattendedUpgrades
>
> been offered as a possible answer?
yes, several times!!

> I have used it as a guide for 
> unattended-upgrades setup on a sizable handful of systems, and with
> uniform success. As I recall it, install defaults apply only security
> upgrades, and of course require that /etc/apt/sources.list include the
> version appropriate reference to security.debian.org -
>
> deb http://security.debian.org/ jessie/updates main contrib non-free
>
> for example.

Yes.

Perhaps there is a recent temporary bug in it??  As I said, I had a short-term 
use for it and have moved on.  Though I might want to look again if I could 
do so quickly.

Lisi
>
> Tom Dial
> tdial@acm.org

[toc] | [prev] | [next] | [standalone]

#180243

[Multipart message — attachments visible in raw view] — view raw

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 have some packages
from backports that won't be auto-updated and likewise jessie-updates. I
found /var/log/unattended-upgrades useful to establish this.

I do not know what is wrong with Gregor's setup.

If you Lisi revisit this and it doesn't work, I could try to help.


-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀ Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [next] | [standalone]

#180273

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web