Package: sparkleshare Version: 0.6.0-1 Severity: normal By silently changing my identity file sparkleshare rendered all my other ssh accesses inoperational. That scared me quiet a bit for a moment. I would much ruther see sparkleshare use the normal ssh credentials as it does without that line in .ssh/config. I think upstream should simply correct the path they give in their interface or check, wether there already is a key and use that if its there.
Best regards Kai -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sparkleshare depends on: ii git 1:1.7.8.3-1 ii gnome-icon-theme 3.2.1.2-1 ii gvfs 1.10.1-2 ii libc6 2.13-24 ii libglib2.0-cil 2.12.10-2 ii libgtk2.0-cil 2.12.10-2 ii libmono-corlib2.0-cil 2.10.5-2 ii libmono-posix2.0-cil 2.10.5-2 ii libmono-system2.0-cil 2.10.5-2 ii libnotify0.4-cil 0.4.0~r3032-4 ii libwebkit1.1-cil 0.3-5 ii mono-runtime 2.10.5-2 sparkleshare recommends no packages. sparkleshare suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
