[FFe] evince 42
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evince (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Why Needed
----------
The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4).
The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze.
The Ubuntu Desktop Team commits to packaging the final evince 42 stable release and working to fix any regressions introduced in the update. We do have the ability to use a "really" version number in case we decide we need to go back to the 41 version.
What Changed
------------
https:/
https:/
For this release I have reverted 2 commits that required a new version of libarchive since that wasn't included in 22.04 LTS yet.
Build Test
----------
Builds successfully
Install Test
------------
$ sudo apt install ./../build-
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'evince' instead of './../build-
Note, selecting 'evince-common' instead of './../build-
Note, selecting 'gir1.2-evince-3.0' instead of './../build-
Note, selecting 'libevdocument3-4' instead of './../build-
Note, selecting 'libevview3-3' instead of './../build-
The following packages were automatically installed and are no longer required:
libabsl20200923 libicu67 libpoppler115
Use 'sudo apt autoremove' to remove them.
Suggested packages:
unrar
The following packages will be upgraded:
evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3
5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B/821 kB of archives.
After this operation, 803 kB disk space will be freed.
Get:1 /home/jeremy/
Get:2 /home/jeremy/
Get:3 /home/jeremy/
Get:4 /home/jeremy/
Get:5 /home/jeremy/
(Reading database ... 207369 files and directories currently installed.)
Preparing to unpack .../evince-
Unpacking evince-common (42~beta-1) over (41.3-3) ...
Preparing to unpack .../evince_
Unpacking evince (42~beta-1) over (41.3-3) ...
Preparing to unpack .../libevdocume
Unpacking libevdocument3-
Preparing to unpack .../libevview3-
Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ...
Preparing to unpack .../gir1.
Unpacking gir1.2-
Setting up evince-common (42~beta-1) ...
Setting up libevdocument3-
Setting up libevview3-3:amd64 (42~beta-1) ...
Setting up evince (42~beta-1) ...
Setting up gir1.2-
Processing triggers for desktop-file-utils (0.26-1ubuntu2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu2) ...
Processing triggers for libglib2.0-0:amd64 (2.71.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu1) ...
Processing triggers for man-db (2.10.1-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
N: Download is performed unsandboxed as root as file '/home/
$ evince
(runs ok)
Hey Jeremy! Thanks for filling in this FFe. Did you do a test build of the new evince for non-amd64 architectures as well (like in some PPA, for instance)? Also, I assume that the two reverted commits for the new libarchive support have been rather non-invasive, right? If the answer is 'yes' for both, I think we can go ahead with this FFe.
Seeing that the NEWS file advertises the libarchive >= 3.6.0 dependency, I was wondering: do you want/need to have this in jammy? Are we missing out (or risking regressing) some features by sticking with the old version? I don't think Foundations had plans on pulling in the new upstream version past FF, but we could discuss that if there is *actual* need for it (since it's out since last month). Though Debian's still on 3.5.2, and so far this was a merge/sync.