> First, some fonts in devpdf (U-* fonts) are not built unless
> `afmtodit' is already present (for example if groff is already
> installed). Attached a patch to force the build of afmtodit before
> fonts/devpdf.
Applied, thanks.
> The second problem is that the example
> contrib/mom/examples/l
Hi Werner and all the list,
On Sat, Oct 11 2014 at 09:13:16 AM, Werner LEMBERG wrote:
> I want to wait a few days so that you can test and check whether
> everything's fine. Please do so!
I've seen two more minor problems:
First, some fonts in devpdf (U-* fonts) are not built unless `afmtodit'
Hello Werner,
On Thu, Oct 23 2014 at 07:53:20 AM, Werner LEMBERG wrote:
>> Here is a patch containing the modifications I had to make to
>> correct the 3 problems mentioned above.
>
> Please apply!
Commited,
Regards,
--
Bertrand Garrigues
> If I'm not mistaken you changed:
>
> install_data: install_always $(make_install_examples)
>
> for:
>
> install_data: install_always install_examples
>
> which causes the the `install_examples' rule to be executed, causing
> the error. Why did you have to make this change? It seems to me
>
Hi all,
On Sat, Oct 11 2014 at 09:13:16 AM, Werner LEMBERG wrote:
> I want to wait a few days so that you can test and check whether
> everything's fine. Please do so!
I've found a few issues on the install target if you pass the option
--with-doc=no to configure.
- In chem I got this error:
On Tue, Oct 14, 2014, Werner Lemberg wrote:
> Thanks. Now waiting for Peter's last changes – I've also contacted
> Eli Zaretskii, asking him to retry his Win32 port, which probably
> needs minor modifications here and there.
I'll be pushing the changes to om.tmac and some modified doc files
to th
> Please, add to doc-common
> .ds doc-operating-system-Darwin-14.0.0 14.0.0
>
> OS X 10.10 was released yesterday.
Done.
Werner
Dear Werner,
>> minor update for Darwin (AKA OS X) versions
>
> Applied, thanks.
Please, add to doc-common
.ds doc-operating-system-Darwin-14.0.0 14.0.0
OS X 10.10 was released yesterday.
Michail
On 10/16/14, Werner LEMBERG wrote:
>> Last year, Werner wrote
>> (http://lists.gnu.org/archive/html/groff/2013-11/msg00105.html) that
>> the top-level TODO was obsolete. Is the best approach to delete the
>> file, or replace its content with a pointer to the bug tracker?
>
> I would favor the lat
> Last year, Werner wrote
> (http://lists.gnu.org/archive/html/groff/2013-11/msg00105.html) that
> the top-level TODO was obsolete. Is the best approach to delete the
> file, or replace its content with a pointer to the bug tracker?
I would favor the latter. However, someone should check whethe
The content of TODO and tmac/TODO was last touched over ten years ago.
Last year, Werner wrote
(http://lists.gnu.org/archive/html/groff/2013-11/msg00105.html) that
the top-level TODO was obsolete. Is the best approach to delete the
file, or replace its content with a pointer to the bug tracker?
> How about the attached?
Applied, thanks!
Werner
On Sat, Oct 11, 2014 at 12:03:14PM +0200, Werner LEMBERG wrote:
> Colin Watson wrote:
> > I tried running a test "make dist", importing that into my Debian
> > packaging branch, and building. This failed because
> > src/utils/xtotroff was missing. On looking back I see this in the
> > configure o
> Thanks. Now waiting for Peter's last changes – I've also contacted
> Eli Zaretskii, asking him to retry his Win32 port, which probably
> needs minor modifications here and there.
Eli says that he needs two weeks, so let's make a new groff release in
the end of October. This should give plenty
> I've now pushed my changes, and updated NEWS accordingly.
Thanks. Now waiting for Peter's last changes – I've also contacted
Eli Zaretskii, asking him to retry his Win32 port, which probably
needs minor modifications here and there.
Werner
Hi Werner,
Werner LEMBERG wrote on Sat, Oct 11, 2014 at 09:13:16AM +0200:
> I think I've now done everything to make a new release ??? essentially,
> it was a matter of continued comparation between the last tarball and
> the current git repository.
Thank you for doing all that work. Also thank
On 12/10/14 19:37, Werner LEMBERG wrote:
>> I too have a couple of trivial patches for pdfroff: [...]
>>
>> I guess it would be good to get these into the release, but I'll
>> need a day or two to finalize them.
>
> No problem :-)
I've now pushed my changes, and updated NEWS accordingly.
--
Reg
>>> I pulled from git and did a make distclean.
>>
>> This isn't enough. You have to re-execute `config.status'.
>
> make distclean says:
>
> rm -f Makefile config.cache config.log config.status groff.log
> groff.sum src/include/config.h site.bak site.exp stamp-h test-groff
>
> There is no co
Am 12.10.2014 um 20:50 schrieb Werner LEMBERG :
>
>> I pulled from git and did a make distclean.
>
> This isn't enough. You have to re-execute `config.status'.
make distclean says:
rm -f Makefile config.cache config.log config.status groff.log groff.sum
src/include/config.h site.bak site.ex
> I pulled from git and did a make distclean.
This isn't enough. You have to re-execute `config.status'.
Werner
Am 12.10.2014 um 18:14 schrieb Werner LEMBERG :
I pulled from git and did a make distclean.
>> During make:
>>
>> sed -e "s;@VERSION@;1.22.3;" webpage.ms [...]
>> sed: RE error: illegal byte sequence
>
> Should be fixed now.
Sorry, it isn't:
sed -e "s;@VERSION@;1.22.3;" webpage.ms | GROFF_CO
> I too have a couple of trivial patches for pdfroff: [...]
>
> I guess it would be good to get these into the release, but I'll
> need a day or two to finalize them.
No problem :-)
Werner
On 11/10/14 20:45, Peter Schaffter wrote:
> Werner --
>
> On Sat, Oct 11, 2014, Werner Lemberg wrote:
>> After Bernd's commits to fix the IPC issue, I can do `make dist' and
>> distribute it. Before doing this, however, I want to wait a few days
>> so that you can test and check whether everythin
Hi Werner,
> > /usr/bin/install -c -m 644 ./m.tmac \
> > /usr/local/share/groff/1.22.3/tmac/m.tmac
> > sed: RE error: illegal byte sequence
>
> Hmm. I can't believe that the `install' program is involved.
Could the OP be doing a `make -j' parallel install, so the output is
muddled up?
Ch
> During make:
>
> sed -e "s;@VERSION@;1.22.3;" webpage.ms [...]
> sed: RE error: illegal byte sequence
Should be fixed now.
> and during make install:
>
> /usr/bin/install -c -m 644 ./m.tmac \
> /usr/local/share/groff/1.22.3/tmac/m.tmac
> sed: RE error: illegal byte sequence
Hmm. I
> minor update for Darwin (AKA OS X) versions
Applied, thanks.
Werner
> The reason is because the gropdf download file can include
> directory/filenames which may include spaces (this is especially
> true for windows installation). So it does not make a good choice as
> a field separator.
This is not documented, BTW...
I've added a small remark to gropdf.man to me
On Sun 12 Oct 2014 13:43:28 Axel Kielhorn wrote:
> While the grops man page says:
>
> fields may be separated by tabs or spaces;
>
> This is slightly inconsistent.
> (Of course you can argue that these are different programs
> and expecting them to use the same syntax is naïve. I wouldn't
Am 12.10.2014 um 13:10 schrieb Werner LEMBERG :
>
>> I had a problem with make install (again illegal byte sequence).
>> As a result I had an incomplete installation.
>> This was fixed with LANG=C.
>
> Uh, oh, this is not enough information. Please show us the *exact*
> error message.
During
Dear Werner,
minor update for Darwin (AKA OS X) versions
(inspired by
http://opensource.apple.com/source/groff/groff-38/patches/tmac__doc-common.diff)
Michail
--- doc-common.org 2014-10-12 13:47:20.0 +0400
+++ doc-common 2014-10-12 15:15:48.0 +0400
@@ -619,6 +619,7 @@
.ds
> I had a problem with make install (again illegal byte sequence).
> As a result I had an incomplete installation.
> This was fixed with LANG=C.
Uh, oh, this is not enough information. Please show us the *exact*
error message.
> download in devpdf really needs tabs, using space as a separator
>
Am 12.10.2014 um 11:11 schrieb Werner LEMBERG :
> Well, this looks like a bug in the texi2pdf script. What texinfo
> version are you using?
Texinfo 4.8 (1.34)
Since texi2pdf is just a wrapper around texi2dvi the problem lies there.
(There is neither $LANG nor $LC_ALL in both scripts.)
>> W
> When running
>
> texi2pdf -e groff.texinfo
>
> I get:
> sed: RE error: illegal byte sequence
[Uh, oh, another case where people mix up `illegal' with `invalid'.
But perhaps in the US there isn't a big difference, given how many
people are sitting in jail...]
> This used to work on MacOS 10.6
Am 11.10.2014 um 09:13 schrieb Werner LEMBERG :
>
> After Bernd's commits to fix the IPC issue, I can do `make dist' and
> distribute it. Before doing this, however, I want to wait a few days
> so that you can test and check whether everything's fine. Please do so!
>
>
>Werner
I tried to
On Sat, Oct 11 2014 at 09:29:47 PM, Werner LEMBERG wrote:
>> Here is a patch that calls `config.status' before `make distclean'
>> in tmp/src/libs/gnulib to force the creation of .deps directories,
>> which fixes the problem. [...]
>
> Thanks, please commit.
Done.
Regards,
--
Bertrand Garrigue
> I working on changes to the mom macros that I'd like to go into the
> release. Getting close to finishing them. Can you hold off until I
> commit them?
Certainly.
> Should be in a day or two.
Great!
Werner
Werner --
On Sat, Oct 11, 2014, Werner Lemberg wrote:
> After Bernd's commits to fix the IPC issue, I can do `make dist' and
> distribute it. Before doing this, however, I want to wait a few days
> so that you can test and check whether everything's fine. Please do so!
I working on changes to t
> Here is a patch that calls `config.status' before `make distclean'
> in tmp/src/libs/gnulib to force the creation of .deps directories,
> which fixes the problem. [...]
Thanks, please commit.
> However I dont' understand the purpose of calling
> $(top_builddir)/$$d/Makefile, we were trying to
Hi Werner,
On Sat, Oct 11 2014 at 09:13:16 AM, Werner LEMBERG wrote:
> Folks,
>
>
> I think I've now done everything to make a new release – essentially,
> it was a matter of continued comparation between the last tarball and
> the current git repository. There are surprisingly few changes
> (ex
> I tried running a test "make dist", importing that into my Debian
> packaging branch, and building. This failed because
> src/utils/xtotroff was missing. On looking back I see this in the
> configure output from before "make dist":
>
> configure: gxditview and xtotroff won't be built
>
> I
On Sat, Oct 11, 2014 at 09:13:16AM +0200, Werner LEMBERG wrote:
> I think I've now done everything to make a new release – essentially,
> it was a matter of continued comparation between the last tarball and
> the current git repository. There are surprisingly few changes
> (expect Bernd's clean-u
Folks,
I think I've now done everything to make a new release – essentially,
it was a matter of continued comparation between the last tarball and
the current git repository. There are surprisingly few changes
(expect Bernd's clean-up of copyright issues), so I don't expect large
surprises.
Af
42 matches
Mail list logo
