arch all packages not correctly superseded across all architectures

[James Troup]

If foo_1.0-1_all.deb is in the archive and foo 1.0-2 is uploaded which changes the architecture to any, 1.0-1 should be removed from all architectures. Currently soyuz doesn't do this. An extant example is cowbell on hppa, which has 0.2.6.2-0ubuntu1_all in it's Packages file, despite the existence of 0.2.7-1ubuntu3 which is architecture: any (but not yet built for hppa, obviously).

[James Troup (elmo)]

Sorry, on re-reading this isn't very clear. FWIW, the algorithm 'dak make-suite-file-list' uses is:

 o For each suite:
  o For each pkg:
   o If there's no arch_all deb, continue
   o If there's only an arch_all deb, continue
   o [if we got here, we have an arch_all deb and at least one arch_any .deb]
   o Determine the highest version number of the !_all .deb's
   o Compare that version number with the version number of the arch_all deb
    o If the highest arch_any is > the arch_all, remove the arch_all (NB: from all architectures - but that's implicit in the dak database model) copy of the package from this suite
    o If the arch_all > highest arch_any, remove all of the arch_any entries for this package from this suite.

Hopefully that's clearer.

[Celso Providelo (cprov)]

I guess so, however it might have some issues at implementation time, it's a good candidate for Paris discussion. Thank you for the rich feedback.

[James Troup (elmo)]

As I import gutsy into DAK, I'm running into this yet again. It's only a matter of time before this bug leaves an arch: all package with a security vulnerability exposed to some of our users; it'd be good if we could at least get this bug on the roadmap/schedule.

[Celso Providelo (cprov)]

Sorry for letting this fall off the radar. i will try to address this during 1.1.11

[Celso Providelo (cprov)]

RF 5350