On Ma, 01 oct 13, 13:56:32, Bob Proulx wrote:
Chris Bannister wrote:
Vincent Lefevre wrote:
During important upgrades such as locales, I avoid doing things
like starting an xterm... Usually, already running applications
You do system upgrades WITH X running? :(
One of my machines
On 2013-09-30 04:03:54 +1300, Chris Bannister wrote:
On Sat, Sep 28, 2013 at 03:45:01PM +0200, Ralf Mardorf wrote:
On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
During important upgrades such as locales, I
Chris Bannister wrote:
Vincent Lefevre wrote:
During important upgrades such as locales, I avoid doing things
like starting an xterm... Usually, already running applications
You do system upgrades WITH X running? :(
One of my machines is an Unstable Sid system as a desktop. I am using
it
On Sat, Sep 28, 2013 at 03:45:01PM +0200, Ralf Mardorf wrote:
On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
During important upgrades such as locales, I avoid doing things
like starting an xterm... Usually,
On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
During important upgrades such as locales, I avoid doing things
like starting an xterm... Usually, already running applications
You do system upgrades WITH X running? :(
If there is a problem with the upgrade of X, you could
On Sun, 2013-09-29 at 01:15 +1200, Chris Bannister wrote:
On Tue, Sep 24, 2013 at 02:20:39AM +0200, Vincent Lefevre wrote:
During important upgrades such as locales, I avoid doing things
like starting an xterm... Usually, already running applications
You do system upgrades WITH X
When packages are upgraded (e.g. locales), cron scripts can given
errors. Is it possible to lock (delay) them during a package upgrade?
Shouldn't this be done by default?
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog:
Vincent Lefevre wrote:
When packages are upgraded (e.g. locales), cron scripts can given
errors. Is it possible to lock (delay) them during a package upgrade?
Shouldn't this be done by default?
I have noticed this at times too. When I am doing a full system
upgrade from major release to major
On 2013-09-23 14:11:31 -0600, Bob Proulx wrote:
Vincent Lefevre wrote:
When packages are upgraded (e.g. locales), cron scripts can given
errors. Is it possible to lock (delay) them during a package upgrade?
Shouldn't this be done by default?
I have noticed this at times too. When I am
9 matches
Mail list logo