Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc.

2010-09-09 Thread Josselin Mouette
Le mercredi 08 septembre 2010 à 13:02 -0700, Paul Taylor a écrit : Hi Josselin: Thanks for your reply. Here is what I get when I enter the command you suggested: gnome-control-center: Depends: evolution-data-server but it is not going to be installed Does gnome-control-center actually

Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc.

2010-09-09 Thread Paul Taylor
Hi Josselin: Thanks again. Looking at bug 592525 I begin to see how dependency creep happens. --- On Thu, 9/9/10, Josselin Mouette j...@debian.org wrote: From: Josselin Mouette j...@debian.org Subject: Re: Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome

Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc.

2010-09-08 Thread Paul Taylor
j...@debian.org wrote: From: Josselin Mouette j...@debian.org Subject: Re: Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc. To: PolicyKit jenningsthe...@yahoo.ca, 595...@bugs.debian.org Received: Sunday, September 5, 2010, 10:26 AM Le

Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc.

2010-09-05 Thread Josselin Mouette
Le mardi 31 août 2010 à 16:19 -0400, PolicyKit a écrit : I just did a full-upgrade, and was forced to either accept the addition of evolution-data-server or not complete the upgrade. (I ran aptitude with the ''-R' switch, but it made no difference). As far as I know nothing else I have

Bug#595070: Attempting to uninstall evolution-data-server forces removal of gnome-core, gnome-panel, etc.

2010-08-31 Thread PolicyKit
Package: gnome-core Version: 1:2.30+1 Severity: normal I'm filing this bug against gnome-core because I wasn't sure where to put it.The bug also relates to other gnome packages as listed below. For the first complaint related to this issue, please see Bug Report #563484. I just did a