Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

Use RFC5322 Timestamp Format #351

Closed
corygalyna opened this issue Jun 23, 2023 · 6 comments
Closed

Use RFC5322 Timestamp Format #351

corygalyna opened this issue Jun 23, 2023 · 6 comments
Assignees
@hollowaykeanho
Labels
Bug Case is about a technical glitch. Critical Red alert. High attention needed. HestiaHUGO All Hestia Hugo related matter. NON-Backward Compatible Solution is NOT backward compatible. Released Implementation got released and shipped.

Comments

@corygalyna
Copy link
Member

Description

Please provide a short description of what you have encountered below.

Appearently, Debian 12 uses a different time stamp format for its default presentation. We best use RFC 5322 format like Mon, 14 Aug 2006 02:34:56 -0600.

Command is: date --rfc-email.

Expected Behavior

Please specify the expected behavior of your usage below.

Consistent date format usage.

Current Behavior

Please specify the current behavior of software below.

very custom format.

Steps to Reproduce (COMPULSORY)

Please specify all the steps required to re-produce the problem.

Attachments

Please drag and drop the necessary data files (e.g. screenshot, logs, etc)
below.
@corygalyna corygalyna added Bug Case is about a technical glitch. Critical Red alert. High attention needed. NON-Backward Compatible Solution is NOT backward compatible. HestiaHUGO All Hestia Hugo related matter. labels Jun 23, 2023
@corygalyna corygalyna changed the title Debian 12 Uses A Different Timestamp Use RFC-Email Timestamp Jun 23, 2023
@corygalyna
Copy link
Member Author

@hollowaykeanho , I know we're about to release but can we include this feature as well? It's non-backward compatible. Debian 12 (bookworm) produced a different date format causing inconsistencies.

@hollowaykeanho
Copy link
Member

I didn't notice that... yeah but it will have slight delay. It should be included and stick to a consistent format.

@corygalyna
Copy link
Member Author

TQ.

@hollowaykeanho
Copy link
Member

I will do this after every pages are finalized and published first. It's a breaking change.

@hollowaykeanho hollowaykeanho added the Doing Someone is working on the case. label Jun 23, 2023
@hollowaykeanho hollowaykeanho self-assigned this Jun 23, 2023
@hollowaykeanho hollowaykeanho changed the title Use RFC-Email Timestamp Use RFC5322 Timestamp Format Jun 23, 2023
@hollowaykeanho
Copy link
Member

Implemented in 6100b53

@hollowaykeanho hollowaykeanho added Done and Pending Release Completed and staging for next release. and removed Doing Someone is working on the case. labels Jun 24, 2023
@hollowaykeanho
Copy link
Member

Released in version v.1.2.0.

@ZORALab ZORALab locked as resolved and limited conversation to collaborators Jun 26, 2023
@hollowaykeanho hollowaykeanho added Released Implementation got released and shipped. and removed Done and Pending Release Completed and staging for next release. labels Jul 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hollowaykeanho hollowaykeanho

Labels
Bug Case is about a technical glitch. Critical Red alert. High attention needed. HestiaHUGO All Hestia Hugo related matter. NON-Backward Compatible Solution is NOT backward compatible. Released Implementation got released and shipped.
Projects
No open projects
ZORALab's Hestia Project
Status: [ DELIVERED ] v1.2.2 and before
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hollowaykeanho @corygalyna