Hi Gabriel,

Thanks for reporting. I can't see how you're getting this warning,
considering that there's no '--force-yes' in your script. It's been
removed from apticron since dec/2015. See #806948.

Maybe you're getting it from another server, or from another apticron
script in your server?

Bests,

On Wed, Feb 07, 2018 at 05:10:06PM -0500, Gabriel Filion wrote:
> Package: apticron
> Version: 1.1.61
> Severity: normal
> 
> Hello,
> 
> Ever since we have stretch servers using apticron, we're getting emails
> from the cron runs that show only two warning messages, twice the same
> line:
> 
> W: --force-yes is deprecated, use one of the options starting with
> --allow instead.
> 
> 
> I've run apticron with tracing on (bash -x apticron) and found out that
> the two following commands are the ones causing the warnings:
> 
> /usr/bin/apt-get -q -y --ignore-hold --allow-unauthenticated -s
> dist-upgrade
> 
> and:
> 
> /usr/bin/apt-get --ignore-hold -qq -d dist-upgrade
> 
> This means that apticron is calling apt-get with a deprecated set of
> arguments, but I'm not sure how to fix this yet.
> 
> -- System Information:
> Debian Release: 9.3
>   APT prefers oldoldstable
>   APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
> Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_CA.utf8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_CA.utf8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages apticron depends on:
> ii  apt                    1.4.8
> ii  bzip2                  1.0.6-8.1
> ii  cron [cron-daemon]     3.0pl1-128+b1
> ii  debconf [debconf-2.0]  1.5.61
> ii  dpkg                   1.18.24
> ii  mailutils [mailx]      1:3.1.1-1
> ii  ucf                    3.0036
> 
> Versions of packages apticron recommends:
> ii  apt-listchanges  3.10
> ii  iproute2         4.9.0-1+deb9u1
> 
> apticron suggests no packages.
> 
> -- debconf information excluded

-- 
tiago

Reply via email to