F-Droid

8147 readers

32 users here now

F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.

Website | GitLab | Mastodon

Matrix space | forum | IRC

founded 3 years ago

MODERATORS

fossdd@lemmy.ml

testman@lemmy.ml

Etar not updating on f-droid (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by kixik@lemmy.ml to c/fdroid@lemmy.ml

9 comments fedilink hide all child comments

When updating f-droid, and etar I believe is trying to update from 1.0.34 to 1.0.35, the following error shows up:

Error installing Etar - Opensource Calendar

Error - 112: The system failed to install the package because it s attempting to define a permission that is already defined by some existent package

Not sure what's going on, since there's no mention of which other package has already defined the permission Etar is trying to define. Also, 1.0.34 works fine, and what's advertised as new:

Add url field
Bug fixes
New translatios

So I don't see anything about permissions, :(

Is this happening to others? Any work around, other than waiting for the issue to go away on a future release?

Edit: There's a reported issue on Etar's github: F-Droid Version 1.0.35 Will Not Install, which seems to affect LOS, and therefore LOS for microG (what I use)

you are viewing a single comment's thread
view the rest of the comments

[–] danileonis@lemmy.ml 3 points 1 year ago (1 children)

Not an Etar user but you can try to use Obtainium for update.

[–] kixik@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (1 children)

Perhaps, I just read about Obtainium, hehe. Thanks for the hint. At this point I'd like to understand what's the issue first, because I'd like to still install it from F-Droid (I would do it with obtainium that way), and I can't tell right now if the issue is on the app, or on the F-Droid build, and to me it's really curious that the error says "defining" instead of "trying to acquire", which doesn't seem like something an app would do. Perhaps it's just a F-Droid message, and not an app installing one. Can't tell. But as I'd like to keep using F-Droid, then perhaps it's good to see if it's a temporal issue just with the last release on F-Droid, that release of the app itself, or something that will remain.

BTW, I use apkgrabber for a few apps from apkmirror, and obtainium might perfectly be an option...

Edit: Just found out it's the app having issues with LOS, and therefore LOS for microG. See the edit on my original post. Thanks !

[–] danileonis@lemmy.ml 1 points 1 year ago

I use Obtainium for apps not on F-Droid or as a backup uploader for this type of cases. You can also try to use an alternative app for F-Droid, I usually prefer Droidi-fy,