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. Re: Openssl 3.0.0 (Russ Allbery)
   2. Re: INN snapshot changes (Russ Allbery)


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 Sep 2021 10:58:57 -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:

> All of the /usr/libXX directories exist on the Debian Buster I have:

> 8:34 news@vps /usr% ls -l
> total 100K
> drwxr-xr-x  2 root root  48K sept.  3 07:47 bin/
> drwxr-xr-x  2 root root 4,0K nov.  22  2020 games/
> drwxr-xr-x 41 root root 4,0K ao?t   6 08:45 include/
> drwxr-xr-x 58 root root 4,0K juil. 13 18:05 lib/
> drwxr-xr-x  2 root root 4,0K janv.  8  2021 lib32/
> drwxr-xr-x  2 root root 4,0K janv.  8  2021 lib64/
> drwxr-xr-x  2 root root 4,0K janv.  8  2021 libx32/
> drwxr-xr-x 10 root root 4,0K janv.  8  2021 local/
> drwxr-xr-x  2 root root  12K ao?t   3 08:17 sbin/
> drwxr-xr-x 98 root root 4,0K juil. 13 18:05 share/
> drwxr-xr-x  2 root root 4,0K nov.  22  2020 src/

> Though everything is in /usr/lib, and only the symlink to the dynamic
> loader in /usr/lib64:

> 8:35 news@vps /usr% ls lib32
> 8:35 news@vps /usr% ls libx32
> 8:35 news@vps /usr% ls lib64
> ld-linux-x86-64.so.2@
> 8:35 news@vps /usr% ls lib | wc -l
> 63

> Hmmm...  Maybe it is a non-standard installation?
> It is how this VPS was delivered to me.

Oh!  Right!  Because it's usrmerged.  So the loader, which has to be in
/lib64, has been moved to /usr/lib64, so all of this has now become
pointless.

> I've seen the commit you've done in rra-c-util about that.  I confirm
> the issue for OpenSSL 3.0.0 is fixed.  RRA_SET_LDFLAGS correctly sees
> the lib64 directory and sets LDFLAGS accordingly.

> INN does not use RRA_SET_LIBDIR but as far as I see, I believe the
> behaviour is unchanged from before.

Great, and I'll remove the test for /usr now as well because I somehow
missed that RRA_SET_LIBDIR already checks to see if the library directory
exists anyway, and usrmerge makes this all obsolete.

Sorry about the confusion.  I think I'm finally up to speed now.  Thank
you for the explanations!

-- 
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: Tue, 14 Sep 2021 11:00:29 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN snapshot changes
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

Julien ?LIE <[email protected]> writes:

> There seems to be a synchronisation issue though because latest CURRENT
> is 20210912, latest STABLE is 20210910 and inn-2.7-20210913.tar.gz is
> not present at <https://downloads.isc.org/isc/inn/snapshots/>...

Yeah, I'm getting all sorts of weird timeout errors from their rsync
client talking to my server.  I think something may be having trouble on
the ISC side.

-- 
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 8
*******************************************

Reply via email to