Package Details: morgen-bin 4.0.1-1

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.
Upstream URL: https://morgen.so
Keywords: calendar
Licenses: custom
Conflicts: morgen3-bin
Provides: morgen
Submitter: eso
Maintainer: eso
Last Packager: eso
Votes: 7
Popularity: 0.000284
First Submitted: 2021-06-23 09:38 (UTC)
Last Updated: 2026-01-27 10:34 (UTC)

Latest Comments

1 2 3 Next › Last »

eso commented on 2026-01-22 15:11 (UTC)

@materemias That's exactly the plan. There is already a morgen3-bin package with the latest state of version 3. I'm having a look at packaging morgen 4 soonish. Unfortunately the v4 feature removal entirely eliminates my use cases for using morgen in the first place, I'm not yet sure about the continuation of this package.

materemias commented on 2026-01-21 09:31 (UTC)

Morgen 4 is out. since it has dropped Exchange on-prem and some CalDAV services maybe it is worth to fork this into a legacy morgen3-bin and update this to v4

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 ...

==> Making package: morgen-bin 3.5.1-1 (Thu 11 Jul 2024 15:15:18)
==> Retrieving sources...
  -> Downloading morgen-bin_3.5.1-1.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 81.0M  100 81.0M    0     0  32.1M      0  0:00:02  0:00:02 --:--:-- 32.1M
  -> Found morgen
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    morgen-bin_3.5.1-1.xz ... FAILED
    morgen ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/mike/.cache/yay/morgen-bin 
     context: exit status 1 


:: (1/1) Parsing SRCINFO: morgen-bin
==> Making package: morgen-bin 3.5.1-1 (Thu 11 Jul 2024 15:15:21)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found morgen-bin_3.5.1-1.xz
  -> Found morgen
==> Validating source files with b2sums...
    morgen-bin_3.5.1-1.xz ... FAILED
    morgen ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: morgen-bin-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
morgen-bin - exit status 1

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:

==> Making package: morgen-bin 3.2.2-2 (Sat 10 Feb 2024 11:48:11 AM CET)
==> Retrieving sources...
  -> Found morgen-bin_3.2.2-2.xz
  -> Found morgen
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    morgen-bin_3.2.2-2.xz ... FAILED
    morgen ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/rafael/.cache/yay/morgen-bin
     context: exit status 1


:: (1/1) Parsing SRCINFO: morgen-bin
==> Making package: morgen-bin 3.2.2-2 (Sat 10 Feb 2024 11:48:12 AM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found morgen-bin_3.2.2-2.xz
  -> Found morgen
==> Validating source files with b2sums...
    morgen-bin_3.2.2-2.xz ... FAILED
    morgen ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: morgen-bin-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
morgen-bin - exit status 1

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 contain debug?

Ezio652 commented on 2024-02-08 12:29 (UTC)

@eso:

$ yay -S morgen-bin
AUR Explicit (1): morgen-bin-3.2.2-2
:: (1/1) Downloaded PKGBUILD: morgen-bin
  1 morgen-bin                       (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 morgen-bin                       (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: morgen-bin 3.2.2-2 (Thu 08 Feb 2024 01:22:34 PM CET)
==> Retrieving sources...
  -> Downloading morgen-bin_3.2.2-2.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 73.6M  100 73.6M    0     0  13.5M      0  0:00:05  0:00:05 --:--:-- 17.6M
  -> Found morgen
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    morgen-bin_3.2.2-2.xz ... Passed
    morgen ... Passed
:: (1/1) Parsing SRCINFO: morgen-bin
==> Making package: morgen-bin 3.2.2-2 (Thu 08 Feb 2024 01:22:41 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found morgen-bin_3.2.2-2.xz
  -> Found morgen
==> Validating source files with b2sums...
    morgen-bin_3.2.2-2.xz ... Passed
    morgen ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting morgen-bin_3.2.2-2.xz with bsdtar
==> Sources are ready.
==> Making package: morgen-bin 3.2.2-2 (Thu 08 Feb 2024 01:22:44 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
objcopy: ./opt/Morgen/chrome_crashpad_handler: debuglink section already exists
objcopy: ./opt/Morgen/libEGL.so: debuglink section already exists
objcopy: ./opt/Morgen/libGLESv2.so: debuglink section already exists
objcopy: ./opt/Morgen/libffmpeg.so: debuglink section already exists
objcopy: ./opt/Morgen/libvk_swiftshader.so: debuglink section already exists
objcopy: ./opt/Morgen/morgen: debuglink section already exists
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "morgen-bin"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding changelog file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Creating package "morgen-bin-debug"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: morgen-bin 3.2.2-2 (Thu 08 Feb 2024 01:24:50 PM CET)
==> Cleaning up...
doas (...) password: 
loading packages...
warning: morgen-bin-3.2.2-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (2)       Old Version  New Version  Net Change

morgen-bin        3.2.2-2      3.2.2-2        0.00 MiB
morgen-bin-debug               3.2.2-2       10.47 MiB

Total Installed Size:  296.25 MiB
Net Upgrade Size:       10.47 MiB

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.

1 2 3 Next › Last »