Using bug report database

When I run dpkg-scanpackages to update my local repository databases, I got this error messages:

Can’t locate IO/ in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/bin/dpkg-scanpackages line 23.
BEGIN failed–compilation aborted at /usr/bin/dpkg-scanpackages line 23.

What was that mean? I don’t understand, but I know where to find the information about that, it is bug report.

$ dpkg -S /usr/bin/dpkg-scanpackages
dpkg-dev: /usr/bin/dpkg-scanpackages
$ querybts dpkg-dev
Querying Debian BTS for reports on dpkg-dev…

(1-7/70) What would you like to do next [N|b|m|r|q|f|?]? f
Enter the search pattern (a Perl-compatible regular expression)
or press ENTER to exit: dpkg-scanpackages
Outstanding bugs — Wishlist items; Unclassified (35 bugs): 1 report
1) #308560 [DPKG-SCANPACKAGES] add exclude and include options
Resolved bugs — Normal bugs (8 bugs): 2 reports
2) #494136 dpkg-scanpackages: Does not scan user defined fields from packages that were given in the contro
3) #557013 dpkg-dev: dpkg-scanpackages doesn’t find IO/

I searched for “dpkg-scanpackages” keyword, and there’s one result bug #557013 which looks like the one I’ve experienced with.

From the explanation, it is known that to avoid such error like that, we can install libio-string-perl package. Umm, obviously this package hasn’t installed in my system, but without this package in the past, it was smooth with dpkg-scanpackages, wasn’t it? To me this is indeed a real bug. Thankfully, by reading all the related bug reports and the quick answer from the devs, finally there is one solution to this, that the maintainer urges us to upgrade to the latest dpkg-dev, which is version

OK, let’s check this package’s status:

$ apt-cache policy dpkg-dev
Installed: 1.15.5
Version table: 0
500 unstable/main Packages 0
500 unstable/main Packages
*** 1.15.5 0
100 /var/lib/dpkg/status

Yes, it seems that I have missed two versions. So, with no hesitate at all, I upgrade the dpkg-dev package. And after that, I once again run the dpkg-scanpackages, and the error is disappeared.

The point of this story is what should we do at the very first time when we deal with such error or unproper circumstances in the system. The very first time of course is to look at the bug reports of the distro we used. Just point the browser, or with specific command like querybts in Debian, then we will be able to dive into the bug report databases.

Tags: ,


Leave a Reply

XHTML: You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>