From alx.manpages at gmail.com  Mon Apr 24 22:26:15 2023
From: alx.manpages at gmail.com (Alejandro Colomar)
Date: Tue, 25 Apr 2023 00:26:15 +0200
Subject: Fwd: groff-1.23.0.rc4 - no ./configure?
In-Reply-To: <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
References: <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
Message-ID: <392f5f80-2c3a-dbdd-6416-c6ed4e877668@gmail.com>

Let's see if I had this email subscribed.


-------- Forwarded Message --------
Subject: Re: groff-1.23.0.rc4 - no ./configure?
Date: Tue, 25 Apr 2023 00:25:14 +0200
From: Alejandro Colomar <alx.manpages at gmail.com>
To: G. Branden Robinson <g.branden.robinson at gmail.com>
CC: groff mailing list <groff at gnu.org>, cgit at lists.zx2c4.com, Oliver Corff <oliver.corff at email.de>

[CC += CGit]

Hi Branden!

On 4/25/23 00:14, G. Branden Robinson wrote:
> Hi Oliver,
> 
> At 2023-04-24T22:40:23+0200, Oliver Corff wrote:
>> I went to https://git.savannah.gnu.org/cgit/groff.git today to
>> download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the
>> archive.
> 
> I've made the same mistake myself!
> 
> The official distribution archives are not available via the cgit
> interface.  cgit doesn't know about FSF deployment procedures and hasn't
> been taught.

Curious way to put it.  I wondered something along those lines recently:
Is it possible to teach cgit how to create a tarball?  It would be nice
if I just made a tag and cgit would do the automated process necessary
for the tarball.

Moreover, I considered not releasing tarballs anymore as a possibility,
since one can produce them following some repeatable command.

Would I be able to teach cgit to run

    $ make dist-gz

And then find the tarball in ./.tmp/$(git describe).tar.gz ?

Cheers,
Alex

> 
> As noted in the RC announcement email[1], you need to get the
> distribution archive from the alpha.gnu.org website.
> 
>   https://alpha.gnu.org/gnu/groff/
> 
>> How do I configure the makefile? I fail to see a ./configure script.
> 
> Carlos's response here was correct--you have to use the INSTALL.REPO
> instructions if you want to build from the Git repository--but if you
> want to provide feedback on the release candidate, then that's not the
> procedure to follow.
> 
> Regards,
> Branden
> 
> [1] https://lists.gnu.org/archive/html/groff/2023-04/msg00135.html

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


From alx.manpages at gmail.com  Mon Apr 24 23:35:03 2023
From: alx.manpages at gmail.com (Alejandro Colomar)
Date: Tue, 25 Apr 2023 01:35:03 +0200
Subject: groff-1.23.0.rc4 - no ./configure?
In-Reply-To: <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
References: <2b5c5ec1-c432-fa3e-8880-bc59ae04e0f4@email.de>
 <20230424221409.62yozpbcqfzoptjs@illithid>
 <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
Message-ID: <c57871ee-a5ad-b936-747e-1ca289f0670a@gmail.com>



On 4/25/23 00:25, Alejandro Colomar wrote:
> [CC += CGit]
> 
> Hi Branden!
> 
> On 4/25/23 00:14, G. Branden Robinson wrote:
>> Hi Oliver,
>>
>> At 2023-04-24T22:40:23+0200, Oliver Corff wrote:
>>> I went to https://git.savannah.gnu.org/cgit/groff.git today to
>>> download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the
>>> archive.
>>
>> I've made the same mistake myself!
>>
>> The official distribution archives are not available via the cgit
>> interface.  cgit doesn't know about FSF deployment procedures and hasn't
>> been taught.
> 
> Curious way to put it.  I wondered something along those lines recently:
> Is it possible to teach cgit how to create a tarball?  It would be nice
> if I just made a tag and cgit would do the automated process necessary
> for the tarball.
> 
> Moreover, I considered not releasing tarballs anymore as a possibility,
> since one can produce them following some repeatable command.
> 
> Would I be able to teach cgit to run
> 
>     $ make dist-gz
> 
> And then find the tarball in ./.tmp/$(git describe).tar.gz ?

Probably not.  My guess is that cgit just calls git-archive(1).

> 
> Cheers,
> Alex
> 
>>
>> As noted in the RC announcement email[1], you need to get the
>> distribution archive from the alpha.gnu.org website.
>>
>>   https://alpha.gnu.org/gnu/groff/
>>
>>> How do I configure the makefile? I fail to see a ./configure script.
>>
>> Carlos's response here was correct--you have to use the INSTALL.REPO
>> instructions if you want to build from the Git repository--but if you
>> want to provide feedback on the release candidate, then that's not the
>> procedure to follow.
>>
>> Regards,
>> Branden
>>
>> [1] https://lists.gnu.org/archive/html/groff/2023-04/msg00135.html
> 

From alx.manpages at gmail.com  Tue Apr 25 10:32:19 2023
From: alx.manpages at gmail.com (Alejandro Colomar)
Date: Tue, 25 Apr 2023 12:32:19 +0200
Subject: groff-1.23.0.rc4 - no ./configure?
In-Reply-To: <20230424235109.u3nto6bh3zlbudx6@illithid>
References: <2b5c5ec1-c432-fa3e-8880-bc59ae04e0f4@email.de>
 <20230424221409.62yozpbcqfzoptjs@illithid>
 <7f1e5e38-be73-c0b9-82be-f39f55a46626@gmail.com>
 <c57871ee-a5ad-b936-747e-1ca289f0670a@gmail.com>
 <20230424235109.u3nto6bh3zlbudx6@illithid>
Message-ID: <a790a5ab-6e51-223a-c73b-e3cf7f5601fb@gmail.com>

Since cgit's list is subscribers-only, I've CCd its maintainer.
Also CCd cgit-pink (I hope this one is not subscriber-only).

On 4/25/23 01:51, G. Branden Robinson wrote:
> At 2023-04-25T01:35:03+0200, Alejandro Colomar wrote:
>>> Curious way to put it.  I wondered something along those lines
>>> recently: Is it possible to teach cgit how to create a tarball?  It
>>> would be nice if I just made a tag and cgit would do the automated
>>> process necessary for the tarball.
>>>
>>> Moreover, I considered not releasing tarballs anymore as a
>>> possibility, since one can produce them following some repeatable
>>> command.
>>>
>>> Would I be able to teach cgit to run
>>>
>>>     $ make dist-gz
>>>
>>> And then find the tarball in ./.tmp/$(git describe).tar.gz ?
>>
>> Probably not.  My guess is that cgit just calls git-archive(1).
> 
> It's complicated, and has come up before[1].  I used to try to support
> the cgit-constructed tarballs but it was too much support effort.
> 
> A big part of the problem is that whatever assembles the archives
> doesn't pay attention to git submodules.  One of the most important
> differences between a cgit-generated archive from the groff repo and a
> distribution archive prepared by the maintainer is that the latter
> includes the gnulib sources.  (Including the stuff that "make dist"
> constructs for inclusion in the archive is the other important element.)
> 
> Regards,
> Branden
> 
> [1] This is just one thread of several.
> 
>     https://lists.gnu.org/archive/html/groff/2022-07/msg00064.html

From list at eworm.de  Tue Apr 25 17:13:54 2023
From: list at eworm.de (Christian Hesse)
Date: Tue, 25 Apr 2023 19:13:54 +0200
Subject: [PATCH 1/1] git: update to v2.40.1
Message-ID: <20230425171354.30839-1-list@eworm.de>

From: Christian Hesse <mail at eworm.de>

Update to git version v2.40.1, no additional changes required.

Signed-off-by: Christian Hesse <mail at eworm.de>
---
 Makefile | 2 +-
 git      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 5cc4a9d..3fc1d5a 100644
--- a/Makefile
+++ b/Makefile
@@ -14,7 +14,7 @@ htmldir = $(docdir)
 pdfdir = $(docdir)
 mandir = $(prefix)/share/man
 SHA1_HEADER = <openssl/sha.h>
-GIT_VER = 2.40.0
+GIT_VER = 2.40.1
 GIT_URL = https://www.kernel.org/pub/software/scm/git/git-$(GIT_VER).tar.xz
 INSTALL = install
 COPYTREE = cp -r
diff --git a/git b/git
index 73876f4..0d1bd1d 160000
--- a/git
+++ b/git
@@ -1 +1 @@
-Subproject commit 73876f4861cd3d187a4682290ab75c9dccadbc56
+Subproject commit 0d1bd1dfb37ef25e1911777c94129fc769ffec38
-- 
2.40.1