Bug#366678: apt 0.6.44 changed tagfile code

2006-06-02 Thread Michael Vogt
On Wed, May 24, 2006 at 06:52:32AM +1000, Graham Williams wrote: Received Mon 15 May 2006 9:44pm +1000 from Michael Vogt: [..] 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

Bug#366678: apt 0.6.44 changed tagfile code

2006-05-23 Thread Graham Williams
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

Bug#366678: apt 0.6.44 changed tagfile code

2006-05-15 Thread 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

Bug#366678: apt 0.6.44 changed tagfile code

2006-05-14 Thread Graham Williams
Received Sat 13 May 2006 5:51am +1000 from Michael Vogt: Hi, 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.

Bug#366678: apt 0.6.44 changed tagfile code

2006-05-12 Thread Michael Vogt
Hi, 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