Search Criteria
Package Details: morgen-bin 3.5.13-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/morgen-bin.git (read-only, click to copy) |
---|---|
Package Base: | morgen-bin |
Description: | Morgen is a modern, intuitive and smart calendar application and successor to MineTime |
Upstream URL: | https://morgen.so |
Keywords: | calendar |
Licenses: | custom |
Provides: | morgen |
Submitter: | eso |
Maintainer: | eso |
Last Packager: | eso |
Votes: | 6 |
Popularity: | 0.000107 |
First Submitted: | 2021-06-23 09:38 (UTC) |
Last Updated: | 2024-11-06 13:01 (UTC) |
Latest Comments
1 2 3 Next › Last »
eso commented on 2024-07-12 09:15 (UTC)
@mborko There is a general problem: When a new version of Morgen is released, the company's CD pipeline simply overwrites the previous package file (which is only called "x64"), so the downloaded package is not distinguishable by filename regarding the version being packaged. If that happens, and I fail to immediately be notified a new version exists, the PKGBUILD will fail due to checksum mismatch. To my knowledge, Morgen does not provide a way to persistently download any particular version (or any non-current version at all, for that matter).
In short: the morgen-bin_3.5.2-1 AUR package doesn't actually include the link to that particular version, but simply the most recent one as nothing else is provided by Morgen afaik.
mborko commented on 2024-07-11 13:18 (UTC)
I see, that this is not the first time ...
Is it possible to update the checksums?
eso commented on 2024-02-12 12:14 (UTC)
@rabi: Morgen released a new version again, please try again.
rabu commented on 2024-02-10 10:49 (UTC)
@eso My process to get the pacakage running after the certificate was invalid again was normally. 1. yay -R morgen-bin 2. yay -Scc 3. yay -S morgen-bin
But I'm not able to install it this way anymore.
Getting this error:
Ezio652 commented on 2024-02-09 22:37 (UTC)
@eso: Thank you as well, fixed the issue with the debug build (to clarify, it was the
debug
option). Must have made a sometime ago.Y2K350 commented on 2024-02-08 23:47 (UTC)
@eso Thank you so much for the reply, I am still kind of a noob to Arch on some level, but figured I should let you know of the error. I appreciate your reply and update.
eso commented on 2024-02-08 12:48 (UTC)
@Ezio652 Does the
OPTIONS
setting in your/etc/makepkg.conf
by any chance containdebug
?Ezio652 commented on 2024-02-08 12:29 (UTC)
@eso:
My log from a "clean" install aka with the cache deleted. So no existing build-files. It seems the build then creates a
morgen-bin-debug
somehow. I don't understand PKGBUILDs enough see a reason for this.eso commented on 2024-02-08 11:58 (UTC)
@Ezio652 Can't reproduce, I'm not aware of any debug symbols - can you elaborate? I've only updated the PKGBUILD to reflect the correct file naming of the binary, which now properly includes name, version and release. The morgen binary available for download is only called "x64", which seems to confuse some AUR clients when comparing versions and hence raising b2sum errors if that file already exists in cache from a previously installed version.
Ezio652 commented on 2024-02-08 11:39 (UTC)
@eso To me it looks like the normal install process now also installs the debug-symbols-variant with it.
To me this seems unnecessary. Can we maybe remove that one?
1 2 3 Next › Last »