Handle repository label changes

Open

#622 opened on Jun 1, 2020 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 48/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: python
Domain: desktop

Research direction

Start by reproducing the PPA Label-change error in the update manager and compare it with the terminal apt behavior described in the issue. Trace the update-manager path that reports the synaptic error and determine how repository changes are surfaced. Done means users can explicitly accept the Label change in the update manager, or receive a clear notification and recovery path.

Written by the indexing model from the issue text.

Description

FEATURE REQUEST

Is your feature request related to a problem? Please describe.
PPAs can change their 'Label' values and mintupdate currently can't do anything about it but report it as a synaptic error and you can no longer use that repository for updates.

The issue reported by the update manager:
Repository 'http://ppa.launchpad.net/kisak/kisak-mesa/ubuntu bionic InRelease' changed its 'Label' value from 'kisak-mesa' to 'kisak-mesa fresh'

While using apt in the terminal, things are a bit different in the sense that you're presented with the option to accept the change and continue to use that source:

E: Repository 'http://ppa.launchpad.net/kisak/kisak-mesa/ubuntu bionic InRelease' changed its 'Label' value from 'kisak-mesa' to 'kisak-mesa fresh'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

Describe the solution you'd like
It would be nice if the update manager would ask the same, so the users can fix it without having to use the terminal - because this doesn't go away by itself.

Describe alternatives you've considered
Alternatively, you could silently disable that PPA and notify the user that they have to accept the changes by using the terminal.

Dominant language: Python
Stars: 425
Forks: 190
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

RadioSelectButtonGroup does not render as a button group through bootstrap_field Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

zostera/django-bootstrap4#894 · Opened Sep 21, 2026
[Bug]: control_ui.show_thinking = false does not stop the live reasoning stream, so thinking events and done.reasoning_content still reach the web UI Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

use-agent-os/agent-os#3276 · Opened Sep 21, 2026
Build fails with LTO enabled: conflicting types for z_shared_sw_isr_table between isr_tables.c and sw_isr_table.h Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

zephyrproject-rtos/zephyr#119726 · Opened Sep 21, 2026
[Bug]: redact_sensitive_text does not recognise Discord bot tokens Open

area/auth bug comp/agent P3 platform/discord type/security

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

NousResearch/hermes-agent#117848 · Opened Sep 21, 2026
Windows: hooks treat CLAUDE_PROJECT_DIR (C:/... style) as relative, session summaries written to a doubled path Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

zilliztech/memsearch#759 · Opened Sep 21, 2026

More Python issues