From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: The desktop file shipped with spotify-adblock package doesn't suit Void installation of Spotify
Date: Sat, 18 Jun 2022 14:08:04 +0200 [thread overview]
Message-ID: <20220618120804.IMgSKX_y8H_RFeVVcDUT2vSbXWvyubR3kdIb5od-MEE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37596@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/37596#issuecomment-1159453337
Comment:
> Seems there's at least two bugs with current .desktop files, since there's another I posted a few days ago:
> https://github.com/void-linux/void-packages/issues/37555
>
> Should we merge those reports for clarity reasons, I wonder?
No, that's a different bug, it's not related to this at all.
> Sorry for intruding, but my own bug report accessed through the link above in this comment, since it was posted two days before the new "forms" were implemented, currently lacks the "bug"/"needs-testing" flags. Is it possible to add those, or should I just close the issue and re-post? Commenting here since both issues, although technically different, are still pretty similar, and maybe should be merged.
I will mark it manually.
prev parent reply other threads:[~2022-06-18 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 11:11 [ISSUE] " JuniorSuperTux
2022-06-18 11:36 ` TeusLollo
2022-06-18 11:37 ` TeusLollo
2022-06-18 11:42 ` TeusLollo
2022-06-18 11:43 ` TeusLollo
2022-06-18 11:43 ` TeusLollo
2022-06-18 12:08 ` paper42 [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=20220618120804.IMgSKX_y8H_RFeVVcDUT2vSbXWvyubR3kdIb5od-MEE@z \
--to=paper42@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).