Hi Dave,
On mer., juil. 31 2024 at 02:15:18 , Dave Kemper wrote:
> On Tue, Jul 30, 2024 at 6:45 PM G. Branden Robinson
> wrote:
>> I hope you will join me in thanking him for his excellent work.
>
> Absolutely. Bertrand, your contributions, being mostly to the
> underpinnings, may never have be
Hi Branden,
On mar., juil. 30 2024 at 06:44:42 , "G. Branden Robinson"
wrote:
> Hi folks,
>
> I've heard back from Bertrand Garrigues, and he advised that I start the
> hand-off process for GNU maintainership of the groff package/project.
>
> I have conseque
Hi Branden,
On mar., mai 23 2023 at 02:15:33 , "G. Branden Robinson"
wrote:
>> > Myself, I wonder if K-P couldn't be implemented above the formatter
>> > itself, using a diversion. We could then put the implementation in
>> > an auxiliary macro package.
[...]
> I'll note that even if K-P can't
info manual)
and the man pages groff_mm(7) and eqn(1).
Since groff 1.22.4 was released in December 2018, 28 people have made a
total of over 4,500 commits:
14 Bertrand Garrigues
14 Bjarni Ingi Gislason
2 Bruno Haible
6 Colin Watson
1 Cynthia A. E. Livingston
1 Dami
Hi Branden,
On mer., juil. 05 2023 at 05:11:37 , "G. Branden Robinson"
wrote:
[...]
> If what I'm using as a template in the ANNOUNCE file[A] doesn't fit what
> you want to say, then I'd suggest adding the following, though I don't
> insist on either of them.
Ah, I've completely forgotten your
Hi Branden,
On dim., juil. 02 2023 at 01:09:41 , "G. Branden Robinson"
wrote:
> At 2023-07-02T19:44:32+0200, Bertrand Garrigues wrote:
>> If no, I'll tag the official 1.23.0 on the latest sha
>> (198346d187de9e340bbf9d4f80c2dc4d42f5f74e), in a few days (let's
Hi Peter, Hi Branden,
On lun., juin 26 2023 at 06:31:45 , Peter Schaffter wrote:
> On Mon, Jun 26, 2023, G. Branden Robinson wrote:
>> Peter, Bertrand, and I all agreed that the code changes to the mom(7)
>> macro package Peter committed to the master branch accidentally earlier
>> this month are
to switch to "developer mode"), use the git repo of the
package and clone it. You will have to follow the detailed
instruction of the package, and you may have to install more
development tools.
Regards,
Bertrand Garrigues
Hi Ingo,
On Sat, Aug 27 2022 at 12:49:05 PM, Ingo Schwarze wrote:
> Bertrand Garrigues via wrote on Fri, Aug 26, 2022 at 11:53:07PM +0200:
[...]
>> Could you please detail here what is your list of blockers that you
>> think must be absolutely fixed before the official 1.23.0
Hi Ingo, Hi Branden,
On Fri, Aug 26 2022 at 02:04:57 PM, "G. Branden Robinson"
wrote:
> At 2022-08-26T13:51:25+0200, Ingo Schwarze wrote:
>> Also, my best wishes for Bertrands further and speedy recovery!
> He has mine as well!
Thanks for your kind words,
> Bertrand is going to manage this rel
Hi Branden,
On Wed, May 25 2022 at 10:56:37 PM, "G. Branden Robinson"
wrote:
[...]
> Can you do the "git tag 1.23.0.rc2"?
Sorry for my late answer, I have some annoying health issues since June
(basically a problem in my internal ear that makes me dizzy). Nothing
too serious (at least for the
Hi Branden,
On Tue, Apr 26 2022 at 03:24:43 AM, "G. Branden Robinson"
wrote:
> Hello again, Bertrand. I'm back in the saddle. Let me iterate my
> thanks to you for grappling submodule and build system issues.
This wasn't too long to upgrade as there were no issues; I'm really
sorry for being
Hi John,
On Sun, Apr 24 2022 at 04:39:57 AM, John Gardner wrote:
> On macOS, Groff builds and installs perfectly from a fresh checkout
> (currently using
> f55d8f41).
>
> However, running `make check` produced 6 failing tests:
[...]
> I've saved the build log and test-suite.log. Should I open a
Hi Werner,
On Sat, Apr 23 2022 at 05:33:26 PM, Werner LEMBERG wrote:
> 'gnulib' now supports non-recursive builds natively. You want to have
> a look at the following patch from `ttfautohint` that demonstrates how
> to update this feature.
>
>
> https://repo.or.cz/ttfautohint.git/commit/a938f
Hi Branden,
On Fri, Apr 22 2022 at 01:30:54 AM, "G. Branden Robinson"
wrote:
> Hi folks,
>
> Just wanted to advise that I'll be traveling for a few days so my usual
> periodic burst of commits to groff Git's repo will be delayed.
>
> I'm attaching the work that I have pending, in the event I sho
Hi Branden,
On Fri, May 21 2021 at 04:57:59 PM, "G. Branden Robinson"
wrote:
> I have a reproducible problem that I don't understand.
[...]
>
> $ echo '@c' >> doc/groff.texi
> $ (cd build && make -j all check)
[...]
> .../groff/build/../doc/groff.texi
> makeinfo: rename doc/groff.info failed: No
next week or the week after. We could also add Deri's
latest extension to gropdf and ms, what do you think? I also owe a
small dev for Ingo on the texinfo doc generation (this was discussed
off-list last year).
Regards,
Bertrand Garrigues
oxes'. You example is generated in
build/contrib/sboxes/msboxes.pdf, and the new .tmac is installed with
other .tmac files in the normal tmac dir.
Regards,
Bertrand Garrigues
edn't be from a file) and shortened the lines to be under 80
>> columns. Further refinements welcome.
>
> I think these are good fixes. And the preconv man page has certainly
> been improved, in my self-serving opinion, to make it clear what one
> gives up when uchardet is missing.
>
> Makez-vous le patch und bug-filen Sie?
Yes the wording is much better, I've pushed it on master, thanks.
Regards,
Bertrand Garrigues
st this version.
If you find an issue please indicate which system you are running and
provide an example or test file so that we could try to reproduce the
bug.
Regards,
Bertrand Garrigues
dment by firing a commit that changes 509
files; well it's just to update the copyright date... This time I've
been more cautious and I think everything is in order.
I found no issue in the build so if you are out of ammo I can tag and
push the 1.23.0.rc1 on GNU's alpha ftp.
Regards,
Bertrand Garrigues
Hi Ingo,
On Sun, Oct 25 2020 at 06:16:44 PM, Ingo Schwarze wrote:
> Bertrand Garrigues wrote on Sat, Oct 24, 2020 at 07:54:43PM -0400:
>
>> bgarrigues pushed a commit to branch master
>> in repository groff.
>>
>> commit a2e955e07354c83939fabffebcf720dd1f6b
Hi,
On Wed, Oct 21 2020 at 01:24:25 AM, Bertrand Garrigues
wrote:
> Building a 1.23.rc1 tag unexpectedly broke all the mom examples
> generation (there's just garbage in the pdf files). I'll try to figure
> out why tomorrow.
This is because of the:
const char *revisi
Hi,
On Mon, Oct 12 2020 at 01:32:37 AM, Bertrand Garrigues
wrote:
> 1.23 looks prettier to me too; so I will first make a 1.23.rc1 tag. I
> just need to check that the non-numerical 'rc' won't harm, for example
> if a something attempts to check the patch number.
ION_C99 are reasoably robust, we can
> postpone further deliberation until after release, i think.
[...]
> I will re-test ASAP with the upcoming libc change; to save time,
> i will do so without waiting for that change to be committed.
OK, thanks for doing these tests; for the moment I think there is nothing
blocking the release.
Regards,
Bertrand Garrigues
Hi Ingo,
On Mon, Oct 12 2020 at 06:08:27 PM, Ingo Schwarze wrote:
> A major problem with gnulib emerged just now that we should perhaps
> treat as a blocker.
[...]
> The code in
>
> gnulib/lib/vasnprintf.c
>
> line 4879 puts a format string containing a %n directive into
> writeable memory and
Hi Branden,
On Sun, Oct 11 2020 at 02:18:20 PM, "G. Branden Robinson"
wrote:
> At 2020-10-11T00:04:16+0200, Bertrand Garrigues wrote:
>> I don't have much time to make large changes in the code base (my
>> Knuth-Plass work is unfortunately in standby now), but for
Hi Werner,
On Sun, Oct 11 2020 at 04:59:43 AM, Werner LEMBERG wrote:
>> Just a question on the version though: We are talking about 1.23 and
>> not 1.23.0, and I see that we also had a 1.22 version (not a
>> 1.22.0), is there a particular reason to omit the patch number if it
>> is equal to 0?
>
Hi Werner,
On Sat, Oct 10 2020 at 05:34:02 PM, Werner LEMBERG wrote:
>> My main argument against that is a selfish one. Somebody would have
>> to go through all the Savannah tickets that are marked as fixed in
>> 1.22.5 and change them.
>
> Simply change the name of the label, and you are done.
Hi Branden,
On Sat, Oct 10 2020 at 08:56:49 PM, "G. Branden Robinson"
wrote:
> We have a formal expression of interest in a new release.
>
> https://savannah.gnu.org/bugs/?59216
>
> Bertrand, do you think you will be available to serve as release
> engineer, or do we need to solicit interest in
Hi Branden,
On Sat, Jul 25 2020 at 04:27:54 PM, "G. Branden Robinson"
wrote:
> At 2020-07-25T07:10:11+0200, Werner LEMBERG wrote:
>> > Sorry for the somewhat loud subject line, but we don't often see
>> > Werner or Bertrand on this list anymore and to my recollection, I've
>> > never seen Vaibha
Hi Ralph,
On Sun, Jan 05 2020 at 06:20:10 PM, Ralph Corderoy
wrote:
>> Werner wrote:
>> > I think the proper way for testing groff would be to make it run
>> > with a fuzzer,
>>
>> Yes, that would no doubt be useful.
> ...
>> is kind of orthogonal to developing a test suite, though.
> ...
>> A t
Hi Ingo,
On Thu, Jan 16 2020 at 06:56:09 PM, Ingo Schwarze wrote:
> seeing that Branden is currently working actively on groff,
I was trying to catch up all my unread mails, unfortunately last year
I was too busy to work for groff, hope this year will be better.
> is anyone willing to provide an
On Wed, May 15 2019 at 01:17:12 PM, Mikkel Meinike Nielsen
wrote:
> ons. 15. maj 2019 10.53 skrev Morten Bo Johansen :
>> On 2019-05-14 Bertrand Garrigues wrote:
>>
>> > Fonts are detected during the build process, so you can't just install
>> > the missin
ly, and I've never tried to build groff on Android.
Are you familiar with the NDK? If yes could you try to build groff from
the sources? If not, please first give me the Android version you are
using and I'll see if I can give you instructions on how to build it.
Regards,
Bertrand Garrigues
Hi Richard,
On Tue, Feb 19 2019 at 10:58:17 PM, Colin Watson wrote:
> On Tue, Feb 19, 2019 at 05:00:43PM +, Richard Morse wrote:
>> Hi! I just upgraded to groff 1.22.4, and suddenly my files are not
>> turning into PDFs properly. The error is "can't find font NR" (and
>> "NI"). This is on Mac
Hi Ingo,
On Thu, Jan 31 2019 at 02:14:13 PM, Ingo Schwarze wrote:
> i just submitted the following patch to the groff bugtracker:
>
> https://savannah.gnu.org/bugs/index.php?55616
>
> The (identical) rationale and patch are reproduced below for
> convenience.
>
> I'm posting this heads-up just
Hi Ralph,
On Thu, Jan 10 2019 at 10:46:37 PM, Ralph Corderoy
wrote:
>> Therefore I would like to add a '--debug' or '--log' option to 'groff'
>> that will make groff log all the calls to the preprocessors and to
>> troff into a file (so that stdin and stderr will not be impacted) and
>> also spr
I find debugging groff quite uneasy, due to the fact that it uses
various programs with pipes; it's even worse when its is invoked by
'pdfmom' which makes several pass of groff to generate table of contents
and pdf links.
Therefore I would like to add a '--debug' or '--log' option to 'groff'
that
Hi,
After a last commit (copyright year displayed on 'groff --version'),
I've created tag 1.22.4 and pushed the official package on GNU ftp.
Below is the annoucement done on the GNU info mailing list.
I just need to make a few update on the groff website.
Many thanks to everyone who contributed,
ke -j
sudo make install
Regards,
Bertrand Garrigues
demands a fix for the next release? If
no, then I'll make a rc5 for (hopefully) final checks before releasing
the 1.22.4.
Regards,
Bertrand Garrigues
Hi Branden, Peter,
On Mon, Dec 17 2018 at 09:36:41 PM, "G. Branden Robinson"
wrote:
> At 2018-12-17T20:56:53-0500, Peter Schaffter wrote:
>> Branden --
>>
>> I'd like the bibliography/refer fix to mom to be in the upcoming
>> release. On my end, regression tests check out and the sample docs
>
Hi Dave,
On Thu, Dec 13 2018 at 06:26:24 PM, Dave Kemper wrote:
> As long as we're still considering documentation fixes, here's another
> set. These are all low urgency but also low risk, so depending on the
> prevailing winds, they could go into this release or wait till the
> next one.
>
> Th
Hi Branden,
On Wed, Dec 12 2018 at 11:46:43 AM, "G. Branden Robinson"
wrote:
> It's starting to sound like (1) either there's going to be an rc5 or
> we're about to close in on final;
Yes. I've just pushed update on texinfo doc installation and
uninstallation. I need to make some more overall
On Tue, Dec 11 2018 at 11:13:00 PM, Bertrand Garrigues
wrote:
> Hi Branden,
>
> On Mon, Dec 10 2018 at 05:55:10 PM, "G. Branden Robinson"
> wrote:
>> At 2018-12-10T23:24:50+0100, Bertrand Garrigues wrote:
>>> You can push no_more_makefile.comm.
Hi Branden,
On Mon, Dec 10 2018 at 05:55:10 PM, "G. Branden Robinson"
wrote:
> At 2018-12-10T23:24:50+0100, Bertrand Garrigues wrote:
>> You can push no_more_makefile.comm.diff. As Peter has just modified the
>> texinfo doc by refering to "Collection of Install
Hi Brandent,
On Sun, Dec 09 2018 at 06:50:32 PM, "G. Branden Robinson"
wrote:
> At 2018-12-10T00:43:39+0100, Bertrand Garrigues wrote:
[...]
>> hmm... the patch does not apply for me (I'm on master
>> 92f40b186aa2adda8039fff09c1246bdd30dbd3d).
>
> It f
Hi Ingo,
On Mon, Dec 10 2018 at 01:58:56 AM, Ingo Schwarze wrote:
[...]
> My first impulse was to say "presumably, at some time in the (possibly
> remote) past, systems existed where libm provided a viable implementation
> of hypot(), but failed to declare it. Your propsed direction
> might bre
Hi Ingo,
On Sun, Dec 09 2018 at 02:32:00 PM, Ingo Schwarze wrote:
> Ralph Corderoy wrote on Sun, Dec 09, 2018 at 10:36:25AM +:
>> The time-honoured way to achieve this is using the built-in `set'.
>>
>> $ l='foo bar xyzzy'
>> $ set -- $l; for f; do echo f=$f; done | fmt
>> f=foo
Hi Ingo,
On Sun, Dec 09 2018 at 01:59:11 PM, Ingo Schwarze wrote:
> Then, the test that the gnulib hypot module is supposed to replace
> intends to test whether the function needs to be *declared*. In
> the past, our build system did not provide any replacement code for
> a missing hypot() objec
On Sun, Dec 09 2018 at 12:15:20 AM, "G. Branden Robinson"
wrote:
> At 2018-12-09T01:02:19+0100, Bertrand Garrigues wrote:
>> > I'm attaching the fix to the "POSITIONS FROM INSTALLATION" section
>> > (which I would like to rename--it's pretty
Hi Werner,
On Sat, Dec 08 2018 at 09:56:07 PM, Werner LEMBERG wrote:
>> On Solaris 9, installation still fails because of the "for f in ;
>> do" we discussed earlier, and the test suite still fails as shown at
>> the end (no change in that respect), but i see no regressions from
>> your patch.
>
Hi Branden,
On Sat, Dec 08 2018 at 02:04:33 PM, "G. Branden Robinson"
wrote:
> At 2018-12-08T18:58:01+0100, Bertrand Garrigues wrote:
>> > * How do i know what to insert for ?
>> [...]
>>
>> In the main groff(1) man page there is the 'POSITIONS FRO
[...]
> I do not see any regressions so far. So now we also know that it is
> possible to build this groff release with the complete LLVM toolchain.
That's a good thing,
> Bertrand Garrigues wrote on Sat, Dec 08, 2018 at 01:07:26AM +0100:
>> Yes the test is buggy. On my GNU/L
Hi Ingo, hi Peter,
On Fri, Dec 07 2018 at 08:46:23 PM, Ingo Schwarze wrote:
> Peter Schaffter wrote on Fri, Dec 07, 2018 at 11:18:32AM -0500:
[...]
>> Bertrand, how do you feel about omitting the local docs, leaving
>> just the pointer to the online docs? If you're agreeable, I can
>> commit the
Hi Ingo,
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
> What is potentially more serious is that "make" dies like this:
>
> CXX src/libs/libgroff/libgroff_a-hypot.o
> ../src/libs/libgroff/hypot.cpp:24:30: error: ‘double hypot(double, double)’
> conflicts with a previous declar
Hi Ingo,
On Thu, Dec 06 2018 at 09:45:31 PM, Ingo Schwarze wrote:
> i found out more about why the mom test is failing on Solaris 11.
> It turns out not just the test is broken, but there is likely a
> portability issue in gropdf(1).
>
> I see this in the build log:
>
> GROFFcontrib/mom/e
Hi Ingo,
On Thu, Dec 06 2018 at 06:44:18 PM, Ingo Schwarze wrote:
> Hi Bertrand,
>
> i finally figured out the hdtbl failure on Solaris.
> The mom test is still failing, though.
>
> OK to push the patch below, before release?
> I see no regression on OpenBSD, and no regression on Debian.
No regr
Hi Peter,
On Tue, Dec 04 2018 at 03:16:50 PM, Peter Schaffter wrote:
> Thanks for replying so thoroughly, and so passionately, to my query
> about the mom manpage.
[...]
I won't discuss (at least today) what is the best place to document mom
(manpage or html doc), but as a regular mom user I alw
Hi Dave,
On Wed, Dec 05 2018 at 09:11:45 AM, Dave Kemper wrote:
> Since a new rc will have to be built anyway,
Yes, unfortunately the "Final RC" in my mail subject was too optimistic.
> any chance this patch could be included? It's not critical by any
> means, but it's very low-risk (correcting
Hi Ingo and Colin,
On Mon, Dec 03 2018 at 01:48:19 AM, Bertrand Garrigues
wrote:
> On Sat, Dec 01 2018 at 04:44:45 PM, Ingo Schwarze wrote:
>> So it appears you are unconditionally testing for optional features
>> in the test suite.
>
> Yes, I will work on Colin's sug
Hi Werner,
On Sat, Dec 01 2018 at 07:09:44 AM, Werner LEMBERG wrote:
>> Anything in particular you want me to have a closer look at on
>> OpenBSD, Debian Jessie, or Solaris 9, 10, or 11?
>
> Thanks for checking the issues! As soon as they are fixed I suggest
> we contact Nelson Beebe[*] to build
Hi Colin,
On Sat, Dec 01 2018 at 01:13:54 AM, Colin Watson wrote:
> I pushed a couple of corrections to error paths in the new
> contrib/mom/examples/test-mom.sh.in script. Not perhaps quite critical,
> but since it was only added a week ago and the changes can only possibly
> affect "make check
Hi Ingo,
On Sat, Dec 01 2018 at 04:44:45 PM, Ingo Schwarze wrote:
> OpenBSD-current:
>
> schwarze@isnote $ make check
> make check-am
> make
> make all-am
> make check-TESTS
> PASS: contrib/gdiffmk/tests/gdiffmk_tests.sh
> sed -e
> "s|[@]abs_top_builddir[@]|/usr/ports/pobj/groff-1.22.4/gro
Ingo,
On Sat, Dec 01 2018 at 01:20:30 AM, Ingo Schwarze wrote:
> On Solaris 11, with the following workaround, it built, it installed,
> and it runs.
>
> export groff_cv_decl_needed_hypot=no
> ../configure
I'll check what you've described on this issue on your other mail next
week. Should I
Hi Ingo,
Thanks for all your tests !
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
[...]
> However, there are problems on Oracle Solaris 11:
[...]
> checking whether URW fonts in pfb format are available...
> grep: illegal option -- A
> Usage: grep [-c|-l|-q] -bhinsvw pattern file
groff documentation that briefly
describes how 'troff' processes the input: "5.32 gtroff Internals".
Could be enhanced later on.
Regards,
Bertrand Garrigues
Hi Ingo,
On Fri, Nov 30 2018 at 05:33:11 PM, Ingo Schwarze wrote:
[...]
> However, there are problems on Oracle Solaris 11:
>
> schwarze@unstable11s [unstable11s]:~/groff-1.22.4.rc4/build > uname -a
> SunOS unstable11s 5.11 11.3 sun4u sparc SUNW,SPARC-Enterprise
>
> This is from ../configure
'make uninstall'. You can also download and
build the 1.22.4.rc4 from git:
git clone https://git.savannah.gnu.org/git/groff.git
cd groff
git checkout 1.22.4.rc4
./bootstrap
mkdir build
cd build
../configure
make -j
sudo make install
Regards,
Bertrand Garrigues
'preconv -v') or not; if I'm not mistaken all the man pages are
aligned now?
Do you have more things you would like to commit? If no I would make a
rc4 for final sanity checks (only allowing important bug fixes) before
releasing the official 1.22.4.
Regards,
Bertrand Garrigues
is integrated into groff, but I'm not willing
> to devote my own energy to dealing with the abomination that is
> automake, so I will need someone else to assist with build system
> integration.
I've opened a ticket: https://savannah.gnu.org/bugs/index.php?55107.
We will see after the release 1.22.4 is completed how we can integrate
your code.
Regards,
Bertrand Garrigues
(which is used as "less important then minor" and/or
"Issue which is mainly a matter of taste "). New features that are
important should be marked with a Normal or Important severity.
Please feel free to comment on these changes.
I'll make some more cleaning in the tracker in the next few days.
Regards,
Bertrand Garrigues
ing this update. I'm trying to catch up
months of inactivities and I have dozens of unread mails from the groff
mailing list, so you still have a bit of time.
Regards,
Bertrand Garrigues
bl examples
connected to 'make check'. It justs use 'gs -o /dev/null/ -sDEVICE=bbox'
and 'grep' to count the number of pages. I'll also add something for
the pdf examples (probably using 'pdftotex' and/or 'pdfinfo').
Regards,
Bertrand Garrigues
git/groff.git
cd groff
git checkout 1.22.4.rc3
./bootstrap
mkdir build
cd build
../configure
make -j
sudo make install
Regards,
Bertrand Garrigues
Hi Dave,
On Wed, Jun 20 2018 at 08:10:48 PM, Dave Kemper wrote:
>> Currently there is no 'me' example in groff source tree, I was
>> wondering if you would like to contribute an provide an 'me' example
>> (something more like a real document rather than the test file from
>> the bug)?
>
> Hi Bert
ree, I was wondering
if you would like to contribute an provide an 'me' example (something
more like a real document rather than the test file from the bug)? This
way we would have an extra sanity check on the 'me' package.
Regards,
Bertrand Garrigues
Hi Branden,
On Mon, Jun 18 2018 at 07:36:11 PM, "G. Branden Robinson"
wrote:
> At 2018-06-19T00:49:03+0200, Bertrand Garrigues wrote:
>> I will try now to finish the release now, and I'm currently checking all
>> my unread mails. I've also checked the recent
OCKS and BLOCKE commands. Supports all the
transition types introduced in PDF v1.5. (See gropdf man page)
- To Branden: you've tagged commit
3fa04f3e60bebfdcf968f573e6b46e6236a55789 (tag 1.22.4), is there any
special reason for that or is it a mistake?
Thanks,
Regards,
Bertrand Garrigues
Hi Ingo and everyone on the list,
On Thu, Mar 29 2018 at 08:05:48 PM, Ingo Schwarze wrote:
> Salut Bertrand,
>
> Bertrand Garrigues wrote on Thu, Mar 29, 2018 at 12:46:58AM +0200:
>
>> Release candidate 1.22.4.rc2 is now available from GNU's alpha ftp.
[...]
> OpenBS
etting.mom' at FT, line 24.
> GROFFcontrib/mom/examples/slide-demo.pdf
> [mom]: Aborting '../contrib/mom/examples/slide-demo.mom' at FT, line 34.
> GROFFcontrib/pdfmark/pdfmark.pdf
>
> The devpdf download file looks good (it points to the correct font locations)
> My system is MacOS 10.11.
> LANG="de_DE.UTF-8“ setting LANG to „c“ doesn’t change anything.
Could you please provide me the full configure + build logs?
Thanks,
Regards,
Bertrand Garrigues
uild the 1.22.4.rc2 from git:
git clone https://git.savannah.gnu.org/git/groff.git
cd groff
git checkout 1.22.4.rc2
./bootstrap
mkdir build
cd build
../configure
make -j
sudo make install
Thanks to everyone that is willing to test this version.
Regards,
Bertrand Garrigues
On Sun, Mar 25 2018 at 11:22:13 PM, Ingo Schwarze wrote:
> Hi Bertrand,
>
> Bertrand Garrigues wrote on Sun, Mar 25, 2018 at 10:49:43PM +0200:
>
>> That's right, release candidates should be named 1.22.4.rc1, 1.22.4.rc2
>> etc... before releasing the final 1.22.4
Hi Werner,
On Sun, Mar 18 2018 at 02:44:34 AM, Werner LEMBERG wrote:
>> right now, the string is "1.22.3.rc1.43-e7a3", with "3.rc1", even
>> though this is actually a *4* release candidate.
>
> Yes, this is a mistake. Bertrand, please fix :-)
That's right, release candidates should be named 1.2
Hi Peter,
On Fri, Mar 16 2018 at 01:05:17 PM, Peter Schaffter wrote:
> Ingo --
>
> On Thu, Mar 15, 2018, Ingo Schwarze wrote:
>> After a fierce fight resulting in the death of the vicious
>> git-version-gen dragon, i finally managed to test,
>
> A good fight, St. George. :)
>
>> ...that your patc
e first 3
numbers to build the directory name), what's the problem with having the
various programs printing a unique version (for example with 'groff
--version')? Does this bring extra testing difficulties? Having a
unique version seems better when people report a bug (otherwise they
would just say "I'm using 1.22.3" or "I'm using groff from git").
Regards,
Bertrand Garrigues
d).
Usually when updating from git 'make clean' and 'make' is enough.
- If you really want to totally clean your environment then you should
call 'git -xfd' before calling 'bootstrap'. With the commands you
passed -- 'git reset --hard &am
.
You are right, this file is no longer needed, so I've removed it
(commited on master).
Regards,
Bertrand Garrigues
Hi Colin,
On Fri, Mar 09 2018 at 12:31:11 PM, Colin Watson wrote:
> On Mon, Mar 05, 2018 at 07:55:34PM +0100, Werner LEMBERG wrote:
>> Colin Watson wrote:
>> > Would it be possible to include these simple fixes in 1.22.4?
>> >
>> > https://lists.gnu.org/archive/html/groff/2017-02/msg00015.html
ated maintainer :-) Peter, please have a look and adjust
> it accordingly!
Peter,
I've just seen that you have commited version 2.3 of 'mom', does this
include the fixes Werner mentioned?
If 'mom' is ready then I'm planning to release an rc2 as there were
quite some changes since rc1.
Regards,
Bertrand Garrigues
Hi Colin,
On Thu, Feb 22 2018 at 11:07:56 AM, Colin Watson wrote:
> On Wed, Feb 21, 2018 at 11:48:56PM +0100, Bertrand Garrigues wrote:
>> I'll add a check on the presence of pkg-config in m4/groff.m4 and update
>> the doc.
>
> But the pkg-config macros themselves al
.4-1 release.
This is only a matter of a few git commands and is easy to do (compared
to having to manage 2 distinct packages). The macro package maintainer
could also request the proper rights from GNU to push releases, this
does not even require an official maintainer status, I could declare him
as a person of trust allowed to make release (there would be some
administrative stuff to do though).
Regards,
Bertrand Garrigues
Hi Ralph,
On Sat, Feb 17 2018 at 01:05:38 PM, Ralph Corderoy
wrote:
> Various compilation warnings result, that you probably know about.
>
> Output includes
>
> common.roff: elapsed time: 0 seconds
> common.roff: elapsed time: 0 seconds
> troff: ../doc/automake.mom:54: can't transpar
On Sat, Feb 17 2018 at 03:43:53 PM, Colin Watson wrote:
> On Sat, Feb 17, 2018 at 12:40:57PM +, Ralph Corderoy wrote:
>> Hi Bertrand,
>>
>> > git clone https://git.savannah.gnu.org/git/groff.git
>> > cd groff
>> > git checkout 1.22.3.rc1
>> > ./bootstrap
>>
>> ./bootstrap fails here.
sing the official 1.22.4, so please take your time to
complete your work, I think it's a nice feature and would like to
include it into the 1.22.4.
Regards,
Bertrand Garrigues
t, I often use 'make -j' out of laziness and it works fine on
my machine, but it's better use your command.
Regards,
Bertrand Garrigues
hat can take some time to test.
Regards,
Bertrand Garrigues
Hi Peter,
On Tue, Jan 23 2018 at 12:01:19 AM, Bertrand Garrigues
wrote:
> On Mon, Jan 22 2018 at 01:59:50 PM, Peter Schaffter
> wrote:
>> By coincidence, I just took care of the same thing in the master
>> branch om.tmac-u, for inclusion in my next commit. You're ri
Peter,
On Mon, Jan 22 2018 at 01:59:50 PM, Peter Schaffter wrote:
> Bertrand --
>
> On Sun, Jan 21, 2018, Bertrand Garrigues wrote:
>> I've just pushed on the 'unique-version' branch a commit on the mom
>> macro package to use the new .Y, could you pleas
1 - 100 of 212 matches
Mail list logo
