Re: Atkinson Hyperlegible font [was: Idea: Let selection of default fonts be based on Noto]
On 2023-08-31 11:22, TJ wrote: On 30/08/2023 10:32, Gunnar Hjalmarsson wrote: On 2023-07-14 17:13, Gunnar Hjalmarsson wrote: On 2023-07-13 09:37, TJ wrote: Could you consider including the visually-impaired friendly Atkinson Hyperlegible Font? https://brailleinstitute.org/freefont To me it looks like a reasonable font to make selectable in Ubuntu. But before that can be really considered, it would need to be packaged in a sensible way for Debian. Even if the Atkinson Hyperlegible font files are actually included in the texlive-fonts-extra package, they would need to be broken out into a separate package. Package created: https://packages.ubuntu.com/mantic/fonts-atkinson-hyperlegible Maybe that is sufficient. A user can do: sudo apt install fonts-atkinson-hyperlegible and pick Atkinson Hyperlegible in the web browser and/or Tweaks. Otherwise, if we want to include it on the ISO, I'm assuming that we should have a blessing from the desktop team before submitting a MIR. Thank-you - that is really useful for visually impaired operators (and that includes those with reasonably good vision that is starting to go fuzzy at close range!). Being used in the installers (or an easily found Accessibility option) would be icing on the cake. Hmm.. The installer is beyond the scope of my fonts overhaul project. :/ Without knowing, I would guess that the fonts used in the desktop installer are determined by the flavor it installs. So in case of standard Ubuntu it's probably the Ubuntu font for latin scripts, while it may be Noto Sans for some of the flavors. But I may be wrong. And in any case it may be possible to set the installer font specifically. If you want to make such a request, one way is an issue here: https://github.com/canonical/ubuntu-desktop-installer/issues Having to hunt for such support often makes those needing it feel like second-class citizens yet for something like this there is very little, if any, down-side to everyone using this by default (especially in an installer where the defaults should cater for all use-cases where there is no opportunity to customise the early experience - particularly for newcomers and novices). -- Rgds, Gunnar Hjalmarsson https://launchpad.net/~gunnarhj -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
git-ubuntu 1.1 released
I have released git-ubuntu 1.1. The major addition is the rich history adoption via changes files and the corresponding `git ubuntu prepare-upload` command, which many of you have been using already via the edge channel. This feature is now available in the stable channel. Install with: sudo snap install --classic git-ubuntu or, to switch the already-installed snap back to the stable channel from the edge channel: sudo snap refresh --stable git-ubuntu Preliminary documentation is now available: https://canonical-git-ubuntu.readthedocs-hosted.com/en/latest/ In between 1.0 and 1.1 were changes to the importer service itself to import all packages into Launchpad, for which there was no release of the tooling; hence the apparent delay between releases this time. Notable changes from 1.0 to 1.1 --- Rich history is adopted if a reference exists to it in the changes file associated with an upload, provided that it can be retrieved and matches the upload itself. A new `prepare-upload` subcommand provides a low level CLI interface that developers can script against to integrate into their workflows. See the howto documentation[1] for details. Steve Langasek has written an experimental higher level wrapper that currently lives in the git-ubuntu source tree as `sandbox/gu-build` to support some common workflows, such as to automatically include the correct `dpkg-genchanges -v` option automatically for the upload of package merges. See his mailing list post[2] for details. The snap is now based on core20. All packages are imported by default and the manual allowlist functionality is removed. The denylist exists to stop futile retries for edge case packages that fail to import; my goal is to whittle this down to zero. The importer now automatically sets a repository as default for its target after it is imported. This means that manual intervention for new source packages is no longer required before `git ubuntu clone` will work. Thanks to the Launchpad team for implementing the access control needed for the importer to do this safely. Commits included in this release Andreas Hasenack (2): Import redis, requested by sergiodj Add libtpms to import list Athos Ribeiro (3): Do not rely on host perl stack Test dpkg tooling confinement Check if perl dependent commands are runnable Brian Murray (2): import packages for the SRU team add in virtualbox packages Bryce Harrington (14): whitelist: Drop php-horde-* whitelist: Add php7.4 and recently touched php-* packages Add fish to import whitelist Add php-league-commonmark to whitelist Add phpunit to whitelist Whitelist *php* packages from main and universe Whitelist *ruby* packages from main and universe build: Ensure fetch_orig() always returns a list Add composer to the whitelist. Add python-sqlalchemy-utils to the whitelist. Add python-django-formtools to the whitelist. Add several packages to the whitelist. Add three packages for +1 maintenance to the whitelist. Add thin to the whitelist. Christian Ehrhardt (3): whitelist: add openmpi whitelist: add packages related to mdevctl MIR (LP: #1889248) add libfabric to whitelist Lena Voytek (1): Updates for inclusive naming Paride Legovini (1): snapcraft: drop --enable-experimental-package-repositories Robie Basak (135): Update release process to also close fixed bugs prometheus-alertmanager changelog date override Add west-chamber to whitelist Add xtables-addons to whitelist Remove import exception catching Handle pygit2 type attribute API change Fix Python string escaping Handle git email address configuration fixture Do not raise StopIteration() directly logging.warn() -> logging.warning() Add missing dependency on ubuntutools Update packaging to be based on 20.04 Add recent whitelist requests Fix tests when run in non-UTC timezones Also add ansible-base to whitelist Merge branch 'core20' Add ubuntu-dev-tools for update-maintainer Drop GPG key ID workaround Drop pinning Drop pygit2_signature_tuple Drop GitUbuntuRepository.descendant_of() Correctly compare package version strings Instantiate HTTPError better in tests Add smart whitelist support Merge branch 'smart-whitelisting' Merge branch 'lp1924983' snap: add python3-secretstorage for GNOME keyring Merge branch 'keyring-secretstorage' Refactor validate_upload_tag() Rename validate_upload_tag() Pass through spi Add get_changes_file_url() method Add rich history import from changes files Merge branch 'rich-history-from-changes-file' source_builder: fix test changelog sign-off line Add integration test for sed Fix
git-ubuntu 1.1 released
I have released git-ubuntu 1.1. The major addition is the rich history adoption via changes files and the corresponding `git ubuntu prepare-upload` command, which many of you have been using already via the edge channel. This feature is now available in the stable channel. Install with: sudo snap install --classic git-ubuntu or, to switch the already-installed snap back to the stable channel from the edge channel: sudo snap refresh --stable git-ubuntu Preliminary documentation is now available: https://canonical-git-ubuntu.readthedocs-hosted.com/en/latest/ In between 1.0 and 1.1 were changes to the importer service itself to import all packages into Launchpad, for which there was no release of the tooling; hence the apparent delay between releases this time. Notable changes from 1.0 to 1.1 --- Rich history is adopted if a reference exists to it in the changes file associated with an upload, provided that it can be retrieved and matches the upload itself. A new `prepare-upload` subcommand provides a low level CLI interface that developers can script against to integrate into their workflows. See the howto documentation[1] for details. Steve Langasek has written an experimental higher level wrapper that currently lives in the git-ubuntu source tree as `sandbox/gu-build` to support some common workflows, such as to automatically include the correct `dpkg-genchanges -v` option automatically for the upload of package merges. See his mailing list post[2] for details. The snap is now based on core20. All packages are imported by default and the manual allowlist functionality is removed. The denylist exists to stop futile retries for edge case packages that fail to import; my goal is to whittle this down to zero. The importer now automatically sets a repository as default for its target after it is imported. This means that manual intervention for new source packages is no longer required before `git ubuntu clone` will work. Thanks to the Launchpad team for implementing the access control needed for the importer to do this safely. Commits included in this release Andreas Hasenack (2): Import redis, requested by sergiodj Add libtpms to import list Athos Ribeiro (3): Do not rely on host perl stack Test dpkg tooling confinement Check if perl dependent commands are runnable Brian Murray (2): import packages for the SRU team add in virtualbox packages Bryce Harrington (14): whitelist: Drop php-horde-* whitelist: Add php7.4 and recently touched php-* packages Add fish to import whitelist Add php-league-commonmark to whitelist Add phpunit to whitelist Whitelist *php* packages from main and universe Whitelist *ruby* packages from main and universe build: Ensure fetch_orig() always returns a list Add composer to the whitelist. Add python-sqlalchemy-utils to the whitelist. Add python-django-formtools to the whitelist. Add several packages to the whitelist. Add three packages for +1 maintenance to the whitelist. Add thin to the whitelist. Christian Ehrhardt (3): whitelist: add openmpi whitelist: add packages related to mdevctl MIR (LP: #1889248) add libfabric to whitelist Lena Voytek (1): Updates for inclusive naming Paride Legovini (1): snapcraft: drop --enable-experimental-package-repositories Robie Basak (135): Update release process to also close fixed bugs prometheus-alertmanager changelog date override Add west-chamber to whitelist Add xtables-addons to whitelist Remove import exception catching Handle pygit2 type attribute API change Fix Python string escaping Handle git email address configuration fixture Do not raise StopIteration() directly logging.warn() -> logging.warning() Add missing dependency on ubuntutools Update packaging to be based on 20.04 Add recent whitelist requests Fix tests when run in non-UTC timezones Also add ansible-base to whitelist Merge branch 'core20' Add ubuntu-dev-tools for update-maintainer Drop GPG key ID workaround Drop pinning Drop pygit2_signature_tuple Drop GitUbuntuRepository.descendant_of() Correctly compare package version strings Instantiate HTTPError better in tests Add smart whitelist support Merge branch 'smart-whitelisting' Merge branch 'lp1924983' snap: add python3-secretstorage for GNOME keyring Merge branch 'keyring-secretstorage' Refactor validate_upload_tag() Rename validate_upload_tag() Pass through spi Add get_changes_file_url() method Add rich history import from changes files Merge branch 'rich-history-from-changes-file' source_builder: fix test changelog sign-off line Add integration test for sed Fix
Re: Idea: Let selection of default fonts be based on Noto
On 30/08/2023 10:32, Gunnar Hjalmarsson wrote: On 2023-07-14 17:13, Gunnar Hjalmarsson wrote: On 2023-07-13 09:37, TJ wrote: Could you consider including the visually-impaired friendly Atkinson Hyperlegible Font? https://brailleinstitute.org/freefont To me it looks like a reasonable font to make selectable in Ubuntu. But before that can be really considered, it would need to be packaged in a sensible way for Debian. Even if the Atkinson Hyperlegible font files are actually included in the texlive-fonts-extra package, they would need to be broken out into a separate package. Package created: https://packages.ubuntu.com/mantic/fonts-atkinson-hyperlegible Maybe that is sufficient. A user can do: sudo apt install fonts-atkinson-hyperlegible and pick Atkinson Hyperlegible in the web browser and/or Tweaks. Otherwise, if we want to include it on the ISO, I'm assuming that we should have a blessing from the desktop team before submitting a MIR. Thank-you - that is really useful for visually impaired operators (and that includes those with reasonably good vision that is starting to go fuzzy at close range!). Being used in the installers (or an easily found Accessibility option) would be icing on the cake. Having to hunt for such support often makes those needing it feel like second-class citizens yet for something like this there is very little, if any, down-side to everyone using this by default (especially in an installer where the defaults should cater for all use-cases where there is no opportunity to customise the early experience - particularly for newcomers and novices). -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: new seeds feature: alternatives in germinate 2.4.2
On Fri, 1 Sept 2023 at 04:23, Julian Andres Klode < julian.kl...@canonical.com> wrote: > This means that only the first package ends up getting a Task > field, and hence installation during image build - which uses > the task feature of apt (apt install task-name^) This isn't how image builds install tasks, for better or worse. In lucid and earlier, the Task header is used but it's matched by hand rather than using the ^ syntax -- I'm not sure why though, it may be something to do with not wanting to install the packages that have the task header but are from a foreign architecture. In mantic though, livecd-rootfs uses the package lists produced by germinate directly. Given these package lists are what drive the Task header in the archive, I expect it doesn't make any difference though. Cheers, mwh is still as > predictable as before - the resolving there doesn't change > (task-name^ expands to all packages with Task: task-name). > > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance, please look at NBS [Was: +1 maintenance report (Week of 2023-08-21)]
On Thu, Aug 31, 2023 at 02:40:55PM -0300, Athos Ribeiro wrote: > I was on +1 maintenance on the week of 2023-08-21. > I started the week using the Ubuntu archive tooling to re-triggering a few > tests and running the find-proposed-cluster script to find good candidates > to work on. Please keep the NBS report in mind as well: https://ubuntu-archive-team.ubuntu.com/nbs.html There has not been much progress on this list for roughly a month, and there are lots of packages here needing active attention of the kind that would not be blocked by a glibc migration :) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report (Week of 2023-08-21)
I was on +1 maintenance on the week of 2023-08-21. I started the week using the Ubuntu archive tooling to re-triggering a few tests and running the find-proposed-cluster script to find good candidates to work on. The majority of the reported clusters were blocked on the glibc transition then. Therefore, I decided to focus some effort on helping unblocking those. In special, I worked on debugging and trying to advance LP: #2031912 along with other folks (thanks to everyone involved in fixing this one, in special, sergiodj for all the debugging and patches). Other than glibc, there weren't many large clusters to work on. I the focused on retriggering some tests. rust-trust-dns-proto: This was blocking a few rust packages due to a DEP8 failure. Some of the tests perform DNS queries which are not allowed in the autopkgtest infra. I added a delta to the package to mark those tests as flaky (they pass in Debian) and unblock those rust packages. -- Athos Ribeiro -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
new seeds feature: alternatives in germinate 2.4.2
o/ This week I worked on a new feature in germinate that very much improves our ability to express dependencies in the meta packages: You can now list alternatives for seed entries. For example, and this is the reason that triggered this feature: * systemd-timesyncd | time-daemon How does this work? Germinate will continue to seed the first package as before, it generally ignores any alternatives present, but will add them back when generating meta package dependencies. This means that only the first package ends up getting a Task field, and hence installation during image build - which uses the task feature of apt (apt install task-name^) is still as predictable as before - the resolving there doesn't change (task-name^ expands to all packages with Task: task-name). However, you can then later replace the first package with an alternative. For example, after installing the cloud-minimal task, you can then install chrony and it will replace systemd-timesyncd and satisfy the | time-daemon part of ubuntu-cloud-minimal's dependency. You can also install the meta package and an alternative together, but do note that apt may also pick alternatives for other stuff you did not intend (e.g. if a package was seeded that depends on firefox | www-browser and you install the metapackage and have another www-browser installed, it would not install firefox whereas apt install seed^ would still install firefox despite you having another www-browser), so generally you want to rely on the task field to install and then install anything conflicting with that later. I expect this is mostly useful for virtual packages with a default provider like time-daemon above. It is standard practice for debs to always have `default | virtual-package` as the dependency, and now we can express that in the metapackages as well. Please make sure to use germinate 2.4.2 which will land in mantic probably tomorrow (it needs to be synced from Debian) to update ubuntu-meta to ensure that the alternatives are present. Thank you! -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
