Package Details: mconnect-git 426.3991150-2

Git Clone URL: (read-only, click to copy)
Package Base: mconnect-git
Description: KDE Connect protocol implementation in Vala/C for non-KDE desktops
Upstream URL:
Licenses: GPL2
Conflicts: mconnect
Provides: mconnect
Submitter: American_Jesus
Maintainer: nicolarevelant
Last Packager: nicolarevelant
Votes: 21
Popularity: 0.46
First Submitted: 2016-03-24 23:21 (UTC)
Last Updated: 2024-01-14 15:59 (UTC)

Latest Comments

1 2 3 Next › Last »

guglovich commented on 2022-03-14 11:30 (UTC) (edited on 2022-03-14 11:30 (UTC) by guglovich)

(mconnectctl:23561): WARNING : 14:24:40.768: main.vala:301: communication with service failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mconnect was not provided by any .service files

Error when attempting to scan devices

guglovich commented on 2021-10-14 20:00 (UTC)

@deboeckj Thank you very much

deboeckj commented on 2021-10-13 18:26 (UTC)

@guglovich that seems to be a change in the vala compiler...

I've fixed it in the sourcecode itself

guglovich commented on 2021-10-11 12:46 (UTC) (edited on 2021-10-11 12:47 (UTC) by guglovich)

../src/mconnect/transfer-manager-proxy.vala:99.9-99.36: warning: unhandled error `GLib.Error'

    jp.bus_unregister (this.bus);

../src/mconnect/transfer-manager-proxy.vala:65.9-65.38: warning: unhandled error `GLib.Error'

    tproxy.bus_register (this.bus);

Compilation failed: 2 error(s), 11 warning(s) ninja: build stopped: subcommand failed.

duffydack commented on 2021-06-21 17:30 (UTC)

Updated, all good. Nice.

ValHue commented on 2021-06-21 16:35 (UTC) (edited on 2021-06-21 16:36 (UTC) by ValHue)

@duffydack: I have left the one I was using. I have checked that the value it generates is higher, so if a system update is done, mconnect will update. (gdb has been added)

ValHue commented on 2021-06-21 15:41 (UTC)

@duffydack @jonathannerat: I do not know if it will be appropriate, I have reviewed the AUR rules to see how to proceed in this case, and I have not found something similar to this situation.

I think it is best to keep the package name and update the source. In the end it is about indicating which program provides, and it will remain mconnect (the git version)

As soon as I find a gap, I upload a new update, the problem I see is that when generating the version of the package, a lower value than the current one comes out and then the update is not forced, I suppose that if that happens I will resort to epoch

duffydack commented on 2021-06-21 15:04 (UTC) (edited on 2021-06-21 19:01 (UTC) by duffydack)

@ValHue @jonathannerat: Personally I'd just replace the source, keep the pkg name as-is.