From: MENGUAL Jean-Philippe <mengualjeanphi@free.fr>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Update Edbrowse
Date: Sat, 23 Aug 2014 15:47:50 +0200 [thread overview]
Message-ID: <53F89B86.2090100@free.fr> (raw)
In-Reply-To: <20140823133611.GS2748@toaster.adamthompson.me.uk>
I'm going to have alook at this, since at the last time of checking, the
js 31 package (from experimental) contained a broken symlink in place of
jsapi.h. Also, do you know of any docs for mozjs 31, as all docs on the
mozilla website talk about mozjs 24.
The situation of JS support in Mozilla 31 is not clear for me. That is
why I filled bug 758928 on Debian about libmozjs, so that the maintainer
could explain to me the situation. We can also write to
icedove-dev@packages.debian.org to contact the maintainers and asking.
It's my next task if no an]ier on my "bug" report.
>> After checking, freeze happens on November. So:
>> 1. Do you want now to work on compatibility with JS 31?
>> 2. Otherwise, I propose we wait end of September to be sure Edbrowse builds
>> on any architecture without problem. Next, you could release in 1st 15 days
>> of October. Then I could introduce the released package in sid (October,
>> 15th), and it willl go to testing (and be frozen) on Octoberb 25th.
>> Does it fit? Do you want a more restricted schedule?
> The timings sound fine to me provided the new edbrowse package runs correctly.
> Incidentally, I'd be interested to see how you built this as the last time I
> tried against a Debian packaged mozjs it segfaulted as soon as you attempted to run it.
You can see the package with apt-get source edbrowse. I think it ships
the debian/ dir. See rules file to see what happens. If you want to try
seeing exactly what does dh-auto_build, you can run pdebuild or
dpkg-buildpackage and you will see the commands it run (as it displays
make output).
I do not any particular thing, but I rely on libmozjs24.0 package, which
seems more reliable. That's also why I wait for September 15th, to see
if someone has a segfault or if the Debian Release team find a conflict
with a Mozilla tool (that is why it was removed from Debian). Feedbacks
will enable to test now it works. Maybe the libmozjs had a successful
update.
Regards,
>
> Cheers,
> Adam.
--
Jean-Philippe MENGUAL
accelibreinfo, votre partenaire en informatique adaptée aux déficients visuels
Mail: texou@accelibreinfo.eu
Site Web: http://www.accelibreinfo.eu
next prev parent reply other threads:[~2014-08-23 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 17:39 MENGUAL Jean-Philippe
2014-08-22 20:32 ` Adam Thompson
2014-08-22 20:43 ` MENGUAL Jean-Philippe
2014-08-22 22:11 ` Chris Brannon
2014-08-23 13:02 ` MENGUAL Jean-Philippe
2014-08-23 13:36 ` Adam Thompson
2014-08-23 13:47 ` MENGUAL Jean-Philippe [this message]
2014-08-30 15:11 ` Adam Thompson
2014-09-01 18:36 ` MENGUAL Jean-Philippe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F89B86.2090100@free.fr \
--to=mengualjeanphi@free.fr \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=arthompson1990@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).