all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vinicius Monego <monego@posteo.net>
Cc: 53394@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#53394] [PATCH] gnu: Openbox: Make compatible with Python 3.
Date: Tue, 29 Mar 2022 12:06:24 +0200	[thread overview]
Message-ID: <87zgl913a7.fsf_-_@gnu.org> (raw)
In-Reply-To: <1f60b35cb7b09c8f0799378b9fcdf1be442d415a.camel@posteo.net> (Vinicius Monego's message of "Sun, 06 Feb 2022 18:56:14 +0000")

Leo, Vinicius,

What’s the status of this patch?  Looks like it was almost ready.

Thanks,
Ludo’.

Vinicius Monego <monego@posteo.net> skribis:

> Em qui, 2022-01-20 às 13:11 -0500, Leo Famulari escreveu:
>> As the patch file says, Openbox seems abandoned upstream. So, as
>> Python 2 is
>> phased out, we can either use a patch like this, or remove Openbox.
>> 
>> I rebuilt all affected packages on x86_64-linux, and there were no
>> new build
>> failures, only the same failures as before this patch:
>> 
>> kdepim-runtime-20.04.1
>> kmail-20.04.1
>> akregator-20.04.1
>> scorep-openmpi-3.1
>> smb4k-3.0.6
>> 
>
> [...]
>
> I noticed that with 'python' the shebang in libexec/openbox-xdg-
> autostart becomes '#!/usr/bin/env python' while with python-wrapper it
> changes to the store path.
>
> I also 'cat' that file and the code is still in Python 2. Can you check
> this?
>
> openbox.scm is missing the copyright line, and python2-xdg should be
> changed to python-xdg. There are trailing whitespaces in the patch.




      reply	other threads:[~2022-03-29 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 18:11 [bug#53394] [PATCH] gnu: Openbox: Make compatible with Python 3 Leo Famulari
2022-02-06 18:56 ` Vinicius Monego
2022-03-29 10:06   ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgl913a7.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53394@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=monego@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.