Package: gnunet-client Version: 0.8.1b-5+b2 Severity: important Dear Maintainer,
I wanted to have gnunet-chat on this box, so I searched to see which package provides it. A little surprised that it isn't on "gnunet-tools" but on "gnunet-client". I proceeded to install gnunet-client. As you might be aware, gnunet-client depents on gnunet-common, but neither of those need gnunet- tools, so I ended up with both gnunet-client and gnunet-tools installed. After the installation, I tried to use gnunet-chat, by running the command "gnunet-chat". That command fails, stating that it failed to run gnunet-setup. After looking for that binary, I found out that gnunet-setup is indeed not present, and the package that provides it is gnunet-tools, which wasn't installed. In other words, gnunet-client, as it is, doesn't work (at least some of the provided binaries don't - gnunet-chat being the example) unless the gnunet-tools package is installed. Thus, either gnunet-client needs to depend on gnunet-tools (either directly or indirectly), or the binaries that need them should be packaged in gnunet-tools instead of being in gnunet-client. I didn't test this on the version uploaded on experimental, but I did check it's dependencies, and I'm pretty sure that experimental's gnunet-chat still need gnunet-setup... -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.0.0-2-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnunet-client depends on: ii gettext 0.18.1.1-5 ii gnunet-common 0.8.1b-5+b2 ii libadns1 1.4-2 ii libc6 2.13-21 ii libextractor1c2a 1:0.5.23+dfsg-7.1 ii libgcrypt11 1.5.0-3 ii libgmp10 2:5.0.2+dfsg-2 ii libltdl7 2.4.2-1 ii zlib1g 1:1.2.3.4.dfsg-3 gnunet-client recommends no packages. Versions of packages gnunet-client suggests: ii gnunet-server <none> ii libextractor-plugins 1:0.5.23+dfsg-7.1 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
