apt-file Reply-To: In-Reply-To: <20090226160515.gd4...@belanna.comodo.priv.at> X-Debbugs-No-Ack: please
-=| gregor herrmann, Thu, Feb 26, 2009 at 05:05:15PM +0100 |=- > On Thu, 26 Feb 2009 17:11:27 +0300, Ilya Martynov wrote: > > > I tried to build POE::Component::SSLify from CPAN and noticed that > > dh-make-perl cannot find all dependancies for the module using > > apt-file: > > > > i...@denmark:~/tmp/POE-Component-SSLify-0.15$ dh-make-perl > > Found: POE-Component-SSLify 0.15 (libpoe-component-sslify-perl arch=all) > > + perl found in perl > > - Net::SSLeay not found in any package > > I can't reproduce this problem: > > > gre...@belanna:/tmp/perl/POE-Component-SSLify-0.15$ dh-make-perl > Found: POE-Component-SSLify 0.15 (libpoe-component-sslify-perl arch=all) > Parsing > /var/cache/apt/apt-file/ftp.at.debian.org_debian_dists_unstable_Contents-i386.gz > ... > [..] > + perl found in perl > + Net::SSLeay found in libnet-ssleay-perl > > Needs the following debian packages: libnet-ssleay-perl (>= 1.30) > > [..] > > > (And if I ran it a second time the "Parsing /var/cache/..." is > missing as expected but the result is the same.) > > Could you try to "rm ~/.dh-make-perl/Contents.cache" and run > dh-make-perl again? Maybe there is some problem with the cache ... I think I have found the root reason. Hopefuly it is not cache-related. By default dh-make-perl parses only Contents files the distribution part of whose names is either 'sid' or 'unstable'. So on a pure stable (or testing) system, AptContents has nothing to parse and should fail to detect *any* dependency package. I am not very sure why I filtered on distribution at all. Perhaps to avoid false positives when using unofficial repositories, or to save time parsing. OTOH, if these repositories are in sources.list, the admin relies on them so... I think I shall remove the filtering and see what happens. -- dam JabberID: d...@jabber.minus273.org
signature.asc
Description: Digital signature
