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 7766] logrotate default gzip path is usually wrong
Date: Tue,  6 Jan 2015 14:08:08 +0000 (UTC)	[thread overview]
Message-ID: <20150106140808.6D4C18043A@busybox.osuosl.org> (raw)
In-Reply-To: <bug-7766-163@https.bugs.busybox.net/>

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

Henrik Juul Pedersen <hjp@liab.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Henrik Juul Pedersen <hjp@liab.dk> 2015-01-06 14:08:08 UTC ---
After looking closer into the LSB and FSH, it seems that /bin is actually still
used by the standard, and it states:

The following programs, or symbolic links to programs, must be in /bin if the
corresponding subsystem is installed:
...
gzip    The GNU compression utility (optional)
gunzip    The GNU uncompression utility (optional)
...

So I guess that only looking for gzip in /bin/gzip is correct according to the
standard, and the real issue is why no symlink exist in /bin/ for the two
programs. I'll look into this, and possibly file another bug on the subject.

-- 
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:[~2015-01-06 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 13:48 [Buildroot] [Bug 7766] New: logrotate default gzip path is usually wrong bugzilla at busybox.net
2015-01-06 14:08 ` bugzilla at busybox.net [this message]
2015-01-06 14:20 ` [Buildroot] [Bug 7766] " bugzilla at busybox.net
2015-01-06 14:38 ` bugzilla at busybox.net
2015-01-06 14:43 ` bugzilla at busybox.net
2015-01-06 17:05 ` bugzilla at busybox.net
2015-01-06 20:18 ` 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=20150106140808.6D4C18043A@busybox.osuosl.org \
    --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.