Hi Mark, Am Tue, Feb 11, 2025 at 12:01:10PM -0800 schrieb Mark Millard: > It did finish --after 39:49:02 . > > As long as the O(n²) build-time problem exists: Is the > package's build worth the delays to most other package > builds that are done on on any specific builder machine? > > ampere1 cycles through building and distributing: > 141arm64-quarterly > 141releng-armv7-quarterly > 1341arm64-quarterly > 134releng-armv7-quarterly > > ampere3 is similar (default here is a.k.a. latest): > 141arm64-default > 141releng-armv7-default > 1341arm64-default > 134releng-armv7-default > > If the armv7's all have that time problem, the > problem looks to adds days to the time to complete > a cycle of 4 types of builds. > > > The reason why you see this only now is that I have recently pushed a patch > > to fix math/octave on armv7; previously it didn't build.= > > Should the package be considered broken for armv7 until > it is fixed to build in a normal time frame instead of > an O(n²) tiem frame, just because it takes too long as > stands?
Yes, please mark it as broken. It's only a metaport, so no functionality is lost by not providing it. The underlying problem should be fixed. Yours, Robert Clausecker -- () ascii ribbon campaign - for an encoding-agnostic world /\ - against html email - against proprietary attachments
