Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. INN Git tag format changed (Russ Allbery)
2. GitHub Actions CI now enabled for INN pull requests (Russ Allbery)
3. Re: Openssl 3.0.0 (Russ Allbery)
4. INN snapshot changes (Russ Allbery)
5. Re: INN snapshot changes (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Sun, 12 Sep 2021 18:23:56 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: INN Git tag format changed
Message-ID: <[email protected]>
Content-Type: text/plain
When I converted the repository, I used the tag naming convention I
started using years ago when first using Git: put all tags in their own
namespace, so the release tags were all release/<version> (like
release/2.6.4).
However, this doesn't play well with git describe, which I want to use for
snapshots, and isn't the convention in the Git world. The two common
conventions are either v2.6.4 or a bare 2.6.4. Since the latter works
best with git describe without any special reformatting, I've gone with
that.
I've pushed new bare version tags and deleted the release/* tags.
(Figured best do that early on before anyone starts depending much on the
new repository and format.)
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 2
Date: Sun, 12 Sep 2021 18:26:52 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: GitHub Actions CI now enabled for INN pull requests
Message-ID: <[email protected]>
Content-Type: text/plain
I've enabled some simple GitHub Actions testing for all pull requests and
pushes for the main branch. This does the same checks that we are doing
when generating snapshots: builds with various options with warnings
enabled plus running the (somewhat meager, alas) test suite. That should
at least give us a basic sanity check for pull requests.
(Sorry about the noise in inn-committersts earlier. I hadn't realized
that branches in the repository would also generate notifications, and was
iterating on fixing issues that were only showing up on the GitHub Ubuntu
runners.)
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 3
Date: Sun, 12 Sep 2021 18:34:05 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Openssl 3.0.0
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> It was indeed a late change in July 2021 before the final OpenSSL 3.0.0
> release:
> https://github.com/openssl/openssl/issues/16121
> https://github.com/openssl/openssl/commit/74b7f339aa58af57c0e71b7efca66e6f2db5ae2e
Looks like someone reported (correctly) an issue with using a prefix that
didn't already exist, and they "fixed" the issue by just assuming every
system uses the /lib64 convention. The comment that this commit deleted
explains why that code was there....
> On Debian Buster, I see symlinks for /libXX to /usr/libXX
> lrwxrwxrwx 1 root root 7 Jan 8 2021 lib -> usr/lib/
> lrwxrwxrwx 1 root root 9 Jan 8 2021 lib32 -> usr/lib32/
> lrwxrwxrwx 1 root root 9 Jan 8 2021 lib64 -> usr/lib64/
> lrwxrwxrwx 1 root root 10 Jan 8 2021 libx32 -> usr/libx32/
Ah, this has gotten rather more muddled with usrmerge, I see. Prior to
usrmerge, /lib64 was a regular directory on Debian that contained a single
file (a symlink for the dynamic loader, which by Linux ELF convention is
in /lib64 although Debian doesn't otherwise use that path).
However, I suspect that /usr/lib64 does not exist, correct? It at least
doesn't on my system. So Autoconf will still detect that Debian doesn't
use lib64 and libraries should be installed in lib.
> Yes, the fix is more complex than suggested in my previous message. In
> the GCC C Farm, I for instance see Alpine with /lib and /usr/lib only
> but OpenSSL configure sets LIBDIR=lib64
I think the answer is to always check for lib64 before lib when looking
for libraries, but preserve the current logic when installing libraries.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 4
Date: Sun, 12 Sep 2021 21:20:02 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: INN snapshot changes
Message-ID: <[email protected]>
Content-Type: text/plain
I think I have updated snapshot generation so that it will base the
snapshots on Git rather than Subversion. I've also moved, but not gotten
rid of, the daily snapshots since there was a request to keep them.
The daily snapshots are now in a subdirectory named daily of the snapshots
directory and should continue working as before.
At the top level, there should (starting after tonight) be snapshots from
the 2.6 and main branches. The 2.6 snapshots will use the version number
from git describe. Since that's useless for main because of our branching
strategy, the main snapshots will still be time-based, but the version
number will be a little different (2.7-YYYYMMDD), and the date will be
that of the most recent commit. Both should only be generated if
something changed.
If you want to keep using the snapshots as before, just update your path
to use the daily directory.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 5
Date: Sun, 12 Sep 2021 21:21:56 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN snapshot changes
Message-ID: <[email protected]>
Content-Type: text/plain
Oh, and I should have noted that I probably didn't get this right, so the
chances are high that no snapshot will show up tomorrow and I'll have to
fix some bugs and iterate on it.
--
Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 133, Issue 6
*******************************************
