Switch to new HTTPS-capable domains for PPAs
Bug #1959015 reported by
Colin Watson
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| software-properties (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04.
The changes are:
* http://
* https:/
Related branches
~cjwatson/software-properties:new-ppa-domains
- Ubuntu Core Development Team: Pending requested
-
Diff: 88 lines (+21/-9)5 files modifieddebian/changelog (+6/-0)
softwareproperties/ppa.py (+9/-3)
tests/test_add_apt_repository.py (+1/-1)
tests/test_dbus.py (+1/-1)
tests/test_shortcuts.py (+4/-4)
| summary: |
- Switch to new HTTPS-capable domain for PPAs + Switch to new HTTPS-capable domains for PPAs |
| tags: | added: rls-jj-incoming |
| tags: | added: fr-2003 |
| Changed in software-properties (Ubuntu Jammy): | |
| importance: | Undecided → Medium |
| tags: | removed: rls-jj-incoming |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in software-properties (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in software-properties (Ubuntu Jammy): | |
| status: | Confirmed → Fix Released |
| Changed in software-properties (Ubuntu): | |
| assignee: | nobody → Kevin bush (akjk32002) |
| Changed in software-properties (Ubuntu Jammy): | |
| assignee: | nobody → Kevin bush (akjk32002) |
| Changed in software-properties (Ubuntu): | |
| assignee: | Kevin bush (akjk32002) → nobody |
| Changed in software-properties (Ubuntu Jammy): | |
| assignee: | Kevin bush (akjk32002) → nobody |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.