On Friday 17 April 2015 17:18:59 The Wanderer wrote:
> On 04/17/2015 at 11:41 AM, Lisi Reisz wrote:
> > On Friday 17 April 2015 15:51:23 The Wanderer wrote:
> >> On 04/17/2015 at 10:18 AM, Lisi Reisz wrote:
> >>> A valid point. But changing code name reduces the risk of
> >>> absentmindedly upgrad
On 04/17/2015 at 11:41 AM, Lisi Reisz wrote:
> On Friday 17 April 2015 15:51:23 The Wanderer wrote:
>
>> On 04/17/2015 at 10:18 AM, Lisi Reisz wrote:
>>> A valid point. But changing code name reduces the risk of
>>> absentmindedly upgrading and then thinking oops. Particularly in
>>> the case
On Friday 17 April 2015 15:51:23 The Wanderer wrote:
> On 04/17/2015 at 10:18 AM, Lisi Reisz wrote:
> > On Friday 17 April 2015 15:08:13 The Wanderer wrote:
> > A valid point. But changing code name reduces the risk of
> > absentmindedly upgrading and then thinking oops. Particularly in the
> > c
On 04/17/2015 at 10:18 AM, Lisi Reisz wrote:
> On Friday 17 April 2015 15:08:13 The Wanderer wrote:
>
>> My point is that it's easy to take this approach even with
>> sources.list naming testing explicitly, simply by not initiating
>> the actual upgrade. There's no need to track a release by code
On Fri, 17 Apr 2015 15:18:40 +0100
Lisi Reisz wrote:
Hello Lisi,
>And I am paranoid about my own incompetence and forgetfulness. :-(
From my experiences of you here (and on other lists) I think you're not
giving yourself enough credit. IOW, I reckon you're smarter than you
think you are.
--
On Friday 17 April 2015 15:08:13 The Wanderer wrote:
> My point is that it's easy to take this approach even with sources.list
> naming testing explicitly, simply by not initiating the actual upgrade.
> There's no need to track a release by codename, even temporarily, in
> order to avoid the chaos.
On 04/17/2015 at 09:55 AM, Lisi Reisz wrote:
> On Friday 17 April 2015 14:43:53 The Wanderer wrote:
>
>> I do generally wait a week or three after a new stable release
>> before dist-upgrading, and I _always_ review the apt-listchanges
>> report for any dist-upgrade before giving the go-ahead to
On Friday 17 April 2015 14:43:53 The Wanderer wrote:
> I do generally wait a week or three after a new stable release before
> dist-upgrading, and I _always_ review the apt-listchanges report for any
> dist-upgrade before giving the go-ahead to proceed with it, but that's
> about the limit of how f
On 04/16/2015 at 05:34 PM, Patrick Wiseman wrote:
> On Thu, Apr 16, 2015 at 5:25 PM, David Wright
> wrote:
>
>> Quoting Joe (j...@jretrading.com):
>>> However long the wait, the result will be the same. In fact, the
>>> longer the wait, the more upgrades there will be in one go.
>>
>> This may
On Fri, Apr 17, 2015 at 01:04:15PM +0100, Lisi Reisz wrote:
> On Friday 17 April 2015 11:36:26 Darac Marjal wrote:
> > On Thu, Apr 16, 2015 at 04:25:41PM -0500, David Wright wrote:
> > > Quoting Joe (j...@jretrading.com):
> > > > On Thu, 16 Apr 2015 21:11:06 +0100
> > > >
> > > > Lisi Reisz wrote:
On Thu, Apr 16, 2015 at 10:27:51PM +0100, Brad Rogers wrote:
> On Thu, 16 Apr 2015 21:11:06 +0100
> Lisi Reisz wrote:
>
> Hello Lisi,
>
> >But it will be awful the day that Jessie goes Stable because everything
> >will immediately update willy-nilly and out of your control, all at
> >once, to
>
On Friday 17 April 2015 11:36:26 Darac Marjal wrote:
> On Thu, Apr 16, 2015 at 04:25:41PM -0500, David Wright wrote:
> > Quoting Joe (j...@jretrading.com):
> > > On Thu, 16 Apr 2015 21:11:06 +0100
> > >
> > > Lisi Reisz wrote:
> > > > As opposed to problems in a fortnight? If you change all of th
On Thu, Apr 16, 2015 at 04:25:41PM -0500, David Wright wrote:
> Quoting Joe (j...@jretrading.com):
> > On Thu, 16 Apr 2015 21:11:06 +0100
> > Lisi Reisz wrote:
> > > As opposed to problems in a fortnight? If you change all of them,
> > > you will have a whirlwind as soon as Jessie becomes Stable.
On Thursday 16 April 2015 22:27:51 Brad Rogers wrote:
> Admittedly, one has to be fairly confident in one's own abilities to
> select updates wisely. So, as a result, I'd probably advise complete
> newcomers to use codenames. At least until they gained some
> knowledge/skill in handling updates.
On Fri, 17 Apr 2015 08:49:07 +0200
Petter Adsen wrote:
> On Thu, 16 Apr 2015 22:00:58 +0100
> Joe wrote:
>
> > On Thu, 16 Apr 2015 21:11:06 +0100
> > Lisi Reisz wrote:
> > > But it will be awful the day that Jessie goes Stable because
> > > everything will immediately update willy-nilly and ou
On Thu, 16 Apr 2015 22:00:58 +0100
Joe wrote:
> On Thu, 16 Apr 2015 21:11:06 +0100
> Lisi Reisz wrote:
> > But it will be awful the day that Jessie goes Stable because
> > everything will immediately update willy-nilly and out of your
> > control, all at once, to Stretch (which will be the new t
On Thu, 16 Apr 2015 16:25:41 -0500
David Wright wrote:
> Quoting Joe (j...@jretrading.com):
>
> > This upgrade of old Testing to new Testing is the first real-world
> > preview of the *next* Stable upgrade, or at least some of it. I'm
> > sure a lot of thought has gone into preparing for it.
>
On Thu, 16 Apr 2015 21:11:06 +0100
Lisi Reisz wrote:
Hello Lisi,
>But it will be awful the day that Jessie goes Stable because everything
>will immediately update willy-nilly and out of your control, all at
>once, to
I've been using 'testing' (as opposed to codenames) for years without
problem
On Thu, Apr 16, 2015 at 5:25 PM, David Wright wrote:
> Quoting Joe (j...@jretrading.com):
>> On Thu, 16 Apr 2015 21:11:06 +0100
>> Lisi Reisz wrote:
>> > As opposed to problems in a fortnight? If you change all of them,
>> > you will have a whirlwind as soon as Jessie becomes Stable. If I
>> >
Quoting Joe (j...@jretrading.com):
> On Thu, 16 Apr 2015 21:11:06 +0100
> Lisi Reisz wrote:
> > As opposed to problems in a fortnight? If you change all of them,
> > you will have a whirlwind as soon as Jessie becomes Stable. If I
> > were in your shoes, I would change the one reference to testi
On Thu, 16 Apr 2015 21:11:06 +0100
Lisi Reisz wrote:
> On Thursday 16 April 2015 17:05:54 Harry Putnam wrote:
> > My current sources.list:
> >
> >
> > In the first three, if I just change the word `jessie' to `testing'
> > will that work seemlessly or lead to problems?
> >
> > I'm a little loath
On 04/16/2015 04:11 PM, Lisi Reisz wrote:
It's no test at all. At the moment testing and Jessie are the same thing.
But it will be awful the day that Jessie goes Stable because everything will
immediately update willy-nilly and out of your control, all at once, to
Stretch (which will be the ne
On Thursday 16 April 2015 17:05:54 Harry Putnam wrote:
> My current sources.list:
>
>
> ,
>
> | deb http://ftp.us.debian.org/debian testing main contrib non-free
> | deb-src http://ftp.us.debian.org/debian testing main contrib non-free
> |
> | deb http://ftp.debian.org/debian/ jessie-updates ma
On Thu, 16 Apr 2015 12:57:37 -0500
David Wright wrote:
Hello David,
>In which case you don't understand it.
Okay, fair enough. My mistake.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
I hope I live to relive the days gone
Brad Rogers writes:
> On Thu, 16 Apr 2015 17:40:47 +0100
> Darac Marjal wrote:
>
> Hello Darac,
>
>>At the moment, "stable" is a pointer to "wheezy", "testing" points to
>>"jessie" and "unstable" points to sid.
>
> AIUI, that's the wrong way round. Wheezy is a link to stable, jessie
> links to
Quoting Brad Rogers (b...@fineby.me.uk):
> AIUI, that's the wrong way round. Wheezy is a link to stable, jessie
> links to testing, etc.
>
> Consider; old-stable, stable, testing and unstable always exist. The
> code names change meaning and fall out of use over time - with the
> exception of
On Thu, 16 Apr 2015 17:40:47 +0100
Darac Marjal wrote:
Hello Darac,
>At the moment, "stable" is a pointer to "wheezy", "testing" points to
>"jessie" and "unstable" points to sid.
AIUI, that's the wrong way round. Wheezy is a link to stable, jessie
links to testing, etc.
Consider; old-stable
Quoting Harry Putnam (rea...@newsguy.com):
> My current sources.list:
>
>
> ,
> | deb http://ftp.us.debian.org/debian testing main contrib non-free
> | deb-src http://ftp.us.debian.org/debian testing main contrib non-free
> |
> | deb http://ftp.debian.org/debian/ jessie-updates main contrib
On Thu, Apr 16, 2015 at 12:05:54PM -0400, Harry Putnam wrote:
> My current sources.list:
>
>
> ,
> | deb http://ftp.us.debian.org/debian testing main contrib non-free
> | deb-src http://ftp.us.debian.org/debian testing main contrib non-free
> |
> | deb http://ftp.debian.org/debian/ jessie-u
My current sources.list:
,
| deb http://ftp.us.debian.org/debian testing main contrib non-free
| deb-src http://ftp.us.debian.org/debian testing main contrib non-free
|
| deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
| deb-src http://ftp.debian.org/debian/ jessie-up
30 matches
Mail list logo
