Re: Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
On Wed, Mar 29, 2000 at 04:37:41PM -0600, Brian Boonstra wrote: Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. According to the docs, you don't need that any more. Just remove the line 'check-local-xserver' from your /etc/X11/xdm/xdm.options. The short explanation is somewhere in the /usr/doc/xserver-common/changelog.Debian.gz file. Reasonable, but that doesn't really help /etc/init.d/xdm. I've changed /etc/init.d/xdm by hand for now, but I doubt this is what the maintainers meant for *everyone* to do. It worked fine when i upgraded. Perhaps you had previously changed /etc/init.d/xdm, and then didn't replace it when installing the new version of xdm? That would leave you with the old file, still looking for parse-xf86config. parse-xf86config was removed in xfree86 3.3.6-4. changelog.Debian explains why. Maybe I somehow ended up with a broken xserver-common? That would explain the bad init script, I guess. /etc/init.d/xdm is in xdm, not xserver-common ;) -- finger for GPG public key. pgpthlSaHPrVG.pgp Description: PGP signature
Re: Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
On Wed, Mar 29, 2000 at 08:24:59AM -0800, tjm wrote: Brian Boonstra wrote: Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. According to the docs, you don't need that any more. Just remove the line 'check-local-xserver' from your /etc/X11/xdm/xdm.options. The short explanation is somewhere in the /usr/doc/xserver-common/changelog.Debian.gz file. Hi, this means that some dependency is broken. The offending packages should conflict with their predecessors. Maybe someone could file a bug report. Bye, Jens
Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
Hi Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. Any clues as to how I can get it back? - Brian
Re: Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
Brian Boonstra wrote: Hi Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. Any clues as to how I can get it back? - Brian Yeah, I noticed that too. It seems that parse-xf86config has been removed from xserver-common (and removed altogether). My kdm init script was complaining. I just changed the kde.config(?) file to not check for or parse an XF86Config file. Probably not the best solution, but it works. Maybe Brandon will respond and tell us what the future is for this. dyer
Re: Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
Brian Boonstra wrote: Hi Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. Any clues as to how I can get it back? - Brian According to the docs, you don't need that any more. Just remove the line 'check-local-xserver' from your /etc/X11/xdm/xdm.options. The short explanation is somewhere in the /usr/doc/xserver-common/changelog.Debian.gz file. -- tony mollica [EMAIL PROTECTED]
Re: Woody: missing parse-xf86config? /etc/init.d.xdm wants it!
Something blew away a program called parse-xf86config this weekend. I suspect it was when I did my apt-get upgrade. This is a problem because /etc/init.d/xdm won't run properly without it. According to the docs, you don't need that any more. Just remove the line 'check-local-xserver' from your /etc/X11/xdm/xdm.options. The short explanation is somewhere in the /usr/doc/xserver-common/changelog.Debian.gz file. Reasonable, but that doesn't really help /etc/init.d/xdm. I've changed /etc/init.d/xdm by hand for now, but I doubt this is what the maintainers meant for *everyone* to do. Maybe I somehow ended up with a broken xserver-common? That would explain the bad init script, I guess. - Brian
