| Git Clone URL: | https://aur.archlinux.org/masterpdfeditor.git (read-only, click to copy) |
|---|---|
| Package Base: | masterpdfeditor |
| Description: | A complete solution for viewing, creating and editing PDF files |
| Upstream URL: | https://code-industry.net/free-pdf-editor/ |
| Keywords: | master-pdf-editor |
| Licenses: | custom |
| Submitter: | farseerfc |
| Maintainer: | pgoetz |
| Last Packager: | pgoetz |
| Votes: | 191 |
| Popularity: | 1.00 |
| First Submitted: | 2016-12-05 01:50 (UTC) |
| Last Updated: | 2024-11-04 16:49 (UTC) |
OK, should be fixed now. I use pacaur to install AUR packages and noticed it seems to keep the source tar.gz for every version ever installed. I install masterpdfeditor a lot, so must have hit some kind of file limit, so the old incorrect checksum worked, but the correct one didn't, which is why I didn't catch this immediately. Deleting all the old copies resolved the issue.
Also, thanks for the heads up.
@nTia89 @Icecube63 @thibaultmol Not sure what is going on, at the moment. I thought I had the correct sha1sum, updated it with what is on Code Industry page, and downloaded the .tar.gz file to compute the sha1sum myself (they were the same). It all checks out but now when I try to install the package on my workstation, I get a failed validity check as well. When I test installed the package yesterday, I didn't.
You have to change the first sha1sums to '9055c1edfd28442acd97b3228ee753335d381a09'
==> Validating source_x86_64 files with sha1sums... master-pdf-editor-5.7.40-qt5.x86_64.tar.gz ... FAILED net.code-industry.masterpdfeditor5.desktop ... Passed ==> ERROR: One or more files did not pass the validity check!
There's a bug in the net.code-industry.masterpdfeditor5.desktop file for version 5.7.40 which prevents the application from appearing in the menu:
Exec=/opt/master-pdf-editor-5/masterpdfeditor5.sh %f
There is no such shell script in /opt/master-pdf-editor-5
For the time being I'll have to build a new version of the package which includes an edited version of this file.
I already removed the offending comments.
@Alad Not at all following what this is in reference to or what "discussing keygens" even means. Is this some comment pinned to every AUR comment section, or in reference to some specific transgression?
The next person who discusses keygens will have their account suspended indefinitely.
Pinned Comments
Alad commented on 2021-03-03 16:25 (UTC)
The next person who discusses keygens will have their account suspended indefinitely.