[MIR] libcloudproviders

Bug #1998492 reported by Sebastien Bacher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libcloudproviders (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

[Availability]
The package libcloudproviders is already in Ubuntu universe.
The package libcloudproviders build for the architectures it is designed to work on.
It currently builds and works for architetcures: amd64 arm64 armhf i386 ppc64el riscv64 s390x
Link to package https://launchpad.net/ubuntu/+source/libcloudproviders

[Rationale]
- The package libcloudproviders is required in Ubuntu main for cloud providers integration in the GTK fileselector and nautilus sidepanel
- The feature will benefit users of the supported services (current only nextcloud)
- The package libcloudproviders is a new runtime dependency of package nautilus that we already support

- The package libcloudproviders is required in Ubuntu main no later than Feb 23 due to feature freeze

[Security]
- No CVEs/security issues in this software in the past

- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024)
- Packages does not contain extensions to security-sensitive software

[Quality assurance - function/usage]
- The package works well right after install

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu and has no open reports
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libcloudproviders/+bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libcloudproviders
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
- The package does not run a test at build time because upstream doesn't provide one, that's something we should work on prior to promotion

- The package does not run an autopkgtest but upstream has installed tests which could probably be enabled for that purpose, that's something we need to work on

- The package does have not failing autopkgtests right now

[Quality assurance - packaging]
- debian/watch is present and works

- The Maintainer information is correct since the package is in sync with Debian

- Please link to a recent build log of the package https://launchpadlibrarian.net/564381026/buildlog_ubuntu-jammy-amd64.libcloudproviders_0.3.1-2_BUILDING.txt.gz

- The existing minor lintian warnings are fixed in the packaging Vcs

- Lintian overrides are not present

- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies

- The package will be installed by default, but does not ask debconf questions

- Packaging and build is easy, link to d/rules https://salsa.debian.org/gnome-team/libcloudproviders/-/blob/debian/master/debian/rules

[UI standards]
- Application is not end-user facing (does not need translation)

[Dependencies]
- No further depends or recommends dependencies that are not yet in main

[Standards compliance]
- This package correctly follows FHS and Debian Policy

[Maintenance/Owner]
- Owning Team will be desktop-packages
- Team is not yet, but will subscribe to the package before promotion

- This does not use static builds
- This does not use vendored code
- This package is not rust based
- The package successfully built during the most recent test rebuild

[Background information]
The Package description explains the package well
Upstream Name is libcloudproviders
Link to upstream project https://gitlab.gnome.org/World/libcloudproviders

Revision history for this message
Sebastien Bacher (seb128) wrote :

setting as incomplete and not subscribing ubuntu-mir for now since it's not likely to be accepted until we figure out a better testing story

Changed in libcloudproviders (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libcloudproviders (Ubuntu) because there has been no activity for 60 days.]

Changed in libcloudproviders (Ubuntu):
status: Incomplete → Expired
description: updated
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.