The m68k buildd was choking on logrotate due to a gcc internal error in gcc-3.3. I've been pestered into ensuring that 3.7 gets into sarge [m68k]. All other arches are up-to-date in sarge. Only m68k has a much older revision, due to the gcc error. What I've done is to compile a binary-only upload on crest using gcc-3.0 and uploaded it to incoming today. As the changelog shows "low" priority, what's the chances of logrotate_3.7-2_m68k.deb getting into sarge? (Logrotate is "Priority: important") -- Paul Martin <pm@debian.org>
Attachment:
signature.asc
Description: Digital signature