Dimitri Maziuk wrote:
> * Kevin C. Smith ([EMAIL PROTECTED]) spake thusly:
> > On Sun, Dec 09, 2001 at 08:17:05PM -0500, David Z Maze wrote:
> > > Jeffrey W Baker <[EMAIL PROTECTED]> writes:
> > > JWB> Today's update to X in unstable overwrote my XF86Config-4 without
> > > even
> > > JWB> asking
* Kevin C. Smith ([EMAIL PROTECTED]) spake thusly:
> On Sun, Dec 09, 2001 at 08:17:05PM -0500, David Z Maze wrote:
> > Jeffrey W Baker <[EMAIL PROTECTED]> writes:
> > JWB> Today's update to X in unstable overwrote my XF86Config-4 without even
> > JWB> asking permission. My config file was very twe
On Sun, Dec 09, 2001 at 08:17:05PM -0500, David Z Maze wrote:
> (Reading/filing reports in the Debian BTS tends to be a far more
> effective way of getting problems fixed than asking about them on
> debian-user; a fair number of developers don't read debian-user at
> all, and so your problem will n
On Sun, Dec 09, 2001 at 08:17:05PM -0500, David Z Maze wrote:
> Jeffrey W Baker <[EMAIL PROTECTED]> writes:
> JWB> Today's update to X in unstable overwrote my XF86Config-4 without even
> JWB> asking permission. My config file was very tweaked. Why does this
> JWB> happen?
It's backed up in /etc
Jeffrey W Baker <[EMAIL PROTECTED]> writes:
JWB> Today's update to X in unstable overwrote my XF86Config-4 without even
JWB> asking permission. My config file was very tweaked. Why does this
JWB> happen?
See Debian bug #123053 (serious).
(Reading/filing reports in the Debian BTS tends to be a f
On Sun, 2001-12-09 at 12:48, Jeffrey W. Baker wrote:
> Today's update to X in unstable overwrote my XF86Config-4 without even
> asking permission. My config file was very tweaked. Why does this
> happen?
Before I get the obvious response to this, I know about the ##BEGIN BLAH
BLAH BLAH ### secti
6 matches
Mail list logo