Update release name in working PPAs upgrades to non-existing PPA name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Y PPA Manager |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The functionality "Update release name in working PPAs" says it upgrades the ubuntu name but only if the PPA works with the new Ubuntu version.
It actually upgrades all PPAs, making some of them non-working.
Steps to reproduce:
I have upgraded from Xenial to Yakkety.
I have all my PPAs updated to yakkety, except docker.list which does not have yakkety, so it stays to xenial.
When I do "sudo apt update" I get no errors.
Then I use the function in YPPA above. I expect that YPPA will find my docker PPA. Will try it with yakkety, see it does not work and leave my PPA with xenial.
However, the PPA is updated to yakkety.
Then update gives me this:
---
W: The repository 'https:/
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https:/
E: Some index files failed to download. They have been ignored, or old ones used instead.
---
This is my "docker.list" file when update is working with no errors and before running YPPA:
deb https:/
And this is after YPPA and with the update error:
deb https:/
Changed in y-ppa-manager: | |
status: | In Progress → Fix Released |
Thank you for the bug report!
The Docker repository you're using is not a Launchpad PPA and somehow Y PPA Manager sees it as supporting the new release and updates it. It does only update working PPAs as long as they are Launchpad PPAs.
I'll look into it, but since third-party repository don't follow some standards, I may have to disable this feature for non-Launchpad PPAs.