Release on F-Droid
Opened this issue · 10 comments
Answering to your ping on the other side (I'm currently not active at F-Droid): Funny there's a badge in your readme pointing to a 404 on F-Droid, but no badge pointing to mine 😜
Why would the signing certificate change? That makes updates impossible, as you might know. And the current certificate looks fine to me.
Answering to your ping on the other side (I'm currently not active at F-Droid): Funny there's a badge in your readme pointing to a 404 on F-Droid, but no badge pointing to mine 😜
Why would the signing certificate change? That makes updates impossible, as you might know. And the current certificate looks fine to me.
Somehow I expected to be on F-Droid earlier. 🤣
I added links to IzzyOnDroid now.
I am sorry to read about the problems at the F-Droid orga.
Unfortunately I did not put the certificate into my password manager and do not have access at the moment. 🙈
I will contact Heinrich about this because he might have the keystore.
Thanks @CrazyMarvin – looking forward to hear back from you then. And as for signing keys, recommended reading: How to keep your key safe and what measures to take for the event of loss? Written by someone you might know 😉
Thanks @CrazyMarvin – looking forward to hear back from you then. And as for signing keys, recommended reading: How to keep your key safe and what measures to take for the event of loss? Written by someone you might know 😉
That is a great article from an awesome person! 😂
Heinrich was able to help me get the original signing key so upgrading for IzzyOnDroid users will be easy going. 😌
That is a great article from an awesome person! 😂
Thanks! 🤗 And glad you enjoyed it 😄
Heinrich was able to help me get the original signing key so upgrading for IzzyOnDroid users will be easy going. 😌
Yay 🥳 Wonderful!
Btw, thanks for adding Fastlane! Just leaving a note that your full_description.txt will render a bit "strange" at F-Droid, and weird with my repo (when I'd try rendering it as Markdown). Not sure what format that should be, it's quite a little mix 😜
- lines 5-9 would render fine as bullet-point list would you use an asterisk (
*) instead of a check mark (√) as leading character - similarly, lines 17-22 if they were preceded by an empty line (and using an asterisk)
- lines 24-27 would render as a single paragraph. If you wanted that as multiple paragraphs, those would need to be separated by empty lines between them. Same for lines 29-30 and 13-14
Of course I could take the text as-is, just replacing each line break with <br> as F-Droid does. But honestly, that wouldn't look half as good 😉 So I wait your decision (and maybe adjustment) before enabling the full description here.
Btw, thanks for adding Fastlane! Just leaving a note that your
full_description.txtwill render a bit "strange" at F-Droid, and weird with my repo (when I'd try rendering it as Markdown). Not sure what format that should be, it's quite a little mix 😜
- lines 5-9 would render fine as bullet-point list would you use an asterisk (
*) instead of a check mark (√) as leading character- similarly, lines 17-22 if they were preceded by an empty line (and using an asterisk)
- lines 24-27 would render as a single paragraph. If you wanted that as multiple paragraphs, those would need to be separated by empty lines between them. Same for lines 29-30 and 13-14
Of course I could take the text as-is, just replacing each line break with
<br>as F-Droid does. But honestly, that wouldn't look half as good 😉 So I wait your decision (and maybe adjustment) before enabling the full description here.
Thanks for the hint, @IzzySoft. Please check if my adjustments look fine. The file is using HTML consistently now.
Thanks! That looks fine for my repo (in which I've now set it to be rendered as Markdown). Note however that F-Droid will rather take it as-is, replacing each newline with <br> and then use the result as HTML – so be prepared for "blank lines" inside the bullet-point lists there. Will render absolutely fine with my repo, though, which properly converts it to HTML and then removes all line breaks (resulting in a single line of proper HTML to avoid fdroidserver from doing its <br> thingy).
Thanks! That looks fine for my repo (in which I've now set it to be rendered as Markdown). Note however that F-Droid will rather take it as-is, replacing each newline with
<br>and then use the result as HTML – so be prepared for "blank lines" inside the bullet-point lists there. Will render absolutely fine with my repo, though, which properly converts it to HTML and then removes all line breaks (resulting in a single line of proper HTML to avoid fdroidserver from doing its<br>thingy).
May you please open a PR with your suggestion? I am not 100% sure what you mean.
Metadata Remover is available on F-Droid now. 🥳