From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>, 66015-done@debbugs.gnu.org
Subject: bug#66015: [PATCH] gnu: python-pyxel: Update to 1.4.3-2.be75b72.
Date: Sat, 16 Sep 2023 17:53:47 +0200 [thread overview]
Message-ID: <f8669f03ebb641c89476fbe70be1c232ba71cbf4.camel@gmail.com> (raw)
In-Reply-To: <86led64ib8.fsf@gmail.com>
Am Samstag, dem 16.09.2023 um 10:46 +0200 schrieb Simon Tournier:
> Hi Liliana,
>
> Oh, cool! That was fast. :-) Thank you.
>
> On Fri, 15 Sep 2023 at 21:53, Liliana Marie Prikler
> <liliana.prikler@gmail.com> wrote:
> > * gnu/packages/game-development.scm (python-pyxel): Update to
> > 1.4.3-2.be75b72.
> > [version]: Use git-version even though it is a release.
> > [source]<git-reference>: Use commit.
> > <snippet>: Adjust accordingly.
>
> I have not tried the patch but LGTM. If it builds fine for you, feel
> free to push… and close. :-)
I only rarely submit patches that don't at least build for myself.
Pushed and done.
> > Refering to things by commit ought to be fine since we have SWH as
> > an additional buffer.
>
> If upstream removes Git commit
> be75b724cae9e10e56a82a5421f9dd65390f1a06
> then it is an interesting use-case for testing Guix robustness when
> fallbacking to SWH. :-)
>
> I expect that it just works™ but I am not aware of any real world
> test about this very same use-case. Wait and see.
Yeah, I doubt that they'll reuse it this late in the game, but you're
right that we're basically walking on dreams rn.
Cheers
prev parent reply other threads:[~2023-09-16 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 19:09 bug#66015: Removal of python-pyxel Simon Tournier
2023-09-15 19:53 ` bug#66015: [PATCH] gnu: python-pyxel: Update to 1.4.3-2.be75b72 Liliana Marie Prikler
2023-09-16 8:46 ` Simon Tournier
2023-09-16 15:53 ` Liliana Marie Prikler [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8669f03ebb641c89476fbe70be1c232ba71cbf4.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=66015-done@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).