Today I've read about Debians Multiarch capabilities for the first time.
Is it possible to use this technique to build deb packages of libraries
for the mingw crosscompile toolchain too?
I have to build Windows executables and therefore need some libraries.
For now, I build and install them loc
Am Wed, 11 Mar 2015 21:16:20 +0500 schrieb Andrey Rahmatullin:
> On Wed, Mar 11, 2015 at 01:27:21PM +0000, Joerg Desch wrote:
>> Switch to 'en'
>> New LOCALE: 'C'
>> Hello World Switch to 'de'
>> New LOCALE: 'C'
>> Hello Wor
Hi.
I'm running Debian Squezze on a small AMD Geode based embedded PC. I need
to use the gettext library independend from the system wide language
settings to toggle the language for strings only.
On my PC, the test runs within a chroot environment als expected. On the
embedded PC, it doesn't
Am Thu, 12 Mar 2015 09:29:01 +0100 schrieb Tomas Pospisek:
> /etc/locale.gen
>
> Also 'man locale'
> *t
OK, the package "locales" wasn't installed by the embedded distribution.
After installing locales and selecting "en_GB.UTF8" as default, my sample
still not use "de_DE.UTF8". So I've called
Am Thu, 12 Mar 2015 09:57:08 + schrieb Colin Watson:
> There is no such locale. Perhaps you meant en_GB.UTF-8 or en_US.UTF-8.
You are right. But this selection isn't needed. ;-)
I've already changed this in my current sample.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian
Am Thu, 12 Mar 2015 09:29:01 +0100 schrieb Tomas Pospisek:
> /etc/locale.gen
The solution was simple. While "dpkg-reconfigure locales" only allows the
selection of one language. I thought that this should be the default. But
instead all not selected entries are not possible.
So the solution wa
Am Thu, 12 Mar 2015 20:24:21 +0100 schrieb Wouter Verhelst:
> I've been fighting with that myself the other day.
> echo $LANGUAGE?
is already unset.
> This is a GNU extension which does have some use, but it *breaks* in
> some non-wrong use cases.
Until now, I'm really happy with the toolchain
Hi. I currently maintain a repository with my own backports for Jessie.
Therefore I have a Release file with a suite entry "stable". Since my
backports should be overwriteable by the official backport repository,
I want change the "name" of the origin von "stable" to "jessie-backports".
How do I
I've just tried it without "Version:" and with "Suite:" and "Codename:"
set to jessie-backports.
After this, "apt-get update" prints the error (jessie expected but jessie-
backports received):
W: Konflikt bei Distribution: http://debian.jdesch.de jessie/ Release
(jessie erwartet, aber jessie-ba
Am Fri, 10 Mar 2017 11:04:40 +0800 schrieb Paul Wise:
> Did you also update your sources.list?
No, because I use the directory name for it. Or isn't an entry with an
trailing slash an directory?
deb http://debian.jdesch.de/repositories/experimental/ jessie/
10 matches
Mail list logo
