On Sun, Dec 28, 2003 at 04:53:53PM -0500, Colin Walters wrote: > On Fri, 2003-12-26 at 11:26, Matt Zimmerman wrote: > > > I found this bug; it was here (srcrecords.cc): > [...] > > Ah, good catch. My C++-fu is weak. I had tried valgrind, but it only > gave me an error much later.
For some reason it became unreproducible shortly after I found it the first time, so I assumed I had messed up my build. It wasn't until it resurfaced recently that I tracked it down. I just ran into another issue that I'd appreciate some input/background on. It appears that while apt 0.5 retrieves the per-section Release files (e.g., dists/stable/main/binary-i386/Release), apt 0.6/apt-secure only retrieves the top-level one (e.g., dists/unstable/Release). LoadReleaseInfo still tries to read the per-section file, which isn't there because it was never downloaded, and so things like pinning are broken. Was the intention to move away from per-section Release files, and to only use the top-level one? Or was this an oversight, and we should be downloading these files and continuing to use them? -- - mdz
