Update release name in working PPAs upgrades to non-existing PPA name

Bug #1639639 reported by braykov
6
This bug affects 1 person
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://apt.dockerproject.org/repo ubuntu-yakkety Release' does not have a Release file.
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://apt.dockerproject.org/repo/dists/ubuntu-yakkety/main/binary-i386/Packages 403 Forbidden
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://apt.dockerproject.org/repo ubuntu-xenial main
And this is after YPPA and with the update error:
deb https://apt.dockerproject.org/repo ubuntu-yakkety main

Revision history for this message
Alin Andrei (nilarimogard) wrote :

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.

Changed in y-ppa-manager:
status: New → In Progress
Revision history for this message
Alin Andrei (nilarimogard) wrote :

I updated this feature to only support Launchpad PPAs. I could have fixed it for the Docker repository but then I'm sure some other third-party repositories would still cause issues, so it's better to be safe. Furthermore, Y PPA Manager is only for Launchpad PPAs and was never intended to support other repositories.

The PPA should be updated in a few minutes.

Thank you very much for the bug report!

Changed in y-ppa-manager:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.