Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes: > The problem is that there are now two source packages which produce the same > binaries. How can an autobuilder know which of the two should be build? Well, to Ben's credit it should be said that this problem is somewhat peculiar to turtle. AFAIK the other autobuilder just pick up whatever source packages are uploaded in roughly FIFO fashion, compile, upload, and forget about them. The db -> db2 renaming will be hardly noticable there. That the last version of "db" failed to build on the Hurd, and therefore got stuck in the "failed" state contributed to the mess. Maybe turtle could be extended to at least detect this kind of overlap. An automatic solution could only work heuristically -- you're right that source versions are not always equal[1], but in 99 % of the cases they are. Footnotes: [1] gcc-defaults 0.5 produces gcc 1:2.95.3-5 -- Robbe
Attachment:
signature.ng
Description: PGP signature