From: "Ludovic Courtès" <ludo@gnu.org>
To: Sughosha <Sughosha@proton.me>
Cc: 60148@debbugs.gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#60148] [PATCH] gnu: gnome-shell-extension: Update to 20
Date: Tue, 17 Jan 2023 15:55:59 +0100 [thread overview]
Message-ID: <87k01lgqgw.fsf_-_@gnu.org> (raw)
In-Reply-To: <X3LtXijIRVGs-7QcHgg6HG574dhHuqwpdq0N2SNcQ7RuS4TehzXIDhU6l-w0yCPjqU6tXzOoawHZkbqMFCaxh0CzTr_5hypx5qOnJE9Q6OY=@proton.me> (Sughosha@proton.me's message of "Sat, 24 Dec 2022 23:20:44 +0000")
Hi,
Sughosha <Sughosha@proton.me> skribis:
> It seems the developer released it for GNOME 43 (https://github.com/hslbck/gnome-shell-extension-radio/blob/1233305a9f186732fb2d44bf574751e744ca36e7/radio%40hslbck.gmail.com/metadata.json#L2), but for me it is working fine with `gsettings set org.gnome.shell disable-extension-version-validation false`. The version currently available in Guix (v19) is anyways broken, so I would recommend updating it.
[...]
> Liliana Marie Prikler <liliana.prikler@gmail.com> schrieb am Samstag, 24. Dezember 2022 um 07:35:
[...]
>> I tried this in a VM and it warned me about a version incompatibility.
Liliana, what would you suggest? If the currently-packaged version is
already “broken”, then maybe we should apply this upgrade?
TIA,
Ludo’.
next prev parent reply other threads:[~2023-01-17 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 5:56 [bug#60148] [PATCH] gnu: gnome-shell-extension: Update to 20 Sughosha via Guix-patches via
2022-12-21 13:03 ` [bug#60148] (No Subject) Sughosha via Guix-patches via
2022-12-24 6:35 ` [bug#60148] [PATCH] gnu: gnome-shell-extension: Update to 20 Liliana Marie Prikler
2022-12-24 23:20 ` Sughosha via Guix-patches via
2023-01-17 14:55 ` Ludovic Courtès [this message]
2023-01-17 19:57 ` Liliana Marie Prikler
2023-01-22 9:11 ` bug#60148: " Liliana Marie Prikler
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=87k01lgqgw.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=60148@debbugs.gnu.org \
--cc=Sughosha@proton.me \
--cc=liliana.prikler@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 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.