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 6164] New: openvpn usage of ip tool from Busybox
Date: Thu,  4 Apr 2013 14:52:28 +0000 (UTC)	[thread overview]
Message-ID: <bug-6164-163@https.bugs.busybox.net/> (raw)

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

           Summary: openvpn usage of ip tool from Busybox
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: aleksandar.zivkovic at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Overview: wrong condition for openvpn configuration on ip application usage

Steps to Reproduce:
Build openvpn without selected package BR2_PACKAGE_IPROUTE2

Actual Results: 
Built application will seek for ip tool in path /bin/ip which is location of
BR2_PACKAGE_IPROUTE2. Location of Busybox version of ip is /sbin/ip

Expected Results:
If openvpn is build without selected package BR2_PACKAGE_IPROUTE2 it should
select Busybox version of ip: /sbin/ip.


Build Date & Platform: BR 2013.02

-- 
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:[~2013-04-04 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 14:52 bugzilla at busybox.net [this message]
2013-04-04 14:53 ` [Buildroot] [Bug 6164] openvpn usage of ip tool from Busybox bugzilla at busybox.net
2013-04-04 16:56 ` bugzilla at busybox.net
2013-05-04 13:55 ` 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-6164-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.