2016-06-18 20:38 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > Quoting Jérémy Lal (2016-06-18 20:20:24) > > 2016-06-18 14:47 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > > > > > Quoting Jérémy Lal (2016-06-18 14:16:11) > > > > > Update: v8 has dropped armv5 support, see > > > > > https://github.com/nodejs/node/issues/5810 > > > > > https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk > > > > > I'm going to remove "armel" from the list of Architectures. > > > > > > > > And as usual, i'm completely lost when it comes to that part. It's > easy > > > to > > > > do something, > > > > but i don't understand clearly all the consequences on existing armel > > > > packages that depend > > > > or build-depend on nodejs; > > > > - should i whitelist in debian/control Architecture field ? > > > > it seems error-prone since i must be sure i'm not forgetting any > official > > > > arch, and blacklisting > > > > is not possible ("any -armel" would have been so cool, though). > > > > - should i leave architecture "any", and ask removal of nodejs/armel > from > > > > testing then artificially > > > > make it fail when building on armel ? > > > > > > No matter if also doing other things, we must request removal, for > > > nodejs itself and also for all arch-any reverse dependencies of nodejs. > > > > > > > Agreed. > > > > > > > Marking in source that the package is not targeted armel at all is a > > > nice thing to do but not essential, as I understand it. > > > > > > Some mecanism must be set to prevent building on armel, because actual > > buildd armel servers are armv7 and as such are supported by nodejs >= 4. > > Not sure I understand what you are saying here. > > If a buildd succesfully compiles code which does *not* request any ARMv6 > or ARMv7 features (e.g. hardfloat or neon), then is there any problem at > all?!? > > > > Otherwise it is right that only removing nodejs and reverse deps from > > testing would be enough. > > If you really want, you can add a build rule to explicitly fail, but > please elaborate why that would be necessary. > > armel is >= armv5t but v8 now supports only >= armv7, which is also the kind of cpu the build servers have. This bug was reported by a user having a armv5 cpu.