Package Details: mautrix-discord-bin 0.7.1-1

Git Clone URL: https://aur.archlinux.org/mautrix-discord-bin.git (read-only, click to copy)
Package Base: mautrix-discord-bin
Description: A Matrix-Discord puppeting bridge
Upstream URL: https://github.com/mautrix/discord
Licenses: AGPL-3.0-or-later
Provides: mautrix-discord
Submitter: marcool04
Maintainer: marcool04
Last Packager: marcool04
Votes: 3
Popularity: 0.000123
First Submitted: 2023-04-23 15:25 (UTC)
Last Updated: 2024-11-16 19:12 (UTC)

Latest Comments

marcool04 commented on 2023-05-28 14:29 (UTC) (edited on 2023-11-17 09:20 (UTC) by marcool04)

You're welcome. Actually, thinking about it a bit more, this PKGBUILD did need some adjustment to follow best practices: the files downloaded should be pinned to the version, which would have avoided this problem. Pkgrel 5 does that.

Best,

Mark

shtrophic commented on 2023-05-28 12:21 (UTC) (edited on 2023-05-28 12:22 (UTC) by shtrophic)

Ah yes, cleaning my cache with paru -Sccdd was it. Thanks for your prompt help!

marcool04 commented on 2023-05-28 11:37 (UTC) (edited on 2023-05-28 11:41 (UTC) by marcool04)

@Sir-Photch are you using an AUR helper by any chance? Architecture dependent files are NOT cleaned up automatically by makepkg before attempting to perform an update of a package, so if they are already present (from a previous version), a failure occurs at the verify stage, when the old file is checked against the new checksums. The solution is to always build packages in a clean clone of the AUR git repository, which not all AUR helpers do.

This is quite probably what is happening here, because you have 0.3.0-1 installed, and we have this in your output: 

> Found mautrix-discord-amd64

So the correct, new binary for 0.4.0 is not being downloaded, and verify is comparing the binary from 0.3.0 against the checksum for 0.4.0.

Delete the AUR helper's cache and try again (at least the cache for mautrix-discord-bin). Or if you are building manually with makepkg, do so from a clean clone of https://aur.archlinux.org/mautrix-discord-bin.git like I indicated in my previous comment, not one where there is already a mautrix-discord-amd64 file.

If all of those attempts still fail, I would be grateful if you could do a bit more debugging and give me the sha256 sums for the files that are being downloaded.

shtrophic commented on 2023-05-28 11:31 (UTC) 

Aur (1)                  Old Version  New Version  Make Only
aur/mautrix-discord-bin  0.3.0-1      0.4.0-4      No

:: Proceed to review? [Y/n]:

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
:: Proceed with installation? [Y/n]:
fetching devel info...
==> Making package: mautrix-discord-bin 0.4.0-4 (Sun 28 May 2023 11:30:59 AM UTC)
==> Retrieving sources...
  -> Found v0.4.0.zip
  -> Found sysusers-mautrix-discord.conf
  -> Found mautrix-discord.tmpfiles
  -> Found mautrix-discord.service
  -> Found log-path.diff
  -> Found mautrix-discord-amd64
==> Validating source files with sha256sums...
    v0.4.0.zip ... Passed
    sysusers-mautrix-discord.conf ... Passed
    mautrix-discord.tmpfiles ... Passed
    mautrix-discord.service ... Passed
    log-path.diff ... Passed
==> Validating source_x86_64 files with sha256sums...
    mautrix-discord-amd64 ... FAILED
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'mautrix-discord-bin-0.4.0-4':
error: packages failed to build: mautrix-discord-bin-0.4.0-4

marcool04 commented on 2023-05-24 15:11 (UTC)

@Sir-Phtoch could you specify? I have:

$ git clone "https://aur.archlinux.org/mautrix-discord-bin.git"
Cloning into 'mautrix-discord-bin'...
remote: Enumerating objects: 25, done.
remote: Counting objects: 100% (25/25), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 25 (delta 7), reused 25 (delta 7), pack-reused 0
Receiving objects: 100% (25/25), 6.60 KiB | 6.60 MiB/s, done.
Resolving deltas: 100% (7/7), done.
[mark@t480 Downloads]$ cd mautrix-discord-bin/
[mark@t480 mautrix-discord-bin]$ makepkg -s
==> Making package: mautrix-discord-bin 0.4.0-4 (Wed 24 May 2023 05:09:19 PM CEST)
[snip]
==> Retrieving sources...
  -> Downloading v0.4.0.zip...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  140k    0  140k    0     0   231k      0 --:--:-- --:--:-- --:--:--  231k
  -> Found sysusers-mautrix-discord.conf
  -> Found mautrix-discord.tmpfiles
  -> Found mautrix-discord.service
  -> Found log-path.diff
  -> Downloading mautrix-discord-amd64...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 17.6M  100 17.6M    0     0  19.0M      0 --:--:-- --:--:-- --:--:-- 19.0M
==> Validating source files with sha256sums...
    v0.4.0.zip ... Passed
    sysusers-mautrix-discord.conf ... Passed
    mautrix-discord.tmpfiles ... Passed
    mautrix-discord.service ... Passed
    log-path.diff ... Passed
==> Validating source_x86_64 files with sha256sums...
    mautrix-discord-amd64 ... Passed
[snip]
==> Finished making: mautrix-discord-bin 0.4.0-4 (Wed 24 May 2023 05:09:28 PM CEST)

which checksum is failing?

shtrophic commented on 2023-05-24 11:28 (UTC)

checksums fail for the latest update

marcool04 commented on 2023-05-07 07:03 (UTC)

Thanks @Sir-Photch for your careful testing. These errors happen because I didn't test in a "clean" environment and as I redirect all logging to systemd-journald I didn't catch any error there. There was also the same problem here that you noticed in the mautrix-whatsapp-bin package concerning unsafe path transitions. The problem there is that mautrix-discord needs write permission to its config folder in /etc/ to modify the config file on startup, so I made that 770 and root:mautrix-discord owned. Let me know if you can see any problem with that. Best, Mark.

shtrophic commented on 2023-05-07 02:05 (UTC)

I believe that the logpath in mautrix-discord.yaml has to be changed to /var/log/mautrix-discord/mautrix-discord.yaml, since /var/log is not writable for the service.