[BPO] Backport opencpn 5.6.0 from Jammy
Bug #1956004 reported by
Alec Leamas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
opencpn (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Focal |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
The current release is so old that it is unusable. Thus it forces users to the PPA at https:/
[Scope]
This is about backporting 5.6.0 from Jammy to Focal/20.04
[Other Info]
5.6.0 is in Debian Testing. The Bullseye backport is currently in the backports new queue.
Package sources: https:/
description: | updated |
summary: |
- [BPO] Backport 5.6.0 from Jammy + [BPO] Backport opencpn 5.6.0 from Jammy |
Changed in opencpn (Ubuntu): | |
importance: | Undecided → Low |
Changed in opencpn (Ubuntu Focal): | |
importance: | Undecided → Low |
tags: | added: upgrade-software-version |
To post a comment you must log in.
Adding the Debian backport checklist
- Current version is two versions behind. As a result, upstream directs all users to the PPA, a packaging which does not meet basic standards. Ergo: backporting is meaningful.
- The package has a substantial user base although this for now means the PPA users.
- Package is available in Debian Bookworm and Jammy.
- Opencpn is a leaf package, no reverse dependencies.
- No other Ubuntu backports exist.
- I also maintain the Debian package and is also fairly active in the upstream project.