Postgres-Fehler beim Upgrade von 3.3 auf 3.4 verursacht durch Locale-Probleme

Falco · 2. Januar 2025 um 01:00

Maybe related to your change @featheredtoast ?

github.com/discourse/discourse_docker

DEV: generate only en_us locales

discourse:main ← discourse:generate-locales

opened 06:53PM - 31 Aug 24 UTC

featheredtoast

+9 -5

Wondering if we really need all locales installed in the base image here. Ins…talling the pre-built locales-all package via apt takes 245MB Generating just c and en_us locales takes 22MB @xfalcox I know it's been a while since the move to debian, but do you remember if this is necessary? One guess I have is the original call to locale-gen was being called a few layers later, with no locale.gen configuration file -- I'm assuming locale-gen en_US used to work, but it doesn't appear to actually do anything in debian given debian's default `/etc/locale.gen` is empty

Thema		Antworten	Aufrufe
Postgresql upgrade error with locale on rebuild Installation	8	1600	8. Juni 2024
Upgrade failed spectacularily Support	25	453	10. Februar 2025
Hundreds of megabytes of apparently duplicate locale .js files Support	7	88	3. April 2025
PostgreSQL 15 update Announcements	104	3434	9. Juni 2025
Major woes upgrading from 1.6.0 to 1.8.0 -- broken site Installation	10	2989	8. November 2017

Postgres-Fehler beim Upgrade von 3.3 auf 3.4 verursacht durch Locale-Probleme

Verwandte Themen