Github messages for voidlinux
 help / color / mirror / Atom feed
From: lee2sman <lee2sman@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pyradio needs to use new pipx install method (and not allow self-update from outside Void's repo)
Date: Fri, 08 Dec 2023 21:25:34 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47653@inbox.vuxu.org> (raw)

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

New issue by lee2sman on void-packages repository

https://github.com/void-linux/void-packages/issues/47653

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.13_1 x86_64 GenuineIntel uptodate rFFFFF

### Package(s) Affected

pyradio-0.9.2.13_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/coderholic/pyradio/issues/211

### Expected behaviour

pyradio installed via Void's repo shouldn't allow update through non-distro source.

### Actual behaviour

1. pyradio currently automatically prompts and then tries to update and allow someone to update-install from a non-distro source.
2. pyradio now needs pipx for install so won't be able to update without that. See [packagers info](https://github.com/coderholic/pyradio/blob/master/docs/packagers-info.md)

### Steps to reproduce

1. run pyradio
2. It will prompt if there is a new version of the software. Click 'y' to update.
3. It will try to run update, but update fails.

             reply	other threads:[~2023-12-08 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 20:25 lee2sman [this message]
2024-01-17  0:42 ` [ISSUE] [CLOSED] " classabbyamp

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47653@inbox.vuxu.org \
    --to=lee2sman@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).