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.

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.

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

Pkg-javascript-devel mailing list

Reply via email to