All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4700] New: setlocalversion not working for combination svn/ubuntu 11.10/non-english locale
Date: Mon, 16 Jan 2012 08:59:50 +0000 (UTC)	[thread overview]
Message-ID: <bug-4700-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=4700

           Summary: setlocalversion not working for combination svn/ubuntu
                    11.10/non-english locale
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: fpasch at googlemail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 3974
  --> https://bugs.busybox.net/attachment.cgi?id=3974
patch for setlocalversion

Running buildroot on Ubuntu 11.10 Oneiric Ocelot with German locale from a
private subversion repository...

LANG=C doesn't change the output of svn to english here, hence, the output of
setlocalversion stays empty.

My fix is to change LANG=C to LC_ALL=C (see attached patch)

Simon Pasch

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2012-01-16  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16  8:59 bugzilla at busybox.net [this message]
2012-01-16 12:57 ` [Buildroot] [Bug 4700] setlocalversion not working for combination svn/ubuntu 11.10/non-english locale bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-4700-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.