Received Mon 15 May 2006 9:44pm +1000 from Michael Vogt: > On Mon, May 15, 2006 at 06:48:04AM +1000, Graham Williams wrote: > > Received Sat 13 May 2006 5:51am +1000 from Michael Vogt: > > > I looked into wajigs code and it turns out that the problem is that > > > the latest apt uses MMap inside the pkgTagFile that is used on a pipe > > > from wajig. This obviously does no longer work. I'll investigate what > > > can be done about it. See #350025 for the rational of that change. > > > > > > There are better (and faster) ways in python-apt nowdays to read the > > > description for packages btw (no need to pipe from apt-cache > > > dumpavail). > [..] > > Looks a bit of a problem with the new apt. I've not had a look at the > > newer python-apt, so any specific pointers are most welcome! > > I was not aware that the pkgTagFile code was used on things like > pipes, otherwise I would have not done the mmap modification in > libapt. If more applications use it this way (and break because of > it), I'll revert it. > > I attach a patch that switches a bit of wajig to use more recent
[...] Thanks again Michael. I've not had a chance to explore the new apt. So for now I've reverted to placing the output of dumpavail into a temporary file. Not the best solution, but the simplest just at present. This bug fix will be in 2.0.33 of wajig after I've tested it a bit more. Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
