From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: remaining missing packages in 64-bit release
Date: Sun, 14 Jul 2013 02:38:00 -0000 [thread overview]
Message-ID: <20130714023820.GA5371@ednor.casa.cgf.cx> (raw)
In-Reply-To: <pj04u8dquigggua1p2s3dr9oa3p8f04e4e@4ax.com>
On Sat, Jul 13, 2013 at 09:44:40PM -0400, Andrew Schulman wrote:
>> upset: *** warning - package openbox requires nonexistent package xprop
>> upset: *** warning - package openbox requires nonexistent package xsetroot
>> upset: *** warning - package python3-pyqt4 requires nonexistent package python3-dbus
>> upset: *** warning - package svn_load_dirs requires nonexistent package perl_vendor
>> upset: *** warning - package xinit requires nonexistent package xrdb
>
>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.
I'm trying to minimize the number of gotchas in rolling out x86_64 and
having missing packages is one that we should be able to relatively
easily fix.
cgf
next prev parent reply other threads:[~2013-07-14 2:38 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 [this message]
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
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=20130714023820.GA5371@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).