Github messages for voidlinux
 help / color / mirror / Atom feed
From: metaleap <metaleap@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: SFML: update to 2.6.1
Date: Tue, 05 Dec 2023 13:56:09 +0100	[thread overview]
Message-ID: <20231205125609.muLTJzg5zH7tqkAjx_c7rVZc41ccTkPILx8U5EKdY8Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47595@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

New comment by metaleap on void-packages repository

https://github.com/void-linux/void-packages/pull/47595#issuecomment-1840699640

Comment:
> There was a different attempt at updating SFML #47454 with a working SFML template,

Thanks for _that_ hint, @Johnnynator ! The error I had earlier no longer occurs locally now, having brought in from #47454 what here was missing. Very nice, hope it'll be the same in the CI/CD pipeline stuff here.

> but missing the updates to all the revdeps.

~~Will follow~~ just did the steps, no errors locally afterwards with `./xbps-src pkg SFML` so let's see...

  parent reply	other threads:[~2023-12-05 12:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 11:07 [PR PATCH] " metaleap
2023-12-05 11:35 ` [PR PATCH] [Updated] " metaleap
2023-12-05 11:44 ` Johnnynator
2023-12-05 12:22 ` [PR PATCH] [Updated] " metaleap
2023-12-05 12:28 ` metaleap
2023-12-05 12:29 ` metaleap
2023-12-05 12:29 ` metaleap
2023-12-05 12:34 ` metaleap
2023-12-05 12:52 ` [PR PATCH] [Updated] " metaleap
2023-12-05 12:55 ` metaleap
2023-12-05 12:55 ` metaleap
2023-12-05 12:56 ` metaleap [this message]
2023-12-05 12:56 ` metaleap
2023-12-05 13:15 ` metaleap
2023-12-05 16:26 ` metaleap
2023-12-05 23:22 ` [PR PATCH] [Closed]: " Johnnynator
2023-12-05 23:24 ` Johnnynator
2023-12-06  7:27 ` metaleap
  -- strict thread matches above, loose matches on Subject: below --
2023-11-28  0:36 [PR PATCH] " ChrisMalnick
2023-11-28 11:34 ` Johnnynator

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=20231205125609.muLTJzg5zH7tqkAjx_c7rVZc41ccTkPILx8U5EKdY8Q@z \
    --to=metaleap@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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. 
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 NNTP newsgroup(s).