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

Bug#275852: marked as done (pkgTagFile::Step fails on large Release files)

Your message dated Wed, 25 Nov 2009 21:38:22 +0100
with message-id <c64043e60911251238k32bd2d6fic2aa3ca359bd2f9c@mail.gmail.com>
and subject line pkgTagFile::Step fails on large Release files - still?
has caused the Debian Bug report #275852,
regarding pkgTagFile::Step fails on large Release files
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 owner@bugs.debian.org
immediately.)


-- 
275852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275852
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: python-apt
Version: 0.5.10
Severity: normal


When you do
parse = apt_pkg.ParseTagFile('/srv/debian.org/debian/dists/sid/Release')
parse.Step()

it fails on the Step(), where it will succeed on woody, etc.

Investigation shows that removing the 'hurd-i386' lines from the
MD5Sum: sections results in it working.

-- System Information:
Debian Release: 3.1
  APT prefers experimental
  APT policy: (990, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to ga_IE.UTF-8)

Versions of packages python-apt depends on:
ii  apt [libapt-pkg-libc6.3-5-3 0.5.27       Advanced front-end for dpkg
ii  apt-utils [libapt-inst-libc 0.5.27       APT utility programs
ii  libc6                       2.3.2.ds1-17 GNU C Library: Shared libraries an
ii  python                      2.3.4-4      An interactive high-level object-o

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 0.6.45

Hi Christian Aichinger & Alastair McKinstry,

as the Release files are now (much) bigger than 32kb and
it doesn't seem to be reproducible anymore i am closing the
bug now, but feel free to reopen it if this bug is really still
reproducible!

btw: Thanks Christian Aichinger for your patch!
It seems as Michael Vogt has fixed it in a different way by let
Fill() ensure that the buffer always ends with a double newline
in rev 1416.1.109 of the official debian-sid branch.


Best regards / Mit freundlichen Grüßen,

David "DonKult" Kalnischkies

--- End Message ---
Reply to: