[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#228379: gcj: contains badly broken filename



On Sun, Jan 18, 2004 at 06:33:21PM +0100, Wouter Verhelst wrote:

> Not sure whether this is actually a gcj bug or a dpkg one, but it's
> ugly:
> 
> Removing gcj-3.3 ...
> dpkg: error processing gcj-3.3 (--purge):
>  cannot remove `/home/buildd/build/chroot-unstable/usr/share/man/man1/m68k-linux-gcj-3.3.1.gzGSKYOUt.gzbian.gzlder.classssclassdapter.classslassssompositeContext.classn.org>
> Source: python-gtk2
> Version: 2.0.0-3
> Replaces: python2.2-gtk2 (<< 1.99.17-4), python2.3-gtk2': File name too long
> 
> if you need any further information, please let me know.
> 
dpkg CVS HEAD seems to already NULL-terminate this buffer, but the fix
never made it back onto the stable branch.  I suspect that nobody
actually noticed it when they rewrote that bit of code, the log message
for the revision isn't that helpful :(

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: Digital signature


Reply to: