public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: autoconf packaging error
Date: Tue, 15 Nov 2011 13:57:00 -0000	[thread overview]
Message-ID: <4EC26FB0.2070600@cwilson.fastmail.fm> (raw)
In-Reply-To: <CAEhDDbDCx3MPN-RZZ9Eo1_EWr2mbdxx9_qKbgmwzYQ0Rd4G+PA@mail.gmail.com>

On 11/15/2011 5:06 AM, Csaba Raduly wrote:
> Hi all,
> There seems to be a packaging error in autoconf (autoconf2.5-2.68-1
> according to cygcheck -f /usr/share/man/man1/autoconf-2.68.1.gz).
> The shorter names for the man pages point to non-existent files:
>
> The symlinks don't appear in the output of cygcheck -l autoconf2.5; I
> suspect the post-install script.

Yes, there's a bug in /etc/postinstall/autoconf2.5.sh:


#!/bin/bash -e

# make unversion man pages
pushd /usr/share/man/man1 >/dev/null 2>&1
for fn in autoconf autoheader autom4te autoreconf autoscan \
         autoupdate config.guess config.sub ifnames
do
         rm -f ${fn}.1.gz 2>/dev/null || /bin/true
-       ln -fs ${fn}-2.67.1.gz ${fn}.1.gz 2>/dev/null || /bin/true
+       ln -fs ${fn}-2.68.1.gz ${fn}.1.gz 2>/dev/null || /bin/true
done
popd >/dev/null 2>&1


For now, the short term workaround is to make the indicated change, and 
re-run the script manually (perhaps in an elevated shell).

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2011-11-15 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 10:06 Csaba Raduly
2011-11-15 13:57 ` Charles Wilson [this message]

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=4EC26FB0.2070600@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).