On 2018/01/24 22:42, Sylvestre Ledru wrote:
On 24/01/2018 08:08, ISHIKAWA,chiaki wrote:
The following issue related to npm package affects only a subset of
mozilla developers: only the patch contributors who develop on their
PCs that run Debian GNU/Linux.
|mach bootstrap| to set up the development tools and niceties fails
now under Debian GNU/Linux.
This is because "npm" package is no longer in the standard package
archive :-(
Could you please report a bug?
Mark added npm as a dependency on Debian [1], as I run Debian unstable,
I didn't see it wasn't available for stretch or testing.
Sorry about that.
I also reported a bug on Debian side [2] so that it is clear that npm
needs love in Debian.
Cheers,
Sylvestre
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1424921
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888272
I will report a bugzilla.
Yes, I think npm nees supporters on Debian repository management now
that it seems to be used in many applications so much so that I find
them quite unexpected very often as in the case of mozilla build (!).
After an upgrade of mozilla source tree in December (the first after
late summer) and OS upgrade, I encountered many issues.
- blessing bug or an issue:
I have reported it now.
https://bugzilla.mozilla.org/show_bug.cgi?id=1432867
- then strange missing files issue when I enable official-branding
ac_add_options --enable-official-branding
The following closed bug is for M-C portion of the tree.
https://bugzilla.mozilla.org/show_bug.cgi?id=1416968
But I found that there is an issue on C-C tree side, too.
We are missing under the directory
comm-central/other-licenses/branding/thunderbird
two files
mailicon48.png
mailicon64.png
jar.mn modified in December refers to these files.
I said "strange missing files" because I thought these files are
supposed to have been
added to the tree,
https://bugzilla.mozilla.org/show_bug.cgi?id=1417334
But maybe the testing with official-branding enabled was not done.
- There could have been a few other issues before I could finally run
|mach build|, but now I can finally.
Then I am seeing tons of compiler error messages that basically says
ISO C++
does not allow certain things in constant expression (I am afraid
clang is too lenient on this) from GCC, and then I got segfault from
clang-4 when I switched to clang to see how it goes on clang side.
clang-5 still spews out many error message. I have no idea what is going
on with C-C tree right now. I will check with dev-apps-thunderbird ML
after I report the few unreported issues including this one in this mail
thread.
TIA
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
