public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep
Date: Mon, 12 Oct 2015 13:16:00 -0000	[thread overview]
Message-ID: <561BB2A4.2030009@dronecode.org.uk> (raw)
In-Reply-To: <1442937170-17580-1-git-send-email-jon.turney@dronecode.org.uk>

On 22/09/2015 16:52, Jon Turney wrote:
> (Further note: autodep is broken in upset.  Many package which should have a
> dependency on _update-info-dir do not have one, and only 19 packages do, so this
> is not working as intended at the moment.
>
> Yes, this means that the autodep on the cygwin package isn't working correctly,
> either.)

While I still think this needs replacing with something better, this 
particular issue was actually quite straightforward to fix, so I fixed 
this on sourceware yesterday.

The results given by the package search web page were inaccurate for a 
short while, while packages were re-scanned to check autodeps.

There are now 155 packages which depend on _update-info-dir.

  parent reply	other threads:[~2015-10-12 13:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:53 Jon Turney
2015-09-22 15:53 ` [PATCH setup 2/3] Remove unfinished, unused support for 'autodep:' lines in setup.ini Jon Turney
2015-09-22 15:53 ` [PATCH setup 3/3] Add support for 'trigger:' " Jon Turney
2015-09-22 15:54 ` [PATCH setup 1/3] Remove unused regex code Jon Turney
2015-09-22 17:33 ` [PATCH setup 0/3] Setup replacement for incver_ifdep Achim Gratz
2015-09-23 17:17   ` Jon Turney
2015-09-23 18:09     ` Achim Gratz
2015-10-12 13:16 ` Jon Turney [this message]
2015-10-12 17:38   ` Achim Gratz
2015-10-15 13:18     ` Jon Turney
2015-10-15 18:01       ` Achim Gratz
2015-10-19 15:41         ` Corinna Vinschen
2015-10-19 17:21           ` Achim Gratz
2015-10-20 10:21             ` Corinna Vinschen
2015-11-23 15:14               ` Jon Turney
2015-11-23 18:54                 ` Achim Gratz
2015-11-24 16:59                   ` Jon Turney
2015-11-24 18:44                     ` Achim Gratz
2015-11-26 10:11                       ` Corinna Vinschen
2015-11-26 18:12                         ` Achim Gratz
2016-01-28 17:33                         ` Jon Turney
2016-01-28 18:06                           ` Achim Gratz
2016-01-28 18:41                             ` [GOLDSTAR] " Corinna Vinschen
2016-01-29 16:37                               ` Andrew Schulman
2016-01-28 18:42                           ` Ken Brown
2016-01-28 20:06                             ` Eric Blake
2016-01-28 20:17                               ` Ken Brown
2016-01-28 20:22                                 ` Eric Blake
2016-01-29 14:22                                   ` Jon Turney
2016-01-29 14:53                                     ` Ken Brown
2016-01-29 19:17                                       ` Achim Gratz
2016-01-29 21:34                                         ` Ken Brown
2016-02-06 14:29                                       ` Ken Brown
2016-02-06 15:31                                         ` Jon Turney
2016-02-06 15:52                                           ` Jon Turney
2015-11-23 15:14         ` Jon Turney
2015-10-19 15:33   ` [GOLDSTAR] " Corinna Vinschen
2015-10-19 21:06     ` Andrew Schulman

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=561BB2A4.2030009@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@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).