[Steve Langasek] > The s390 buildd maintainer presumes to mark all packages as > 'Not-for-us' if he doesn't feel like building them for the arch, > without bothering to reach a consensus first together with the > maintainer, the ftp masters, or the maintainers of the P-a-s > overrides.
Is the unilateral flagging of not-for-us being addressed in any way? Some options might be to - Change the behavior of the current s390 buildd admin, if required by taking this to the Technical Committee - Replace the s390 buildd admin - Replace the s390 buildd and admin - Drop s390 as a release architecture as it is failing to build packages that previously was build on that architecture. Are any of these or other options being implemented to solve this issue? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
