Your message dated Fri, 30 May 2014 10:50:32 +0400 with message-id <[email protected]> and subject line Re: Bug#749774: [eiskaltdcpp-gtk3] Package description suggests nonexistent package has caused the Debian Bug report #749774, regarding [eiskaltdcpp-gtk3] Package description suggests nonexistent package to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 749774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749774 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: eiskaltdcpp-gtk3 Version: 2.2.9-3+b1 Severity: minor --- Please enter the report below this line. --- Hi there, the package description mentions that one should install eiskaltdcpp-gtk-unstable if one experiences problems with the -gtk3 package, but eiskaltdcpp-gtk-unstable is not in the archive. I guess eiskaltdcpp-gtk is meant instead. Cheers - Fuddl --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 unstable ftp.de.debian.org 1 experimental ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---Hi, > the package description mentions that one should install > eiskaltdcpp-gtk-unstable if one experiences problems with the -gtk3 > package, but eiskaltdcpp-gtk-unstable is not in the archive. I guess > eiskaltdcpp-gtk is meant instead. Sorry, but your assumption is wrong: 1) Package description say nothing about *-unstable packages. 2) *-unstable packages are packages with daily builds of the program, and they should not be present in official archive. 3) If you look into file [1] you will find that the main idea is the preventing possible troubles on users systems when they are switching from packages with daily builds to stable packages from main archive. (There were few such cases in the past.) [1] https://github.com/tehnick/eiskaltdcpp-debian/blob/master/debian/control Best regards, Boris
--- End Message ---
