Arch Linux User Repository

I have downgraded the AUR package to 0.13.0 while we wait for blueprint-compiler to be updated. Thank you to those who reported the latest build's failure to build.

0.14.1 fails with:

[25/28] Generating data/resources/blueprints with a custom command
FAILED: data/resources 
/usr/bin/blueprint-compiler batch-compile data/resources/. ../data/resources ../data/resources/ui/about.blp ../data/resources/ui/attachment.blp ../data/resources/ui/call_message_item.blp ../data/resources/ui/channel_messages.blp ../data/resources/ui/channel_item.blp ../data/resources/ui/channel_item_compact.blp ../data/resources/ui/channel_list.blp ../data/resources/ui/channel_info_dialog.blp ../data/resources/ui/dialog_clear_messages.blp ../data/resources/ui/dialog_unlink.blp ../data/resources/ui/error_dialog.blp ../data/resources/ui/setup_window.blp ../data/resources/ui/linked_devices_window.blp ../data/resources/ui/message_item.blp ../data/resources/ui/preferences_window.blp ../data/resources/ui/shortcuts.blp ../data/resources/ui/text_entry.blp ../data/resources/ui/window.blp ../data/resources/ui/submit_captcha_dialog.blp ../data/resources/ui/new_channel_dialog.blp ../data/resources/ui/components/context_menu_bin.blp ../data/resources/ui/components/emoji_picker.blp ../data/resources/ui/components/attachment_audio.blp ../data/resources/ui/components/attachment_file.blp ../data/resources/ui/components/attachment_photo.blp ../data/resources/ui/components/attachment_video.blp ../data/resources/ui/components/item_row.blp ../data/resources/ui/components/time_divider.blp ../data/resources/ui/components/letter_divider.blp ../data/resources/ui/components/label.blp ../data/resources/ui/components/indicators.blp
error: Adw.AlertDialog is not a Adw.MessageDialog, so it doesn't have responses
at ../data/resources/ui/dialog_clear_messages.blp line 10 column 3:
  10 |  responses [
     |  ^

For me the build seems to hang after cargo finishes:

   Compiling flare v0.11.1 (/home/marcin/.cache/yay/flare/src/flare-0.11.1)
    Finished release [optimized] target(s) in 7m 58s
(hangs here)

Installing gnome-keyring solves the issue reported at 2023-08-17, 07:22 UTC. Maybe it needs be added to the depends array?

But it is really inconvenient to have to store secrets in gnome-keyring, if I use other methods :-(.

I have freshly built and installed the package.

When I start flare, a popup windows occurs saying

Error

The communication with Libsecret failed

DBus(
    Zbus(
        MethodError(
            OwnedErrorName(
                ErrorName(
                    Str(
                        Owned(
                            "org.freedesktop.DBus.Error.ServiceUnknown",
                        ),
                    ),
                ),
            ),
            Some(
                "The name org.freedesktop.secrets was not provided by any .service files",
            ),
            Msg {
                type: Error,
                sender: UniqueName(
                    Str(
                        Borrowed(
                            "org.freedesktop.DBus",
                        ),
                    ),
                ),
                reply-serial: 2,
                body: Signature(
                    "s",
                ),
            },
        ),
    ),
)

Regards!

This package was wrongly marked out-of-date, with a comment about URLs not working. The package is indeed working and is not out-of-date. In future, please create a comment for this kind of concern, rather than making the package out-of-date.

There is another typo:

source=("https://gitlab.com/schmiddi-on-/$pkgname/-/archive/$pkgver/$pkgname-$pkgver.tar.gz")

should be

source=("https://gitlab.com/schmiddi-on-mobile/$pkgname/-/archive/$pkgver/$pkgname-$pkgver.tar.gz")

That has been fixed. My apologies for the typo.

The upstream URL seems to have changed. It's https://gitlab.com/schmiddi-on-mobile/flare not https://gitlab.com/schmiddi-on-mobileii/flare, notice the two ii's in mobileii.

I am not going to rename the binary. The binary is named according to the project itself. If you have an issue with that, I suggest you open an issue there.