Oliver Falk wrote:
Thorsten Leemhuis schrieb:
Dennis Gilmore schrieb:
[...]
if a build fails on a secondary arch then it will not affect the
primary arch.
I agree with this scheme, but nevertheless one note: In this case it
IMHO would be nice to normally(¹) give the secondary arch maintainers a
small chance (three to seven days maybe?) to fix packages before the
primary arch packages hit the repo to prevent this:
day 0: foo-1.0.1-7 in the repos for i386, x86_64, ppc, sparc, ia64
day 1: foo-1.2.0-1 gets submitted to buildsys; fails on sparc and ia64;
package gets pushed to the i386, x86_64 repos nearly immediately
day 2: foo-1.2.0-2 fixes build on sparc and gets pushed to the i386,
x86_64 and sparc repos
day 3: foo-1.2.0-3 fixes build on ia64 and gets pushed to the i386,
x86_64 sparc and ia64 repos
Users of i386 and x86_64 that update daily would have had two package
updates without any benefit for them :-( I'd like to aoid that if easily
possible.
Just my 2 cent.
Thorsten; Very good point, didn't even think about this possibility...
Maybe some extra step from (co-)maintainers and/or sub-arch
maintainers is needed here to finally push the package!?
Does the secondary arch sig actually exist yet? Sounds like we have a
fair number of arch's and people now that it would be good for them to
teamup.
-Mike
