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
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-t
, debian users,
> >
> > * Mark Fletcher [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 nee
> 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 A
figure 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
unatt
ink) 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
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
/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 upgra
On Friday 24 March 2017 17:34:58 Teemu Likonen wrote:
> Lisi Reisz [2017-03-24 17:13:21Z] wrote:
> > On Friday 24 March 2017 09:56:23 didier gaumet wrote:
> >> # dpkg-reconfigure -plow unattended-upgrades
> >
> > This is what I had missed! I have now run it.
>
&g
Lisi Reisz [2017-03-24 17:13:21Z] wrote:
> On Friday 24 March 2017 09:56:23 didier gaumet wrote:
>> # dpkg-reconfigure -plow unattended-upgrades
>
> This is what I had missed! I have now run it.
The command creates file /etc/apt/apt.conf.d/20auto-upgrades:
APT::Periodic:
ated, either by typing a
> content in an editor or you can symply type as root:
> # dpkg-reconfigure -plow unattended-upgrades
This is what I had missed! I have now run it.
> > lisi@Eros:~$ su
> > Password:
> > root@Eros:/home/lisi# unattended-upgrades
> > root
econfigure -plow unattended-upgrades
> lisi@Eros:~$ su
> Password:
> root@Eros:/home/lisi# unattended-upgrades
> root@Eros:/home/lisi#
>
> What has that done? I can verify nothing because I can't see what it has or
> has not done. It took a long while doing it, but ap
On Thursday 23 March 2017 04:26:17 Teemu Likonen wrote:
> Lisi Reisz [2017-03-22 00:37:18Z] wrote:
> > How do I get unattended upgrades a) to function and b) to tell me when
> > it has upgraded something.
>
> Probably you need to add the following lines in the top of
I quote:
> > -
> > To install these packages, run the following command as root:
> >
> > # apt-get install unattended-upgrades apt-listchanges
> > The default configuration file for the unattended-upgrades package is
> > at /etc/apt/apt.conf.d/50unatten
Le 23/03/2017 à 02:06, Lisi Reisz a écrit :
>
> Thank you. Yes, I have read and tried to follow it. I quote:
> -
> To install these packages, run the following command as root:
>
> # apt-get install unattended-upgrades apt-listchanges
> The default configuration fi
Lisi Reisz [2017-03-22 00:37:18Z] wrote:
> How do I get unattended upgrades a) to function and b) to tell me when
> it has upgraded something.
Probably you need to add the following lines in the top of
/etc/apt/apt.conf.d/50unattended-upgrades file (or some other file in
the same dir
nstall unattended-upgrades apt-listchanges
The default configuration file for the unattended-upgrades package is
at /etc/apt/apt.conf.d/50unattended-upgrades. The defaults will work fine,
but you should read it and make changes as needed.
# editor /etc/apt/apt.conf.d/50unattended-upgrades
---
there is a doc in the Debian wiki:
https://wiki.debian.org/UnattendedUpgrades
tl:dnr:
How do I get unattended upgrades a) to function and b) to tell me when it has
upgraded something.
With Debian unattended-upgrades installed I can't make out form Adam whether
they have run. I have run:
# cd /var/log/unattended-upgrades/
# cat unattended-upgrades-shutdown.log
Can anyone help with this?
Just to be clear, after apache is upgraded via unattended-upgrades,
apache is in the stopped state. I have to manually start it again.
On 27/02/2017 12:45 PM, Yasir Assam wrote:
> Running Jessie. Every time apache is upgraded through
> unattended-upgrades, it
Running Jessie. Every time apache is upgraded through
unattended-upgrades, it isn't restarted.
Here's an excerpt from syslog:
Feb 27 06:41:32 musomates systemd[1]: Starting LSB: Apache2 web server...
Feb 27 06:41:32 musomates apache2[24650]: Starting web server: apache2.
Feb 2
h seems to take care of an
unattended upgrade process being finished properly in case of a
shutdown/reboot of the system. This is done via the python script
/usr/share/unattended-upgrades/unattendedupgrade-shutdown.
I'm wondering what's happening if I put my system to sleep (via
s
On 02/06/2017 09:25 PM, Unman wrote:
On Mon, Feb 06, 2017 at 01:19:00PM +, Patrick Schleizer wrote:
The unattended-upgrades was not installed on my Debian jessie system.
After upgrading to Debian stretch, the package unattended-upgrades got
installed. 'reverse-depends unattended-upg
17 at 13:19:00 +, Patrick Schleizer wrote:
> >> >> > The unattended-upgrades was not installed on my Debian jessie
> >> >> > system. After upgrading to Debian stretch, the package
> >> >> > unattended-upgrades got installed. 'reverse-d
Lisi Reisz writes:
> On Monday 06 February 2017 18:24:38 Mart van de Wege wrote:
>> Lisi Reisz writes:
>> > On Monday 06 February 2017 13:54:11 Brian wrote:
>> >> On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
>> >> > The unattended-u
On Tue, Feb 07, 2017 at 02:25:12AM +, Unman wrote:
> On Mon, Feb 06, 2017 at 01:19:00PM +, Patrick Schleizer wrote:
> > The unattended-upgrades was not installed on my Debian jessie system.
> > After upgrading to Debian stretch, the package unattended-upgrades got
> >
On Mon, Feb 06, 2017 at 01:19:00PM +, Patrick Schleizer wrote:
> The unattended-upgrades was not installed on my Debian jessie system.
> After upgrading to Debian stretch, the package unattended-upgrades got
> installed. 'reverse-depends unattended-upgrades' [1] did not
On Monday 06 February 2017 18:24:38 Mart van de Wege wrote:
> Lisi Reisz writes:
> > On Monday 06 February 2017 13:54:11 Brian wrote:
> >> On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
> >> > The unattended-upgrades was not installed on my Debi
On Mon, Feb 06, 2017 at 07:24:38PM +0100, Mart van de Wege wrote:
>
> I agree with the developers' sentiment that automatic upgrades are a
> good thing, but I really think Debian could have cooked up a better
> script than !@#$% 'unattended-upgrades'.
>
Standard
Lisi Reisz writes:
> On Monday 06 February 2017 13:54:11 Brian wrote:
>> On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
>> > The unattended-upgrades was not installed on my Debian jessie system.
>> > After upgrading to Debian stretch, the pack
at 13:19:00 +, Patrick Schleizer wrote:
> > > > > The unattended-upgrades was not installed on my Debian jessie
> > > > > system. After upgrading to Debian stretch, the package
> > > > > unattended-upgrades got installed. 'reverse-depends
>
On Monday 06 February 2017 16:55:25 Joe wrote:
> On Mon, 6 Feb 2017 16:30:36 +
>
> Lisi Reisz wrote:
> > On Monday 06 February 2017 13:54:11 Brian wrote:
> > > On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
> > > > The unattended-upgrades w
On Mon, 6 Feb 2017 16:30:36 +
Lisi Reisz wrote:
> On Monday 06 February 2017 13:54:11 Brian wrote:
> > On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
> > > The unattended-upgrades was not installed on my Debian jessie
> > > system. After upgra
On Monday 06 February 2017 13:54:11 Brian wrote:
> On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
> > The unattended-upgrades was not installed on my Debian jessie system.
> > After upgrading to Debian stretch, the package unattended-upgrades got
> > instal
On Mon 06 Feb 2017 at 13:19:00 +, Patrick Schleizer wrote:
> The unattended-upgrades was not installed on my Debian jessie system.
> After upgrading to Debian stretch, the package unattended-upgrades got
> installed. 'reverse-depends unattended-upgrades' [1] did not make me
The unattended-upgrades was not installed on my Debian jessie system.
After upgrading to Debian stretch, the package unattended-upgrades got
installed. 'reverse-depends unattended-upgrades' [1] did not make me any
wiser. There must be a gap of my apt knowledge. Can anyone shed light on
t
On Thu, 9 Jun 2016 11:39:36 +0200, Wolfgang Karall
wrote:
>It's not unattended-upgrades, what you're seeing is the output of
>needrestart, which is configured by default to only showing what it
>would do, but not actually restarting anything.
>
>Take a look at the
Hello,
On 16-06-08 22:11:33, Jesper Dybdal wrote:
> At the end of unattended-upgrades-dpkg.log, I see:
>
> >Services to be restarted:
> >Skipping dbus.service...
> >systemctl restart apache2.service cron.service
> >Log ended: 2016-06-08 04:36:36
>
> How
I am running up-to-date Jessie (8.5) with unattended-upgrades to provide
security upgrades. But it seems that its attempts to restart services
fail.
Early this morning unattended-upgrades upgraded "libexpat1".
At the end of unattended-upgrades-dpkg.log, I see:
>Services to
Quoting moxalt (mox...@riseup.net):
> On Tue, 13 Oct 2015 19:22:55 +0200, Ondřej Grover
> wrote:
> > It wouldn't be an overkill if there was a simple way to manage a local
> > repository and packages with custom modifications. I have looked around and
> > it didn't seem that straight-forward. Is
On Tue, 13 Oct 2015 19:22:55 +0200, Ondřej Grover
wrote:
> >
> > The most "Debian-proper" way? I'm not really sure- I would edit the script
> > myself and just keep that as the local version. The only problem is that
> > newer
> > versions of the package would probably overwrite it- but they may
>
> The most "Debian-proper" way? I'm not really sure- I would edit the script
> myself and just keep that as the local version. The only problem is that
> newer
> versions of the package would probably overwrite it- but they may offer a
> 'local version of config' menu like GRUB and libpolkit do.
On Mon, 12 Oct 2015 19:43:00 +0200, Ondřej Grover
wrote:
> Because I get such emails for more hosts and it's inconvenient to try to
> match up the changelogs with reports. I would also like to see the full log
> for needrestart output.
>
> As I asked in my original question, I'd like to know wha
scripts is. If that is to roll my own
package with a patch, I wonder what the recommended and most maintainable
way is these days.
Kind regards,
Ondřej Grover
On Sun, Oct 11, 2015 at 7:52 PM, moxalt wrote:
> So you want to combine the output of unattended-upgrades itself and
> apt-listch
So you want to combine the output of unattended-upgrades itself and
apt-listchanges into a single e-mail? Why?
Also, couldn't you just edit the script to make it function as you want it?
Hello,
I'm trying to configure unattended-upgrades to include apt-listchanges
output in the mail it sends me. I had a look at the Python
script /usr/bin/unattended-upgrade and it seems it forces apt-listchanges
to send a separate email. Is there a way around this?
One way I though of was to
On 3/16/2015 10:53 PM, Seeker wrote:
On 3/16/2015 3:57 AM, Tapio Lehtonen wrote:
I can't understand how unattended upgrades continues to work after
Jessi is stable. In wheezy the config file has
"origin=Debian,archive=stable,label=Debian-Security";
"origin=Debi
On 3/16/2015 3:57 AM, Tapio Lehtonen wrote:
I can't understand how unattended upgrades continues to work after
Jessi is stable. In wheezy the config file has
"origin=Debian,archive=stable,label=Debian-Security";
"origin=Debian,archive=oldstable,label=Debian-Securit
I can't understand how unattended upgrades continues to work after
Jessi is stable. In wheezy the config file has
"origin=Debian,archive=stable,label=Debian-Security";
"origin=Debian,archive=oldstable,label=Debian-Security";
I don't want to upgrade from Whe
On 19/02/2015 15:05, Marko Randjelovic wrote:
The best solution I see is to edit your /etc/cron.daily/apt and set
COLUMNS and LINES environment variables manualy, but since
/usr/lib/perl5/Term/ReadKey.pm belongs to libterm-readkey-perl
package, I would check if this package is installed and if
On Thu, 19 Feb 2015 08:41:33 +0200
Brent Clark wrote:
> Good day Guys
>
> I just installed and new to unattended-upgrades.
>
> Looking at the logs this morning I see the folllowing.
>
> cat
> /var/log/unattended-upgrades/unattended-upgrades-dpkg_2015-02-
Good day Guys
I just installed and new to unattended-upgrades.
Looking at the logs this morning I see the folllowing.
cat
/var/log/unattended-upgrades/unattended-upgrades-dpkg_2015-02-19_06\:48\:53.476190.log
(Reading database ... 60516 files and directories currently installed.)
Preparing
t; been a problem until now. I'm not a programmer so bear with me.
> >
> > No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log
> > other than the dry runs.
> >
> > Any help would be greatly appreciated.
>
> My experiences with unattended
On Tuesday 21 October 2014 22:59:05 Andrei POPESCU wrote:
> On Ma, 21 oct 14, 22:45:20, Chris wrote:
> > $ls -lah |grep apt
> > -rw-r--r-- 1 root root 15K Sep 23 08:20 apt
>
> The script is not executable ;)
>
> Kind regards,
> Andrei
oh... I guess that was the problem. Is this a common pract
appears in /var/log/unattended-upgrades/unattended-upgrades.log
> other than the dry runs.
>
> Any help would be greatly appreciated.
My experiences with unattended-upgrades from Wheezy is that it is not
very useable for me. It's possible to get the security support working,
but if you
On Ma, 21 oct 14, 22:45:20, Chris wrote:
>
> $ls -lah |grep apt
> -rw-r--r-- 1 root root 15K Sep 23 08:20 apt
The script is not executable ;)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.
On Monday 20 October 2014 20:58:48 Andrei POPESCU wrote:
> On Lu, 20 oct 14, 20:39:59, Chris wrote:
> > Yes, I do have anacron installed because I thought that might be the
> > problem.
>
> If you have anacron installed the jobs will be run by anacron, but you
> already have proven that daily cron
On Lu, 20 oct 14, 20:39:59, Chris wrote:
>
> Yes, I do have anacron installed because I thought that might be the problem.
If you have anacron installed the jobs will be run by anacron, but you
already have proven that daily cronjobs work, so that's probably a dead
end.
> How would you sugges
On Monday 20 October 2014 20:13:14 Andrei POPESCU wrote:
> On Lu, 20 oct 14, 17:48:35, Chris wrote:
> > No, that's not the problem.
> >
> > "No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log
> > other than the dry runs."
> >
On Lu, 20 oct 14, 17:48:35, Chris wrote:
>
> No, that's not the problem.
>
> "No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log
> other than the dry runs."
>
> i.e. today on 20 October the last entry is still from yesterday:
>
&g
On Sun, Oct 19, 2014 at 02:46:07PM +0200, Chris wrote:
> "origin=Debian,archive=stable,label=Debian-Security";
> Unattended-Upgrade::Origins-Pattern::
> "origin=Debian,archive=oldstable,label=Debian-Security";
^
Is that right?
--
"If you're not careful, the newsp
found that can be upgraded
> > unattended
>
> Seems like there's nothing to upgrade.
>
> Kind regards,
> Andrei
No, that's not the problem.
"No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log other
than the dry runs."
i.e. today on 20 O
On Du, 19 oct 14, 14:46:07, Chris wrote:
> Hi,
>
> I'm having no luck getting unattended-upgrads working on a Wheezy server.
...
> 2014-10-19 14:38:11,709 INFO No packages found that can be upgraded unattended
Seems like there's nothing to upgrade.
Kind regards,
Andrei
--
http://wiki.debian.or
Hi,
I'm having no luck getting unattended-upgrads working on a Wheezy server. The
image for Wheezy is from my vServer provider and has not been a problem until
now. I'm not a programmer so bear with me.
No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log other
Am Montag, 28. Oktober 2013, 11:58:00 schrieb Bob Proulx:
> Florian Lindner wrote:
> > > Florian Lindner wrote:
> > > > root@astarte ~ # ll /etc/cron.daily
> > > > -rwxr-xr-x 1 root root 14985 Jun 4 11:33 apt.dpkg-dist*
> >
> > The thing what puzzles me most is that if the apt.dpkg-dist script
>
Florian Lindner wrote:
> > Florian Lindner wrote:
> > > root@astarte ~ # ll /etc/cron.daily
> > > -rwxr-xr-x 1 root root 14985 Jun 4 11:33 apt.dpkg-dist*
>
> The thing what puzzles me most is that if the apt.dpkg-dist script
> is called manually it logs just fine and everything. But the cron
> job
013/10/27 Florian Lindner :
> > Hello,
> >
> > on Debian Wheezy I try to use the included unattended upgrades script for
> > security updates:
> >
> > root@astarte ~ # cat /etc/apt/apt.conf
> > APT::Install-Recommends "0";
> > APT::Instal
:Periodic::Unattended-Upgrade "1";
>
>
> root@astarte ~ # ll /etc/cron.daily
> -rwxr-xr-x 1 root root 14985 Jun 4 11:33 apt.dpkg-dist*
>
>
> but the last line in /var/log/unattended-upgrades/unattended-upgrades.log is
> from 2013-10-25 when I executed apt.dpkg-dis
Hello,
on Debian Wheezy I try to use the included unattended upgrades script for
security updates:
root@astarte ~ # cat /etc/apt/apt.conf
APT::Install-Recommends "0";
APT::Install-Suggests "0";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Verbose
On Thu, Mar 7, 2013 at 5:35 PM, David Sastre Medina <
d.sastre.med...@gmail.com> wrote:
> On Thu, Mar 07, 2013 at 12:47:31PM +0100, A wrote:
> > On Thu, Mar 7, 2013 at 11:18 AM, David Sastre Medina <
> > d.sastre.med...@gmail.com> wrote:
> > >
> > > This is from /etc/cron.daily/apt:
> > >
> > > #
On Thu, Mar 07, 2013 at 12:47:31PM +0100, A wrote:
> On Thu, Mar 7, 2013 at 11:18 AM, David Sastre Medina <
> d.sastre.med...@gmail.com> wrote:
> >
> > This is from /etc/cron.daily/apt:
> >
> > # auto upgrade all upgradeable packages
> > UPGRADE_STAMP=/var/lib/apt/periodic/upgrade-stamp
> > if whic
Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> > > > Hola, David,
> > > >
> > > > The file exists under that path, but I can't confirm if it's running
> > > since
> > > > 'invoke-rc.d unattended-upgrades status' retu
sts under that path, but I can't confirm if it's running
> > since
> > > 'invoke-rc.d unattended-upgrades status' returns no output. The same for
> > > 'start' or 'stop' options, no output. I've checked that the proper
> > symli
On Wed, Mar 6, 2013 at 9:03 PM, David Sastre Medina <
d.sastre.med...@gmail.com> wrote:
> On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> > Hola, David,
> >
> > The file exists under that path, but I can't confirm if it's running
> since
> >
On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> Hola, David,
>
> The file exists under that path, but I can't confirm if it's running since
> 'invoke-rc.d unattended-upgrades status' returns no output. The same for
> 'start' or 'stop' op
Hola, David,
The file exists under that path, but I can't confirm if it's running since
'invoke-rc.d unattended-upgrades status' returns no output. The same for
'start' or 'stop' options, no output. I've checked that the proper symlinks
to the file e
On Tue, Mar 05, 2013 at 01:01:45PM +0100, A wrote:
> Hi there,
>
> I've been trying to make *unattended-upgrades* working on Wheezy with no
> success so far.
>
> The steps I have followed are:
>
> - Install *unattended-upgrades*
> - Enable it
>
&g
Hi there,
I've been trying to make *unattended-upgrades* working on Wheezy with no
success so far.
The steps I have followed are:
- Install *unattended-upgrades*
- Enable it
sudo dpkg-reconfigure -plow unattended-upgrades
- Uncomment the following lines in
*/etc/apt/apt.c
2012-03-11 17:13, Aaron Marks skrev:
Unfortunately new packages are not installed. That's what my
unattended-upgrades.log looks like:
2012-03-11 07:03:24,239 INFO Initial blacklisted packages:
2012-03-11 07:04:15,883 INFO Starting unattended upgrades script
2012-03-11 07:04:21,575 INFO Al
I am using Debian wheezy and unattended-upgrades. I would like to install all
updates automatically.
That's my sources.list:
deb http://ftp.de.debian.org/debian/ wheezy main non-free contrib
deb-src http://ftp.de.debian.org/debian/ wheezy main non-free contrib
deb http://security.debia
El 2011-01-05 a las 14:43 +, Tony van der Hoff escribió:
(resending to the list)
> On 05/01/11 12:50, Camaleón wrote:
>> If my findings are correct, the problem is in the script itself and the
>> package should be updated... but being for lenny (stable), I'm not sure
>> if that is possible.
>
On Tue, 04 Jan 2011 22:51:51 +0100, Simon Hollenbach wrote:
>> > Thanks for replying, Cameleon, but as I said, apt-get install just
>> > did it effortlessly. No interaction required.
>>
>> No prompts asking you about when using "apt-get upgrade"? Weird,
>> because that was what the log said and t
> > Thanks for replying, Cameleon, but as I said, apt-get install just did
> > it effortlessly. No interaction required.
>
> No prompts asking you about when using "apt-get upgrade"? Weird, because
> that was what the log said and the package gets blacklisted because of
> that :-?
>
Hi folks,
I
nteraction required.
No prompts asking you about when using "apt-get upgrade"? Weird, because
that was what the log said and the package gets blacklisted because of
that :-?
> I suspect it's a bug, but I don't know enough to report it...
You can open a bug report f
script with a "--debug" flag
("unattended-upgrades --debug") to get additional information :-?
Yes, excellent idea; thanks very much:
(...)
(leaving just -what I think- is the relevant part)
2011-01-04 16:13:26,586 DEBUG pkg 'phpmyadmin' has conffile prompt
>> Maybe you can run the script with a "--debug" flag
>> ("unattended-upgrades --debug") to get additional information :-?
>>
> Yes, excellent idea; thanks very much:
(...)
(leaving just -what I think- is the relevant part)
> 2011-01-04 16:13:26,586 DE
On 04/01/11 15:58, Camaleón wrote:
On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
Can anyone explain why this happens? Should I upgrade phpmyadmin
manually?
Maybe you can run the script with a "--debug" flag ("unattended-upgrades
--debug") to get ad
On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
> I have lenny-based VPS server, which looks after itself pretty well.
> Following the recent security notice regarding PHPMyAdmin, I checked the
> unattended-upgrades log, where I was surprised to notice that it had
>
I have lenny-based VPS server, which looks after itself pretty well.
Following the recent security notice regarding PHPMyAdmin, I checked the
unattended-upgrades log, where I was surprised to notice that it had
skipped the upgrade:
2011-01-03 07:51:03,658 INFO Initial blacklisted packages
Hi!
I’m using Debian/Stable and having trouble with the package
unattended-upgrades in combination with apt-listbugs. This combination
doesn’t seem to work. According the log:
2010-11-24 05:37:15,226 INFO Packages that are upgraded: libssl-dev libssl0.9.8
openssl
2010-11-24 05:37:15,226
hi,
I just discovered the existence of unattended-upgrades for apt on
debian. But I can't find any documentation for it (google gives me all
ubuntu references, and not much of that with any detail). Is it safe to
use on production machines? Should I just use it for security updates?
Do
101 - 191 of 191 matches
Mail list logo