[ISSUE] [fetchmail] bad timestamp in case of tzoffset%60!=0

[ISSUE] [fetchmail] bad timestamp in case of tzoffset%60!=0

[riddicc]

[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]

New issue by riddicc on void-packages repository

https://github.com/void-linux/void-packages/issues/55035

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.18_1 x86_64 GenuineIntel uptodate hold FFF

### Package(s) Affected

fetchmail-6.4.30_5

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Reported by @rriddicc via Gitlab #49. https://gitlab.com/fetchmail/fetchmail/-/issues/49
Fixed in 6.5.0: https://gitlab.com/fetchmail/fetchmail/-/blob/11ce732103548fbfef957530db4210daa72f78ae/NEWS
i suggest to upgrade to 6.5.2, since 6.4 is not supported anymore...

### Expected behaviour

If the UTC offset is 00:00:37 (e. g. because the system time is TAI (International Atomic Time)),
then the timestamp "12:34:56+00:00:37" (which is TAI) should become "12:34:19+00:00" (which is UTC).

Motivation: Since I do not like smeared seconds or minutes with 59 or 61 seconds, I use a special timezone file.
https://titan.wgboome.org/tai.html

### Actual behaviour

Currently fetchmail makes "12:34:56+00:00" out of "12:34:56+00:00:37",
which moves the time 37 seconds in the past on a box
that is proud of its +/-2msec system clock jitter... 😋

My workaround (a wrapper which sets TZ=UTC) is a little uncomfortable...

### Steps to reproduce

1. install TAI timezone file
2. run fetchmail
3. look at the timestamps added by fetchmail

Re: [ISSUE] [CLOSED] [fetchmail] bad timestamp in case of tzoffset%60!=0

[ahesford]

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Closed issue by riddicc on void-packages repository

https://github.com/void-linux/void-packages/issues/55035

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.18_1 x86_64 GenuineIntel uptodate hold FFF

### Package(s) Affected

fetchmail-6.4.30_5

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Reported by @rriddicc via Gitlab #49. https://gitlab.com/fetchmail/fetchmail/-/issues/49
Fixed in 6.5.0: https://gitlab.com/fetchmail/fetchmail/-/blob/11ce732103548fbfef957530db4210daa72f78ae/NEWS
i suggest to upgrade to 6.5.2, since 6.4 is not supported anymore...

### Expected behaviour

If the UTC offset is 00:00:37 (e. g. because the system time is TAI (International Atomic Time)),
then the timestamp "12:34:56+00:00:37" (which is TAI) should become "12:34:19+00:00" (which is UTC).

Motivation: Since I do not like smeared seconds or minutes with 59 or 61 seconds, I use a special timezone file.
https://titan.wgboome.org/tai.html

### Actual behaviour

Currently fetchmail makes "12:34:56+00:00" out of "12:34:56+00:00:37",
which moves the time 37 seconds in the past on a box
that is proud of its +/-2msec system clock jitter... 😋

My workaround (a wrapper which sets TZ=UTC) is a little uncomfortable...

### Steps to reproduce

1. install TAI timezone file
2. run fetchmail
3. look at the timestamps added by fetchmail

Re: [fetchmail] bad timestamp in case of tzoffset%60!=0

[ahesford]

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/55035#issuecomment-2833849983

Comment:
As we don't ship a TAI zonefile and this is an upstream bug that will be reconciled with a software update, this is not a Void bug.