Re: [LAU] Jack, lowlatency, generic, update

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <gnome@...>
Cc: linux-audio-user <linux-audio-user@...>
Date: Monday, June 3, 2013 - 6:33 am

This is a multi-part message in MIME format.
--------------000905040407050306080203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Am 03.06.2013 01:36, schrieb david:

I do it the other way round, I put on hold what I didn't want to
upgrade, and upgrade the rest.
I never do a backup, and in the last 10 Years I didn't ever need one. ;-)
I usually do apt-get update && apt-get -u dist-upgrade and read the
output, that gives me enough information if I need to put packages on
hold, or if I could safely just run the full upgrade.
If a package is broken after upgrade, I just downgrade it to the one
from testing.

--------------000905040407050306080203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Am 03.06.2013 01:36, schrieb david:
I
always do a backup first. Have had trivial things like changes in
X video drivers make X unusable.

Although I benefit
from the developments in multimedia

software I'm not sure I like exposing my system to so many

opportunities for failure.

A strategy I've used in past is to *not*
upgrade until I

need something. Maybe could call it it "choose your own

freeze".

I usually just upgrade what I want when I want.

I do it the other way round, I put on hold what I didn't want to
upgrade, and upgrade the rest.
I never do a backup, and in the last 10 Years I didn't ever need
one. ;-)
I usually do apt-get update && apt-get -u dist-upgrade  and
read the output, that gives me enough information if I need to put
packages on hold, or if I could safely just run the full upgrade.
If a package is broken after upgrade, I just downgrade it to the one
from testing.

--------------000905040407050306080203--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Jack, lowlatency, generic, update, Alf Haakon Lund, (Sat Jun 1, 8:52 pm)
Re: [LAU] Jack, lowlatency, generic, update, Len Ovens, (Sat Jun 1, 11:33 pm)
Re: [LAU] Jack, lowlatency, generic, update, Alf Haakon Lund, (Sun Jun 2, 1:28 am)
Re: [LAU] Jack, lowlatency, generic, update, david, (Sun Jun 2, 9:40 am)
Re: [LAU] Jack, lowlatency, generic, update, Joel Roth, (Sun Jun 2, 10:06 pm)
Re: [LAU] Jack, lowlatency, generic, update, david, (Sun Jun 2, 11:36 pm)
Re: [LAU] Jack, lowlatency, generic, update, hermann meyer, (Mon Jun 3, 6:33 am)
Re: [LAU] Jack, lowlatency, generic, update, david, (Tue Jun 4, 9:34 am)
Re: [LAU] Jack, lowlatency, generic, update, hermann meyer, (Wed Jun 5, 11:30 am)
Re: [LAU] Jack, lowlatency, generic, update, david, (Wed Jun 5, 7:04 pm)
Re: [LAU] Jack, lowlatency, generic, update, Chris Bannister, (Sun Jun 2, 4:49 pm)
Re: [LAU] Jack, lowlatency, generic, update, david, (Sun Jun 2, 6:29 pm)
Re: [LAU] Jack, lowlatency, generic, update, Len Ovens, (Sun Jun 2, 3:06 pm)
Re: [LAU] Jack, lowlatency, generic, update, david, (Sun Jun 2, 6:58 pm)
Re: [LAU] Jack, lowlatency, generic, update, Len Ovens, (Mon Jun 3, 12:07 am)
Re: [LAU] Jack, lowlatency, generic, update, david, (Tue Jun 4, 9:36 am)
Re: [LAU] Jack, lowlatency, generic, update, Alf Haakon Lund, (Sun Jun 2, 4:26 pm)
Re: [LAU] Jack, lowlatency, generic, update, Barney Holmes, (Sun Jun 2, 8:10 pm)
Re: [LAU] Jack, lowlatency, generic, update, Simon Wise, (Sun Jun 2, 12:06 pm)
Re: [LAU] Jack, lowlatency, generic, update, Chris Bannister, (Sun Jun 2, 4:55 pm)
Re: [LAU] Jack, lowlatency, generic, update, John Murphy, (Sat Jun 1, 10:24 pm)