public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: David Rothenberger <daveroth@acm.org>
To: cygapps <cygwin-apps@cygwin.com>
Subject: Re: remaining missing packages in 64-bit release
Date: Sun, 14 Jul 2013 18:24:00 -0000	[thread overview]
Message-ID: <51E2ECCD.6010007@acm.org> (raw)
In-Reply-To: <51E239B2.8080006@users.sourceforge.net>

On 7/13/2013 10:40 PM, Yaakov (Cygwin/X) wrote:
> On 2013-07-13 21:38, Christopher Faylor wrote:
>> On Sat, Jul 13, 2013 at 09:44:40PM -0400, Andrew Schulman wrote:
>>> There are of course other packages that could be called missing because
>>> they haven't been ported to x86_64 yet, and other packages that
>>> depend on
>>> them can't be released until they are.
>>
>> Ah, good point.  I'll check tomorrow and make a more comprehensive list.
> 
> Attached.

Since this is based on source packages, it misses that gcc-java is not
yet in the distribution, hence pdftk cannot be built.

-- 
David Rothenberger  ----  daveroth@acm.org

McEwan's Rule of Relative Importance:
        When traveling with a herd of elephants, don't be the first to
        lie down and rest.

  parent reply	other threads:[~2013-07-14 18:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-13 19:05 Christopher Faylor
2013-07-13 22:15 ` David Rothenberger
2013-07-14 12:14   ` Ken Brown
2013-07-14  1:44 ` Andrew Schulman
2013-07-14  2:38   ` Christopher Faylor
2013-07-14  5:40     ` Yaakov (Cygwin/X)
2013-07-14  6:24       ` David Stacey
2013-07-14  7:32         ` Yaakov (Cygwin/X)
2013-07-14 13:12           ` David Stacey
2013-07-14  9:30       ` Achim Gratz
2013-07-14 18:06         ` Yaakov (Cygwin/X)
2013-07-15  1:17         ` Christopher Faylor
2013-07-15  3:47           ` Yaakov (Cygwin/X)
2013-07-15 15:11           ` Christopher Faylor
2013-07-14 12:28       ` marco atzeri
2013-07-14 18:24       ` David Rothenberger [this message]
2014-04-21 23:49       ` jdzstz
2014-04-22  7:45         ` Corinna Vinschen
2013-07-18 19:03   ` Damien Doligez
2013-07-19  8:58     ` 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=51E2ECCD.6010007@acm.org \
    --to=daveroth@acm.org \
    --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).