** Description changed: [Availability] The package ptyxis is already in Ubuntu universe. The package ptyxis build for the architectures it is designed to work on. It currently builds and works for all Ubuntu architectures except for i386 where it is not needed. Link to package https://launchpad.net/ubuntu/+source/ptyxis [Rationale] - The package ptyxis is required in Ubuntu main for modernizing Ubuntu Desktop's terminal - The package ptyxis will generally be useful for a large part of our user base - Package ptyxis covers the same use case as gnome-terminal, but is better because [below], thereby we want to replace it. + Simpler preferences dialog but still full of features + Improved theming + Uses gtk4 (gnome-terminal will eventually switch to gtk4) - + Part of the GNOME ecosystem. GNOME's default terminal is currently GNOME Console which isn't really suitable for us. I think GNOME will eventually switch to Ptyxis as the default terminal because both gnome-terminal and gnome-console aren't ideal for GNOME. Fedora Workstation switched from gnome-terminal to Ptyxis in 2024. + + Part of the GNOME ecosystem. GNOME's default terminal is currently GNOME Console which isn't really suitable for us (too few features that we care about). I think GNOME will eventually switch to Ptyxis as the default terminal because both gnome-terminal and gnome-console aren't ideal for GNOME. Fedora Workstation switched from gnome-terminal to Ptyxis in 2024. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The binary packages ptyxis needs to be in main to achieve Ubuntu Desktop's goal of modernizing the pre-installed terminal app - All binary packages built by ptyxis need to be in main (there is only one binary package) - The package ptyxis is required in Ubuntu main no later than August 14 due to Ubuntu 25.10 Feature Freeze. We want early feedback in 25.10 before 26.04 LTS. [Security] - No CVEs/security issues in this software in the past + + https://security-tracker.debian.org/tracker/source-package/ptyxis - RULE: - Check for security relevant binaries, services and behavior. - RULE: If any are present, this requires a more in-depth security review. - RULE: Demonstrating that common isolation/risk-mitigation patterns are used - RULE: will help to raise confidence. For example a service running as root - RULE: open to the network will need to be considered very carefully. The same - RULE: service dropping the root permissions after initial initialization, - RULE: using various systemd isolation features and having a default active - RULE: apparmor profile is much less concerning and can speed up acceptance. - RULE: This helps Ubuntu, but you are encouraged to consider working with - RULE: Debian and upstream to get those security features used at wide scale. - RULE: - It might be impossible for the submitting team to check this perfectly - RULE: (the security team will), but you should be aware that deprecated - RULE: security algorithms like 3DES or TLS/SSL 1.1 are not acceptable. - RULE: If you think a package might do that it would be great to provide a - RULE: hint for the security team like "Package may use deprecated crypto" - RULE: and provide the details you have about that. - TODO: - no `suid` or `sgid` binaries - TODO-A: - no executables in `/sbin` and `/usr/sbin` - TODO-B: - Binary TBD in sbin is no problem because TBD - TODO-A: - Package does not install services, timers or recurring jobs - TODO-B: - Package does install services, timers or recurring jobs - TODO-B: TBD (list services, timers, jobs) - TODO: - Security has been kept in mind and common isolation/risk-mitigation - TODO: patterns are in place utilizing the following features: - TODO: TBD (add details and links/examples about things like dropping - TODO: permissions, using temporary environments, restricted users/groups, - TODO: seccomp, systemd isolation features, apparmor, ...) - TODO-A: - Packages does not open privileged ports (ports < 1024). - TODO-B: - Packages open privileged ports (ports < 1024), but they have - TODO-B: a reason to do so (TBD) - TODO-A: - Package does not expose any external endpoints - TODO-B: - Package does expose an external endpoint, it is - TODO-B: TBD endpoint + TBD purpose - TODO: - Packages does not contain extensions to security-sensitive software - TODO: (filters, scanners, plugins, UI skins, ...) + - no `suid` or `sgid` binaries + - no executables in `/sbin` and `/usr/sbin` - RULE: The package should not use deprecated security algorithms like 3DES or - RULE: TLS/SSL 1.1. The security team is the one responsible to check this, - RULE: but if you happen to spot something it helps to provide a hint. - RULE: Provide whatever made you suspicious as details along that statement. - RULE: Or remove the following lines entirely if you did not spot anything. - TODO: - I've spotted what I consider deprecated algorithms, the security team - TODO: should have a more careful look please, details are: + - Package does not install services, timers or recurring jobs + There is only the basic gapplication service used by most modern GTK3 or GTK4 apps. + + - Packages does not open privileged ports (ports < 1024). + - Package does not expose any external endpoints + - Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) [Quality assurance - function/usage] - The package works well right after install * There is a significant usability bug, LP: #2083705, that we expect to be able to fix with an upload of the bash package in May [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/ptyxis/ - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ptyxis - Upstream https://gitlab.gnome.org/chergert/ptyxis/-/issues [Quality assurance - testing] - The package does not run a test at build time because none have been created for this app because it is a GUI app for command line interaction. - The package does not run an autopkgtest because there isn't really a framework to test GUI apps - The package can not be well tested at build or autopkgtest time because it is only a GUI app. To make up for that: + We have created a manual test plan: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Terminal + We will execute that test plan on uploads regularly (when uploading new major releases of ptyxis to Ubuntu and before every ptyxis SRU) [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/ptyxis/48.1-1 - 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, link to debian/rules https://salsa.debian.org/gnome-team/ptyxis/-/blob/debian/latest/debian/rules [UI standards] - Application is end-user facing, Translation is present, via standard intltool/gettext or similar build and runtime internationalization system https://translations.launchpad.net/ubuntu/plucky/+source/ptyxis/+pots/ptyxis - End-user applications that ships a standard conformant desktop file https://salsa.debian.org/gnome-team/ptyxis/-/blob/debian/latest/data/org.gnome.Ptyxis.desktop.in.in [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] - The owning team will be Desktop Packages and I have their acknowledgement for that commitment - The future owning team is not yet subscribed, 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 has been built within the last 3 months in the archive - Build link on launchpad: https://launchpad.net/ubuntu/+source/ptyxis/48.1-1 [Background information] The Package description explains the package well Upstream Name is ptyxis Link to upstream project https://gitlab.gnome.org/chergert/ptyxis Link to upstream homepage https://devsuite.app/ptyxis/ The maintainer of Ptyxis is the same maintainer as gnome-builder, gnome- text-editor, and sysprof. See https://devsuite.app/ The app was originally named Prompt https://blogs.gnome.org/chergert/2023/12/14/prompt/ Once ptyxis is accepted into Ubuntu main, we will apply a build option to change the user visible branding from Ptyxis to Terminal. We will demote gnome-terminal to universe. It is possible to create custom profiles in gnome-terminal. We will not provide any migration for those profiles. People can either re-create those profiles in Ptyxis or install gnome-terminal from universe and continue to use gnome-terminal.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2108942 Title: [MIR] ptyxis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptyxis/+bug/2108942/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
