Le lundi 28 juillet 2025, 16:37:15 CEST Paul Tagliamonte a écrit : > One of the first things that jumped out was the way in which this > package builds. IIRC, the android ndk (due to being out of date in > Debian[1]) was downloaded at build-time. All builds (even nonfree!) > should be building without network. For main and contrib this > would be a hard reject. I think we'd apply the same standard for > non-free. From what I understood, non-free packages are usually not built by the Debian infrastructure unless we use "XS-Autobuild: yes" in d/control. So I though that usually, for non-free packages, the maintainer uploads both the source and binary packages. So the "building without network" would not be an issue. > If the NDK can't be updated (or this be changed) due to > distributibility issues, that's also something that would need fixing :) [...] > [1]: Someone should really file a RoM or RoQA on that package Actually the NDK is not in the archive yet. I started to work on it but it's a big package given that it depends/ships a custom llvm/clang (ie. with Android/ Google specific changes). I created an RFP at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109642 Regards Fab
Attachment:
signature.asc
Description: This is a digitally signed message part.