this post was submitted on 13 Sep 2023
8 points (100.0% liked)

F-Droid

8069 readers
23 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
8
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
[โ€“] Moonrise2473@feddit.it 4 points 1 year ago (1 children)

Maybe the signature doesn't match?

Like you installed from GitHub (developer signature) and then you're trying to install an update from fdroid (fdroid, different signature)

[โ€“] kixik@lemmy.ml 1 points 1 year ago

Nope, I only install F-Droid provided apps from F-Droid. When changing that, like when moving Newpipe from the F-Droid provided one to the Newpipe repo, I have to uninstall it 1st.

Now, the issue is not about signature. It's about "defining" a permission, which BTW, I can't tell what that exactly means. In my mind defining is not quite the same as trying to acquire, and the later is more reasonable for an app to me, and can't understand how come an app can define a permission. But oh well, perhaps the error message is not as accurate.