| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <47307B3D.2010708@redhat.com> Date: Tue, 06 Nov 2007 08:33:33 -0600 From: Eric Sandeen <sandeen@...hat.com> To: Thierry Vignaud <tvignaud@...driva.com> CC: Theodore Tso <tytso@....edu>, ext4 development <linux-ext4@...r.kernel.org> Subject: Re: [PATCH e2fsprogs] - remove timestamps from .po files Thierry Vignaud wrote: > Eric Sandeen <sandeen@...hat.com> writes: > >> Another one that's been in RH/Fedora specfiles a while. >> Remove timestamps from .po files to avoid multilib conflicts. >> It ain't pretty but it works. > > Sorry but that's insane. > > Pos should not be updated on build. They should only be updated by > upstream developers instead. This enable translators to catch up and > prevent such hackery Hrm, good point. > Your spec file should not contain "make -C po update-po" in the first > place. > This is a fedora bug, not an e2fsprogs one IMHO. > > You introduced your own multi-lib in the first place... Apparently there was some issue with this, once upon a time, which resulted in our rpms needing to update the po files... I guess I need to do a bit more code archeology / research. It looks like sct added this when the pkg updated to 1.36, though there is no comment about why. I inherited lots of history when I got e2fsprogs, so please forgive me as I work through it. :) One question though, then - what is the existing timestamp removal mechanism for, then? -Eric - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists