| 2023-05-21 16:24:07 |
Jeremy Bícha |
bug |
|
|
added bug |
| 2023-05-21 16:24:19 |
Jeremy Bícha |
bug |
|
|
added subscriber MIR approval team |
| 2023-05-21 16:26:49 |
Jeremy Bícha |
description |
[Availability]
The package cairomm1.16 is already in Ubuntu universe.
The package cairomm1.16 is built for all Ubuntu architectures except i386 (where it is not needed)
Link to package https://launchpad.net/ubuntu/+source/cairomm1.16
[Rationale]
- The package cairomm1.16 is a new runtime dependency of package transmission that we already support. (Transmission has been included in Ubuntu Desktop for many years. Transmission previously used C for the desktop app but C++ for much of the rest of the codebase. With the latest version, Transmission has standardized on C++ for all its codebase.)
- cairomm1.16 is part of the GTK4 stack for C++. A different source package, cairomm, is part of the GTK3 C++ stack. We are not yet able to drop the GTK3 C++ stack to universe. However, we do want to support GTK4 C++ now. GTK4 is now used for a considerable amount of default Ubuntu Desktop apps.
- There are 3 GTK3 C++ apps in main, gparted, gnome-system-monitor, and open-vm-tools-desktop.
+ It seems likely that gnome-system-monitor will be ported to GTK4 for GNOME 45 (Ubuntu 23.10) or at least GNOME 46 (Ubuntu 24.04 LTS). See the checklist and recent comments at https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/merge_requests/55
+ gparted is included in the Ubuntu Desktop installer only. It is not part of the default install. There currently are no plans to port gparted to GTK4. https://gitlab.gnome.org/GNOME/gparted/-/issues/176
+ open-vm-tools-desktop might not need to be in main. If this is a concern, we should check with the Server and Desktop teams.
- The package cairomm1.16 is required in Ubuntu main no later than August 17, Ubuntu 23.10 Feature Freeze, because it is a dependency of transmission and perhaps gnome-system-monitor 45.
[Security]
- No CVEs/security issues in this software in the past
+ https://ubuntu.com/security/cve?package=cairomm
+ https://security-tracker.debian.org/tracker/source-package/cairomm
+ https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=cairomm
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Package does not open privileged ports (ports < 1024)
- Package does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...)
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs
+ Ubuntu https://bugs.launchpad.net/ubuntu/+source/cairomm
https://bugs.launchpad.net/ubuntu/+source/cairomm1.16
+ Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm1.16
+ Upstream https://gitlab.gnome.org/GNOME/cairomm/-/issues
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/cairomm1.16/1.16.2-3/+latestbuild/amd64
- The package does not run an autopkgtest
gtkmm4.0 does have basic build tests and an autopkgtest. Those test would fail if cairomm1.16 is seriously broken.
RULE: - If no build tests nor autopkgtests are included, and/or if the package
RULE: requires specific hardware to perform testing, the subscribed team
RULE: must provide a written test plan in a comment to the MIR bug, and
RULE: commit to running that test either at each upload of the package or
RULE: at least once each release cycle. In the comment to the MIR bug,
RULE: please link to the codebase of these tests (scripts or doc of manual
RULE: steps) and attach a full log of these test runs. This is meant to
RULE: assess their validity (e.g. not just superficial)
TODO: - The package can not be tested at build or autopktest time because TBD
TODO: to make up for that here TBD is a test plan/automation and example
TODO: test TBD (logs/scripts)
RULE: - In some cases a solution that is about to be promoted consists of
RULE: several very small libraries and one actual application uniting them
RULE: to achieve something useful. This is rather common in the go/rust space.
RULE: In that case often these micro-libs on their own can and should only
RULE: provide low level unit-tests. But more complex autopkgtests make no
RULE: sense on that level. Therefore in those cases one might want to test on
RULE: the solution level.
RULE: - Process wise MIR-requesting teams can ask (on the bug) for this
RULE: special case to apply for a given case, which reduces the test
RULE: constraints on the micro libraries but in return increases the
RULE: requirements for the test of the actual app/solution.
RULE: - Since this might promote micro-lib packages to main with less than
RULE: the common level of QA any further MIRed program using them will have
RULE: to provide the same amount of increased testing.
TODO: - This package is minimal and will be tested in a more wide reaching
TODO: solution context TBD, details about this testing are here TBD
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field (package is maintained in Debian)
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package
https://launchpad.net/ubuntu/+source/cairomm1.16/1.14.4-2/+latestbuild/amd64
- Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug.
- 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
https://salsa.debian.org/gnome-team/cairomm1.16/-/blob/debian/master/debian/rules
[UI standards]
- Application is not end-user facing (does not need translation)
- Application is not end-user facing (does not need .desktop file)
[Dependencies]
- There is a dependency that is not yet in main, MIR for libsigc++-3.0 is LP: #2020272
[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 cairomm
Link to upstream project https://gitlab.gnome.org/GNOME/cairomm |
[Availability]
The package cairomm1.16 is already in Ubuntu universe.
The package cairomm1.16 is built for all Ubuntu architectures except i386 (where it is not needed)
Link to package https://launchpad.net/ubuntu/+source/cairomm1.16
[Rationale]
- The package cairomm1.16 is a new runtime dependency of package transmission that we already support. (Transmission has been included in Ubuntu Desktop for many years. Transmission previously used C for the desktop app but C++ for much of the rest of the codebase. With the latest version, Transmission has standardized on C++ for all its codebase.)
- cairomm1.16 is part of the GTK4 stack for C++. A different source package, cairomm, is part of the GTK3 C++ stack. We are not yet able to drop the GTK3 C++ stack to universe. However, we do want to support GTK4 C++ now. GTK4 is now used for a considerable amount of default Ubuntu Desktop apps.
- There are 3 GTK3 C++ apps in main, gparted, gnome-system-monitor, and open-vm-tools-desktop.
+ It seems likely that gnome-system-monitor will be ported to GTK4 for GNOME 45 (Ubuntu 23.10) or at least GNOME 46 (Ubuntu 24.04 LTS). See the checklist and recent comments at https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/merge_requests/55
+ gparted is included in the Ubuntu Desktop installer only. It is not part of the default install. There currently are no plans to port gparted to GTK4. https://gitlab.gnome.org/GNOME/gparted/-/issues/176
+ open-vm-tools-desktop might not need to be in main. If this is a concern, we should check with the Server and Desktop teams.
- The package cairomm1.16 is required in Ubuntu main no later than August 17, Ubuntu 23.10 Feature Freeze, because it is a dependency of transmission and perhaps gnome-system-monitor 45.
[Security]
- No CVEs/security issues in this software in the past
+ https://ubuntu.com/security/cve?package=cairomm
+ https://security-tracker.debian.org/tracker/source-package/cairomm
+ https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=cairomm
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Package does not open privileged ports (ports < 1024)
- Package does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...)
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs
+ Ubuntu https://bugs.launchpad.net/ubuntu/+source/cairomm
https://bugs.launchpad.net/ubuntu/+source/cairomm1.16
+ Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm1.16
+ Upstream https://gitlab.freedesktop.org/cairo/cairomm/-/issues
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/cairomm1.16/1.16.2-3/+latestbuild/amd64
- The package does not run an autopkgtest
gtkmm4.0 does have basic build tests and an autopkgtest. Those test would fail if cairomm1.16 is seriously broken.
RULE: - If no build tests nor autopkgtests are included, and/or if the package
RULE: requires specific hardware to perform testing, the subscribed team
RULE: must provide a written test plan in a comment to the MIR bug, and
RULE: commit to running that test either at each upload of the package or
RULE: at least once each release cycle. In the comment to the MIR bug,
RULE: please link to the codebase of these tests (scripts or doc of manual
RULE: steps) and attach a full log of these test runs. This is meant to
RULE: assess their validity (e.g. not just superficial)
TODO: - The package can not be tested at build or autopktest time because TBD
TODO: to make up for that here TBD is a test plan/automation and example
TODO: test TBD (logs/scripts)
RULE: - In some cases a solution that is about to be promoted consists of
RULE: several very small libraries and one actual application uniting them
RULE: to achieve something useful. This is rather common in the go/rust space.
RULE: In that case often these micro-libs on their own can and should only
RULE: provide low level unit-tests. But more complex autopkgtests make no
RULE: sense on that level. Therefore in those cases one might want to test on
RULE: the solution level.
RULE: - Process wise MIR-requesting teams can ask (on the bug) for this
RULE: special case to apply for a given case, which reduces the test
RULE: constraints on the micro libraries but in return increases the
RULE: requirements for the test of the actual app/solution.
RULE: - Since this might promote micro-lib packages to main with less than
RULE: the common level of QA any further MIRed program using them will have
RULE: to provide the same amount of increased testing.
TODO: - This package is minimal and will be tested in a more wide reaching
TODO: solution context TBD, details about this testing are here TBD
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field (package is maintained in Debian)
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package
https://launchpad.net/ubuntu/+source/cairomm1.16/1.14.4-2/+latestbuild/amd64
- Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug.
- 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
https://salsa.debian.org/gnome-team/cairomm1.16/-/blob/debian/master/debian/rules
[UI standards]
- Application is not end-user facing (does not need translation)
- Application is not end-user facing (does not need .desktop file)
[Dependencies]
- There is a dependency that is not yet in main, MIR for libsigc++-3.0 is LP: #2020272
[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 cairomm
Link to upstream project https://cairographics.org/cairomm/
https://gitlab.freedesktop.org/cairo/cairomm |
|
| 2023-05-30 11:45:18 |
Jeremy Bícha |
description |
[Availability]
The package cairomm1.16 is already in Ubuntu universe.
The package cairomm1.16 is built for all Ubuntu architectures except i386 (where it is not needed)
Link to package https://launchpad.net/ubuntu/+source/cairomm1.16
[Rationale]
- The package cairomm1.16 is a new runtime dependency of package transmission that we already support. (Transmission has been included in Ubuntu Desktop for many years. Transmission previously used C for the desktop app but C++ for much of the rest of the codebase. With the latest version, Transmission has standardized on C++ for all its codebase.)
- cairomm1.16 is part of the GTK4 stack for C++. A different source package, cairomm, is part of the GTK3 C++ stack. We are not yet able to drop the GTK3 C++ stack to universe. However, we do want to support GTK4 C++ now. GTK4 is now used for a considerable amount of default Ubuntu Desktop apps.
- There are 3 GTK3 C++ apps in main, gparted, gnome-system-monitor, and open-vm-tools-desktop.
+ It seems likely that gnome-system-monitor will be ported to GTK4 for GNOME 45 (Ubuntu 23.10) or at least GNOME 46 (Ubuntu 24.04 LTS). See the checklist and recent comments at https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/merge_requests/55
+ gparted is included in the Ubuntu Desktop installer only. It is not part of the default install. There currently are no plans to port gparted to GTK4. https://gitlab.gnome.org/GNOME/gparted/-/issues/176
+ open-vm-tools-desktop might not need to be in main. If this is a concern, we should check with the Server and Desktop teams.
- The package cairomm1.16 is required in Ubuntu main no later than August 17, Ubuntu 23.10 Feature Freeze, because it is a dependency of transmission and perhaps gnome-system-monitor 45.
[Security]
- No CVEs/security issues in this software in the past
+ https://ubuntu.com/security/cve?package=cairomm
+ https://security-tracker.debian.org/tracker/source-package/cairomm
+ https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=cairomm
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Package does not open privileged ports (ports < 1024)
- Package does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...)
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs
+ Ubuntu https://bugs.launchpad.net/ubuntu/+source/cairomm
https://bugs.launchpad.net/ubuntu/+source/cairomm1.16
+ Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm1.16
+ Upstream https://gitlab.freedesktop.org/cairo/cairomm/-/issues
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/cairomm1.16/1.16.2-3/+latestbuild/amd64
- The package does not run an autopkgtest
gtkmm4.0 does have basic build tests and an autopkgtest. Those test would fail if cairomm1.16 is seriously broken.
RULE: - If no build tests nor autopkgtests are included, and/or if the package
RULE: requires specific hardware to perform testing, the subscribed team
RULE: must provide a written test plan in a comment to the MIR bug, and
RULE: commit to running that test either at each upload of the package or
RULE: at least once each release cycle. In the comment to the MIR bug,
RULE: please link to the codebase of these tests (scripts or doc of manual
RULE: steps) and attach a full log of these test runs. This is meant to
RULE: assess their validity (e.g. not just superficial)
TODO: - The package can not be tested at build or autopktest time because TBD
TODO: to make up for that here TBD is a test plan/automation and example
TODO: test TBD (logs/scripts)
RULE: - In some cases a solution that is about to be promoted consists of
RULE: several very small libraries and one actual application uniting them
RULE: to achieve something useful. This is rather common in the go/rust space.
RULE: In that case often these micro-libs on their own can and should only
RULE: provide low level unit-tests. But more complex autopkgtests make no
RULE: sense on that level. Therefore in those cases one might want to test on
RULE: the solution level.
RULE: - Process wise MIR-requesting teams can ask (on the bug) for this
RULE: special case to apply for a given case, which reduces the test
RULE: constraints on the micro libraries but in return increases the
RULE: requirements for the test of the actual app/solution.
RULE: - Since this might promote micro-lib packages to main with less than
RULE: the common level of QA any further MIRed program using them will have
RULE: to provide the same amount of increased testing.
TODO: - This package is minimal and will be tested in a more wide reaching
TODO: solution context TBD, details about this testing are here TBD
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field (package is maintained in Debian)
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package
https://launchpad.net/ubuntu/+source/cairomm1.16/1.14.4-2/+latestbuild/amd64
- Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug.
- 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
https://salsa.debian.org/gnome-team/cairomm1.16/-/blob/debian/master/debian/rules
[UI standards]
- Application is not end-user facing (does not need translation)
- Application is not end-user facing (does not need .desktop file)
[Dependencies]
- There is a dependency that is not yet in main, MIR for libsigc++-3.0 is LP: #2020272
[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 cairomm
Link to upstream project https://cairographics.org/cairomm/
https://gitlab.freedesktop.org/cairo/cairomm |
[Availability]
The package cairomm1.16 is already in Ubuntu universe.
The package cairomm1.16 is built for all Ubuntu architectures except i386 (where it is not needed)
Link to package https://launchpad.net/ubuntu/+source/cairomm1.16
[Rationale]
- The package cairomm1.16 is a new runtime dependency of package transmission that we already support. (Transmission has been included in Ubuntu Desktop for many years. Transmission previously used C for the desktop app but C++ for much of the rest of the codebase. With the latest version, Transmission has standardized on C++ for all its codebase.)
- cairomm1.16 is part of the GTK4 stack for C++. A different source package, cairomm, is part of the GTK3 C++ stack and is currently in main. For more rationale about promoting the GTK4 stack for C++ to main, see the gtkmm4.0 MIR bug LP: #2020472
- The package cairomm1.16 is required in Ubuntu main no later than August 17, Ubuntu 23.10 Feature Freeze, because it is a dependency of transmission and perhaps gnome-system-monitor 45.
[Security]
- No CVEs/security issues in this software in the past
+ https://ubuntu.com/security/cve?package=cairomm
+ https://security-tracker.debian.org/tracker/source-package/cairomm
+ https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=cairomm
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Package does not open privileged ports (ports < 1024)
- Package does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...)
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs
+ Ubuntu https://bugs.launchpad.net/ubuntu/+source/cairomm
https://bugs.launchpad.net/ubuntu/+source/cairomm1.16
+ Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cairomm1.16
+ Upstream https://gitlab.freedesktop.org/cairo/cairomm/-/issues
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/cairomm1.16/1.16.2-3/+latestbuild/amd64
- The package runs an autopkgtest, and is currently passing on all architectures (except for i386 where it is not built)
https://autopkgtest.ubuntu.com/packages/cairomm1.16
- The package does have not failing autopkgtests right now
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field (package is maintained in Debian)
- This package does not yield massive lintian Warnings, Errors
- Please link to a recent build log of the package
https://launchpad.net/ubuntu/+source/cairomm1.16/1.14.4-2/+latestbuild/amd64
- Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug.
- 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
https://salsa.debian.org/gnome-team/cairomm1.16/-/blob/debian/master/debian/rules
[UI standards]
- Application is not end-user facing (does not need translation)
- Application is not end-user facing (does not need .desktop file)
[Dependencies]
- There is a dependency that is not yet in main, MIR for libsigc++-3.0 is LP: #2020272
[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 cairomm
Link to upstream project https://cairographics.org/cairomm/
https://gitlab.freedesktop.org/cairo/cairomm |
|
| 2023-05-30 11:45:29 |
Jeremy Bícha |
cairomm1.16 (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2023-06-20 14:39:00 |
Christian Ehrhardt |
cairomm1.16 (Ubuntu): assignee |
|
Lukas Märdian (slyon) |
|
| 2023-06-27 14:13:12 |
Lukas Märdian |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032457 |
|
| 2023-06-27 14:13:16 |
Lukas Märdian |
cairomm1.16 (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2023-06-27 14:13:22 |
Lukas Märdian |
cairomm1.16 (Ubuntu): assignee |
Lukas Märdian (slyon) |
Jeremy Bícha (jbicha) |
|
| 2023-07-05 17:47:28 |
Jeremy Bícha |
cairomm1.16 (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2023-07-05 17:47:30 |
Jeremy Bícha |
cairomm1.16 (Ubuntu): assignee |
Jeremy Bícha (jbicha) |
|
|
| 2023-07-06 06:11:00 |
Christian Ehrhardt |
cairomm1.16 (Ubuntu): status |
Confirmed |
Fix Committed |
|
| 2023-07-08 05:25:50 |
Steve Langasek |
cairomm1.16 (Ubuntu): status |
Fix Committed |
Fix Released |
|
