tag 425533 +wontfix thanks On Tuesday 22 May 2007, you wrote:
> The conflict is not bogus. Seahorse does not work when launched in > gnupg-agent. Yes. it is bogus. Just because there is a need for configuration in order to have both of them work, doesn't warrant a conflict. It is just a 'easy hackaround' for not documenting that users need to do some configuration in order to have them coinstallable. See the last message in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415842 Several http daemons can also be co-installed, even if they can't bind port 80 all of them. (even though it is their default configuration). > This dependency/conflict knot is the only one preventing a full > gnome/KDE parallel install. As I said - blame the ones who introduces the bogus conflict. /Sune -- I cannot cancel a memory of the kernel to the head over a RO mouse, how does it work? From the folder menu inside Windows 96 you never have to install the device, in such way you neither must boot with a ADSL clock, nor should ever click the folder of a site but then you either can't save the USB IDE display to a SCSI code, or have to ping to the 2-inch login on the window on a desktop for unlinking the Fast DLL CPU.
signature.asc
Description: This is a digitally signed message part.