| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This reverts commit e280a467702b94bee0d3a6f6af9f60d057a6cb97.
|
|
|
|
|
|
|
|
This reverts commit 911e6b152c808b9a9bbffad7bea4fbe3542d0a28.
|
|
|
|
update pot file
remove transifex configuration
remove es_ES files/folder/config as es exists
|
|
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
|
|
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] <[email protected]>
|
|
ci: add missing release.yml
ci: remove redundant GH CLI installation step
ci: add set -eo pipefail to workflow scripts
|
|
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.
|
|
This makes the code a tad clearer.
|
|
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.
|
|
|
|
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 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.
|
|
Fixes #527.
|
|
Fix crash if filename retrieval fails, which currently happens with
RAR 7.00 directories.
An upcoming fix with properly parse those, but it's better not to crash
on malformed/unexpected input nonetheless.
Part of #527.
|
|
Based off https://github.com/mate-desktop/mate-panel/pull/1415
|
|
|
|
|
|
|
|
‘strcasecmp’ [-Werror=implicit-function-declaration]".
|
|
Fix https://github.com/mate-desktop/engrampa/issues/510
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix https://github.com/mate-desktop/engrampa/issues/501
|
|
I had been relying on `unrar-free` being available as `unrar`, but that
seems to be a Debian thing, so accept the `unrar-free` itself as an
alternative.
The code has been refactored a little to avoid some duplication, but it
basically just adds `unrar-free` as a lower precedence alternative.
|
|
Tested with unrar-free 0.1.3.
|
|
Check the fields count before retrieving it not to go out of bounds.
This also slightly revise the logic to require the proper number of
fields in the RAR5 `attribute_field_with_space()` case.
|
|
Merge version matching for rar and unrar. This is ever so slightly
slower in theory for unrar 5.x because there's an additional
unnecessary `sscanf()` call, but it's not actually gonna matter, and
saves quite a bit of duplicated logic.
This also makes the matching a bit more safe by verifying `sscanf()`
actually worked, and avoids using a uninitialized `version` value due
to an unexpected input.
Finally, this makes the parsing a bit more strict by requiring a
version number after the `RAR` and `UNRAR` line prefixes -- leading not
to using the uninitialized version variable.
This will be required by the upcoming unrar-free support as it reports
a `RAR archive ...` line that would have matched the `RAR` version
check.
|
|
Fix crash if the `zip` command emits a line starting with one of 'd?-'
yet having less than 8 fields in it, or if the date field is malformed.
|
|
Offset was not properly updated when adding support for EPUB+ZIP in
84fb5cfe96263f79e50b68a5a6996e40c514cf74, leading to disabling both ZIP
and RAR when the option unar-open-zip was enabled.
|
|
|
|
Signed-off-by: raveit65 <[email protected]>
|
|
- reported by translators
https://app.transifex.com/mate/MATE/translate/#id/master--engrampa/470908044
|
|
Fix https://github.com/mate-desktop/engrampa/issues/496
|
|
|
|
|
|
|
|
|
|
|
|
MAGIC returned incorrect mime type while processing tar compression type
Fix https://github.com/mate-desktop/engrampa/issues/492
|