engrampa, branch 1.28

release 1.28.3

2026-05-04T17:53:42+00:00

fixed wrong drag&drop activation when in single click mode

2026-05-04T13:44:19+00:00

when calling the parent button_press_event function a
button released event could be emitted, in that case
stop the drag&drop action.

Backported from https://gitlab.gnome.org/GNOME/file-roller/-/commit/279b76d6

Fixes #547

build(deps): bump actions/checkout from 5 to 6

2026-03-17T16:09:20+00:00

Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v5...v6)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot]

ci: restructure github actions to use the same structure for all repos

2026-03-17T15:56:38+00:00

ci: add missing release.yml

ci: remove redundant GH CLI installation step

ci: add set -eo pipefail to workflow scripts

lha: Fix support for file names with spaces

2026-03-13T23:01:59+00:00

See e.g. lha_os2_208/lfn.lzh or lha_os2_208/h3_lfn.lzh from
https://github.com/fragglet/lhasa/tree/master/test/archives.

lha: Use named fields instead of magic numbers

2026-03-13T23:01:59+00:00

This makes the code a tad clearer.

lha: Fix crash, parse lha list output correctly

2026-03-13T23:01:59+00:00

The output from the `lha` list archive command is eclectic and
inconsistent, and engrampa was actually crashing when opening certain
archives (eg. lha_os2_208/h3_subdir.lzh in the Lhasa test suite). But this
also fixes the list parsing more generally. With this change, engrampa
now appears to successfully open all of the .lzh files in the Lhasa test
suite correctly without crashing.

The first field in lha's list output either contains Unix permissions or
an OS name in [brackets]. There was already hard-coded support for
[MS-DOS], [generic], [unknown] and [Amiga], but other OS names were not
handled properly. This is now fixed, with an approach that is mindful of
the fact that the OS name can contain spaces.

Empty value (whitespace) in the UID/GID column is also handled
correctly.  This was partially working because of the aforementioned
special-casing, but now is fixed more generally.

fix memleaks

2026-03-12T16:25:03+00:00

Avoid critical errors with invalid dates

2025-07-02T20:12:54+00:00

This likely should not happen with valid dates, but can if a archiver
reports invalid ones for whatever reason (legitimate weird dates, or
parser failures for example).

rar: Fix asking password for encrypted archives with RAR7

2025-06-25T08:12:38+00:00

RAR 7.0 outputs a different error when password is missing:

>
> Incorrect password for foo.rar
> Incorrect password for foo.rar
> Cannot find volume foo.r00

Whereas RAR 6.21 doesn't output the last 2 lines.

The error about volumes confuses the parser thinking there's a volume
issue, which hides the incorrect password one.

Note that RAR 7.0 outputs this *most of the time*, but once in a while
it'll also skip the last 2 lines.  Whether it is a race condition or
not, it at least happens often enough with RAR 7.0 to consider this its
normal behavior and handle it.

Fixes #526.