Hello Luke Faraone and the rest of the (still named? ;P) FTP Team. This followup on your rejection mail available at: http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/2017-August/136005.html
I understand your pain in reviewing this, but was hoping for some understanding of our situation. I don't see accepting libmozjs52 despite its inferiour debian/copyright file as a real problem for Debian. We're already shipping this bundled in the firefox package and this is where the copyright file comes from. In other words, firefox is already opening Debian up for anything by shipping an inferiour copyright file. Rejecting libmozjs52 for this reason doesn't save Debian from any potential harm. Noone involved in pkg-gnome really like having to deal with libmozjs at all and we've tried our best to convince gjs upstream of switching to something else, but they unfortunately think they need and like the mozilla extensions. We don't have any volunteers that want to take on the task of updating debian/copyright, so at the moment we'll just have to wait until someone updates firefoxes version and copy it over again. The problem is that we don't know if firefox will ever do that since they already passed though NEW. We where aiming for packaging the GNOME 3.26 BETA release so that we can bring up any issues we find before the final 3.26 release with upstream. I hope you can relate with everyone reporting minor issues after we've already shipped a debian stable release. It would be much better if everyone tested and reported during freeze, right? Unfortunately this unexpected problem stops us from updating the core components and since upstream doesn't support mixing versions (and we don't have the resources to try to reproduce every problem every user hints at in a vague bug report) we're pretty much stuck. Is there any way forward for us other than just waiting and praying? Could you make a compromise given we already ship the same thing in the archive already? Regards, Andreas Henriksson
