This is present on Lucid (server)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/223502
Title:
apt cron.daily script doesn't check value-existence
--
ubuntu-bugs mailing list
Confirmed this is still present on Hardy.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirmed this is still present on Hardy.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems the values for these variables are user based.
Then if you run the command gconftool --get
/system/http_proxy/use_http_proxy with a user that is not the proper
one, you get that error.
In /etc/cron.daily/apt you have:
admin_user=$(getent group admin|cut -d: -f4|cut -d, -f1)
and:
The bug status makes this look like it's fixed, but it is still broken
in Intrepid (and I can't figure out how to indicate that). As Intrepid
is still a supported release, this seems like relevant information.
--
apt cron.daily script doesn't check value-existence
As of April 24, 2009 this bug is back in Hardy, most likely a regression
issue.
/etc/cron.daily/apt:
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/http_proxy/host'
No value set for `/system/http_proxy/port'
--
apt cron.daily script doesn't check value-existence
** Changed in: apt (Ubuntu Jaunty)
Status: Confirmed = Fix Committed
** Changed in: apt (Ubuntu Jaunty)
Assignee: (unassigned) = Michael Vogt (mvo)
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification
This bug was fixed in the package apt - 0.7.20.2ubuntu5
---
apt (0.7.20.2ubuntu5) jaunty; urgency=low
[ Colin Watson ]
* cmdline/acqprogress.cc:
- Call pkgAcquireStatus::Pulse even if quiet, so that we still get
dlstatus messages on the status-fd (LP: #290234).
[
Please don't assign bugs to ubuntu-core-dev. It's sufficient to just
leave it unassigned.
** Changed in: apt (Ubuntu)
Assignee: Ubuntu Core Development Team (ubuntu-core-dev) = (unassigned)
** Changed in: apt (Ubuntu Jaunty)
Importance: Undecided = Low
--
apt cron.daily script doesn't
** Changed in: apt (Ubuntu)
Assignee: (unassigned) = Claudio (ubuntu-bugs-apt-get)
** Changed in: apt (Ubuntu)
Assignee: Claudio (ubuntu-bugs-apt-get) = Ubuntu Core Development Team
(ubuntu-core-dev)
--
apt cron.daily script doesn't check value-existence
+1
I use this workaround myself.
It is standard behaviour on Ubuntu Server/JeOS installs so it needs to
be fixed IMHO
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same here. I gave up after numerous attempts to set a (empty) value for
these keys but to no avail. Redirecting to stderr fixes.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Same here. I gave up after numerous attempts to set a (empty) value for
these keys but to no avail. Redirecting to stderr fixes.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
also happens on one of my systems. The applied patch fixes the problem.
** Changed in: apt (Ubuntu)
Status: New = Confirmed
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
I have the same problem. I have applied your patch manually. Why do you
have inserted the ; at the end of the first two new lines?
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
I'm Perl afflicted. That's probably why i tend to type ; after each
line. It doesn't hurt though, in the shellscript.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Patch against cron.daily/apt
http://launchpadlibrarian.net/13979915/cron_daily_apt.diff
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
17 matches
Mail list logo
