[MIR] libayatana-appindicator
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libayatana-appindicator (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Availability
It's available on the Ubuntu supported architectures
https:/
The package is in sync with Debian
* Rationale
The source is a community maintained replacement for our current libappindicator. Debian has transitioned and we plan to follow their lead now, demoting libappindicator to universe until we can remove it from the archive.
The binary to promote is libappindicator3-1
The request is low priority, it's a target of opportunity transition, it doesn't need to land this cycle
* Security
There is no known security issues
https:/
https:/
https:/
* Quality assurance
The desktop team is going to subscribe to the package
https:/
https:/
The source depends on some outdated libraries but that's because there are still old applications needing it, that's already the case with our libappindicator so not a change of status
The package enables upstream tests during the build but some are currently failing (and the Debian package doesn't stop the build on errors), that has been reported to Debian https:/
The package doesn't provide autopkgtests, which has been reported to Debian . That's not a regression compared to our current libappindicator
Update, the tests issue has been resolved in Debian and Impish now
* Dependencies
Package: libayatana-
Depends: libayatana-
libayatana-
* Standards compliance
current 4.5.1 standards-version, debhelper compat 13, dh style simple rules
* Maintenance
Upstream is active, the package is maintained in Debian and desktop team is going to sign up for Ubuntu
Changed in libayatana-appindicator (Ubuntu): | |
assignee: | nobody → Didier Roche (didrocks) |
Changed in libayatana-appindicator (Ubuntu): | |
status: | New → Fix Committed |
assignee: | Didier Roche (didrocks) → nobody |
Changed in libayatana-appindicator (Ubuntu): | |
status: | Fix Committed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.