Skip to content
TheChatArchiveThe Chat Archive
Geminigemini-2.5-pro-exp-03-25-grounding· GoogleHugging Face LMArena Search Arena 24K

Where to publish wrong fingerprint issue for kde f-droid repo

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Perplexitysonar-reasoning-pro-high’s answer.
  1. User

    Where to publish wrong fingerprint issue for kde f-droid repo

  2. Gemini Assistant

    To report an issue with the fingerprint of the KDE F-Droid repository, the primary place to report bugs related to KDE projects is the KDE Bug Tracking System[1][2][3].

    Here's a breakdown of where and why:

    1. KDE Bug Tracking System: Since KDE manages its own F-Droid repository, issues concerning its configuration, including the signing key and fingerprint, fall under their responsibility[1][6]. You should report the bug at https://bugs.kde.org[1][2][7]. When reporting, be specific about the issue, mentioning it relates to the Android F-Droid repository fingerprint.
    2. KDE Community Android/F-Droid Page: KDE provides information about their F-Droid repository, including the correct fingerprint, on their community wiki[1][6]. You might find verification details or contact points there as well. The current fingerprint listed is B3EBE10AFA6C5C400379B34473E843D686C61AE6AD33F423C98AF903F056523F[1][9].
    3. F-Droid Data Issue Tracker: While less likely to be the primary channel for a third-party repository issue like KDE's, the F-Droid data issue tracker on GitLab is used for reporting problems with app metadata within the main F-Droid repository (e.g., outdated apps, incorrect features listed)[10][11]. If the fingerprint issue was related to how F-Droid processes repository metadata in general, this might be relevant, but for a specific key issue of a known third-party repo, reporting directly to the source (KDE) is usually best.

    Recommendation:

    Report the fingerprint issue on the KDE Bug Tracking System (https://bugs.kde.org)[1][3][5]. Provide details such as:

    • The exact repository URL you are using (https://cdn.kde.org/android/fdroid/repo/).
    • The fingerprint you are expecting (e.g., the one listed on the KDE Community page)[1][6].
    • The fingerprint you are actually observing.
    • Where you are seeing the incorrect fingerprint (e.g., in the F-Droid client when adding the repo).
    • The version of the F-Droid client you are using.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.