2009/2/6 Francesco Pietra :
> Does the likely presence of corrupted X files hinder a clean unistalling?
If by "corrupted" you mean configuration files left behind (default
action) you can add "--purge" on the end of your aptitude or apt-get
command to also remove config files, nothing is left beh
On Thu, Feb 05, 2009 at 04:19:07PM +0100, Francesco Pietra wrote:
> May I ask advice to remove completely X - without leaving broken
> packages - from a multisocket server running on debian amd64 lenny,
> kernel 2.6.26?
>
> Is it enough to purge remove the packages "xorg" and "xbase-clients"?
If
On 02/05/2009 09:19 AM, Francesco Pietra wrote:
Hi:
May I ask advice to remove completely X - without leaving broken
packages - from a multisocket server running on debian amd64 lenny,
kernel 2.6.26?
Is it enough to purge remove the packages "xorg" and "xbase-clients"?
And maybe a few others
Hi:
May I ask advice to remove completely X - without leaving broken
packages - from a multisocket server running on debian amd64 lenny,
kernel 2.6.26?
Is it enough to purge remove the packages "xorg" and "xbase-clients"?
Does the likely presence of corrupted X files hinder a clean unistalling?
On Tue, 20 Apr 2004 18:05:33 +0200, Vincent Lefevre wrote:
> Why does "apt-get dist-upgrade" prefer removing x-window-system-core to
> upgrading it?
Looks like you're doing a dist-upgrade to testing... I
generally don't do that, testing often has broken d
Why does "apt-get dist-upgrade" prefer removing x-window-system-core
to upgrading it?
ay:~> sudo apt-get dist-upgrade -s
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages will be REMOVED:
x-window-system-core xlibmesa3
6 matches
Mail list logo