Oh, they were all in NEW because of a kernel ABI bump, producing new binaries. They've since all been processed, of course. Your example above still hilights the problem I'm referring to, however:
If I pick a random package that appears in all the binary uploads (say, linux-libc-dev), I get filter returns for all the binary uploads. If I filter on linux-source-2.6.17, I get the source package, and the one binary upload that produced a binary package by that name (I would expect to get all the binary uploads for the source package "linux-source-2.6.17")
Oh, they were all in NEW because of a kernel ABI bump, producing new binaries. They've since all been processed, of course. Your example above still hilights the problem I'm referring to, however:
If I pick a random package that appears in all the binary uploads (say, linux-libc-dev), I get filter returns for all the binary uploads. If I filter on linux-source- 2.6.17, I get the source package, and the one binary upload that produced a binary package by that name (I would expect to get all the binary uploads for the source package "linux- source- 2.6.17" )