bug#63077: [PATCH] gnu: gnutls: skip examples on mingw.
Hi,
On ven., 05 janv. 2024 at 13:06, Maxim Cournoyer
wrote:
> Vivien Kraus writes:
>
>> * gnu/packages/tls.scm (gnutls): Skip the doc/examples subdir on mingw,
>> because the gnulib modules are not correct.
>> ---
>> gnu/packages/tls.scm | 9 +
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
>> index 6d7cff41b0..9e16b04702 100644
>> --- a/gnu/packages/tls.scm
>> +++ b/gnu/packages/tls.scm
>> @@ -253,6 +253,15 @@ (define-public gnutls
>> (substitute* "tests/fastopen.sh"
>> (("^unset RETCODE")
>>"exit 77\n" ;skip
>> + #$@(if (target-mingw?)
>> + #~((add-after 'unpack 'skip-doc-examples
>> + ;; The examples in doc do not link to correct
>> + ;; gnulib modules.
>> + (lambda _
>> + (substitute* "doc/Makefile.in"
>> + (("SUBDIRS = examples")
>> +"SUBDIRS =")
>> + #~())
>
> Did you report it upstream? Perhaps they'd know how to properly fix it.
Digging all bugs, what about this?
It could be nice if it is fixed upstream. On the other, we could also
apply a fix waiting such fix.
WDYT?
Cheers,
simon
bug#68359: Acknowledgement (Can't pull my channel because of getaddrinfo -8 error)
Hi, On jeu., 18 janv. 2024 at 05:50, "ShinyZero0" via Bug reports for GNU Guix wrote: > Well, the issue seems to be with the commit that adds the transformed > polybar package like this: > > ``` > (define-module (zero packages polybar)) > (use-modules (guix packages) > (guix transformations) > (gnu packages wm)) > (define-public > polybar-3.7.1 > ((options->transformation > '((with-version . "polybar=3.7.1"))) polybar)) > ``` Well, the bug seems coming from your channel. Could you update it and make it compliant with Guix proper. Somehow, I am going to close this issue because it is not a bug. :-) Is it fine? Let us know if more details are required. Cheers, simon
bug#69735: [BUG] Error running any docker-composse command
Greetings, with the last Commit, Python-Docker was updated, apparently this
causes errors with Docker-Compose, the apparent solution is to update the
Docker-Composse version, but changes the installation method of Python to Go,
so I can't Generate the patch to update the package.
Give the error:
/gnu/store/v2sr2wqfjnnlf4cr6fbaadslrlz9cdj4-python-paramiko-2.7.2/lib/python3.10/site-packages/paramiko/transport.py:219:
CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
Traceback (most recent call last):
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/bin/.docker-compose-real",
line 33, in
sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts',
'docker-compose')())
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/main.py",
line 81, in main
command_func()
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/main.py",
line 200, in perform_command
project = project_from_options('.', options)
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/command.py",
line 60, in project_from_options
return get_project(
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/command.py",
line 152, in get_project
client = get_client(
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/docker_client.py",
line 41, in get_client
client = docker_client(
File
"/gnu/store/fh9sgccvjx86f168qvh7rvan3rnbydlg-docker-compose-1.29.2/lib/python3.10/site-packages/compose/cli/docker_client.py",
line 124, in docker_client
kwargs = kwargs_from_env(environment=environment, ssl_version=tls_version)
TypeError: kwargs_from_env() got an unexpected keyword argument 'ssl_version'
Thanks
bug#69735: [BUG] Error running any docker-composse command
I found this that can be helpful to solve the problem https://github.com/bonfire-networks/bonfire-app/blob/main/manifest.scm
bug#63077: [PATCH] gnu: gnutls: skip examples on mingw.
Hello,
Le vendredi 08 mars 2024 à 18:22 +0100, Simon Tournier a écrit :
> > > + #$@(if (target-mingw?)
> > > + #~((add-after 'unpack 'skip-doc-examples
> > > + ;; The examples in doc do not link to
> > > correct
> > > + ;; gnulib modules.
> > > + (lambda _
> > > + (substitute* "doc/Makefile.in"
> > > + (("SUBDIRS = examples")
> > > + "SUBDIRS =")
> > > + #~())
> >
> > Did you report it upstream? Perhaps they'd know how to properly
> > fix it.
>
> Digging all bugs, what about this?
>
> It could be nice if it is fixed upstream. On the other, we could
> also
> apply a fix waiting such fix.
I reported it, and I believe upstream fixed it:
https://gitlab.com/gnutls/gnutls/-/merge_requests/1761/diffs?commit_id=5db0db2e83da54d799f55984dc33039d6b22c933
However it’s difficult to check because libidn2 fails (maybe the more
recent 2.3.7 does not). This libidn2 failure seems to have been
reported here:
https://gitlab.com/libidn/libidn2/-/issues/113
I notice that libidn2 uses its own libunistring instead of the guix’
one, because libunistring is not an input of libidn2. Is this intended
to avoid a cycle?
Best regards,
Vivien
bug#48323: guix-daemon.service and guix-publish.service use deprecated StandardError/StandardOutput features
On 2023-07-20, Vagrant Cascadian wrote: > On 2022-04-29, Ludovic Courtès wrote: >> Vagrant Cascadian skribis: >> >>> Both guix-daemon.service and guix-publish.service make use of >>> StandardError=syslog and StandardOutput=syslog. >> >> [...] >> >>> So apparently need to switch the .service files to use "journal". I am >>> not sure what implications that would have for installing guix on a >>> foreign distro, such as minimum systemd version, or if anything needs >>> significant changes. >> >> Could you confirm that setting those to “journal” works on Debian? >> >> If it does, it’s probably safe now to make this change, so feel free to >> commit it in Guix. > > So, I finally got around to testing this... > > Feels a little odd just pushing after testing over a year later, > although the patch is fairly trivial... And finally pushed the patch, as 5f100c68a4a8ef9ed5599bb99c910018869bc6f3! live well, vagrant signature.asc Description: PGP signature
