On Sun, 6 May 2012, Steve Langasek wrote:
> On Wed, May 02, 2012 at 10:23:41PM +0200, Santiago Vila wrote:
> > I think including .mo files in a library package is wrong by itself,
> > with or without multiarch, because the next sonme bump will force
> > the new library package to conflict the old
On Wed, May 02, 2012 at 10:23:41PM +0200, Santiago Vila wrote:
> I think including .mo files in a library package is wrong by itself,
> with or without multiarch, because the next sonme bump will force
> the new library package to conflict the old one, which is contrary
> to the general design of l
Santiago Vila wrote:
> I remember well the bug by Neil Williams:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468209
>
> where he asked --endianness to be documented, as he was thinking about
> using it in his embedded projects to override the current msgfmt default of
> always creating l
[ Adding Steve Langasek, multiarch architect in Debian, to Cc list ].
On Thu, 3 May 2012, Bruno Haible wrote:
> Hi Santiago,
>
> > A long time ago, people working on embedded systems in Debian had the
> > idea that it would be a good thing to have .mo files in the same
> > endianness as the arch
severity 671257 wishlist
thanks
El 02/05/12 20:56, Paul Martin escribió:
Package: gettext
Version: 0.18.1.1-6
Severity: important
Tags: l10n
msgfmt produces binary files which vary dependent on the endianness of
the system you build on.
As localization files are supposed to be placed in /usr/s
Package: gettext
Version: 0.18.1.1-6
Severity: important
Tags: l10n
msgfmt produces binary files which vary dependent on the endianness of
the system you build on.
As localization files are supposed to be placed in /usr/share/ this
means that packages with localized strings fail the requirement
6 matches
Mail list logo
