natkr/flickboard
7
64
Fork
You've already forked flickboard
16

F-Droid can't build #427

Open
opened 2026年05月18日 08:26:20 +02:00 by licaon-kter · 3 comments

When ready to release, after tagging, clone a fresh repo, checkout the tagged commit, build a fresh APK to upload.

Did you do that or used an archive?

META-INF/version-control-info.textproto
1c1,5
< generate_error_reason: NO_VALID_GIT_FOUND
---
> repositories {
> system: GIT
> local_root_path: "$PROJECT_DIR"
> revision: "1466b4ffbe2ad554c3d20aae87fede6a6fb91225"
> }
When ready to release, after tagging, clone a fresh repo, checkout the tagged commit, build a fresh APK to upload. Did you do that or used an archive? ``` META-INF/version-control-info.textproto 1c1,5 < generate_error_reason: NO_VALID_GIT_FOUND --- > repositories { > system: GIT > local_root_path: "$PROJECT_DIR" > revision: "1466b4ffbe2ad554c3d20aae87fede6a6fb91225" > } ```
Owner
Copy link

Hm, that's very strange..

When ready to release, after tagging, clone a fresh repo, checkout the tagged commit, build a fresh APK to upload.

I usually just build it in-place in my usual worktree after verifying that it's clean.

(I realize that that's a fallible process, but it shouldn't fail in that way...)

Hm, that's very strange.. > When ready to release, after tagging, clone a fresh repo, checkout the tagged commit, build a fresh APK to upload. I usually just build it in-place in my usual worktree after verifying that it's clean. (I realize that that's a fallible process, but it shouldn't fail in *that* way...)
Owner
Copy link

Aah, fun. Their stamping seems to fail because it doesn't support packed refs. I have to run off to work now, but I'll try to sort this out later today.. in the meantime, you should be able to repro the existing apk by running git pack-refs --all.

Aah, fun. Their stamping seems to fail because [it doesn't](https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:build-system/gradle-core/src/main/java/com/android/build/gradle/internal/tasks/ExtractVersionControlInfoTask.kt;l=84-87;drc=24548ccac3813558373462f04d14e6738141624d) support [packed refs](https://git-scm.com/docs/git-pack-refs). I have to run off to work now, but I'll try to sort this out later today.. in the meantime, you should be able to repro the existing apk by running `git pack-refs --all`.
Owner
Copy link

Should be fixed in v0.3.4.1. Sorry about that!

Should be fixed in [v0.3.4.1](https://codeberg.org/natkr/flickboard/releases/tag/v0.3.4.1). Sorry about that!
Sign in to join this conversation.
No Branch/Tag specified
main
spike/old/layout-editor-v1
spike/hct-colour-sliders
features/binary-landscape-keyboard-alignment
v0.3.4.1
v0.3.4
v0.3.4-beta1
v0.3.3
v0.3.3-beta1
v0.3.2
v0.3.2-beta2
v0.3.2-beta1
v0.3.1
v0.3.1-beta2
v0.3.1-beta1
v0.3.0.1
v0.3.0
v0.2.7
v0.2.7-beta7
v0.2.7-beta6
v0.2.7-beta5
v0.2.7-beta4
v0.2.7-beta3
v0.2.7-beta2
v0.2.7-beta1
v0.2.6.1
v0.2.6
v0.2.6-beta1
v0.2.5
v0.2.5-beta5
v0.2.5-beta4
v0.2.5-beta3
v0.2.5-beta2
v0.2.5-beta1
v0.2.4
v0.2.4-beta2
v0.2.4-beta1
v0.2.3
v0.2.2
v0.2.2-beta11
v0.2.2-beta10
v0.2.2-beta9
v0.2.2-beta8
v0.2.2-beta7
v0.2.2-beta6
v0.2.2-beta5
v0.2.2-beta4
v0.2.2-beta3
v0.2.2-beta1
v0.2.1
v0.2.1-beta9
v0.2.1-beta8
v0.2.1-beta7
v0.2.1-beta6
v0.2.1-beta5
v0.2.1-beta4
v0.2.1-beta3
v0.2.1-beta2
v0.2.1-beta1
v0.2.0.1
v0.2.0
v0.2.0-beta5
v0.2.0-beta4
v0.2.0-beta3
v0.2.0-beta2
v0.2.0-beta1
v0.1.11
v0.1.11-beta2
v0.1.11-beta1
v0.1.10
v0.1.10-beta1
v0.1.9
v0.1.8
v0.1.8-beta11
v0.1.8-beta10
v0.1.8-beta9
v0.1.8-beta8
v0.1.8-beta7
v0.1.8-beta6
v0.1.8-beta5
v0.1.8-beta4
v0.1.8-beta3
v0.1.8-beta2
v0.1.8-beta1
v0.1.7
v0.1.7-beta2
v0.1.7-beta1
v0.1.6
v0.1.6-beta7
v0.1.6-beta6
v0.1.6-beta5
v0.1.6-beta4
v0.1.6-beta3
v0.1.6-beta2
v0.1.6-beta1
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.13
v0.0.12
v0.0.11
v0.0.10
v0.0.9
v0.0.8
v0.0.7
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
bug
Something isn't working
bug/gesture
A gesture recognition problem
bug/motorola
Bugs that have only been confirmed on Motorola devices
bug/samsung
Bugs that have only been confirmed on Samsung devices
bug/unreproducible
A bug that I can't seem to reproduce, more information is required
cleanup
Maintenance tasks
community
Community/discussion infrastructure
design
Involves design question(s)
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
emoji
Emoji-related features
feature
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
layout
Add or change a keyboard layout
meta
Questions about the process itself
question
Further information is requested
wontfix
This will not be worked on
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
natkr/flickboard#427
Reference in a new issue
natkr/flickboard
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?