On Thu, 13 Mar 2003 13:00:25 -0500
Joey Hess <[EMAIL PROTECTED]> wrote:
> Richard Kimber wrote:
> > Actually, this is ambiguous, because "local changes must be preserved"
> > can both mean "backed up" (which is what happened in my xinetd case)
> > and"remain active", which is what I think should h
Richard Kimber wrote:
> Actually, this is ambiguous, because "local changes must be preserved" can
> both mean "backed up" (which is what happened in my xinetd case) and
> "remain active", which is what I think should happen.
The rest of the section clarifies it pretty well I think.
--
see shy j
On Wed, 12 Mar 2003 19:51:34 -0500
Joey Hess <[EMAIL PROTECTED]> wrote:
> Any package in debian that, during installation or upgrade, loses
> changes you have locally made to a config file is broken. A bug report
> of severity serious should be filed on it for its violation of debian
> policy, sec
Hall Stevenson wrote:
> I *believe* you can configure debconf to NOT overwrite existing config
> files, automatically overwrite them, or prompt you before doing so.
debconf is a system for asking questions. It has nothing to do with
config files. It does not modify config files.
Any package in
Thanks very much to all who responded and contributed to the
discussion.
I did the upgrade, and have experienced no problems at all so far.
Nice,
Jim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, 12 Mar 2003 15:09:44 -0500
Hall Stevenson <[EMAIL PROTECTED]> wrote:
>
> I *believe* you can configure debconf to NOT overwrite existing config
> files, automatically overwrite them, or prompt you before doing so. With
>
> either of the last two options, it will still create a backup of
On Wed, Mar 12, 2003 at 03:09:44PM -0500, Hall Stevenson wrote:
> At 07:47 PM 3/12/2003 +, Richard Kimber wrote:
> >I've upgraded, and only noticed two things.
> >
> >1) My xinetd.conf file was overwritten without asking me, which I don't
> >feel is right, and
>
> I *believe* you can configure
At 07:47 PM 3/12/2003 +, Richard Kimber wrote:
I've upgraded, and only noticed two things.
1) My xinetd.conf file was overwritten without asking me, which I don't
feel is right, and
I *believe* you can configure debconf to NOT overwrite existing config
files, automatically overwrite them,
On Wed, 12 Mar 2003 18:27:03 +
Colin Watson <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 12, 2003 at 11:41:52AM -0600, Brooks R. Robinson wrote:
> > Jim McCloskey wrote:
> > | I expected to see all sorts of messages here about difficulties with
> > | testing after the migration of glibc 2.3.1-14.
On Wed, Mar 12, 2003 at 11:41:52AM -0600, Brooks R. Robinson wrote:
> Jim McCloskey wrote:
> | I expected to see all sorts of messages here about difficulties with
> | testing after the migration of glibc 2.3.1-14.
> |
> | Hardly anything, though.
> |
> | I've been holding back from the upgrade til
| I expected to see all sorts of messages here about difficulties with
| testing after the migration of glibc 2.3.1-14.
|
| Hardly anything, though.
|
| I've been holding back from the upgrade till things settle down.
|
| Are there any brave souls who went ahead and upgraded and have the
| time to
Jim McCloskey wrote:
I expected to see all sorts of messages here about difficulties with
testing after the migration of glibc 2.3.1-14.
Hardly anything, though.
I've been holding back from the upgrade till things settle down.
Are there any brave souls who went ahead and upgraded and have the
tim
On Tue, Mar 11, 2003 at 04:49:19PM -0800, Jim McCloskey wrote:
|
| I expected to see all sorts of messages here about difficulties with
| testing after the migration of glibc 2.3.1-14.
|
| Hardly anything, though.
|
| I've been holding back from the upgrade till things settle down.
|
| Are ther
13 matches
Mail list logo
