Skip to content

Handle repository label changes #622

Open

Description

@kneekoo

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.

Activity

  1. codingthat commented on Jun 3, 2020

    @codingthat

    Note to those still in the habit of typing apt-get instead of apt, the former also doesn't offer to fix it for you.

  2. kneekoo commented on Jul 17, 2020

    @kneekoo
    Author

    Another one:

    E: Repository 'http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal InRelease' changed its 'Label' value from 'lutris' to 'Lutris stable'
    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] y
    
    
  3. kneekoo commented on Feb 27, 2025

    @kneekoo
    Author

    This is still an issue with Linux Mint 22.1 and mintUpdate 7.0.6, we're stil forced to do apt update in the terminal to accept the label change, or mintUpdate cannot perform updates from the affected repositories.

    E: Repository 'https://ppa.launchpadcontent.net/minetestdevs/stable/ubuntu noble InRelease' changed its 'Label' value from 'Luanti Stable Releases' to 'Minetest Stable Releases'
    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] y
    
  4. kneekoo commented on Apr 9, 2026

    @kneekoo
    Author

    This is still an issue in Mint 22.3 with mintUpdate 7.1.4. Please look into this.

  5. FrivolousSquid commented on Apr 10, 2026

    @FrivolousSquid

    This also hit me today. I gave a basic attempt at trying to debug it (which is an adventure, as I'm not very familiar with debugging python). In my case, the full dialog box's text is:

    Failed to download repository information
    Check your Internet connection.
    Details:
    W:This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details., E:Repository 'https://ppa.launchpadcontent.net/ubuntuhandbook1/gimp-3/ubuntu noble InRelease' changed its 'Label' value from 'GIMP 3.0' to 'GIMP 3.x'

    What I've managed to find so far:

    1. There appears to be code to catch the text of this error message via string matching on "changed its" in mintUpdate.py at line 2292, which doesn't seem to ever get executed:
      if "apt.cache.FetchFailedException" in error and " changed its " in error:
      error += "\n\n%s" % _("Run 'apt update' in a terminal window to address this")

    2. The actual text of the error dialog box appears to be coming from aptkit, rather than mintUpdate, with error ERROR_REPO_DOWNLOAD_FAILED

    I'm really not sure where to take it from here, but I hope that helps point someone in the right direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions