Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Update F-Droid repository

Ideas, future talk, development

2

2

1186

Log in to reply

S
sandman last edited by

Are there any plans to do this?
1 Reply Last reply
Reply Quote 0
rfc2822 developer last edited by rfc2822
Hello @sandman!
1. We can’t update the F-Droid repository. That’s the job of F-Droid people. We don’t have any influence on that.
2. What we can do is to help the F-Droid people to get up-to-date information about the source code location etc.
We have already done so: https://gitlab.com/fdroid/fdroiddata/merge_requests/1023/diffs

By the way, we’re not related to F-Droid in any way and everybody can submit merge requests to fdroiddata. You can do so yourself, too
1 Reply Last reply
Reply Quote 0

Tweets by DAVx5App

Similar topics

N

build from source with local ical4j
Ideas, future talk, development • • Nodgaizuad

2

0
Votes

2
Posts

9
Views

Hello,

Unfortunately, it’s not that easy. I guess you would have to exclude the dependency ical4j from ical4android and include a new submodule (= the downloaded local ical4j) instead.
proposal to improve manual sync usability
Ideas, future talk, development • • TheOtherDoctor

2

0
Votes

2
Posts

13
Views

@TheOtherDoctor A note on the brute-force approach which other apps (example: Synker) use - providing a (possibly power-draining) desktop widget just to enforce they maintain a handle to run processes which Android otherwise does not like them to… honestly, when having to decide to either further struggle with an unwilling device or just sacrifice a bit of runtime for now… the latter is a tempting alternative.
Д

Implement RFC 7809 (Time Zones by Reference)
Ideas, future talk, development • enhancement postponed • • Дилян Палаузов

12

0
Votes

12
Posts

22
Views

Д

Here one current example: I schedule in August 2020 a meeting, targeted for Fuji, for 2020-11-11 and send an .ics invitation, bundling tz definitions. Afterwards the Fuji experts change DST rules, so that the switch does not happen on 2020-11-08 but on 2020-12-20. The UTC offset calculations, included in the .ics invitation, are therefore for that meeting wrong. Nobody thinks on regenerating and resending the .ics file with new tz data. If the OS gets updates, then that event might be presented correctly, if the .ics interpreter ignores the bundled TZ definitions, if the .ics interpreter sees no bundled timezone definitions, or if the .ics interpreter shows to the user, that the bundled TZ definitions are outdated, and there are two possible times for the start.

There is no ultimate right way on technical level to prevent troubles here, not bundling the time zone definitions in the .ics file saves band width.

See also https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/fiji-dst-end-date-correction-update-now-available/ba-p/1669658 and https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/interim-guidance-on-2020-time-zone-updates-for-fiji/ba-p/1766806 .

1 / 1