Up.
Confirmed still there on Ubuntu 14.04.1 LTS.
Should we raise the bug for anacron then?
I've set up the transparent proxy locally to avoid this.
** Changed in: update-notifier (Ubuntu)
Status: Expired = Confirmed
** Package changed: update-notifier (Ubuntu) = anacron (Ubuntu)
**
Note that this is NOT cron !!!
Date: Tue, 8 Jul 2014 07:48:29 +0300
From: Anacron r...@..fi
To: r...@...fi
So this is a problem with anacron, which when run via
/etc/cron.d/anacron does not inherit the environment from cron's pam
handler (because anacron is run via an upstart job,
[Expired for update-notifier (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: update-notifier (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, now it raise:
/etc/cron.daily/update-notifier-common:
Traceback (most recent call last):
File /usr/lib/update-notifier/package-data-downloader, line 239, in
process_download_requests
dest_file = urllib.urlretrieve(files[i])[0]
File /usr/lib/python2.7/urllib.py, line 94, in
I confirm this bug, on a 14.04.1 LTS.
I've tried to add:
# We have to set also proxy. See:
# https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1317920
#
http_proxy=http://proxy:8080/;
https_proxy=https://proxy:8080/;
ftp_proxy=ftp://proxy:8080/;
on /etc/anacrontab config
The cronjob is run from cron; cron is configured via /etc/pam.d/cron to use
pam_env.so by default, which reads
/etc/environment. Why is this not working on your system?
Same happens also Ubuntu 12.04.4 LTS
Note that this is NOT cron !!!
Date: Tue, 8 Jul 2014 07:48:29 +0300
From: Anacron
I created two simple cron scripts on a new installation of Ubuntu 14.04
amd64 with all updates installed (the only additional package I
installed was cifs-utils).
/etc/cron.daily/testenv-daily:
#!/bin/sh
logger -t testenv-daily http_proxy=$http_proxy
/etc/cron.hourly/testenv-hourly:
#!/bin/sh
The cronjob is run from cron; cron is configured via /etc/pam.d/cron to
use pam_env.so by default, which reads /etc/environment. Why is this
not working on your system?
Individual cron jobs should definitely not be expected to source
/etc/environment directly.
** Changed in: update-notifier
