You apparently need more perl packages installed, see
https://stackoverflow.com/questions/70464585/error-when-installing-openssl-3-0-1-cant-locate-ipc-cmd-pm-in-inc
On Fri, Sep 8, 2023 at 7:03 PM Shruti <
shruti.barapa...@students.iiserpune.ac.in> wrote:
> Using cached file
> /scratch/user/sagema
Using cached file
/scratch/user/sagemath/sage-10.1/upstream/openssl-3.0.8.tar.gz
openssl-3.0.8
Setting up build directory for openssl-3.0.8
Finished extraction
No patch files found in ../patches
**
we'll need the full logs, including the top-level config.log
On Friday, September 8, 2023 at 10:50:15 AM UTC-7 Shruti wrote:
> Error message in the log file:
> Setting up build directory for openssl-3.0.8
> Finished extraction
> No patch files found in ../patches
> Package 'openssl' is currently
Error message in the log file:
Setting up build directory for openssl-3.0.8
Finished extraction
No patch files found in ../patches
Package 'openssl' is currently not installed
No legacy uninstaller found for 'openssl'; nothing to do
Configuring openssl for target reported by gcc -dumpmachine:
x86
Hi,
Please review
https://github.com/sagemath/sage/pull/36144
and
https://github.com/sagemath/sage-binder-env/pull/16
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an em
> Note that "github-actions[bot]" in Reviewers. What does this mean? I
don't understand how this happened...
>
> Could this be somehow related with the recent synchronization turn-on?
Yes, since the GitHub state request-changes was not set before you add the s:
needs work label the bot sets it f
> I think this is too verbose. In particular, the message "kwankyu
requested changes for this PR" is redundant.
>From the point of view of a developer familiar with Trac status labels, I
agree. However, a key goal of the GitHub migration was to attract new
developers who are familiar with the G
