On Thu, Jul 23, 1998 at 06:04:45PM +0100, Philip Hands wrote: > > On Thu, Jul 23, 1998 at 05:26:27PM +0100, Philip Hands wrote: > > > According to Brian, we're ignoring the X bug (see below) > > >=20 > > > If there's a reason that that is a Bad Idea, he should probably be told. > > > > No. > > > > But Philip: please make a Readme on the cdrom about this bug. > > Can someone tell me what the Problem/Solution is, I've lost track I hoppe, I have the right bug. xbase has two important bugs (24816 and 24836) and the bugs are the same bug. See http://www.debian.org/Bugs/db/24/24836.html.: # Package: xbase # Version: 3.3.2.2-3 # Severity: important # # Hi, # # When upgrading xbase with dselect/apt, I was asked at some point if I # wanted to stop xdm. Because stopping the xdm session would mean aborting # apt that was running the very upgrade procedure, I chose "n". After a # second, the entire X session, including all xterms and other running # X clients was torn down nevertheless and I was back at the console. # Needless to tell that this was very surprising. # # I'm setting the Severity: to important because this "Feature" causes # data loss (the data stored in all open X apps and xterms that are # unexpectedly killed.) # # The good news is that everything seems to run okay after (re)running # dselect/apt's configure and install methods. The bug is important. But it is only a bug, if you update xbase. A new debian user don't see the bug. And a old debian-user read the README. all right? Grisu
Attachment:
pgp5ZCQdvqF9J.pgp
Description: PGP signature