On Mon, May 05, 2008 at 09:50:22AM -0700, Kevin B. McCarty wrote:
> Package: dictionaries-common
> Version: 0.98.5
> Severity: normal
> 
> Hi,
> 
> During an upgrade of my sid chroot, dictionaries-common 0.98.5 was
> pulled in by myspell-en-us (which was pulled in by libhunspell-1.2,
> which was pulled in by iceweasel).  The dictionaries-common package was
> not previously installed.
> 
> The following messages were printed from the postinst script:
> 
> > Setting up dictionaries-common (0.98.5) ...
> > readdir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 143, <STDIN> line 2.
> > closedir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 144, <STDIN> line 2.
> > readdir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 143, <STDIN> line 2.
> > closedir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 144, <STDIN> line 2.
> > readdir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 143.
> > closedir() attempted on invalid dirhandle DIR at 
> > /usr/share/perl5/Debian/DictionariesCommon.pm line 144.
> > Updating OpenOffice.org's dictionary list... done.
> 
> It's possible that the warnings have something to do with the upgrade to
> perl 5.10, as the dictionaries-common postinst was run after perl
> 5.10.0-9 preinst and unpacking, but before perl postinst.

Thanks for reporting,

I could not reproduce this with perl 5.8.8, so I guess this is indeed
related to perl 5.10.

I could not yet upgrade perl to 5.10 because of a dependency problem of
libdbd-sqlite3-perl and libft-perl, so I will have to wait for tomorrow. If
things are not fixed I will remove things depending on them and retry.

In the meantime, I have looked at what seems to be the relevant code
(in the updatedb function) and I plan to change it anyway to use globbing. I
expect that will make code easier to read and as a side effect fix this bug.

Regards,

-- 
Agustin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to