On Wednesday, July 08, 2015 09:03:45 AM Mike Miller wrote:
> On Wed, Jul 08, 2015 at 18:36:29 +0900, Norbert Preining wrote:
> > Great, does that mean I don't need to investigate 3.8.2 build fixes
> > anymore? I am on a conference and low on time, so I couldn't
> > do more testing and fixing for th
On Wed, Jul 08, 2015 at 18:36:29 +0900, Norbert Preining wrote:
> Great, does that mean I don't need to investigate 3.8.2 build fixes
> anymore? I am on a conference and low on time, so I couldn't
> do more testing and fixing for the 3.8.2 version.
Yes, I think the patch I submitted should be suff
Hi Mike,
On Wed, 08 Jul 2015, Mike Miller wrote:
> Much thanks Norbert for investigating and finding the necessary changes.
> I've confirmed that these changes are necessary for building upstream
> source also. I'll take care of making sure these are addressed upstream.
Thanks, that is good to he
On Mon, Jul 06, 2015 at 20:19:32 -0400, Scott Kitterman wrote:
> On July 6, 2015 8:08:31 PM EDT, Norbert Preining wrote:
> >On Mon, 06 Jul 2015, Scott Kitterman wrote:
> >> Thanks. Would you be able to look at octave 3.8.2 in unstable as
> >well? The
> >> code you fixed in escape-backslash-for-
On July 6, 2015 8:08:31 PM EDT, Norbert Preining wrote:
>On Mon, 06 Jul 2015, Scott Kitterman wrote:
>> Thanks. Would you be able to look at octave 3.8.2 in unstable as
>well? The
>> code you fixed in escape-backslash-for-texinfo-in-source isn't in
>3.8.2, but it
>> appears to have similar p
On Mon, 06 Jul 2015, Scott Kitterman wrote:
> Thanks. Would you be able to look at octave 3.8.2 in unstable as well? The
> code you fixed in escape-backslash-for-texinfo-in-source isn't in 3.8.2, but
> it
> appears to have similar problems elsewhere.
Have you tried fixing the Makefile.am frag
On Monday, July 06, 2015 05:08:05 PM Norbert Preining wrote:
> Hi Scott,
>
> To finish this up, here is a debdiff between 4.0.0-1 and my version
> that did build in a clean chroot.
>
> All the best
>
> Norbert
>
Thanks. Would you be able to look at octave 3.8.2 in unstable as well? The
code
Hi Scott,
To finish this up, here is a debdiff between 4.0.0-1 and my version
that did build in a clean chroot.
All the best
Norbert
PREINING, Norbert http://www.preining.info
JAIST, Japan
On Mon, 06 Jul 2015, Scott Kitterman wrote:
> In the time I had today to work on it today, I didn't figure it out, but
> thanks
> for the progress. Hopefully someone else will have time.
Probably the attached patch instead of editing the DOCSTRINGS
will work
Norbert
--
Thanks,
In the time I had today to work on it today, I didn't figure it out, but thanks
for the progress. Hopefully someone else will have time.
Scott K
On Monday, July 06, 2015 10:50:40 AM Norbert Preining wrote:
> Postscriptum:
>
> On Mon, 06 Jul 2015, Norbert Preining wrote:
> > * finally
Postscriptum:
On Mon, 06 Jul 2015, Norbert Preining wrote:
> * finally the critical part - fix the argument processing in texinfo source
> the problem is basically that
> munge-texi.pl
> creates code like
> @qcode{"\a"}
> which needs to be changed to
> @qcode{"\\a"}
>
>
Hi Scott,
ok, here is what you have to do, but I cannot *fully* fix it
as the problem comes from
munge-texi.pl
What needs to be done are three things:
* add texlive-fonts-recommended to the build deps
this is necessary for newer texinfo (although nobody knows why ;-)
diff --git a/de
Hi Scott,
thanks for pointing us at that. I have contacted the texinfo upstream,
as I have the strange feeling that I have seend a similar error floating
by on the texinfo mailing list.
On Sat, 04 Jul 2015, Scott Kitterman wrote:
> I was hoping one of you could take a look at #790626 to see if yo
I was hoping one of you could take a look at #790626 to see if you could
determine why Octave is FTBFS with the new texinfo? It's a matter of some
urgency since the Octave FTBFS is blocking the Qscintilla2 transition from
finishing.
Thanks,
Scott K
signature.asc
Description: This is a digita
14 matches
Mail list logo
